Create the 2.6.11 release

[x] Create a new migration for the new version, eg. 2.6.11 which should implement getVersion and getReleaseNotes methods
Update the version constant in the project:

[x] package.json
[x] composer.json
[x] .htaccess (minor only)
[x] install/index.php
[x] install/includes/htaccess.txt (minor only)
[x] LICENCE (minor only)
[x] symphony/assets/js/src/symphony.js (minor only)
[x] Update the README.md file, replacing the version constant and updating any metadata as required

[x] Run grunt
[x] Create a commit, usually Release 2.6.x and push to the corresponding branch. Testing at this point is recommended!
[x] Checkout the master branch and merge in the 2.6.11
[x] Create an associated tag for the release, eg. 2.6.11
[x] Create a github release with associated tag, eg. 2.6.11
[x] Generate doc
[x] Upload doc
[x] Create bundle
[x] Upload bundle
[x] Create version 2.6.11 on symext
[ ] Rebase 2.7.x
[ ] Rebase 2.8.x

After a fresh installation using git checkout --track origin/bundle the /install/ says "This script will update your existing Symphony installation to version 2.6.9."

Thanks for spoting it @cylkee I've just rebased on top of master and pushed the bundle. I guess I need to had a new step to the release process. Please delete your local bundle branch before re-running your checkout command.


Future of saleor-sdk

Since Saleor is GraphQL-first API, there is no need to build a classic "SDK" that hides common operations - this is handy for REST APIs.
We aim to provide good docs and using tools around graphQL (like graphql codegen), that automatically "generates SDK" exactly for client needs.
It seems that only benefit of saleor-sdk is to provide reusable logic of authentication.
This issue is to track decision process - of following possibilities:

Deprecate this package and make auth logic part of client (Dashboard, Storefront)
Inject this package into Dashboard/Storefront
Extract new package, specific to auth (eg saleor/auth-sdk or saleor/auth), reuse it in Dashboard, Storefront + custom storefronts

Saleor SDK is DEPRECATED. See the announcement: https://github.com/saleor/saleor/discussions/12891


[1.4.4] vulcanize output has incorrect ordering

I've come across an issue that I can resolve in this instance, but looks like it could point to a larger problem.
I have a polymer 9.0 behaviour defined that looks like:
<link rel="import" href="../other-behavior/other-behavior.html">

<script>
  DatastoreBehavior = [OtherBehavior, { <behaviour content> }];
</script>

With OtherBehavior defined as:
<link rel="import" href="../../../bower/iron-meta/iron-meta.html">

<script>
  OtherBehavior = { <behavior content> };
</script>

The order in which these files are included in the vulcanize output:

DatastoreBehavior
IronMeta
OtherBehavior

i.e. DatastoreBehavior's reference to OtherBehavior is undefined because OtherBehavior is included after DatastoreBehavior.
The complete set of imports in the file being vulcanized:
<link rel="import" href="../../../../bower/test-fixture/test-fixture.html">

<link href="../my-datastore.html" rel="import">

and of 'my-datastore.html'
<link rel="import" href="../../../bower/polymer/polymer.html">

<link rel="import" href="../../../components/datastore-behavior/datastore-behavior.html">
<link rel="import" href="../../../components/other-behavior/other-behavior.html">

Note: I don't actually need other-behavior.html here - it just demonstrates the problem - i.e. that the import ordering in 'my-datastore.html' appears to be trumping an actual dependency ordering - namely that datastore-behavior.html declares a dependency on other-behavior.html, but the sibling ordering in my-datastore.html takes precedence. Seems this should be the other way around?

I think this is fixed in 1.8.1 which uses hydrolysis 1.12 and an ordering fix: https://github.com/Polymer/hydrolysis/pull/117.
Please reopen if this is not the case.


#50526 issue: CodeAlly Down flag fixed and added margin on top

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #50526

Thank you for opening this pull request.
We’ve reviewed your pull request and decided not to merge it; However, We would welcome future pull requests from you.
You are welcome to read these guidelines to learn more about contributing to this project.
Happy contributing.


MetricsEndpointProvider should not add Juju unit charm labels by default

Bug Description
At present MetricsEndpointProvider adds juju_unit and juju_charm labels to alert rules. These to labels should not be added to the alert rule. However if they were already present in an alert rule they must not be removed.
To Reproduce

Follow the deployment steps shown in the README file for the cos-proxy-operator
Browse to the Prometheus dashboard and you should see alert rules with juju_unit and juju_charm labels.

Environment
As described in the README of cos-proxy-operator
Relevant log output
A sample flawed alert rule is shown below

name: CPU_Usage
expr: cpu_usage_idle{group="promoagents-juju",is_container!="True"} < 10
for: 5m
labels:
cloud: juju
juju_application: telegraf
juju_model: reactive
juju_model_uuid: 98b85b1
juju_unit: telegraf/1
override_group_by: host
severity: page
annotations:
description: Host {{ $labels.host }} has had <  10% idle cpu for the last 5m
summary: Host {{ $labels.host }} CPU free is less than 10%

### Additional context

_No response_

For the avoidance of doubt, we must:

We can (SHOULD?) add the juju_charm to the alert rule labels, as it is useful context in a notification (“oh cassandra is misbehaving”)
We MUST NOT add the juju_unit label to the alert rule
We MUST NOT add matchers to the alert rule’s expression via PromQL transformer for juju_charm

This is done. Closing.


UNIX Timestamp Conversion

I'm using the Date/Time Formatter to convert two differently formatted time stamps.

servertime: "2018-06-03T00:30:56.982+01:00" = serverunix: "1527985856982"
devicetime: "2018-06-03 00:30:56.678239" = deviceunix: "1529713856678"

The second conversion results in a unix time corresponding to the wrong date: Saturday, June 23, 2018 12:30:56.678 AM.
Could you please clarify if this is user error or an issue with the converter itself?

Hi, sorry about the delayed response.
This is a known issue. I tried to get MomentJS to fix it but they declined saying that you shouldn't use so many decimals on seconds - go figure. They are wrong of course, a utility should at least issue a warning if data is out of scope.
There is another closed issue on this #20 and I did think I'd put something into the docs. I thought that I'd tried to filter out errors like that as well but clearly I either dreamt that or couldn't make it work reliably.
I'm afraid that the only thing you can do right now is to trim the seconds values to 3dp or less.

Thanks for the confirmation and apologies for missing the prior issue.

No problem.


Create output file

Makes output_dir flag optional
Removes overwrite flag
Creates a new directory at the supplied output_dir named Redacted_[time_stamp] and places redacted images inside.
Defaults to current directory if no output_dir is given.

Closes #48 Closes #72

Opened as a draft for implementation discussion. Will need to adjust tests if this is the agreed implementation.
I believe this eliminates the need of a new template for the gui.
@manthey @naglepuff @brianhelba


MESSAGE_PARSE_ERROR crashes the server

After having broken the client to send random data to the server in the following manner:
in Connection class in the client, in sendMsg method, wrap the sending in a for loop looping over the available actions:
for(let key in C.ACTIONS) {
  this.send(messageBuilder.getMsg(topic, C.ACTIONS[key], data));
}

using the script at:https://github.com/deepstreamIO/test-scripts/blob/master/records/broken-client-record.js
The server crashed with the following message:
MESSAGE_PARSE_ERROR | [object Object]
deepstream.io/protocol/text/src/message-builder.ts:201
  const builder = BUILDERS[message.topic][errorAction]
                                          ^
TypeError: Cannot read property '67' of undefined

what topic did it break on?

It was records R

This issue is fixed in v4 since v4 uses the binary protocol


fix corners of shadow on iOS

Hello,
i found an issue with iOS, which looks like this:

This pull request will fix that by changing focal point of gradient.

thanks for help ~


Adds assistant argument to RemoteScheduler.get_work

Workers can't use the remote scheduler at all with the bug this fixes.

Thanks!

No problem. Luigi works with this change. I'm working on making it possible to actually run an assistant now.

Wait so Luigi was broken until this fix? That's not good.

Yeah, there aren't any tests to verify the RemoteScheduler interface. So the tests passed even though get_work was giving an invalid named argument.

Ok – we should add some tests for that. I think the tests might have been deactivated because of some issues with Tornado – remember seeing a comment about that. Might be worth turning them back on

@erikbern If you are talking with the issue with Travis, we didn't deactivated the test, they just run in a subprocess now. However, coverage don't capture them. There is way around it thou: http://nedbatchelder.com/code/coverage/subprocess.html http://blog.fizyk.net.pl/blog/gathering-tests-coverage-for-subprocesses-in-python.html
For the RemoteScheduler, there is some tests but is pretty limited https://github.com/spotify/luigi/blob/master/test/rpc_test.py. The best will probably to subclass https://github.com/spotify/luigi/blob/6c342f3b7c380d63cbdb53578a8ebff8da0adf32/test/central_planner_test.py#L28

Great thanks. I realized I think we test running a server but we don't ever try to query it for work


updating usage of ServicePrincipalName

fixed usage of Set-AzureRmKeyVaultAccessPolicy

@PiDiBi,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@PiDiBi : Thanks for your contribution to the Azure documentation! The author, @adhurwit, has been notified to review your proposed change.

@adhurwit - Hi Adam, would you please validate this change. I'm not familiar enough with the topic to validate. Thanks,
Bruce

@adhurwit - Hi Adam, would you please validate this change. I'm not familiar enough with the topic to validate. Thanks,
Bruce

OK @sign-off

OK @sign-off


Revert Zug-compatible rewards for now

This reverts commit 0a875b88d683477220842ff588f27d22019101f8, reversing changes made to e091dbfd1b0cce7d40e7e0b92935bdb0746acc79.
Changes to be committed:
modified:   execution_engine/src/core/engine_state/mod.rs
modified:   execution_engine/src/core/engine_state/step.rs
modified:   execution_engine/src/core/runtime/mod.rs
modified:   execution_engine/src/system/auction.rs
modified:   execution_engine_testing/test_support/src/auction.rs
modified:   execution_engine_testing/test_support/src/step_request_builder.rs
modified:   execution_engine_testing/test_support/src/wasm_test_builder.rs
modified:   execution_engine_testing/tests/benches/auction_bench.rs
modified:   execution_engine_testing/tests/src/test/regression/ee_1152.rs
modified:   execution_engine_testing/tests/src/test/regression/gov_89_regression.rs
modified:   execution_engine_testing/tests/src/test/regression/regression_20220221.rs
modified:   execution_engine_testing/tests/src/test/step.rs
modified:   execution_engine_testing/tests/src/test/system_contracts/auction/bids.rs
modified:   execution_engine_testing/tests/src/test/system_contracts/auction/distribute.rs
modified:   node/src/components/consensus/consensus_protocol.rs
modified:   node/src/components/consensus/era_supervisor.rs
modified:   node/src/components/consensus/highway_core/finality_detector.rs
modified:   node/src/components/consensus/highway_core/finality_detector/horizon.rs
new file:   node/src/components/consensus/highway_core/finality_detector/rewards.rs
modified:   node/src/components/consensus/highway_core/highway_testing.rs
modified:   node/src/components/consensus/highway_core/state/params.rs
modified:   node/src/components/consensus/highway_core/state/tests.rs
modified:   node/src/components/consensus/protocols/highway.rs
modified:   node/src/components/consensus/protocols/highway/tests.rs
modified:   node/src/components/consensus/protocols/zug.rs
modified:   node/src/components/consensus/utils/weight.rs
modified:   node/src/components/contract_runtime/operations.rs
modified:   node/src/types/block.rs
modified:   resources/test/rpc_schema_hashing.json
modified:   smart_contracts/contracts/test/auction-bids/src/main.rs
modified:   types/src/system/auction/constants.rs
modified:   types/src/system/auction/entry_points.rs

bors merge


Changed token creation to URL - Encoded

For some reason, when trying to create a new token it resulted in an error:
goroutine 1 [running]:
log.Panic({0x1400014fcf0?, 0x0?, 0x0?})
/home/migue/.asdf/installs/golang/1.20.5/go/src/log/log.go:384 +0x64
github.com/Madh93/toffu/cmd.glob..func5(0x1013e7c80?, {0x10100d264?, 0x0?, 0x0?})
/home/migue/Workspace/repos/toffu/cmd/token.go:17 +0x5c
github.com/spf13/cobra.(*Command).execute(0x1013e7c80, {0x1014257e8, 0x0, 0x0})
/home/migue/.go/pkg/mod/github.com/spf13/cobra@v1.7.0/command.go:944 +0x5b0
github.com/spf13/cobra.(*Command).ExecuteC(0x1013e76c0)
/home/migue/.go/pkg/mod/github.com/spf13/cobra@v1.7.0/command.go:1068 +0x35c
github.com/spf13/cobra.(*Command).Execute(...)
/home/migue/.go/pkg/mod/github.com/spf13/cobra@v1.7.0/command.go:992
github.com/Madh93/toffu/cmd.Execute(...)
/home/migue/Workspace/repos/toffu/cmd/root.go:31
main.main()
/home/migue/Workspace/repos/toffu/main.go:11 +0x40
And when digging into it, it was a result of the petition always getting status code 403: Forbidden.
For some reason, simply changing content type from application/json to url-encoded fixed the problem.

Thank you for identifying this issue :smiley:


old peer dependencies still on npm

I've freshly installed react-file-download and it says it has the wrong peer dependencies:
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.15.0".
Since the source code no longer has these dependencies, i can only imagine that the changes have not been published properly.

My apology for the sloppiness.
Just published 0.3.4.

Thanks for the quick response!


💵 Explore fiat-denominated accounts

Feature description
More and more services are offering fiat denominated accounts via synthetic assets:

kollider
galoy

Those services often offer multiple balances to their users. In Kollider's case it's:

Bitcoin
synthetic USD
synthetic EUR

We want to explore how this can be integrated into Alby by creating a connector for Kollider. (see WIP branch linked to this issue)
Context
When connecting a Kollider account () a user would need to choose which balance should be used within Alby, it's currently out of scope to support multiple balances.
A connector would need to signal the current currency to the extension.
Questions

What changes are needed in order for Alby to work with fiat-denominated accounts?

Receive & send screens
Balance in Account selector
Fiat currency conversion in transaction lists
Fiat inputs

Useful links

Kollider LNDHubx

Out of scope

Having multiple balances in one account

In the first step what we imo need to look at is how we can let the connector decide what currency the return amounts have.
E.g. when we show the account balance we have a hard coded "sats" there. this would need to be the currency of the connector.
Same in the incoming invoices.
I'd also say if the currency is not btc/sats then we do not show any other fiat amount (or we show the sats amount, whatever is easier)
in the outgoing payments list I'd still try to store sats amounts.

First Implementation

[ ] Create new connector "Kollider"
[ ] add new connector to Websites screen
[ ] when user creates Kollider => prompt user with "Which balance/account you want to add"
[ ] either store this base currency in Settings (TBD)
[ ] and/or add method to connector "getBaseCurrency" (TBD)
[ ] Decision: No convertion will happen at any place, just do not show fiat at all

just for completeness:
Here is the code where I explored Kollider: https://github.com/getAlby/lightning-browser-extension/pull/1770
there does not need to be a special prompt, just like other connectors need some information this needs a "currency":

I would also call it just getCurrency - because those accounts will only have one currency I guess.
and in the first step I'd only do all this in the account menu thing.
The outgoing payments are stored locally and are not per connector, there we only have the sats amounts (we don't even know the actual fiat amount that was paid from that account then)
And then we also can show the sats amount in the incoming invoices I guess.
All inputs an webln calls stay in sats.


Difference in the KL loss terms in the paper and the code

The algorithm for the KL balancing in the paper has the posterior and prior terms given as kl_loss = compute_kl(stop_grad(posterior), prior).  So I had assumed that the code would have computed the loss as value = kld(dist(sg(post)), dist(prior)).
But instead the code has the terms reversed, with the KL loss formulated as (in networks.py, line 168) value = kld(dist(prior), dist(sg(post))).
Does that have something to do with the implementation of the kl divergence function in tensorflow_probability?

KL balancing is implemented as weighted average of two terms, the KL with stop-grad prior and the KL with stop-grad posterior.
The value you found in the code is only used for logging. It is not what the gradient is computed of.


Unable to connect with Fabric SQL endpoint using az-cli credentials with version 5.2.0

Describe the bug
Using Microsoft.Data.SqlClient version 5.2.0 I'm no longer able to auth with Fabric using AAD credentials. The same test-program works using version 5.1.5.
Exception message:
Stack trace:
Unhandled exception. Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 26 - Error Locating Server/Instance Specified)
 ---> System.Net.Sockets.SocketException (0x80004005): Undefined error: 0
   at Microsoft.Data.SqlClient.SNI.SSRP.GetPortByInstanceName(String browserHostName, String instanceName, TimeoutTimer timeout, Boolean allIPsInParallel, SqlConnectionIPAddressPreference ipPreference)
   at Microsoft.Data.SqlClient.SNI.SNIProxy.CreateTcpHandle(DataSource details, TimeoutTimer timeout, Boolean parallel, SqlConnectionIPAddressPreference ipPreference, String cachedFQDN, SQLDNSInfo& pendingDNSInfo, Boolean tlsFirst, String hostNameInCertificate, String serverCertificateFilename)
   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, TimeoutTimer timeout, SqlConnectionString connectionOptions, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool, Func`3 accessTokenCallback)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open()
   at Program.<Main>$(String[] args) in /Users/alatter/projects/demos/csharp-sql-cli/Program.cs:line 10

To reproduce
Include a complete code listing (or project/solution) that we can run to reproduce the issue.
Partial code listings, or multiple fragments of code, will slow down our response or cause us to push the issue back to you to provide code to reproduce the issue.

using Dapper;
using Microsoft.Data.SqlClient;

var server = Environment.GetEnvironmentVariable("SQL_ENDPOINT");
var connString = $"Server={server};Authentication=Active Directory Default; Encrypt=True;";

using var sqlConnection = new SqlConnection(connString);

sqlConnection.Open();
Console.WriteLine("Connected successfully!");

foreach (var o in sqlConnection.Query("SELECT 1;"))
{
    Console.WriteLine(o);
}

Working csproj file:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
    <RootNamespace>csharp_sql_cli</RootNamespace>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Dapper" Version="2.1.35" />
    <PackageReference Include="Microsoft.Data.SqlClient" Version="5.1.5" />
  </ItemGroup>

</Project>

Broken csproj file:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
    <RootNamespace>csharp_sql_cli</RootNamespace>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Dapper" Version="2.1.35" />
    <PackageReference Include="Microsoft.Data.SqlClient" Version="5.2.0" />
  </ItemGroup>

</Project>

Expected behavior
A clear and concise description of what you expected to happen.

Run az login -t <tenant id>
Create a Fabric Warehouse or Lakehouse, note the SQL endpoint for your Fabric Workspace
In your shell:SQL_ENDPOINT=<something>.datawarehouse.fabric.microsoft.com dotnet run

When this works it should print something like:
Connected successfully!
{DapperRow,  = '1'}

Further technical details
Microsoft.Data.SqlClient version: 5.2.0
.NET target: net8.0
SQL Server version: N/A
Operating system: MacOS 14.5 (23F79) (Sonoma)
Additional context
Add any other context about the problem here.

Now that I look at the error-message, I'm not sure my auth-method makes a difference, but I'm including that detail here just in case.

Please try again after the 5.2.1 Hotfix is published and please let us know if you are still having an issue.

5.2.1 seems better. Closing.


free does not compile on void pointers

wlp::is_fundamental<Type>::value is false for void

Did you fix this?

I'll deal with it later when I redo memory


Check to see if the default clusternetwork is not found: MAISTRA-700

There was a second part to this, when reconciling the namespaces through member roll.  I'm going to update the PR and request reviews again.


Reduce number of generated Patterns for atomic components

Def. 'Atomic Type'
An atomic type is a type that can't be further deconstructed. If a (Tuple) component of a deconstructed object is of one of these types, we should not generated Matchers that have an arity > 1 for these components.
Example:
class Person {
    String name;
    int age;
}

Because name and age are atomic, the only matchers can be $_, $(), $(value), plus matchers of arity 0 or 1 (, e.g. Pattern0 and Pattern1).
These types should be atomic:

Boolean
Byte
Character
Double
Float
Integer
Long
Short
String

This list may not be exhaustive, yet.
Additionally the use of generic type parameters T has to be checked in this context.

Optimizations must take place with the type tree in mind. E.g. if Integer is atomic, so is Number. In order to keep the 'lookup-table' of atomic type small, we need to check inheritance relation during optimization.
Also we must create a directed dependency graph before optimization. We can calculate the maximum Pattern arity, when we know the maximum arity of the components.
Example:
Address(String, Integer)
// String is atomic => max arity 1
// Integer is atomic => max arity 1
// => overall max arity = 2

Person(String, Address)
// String is atomic => max arity 1
// depends on Address, which has max arity 2
// => overall max arity = 3

Another optimization idea: compare bytecode size different types of generated files

interface
abstract class
final class

the contained methods should be all static

Further optimization:

omit type hint for Pattern0.<...> create(...), if type hint has no generics
use primitive values in method signatures, if applicable
the generator will use an ImportManager. Do imports really reduce bytecode size? However, it will reduce java file size.
Move method bodies into static methods of Pattern0..8

Example
public final class MyPatterns {
    public static <__ extends java.time.LocalDate> Pattern0 LocalDate(java.lang.Integer p1, java.lang.Integer p2, java.lang.Integer p3) {
        return Pattern0.<java.time.LocalDate>create(java.time.LocalDate.class, t -> Xxx.LocalDate(t).transform((t1, t2, t3) -> Pattern0.equals(t1, p1).flatMap(_1 -> Pattern0.equals(t2, p2).flatMap(_2 -> Pattern0.equals(t3, p3)))));
    }
}

will be
public interface MyPatterns {
    static <__ extends LocalDate> P0 LocalDate(int p1, int p2, int p3) {
        return P0.create(LocalDate.class, t -> Xxx.LocalDate(t).transform((t1, t2, t3) -> equals(t1, p1).flatMap(_1 -> equals(t2, p2).flatMap(_2 -> equals(t3, p3)))));
    }
}

This is obsolete now. The current version of Match does have 1 method per pattern.
We will therefore not apply any (so called) optimizations, e.g. defining atomic types. Without atomic types we have more flexibility to define match patterns for arbitrary objects.


jsonschema2pojo:generate nothing generated

Hi I'm trying to generate sources
I've copied the project: https://github.com/joelittlejohn/jsonschema2pojo/tree/master/jsonschema2pojo-maven-plugin/src/test/resources/example
I've deleted the json files
and I've placed in same directory the files: https://www.hl7.org/fhir/fhir.schema.json.zip
these are the schemas of the FHIR norm
I've compiled but no files are generated
I've tried to add includes, sourcespaths etc.
But nothing is generated.
No errors but nothing is generated.
Thank.
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">   <modelVersion>4.0.0</modelVersion>   <groupId>fr.aphp.fhir</groupId>   <artifactId>json-fhir</artifactId>   <packaging>jar</packaging>   <version>1.0-SNAPSHOT</version>   <name>json-fhir</name>   <url>http://maven.apache.org</url>   <dependencies>     <dependency>       <groupId>junit</groupId>       <artifactId>junit</artifactId>       <version>3.8.1</version>       <scope>test</scope>     </dependency>         <dependency>             <groupId>commons-lang</groupId>             <artifactId>commons-lang</artifactId>             <version>2.4</version>         </dependency>         <dependency>             <groupId>com.fasterxml.jackson.core</groupId>             <artifactId>jackson-databind</artifactId>             <version>2.0.0</version>         </dependency>     </dependencies>  <build>   	<plugins> 	  <plugin>         <groupId>org.jsonschema2pojo</groupId>         <artifactId>jsonschema2pojo-maven-plugin</artifactId>         <version>0.5.1</version>          <configuration>             <sourceDirectory>${basedir}/schema</sourceDirectory>             <targetPackage>com.example.types</targetPackage>             <includes>               <include>**/*.json</include>             </includes>             <includeHashcodeAndEquals>false</includeHashcodeAndEquals>             <includeToString>false</includeToString>         </configuration>         <executions>           <execution>             <goals>               <goal>generate</goal>             </goals>           </execution>         </executions>       </plugin>   	</plugins>   </build> </project>

Hi. I see a lot of these schemas use allOf. From a quick browse, it looks like every schema is defined using allOf. This library does not support allOf.

Thank.
Do you know a way to explore to get to the result, another lib?
Making a Maven plugin is not a problem for me.


Spell Timers with same name(s)/Regex Issue

Attempting to configure a Spell Timer for Thunder(I/II/III) on Black Mage, as each level of Thunder has a different duration.
Created 3 individual Spell Timers, each using "Spell Name" Thunder, and matching text as:

You cast Thunder
You cast Thunder II
You cast Thunder III

When casting Thunder, timer shows as expected.
When casting Thunder II, timer for both Thunder (1) and (2) appear.
When casting Thunder III, timer for all 3 versions appears.
===
Changed "priority" of timers, since all 3 timers have the same name, highest priority (smaller as per options) should only ever be visible in case of duplicate.
No effect, all 3 timers continue to appear when casting Thunder III.
===
Attempted to define exact string matches.

^You cast Thunder$
^You cast Thunder II$
^You cast Thunder III$

No spell timers appear when using standard regex formatting (above).

You cast Thunder II.$ ?
Theres other stuff befroe it in the act log. And there's a period at the end.

Yes, this is normal of Regex.
^ Indicates the beginning of what should be matched
$ Indicates the end.
Essentially, I am asking it to match the string exactly, preventing "Thunder" from matching when it sees "Thunder III"

Issue is also occurring with Bio/Bio II on SMN/SCH
(See Below)

No Timers Active/No Spells Cast

Bio Cast - Timer for Bio Active

Bio Wears Off - Timer for Bio Ends

Bio II Cast - Timer for Bio AND Bio II Active

My spell timers are configured as follows:

Thunder Timer Issue

Thunder Cast - Timer for Thunder Active

Thunder Wears Off - Timer for Thunder ends

Thunder II Cast - Timers for Thunder AND Thunder II active (even though same name)

Thunder Wears Off - Timer(s) for Thunder end

Thunder III Cast - Timers for Thunder, Thunder II AND Thunder III active (even though same name)

===
Additionally, here are my spell timer settings for Thunder / Thunder II / Thunder III

Also affected by this:
Aero / Aero II
Miasma / Miasma II

Please try these.


Prometheus annotation serializing incorrectly

The YAML serialization of the prometheus port annotation is generating a bad UTF-8 escape:
# From the pachd Service.
metadata:
  annotations:
    prometheus.io/port: "\u9:?:"

It's odd that this is using a single unicode character, instead of an integer, but the JSON has:
"prometheus.io/port": "⎃"

(a single unicode character).
This incorrect serialization results in a parse error from kubectl.

I think this one is addressed via this https://github.com/pachyderm/pachyderm/issues/3073

Agreed this is a duplicate of #3073.


Revert "RHBPMS-4249, JBPM-5319 - Transaction exception for Per Proces…

…s Instance deployment in WebLogic"

PLEASE DON'T MERGE THIS PR.
@mariofusco and @mswiderski do a reseacrh and maybe we don't have to revert the commit
https://github.com/droolsjbpm/jbpm/commit/9ab7eb72c96f1e6ffb6692266cddfdc01c43898e


feat(client): integrate Vercel Analytics for improved user insights

feat(client): integrate Vercel Analytics for improved user insights

Added @vercel/analytics package to the client dependencies in package.json.
Updated main.tsx to include the Analytics component, enabling tracking of user interactions.

This enhancement allows for better monitoring and analysis of user behavior within the application.

#39  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 29, 7:54 AM EST: A user started a stack merge that includes this pull request via Graphite.


Sanitizes Code Reviews README and adds information about metrics

Moves guidance solely focused on how to create PRs into its own file
Sanitizes and restructures README.md
Adds information on code reviews metrics
Adds useful resources

Addresses issues #168 and #120

Could you link the issues in the "Linked issues" section of the PR pls?

Could you link the issues in the "Linked issues" section of the PR pls?

Closing this PR as it has become convoluted, and starting fresh.


Problems with Notion the blog doesn't work

Mac book, OSX: 10.15.7
Notion 2.0.17
I state that I am not an expert. i managed to get online with vercel and with the localhost.
in the .env file I manually entered the token and the blog id.
I used the code:
export NOTION_TOKEN = '' and export BLOG_INDEX_ID = ''
but it's like it's not connected to Notion. It does not read the table I made following the instructions.
it's like it doesn't read the BLOG_INDEX_ID and the Notion_Token
I tried to insert it in many ways and nothing, it does not create any pages
Can you take a step by step video please?
quello che vedo #

Hi, are you seeing any errors in your logs? If it fails to fetch the data it should say so in your deployment's function logs.

Did you find any solution?

Hi, I have the same problem.
I saw function logs.
[GET] /_next/data/FSYgZnDdqX101WjvgFtWj/blog.json
02:18:07:92
info  - Loaded env from /var/task/.env
2022-02-27T17:18:09.170Z	d65a9e52-2e6d-4e1b-8cb6-dc5b17a95f08	WARN	Failed to load Notion posts, have you run the create-table script?

I ran the create-table.js scripts in local, but I got "failed to load Notion posts".
Logs
$ docker compose up
[+] Running 1/1
 ⠿ Container notion-blog-node-1  Recreated                                                                                10.5s
Attaching to notion-blog-node-1
notion-blog-node-1  | yarn run v1.22.5
notion-blog-node-1  | $ next dev
notion-blog-node-1  | ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
notion-blog-node-1  | info  - Loaded env from /usr/src/app/.env
notion-blog-node-1  | info  - Using webpack 5. Reason: future.webpack5 option enabled https://nextjs.org/docs/messages/webpack5
notion-blog-node-1  | Browserslist: caniuse-lite is outdated. Please run:
notion-blog-node-1  | npx browserslist@latest --update-db
notion-blog-node-1  |
notion-blog-node-1  | Why you should do it regularly:
notion-blog-node-1  | https://github.com/browserslist/browserslist#browsers-data-updating
notion-blog-node-1  | event - compiled successfully
notion-blog-node-1  | event - build page: /
notion-blog-node-1  | wait  - compiling...
notion-blog-node-1  | event - build page: /next/dist/pages/_error
notion-blog-node-1  | event - compiled successfully
notion-blog-node-1  | event - build page: /blog
notion-blog-node-1  | wait  - compiling...
notion-blog-node-1  | event - compiled successfully
notion-blog-node-1  | Failed to load Notion posts, have you run the create-table script?
notion-blog-node-1  | wait  - compiling...
notion-blog-node-1  | event - compiled successfully

Dockerfile , Compose file
FROM node:14.15.3
WORKDIR /usr/src/app

RUN curl https://deb.nodesource.com/setup_12.x | bash
RUN curl https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list

RUN apt-get update && apt-get install -y yarn
RUN apt install direnv

RUN yarn install

version: '3'
services:
  node:
    build:
      context: .
      dockerfile: ./docker/Dockerfile
    env_file:
      - .env
    volumes:
      - .:/usr/src/app
    command: sh -c "yarn dev"
    ports:
      - "3000:3000"

Hi guys !
This problem is resolved by upgrading to latest revision.
Maybe, this problem caused by notion api spec upgrade about src/lib/notion/queryCollection.ts
src is here


Request form: Improve wording of Submission Deadline Author Reorder

PCs are still getting confused about how to interpret this field. One way to make it more clear is if we change the options to be something like: "Allow author reorder only", "Allow add/remove authors", and "Don't allow changes".

The current options are as follows, I am not sure your suggestion makes them any more clear?

'Allow addition and removal of authors',
'Allow reorder of existing authors only',
'Do not allow any changes to author lists'

I am hesitant to make this change and changing the values since some venues will already have these values. What if we change the description:
'description': 'Choose how authors may edit the author list. You can allow authors to 1)add/remove authors, 2)reorder existing authors only or 3)make no changes to the author list.'
What do you think? @melisabok @enrubio

ok, let's change the description.

Ooh I see. I made this issue after changing author reorder for Neurips and their request form still has the old options: Yes / No / No changes
I forgot we already changed this. I think the description & options we have now are self-explanatory and straightforward. I'm ok with closing the issue.


Exclude self from offline TMPE mod check

Thanks to @kvakvs for spotting the issue
Thanks to @dymanoid for idea to use ManifestModule.ModuleVersionId

Mod performing the check gets its own Guid from:
 Assembly.GetExecutingAssembly().ManifestModule.ModuleVersionId

When checking local mods (which only happens when a build is using RELEASE or RELEASE LABS), the Guid of the mod being inspected is determined by:
        public Guid GetModVerId(PluginInfo plugin)
        {
            return plugin.userModInstance.GetType().Assembly.ManifestModule.ModuleVersionId;
        }

If the two Guid values match, the local (offline) build is skipped by the compatibility checker, this preventing local RELEASE or RELEASE LABS from flagging themselves as duplicate.
Not currently working.
Idea is to have some unique value on the TrafficManagerMod : IUserMod (currently a static int Build, but could be on the instance instead) and pass that in to the mod checker so it can filter out "self" when scanning for offline mods.

Example content of TMPE.log:
[Info] @ 185124035 incompatible_mods.txt contains 46 entries
[Info] @ 185181493 Scanning for incompatible mods; Self GUID = ebe5de81-6b78-482b-859b-8e2a0181ba90
[Info] @ 185204304 Skipping local TM:PE with GUID 'ebe5de81-6b78-482b-859b-8e2a0181ba90' in 'C:\Users\aubergine\AppData\Local\Colossal Order\Cities_Skylines\Addons\Mods\TrafficManager'
[Info] @ 185219441 Local TM:PE detected: 'TM:PE 10.20 LABS' in 'C:\Users\aubergine\AppData\Local\Colossal Order\Cities_Skylines\Addons\Mods\TrafficManagerOld'
[Info] @ 185249570 Scan complete: 1 incompatible mod(s) found

I might make a couple more tweaks to the logging, don't merge yet

It can now detect any other version of TM:PE, whether online or offline, even versions it's never seen before (like my test build for PR #333).

Log file looks like:
[Info] @ 192217044 TrafficManager.Resources.incompatible_mods.txt contains 46 entries
[Info] @ 192249006 Scanning for incompatible mods; My GUID = 5d6986e0-0c74-4629-b602-ad9e5ffbb3da
[Info] @ 192272061 Found myself: 'TM:PE 10.20 LABS' (Workshop ID: LOCAL, GUID: 5d6986e0-0c74-4629-b602-ad9e5ffbb3da) in 'C:\Users\aubergine\AppData\Local\Colossal Order\Cities_Skylines\Addons\Mods\TrafficManager'
[Info] @ 192304510 Detected conflicting 'TM:PE 10.20 LABS' (Workshop ID: LOCAL, GUID: 45bba401-0fd5-4b66-9548-c720294182bc) in 'C:\Users\aubergine\AppData\Local\Colossal Order\Cities_Skylines\Addons\Mods\TrafficManagerOld'
[Info] @ 192321845 Detected conflicting 'TM:PE 10.20 LABS' (Workshop ID:<PHONE_NUMBER>, GUID: 61cf1dac-7965-4ec2-b2e2-28f093ab742c) in 'C:\Program Files (x86)\Steam\steamapps\workshop\content\255710\1781170897'
[Info] @ 192335649 Detected conflicting 'TM:PE 10.20' (Workshop ID: 583429740, GUID: 2a3f5abb-c4b4-499a-bcf3-0c9b056df384) in 'C:\Program Files (x86)\Steam\steamapps\workshop\content\255710\583429740'
[Info] @ 192350925 Scan complete: 3 incompatible mod(s) found

This approach should also be far more robust for users running the mod in offline mode (eg. via EA's Origin service) as it will now check for other offline TM:PE installs.


[#170442909] upgrade react hook form

Warnings

:warning:
Please include a description in the Pull Request.

Affected stories

⚙ #170442909: Aggiornare reat-hook-form alla versione 4.x

  Generated by :no_entry_sign: dangerJS against 7a8e9ca303e2f56d4ea8d25cf4add72efc930a1e


Data quality flags - planning

We want a flag database
General

L1 -> Flags applied to data -> Filtering -> Computation -> L2
L2 filters out data and assigns a quality column

Add a flag API is something like:

Timestamp?		Not necessary given ID but useful for quick separation by e.g. year/month
Observation ID	Necessary
Severity		Drop/Warning/Note
Flag type		Out_of_bounds/Timestep_outlier/Expert_opinion/...
Author			Author (human or algorithmic)
Remark			Remark

Other things we will want

Get flags for a year/month
Get flags for a timestamp/ID
Get flags for an ID
Clear flag(s)

Implementation

~Data frames saved to disk (RData? something quick), probably in year/month folders for efficiency~
Genuine database: less code, higher performance! https://cran.r-project.org/web/packages/RSQLite/vignettes/RSQLite.html

Flags come from

OOB column -> converted
Outlier or other statistical analysis
Relationship or other analysis
Human QAQC (e.g., Shiny app)

Flags get written out as CSVs with

L1_flag intermediate data product?
L2 data?

What about "hierarchical flags"? Discuss this with @roylrich @selinalcheng @stephpenn1

I have played with RSQLite and it's dead simple. Much better than writing our own code!

How do flags get removed from the database? Does L2 remove them?

Basically: is the flags database persistent between driver() invocations?

If not, everything is simplified: we expect that L1.qmd will create/overwrite the database (using the OOB column); L2_algorithmic.qmd and Shiny app Human_QAQC (neither of which exists yet) will add to it; and L2 will read it.
If yes, ...

NCAS data https://sites.google.com/ncas.ac.uk/ncasobservations/home/data-project/ncas-data-standards/ncas-amof/data-quality-flags
As the name suggests, data quality flags are used to let the user know the quality of a particular data variable or factors that impact on the quality of a variable. In this standard we use an integer value in the range 0 to n:
0 is reserved for future use and is not used
1 is always good data.
The values of n, what they represent and how data with that flag value should be interpreted is incorporated into files by means of the a variable that is structured as follows.
A file containing just one data quality flag will contain the variable qc_flag
Where a  file contains more that on data quality flag variable the data quality flag named is structured as:  qc_flag_<name>

Ameriflux https://ameriflux.lbl.gov/data/flux-data-products/data-qaqc/physical-range-module/
Pastorello, G., et al. (2020), The FLUXNET2015 dataset and the ONEFlux processing pipeline for eddy covariance data, Scientific Data, 7(1), 225, DOI:10.1038/s41597-020-0534-3
Chu, H., Christianson, D. S., Cheah, Y.-W., Pastorello, G., O’Brien, F., Geden, J., Ngo, S.-T., Hollowgrass, R., Leibowitz, K., Beekwilder, N. F., Sandesh, M., Dengel, S., Chan, S. W., Santos, A., Delwiche, K., Yi, K., Buechner, C., Baldocchi, D., Papale, D., Keenan, T. F., Biraud, S. C., Agarwal, D. A., and Torn, M. S.: AmeriFlux BASE data pipeline to support network growth and data sharing, Sci Data, 10, 614, 2023.

UGA LTER https://gce-lter.marsci.uga.edu/gce_toolbox/wiki/QAQC.htm
QA/QC flag codes should be documented in the metadata (i.e. 'Data' category, 'Codes' field) using the following format: "Q = questionable value, I = invalid value, M = missing", etc. This ensures that the flag codes are properly displayed in standard and XML metadata, and also allows column values codes to be automatically generated when flags are optionally converted to encoded integer columns during ASCII or MATLAB export operations or manually in the structure editor. A GUI flag definition editor is provided with the GCE Data Toolbox, which can be opened using the 'View/Edit Q/C Flag Definitions' option on the 'Edit > Q/C Flag Functions' menu.

Suggested flag codes are listed below:

   I = invalid value (out of range) -- use for out-of-range/impossible values (e.g. negative mass)
   Q = questionable value -- use for values outside of expected range (e.g. below detection limit,
       well outside of historical value range, pattern indicating data contamination)
   E = estimated value -- use for values that were estimated by interpolation or other means
   S = spike/noise -- use for sharp discontinuities/spikes indicating data contamination


Total number of tests all over india not shown

Is your feature request related to a problem? Please describe.
The default page shows the total number of test of Maharashtra and then you can only the the total number of tests state wise
Describe the solution you'd like
You can show total number of tests for default and then statewise after selecting different states.

Duplicate of #937


Add post about FAF in OpenShift

I've updated it according to your comments, except the persistent volume.

I would wait with merging this a few days. There are changes in upstream FAF which make this possible. It is not released yet - I am waiting for 'unpackaged problems' and then I will release new FAF and faf-image as well. Then it would be more suitable to post this article - since it would work as described.


Build Vue.js Application with Django REST API and Axios

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #5401

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Ook

@mercymeave done with the changes

Most of your code including comments, variables names, comments, and functions appear to have been taken from other articles such as https://codewithstein.com/combining-django-and-vuejs-everything-you-need-to-know/ We focus more on unique content. Thanks
New Scan 10_30 AM Copyleaks Report.pdf


How to tell if check_callback returns false on dnd_stop

Link to SO issue:
https://stackoverflow.com/questions/62842037/jstree-tell-if-check-callback-is-true-during-dnd-stop-event
I am dragging from one tree to another and only allowing items from tree 1 to be dropped on certain items on tree2.  How can i tell on dnd_stop if the drag was succesful or was not allowed byt the check_callback function:
check callback
"check_callback": function(operation, node, node_parent, node_position, more) {
                if (!more || !more.dnd) return true;
                var allow;
                switch (node_parent.text) {
                    case "programs":
                        allow = ['exe'].indexOf(node.id.split('.').pop())
                        break;
                    default:
                        allow = -1;
                }
                return allow > -1;
}
        }

dnd_stop:
$(document).on('dnd_stop.vakata', function(e, data) {
        console.log(e, data);
        // was this an dropped event or prevented by check_callback?????
       //find drop target
       ref = $j('#tree2').jstree(true);
       parent = ref.get_node(data.event.target);
 });

Thanks

You can not - dnd_stop happens BEFORE the final check_callback. When dealing with tree-to-tree moves - do NOT use the low-level dnd* events - all you need are the jstree events.

Which street event should I look at?  Create_node doesnt seem to be fired.
On July 15, 2020 5:49:54 PM Ivan Bozhanov<EMAIL_ADDRESS>wrote:

You can not - dnd_stop happens BEFORE the final check_callback. When
dealing with tree-to-tree moves - do NOT use the low-level dnd* events -
all you need are the jstree events.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@vakata I went through every event in jstree events and couldnt find any that triggers on drag stop.  I figured i had two options:

rerun the call back manually and see if i am in true/false state
check the icon.

I went with option 2:
$j(document).on('dnd_stop.vakata', function(e, data) {
           if ($j('.jstree-icon.jstree-ok').length > 0) {
               console.log(e, data);
               ref = $j('#project_list_container').jstree(true);
               parent = ref.get_node(data.event.target);
           } else
               console.log('canceled')
       });


General: Disable loading buttons

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines and ensured that the layout is responsive.

Motivation and Context

In some edge cases a button could be pressed multiple times which lead to some bugs in Artemis. E.g. pressing "Start exercise" for a programming exercise could lead to multiple submissions.
Description

A button with a loading animation is now also automatically disabled.
Steps for Testing

Prerequisites:

1 Instructor
1 Student
1 Programming Exercise

Log in to Artemis
Try to start the exercise multiple times by spamming "Start exercise" (an auto clicker might help here)
Check if the submissions are only registered once. This can be done in two ways:

Go to the repository and check the settings on the left side. The "Weebhooks" tab should only contain one web hook
Submit something as a student and check the amount of submissions in the participation overview of the exercise

Review Progress

Code Review

[x] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Change looks good to me 👍


PublicGatewayIP not created on the target cluster

Hello
Following the documentation available here: https://marketplace.upbound.io/providers/scaleway/provider-scaleway/v0.3.0/resources/vpc.scaleway.upbound.io/PublicGatewayIP/v1alpha1
we have been unable to create a PublicGatewayIP.
Below is the manifest used:
apiVersion: vpc.scaleway.upbound.io/v1alpha1
kind: PublicGatewayIP
metadata:
  name: vpc-public-gateway-ip
spec:
  forProvider: {}
  providerConfigRef:
    name: crossplane-project

The object status is
➜  ~ kubectl get publicgatewayip
NAME                   SYNCED   READY   EXTERNAL-NAME   AGE
vpc-public-gateway-ip   False    False                   10m

After 10 minutes, the object has not been created, performing a 'describe object' we can observe an error regarding insufficient permissions
Status:
  At Provider:
  Conditions:
    Last Transition Time:  2024-08-02T09:20:39Z
    Reason:                Creating
    Status:                False
    Type:                  Ready
    Last Transition Time:  2024-08-02T09:23:29Z
    Message:               create failed: apply failed: scaleway-sdk-go: insufficient permissions: write vpc_gw_ip:
    Reason:                ReconcileError
    Status:                False
    Type:                  Synced
    Last Transition Time:  2024-08-02T09:23:29Z
    Reason:                Finished
    Status:                True
    Type:                  AsyncOperation
    Last Transition Time:  2024-08-02T09:20:40Z
    Message:               apply failed: scaleway-sdk-go: insufficient permissions: write vpc_gw_ip:
    Reason:                ApplyFailure
    Status:                False
    Type:                  LastAsyncOperation
Events:
  Type    Reason                   Age                   From                                                            Message
  ----    ------                   ----                  ----                                                            -------
  Normal  CreatedExternalResource  32s (x5 over 3m22s)   managed/vpc.scaleway.upbound.io/v1alpha1, kind=publicgatewayip  Successfully requested creation of external resource
  Normal  PendingExternalResource  22s (x20 over 3m20s)  managed/vpc.scaleway.upbound.io/v1alpha1, kind=publicgatewayip  Waiting for external resource existence to be confirmed

However, the 'scaleway-provider' has a cluster role that should allow the public gateway ip creation:
Resources
gatewaynetworks, gatewaynetworks/status, privatenetworks, privatenetworks/status, publicgatewaydhcps, publicgatewaydhcps/status, publicgatewayips, publicgatewayips/status, publicgatewaypatrules, publicgatewaypatrules/status, publicgateways, publicgateways/status, vpcs, vpcs/status
Verbs
get, list, watch, update, patch, create
Api Groups
vpc.scaleway.upbound.io

We need the PublicGatewayIp to create a PublicGateway.
Could you kindly check?
Thanks in advance.

Hello,
I'm currently evaluating the crossplane scaleway provider myself, and I was abble to create a publicGatewayIP.
Reading your trace, I think your permission problem is not on the k8s side ( as the PublicGatewayIP object is created in k8s) but on the permission associate to the scaleway credentials you give to configure the scaleway crossplane provider. In other word maybe the API key you use in your provider doesn't have the right to create a vpc_gw_ip in your targeted scaleway project.
Hope, it helps.


Re-enabling species selection for nukies, adding species blacklisting

Reverts space-wizards/space-station-14#29693
This change does not fit within the game pillars of SS14, specifically it needlessly limits player agency/choice with very dubious reasoning. "Species design is diverging a lot more" is not an excuse to ignore core pillars of what makes Spacestation unique, especially not when there are alternative solutions that do not involve removing existing player expression.
If "Species design is diverging" to the point where it is no longer compatible with the core pillars of the game then it needs to go back to the drawing board. Nukies are not the only antag or combat role, what next are we going to force security and command to be human for "balance"? A reasonable solution to the issue that this PR is trying to fix would be to either:
A) Whitelist species for nukies to not allow vox until they are properly supported
B) Just put in the extra work to support vox nukies.
It's absolutely unacceptable to completely remove a large player-facing feature like this just because you don't want to do more work.

It's been proposed before but having a magic mirror to alter species on the nukie outpost would also solve the issue.
Playing a vox/diona/moth/whaever character and rolled nukies? Don't want to handicap yourself by playing this species?

Holy based

jez sweep

Can we keep the speciesOverride code block for downstream?
I don't see a real need to remove the full code block if you just need to remove speciesOverride: Human on nukies yml.

Ideally, a nukie-specific section on the create-a-character screen would solve everyone's issues, no?
I know a common complaint right now is that people WANT to play diona and such, but decline too because of the chance of them rolling nukie.

Forcing species bans on certain stuff will definitely diminish the RP aspect of the game a lot more than it already is.

I have no idea why this was merged in the first place, seeing as how the github post had TONS of discussion and valid points as to why it shouldn't happen mechanically, on top of making cybersun seem specist. I don't understand why we are even allowed to discuss in github if it's going to be ignored and merged anyway.

I have no idea why this was merged in the first place, seeing as how the github post had TONS of discussion and valid points as to why it shouldn't happen mechanically, on top of making cybersun seem specist. I don't understand why we are even allowed to discuss in github if it's going to be ignored and merged anyway.

This does happen a lot from what I see, which sucks. Nothing we can do about it though 🤷

a magic mirror is easier said than done when you realize you're going to have to somehow transcode one species to another

We have polymorph, it wouldn't be that crazy.

This does happen a lot from what I see, which sucks. Nothing we can do about it though 🤷
We've been having internal discussions about both the handling of the situation and the way the PR was handled initially. I should have handled things more professionally and I regret being so emotional around the issue since that only served to inflame the situation.

We're aware of people's concerns around Github discussions being ignored and that has been part of the discussions around what we can do better in the future and changes that we can make to have better communication both within the maintainer team and with the community as a whole.
We hear you and you aren't being ignored. There will likely be some changes to how we handle PR reviews and maintainer-contributor communication in the future from the results our internal discussions. The specifics of that will be shared soon.

Isn't the actual issue here that there's no code or assets support for these species as Nuke Ops? As in, they can't wear the hardsuit and they don't have support for the alternative breathable gas tanks that they need? This shouldn't be reverted until that issue is resolved. Otherwise, there's no reason to keep the species blocked, although I could see a similar issue occurring if someone were to implement Plasmamen.

We hear you and you aren't being ignored. There will likely be some changes to how we handle PR reviews and maintainer-contributor communication in the future from the results our internal discussions. The specifics of that will be shared soon.

This is a public, open source codebase for an open source video game. Any and all discussions should be publicly visible with input from the people working on the project, same as at SS13. Anything else would be disrespectful to the decades of work I and every other other Space Station 13 developers have put in making the game you guys are re-creating using our spritework and game design piece by piece. We did not do all this work in the public and as an open source initiative

This shouldn't be reverted until that issue is resolved.

I would suggest an alternative (a much better one) simply make it so voxes cannot play nukies, as overall that leads to more species diversity then only humans without changing a significant amount of the game.

This is a public, open source code base for an open source video game. Any and all discussions should be publicly visible with input from the people working on the project, same as at SS13.

Design discussion around what the reversion PR is publicly visible in both the #character-species and #development channels, with the development channel open for anyone to comment in.

We did not do all this work in the public and as an open source initiative just for critical design decisions to be made in a smoky backroom the average line developer cannot access. Please rectify this.

The internal discussions I was referring to were around staff conduct, how the PR and discussion around it was handled and solutions for conflict mitigation, not the changes themselves. Discussions around those can be found in the channels I mentioned above. The vast majority of changes are discussed in the relevant work-group channel, #Maintainers, #Contributors, #Development, all of which are publicly visible (with development open for messages). Some changes however are contentious, can be abused (exploit fixes), or involve admin rule implications and for those reasons may initially be discussed in internal channels.
As a result of discussions around the handling of both the initial PR and revert PR we are implementing new maintainer/PR review policies effective immediately: https://docs.spacestation14.com/en/staff/maintainer-policy.html.
These policies are aimed at giving more time for all stakeholders (both maintainers and contributors) to express feedback/criticism/suggestions on the PR. The policy also addresses the issue of contributor/discussion comments appearing to be ignored by requiring all valid dissents/criticisms to be addressed by the PR author before a PR can be merged.
This doesn't really apply to contributors but, we also implemented a conflict resolution policy for handling inter-staff conflicts to help de-escalate heated discussions between staff members.

Disclaimer this is my personal opinion not one of the project as a whole:

This is a public, open source codebase for an open source video game. [...] Anything else would be disrespectful to the decades of work I and every other other Space Station 13 developer have put in [...]. We did not do all this work in the public and as an open source initiative just for critical design decisions to be made in a smoky backroom the average line developer cannot access. Please rectify this.

The spirit of Open Source is freedom, the freedom for you to view what makes up an application, the freedom to build off of that software to make new things, the freedom to develop off the software how you want, and the freedom to use the software how you want.

just for critical design decisions to be made in a smoky backroom the average line developer cannot access. Please rectify this.

I know what you are going for with this and I completely agree with your sentiment (siloing is bad), but I'd like to play devils advocate for a second because it's important. Open Source is freedom. It's the freedom to run your project the way you want, if someone wants to develop a SS14 fork with a siloed development model that is their right as it is their right to closed source the their fork if they so choose.
(This isn't a personal attack, I just disagree with this bit of what you are saying and how you are saying it)
Imposing ways of doing things onto people "because it's open source" and using your contributions as justification to impose your way of development onto someone else makes the open source community look bad. It comes across as gate-keeping and might push people away from adopting open source as a development model for fears of being forced into a development model they do not want.
There are many different ways to make open source software and as long as people are free to access, and build off of the code and ideas of the software, the ideals of open source software spread further and the world is better off from it.

 The whole problem with the original PR was that we "can't foresee what might break in the future".

 The whole problem with the original PR was that we "can't foresee what might break in the future".

We won't know if stuff breaks if it isn't allowed to break first.
If you are adding a new species you have hopefully tested it with Nukies (and thus added it to the blacklist if necessary).
If you've somehow forgotten Nukies exist or just didn't bother testing (bad dev!), having it be included in Nukies by default means at least players will be able to quickly find and point out the issues, at which point it can be killswitched.

If you are adding a new species you have hopefully tested it with Nukies (and thus added it to the blacklist if necessary).

Literally the whole reason there is even drama about this PR is because that didn't happen.

Players will be able to "quickly find and point out the issues" with a whitelist just the same, but the difference is that with a whitelist there will be a sanity check involved before they become playable. It may or may not catch the issue, but is clearly the better way to include a change that will potentially disrupt subsequent rounds
In the vox case, it was literally pointed out on their gear PR that they don't work with nukies yet, I assume this was forgotten when they were merged. Meaning they would likely also have been forgotten off the whitelist, but would have sailed past a blacklist.
Whitelist fails in a safer way

If you are adding a new species you have hopefully tested it with Nukies (and thus added it to the blacklist if necessary).

Literally the whole reason there is even drama about this PR is because that didn't happen.

If you've somehow forgotten Nukies exist or just didn't bother testing (bad dev!), having it be included in Nukies by default means at least players will be able to quickly find and point out the issues, at which point it can be killswitched.

The problem wasn't that we didn't have a whitelist at the time, it was that devs failed to properly test the species before adding it.  but someone who is gung-ho about flaunting testing can just as easily add the species to the whitelist and bulldoze on ahead.
Neither a whitelist nor a blacklist solves the issue of irresponsible devs. But it does solve cleaning up their mess, or letting a responsible dev safely release a partially finished species.

Players will be able to "quickly find and point out the issues" with a whitelist just the same, but the difference is that with a whitelist there will be a sanity check involved before they become playable. It may or may not catch the issue, but is clearly the better way to include a change that will potentially disrupt subsequent rounds In the vox case, it was literally pointed out on their gear PR that they don't work with nukies yet, I assume this was forgotten/missed when they were merged. Meaning they would likely also have been forgotten off the whitelist, but would have sailed past a blacklist.
Whitelist fails in a safer way

I can buy that - I think our development cycle is fast enough that knocking a species onto the blacklist after players report it failing ingame is okay enough, but it's not a hill I feel I have to die on. My point is that the drama was caused by irresponsible devs and not having a way to killswitch species, not that we got a blacklist instead of a whitelist.


Backspace Button

I think the design of the backspace button not is cool. Maybe if you change for a normal button it would be better

Can I work on this issue?

Yes!!!

There might be a practical solution to this, there is a symbol in unicode that was made for this

That's what I'm Talking about!!! Good job @peterekepeter!

@sonya323 if you come up with anything better, let me know though.

Duplicate of #13


#10 Parameterized each list tile

listItems array created, with customizable fields for each item within
components folder gets several new additions
drawer state moved to App

Couldn't figure out how to center icons in closed sidebar. Any pointers?


Proxy api is not working in deployment

Hello @kailong321200875
Thank you for your kind responses.
I tried to deploy my project on vercel and it's done.
But the api is not working.
vite.config.ts

src/config/axios/config.ts

When I try to make a request in deployed website, 404 error is occured.

How can I fix?

base: '/api'，That's right

Hello @kailong321200875
I deployed pro not base.
And you mean that use '/api' instead of 'api'?


kctrl: Allow users to use ytt overlay while creating package installs easily

Describe the problem/challenge you have
Allow users to supply an overlay file or inline (simiolar to how we handle values file) that can be fed into the ext.packaging.carvel.dev/ytt-paths-from-secret-name annotation.
Describe the solution you'd like
A flag like --overlay which can be used multiple times (similar to how kapp accepts multiple -f flag) which can be used to create multiple overlaying annotations.
Acceptance criteria:

[ ] Creates secrets with ownership annotations using overlays provided by the user
[ ] These secrets should be added as overlays via annotation
[ ] They should be garbage collected while uninstalling
[ ] Tests

Open questions

Should we allow multiple overlays? Does this help users organise their overlays better?
Should we create one secret with multiple file keys?
How do we handle updates? Do we merge if only one file is provided? Or do we clobber and overwrite the list of overlays each time? (not merging would be consistent with how we handle values secrets today)

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Branched out from #412
Relevant documentation on the cluster side of things : https://carvel.dev/kapp-controller/docs/v0.36.1/package-install-extensions/#adding-paths-to-ytt-overlays

First off, would love to make sure we have a --dry-run or similar option, since most of my exposure to using this annotation is then committing the results to git instead of applying then and there.
We use this annotation a lot, and it comes up for several reasons:

This is (as you mentioned) the only way to apply an overlay to a PackageInstall
We store everything as an App CR that creates PackageInstalls, and we need to store SOPS encrypted files as wrapped secrets, we then apply that secret into the cluster and link it to the PackageInstall with this annotation.
While the primary motivation are overlays, you can also use this to "bundle" other manifests into a Package -- things like roles, namespaces, or other things that the package itself should handle but doesn't.

Regarding:

Should we create one secret with multiple file keys?
We don't usually do this as it's very confusing for newer users, I realize it's possible (and we've done it on occasion) but it makes things a little harder to understand so I'd recommend against it but only weakly and can be convinced otherwise.

Also, I really think given the utilization of these use cases we should really move this out of the annotations and into an actual field.

That does make a lot of sense, thanks!
Re:

Also, I really think given the utilization of these use cases we should really move this out of the annotations and into an actual field.

From a kctrl perspective I believe we will have to use the annotations till we are sure everyone has moved on to a newer version if we decide to make that change in kapp-controller I imagine kapp-controller might support both for a while as well.

As discussed over slack, I use this to provide an additional capability that one of the packages that I use does not provide:
apiVersion: packaging.carvel.dev/v1alpha1
kind: PackageInstall
metadata:
  name: contour
  namespace: tce-packages
  annotations:
    ext.packaging.carvel.dev/ytt-paths-from-secret-name.0: contour-tce-packages-ingressclass-overlay
spec:
  paused: #@ data.values.packageinstall.paused
  canceled: #@ data.values.packageinstall.canceled
  noopDelete: #@ data.values.packageinstall.noopDelete
  syncPeriod: #@ data.values.packageinstall.syncPeriod
  serviceAccountName: contour-tce-packages-sa
  packageRef:
    refName: contour.community.tanzu.vmware.com
    versionSelection:
      constraints: 1.20.1
      prereleases: {}
  values:
    - secretRef:
        name: contour-tce-packages-values
---
apiVersion: v1
kind: Secret
metadata:
  name: contour-tce-packages-ingressclass-overlay
  namespace: tce-packages
stringData:
  contour-ingressclass-overlay.yaml: |
    ---
    apiVersion: networking.k8s.io/v1
    kind: IngressClass
    metadata:
      name: contour-default
      annotations:
        "ingressclass.kubernetes.io/is-default-class": "true"
    spec:
      controller: projectcontour.io/contour

The main issue I currently have is that there's no way to do this via the CLI so I need to install packages manually (or patch them) after created via the CLI.
Another example:
apiVersion: packaging.carvel.dev/v1alpha1
kind: PackageInstall
metadata:
  name: kubeapps
  namespace: tce-packages
  annotations:
    ext.packaging.carvel.dev/ytt-paths-from-secret-name.0: kubeapps-tce-packages-overlay
    ext.packaging.carvel.dev/helm-template-name: kubeapps
    ext.packaging.carvel.dev/helm-template-namespace: kubeapps
spec:
  paused: #@ data.values.packageinstall.paused
  canceled: #@ data.values.packageinstall.canceled
  noopDelete: #@ data.values.packageinstall.noopDelete
  syncPeriod: #@ data.values.packageinstall.syncPeriod
  serviceAccountName: kubeapps-tce-packages-sa
  packageRef:
    refName: kubeapps.community.tanzu.vmware.com
    versionSelection:
      constraints: 8.0.13
      prereleases: {}
  values:
    - secretRef:
        name: kubeapps-tce-packages-values
---
apiVersion: v1
kind: Secret
metadata:
  name: kubeapps-tce-packages-overlay
  namespace: tce-packages
stringData:
  contour-ingressclass-overlay.yaml: |
    #@ load("@ytt:overlay", "overlay")
    #@ load("@ytt:data", "data")
    #! Add kubeapps namespace
    ---
    apiVersion: v1
    kind: Namespace
    metadata:
      name: "kubeapps"
    #! Add HTTPProxy. We need to make sure that contour Ingress Controller is deployed, as this relies on Contour HTTPProxy
    ---
    kind: HTTPProxy
    apiVersion: projectcontour.io/v1
    metadata:
      name: kubeapps-grpc
      namespace: kubeapps
    spec:
      virtualhost:
        fqdn: #@ data.values.ingress.hostname
      routes:
        - conditions:
          - prefix: /apis/
          pathRewritePolicy:
            replacePrefix:
            - replacement: /
          services:
          - name: kubeapps-internal-kubeappsapis
            port: 8080
            protocol: h2c
        - services:
          - name: kubeapps
            port: 80
    #@overlay/match by=overlay.subset({"kind":"Deployment", "metadata":{"name": "kubeapps-internal-apprepository-controller"}})
    ---
    spec:
      template:
        spec:
          containers:
            #@overlay/match by="name"
            - name: controller
              args:
              #@overlay/match by=overlay.subset("--user-agent-comment=kubeapps/2.4.4")
              #@overlay/replace via=lambda left, right: left.replace("kubeapps/2.4.4", right)
              - tanzu-community-extension-for-docker-desktop/v0.0.1
    #! AUTH Token
    ---
    apiVersion: v1
    kind: ServiceAccount
    metadata:
      name: token-user
      namespace: kubeapps
    ---
    apiVersion: rbac.authorization.k8s.io/v1
    kind: ClusterRoleBinding
    metadata:
      name: token-user
    roleRef:
      apiGroup: rbac.authorization.k8s.io
      kind: ClusterRole
      name: cluster-admin
    subjects:
    - kind: ServiceAccount
      name: token-user
      namespace: kubeapps

@100mik can you elaborate on the --ytt-overlays use case?

or directories with overlay files.

This functionality in particular would be great even for gitops use cases, having the ability to dump my files into a directory and then kctrl blah blah -f my_directory and dump out a well formatted secret that already injects all of the files would be super handy.  I don't think even kubectl has that kind of smartness when --dry-run creating secrets.

We did go with --ytt-overlays as it was consistent with how we handle values


No line number or example for whitespace expression in case expr

This code
f : String -> String
f str =
    case str of
        "" -> ""
        _ ->

produces and error without any line number or indication of place:
-- SYNTAX PROBLEM ----------------------------------------------------- Test.elm

I need whitespace, but got stuck on what looks like a new declaration. You are
either missing some stuff in the declaration above or just need to add some
spaces here:

I am looking for one of the following things:

    whitespace

Detected errors in 1 module.

Thanks for reporting this! It's a duplicate of https://github.com/elm-lang/error-message-catalog/issues/96 so I'm going to close it in order to have one fewer issue to track.


feat(RingTheory/Derivation): define bundled CommDifferentialRing and DifferentialAlgebra

Define a typeclass CommDifferentialRing of CommRings with a bundled Derivation, and a DifferentialAlgebra for Algerbas on differential rings whose algebraMap commutes with the derivation.

Is there a problem with the instance I add?

Do you plan to add more results about this? Please move it into a new file in that case.

Do you plan to add more results about this? Please move it into a new file in that case.

A few more, proving that AlgHoms commute with the derivative in some cases. What's a good name for this file?

RingTheory/Derivation/DifferentialRing or RingTheory/DifferentialRing both makes sense IMO.

How would class DifferentialRing (R : Type*) [CommRing R] where help for having multiple derivatives?


Log WinHTTP errors

Determining the cause of HTTP failures on Windows is difficult, because the actual errors given by WinHTTP are never queried or logged in any way.

What is the symptoms that we're experiencing, that we need more logging?

I wasn't involved in this one, but I've done similar (and way more) with my TestHTTP tool
Timeouts, DNS resolution failures, certificate issues, have all popped up on occasion.
Far more information can be gained using WINHTTP_STATUS_CALLBACK

The issue to solve here is that all request errors that aren't status codes returned by a 'successful' request just end up as -800, giving no context as to what actually went wrong

Oh wait no, this PR is mine, I forgot about it

General request failures that don't result in a reply with a status code just end up returning status -800. Without a verbose logging mode, we can't dig too deeply, but these function returns should provide some context.
Since this PR, I rebuild my TestHTTP tool, and have some additional changes I could make here to work out issues, which I'll take a look at tomorrow.
Current issues that we get stumped by typically are DNS resolution issues, timeouts, and certificate problems


feat(slatetoreact): add serializer

This is an interesting concept and worth exploring further.
All the work done so far on slateToDom is moved to a convertSlate function that accepts transform functions to apply when returning domhandler Text, Element or Document nodes.
By default, these transform functions do nothing - they just return the input. As a result, all existing tests continue to pass.
A slateToReact serializer is added that uses these transform functions to return React elements. A simple test is included that uses React Testing Library to check we are rendering valid React elements.
This seems to be the only maintainable way to proceed. As has been proved by development so far, serializing Slate to HTML comes with a lot of caveats/config/considerations (e.g. handling whitespace). As a result, it would be ideal to use a central Slate to DOM serializer, and adapt that in order to return any other type of component or markup.

Concerned the library is going to grow too much with dependencies. If this experiment works, then it's worth keeping in mind that it may be advisable to create separate libraries for supported frameworks. e.g. slate-serializers-react or something.


Adds support for dark-mode and accessibility starting with iOS 13.

Previous versions of iOS will work the same as before.
The color mapping that I used in the JZWeekViewColor is as follows.
UIColor.white --> systemBackground all used to color backgrounds
columnHeaderWeekday: UIColor { return UIColor(hex: 0x757575) } --> secondaryLabel
columnHeaderDay: UIColor { return UIColor(hex: 0x757575) } --> secondaryLabel
allDayHeader: UIColor { return UIColor(hex: 0x757575) } --> secondaryLabel
rowHeaderTime: UIColor { return UIColor(hex: 0x999999) } --> tertiaryLabel
gridLine: UIColor { return UIColor.lightGray } --> separator
today: UIColor { return UIColor(hex: 0x0089FF) } --> systemBlue
appleCalendarRed: UIColor { return UIColor(hex: 0xFC3D39) } --> systemRed
If you have any questions feel free to reach out. This is a fix that we're using at the company I'm working at in order to fully support dark mode and accessibility in our app. Hopefully, it's pretty straightforward.
I renamed a lot of the colors to be more semantic to match the new iOS UIColor naming conventions (with the exception of blue and red). There's a good article on that here. https://nshipster.com/dark-mode/
Thanks so much for your hard work on this pod!

@cmriboldi  Thanks for the pr. It looks good to me.
Although JZWeekViewColors should be changed in the future, it is a fantastic solution now.
I am quite busy recently, I will try these colors first and merge it asap.

@zjfjack, Hey ✋ when will this get merged?

The same here, wondering if this will get merged anytime soon.

I will try to restart some work recently. I stopped updating this project
for a while. Hopefully next week.
On Wed, 19 Feb 2020 at 10:44, Eduardo Chavez<EMAIL_ADDRESS>wrote:

@zjfjack https://github.com/zjfjack, Hey ✋ when will this get merged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zjfjack/JZCalendarWeekView/pull/109?email_source=notifications&email_token=ABEWYPRIGIEXOVM4XSEKZCDRDRXFJA5CNFSM4I5IRAD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMFZEFI#issuecomment-587960853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEWYPXH2CEVYJL42IPXURLRDRXFJANCNFSM4I5IRADQ
.


Adding the Actual functionality of the lib.

The just-pushed commit e3cff27 should:

Fix :

Use componentDidUpdate instead of componentWillUpdate

Fix :

text prop should be required (i.e no defaultProp for it)

Upgrade both react and react-dom dev-deps to 16.5.2 or newer minor level version.

@bitriddler If you think it's good enough for now, we can merge, bump to V1.0.0 and start on the demo page?

Merging this and let the party begin! 🎉🎉 🎈


Add Chathumina Vimukthi to Contributors List

@ChathuminaVimukthi, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

The guidelines were really good and I felt awesome after making the PR and I'd love to check out other projects.
Thanks for the info !


Puzzle/Plug-In/Extension Icon

Icon Request

Icon name: Puzzle
Tags of this icon: Plugin, Puzzle, Extension, Add-on, Integration
Use case: For App Plugin or Extension Icon
Screenshots of similar icons:

https://remixicon.com/icon/puzzle-line
https://remixicon.com/icon/puzzle-2-line


Refresh Web Agent

PR includes:

Web agent decorator which provides a refresh rate to keep up to date values on decorated web agents.
Memory Web Agent decorated by RefreshWebAgent.
Dependant on https://github.com/foam-framework/foam2/pull/845

lgtm!!


add a web framework to deal with http

i created a new branch and choose NestJS as my web framework


glTF instancing and bounding box fixes

Fixes #6378 by adding support for the glTF 2.0 instancing extension described in the issue. It successfully renders the model referenced in the issue.
Fixes #5937. Fixes https://github.com/iTwin/itwinjs-backlog/issues/969. Both relate to incorrect bounding boxes computed for glTF models. For unclear reasons we were applying inverse transforms to the bounding boxes.

@alarkbentley @Ellord207 FYI.

Blocked by #6380.

  1) GltfReader
       computes bounding boxes:

      AssertionError: expected false to be true
      + expected - actual

      -false
      +true

      at Context.<anonymous> (agent/_work/1/s/core/frontend/src/test/tile/GltfReader.test.ts:383:78)


Promises instead of callbacks

First, thumbs up for this project! It looks like magic :) I also like that it can potentially make a lot of cordova plugins obsolete (thinking of the device plugin) when you can now have very simple snippets only to directly call native API.
And that brings me to the biggest issue I see at the moment when looking at the code. Since all native calls are async they need to be nested in the default nodejs callback pattern. However the Promise pattern can achieve much better read-ability (if done right).
Do you think this project could be promisified somehow?

I agree on this. However, we should take into account that there is no babel or other transpiler available. So we should leave our ES6 syntax home and write old school highly compatible javascript.

Maybe using Q promise or another library? https://github.com/kriskowal/q


Fixed command to run azure function

I'm not sure why I had func run in the first place. Must have been a typo on my part.
The correct command is func start.

You're right, I missed this also (prob due to dotnet run, and it seems it used to be func run in v1 of the CLI)


[API Bug] Detail tag isn't showing the loading indicator animation

Raycast version: 1.25.3
Description
When we are using the tag <Detail /> to present text content and make use of the prop isLoading, the view is not presenting the loading animator indicator like it is being presented when we are using the tag <List />.
Steps To Reproduce

Create a screen which renders a <Detail /> tag and add a prop isLoading, i.e:

<Detail isLoading={ true } markdown="Small content" />

The current behavior

The expected behavior

Hey @unnamedd, I can only reproduce this when I use the Detail component in a navigation stack, i.e. when the Detail view gets pushed, the isLoading property doesn't seem to be respected. When used standalone, outside of a navigation stack, it works as expected. Can you confirm this?

Yes @fe9lix, it is confirmed. In a navigation stack it is not working, but in a standalone mode it is showing the loading animation. Here a small gif to confirm that:

The fix for this issue was released in the version 1.25.4, therefore I'm closing this issue.


Speed on Mac

@sreeder and @jmeline , you may know this already, but I notice that almost all aspects of the program are slower on Mac. Clicking to plot a data series, clicking to edit a data series, basic operations. Hopefully the refactoring will address?

I'm going to close this issue. @horsburgh can re-open if you have experienced this.


Allow non-square input shape for keras models

Hello!
It works more or less, thank you! Is it possible to change NN input size to 1600x800?

Hi,
I could push update to allow non square input size. There are no pretrained weights for it, so you'll have to train from scratch.
But in your particular case - I'm not sure if this kind of resolution will work with Edge TPU. I gave it a quick try and compiler failed to create a model.

Sure, I will do experiments
Maybe 800x800 is good solution Than I will divide picture into 2 parts

I had closer look at this and it seems like edgetpu_compiler is not particularly happy about non square inputs for this model (regardless of shape). Since I want to be sure that people using pretrained and finetuned keras model have no problem compiling it to the device, check for square inputs will not be removed.

Got it. It is very interesting why...

Dear @xadrianzetx I noticed before that deeplab recognize some objects better when input is larger.  Could you advice how to change from 513x513 to 800x800?

You can create new instance of keras model with input shape you want like so:
import coral_deeplab as cdl

model = cdl.applications.CoralDeepLabV3(input_shape=(800, 800, 3))

As I said earlier, there are no pretrained weights for this shape, so you have to train this model yourself. I think you can use scripts you posted in other issue to do so.

FYI: 800x800 trainubg with Nvidia 1080Ti failed, I have switched to try train 512x512