NIFI-8230 Removed default Sensitive Properties Key

Description of PR
NIFI-8230 Removes the default internal Sensitive Properties Key which provided fallback support when the value of nifi.sensitive.props.key was empty.  NiFi used the default internal value on new installations where the administrator had not configured a sensitive properties key.
To maintain ease of use, this PR includes an update to NiFiPropertiesLoader.get() that checks for a null or blank sensitive properties key and generates a random key when the flow configuration file is not found.  The random key generation process uses java.util.SecureRandom to generate an array of 24 bytes, which is then encoded using Base64 without padding to produce a 32 character string.  Using Base64 without padding avoids introducing unsupported property characters while also providing a reasonable range of potential random characters.
This approach supports generating a random key for installations of NiFi while avoiding random generation when upgrading.  Existing flow configurations may already contain sensitive properties encrypted with the default internal key.  For upgrades of existing installations that do not have a sensitive properties key, NiFi logs and error and throws an exception referencing the Administration Guide section on Migrating a Flow with Sensitive Properties.  To support migration, the ConfigEncryptionTool retains the default internal value for reading existing flows.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[X] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Great job, @exceptionfactory !

Great job, @exceptionfactory !

Thanks for the helpful feedback @CefBoud!  I made changes and pushed an update to address your comments.

Excellent work, @exceptionfactory.  Nicely refactored!

I'll test this out

Just to summarize the latest changes, after some additional discussion with @markap14, he suggested that implementing a simplified command for setting the Sensitive Properties Key to make the migration path easier for current users with blank keys.
The most recent commit includes an update to nifi.sh to support the following:
nifi.sh set-sensitive-properties-key <sensitivePropertiesKey>
The script passes the new key to the command class, which reads the current key from nifi.properties and falls back to the internal default value if the existing value is blank.
This approach required refactoring the PropertyEncryptor classes to a separate module named nifi-property-encryptor.  The new command class is located under nifi-flow-encryptor.  The existing ConfigEncryptionTool continues to work, but contained a lot of the same code, so this change provided an opportunity to refactor ConfigEncryptionTool to leverage the PropertyEncryptor interface.  This simplifies ConfigEncryptionTool and also removes code that diverged from the standard property encryption approach.
With these changes, the Admin Guide now includes a new section describing the set-sensitive-properties-key command.

@exceptionfactory I gave this a try. Loaded up a flow created on main and then tried to startup. It failed almost immediately, telling me that i had to set the sensitive props key, which is good.
So then I tried to run the command update the key:
nifi-1.14.0-SNAPSHOT $ bin/nifi.sh set-sensitive-properties-key "the quick brown fox jumped over the lazy dog"

Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_281.jdk/Contents/Home
NiFi home: /Users/mpayne/devel/nifi/nifi-assembly/target/nifi-1.14.0-SNAPSHOT-bin/nifi-1.14.0-SNAPSHOT

Bootstrap Config File: /Users/mpayne/devel/nifi/nifi-assembly/target/nifi-1.14.0-SNAPSHOT-bin/nifi-1.14.0-SNAPSHOT/conf/bootstrap.conf

Unexpected number of arguments [9]
Usage: SetSensitivePropertiesKey <sensitivePropertiesKey>

So it appears there's an issue of some sort in the way that the arguments are passed in the nifi.sh script to the Java program, as it appears that even though "the quick brown fox jumped over the lazy dog" was quoted, it was passed to the Java program as 9 separate arguments.

@exceptionfactory I gave this a try. Loaded up a flow created on main and then tried to startup. It failed almost immediately, telling me that i had to set the sensitive props key, which is good.
So then I tried to run the command update the key:
nifi-1.14.0-SNAPSHOT $ bin/nifi.sh set-sensitive-properties-key "the quick brown fox jumped over the lazy dog"

Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_281.jdk/Contents/Home
NiFi home: /Users/mpayne/devel/nifi/nifi-assembly/target/nifi-1.14.0-SNAPSHOT-bin/nifi-1.14.0-SNAPSHOT

Bootstrap Config File: /Users/mpayne/devel/nifi/nifi-assembly/target/nifi-1.14.0-SNAPSHOT-bin/nifi-1.14.0-SNAPSHOT/conf/bootstrap.conf

Unexpected number of arguments [9]
Usage: SetSensitivePropertiesKey <sensitivePropertiesKey>

So it appears there's an issue of some sort in the way that the arguments are passed in the nifi.sh script to the Java program, as it appears that even though "the quick brown fox jumped over the lazy dog" was quoted, it was passed to the Java program as 9 separate arguments.

Thanks for the feedback @markap14!  I pushed an update to nifi.sh that passes quoted arguments to SetSensitivePropertiesKey to handle quoted values as a single argument.
I also adjusted the minimum required key length to 12, aligning with the existing length requirement of 12 in StandardPropertySecretKeyProvider.

@markap14 Do you have any additional feedback, or do the latest changes look good?  Thanks!

All looks good to me at this point @exceptionfactory. Thanks! I rebased against main, resolved the merge conflict, and merged to main.

Thanks @markap14, and thanks to @bbende, @CefBoud, and @thenatog for the feedback along the way!


Continuing Archived-At issues

After 08-25-2022, when the postconfirm Archived-At issues was fixed for the second time, there are still a few messages that have incorrect Archived-At headers, though far less than was happening before the fix.
Examples: (date, message link, incorrect header value)
12-14-2022,https://mailarchive.ietf.org/arch/msg/auth48archive/SGIk8LXmIiSwdDT6D-ARmtRoyss,hcvPTMHdX352X228HPoFgqGbd78
12-06-2022,https://mailarchive.ietf.org/arch/msg/v6ops/D7pl_3J7PMnOvx_e_rsKJ2CIcac,UjM3z5SdEVIAiZqPGYQxiyjv1EA
10-25-2022,https://mailarchive.ietf.org/arch/msg/netmod/uoogBQMtHfDwkgcb1MagUikbiF4,NZI5GjffkWMPo54S9rZqLOV9Whw
10-21-2022,https://mailarchive.ietf.org/arch/msg/idr/JuAQpRO-luMPwmJraowu1bLp1AM,uWmGZMVTsn1pX1vydg3C1cHjD7Q
09-29-2022,https://mailarchive.ietf.org/arch/msg/savnet/GW2jT3J8CyAAB8KokNQVQ3ZcW4Y,YMx-UFTTHlj-U-iNyoE6wcXRIcM

All examples of this issue (in the comments) look to have problematic Message-ID headers. 4 of the 5 are from a chinaunicom.cn sender and have values like:
Message-ID<EMAIL_ADDRESS>The other, from 09-29, has an empty Message-ID header.

More information. The problematic Message-ID is properly handled by Mail Archive (specifically email.EmailMessage) so the message detail URL is correct. Postconfirm includes the extra characters in the message-id and so computes an Archived-At header that doesn't match the archive URL.

As of 2023-02-03, we run scan_all.py archived_at_report each night from cron to check for new incorrect Archived-At headers and create entries in Redirect as needed. This is needed until postconfirm is upgraded to Python3. See https://github.com/ietf-tools/postconfirm/issues/31


[Event Request] Codeunit::"Whse.-Post Shipment" - Function PostSourceDocument - OnPostSourceDocumentAfterGetWhseShptHeader

We like to request the following Event:
Object: Codeunit::"Whse.-Post Shipment"
Function: PostSourceDocument
Publisher Event: OnPostSourceDocumentAfterGetWhseShptHeader
Reason: To implement custom business logic
Where is the event placed:
with WhseShptLine do begin
WhseShptHeader.Get("No.");
OnPostSourceDocumentAfterGetWhseShptHeader(WhseShptLine, WhseShptHeader);
case "Source Type" of
DATABASE::"Sales Line":
Event Code:
[IntegrationEvent(false, false)]
local procedure OnPostSourceDocumentAfterGetWhseShptHeader(WhseShptLine: Record "Warehouse Shipment Line"; var WhseShptHeader: Record "Warehouse Shipment Header")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


License mismatch between LICENSE.md and code header

According to the LICENSE.md file on this repository, this code is licensed under an MIT License. According to the header of avdweb_AnalogReadFast.h however, this code is licensed under the GPL v3 license.
This conflict should be resolved as these two licenses are very different from one another. Thank you!

I have deleted the licence in the header, so it should be ok now


Ticket05/ref form

Hi! @valerialp and I were refactoring the fill_form.js partial and reducing the 6 functions to just one called fillAllInputs using event, currentTargets and one big conditional with six conditions depending on myKey value.
Is anyone free and interested to review this? :) Let us know if there are any doubts or issues with this.
Thanks!

All conflicts solved by:

Simplifying the function fillUserInfoObject at fill_form,js with just 2 parameters.
Re-adding missing classes of circle elements at _main-preview.html partial.


Design doc for "Scale Mode"

Propose a design to teach hive to be able to scale to O(100k) spoke
clusters.
HIVE-1862

@abutcher @jnpacker @xiangjingli PTAL, thx!


copr: aggr null for first

ref: pingcap/tidb#2057
@siddontang @coocood PTAL

LGTM

@siddontang PTAL

Seem not the same with the TiDB PR.

TiDB uses a flag to indicate if the result is set. But we use an Option already, no need to add an additional flag.

LGTM


Table body with missing data when markdown is padded

Table rendering changed after version 0.15.2.
For table (note spaces on the left of the table):
  | Col 1 | Col 2 | Col 3 |
  |-------|-------|-------|
  | A1 | B1 | C1 |

With version 0.15.2 I get expected :

Col 1
Col 2
Col 3

A1
B1
C1

But with versions 0.16.1 and 0.17.0 I get a table with first column empty and last column missing:

Col 1
Col 2
Col 3

A1
B1

Without spaces on the left of the Markdown table, the HTML is correct.

Yep, that's a bug! Will fix ASAP.

Fixed and released 0.17.1 with the fix: https://github.com/commonmark/commonmark-java/blob/main/CHANGELOG.md#0171---2021-02-03
Thanks for reporting!

Thank you for this fast fix and release :+1:


[Question] How can I disable /debug/pprof on node_ip:6060 ?

When I access {$node_ip}:6060/debug/pprof/, I can see debug info on it.

Can I disable /debug/pprof on {$node_ip}:6060, or limit its access permission?
It may related to node-disk-manager.
@https://github.com/harvester/node-disk-manager/blob/master/main.go#L14

Hi @W0n9,
I thought this related to [ENHANCEMENT] Do not expose port 6060 with NDM
It would be resolved with v1.3.0.
In the previous version, please change the parameter profile-listen-address to "" to avoid enable profiler by default

Hi @W0n9,
I thought this related to [ENHANCEMENT] Do not expose port 6060 with NDM
It would be resolved with v1.3.0.
In the previous version, please change the parameter profile-listen-address to "" to avoid enabling profiler by default

I have applied args to container, LGTM, thanks
spec:
      containers:
        - args:
            - '--profile-listen-address'
            - ''
          command:
            - node-disk-manager


Fixes main() dnstap.Output close nil panic

In 8df42ac7728772ec76d8f569d65e1cfa4dfa938b the dnstap.Output handling
was reworked to allow reopening the output on SIGHUP. In the process
a nil panic was introduced in main():
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x5b1b6f]

goroutine 1 [running]:
main.main()
>-/go/src/github.com/dnstap/golang-dnstap/dnstap/main.go:159 +0x1ef
	exit status 2

The root cause is on L159 where the main function tries to call
o.Close() while o is nil.
This commit removes both the unused o variable from main() as well
as the o.Close() that triggers the nil panic. There is no resource
being leaked since the SIGHUP rework defers a Close() in
outputLoop().

Thank you for the fix, will merge shortly.

@cmikk Thanks for the quick review & merge :-)


#15 Begin work on refactoring

I'm going to be merging the restructuring pretty regularly, as I imagine it will take a while and I don't want a branch to diverge too much.


Allow middleware to run client-side only in SSR mode

What problem does this feature solve?
Middleware frequently need to check state such as whether a user is logged in.
If you want to redirect users to a login page based on their logged in status on every page, you cannot do this via a middleware in SSR mode.
Changing the whole app to SPA mode for this one feature will slow the entire app down.
What does the proposed changes look like?
A flag in nuxt.config.json to run middlewares in client side only.

This feature request is available on Nuxt community (#c10739)

I would suggest the feature of using middleware.client.js and middleware.server.js vs this flag so it matches the same feature of plugins.  This would also eliminate a bunch of if(process.client) stuff as well.  I may be working on a pull on this at some point but currently don't have time.

I think the right approach here is to early return if it's being run on the server side:
export default defineNuxtRouteMiddleware(to => {
  if (process.server) return
  // client logic
})


Drop TestServer

I've had a number of issues with AspNet Core's TestServer. For example:
https://github.com/dotnet/aspnetcore/issues/18463
https://github.com/dotnet/aspnetcore/issues/21677
Essentially it's not HTTP spec compliant and has edge cases that make it different from Kestrel that I run into.
Going to drop support for it, remove it from tests and generally discourage usage.

Its a bad testing model as well as your testing config and build.

It appears they fixed both of these issues as well as a couple more because they ran into them when they made their own reverse proxy 😬 .NET OSS is frustrating sometimes.


Fix typo in swarm filters doc

Describe the proposed changes
Fix typo scheduler form running containers to scheduler from running containers
Unreleased project version

Related issue

Related issue or PR in another project

Please take a look

Deploy preview ready!
Built with commit 10a3f3be80a0f7226c4e0dec191a4bee65d37af4
https://deploy-preview-752--docker-docs.netlify.com

Thanks, @dongyuzheng :)


refactor: rename PinStatus id → requestid

This is an attempt to clarify the difference between cid identifier in request and id in response:

adds "Identifiers" section to the docs and clarifies purpose of each
BREAKING CHANGE: id is renamed to requestid

I believe this will make it easier for people to reason requestid vs cid, but can restore old field name if community decides it is not worth the hassle.

PREVIEW: https://ipfs.github.io/pinning-services-api-spec/#specUrl=https://raw.githubusercontent.com/ipfs/pinning-services-api-spec/docs/pid/ipfs-pinning-service.yaml
cc @obo20 @andrew @aschmahmann  @GregTheGreek @priom @jsign  @sanderpick @andrewxhill @ipfs/wg-pinning-services
Please provide feedback (even if its just :+1: / :-1:)

I would have thought pid corresponds to peerID (which incidentally looks like a CID), not PinID. For this reason it does not seem to me like the best name. Perhaps it does not hurt to be specific and name this requestid or trackid.

If we're going to rename it, +1 to requestid, just remove the ambiguity. I saw pid and immediately thought process id, so it's clear to me it's not really alleviating confusion.

I saw pid and immediately thought process id
+1 on that, also +1 on @hsanjuan's requestid

+1 to @jacobheun and @hsanjuan, plus "pid" has some unpleasant real-world meaning.

Thanks for quick feedback! renamed it to requestid and updated PR to reflect that

Any thoughts on objectid, serviceid, or psid(pinning service id)?
requestid works for me, but it makes me immediately think of the api request itself which could be confusing to some people seeing as you may make multiple api requests to a single ID over its life cycle.

I think those are also fine, but requestid enables us to provide better mental model:

Every (HTTP) request to create a pin object at a pinning service has a unique ID
You use this ID to check the status of ongoing pin request, and for revoking / replacing it later.


Unable to install - could not find driver

When running php artisan canvas:install I get the following -
root@2736700b8911:/app# php artisan canvas:install

Welcome to the Canvas Install Wizard! You'll be up and running in no time...

Setting up your database...

An unexpected error occurred. Installation could not continue.
✘ could not find driver

Migrations were rolled back. Please run the installer again.

If this error persists please consult https://github.com/cnvs/easel/issues.

If I run it again, it asks me to add admin user details but then immediately shows the same error - could not find driver. There is nothing in the logs to investigate further.

Debugging seems to point me to when the DB is trying to seed or the user is created. The user is created in the DB though. Will update when I have more info.

@richdynamix Thanks for checking out Canvas! I'll take a look at this today and see if I can find a solution for you.

@richdynamix What type of DB are you installing Canvas on?

Hi @austintoddj I am installing this on a MySQL 5.7 DB. My project setup is with Docker.
loving the new webiste btw ;)

Thanks @richdynamix, glad you like the new site! Haven't actually done my own installations on Docker, so I don't have a ton of familiarity with it. I will keep digging though and see what I come up with.

Hey @austintoddj Did you manage find any resolution to this issue? Really keen to build my next blog with Canvas 😁

@richdynamix Did the error you encountered happen using v3.2.10?

Ditto this issue; although my configuration is slightly different.  I'm running a VirtualBox instance of an Ubuntu PHP 7.1 box on a Mac, provisioned with Vagrant via Puphpet.  The source files in this setup are on the Mac's native filesystem, mapped to a folder within the virtualized guest OS and configured as the www root in its nginx config.  Because of this arrangement, the composer create-project --prefer-dist cnvs/canvas blog command must be run on the host OS (the Mac), but then you must ssh into the Vagrant box (virtualized guest OS) to run php artisan canvas:install.  If you try to run php artisan canvas:install from the host OS (on your main computer), it can't connect to the correct MySQL database since that runs in the virtualized guest OS (or, in the case of @richdynamix a Dockerized container; try docker exec -it {container name} bash, find your blog Laravel project folder, then try php artisan canvas:install from there - see if that works!).
It's worth noting that the installation instructions do not warn you to cd blog after the composer command finishes, in order to proceed with the canvas:install.  You might want to mention that.
Even after successfully creating the project, as with @richdynamix, I am also unable to php artisan canvas:install and get the same error message:

An unexpected error occurred. Installation could not continue.
✘ could not find driver

This happens only after it asks for my email address, a password, a first name and a last name.  POW!  Right then and there; an error about finding the driver.

A series of DB tables are created in MariaDB (MySQL)
canvas_posts has 1 row (a 'hello world' post)
canvas_users has 1 row (a user, but it only has the email address in it; no password, no first or last name)
canvas_migrations has 17 rows (weird stuff, apparently dating back to 2016)

Hope that helps you get to the bottom of things!

@unrivaledcreations First off, thanks for the extremely detailed and well-worded response, it's a huge help. Hopefully I can answer what questions you have and we can get to the bottom of this.
As for what you're seeing in the database:

A fresh installation will yield just enough blog data to get you started and understand what's going on
The migrations table holds records of all the database changes in the application and throughout its development. See more here

Do you have each of these extensions installed in your VirtualBox that you're running Canvas in?

PHP extensions (PDO, SQLite, OpenSSL, Mbstring, Tokenizer, Zip)

SQLite and Zip were both missing.  Mbstring would normally be missing from a stock PuPHPet configuration, too, except I'd already added that to make phpMyAdmin work.
For others using PuPHPet to manage your dev environment, edit your config.yaml file and add these lines:

Under php:modules:php, add - mbstring and - sqlite
Under php:modules:pecl, add - zip

@richdynamix, if you're using a Docker container, you'll have to find a container that has all these extensions already installed for you, or you'll have to add them yourself (and document those steps so you remember to do it again later when using future container updates).  Good luck to you!

Thanks for the update @unrivaledcreations. I'll definitely look into adding a check into the canvas:install process. 👍

I am having the exact same issue while trying to install. Everything goes smoothly, i added the db credentials to the .env file, and then dophp artisan canvas:install
and of course i get the same error again. For the record i am doing this on a digitalocean 1gb ubuntu 16.04 droplet, and php modules list seems ok except maybe that i have "sqlite2" rather than simply "sqlite" installed. could this be the issue?
I will try to look deeper into this later today


Move to JuliaParallel

Hi Jared,
Would you consider moving this repository to the JuliaParallel organization?  I can send you an invite to join the organization so you can have push access.  It would be great to give your work more visibility and prevent duplication of effort.  A PETSc interface has been on wishlist for parallel Julia for a long time.  I think now is the right time to start working towards this goal now that we will start to have package precompilation so load times won't be intolerable.
What do you think?

Sounds like a good idea.

Any updates on this? It will make it slightly easier for us to open PRs and probably also give a little omre visibility.

Bump @JaredCrean2. It is ok that the package is WIP.

What do I need to do?  I'm not familiar with how the umbrella organizations work?

Join the JuliaParallel organization (if you have not already).  Then click on the "settings" tab in the right hand panel for the github Petsc.jl page.  You should see the transfer ownership option at the bottom of the settings page.

How do I join the organization?  For other organizations I got added by the organization admins.

I just sent an invitation


Add Meta tags

This is a collection of all used meta tags like standard html & Swift, Apple, Windows, Facebook etc.

https://github.com/RALMAZ/Awesome-meta-tags
This is a collection of all used meta tags like standard html & Swift, Apple, Windows, Facebook etc.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

No table of contents, license, or contribution guidelines. Doesn't have the suggested tags. Make the title Awesome Meta Tags Please read the contribution guide lines and fix your errors.


Source of randomness for selecting relayers

Hey everyone, this is a challenge we were exploring with @Perseverance for one of the possible solutions for the collision problem. Would love to hear whether you think something like this could work, or a more complex PRNG is required.
Introduction
One of the directions under consideration for the collision problem is to have relayers register on-chain, put a stake, and have the protocol randomly select a relayer every epoch to submit a batch of meta txes to a smart contract. Selecting a relayer on-chain requires a source of randomness that can't be predicted ahead of time or manipulated in a way to increase a relayer's chance of getting selected.
Problem Statement
Given a list of relayers R = [R_1, R_2, ..., R_n], and function isTurnOf(R_i) which returns true if R_i can produce a block during this block (B), we'd like to discuss employing the parent's block hash (P_h) as a source of entropy in isTurnOf, e.g. by checking if R[uint256(P_h) % n] == R_i. Using P_h is usually not a good practice, due to the following reasons:

Miners could withhold a block, if the block hash is disadvantageous for them.
During B, P_h is known, and therefore, users (and specially miners) can make transactions to influence the decision in isTurnOf.

Discussion
In the case of selecting a relayer:

The reward a miner would forego by withholding a block, is probably significantly than the reward of a batch of meta txes (also depends on the number of meta txes in a batch).

In the simple isTurnOf mentioned above, if R is mutable, the miner could create the transactions and add them to the beginning of the block to influence the decision (if it's their turn to propose block). This might seem like a very unlikely case to assume such collaboration between a relayer and a miner, but, I think a considerable percent of relayers could also be miners (as miners are running a full node anyway and the marginal cost of running a relayer is low).

Possible Improvements
Two general approaches could help with problem 2.:

Fix R, for at least one block before B, e.g. if a new relayer calls register, or an existing relayer calls withdraw, they are put on a queue, that is processed the next block.
Modify isTurnOf to make it unpredictable for everyone but the relayer who should submit batch now. For example, have each relayer commit to a random value (e.g. keccak256(S)) on register, and on every execTransactions, and pass that to isTurnOf(R_i, S). This limits miners to only knowing whether it's their turn this block or not, so it becomes harder for them to influence the decision by front-running. However, because nobody but the relayer knows whose turn it is, it becomes hard to punish relayers for not submitting blocks, if this is required by the protocol.

Extension
The simple protocol outlined above can be further extended in various ways. One particular extension, is to select a shuffled subset of R (D for dynasty) every M=32 blocks, in which, isTurnOf(D_i) == true in block B_i where 0 <= i < M.

@PhABC your input is appreciated.


Vulnerability roundup 67: libsass-3.5.5: 4 advisories

search, files

[ ] CVE-2018-20821 (nixos-unstable, nixos-19.03)
[ ] CVE-2018-19797 (nixos-19.03)
[ ] CVE-2018-19826 (nixos-19.03)
[ ] CVE-2018-19827 (nixos-19.03)

Scanned versions: nixos-unstable: dfd8f84aef1; nixos-19.03: cf3e277dd0b. May contain false positives.

See also #60840, #52973, #58266, #54804, #53571. libsass did not have a new release when we checked last time.

nixos-19.09 has libsass-3.6.1 which is not listed as vulnerable in the CVE.
nixos-19.03 still has libsass-3.5.5, but I'm not sure what the support policy is here. Do we keep issues open if they only affect the last release? This would be helpful to know as I'm currently going through the CVE roundup list to try to update the case status, and a lot of them have been fixed in unstable and 19.09.
Upstream has indicated that no further releases for 3.5 series will be made, so we can consider it EOL. If we need to support 19.03 still, libsass would have to be updated to 3.6.x.

I don't think we should upgrade libsass to 3.6. on 19.03.


docs: Add user guide for viewing messages from a stream.

Added user guide for viewing messages from a stream.
Added a link to new documentation from the index.md table of contents.

Automated message from Dropbox CLA bot
@maydhak, it looks like you've already signed the Dropbox CLA. Thanks!

Looks good to me,
@trueskawka ?

Agreed. I'll approve the task in the GCI app and we can merge later.
Thanks @maydhak for working on this!

@maydhak One thing you could fix if you had some time before the merge, is making lines no longer than 76 characters - it's easier to read in the terminal.

Merged! Thank you, @maydhak!
I've fixed the line lengths, so that's where the conflicts with your feature branch are coming from. Nothing to be worried about ;)


Document Asset Bundling (Files/Images/Fonts)

I might be able to tackle this one, were you thinking as a guide or more as a concept page? I see it's already mentioned briefly here but that's pretty much it.

Many folks seem to have problems when it comes to including assets in their bundles correctly e.g most of them coming from task runners like Gulp || grunt, store their images etc in one separate ./assets folder and complain about the difficult management of these assets. The list goes on when using ETWP and the paths are off etc etc. 😛 tbh I guess it will be difficult to document, but a few 101 examples to understand the difference between File Tree <=> Dependency Graph would be helpful :)

So how about an "Asset Management" guide that goes through loading images, either directly via js or css, and then also discusses aliasing for for those that want to stick with an /assets directory? For example, if you alias, then you can do things like import Img from 'Assets/image.png'. I find that approach really useful for some other things (not really for assets).

but a few 101 examples to understand the difference between File Tree <=> Dependency Graph would be helpful :)

Don't assets like images and fonts just become a part of your dependency graph? Not sure exactly what you mean here...

Don't assets like images and fonts just become a part of your dependency graph? Not sure exactly what you mean here...

Many don't understand the Dependency Graph approach at all at the beginning :). They still think in terms of a file tree, I especially noticed that (subjective), when it comes to assets loading. They see the 101 React Tutorials and do it with the CSS but without really understanding why in terms of the underlying concept(s) 😛
General
File Tree
|– assets
|  |– img.png
|  |– icons
|  |  |– icon.svg
|  |  |–  etc... and more deeply nested like per 'page'
|– styles
|– pages
|- gulpfile.js

Dependency Graph
|– components
|  |– component
|  |  |– index.js
|  |  |– index.css
|  |  |– icon.svg
|  |  |– img.png
|  |  |– subcomponent
|  |  |  |– index.js
|  |  |  |– index.css
|  |  |  |– icon.svg
|  |  |  |– img.png
|
|
|– entry.js
|– index.html
|- webpack.config.js

entry.js
import component from './components/component'

components/component
import style from './index.css'

import icon from './icon.svg'
import img from './img.png'

import subcomponent from './subcomponent'

const Component = () => {...}

export default  Component

components/component/sub
import style from './index.css'

import icon from './icon.svg'
import img from './img.png'

const SubComponent = () => {...}

export default  SubComponent

EDIT: Ah you mean they don't get bundled with the js but are instead added to the build directory as individual files?

Yep 🙃 and this comes to the mix in additionally afterwards, most think webpack will keep the original src [file/folder] structure (like grunt/gulp) and not that it will get resolved && flattened in the output along with their bundle.js

Ok yea I think I have enough to get started on a guide now... thanks for the details!

There're endless ways to do it and you mentioend resolve.alias already, so please don't understand the examples above as the non plus ultra, but when it clicked on the concept, many don't seem to have bigger problems bringing resolve etc into the mix 😛 , so the above should just highlight the overall difference between to two common approaches generally

Mentioning the relation between the Dependeny Graph and 'webpack walking the import/require() statements` also seemed to work well as a hint (from my experience) :D

Yeah, I follow you 👍 ... maybe some links to concept pages throughout wouldn't hurt either. I'll ping you for a review once I have something in the works, sounds good?


[4.x] Adds a DialectFactory implementation to permit Hibernate to introspect database metadata properly when supporting container-mode JPA

This PR introduces a DialectFactory implementation that can introspect a DataSource-reachable DatabaseMetaData to discover and build the proper Dialect for Hibernate to use to communicate with a database.
The DialectFactory implementation is needed because Hibernate's default DialectFactory implementation is incapable of discovering database connectivity information that is indirectly linked by a META-INF/persistence.xml's <jta-data-source> element.  (The default Hibernate behavior relies on an application-mode-JPA-only property that, interestingly, the specification rightly discourages users from providing when using container-mode JPA.)
The DataSourceBackedDialectFactory detects the case when the DialectResolutionInfoSource supplied to the DialectFactory's buildDialect() method is null.  (The possibility of its being null is not documented, but it is very commonly null in almost all situations.)  When this state of affairs holds, the DataSourceBackedDialectFactory will get its hands on a DatabaseMetaData and build a proper DialectResolutionInfoSource representing it.  It will then hand this off to an invocation of the default DialectFactory implementation's buildDialect() method.
The net result is that dialect introspection happens properly even when the only way that Hibernate can "see" the database is by way of a JTA data source.
The other methods in the class are related to actually getting it recognized by Hibernate's convoluted bootstrap sequencing. Notably, the DialectFactory implementation will not register itself if the user has specified a Dialect explicitly.
This PR also ensures that Hibernate javadoc is correctly linked.
This PR also ensures that the existing CDISEJtaPlatformProvider class functions properly even when CDI is not present.

@barchetta I've tagged you mainly to take a look at the javadoc work (Hibernate didn't have an element-list or any offlineLink entries).


即使挂了全局代理，也不能下载港澳台区的番剧

bilix get_video https://www.bilibili.com/bangumi/play/ep398594 --cookie ************************
WARNING  GET ConnectError url: https://www.bilibili.com/bangumi/play/ep398594
WARNING  GET ConnectError url: https://www.bilibili.com/bangumi/play/ep398594
WARNING  GET ConnectError url: https://www.bilibili.com/bangumi/play/ep398594
ERROR    GET 超过重复次数 https://www.bilibili.com/bangumi/play/ep398594
Traceback (most recent call last):
File "C:\Program Files\Python310\lib\site-packages\anyio\streams\tls.py", line 130, in _call_sslobject_method
result = func(*args)
File "C:\Program Files\Python310\lib\ssl.py", line 974, in do_handshake
self._sslobj.do_handshake()
ssl.SSLSyscallError: Some I/O error occurred (_ssl.c:997)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Program Files\Python310\lib\site-packages\httpcore_exceptions.py", line 10, in map_exceptions
yield
File "C:\Program Files\Python310\lib\site-packages\httpcore\backends\asyncio.py", line 76, in start_tls
raise exc
File "C:\Program Files\Python310\lib\site-packages\httpcore\backends\asyncio.py", line 67, in start_tls
ssl_stream = await anyio.streams.tls.TLSStream.wrap(
File "C:\Program Files\Python310\lib\site-packages\anyio\streams\tls.py", line 122, in wrap
await wrapper._call_sslobject_method(ssl_object.do_handshake)
File "C:\Program Files\Python310\lib\site-packages\anyio\streams\tls.py", line 151, in _call_sslobject_method
raise BrokenResourceError from exc
anyio.BrokenResourceError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Program Files\Python310\lib\site-packages\httpx_transports\default.py", line 60, in map_httpcore_exceptions
yield
File "C:\Program Files\Python310\lib\site-packages\httpx_transports\default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "C:\Program Files\Python310\lib\site-packages\httpcore_async\connection_pool.py", line 253, in handle_async_request
raise exc
File "C:\Program Files\Python310\lib\site-packages\httpcore_async\connection_pool.py", line 237, in handle_async_request
response = await connection.handle_async_request(request)
File "C:\Program Files\Python310\lib\site-packages\httpcore_async\http_proxy.py", line 258, in handle_async_request
connect_response = await self._connection.handle_async_request(
File "C:\Program Files\Python310\lib\site-packages\httpcore_async\connection.py", line 86, in handle_async_request
raise exc
File "C:\Program Files\Python310\lib\site-packages\httpcore_async\connection.py", line 63, in handle_async_request
stream = await self._connect(request)
File "C:\Program Files\Python310\lib\site-packages\httpcore_async\connection.py", line 150, in _connect
stream = await stream.start_tls(**kwargs)
File "C:\Program Files\Python310\lib\site-packages\httpcore\backends\asyncio.py", line 64, in start_tls
with map_exceptions(exc_map):
File "C:\Program Files\Python310\lib\contextlib.py", line 153, in exit
self.gen.throw(typ, value, traceback)
File "C:\Program Files\Python310\lib\site-packages\httpcore_exceptions.py", line 14, in map_exceptions
raise to_exc(exc)
httpcore.ConnectError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Program Files\Python310\lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Program Files\Python310\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "C:\Program Files\Python310\Scripts\bilix.exe_main.py", line 7, in
File "C:\Program Files\Python310\lib\site-packages\click\core.py", line 1130, in call
return self.main(*args, **kwargs)
File "C:\Program Files\Python310\lib\site-packages\click\core.py", line 1055, in main
rv = self.invoke(ctx)
File "C:\Program Files\Python310\lib\site-packages\click\core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Program Files\Python310\lib\site-packages\click\core.py", line 760, in invoke
return _callback(*args, **kwargs)
File "C:\Program Files\Python310\lib\site-packages\bilix_main.py", line 322, in main
loop.run_until_complete(cor)
File "C:\Program Files\Python310\lib\asyncio\base_events.py", line 641, in run_until_complete
return future.result()
File "C:\Program Files\Python310\lib\site-packages\bilix\download\downloader_bilibili.py", line 387, in get_video
video_info = await api.get_video_info(self.client, url)
File "C:\Program Files\Python310\lib\site-packages\bilix\api\bilibili.py", line 173, in get_video_info
res = await req_retry(client, url, follow_redirects=True)
File "C:\Program Files\Python310\lib\site-packages\bilix\utils.py", line 46, in req_retry
raise pre_exc
File "C:\Program Files\Python310\lib\site-packages\bilix\utils.py", line 28, in req_retry
res = await client.request(method, url, follow_redirects=follow_redirects, **kwargs)
File "C:\Program Files\Python310\lib\site-packages\httpx_client.py", line 1533, in request
return await self.send(request, auth=auth, follow_redirects=follow_redirects)
File "C:\Program Files\Python310\lib\site-packages\httpx_client.py", line 1620, in send
response = await self._send_handling_auth(
File "C:\Program Files\Python310\lib\site-packages\httpx_client.py", line 1648, in _send_handling_auth
response = await self._send_handling_redirects(
File "C:\Program Files\Python310\lib\site-packages\httpx_client.py", line 1685, in _send_handling_redirects
response = await self._send_single_request(request)
File "C:\Program Files\Python310\lib\site-packages\httpx_client.py", line 1722, in _send_single_request
response = await transport.handle_async_request(request)
File "C:\Program Files\Python310\lib\site-packages\httpx_transports\default.py", line 352, in handle_async_request
with map_httpcore_exceptions():
File "C:\Program Files\Python310\lib\contextlib.py", line 153, in exit
self.gen.throw(typ, value, traceback)
File "C:\Program Files\Python310\lib\site-packages\httpx_transports\default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.ConnectError

经过我测试是可以正常下载的。该错误为网络连接失败，再检查一下代理设置吧

对于这个问题不能很好的帮你测试，因为我在hk服务器上没有装代理，使用的也不是win和clash。在hk服务器上直接下载是可以的

经过我测试是可以正常下载的。该错误为网络连接失败，再检查一下代理设置吧

使用的是Clash for Windows全局代理，两个机场的HK节点均有此提示

换个软件开全局试试吧。比如v2rayn。


crash in 1.19.3

Description: Initializing game
java.lang.RuntimeException: Could not execute entrypoint stage 'main' due to errors, provided by 'brb'!
	at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.lambda$invoke0$0(EntrypointUtils.java:51)
	at net.fabricmc.loader.impl.util.ExceptionUtil.gatherExceptions(ExceptionUtil.java:33)
	at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:49)
	at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.invoke(EntrypointUtils.java:35)
	at net.fabricmc.loader.impl.game.minecraft.Hooks.startClient(Hooks.java:52)
	at net.minecraft.class_310.<init>(class_310.java:465)
	at net.minecraft.client.main.Main.method_44604(Main.java:205)
	at net.minecraft.client.main.Main.main(Main.java:51)
	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:461)
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.prismlauncher.impl.OneSixLauncher.invokeMain(OneSixLauncher.java:104)
	at org.prismlauncher.impl.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:176)
	at org.prismlauncher.impl.OneSixLauncher.launch(OneSixLauncher.java:186)
	at org.prismlauncher.EntryPoint.listen(EntryPoint.java:144)
	at org.prismlauncher.EntryPoint.main(EntryPoint.java:74)
Caused by: java.lang.NoSuchFieldError: field_11143
	at marsh.town.brb.BrewingStand.Result.<init>(Result.java:23)
	at marsh.town.brb.Loaders.PotionLoader.init(PotionLoader.java:28)
	at marsh.town.brb.BetterRecipeBook.init(BetterRecipeBook.java:28)
	at marsh.town.brb.fabric.BetterRecipeBookFabric.onInitialize(BetterRecipeBookFabric.java:9)
	at net.fabricmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:47)
	... 17 more

can confirm, crashes on 1.19.3

every update I essentially have to rewrite the entire mod, since it mixins so much. I tried to get 1.19 to work but I gave up since the task was so daunting

It's best to take your time instead of having to dedicate yourself into mods heavily as it can cause burn out when updating alot.

Hello @mrshmllow, would love to see the mod for 1.19.3 as well 😊
It's really frustrating how Mojang wants to go the way now, with less or more bigger changes between minor versions...

Since there's a 1.19.3 version wouldn't it make sense to close this issue?

Thanks for the notify @Aces-and-Jacks.
Pleae upload the newest release on Modrinth @mrshmllow 😊

I couldn't, it was bugged out

@sternschnaube fixed

Thanks 😇

I don't mind! feel free to upstream anything or whatever but it's cool

fixed

Earlier I think I saw the different versions being there. Tho unless I'm wrong and it was all meant to be in one file which doesn't seem correct, I think it broke again

Works flawless on 1.19.3 for me.
I got the file from Curse.

Oh, yeah 1.19.3 on curseforge works great. Just on modrinth it's broken I think

I just used my launcher to find and select the mod from Modrinth and it listed only one available version for 1.19.3 - 1.7.0.

 I've been looking at the wrong link without realizing it. Sorry for the trouble


Please update from main line

Please pull latest changes from cheerio latest

I think it would be better to pull a stable version rather than master from cheerio. Would that solve your  problem?

Yes thank you sir that would be awesome!! And much smarter then my initial request, thank you!

@Noitidart 1.0.0-rc.2 is merged and released.

Thank you!!! Could you share the steps to take, so maybe I or others can
help make these updates.
On Wed, Sep 12, 2018 at 12:50 PM Ouyang Yadong<EMAIL_ADDRESS>wrote:

@Noitidart https://github.com/Noitidart 1.0.0-rc.2 is merged and
released https://www.npmjs.com/package/cheerio-without-node-native.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/oyyd/cheerio-without-node-native/issues/6#issuecomment-420775177,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGE8icEFEVyS_VIJzz7mjvPXZxNqP-OCks5uaWWYgaJpZM4WWSjC
.

This repo is mainly cheerio itself. Pick these commits and merge them into a forked cheerio repo or branches.


Multiset support

Sometime ago JOOQ introduced Multiset Operator, which is really nice way to deal with associations - https://blog.jooq.org/jooq-3-15s-new-multiset-operator-will-change-how-you-think-about-sql. In short, it allows to fetch associated data with main entity (as nested collections) in one request  and solves problem of de-dupication with normal joins.
Any chance we will get something similar in this great library?

Hi @apawelec. Multiset operator seems like an interested idea. :eyes:


[YUNIKORN-2540] Deduplicate for the constants in pkg/cache/context_test.go

What is this PR for?
Constants are duplicated in the pkg/cache/context_test.go
Move to a central point of defining the constants for the test at the top of the file.
The related constant variables as below:
const (
Host1 = "host0001"
Host2 = "host0002"

appID1       = "app00001"
appID2       = "app00002"
appID3       = "app00003"
appID4       = "app00004"
appID5       = "app00005"
appIDUnknown = "app-none-exist"

uid1       = "uid_0001"
uid2       = "uid_0002"
uid3       = "uid_0003"
uid4       = "uid_0004"
uid5       = "uid_0005"
uidUnknown = "uid_0000"

pod1UID     = "task00001"
pod2UID     = "task00002"
taskUID1    = "task00001"
taskUID2    = "task00002"
taskUID3    = "task00003"
taskUID4    = "task00004"
taskUnknown = "non_existing_taskID"

podName1     = "pod1"
podName2     = "pod2"
podName3     = "pod3"
podName4     = "pod4"
podNamespace = "yk"

nodeName1    = "node1"
nodeName2    = "node2"
fakeNodeName = "fake-node"

queueNameA       = "root.a"
queueNameB       = "root.b"
queueNameC       = "root.c"
queueNameUnknown = "root.other"

annoAppID1 = "yunikorn-test-00001"
annoAppID2 = "yunikorn-test-00002"
annoAppID3 = "yunikorn-test-00003"
annoAppID4 = "yunikorn-test-00004"
annoAppID5 = "yunikorn-test-00005"

APIVersion1 = "v1"
testUser    = "test-user"

)
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2540
How should this be tested?
It should pass all test cases.
Screenshots (if appropriate)

Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

I made a e2e test, script as : "./scripts/run-e2e-tests.sh -a test -n yktest -v kindest/node:v1.28.0" or "./scripts/run-e2e-tests.sh -a test -n yktest -v kindest/node:v1.30.0", both failed with preemption.

@SophieTech88 please rebase your branch with master changes.

Actually never mind, I did myself so we can have a green build.

Actually never mind, I did myself so we can have a green build.

Many thanks for your help.


Epic: API CRUD Commands

API Create, Read, Update, and Delete Commands
User Stories
List the user stories that are associated with this epic.

[ ] As a front-end dev, I want perform CRUD on the USER table, so that I can manage the USER table.
[ ] As a front-end dev, I want perform CRUD on the OFFICER table, so that I can manage the OFFICER table.
[ ] As a front-end dev, I want perform CRUD on the OFFICER POSITION table, so that I can manage the OFFICER POSITION table.
[ ] As a front-end dev, I want perform CRUD on the SCHEDULE table, so that I can manage the SCHEDULE table.
[ ] As a front-end dev, I want perform CRUD on the MENTOR table, so that I can manage the MENTOR table.
[ ] As a front-end dev, I want perform CRUD on the COURSE table, so that I can manage the COURSE table.
[ ] As a front-end dev, I want perform CRUD on the COURSE TAKEN table, so that I can manage the COURSE TAKEN table.
[ ] As a front-end dev, I want perform CRUD on the SKILL table, so that I can manage the SKILL table.
[ ] As a front-end dev, I want perform CRUD on the MENTOR SKILL table, so that I can manage the MENTOR SKILL table.

These will be adjusted following a meeting with the product owner to determine what features they do and don't want to be editable
Technical Requirements
List the technical requirements for this epic.

[ ]Schema complete

Design Considerations
List the design considerations for this epic.

[ ] What tables need all 4 functions
[ ] What tables will only need some functionality
[ ] What should be readable

Dependencies

[ ] Auth to determine who can access the API

[ ] [Epic 1]

[ ] [Epic 2]

[ ] [Epic 3]

Design Documents
List the design documents associated with this epic.

[ ] [Document 1]
[ ] [Document 2]
[ ] [Document 3]


Feat: change groupID to id & add onClick callback in legend

closes : https://github.com/zakodium/react-plot/issues/279
closes : https://github.com/zakodium/react-plot/issues/280

Not sure how to test. Did you change as asked in the issue the following example that contains 2 series ? https://deploy-preview-288--react-plot.netlify.app/?path=/story/api-legend--with-two-series because this file does not seem to have change in thie PR.
I think the call back could have 2 parameters: id of the series + event. The goal is to know on which series in the legend you clicked and to be able to change something. In issue #280 the goal is to highlight a specific series (we have 2 series and we can toggle the selection of them).

Here is an example of the kind of functionality we need to achieve.

Because the legend use the style of the series it should rather be easy at this level. By changing the style of the series the style of the legend will change at the same time.
If you prefer you can create a new example with 5 lines series and more funny style modifications when selected like in the animated gif example.

To highlight selected Series you could user stroke-width and also this SVG property: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/stroke-dasharray

WithTwoSeries story updated

The first legend storybook crash

The functionality is ok but what is missing is the highlight in the legend. The style of the series is the legend is expected to be the same as the style of the series so when you change the thickness of the line it should be reflected in the legend and this is not the case.

@wadjih-bencheikh18 The current version still does not apply the style in the legend. The goal is not that the text in the legend becomes bold but only that the representation of the series takes the same style as the series.
Currently the redline or blue line that is just in front of the legend does not change its width even when selected

I would expect because they use the same styling options as the series that they are updated automatically.

the representation of the series takes the same style as the series

i did't know , i though we just need a simple representation that we can change each legend style using id
no problem


Windspeed and Windspeed Gust bad values in Weather Underground

I'm pretty sure that the plugin is somewhat reporting bad wind speed / gusts in Weather Underground. For example, I have today a max gust of 35 Km/h and plugin says, in Eve App, 104Km/h. Has anyone noticed this issue?

Already reported and being worked on here: Issue #296

Yes, duplicate of 296.
Closing as a duplicate


Template team feedback #35867

name: Backport PR to branch
on:
issue_comment:
types: [created]
schedule:
# once a day at 13:00 UTC to cleanup old runs
- cron: '0 13 * * *'
permissions:
contents: write
issues: write
pull-requests: write
actions: write
jobs:
backport:
uses: dotnet/arcade/.github/workflows/backport-base.yml@main

@bnhassin commented on #258 https://github.com/devcontainers/spec/issues/258

If you have a spec-specific request or bug, please feel free to file a new issue. Thank you!


Invalid query parameter "provider" in FindServicePlanByDescription

Command
The functions "FindServicePlanByDescription" and "FindServiceOfferingByLabelAndProvider" generate a query string in the following form (example for the application-logs service)
curl -X GET 'https://<cf api>/v2/services?inline-relations-depth=1&q=label%3application-logs%3Bprovider%3A' \
  -H 'authorization: <your authorization token>

What occurred
Response:
{
    "description": "The query parameter is invalid: provider",
    "error_code": "CF-BadQueryParameter",
    "code": 10005
}

What you expected to occur
Interestingly, when submitting the query string without the url escapes, e.g.
curl -X GET 'https://<cf api>/v2/services?inline-relations-depth=1&q=label:application-logs;provider:' \
  -H 'authorization: <your authorization token>

Then I get a valid response.
However, generally in newer versions of the CF API for /v2/services, the "provider" is indeed an invalid filter parameter and should be removed:
https://apidocs.cloudfoundry.org/280/services/list_all_services.html
CLI Version
6.33.0+a345ea34d.2017-11-20
CC API Endpoint Version
2.99.0
CF Trace
This is actually a terraform trace; the cloud foundry provider uses the function FindServicePlanByDescription which results in the query:
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: REQUEST: [2017-11-29T22:45:26+01:00]
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: GET /v2/services?inline-relations-depth=1&q=label%3Axsuaa%3Bprovider%3A HTTP/1.1
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Host: [removed]
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Accept: application/json
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Authorization: [PRIVATE DATA HIDDEN]
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Connection: close
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Content-Type: application/json
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: User-Agent: go-cli 0.0.0-unknown-version / linux
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry:
2017-11-29T22:45:26.137+0100 [DEBUG] plugin.terraform-provider-cloudfoundry:
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: 2017/11/29 22:45:26
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: RESPONSE: [2017-11-29T22:45:26+01:00]
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: HTTP/1.1 400 Bad Request
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Connection: close
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Content-Length: 121
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Content-Type: application/json;charset=utf-8
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Date: Wed, 29 Nov 2017 21:45:28 GMT
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: Server: nginx
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: X-Content-Type-Options: nosniff
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: X-Ratelimit-Limit: 80000
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: X-Ratelimit-Remaining: 78707
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: X-Ratelimit-Reset:<PHONE_NUMBER>
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: X-Vcap-Request-Id: 45b1ac88-960a-46c7-4b3d-9c986eeb097a::69a4a575-0766-4b56-8075-a6a1a16332ed
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry:
2017-11-29T22:45:26.421+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: {
2017-11-29T22:45:26.422+0100 [DEBUG] plugin.terraform-provider-cloudfoundry:   "description": "The query parameter is invalid: provider",
2017-11-29T22:45:26.422+0100 [DEBUG] plugin.terraform-provider-cloudfoundry:   "error_code": "CF-BadQueryParameter",
2017-11-29T22:45:26.422+0100 [DEBUG] plugin.terraform-provider-cloudfoundry:   "code": 10005
2017-11-29T22:45:26.422+0100 [DEBUG] plugin.terraform-provider-cloudfoundry: }
Platform & Shell Details
Running this on Ubuntu 16.04 64-bit using the 0.10 release of terraform cloud foundry provider which uses the CF CLI libraries:
https://github.com/orange-cloudfoundry/terraform-provider-cloudfoundry/releases/tag/v0.10.0
Any other relevant information

@zrob Our code appends this provider value and it seems to have been a documented parameter until http://apidocs.cloudfoundry.org/230/services/list_all_services.html.
CF v231 release notes do document a host of apidocs changes, although this one is not listed. Was this never supported?

Hi @chrismathias
Those APIs are used by cf migrate-service-instances, which is only supported up to CF API version 2.46.0. CC versions after that removed the provider parameter.
When you run this command on a recent CF release, you'll get a message saying so:
D:\Users\koperd\Downloads\bin\panic>cf migrate-service-instances a b c d e
FAILED
migrate-service-instances only works up to CF API version 2.46.0. Your target is 2.99.0.

We don't publish our internal APIs for public use, so if you use a project that depends on it, please file an issue there.
Regards,
Dies Koper
CF CLI PM

Hi @dkoper ,
Thanks for taking the time to investigate. I will open an issue for the cloud foundry terraform project which uses these functions. https://github.com/orange-cloudfoundry/terraform-provider-cloudfoundry
Thanks again and best regards,
Christian

Hi @dkoper ,
Thanks again for taking the time to look at this issue.
Best regards,
Christian


Public cats.parse.Parsers?

Should parsers be public? We're (potentially) able to replace parboiled2 without breaking binary compatibility because all the parsers were private[http4s].  But unlike our parboiled2 fork, we're not shading cats-parse.  If we're not shading the dependency, is there any reason to encapsulate the implementation?

This is more interestingly discussed in #4733.


Fix the path issue in make_apk.py

fix the path issue in Crosswalk Lite

@halton @shawngao5 @lincsoon , please help review, thanks!

@d0ngjun, in git log: fix -> Fix. Please describe in detail, I think you have xwalk bug number related.

LGTM, will merge.


Is cortx-motr-tests-ut-*.rpm needed?

I am following the readme to install Hare. The scripts/m0 make rpms will generate 5 rpms inside ~/rpmbuild/RPMS/x86_64/. One of the rpm is cortx-motr-tests-ut-2.0.0-*.el7.x86_64.rpm which can't be installed. When we run sudo rpm -ivh ~/rpmbuild/RPMS/x86_64/cortx-hare-*.rpm, it will generate this error
error: Failed dependencies:
	cortx-motr conflicts with cortx-motr-tests-ut-2.0.0-1_gite28e4d3_3.10.0_1127.19.1.el7.x86_64

Which in turn will prevent the installation of the other 4 RPMs.
So, what is the purpose of this cortx-motr-tests-ut-2.0.0-*.el7.x86_64.rpm and can we remove it from the ~/rpmbuild/RPMS/x86_64/ so that the other rpm installation can run without error?
Thanks

@pavankrishnat pls make necessary changes in README.

Yes @daniarherikurniawan we can remove cortx-motr-tests-ut-2.0.0-*.el7.x86_64.rpm and install other rpms

@vaibhavparatwar @pavankrishnat , I made this PR https://github.com/Seagate/cortx-hare/pull/1672 to address this. Feel free to close the PR if you have another solution. Thanks!

@daniarherikurniawan lets use this PR https://github.com/Seagate/cortx-hare/pull/1681 for this issue as we do not want to remove some files which are created by make files. Here we are handling using the command and installing rpms other than cortx-motr-test *.rpms.

@vaibhavparatwar  Okay, that would work! :)
I will close another PR.

Closing this updated README with the link to motr QSG for building & installing Motr rpms


Change maximum Send/ Receive value to 262,800,000 Beams

Description
Change maximum value to 262,800,000 Beams in the BEAM fields in the Send and Receive screens.
Please make sure to take into account the Fee value, e.g. if the fee is 10 groths, than the maximum amount to enter will be reduced accordingly.

Also user can't input fee, if send value is maximum.
Example: set fee to zero, amount set to maximum.
Expected result: user can't input fee

in the line transaction amount it is possible to enter 9 zeros to the decimal point.

Please implement the same logic of entering the amount on "receive" and "send" screens as on the desktop wallet.

сhecked


Upgrade to <IP_ADDRESS> from <IP_ADDRESS>7

Any issue should pay attation ?
or Just use nuget install will be ok?
for help.

Well, the biggest change is NHibernate 4.x.  For Fluent - you can see release notes for each release, we don't roll out very often

One breaking change is that prefixes now always cascade to components #298
There doesn't seem to be a way to configure it NOT to use the prefixes on component fields so you may end up having to rename columns.

Closing this, feel free to reopen if you have more questions


source_id registration of GCOAST-AHOIB1-1

label
GCOAST-AHOIB1-1
label_extended
Regional coupled atmosphere-hydrological discharge-ocean-sea ice-biogeochemical model based on cosmo-clm v6.0, HD v5.2, NEMO v3.6 and ECOSMO for the North and Baltic Sea
source_id
GCOAST-AHOIB1-1
source_type
AORCM
release_year
2024
activity_participation
DD
institution_id
CLMcom-Hereon
further_info_url

What license do you choose?
CC BY 4.0

Thank you for the input, Ha. Shall we capitalize COSMO-CLM in the extended label? see also #197
Also, we should add some further_info_url to have some details of this model. If there's no URL of this very specific configuration, we could use in the meantime the same as in #198. What do you think? In such a case, you can freely use this thread to explain the differences with the other versions (#198, #197), or add links to the components.
Which version of ECOSMO are you using?

Great! Thanks a lot, Jesus! The ECOSMO model doesn't have a version number.

/register
OK. Let's go ahead, then


use OBJ/MTL instead of Blender file for 🏜 Desert Terrain environment (fixes issue #178)

Fix #178

Use OBJ/MTL files generated from Blender model source file
Point the Unity scene to use the new models, applying the "Red" material
Blender is no longer required to be installed on the system
Remove old temp files (*.blend1)

thanks, I'll update this tomorrow. (@caseyyee if you have a minute, you might be able to eyeball the changes needed.)

@caseyyee: I updated the files for the Desert Environment models (OBJ+MTL+Blender files) from the ones you sent me.
in both VR and non-VR, notice how dark the lighting/material now appears:

I'm running Unity version 2017.3.1f1; I know the project settings are set to 2017.3.0f3, and I believe that's the version you're using too. I doubt there was any breaking change in a patch-version update, but just figured I'd mention it.

@caseyyee okay, per our Slack conversation, I just fixed this by unchecking the Static property, and the lighting looks proper again now.

@cvan looks good!  r+ thanks for this!


Adding more tags to the system

Hello. Has anyone fully solved the issue of adding multiple tags? I've looked into discussions among the question titles here, but I couldn't find a precise and clear solution. Has anyone been able to use this library for multiple anchors and multiple tags for example 4 anchors and 4 tags or more? Or perhaps, does anyone know of a different library suitable for this situation? Your recommendations are highly valuable.

Anthony,
My last experience with this lib was 7ish years ago. I couldn't get it to
work then. That is why I moved to some other lib and esp32 type modules.
I have not been in iot scene for good 3 years now.
I'm sorry I can't be of more help.
On Sun, Apr 28, 2024, 10:16 anthony211212 @.***> wrote:

Hello. Has anyone fully solved the issue of adding multiple tags? I've
looked into discussions among the question titles here, but I couldn't find
a precise and clear solution. Has anyone been able to use this library for
multiple anchors and multiple tags for example 4 anchors and 4 tags or
more? Or perhaps, does anyone know of a different library suitable for this
situation? Your recommendations are highly valuable.
—
Reply to this email directly, view it on GitHub
https://github.com/thotro/arduino-dw1000/issues/343, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGHHXNLSTQWU3P6ZDHME6LY7UADVAVCNFSM6AAAAABG5AVFWWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3DONJZGQ2DCMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hello. I know some modules ESP32 UWB(Ultra Wideband) and ESP32 UWB DW3000(Ultra Wideband). Do you know any library for them to use multiple tags and anchors ?

Bonjour,
Je travail actuellement sur la même problématique. Avez-vous trouvez une solution?
Ou même une façon de limiter le nombres de balises qui ce connectes de façon "propre"?

Hello. Not yet. Do you have any idea?

Update for anyone who encounter this problem
You can find an updated version that fixes this and other problems here: https://github.com/jremington/UWB-Indoor-Localization_Arduino/tree/main/DW1000_library_pizzo00

@pizzo00 Which algorithm did you use to find the tag's position, and what was your error value?

The trilateration algorithm is beyond the scope of the library but I personally use the @jremington implementation of this paper with a RMSE of 2m on a distance of 30m from the anchors

@pizzo00 Merci beaucoup pour votre travail. Cependant, je ne parviens pas a utiliser votre bibliothèque, La compilation est OK avec le Biblio d'origine, mais j'ai de nombreuse erreur avec la votre. Devons-nous modifier des éléments dans notre script?

@scal68 Now it is sufficient to call the function DW1000Ranging.init, with the type, the short address, a mac address, a flag for high_power, the transmission mode, and the usual parameters.
My code looks like this:
static constexpr byte MY_MODE[] = {DW1000.TRX_RATE_6800KBPS, DW1000.TX_PULSE_FREQ_16MHZ, DW1000.TX_PREAMBLE_LEN_64};

void setup()
{
    Serial.begin(115200);
    delay(1000);

    uint16_t shortMacAddress = 118;  //"76:00";
    char *wifiMacAddress = "00:00:00:AA:AA:AA"; //I get it from the esp board through WiFi.macAddress();

    // init the configuration
    SPI.begin(SPI_SCK, SPI_MISO, SPI_MOSI);
#if C_TAG
    DW1000Ranging.init(BoardType::TAG, shortMacAddress, wifiMacAddress, true, MY_MODE, PIN_RST, PIN_SS, PIN_IRQ);
#elif C_ANCHOR
    DW1000Ranging.init(BoardType::ANCHOR, shortMacAddress, wifiMacAddress, true, MY_MODE, PIN_RST, PIN_SS, PIN_IRQ);
#endif
}


TAVOSS-TR:Secondmate

Version of the project
NA
Tech Stack
DevOps [DO]
Project details
An open-source, mini imitation of GitHub Copilot for Emacs
Languages used
GO
Domain
Technology
Industry
All
Open Source Project type
Others
Repo URL
https://github.com/samrawal/emacs-secondmate
Webpage
No response
License
Apache-2.0
Other license
No response
Reason , why we must track this project.
The tool can be leveraged to play around with scaled-down capabilities as that of GitHub co-pilot to gain expertise

This project is accepted for tracking hence closing this issue with status as Tracked


docs(migration): operator reference Replace _ with - in directory name

Add aliases to each file
also added description to each file so section landing page looks nicer

abandoning


[SQL] Removes FileFormat.prepareRead

What changes were proposed in this pull request?
Interface method FileFormat.prepareRead() was added in #12088 to handle a special case in the LibSVM data source.
However, semantics of this interface method isn't intuitive: it returns a modified version of the data source options map. Considering that the LibSVM case can be easily handled using schema metadata inside inferSchema, we can remove this interface method to keep the FileFormat interface clean.
How was this patch tested?
Existing tests.

JIRA is down. Will create a ticket for it later.
cc @rxin @cloud-fan

Test build #60618 has started for PR 13698 at commit 6314635.

Test build #60618 has finished for PR 13698 at commit 6314635.

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

Merged build finished. Test PASSed.

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

LGTM

Test build #60635 has started for PR 13698 at commit eeb8d52.

Test build #60635 has finished for PR 13698 at commit eeb8d52.

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

Merged build finished. Test PASSed.

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

thanks, merging to master/2.0!


Implemented CreateDisks with GCE Go client Disk structs.

Codecov Report

Merging #66 into master will decrease coverage by 0.14%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master      #66      +/-   ##
==========================================
- Coverage   77.85%   77.71%   -0.15%
==========================================
  Files          21       21
  Lines        1513     1503      -10
==========================================
- Hits         1178     1168      -10
- Misses        248      250       +2
+ Partials       87       85       -2

Impacted Files
Coverage Δ

daisy/workflow/step_create_instances.go
79.85% <100%> (-0.57%)
:arrow_down:

daisy/workflow/step_create_images.go
92.06% <100%> (-0.25%)
:arrow_down:

daisy/workflow/common.go
92.2% <100%> (+0.65%)
:arrow_up:

daisy/workflow/step_create_disks.go
80% <72.72%> (-10%)
:arrow_down:

daisy/compute/compute.go
74.74% <84.61%> (+1.84%)
:arrow_up:

Continue to review full report at Codecov.

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


combo breaks on replay when it's not supposed to

video proof: https://youtu.be/ETbRa1GbpqE
*video muted because of copyright

yep im having the same issue, tried reinstalling but the combo still breaks and the acc/misscount is always completely off.
dual core i5-5300u
intel hd 5500
8gb ram


Define environment conda file with minimal package list

The current environment.yml file that defines the Conda environment contains many packages not useful for the project.
It would better to have a smaller environment.yml file with only needed packages for the project.
@KarinDuong would you mind taking a look at it?

@pierrepo It's done, this version suitable for you?

Done :)

Thanks. I will now create a pull request to slightly improve the file.
I'll show you how to close automatically this issue from the PR.


[Style] Contact form h2 tag color and shadow effect

What's the style idea?
I checked the contact form where I found there isn't looks good contact form h2 tag color.
So please assign me this task under gssoc'24.
I'll fix this issue.
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

Provide the screenshot before and after your changes @sakeel-103


最新消息， 我被拒了，直接拒绝，新版本也不行了？

Guideline 2.5.2 - Performance
Your app, extension, or linked framework appears to contain code designed explicitly with the capability to change your app’s behavior or functionality after App Review approval, which is not in compliance with App Store Review Guideline 2.5.2 and section 3.3.2 of the Apple Developer Program License Agreement.
This code, combined with a remote resource, can facilitate significant changes to your app’s behavior compared to when it was initially reviewed for the App Store. While you may not be using this functionality currently, it has the potential to load private frameworks, private methods, and enable future feature changes. This includes any code which passes arbitrary parameters to dynamic methods such as dlopen(), dlsym(), respondsToSelector:, performSelector:, method_exchangeImplementations(), and running remote scripts in order to change app behavior and/or call SPI, based on the contents of the downloaded script. Even if the remote resource is not intentionally malicious, it could easily be hijacked via a Man In The Middle (MiTM) attack, which can pose a serious security vulnerability to users of your app.

今天早晨刚刚被拒，也是楼主的原因

me too!

新版本是做了类名和方法名混淆的？

改了类名都不行了，也被拒

我也是这个原因别拒

日了🐶

Apple应该是更新了检测机制，混淆方法失效了。
这次从In Review到Reject只有几秒，应该是自动化手段升级了。

@gin7758258   我把JSPatch 去了，依旧被拒,原因还是这个   只是用了最新版的Bugly,郁闷了

@ahhsxp  bugly也是用的JSPatch，http://bugly.qq.com/bbs/forum.php?mod=viewthread&tid=2871

@wesleydotyang   只是使用了Bugly的异常上报，没有使用热修复   而且是使用了最新版

新版的Bugly不是说移除了JSPatch了吗？

@ningman  恩！ 里面没有了  然后还是被拒   一脸懵逼

@ahhsxp  看来Bugly已被加入黑名单。。。

是不是误伤啊，bugly 不集成jspatch的版本不应该被拒啊

我提交的App也被拒了，原因：
Guideline 2.5.2 - Performance
Your app, extension, or linked framework appears to contain code designed explicitly with the capability to change your app’s behavior or functionality after App Review approval, which is not in compliance with App Store Review Guideline 2.5.2 and section 3.3.2 of the Apple Developer Program License Agreement.
This code, combined with a remote resource, can facilitate significant changes to your app’s behavior compared to when it was initially reviewed for the App Store. While you may not be using this functionality currently, it has the potential to load private frameworks, private methods, and enable future feature changes. This includes any code which passes arbitrary parameters to dynamic methods such as dlopen(), dlsym(), respondsToSelector:, performSelector:, method_exchangeImplementations(), and running remote scripts in order to change app behavior and/or call SPI, based on the contents of the downloaded script. Even if the remote resource is not intentionally malicious, it could easily be hijacked via a Man In The Middle (MiTM) attack, which can pose a serious security vulnerability to users of your app.
Next Steps
To resolve this issue, please perform an in-depth review of your app and remove any code, frameworks, or SDKs that fall in line with the functionality described above and resubmit your app’s binary for review.
引入的是JSPatch 1.7，上一个App更新版本也引入了，审核通过，这一次更新版本就被拒了。。。。

早上看邮件同样被拒~悲剧呀 有没有兄弟有解决方案

应该是不行了，今天早上直接rejected。

请使用 SDK 1.7.1 版本：https://jspatch.com/Index/sdk

5.20号提交的还是被拒了。会有新版本更新吗

有人试过1.7.2了吗？

我被拒了，但是没有使用热更新啊


Unable to pull latest stacks from community staging deployment

Which area this feature is related to?
/kind bug

Which area this bug is related to?

/area registry
What versions of software are you using?
Go project
Operating System and version: N/A
Go Pkg Version: 1.17
Bug Summary
Describe the bug:

While using odo version 3 against our community registry staging deployment, there is an error when trying to fetch the latest version of the stack. The error thrown appears to be a not found error type when the client attempts to fetch content descriptors or the manifest from the OCI registry.
This error happens at inconsistent attempts and seems to successfully fetch the stack at inconsistent number of tries. After trying on other deployments, this seems to be isolated to the community staging deployment.
To Reproduce:

Run the following commands with odo version 3:
odo preference add registry stage https://registry.stage.devfile.io

go stack
odo init --name aname --devfile go --devfile-version latest --devfile-registry stage

python stack
odo init --name aname --devfile python --devfile-version latest --devfile-registry stage

java-springboot stack
odo init --name aname --devfile java-springboot --devfile-version latest --devfile-registry stage

Expected behavior

The output of any of these odo init commands should be something like the following:
  __
 /  \__     Initializing a new component
 \__/  \
 /  \__/    odo version: v3.8.0
 \__/

 ✓  Downloading devfile "go:latest" from registry "stage" [543ms]

Your new component 'aname' is ready in the current directory.
To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
Changes will be directly reflected on the cluster.
To deploy your component to a cluster use "odo deploy".

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Manifest not found error output
  __
 /  \__     Initializing a new component
 \__/  \
 /  \__/    odo version: v3.8.0
 \__/

 ✗  Downloading devfile "go:latest" from registry "stage" [296ms]
 ✗  unable to download devfile: failed to pull stack go:latest from registry.stage.devfile.io/devfile-catalog/go:2.0.0 with allowed media types [application/vnd.devfileio.devfile.layer.v1 image/png image/svg+xml application/vnd.devfileio.vsx.layer.v1.tar application/x-tar]: failed to copy: httpReadSeeker: failed open: content at https://registry.stage.devfile.io/v2/devfile-catalog/go/manifests/sha256:c15d231dc4ce9a82f787f91390a066f1edfcc611c016fd8748dc65a29287ba3b not found: not found
the command failed, the devfile has been removed from current directory

Content descriptor error output
  __
 /  \__     Initializing a new component
 \__/  \
 /  \__/    odo version: v3.8.0
 \__/

 ✗  Downloading devfile "go:latest" from registry "stage" [416ms]
 ✗  unable to download devfile: failed to pull stack go:latest from registry.stage.devfile.io/devfile-catalog/go:2.0.0 with allowed media types [application/vnd.devfileio.devfile.layer.v1 image/png image/svg+xml application/vnd.devfileio.vsx.layer.v1.tar application/x-tar]: failed to copy: httpReadSeeker: failed open: could not fetch content descriptor sha256:013466fc4eed3c375821002e5e7e80939aa848b7fb86d5b6b4b131422b29b146 (application/x-tar) from remote: not found
the command failed, the devfile has been removed from current directory

Server Log
[GIN] 2023/03/24 - 17:41:47 | 200 | 1.349969ms | x.x.x.x | GET "/v2index"
[GIN] 2023/03/24 - 17:41:47 | 200 | 2.465988ms | x.x.x.x | HEAD "/v2/devfile-catalog/go/manifests/2.0.0"

Additional context

Any workaround?

No official workarounds have been found, however since the errors do not happen every time it can be retried for a successful fetch.
Suggestion on how to fix the bug

Not discovered at this time.

Devfile registry server logs do not show any error has occurred, however does miss request logs when client errors which shows when client does a successful fetch of the stack.

After further investigation I found that the image tag for the OCI registry component used on our staging deployment was a year outdated. This image would lack the sufficient security permissions needed for the required setup security context definitions: https://github.com/devfile/registry/blob/47eee922b60b5a90e0fbcbf9966300c990127de4/.ci/deploy/devfile-registry.yaml#L142
Since updating this image tag we have noticed no more occurrences of these errors.

Updating the image tag has been confirmed to resolve this issue, closing now.


Update yargs-unparser to v1.6.0

Description of the Change
Fixes Prototype Pollution vulnerability of lodash via yargs-unparser.
Applicable issues
closes #3965

Coverage remained the same at 92.432% when pulling bee3d955d5cd377498b7f3037f5bda82d9780122 on juergba/yargs-unparser into 8e6e747837444aca4341ab6cc03688bc8a2a5c6d on master.


Consider graph scale toggling: absolute vs. relative, or similar.

Closing because I believe this is rendered obsolete with the different way we constructed the charts in subsequent builds.


Convert projects on GH to forks

These projects are on GH and should become forks:

[x] cppcheck
[ ] meta-clang
[ ] meta-openembedded

@offa still a todo?

I think so, but really low prio.


bug: wrong voting power on offchain pending proposals

Voting power for all pending proposals are using the latest block.
This is the default behavior for onchain proposals, but not for offchain, which should use the proposal snapshot (set at the proposal creation time)

Will be a very quick fix after https://github.com/snapshot-labs/sx-monorepo/pull/938


S3: Crash in GetObjectCallable

I got crash stack as below:
#0  0x00007f6a8d86c1c0 in Aws::External::tinyxml2::StrPair::GetStr() ()
#1  0x00007f6a8d86d09c in Aws::External::tinyxml2::XMLNode::Value() const ()
#2  0x00007f6a8d8a6dd9 in Aws::Utils::Xml::XmlNode::GetName() const ()
#3  0x00007f6a8d883943 in Aws::Client::AWSXMLClient::BuildAWSError(std::shared_ptrAws::Http::HttpResponse const&) const ()
#4  0x00007f6a8d880f69 in Aws::Client::AWSClient::AttemptOneRequest(std::basic_string<char, std::char_traits, Aws::Allocator > const&, Aws::AmazonWebServiceRequest const&, Aws::Http::HttpMethod) const ()
<and more ...>
Last piece of trace looks like below:
[TRACE] 2016-12-20 09:16:45 CurlHttpClient [139718591420160] 16360 bytes written to response.
[TRACE] 2016-12-20 09:16:45 CurlHttpClient [139718591420160] 1048 bytes written to response.
[DEBUG] 2016-12-20 09:16:45 CurlHandleContainer [139718591420160] Releasing curl handle 0x7f12c0028560
[DEBUG] 2016-12-20 09:16:45 CurlHandleContainer [139718591420160] Notified waiting threads.
[DEBUG] 2016-12-20 09:16:45 AWSClient [139718591420160] Request returned error. Attempting to generate appropriate error codes from response
[TRACE] 2016-12-20 09:16:45 AWSClient [139718591420160] Error response is a Ã^KXÅ<9f>mpÉ<99>mi^XM0Ë^D^]É^D<99>l^L .
It seems the content of error response it strange which cause the crash.
For those not crash request, it looks like this:
[TRACE] 2016-12-20 09:16:45 CurlHttpClient [139718591420160] 1048 bytes written to response.
[DEBUG] 2016-12-20 09:16:45 CurlHandleContainer [139718591420160] Releasing curl handle 0x7f12c0028560
[DEBUG] 2016-12-20 09:16:45 CurlHandleContainer [139718591420160] Notified waiting threads.
[DEBUG] 2016-12-20 09:16:45 AWSClient [139718591420160] Request returned error. Attempting to generate appropriate error codes from response
[TRACE] 2016-12-20 09:16:45 AWSClient [139718591420160] Error response is
[WARN] 2016-12-20 09:16:45 AWSErrorMarshaller [139718591420160] Encountered Unknown AWSError
XML_ERROR_PARSING_TEXT
Unable to generate a proper httpResponse from the response stream.   Response code:<PHONE_NUMBER>:
[TRACE] 2016-12-20 09:16:45 AWSClient [139718591420160] Request was either successful, or we are now out of retries.
[TRACE] 2016-12-20 09:16:45 AWSClient [139718591420160] No content body, content-length headers

We'll need some more information to be able to possibly help with this.
What platform are you on?  Are you building from source or using a packaged version?  If building, what is your cmake command line?  How are you integrating the SDK with your application (cmake export file, etc...)?  How reproducible is the crash?  Have you tried debugging the crash (in particular what is in the httpResponse being parsed and what came across the wire for the response)?

I think the problem is with this code "HttpResponseCode::REQUEST_NOT_MADE". This is defined as "-1" and used in CurlHttpClient.cpp. But it's never processed specially. If I register "ContinueRequest" handler and cancel the request in the middle, and then "AWSXMLClient::BuildAWSError" will be trying to parse some binary data as XML. That will cause high chance (but not always) for crash.

A quick fix can look like below:
_static bool DoesResponseGenerateError(const std::shared_ptr& response)
{
if (!response) return true;
int responseCode = static_cast<int>(response->GetResponseCode());
return response == nullptr || (responseCode < SUCCESS_RESPONSE_MIN **&& responseCode >0**) || responseCode > SUCCESS_RESPONSE_MAX;

}_

Fixed


Distorted member photos

The thumbnail photos in the list are sometimes distorted even if they're correct on the actual member page.
In the 104th senate, for instance:

Ah, yeah, this probably will probably impact any portrait member photo. Probably easier to crop the photos than fix the display.

Okay, I whipped up a shell script to quarantine the landscape photos. We lose 302 photos to this but I am confident the remaining photos should display fairly well. I am going to experiment with automatic smart cropping on the landscape and see how badly that mangles things.

I did a shell script to center-crop to 4:5 aspect ratio all of our landscape images. The effect generally looks good. I have deployed the cropped files to fix it.
There were 19 files that did not crop well.
Can someone who is not me download this zip file, manually crop the images inside to a 4:5 aspect ratio (100 width for every 125 height) as appropriate and then reupload them to vvd's /static/img/bios/ folder (you can use sftp) and do a commit? Then close this issue

I cropped the 15 photos referenced above and uploaded and committed.  There is one remaining real problem which is that 009662.jpg does not appear to contain an image of a person at all!    Also, while not strictly speaking a problem, I think 015427.jpg is Joe Kennedy.  I am sure we could find a better image of him that the one that I just cropped.

I updated to a better picture of J. P. Kennedy.   009662 (Daniel Verplanck of NY) has as is picture a picture of his house.  It from wikipedia,  I did a little searching for a better image of him, without success.   I am going to call this closed and we can ad 009662 to the short list of folks for whom we do not have images.

Thanks Jeff! If you notice any other photos that seem bad, feel free to keep adding to the manual folder as necessary!

Still present for some

I have a maintenance script in /usr/scripts/voteview_metadata/updateDB/imageAspectRatio/ called smartcrop-batch. Our ideal aspect ratio is 5:4 (1.25). The script scans for anything about 1.35 (too long) or below 1.15 (too wide) and uses facial recognition to crop to 5:4 as best as it can. So the absolute most that a remaining image will be squished or stretched is 8%.
Feel free to alter the parameters here if you want the tolerance to be a little lower, but we cause quality degradation by re-encoding a JPG so unless you think the aspect ratio is real bad I wouldn't.


update for finalization

@tarotis and @xrotwang, I have now flattened this repository to work as a simple collection of scripts with a make file and results. The library is now integrated into lingrex. Requirements must be adjusted, once lingrex is updated to the next version.

As time rushes and all was computed safely, I will now just release this as version 1.0.


Continue report screen

Description:

Linked issues:

Screenshots:

How to test:

Current status

LGTM. But, solve conflicts.
Also, i see React-native version is 0.62.2 when the MIT project is built in RN 0.61.5, wouldn't that make any trouble?

I can try fixing this today if I have time We should use the same one but not sure why updated

images asset missing, the same asset as the other PR

This is gonna b fixed on the other one


Reenable test_coordinatory.py tests

When working on #162 I was not able to get some of the tests to pass neither locally, nor on GitHub Actions. This was with the LLM, vectordb, graphdb and artemis running so I believe there is a problem with the test(s)
I skipped test_sequential_coordinator(), which will need reenabling

test_coordinator.py and test_tools.py both make use of llama3.1 (instead of Phi-3-mini-4k-instruct-q4.gguf). So we'll also need to install and start Ollama.

Using Groq might be a good option for these tests.


chore(main): release siyuan-plugin-publisher 1.19.1

:robot: A new release will be created
1.19.1 (2024-02-18)
Bug Fixes

#1035 代码块里面的文本不应该被错误转义 (8fc148f)
deps: bump @vueuse/core from 10.7.1 to 10.7.2 (30047db)
deps: bump actions/cache from 3 to 4 (c7591e3)
deps: bump element-plus from 2.4.4 to 2.5.5 (070501c)
deps: bump pnpm/action-setup from 2 to 3 (4a8c07a)
deps: bump siyuan from 0.9.1 to 0.9.3 (7a2d36a)
deps: bump vue from 3.4.5 to 3.4.19 (0c74d35)

Miscellaneous

deps-dev: bump @vitejs/plugin-vue from 5.0.2 to 5.0.4 (2994019)
deps-dev: bump @vitest/coverage-v8 from 1.1.3 to 1.2.2 (e41c57d)
deps-dev: bump vercel from 33.0.2 to 33.5.1 (8277d01)
deps-dev: bump vitest from 1.1.3 to 1.2.2 (3ba33bc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/terwer/siyuan-plugin-publisher/releases/tag/siyuan-plugin-publisher-v1.19.1 :sunflower:


Integration not showing

Hi Midstar. After installing your Heatmiser WiFi integration from HACS it doesn’t show in HA integrations. It worked fine on my old system but after reinstall to new pi this week it doesn’t show. I’ve cleared cache and full restart but nothing. Please help this was such a great integration before.

Hi
Unfortunately I have no idea why it don't work. Also, I'm sorry to inform you that I will not maintain the heatmiser_wifi_ha project anymore since I replaced my Heatmiser Thermostat with another system.
BR,
Joel

I have exactly the same issue, reset HA on a new Pi and can't get the plugin to work :(


⚠ Bofrost.at has degraded performance

In 13843bb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1500 ms

Resolved: Bofrost.at performance has improved in 1061c04 after 10 minutes.


Nvidia Tx2 is hard to use

hi, I have run the demo successfully on PC.
But when I temp to use it on Tx2, it nearly makes me collapse .
Opset 16 is required by LightGlue.onnx, but Tx2 can only  support onnxruntime 1.11.0, whose opset is till 15.
And torch on Tx2 requires python==3.6, which stop me from installing onnxruntime>1.12.0.
Have you got any idea?

Hi @demonove, happy to hear that LightGlue-ONNX is useful for you.
ONNX opset 16 is only required because of SuperPoint's grid sample operation. See https://github.com/fabio-sim/LightGlue-ONNX/issues/19 for more information. DISK-LightGlue supports opset 12+:

disk_opset12.onnx
disk_lightglue_opset12.onnx
disk_lightglue_end2end_opset12.onnx

I hope you find these models helpful!

Hi @fabio-sim, thanks for the models you've given.
I found another question!
When using export.py to turn a onnx mode, it will include sdpa.py which import torch.onnx._constant, torch.onnx._type_utils, torch.onnx.symbolic_helper. All these imports are all offered by torch 2.0, but Tx2 can only use torch 1.10.
Is there any way makes export.py support for torch 1.10?


Select default TM theme according the Apparence Theme

Today the TM default theme is everytime ligtht. When user changes the "Apparence Theme" to dark it should select the TM theme "dark".

@mickaelistria now we have 2 default themes "light" and "dark" which is choosen according the E4 Theme Appearance:

To do that, the theme extension point was improved with new attribute defaultForE4ThemeId:
<extension
         point="org.eclipse.textmate4e.ui.themes">
      <theme
            id="org.eclipse.textmate4e.ui.themes.SolarizedLight"
      		name="%Theme.SolarizedLight.name"
            path="./themes/Solarized-light.css"
            defaultForE4ThemeId="*" >
      </theme>
      <theme
            id="org.eclipse.textmate4e.ui.themes.Dark"
      		name="%Theme.Dark.name"
            path="./themes/Dark.css"
            defaultForE4ThemeId="org.eclipse.e4.ui.css.theme.e4_dark" >
      </theme>
   </extension>

The defaultForE4ThemeId is the default TM theme to apply when E4 Theme (Classic, Dark, etc) is selected. @mickaelistria what do you think about the name defaultForE4ThemeId, do you like it?

@mickaelistria what do you think about the name defaultForE4ThemeId, do you like it?

yes, I think it makes sense. However, I'd like to try a few more proposals:

workbenchTheme
eclipseTheme
applicationTheme
`targetWorkbenchTheme"

I like eclipseThemeId  what do you think @mickaelistria ?

+1