Phoenix For Cloudera - v4.7 Support

I have recently started using phoenix with hbase. Since it doesn't work out-of-the-box on CDH, this git repo has been very helpful.
I wanted to know if there is any recent work being done to make the latest phoenix version 4.7 compatible with CDH 5.5.2.
Thanks,
Amit.

Yes this is something I will be working on soon.

That's great.
I had a question - At a high level what are the code changes made to phoenix to make it work with cloudera? Given the way phoenix is installed (by copy pasting the jars on the hbase master and region servers) what triggered a need to modify phoenix especially since we don't operate phoenix separately.
Thanks!

There are several differences between Cloudera HBase and Apache HBase in the internal interfaces upon which Phoenix depends: coprocessor, scanner, and tracing APIs for example. The changes needed are largely simple fixups for slight differences, but these are still necessary for successful compilation.

Still waiting on the 4.7.0 release. Currently at RC6

I've run into a roadblock.
Phoenix 4.7 depends on Tephra, developed by Cask. Tephra is also not compatible with CDH HBase because of the changes Cloudera has made to various APIs. All of the transaction functionality is broken. Teprha needs a port to CDH first.
Caused by: java.lang.NoSuchMethodError: org.apache.hadoop.hbase.client.OperationWithAttributes.setAttribute(Ljava/lang/String;[B)Lorg/apache/hadoop/hbase/client/OperationWithAttributes;
at co.cask.tephra.hbase10.TransactionAwareHTable.addToOperation(TransactionAwareHTable.java:670)
at co.cask.tephra.hbase10.TransactionAwareHTable.transactionalizeAction(TransactionAwareHTable.java:559)
at co.cask.tephra.hbase10.TransactionAwareHTable.getScanner(TransactionAwareHTable.java:287)
at org.apache.phoenix.iterate.TableResultIterator.initScanner(TableResultIterator.java:120)
at org.apache.phoenix.iterate.ParallelIterators$1.call(ParallelIterators.java:108)
at org.apache.phoenix.iterate.ParallelIterators$1.call(ParallelIterators.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask.run(JobManager.java:183)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

I pushed up what I have so far as https://github.com/chiastic-security/phoenix-for-cloudera/tree/4.7-HBase-1.0-cdh5.5-WIP-BROKEN

It so happens I heard on good authority that Tephra has a CDH compatibility module, and indeed it does.
Pushed up https://github.com/chiastic-security/phoenix-for-cloudera/tree/4.7-HBase-1.0-cdh5.5


Upgrade 14.0.0-beta.6 and request crash

static let cz_provider = MoyaProvider(endpointClosure: endpointMapping,
requestClosure: timeoutClosure,
plugins: [RequestHudPlugin, RequestAlertPlugin()])
cz_provider.request(MultiTarget(target), callbackQueue: callbackQueue, progress: progress) { (result) in}  This line collapses, and the console has no typos，14.0.0-beta.5 No problem

Hey @lczalh
Can you please provide more on the crash log, the way you installing Moya, which version of Xcode?  ... so we can better understand what is happening :))

Xcode Version 11.2.1

Installing with swift package manager?
Seems like the same crash reporter in #1958

I use cocoapods,  doesn't crash when using 14.0.0-beta.5

This might seems like an obvious question and maybe you already have done that, but have you tried a clean (clear derived data folder) build with the new version?
If you already did that and still have the issues, we have to investigate that in more detail :))

Hey @lczalh
Any updates on this? Did you make it work? if not I can try reproduce the issue get on an investigation :))

Sorry, I'm in a hurry. It's back to 14.0.0-beta.5

The same for me, crashes

I've just tried creating a dummy project and perform a request with beta6 and it didn't crash. Could you guys provide context about those crashes? Xcode version, parameters used in the request call, etc.
Anything will be helpful at this point. The best would be a sample project which replicates the crash.

Ok, i've got some free time today and tried to reproduce this strange issue. Updated to latest beta release, but couldn't get any issues. So I think this issue can be closed for now.

my_name/Carthage/Checkouts/Moya/Sources/RxMoya/MoyaProvider+Rx.swift:24:29: error: type 'Result<Response, Error>' has no member 'error'
                    single(.error(error))
                           ~^~~~~~~~~~~~

Xcode version 12


Could not load helper TestCafe from module './helper/TestCafe'

I am simply trying to runnpx codeceptjs initand select TestCafe
I get the following error.
jordanbenyon@Jordans-MBP codeceptJStestcafe % npx codeceptjs init

  Welcome to CodeceptJS initialization tool
  It will prepare and configure a test environment for you

Installing to /Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe
? Where are your tests located? ./*_test.js
? What helpers do you want to use? TestCafe
? Where should logs, screenshots, and reports to be stored? ./output
? Do you want localization for tests? (See https://codecept.io/translation/) English (no localization)
Error: Cannot find module 'qrcode-terminal'
Configure helpers...

Steps file created at ./steps_file.js
Config created at /Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/codecept.conf.js
Directory for temporary output files created at './output'
Intellisense enabled in /Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/jsconfig.json
(node:44418) UnhandledPromiseRejectionWarning: Error: Could not load helper TestCafe from module './helper/TestCafe':
Cannot find module 'qrcode-terminal'
Error: Cannot find module 'qrcode-terminal'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/helper/TestCafe.js:5:16)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at createHelpers (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/container.js:166:13)
    at Function.create (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/container.js:42:25)
    at Codecept.init (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/codecept.js:56:15)
    at module.exports (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/command/definitions.js:42:12)
    at finish (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/command/init.js:194:7)
    at inquirer.prompt.then (/Users/jordanbenyon/Desktop/Dev Workspace/Automation/projects/codeceptJStestcafe/node_modules/codeceptjs/lib/command/init.js:228:7)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:44418) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:44418) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Details

CodeceptJS version: 2.6.11
NodeJS Version: v10.22.1 (also tried with latest)
Operating System: MacOS Catalina V10.15.6
Configuration file: not set up

Hello @Benyon

Error: Cannot find module 'qrcode-terminal'

It seems you don't have the module qrcode-terminal installed.
So, run npm install qrcode-terminal and then npx codeceptjs init
Let me know if it works.
Sincerely,
Bruno Klein

Hello @Benyon

Error: Cannot find module 'qrcode-terminal'

It seems you don't have the module qrcode-terminal installed.
Try to run:

npm init -y
npm install qrcode-terminal
npx codeceptjs init

Let me know if it works.
Sincerely,
Bruno Klein


Updated to golang 1.14 and alpine 3.11

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Could you help to sign your commits? Thanks.

I am afraid that this pull request is included in https://github.com/dragonflyoss/Dragonfly/pull/1239, then I am closing it. Please feel free to tell me if you have any thoughts. @ducksecops


Update west.yaml to point to the latest repo

Update west.yaml

@lgirdwood for some reason cannot add reviewers

Let me give you write access.


Map/List Grid Resizing

When page loads and on window size change, resize the map/list grid to take up the whole viewable screen (adjust height of map/list grid container so that the height won't extend beyond the current viewport so user does not have to scroll to see whole container)
Refactor SCSS file to split styles into different documented parts
Add more specific styling for the map, list and resource views

Was this supposed to be fixed? (when you scroll to the bottom of the list of resources)

@stephanieyshi yeah are you on the right branch with all the recent changes pulled and are there are JS or SCSS errors? Since the background of the left panel should also be changed. This is what I see on the branch rn:

Ok, not sure why it wasn't updating correctly.
Is it possible to make the search section float over the list, or is that something that was decided against?

haven't decided yet! this PR is to resize the map/list grid so it stays completely on the screen so we can discuss those changes and implement them in another PR


Upgrading to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>all metric names are postfixed with _total

Upgrading to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>all metric names are postfixed with _total. This has impacted all our grafana dashboards. Is this anywhere documented, I couldn't find. And any reason why such post fix is needed?
Example:
Old metric name: incoming_event
New metrics name (just by upgrade): incoming_event_total

Hi, can you share which version do you upgrade from?

Thanks, @weyert for informing me about this. It would be great to document such breaking changes explicitly (All our grafana dashboards are impacted and we nee update the underlying promql queries)
Also, is there any such convention for gauges? Please let me know.

I would not revert the change as this is actually part of the openmetrics standard now. Retroactively updating the changelog seems like a reasonable step though.

The MetricPoint's Total Value Sample MetricName MUST have the suffix "_total".

_https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#counter-1_

Looks like this should be closed as it is behaving according to spec.


Include debug adapter "type" on extension "contributions" page

From #14680
Which debug types are supported? I have to read the readme. Could this include "node2" somewhere?

We accept PRs that fix this


Cleaner Handler to perform service actions

Is your feature request related to a problem? Please describe
In the main template we would like to be able to register extensions for the package deployer, The ideal way is to have handlers that are invoked for the specific stage.

@markcunninghamuk I know we just discussed this on the call but I think we need more context here as I can't remember what this relates to 😄

@markcunninghamuk I know we just discussed this on the call but I think we need more context here as I can't remember what this relates to 😄

Was thinking on the lines of.
public Interface IPackageDeployerExtension
{
void Execute()
}

Then each service Implements IPackageDeployerExtension leaving you with something like
App.RegisteredHandlers.ForEach(handler =>{
   handler.Execute()
}

This way you could add additional handlers without modifying the core template class. You would just register your handler and it will automatically work.

Was thinking on the lines of.
public Interface IPackageDeployerExtension
{
void Execute()
}

Then each service Implements IPackageDeployerExtension leaving you with something like
App.RegisteredHandlers.ForEach(handler =>{
   handler.Execute()
}

This way you could add additional handlers without modifying the core template class. You would just register your handler and it will automatically work.

Ah, yes - this is similar to how me and @tdashworth were thinking about refactoring the services. Essentially mini ImportExtensions  that handle where their own logic is supposed to trigger (as opposed to the PackageTemplateBase having to worry about all of that). Of course we'd probably need a way of having a shared context.

Ah, yes - this is similar to how me and @tdashworth were thinking about refactoring the services. Essentially mini ImportExtensions  that handle where their own logic is supposed to trigger (as opposed to the PackageTemplateBase having to worry about all of that). Of course we'd probably need a way of having a shared context.

Exactly, it makes it also less error prone as you only add the handler for new features without risking damage to other services

Exactly, it makes it also less error prone as you only add the handler for new features without risking damage to other services

@ewingjm @markcunninghamuk @mjahlv I have been thinking about this recently and have come up with some questions...
Do we want to use reflection to find these handlers? If so, do we want to support different constructors or only the one?
I still think this is a good idea but I also like knowing the order in which the steps are executed within the lifecycle event. I was thinking we could create a dependency attribute that ensures those handlers are called first but then we have to build that dependency tree and ensure it's valid with no loops... This approach also removes that high-level view of which order the deployment steps are executed.
What are your thoughts?

I started looking into options recently for this, One I wanted to try was MediatR, It supposedly aims to loosly couple components by turning it into more of a publish / subscribe event handler.
Suggest we have a call for 20 to discuss approaches.
Mark

From: Max Ewing @.>
Sent: Monday, January 25, 2021 09:41
To: Capgemini/powerapps-packagedeployer-template @.>
Cc: markcunninghamuk @.>; Mention @.>
Subject: Re: [Capgemini/powerapps-packagedeployer-template] Cleaner Handler to perform service actions (#28)
Ah, yes - this is similar to how me and @tdashworthhttps://github.com/tdashworth were thinking about refactoring the services. Essentially mini ImportExtensions that handle where their own logic is supposed to trigger (as opposed to the PackageTemplateBase having to worry about all of that). Of course we'd probably need a way of having a shared context.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Capgemini/powerapps-packagedeployer-template/issues/28#issuecomment-767066157, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFKLYCG7HQUAPE3ZZKPSTUTS3XCOFANCNFSM4WR7KOKQ.

I started looking into options recently for this, One I wanted to try was MediatR, It supposedly aims to loosly couple components by turning it into more of a publish / subscribe event handler.
Suggest we have a call for 20 to discuss approaches.
Mark

Oh okay! I've used MediatR in the past which I enjoyed using. Essentially I will handle all the reflection logic for us although I used it with DI container it also handle the constructors.
I'll set something up when we're all available 😀


[enhancement]: SDXL-turbo support

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
<EMAIL_ADDRESS>/ @gmail.com, Discord: @orbitalexplorer Telegram: https://t.me/Obe_Willaert Twitter/X: @ExplorerOrbital
What should this feature add?
Real time generation as you type and support for sdxl turbo because now the images I get with sdxl turbo (configured to let it think it's sdxl) get very incorrect images:

and this is sdxl with refiner

Alternatives
No response
Additional Content
No response

We have support for SDXL Turbo already. You need to ensure your CFG and steps are at 1. You also likely want to use a specific set of schedulers (like Euler Ancestral) as some have issues.

Oh I see I did not see my CFG to 1, thanks for the response. But am I once again missing something because the quality is way worse than the normal version.

If the image is coherent you are probably not missing anything. The image quality of turbo is going to worse than the full model.

No, it's not coherent, some parts of the image are duplicate and the style is totally different.
These are the ones I get now, totally different from the ones above.

Turbo can only generate images at 512x512.

Oh I thought Emad tweeted it can do 786, but that still doesn't explain the style difference, maybe it's just a bit worse and doesn't know the style so well.

Oh yeah I see it now on their page, I read this tweet and assumed it was without upscaling

Yep - It's just worse.


can't set contract to account eosio

I launch nodeos with self generated keypair and specify the keypair with --private-key. I believe this keypair is used for account eosio. I import the private key into wallet and set contract to this account. The cleos complains

Error 3050003: eosio_assert_message assertion failure
Error Details:
assertion failure with message: unable to find key

I check my wallet with command
cleos wallet keys

and find the keypair of eosio I imported. Why can't I set contract to eosio account. Please help!

It seems like you don't have either some required accounts or system token.
See https://github.com/EOSIO/eos/wiki/Tutorial-Bios-Boot-Sequence
parts "Create important system accounts", "Install the eosio.tokencontract", "Create and allocate the SYS currency" (system token is called SYS by default, on mainnet it probably will be EOS).
I am closing the ticket. Feel free to reopen if the documentation didn't help.


Add links to source code to blog posts.

If possible, add links to blog posts that either download an .Rmd or just link to the appropriate GitHub page.

There's an example on how to edit a template to add a "Edit on GitHub" button here: https://bookdown.org/yihui/blogdown/templates.html

related: https://github.com/rstudio/blogdown/issues/106

https://github.com/fmmattioni/downloadthis


Do not panic on exceeding 4096 prints per frame

Currently, because we use a mpsc::SyncSender, we have to set a given max buffer size, I chose 4096. We assume it is never exceeded, which will panic if user once request more than 4096 messages at once. It is probably worthwhile not panicking.

What would be the desired behaviour? Logging through bevy_log?
I reckon that propagating the Result would make screen_print! more cumbersome to use.

You are right, logging an error! is the only sensible alternative.


Web Validator: build rules page from JSON

The rules page hosted on the validator site is currently generated from a transformed RULES.md markdown file
A JSON file is available now that is generated from Java sources that should contain all the same detail and provide a better data-source for render an interactive web page.
Convert the current rules.html build process to use the JSON data source instead of relying on RULES.md

The current JSON export we have seems to be largely missing error- and field-level descriptions


WW transfer - initial files, no custom sections

Per Brandon, only merging up the initial files.
Will do the custom website sections in a follow-up branch
Note -- this is the second attempt of waterworld. first branch had issues with builds

Closing now that #135 is merged.


Im planning to use this actuator for my 6DOF robotic arm

Hi,
Is this a good actuator candidate to be used for a robotic arm with 6 degrees of freedom? Im looking for torque, velocity and a bit of position control (not heavily critical ) what kind of repeatability can I expect from this arm and my approx payload

Hi,
no - I don't think this is a good candidate for a 6dof arm.
This actuator module was designed for dynamic legged robots.
It's best suited for short high-performance motions and hard impacts.
Handling payloads for longer periods of time will heat up the motors too much.
Also there is no joint sensor on the output - that means the elasticity of the transmission results in end effector position errors. We have not measured the positioning repeatability.
We are using the actuator module for a 3 finger hand: https://github.com/open-dynamic-robot-initiative/open_robot_actuator_hardware/blob/master/mechanics/tri_finger_edu_v1/README.md#trifingeredu-v1
But for a 6dof arm you'll need higher gear ratios or stronger motors for the shoulder actuators.
This would require redesigning a lot of the mechanics.


Numbers.vim + Nerdtree: How do I get rid of line numbers in NerdTree pane?

I have NERDTreeShowLineNumbers=0 in my vimrc.local, but numbers are still displayed in the NerdTree pane. Anyone know how to get rid of them?

this questions seems to be uninformative. You have to provide further information.
I could not replicate the problem


Updated plugin to include team profile configuration

Signed-off-by: anaxceron<EMAIL_ADDRESS>Updated plugin to include team profile configuration

Published...


518 sayg only singles and superleague

Resolves #518

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 14 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 95.487%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
6706

Relevant Lines:
6800

💛  - Coveralls


Added name to readme file

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Hi @samuel-ma , if you have opened another PR for the same issue ,kindly close this.
I believe PR #2164 is yours.
Thanks ;)

closed in favor of #2164


fix bug

Changes Proposed

Check List

[ ] The title of my pull request is a short description of the changes
[ ] This PR relates to some issue:
[ ] I have documented the changes made (if applicable)
[ ] I have covered the changes with unit tests

Codecov Report
Patch and project coverage have no change.

Comparison is base (65b08a5) 30.04% compared to head (2ebf633) 30.04%.
 Consider uploading reports for the commit 61568bb to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@                Coverage Diff                 @@
##           helm-dashboard-v2     #447   +/-   ##
==================================================
  Coverage              30.04%   30.04%
==================================================
  Files                     10       10
  Lines                   1348     1348
==================================================
  Hits                     405      405
  Misses                   902      902
  Partials                  41       41

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Some minor API inconsistencies

I'm working on a much needed update to the luv docs. It's nearly done, but I want to highlight some API inconsistencies that I found. None of these seem to be a big deal, some of them are nitpicky, but I wanted to get this list here while I have it

uv.tty_set_mode accepts raw tty_set_mode_t enum instead of a lua string
uv.getaddrinfo hints take raw integer values (I think they are in uv.constants?)

compare to:

uv.run mode accepts lua string instead of raw uv_run_mode enum
uv.udp_set_membership accepts lua string instead of raw uv_membership enum
uv.poll_start accepts lua string instead of raw int for events

uv.tty_set_mode could optionally accept a string so that the change isn't breaking. Should we allow other enum-accepting functions to accept ints? Should we expose more enums at uv.constants?

uv.new_tcp accepts raw int for flags
uv.new_udp accepts raw int for flags

compare to:

uv.tcp_bind accepts a table of booleans instead of raw int for flags
uv.udp_bind accepts a table of booleans instead of raw int for flags
uv.fs_event_start accepts a table of booleans instead of raw int for flags

Might be fixed? See #393 and #398.

uv.getaddrinforeturns table with addr, port, family

compare to:

uv.getnameinfo accepts table with ip, port, family
uv.tcp_getpeername returns table with ip, port, family
uv.tcp_getsockname returns table with ip, port, family
uv.udp_getsockname returns table with ip, port, family
uv.udp_getpeername returns table with ip, port, family

You can't directly use a getaddrinfo result in getnameinfo, but would you want to?

That's all I have for here. I'll be opening other issues or maybe PRs for things that I think deserve there own.

Replying to your comment in #393 here:
The most future proof way to bind new_udp/new_tcp would be to accept a table with key "family" that can either be a string like "inet" or a raw AF_ enum integer (this matches luv_getaddrinfo), because techincally the flags param of uv_new_udp could have more added to it in the future (right now it uses flags & 0xFF for the AF_ enum part).
Might be worth changing it to accept an integer, a string, or a table? That way it'd be easy to expand it if necessary in the future but the default would be to specify AF_ only (the current behavior).

Not really an inconsistency, but something I noticed when reading through the new docs:

uv.new_pipe's ipc argument should probably be made optional (defaulted to false) rather than required

misc.c returns various Lua numbers.
For these, it is fine because libuv uses a double:

uv.uptime
uv.loadavg

But for the rest of these, it's not clear why a Lua number is used:
Libuv returns uint64_t:

uv.get_constrained_memory
uv.get_total_memory
uv.get_free_memory
uv.hrtime

Libuv returns uv_pid_t (int on Windows, pid_t on Unix, which seems to be int on GCC)

uv.os_getppid
uv.os_getpid

Libuv returns int:

uv.os_getpriority

uv.gettimeofday uses a Lua integer for tv_sec if  __LP64__ is defined; a Lua integer is always used for tv_usec.
Libuv uses:
typedef struct {
    int64_t tv_sec;
    int32_t tv_usec;
} uv_timeval64_t;

uv.cpu_info uses a Lua number for every table field (except model).
Libuv uses:
typedef struct uv_cpu_info_s {
    char* model;
    int speed;
    struct uv_cpu_times_s {
        uint64_t user;
        uint64_t nice;
        uint64_t sys;
        uint64_t idle;
        uint64_t irq;
    } cpu_times;
} uv_cpu_info_t;

returning Lua numbers instead of integers
uint64_t

Isn't this a more general problem? PUC Lua doesn't have the concept of uint64 at all, does it? lua_Integer is a signed integer (ptrdiff_t).

Hmmm good point. There's no guarantee that a Lua integer is 64 bits.


Fix sizing month header on every frame and add more calendar model caching

Details
This PR fixes 2 issues:

I was never caching the result of self-sizing a month header, causing us to call systemLayoutSizeFitting on every frame 💀
We weren't caching calendar item models for some calendar slots, like for day ranges and month backgrounds

Related Issue
N/A
Motivation and Context
Performance improvements
How Has This Been Tested
Example app, Airbnb app

Hmm yeah, I'll think about how that might be possible. We don't expose whether something was returned from cache or not, but I bet there's some way we could get it tested.


Improvements to Dino readme

Dino view service README should have similar improvements to those suggested by @davidradl to the Tex README.

Fixed by #3755


SHA384/512 gives wrong hash on linux-aarch64

The hash calculated by the openssl using SHA384/512 is wrong on linux-aarch64 while on "linux-octeon32", "x86", "x86_64" it is correct.
Openssl version: Checked with Openssl version 1.0.1p / 1.0.2k / 1.0.2l / 1.1.0i
Command used: echo $(echo -n "hello" | ./openssl dgst -sha512)
Output:
linux-aarch64: - 92496a87ea2af6f3bf72cdfb26596b0c2d589232d714098ea8594d3ed5ad134b16d3c8f8a213157477e3c965d03274f143798024e1afa523de715051281ba280
linux-octeon32: 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043
x86: 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043
x86_64: 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043
we can see that the output on all platform is same and correct except for linux-aarch64.
Configure Output on linux-aarch64:
CC= //aarch64-2019.02/bin/aarch64-linux-gnu-gcc
CFLAG= -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS  -DDSO_DLFCN -DHAVE_DLFCN_H -g -DOPENSSL_NO_HEARTBEATS -nostdinc -Wall -fpic -fPIC -Werror -Wunused -Wno-unused-but-set-variable -Wno-format -Wno-write-strings -Wno-parentheses -Wno-address -Wno-narrowing  -Wno-error -Wno-narrowing -g -I//aarch64-2019.02/lib/gcc/aarch64-linux-gnu/7.4.1/include -I//aarch64-2019.02/lib/gcc/aarch64-linux-gnu/x.x.x/include-fixed -Wno-error -DOS_LINUX -DARCH_ARM -D__LINUX_ARM_ARCH__=8 -DAP010 -D_UNIX -DNDEBUG -DBUILD_SYSTEM_VERSION=2 -DDEBUG -DCV_DEBUG  -isystem//aarch64-2019.02/aarch64-linux-gnu/libc/usr/include/ -O3 -DB_ENDIAN -DTERMIO  -Wall
DEPFLAG= -DOPENSSL_NO_EC_NISTP_64_GCC_128 -DOPENSSL_NO_GMP -DOPENSSL_NO_JPAKE -DOPENSSL_NO_MD2 -DOPENSSL_NO_RC5 -DOPENSSL_NO_RFC3779 -DOPENSSL_NO_SCTP -DOPENSSL_NO_STORE -DOPENSSL_NO_UNIT_TEST
PEX_LIBS=
EX_LIBS= -ldl
EXE_EXT=
ARFLAGS=
AR= //aarch64-2019.02/bin/aarch64-linux-gnu-ar $(ARFLAGS) r
RANLIB= //aarch64-2019.02/bin/aarch64-linux-gnu-ranlib
NM= nm
PERL= /usr/bin/perl
TAR= tar
TARFLAGS= --no-recursion --record-size=10240
MAKEDEPPROG=makedepend
LIBDIR=lib
All other functionality is working fine except the wrong HASH calculation using SHA384/SHA512.
Is this know issue or any fix available in any build?

Checked with Openssl version 1.0.1p / 1.0.2k / 1.0.2l / 1.1.0i

These are all very old and out of support versions. Please can you check again with a currently supported version of OpenSSL (e.g. 3.1.4 or 3.0.12)

Thanks @mattcaswell for very quick reply.
Sure, I will try on 3.x but need some time as there is huge change inbetween 3.x & where we are.
By any chance, have you (or anyone else) come across this kind of issue i.e. SHA384/512 have failed on any processor?

I don't recall seeing this before - but that's no guarantee that we haven't!

I don't think any of the hashes posted are correct.
Here is what I get:
$ echo -n "hello" | sha256sum
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824  -
$ echo -n "hello" | openssl dgst -sha256
SHA2-256(stdin)= 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

do you have sha256sum on those platforms?

I see the problem.  The command posted in the description has -sha256, but the outputs are actually for -sha512:
$ echo -n "hello" | sha512sum
9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043  -
$ echo -n "hello" | openssl dgst -sha512
SHA2-512(stdin)= 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043

I agree the 9b71... hashes are correct.

@jamuir : yes, it was a typo. I have corrected it to SHA512.

@MannuSD So can I double-check: there is no problem, and this issue can be closed?

@MannuSD So can I double-check: there is no problem, and this issue can be closed?

@tom-cosgrove-arm : Problem is still there. On  linux-aarch64 based system the SHA512 & SHA384 is not corrected computed. I can re-confirm that this issue is on multiple versions of openssl 1.0.1, 1.0.2 and 1.1.0.
Regarding the above comment: While describing the issue in description section SHA256 got typed instead of SHA512 (which I corrected). So, you can ignore that comment.
We have started checking on openssl 3.1 but it will take time to adopt the changes in our system.
So, I would like to request to not close the issue for now...

this issue is on multiple versions of openssl 1.0.1, 1.0.2 and 1.1.0

Note that these versions of OpenSSL are all end of life, and so won't get any fixes.
If there are issues with 3.x we will absolutely fix those

On linux-aarch64 based system the SHA512 & SHA384 is not correctly computed. I can re-confirm that this issue is on multiple versions of openssl 1.0.1, 1.0.2 and 1.1.0.

when I use OpenSSL 1.1.1 on aarch64 the correct hash is computed:
$ openssl version
OpenSSL 1.1.1d  10 Sep 2019
pi@raspberrypi:~ $ echo -n "hello" | openssl dgst -sha512
(stdin)= 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043
pi@raspberrypi:~ $ echo -n "hello" | sha512sum
9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043  -

On linux-aarch64 based system the SHA512 & SHA384 is not correctly computed. I can re-confirm that this issue is on multiple versions of openssl 1.0.1, 1.0.2 and 1.1.0.

when I use OpenSSL 1.1.1 on aarch64 the correct hash is computed:
$ openssl version
OpenSSL 1.1.1d  10 Sep 2019
pi@raspberrypi:~ $ echo -n "hello" | openssl dgst -sha512
(stdin)= 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043
pi@raspberrypi:~ $ echo -n "hello" | sha512sum
9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043  -

@jamuir : Thanks you for trying it at your end and confirming that it is working fine.
Will it be possible for you to share the Configure command output? I just want to make sure that we are not missing any flag or misconfigured it at our end.

I didn't compile that version myself.  It is included with Raspberry Pi OS.
Here is the output of openssl version -a, which may be helpful:
$ openssl version -a
OpenSSL 1.1.1d  10 Sep 2019
built on: Tue Aug 24 08:30:43 2021 UTC
platform: debian-arm64
options:  bn(64,64) rc4(char) des(int) blowfish(ptr)
compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-RzZXhH/openssl-1.1.1d=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
OPENSSLDIR: "/usr/lib/ssl"
ENGINESDIR: "/usr/lib/aarch64-linux-gnu/engines-1.1"
Seeding source: os-specific

Just built 1.1.1 myself and the hash is computed correctly.
$ cd ~/tmp
$ wget https://www.openssl.org/source/openssl-1.1.1w.tar.gz
$ tar xfz openssl-1.1.1w.tar.gz
$ cd openssl-1.1.1w/
$ echo ./Configure linux-aarch64 -Werror --strict-warnings --debug >> doit.bash
$ echo make -j2 >> doit.bash
$ echo make test >> doit.bash
$ . doit.bash &> log.txt

The contents of log.txt show that all tests were successful.
$ LD_LIBRARY_PATH=. ./apps/openssl version
OpenSSL 1.1.1w  11 Sep 2023
$ echo -n "hello" | LD_LIBRARY_PATH=. ./apps/openssl dgst -sha512
(stdin)= 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043

@MannuSD : can you try out the above steps and tell us if it works for you?  This could be done fairly quickly, and it probably makes sense to figure out the sha512 failure before investing a lot of time migrating to 3.x.

Just built 1.1.1 myself and the hash is computed correctly.
$ cd ~/tmp
$ wget https://www.openssl.org/source/openssl-1.1.1w.tar.gz
$ tar xfz openssl-1.1.1w.tar.gz
$ cd openssl-1.1.1w/
$ echo ./Configure linux-aarch64 -Werror --strict-warnings --debug > doit.bash
$ echo make -j2 >> doit.bash
$ echo make test >> doit.bash
$ . doit.bash &> log.txt

The contents of log.txt show that all tests were successful.
$ LD_LIBRARY_PATH=. ./apps/openssl version
OpenSSL 1.1.1w  11 Sep 2023
$ echo -n "hello" | LD_LIBRARY_PATH=. ./apps/openssl dgst -sha512
(stdin)= 9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca72323c3d99ba5c11d7c7acc6e14b8c5da0c4663475c2e5c3adef46f73bcdec043

@MannuSD : can you try out the above steps and tell us if it works for you? This could be done fairly quickly, and it probably makes sense to figure out the sha512 failure before investing a lot of time migrating to 3.x.

Thank you @jamuir . Definitely, we will take it as first thing tomorrow and will update the result here.
Thanks once again for trying it proactively.


Where to put account credentials?

If some kind of documentation exists I could not find it.

hello there, there isn't an option to login into your account currently. You can suggest this, but I doubt it's going to be added.

If Fritter is meant to be used without logging in, IMHO it should not be called a Twitter client. Sending messages is an integral part of a social media service. Software that lacks this functionality is not a client to that social media service. Calling Fritter a Twitter messages browser would be more accurate.

Sorry, Fritter isn't designed to be a full-fat social media app - it's designed to interact with Twitter (follow users, have a feed, save tweets and media, etc.), but without needing to divulge any personal information, or require an account to use, keeping your data as private as possible.
This should be sufficiently documented on fritter.cc, but please let me know if you feel there's any information missing!
For a client that does support both reading and writing tweet data, Twidere X is pretty decent as an alternative 🙂

Thank you!
Fritter is described as a free, open-source Twitter client
here https://f-droid.org/en/packages/com.jonjomckay.fritter/
and here: https://github.com/jonjomckay/fritter/blob/master/README.md
There is no link to fritter.cc on these pages. All I am saying that a user who downloads Fritter from F-droid is likely to make a faulty assumption on what Fritter is based on the description and the documentation available at that time.


Added support for mongodb 2.x

This is similar to pr #30 , but it makes it possible for library to work both for mongodb 1.x and mongodb 2.x - so no downside.

Since creating pr I made forced update of commit. Now I have specified version dependencies in package.json (>=1.3.19 <3.0).


Reduce app size by using unbundled models

Can one use unbundled models as explained here ?

@bharat-biradar ... Can it be done ?

@wazini-john Sorry I had not noticed. I don't think ut is possible, we would need an actual application I suppose. But I'll check once and let you know. Thank you.

I think loading the model from Google Play Services would lead to smaller bundles

Was Running the build without specifying the project folder ie flutter build apk --obfuscate --split-debug-info=./PROJECTNAME/build/symbols

@wazini-john The plugin works with unbundled models but not all API's support unbundled models we have only 3 API's working with unbundled models. But there was a decrease in the size of apk. @fbernaly Should we change the available models to unbundled ones?

What API's ?
And how do we remove the overhead files while getting the same functionalities?

@wazini-john The details have been updated in the readme. Can I close this issue or do you have any other queries?

sure.. thanks

How to clean up any bundles built up in the app ? Or what lines do we add to prevent any kind of bundling?

@bharat-biradar

@wazini-john You can't prevent bundling but you can exclude other assets such pose detection model whose size nearly 24 mb. For information regarding this refer #26 .

What assets do we exclude all together ? @bharat-biradar

@wazini-john Assets that you do not need. For example, if you are working on face detection, you won't be needing model for pose detection or hobbes.tflite etc... Exclude them as shown here. At the end analyze your apk, if there assets that are not being used, ignore those assets.

I'm using face detection in my app and since we'll be using Google Play face API.

Can we exclude all assets generated ?
Does using Google Play APIs affect iOS?

Does using Google Play APIs affect iOS?
No, it does not.
Can we exclude all assets generated ?
You cannot exclude all the generated assets, because some of the assets are may be generated by other plugins or flutter itself. Exclude assets that are used by google_ml_kit plugin only.

If you see in this image mlkit_pose, hobbes.tflite, object_labeler etc... are used by ml kit whereas flutter_assets are used for different purpose so do not, exclude them.

Sorry to disturb but do you have a list of all assets generated by the package ?

The above screenshot contains the list of assets for the latest version of example app. Out of these mlkit_pose, hobbes.tflite, object_labeler.tflite, mlkit_oft_default_classifier, mlkit_odt_lacalizer are generated by plugin.

Final question ... Can I exclude models in assets ?

What models?

The one below hobbes here

Yes you can. Try excluding them, if they interfere with working you can always revert back 😀.

Removing them breaks the app.
Thanks


Fix shell output log formatting.

This fixes #982.
Signed-off-by: James Peach<EMAIL_ADDRESS>

Tests passed! Merging now.

https://github.com/gruntwork-io/terratest/releases/tag/v0.37.8


expose vcap_services for unit tests

Expose vcap_services for unit tests

@jbayer - Randall is a member of cfibmers, but has not yet made his membership public. Please proceed with processing the PR, thanks.

closed accidentally.

great, no problems from the CLA perspective, please proceed


Update libcontainer to 0596e6384a586223c56c5ea7d14467ebf5d17247

It includes fixes to selinux Getfilecon and mounting sysfs.
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

LGTM

LGTM


Cannot get the Python 3.5 package to compile on XCode 8

Hi,
I tried to compile the repo on XCode 8.1. The compile only fails for Python with the following message:
# Configure target Python
cp -f /Users/proffan/Projects/Development/ios/Python-Apple-support/patch/Python/Setup.embedded build/iOS/Python-3.5.2-iphonesimulator.x86_64/Modules/Setup.embedded
cd build/iOS/Python-3.5.2-iphonesimulator.x86_64 && PATH=/Users/proffan/Projects/Development/ios/Python-Apple-support/build/macOS/Python-3.5.2-macosx.x86_64/python/bin:/usr/local/sbin:/usr/local/bin:/Users/proffan/.rbenv/bin:/usr/bin:/bin:/usr/sbin:/sbin ./configure CC="xcrun --sdk iphonesimulator clang -arch x86_64 --sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.1.sdk -miphoneos-version-min=7.0 " LD="xcrun --sdk iphonesimulator clang -arch x86_64 --sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.1.sdk -miphoneos-version-min=7.0 " --host=x86_64-apple-iOS --build=x86_64-apple-darwin16.1.0 --prefix=/Users/proffan/Projects/Development/ios/Python-Apple-support/build/iOS/Python-3.5.2-iphonesimulator.x86_64/dist --without-pymalloc --without-doc-strings --disable-ipv6 --without-ensurepip ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no
checking build system type... x86_64-apple-darwin16.1.0
checking host system type... Invalid configuration `x86_64-apple-iOS': system `iOS' not recognized
configure: error: /bin/sh ./config.sub x86_64-apple-iOS failed
make: *** [build/iOS/Python-3.5.2-iphonesimulator.x86_64/Makefile] Error 1

I think the problem is with the --host option, but I have no idea how to change that line.
Thank you again for your great work.

Hello,
I stumbled over the exact same issue using XCode 8.2.1 and targeting iOS 10.2.
By setting --host=aarch64-apple-ios the build seemed to start, basically. It doesn't work though, due to a compile-time error regarding Python\random.c ...

Thanks for the report.
Based on the error you're seeing, it looks like a patch hasn't been applied correctly - the iOS target has to be added to one of the configure scripts, as it's isn't supported natively by automake. I'll have to take a closer look next time I do a release.

Hello,
first of all thanks for your great work and your reply.
After some hours of fiddling around, I've got a little follow up to that issue. The build seems to work (for all targets/platforms) with some minor changes to the pybee 3.5 branch.
As mentioned above the configure --host flag needs to be altered. It seems like this is necessary due to capitalisation issue.
Instead of fixing the value to -ios (as suggested before) a call to tr should solve this problem in a more robust way for all targets (sadly, a GNU Make call to lc didn’t work out…):

$$(MACHINE_DETAILED-$1)-apple-$2 to --host=$$(MACHINE_DETAILED-$1)-apple-$(shell echo $2 | tr '[A-Z]' ‚[a-z]‘)

Addressing the upcoming compilation errors. They've been discussed in the accompanying [python.org issue23670](http://b
ugs.python.org/issue23670) earlier this year.
For now, removing the affected lines from the source seems to work. However, this doesn't seem to be a no long-term solution, and might eventually result in runtime problems.

sed -ie 's/getentropy(buffer, len);/res=0;/' $$(PYTHON_DIR-$1)/Python/random.c
sed -ie 's/ret = clock_settime((clockid_t)clk_id, &tp);/ret=0;/' $$(PYTHON_DIR-$1)/Modules/timemodule.c

Kind Regards

Thanks for those updates. I'll take a look at getting those changes integrated as soon as I get a chance.

I think a better approach is to patch the pyconfig.h (https://github.com/ButterflyNetwork/Python-Apple-support/commit/21ec86a5413ba453775e4c690e6ac20451f20ab8):
sed -ie 's|\#define HAVE_GETENTROPY 1|/* \#undef HAVE_GETENTROPY */|' $$(PYTHON_DIR-$1)/pyconfig.h
sed -ie 's|\#define HAVE_CLOCK_GETTIME 1|/* \#undef HAVE_CLOCK_GETTIME */|' $$(PYTHON_DIR-$1)/pyconfig.h

Or even better yet, figure out how to get autoconf to properly detect these properties for iOS.

This should be addressed in the most recent binary builds (uploading as I type)


api proxy pass

Is your feature request related to a problem? Please describe.
A lot of people building are used to web development and use the browsers fetch or other ja library (e.g. axios) to make api requests. So it would useful if people could simply reuse their code using fetch and have a proxy pass for the api (so we could avoid CORS) issues.
At the moment I have a codebase that uses js fetch in electron but I cannot use it in tauri due to CORS (with auth).
Describe the solution you'd like
It would similiar to webpack api proxy link. I guess an alternative could be the ability to remove CORS restrictions in the webview like you can do it in electron (set websecurity to false).
Describe alternatives you've considered
I guess this could a plugin that runs a proxy server. Maybe some rust library exists for this and is easy to implement.
Additional context
tauri http is still not a full alternative as it doesn't support multipart forms and the file upload plugin only supports uploading files from path but not js File objects.

The recommended way to bypass CORS is to use our HTTP API that goes through Rust. See fetch.


Stops git-auto-fetch plugin from asking for ssh-key passphrase

This takes care of not prompting for the ssh-key passphrase that can then not be entered.
This fixes #8381
PS: I also prefixed the git commands with command to not run into any issues with aliases or functions.
PPS: @slavaGanzin, it looks like you wrote most of this code, maybe you can take a look at it :smile:

@Syphdias looks good for me.


Deprecation of the official Discord SDK for RPC

Since discord has decided to deprecate the base library this depends on I can no longer continue support for it. The new SDK is not on github and doesn't really offer any good way to make similar bindings since the distribution doesn't offer the same range of platforms or documentation.
Fixing bugs myself in the SDK through pull requests seems out of the picture now.
Deprecation Notice

sad. was working on a spotify alternative and thought about integrating discord into it :(


backblaze-b2: 1.3.6 -> 1.3.8

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/backblaze-b2/versions.
meta.description for backblaze-b2 is: '"Command-line tool for accessing the Backblaze B2 storage service"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/h35fwrmwphx7hnf2117nzv8s2f108hbn-backblaze-b2-1.3.8/bin/.backblaze-b2-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/h35fwrmwphx7hnf2117nzv8s2f108hbn-backblaze-b2-1.3.8/bin/backblaze-b2 had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 1.3.8 with grep in /nix/store/h35fwrmwphx7hnf2117nzv8s2f108hbn-backblaze-b2-1.3.8
directory tree listing: https://gist.github.com/4e35b4c137720e248b1216484ba85417
du listing: https://gist.github.com/7c2981241d00eb45bb85aca7400d2532

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
backblaze-b2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h35fwrmwphx7hnf2117nzv8s2f108hbn-backblaze-b2-1.3.8 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A backblaze-b2 https://github.com/r-ryantm/nixpkgs/archive/ce709426ae6942544881a37ab6436fcfbfee869a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h35fwrmwphx7hnf2117nzv8s2f108hbn-backblaze-b2-1.3.8
ls -la /nix/store/h35fwrmwphx7hnf2117nzv8s2f108hbn-backblaze-b2-1.3.8/bin

cc @hrdinka @kevincox for testing.

Tested locally, thanks!


Don't wget --quiet jq.  Ask the user what to do.

It might not be shifty to packet for this to happen but to me doing that is pretty shifty even if it's not all that bad.  Not only are you downloading a binary blindly onto your users servers assuming everything is going to be quite alright, but you neglect to even verify said download and make sure it's specific version.
Why not just install jq by default as well? Or install it from apt?  It's in the repositories...

Just so things are clear: https://github.com/packethost/packet-block-storage/blob/22effe411d23bb60b24ea9e19dc365728623a7dd/packet-block-storage-attach#L32

@envygeeks agreed, this is a hack done in the interest of time IMO. will work on a fix, thanks for submitting an issue!

#7 is related; the installed binary is the wrong architecture on aarch64 servers.

I assume #8 has since fixed this, @vielmetti ? jq is being installed via Yum and Apt, no longer fetched via wget.

Yes, the wget is no longer in the script. Closing.


Add kubvirt_number_of_vms recording rule

What this PR does / why we need it:
Add a recording rule to count all VM in the cluster.
In this PR, I also refactored recording rules. Before recording rules and alerts were all together, and recording rules were manually added to the metrics doc generator.
I moved recording rules to an exported function. The result is appended to the list with the alerts and the function is imported by doc-generator. This allows us to be sure that all recording rules are being documented.
Release note:

Add kubevirt_vm_count recording rule

JIRA ticket:
https://issues.redhat.com/browse/CNV-23011

/cc @enp0s3 @fossedihelm

Total is only for counter metrics, so kubvirt_number_of_vms or
kubevirt_vm_number, @sradco WDYT?
On Tue, 2 May 2023 at 12:29 João Vilaça @.***> wrote:

@.**** commented on this pull request.
In docs/metrics.md
https://github.com/kubevirt/kubevirt/pull/9652#discussion_r1182314240:

+### kubevirt_virt_operator_leading_total
+The number of virt-operator pods that are leading. Type: Gauge.

+### kubevirt_virt_operator_ready_total
+The number of virt-operator pods that are ready. Type: Gauge.
+
+### kubevirt_virt_operator_up_total
+The number of virt-operator pods that are up. Type: Gauge.
+
+### kubevirt_vm_container_free_memory_bytes_based_on_rss
+The current available memory of the VM containers based on the rss. Type: Gauge.
+
+### kubevirt_vm_container_free_memory_bytes_based_on_working_set_bytes
+The current available memory of the VM containers based on the working set. Type: Gauge.
+
+### kubevirt_vm_count
_total?
—
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/pull/9652#discussion_r1182314240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APJI7IP6MURNMQSC3YRHWA3XEDHYFANCNFSM6AAAAAAXJS6FMA
.
You are receiving this because you commented.Message ID:
@.***>

--
Aviv Litman
BI Associate Software Engineer
Red Hat https://www.redhat.com/
@.***
https://www.redhat.com/

/retest

/lgtm

@machadovilaca  There is a spelling issue with the metric name in the PR name

/lgtm

/retest

@machadovilaca Hi. Can you please extract the refactor part into a separate commit?

updated @enp0s3

/lgtm


Cannot create subdirectory

Not sure if this is an issue or not. I am just using README.md examples. Upload works great but creating a directory fails.
Trying to create directory at os level fails too.
If it is not an issue, how to create subdirs?
Thanks in advance.

Fixed in pull  #request #4


remove view-traffic-manager profile-change-history.md

Hi @joaoma, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (joaoma). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Create new kata: Bounded Knapsack

I have finished writing the tasks, tests, and reference implementation for the Knapsack Problem kata that I had proposed in #416. I would greatly appreciate if it could be reviewed, and any feedback on how the kata could be improved so that it can be incorporated into the repository. I recognize that the kata for the Knapsack Problem is different and potentially more complex than the other existing Grover katas, so if there are any parts of the new kata that might need clarification, please let me know.

@msoeken Thank you very much for your careful review. I'm grateful that you had brought up the use of within/apply, which I had not previously been aware of. I have batch-committed all of the changes, and revised the parts of the code that you had referenced. Please let me know if I had missed any changes, or if you have any other suggestions.
In addition, could you briefly explain what the Microsoft checks do? If any of the checks fail, how should I change my code to pass the check? Thank you.

@msoeken Thank you for approving the kata. I've finalized the last few changes; feel free to let me know if I missed anything.
I've also noticed that some of the checks are not passing: how should the kata be changed to pass them? Or does the kata not have to pass all the checks, but just need to be merged by a member with write access? Please let me know if you have any comments. Thank you.

@emax-wenjun There are some problems with the new knapsack project on CI. Maybe you can have a look at your side. Here are the error messages in case you cannot see them:
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(124,49): error QS6210: The type of the given argument does not match the expected type. Got an argument of type (Qubit[] => Result[]), expecting one of type ('T -> 'U) instead. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(124,23): error QS6212: The type parameter resolution for the call is ambiguous. Please provide explicit type arguments, e.g. Op<Int, Double>(arg). [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(124,58): error QS6212: The type parameter resolution for the call is ambiguous. Please provide explicit type arguments, e.g. Op<Int, Double>(arg). [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(176,40): error QS5022: No identifier with the name "XS" exists. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(176,28): error QS6222: The type of the given expression cannot be determined. Provide explicit type arguments ("identifier<commaSeparatedTypeArguments>"). [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(321,17): error QS6312: The called operation does not support the necessary functor(s) for the requested auto-generation of a specialization. Missing support for functor(s) Adjoint. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(322,17): error QS6312: The called operation does not support the necessary functor(s) for the requested auto-generation of a specialization. Missing support for functor(s) Adjoint. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/ReferenceImplementation.qs(146,47): error QS6201: The shape of the given tuple does not match the expected type. Got an argument of type (Qubit[][], Int[], Qubit[]), expecting one of type ('T[], 'U[]) instead. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/work/1/s/BoundedKnapsack/Tests.qs(185,25): error QS6210: The type of the given argument does not match the expected type. Got an argument of type Bool, expecting one of type (Bool, String) instead. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]
/home/vsts/.nuget/packages/microsoft.quantum.development.kit/0.12.20072031/build/Microsoft.Quantum.Development.Kit.targets(25,5): error MSB3073: The command "dotnet "/home/vsts/.nuget/packages/microsoft.quantum.development.kit/0.12.20072031/build/../tools/qsc/Microsoft.Quantum.CsharpGeneration.App.dll"  --qst "BoundedKnapsack" --input "ReferenceImplementation.qs" "Tasks.qs" "Tests.qs" --references "/home/vsts/.nuget/packages/microsoft.dotnet.platformabstractions/1.0.3/lib/netstandard1.3/Microsoft.DotNet.PlatformAbstractions.dll" "/home/vsts/.nuget/packages/microsoft.extensions.dependencymodel/1.0.3/lib/netstandard1.6/Microsoft.Extensions.DependencyModel.dll" "/home/vsts/.nuget/packages/microsoft.quantum.qsharp.core/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.QSharp.Core.dll" "/home/vsts/.nuget/packages/microsoft.quantum.runtime.core/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.Runtime.Core.dll" "/home/vsts/.nuget/packages/microsoft.quantum.simulators/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.Simulation.Common.dll" "/home/vsts/.nuget/packages/microsoft.quantum.simulators/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.Simulation.QCTraceSimulatorRuntime.dll" "/home/vsts/.nuget/packages/microsoft.quantum.simulators/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.Simulators.dll" "/home/vsts/.nuget/packages/microsoft.quantum.standard/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.Standard.dll" "/home/vsts/.nuget/packages/microsoft.quantum.xunit/0.12.20072031/lib/netstandard2.1/Microsoft.Quantum.Xunit.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.testhost/15.7.2/lib/netstandard1.5/Microsoft.TestPlatform.CommunicationUtilities.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.objectmodel/15.7.2/lib/netstandard1.5/Microsoft.TestPlatform.CoreUtilities.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.testhost/15.7.2/lib/netstandard1.5/Microsoft.TestPlatform.CrossPlatEngine.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.objectmodel/15.7.2/lib/netstandard1.5/Microsoft.TestPlatform.PlatformAbstractions.dll" "/home/vsts/.nuget/packages/microsoft.codecoverage/1.0.3/lib/netstandard1.0/Microsoft.VisualStudio.CodeCoverage.Shim.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.testhost/15.7.2/lib/netstandard1.5/Microsoft.VisualStudio.TestPlatform.Common.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.objectmodel/15.7.2/lib/netstandard1.5/Microsoft.VisualStudio.TestPlatform.ObjectModel.dll" "/home/vsts/.nuget/packages/newtonsoft.json/12.0.3/lib/netstandard2.0/Newtonsoft.Json.dll" "/home/vsts/.nuget/packages/microsoft.testplatform.testhost/15.7.2/lib/netstandard1.5/testhost.dll" "/home/vsts/.nuget/packages/xunit.abstractions/2.0.1/lib/netstandard1.0/xunit.abstractions.dll" "/home/vsts/.nuget/packages/xunit.assert/2.3.1/lib/netstandard1.1/xunit.assert.dll" "/home/vsts/.nuget/packages/xunit.extensibility.core/2.3.1/lib/netstandard1.1/xunit.core.dll" "/home/vsts/.nuget/packages/xunit.extensibility.execution/2.3.1/lib/netstandard1.1/xunit.execution.dotnet.dll" --output "obj/qsharp/"" exited with code 2. [/home/vsts/work/1/s/BoundedKnapsack/BoundedKnapsack.csproj]

Build FAILED.

@msoeken The errors are all easy to address except for the first three. I'm not quite sure why the check thinks that the types don't match, since the input of ResultArrayAsInt is Result[], which matches the output of MultiM. Perhaps the operation Compose doesn't work with arrays? If that is the case, we may need to use a different operation or perform the task in the long way.
I also don't know what errors #2 and #3 are talking about either. They don't seem to be a problem when I build the project in my Visual Studio. If you understand and could explain to me what an ambiguous type parameter resolution is, I would be grateful.

@msoeken Thank you helping to identify the problem, and for reviewing the kata. All the checks are now passed.

@msoeken Since you've approved of the changes in this pull request, would you mind merging it with the master branch? I don't have write access so I can't do it myself. If there any other changes that you would suggest, I would be happy to implement them.

@emax-wenjun I would like to wait until @tcNickolas approves.

@tcNickolas Are there any other changes that you would suggest to this pull request before it is to be merged? Please let me know if there's anything else I can do, or if you have any other comments.

@tcNickolas Thank you very much for your careful review. I will work on all the suggestions in the next few days.

@tcNickolas The changes that you suggested have now been implemented. Feel free to let me know if I missed any, or if there are to be any further changes, at your convenience.

@tcNickolas Will you have the opportunity to complete your review in the near future? Please let me know, at your convenience, of any  further changes that you would like to have made.

Those new errors are introduced by a combination of https://github.com/microsoft/QuantumKatas/pull/469/ and https://github.com/microsoft/QuantumKatas/pull/467: we changed the way project dependencies work, and then did a change to the (now not used directly) Common project. You'll need to change your csproj file to match the other csproj files: have two package references (to Microsoft.Quantum.Katas and Microsoft.Quantum.Xunit) and no project reference to Common, and that should work.
(Apologies for another delay reviewing, I have some urgent work to finish this week which means I only have bandwidth for very simple things on the Katas :-( I hope to get back to reviewing the more interesting things next week!)

@tcNickolas Hi, I just want to check in. Will you have an opportunity in the near future to continue the review of this kata?

I'm terribly sorry for the delay reviewing this - between some urgent work and the smoke season that has befallen West coast in the past two weeks I had very little time to work on the Katas, and no chance to focus on this review at all :-( I really hope to be able to set aside some time next week to catch up on this review and on the others...

@tcNickolas I understand. Please take your time, and I hope everything goes well for you.

@tcNickolas Hi. Have you had a chance to take a look at the reset of the kata?

Hi @tcNickolas, have you had a chance to review the remainder of the pull request? Thanks.

@tcNickolas Thank you so much for thoroughly reviewing and editing this kata! I've only just had the opportunity to read the changes, and I can probably resume working on further changes in the near future. As for the paper, I don't think I'm allowed to give it out prodigally since it's published in a journal, but I might be able to get you a copy if you privately message me. I'm excited to continue working on this kata!

@emax-wenjun It will be great if you have the time to finish the kata! I filed issue #638 with some extra thoughts on the last chapter but haven't gotten to doing it yet, so if you want to pick it up, great! I'll try to be more responsive with the next review, I promise!

@emax-wenjun I wonder if you'd be interested in writing a blog post about this algorithm and its Q# implementation for Q# Advent Calendar? You could probably use some of the text from your paper, and it would be a great learning resource to accompany the kata (as well as a nice way to advertise it!)
Let me know if that sounds interesting!


feat(geography): track the fully loaded countries in state

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: N/A
What is the new behavior?

Adds state for tracking the fully loaded countries
Adds selectors for checking if a country is fully loaded
Adds some generic default values

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
This is needed because a country's subdivision should be not a required value only when the country has been fully loaded and no subdivions are present. Otherwise there is no way to determine whether or not a country has subdivisions without actually trying to load them all.

@damienwebdev You mean store that info as a subfield of DaffCountry? So set it in the entities reducer?

@griest024 Yes. I think that makes more sense the storing a map of props elsewhere and having to go search for the prop in another piece of the state tree.

@damienwebdev changed

lgtm


Blog images with custom widths

Blog images right now always take up the width of the text area.  This is fine for most cases but there are cases where the image looks way too big.
Create a way to explicitly specify the width.

The code to change this is at portfolio/components/ReactMarkdownCustom.tsx.


[Bug]: KafkaContainer networkAliases not available anymore after update to 1.19.2

Module
Kafka
Testcontainers version
1.19.2
Using the latest Testcontainers version?
Yes
Host OS
Windows
Host Arch
x86
Docker version
Client:
 Cloud integration: v1.0.29
 Version:           20.10.22
 API version:       1.41
 Go version:        go1.18.9
 Git commit:        3a2c30b
 Built:             Thu Dec 15 22:36:18 2022
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.16.3 (96739)
 Engine:
  Version:          20.10.22
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.9
  Git commit:       42c8b31
  Built:            Thu Dec 15 22:26:14 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.14
  GitCommit:        9ba4b250366a5ddde94bb7c9d1def331423aa323
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

What happened?
Disclaimer: The error described in this issue can easily be avoided. I am just creating this issue to inform you about a regression issue, which was not expected from a minor version update.
We are using KafkaContainer together with a custom SchemaRegistryContainer for our Spring Boot Integration-Tests.
In order to connect both, we define a Network for the KafkaContainer and configure the SchemaRegistryContainer to use the same network with a network alias set as SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS url:
@Testcontainers
class KafkaContainerInitializer : ApplicationContextInitializer<ConfigurableApplicationContext> {
    companion object {
        private const val CONFLUENT_VERSION = "confluentinc/cp-kafka:7.0.10"

        @Container
        val kafkaContainer: KafkaContainer = KafkaContainer(DockerImageName.parse(CONFLUENT_VERSION))
            .withNetwork(Network.newNetwork())

        @Container
        val schemaRegistryContainer: SchemaRegistryContainer =
            SchemaRegistryContainer().withKafka(kafkaContainer)
    }

    override fun initialize(applicationContext: ConfigurableApplicationContext) {
        kafkaContainer.start()
        schemaRegistryContainer.start()
    }
}

class SchemaRegistryContainer : GenericContainer<SchemaRegistryContainer>(
    "confluentinc/cp-schema-registry:7.0.10"
) {

    init {
        withExposedPorts(8081)
    }

    fun withKafka(kafka: KafkaContainer): SchemaRegistryContainer {
        return withKafka(kafka.network!!,  "${kafka.networkAliases[0]}:9092")
    }

    private fun withKafka(network: Network, bootstrapServers: String): SchemaRegistryContainer {
        withNetwork(network)
        withEnv("SCHEMA_REGISTRY_HOST_NAME", "schema-registry")
        withEnv("SCHEMA_REGISTRY_LISTENERS", "http://<IP_ADDRESS>:8081")
        withEnv("SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS", "PLAINTEXT://$bootstrapServers")
        return this
    }
}

After the update to version 1.19.2 kafka.networkAliases[0] throws a IndexOutOfBoundsException because no network alias is configured. This is likely related to this commit: https://github.com/testcontainers/testcontainers-java/pull/7748
It can easily be fixed by setting an alias explicitly using the withNetworkAliases method but, as pointed out, such a regression issue was not expected by a minor version update. Therefore, and to make sure no other issues occurred with the change, I'm opening this bug.
Relevant log output
No response
Additional Information
No response

We have this problem on our Ubuntu GIthub Action runners but it works fine on MacOS

I'll try and get a new bug reported raised if required.
I made the changes in my code to use the .withNetworkAlias against 1.19.2 which got past this index out of bounds error but I then get problems on the kafka-streams health check failing.
Timed out waiting for node assignment. Call: listTopics
Again works fine on my work MacOS laptop but fails on the Ubuntu GHA runner we have.
1.19.1 worked fine, I'll try and get time towards the end of the week to make a reproducible version on my Linux laptop


Add gstreamer1.0-plugins-bad (to get HLS plugin)

Closes https://github.com/aotuai/brainframe-qt/issues/105
Because gstly's logic prevents BrainFrame from choosing anything other than the HLS (http livestream) plugin from gstreamer1.0-plugins-bad, this should be fine to add from a licensing perspective.

Couple questions:

I assume the license for the HLS plugin in compatible with ours?
This probably introduces new libraries to the Pyinstaller image. Will you add them to the whitelist of libraries allowed for inclusion?
Is it not just possible to get the HLS plugin w/o all the other plugins?

I assume the license for the HLS plugin in compatible with ours?

Yes

This probably introduces new libraries to the Pyinstaller image. Will you add them to the whitelist of libraries allowed for inclusion?

Incorrect. This is actually bringing the snap build back to parity with the windows/linux pyinstaller builds, which already include the HLS plugin, and have the requisite whitelist.

Is it not just possible to get the HLS plugin w/o all the other plugins?

As with all things, yes, but it would require building quite a few things from scratch.


Got the Error in recommender system

When i tried to run the recommended system, i got the following error
import turicreate as tc
data = tc.SFrame({'user_id': ["Ann", "Ann", "Ann", "Brian", "Brian", "Brian"],
'item_id': ["Item1", "Item2", "Item4", "Item2", "Item3", "Item5"],
'rating': [1, 3, 2, 5, 4, 2],
'country':["United States","United States","United States","United States","United States","United States"]
})
m = tc.factorization_recommender.create(data, target='rating')
recommendations = m.recommend()
country = 'United States'
recommendations=m.recommend(users=users['user_id'][users['country']==country].unique(), items=items['item_id'][items['country']==country])
print recommendations
Error is
Traceback (most recent call last):
File "sample.py", line 14, in
recommendations=m.recommend(users=users['user_id'][users['country']==country].unique(), items=items['item_id'][items['country']==country])
NameError: name 'users' is not defined

@Padalingam - The issue is this part of code on line 14:
users['user_id'][users['country']==country].unique().
There isn't a variable called users.
I think what you are trying to get recommendations for all users of a country and limit those recommendations to only items rated by users of that country. If that is the case, I would recommend creating a temporary variables to make things easier.
Replace line 14 with the following:
country_ratings = data[data['country']==country]
recommendations = m.recommend(users=country_ratings['user_id'].unique(),
                               items=country_ratings['item_id'].unique())

Sounds like this issue has been resolved. @Padalingam, please reopen if you continue to see an issue here after applying @TobyRoseman's suggested change. Thanks!

Its working fine. Now, my question is after i got the recommended model. how can i store it as a .mlmodel file and to use that recommended model into my iOS project

@Padalingam - That is an open issue, which we are tracking in #34.


Make convenient ETag header construct function

Problem: PR #446 (commit 0ce2754eb735d2acb94e2c45758392335a448f99) added the
type EntityTag to fix the malformed ETag and If-Modified-Since headers. In
the process construction of the ETag header became more difficult due to it
now containing an inner object instead of a simple String.
Fix: Add a simple apply function to the object to give the same behavior we had
before.
This PR should be binary backwards compatible with 0.11.0: it only modifies the
internal of the ETag header parser and introduces one new method to the ETag
object.

:+1:, land on 0.11 maintenance branch.

Closed via cherry-picked commit a3404fd041cd2beb27aff0db975596b9e35c087c on branch https://github.com/http4s/http4s/tree/release/v0.11.1


Planning module's output when having PLANNING_ERROR

Description of Scenario
I have generated a scenario (record file attached below) with Apollo 7.0 using SimControl and noticed an abnormal planning output. The scenario's cyber record, full planning output, and a script to extract those planning messages are all included in the attachment.
Consider the following planning message (only key information included, full file in attachment), vehicle was traveling at about 3 m/s before this message was generated:
header {
  timestamp_sec:<PHONE_NUMBER>.0802026
  module_name: "planning"
  sequence_num: 298
  lidar_timestamp: 0
  camera_timestamp: 0
  radar_timestamp: 0
  status {
    error_code: PLANNING_ERROR
    msg: "Failed to init reference line info."
  }
}
debug {
  planning_data {
    adc_position {
      header {
        timestamp_sec:<PHONE_NUMBER>.034947
        module_name: "SimControl"
        sequence_num: 2191
      }
      pose {
        position {
          x:<PHONE_NUMBER>165494
          y: 4141582.055045245
          z: 0.0
        }
...
        linear_velocity {
          x: 3.143305029907031
          y: -0.05644375319608064
          z: 0.0
        }
        linear_acceleration {
          x: -3.3543739905028147
          y: 0.06023387989580283
          z: 0.0
        }
...
}
gear: GEAR_DRIVE
trajectory_point {
  path_point {
    x:<PHONE_NUMBER>165494
    y: 4141582.055045245
    theta: -0.017954887330706715
    s: 0.0
  }
  v: 0.0
  a: 0.0
  relative_time: -0.002025127410888672
}
trajectory_point {
  path_point {
    x:<PHONE_NUMBER>165494
    y: 4141582.055045245
    theta: -0.017954887330706715
    s: 0.0
  }
  v: 0.0
  a: 0.0
  relative_time: 0.09797487258911133
}
trajectory_point {
  path_point {
    x:<PHONE_NUMBER>165494
    y: 4141582.055045245
    theta: -0.017954887330706715
    s: 0.0
  }
  v: 0.0
  a: 0.0
  relative_time: 0.19797487258911134
}
...
decision {
  main_decision {
    not_ready {
      reason: "PLANNING_ERROR: Failed to init reference line info."
    }
  }
}

The current velocity of the ego vehicle is (x: 3.143305029907031, y: -0.05644375319608064), so about 3 m/s; but the planning module's output trajectory points all have v:0.0, a:0.0, and path_point at exactly where the ego vehicle is currently at. Since I am using SimControl, it received this planning message and published the ego vehicle's next localization at this coordinate with speed = 0.0 m/s. In other words, the ego vehicle decelerated from 3 m/s to 0 m/s in less than 0.01 seconds.
My understanding is that, since there is a PLANNING_ERROR, the planer is asking the vehicle to stop immediately (v=0), as opposed to decelerate immediately (a < 0) until stopped (v=0).
Attachments
report.zip
Questions

When a PLANNING_ERROR happens, is it expected for all trajectory points to have v=0 and a=0?
Knowing that the vehicle is already traveling at 3m/s, is it reasonable to produce trajectory_points that all have v=0m/s? There is no way to decelerate that fast.
The original scenario was executed by SimControl, which is not the same as a vehicle's actual Control module. When the vehicle's control module receives such planning message (current v = 3 m/s, trajectory_point = 0 m/s), what would it do?

Hi yuqi,
When there is a PLANNING_ERROR due to the fact that it failed to initialize the reference line, apparently it cannot move forward under such scenario. so I think it makes sense to not to plan any more trajectories and let the control module to brake as fast as possible. I'm not entirely sure on this but you may check the source code for the planning module.
I think when the control module receives all zero velocity trajectories, it will decelerate as fast as it can. You may be able to confirm this by manually publishing such trajectory points when you're running with the simulator together.
Since the sim control does perfect control and it does not simulates vehicle dynamics. so it will definitely jumps from 3m/s to 0m/s because the planned trajectory said so.

Hi @ntutangyun ,
Thanks for your response! So in the scenario, the planning message after the one I included above asks the ego vehicle to accelerate from 0 m/s to 3 m/s instantly. Putting this all together would mean that the vehicle is able to travel at its original speed but for some reason is asked to decelerate to 0 m/s and then accelerate back to 3 m/s.
Dreamview + SimControl seems to be the only "built-in" scenario testing method, and the perfect control relies on the Planning module to produce a physically feasible trajectory. Therefore the question is, when a planning error happens, should the planning trajectory be something like [ v=3, v=2.6, v=2.2, v=1.8, ... v=0 ] which represents a feasible fast decelerating trajecotry; or should it be [ v=0, v=0, v=0, v=0, ... v=0 ], which is a physically impossible trajectory that can only be interpreted by the Control module to hopefully do the right thing? In other words, "exit gracefully" rather than simply not plan at all.
I want to argue it might be safer to produce a controlled decelerating trajectory without changing the heading, rather than an all-0 trajectory. If the Control module interprets all-0 trajectory as "brake as hard as possible", would this cause some extreme high deceleration which in turn causes passenger comfort violation? in more extreme cases, would this over-deceleration cause vehicle skid?
p.s. I'll try to see if I can produce Planning messages and observe the Control module's behavior using Apollo + LGSVL

I think it's ok for the moment for two reasons:

if the control module is involved and the vehicle dynamics are correct, then even if the planned trajectory has an abrupt jump in speed for whatever reason. for example from 0m/s to 3m/s, then the physical vehicle itself won't be able to change its speed instantly. assume the frequency is 10Hz. then after 100 ms, say the vehicle is only able to accelerate to 0.5m/s from 0m/s, then in the next planning phase, the planning module will take the latest speed into consideration and fix itself, i.e., planning the speed as 0.5m/s, 0.6m/s, ... 2.5m/s, 3.0m/s, etc.

I agree with you that the planning module should implement sufficient fail-safe and fail-operational mechanisms, for example, when a planning error is encountered, a safe decelerating trajectory should be produced. Again, Apollo open-source version is not perfect, and for the current implementation, it depends on the control module to handle the slow deceleration tasks. This is actually also helpful in certain cases.

Note that if the planning module hangs or crashes suddenly, the control module will try to follow its last received trajectory.
As a result, if you think about it, it is actually safer for the planning module to produce a fallback trajectory with all 0m/s velocities, such that when the planning module fails to work, the control module will at least be able to follow the fallback trajectory and put the vehicle to an immediate stop. On the other hand, if the planning module tried to produce a deceleration trajectory with the last velocity greater than zero and it crashes. then it's gonna be very dangerous for the control module to keep driving the vehicle, isn't it?
In summary, Apollo open-source is not perfect, and it has not implemented sufficient fail-safe and fail-operational mechanisms. So if you're targeting its fail-safe and fail-operational mechanisms, for sure, you will discover much more issues.
So, based on the current implementation and how the planning and control work together, I don't think it's an issue to produce all zero velocity trajectories when it encounters extreme errors such as this one: "reference line failed to initiate", where the planning module usually needs to restart to resolve this issue.

Your comments are so insightful, it is great to be able to discuss this with you. I got 2 high-level conclusions for now:

It can be good if the planning module can be self-sufficient in terms of fail-safe. Since an error is produced and the module will potentially crash, even if a fail-safe fallback trajectory is to be produced, it must reach v = 0 at the end.

Certain outputs will seem to be an error of a specific module, but the system as a whole can tolerate such errors.

I agree that Apollo at the moment is not perfect yet. I focus on using SimControl to test its prediction and planning module. So far this is the only insufficient fail-safe condition that I met.

btw I learned the terms fail-safe and fail-operational in the whitepaper:
A Framework for September 2018 Automated Driving System Testable Cases and Scenarios
you can check it out although it's a bit old..

@daohu527 We did some further investigation on this problem and found the following comment https://github.com/ApolloAuto/apollo/blob/aa0c5eb66189b86a724206305712cfb337c07619/modules/planning/on_lane_planning.cc#L185-L186
Which generated trajectory_points at ego's current location all with v = 0.0, as discussed in this post. Intuitively, planning is asking the ego vehicle to freeze at the current location immediately.
Since the comment suggests this will cause unexpected behavior from the controller, I want to try to fix this function by changing the output to a hard braking (a = -4 m/s^2) trajectory following the vehicle's current heading, with velocity such as [ v=3, v=2.6, v=2.2, v=1.8, ... v=0 ]. Do you have any suggestions or thoughts?

It usually has no path to call this fallback function(just for safe). if there is a path，we will use GenerateFallbackSpeed func to generate a fallback speed

@qwetqwe Does "has no path to call this fallback" mean, if there is no path (i.e., Driveable then this function will be called?
During the scenarios that I was running with Apollo + SimControl, GenerateStopTrajectory occasionally gets called while the ego is traveling with positive speed. Since I am using SimControl, it perfectly executes the decision, so sometimes Apollo travelling at 3 m/s suddenly does a complete stop (0 m/s) and then resumes moving forward at the original speed (3 m/s). This behavior causes the scenario to be unrealistic because Apollo reaches a complete stop without any deceleration.
Since GenerateStopTrajectory produces a physically impossible decision, and SimControl does not take that into account. What would you suggest I do to make the scenario realistic?


Rewrote code to make all variables finals and created functions

Max, please write the tests and put the code into a separate class that can be unit-tested. Thanks.

LGTM


make partition replication information a bit more clear

Update the partition replication information to be a bit more clear about how many partitions are in which replication states. Also make explicit what is the average v. target replication.

r? @bartle-stripe
cc? @stripe/storage

lgtm


data

data added

@sarome-picf Please make a Good Contribution if you want your changes to be merged to the main Branch 🤖

Will do. Just one question though, what is an example of a Good contribution?
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: Aaron Markus @.>
Sent: Friday, August 2, 2024 9:01:15 AM
To: aaron-muti-420/Int-Git-GitHub-Ops @.>
Cc: sarome-picf @.>; Mention @.>
Subject: Re: [aaron-muti-420/Int-Git-GitHub-Ops] data (PR #6)
@sarome-picfhttps://github.com/sarome-picf Please make a Good Contribution if you want your changes to be merged to the main Branch 🤖
—
Reply to this email directly, view it on GitHubhttps://github.com/aaron-muti-420/Int-Git-GitHub-Ops/pull/6#issuecomment-2264704106, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BD5NILG3XMMOVUNLESTYGKTZPMVDXAVCNFSM6AAAAABL27LYPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRUG4YDIMJQGY.
You are receiving this because you were mentioned.Message ID: @.***>

Will do. Just one question though, what is an example of a Good contribution? Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
…
________________________________ From: Aaron Markus @.> Sent: Friday, August 2, 2024 9:01:15 AM To: aaron-muti-420/Int-Git-GitHub-Ops @.> Cc: sarome-picf @.>; Mention @.> Subject: Re: [aaron-muti-420/Int-Git-GitHub-Ops] data (PR #6) @sarome-picfhttps://github.com/sarome-picf Please make a Good Contribution if you want your changes to be merged to the main Branch 🤖 — Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BD5NILG3XMMOVUNLESTYGKTZPMVDXAVCNFSM6AAAAABL27LYPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRUG4YDIMJQGY. You are receiving this because you were mentioned.Message ID: @.***>

Look at the Contribution Guides

👍
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: Aaron Markus @.>
Sent: Friday, August 2, 2024 9:56:19 AM
To: aaron-muti-420/Int-Git-GitHub-Ops @.>
Cc: sarome-picf @.>; Mention @.>
Subject: Re: [aaron-muti-420/Int-Git-GitHub-Ops] data (PR #6)
Will do. Just one question though, what is an example of a Good contribution? Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
…
________________________________ From: Aaron Markus @.> Sent: Friday, August 2, 2024 9:01:15 AM To: aaron-muti-420/Int-Git-GitHub-Ops @.> Cc: sarome-picf @.>; Mention @.> Subject: Re: [aaron-muti-420/Int-Git-GitHub-Ops] data (PR #6https://github.com/aaron-muti-420/Int-Git-GitHub-Ops/pull/6) @sarome-picfhttps://github.com/sarome-picfhttps://github.com/sarome-picf Please make a Good Contribution if you want your changes to be merged to the main Branch 🤖 — Reply to this email directly, view it on GitHub<#6 (comment)https://github.com/aaron-muti-420/Int-Git-GitHub-Ops/pull/6#issuecomment-2264704106>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BD5NILG3XMMOVUNLESTYGKTZPMVDXAVCNFSM6AAAAABL27LYPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRUG4YDIMJQGY. You are receiving this because you were mentioned.Message ID: @.***>
Look at the Contribution Guides
—
Reply to this email directly, view it on GitHubhttps://github.com/aaron-muti-420/Int-Git-GitHub-Ops/pull/6#issuecomment-2264795388, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BD5NILENPPBIWFJZC5R6M53ZPM3SHAVCNFSM6AAAAABL27LYPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRUG44TKMZYHA.
You are receiving this because you were mentioned.Message ID: @.***>


Managing Secrets in a React Native App

🚧Draft 👷 ✏ 🚧
Soliciting feedback from new RN developers and old hats!
Don't know why .bundle/config changed!

Updated per comments - see the rich diff here
https://github.com/artsy/artsy.github.io/pull/458/commits/9ed4d5ab2270d2c4129e978f306fb3397560d994?short_path=248c3cf#diff-248c3cf12c35d1bc13e40b7d9008f340

Looks great! Ship it, I say 👍

merge on green


[WIP] Improved barcode options

This is a WIP of how I want to implement barcode specific options. It does also allow for the awful optionsFromStrings.js to be removed.
It is not done and does not yet work fully, but what do you think of the general idea @SanichKotikov ?

And please, do not forget about options for CODE128 :)

Of course I will not 😉 I just added EAN to test with and there is a lot of other options thats need to be added.


Sk model written evals

Added yaml for sycophancy evaluation in model-written-evals.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: baberabb:white_check_mark: lintangsutawika:x: y12uc231You have signed the CLA already but the status is still pending? Let us recheck it.


Preserve Back Button Navigation When Searching

Ajax request on each entered character in search field results in a new GET request that breaks back button navigation.  The page visited prior to searching should be preserved as the back button navigation target.

@iroskam Which page is this? could you take a screenshot?

In any preprints section.  This example shows my initial navigation to OSF from a new tab then to the Preprints.  Each of the "OSF Preprints | Search" histories were added as each character of "tallest" was entered into the search bar.

what browser are you using?


Add tests and ruff execution to GitHub Actions

To improve code quality and catch issues early, we should add the following to the GitHub Actions workflow:

Run tests: Ensure all tests are executed automatically on each push or pull request.
Ruff linting: Integrate ruff to enforce consistent code style and catch linting errors.

Goal: Update the GitHub Actions configuration to run both tests and ruff on each CI run.

It's a very great suggestion from @GabLeRoux. I can help you with this, by adding the necessary actions. Its also a good starter for me to start contributing to this cool project @Flexonze.

Most of the work is already done in #1 for this current issue, but here are some other ideas that will also improve this.

Add a build and publish step that will automatically do these things (when on a tag or a branch like release/x.x.x:
Execute the desired commands to prepare the package
Package the library
Create a Github Release with automatic description (we can use https://github.com/softprops/action-gh-release with generate_release_notes set to true, it works very well)
Publish the library on Pypy
Add an action that will automatically reply to the pull-request with coverage results (increase and decrease, etc.)
I think this one is good and allows doing it with coveralls https://github.com/marocchino/sticky-pull-request-comment

🙏

Hey @hammadarshad1! @GabLeRoux has already taken care of it, but your contribution is more than welcome! I've added a bunch of issues that would be useful if you want to take a look, or feel free to open your own issues. :smile:


Bakcup broken since ESPHome 2023.12

The contents of the backed up file is:
null
...

Also, the GPIO pin validation fails with this component added:
INFO ESPHome 2023.12.0b1
INFO Reading configuration /root/config/kazan-124.yaml...
INFO Generating C++ source...
INFO Reading configuration /root/config/kazan-124.yaml...
Failed config

binary_sensor.gpio: [source <unicode string>:157]

  Pin 5 is used in multiple places.
  platform: gpio
  pin:
    number: 5
    inverted: True
    mode:
      input: True
      pullup: True
      output: False
      open_drain: False
      pulldown: False
      analog: False
  name: Junkers betáp
  device_class: power
  id: power_active
  filters:
    - delayed_on: 300ms
    - delayed_off: 300ms
  disabled_by_default: False
light.status_led: [source <unicode string>:183]

  Pin 2 is used in multiple places.
  platform: status_led
  id: onboard_led
  internal: True
  pin:
    number: 2
    inverted: True
    mode:
      output: True
      input: False
      open_drain: False
      pullup: False
      pulldown: False
      analog: False
  disabled_by_default: False
  restore_mode: ALWAYS_OFF
  name: onboard_led
output.esp8266_pwm: [source <unicode string>:240]

  Pin 15 is used in multiple places.
  platform: esp8266_pwm
  id: pwm_output_hw
  pin:
    number: 15
    mode:
      output: True
      input: False
      open_drain: False
      pullup: False
      pulldown: False
      analog: False
    inverted: False
  frequency: 1000.0
  zero_means_zero: False
Pin 5 is used in multiple places

Pin 2 is used in multiple places

Pin 15 is used in multiple places

INFO Backup config will take: 29 bytes
INFO Compiling app...

Reference Discord: https://discord.com/channels/429907082951524364/1184783083048812616

true ... and "allow_other_uses: true" does not resolve the issue

Thanks for reporting. I will investigate it.

fixed


[vscode/webview] need a button on a particular violation to generate fix

this may already exist.
Definition of Done:

We expose a "generate fix" button in our webview after a user has performed an an analysis and is navigating. violations.

I think this one is nearly done. I think we need to update this to be "Get Solution" and connect it to our, not yet implemented, GetSolution function in the analyzerClient.
Could you confirm this @ibolton336 ?
Originally, I had thought we might want to make this button more plainly visible instead of under a kebab dropdown type menu but @sjd78 's wireframes had it there. You (@sjd78) still good with it being in the dropdown?

Additionally, I think this issue need to expand in it's scope. Instead of simply rendering or updating the button, I think it should cover the whole flow (from the webviews perspective) from:

The user clicks the "Generate Fix" or "Get Solution"...to
When the user "reconciles" the proposed solution(s).

This includes rendering/disabling user input into the webview while a solution is being retrieved AND preventing the user from proceeding until they have accepted/rejected/modified manually the proposed solution.

Done from #122


Missing JPE extension while trying to get images from the server

Why ImagePicka does not allow to choose extensions that are allowed ?
Would be nice to have JPE format accepted here as well.
I have some images I need to get, and there is no way to do this.

Currently, Image Picka detects image URL with image-extensions. See also: https://github.com/arthurvr/image-extensions/issues/37
I think it is not really useful to make the list configurable (it's a 123 lines list). Maybe we should just insert missing extensions to the list in Image Picka.

Maybe we should build our own list according to https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types