Admin User

How can I create a user that can "manage-blog", like an admin of the system

You need the knowledge of laravel crude operations to do this. It doesn't necessarily mean that the function should be available in Adminlte you downloaded

See https://laravel.com/docs/5.8/authorization


Discrepanies regarding the position of spawning

Hi Team,
I am trying to find suitable spawning points for my vehicle for the respective scenario using simple_vehicle_control. If I roam around using manual_control.py in external control and find a suitable junction and provide those coordinates as initial position in my xosc file with the same map, my vehicle is getting spawned at a different location. Anyone experienced this issue
Desktop (please complete the following information):

OS: [e.g. Ubuntu 18.04]
CARLA Version [e.g. CARLA 0.9.11]
Python version [e.g. 2.7]
Version [e.g. 0.9.11]

Additional context
Add any other context about the problem here.

Be careful, that OSC is right-handed, but CARLA left-handed. Either you use "CARLA:" at the start of the XOSC description field, or you have to invert the y coordinate.
https://github.com/carla-simulator/scenario_runner/blob/master/Docs/openscenario_support.md#general-openscenario-setup


Support Deequ 2.0.0 (Spark 3.1) and 2.0.1 (Spark 3.2)

Related issues

#31
#70
#90

Related PRs

#96
#75
#32

Changes
In order to support latest deequ releases, a few adjustments were necessary:

[x] Added deequ 2.0.0-spark-3.1 and 2.0.1-spark-3.2 to the list of supported deequ/Spark versions
[x] Adapted CategoricalRangeRule and FractionalRangeRule to include extra arguments for deequ>=2.0.0.
[x] Improved tests to ensure functionality for suggestions

Additionally, a few technical debts were addressed

[x] Now using SparkContext to retrieve the currently installed Spark version (no need to set SPARK_VERSION environment variable)
[x] Added a Github workflow to test the library with multiple Spark versions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hey, @gucciwang!
Wanted to hear your thoughts on this PR. Let me know if there's anything else we could do to enable this support for Deequ>=2.x 😃
Thanks!

Can't wait for the fix of #70

🥺

Is there a test report (if not from CI) that we can review? Just to make sure everything passes.

@chenliu0831 You can check the reports of tests here while I'm addressing your suggestions. As soon as we merge it, I'd expect to see them running on awslabs/pydeequ. :)

@chenliu0831 You can check the reports of tests here while I'm addressing your suggestions. As soon as we merge it, I'd expect to see them running on awslabs/pydeequ. :)

Thanks, please just post a final link again when you are ready, I will review & approve

Done! Here is the last run of the CI workflow for c410f72

Hi are you going to release the python package soon ?

Hi, are you expecting to give support for spark 3.2.1, and thus, databricks runtime 10.4?


add builder/hyperv-vmcx

Issue
fixes https://github.com/mayn/packerlicious/issues/66
see PR for original work https://github.com/mayn/packerlicious/pull/86
re-merging to preserver original author's credit

Coverage increased (+0.1%) to 82.387% when pulling ce2de476f3e4d4d6f25090c7cce5b449b9b94dc7 on mayn-issue66 into 17603ccf39fe65f5622e49e6a1ff0fcc4e7f5163 on master.


feat: edit "thing" assets metadata

Proposed Changes

allow to edit metadata and service-SD of thing asset type

Added don't merge label for now, as it is not a current priority.


MDAO mutates the class specific it "of" and adds "ids" to it.

This really shouldn't happen.  If were missing some feature from ID support lets file a ticket for that rather than monkey-patch classes on the fly.
Relevant line:  https://github.com/foam-framework/foam2-experimental/blob/master/src/foam/dao/MDAO.js#L79
@kgrgreer

Offending commit: a736c585913938eb75c77a0f97abce6a621bebed

Indices are composites (chains), so I should be able to just ask the system to build an Index for the ID and set it to be my delegate without me having to know if it's a multi-part ID or a single-part.

This predates IDSupport, IIRC, and I'm looking at it now

Original title: MDAO sets this.of$cls.ids = ['id'];  It shouldn't mutate the class.

This also includes the final refactoring to change the names of some of the index setting methods.

Related tasks broken out: #134, #135


What is the reason for node.collect(node) ?

Thanks for this great lib!
I was wondering why the api for this call is node.collect(node)?
Since it's called on the same object couldn't it be node.collect()?

The reason is that custom functions (like collect) are not copied on cloning.
And you calling .collect(node) on template node returned from h function, not on the cloned one.
For nodes, that are not cloned and used directly, it could be reasonable, but not consistent with API.
I think clone-collect can be considered as default usage pattern, that's why API implemented in favor of this.

Here is one example:
https://github.com/Freak613/stage0/blob/master/examples/sierpinski/app.js#L49
Check out examples folder, it demonstrates this pattern very well.


Errors when building directories

Hello. I am having issues building the release shared directory for x32 build in VS 2022. As directed i used the x86 native tools comman prompt to run build the directory.  I made sure NASM and perl are installed and include paths are in my environment variables.
I initialized the directory with perl Configure VC-WIN32 --prefix=C:\Out\DLL\x32\Release --openssldir=C:\Out\SSL
After which it generated the make file. after which i ran nmake clean to make sure that i start a clean build before running nmake. The problem  is that i keep getting inconsistent errors regardless of how many times i run it. I was building from the master directory from which i successfully build the shared and static release directories for x64 builds. The errors were the same when i tried building the debug directories so i switched to 1.1.1.stable directory and was successful in building the rest except the release shared directory for x32 build. I error i keep getting is attached below. Please help

Internal errors of compiler indicate some HW problem with your machine or the compiler itself having some bug(s). I am sorry but I do not think we can help here much more.

Closing since this is marked as resolved.


Documentation cleanup and updating (new server API, and server launch switches)

Because there are new APIs overlays and admin UIs can use to get smashgg data, the docs need to be updated

Things to update:

SmashGG endpoints (docs/api.md)
!serverconfig "global" call (docs/api,md and docs/overlays.md)
@scoreman/server launch switches (packages/server/README.md)
Update sample return responses (docs/api.md) with the new fields (player status, and commentator enable/disable)
Document how to enable/disable/configure auth on POST /api/scoreboard (the file is in packages/server/data/users.json.sample). This can be a whole new file within the docs dir, like docs/auth.md
General revision of all the README.md in every package

Things to update:

SmashGG endpoints (docs/api.md)
!serverconfig "global" call (docs/api,md and docs/overlays.md)
@scoreman/server launch switches (packages/server/README.md)
Update sample return responses (docs/api.md) with the new fields (player status, and commentator enable/disable)
Document how to enable/disable/configure auth on POST /api/scoreboard (the file is in packages/server/data/users.json.sample). This can be a whole new file within the docs dir, like docs/auth.md
General revision of all the README.md in every package


caught TypeError: Cannot read properties of undefined (reading 'onPlayerVolumeChanged')

I'm seeing this error randomly, its not constant.  When it happpens it stops the ds/player from working and throws me a "black" screen of doom:
source is this:
,
a.prototype.onPlayerVolumeChanged = function(t) {
this.adUi.onPlayerVolumeChanged(t),
this.sdkImpl.onPlayerVolumeChanged(t)
}

Hello @spormeon ,
Possibly, do you have a test case that reproduces the issue 100% of the time? You can email more info to<EMAIL_ADDRESS>Thank you,
Jackson
IMA SDK team

emailed it to you

Hello @spormeon ,
Thank you for sharing the test page. Testing ~30 times, I did see the player stall with a black screen once. However, I did not see an error thrown related to:
a.prototype.onPlayerVolumeChanged = function(t) {
  this.adUi.onPlayerVolumeChanged(t),
  this.sdkImpl.onPlayerVolumeChanged(t)
}

If you could capture the VAST, or VAST url that triggers the error 100% of the time, that may be the best way to proceed.
Thank you,
Jackson
IMA SDK team

i might of got rid of the volumechnage errors by some tweaks i pushed live the othe day,  I'll test it  and see if it come back

i don't know why, it only happens if we use video.js greater than v7.21.3

Hello @spormeon ,
Any updates on being able to reproduce this issue?
Thank you,
Jackson
IMA SDK team


PyPDF failed to extract text from some PDFs. Maybe slate3k could be the PDF extractor lib?

Hi!
I had some issues extracting PDF texts with PyPDF. Turns out that it was extracting only the footer text of the document. I tried to fix it, but with no lucky. Then I tried slate3k and it worked like a charm.
Do you think there is space for it on datasciente-tools?

Sure! Add it to both CPU and GPU Dockerfiles.
Sent from my iPhone

On 4 Nov 2018, at 02:06, Tiago de Oliveira Stutz<EMAIL_ADDRESS>wrote:
Hi!
I had some issues extracting PDF texts with PyPDF. Turns out that it was extracting only the footer text of the document. I tried to fix it, but with no lucky. Then I tried slate3k and it worked like a charm.
Do you think there is space for it on datasciente-tools?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


minor AttributeDefinition#marshallAsElement() javadoc fix

marshallAsElement lies!

Linux Build 1966 is now running using a merge of 63ec21aa5801006d87f34c0ad1f725911bbe4aa7

Windows Build 1516 is now running using a merge of 63ec21aa5801006d87f34c0ad1f725911bbe4aa7

Core - Full Integration Build 1106 is now running using a merge of 63ec21aa5801006d87f34c0ad1f725911bbe4aa7

Linux Build 1966 outcome was SUCCESS using a merge of 63ec21aa5801006d87f34c0ad1f725911bbe4aa7
Summary: Tests passed: 3207, ignored: 71 Build time: 0:25:24

Windows Build 1516 outcome was FAILURE using a merge of 63ec21aa5801006d87f34c0ad1f725911bbe4aa7
Summary: Execution timeout (new); tests passed: 2932, ignored: 58; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:07
Build problems:
Execution timeout
Process exited with code 1

Core - Full Integration Build 1106 outcome was SUCCESS using a merge of 63ec21aa5801006d87f34c0ad1f725911bbe4aa7
Summary: Tests passed: 2877, ignored: 377, muted: 1 Build time: 0:50:04


Skip packaging tests

When tests were not included in the Dockerfile
the src directory was being flattened leading
to incorrect paths.
Change-type: patch
Signed-off-by: Kyle Harding<EMAIL_ADDRESS>

@balena-ci I self-certify!


What does this mod do?

The main goals of the mod were to make the balance of ranged weapons more consistent, and to make archery more skill-based than it is by default.
In vanilla VS, arrows had the issue that at higher metal tiers, they were becoming extremely inefficient compared to spears, as shown in this table. The mod fixed the efficiency of spears at 200% of arrows no matter the tier, to make the cost advantage of spears more reasonable.
The spear throw attack was also easily spammable and started with high damage at flint but scaled very poorly with better materials, which in some ways made the flint spear the best one even for well equipped characters. I made high-tier spears deal more damage, and added cooldown to ranged attacks to stop spear spam from dominating fights so much.
In vanilla the bow is also fairly inaccurate, and past about 50 blocks it can be entirely up to RNG whether you hit or miss. The mod replaced this inaccuracy with mouse drift, so that a good player could compensate and shoot accurately even at long distances. After a while of getting used to it, I could hit a bighorn sheep at 80 blocks fairly reliably, and I'm sure a good archer could stretch it a little further still. I also made the spear a little more short-ranged, but mostly removed its accuracy penalty when running to make up for it.
Unfortunately I didn't finish the mod because 1.14 dropped as I was working on it, and I didn't have the time to test how the mod would be affected by the addition of steel and classes. I also wasn't quite happy with how the mouse drift and cooldown worked, those could use some improvement as well.

Update 1.15 (pre-releases) recently released by the way


Try out an operation macro

This introduces an operation! macro which reduces the amount of boiler plate around declaring operations considerably.
This is how it looks when called:
operation! {
    CreateCollection,
    client: DatabaseClient,
    collection_name: String,
    partition_key: PartitionKey,
    ?consistency_level: ConsistencyLevel,
    ?indexing_policy: IndexingPolicy,
    ?offer: Offer
}

And it expands to:
#[derive(Debug, Clone)]
pub struct CreateCollectionBuilder {
    client: DatabaseClient,
    collection_name: String,
    partition_key: PartitionKey,
    consistency_level: Option<ConsistencyLevel>,
    indexing_policy: Option<IndexingPolicy>,
    offer: Option<Offer>,
    context: Context,
}

impl CreateCollectionBuilder {
    pub(crate) fn new(
        client: DatabaseClient,
        collection_name: String,
        partition_key: PartitionKey,
    ) -> Self {
        Self {
            client,
            collection_name,
            partition_key,
            consistency_level: None,
            indexing_policy: None,
            offer: None,
            context: Context::new(),
        }
    }

    setters! {
        consistency_level: ConsistencyLevel => Some(consistency_level),
        indexing_policy: IndexingPolicy => Some(indexing_policy),
        offer: Offer => Some(offer),
        context: Context => context,
    }
}

#[cfg(feature = "into_future")]
impl std::future::IntoFuture for CreateCollectionBuilder {
    type IntoFuture = CreateCollection;
    type Output = <CreateCollection as std::future::Future>::Output;
    fn into_future(self) -> Self::IntoFuture {
        Self::into_future(self)
    }
}

/// The future returned by calling `into_future` on the builder.
pub type CreateCollection =
    futures::future::BoxFuture<'static, azure_core::Result<CreateCollectionResponse>>;

This would ensure all of our operation builders follow the same pattern.
Some current limitations:

Does not work for pageable operations
Does not work for operations that require a generic param

I believe both of these limitations are pretty easy to overcome, but I wanted to see what folks thought.
Thoughts?

@bmc-msft any thoughts on what we should use for option instead of the ??

Not at this time.  It's livable and given it's only for internal use, we can move to it and adjust if we need to.
It would be good to document the macro with the example you provided.

Ok I'm happy where this ended up. There are about 1000 fewer lines of operations code in Cosmos, and this will only grow as we add more operations from other SDKs.
The following is the syntax we currently have. In the interest of keeping the macro definition simple I'd like to avoid getting too fancy, but we could certainly improve some things. I'll make note of some ideas. Also, please note that the usage below is the most gnarly it can possibly be (i.e., it uses all the features of the macro for instruction purposes). No actual usage is this complex.
operation! {
    #[stream] // This instructs the macro to avoid generating the `IntoFuture` definition and instead assume it's a stream
    ListAttachments<T: Serialize + Send>,
    client: DocumentClient, // Which client is used always comes next
    document: T,  // Then a list of all the required options. We could require the user to annotate these with `#[required]`
    ?consistency_level: ConsistencyLevel // Then all the optional options marked by `?`. If we require the use of `#[required]` then we could drop the `?` here.
    #[skip] // This instructs the follow field to not generate a setter automatically. This is useful when you want a more complex setter
    partition_key_serialized: String
}

Thoughts?


dde-polkit-agent: init at 0.2.1; dpa-ext-gnomekeyring: init at 0.1.0

Motivation for this change

Add dde-polkit-agent (PolicyKit agent for Deepin Desktop Environment)

Add dpa-ext-gnomekeyring (GNOME keyring extension for dde-polkit-agent)

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build deepin.dde-polkit-agent deepin.dpa-ext-gnomekeyring

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: deepin.dde-polkit-agent, deepin.dpa-ext-gnomekeyring
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: deepin.dde-polkit-agent, deepin.dpa-ext-gnomekeyring
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0
shrinking /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0/lib/polkit-1-dde/plugins/libdpa-ext-gnomekeyring.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0/lib
patching script interpreter paths in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0
checking for references to /build in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0...
postPatchMkspecs
/nix/store/igv5xlyj414jp408f7svab8n8bq5xxlp-dde-polkit-agent-0.2.1
/nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0

Success on aarch64-linux (full log)
Attempted: deepin.dde-polkit-agent, deepin.dpa-ext-gnomekeyring
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0
shrinking /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0/lib/polkit-1-dde/plugins/libdpa-ext-gnomekeyring.so
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0/lib
patching script interpreter paths in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0
checking for references to /build in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0...
postPatchMkspecs
/nix/store/2mp0d8klnzbvnawmjj5hfx2bcf0nnafr-dde-polkit-agent-0.2.1
/nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0

@GrahamcOfBorg eval

@GrahamcOfBorg build deepin.dde-polkit-agent deepin.dpa-ext-gnomekeyring

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: deepin.dde-polkit-agent, deepin.dpa-ext-gnomekeyring
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: deepin.dde-polkit-agent, deepin.dpa-ext-gnomekeyring
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0
shrinking /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0/lib/polkit-1-dde/plugins/libdpa-ext-gnomekeyring.so
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0/lib
patching script interpreter paths in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0
checking for references to /build in /nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0...
postPatchMkspecs
/nix/store/2mp0d8klnzbvnawmjj5hfx2bcf0nnafr-dde-polkit-agent-0.2.1
/nix/store/kkgx64mfz02d9x4hvfc01kkvagy6nll8-dpa-ext-gnomekeyring-0.1.0

Success on x86_64-linux (full log)
Attempted: deepin.dde-polkit-agent, deepin.dpa-ext-gnomekeyring
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0
shrinking /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0/lib/polkit-1-dde/plugins/libdpa-ext-gnomekeyring.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0/lib
patching script interpreter paths in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0
checking for references to /build in /nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0...
postPatchMkspecs
/nix/store/igv5xlyj414jp408f7svab8n8bq5xxlp-dde-polkit-agent-0.2.1
/nix/store/pnz2vd0l916nrbn46r99v6f036nfbr43-dpa-ext-gnomekeyring-0.1.0

@xeji I think it is ok now. It seems that grahamcofborg-eval was failing because of libgnome_keyring3. After replacing it by gnome3.libgnome-keyring it succeeds.


fixed Ember 2.0 deprecation

Your change looks good, not sure why tests broke here

@wcurtis The build failure will likely be fixed by updating ember cli, e.g. see https://github.com/sweettooth/ember-cli-stripe/pull/20 which does exactly that.
Let me know if I can do anything to help get this released, thanks! :)

should be fixed with 1.0


gce: allow looking for images in a different project

Tested on staging, and it worked as expected. :tada:

To make this work, you need to go into Permissions on the project that contains the images, and add the GCE account that the worker uses with a Viewer role.

What does this look like across projects? what kind of account is the worker in project using, that you can specify in the other?

The workers are generally using service accounts, so you specify the service account identifier (usually something like username@project-name.iam.gserviceaccount.com).

THIS.
IS.
SO.
FRIGGIN.
AWESOME.
!.


add premium client functionality

before ask for client name in sale option, include a new question about if the client is premium or not.

if the answer is No, continue flow as is

if the answer is Yes,
create a premiumClient object which extends from Client,
it has a points attribute and its pay method is the same as parent client but for each 10€ sales, it adds 1 point. e.g. if sale 35€, premiumClient gets 3 points.
show its points earned after the sale total amount

set issue label as enhancement to be tracked

commit message with verb + #numberIssue + details

include screenshot in issue once the fix is working and code has been pushed to main branch

wait for QA validation

Lines of code:

Console output:

ok
ok
ok
ok
ok
great job, you got +1 in UF4P1


Templates necessary for taggable single select with async search

Reproduction Link
fiddle
Steps to reproduce
I am trying to implement a taggable single select with an async search on strings. When the fiddle has :multiple="true" and the behavior is expected.
Expected behaviour
When setting :multiple="false", I cannot determine the correct combination of slots and properties to be able to delete a currently selected value. I can style the selected option, however I cannot determine the appropriate template for enabled remove functionality.
Actual behaviour
The remove functionality must be manually implemented in single select and hence the option cannot be unselected. You can overwrite the tag with either a new tag or a new async search value, but the form behavior is unexpected and unintuitive.

Great catch! I think we really need the clear button mentioned in #915. Closing this one, since it will be solved once the clear button is implemented.


[6.0] Sema: Report public conformances to non-publicly imported protocols

Exportability checking for non-public imports relies on classic access-level checks for some of the work. However while conforming to a local internal protocol from a public type is allowed, we should disallow it for imported types even when they are imported as internal.
Track exportability issues on conformances to protocols separately from the general category. Use that information to improve the diagnostics and report these issues for access-level on imports.

Scope: Affects users of access-level on imports
Risk: Medium, most of these issues should already be reported by swiftinterface verification but this may error on some that are not verified.
Reviewed by @tshortli
Cherry-pick of #74142
Resolves rdar://128420980

@swift-ci Please test


Add support for jump to definition for stdlib/Foundation symbols

This work involves generating an interface view for a module.
Working out the location of the symbol within this generated file.
Somehow passing all of this in a response.
How this is all done and how much of it should be up to sourcekit-lsp is undefined at this point in time. I've basically added this as a placeholder for work to be done in the future, once we have a better idea what that work should be.

I see SourceKit-LSP already supplies the path to the .swiftinterface file in the textDocument\definition response. If SourceKit-LSP could provide an actual position in that file and we had a method of combining the .swiftinterface and the related .swiftdoc we could possibly do a lot of the work for this on the VS Code side.

rdar://99329577

See https://github.com/swift-server/vscode-swift/issues/408 for update


feature-friend-request

Story: As a user I should be able to send friend requests to other users#3

Thank you Neena. We just discussed most of your comments. Also, since chaat development is now parked, I will not continue the discussion here.


version is missing in init.pyi

Describe the bug
Mypy tells me that __version__ doesn't exist for sqlalchemy, but it's just missing in the __init__.pyi
Expected behavior
__version__  should be defined
To Reproduce
import sqlalchemy

print(sqlalchemy.__version__)

Versions.

OS: Linux
Python: 3.7.1
SQLAlchemy: 1.4.18
mypy: 0.902
SQLAlchemy2-stubs: 0.0.2a2

Thanks for reporting. If you could contribute a fix it would be great!

Sure, I'll do so :-)

thanks!


v2_key no longer exists by default

Depends on: https://github.com/ManageIQ/manageiq/pull/4108
@kbrock Please review, @Fryguy helped me on both 4108 and this one.

good job @jrafanie


Incorporate ICDO mappings from progenetix

Currently we have ICDO mappings souirced fro NCIT, of the form `ICDO:nnnn/n'
progenetix has more complete mappings
https://github.com/progenetix/ICDOntologies/tree/master/current
TODO: determine consistency of these two
We will likely want to map each cancer term in mondo to a pair icdot/icdom as in the above.
E.g.
https://github.com/progenetix/ICDOntologies/blob/master/current/icdom-84303%2Cicdot-C34.9.yaml
equivalents:
- label: Lung mucoepidermoid carcinoma
  id: ncit:C45544
examples:
- labels: Lung mucoepidermoid carcinoma [cell line EPLC-272H]
input:
- label: Mucoepidermoid carcinoma
  id: icdom-84303
- label: Lung and bronchus
  id: icdot-C34.9

This could be formalized by an equivalence axiom between precomposed mondo class and class expression icdom AND disease-has-location some icdot
However, for convenience we may want to make simple xrefs to a conjoined string and have this resolve to URLs like https://progenetix.org/api/ncitcodes/icdom-85003,icdot-C50/
todo: determine license of progenetic mappings
cc @mbaudis
Map each mondo class with an ncit equivalent to a icdot/icdom combo, see https://github.com/progenetix/ICDOntologies/tree/master/current
What is the license of these mappings?

We have identified cases where the mapping is too general e.g
https://github.com/progenetix/ICDOntologies/blob/master/current/icdom-80003%2Cicdot-C44.9.yaml
@nicolevasilevsky will examine all 512 mappings. We will first need to turn this into a google sheet. @paulacarrio has scripts in the tools folder to turn into ods, but we could also do a quick yaml2tsv and load that into a sheet

Note mappings as:

ok
too general
wrong

I made a spreadsheet:
https://docs.google.com/spreadsheets/d/1_6ZX715m3A0Iy9pmPjD_7OtmAAIuxAutFZEuA5XXNdY/edit#gid=356020133
can you move to mondo drive nicole?
this was the script I used:
import yaml
import click

@click.command()
@click.argument('input', nargs=-1)
def create_tsv(input):
    for f in input:
        #print(f)
        with open(f, 'r') as f:
            obj = yaml.load(f, Loader=yaml.SafeLoader)
            if len(obj['equivalents']) > 1:
                raise "too many equivalents"
            x = obj['equivalents'][0]
            icdom = ('_','_')
            icdot = ('_','_')
            for i in obj['input']:
                label = i['label']
                id = i['id']
                if id.startswith('icdom'):
                    icdom = (id, label)
                elif id.startswith('icdot'):
                    icdot = (id, label)
                else:
                    raise "unknown ID type"
                vals = [icdom[0], icdom[1], icdot[0], icdot[1], x['id'], x['label']]
            print("\t".join(vals))
            #print(obj)

if __name__ == "__main__":
    create_tsv()

@mbaudis I am half way done with reviewing the mappings. I'll keep going but do you want to review what I have done so far?
You could highlight cells with any issues or create a new column with notes for issues

@nicolevasilevsky Great - I had done some "random" annotations but will switch to systematic notes.

@nicolevasilevsky line 140 ... break for today; pls. have a look.

@cmungall said this should be lower priority for me to review these mappings. @mbaudis do you have enough feedback from me, at the moment?
Do you know how to make new term requests to NCIt?

@nicolevasilevsky AFAIK @paulacarrio & @qingyao have submitted a list of term requests. But we have now a icdom + icdot <-> NCIt service online, w/ GH repo etc.:

https://progenetix.org/service-collection/ontologymaps
repo https://github.com/progenetix/ICDOntologies
JSON for all current https://progenetix.org/services/ontologymaps?filters=NCIT,icdom,icdot
some documentation ... https://info.progenetix.org/doc/services/ontologymaps.html

There is also some UBERON <-> ICD-O topography.
We actually would much appreciate if:

this is being re-used
becomes interactive w/ contributions for those mapping types - right now we have only subsets which are driven mostly by our own data

I am going to close this as there hasn't been any response in a couple months. Please reopen if still needed, thanks!

@nicolevasilevsky @cmungall  Stale item, but the issue still remains that there is no good representation of ICDO T+M pairs w/ the corresponding NCIT terms.
NCIT now covers most of our combinations, but a direct mapping does not exist anywhere beyond our resource (?). So no idea how to go about this; as indicated, happy to provide/extend the mappings if someone has a way to integrate them in a lookup (?) service or annotation for term equivalence.

I'll bring this up with Chris at one of our Mondo calls in the new year.

Great - thanks! Happy to get looped in if needed.

Hi @mbaudis
I talked to Chris about this and he said we could probably an OWL version of ICD-O  with Koza or LinkML (similar to the way we did this with monochrome) and host it on OLS. We have a lot of other competing priorities though, so I'll come back to this in a couple months and see if our development team can work on this. Thanks!

@nicolevasilevsky Great - please keep me posted; I'd like to help... And preferably LinkML :-)

see also https://github.com/mapping-commons/sssom/issues/222 - can we bump the priority on this?

@mellybelly should we bump the priority on this in favor of other work, like ICD10 mappings, NCIT mappings, MedGen mappings, etc?
If @mbaudis can provide a sssom mapping file instead of the spreadsheet, we can easily add these into Mondo. However, if we need to review all the mappings and create a file ourselves, it will be a big lift and we'll to need deprioritize other work.

@nicolevasilevsky I don't have the resources to provide a sssom'd version; but more than that I wouldn't know how to express the ICD-O pairs correctly. Internally we just concatenate them to get unique keys (icdom-85032::icdot-C50.9 ...) but is there a way to do this in the sssom schema? (real not my area...)
Also: IMO many of the mappings could be done better w/ the current version of NCIt.
So:

I see this as a basis for some collaborative project
an obvious target (besides our data) would be to do this for TCGA (data existing) and ICGC ARGO (data emerging ... @mcourtot ...)
we can easily provide a subset of sane mappings for prototyping/setting this up
I'm not sure how you'd handle the high level mappings where you have the 1:1 correspondence between single ICD-O topography or morphology codes (e.g. "Adenocarcinoma, NOS - 8140/3" == "Adenocarcinoma - NCIT:C2852"); in our concept which requires ICD-O pairs we'd just map all the topography options we encounter

Thanks @mbaudis. Let me discuss with Nico and we can come up with a plan to move forward. :)


Evaluating using My Own Code

Hi!
Thanks for the nice work.
I want to use the three approaches used here for comparison in my own pipeline.
What I do is that

Train a model on my poisoned data.
Evaluate the feature space representation of the training data using the trained model (ResNet-32, so it would be the output of the 'layer3' below).https://github.com/SewoongLab/spectre-defense/blob/ccf594a8ae39fd5c6a077d8696efe19888055a1e/resnet.py#L112.
Then, I use your Julia code to compute the samples that need to be removed for the target label.

Am I right? Because I am getting a mixed performance and I want to double check.

In our paper, we actually save the representations one basic block before layer3. (This is layer 14 in the SequentialImageNetwork.) We are very interested in backdoors that can bypass SPECTRE so if you cannot find a layer that works well, we would be happy to look more closely at why SPECTRE is failing.

Thanks! I am running my experiments with a slightly modified version of ResNet-32, where the BatchNorm2d is done before the shortcut, and I am not sure whether this is the culprit. Interestingly in this case, Spectre works accurately on label consistent attacks and detect all the poisoned data. But on sinusoid attack and badnets it can remove 84% and 87% of the poisoned data, but the remaining 16% and 13% are enough to poison the model after retraining.
Below is the architecture of the blocks that I am using:
(3): BasicBlock(
      (conv1): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
      (bn1): BatchNorm2d(64, eps=1e-05, momentum=0.1, affine=True, track_running_stats=True)
      (conv2): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
      (bn2): BatchNorm2d(64, eps=1e-05, momentum=0.1, affine=True, track_running_stats=True)
      (shortcut): Sequential()
    )

And here is the blocks in the Spectre code:
(14): BasicBlock(
    (bn1): BatchNorm2d(64, eps=1e-05, momentum=0.1, affine=True, track_running_stats=True)
    (conv1): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
    (bn2): BatchNorm2d(64, eps=1e-05, momentum=0.1, affine=True, track_running_stats=True)
    (conv2): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
    (shortcut): Sequential()
  )

Unfortunately, it's not clear to me what effect the different basic block structures might have on the representations. What you can try is pulling representations from various points inside the basic block. This is the idea behind the class BasicBlockSplitter in model.py, although we didn't need to use it in the end for our own experiments.
What you can also try is looking at a PCA pairplot of the representations and see if there is any obvious way to separate the poison and clean points. This lets you determine whether the failure to remove the poison was because

the representations of poison data have no detectable spectral signature, or
the covariance estimation and QUE scoring failed to detect the spectral signature of the poison.


error: use of deleted function

I have a class PhoneExtractor,the header file like:
class PhoneExtractor{         public:                 PhoneExtractor(){}                 PhoneExtractor(string conf_file_name);                 //PhoneExtractor();                 ~PhoneExtractor(); }
I use boost python,the file like:
`using namespace boost::python;
BOOST_PYTHON_MODULE(libextractor)
{
class_("PhoneExtractor",initstd::string())
.def("chainDecode", &PhoneExtractor::chainDecode)
;
}`
But I got error:

/home/mahch/workspace/dep/lib/include/boost/python/object/value_holder.hpp:133:13: error: use of deleted function ‘PhoneExtractor::PhoneExtractor(const PhoneExtractor&)’
BOOST_PP_REPEAT_1ST(N, BOOST_PYTHON_UNFORWARD_LOCAL, nil)

I don't know where I am wrong,can you help me ?

@mahuichao I'm facing the same error. Did you find a way to solve this?


Catch and log exceptions in ObjC (and Swift) plugin registrants

The Java registrant was recently updated to catch and log exceptions during plugin registration, to address the fact that the behavior for an Android plugin throwing was extremely confusing (it and all plugins after it alphabetically just didn't work).
We just had a spate of bugs where a popular plugin shipped a completely-broken-on-iOS version that threw an exception during registration, and the effect was that the app crashed (see https://github.com/flutter/flutter/issues/89859 for an example). If you don't know what to look for, it's not super obvious that the culprit is the plugin, not Flutter. If we catch it we can:

clearly log the problem, including the plugin's name (in this particular case the exception message has the name of the plugin in the class name, but there's no reason for that to always be true)
not crash, so that the behavior is "the broken plugin doesn't work" not "the whole app crashes"

/cc @jmagman

@stuartmorgan is this still a p3?


feat(tencent-mail): add tencent mail connector

Summary

https://cloud.tencent.com/product/ses

Testing

local test, send mail suucess

thanks for contributing @StringKe. we're going to archive this repo in favor of the connectors directory in the Logto monorepo.


Better syntax highlighting

Previously:

Now:

this should have distinctive color.
keywords like super, instanceof, typeof should have proper highlighting.
Would be great if I can tell class/interface/const from each other by color too, currently:

Another thing is it would be great to  have some special highlighting for built-ins like document and console.

OK, something else...
Previously I could at least tell primitives from other constructs, and have a nested object displayed fine...

Now this looks terrible:

My syntax highlighting for JavaScript vanished completely after installing this plugin, my Color Theme is set to Dark+ (default dark), previously it looked like this:

After installing this plugin in everything was white:

I notice now that this repo only mentions TypeScript but the tweet here suggested JavaScript improvements too, either way, if this is only TypeScript it shouldn't really cause issues with other languages?

@octref Thank you for trying out the grammar and reporting the issues.
Most of the issues are theme related rather than issue with grammar and i will file those in Microsoft/vscode repo and reference this back.
this and super are scoped as variable.language but they aren't colorized correctly by the theme.
instanceof, typeof are scoped as keyword.operator and not colorized again the issue with the theme.
I am already talking to vscode folks about the color of typeliteral as part of #173 but I will file a bug just to make sure we are tracking it.
document and console are scoped correctly, its the theme that needs to handle it.

@Jmclerck Can you please provide more information of other extensions installed, vscode version etc so we can investigate this further? I am going to move your issue into separate one just to make sure we are tracking it correctly.

@sheetalkamat Thanks. But as this grammar won't make it to Sep release, I think it'd be better if you can modify the stock theme a bit so it works with well with the grammar, and publish it to marketplace.
Also, Sep release will allow extensions to specify depdendencies -- maybe you can add the theme as a dep for the grammar.
Otherwise it'd be a really bad experiences for users.

@octref I have raised vscode theme bugs to track this and will let bug owner decide how to approach this.
Sorry I don't know if I can help much since the issue isn't in the grammar.

Closing this issue as there are vscode issues to track the underlying issues

@sheetalkamat
I'll give it a try to see if I can build a theme.
Is there a fast way to know the type of each token (like this is variable.language)?
Inspecting the css is really slow...

@octref you could use our test framework

Clone this repo
cd build
npm install
cd ../test
npm install
Add your required code say in cases\test.ts
npm test
It would generate a file called generated\test.baseline.txt, It would have the scopes for the whole file


C4GT Community: Basic Details of TANMAY KUMAR SWAIN

Ticket Contents
Description
Please provide the following basic details to help us understand your background and context better.

Name:
GitHub Username:
LinkedIn Profile:
College/University:
If you feel comfortable, you can also provide additional information such as your area of expertise or any specific information you'd like to share.

Goals

[ ] Adding your basic details

Implementation Details
To implement the changes in the Community.md file on the GitHub repository (https://github.com/Code4GovTech/C4GT/blob/main/Community.md), follow these steps:

Fork the Repository:

Visit the repository (https://github.com/Code4GovTech/C4GT).
Click the "Fork" button in the upper right corner to create a fork of the repository in your GitHub account.

Clone Your Fork:

Open a terminal or command prompt.
Run the following command to clone your fork to your local machine:

     git clone https://github.com/your-username/C4GT.git

Navigate to the Repository:

Change into the repository directory:

    cd C4GT

Edit the Community.md File:

Open the Community.md file in a text editor. You can use any code editor or a simple text editor.
Locate the existing table and replace the details with your own:

        Name
        Your Name

        GitHub
        https://github.com/your-username

        LinkedIn
        https://www.linkedin.com/in/your-linkedin

        College
        Your College/University

Save Changes:

Save the changes to the Community.md file.

Click on the "New pull request" button.
Ensure the base repository is Code4GovTech/C4GT and the base branch is main.
Ensure the head repository is your fork and the compare branch is main.
Click "Create pull request" and provide a meaningful title and description.
Click "Create pull request" again to submit the pull request.
Your changes will now be submitted as a pull request to the original repository, and the maintainers can review and merge them.

Product Name
C4GT
Organisation Name
C4GT
Tech Skills Needed
Markdown
Mentor(s)
@Shruti3004
Complexity
Beginner
Category
Documentation

UPDATE


Add Web Demo & Docker environment

Hey @cszn! 👋
This pull request makes it possible to run your model inside a Docker environment, which makes it easier for other people to run it.  We're using an open source tool called Cog to make this process easier.
This also means we can make a web page where other people can try out your model! View it here: https://replicate.com/cszn/scunet. The docker file can be found under the tab ‘run model with docker’.
We have added some examples, but do claim the page so you can own the page, customise the Example gallery as you like, push any future update to the web demo, and we'll feature it on our website and tweet about it too. Moreover, when the page is claimed, it will be automatically linked to the arXiv website as well (under “Demos”)! You can find the 'Claim this model' button on the top of the page ~
In case you're wondering who I am, I'm from Replicate, where we're trying to make machine learning reproducible. We got frustrated that we couldn't run all the really interesting ML work being done. So, we're going round implementing models we like. 😊

Thanks.


Upgraded to RC2 and Added Provisional Support for Netstandard 1.5

The support for netstandard 1.5 is commented out in project.json. To complete it the following needs to be resolved:

ExtensionMethods.Normalize needs to be changed so that it does not return a dynamic type.
I added a System.Drawing.Color type which is only compiled for #if NETSTANDARD1_5. There is a known colour table which needs to be filled in or known colours can be removed altogether. The choice is yours.

I have added TODO comments for both items so you can find them easily.

Other things to note and do:

netstandard1.5 does contain System.Drawing.Primitives but this does not contain the Color class. I have read somewhere that a cross platform version of System.Drawing is coming eventually but when is unknown.
I forgot to mention that obviously the ColorMapper class will not work on other platforms like Linux and Mac. The correct approach would be to work out the platform and make the OS calls to change the console colours.

A temporary workaround might involve using the current ColorMapper on Windows and switching it to a different one which just picks the nearest looking ConsoleColor to the Color you've asked for.

Hey Muhammad,
Thanks for this update!  I don't have much spare time to work on this at the moment, so I've added you as a collaborator, which (I think) should allow you to merge this PR if you like.  Also, feel free to add your name to the "owners" array in the project.json files.  I'm happy to upload a new version of the NuGet package to the website, just let me know if that needs to be done.
Thanks again for this PR, and apologies for not being more helpful.
-Tom

Still, the upgrade is appreciated.  Thanks for the PR!


Receiving TypeError: undefined

Running this lib for the first time and receiving this Type Error:
TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[14], "react-native-big-calendar").Calendar')

This error is located at:
    in Unknown (at SceneView.tsx:122)
    in StaticContainer
    in EnsureSingleNavigator (at SceneView.tsx:114)
    in SceneView (at useDescriptors.tsx:153)
    in RCTView (at View.js:34)
    in Unknown (at CardContainer.tsx:245)
    in RCTView (at View.js:34)
    in Unknown (at CardContainer.tsx:244)
    in RCTView (at View.js:34)
    in Unknown (at CardSheet.tsx:33)
    in CardSheet (at Card.tsx:573)
    in RCTView (at View.js:34)
    in Unknown (at createAnimatedComponent.js:217)
    in AnimatedComponent (at createAnimatedComponent.js:278)
    in AnimatedComponentWrapper (at Card.tsx:555)
    in PanGestureHandler (at GestureHandlerNative.tsx:13)
    in PanGestureHandler (at Card.tsx:549)
    in RCTView (at View.js:34)
    in Unknown (at createAnimatedComponent.js:217)
    in AnimatedComponent (at createAnimatedComponent.js:278)
    in AnimatedComponentWrapper (at Card.tsx:544)
    in RCTView (at View.js:34)
    in Unknown (at Card.tsx:538)
    in Card (at CardContainer.tsx:206)
    in CardContainer (at CardStack.tsx:623)
    in RCTView (at View.js:34)
    in Unknown (at Screens.tsx:84)
    in MaybeScreen (at CardStack.tsx:616)
    in RCTView (at View.js:34)
    in Unknown (at Screens.tsx:54)
    in MaybeScreenContainer (at CardStack.tsx:498)
    in CardStack (at StackView.tsx:462)
    in KeyboardManager (at StackView.tsx:458)
    in RNCSafeAreaProvider (at SafeAreaContext.tsx:76)
    in SafeAreaProvider (at SafeAreaProviderCompat.tsx:42)
    in SafeAreaProviderCompat (at StackView.tsx:455)
    in RCTView (at View.js:34)
    in Unknown (at StackView.tsx:454)
    in StackView (at createStackNavigator.tsx:87)
    in StackNavigator (at app.routes.js:22)
    in Routes (at routes/index.js:9)
    in EnsureSingleNavigator (at BaseNavigationContainer.tsx:409)
    in BaseNavigationContainer (at NavigationContainer.tsx:91)
    in ThemeProvider (at NavigationContainer.tsx:90)
    in NavigationContainer (at routes/index.js:8)
    in Routes (at App.js:21)
    in PersistGate (at App.js:19)
    in Provider (at App.js:18)
    in App (at renderApplication.js:47)
    in RCTView (at View.js:34)
    in Unknown (at AppContainer.js:107)
    in RCTView (at View.js:34)
    in Unknown (at AppContainer.js:134)
    in AppContainer (at renderApplication.js:40)

Maybe is happening because of some configuration, but I implemented:
at configuration: yarn add react-native-big-calendar
also added: yarn add @types/react @types/react-native

export default () => {
const events = [
    {
      title: 'Meeting',
      start: new Date(2020, 1, 11, 10, 0),
      end: new Date(2020, 1, 11, 10, 30),
    },
    {
      title: 'Coffee break',
      start: new Date(2020, 1, 11, 15, 45),
      end: new Date(2020, 1, 11, 16, 30),
    },
  ];

return(
 <Calendar events={events} height={300} />
)
}

Hi @DavidInojosa , thank you for reporting!
I've fixed it on v1.0.4, so please upgrade your dependency and confirm that it was fixed.


iOS8 -Delay in returning correct currentReachabilityStatus

When I turned internet off, currentReachabilityStatus method returns value NotReachable after 3-4 seconds.
Device- iPhone 5c with iOS8.0 beta

Is there a fix in progress?

Check the V4 branch - its asynchronous & uses block based callback for getting current reachable status:
https://github.com/tonymillion/Reachability/tree/v4dev

Still seeing the same problem (especially with loss of wifi connection) with the v4dev branch on iPhone 6 / iOS 8.3.  Ran the iOSReachabilityTestArc project on the device.  Backgrounded the app, turned off wifi and foregrounded the app again.  A 3 - 4 second delay before the UI catches up.   Any ideas?

@tonymillion it seems to be regression from iOS7. Any updates on this? Can we expected this to be fixed in the future?
Thanks

IMPORTANT: Reachability must use DNS to resolve the host name before it can determine the Reachability of that host, and this may take time on certain network connections.  Because of this, the API will return NotReachable until name resolution has completed.  This delay may be visible in the interface on some networks.

Any word on when the asynchronous changes will make it into master, @tonymillion?

any result for this issue?


Where i can get grid.unit for applying it in setting ?

Hi PinCode!
If I want to setup styleLockScreenButton, in documentations said:

styleLockScreenButton
Button of the lock screen
backgroundColor: colors.turquoise, borderRadius: grid.border, paddingLeft: grid.unit * 2, paddingRight: grid.unit * 2, paddingBottom: grid.unit, paddingTop: grid.unit

I was wondering, where I can get "grid.unit", to use it with other default options?

Hi :)
It's in the grid.ts file.
I'm not exposing it though. It's equal to 16px :)


Add Star Trek - United Federation of Planets flag from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of ShpongleCraft, to add Star Trek - United Federation of Planets flag to CKAN.
Please direct questions about this pull request to ShpongleCraft.

This mod is against KS rules, so I bet it will be deleted. Closing PR.


Clarify REGEXT out-of-scope

The REGEXT working group is chartered to maintain and standardize extensions to EPP, therefore extensions or changes for EPP, including those added by RPP, are explicitly out of scope for the RPP working group.

Found "including those added by RPP" phrase confusing. What does that mean?

Hi @jasdips,
the intention was to mention, that RPP group would not work on EPP extension for the counterparts of RPP functionality not existing in EPP.
Reading it again I also can share your confusion. Would this text work better for you:
The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group.

Perfect.

Pawel,
I don’t get the goal here.  It still has not been determined what is included and not included in RPP based on what has been defined for EPP, including the EPP extensions.  The goal of “RPP Overlap with EPP” should not include explicit out of scope items for the RPP working group in the charter as it related to EPP interoperability.    Please remove this sentence from the charter.
--
JG
@.***
James Gould
Fellow Engineer
<EMAIL_ADDRESS>703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.comhttp://verisigninc.com/
From: Pawel Kowalik @.>
Reply-To: SIDN/ietf-wg-rpp-charter @.>
Date: Friday, November 15, 2024 at 12:31 PM
To: SIDN/ietf-wg-rpp-charter @.>
Cc: Subscribed @.>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36)
Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi @jasdipshttps://secure-web.cisco.com/1mXDjtHI4poiW9Ezwfw2j5yL-YNvz0qOm5lDDai-pzD0GvKNgX1-vghfyOcIGANDLLOe_0KRBn8-TaHG6VCY5auxaDmDEdsA7z9bNbxpyHHw6eAKbj8ZKBmIglxlx-Ws-f-eZN_gKRbibhkvjT8OCQaoKPTZXbezWMgYLARkR3k-Mc5zn3U3BkWO36H7TfLk9XBaNFGDYWxML9uqWK_ow4nQ9RbiA8m4VN1_DChWcF7BjzFubthLgo6kRl-oF53fR5pwbJ5ZM3TCYr5ianDuxk9Y5zQxRH55HddcJUMRaX5o/https%3A%2F%2Fgithub.com%2Fjasdips,
the intention was to mention, that RPP group would not work on EPP extension for the counterparts of RPP functionality not existing in EPP.
Reading it again I also can share your confusion. Would this text work better for you:
The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group.
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1jm507_RwECFJvknsQ2A6yH6a1uqrN4sZFdndavzJoXWlScEJmnDXbxu43MZDnqjkySMPkviuUoRMeUv91sopJzz8uzJOa2SkeSZSml8OZdom8KZ6rfc3PZMr5ESGnpJErp0HFWFnoy21c53KwwtzhwCA6GP8BsEbJhZkdC0bht9Zl0MtficTP6WJGM1bKeDIAM9Sc_nO_mH4S6tI2sfh9hsMbD60kaK__H9xEpHx7cw2yNV9_swJPR9xIMxYsu47Duta7sxIxWdQjVT_3uIzENZ2G7ySrzhujVrk5oNIOGg/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2479492263, or unsubscribehttps://secure-web.cisco.com/1_4CuECJipedKOGmvAFhA3Ay6Ql1uv8pt2OSaR5qcGNFhWEcGz-TdTdA8HU7-Vk8rgtZoHEyOGLjcRB6VPOPV51ykBNNuG0f5PFxJDLcWh_xfEKysPbRx9iHyabsZkGQac6-_3EjbaZiF1cMWcO_jZTY6wNb3yBxlj-04eBA5ilbJ94zaoncv4ITw4NR_fCiiiXc2jM2ZNehE_JAO_aexTvX7CP9MRPbnthTTvlhUJ6U7xbfHWnwA6JYIij_yqP-cvB-4NueqEM2WlwA0a3xBX1Yx9WjGmXJ_zuqDj87z7fU/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNLA5RJOCZFNTTVRNTT2AYUURAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZGQ4TEMRWGM.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The wording means that work on EPP is out of scope for the RPP working group, including creation of EPP extensions that are functional equivalents of RPP.

How about simplifying this to read?
“Creation of EPP extensions is out of scope for the RRP working group.”
We don’t need to specify why the EPP extensions are being created, but that all EPP extension work is out-of-scope for the RRP working group.
--
JG
@.***
James Gould
Fellow Engineer
<EMAIL_ADDRESS>703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.comhttp://verisigninc.com/
From: Andrew Newton @.>
Reply-To: SIDN/ietf-wg-rpp-charter @.>
Date: Friday, November 15, 2024 at 2:50 PM
To: SIDN/ietf-wg-rpp-charter @.>
Cc: rpp-ietf @.>, Comment @.***>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36)
Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
The wording means that work on EPP is out of scope for the RPP working group, including creation of EPP extensions that are functional equivalents of RPP.
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1IHjTslC-ZDDhXZfUnhYQBpQLK0egZ3l4e_uazlNkynxogwyw3Wtb8fGjlLHNowFpIZ0a5w9uAnkkY50nTR8UgQm0lbMtU4Sd337ZP2kOCevTyFrGbEAOoo8qnme1UplC1lrDnXnFnLQUsrIQKP7mnzbh-ZVXD1Dw7p7Qef-Cdjch618CRWxUjM9vbFVqmMYvHdr8uhPX-hJ6HIzSimgXlcU7B5flK6qf6aOwJA5z5EFvsfhqz-f8xJlQODKQj53JUJAorp6YV_st5RAXNEp6uZNS2UogNTU144wvM_x_nRc/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2479811976, or unsubscribehttps://secure-web.cisco.com/1eIo1SFxyc8KViTJW4qg4P9hNWBgXaeJRl4nZWh4u91i4_NCC-1kYBYSmLax8P3Wl9kfwxl2FMEFfH8tgCfoZJx4dEelCnZJd7QlZi97ccjuQloL8SWRNQb3YXisHsDpsESGXE32AnUK0qqMfDG3miql8Wgp8-EifeYeKQhHm61ymwWweLKQuEXgHX5I9YayWh0EqqMvMnoqfgNmlkIe0lTRRCZYOyS6zv0j_gl7I8JHsZxBCe9GlSrAdLfkiX-yEK4cp7TWS2a8HLrEhKBwQmzGRyw05nitbR0nUsrLEXKo/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNJYBQP6F2KM2BUF3VL2AZGANAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAYTCOJXGY.
You are receiving this because you commented.Message ID: @.***>

+1

Maarten
How about simplifying this to read?
“Creation of EPP extensions is out of scope for the RRP working group.”
We don’t need to specify why the EPP extensions are being created, but that all EPP extension work is out-of-scope for the RRP working group.
--
JG
@.***
James Gould
Fellow Engineer
<EMAIL_ADDRESS>703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.comhttp://verisigninc.com/
From: Andrew Newton @.>
Reply-To: SIDN/ietf-wg-rpp-charter @.>
Date: Friday, November 15, 2024 at 2:50 PM
To: SIDN/ietf-wg-rpp-charter @.>
Cc: rpp-ietf @.>, Comment @.***>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36)
Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
The wording means that work on EPP is out of scope for the RPP working group, including creation of EPP extensions that are functional equivalents of RPP.
—
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1IHjTslC-ZDDhXZfUnhYQBpQLK0egZ3l4e_uazlNkynxogwyw3Wtb8fGjlLHNowFpIZ0a5w9uAnkkY50nTR8UgQm0lbMtU4Sd337ZP2kOCevTyFrGbEAOoo8qnme1UplC1lrDnXnFnLQUsrIQKP7mnzbh-ZVXD1Dw7p7Qef-Cdjch618CRWxUjM9vbFVqmMYvHdr8uhPX-hJ6HIzSimgXlcU7B5flK6qf6aOwJA5z5EFvsfhqz-f8xJlQODKQj53JUJAorp6YV_st5RAXNEp6uZNS2UogNTU144wvM_x_nRc/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2479811976, or unsubscribehttps://secure-web.cisco.com/1eIo1SFxyc8KViTJW4qg4P9hNWBgXaeJRl4nZWh4u91i4_NCC-1kYBYSmLax8P3Wl9kfwxl2FMEFfH8tgCfoZJx4dEelCnZJd7QlZi97ccjuQloL8SWRNQb3YXisHsDpsESGXE32AnUK0qqMfDG3miql8Wgp8-EifeYeKQhHm61ymwWweLKQuEXgHX5I9YayWh0EqqMvMnoqfgNmlkIe0lTRRCZYOyS6zv0j_gl7I8JHsZxBCe9GlSrAdLfkiX-yEK4cp7TWS2a8HLrEhKBwQmzGRyw05nitbR0nUsrLEXKo/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNJYBQP6F2KM2BUF3VL2AZGANAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAYTCOJXGY.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/SIDN/ietf-wg-rpp-charter/issues/36#issuecomment-2479837346, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AALSFIEME2FNMEAK6RKP4JT2AZICFAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAZTOMZUGY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Addition to the text was aimed to address #20. I'm ok to go with simple text as well.

The current text says:

The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group.

"any extensions or changes to EPP" covers the creation of EPP extensions. It seems to me and additional sentence of "Creation of EPP extensions is out of scope..." is both unnecessary and more wordy. I am inclined to close this issue absent a compelling reason not do so.

TBH, I find the current paragraph more contextual. But, no strong opinion here if we go with James' suggestion.

We don’t need to repeat the purpose of REGEXT or project the reasons why EPP extension work is out-of-scope.

The concern regarding the interplay between EPP and RPP has been brought up multiple times, so I'd prefer to keep the context. I'll let the AD determine if context needs to be removed.


fix reply time display bug

fix  https://github.com/cofacts/rumors-site/issues/265
createdAt is property of reply, not articleReply

Hello @jojomango thanks for taking a look at the issue!
It turns out that ArticleReply actually have createdAt attribute on the API.
"""The linkage between an Article and a Reply"""
type ArticleReply {
  replyId: String
  reply: Reply

  # ...(omitted)...

  status: ArticleReplyStatusEnum
  createdAt: String
  updatedAt: String
}

Seems that the root cause is that we forgot to include articleReply's createdAt in our GraphQL queries. To be more specific, we forgot to include createdAt in ReplyItemArticleReplyData fragment. Would you take a look and give it a try? Thanks!


remain all support imageset in fast&&stable channel

Signed-off-by: ldpliu<EMAIL_ADDRESS>https://github.com/open-cluster-management/backlog/issues/17465

/unhold

/approve

/approve
/lgtm

/approve

There is no OWNERS file that's why we see this error. Merging pull request.


initial commit with starter files and product offering

No other commits. This was the first one, therefore no risk of problems with a self-merge.


docs: update baidu_qianfan_endpoint.ipynb doc

Description: Updated the docs for the chat integration module baidu_qianfan_endpoint.ipynb
Issue:  #15664
**Dependencies:**N/A

The stream mode of the baichuan model has a bug where it automatically adds the sentence_id when it returns, which may require modifying the source code of this model, I used a try-catch block to skip this Type error and it works fine.

For the other model, baichuan, it is more problematic. Baichuan has updated their API and its usage rules, now they don't use the secret key anymore and the API base and usage rules have completely changed, the baichuan model code libs/community/langchain_community/chat_models/baichuan.py in the langchain community is completely outdated. It is not possible to update the doc for the baichuan model at this monment.

I've removed that file.

I uploaded some changes by mistake, I have reverted it.


Do not backfeed retweets of mentions

This issue is discussed on https://chat.indieweb.org/dev/2018-04-30, search for "retweet").
Summary:

There was a tweet that mentioned my Twitter handle: https://twitter.com/jxxf/status/990787587278295040
When I retweeted that, that tweet did not generate a "repost" webmention, but the exact same "link" webmention as the original tweet.
So I ended up with duplicate webmentions of the same tweet with just different time stamps (original tweet time stamp and retweet time stamp). The author, webmention type, etc. all was the exact same in the two.

This is WM created by bridgy for the retweet: https://brid-gy.appspot.com/post/twitter/kaushalmodi/990803136448253952. It should have looked like this instead: https://brid.gy/repost/twitter/kaushalmodi/990787587278295040/990803136448253952.

thanks for filing!

Thanks!


Transfering learning on custom dataset

I have collected the images of red geranium plant and red azalea plants. Than, I have trained them on alexnet, vgg16 and resnet50. Now, I have converted them onnx and to TensorRT. Now the model classifies it other than azalea or geranium.
For example: The vgg16 classifies as,
class 0580 - 0.045837  (greenhouse, nursery, glasshouse)
class 0706 - 0.031021  (patio, terrace)
class 0738 - 0.818848  (pot, flowerpot)
class 0883 - 0.018097  (vase)
How can I test correct classification as only azalea or geranium.

Hi @priyaganaboor-hash, is your labels.txt listed in alphabetical order?
What does the folder structure of your dataset look like?
What accuracy did PyTorch train your model to?

Hi,

Yes, The labels.txt listed in alphabetical order.

The folder structure of dataset is ,
‣ train/
• azalea/
• geranium/
‣ val/
• azalea/
• geranium/
‣ test/
• azalea/
• geranium/

For all the models I got accuracy between 70 to 80%.

I have trained the network on my local pc, on a custom program, and even converted to .onnx format, in my local PC.  After that, I am running imagenet.py(from the repo) to convert it to TensorRT and display the single image classification on Jetson nano.

What does your labels.txt look like?
Are you specifying --labels=<my-labels-file.txt> on the command line?  Because it appears to be using the default labels.txt from 1000-class imagenet model.
What command line are you using to run the model in imagenet/imagenet.py?

Yes, I am mentioning the --labels in the command-line argument.
NET=models/PlantClassification
DATASET=data/PlantClassification
$ imagenet.py --model=$NET/PlantClassification/vgg16.onnx --input_blob=input_0 --output_blob=output_0 --labels=$DATASET/labels.txt $DATASET/test/geranium/test_img_01.jpg  $DATASET/test/geranium/output.jpg
I didn't understand --input_blob=input_0 --output_blob=output_0  so I tried with and that command thinking image name format.

@dusty-nv, I  have used  -- network=vgg16, is this correct? I saw the default is googlenet so changed it.

Try it without --network, like the following:
imagenet.py --model=$NET/vgg16.onnx --input_blob=input_0 --output_blob=output_0 --labels=$DATASET/labels.txt $DATASET/test/geranium/test_img_01.jpg $DATASET/test/geranium/output.jpg

Hey @dusty-nv
for command,
$ imagenet.py --model=models/PlantClassification/vgg.onnx --input_blob=input_0 --output_blob=output_0 --labels=data/PlantClassification/labels.txt data/PlantClassification/test/azalea/test5.jpeg data/PlantClassification/test/azalea/output.jpeg
I am getting error as,
[TRT]    device GPU, models/PlantClassification/vgg.onnx initialized.
[TRT]    imageNet -- loaded 3 class info entries
[TRT]    imageNet -- didn't load expected number of class descriptions  (3 of 2)
[TRT]    imageNet -- failed to load synset class descriptions  (3 / 3 of 2)
[TRT]    imageNet -- failed to initialize.
jetson.inference -- imageNet failed to load built-in network 'googlenet'
Traceback (most recent call last):
File "/usr/local/bin/imagenet.py", line 55, in
net = jetson.inference.imageNet(opt.network, sys.argv)
Exception: jetson.inference -- imageNet failed to load network
I have only two classes, I dont understand this error.

Hey! @dusty-nv
I just deleted labels.txt  and created new one and used the same above command again, It worked this time.
Thank you so much! You have done a great job.


🙋 Suggestion: Start printing backtrace from panic's position

Looking at the way human-panic handles backtrace, I feel like it would be better to suggest to stop printing unnecessary frames we get from backtrace as it has own calls, and instead jump straight to user code. This is how I made for my lazy panic handlers when backtrace is on https://github.com/DoumanAsh/lazy-panic.rs/blob/master/src/formatter.rs#L189-L202
Expected Behavior
Prints stacktrace from user code
Current Behavior
Prints stacktrace from human-panic and its dependency backtrace
Possible Solution
Calculate where user code's panic starts and start printing from this point (Not sure if it is platform dependent number, but both windows and linux had the same stack trace in my experiments)
Context
I just feel it would improve usability for reports with backtrace

Yea, this is a good idea. I just tagged this in for the 2.0 release, even though its not technically a breaking change.


Add baby anaconda to snake hatch

Details : https://github.com/python-discord/sir-lancebot/issues/821
Relevant Issues

Closes #821

Description

The snake was added in the _utils file and is implemented through a linking of a igmur image
Did you:

[x] Join the Python Discord Community?
[x] Read all the comments in this template?
[x] Ensure there is an issue open, or link relevant discord discussions?
[x] Read and agree to the contributing guidelines?

Done

can i close this pr ?

I ran the linting tho and its a 1 line change afterall 🤔

Looks like the problem is that the "baby cobra" line now has trailing whitespace, if you have the linting set up correctly it should detect that, have you run poetry run task precommit?

Linting process have been completed and i've fixed that from my end

I've added the anaconda logo and here's the preview :

Tysm :)


add new user liujunpeng and new company inspur

Thank you for contributing to openstack/stackalytics!
openstack/stackalytics uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Add CLI argument for extra lines of configuration

We should add a CLI argument to add extra lines of configuration when the bootstrap configuration is applied to the device.
vrnetlab has no aspiration of becoming a generic configuration management system. The focus has always been, and will continue to be, on doing the minimal amount of configuration so that the router can then be configured through NETCONF/YANG. vrnetlab configures this bootstrap config across a serial console which is both slow and error prone so trying to shove a large configuration through that mechanism is a bad idea.
Sometimes however, it can be useful to be able to enter a few extra lines of config and so I think we should have an option for that. Those lines are sent to the device in the bootstrap_config() function, while we are in configuration mode. I.e. the user doesn't need to bother with doing "configure" first or committing the configuration at the end.
I suggest we called the CLI arg --extra-config and that it's a semi-colon separated list of commands to run.

Wouldn't a file be better than trying to cram it all on the command line?

@emjemj in my case no, I think it's easier sticking to a CLI arg and I don't want a bunch of small temp files on disk. One doesn't exclude the other though, we could have a --extra-config-file, cool? Will you implement it? :)

I see where this is going ;) Also, as you've stated before, repeating --extra-config for each line would be prettier than semi-colon separated list of commands. Possibly with a short-hand -X or similar to reduce typing.


Node June 2016 security updates (0.10.46, 0.12.15, 5.12.0, 4.4.6)

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same formula update/change?
[ ] Have you built your formula locally prior to submission with brew install <formula> (where <formula> is the name of the formula you're submitting)?
[x] Does your submission pass brew audit --strict --online <formula> (after doing brew install <formula>)?
[ ] Does your submission adhere to Versions "Acceptable Formulae" guidelines?

Node LTS / Maintenance updates for the latest security release: https://nodejs.org/en/blog/vulnerability/june-2016-security-releases/ (node v6.x is not affected).

Merged. Thanks again @chrmoritz! Appreciated as ever :bow:.


[TS 5.4.0-beta] Tuple type members being perserved

🔎 Search Terms
spread tuple type narrowing
🕗 Version & Regression Information

This changed between versions 5.3.3 and 5.4.0-beta
This changed in 5.4.0-dev.20240120

⏯ Playground Link
https://www.typescriptlang.org/play?ts=5.4.0-beta#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXwHMQMAVAHhID4AKASgC54SBuAKFYAUYcBbLAZxAA6KBAjUA2kVJl+GGFlQEatADTwhm6eSioAnioC6tVvDNCMACxCpq1OP2QQMteAF5K8AN6mzfswD0AfAAegD8vv5geHLw1lDA7vAOThgSAAyGzP5+QfAArEIAzIy6euqFACyMcgpKkTnweeENZtGosRhQWBBJKc5C-BBYYCDUAIy02XmFRfBlFULV8GgA1qg4AO6oEoat-s0RjV098PxQ2PyIWCD8Z-KKBLvZB8FkALTv8Kggm-AgMG4MHgigKS0iAF8pqwgA
💻 Code
declare function getT<T>(): T;

Promise.all([getT<string>(), ...getT<any>()])
   .then((result) => {
        // ^?
      const head = result[0];       // 5.3: any, 5.4: string
         // ^?
      const tail = result.slice(1); // 5.3 any, 5.4: unknown[]
         // ^?
      tail satisfies string[];     // <-- new error in 5.4
   });

Additional information about the issue
More of a 'change report' than a 'bug report', I don't think this was part of the 5.4 beta announcement.

This can be bisected to: https://github.com/microsoft/TypeScript/pull/57031 and it's a bug.
When hovering over all we can see this:
(method) PromiseConstructor.all<[string, ...any[]]>(values: [string, ...any[]]): Promise<[string, ...unknown[]]> (+1 overload)

So how [string, ...any[]] was converted into [string, ...unknown[]] here? The reason is that now instantiateMappedTupleType has this ?? unknownType fallback when computing newElementTypes.
But it's not consistent with how mapped types continue to work today:
type Identity<T> = {
   [K in keyof T]: T[K]
}

type Result = Identity<[string, ...any[]]>
// ^? type Result: [string, ...any[]]

So the problem is that what we see in the original repro is actually not a true any but rather an errorType. And if we play around with it we can see the change in the behavior:
type Identity<T> = {
   [K in keyof T]: T[K]
}

type ErrorType = {}['prop']

type Result = Identity<[string, ...ErrorType[]]>
//   ^? 5.3: any (displayed as `any` but it's an `errorType`) 5.4: [string, ...unknown[]]

The PR to which this has been bisected improves the situation (the output should be a tuple and not an any/errorType) but accidentally maps the thing to [string, ...unknown[]].
Why the errorType has crawled into all of this though? Well, I already have a fix for this 😉 : https://github.com/microsoft/TypeScript/pull/57116


Don't decompile globals

Checks to see if a variable is declared in another file before recompiling it as a block.
If an identifier is defined in another file, it is flagged as a global and will fail decompilation.
Fixes Microsoft/pxt-arcade#554

This works, but it feels a bit hacky so I'm open to suggestions.

I think we should probably move this to annotate.ts. The basic approach would be something like this:

Add an IdentifierInfo interface (see below)
In annotate.ts, add an SK.Identifier case to the switch statement
Call getDecl() on the identifier node and if it returns something, check if decl.getSourceFile().name !== "main.ts"
Inject the IdentifierInfo into the Node (node as any).identifierInfo = // whatever
In the decompiler, consume the injected info in the checkExpression() call.

interface IdentifierInfo {
    isGlobal: boolean;
}

@riknoll I've switched the logic to annotate.ts, but I'm noticing that it's flagging all identifiers that are defined elsewhere as global. Not just variables, but namespaces and functions as well. I don't see any side effects though. Is it a problem to flag these or should we limit flagging to only identifiers defined with the let or const keywords.

Yeah, let's filter it. You can check the kind of the node returned by getDecl() and see if it is a variable declaration


Share weights file？

Hi
Have there anybody successfully transferred the weights file to Keras?
Could you please share ResNet18 keras weights?
Thx!

Hi @bityangke.
The ResNet18 model is successfully transferred! You can check it in the tests/ directory:
https://github.com/nerox8664/pytorch2keras/blob/master/tests/resnet18.py
If you already have pretrained model, just simply load it before convertation.

@nerox8664 Thanks very much！


Termite

https://github.com/termite2/Termite/blob/master/documentation/GPIO/main.tsl

Seem to be little to no guidance on I2C. Closing...


Generate zenodo archive

JOSS prequires that the software is uploaded as a Zenodo archive as a part of the acceptance process. You may want to prepare this archive in anticipation of acceptance. You can wait until version 1.0.0 for uploading to zenodo, but you might as well do it now to check that everything works as expected (and re-upload the final version).
Zenodo looks for a citation file in the repo. If the citation file is not present, you will have to add some metadata manually.
This issue is a part of a JOSS review at https://github.com/openjournals/joss-reviews/issues/5967

I have uploaded it here (https://zenodo.org/records/10183124).
Does it looks good to you?

looks good to me except there's a typo in the title
Sent via the Samsung Galaxy S21 Ultra 5G, an AT&T 5G smartphone
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: MaceKuailv @.>
Sent: Tuesday, November 21, 2023 6:11:53 PM
To: MaceKuailv/seaduck @.>
Cc: Subscribed @.***>
Subject: Re: [MaceKuailv/seaduck] Generate zenodo archive (Issue #101)
  External Email - Use Caution

I have uploaded it here (https://zenodo.org/records/10183124).
Does it looks good to you?
—
Reply to this email directly, view it on GitHubhttps://github.com/MaceKuailv/seaduck/issues/101#issuecomment-1821842402, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKP7IKUFDE25ZXPWQEPDSLDYFUYLTAVCNFSM6AAAAAA64AYY2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRHA2DENBQGI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Good catch. Fixed.

I am going to close this as done


Alvr linux build

This adds a build script for ALVR server + client on Debian, Fedora, Pop!_OS, and Ubuntu, and adds deb packaging support.

Feel free to clean up commit history if you'd like, otherwise I'll just squash-merge.

Yeah, the deb packages are still very much experimental; nobody has really tested them for functionality until now. Basically, right now the builds are performed on the following OSs:

Ubuntu 21.04 (Hirsute) build server:

client
20.04 (Focal)
21.04 (Hirsute)

Debian 11 (Bullseye) build server
Fedora 34 build server

I'll try configuring the Ubuntu 20.04 repository to use the Debian 11 build with the next release. I don't have a CI/CD system configured just yet as I was testing different repository software.  That being said, this should probably be merged so I can build a stable release (I can't build stable until the Debian control file and various other parts are merged).


Lack of a way to detect Form type of model-driven app in PCF Context

[Enter feedback here]
There is lack of a way to detect Form type of model-driven app in PCF Context.
Needs the feature like the getFormType  in Client API: getFormType

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

ID: 5f219919-646d-18e5-2766-365f34aea315
Version Independent ID: de311f39-0493-955f-d3fb-7b38071b5ab9
Content: Context (Power Apps component framework API reference) - Power Apps
Content Source: powerapps-docs/developer/component-framework/reference/context.md
Service: powerapps
Sub-service: pcf
GitHub Login: @noazarur-microsoft
Microsoft Alias: noazarur

Thanks for your comment, @keijimscom. This issue has been assigned to the doc author for review.

Added @HemantGaur for visibility, but this appears to be a feature request.  We can't fix this with documentation, so it isn't an actionable issue until that feature is added.
Since the getFormType method returns information like this:

Value
Form type

0
Undefined

1
Create

2
Update

3
Read Only

4
Disabled

6
Bulk Edit

I can see how this would be useful for the PCF developer to have this information in the context.
I'm not aware of another way to detect this.
Recommend posting this feature request on the Power Apps Ideas site.
Closing this


Configurable modal option added to prevent close on click outside

Thanks @shuvroroy 😄
It looks like you included your previous PR in this branch as well. If you can make sure it only includes the changes for the click away feature, that would be perfect.

@PhiloNL I am closing the pr


QUESTION: Why is webpack having trouble resolving a nested node_module

"typescript": "^2.0.10"
"webpack": "2.1.0-beta.27"
I am using module resolution in webpack to avoid using ../../ on the client to import certain modules. My  directory structure looks like this
- dist (transpiled assets)
- node_modules
- lib
   - client
       - typescript
          - some-component
             - some-component.ts
          - some-service
             - some-service.ts
   - server
   - shared
- webpack.config.js
- tsconfig.client.json

In some-component.ts, i want to import from some-service.ts, so I have configured webpack to allow the following module resolution:
const rootDir = __dirname;

const clientPathMappings = [
  path.resolve(rootDir, 'lib/client/typescript'),
  path.resolve(rootDir, 'node_modules')
  ];
......

(inside the config object)
resolve: {
      extensions: ['.ts', '.jade', '.js'],
      modules: clientPathMappings
    }

I can then do this:
import { SomeService } from 'some-service';

When i run webpack, it complains:

ERROR in multi app
Module not found: Error: Can't resolve '/Users/varun/project/api-server/node_modules' in '/Users/varun/project/api-server'
 @ multi app

ERROR in ./~/mongoose/lib/schema.js
Module not found: Error: Can't resolve 'async/each' in '/Users/varun/project/api-server/node_modules/mongoose/lib'
 @ ./~/mongoose/lib/schema.js 11:11-32
 @ ./~/mongoose/lib/browser.js
 @ ./lib/client/typescript/index.ts
 @ multi app

This is definitely a webpack error and not a typescript error, but I've pasted my tsconfig below just in case:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "noImplicitAny": false,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "moduleResolution": "node",
    "removeComments": true,
    "sourceMap": true,
    "lib": [
      "es6",
      "dom"
    ],
    "baseUrl": ".",
    "paths": {
      "*": [
        "lib/client/typescript/*"
      ]
    }
  },
  "exclude": [
    "node_modules"
  ],
  "include": [
    "lib/client/typescript/**/*"
  ]
}

Why can't webpack resolve async/each from within mongoose? And what is webpack's complaint about trying to resolve node_modules as if it were a file and not a folder within which modules I would want to resolve live in?

I was able to get mongoose's complaint about async/each to go away by removing path.resolve from the node_modules path (not sure why that worked):
[
  path.resolve(rootDir, 'lib/client/typescript'),
  'node_modules'
  ];

I'm still getting the issue about resolving node_modules though:
ERROR in multi app
Module not found: Error: Can't resolve '/Users/varun/project/api-server/node_modules' in '/Users/varun/project/api-server'
 @ multi app

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template, or open a new issue.

Yeah sorry about that, i ended up figuring the problem out anyway.

Yeah sorry about that, i ended up figuring the problem out anyway.

Could you please share the solution?


Corrected the Wrongly Wriiten formula of CSA and TSA of hollow sphere

Related Issuse
#567
Closes: #567
Describe the changes you've made
Corrected the Wrongly Wriiten formula of CSA and TSA of hollow sphere
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

@sairish2001 Please review it!

I have corrected the formula,It was written wrongly previously

Check again the files in this PR

ok.,I will check!

@sairish2001 Please check it now!


Perform LV activation/deactivation

This PR introduces:

Deactivation of volume after lvcreate
Activation of volume before usage
Deactivation of volume after usage
sync+lvscan before every lvm operation

This is first step needed to implement shared vg support https://github.com/metal-stack/csi-driver-lvm/issues/62

Hi @kvaps
I still do not understand how lvm-ha setup would look like ? Can you explain a bit more who would be responsible to sync data between nodes and how.

Hey, sorry, for insufficient description to this PR.
I'm solving the issue of using LVM over shared storage (DAS).
Eg. when you have shared LUN connected to multiple nodes in your cluster.

The LVM is used to cut this volume on small pieces
I like design of your driver, and I'm going to develop my own own based on it.
I wish to contribute changes back, but not sure if you'll agree with these changes.

First of all I want driver which will work in both cases: Local LVM and Shared LVM.
The driver should have configurable volume group in StorageClass, thus it can work with many VGs.
Volumes should be created with nodeAffinity to VG's, not to the nodes.
For each VG driver should add label to node with UUID of this VG. Thus if VG is shared across the multuple nodes the Volume can be used on any of them.
The driver should not use cLVM or lvmlockd extensions, they are pretty complex and difficult to maintain. Instead it must to refresh LVM metadata before the each operation on VG. The locks should be implemented using Kubernetes API.
Snapshots support

The design of shared LVM without cLVM and lvmlockd is borrowed from such solutions as OpenNebula and Proxmox.
Both do not require the clustered extension for LVM:
proxmox:

You don't need CLVM as long as you use the pve tools/API to manage volumes (create/delete).

opennebula:

The LVM datastore does not need CLVM configured in your cluster. The drivers refresh LVM metadata each time an image is needed on another Hosts.

here are some excerpts from the LVM mailing list:

cLVM does not control concurrent access, it just cares about propagating the lvm metadata to all nodes and locking during changes of the metadata.

All clustered LVM does is make sure that, as LVM things change, all nodes know about the changes immediately.

https://lists.clusterlabs.org/pipermail/users/2015-December/018263.html
https://www.spinics.net/lists/lvm/msg21913.html
https://ivirt-it.ru/clvm-lvmlockd/

Unfortunately, I have no enough time to continue with this right now. It's better to convert it to draft.
Feel free to leave any comments on my design.

This seems a lot of effort and does not fit well in our use case. It is probably better to take this code and create your own csi driver. But if you have small improvements for this one, they are all welcome.

I hope this is fine to close, please re-open if necessary.


#332 Adding urlNative call to chat_service

#332 So, this final change technically fulfills the requirements of the ticket, but the chat is still broken:
flutter: Failed to send message "[#73567]" to the server: gRPC Error (14, Error connecting: SocketException: OS Error: Connection timed out, errno = 110, address = grpc.maintemplate.ci.getcouragenow.org, port = 33000)
flutter: Failed to receive messages from the server: gRPC Error (14, Error connecting: SocketException: OS Error: Connection timed out, errno = 110, address = grpc.maintemplate.ci.getcouragenow.org, port = 33006)

Hey @ArchitectNate
I spoke to the higher ups, and we can handle your needs :)
You did well on the Issue i gave you and you could start tomorrow if you wanted.
Can you contact me Telegram: gedw99_ww99. I cant seem to find you in my Telegram.
thanks !

Sure, if 15 to 20 hours a week is ok.
On Sun, Apr 12, 2020, 6:58 PM Joe<EMAIL_ADDRESS>wrote:

Hey @ArchitectNate https://github.com/ArchitectNate
I spoke to the higher ups, and we can handle your needs :)
You did well on the Issue i gave you and you could start tomorrow if you
wanted.
Can you contact me Telegram: gedw99_ww99. I cant seem to find you in my
Telegram.
thanks !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/getcouragenow/packages/pull/354#issuecomment-612714600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADYJC5WXJV73FCJG5FAHWTRMJWUBANCNFSM4MGCCQFQ
.


Missing decorators functionallity on plain objects

TypeScript Version:

2.7.0-dev.20171203 (locally)
2.6.1 (globally)

tested also on typescript@next
Code
// Define a simple decorator
const decorator : PropertyDecorator = (target : any, key : string | symbol) : void => {
    console.log(key, target[key]);
}

// I will create a plain object
const obj = {
    some: {
        nestedObj: {
            // Here comes the point of error
            @decorator
            value: 10,
        },
    },
};

Expected behavior:
I would expect it to be transpiled like this:
var obj = {
    some: {
        nestedObj: decorator({
            value: 10,
        }, 'value'),
    },
};

Babel already comes with this feature, and when I saw it I was thinking: "of course, Typescript will support it".
So I've build a feature in my library based on that. Now I have to do this workaround:
function applyDecorators(parent : any, key : string | symbol, ...decorators : PropertyDecorator[]) {
_.forEach(decorator, (d) => {
d(parent, key);
});
}
applyDecorators(obj.some.nestedObj, 'value', decorator1, decorator2);
Actual behavior:
The Visual Studio Code shows error right away. The tsc compiler also shows an error

VSCode Error:

// << Line 148 is here >>
const obj = {
    some: {
        nestedObj: {
            @decorator // // [ts] Declaration expected. any         [[line 152]]
            value: 10, // value <= [ts] Unused label. ||| 10 <= [ts] Left side of comma operator is unused and has no side effects.          [[line 153]]
        }, // [ts] Expression expected         [[line 154]]
    }, // Argument expression expected          [[line 155]]
}; // Argument expression expected          [[line 156]]
// << Line 158 is here >>

tsc@next Error:

tests/integration.ts(152,21): error TS1136: Property assignment expected.
tests/integration.ts(152,31): error TS1146: Declaration expected.
tests/integration.ts(154,17): error TS1109: Expression expected.
tests/integration.ts(155,13): error TS1135: Argument expression expected.
tests/integration.ts(156,9): error TS1135: Argument expression expected.
tests/integration.ts(156,10): error TS1005: ')' expected.
tests/integration.ts(188,5): error TS1128: Declaration or statement expected.
tests/integration.ts(188,6): error TS1128: Declaration or statement expected.
tests/integration.ts(190,1): error TS1128: Declaration or statement expected.
tests/integration.ts(190,2): error TS1128: Declaration or statement expected.

The reason that is not supported is because https://github.com/tc39/proposal-decorators does not provide for it. Decorators are unfortunately limited to classes.
Whatever Babel extension you have that supports this (I'd be curious to know which) is providing functionality that is not even proposed for standardization.

Duplicate of https://github.com/Microsoft/TypeScript/issues/5770


close ResultSet after get result

Call ResultSet.close() method when after getting result from ResultSet, otherwise it will cause memory overflow.(for example use impala
jdbc)
https://issues.apache.org/jira/projects/METAMODEL/issues/METAMODEL-1208

https://patch-diff.githubusercontent.com/raw/apache/metamodel/pull/205.patch

Error might be unrelated. All runs are good, except on OracleJDK8, where an Excel test fails inside Apache POI.
It could easily be the Excel context that has issues. We recently changed it, and it has had some timing problems previously. Of course, the closing of the result set could change the timing slightly, exposing a problem.

I'll have Travis rebuild it to see what happens ...

Hmm. I overspoke - I cannot do that. @q977734161 you'll probably have to make an empty commit to trigger rebuild:
git commit --allow-empty -m "Empty commit to trigger rebuild"

Related note though - it seems that even the master build failed on one of the 4 JVMs that it's building on. I think we have an unstable test that we should look at having fixed.

D'oh, I missed that it was in JDBC, then the Excel issue is unrelated for sure. :-)
In theory, we shouldn't need to close the resultset, as resultsets are supposed to close along with the statements, but drivers can probably easily break that convention, so it's a good thing to ensure the closure in our end.

I use mysql, It's normal,But use Impala jdbc,cause heap overheap.
When using jmap -histo pid command,there are many impala metaset classes,when add close method is normal.


if teacher_force is false, raw_pred should be topk(1)?

rt

Hi lezasantaizi,
I'm not quite sure what you mean by topk(1). In our implementation, the model inputs the output of the previous timestep if teacher_force is false.
If you're referring to the top k parameter of beam search, we did not implement that (i.e. beam size always =  1 )

Thanks for your suggestion, I've added a parameter decode_mode in config. Output format (distribution/ topk(1)/ sampled onehot) of Speller feeding foward to next time step can be selelcted by this flag.