J-R and Ancestry, sitting in a tree...

This quote from the documentation

eager_load_on_include - if set to false, will not include this relationship in join SQL when requested via an include. You usually want to leave this on, but it will break ‘relationships’ which are not active record, for example if you want to expose a tree using the ancestry gem or similar, or the SQL query becomes too large to handle. Defaults to true if not set.

Suggests that someone has tried what I want to do, which is to explore an Ancestry-backed tree using this API. Links would include children (in the Ancestry sense of that term), the parent, etc.
Can anyone point me to an example of integrating these two gems?
Thanks!

Hey @walterdavis!
In order to connect with the rest of the community, you can access the Gitter chat channel, where questions are on-topic and welcome.
There's a question Label for Issues in this repository, but the chat channel has more interaction.
Good luck!

Hey @walterdavis, as the guy who wrote that bit, but who doesn't hang out on the chat channel, I figure I'd respond here.
The good news, is it basically works out the box if you set that flag. E.g I have it set up as such:
class Tree
  has_ancestry
end

class TreeResource < JSONAPI::Resource
  relationship :subtree, to: :many, eager_load_on_include: false
  relationship :children, to: :many, eager_load_on_include: false
  relationship :parent, to: :one, always_include_linkage_data: true, eager_load_on_include: false
end

Hope this helps!

This is brilliant, and much nicer than what I bodged together for a demo. I will be able to move ahead with real code now!
Walter

On Feb 27, 2017, at 3:34 PM, Hugh Barrigan<EMAIL_ADDRESS>wrote:
Hey @walterdavis, as the guy who wrote that bit, but who doesn't hang out on the chat channel, I figure I'd respond here.
The good news, is it basically works out the box if you set that flag. E.g I have it set up as such:
class Tree
has_ancestry
end
class TreeResource < JSONAPI::Resource
relationship :subtree, to: :many, eager_load_on_include: false
relationship :children, to: :many, eager_load_on_include: false
relationship :parent, to: :one, always_include_linkage_data: true, eager_load_on_include: false
end
Hope this helps!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Did you need to create additional resources for Child or Subtree? I am getting an error at startup when I try to duplicate your technique above. JSONAPI: Could not find resource 'child'. (Class ChildResource not found) (NameError). I feel like I'm missing something in my understanding of how these two gems want to work together.

Oh, my bad, it'll get confused about the actual type, you need to do:
class Tree
  has_ancestry
end

class TreeResource < JSONAPI::Resource
  relationship :subtree, to: :many, eager_load_on_include: false, class_name: "Tree"
  relationship :children, to: :many, eager_load_on_include: false, class_name: "Tree"
  relationship :parent, to: :one, always_include_linkage_data: true, eager_load_on_include: false, class_name: "Tree"
end

Thanks. That works perfectly.


(generateTagsFromPublicFiles) Apple Touch Icon being used for browser icon.

Describe the bug
My favicon and icons have transparent backgrounds.
My apple touch icon (and manifest.json icon) have a cyan background.
Nuxt SEO experiments adds my apple-touch-icon.png as a browser icon, with the image in the head twice (with rel="icon" and rel="apple-touch-icon").
It looks like this area is causing the bug:
https://github.com/harlan-zw/nuxt-seo-experiments/blob/main/src/features/generateTagsFromPublicFiles.ts#L31
^ The file (apple-touch-icon.png) includes the text "icon" and the text "apple-touch-icon" so it's pushed twice.
(I'm not adding a reproduction, since it seems like the link above shows the error well, although, if request I can add reproduction)
A good solution might be making the selectors a field in nuxt.config.ts, or by excluding the apple touch icon from icons.
Reproduction
No response
System / Nuxt Info
- Operating System: Windows_NT
- Node Version:     v18.15.0
- Nuxt Version:     3.8.0
- CLI Version:      3.9.1
- Nitro Version:    2.7.0
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      modules, runtimeConfig, devServer, devtools, app, primevue, pwa, site, robots, sitemap, routeRules, seoExperiments, linkChecker, ogImage, googleFonts, turnstile, security, vite, plugins, css, build, tailwindcss, auth
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -

I'll go make a pull request.


CSS

CSS
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
So that I can easilt find and read the information
Acceptance criteria
GIVEN a Prework study guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow.

Added CSS styling
Added info for CSS section in the HTML page
Linked CSS and HTML


Bug: Link to PR velocity term in the Dev card section leads to "Page Not Found"

Describe the bug
The link for the PR velocity term is incorrect in the Dev Card section and it shows extra unnecessary path information.

Solution
Remove the  extra(../../docs/welcome/glossary/#pr-velocity.md) and fix the path to the PR velocity link.
Here is the markdown file that needs fixing
https://github.com/open-sauced/docs/blob/main/docs/features/dev-card.md
Steps to reproduce

Go to the Dev Card feature section
Click on the link in the first paragraph
It will open a "Page Not Found"

Browsers
No response
Additional context (Is this in dev or production?)
production
Code of Conduct

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

Contributing Docs

[X] I agree to follow this project's Contribution Docs

.take

I'm interested in doing this. Can you assign me


Support for AWS c5 instances

https://aws.amazon.com/about-aws/whats-new/2017/11/introducing-amazon-ec2-c5-instances-the-next-generation-of-compute-optimized-instances/

@vinceprignano Thanks! We'll create an internal JIRA to add this to the next release. In the meantime, you can add c5 instances to your mapping files.
https://www.cloudera.com/documentation/director/latest/topics/director_aws_new_instance_types.html#xd_583c10bfdbd326ba-590cb1d1-149e9ca9886--6f9f

Thanks!


[Spring-Cloud] Add support for connection_string for those commands in preview

Change Description:

New Feature:

For spring-cloud create, support connection_string only when enable-java-agent is enabled
For spring-cloud update, only support instrumentation_key
For spring-cloud app-insights update, support connection_string

Bug Fixing:

remove duplicated and never-reach code
fix bug for set zero for sampling_rate

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Spring-Cloud


JOSS submission

https://joss.readthedocs.io/en/latest/example_paper.html

https://github.com/openjournals/joss-reviews/issues/7032#issuecomment-2250162055


Fix STA Query Parsing

Fixes bugs in Query Lexing/Parsing
Add contains() method to filter on Observation->parameters

I would also need a maven release asap once approved :)


Error on Node.JS 6.3.0

Special hotfix for that error:
<PATH-TO-PROJECT>/node_modules/knex/lib/index.js:46
  if (arguments.length === 0 || !config.client && !config.dialect) {
                                       ^

TypeError: Cannot read property 'client' of undefined
    at Knex (/home/user/Projects/yield-active-record/node_modules/knex/lib/index.js:46:40)
    at Object.getInstance (/home/user/Projects/yield-active-record/classes/db-socket.js:36:21)
    at Object.<anonymous> (/home/user/Projects/yield-active-record/classes/active-record.js:13:31)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/user/Projects/yield-active-record/index.js:5:5)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)

How does this error happens only in node 6.3.0? Also I wouldn't like to just patch config to be empty if it is not given. I would rather throw an error in that case. Also this would need test case. Let me know if you are going to make proper fix for the issue and I'll reopen the pull request.

I reproduce this error on Node.JS 4.2.1 and Node.JS 6.3.0. How to reproduce:

Create an empty Node.JS Package: (npm init);
Install "knex" from npm: npm install knex --save;
Create an executable JS-file which requires "knex":

I've founded cause from problem, and sorry for disturbing


Override setting search_path and NAMES on every connection to avoid connection pinning with RDS Proxy

Problem
Not sure where this belongs so I am referencing this as a feature request here. Apologies if that's not right.
https://github.com/prisma/prisma-engines/issues/1692
Setting search_path and NAMES for every new connection causes connections to be pinned with RDS Proxy.
Suggested solution
An option to ignore/skip setting these for every connection by overriding the connection behaviour.
Additional context
https://github.com/prisma/prisma-engines/issues/1692

Yep, I moved that other issue over here so that one will be enough to be looked into.


Use compact prompt when generating requests via Claude 3.5

this pr adds a slim version of system prompt for ai request generation and a suite of tests to evaluate its effects on the results (using goose-quotes from examples). as running these on each commit would be rather expensive and claude api is not fully deterministic at temp=0, they are not run by default, but instructions are provided inside the test.

noice - just looked over the prompt changes, will test locally tomorra

haven't fully finished the vibe check, but one thing i did notice is that it's a little flaky with query params now?
tested on a few routes in goose quotes that accepted query params and every once in a while it would add them, but most of the time not.
old prompt always adds query params fwiw.
other notes:

It's not taking much of a cue from the request history. If i just created a resource, it doesn't use the ID of that resource. However, this problem already appears to happen in the status quo with claude 👀 so not a regression. i think it might have to do with how chunky the history of requests is

It correctly determined multipart form data for a request! Wild

Hono url encoded forms were hard to sniff out, but i also think that's an existing problem

Will keep testing a bit more this eve

separate question: you said you tested on our data we'd collected from our internal honcathons. do you have scripts available for those tests? how did you go about that?

oh also! one more thing. it does tend to add the fpx-trace-id header into requests, which is a no-no. should probably add that instruction back to the system prompt

i had a bit in prompt to emphasize reusing the data from history, wasnt sure if that would be preferable so i left it out, will put it back. the fpx-trace-id is being added because we include it in history of requests, probably will disappear if we filter the headers there
i used https://github.com/actualwitch/experiment to explore the csv with our honcathon data

i have modified the inference logic to remove trace header from history entries, so it shouldn't be resurfacing in responses anymore. i also added a bit to integrate previous requests data, so that should be resolved too


Gateway v6

Currently, we support only Gateway v5. Specifying v6 in client config introduces some subtle problems.
What should be done:

[x] Remove the gateway version switch - introduces problems and doesn't actually help
[ ] Properly implement GWv6

All work should happen on a new branch.

Gateway v6 isn't officially released yet though..

Technically, it is. Still, this is something to investigate.

@Rapptz gave me this: https://github.com/Rapptz/discord.py/commit/ddd3fd0a3dcce2d48b2df26377e136f2310809b3
It should help.

Basics are implemented. Remaining features are to be considered:

Call messages https://github.com/Rapptz/discord.py/commit/bd39c3ef458e7b78e1e4d49367544a04ab764131
System message types (group DM only) https://github.com/Rapptz/discord.py/commit/a128249b6324dd045561cb0be85cdabf8acd7694
Better handling for group DM channel updates https://github.com/Rapptz/discord.py/commit/69c506d7aeb9f1a0a6f711b7b8c144f8b554b0d7

Closing for now.


Can you include the real robot evaluation code?

I'd like to run with real robot but I cannot find the code. The original diffusion policy includes a real_world folder and eva_real_robot.py. How these can be used? Thanks.

Hi @bobd988 ,
Thanks for your interest in our work.
We did not include the real-world robot code as it is very specialized for our hardware setup. In principle, our code can be evaluated in the same way as diffusion policy in eval_real_robot.py
Best,


Move helm version to 3.x in install-helm.sh

Helm v3 no longer requires any in cluster components (like tiller) and makes it quite easy to use as a deployment mechanism (no kubernetes components need to be deployed). I suggest that we shift to the same to make the script easier to maintain.
For helm v3 the install command for any chart needs to change like so,
-    "${HELM}" install "${SCRIPT_DIR}"/../charts/ceph-csi-cephfs --name ${CEPHFS_CHART_NAME} --namespace ${NAMESPACE} --set provisioner.fullnameOverride=csi-cephfsplugin-provisioner --set nodeplugin.fullnameOverride=csi-cephfsplugin --set configMapName=ceph-csi-config --set provisioner.podSecurityPolicy.enabled=true --set nodeplugin.podSecurityPolicy.enabled=true
+    "${HELM}" install --namespace ${NAMESPACE} --set provisioner.fullnameOverride=csi-cephfsplugin-provisioner --set nodeplugin.fullnameOverride=csi-cephfsplugin --set configMapName=ceph-csi-config --set provisioner.podSecurityPolicy.enabled=true --set nodeplugin.podSecurityPolicy.enabled=true ${CEPHFS_CHART_NAME} "${SCRIPT_DIR}"/../charts/ceph-csi-cephfs

IOW, no --name parameter and also the chart path and name move to the end of the CLI.
I would suggest that we change the script to require v3 as the minimum and not write code to support both, as the intent is to keep the code simpler with this change.

Sure it's nice to have thanks @ShyamsundarR


Add weighting options

Add options to allow weighting of data (see comment on Mathworks FX, 28 Feb 2016).

Completed.


Add GNUInstallDirs and USE_AUDIO/USE_WAYLAND options to CMake

include GNUInstallDirs so it can be used for multilib builds (i.e. ABI_X86 64, 32, x32) , so lib/ dir is not hardcoded
add USE_AUDIO option so raylib can be built without alsa on Linux, as supported in Makefile
adds USE_WAYLAND option so raylib can be built with Wayland support

This unearthed a small issue: A full CMake build including examples would fail, because it tries to build the audio_* examples.

@gen2brain Should the pkg-config file be installed to ${CMAKE_INSTALL_LIBDIR}/pkgconfig as well?
(For future (cross-)reference: This PR relates to issue #517)


Is it possible to determine domain name for VM from CS?

It may be possible to get from CS API domain name of VM like vm-name. Actually it might be specified for zone, but please check if it's possible to get it from zone information.

If it's possible, then add FQDN domain name to VM details


fix: bug where operationName was pushed as label but did not exist

Summary
Prometheus has issues with cardinality where metrics with many labels causes a large number of data points and impacts performance, for this reason its generally good practice not to include unbounded labels in metrics.
This PR addresses two issues:

A bug in the plugin where if operationName was not added as a label the server errors on requests.
Remove metrics that will result in a label cardinality issue.

This does mean, url, statusText, http headers will no longer be labels in metrics.

Hi!
Thanks for the PR!
You can generate graphiql html file by running pnpm build.

The title says it is a fix, the changeset says it is a patch :) but this PR has a lot of breaking changes so it needs a major release in that case.

The title says it is a fix, the changeset says it is a patch :) but this PR has a lot of breaking changes so it needs a major release in that case.
@ardatan  yea my bad I changed the implementation after making the PR, its all updated now.


[MM-34353] Migrate 'components/status_dropdown' and associated tests to TypeScript

Summary
This code migrate "components/status_dropdown" component to TypeScript.
Ticket Link
Jira card: https://mattermost.atlassian.net/browse/MM-34353
Github issue: https://github.com/mattermost/mattermost-server/issues/17283
Release Note
- Refactor component to typescript, no changes in UI

Hello @arvinDarmawan,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

/update-branch

Error trying to update the PR.
Please do it manually.

Hello @arvinDarmawan can you please check the error and update to latest master? Thanks

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

@arvinDarmawan Let us know if you need any assistance with this PR.

@arvinDarmawan Let us know if you need any assistance with this PR.

Hi @devinbinnie , I already update the MR since the old MR (which already reviewed)  have several conflicts

Hi, maybe CodeQL / Analyze (javascript)  must be retried  since it's cancelled automatically on github


[SPM] Update GoogleUtils version dependency

Needs re-tag after merge.

re-running CI now that GoogleUtils v8 is released


Implement 100 Member LLMQ to be used by Dash Platform

Implement 100 Member LLMQ to be used by Dash Platform
Benefits of implementing a new LLMQ
Quorum size is 100 instead of 50 so:

Better protection from DoS
Lower possibility of having more than ⅓ low latency or offline nodes.
More secured consensus, much harder to achieve majority for malicious nodes

Validation workload distributed more evenly among network
Do not disturb IS lock process by utilizing the same LLMQ
LLMQ Parameters
type
4
name
llmq_100_67
size
100
This should hit the balance between performance and security for the launch of Dash platform. If we succeed to significantly reduce the block time by consensus optimisations we will reconsider the quorum size. The desire to raise the validator set’s size stems from both concerns with DDos protection and work load distribution.
minSize
90
threshold
Maybe better to set it to 67 to be BFT compatible (>=67/<33). Or we could stick with the normal LLMQ thresholds of 60 (>=60/<=40).
dkgInterval
24
The number of blocks between two DKG sessions. If set to 576 for example, a new DKG session will start once per day. This depends on how quick we want to have new validator quorums form. Probably should be 24 like with IS quorums for simplicity.
dkgPhaseBlocks
2
Number of blocks a single DKG phase is active. It must be high enough to allow all members to exchange all required messages. It must also be high enough to take block time variances into account. Minimum seems to be 2.
dkgMiningWindowStart
10 (not defined by platform team)
dkgMiningWindowEnd
18 (not defined by platform team)
dkgBadVotesThreshold
80
Important for PoSe. Threshold for votes on bad members. If >=dkgBadVotesThreshold members have voted on another member to be bad, that member is also considered bad locally. Should be between 75% - 85%. So maybe 80 would be a good number.
signingActiveQuorumCount
24
keepOldConnections
I'm not really sure about this value (and it wasn't defined by platform team) so we need to figure out what a proper value would be. llmq_50_60 is 25, llmq_400_60 is 5
recoveryMembers
50 (not defined by platform team)
I'm also not really sure about this value...
Activation
I believe this will need to be activated via a BIP9 style hard fork

The LLMQ types table in DIP 6 should be updated to add this new quorum once it has been implemented.

@thephez Would you like to do so?


time must be a Fluent::EventTime (or Integer): Float

My stack:

fluentd 0.14.6
gem install json_pure fluent-plugin-loggly

My config:

accept fluent's own protocol over tcp
sender is Python + fluent-logger
buffered, bulk upload to loggly

Error:
fluentd_1  | 2016-09-09 07:51:17 +0000 http: {"module":"misc","level":"INFO","function":"on_get","thread_name":"MainThread","domain":null,"tid":42,"source":"misc.py:36","message":"Serving an empty response","thread":140138439919360,"pid":23,"user":null,"request_id":"V9Jp9awSAAYAAAAJftUAAACA"}
fluentd_1  | 2016-09-09 07:51:17 +0000 [warn]: emit transaction failed: error_class=ArgumentError error="time must be a Fluent::EventTime (or Integer): Float" tag="http"
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/output.rb:561:in `metadata'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/output.rb:659:in `block in handle_stream_with_custom_format'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/event.rb:100:in `each'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/output.rb:658:in `handle_stream_with_custom_format'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/output.rb:602:in `execute_chunking'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/output.rb:544:in `emit_buffered'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/out_copy.rb:38:in `block in process'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/out_copy.rb:37:in `each'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/out_copy.rb:37:in `process'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/multi_output.rb:89:in `emit_sync'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/event_router.rb:153:in `emit_events'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/event_router.rb:90:in `emit_stream'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/event_router.rb:81:in `emit'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:376:in `on_message'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:231:in `block in handle_connection'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:272:in `block (3 levels) in read_messages'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:271:in `feed_each'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:271:in `block (2 levels) in read_messages'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:280:in `block in read_messages'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:559:in `on_read'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/cool.io-1.4.5/lib/cool.io/io.rb:123:in `on_readable'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/cool.io-1.4.5/lib/cool.io/io.rb:186:in `on_readable'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/cool.io-1.4.5/lib/cool.io/loop.rb:88:in `run_once'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/cool.io-1.4.5/lib/cool.io/loop.rb:88:in `run'
fluentd_1  |   2016-09-09 07:51:17 +0000 [warn]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.6/lib/fluent/plugin/in_forward.rb:190:in `run'
fluentd_1  | 2016-09-09 07:51:17 +0000 [error]: unexpected error on reading data from client address="<IP_ADDRESS>" error_class=ArgumentError error="time must be a Fluent::EventTime (or Integer): Float"

It's partially my responsibility, because I forced a float to .emit_with_time().
My intention was to get fluentd to process timestamp with millisecond granularity.
If I should, in fact use some other data format (a tuple?) please let me know, I can try to come up with a patch against https://github.com/fluent/fluent-logger-python

My intention was to get fluentd to process timestamp with millisecond granularity.

Fluentd's event time is nano-second granularity since v0.14.
Each language loggers should support it in the future, not float for millisecond.

Ok, what is the binary, msgpack format for nanosecond timestamp?

EventTime ext format specification will help you: https://github.com/fluent/fluentd/wiki/Forward-Protocol-Specification-v1#eventtime-ext-format

Thanks, I'll hack up a merge request against python bindings if functionality is not there yet.

https://github.com/fluent/fluent-logger-python/pull/61 :-)

Should be handled by other plugins

Consider that per https://github.com/fluent/fluent-logger-python/pull/61#issuecomment-245987200 plugins cannot simply send new protocol version.
0.12.x handled float in this field (it truncated value to int and accepted the message).
I believe that 0.14.x needs to accept messages with float too, either by truncating to int like before, or by converting float to EventTime internally.

Fluentd v0.12's behavior about floating point numerics are undocumented, and out of support.
It's unexpected result of calling to_i for any objects, including Float values, when needed. It's not limited for float.
You can write filter plugins to convert float into any objects, using Filter#filter_with_time method of Fluentd v0.14. But it can't be supported by Fluentd because of performance reason.

Well guys, it's up to you.
From end-user perspective it's a regression --- this weird stuff we used to do breaks when we upgrade only fluentd in our system.
Perhaps you can get by with documenting this fact, e.g.:

Backwards compatibility notes:
Fluentd 0.14 and later is stricter with incoming data if you use its own protocol.
If you are using xxx, yyy or zzz, please test before deployment.


Run the deploy script locally for Vercel preview build

Issue Number
N/A
Purpose/Implementation Notes
Ran the sitemap deploy scripts locally to generate the latest sitemap files to prevent Vercel from executing them on each preview deploy per commit.
Reason: The sitemap files were older than 30 days. Also, just in case, I temporarily increased the day value to 60 for development.
@davidsmejia Could you please approve this PR right away? It includes the latest generated sitemap files for Vercel preview build, thank you!
Vercel build log:

Types of changes

Bugfix (non-breaking change which fixes an issue)

Checklist

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

a ticket to revert the 60 day setting.

#314


[1.12.2] 3 little bugs (Wireless Energy)

Minecraft version & Mod Version:
1.12.2 - MC
1.12.2 - <IP_ADDRESS>27 Forge
1.12.2 - 1.16.0 Cyclic
Single player or Server:
Singleplayer
Describe problem (what you were doing / what happened):

You can see in the left corner the TOP display with a full RF bar, but in your GUI from the energy transfer Node is nothing aka its empty. (Edit: after a relog the bar is filled)

You can see in the chat "tile.thermalexpansion.machine.name", this occurs if I press the "Detect target block" Button. Connected to this GPS marker is a "Redstone Furnace"

After a relog, the "transfer Rate" slider reset to 500

Crash log (if any):
Nope

Thanks for the bug reports ill get these fixed up soon

In my test it seems like TOP is working ok so far, but ill dig into it a bit more . This was with TOP  1.4.23 and forge <IP_ADDRESS>55

TOP worked good, it was just a refresh rate bug in your GUI from the Energy Transfer Node. (Its like Immersive Engineering, first look in the machine = no energy, close GUI and open it again = full energy)

Oh i see. so ill try reloading the world and NOT opening GUI to replicate that part, hopefully its an easy fix for next version
Bugs 2 and 3 fixed in this version  https://minecraft.curseforge.com/projects/cyclic/files/2581557

Thx


v2.0.0 fails to run programs

I've updated to the latest 2.0.0 version but I can't run any programs anymore.
Here is the error I have in logs:
[PMC] (cc) Unable to execute the command
execvp: No such file or directory

It's working perfectly fine on version 1.9.0
pmc is running on an ARMv8 architecture.

Should have force updated $HOME/.pmc/config.toml as the shell now uses absolute paths, sorry about that. The fix should be setting "bash" to "/bin/bash"

Thanks for the prompt answer.
I've modified bash to /bin/bash in $HOME/.pmc/config.toml and now it works.
Thank you for your work! Awesome tool.

https://github.com/theMackabu/pmc/commit/ccea28ea3feb10ec2eaaa23b82def71772efcd1c added a warning with this commit


[Synapse] az synapse sql screate: add parameter "collation"

Related command

Description

az synapse sql screate: add parameter "collation" to support collation.
Testing Guide

History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Synapse


chapter 8 nginx config and site access

Hi @nickjj
Can you add some instructions to the book to access the staging server in chapter 8? i.e. should it be possible to access the site?
I see that the Vagrantfile defines '80' => '8080' and '443' => '8081' port mappings.
I've tried:
wget http://<IP_ADDRESS>:8080
--2015-11-19 21:28:16--  http://<IP_ADDRESS>:8080/
Connecting to <IP_ADDRESS>:8080... connected.
HTTP request sent, awaiting response... 307 Temporary Redirect
Location: https://<IP_ADDRESS>/ [following]
--2015-11-19 21:28:16--  https://<IP_ADDRESS>/
Connecting to <IP_ADDRESS>:443... failed: Connection refused.

which is fair enough, the nginx conf redirects the user to 443 which is not in use because that's been mapped to 8081.
However attempting to get to the SSL version via 8081 also gives me an error:
wget --no-check-certificate https://<IP_ADDRESS>:8081
--2015-11-19 21:24:29--  https://<IP_ADDRESS>:8081/
Connecting to <IP_ADDRESS>:8081... connected.
WARNING: cannot verify <IP_ADDRESS>'s certificate, issued by '/C=US/ST=NewYork/L=NewYork/O=IT/CN=fakerediscounter.com’:
  Self-signed certificate encountered.
    WARNING: certificate common name 'fakerediscounter.com’ doesn't match requested host name '<IP_ADDRESS>’.
HTTP request sent, awaiting response... 502 Bad Gateway
2015-11-19 21:24:29 ERROR 502: Bad Gateway.

In CoreOS guest the nginx journalctl log is:
Nov 19 10:24:29 core-01 docker[957]: 2015/11/19 10:24:29 [error] 10#10: *5 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: yourrealdomain.com, request: "GET / HTTP/1.1", upstream: "http://<IP_ADDRESS>:8000/", host: "<IP_ADDRESS>:8081"
Nov 19 10:24:29 core-01 docker[957]: <IP_ADDRESS> - - [19/Nov/2015:10:24:29 +0000] "GET / HTTP/1.1" 502 166 "-" "Wget/1.15 (linux-gnu)"
Nov 19 10:28:16 core-01 docker[957]: <IP_ADDRESS> - - [19/Nov/2015:10:28:16 +0000] "GET / HTTP/1.1" 307 180 "-" "Wget/1.15 (linux-gnu)"

Worked it out, this line needs to be 8080:
https://github.com/nickjj/deploy-web-apps-with-docker/blob/master/chapter-8/deploy/nginx/configs/default.conf#L3
all good

Hmm, line 3 of that config shouldn't need to be 8080. nginx is your gateway to the web app.
Vagrant is forwarding those ports because you can't listen on 80 and 443 without root so I forwarded them to something higher.
In your Vagrantfile do you have these values defined? https://github.com/nickjj/deploy-web-apps-with-docker/blob/master/chapter-9/deploy/nginx/docker-entrypoint#L7-L8

My app.py has port 8080 in it, so setting upstream to 8080 worked for me fine. I'm not sure how my app.py drifted away from yours (8000). Anyway it's fine thanks. Now onto the next chapter!


Any release date for new version?

Hello!
First of all thank you for this great project. I can't wait to use new version of whixp.
I'm developing a chat application so after a bit search i decided to use this package. But i want to wait to first stable release of whixp.
So, is there any decided date to release new version?

Just published a new version of the package, but it is not stable yet. Please consider this when you are using the package and if there is any bug or enhancement recommendation, please do not hesitate to open an issue.


Debugging Docker API request parameters and errors

I faced with a situation when a third-party software (Cocaine with Docker plugin) is trying to start docker containers in the wrong way. I ran the docker daemon in debug mode and called some Cocaine client command that should lead to creation and start of the container with a cloud application. Here is what I see in logs (Docker 1.5.0 on Ubuntu 14.10):
time="2015-03-27T13:21:31+03:00" level="debug" msg="Calling POST /containers/create"
time="2015-03-27T13:21:31+03:00" level="info" msg="POST /v1.14/containers/create"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job create()"
Your kernel does not support swap limit capabilities. Limitation discarded.
time="2015-03-27T13:21:31+03:00" level="info" msg="+job log(create, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job log(create, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job create() = OK (0)"
time="2015-03-27T13:21:31+03:00" level="debug" msg="Calling POST /containers/{name:.*}/start"
time="2015-03-27T13:21:31+03:00" level="info" msg="POST /v1.14/containers/c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306/start"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job start(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job allocate_interface(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job allocate_interface(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="info" msg="WARNING: Your kernel does not support swap limit capabilities. Limitation discarded."
time="2015-03-27T13:21:31+03:00" level="info" msg="+job log(start, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job log(start, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="debug" msg="Calling GET /containers/{name:.*}/json"
time="2015-03-27T13:21:31+03:00" level="info" msg="GET /containers/c84042da2f/json"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job container_inspect(c84042da2f)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job start(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job container_inspect(c84042da2f) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="debug" msg="Calling POST /containers/{name:.*}/attach"
time="2015-03-27T13:21:31+03:00" level="info" msg="POST /v1.14/containers/c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306/attach?logs=1&stream=1&stdout=1&stderr=1"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job container_inspect(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job container_inspect(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job attach(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:31+03:00" level="debug" msg="attach: stdout: begin"
time="2015-03-27T13:21:31+03:00" level="debug" msg="attach: stderr: begin"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job log(die, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job log(die, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="info" msg="+job release_interface(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job release_interface(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"
time="2015-03-27T13:21:31+03:00" level="debug" msg="attach: stdout: end"
time="2015-03-27T13:21:31+03:00" level="debug" msg="attach: stderr: end"
time="2015-03-27T13:21:31+03:00" level="info" msg="-job attach(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"
time="2015-03-27T13:21:41+03:00" level="debug" msg="Calling POST /containers/{name:.*}/kill"
time="2015-03-27T13:21:41+03:00" level="info" msg="POST /v1.14/containers/c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306/kill"
time="2015-03-27T13:21:41+03:00" level="info" msg="+job kill(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:41+03:00" level="info" msg="+job log(kill, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest)"
time="2015-03-27T13:21:41+03:00" level="info" msg="-job log(kill, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest) = OK (0)"
time="2015-03-27T13:21:41+03:00" level="info" msg="-job kill(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"
time="2015-03-27T13:21:41+03:00" level="debug" msg="Calling DELETE /containers/{name:.*}"
time="2015-03-27T13:21:41+03:00" level="info" msg="DELETE /v1.14/containers/c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306?v=0"
time="2015-03-27T13:21:41+03:00" level="info" msg="+job rm(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306)"
time="2015-03-27T13:21:41+03:00" level="info" msg="+job log(destroy, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest)"
time="2015-03-27T13:21:41+03:00" level="info" msg="-job log(destroy, c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306, <IP_ADDRESS>:5000/id-session:latest) = OK (0)"
time="2015-03-27T13:21:41+03:00" level="info" msg="-job rm(c84042da2fe4ecd6d73c203ca01c5f22e2c4e3a33ab7cb0489f1a5a4a200e306) = OK (0)"

In case if I run the same client command once again, I see another error:
time="2015-03-27T13:24:04+03:00" level="info" msg="+job release_interface(09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7)"
time="2015-03-27T13:24:04+03:00" level="info" msg="-job release_interface(09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7) = OK (0)"
time="2015-03-27T13:24:04+03:00" level="info" msg="+job log(die, 09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7, <IP_ADDRESS>:5000/id-session:latest)"
time="2015-03-27T13:24:04+03:00" level="info" msg="-job log(die, 09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7, <IP_ADDRESS>:5000/id-session:latest) = OK (0)"
Cannot start container 09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7: Invalid volume specification: var/run/run/co
time="2015-03-27T13:24:04+03:00" level="info" msg="-job start(09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7) = ERR (1)"
time="2015-03-27T13:24:04+03:00" level="error" msg="Handler for POST /containers/{name:.*}/start returned error: Cannot start container 09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7: Invalid volume specification: \x00var/run\x02\x00\x00\x00\x00\x00\x00\x00\x01/run/co\x01\x00\x00\x00\x00"
time="2015-03-27T13:24:04+03:00" level="error" msg="HTTP Error: statusCode=500 Cannot start container 09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7: Invalid volume specification: \x00var/run\x02\x00\x00\x00\x00\x00\x00\x00\x01/run/co\x01\x00\x00\x00\x00"
time="2015-03-27T13:24:04+03:00" level="debug" msg="Calling POST /containers/{name:.*}/kill"

Unfortunately request parameters are lacking in these logs (even with a --log-level="debug").
I guess that these errors are not Docker-specific, but I need additional information on what exactly was happened on the side of Docker daemon. Since Cocaine Docker plugin is written in C++, it's quite difficult to check what parameters were actually passed on the client side.
So I wonder:

What techniques should I use in order to get the parameters of the requests incoming to the Docker REST API;
How can I treat strings looks like that (see below)? How can I find the reason of code 500?

time="2015-03-27T13:24:04+03:00" level="error" msg="HTTP Error: statusCode=500 Cannot start container 09f52e575b52d2b7b62d3fec2ce550800a2102dd04b0ec000136fffc80f100f7: Invalid volume specification: \x00var/run\x02\x00\x00\x00\x00\x00\x00\x00\x01/run/co\x01\x00\x00\x00\x00"

Any help will be appreciated.

The simplest solution I can think of is to run a nginx proxy in front of the docker daemon and log all the requests.
location / {
  proxy_pass http://localhost:2376
}

Look at the logs generated by nginx for the params being passed

@ankushagarwal thanks for a good advice. I've ended up with this:
sudo su
cd /var/run
mv docker.sock docker.sock.orig
socat -v UNIX-LISTEN:/var/run/docker.sock,group=docker,perm=0660,reuseaddr,fork UNIX-CONNECT:/var/run/docker.sock.orig


Run alluxio-start.sh local without SSH

Fix #9185
After this PR running $ bin/alluxio-start.sh local with SSH  disabled on my local laptop:
[10:01:40]binfan@:alluxio (smallfix2)$ bin/alluxio-start.sh local
Assuming NoMount by default.
Killed 1 processes on MacBook-Pro-5
Killed 1 processes on MacBook-Pro-5
Killed 1 processes on MacBook-Pro-5
Killed 1 processes on MacBook-Pro-5
Killed 0 processes on MacBook-Pro-5
Killed 1 processes on MacBook-Pro-5
Starting master @ MacBook-Pro-5. Logging to /Users/binfan/Dropbox/Work/alluxio/alluxio/logs
Starting job master @ MacBook-Pro-5. Logging to /Users/binfan/Dropbox/Work/alluxio/alluxio/logs
Starting worker @ MacBook-Pro-5. Logging to /Users/binfan/Dropbox/Work/alluxio/alluxio/logs
Starting job worker @ MacBook-Pro-5. Logging to /Users/binfan/Dropbox/Work/alluxio/alluxio/logs
Starting proxy @ MacBook-Pro-5. Logging to /Users/binfan/Dropbox/Work/alluxio/alluxio/logs
-----------------------------------------
Starting to monitor all local services.
-----------------------------------------
--- [ OK ] The master service @ MacBook-Pro-5 is in a healthy state.
--- [ OK ] The job_master service @ MacBook-Pro-5 is in a healthy state.
--- [ OK ] The worker service @ MacBook-Pro-5 is in a healthy state.
--- [ OK ] The job_worker service @ MacBook-Pro-5 is in a healthy state.
--- [ OK ] The proxy service @ MacBook-Pro-5 is in a healthy state.
[10:02:30]binfan@:alluxio (smallfix2)$ jps
3953 AlluxioJobMaster
3956 AlluxioWorker
1940
3958 AlluxioJobWorker
3926 AlluxioMaster
3960 AlluxioProxy
4013 Jps

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4052/
Test PASSed.

@apc999 Any way to make cli work after running alluxio-start.sh local? The problem is the CLI needs master hostname as well.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.0 please.


OCIS binary ignores PHOENIX_* env vars

See https://github.com/owncloud/ocis/issues/450#issuecomment-673397996
It appears that despite using the PHOENIX_ env vars, the ocis-phoenix still has side effects.
to verify, I ran PHOENIX_ASSET_PATH=~/work/workspace/ PHOENIX_WEB_CONFIG=~/work/workspace/phoenix/config-ocis.json OCIS_LOG_LEVEL=debug bin/ocis-debug --log-level=debug server > /var/tmp/ocis/ocis.log 2>&1 where there's no Phoenix in the ASSET_PATH.
=> the UI still renders..
so this means those env variables are not used at all...
in the past I believe I've usually set those while running ocis-phoenix, not ocis...
we should fix this...

Addressed in https://github.com/owncloud/ocis-phoenix/pull/76 and https://github.com/owncloud/ocis-phoenix/pull/77.

Already closing, since https://github.com/owncloud/ocis-phoenix/pull/76 is merged and was the critical one. Missing config was already shown in the web ui. https://github.com/owncloud/ocis-phoenix/pull/77 only aligns the service behaviour for an invalid config path with the one for an invalid asset path.


Modifying zshrc causes other commands to behave incorrectly

Describe the bug
Some commands behave strangely.
$ bat .tool-versions
[bat error]: Could not parse pager command.

$ echo $PAGER
bat"

To see a list of supported npm commands, run:
  npm help:/Users/kentaro/.yarn/bin:/Users/kentaro/bin:/Users/kentaro/.yarn/bin

To Reproduce
# environment
Apple M1 Pro
maxOs: 13.6（22G120）

$ brew install rtx

# .zshrc
...
export PAGER='bat'
...
eval "$(/opt/homebrew/bin/rtx activate zsh)"

bat works correctly after comment out eval "$(/opt/homebrew/bin/rtx activate zsh)" and $ source .zshrc
Expected behavior
bat works correctly
rtx doctor output
rtx version:
  2023.9.1 macos-arm64 (c6d59d7 2023-09-13)

build:
  Target: aarch64-apple-darwin
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Wed, 13 Sep 2023 14:18:58 +0000
  Rust Version: rustc 1.72.0 (5680fa18f 2023-08-23)
  Profile: release

shell:
  /bin/zsh
  zsh 5.9 (x86_64-apple-darwin22.0)

rtx data directory:
  /Users/kentaro/.local/share/rtx

rtx environment variables:
  RTX_SHELL=zsh

settings:
  {"always_keep_download": "false", "always_keep_install": "false", "asdf_compat": "false", "disable_default_shorthands": "false", "disable_tools": "[]", "experimental": "false", "jobs": "4", "legacy_version_file": "true", "legacy_version_file_disable_tools": "[]", "log_level": "INFO", "missing_runtime_behavior": "warn", "plugin_autoupdate_last_check_duration": "10080", "raw": "false", "trusted_config_paths": "[]", "verbose": "false", "yes": "false"}

config files:
  /Users/kentaro/.tool-versions

plugins:
  deno        https://github.com/asdf-community/asdf-deno.git#0e14a50
  go          (core)
  java        (core)
  node        (core)
  python      (core)
  ruby        (core)
  rust        https://github.com/code-lever/asdf-rust.git#95acf4f
  terraform   https://github.com/asdf-community/asdf-hashicorp.git#0346f5d

toolset:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
No problems found

I have no idea what would've cause this:
$ echo $PAGER
bat"

To see a list of supported npm commands, run:
  npm help:/Users/kentaro/.yarn/bin:/Users/kentaro/bin:/Users/kentaro/.yarn/bin

I can't make sense of that but it appears to be the issue. Given the age of this I'm going to close but let me know if it's still happening.


Compiler allows exporting type abbreviations that mention private types

(Moved from https://github.com/fsharp/fsharp/issues/572)
The compiler doesn't currently prevent you exporting an alias for a private type, but it probably should.
Repro steps
That is, given this code in an assembly:
module Library
type private Hidden = Hidden of unit
type Exported = Hidden

Actual behavior
Using this from another assembly can produce unexpected results:
// in the consuming executable...
open Library

[<EntryPoint>]
let main argv =
    let x : Exported = Unchecked.defaultof<_>
    printfn "%A" x
    0

Giving:
Unhandled Exception: System.MethodAccessException:
Attempt by method 'Program.main(System.String[])' to access method
'Microsoft.FSharp.Core.PrintfFormat`5<System.__Canon,System.__Canon,System.__Canon,System.__Canon,System.__Canon>..ctor(System.String)' failed.

Expected behavior
The desired behaviour would be that a type abbreviation that mentions private types must also be private. This is how functions and "real" types work - neither of these are accepted:
type ExportedRealType = Bad of Hidden
let printExported (_ : Exported) = printfn "How did you get that?"

Related information
Provide any related information

F#: 4.0 (Core <IP_ADDRESS>)
Operating system: Windows 10
.NET Runtime, CoreCLR or Mono Version: 4.5
Editing Tools: VS2015 Update 2

fix in https://github.com/Microsoft/visualfsharp/pull/1289


disable ashing until husking is added

About the PR
husking just a week away
SM is unaffected
Why / Balance
if someone has 5000 burn at least you can brain transplant them
its also horrifically buggy with shitmed so no more torsoless gamers
Technical details
commented it all out
Media
Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.


Implement undo redo

Successfully implemented undo function for delete command

Java CI testing failed - Reason: seedu.address.logic.commands.AddCommandTest > execute_personAcceptedByModel_addSuccessful() FAILED


built-in fonts and custom fonts examples

Pull request for fonts examples
https://github.com/mkdocs-material/internal/issues/29

I am trying to find a CDN for Noto (or another font really) that is not Google and that is not like Google. I have put in cdnfonts.com for now but I can't seem to find much info on who they are, how they make their money, etc. Do you know anything about jsDeliver? That seems to be the default one for Noto.

@squidfunk I will need to go for a walk (rare sunshine, so will head to the beach) and do a little shopping. Any feedback on this very welcome. I hope I can finish off any remaining work in the afternoon.

Right, should be fine now. Fingers crossed. I did test that both examples work with both insider and public version.

Not sure where we are with this - I thought this had runs its course but GitHub says there are change request to be addressed? I will ask you to review again, mainly because I don't know what else to do.

@squidfunk one example that is missing is that of auto-loading another font from Google Fonts. That does raise the question of data protection and whether we should not use the privacy plugin here. I do note that Google Analytics is turned on, so would we not also need to get peoples' consent?

Hey, sorry that I'm sometimes unresponsive right now, I'm focusing on the search, so I try to minimize distractions, which is why some things slip.

That does raise the question of data protection and whether we should not use the privacy plugin here.

We can use the plugin, but that would make the example impossible to run without Insiders. Note that Google Analytics is configured in mkdocs.yml, but no GOOGLE_ANALYTICS_KEY variable is set during the build, so the integration is not active. It's only Google Fonts that is loaded.
I'd say we keep it simple.

We can use the plugin, but that would make the example impossible to run without Insiders.

We could use the privacy plugin for building the whole set of examples and apply this to the individual examples through the transformation script. That would mean the deployed version would be GDPR compliant and the downloadable examples would not assume the use of Insiders.

Ok, I think I have addressed the requested changes. Also moved the mention of the privacy plugin closer to the top of the page on the custom fonts example.

LGTM! By the way, once a PR is approved on this repository, feel free to merge it whenever you feel it's ready. On the actual Material for MkDocs repository, we need to carefully weigh when PRs can be merged, because it impacts a lot of users, but this repository is for examples/demonstration only, so we can relax it a bit.


Occasional SAXParseException

sbt-sonatype occasionally throws a SAXParseException:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
[info] Loading settings for project binding-scala-build-build from plugins.sbt ...
[info] Loading project definition from /home/travis/build/ThoughtWorksInc/Binding.scala/project/project
[info] Loading settings for project binding-scala-build from coursier.sbt,plugins.sbt ...
[info] Loading project definition from /home/travis/build/ThoughtWorksInc/Binding.scala/project
[info] Loading settings for project fxmlJVM from build.sbt ...
[info] Loading settings for project fxmlJS from build.sbt ...
[info] Loading settings for project XmlExtractorJVM from build.sbt ...
[info] Loading settings for project XmlExtractorJS from build.sbt ...
[info] Loading settings for project FutureBindingJVM from build.sbt ...
[info] Loading settings for project FutureBindingJS from build.sbt ...
[info] Loading settings for project BindingJVM from build.sbt ...
[info] Loading settings for project BindingJS from build.sbt ...
[info] Loading settings for project SafeBufferJVM from build.sbt ...
[info] Loading settings for project SafeBufferJS from build.sbt ...
[info] Loading settings for project JsPromiseBinding from build.sbt ...
[info] Loading settings for project Route from build.sbt ...
[info] Loading settings for project dom from build.sbt ...
[info] Loading settings for project secret from secret.sbt ...
[info] Loading settings for project binding-scala from build.sbt,dynver-dash-separator.sbt,secret.sbt ...
[info] Resolving key references (10173 settings) ...
[info] Set current project to binding-scala (in build file:/home/travis/build/ThoughtWorksInc/Binding.scala/)
[info] Setting Scala version to 2.11.12 on 14 projects.
[info] Excluded 1 projects, run ++ 2.11.12 -v for more details.
[info] Reapplying settings...
[info] Set current project to binding-scala (in build file:/home/travis/build/ThoughtWorksInc/Binding.scala/)
[info] Nexus repository URL: https://oss.sonatype.org/service/local
[info] sonatypeProfileName = com.thoughtworks.binding
[info] Reading staging profiles...
[info] Creating staging repository in profile: com.thoughtworks.binding
[error] org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "
".
[error] 	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
[error] 	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1749)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2967)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
[error] 	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
[error] 	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841)
[error] 	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770)
[error] 	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
[error] 	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
[error] 	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
[error] 	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
[error] 	at scala.xml.factory.XMLLoader.loadXML(XMLLoader.scala:41)
[error] 	at scala.xml.factory.XMLLoader.loadXML$(XMLLoader.scala:37)
[error] 	at scala.xml.XML$.loadXML(XML.scala:60)
[error] 	at scala.xml.factory.XMLLoader.load(XMLLoader.scala:53)
[error] 	at scala.xml.factory.XMLLoader.load$(XMLLoader.scala:53)
[error] 	at scala.xml.XML$.load(XML.scala:60)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$createStage$2(Sonatype.scala:727)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$createStage$2$adapted(Sonatype.scala:726)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$Post$1(Sonatype.scala:612)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.$anonfun$Post$1$adapted(Sonatype.scala:603)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.withHttpClient(Sonatype.scala:637)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.Post(Sonatype.scala:603)
[error] 	at xerial.sbt.Sonatype$NexusRESTService.createStage(Sonatype.scala:726)
[error] 	at xerial.sbt.Sonatype$SonatypeCommand$.$anonfun$sonatypeOpen$1(Sonatype.scala:216)
[error] 	at sbt.Command$.$anonfun$applyEffect$4(Command.scala:142)
[error] 	at sbt.Command$.$anonfun$applyEffect$2(Command.scala:137)
[error] 	at sbt.Command$.process(Command.scala:181)
[error] 	at sbt.MainLoop$.processCommand(MainLoop.scala:151)
[error] 	at sbt.MainLoop$.$anonfun$next$2(MainLoop.scala:139)
[error] 	at sbt.State$$anon$1.runCmd$1(State.scala:246)
[error] 	at sbt.State$$anon$1.process(State.scala:250)
[error] 	at sbt.MainLoop$.$anonfun$next$1(MainLoop.scala:139)
[error] 	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:16)
[error] 	at sbt.MainLoop$.next(MainLoop.scala:139)
[error] 	at sbt.MainLoop$.run(MainLoop.scala:132)
[error] 	at sbt.MainLoop$.$anonfun$runWithNewLog$1(MainLoop.scala:110)
[error] 	at sbt.io.Using.apply(Using.scala:22)
[error] 	at sbt.MainLoop$.runWithNewLog(MainLoop.scala:104)
[error] 	at sbt.MainLoop$.runAndClearLast(MainLoop.scala:59)
[error] 	at sbt.MainLoop$.runLoggedLoop(MainLoop.scala:44)
[error] 	at sbt.MainLoop$.runLogged(MainLoop.scala:35)
[error] 	at sbt.StandardMain$.runManaged(Main.scala:138)
[error] 	at sbt.xMain.run(Main.scala:89)
[error] 	at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109)
[error] 	at xsbt.boot.Launch$.withContextLoader(Launch.scala:128)
[error] 	at xsbt.boot.Launch$.run(Launch.scala:109)
[error] 	at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:35)
[error] 	at xsbt.boot.Launch$.launch(Launch.scala:117)
[error] 	at xsbt.boot.Launch$.apply(Launch.scala:18)
[error] 	at xsbt.boot.Boot$.runImpl(Boot.scala:56)
[error] 	at xsbt.boot.Boot$.main(Boot.scala:18)
[error] 	at xsbt.boot.Boot.main(Boot.scala)
[error] org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "
".
[error] Use 'last' for the full log.

https://travis-ci.org/ThoughtWorksInc/Binding.scala/jobs/512904034

It looks like Sonatype is returning HTML response, instead of XML.. Weird...

I guess there may be an error HTTP status

https://github.com/xerial/sbt-sonatype/blob/465d4688944de884b612396ec199cdb9b6518138/src/main/scala/xerial/sbt/Sonatype.scala#L575
HTTP status code (200) is checked here, so after that XML (or html) will be parsed.

This bug report is a POST request.
It seems that only 500 error status is checked for POST status.
https://github.com/xerial/sbt-sonatype/blob/465d4688944de884b612396ec199cdb9b6518138/src/main/scala/xerial/sbt/Sonatype.scala#L609

Nice catch! Then we need to have more proper status code handling here.

hi - have been hit by the same issue, using sbt-sonatype 3.8. is there a temporary workaround? this is blocking some important release on our side.

Right. Sonatype sometimes returns HTML responses for XML request.
I'm thinking about switching to JSON based APIs and adding more retries around the parsing errors.

imo Sonatype should fix this, you do everything right. I've been trying to publish an artefact for 6 hours and it's failing all the time 🤦♂

Judging from Sonatype's issue tracker (https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-52239?filter=allopenissues)  I would say that this SAXParserException is just because we are getting socket timeouts in a form of automatic HTML failure responses. the plugin should probably still recognize it and print a more informative error message.

ok. I'll work on handling XML parsing exceptions

thank you! at the moment, all of our travis-ci.org builds are affected.
unfortunately changing the plugin probably won't fix it, but being able to see the error response from sonatype would help tremendously. let me know if i can help in any way.

I hate to be a "me too", but I'm now getting this constantly and cannot publish. :-(

situation with sonatype seems to improve, some builds have gone through recently.

Actually if sonatype API is down for such a long time (almost 2 days...), even if we add backoff retries, it will not solve this.

That's true, but being able to see the error response from sonatype would help tremendously.

sbt-sonatype 3.9.1 has switched to JSON based API, so this error will no longer happen. Thanks.

I also introduced different timeout settings for creating a new stage (up to 5 min as this needs to be a single HTTP request) and for closing and promoting stages (up to 60 min). I hope this will mitigate this type of slow response issues.

Brilliant 👍

@mpollmeier Another improvement is that the latest version shows the error response in the warning log even if it is an HTML response :)

yay thank you! :bowing_man:


invariant check pass

Some node types and c types have a few invariants assumed, perhaps there could be an optional check pass in between stages that basically just documents + checks. I remember 8cc had one about the left and right side of a '+' if there was a pointer type for example.
I can see an argument against it in terms of keeping the codebase small. Its just more annoying to remember every assumption and add it later.
As always, I don't mind what approach you take, just a point for discussion.

Rejecting bad expressions such as ptr+ptr is sema's task. It is just incomplete. I will eventually extend it so that it can find all bad expressions.


UniversalTimeScaleClock now() and conversion from unix time

It seems the UniversalTimeScaleClock doesn't have a now() function. Additionally, it isn't clear to me how to convert the std::chrono::steady_clock::time_point from std::chrono::steady_clock::now() to cartographer::common::Time. I saw that there are ROS conversions in cartographer_ros, but that requires ROS as a dependency,
What is the best way to convert std::chrono::steady_clock::time_point and get the current time in cartographer::common::Time format with high precision?
Perhaps an addition for now() such as https://stackoverflow.com/a/17138183/99379 would be appropriate?

struct UniversalTimeScaleClock {
  using rep = int64;
  using period = std::ratio<1, 10000000>;
  using duration = std::chrono::duration<rep, period>;
  using time_point = std::chrono::time_point<UniversalTimeScaleClock>;
  static constexpr bool is_steady = true;

    static time_point now() noexcept
    {
        using namespace std::chrono;
        return time_point
          (
            duration_cast<duration>(system_clock::now().time_since_epoch()) +
            seconds(kUtsEpochOffsetFromUnixEpochInSeconds)
          );
    }
};

I'm not 100% sure if I'm supposed to subtract or add kUtsEpochOffsetFromUnixEpochInSeconds though...
update: adding is the correct behavior

Can you explain a bit what you are trying to do?
The reason that there is no now() function is that timing is best provided with the sensor data and that should not get its time from the system clock for best accuracy. Accurate timing information matters a lot, so ideally this would be hardware timestamps included in the sensor data.
Regarding a conversion from steady_clock, I think the answer is that this should not be done. There intentionally is no fixed relationship and steady_clock::time_points should only be used relative to each other, e.g. to compute durations.

Unfortunately my sensors can't do hardware time synchronization so I'm trying to estimate the skew between multiple hardware times and local machine time in software across multiple hardware devices.
This involves timestamping before making data requests and after they are received on multiple sensors so I can better estimate when in local machine time the data was collected, so I can then determine a corrected hardware time stamp that most accurately matches between two data sources and correctly sample in the pose interpolation buffer.
An example of this sort of thing is TicSync/TriggerSync (pdf). Other approaches are implemented in  https://github.com/ethz-asl/kalibr, with various tradeoffs.
ROS code:
https://github.com/englishar/trigger_sync

Regarding a conversion from steady_clock, I think the answer is that this should not be done. There intentionally is no fixed relationship and steady_clock::time_points should only be used relative to each other, e.g. to compute durations.

I disagree on this point because I have found fusing multiple data sources according to a common time frame to be a very sound and well studied approach to reducing noise/error and improving the accuracy of world state estimates.

Thanks for the context.
There is no fixed relationship between steady_clock and UniversalTimeScaleClock. It is for example allowed by the C++ standard for steady_clock to count time since boot. Likewise, the epoch of system_clock is not specified even though it might be the Unix epoch in practice. clock_gettime's CLOCK_REALTIME makes this guarantee. Do you disagree?
Trying to get the best possible estimate for sensor timing as you suggest is indeed a very good idea. These timestamps have to be accurate relative to each other. Shifting all sensor timestamps by a fixed offset to the correct date and time has no influence on the quality of the resulting trajectory. An approach could be: Computing the offset once at the very beginning, add this constant offset to all sensor data. If you need to convert from a Unix epoch timestamp to UniversalTimeScaleClock for this, you'd have to add kUtsEpochOffsetFromUnixEpochInSeconds, not subtract.

There is no fixed relationship between steady_clock and UniversalTimeScaleClock. It is for example allowed by the C++ standard for steady_clock to count time since boot. Likewise, the epoch of system_clock is not specified even though it might be the Unix epoch in practice. clock_gettime's CLOCK_REALTIME makes this guarantee. Do you disagree?

Yes, I agree. This makes sense now that we are on the same page, thanks. I think in practice every major OS, compiler, and standard library implements unix time. However, now() on the UniversalTimeScaleClock would definitely break in the unusual case a clock does not conform to this ad-hoc unix time convention. I assume this also means any time_points
Considering that, would you consider accepting a PR with either of the following or should I just keep things in user code?

now() with the known  assumption and an accompanying warning in the comments
An additional helper function that achieves a similar result, much like the ROS helpers

I'd prefer to rely on the ad-hoc convention over runtime estimation when it is feasible and correct on my platform, unless there's an approach that would have no limitations?

If you need to convert from a Unix epoch timestamp to UniversalTimeScaleClock for this, you'd have to add kUtsEpochOffsetFromUnixEpochInSeconds, not subtract.

Thanks!

I'm going to vote with @wohe on this and say that now() does not belong in the core library; before I understood what was happing with the time stamps, I would have accidentally abused it (if it was there), and that would have given me the wrong behavior.  Just keep the clock handling where you are handling/converting your messages.

Ok fair enough, thanks!


Netavark: Install rust from upstream

The Fedora rust toolchain is fairly old, especially for a young
language.  It also does not include the rustup utility which is
hampering netavark/aardvark-dns development.  Rather than wait for
Fedora to catch up, install the upstream toolchain and utilities.
Signed-off-by: Chris Evich<EMAIL_ADDRESS>

FYI: @rhatdan this PR will also get you new images for podman w/ updated crun, runc, etc.

LGTM. I am ok with VM using the upstream toolchain for rust, with this in place we can remove lot of custom pulling from netavark's CI code.
@cevich but does this also puts us at a risk that we are not testing with what gets shipped with dnf ? However concerned about this a lot cause if it builds with one toolchain it is highly likely that it will also build with the older one.

You're concerns are valid, and it's not my first-choice.  In my experience it does cause problems, especially in packaging.  Hopefully they can/will be caught by downstream gating tests (assuming we even have them).  In any case, you're right, and it is somewhat "kicking the can down the road" for somebody else to deal with.  At this point though, we really don't know what we don't know, so I say we give it a try.

@cevich Sorry I did a type in my above comment. I am also not concerned a lot about this since its unlikely that builds will fail with what's on fedra dnf.
So yes i agree lets give it a try.

fedora-netavark: sudo: showrun: command not found

Oops.  Trying again...

@rhatdan & @flouthoc give c5309576894480384 a try.

@cevich current rustup-init does not configures rustc profile correctly something like curl https://sh.rustup.rs -sSf | sh -s -- -y does that correctly but its not mandatory I can do that in build_cross task specifically.
Other than above image is working correctly and also contains podman as well, I don't think any change is mandatory I could do that in setup.sh so its not a problem

Force-push: Rebuilding to include configuring rustc, def. something we want to do here and not at test runtime.

Pushed a change with new image.

Pushed a change with new image.

So nothing meaningful actually happens when I merge this, the images are already built.  So I'll hold off until https://github.com/containers/netavark/pull/252 merges, just in case any further related changes are needed.

There's an error that's being ignored but looks bad.  And it seems like I left the cargo package installed on accident...

...and the curl command was messed up.  All my fault.  Building again...

@cevich Did you forgot git add, I still can't see the part where fedora's rust is being removed.

I still can't see the part where fedora's rust is being removed.

Oh, I just removed rust and cargo from the $INSTALL_PACKAGES list.  Ahh, I see another problem though, the $CARGO_HOME env. var. is being blocked by sudo...

force-push: Get $CARGO_HOME through $SUDO (script runs as a temporary/regular user, not root).

force-push: Only run rustup-init.sh once :grin:

Ugh...somehow:
    ...cut...
    fedora-netavark:   Installing       : rust-std-static-1.58.1-1.fc35.x86_64                79/110
    fedora-netavark:   Installing       : rust-1.58.1-1.fc35.x86_64                           80/110
    fedora-netavark:   Installing       : cargo-1.58.1-1.fc35.x86_64                          81/110
    ...cut...

Ahh, it's rpm build that's pulling it in.  Removing that, and also adding rust/cargo to the exclusion list to make sure.

Force-push: Removed clippy due to
�[0;32m    fedora-netavark: Error:�[0m
�[0;32m    fedora-netavark:  Problem: conflicting requests�[0m
�[0;32m    fedora-netavark:   - package clippy-1.55.0-1.fc35.x86_64 requires rust(x86-64) = 1.55.0-1.fc35, but none of the providers can be installed�[0m

There we go, this is what we want to see.

@cevich New image is working fine. Just missing some build tools and gcc. Could you add this dnf -y install make automake gcc gcc-c++ kernel-devel and this is good to go.

New image is working fine. Just missing some build tools and gcc. Could you add this dnf -y install make automake gcc gcc-c++ kernel-devel and this is good to go.

Yep, I'll do that in a separate PR.  No need to rebuild images for that small change.


[SPARK-44640][PYTHON][FOLLOW-UP][3.5] Update UDTF error messages to include method name

(cherry picked from commit 3e22c8653d728a6b8523051faddcca437accfc22)

What changes were proposed in this pull request?

This PR is a follow-up for SPARK-44640 to make the error message of a few UDTF errors more informative by including the method name in the error message (eval or terminate).
Why are the changes needed?

To improve error messages.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing tests.
Was this patch authored or co-authored using generative AI tooling?

No

cc @ueshin

Merged to branch-3.5.


*: remove io from gRPC threads (#8886)

What problem does this PR solve?
Backup and restore involves some IO in gRPC threads. They should be moved to worker threads.
What is changed and how it works?
Remove io from grpc threads
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Integration test

Side effects
Release note

Stabilize backup and restore by removing IO operations from gRPC threads.

/release

/release

/run-all-tests

/merge


Issue/6959 update project release documentation (#7027)

Pull request opened by the merge tool on behalf of #7027

Merged in 3981d9ab7885d39a0abe0fc9960c80d3e1532275


Generic Quad X - Boot Up Problem

The device does not boot up after selected the Generic Quad X as the airframe in the latest stable release. There is no problem on other frame types, the only problem is with Generic Quad X.

Are you able to connect a console and see where it's getting stuck?

Since I calibrated everything and mounted on the frame, I don't want to reset the board again. When you set Generic Quad X, the device does not open at all and therefore you can't connect it to QGC, you can't install the firmware again. I think it may be related to the bootloader. Because I was able to install ArduCopter firmware with the MissionPlanner.
But I can say there is no problem in beta and dev releases. I had tried them also.

Oh, in that case this will be resolved shortly. Use dev (master) for now, it's going to become the next release version very soon.


⚠ GitLab Server has degraded performance

In ee162c0, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 7091 ms

Resolved: GitLab Server performance has improved in e2c1bee.


Cache Fill Plugin

Build failures are expected as this PR depends on PR #7439

Build failures are expected as this PR depends on PR #7439

Duplicated by https://github.com/apache/trafficserver/pull/7470


Italian translation

Hey. Thanks for your PR. Are you using this package? I haven't used it for a while and it is currently not maintained. Does it work for you?

Yes, it works with Laravel Nova 3.4.1

ok I see. I can't take a close look right now but I can merge your translation.


adshort.co

Domain
adshort.co
Link
https://adshort.co/7DMjYu
Version
0.0.0
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
Anything else?
No response

Duplicate of #424.


Highlight across paragraphs Bug

Hi guys,
creating highlights across paragraphs leads to the following bugs (Video Highlight Paragraph):

The text is not marked correctly and the HTML is "destroyed".
After changing to another chapter and calling up the highlight via the menu, the passage is found in the ePub but not marked.
In some cases the upper menu can not be opened afterwards (restart of the app is necessary)
After restarting the app, opening the highlight via the menu will not open the right passage in the ePub.

Tables are similar or even worse (Video Highlight Table). Other readers do not have these problems. We use the current version of FolioReader 1.3.0.
Is the problem known, and if so, is there a (foreseeable) solution?
Many Thanks
Peter

Then problem is known. Is a solution foreseeable here ... this problem is really serious.

Yes, this is a known bug since #37 there is a discussion there. but, it is a complex thing in my point of view. Because we should not simply implement a new solution but try to migrate the existing ones.
On #37 we have discussed implementing it using Rangy. Android version has this already implemented. Probably it is possible to reuse the same concept and it will work between platforms. I don't really have time to work on this right now but I would love to see a pull request on this.
Do you think you can fix it? Many people will be benefited from that.
Android implementation:
https://github.com/FolioReader/FolioReader-Android/blob/master/sample/src/main/assets/highlights/highlights_data.json
https://github.com/FolioReader/FolioReader-Android/blob/master/folioreader/src/main/java/com/folioreader/util/HighlightUtil.java
https://github.com/FolioReader/FolioReader-Android/search?utf8=✓&q=rangy

Thanks for the interesting hint. That sounds great. Our app developer will take look at it and contact you to work with you.

Disclaimer: I am closing GH Issues on this project, I don't work full time on it and I haven't been able to update that recently if you would like to help to maintain that and to push the development of this project forward, just reach me out or open a PR and we can discuss it there.


python3Packages.portalocker: 1.7.0 -> 2.0.0

Motivation for this change
noticed it was out of date
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

actually, this creates a few regressions, probably hold off until azure packages bump accordingly
https://github.com/NixOS/nixpkgs/pull/95531
7 packages failed to build:
azure-cli python27Packages.applicationinsights python27Packages.msal-extensions python27Packages.portalocker python37Packages.azure-identity python37Packages.msal-extensions python38Packages.msal-extensions

4 packages built:
python37Packages.applicationinsights python37Packages.portalocker python38Packages.applicationinsights python38Packages.portalocker


remove use of tx.origin in DFRewards.sol

Is your feature request related to a problem? Please describe.
The use of tx.origin for user authentication is not recommended as it leaves your smart contract vulnerable to potential phishing attacks.
Describe the solution you'd like
I recommend using msg.sender instead as this will prevent this vulnerability. I can see that msg.sender has been used throughout the rest of the smart contracts, only in this instance is tx.origin used.
Describe alternatives you've considered
I believe msg.sender is the best option to be used in this scenario

#285 Suggested PR to fix this issue


[Minor][DOC] Fix doc style in ml.ann.Layer

What changes were proposed in this pull request?
1, fix the indentation
2, add a missing param desc
How was this patch tested?
unit tests

Test build #56231 has started for PR 12499 at commit c305c39.

Test build #56231 has finished for PR 12499 at commit c305c39.

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

Merged build finished. Test PASSed.

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

BTW, I think the documents in Layer.scala should be more meaningful

Hm, yeah it's really trivial, but I also get distracted reading this code when I see the malformed scaladoc. It grabs the eye. Are you able to easily detect this type of problem across the code base and fix any such instance in one go?

@srowen Ok, I will make a quick review of ML/MLLIB tonight. And if there are other file having this issue, I will fix those in this PR.

@srowen  MultilayerPerceptronClassifier was found to have the same problem. Others are OK.

Test build #56355 has started for PR 12499 at commit b5c10c4.

Test build #56355 has finished for PR 12499 at commit b5c10c4.

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

Merged build finished. Test PASSed.

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

OK. On the grounds that this does marginally help readability (I find the out-of-line stars distracting) and we've surveyed for similar problems, i'll merge it.


HBASE-24665 MultiWAL : Avoid rolling of ALL WALs when one of the WAL needs a roll

Still doesn't look good

I think it is a problem in the jenkinsfile of branch-2.2.
@infraio PTAL?
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/view/change-requests/job/PR-2187/2/console
ERROR: Could not find credentials entry with ID 'hbaseqa-at-asf-jira'

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m  6s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 16s
branch-2.2 passed

+1 :green_heart:
compile
0m 54s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 21s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m  3s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
branch-2.2 passed

+0 :ok:
spotbugs
3m 19s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 16s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 43s
the patch passed

+1 :green_heart:
compile
0m 55s
the patch passed

+1 :green_heart:
javac
0m 55s
the patch passed

-1 :x:
checkstyle
1m 20s
hbase-server: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m  2s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
25m  7s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 36s
the patch passed

+1 :green_heart:
findbugs
3m 25s
the patch passed

_ Other Tests _

-1 :x:
unit
312m 44s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 38s
The patch does not generate ASF License warnings.

379m  3s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.replication.multiwal.TestReplicationSyncUpToolWithMultipleWAL

hadoop.hbase.client.TestServerBusyException

hadoop.hbase.master.TestAssignmentManagerMetrics

hadoop.hbase.regionserver.TestLogRoller

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2187

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux bcf185c65b5f 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2187/out/precommit/personality/provided.sh

git revision
branch-2.2 / 363a31a5b3

Default Java
1.8.0_181

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/3/artifact/out/diff-checkstyle-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/3/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/3/testReport/

Max. process+thread count
4871 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Can u pls fix the checkstyle issue and look at the Test fail (TestLogRoller seems related)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  3s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 16s
branch-2.2 passed

+1 :green_heart:
compile
0m 58s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 21s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
branch-2.2 passed

+0 :ok:
spotbugs
3m 23s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 22s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 45s
the patch passed

+1 :green_heart:
compile
0m 53s
the patch passed

+1 :green_heart:
javac
0m 53s
the patch passed

-1 :x:
checkstyle
1m 20s
hbase-server: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m  0s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
25m  9s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 35s
the patch passed

+1 :green_heart:
findbugs
3m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
167m 26s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
0m 32s
The patch does not generate ASF License warnings.

232m  2s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2187

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux a12c005399ac 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2187/out/precommit/personality/provided.sh

git revision
branch-2.2 / 363a31a5b3

Default Java
1.8.0_181

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/4/artifact/out/diff-checkstyle-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/4/testReport/

Max. process+thread count
4336 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/4/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
5m 33s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
6m  7s
branch-2.2 passed

+1 :green_heart:
compile
1m  3s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 36s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m 43s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
branch-2.2 passed

+0 :ok:
spotbugs
3m 58s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 56s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 36s
the patch passed

+1 :green_heart:
compile
1m  3s
the patch passed

+1 :green_heart:
javac
1m  3s
the patch passed

+1 :green_heart:
checkstyle
1m 33s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
29m 49s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 39s
the patch passed

+1 :green_heart:
findbugs
4m  4s
the patch passed

_ Other Tests _

-1 :x:
unit
262m 10s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 29s
The patch does not generate ASF License warnings.

340m 45s

Reason
Tests

Failed junit tests
hadoop.hbase.tool.TestSecureLoadIncrementalHFiles

hadoop.hbase.quotas.TestSpaceQuotaSwitchPolicies

hadoop.hbase.replication.multiwal.TestReplicationSyncUpToolWithMultipleWAL

hadoop.hbase.client.TestMobSnapshotCloneIndependence

hadoop.hbase.tool.TestLoadIncrementalHFiles

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2187

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 29c7a5e327b9 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-agent/workspace/Base-PreCommit-GitHub-PR_PR-2187/out/precommit/personality/provided.sh

git revision
branch-2.2 / 363a31a5b3

Default Java
1.8.0_181

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/5/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/5/testReport/

Max. process+thread count
3974 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/5/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Test fail related?  Specially TestReplicationSyncUpToolWithMultipleWAL?

Irrelevant, these tests is unstable, sometimes succeeds sometimes fails.

Test fail related? Specially TestReplicationSyncUpToolWithMultipleWAL?

Irrelevant, these tests is unstable, sometimes succeeds sometimes fails.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 51s
branch-2.2 passed

+1 :green_heart:
compile
1m  2s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 33s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
branch-2.2 passed

+0 :ok:
spotbugs
3m 40s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 38s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 19s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
checkstyle
1m 26s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 29s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
27m 57s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 33s
the patch passed

+1 :green_heart:
findbugs
3m 33s
the patch passed

_ Other Tests _

-1 :x:
unit
255m 23s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

328m 34s

Reason
Tests

Failed junit tests
hadoop.hbase.replication.multiwal.TestReplicationSyncUpToolWithMultipleWAL

hadoop.hbase.replication.TestReplicationSyncUpTool

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2187

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 446f89f03951 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2187/out/precommit/personality/provided.sh

git revision
branch-2.2 / cb21c5a5ed

Default Java
1.8.0_181

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/6/artifact/out/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/6/testReport/

Max. process+thread count
4518 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2187/6/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


[Feature] Support openai 兼容脚本

Describe the feature
像 ChatGLM2-6B 这样提供一个 openai 兼容脚本
https://github.com/THUDM/ChatGLM2-6B/blob/main/openai_api.py

https://github.com/Yidadaa/ChatGPT-Next-Web/issues/2723
Will you implement it?

[ ] I would like to implement this feature and create a PR!

Done.


Login Page

This is pure HTML+CSS right?

This is pure HTML+CSS right?

This will contain a some functions in C#, since we need to call login function. But that doesn't stop us from making a UI :).

thankfully i have learned up on C# so this will be easier. consider done in ~4 days (i might require assistance with implementing this in the overall structure.)


fix: use single logger instance

PR summary
This PR makes sure that the validator and all rules use a single global instance of the LoggerFactory.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[x] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

Looks good!
I noticed the line static _factory = null; is still present in the logger factory file

good catch... with all the excitement related to this PR I completely whiffed at removing that line :joy:

:tada: This PR is included in version 1.2.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket: