MemoQ as translation provider?

Motivation

We currently experience issues with both DeepL and Google serving corrupted translations (such as putting phrases marked with translate="no" at the start of the sentence rather than where they make sense) for various source/target language pairs, which is not something we can influence. Meanwhile, it seems that these are still correctly handled when translating in MemoQ.
Perhaps MemoQ has a versioned access to DeepL, where they can hold off on using a newer generation of translation models that have regressions.
Proposed Solution

It might make sense to add MemoQ as a translation provider: https://www.memoq.com/integrations/apis
Then MemoQ might serve as a fallback in case we experience similar difficulties with DeepL and Google but not MemoQ in the future.
Alternatives

Do not implement MemoQ as another translation provider. Municipalities will have to accept translations as they come out of either Google or DeepL, or suspend translation activity until the services seem fine again. If MemoQ seems to translate just fine, we might offer municipalities to translate their translations manually for them using MemoQ.
User Story

As a service provider I want to have a working translation provider to recommend my clients so that no interruptions in day to day business and, following that, loss of trust occur.
Additional Context

https://github.com/digitalfabrik/integreat-cms/pull/3135#issuecomment-2424968026

The implementation might be part of https://github.com/digitalfabrik/integreat-cms/issues/1963


Use of undeclared type or module: runtime_primitives AND parity_codec

I am using v2.0 (current repo), and I am building through the collectable workshop code on:
https://substrate.dev/substrate-collectables-workshop/#/1/storing-a-structure
The imports used
use support::{decl_storage, decl_module, StorageMap, dispatch::Result};
use system::ensure_signed;
use runtime_primitives::traits::{As, Hash};
use parity_codec::{Encode, Decode};

the error:
use of undeclared type or module `runtime_primitives`
error[E0433]: failed to resolve: use of undeclared type or module `runtime_primitives`

and
use of undeclared type or module `parity_codec`
error[E0432]: unresolved import `parity_codec`

I am assuming the name of the libraries has changed, or maybe the location of submodules has changed. I can get the workshop working with "substrate-package", but it isn't too far from working with the updated repo.
Also, I make a struct:
#[derive(Encode, Decode, Default, Clone, PartialEq)]
#[cfg_attr(feature = "std", derive(Debug))]

pub struct MyStruct<Hash, Balance> {
    id: Hash,
    dna: Hash,
    price: Balance,
    gen: u64,
}

and, inside my decl_storage! macro, I use:
OwnedStruct get(struct_of_owner): map T::AccountId => MyStruct<T::Hash, T::Balance>;

the following error occurs
error[E0220]: associated type `Balance` not found for `T`

Inside my decl_module, I create a Struct:
let new_struct = OwnedStruct {
                id: <T as system::Trait>::Hashing::hash_of(&0),
                dna: <T as system::Trait>::Hashing::hash_of(&0),
                price: <T::Balance as As<u64>>::sa(0),
                gen: 0,
};

and I can also pass in a Hash, and Balance:
 fn create_struct(origin, value: u32, balance: T::Balance, hash: T::Hash) -> Result {

and declare the same Struct like:
let new_struct = OwnedStruct {
                id: hash,
                dna: hash,
                price: balance,
                gen: 0,
};

The above is not working, any suggestions regarding these errors?
I'd love to help update the workshop code for the newer versions
** BTW this is using substrate 2.0**
Do you know of the correct module/library import syntax?... this is strange

I believe runtime_primitives is imported as primitives:
https://github.com/paritytech/substrate/blob/master/node-template/runtime/Cargo.toml#L16
And parity_codec is imported as codec:
https://github.com/paritytech/substrate/blob/master/node-template/runtime/Cargo.toml#L11
The secondary error may go away once you correctly import the things, so I would check first if you still have the other errors after this fix.

In terms of updating the code for 2.0. We are planning on doing a complete re-write of the whole tutorial for 2.0, since we can do it better the second time around :)
That being said, there are probably other samples across the substrate-developer-hub team that you can update to use 2.0

The As stuff has also been removed, see: https://stackoverflow.com/questions/56081117/how-do-you-convert-between-substrate-specific-types-and-rust-primitive-types


About the camera pose

Thanks for sharing such a great work!
I have run the demo code in the provided docker image successfully. However, I got only the depth files in the output folder. Could you please tell me how to get the estimated poses after I run the inference process?
Thanks!

By the way, the inference speed is really fast! Thanks for sharing such a useful work again~


feat: upgrade to angular 15/16

Hey! First of all thanks for the package, it has served us well over the past few years :)
However, with Angular's newest update to v16, the legacy ngcc compiler has been completely removed, resulting in this package sadly not working with our configuration anymore. Since there have been quite a lot of breaking changes and changes in how libraries are supported in Angular (with the CLI now using ng-packagr under the hood and multi-project workspaces becoming the norm), we decided it was easier to do a full breaking update to not just the dependencies, but also the structure of it all, which this PR is the result of. What that means specifically is:

We moved everything into a CLI-generated monorepo-style workplace (with angular-gauge and demo as the two projects)
We removed the custom webpack configurations, instead completely relying on the Angular CLI
We replaced the 3rd testing party libraries like sinon and chai with equivalent jasmine functions that Angular now provides out of the box
The package now requires at least Angular v15 (but 16 has also been tested and works)

We published this version publicly as<EMAIL_ADDRESS>(on npm), for those who just want to use it now.
Let me know if we can do anything else to help in the merging process!

Released as 5.0.0! 🥳

Amazing, thank you so much for merging and releasing this so quickly! 🥳

I am facing this error while npm start in Angular 15 application.
FYI, I installed using npm i --legacy-peer-deps<EMAIL_ADDRESS>Error: node_modules/@avtest/angular-gauge/lib/gauge.component.d.ts:79:80 - error TS2344: Type '{ dialStartAngle: { alias: "dialStartAngle"; required: false; }; dialEndAngle: { alias: "dialEndAngle"; required: fals
e; }; dialRadius: { alias: "dialRadius"; required: false; }; min: { alias: "min"; required: false; }; ... 10 more ...; animationDuration: { ...; }; }' does not satisfy the constraint '{ [key: string]: string; }'.
  Property '"dialStartAngle"' is incompatible with index signature.
    Type '{ alias: "dialStartAngle"; required: false; }' is not assignable to type 'string'.

79     static ɵcmp: i0.ɵɵComponentDeclaration<GaugeComponent, "mwl-gauge", never, { "dialStartAngle": { "alias": "dialStartAngle"; "required": false; }; "dialEndAngle": { "alias": "dialEndAngle"; "required": false
; }; "dialRadius": { "alias": "dialRadius"; "required": false; }; "min": { "alias": "min"; "required": false; }; "max": { "alias": "max"; "required": false; }; "label": { "alias": "label"; "required": false; }; "c
olor": { "alias": "color"; "required": false; }; "showValue": { "alias": "showValue"; "required": false; }; "gaugeClass": { "alias": "gaugeClass"; "required": false; }; "dialClass": { "alias": "dialClass"; "requir
ed": false; }; "valueDialClass": { "alias": "valueDialClass"; "required": false; }; "valueClass": { "alias": "valueClass"; "required": false; }; "value": { "alias": "value"; "required": false; }; "animated": { "al
ias": "animated"; "required": false; }; "animationDuration": { "alias": "animationDuration"; "required": false; }; }, { "gaugeCreated": "gaugeCreated"; }, never, never, false, never>;


[BUG] Cannot filter on Timestamp using Azure.Data.Tables SDK (Cosmos backend)

Library name and version
Azure.Data.Tables 12.7.0
Describe the bug
When I apply a filter on the Timestamp field, the query returns zero results.
Expected behavior
The query should return the results that satisfy the Timestamp query
Actual behavior
An empty collection is returned. No exception is thrown. Yes there are elements that should satisfy the query. When I run the identical query in Azure Portal, the expected items are returned.
Reproduction Steps
var connectionString = "...";
var table = new TableClient(connectionString, "CommandLogs");

var failureFilter = "UserId eq '76d8bd02-7943-436e-b5a8-d7101a541fd6' and Timestamp ge datetime'2022-10-24T21:50:41Z'";
var successFilter = "UserId eq '76d8bd02-7943-436e-b5a8-d7101a541fd6'";

var failureItems = table.Query<CommandLog>(filter: failureFilter);
var successItems = table.Query<CommandLog>(filter: successFilter);

Console.WriteLine(failureItems.Count());
Console.WriteLine(successItems.Count());

Environment
.NET7 console app

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @nheath99 - If you are using Cosmos as your backend, this is expected behavior (documented here). The service team is aware of it. (dupe of #31171)

documented here: https://learn.microsoft.com/en-us/azure/cosmos-db/table/tutorial-query#query-by-using-an-odata-filter


Implement check:construction

Changes

[ ] Add CheckConstructionHandler
[ ] Add counters for transaction construction
[ ] Add construction testing loop in /internal/tester/construction.go
[ ] implement cmd/check_construction.go (support for signal handlers)
[ ] Migrate logic from cmd/check_data.go to /internal/tester/data.go

Pull Request Test Coverage Report for Build 1791

3 of 117 (2.56%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-6.4%) to 59.843%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/processor/check_data_sync_handler.go
0
2
0.0%

internal/storage/key_storage.go
3
12
25.0%

internal/processor/check_construction_sync_handler.go
0
103
0.0%

Totals

Change from base Build 1775:
-6.4%

Covered Lines:
687

Relevant Lines:
1148

💛  - Coveralls


⚠ Bofrost.de has degraded performance

In 397f54c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 921 ms

Resolved: Bofrost.de performance has improved in ea28825 after 13 minutes.


[9.4.x] ISPN-10784 xsite updates for 9.4.x concurrent writes

https://issues.redhat.com/browse/ISPN-10784

integrated! thanks @oraNod !


RSVP dock is not visible on the meetup page

I visited the meetup page and can not see the rsvp option. Is that because rsvp is closed now ?

Update:

I realized the rsvp close date is set to today after a quick investigation. This explains why it's not visible.

@MrSunshyne Can you please look into it when you've some time? 🙏

Thanks for the feedback!
You're correct. Since the initial date of the meetup was supposed to be tomorrow, rsvp closes today. I'm updating it. Thank you


rocketeer ignite returns "Unknown command 'rocketeer'"

I'm running fish shell and am getting the error Unknown command 'rocketeer' when trying to initiate Rocketeer in a project. Composer is installed and seems to be running normally. Rocketeer is installed globally.
I assume it's a PATH issue on my part. Output of echo $PATH:
/usr/local/sbin /usr/local/bin /usr/local/bin /usr/bin /bin /usr/sbin /sbin

I believe I've resolved the issue by adding this snippet to my config.fish file. If there's a better/cleaner way, I'd love to know:
https://github.com/oh-my-fish/plugin-composer/blob/master/composer.load


Blazor page is rendered before external JavaScript files are loaded

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
In the docs is written that external JavaScript files should be placed after the Blazor script reference. For example:
 <script src="_framework/blazor.{webassembly|server}.js"></script>
 <script src="./_content/{PACKAGE ID}/{SCRIPT PATH AND FILENAME (.js)}"></script>

This works in Firefox, but it can throw an exception in Chrome or Edge because the page is rendered before scripts are loaded.
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/28044
Expected Behavior
Blazor should wait and not call OnAfterRenderAsync function until all external scripts are loaded.
Steps To Reproduce
Create a new project - Blazor Server App.
Pages/_Host.cshtml
     ...
    <script src="_framework/blazor.server.js"></script>
    <script src="test.js?@DateTime.Now.ToString("HHmmss")"></script>
</body>
</html>

wwwroot/test.js
/* paste inside this comment at least 10 MB of any text so that this file is really big  */
function test() { }

Pages/Index.razor
@page "/"
@inject IJSRuntime JS
@code {
	protected override async Task OnAfterRenderAsync(bool firstRender)
	{
		await JS.InvokeVoidAsync("test");
	}
}

Run the app in Chrome, then set throttling to Slow 3G on the network tab and refresh the page.
Exceptions (if any)
Error: Microsoft.JSInterop.JSException: Could not find 'test' ('test' was undefined).
Error: Could not find 'test' ('test' was undefined).
    at https://localhost:44368/_framework/blazor.server.js:1:497
    at Array.forEach (<anonymous>)
    at s.findFunction (https://localhost:44368/_framework/blazor.server.js:1:465)
    at E (https://localhost:44368/_framework/blazor.server.js:1:2611)
    at https://localhost:44368/_framework/blazor.server.js:1:3499
    at new Promise (<anonymous>)
    at Ft.beginInvokeJSFromDotNet (https://localhost:44368/_framework/blazor.server.js:1:3480)
    at Ft._invokeClientMethod (https://localhost:44368/_framework/blazor.server.js:1:75072)
    at Ft._processIncomingData (https://localhost:44368/_framework/blazor.server.js:1:72696)
    at Ft.connection.onreceive (https://localhost:44368/_framework/blazor.server.js:1:67009)
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args)
   at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args)
   at BlazorApp2.Pages.Index.OnAfterRenderAsync(Boolean firstRender) in C:\Users\PetrLastovicka\source\repos\BlazorApp2\Pages\Index.razor:line 6
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningCompone
```ntState)

### .NET Version

7.0.101

### Anything else?

_No response_

Thanks @mkArtakMSFT ... This was worked on at first on https://github.com/dotnet/AspNetCore.Docs/pull/28045, but the best updates where this morning to resolve it on https://github.com/dotnet/AspNetCore.Docs/pull/28051. That last point that I made :point_up: is tracked by my 2023 tracking issue, and I'll discuss that with either Steve or Javier later.


Additional CMS content types from RFC 4073, RFC 5083, and RFC 5084.

For readability's sake, this doesn't include the changes made to other files by make generate_crypto_objects.

trivial addition if we want it for 1.1

+1

commit 505aee2.  merged, thanks.


Added support for redis gears trigger function commands

coverage: 82.215% (-0.05%) from 82.268% when pulling 1dba082c1530842bb346c2a4e1e4c4739f3a72fe on vladvildanov:vv-redis-gears-triggered-functions into d8da27ba02ca65a409f10fc3e9ab64728f0ad3ce on predis:v3.x.

@tillkruss Changelogs updated as separate PR for whole 3.0 update
https://github.com/predis/predis/pull/1393

@tillkruss Needs update on this, it's ready to merge


the 'verify' function takes too much time, about 1.3 seconds

the 'verify' function takes too much time, about 1.3 seconds

In general, the computational work is intentional. That's what supplies security against password crackers. If your system can't handle it in reasonable time, either use a faster system for verification or delegate authorization to a service like Google Firebase or Auth0.
Degrading the work time to make it faster would be irresponsible.
There is an open issue which may have a positive impact on performance. You're welcome to contribute to it if the suggestions help.


Add utility method to allow assigning alternate target to a new session.

Relates to #11.

Perfect! Thank you so much :+1:


Ruby version hard coded in Dockerfile?

After running heroku docker:init, when I run heroku docker:start I’m getting the following output
Your Ruby version is 2.2.1, but your Gemfile specified 2.2.2
Removing intermediate container f55bd50d8d85
 !    Error: Unable to create start image

Changing ENV RUBY_ENGINE 2.2.1 to ENV RUBY_ENGINE 2.2.2 in the generated Dockerfile seems to have fixed this.

Glad you were to work around by updating your Dockerfile. The Ruby version should be detected:

https://github.com/heroku/heroku-docker/blob/master/platforms/ruby/Dockerfile.t#L8

Perhaps the detect isn't always accurate? Pinging @friism

Resolved by https://github.com/heroku/heroku-docker/pull/69


arrow-path icon missing

cannot import ArrowPathIcon (arrow-path) it is missing. but on heroicons weppage i have found it

This icon was added today, published a new version.


Bug in JSDoc

in JSDoc documentation http://usejsdoc.org/tags-param.html
find paragraph "Documenting properties of values in an array"

is this a jscs issue or a plugin issue?


Potential unsoundness in fun::fnat::para_pre_zero ((n : nat) ⋀ (0 == n + 1)  =>  false)

The theorem is correct, but I am concerned that the proof is not sound:
/// `(n : nat) ⋀ (0 == n + 1)  =>  false`.
pub fn para_pre_zero<N: Prop>((ty_n, x): And<Ty<N, Nat>, Eq<Zero, Inc<N>>>) -> False {
    match nat_def::<N, N>(ty_n.clone()) {
        Left(eq_n_zero) => para_eq_zero_one(eq::transitivity(x, app_eq(eq_n_zero))),
        Right(t) => para_eq_inc((ty_n.clone(), lam_app_nop(ty_n).0(t.1))),
    }
}

If one takes a look at nat_def:
/// `(x : nat)  =>  (x == 0) ⋁ (y : nat, (\(y : nat) = x == (y + 1))(y))`.
pub fn nat_def<X: Prop, Y: Prop>(
    _x_ty: Ty<X, Nat>
) -> Either<Eq<X, Zero>, DepTupTy<Y, Nat, Lam<Ty<Y, Nat>, Eq<X, Inc<Y>>>>> {unimplemented!()}

I make Y = X = N and this is what I find non-intuitive, that I can "force" Y to equal something and use it as a contradiction.

One idea is to require theory(x == y) in nat_def.

There is another reason this is unsound: It accesses the second tuple component t.1:
error[E0616]: field `1` of struct `tup::Tup` is private
  --> src/fun/fnat.rs:53:70
   |
53 |         Right(t) => para_eq_inc((ty_n.clone(), lam_app_nop(ty_n).0(t.1))),
   |                                                                      ^ private field

One idea is to use ~!x instead of y.

A better idea might be to use prev(x) instead of y. This has a unique meaning avoids complex collisions.


OS: Fix some Minix bugs.

Description
This PR fixes some of the bugs in @konimex's PR. #547
Features

Term: Fixed bug with init appearing in get_term() output.
Shell: Fixed bug with sh and --version causing an error.
Local IP: Added initial support for Minix.

The Linux ifconfig command doesn't work for me, this change makes it work. I'm not sure if it already worked on your system or not @konimex.

Disk: Fixed df flags on Minix. Disk now works.

Note: Keep your PR open @konimex and we can merge mine into yours or you can manually add the changes since they're tiny.

Merged to minix branch. 👍
I will do some more tests when I get home later.


The first link in the "Where can I learn more about MSBuild?" section points to this same page.

Pete and Repeat were in a boat, and Pete jumped out. Who was left?

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

ID: 22342679-18af-7c79-f902-fe9c0bb55379
Version Independent ID: a8e7c201-6593-458b-5a81-b54e93fde4b5
Content: MSBuild build and release task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/msbuild.md
Product: devops
Technology: devops-cicd
GitHub Login: @vijayma
Microsoft Alias: vijayma

@StingyJack  Thank you for the feedback.
The changes have been made and are pending review.


drivers: gpio_nrfx: support edge interrupts using GPIO SENSE

Currently level interrupts are implemented using GPIO SENSE, but edge
interrupts using GPIOTE events. Using GPIOTE events results in increased
power consumption according to erratas of some nRF MCUs. In case of
nRF52832 it is <20uA in System ON Idle and ~400-450uA when used in
conjunction with SPI or TWI.
Add a user configurable option to select between GPIOTE events and GPIO
SENSE mechanism, for implementing edge interrupts. Selecting GPIO SENSE
option will allow to reduce power consumption in scenarios mentioned by
nRF MCUs erratas.

Changes:

I've restated description, which was saying only about erratas. In fact product specifications also mention increased power consumption when GPIOTE is used (e.g. nRF52840).
Previously SENSE detection was always configured to detect "Low" level. Currently we check state of pin and configure SENSE detection to the opposite state. This fixed case when gpio pin was low during interrupt configuration, which immediately triggered falling edge (but obviously it should not).
GPIOTE events mechanism didn't allow to detect edges on output pins. Using SENSE that is possible, so we no longer return -EINVAL when configuring edge detection on output pins.

Both tests/drivers/gpio/gpio_api_1pin and tests/drivers/gpio/gpio_basic_api pass when tested with nrf52840dk_nrf52840, with GPIOTE and with SENSE. Even more, using SENSE results in all tests in gpio_api_1pin to pass, while detecting edges with GPIOTE on output pins results in skipped tests.


fetchgit: support specifying location of public keys for ssh transport

Follow up on #1923:
Currently using ssh urls for fetchgit results into:

Could not create directory '/var/empty/.ssh'.
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Could not create directory '/var/empty/.ssh'.
Host key verification failed.

Maybe fetchgit should grow an extra parameters?

@domenkozar is this fixed?

No response, so close @zimbatm.

@Profpatsch this is still an issue. You can repro by running nix-build against https://gist.github.com/anonymous/fb9353cabf8dd9fecd28

I just ran into this issue.  For other people who have this same issue, you can work around it by using the alternative HTTPS url that Github provides for cloning (i.e. https://github.com/your-name/your-project.git).  If you are prompted to authenticate when cloning via the HTTPS url, follow these instructions, which include how to deal with two-factor authentication:

Cloning with HTTPS URLs

Okay, so I think this is basically solved by fetchgitPrivate, although I'm going to suggest two possible enhancements to the implementation of fetchgitPrivate.
First, using a variation on the gist that @zimbatm linked to, I can successfully build the repository by replacing fetchgit with fetchgitPrivate (and fixing the sha256 field):
# default.nix

{ pkgs ? import <nixpkgs> {} }:

pkgs.buildRubyGem rec {
  src = pkgs.fetchgitPrivate {
    url = "git@github.com:flori/json.git";
    rev = "80e8213ce940005a1c7314793d39a0c4cc786821";
    sha256 = "0ki6a4vnccb86rmssbc5x3d067zvkhyi6y973068hz81q0rjqf8a";
  };
  gemName = "json";
  version = "1.8.3";
  sha256 = "1nsby6ry8l9xg3yw4adlhk2pnc7i0h0rznvcss4vk3v74qg0k8lc";
}

... and supplying the appropriate SSH config file and SSH_AUTH_SOCK on the command line (since that is how fetchgitPrivate is configured to work):
nix-build default.nix -I ssh-config-file=/path/to/.ssh/config -I ssh-auth-sock=$SSH_AUTH_SOCK

So that alone is probably enough to mark this issue closed, but I'd like to also suggest two improvements to fetchgitPrivate to reduce the need to supply these parameters on the command line:

Use impureEnvVars to automatically inherit the SSH_AUTH_SOCK from the user's environment
Supply the configuration file directly as a nix argument

This would involve simplifying pkgs/build-support/fetchgit/private.nix to this:
{ fetchgit, writeScript, openssh, stdenv }:

sshConfigFile: fetchGitArgs:

derivation ((fetchgit fetchGitArgs).drvAttrs // {
  impureEnvVars = [ "SSH_AUTH_SOCK" ];

  GIT_SSH = writeScript "fetchgit-ssh" ''
    #! ${stdenv.shell}
    exec -a ssh ${openssh}/bin/ssh -F ${sshConfigFile} "$@"
  '';
})

... and then you'd just provide the ~/.ssh/config file in nix:
{ pkgs ? import <nixpkgs> {} }:

pkgs.buildRubyGem rec {
  src = pkgs.fetchgitPrivate /path/to/.ssh/config {
    url = "git@github.com:flori/json.git";
    rev = "80e8213ce940005a1c7314793d39a0c4cc786821";
    sha256 = "0ki6a4vnccb86rmssbc5x3d067zvkhyi6y973068hz81q0rjqf8a";
  };
  gemName = "json";
  version = "1.8.3";
  sha256 = "1nsby6ry8l9xg3yw4adlhk2pnc7i0h0rznvcss4vk3v74qg0k8lc";
}

... and now you can run the build command without any command line arguments:
$ nix-build default.nix

Would people be okay with that proposed change?

src = pkgs.fetchgitPrivate /path/to/.ssh/config {

You mean it’s okay if that’s an argument, since fetchgitPrivate will only be used from private nix files?

Yeah, the .ssh/config file can be made a private file if it contains any secrets, although it shouldn't need to.  The impure SSH_AUTH_SOCK environment variable forwarded from your environment actually does the authentication for you using your ambient ssh agent.  For example, in my case the .ssh/config file was just empty so I could pass writeText "ssh-config" "" if I wanted to.

Actually, I've come to the conclusion that the current behavior of fetchgitPrivate is the ideal behavior and requires no modification
The thing that convinced me that the current behavior is the way to go was getting a package to work with hydra.  The only way to securely provision a secret to a hydra build is via the Nix search path.
Also, the SSH_AUTH_SOCK argument is not necessary (and won't even work in some cases like remote builds).  Another approach is to provide an ssh-config-file with an IdentityFile line, such as this:
StrictHostKeyChecking No
UserKnownHostsFile /dev/null
IdentityFile /path/to/.ssh/id_rsa

... and then supply the path to that on the Nix path like this:
$ nix-build example.nix -I ssh-config-file=path/to/above/config

So the conclusion I came to is that this issue is solved by fetchgitPrivate but could perhaps use better documentation on how to correctly use it in various circumstances (like local vs remote builds, hydra, nixops, etc.).

The only issue with fetchgitPrivate is that tools like nix-prefetch-git don't make a distinction between private and public repos and then the packaging tools like npm2nix, bundix, ... also don't make the distinction. Is there a heuristic that could be used to make that distinction possible?

Actually, there seems to be an issue with this. If nix.useSandbox (formerly known as nix.useChroot) is set, ssh-config-file won't be reachable from the build process, and building by will fail with something like Can't open user config file /path/to/ssh-config-file: No such file or directory. As soon as nix.useSandbox is disabled, everything work as @Gabriel439 described.
To make this work, I think that fetchgitPrivate needs to take ssh-config-file and ssh-auth-sock as input parameters for overriding the current behavior. I'll try this now and submit a pull-request afterwards if it works.

@k0001 There is one reason that you might want to still preserve the old ability to provide ssh-config-file via the NIX_PATH which is that it's the only way that seems to reliably work with Hydra (since Hydra seems to only let you configure the NIX_PATH when customizing an expression to build)

@Gabriel439 just so that we are on the same page: Are you using NixOps to deploy your Hydra instance? If so, how do you manage the deployment and permissions of the ssh-config-file file specified through Hydra, as well as the deployment and permissions of the associated IdentityFile?

@k0001 I don't use nixops to deploy the Hydra instance.  I just use nixos directly

I may open another issue for this- but I am having a similar problem with fetchcvs. Basically, ssh refuses to authenticate anoncvs without /var/empty/.ssh/known_hosts. I wonder if anyone has any work arounds for this? (Currently all of the CVS stuff is fetched through pserver but that can be hit or miss).

This is resolved now (there is builtins.fetchGit, fetch-git, and fetchgitPrivate that all support this).
@matthewbauer: I've opened #41814.

@jokogr You could pass it via NIX_PATH:
nix-build -I ssh-config-file=/path/to/ssh/config

@yegortimoshenko: as @k0001 mentioned, /path/to/ssh/config is inaccessible in a sandbox, i.e. I get an error like "No such file". Are you using a special path to override this?

You can specify additional paths available in sandbox via extra-sandbox-paths in /etc/nix/nix.conf or nix.sandboxPaths NixOS option.

This is resolved now (there is builtins.fetchGit, fetch-git, and fetchgitPrivate that all support this).

@yegortimoshenko Did you mean that fetchGit supports using the same ssh-config-file and ssh-auth-sock parameters on NIX_PATH that is supported by fetchgitPrivate? If so, what's the point of using fetchgitPrivate then?

For posterity, I had no luck trying to pass 'ssh-config-file' to the Hydra jobset. Instead I moved the config file itself to its standard location for Hydra (/var/lib/hydra/.ssh/config) and it got caught up fine.
Tip: you can more interactively test the evaluation by executing hydra-eval-jobset proj jobsetname as the hydra user. You can directly observe what happens over git/ssh then.

Documenting for posterity that fetchgitPrivate was removed in favor of builtins.fetchGit.  See: https://github.com/NixOS/nixpkgs/commit/e578b8499f9e49441d9761875659381f95975fee

I can confirm that fetchGit currently (Nix 2.13.3) works fine for grabbing private repositories. Here is a working example:
builtins.fetchGit {
  url = "git@github.com:user/repo.git";
  rev = "your commit hash";
}


I have a make error。

Hey, you might want to cmake like this :
cmake -B build . -DCMAKE_BUILD_TYPE=RELEASE -D ENABLE_OPENSTA=ON -DENABLE_ABC=ON
It should work !

Hey, you might want to cmake like this : cmake -B build . -DCMAKE_BUILD_TYPE=RELEASE -D ENABLE_OPENSTA=ON -DENABLE_ABC=ON It should work !

Hi,I encountered other problems, and I couldn't find the answer to them by searching online

Hello, It looks like possibly you don't have tcl or tcl-dev installed, but have cmake flags set to enable tcl? I would try installing those. If that doesn't resolve it, could you post more complete logs, and tell us about the system you're building it on? I was unable to replicate that error locally or when building on a ubuntu 20.04 docker image w/openSTA dependencies installed. (openroad/ubuntu20-dev:latest)

I am not using ubuntu system, but cenos system.I have tcl installed on my system.

Okay, I'll give it a try on CentOS.  Do you also have the tcl-devel package installed?

Okay, I'll give it a try on CentOS. Do you also have the tcl-devel package installed?

Thank you, I uninstalled the previous tcl, reinstalled tcl and tcl-devel, and found that the compilation was successful. Thank you for your help.

I have this error, any help?
[ 94%] Building CXX object core/CMakeFiles/unit_tests.dir/kahypar_config.cpp.o
[ 94%] Building CXX object core/CMakeFiles/unit_tests.dir/kahypar_temp_config.cpp.o
[ 94%] Building CXX object core/CMakeFiles/unit_tests.dir/algorithms/optimization/resynthesis.cpp.o
[ 96%] Building CXX object core/CMakeFiles/unit_tests.dir/utility.cpp.o
[ 96%] Building CXX object core/CMakeFiles/unit_tests.dir/algorithms/partitioning/__tests__/sap_test.cpp.o
[ 96%] Building CXX object core/CMakeFiles/unit_tests.dir/algorithms/partitioning/__tests__/partition_manager_junior_test.cpp.o
[ 96%] Building CXX object core/CMakeFiles/lsoracle.dir/lsoracle.cpp.o
[ 98%] Building CXX object core/CMakeFiles/lsoracle.dir/algorithms/optimization/resynthesis.cpp.o
[ 98%] Building CXX object core/CMakeFiles/lsoracle.dir/kahypar_temp_config.cpp.o
[ 98%] Building CXX object core/CMakeFiles/lsoracle.dir/kahypar_config.cpp.o
[ 98%] Building CXX object core/CMakeFiles/lsoracle.dir/utility.cpp.o
In file included from /lustre/S/matianyun/LSOracle/core/lsoracle.cpp:106:0:
/lustre/S/matianyun/LSOracle/core/commands/output/write_partition.hpp: In member function ‘void alice::write_partition_command::write_part(std::__cxx11::string)’:
/lustre/S/matianyun/LSOracle/core/commands/output/write_partition.hpp:75:21: error: ‘write_child’ is not a member of ‘oracle’
             oracle::write_child<network>(i, partitions, verilog);
                     ^~~~~~~~~~~
/lustre/S/matianyun/LSOracle/core/commands/output/write_partition.hpp:75:40: error: expected primary-expression before ‘>’ token
             oracle::write_child<network>(i, partitions, verilog);
                                        ^
At global scope:
cc1plus: warning: unrecognized command line option ‘-Wno-unneeded-internal-declaration’
make[2]: *** [core/CMakeFiles/lsoracle.dir/lsoracle.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
[ 98%] Linking CXX executable unit_tests
[ 98%] Built target unit_tests
make[1]: *** [core/CMakeFiles/lsoracle.dir/all] Error 2
make: *** [all] Error 2


On accessing images in the directory where the .styl lives

Hello.
I am having trouble configuring the loader to look up in current directory (where the .styl file is located).
Instead it's always trying to load them from root css directory (where the master index.styl) is located.
Any clues ?:)

Figured this out :)

do you mind share your config

You can do this an old way (as stylus-loader versions go) in your webpack config:
module.exports = {
  // ...
  stylus: {
    'resolve url': true,
  },
};

Or a newer way:
var stylus = require('stylus');
module.exports = {
  // ...
  stylus: {
    define: {
      url: stylus.resolver(),
    },
  },
};

The older way uses a stylus-loader specific modification to stylus's resolver to consider webpack paths. So I'd recommend that.


Deploy Jan #2 Update; merge 'master' to 'live'

Docs Build status updates of commit 631fb69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/psexec.md
:white_check_mark:Succeeded
View

sysinternals/downloads/pstools.md
:white_check_mark:Succeeded
View

sysinternals/downloads/sysmon.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 631fb69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/psexec.md
:white_check_mark:Succeeded
View

sysinternals/downloads/pstools.md
:white_check_mark:Succeeded
View

sysinternals/downloads/sysmon.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 589ed80:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/psexec.md
:white_check_mark:Succeeded
View

sysinternals/downloads/pstools.md
:white_check_mark:Succeeded
View

sysinternals/downloads/sysmon.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 589ed80:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sysinternals/downloads/psexec.md
:white_check_mark:Succeeded
View

sysinternals/downloads/pstools.md
:white_check_mark:Succeeded
View

sysinternals/downloads/sysmon.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add domains to whitelist (AliExpress orders tracking)

Add this two domains to the whitelist to prevent them from being blocked. If they are blocked, the tracking inside the AliExpress app doesn't work, and also third party apps can't connect with the cainiao servers to fetch the latest updates on the trackings.
@@||global.cainiao.com^$important
@@||region1.app-measurement.com^$important

We have added the following domains


add a script for running via Docker

This simplifies running with Docker, hiding the complexity of the commands from the user.

Would it make sense to merge my proposed changes from #103 into this PR? I can take care of it if so.

I think they can be reviewed/merged independently.


Need forced restart atom after edit webpack config

Webpack contain resolve aliases. After add or edit alias - Nothing happens(eslint shows an error “import/extensions”). For the changes to take effect restart atom is required. Is it normal? How can i fix it?
"plugins": ["import"],
  "settings": {
    "import/resolver": {
        "webpack": {
            config: 'webpack.config.js'
        }
  },

webpack: 4.8.1
eslint: 4.19.1
eslint-plugin-import: 2.11.0
eslint-import-resolver-webpack: 0.9.0

atom comunity q copy https://discuss.atom.io/t/need-forced-restart-atom-after-edit-webpack-config/54982

Yes, many editors need to be restarted when config or plugins change.

That is surprising given that I am just literally right now publishing the caching for the webpack resolve function.
There is an in-memory cache of resolved files but it has a TTL of 30s, IIRC. if you wait ~1 minute, do you see your changes reflected?

No. only restart atom helped

I don’t think this is an issue with this plugin - atom in particular often needs to be restarted whenever anything changes in its plugin deps.

But changed only 'alias' configuration in general webpack config

https://webpack.js.org/configuration/resolve/#resolve-alias

This in not "changes in its plugin deps".
alias: {
  Utilities: path.resolve(__dirname, 'src/utilities/'),
  Templates: path.resolve(__dirname, 'src/templates/')
}

// Add one line alias

alias: {
  Utilities: path.resolve(__dirname, 'src/utilities/'),
  Templates: path.resolve(__dirname, 'src/templates/'),
  Core: path.resolve(__dirname, 'src/core/')
}

Eslint error in line use alias Core like
import CoreUtil from 'Core/Util';
To apply changes webpack config - restart atom.

Right. This is an atom issue, because restarting atom fixes it :-)

@tebaly I'm not certain about Atom's plugin, but the VSCode plugin for ESLint generates its own server in the background and only reads external configs right when it starts, loading them into memory.  I would ask within the Atom plugin repository if there is a way to manually restart the server or to have the server reload the configuration.


Fixed typo in english version of newly released 2.20 blog post

Closes #2640

It should say that the user requests the certificate to be reissued. Compare to German "ausstellen lassen" and not "ausstellen".

There seems to be an increase in typo spelling errors lately...
Thanks for your support @MikeMcC399 !


Stable Diffusion Subject Fidelity(DINO) and Prompt Fidelity(COCA) Calculation

Dear team, thank you for the comprehensive benchmark of Stable diffusion fine-tune approaches.
Could you give the procedure or snippet of code to calculate the Subject Fidelity(DINO) and Prompt Fidelity (COCA) which were shown in this file: https://github.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/community-content/vertex_model_garden/benchmarking_reports/stable_diffusion_v1-5_benchmarking_report.md ?
I've been searching for these keywords but have not had success yet.

Hi,
Thanks for reading the benchmark!
Unfortunately the DINO and COCA calculation algorithms are from an internal implementation which has not yet open sourced. But I believe we can do something similar by following the two papers. There might also be some open-sourced similar algorithms available.
[1] (DINO)](https://arxiv.org/abs/2104.14294)
[2] prompt fidelity scores (CoCa),


stripe-sync no longer works with a fresh run of npm i

The script does not populate https://dashboard.stripe.com/test/products anymore.

What was the fix?

Hi Kai, The fix was to delete the contents of data after cloning the git repo. stripe-sync.sh will fail if it uses the contents of data as it currently exists in this repo. make clean and then make will work however.


Support Windows platform

https://www.reddit.com/r/rust/comments/4jufvh/which_readlinelike_crate/d3afuv8

I really wish there was a readline-like library which worked for windows as well.

@gwenn I'm gonna start taking a look at this if you don't mind.  Going to refer to https://github.com/MSOpenTech/redis/tree/3.0/deps/linenoise which is the windows port of linenoise.

I don't have access to a Windows machine and I tried Windows VM without success.
And there is another fork with windows support here:
https://github.com/arangodb/linenoise-ng
Regards.

Partial support added in #42.  Rust's stdio module for Windows uses the ReadConsoleW from winapi which does not seem to capture modifier keys (CTRL or ALT).  Some additional work needs to be done to instead use the ReadConsoleInputW in winapi to support the same operations as we do in Linux

@kkawakam History (pressing up arrow) does not work on Windows but I assume this is for the same reason as CTRL and ALT?

@Marwes that is probably the case, you should probably continue using linenoise-rs for support on windows.  I am still working on full windows support right now and hopefully I'll have that out this week.

Ok,
Don't take me wrong but...
I started to look at Windows support by using Wine and cross compiling.

refresh screen:
https://github.com/gwenn/rustyline/blob/master/src/lib.rs#L192
clear screen:
https://github.com/gwenn/rustyline/blob/master/src/lib.rs#L416
console input:
https://github.com/gwenn/rustyline/blob/master/src/lib.rs#L959

I am also looking at this project to support ANSI escape sequence on Windows.
If it looks good to you, I can take some time to merge and send a pull request.
Regards.

@gwenn that is totally fine with me.  The only thing is that I would rather want to this platform specific stuff to live outside of lib.rs (kinda following the pattern we see in rust's std lib).
Also can I add you as a collaborator, I don't have as much time to work on this at this moment and I don't want to really block your progress.

@kkawakam Yes, I will try to move platform specific stuff in the tty module. And I don't know what Wine is emulating. There is no hurry. Take your time.

Is there anything blocking a crates.io release with the windows support that works now? Minor testing on the current master seems to work well at least.
Pinning cargo to a revision works fine at the moment but it prevents publishing off libraries which depend on it as git dependencies are not allowed on crates.io.
Mainly running Windows so if there is something I can help test I'd be happy to (not very familiar with the actual Windows API however).

@Marwes I'm gonna push out a release this week, just gonna additional light testing before pushing it out to crates.io

@Marwes Sorry about the delay, I pushed out a new release (1.0.0)


Error when training process ModuleNotFoundError: No module named 'mmdet'

(mmdet) D:\BalancedGroupSoftmax>python tools/train.py configs/bags/gs_faster_rcnn_r50_fpn_1x_lvis_with0_bg8.py
Traceback (most recent call last):
File "tools/train.py", line 8, in
from mmdet import version
ModuleNotFoundError: No module named 'mmdet'
I got this error when I did the training, is there something wrong? I am looking forward for your repply

请问你解决了吗，我也遇到了，应该怎么去解决呢

I can't solve it.


fix: cluster autoselect

Closes #307

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


SuperDialog be show in pager0 of HorizontalPager instead of current page or full screen

When I use HorizontalPager to design my layout, found that SuperDialog be added in other page which always show in the first page.
At start, I think the Dialog is useless yet.
Therefore, It has showed in first page when I use NavigationBar to turn to first page.
Version is 0.2.9.
These is my layout.
Column {
    HorizontalPager {
        Page0 {
             something()
        }
        Page1 {
            SuperDialog()
        }
    }
    NavigationBar{
        turn2Page0
        turn2Page1
    }
}

I can't reproduce this issue in the sample app. It seems to work fine.

Right, i get it.
it is reason that i dont use Scaffold component of miuix in other page.
this issue can close.


Showing poster should hide the video in the background

Current Behavior:
When loading the player with a poster, where the poster has a smaller resolution than the video, both are shown (the video is always in the background). Tested on latest version 1.5.6.
Expected Behavior:
The video should be hidden and the playback starts.
Example:
https://jsfiddle.net/wqz2mdvy/

Additionally the format of the video is not shown correctly as well. The video is a vertical one.

Thanks for reporting! Ah I see, you can easily fix this with some CSS since the poster doesn't cover the video:
media-poster {
  background-color: black;
}

I'll also contemplate adding this to the default theme.


Upgrade to 4.11 and pre-existent saml2 authentication settings

ISSUE TYPE

Bug Report

COMPONENT NAME

SAML2 Auth plugin

CLOUDSTACK VERSION

4.11

CONFIGURATION

Cloudstack 4.5.2 with SAML2 authentication working well on national federation.
OS / ENVIRONMENT

Clean install of Cloudstack 4.11 on Ubuntu 16.04.4 LTS pointing to a copy of 4.5.2 cloudstack production database.
SUMMARY

After upgrade from 4.5.2 to 4.11 (parallel build process) the http://IP:8080/client show an error (HTTP ERROR 503 -
Problem accessing /client/. Reason: Service Unavailable) and UI does not load.
It appears that pre-existent content of columns "key" and "certificate" of rows with "name" content "SAMLSP_X509CERT" and "SAMLSP_KEYPAIR" need some conversion, but the upgrade procedure did not made it.
If we delete the old saml rows from cloud.keystore table, the /client works but https://IP:8080/client/api?command=getSPMetadata returns an certificate different from that registered on national federation. And so, the authentication fails for our web users.
STEPS TO REPRODUCE

1-) Do a clean install of Cloudstack 4.11.
2-) Point this install to a copy of 4.5.2 production database that has SAML2 authentication enabled and  working inside an federation.
3-) Run cloudstack-setup-databases.
4-) Run cloudstack-setup-management and wait for upgrade completion and  cloudstack-management  service start.
5-) Try to access the UI interface

EXPECTED RESULTS

Can access and use a fully functional Cloudstack UI.

ACTUAL RESULTS

HTTP ERROR 503
Problem accessing /client/. Reason:

    Service Unavailable

Hi @eligorio, I've received a similar email privately. The upgrade steps can be amended to not run cloudstack-setup-databases. Instead, shutdown old mgmt server(s), take db backup for cloud, cloud_usage tables, run cloudstack-setup-databases without --deploy-as (i.e. to add a new management server, without deploying a new database), and start new mgmt server. See if can still reproduce the issue. The upgrade process should not alter the SAMLSP_KEYPAIR and SAMLSP_X509CERT keys/certs in the cloud.keystore table. On new installations, this is only created when SAML plugin is enabled.
If the proposed upgrade process was indeed used, and in case this is a bug I can test this and get back to you after next week.

We reproduced the issue using the recipe of your last comment.

Looks like this is a regression, I'll handle it after next week. I think I know the cause @borisstoyanov. As you can see I've already assigned the issue to myself.

@eligorio I could reproduce and I've fixed the issue. You may test upgrade+saml2 login using this PR: https://github.com/apache/cloudstack/pull/2616
If you're looking for a rpm repo to test against, I'll share that next week on dev ML. I'll close the PR, thanks.


Position part of force_torque sensor pose is ignored and this may be confusing or impractical

Original report (archived issue) by Silvio Traversaro (Bitbucket: traversaro).

TL; DR: There is bug in Valkyrie F/T sensor model that could cause up to 20 Nm of error between the simulated F/T measure and the real one.
Back in https://bitbucket.org/osrf/gazebo/issues/940/force-torque-sensor-forcetorquesensorcc , the semantics for force_torque sensor pose tag was defined.
In particular it was decided (probably for back-compatibility) that the point with respect to which the measured torque is expressed was always the origin of the "joint" frame, regardless of the sensor pose and of the frame tag (see https://bitbucket.org/osrf/gazebo/issues/940/force-torque-sensor-forcetorquesensorcc#comment-9473056).
Personally I was ok with this, because I always modeled six axis force torque sensors as "fixed" joints (as described in https://bitbucket.org/osrf/gazebo/issues/940/force-torque-sensor-forcetorquesensorcc#comment-9485945), for which the origin of the joint frame can be freely assigned without any other constraint.
However recently I was porting some estimation software to the Walkman robot ( https://www.walk-man.eu/ ) and I noticed that in building their SDF they choose a different option: they modeled their F/T sensors as sensors measuring the force transmitted over a non-fixed joint. The Walkman model is not public, but then I noticed that the same choice was done in the SDF of the Valkyrie robot, see for example:
    <gazebo reference="${joint_to_attach_sensor_to}">
      <sensor name="${sensorName}" type="force_torque">
        <pose>${origin_xyz} ${origin_rpy}</pose>
        <sensor_number id="${sensor_number}" />
        <node id="${sensor_node}" />
        <api name="${sensor_api}" />
        <always_on>true</always_on>
        <update_rate>500.0</update_rate>
        <force_torque>
          <frame>sensor</frame>
          <measure_direction>parent_to_child</measure_direction>
        </force_torque>
    	</sensor>
    </gazebo>

See https://gitlab.com/nasa-jsc-robotics/val_description/blob/master/model/robots/common/xacro/sensors/ati_force_torque.xacro#L16 .
As in the case of the Walkman, even here the force_torque sensor is instantiated with a non-zero origin_xyz in
<xacro:ati_force_torque_sensor sensorName="${prefix}FootSixAxis"
                               parentLink="${AnkleRollLinkName}"
                               joint_to_attach_sensor_to="${AnkleRollJointName}"
                               origin_xyz="0.0215646 0.0 -0.051054"
                               origin_rpy="3.14 0.0 0.0"
                               sensor_number="${ATI_serial_number}"
                               sensor_node="${ATI_node}"
                               sensor_api="${ForceTorqueSensorApi}" />

See https://gitlab.com/nasa-jsc-robotics/val_description/blob/master/model/robots/common/xacro/leg/leg.xacro#L173 .
Modelling the F/T sensor as attached to a non-fixed joint can make sense if the mass of the flange connecting the F/T sensor with its revolute joint is small enough and its weight and dynamical effect can be safely disregarded. However the presence of a non-fixed joints constraints the joint frame origin to be on the joint's revolution axis, and prevents to correctly simulate a sensor whose origin does not lie on the revolution axis. As far as I understood is the case in Walkman/Valkyrie, and the authors of those models tried to encode the position offset between the joint frame and the sensor frame using the sensor pose, apparently ignoring that the position part would be ignored.
I don't know if there is an easy way to fix this issue in these models. Two possible ways can be:

create a new value for the frame tag: a sensor_posandrot (better name preferable) that means  that the sensor orientation is used to express the wrench, and the sensor origin is used as the point with respect to which the torque is expressed,

or considering that any model with a non-zero sensor position offset for a force_torque sensor is broken, we can just modify the definition of <frame>sensor</frame> to "the sensor orientation is used to express the wrench, and the sensor origin is used as the point with respect to which the torque is expressed".

The problem described in this issue created an error in FT sensor frame localization that went unnoticed for three years: https://github.com/icub-tech-iit/ergocub-software/issues/146 .

Back in https://bitbucket.org/osrf/gazebo/issues/940/force-torque-sensor-forcetorquesensorcc , the semantics for force_torque sensor pose tag was defined.
In particular it was decided (probably for back-compatibility) that the point with respect to which the measured torque is expressed was always the origin of the "joint" frame, regardless of the sensor pose and of the frame tag (see https://bitbucket.org/osrf/gazebo/issues/940/force-torque-sensor-forcetorquesensorcc#comment-9473056).
Personally I was ok with this, because I always modeled six axis force torque sensors as "fixed" joints (as described in https://bitbucket.org/osrf/gazebo/issues/940/force-torque-sensor-forcetorquesensorcc#comment-9485945), for which the origin of the joint frame can be freely assigned without any other constraint.

I can't edit the original post as I don't have write permission on this repo, but updating the reference to working links this is:

Back in https://github.com/gazebosim/gazebo-classic/issues/940 , the semantics for force_torque sensor pose tag was defined.
In particular it was decided (probably for back-compatibility) that the point with respect to which the measured torque is expressed was always the origin of the "joint" frame, regardless of the sensor pose and of the frame tag (see https://github.com/gazebosim/gazebo-classic/issues/940#issuecomment-616046923).
Personally I was ok with this, because I always modeled six axis force torque sensors as "fixed" joints (as described in https://github.com/gazebosim/gazebo-classic/issues/940#issuecomment-616046930), for which the origin of the joint frame can be freely assigned without any other constraint.


Cwl browse

This testing .So please tell me this process is correct or wrong

Yes, this looks OK - except you are committing an extra Readme.md~ - Emacs backup file?
Now could you try to remove that locally with git rm and git commit, then git push again - it should update this pull request.

How about now

Thanks!

Remember to pull as I also merged latest master


Accessability

Added alternative image text
Resized fonts
Used appropriate headers

Portfolio Accessibillity 💯 👍

Add form label to Portfolio
Fix linter Errors ✅

Reviewer's review 💯

Worked on the Reviewer's review
-

 🔥

No Linters errors 👍


Tools for label image

TrainingData.io: TrainingData.io is a medical image annotation tool for data labeling. It supports DICOM image format for radiology AI.
Spare5: Spare5 is a crowdsourcing service for tasks such as data and image annotation, language assessment, and more.
Hive: Hive is a text and image annotation service that helps you create training datasets for content categorization, computer vision, and more.
Appen: Appen provides training data for machine learning models. It provides data annotation solutions for computer vision, text annotation, automatic speech recognition, and more.
Figure Eight: Figure Eight (now an Appen company) is a data annotation platform that supports audio and speech recognition, computer vision, natural language processing, and data enrichment tasks.
Scale: Scale’s API is a data annotation outsourcing company that you can use to create the ground truth for your machine learning models.
Labelbox: Labelbox is a platform for data labeling, data management, and data science. Its features include image annotation, bounding boxes, text classification, and more.
VGG Image Annotator: VGG is an open source image labeling tool that for straightforward tasks that do not require project management. It is available as an online interface and can also be used offline as an HTML file.
Supervise.ly: Supervise.ly is an image annotation and data management tool that you can use create image and video datasets for machine learning models. The platform also includes a self-hosted infrastructure for training your machine learning models and continuing to improve them with human-in-the-loop.
RectLabel: RectLabel is an image annotation tool that you can use for bounding box object detection and segmentation, compatible with MacOS. It includes efficient features such as Core ML to automatically label images, and export to YOLO, KITTI, COCO JSON, and CSV formats.
Prodigy: Prodigy is an annotation tool for various machine learning models such as image classification, entity recognition and intent detection. You can stream in your own data from live APIs, update your model in real-time, and chain models together to build more complex systems.
Lucas é daqui pra baixo
Dataturks: Dataturks is a data annotation outsourcing company that offers many data annotation capabilities, including image segmentation, named entity recognition (NER) tagging in documents, and POS tagging.
ImageTagger: ImageTagger is an open source online platform for collaborative image labeling.
Fast Annotation Tool: Fast Annotation Tool is an open source online platform for collaborative image annotation for image classification, optical character reading, etc.
LabelMe: LabelMe is an open data annotation tool to build image datasets for computer vision research.
Playment: Playment is an image annotation company that you can use to build training datasets for computer vision models. The services offered include bounding boxes, cuboids, points and lines, polygons, semantic segmentation, and object recognition.
Cogito Tech: Cogito Tech provides machine learning training data. The services offered include image annotation, content moderation, sentiment analysis, chatbot training, and more.
OCLAVI: OCLAVI provides annotation tools to help machine learning models learn.
Humans in the Loop: This tool provides data labeling to train and improve your machine learning solutions. Their use cases include face recognition, autonomous vehicles, and figure detection.
WorkAround: WorkAround is a training data annotation platform for AI developers. From open data to business, you can host and annotate data, manage projects, and build datasets alongside top universities and companies.
TaQadam: TaQadam offers on-demand annotation with agents-in-the-loop. Equipped with our mobile application, agents have a simple and secure way to work on your dataset.
Anno-Mage: Anno-Mage is a new image annotation tool that incorporates an existing state-of-the-art object detection model called RetinaNet to show suggestions of 80 common object classes while annotation to reduce the amount of human effort to be put in to annotate images.

https://hackernoon.com/the-best-image-annotation-platforms-for-computer-vision-an-honest-review-of-each-dac7f565fea

https://lionbridge.ai/articles/image-annotation-tools-for-computer-vision/

https://hackernoon.com/how-to-label-data-create-ml-for-object-detection-82043957b5cb

https://app.labelbox.com/
Esse é legal pelas informações que ele da juntamente com os labels que são criados, mas nada automático.


update data docs re: new BQ schema

The new pipeline parses data in to new BQ tables, with a new schema, and new features like date indexing. Update the data docs to reflect the new tables, schema and features.

This work is mostly done and is being tracked here: critzo/m-lab.github.io:newschema


Server availability

The reason I switched over to issuestats.com instead of isitmaintained.com was because the server was not always available, the load time of repository pages was incredibly low as badge loading times were slow.
Unfortunately I'm experiencing the same issues on issuestats.com. Since a few days the site is not available for me, or not all assets will be loaded:

Often the error looks like:

So I'm asking you Hank @hstove, what server technology is used for issuestats.com? Maybe we can find a solution for a better availability.

@hstove Seems like you are uninterested in your own service. Will think about removing it from all of my repos and recommend this also to others.

@julmot indeed, this has always been a free and open source project that was primarily built for Github's data challenge. It was never meant to be a 'startup' or 'service'. I sadly just haven't had the time to maintain it lately. I have no problem with you recommending isitmaintained over issuestats, it seems like a great project and is also currently maintained.
I appreciate you using issuestats!


Add option "use windows authentication" in connection Assistant for SQL Server

that's it

Definitely need this as an option. We have a couple of servers where SQL Authentication is disabled.

Currently, the mssql driver uses tedious which does not support windows authentication. However, msnodesqlv8 driver has support for this.
I have created a fork of the mssql extension that allows you to choose between tedious or msnodesqlv8: https://marketplace.visualstudio.com/items?itemName=fzhem.sqltools-driver-mssql-commver


Failure with typelevel compiler and induction heuristics

Given this example:
case class Id[T](value: String)

object Id {
  implicit def idEncoder[T]: Encoder[Id[T]] = Encoder[String].contramap[Id[T]](_.value)
}

case class Foo(x: String)
case class Foobar(id: Id[Foobar], foo: Foo)

object Foobar {
  implicit val fooEncoder: Encoder[Foo] = deriveEncoder
  implicit val foobarEncoder: Encoder[Foobar] = deriveEncoder
}

This compiles fine on lightbend scala and typelevel scala but if I enable -Yinduction-heuristics in the latter this suddenly fail at the derivation of Encoder[Foobar].
If I change the Foobar object to:
object Foobar {
  implicit val fooEncoder: Encoder[Foo] = deriveEncoder
  implicitly[Encoder[Id[Foobar]]]
  implicit val foobarEncoder: Encoder[Foobar] = deriveEncoder
}

then it doesn't fail on the foobarEncoder but crashes the typelevel compiler triggering this bug:
https://www.bountysource.com/issues/46109047-compiler-error-with-yinduction-heuristics
This version manage to compile fine instead:
object Foobar {
  implicit val fooEncoder: Encoder[Foo] = deriveEncoder
  implicit val foobarIdEncoder: Encoder[Id[Foobar]] = implicitly
  implicit val foobarEncoder: Encoder[Foobar] = deriveEncoder
}

Thanks for the report! My current goal is to have all tests passing on TLC with options like -Yinduction-heuristics enabled by the 0.10.0 release, but I'm not sure it'll happen by 0.9.0.

Closing in cleanup run, If anyone cares about this, please comment and I'll reopen.


Attack Simulator - please confirm "applies to" eligibility.

Could we please confirm the intention of the "Applies to" table? Attack simulator isn't available in P1-only environments.
If the intention is for it to be there because anyone can sign up for a P2 trial to use it, then perhaps further clarification would be warranted? It's a little misleading currently, and not consistent with docs for other attack simulation tooling (e.g., with Defender for Office, documentation clearly states that it only applies to P2).
Otherwise, this doc may have been incorrectly updated to include the "Applies to" section with the rest of the bulk updates in October 2021 (commit https://github.com/MicrosoftDocs/microsoft-365-docs/commit/0091839969f4bb4b58868b7d6a8a5cfc47244eb1).
Thanks!
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e038c807-ffc4-5594-06c9-20f8edec48c2
Version Independent ID: e501e36c-36a2-c6ee-cf09-12a4e62c069e
Content: Experience Microsoft Defender for Endpoint through simulated attacks
Content Source: microsoft-365/security/defender-endpoint/attack-simulations.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @Dansimp
Microsoft Alias: maccruz

@Sizzl Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10543
Once the author approves, the changes will be live.
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @Sizzl Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Messaging/ Alert system

Hello everybody,
as a small pool operator, I currently stumble across overcrowded pools every day and what is even worse:
Retired pools currently have a total of over 17 million ADAs delegated!
My idea was to implement a kind of messaging / alert system in Daedalus, where the delegator in the system receives a message,
that he is currently staked in a pool that is either overcrowded or that the pool is retired.
Would this idea be a possible approach to draw attention to it?
P.S .: I have already introduced myself to @nikolaglumac as a developer and I hope to be able to contribute soon! :)
Arthur (WISE-Pool)

Hi Arthur :-)
Can you expand on the idea?
What messaging/alert type do you have in mind?
Also, we are limited to showing the alerts only once Daedalus is running.
E.g. if you delegate and then don't run Daedalus for a year (during which time the SP you delegate to retires), we have no way to notify the user.
More info is greately appreciated!
Thanks!

Thats an interesting idea ... but I wonder if this should be a 3rd party service maybe optionally initiated from within the wallet - ie. you could (optionally) provide your email and and pool id to a monitoring service who would email you if the pool over-saturates, goes down or gets retired. Then you you're not reliant on having to check the wallet to see if the pool is still active?
If I delegated and came back after a year to find out my pool had been retired for most of the previous year I'd be pretty mad.
But maybe such functionality is outside of the scope of the wallet's responsibility and the onus should be on the delegator to monitor their pool appropriately?

Hi Arthur :-)
Can you expand on the idea?
What messaging/alert type do you have in mind?
Also, we are limited to showing the alerts only once Daedalus is running.
E.g. if you delegate and then don't run Daedalus for a year (during which time the SP you delegate to retires), we have no way to notify the user.
More info is greately appreciated!
Thanks!

Of course, you can only send a notification when the application is running.
First, a "warning message" could be displayed when someone wants to delegate to an overcrowded pool.
It would also be important that the delegator receives a notification as soon as a pool is classified as retired.
At the first step a in-app alert system would be good and maybe a desktop push notification.
Maybe a optional subscription from daedalus wallet with a email connection could be a possible second solution to reach delegators outside the application.

Thats an interesting idea ... but I wonder if this should be a 3rd party service maybe optionally initiated from within the wallet - ie. you could (optionally) provide your email and and pool id to a monitoring service who would email you if the pool over-saturates, goes down or gets retired. Then you you're not reliant on having to check the wallet to see if the pool is still active?
If I delegated and came back after a year to find out my pool had been retired for most of the previous year I'd be pretty mad.
But maybe such functionality is outside of the scope of the wallet's responsibility and the onus should be on the delegator to monitor their pool appropriately?

Yes, this was also in my mind to create a API and link the wallet to a email or similar.

All of this would require Daedalus to be constantly running and that is not realistic.
It is obviously a 3rd party service requirement that needs to be integrated with Daedalus.
As far as Daedalus goes the best we can do is to run a check to see if any of the wallets you have are delegated to a retired stake pool and raise an alert in case they are...

As far as Daedalus goes the best we can do is to run a check to see if any of the wallets you have are delegated to a retired stake pool and raise an alert in case they are...

This would be a great step!

All of this would require Daedalus to be constantly running and that is not realistic.
It is obviously a 3rd party service requirement that needs to be integrated with Daedalus.

Do you have an idea how best to integrate with a 3rd party app to daedalus? A plugin, a api?

An API would do.

@aleincsharp PoolTool on android can provide you updates if the pool changed fees, became over-saturated or produced a new block.
Regardless, this feature is important to have in Daedalus as well. Daedalus have wider adoption

@aleincsharp PoolTool on android can provide you updates if the pool changed fees, became over-saturated or produced a new block.
Regardless, this feature is important to have in Daedalus as well. Daedalus have wider adoption

Yes, the pooltool and adapools apps can do this.
I am working currently on the API! Because this API i a part of my bigger platform/solution it takes more time for now. But i hope to get the first version online soon!

This incident might have been the sort of thing a delegator would have wanted to know about - Pool operator increased margin to 99% just before the end of Epoch:
https://twitter.com/SproutPool/status/1390036177407725568

This incident might have been the sort of thing a delegator would have wanted to know about - Pool operator increased margin to 99% just before the end of Epoch:
https://twitter.com/SproutPool/status/1390036177407725568

Yes, i am working on multiple notifications through telegram, email, twitter, etc.
Because this project/API is a part of my new plattform (https://ada-data.eu/), it takes a little bit longer to implement.

@aleincsharp is that project of yours publicly available? AKA. open source?

@aleincsharp is that project of yours publicly available? AKA. open source?

At the moment no, but i plan to do it, yes!
There is a lot to do, but unfortunately I don't have that much spare time with a normal job. I do it like many others in my spare time. I'll do my best and hurry up! :)

Thanks for all the efforts @aleincsharp!
We need to open more direct communication in order to integrate your service within Daedalus.
Perhaps you could prepare an architectural overview or a plan and present it to us in a call?
We would be glad to push this forward in the 2nd part of May.
cc @darko-mijic

I meant like Google Meet session.

I meant like Google Meet session.

We can schedule the meeting on any platform. As it suits you best.

Hi @aleincsharp! That's great to hear!
I'll reach out to you near the end of next week and we'll find a slot which works for all of us :-)
Looking forward to it!

Has anything happened on this front since 20th of May? Just wondering...

Has anything happened on this front since 20th of May? Just wondering...

Yes, working again on it after a forced break...will try to release first steps soon.


Javalin 4: Construct validator from typed object

Describe the feature
In Javalin 3 Validator could be constructed from typed object:
open class Validator<T>(val value: T?, val messagePrefix: String = "Value", val key: String = "Parameter") {
...

In Javalin 4 the only way to construct Validator is to convert from string to typed object.
Additional context
This makes harder to convert code from Javalin 3 to Javalin 4, when Javalin's Validator used for validation of existing typed objects. To migrate such code, I'd not like to convert back and forth to/from string to get object into Validator, especially if object contains input stream with potentially long data.
p.s. I can try to submit patch for this.

@IvanPizhenko You're welcome to submit a patch, but I can't guarantee it will be merged. There was quite a lot of cleanup related to the validation for v4, which moved type conversion to 1 location. It might make sense to split the current implmentation into type-conversion and validation though, and then you could maybe use the validation part directly?

@tipsy I've submitted PR. I actually did sort of what you talk about above.

So please check this PR, and I hope this can be merged.

@IvanPizhenko The class hierarchy is getting a little out of hand here. Could this be solved simpler?

Good question. But I think I have an idea. Will make another PR.

@tipsy Please look at #1396


FZF style selection menus for building richer UI’s

Summary of the new feature / enhancement
I would love to see a richer set of terminal focused UI commands so I can ship scripts that are more friendly to use for users, without requiring them to pull in a lot of dependencies.
Ever since the release of fzf (https://github.com/junegunn/fzf), fuzzy search in a terminal is a core interaction for any application where I want a less than perfect answer. Say I want to find a file in a folder or search through git branches, fuzzy search allows me to pass in related characters in hope that I might discover what I’m looking for.
Proposed technical implementation details (optional)
Implement a Find-ItemFuzzy or Get-Item -Interactive that users can pipe entries into / pass in an arg to for fuzzy searching through a list of values.

There have been a few requests for fuzzy features and they generally suggest they should be implemented as PSGallery modules.
https://github.com/PowerShell/PowerShell/issues/11298
https://github.com/PowerShell/PowerShell/issues/21163
https://github.com/PowerShell/PowerShell/issues/11487

there is a fairly new module, PowerShellRun
it's very nice and has alot of configuration options.
It does support piping a filelist into it to use the fuzzy search Invoke-PSRunSelector


Customize post_logout_redirect_uri validation in OIDC RP-initiated logout

Context
In local development scenarios, some auth servers relax some specified constraints. For example, in Tanzu, we have use-cases where we remove redirect_uri validation in OAuth2AuthorizationCodeRequestAuthenticationProvider through the OAuth2AuthorizationCoderRequestAuthenticationProvider#setAuthenticationValidator hook.
Feature request
We want to turn off post_logout_redirect_uri validation in OidcLogoutAuthenticationProvider, but it is currently hardcoded.
We would like to have a similar #setAuthenticationValidator in OidcLogoutAuthenticationProvider. We are interested in the redirect uri validation, but maybe this extends to the client identity (e.g. aud claim).
Workaround
For our workaround, we have custom OidcLogoutAuthenticationProvider that wraps around the original, and modifies the client registration (not great). We rely on our custom RegisteredClientRepository and RegisteredClient implementations:
class SsoOidcLogoutAuthenticationProvider implements AuthenticationProvider {

	private final OidcLogoutAuthenticationProvider delegate;

	private final OAuth2AuthorizationService authorizationService;

	private final SsoRegisteredClientRepository registeredClientRepository;

	public SsoOidcLogoutAuthenticationProvider(OidcLogoutAuthenticationProvider delegate,
			OAuth2AuthorizationService authorizationService, SsoRegisteredClientRepository registeredClientRepository) {
		this.delegate = delegate;
		this.authorizationService = authorizationService;
		this.registeredClientRepository = registeredClientRepository;
	}

	@Override
	public Authentication authenticate(Authentication authentication) throws AuthenticationException {
		OidcLogoutAuthenticationToken initialAuth = (OidcLogoutAuthenticationToken) authentication;

		OAuth2Authorization authorization = this.authorizationService.findByToken(initialAuth.getIdTokenHint(),
				new OAuth2TokenType(OidcParameterNames.ID_TOKEN));
		// ... handle error
		SsoRegisteredClient registeredClient = this.registeredClientRepository
			.findById(authorization.getRegisteredClientId());
		// ... handle missing redirect_uri

		// 🚨 Here we modify the registered client to add the current request's
		// post logout redirect uri to the allow-list
		registeredClient.addPostLogoutUri(initialAuth.getPostLogoutRedirectUri());

		return this.delegate.authenticate(initialAuth);
	}

	@Override
	public boolean supports(Class<?> authentication) {
		return this.delegate.supports(authentication);
	}

}

Happy to contribute a PR if that's a valid use-case.

@Kehrlann Thanks for the details and we can certainly add this enhancement. Would you be interested in submitting a PR that adds OidcLogoutAuthenticationProvider.setAuthenticationValidator()?

@jgrandja
Yes, happy to submit a PR. I’ll look at it next week.


strange behavior when using 'setopt ignoreeof' and zsh-syntax-highlighting

I have setopt ignoreeof at the beginning of my .zshrc file. Normally, when I pres ctrl+d I get following message: zsh: use 'exit' to exit. That is desired behavior.
Now when I source sh-syntax-highlighting in .zshrc, suddenly ctrl+d  behaves weird. When I pres ctrl+d I get a list of all available commands, and at the bottom of the screen At Top: Hit TAB for more, or character to insert.

This is another variant of issue #245.  The fix to this issue is to be merged soon, however, it requires zsh 5.3.  Until then, you can try the following workaround:
ctrl-d() { zle -M "zsh: use 'exit' to exit."; return 1 }
zle -N ctrl-d

Put that in your .zshrc before sourcing z-sy-h.  (I tried just bindkey -r "^D", but that removed the use 'exit' to exit message as well.)
For future reference, the message you got is because Ctrl+d also serves as a "list completions" binding; it is bound to the delete-char-or-list widget, not to delete-char.

Sorry, that example was incomplete.  It needs another line:
ctrl-d() { zle -M "zsh: use 'exit' to exit."; return 1 }
zle -N ctrl-d
bindkey '^D' ctrl-d

Fixed on the feature/redrawhook branch.

I can't reproduce this. Starting from zsh -f
setopt ignoreeof
. <path to z-sy-h>
<ctrl-d>

I get the zsh: use 'exit' to exit. message. zsh 5.9 and z-sy-h 0.8.0.


Added little informantion about flask and dotenv.

#325

Dynaconf 3.0.0 (next release) is no more loading .env by default, thanks


add: unit testing on power platform

This PR adds some information about how to perform unit testing on Power platform custom connectors!

After reviewing the comments - please merge in the latest version of the repo to solve the markdown-link-check problems

Once #607 is merged in all outstanding PRs including this one will have to make a few changes and merge master to adopt the new MKDocs structure. This main change is that all the md files move into a docs folder. Please don't hesitate to reach out with any questions and a number of us are more than happy to help with this process - reach out to @fnocera @TessFerrandez @omri374 and @brockneedscoffee

@Guilhermeslucas could you address the conflicts so that we can get this contribution merged in? Please reach out if I can help with anything!


Predictable wheel URL redirect broken for tbvaccine package

The only documentation about the predictable URLs I found is here, combined with the PEP 0491 section about the wheel file name convention. Predictable wheel URLs can therefore be constructed like this:
info = dict(
    distribution='tbvaccine',
    version='0.3.1',
    python='py2.py3',
    abi='none',
    platform='any',
)

info_wheel_file_name = {
    tag: re.sub("[^\w\d.]+", "_", part, re.UNICODE)
    for tag, part in info.items()
}

wheel_file_name = '{distribution}-{version}-{python}-{abi}-{platform}.whl'.format_map(info_wheel_file_name)

url = f'https://files.pythonhosted.org/packages/{info["python"]}/{info["distribution"][0]}/{info["distribution"]}/{wheel_file_name}'

This results in the URL: https://files.pythonhosted.org/packages/py36/t/tbvaccine/tbvaccine-0.3.1-py2.py3-none-any.whl
Expected behavior
I expect this URL to redirect to the correct file, but it only gives me 404:
To Reproduce
$ curl -I 'https://files.pythonhosted.org/packages/py2.py3/t/tbvaccine/tbvaccine-0.3.1-py2.py3-none-any.whl'
HTTP/2 404
content-type: application/octet-stream
server: nginx/1.13.9
accept-ranges: bytes
date: Thu, 07 Mar 2019 11:52:05 GMT
age: 0
content-length: 0
...

** Additional Info **
Weirdly, “Python version” is “3.6” on the file list:

Filename, size & hash
File type
Python version
Upload date

tbvaccine-0.3.1-py2.py3-none-any.whl (8.2 kB)
Wheel
3.6
Dec 14, 2018

The reference you referred to also ends with:

In general this is only a good idea for source as a python_version to fetch tar and zip files.

And that's the only example it shows. Given that, I wouldn't expect this to work for .whl files.
The official guidance is to use the provided API to find a download location. As the redirect service exists only for historical artifacts, I doubt it will be expanded to handle new artifacts and may even be dropped some day.

Hi! The docs aren’t completely truthful, the existence of these URLs is as deliberate as my usage of them instead of the API. If you’re interested in why the predictable wheel URLs exist, please read up in #1944. The short version: It’s for downstream packagers (like linux distribution packages; .deb, .rpm, .pkg.tar.xz, …), where the ability to access a JSON API instead of plain URLs is not always given.

Please don’t take this the wrong way, but I recommend that you improve the style of your online communication. This looking like a bug is independent of the JSON API existing or not. Therefore it’s not very nice to point out that I’m “holding it wrong” (regardless of that assumtion being true or not).
 I don’t know why it fails, but did you know that the preferred way to fetch packages is to retrieve the URL using the JSON API?”
I’ll send a PR improving the docs so that nobody in the future draws the same conclusions that you did.

Hmm, I since figured out that “Python version” in the file list is what has to go in place of the first python_tag:
$ curl -I 'https://files.pythonhosted.org/packages/3.6/t/tbvaccine/tbvaccine-0.3.1-py2.py3-none-any.whl'
HTTP 302
...

That seems like a bug to me. Shouldn’t python_version always correspond to the python_tag in the wheel filename?


In period form, Star year and End year can not have the negative periods

when you add any period, start year and end year should not be negative and start year should always be less that end year. expecting to have some alert message for admin.

Adding on to this issue, the values for start/end year could be expanded to include Common Era(CE) and Before Common Era(BCE). If this does happen, negative values could be used as BCE values while positive values are CE

Current update:

ive implemented the Star year and End year can not have the negative periods and that End year must always be greater than Start Year. However, I am still failing the test suite. Please help lmao.

It is passing all the integration tests


vcpkg: fix toolchain to correctly set the CMAKE_SYSTEM_PROCESSOR vari…

…able
Some build fails because cmake expects the CMAKE_SYSTEM_PROCESSOR to
be correctly set with the system processor flavour.
scripts/toolchains/linux.cmake fails to set it, while other
toolchains correctly set it (see osx.cmake) for example.
This patch fix this bug.

I am seeing new build failures on the following ports with this PR. Let me know if you need build log.
Processing x64-linux                      579 vs 585
     caffe2                        **regression**                Fail vs Pass
     forest                        **regression**                Fail vs Pass
     libuuid                       **regression**                Fail vs Pass
     sobjectizer                   **regression**                Fail vs Pass

This would probably fix issues currently seen on #4635

I had an open PR to address this same issue, but it got closed when we deleted all the branches on this repo.
I'll resubmit it once I have more time to keep working on the issue.
https://github.com/Microsoft/vcpkg/pull/5697

Fixed in #6872


nixos/lib: compress make-ext4-fs with bzip2

Motivation for this change
The AArch64 build has been failing for a few days with the output of it's ext4 image being >2.0GB. This compresses it with bz2, thus solving the problem.
I'll add that currently we compress all these large images with bz2, which is very slow, I'd like to suggest a change to zstd or lzo. This would be specially meaningful in architectures where usually there are more cores at the expense of clock (since compression/decompression is single threaded.) In particular ARM families would benefit, with no downside to other arches. I am preparing this in another branch, but would like to see this one merged first.
Things done

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

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

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

Notify maintainers
cc @samueldr @andir @grahamc @cleverca22

Difference between bzip2 and zstd
❯ time bzip2 -k nixos-sd-image-20.03pre204199.3140fa89c51-aarch64-linux.img
bzip2 -k nixos-sd-image-20.03pre204199.3140fa89c51-aarch64-linux.img  145.93s user 0.44s system 99% cpu 2:26.39 total
❯ time zstd nixos-sd-image-20.03pre204199.3140fa89c51-aarch64-linux.img
nixos-sd-image-20.03pre204199.3140fa89c51-aarch64-linux.img : 26.99%<PHONE_NUMBER> => 591009441 bytes, nixos-sd-image-20.03pre204199.3140fa89c51-aarch64-linux.img.zst)
zstd nixos-sd-image-20.03pre204199.3140fa89c51-aarch64-linux.img  6.50s user 0.33s system 110% cpu 6.196 total

I've done the work to use zstd in another branch and the difference is staggering.

[105 built, 33 copied (814.4 MiB), 187.4 MiB DL]
https://github.com/NixOS/nixpkgs/pull/75595
55 package were built:
vimPlugins.UltiSnips vimPlugins.agda-vim vimPlugins.airline vimPlugins.calendar vimPlugins.coc-lists vimPlugins.coc-nvim vimPlugins.coc-pairs vimPlugins.coc-rls vimPlugins.coc-snippets vimPlugins.coc-tabnine vimPlugins.coc-tsserver vimPlugins.coc-yank vimPlugins.csv vimPlugins.denite vimPlugins.deoplete-fish vimPlugins.deoplete-jedi vimPlugins.deoplete-lsp vimPlugins.deoplete-nvim vimPlugins.dhall-vim vimPlugins.echodoc vimPlugins.editorconfig-vim vimPlugins.falcon vimPlugins.fugitive vimPlugins.gentoo-syntax vimPlugins.gv-vim vimPlugins.jedi-vim vimPlugins.lightline-vim vimPlugins.ncm2-ultisnips vimPlugins.neosnippet vimPlugins.neoterm vimPlugins.neoyank-vim vimPlugins.polyglot vimPlugins.quick-scope vimPlugins.quickfix-reflector-vim vimPlugins.seoul256-vim vimPlugins.table-mode vimPlugins.targets-vim vimPlugins.tmuxNavigator vimPlugins.vim-airline-themes vimPlugins.vim-flagship vimPlugins.vim-go vimPlugins.vim-grepper vimPlugins.vim-jsx-pretty vimPlugins.vim-mucomplete vimPlugins.vim-orgmode vimPlugins.vim-peekaboo vimPlugins.vim-pencil vimPlugins.vim-plug vimPlugins.vim-ruby vimPlugins.vim-slime vimPlugins.vim-snippets vimPlugins.vim-tmux-focus-events vimPlugins.vim-trailing-whitespace vimPlugins.vimtex vimPlugins.zig-vim

I don't think that the following is an issue with which we should concern ourselves right now, but to be kept in mind for the eventual rewrite.
Writing a temporary file is costly. It could result in failing builds if the $NIX_BUILD_TOP directory ends up in a tmpfs, and memory is in contention. A future approach would better be served if it could avoid copying the files and rather directly compressing / streaming in place.
For the second part (streaming into the final image), it would need metadata written in $out (so $out would not be directly an image file) that tells the image builder what is the size of the image. For the first part, (compression) I guess it depends on what compresses the image file. Are there ways that it can be done in-place? Though, if it's writing in a $out directory, rather than a $out file, the temp file could be in $out and removed as needed if this is a concern.
A final strategy for the future could be to merge multiple snippets into one big honking derivation that does all the work. The main drawback would be that the derivation is less flexible, and takes more time to build. A well architected solution could possibly do this with an option.


[v4] Possible problem rendering components inside

Not sure where the problem is, but using slightly modified examples from the site, I run into problems with rendering layouts.
The goal is being able to pass a layout for a route to be rendered in. The problem is that when using <Switch/>, the layout doesn't get rendered unless I hardcoded it around the switch.
Routes:
const routes = [
  {
    path: '/list',
    exact: true,
    component: List,
    layout: CoreLayout,
  },
  {
    path: '/settings',
    exact: true,
    component: Settings,
    layout: HelpLayout,
  },
];

This works:
<Router>

    <CoreLayout>
      <Switch>
        {routes.map((route, i) => (
          <RouteWithSubRoutes key={i} {...route} />
        ))}
        <Route component={NoMatch} />
      </Switch>
    </CoreLayout>

</Router>

export const RouteWithSubRoutes = route => (
  <Route
    {...route}
    render={props => <route.component {...props} routes={route.routes} />}
  />
);

While I would like this to work:
<Router>

    <Switch>
      {routes.map((route, i) => (
        <RouteWithSubRoutes key={i} {...route} />
      ))}
      <Route component={NoMatch} />
    </Switch>

</Router>

export const RouteWithSubRoutes = route => (
  <Route
    {...route}
    render={(props) => {
      if (!route.layout) return <route.component {...props} routes={route.routes} />;

      return (
        <route.layout>
          <route.component {...props} routes={route.routes} />
        </route.layout>
      );
    }}
  />
);

Obviously I cannot have route based layouts this way.
The route.layout bit seems to be ignored completely while the component  gets rendered. A similar solution worked in alpha with Match and Miss.

Your problem is the componentproperty of the route objects. You should be seeing a warning in your console that you cannot use both component and render. When you do prop spreading you are effectively setting <Route component>. Change the name and your code should work.

Weirdly enough I didn't get anything in the console. Renaming fixed the issue, though. Thanks a lot!

Oh, it looks like the warning was lost at some point in time. I'll look into when that happened and maybe it can be re-added.


error 500: Internal Server Error after succesfull SSO logon

I installed Pathfinder on my server and when I logon successfully it get the attached error message and then I'm logged off.
If I try to logon with a character not in my alliance I get the "Access denied" message. So everything seems to work till there.
Unfortunately there is no error message anywhere on the server to be found. Not in the PHP log, not in the server log.
The error is reported in the browser by jQuery.
I tried several different browsers and pc's. So far nothing worked.

Update: I just found out that when I press escape on the error message I can play a bit with everything not related to the map directly like settings or help.

Are you using Apache or NGINX? Also try checking your access logs, not just your error logs.

having this same problem with apache

Just recently upgraded my MySQL as well and I'm seeing no problems so far...
mysqld  Ver 5.7.17-0ubuntu<IP_ADDRESS> for Linux on x86_64 ((Ubuntu))
Is there anything else useful in any of the logs generated (pathfinder or Apache)?

Solved! Was a cache problem with APCu extension. Disabling it let me in. The following error was shown on the apache log [Fri Jan 27 11:14:46.676324 2017] [:error] [pid 7821] [client <IP_ADDRESS>:50449] apc_store() expects parameter 3 to be long, string given, referer:


Environment variable override file should use function logical ID for…

Environment variable override file should use the function logical ID as the map key.
Fixes #28

+1


Create ruchika pr.md

Hi GSSOC Team!
This is my PR which I raised but not been merge
Could you review and merge it
plz add lvel 3 to this Pr I have only 5 points less for innovator badge by merging this i achieve innovator badge
@sanjay-kv @MastanSayyad @aslams2020
https://github.com/swaraj-das/Collect-your-GamingTools/pull/95

@MastanSayyad

merged

Add level 2 to this PR @MastanSayyad


Testing package

Linked Issue:

Checklist:

[ ] Did you sign the Contributor License Agreement?
[ ] Is the linter reporting 0 errors?
[ ] Did you comply with our styleguide?
[ ] Is there adequate test coverage for your new code?
[ ] Does the CI pipeline pass?
[ ] Did you update the documentation?
[ ] Did you update the sample app?
[ ] Do we need to increment the minor/major version?
[ ] Did you change the public API?
[ ] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

Today we substituted build routines using the swift build command with their xcodebuild counterparts. We decided to make this change to ensure stability and consistency with how our consumers will be building.

Codecov Report

Merging #108 (eec720a) into main (a3bc0bc) will decrease coverage by 4.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #108      +/-   ##
==========================================
- Coverage   94.82%   90.73%   -4.09%
==========================================
  Files          65       20      -45
  Lines        1680      680    -1000
==========================================
- Hits         1593      617     -976
+ Misses         87       63      -24

Impacted Files
Coverage Δ

...wiftCurrent/Models/FlowRepresentableMetadata.swift
100.00% <100.00%> (ø)

Sources/SwiftCurrent/Models/Workflow.swift
98.46% <100.00%> (-1.54%)
:arrow_down:

Sources/SwiftCurrent/TestOnly/TestOnly.swift
100.00% <100.00%> (+10.00%)
:arrow_up:

Sources/SwiftCurrent/TypeErased/AnyWorkflow.swift
13.46% <0.00%> (-69.24%)
:arrow_down:

...ces/SwiftCurrent/Protocols/FlowRepresentable.swift
66.66% <0.00%> (-22.23%)
:arrow_down:

...wiftCurrent/Protocols/OrchestrationResponder.swift
80.00% <0.00%> (-20.00%)
:arrow_down:

...SwiftCurrent/TypeErased/AnyFlowRepresentable.swift
82.60% <0.00%> (-4.35%)
:arrow_down:

...rent_UIKit/Extensions/WorkflowUIKitAdditions.swift

...wiftCurrent_SwiftUI/ViewInspector/Inspection.swift

... and 42 more

Continue to review full report at Codecov.

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

I tweaked all the things and IT PASSED! We got our first pipeline pass!!! WOOOO!!!!!!! 🎉🍻


docs: add documentation for .tailcallrc.graphql

Adds documentation for directives properties in .taillrc.graphql
https://github.com/tailcallhq/tailcall/assets/62795688/441b9109-e019-40dc-8a42-f52f69330585
/fixes #740
/claim #740

@ologbonowiwi  @tusharmath
Hmm do we really need it? seemed self explanatory

IMO, we need it. I usually see newcomers have confusion about @server and @upstream.
As for the other fields, they are self-explanatory to us who are familiar with the project, but I'm not so sure about people who are having their first experience with tailcall

I agree @ologbonowiwi - we should add documentation for everything. Secondly and more importantly, the documentation should be a little more detailed. Currently it looks like GPT generated low effort work (sorry 🙈 )

The original version looked way too verbose for the tiny detail box, that's why I went with a concise version
Will rewrite it

@tusharmath
Pushed a new commit, rewrote it all


Install failure for grpcio python tool kit on MacOS 11 with python 3.9

Hello @lidizheng, @gnossen
I'm having trouble installing grpc for python since my OS upgraded to MacOS 11 with python 3.9. When following the instructions on the website
pip3 install grpcio
the command does not find the binary wheel, downloads the source and tries to build it. The error message is huge. Please refer to the attached file.
When I try to manually install the binary wheel suggested, I get the following errors.
~/antlrPythonTst/OpCodeGrammar » pip3 install wheel ~/Downloads/grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl           j.murphy@8-LM-00086
ERROR: grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl is not a supported wheel on this platform.
~/antlrPythonTst/OpCodeGrammar » pip3 install ~/Downloads/grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl             1 ↵ j.murphy@8-LM-00086
ERROR: grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl is not a supported wheel on this platform.
~/antlrPythonTst/OpCodeGrammar » pythin -m pip install ~/Downloads/grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl    1 ↵ j.murphy@8-LM-00086
zsh: command not found: pythin
~/antlrPythonTst/OpCodeGrammar » python -m pip install ~/Downloads/grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl  127 ↵ j.murphy@8-LM-00086
ERROR: grpcio-1.35.0-cp39-cp39-macosx_10_10_x86_64.whl is not a supported wheel on this platform.
Perhaps I'm being completely thick and missing something extremely obvious. I do apologise if I am. From reading the naming convention of the file, it might suggest this wheel is built for macOS 10 perhaps?
errors.log

hello @lidizheng @gnossen,
I updated my macOSx today and was forced to fix my python installation again. I'm not sure what I did differently to the last time but grpc tools for python installed with a hitch (downloaded & installed the binary wheel). I'm assuming when I did the previous upgrade I did something odd with the python3.9 interpreter.  Thank you for taking the time to look into this problem but I think it can be filed under 'silly user error'.  I'll close the bug report.
Regards,