text:
egressgw: init gatewayIP to 0.0.0.0

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

Always init gatewayIP to 0.0.0.0 by default instead of the previous nil value. Before this commit the rules that didn't match any node where added in addMissingEgressRules and removed right after in removeUnusedEgressRules. The egressmap auto convert nil to 0.0.0.0 and removeUnusedEgressRules doesn't do anything to match nil and 0.0.0.0.

/test

/test-1.26-net-next

/test-1.26-net-next

(looks like net-next is hitting https://github.com/cilium/cilium/issues/24667)

/mlh new-flake Cilium-PR-K8s-1.26-kernel-net-next

net-next failure looks like an unrelated flake, marking as ready

@jibi Note I don't think MLH managed to create the flake issue.

We're also missing an approving review.

We're also missing an approving review.

I thought I had already approved it

authors: MrFreezeex jibi pchaigno


text:
ci: Avoid using deprecated "tunnel" flag

The tunnel option is deprecated and will be removed in Cilium v1.15. This commit fixes the remaining uses I have found where the CI explicitly set the old tunnel flag.
Note that the Cilium CLI also still sets the flag some times in our CI, this is addressed by cilium/cilium-cli#1993.

/test

ClusterMesh CI failure looks legitimate. Will need to investigate. Putting back to draft. https://github.com/cilium/cilium/actions/runs/6339393376/job/17218425985

/test

/test

source: gharchive/pull-request

repo: cilium/cilium

license_type: permissive

license_source: github-api


text:
ci: datapath-verifier: bump lvh images

Manually bump the lvh images to the latest versions selected by renovate
(https://github.com/cilium/cilium/pull/35434).

/ci-verifier

/test


text:
CI: Added PProf report each five minutes.

To measure the usage of the CPU in a different parts of the test run the
pprof in background each 5 minutes.
Signed-off-by: Eloy Coto eloy.coto@gmail.com

This change is

test-me-please

@eloycoto please confirm that pprof for runtime tests works. I went through the archive on Jenkins and none of the runtime tests contain the pprof report. I had to check the test-output.log of some of the tests to see why:
From: RuntimeMonitorTest_With_Sample_Containers_cilium_monitor_check_--to/test-output.log
time="2018-08-03T07:39:42Z" level=debug msg="running command: gops pprof-cpu 1"
cmd: "gops pprof-cpu 1" exitCode: 1 stdout:

stderr:
Couldn't resolve addr or pid 1 to TCPAddress: couldn't get port for PID 1: open /home/vagrant/.config/gops/1: no such file or directory

With PRs like this, evidence should be provided that the expected functionality works as expected if it is not testable or evident by the tests themselves passing. This should be done by default for all PRs, so that we do not merge code that is not functioning correctly.

Do we need to run with --pprof to enable it in the DaemonSet?

test-me-please

test-me-please

comments addressed.

Provision error:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/5465/

test-me-please

@eloycoto my primary concern [here](url
https://github.com/cilium/cilium/pull/5078#issuecomment-410327310) was not addressed:

With PRs like this, evidence should be provided that the expected functionality works as expected if it is not testable or evident by the tests themselves passing. This should be done by default for all PRs, so that we do not merge code that is not functioning correctly.

I will check this manually when the tests finish, but proof that something which is added which doesn't have testing provided around it functions correctly should be provided as part of the PR as a comment or an update to the PR description itself.

The following pprof files were created:
find . | grep -i prof
./RuntimePolicies_Checks_CIDR_L3_Policy/profile145008820.pprof
./RuntimeConnectivityTest_Basic_Connectivity_test_Test_connectivity_between_containers_with_policy_imported/profile564986294.pprof
./RuntimeConntrackTest_Conntrack-related_configuration_options_for_endpoints/profile718695783.pprof
./RuntimePolicies_Init_Policy_Test_Init_Egress_Policy_Test/profile092977890.pprof
./RuntimePolicies_Tests_Egress_To_World/profile656499881.pprof
./RuntimePolicyEnforcement_Policy_Enforcement_Default_Default_to_Always_with_policy/profile353300250.pprof
./111-/K8sPolicyTest_GuestBook_Examples_checks_policy_example/cilium-v4z5b-profile-profile857365234.pprof
./111-/K8sPolicyTest_GuestBook_Examples_checks_policy_example/cilium-lzd97-profile-profile422990380.pprof
./111-/K8sServicesTest_External_services_To_Services_first_policy,_match_service_by_labels/cilium-4ctwr-profile-profile055017092.pprof
./111-/K8sServicesTest_External_services_To_Services_first_policy,_match_service_by_labels/cilium-9lhj4-profile-profile707953002.pprof
./111-/K8sPolicyTest_Basic_Test_Denies_traffic_with_k8s_default-deny_egress_policy/cilium-v4z5b-profile-profile546951573.pprof
./111-/K8sPolicyTest_Basic_Test_Denies_traffic_with_k8s_default-deny_egress_policy/cilium-lzd97-profile-profile361188474.pprof
./111-/K8sPolicyTest_Namespaces_policies_Cilium_Network_policy_using_namespace_label_and_L7/cilium-lzd97-profile-profile622975492.pprof
./111-/K8sPolicyTest_Namespaces_policies_Cilium_Network_policy_using_namespace_label_and_L7/cilium-v4z5b-profile-profile485876406.pprof
./111-/K8sServicesTest_Checks_ClusterIP_Connectivity_Checks_service_on_same_node/cilium-9lhj4-profile-profile804674418.pprof
./111-/K8sServicesTest_Checks_ClusterIP_Connectivity_Checks_service_on_same_node/cilium-4ctwr-profile-profile951043989.pprof
./111-/K8sServicesTest_External_services_To_Services_first_endpoint_creation/cilium-4ctwr-profile-profile691151692.pprof
./111-/K8sServicesTest_External_services_To_Services_first_endpoint_creation/cilium-9lhj4-profile-profile660305054.pprof
./111-/K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo/cilium-9lhj4-profile-profile010103167.pprof
./111-/K8sServicesTest_Bookinfo_Demo_Tests_bookinfo_demo/cilium-4ctwr-profile-profile795872340.pprof
./111-/K8sServicesTest_External_services_To_Services_first_policy/cilium-4ctwr-profile-profile258119517.pprof
./111-/K8sServicesTest_External_services_To_Services_first_policy/cilium-9lhj4-profile-profile774555607.pprof
./111-/K8sPolicyTest_Basic_Test_Denies_traffic_with_cnp_default-deny_egress_policy/cilium-v4z5b-profile-profile385234368.pprof
./111-/K8sPolicyTest_Basic_Test_Denies_traffic_with_cnp_default-deny_egress_policy/cilium-lzd97-profile-profile012949181.pprof
./111-/K8sPolicyTest_Basic_Test_ServiceAccount_Based_Enforcement/cilium-v4z5b-profile-profile822024516.pprof
./111-/K8sPolicyTest_Basic_Test_ServiceAccount_Based_Enforcement/cilium-lzd97-profile-profile396024499.pprof
./111-/K8sUpdates_Updating_Cilium_stable_to_master/cilium-pkcqx-profile-profile696334697.pprof
./111-/K8sUpdates_Updating_Cilium_stable_to_master/cilium-m62h5-profile-profile365280999.pprof
./111-/K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies/cilium-v4z5b-profile-profile144775290.pprof
./111-/K8sKafkaPolicyTest_Kafka_Policy_Tests_KafkaPolicies/cilium-lzd97-profile-profile473542672.pprof

Profiling works:
$  go tool pprof ./111-/K8sUpdates_Updating_Cilium_stable_to_master/cilium-pkcqx-profile-profile696334697.pprof
Local symbolization failed for cilium-agent: open /usr/bin/cilium-agent: no such file or directory
Some binary filenames not available. Symbolization may be incomplete.
Try setting PPROF_BINARY_PATH to the search path for local binaries.
File: cilium-agent
Build ID: 0005099267d2e41ff76a0f87aec9f78d253d62cb
Type: cpu
Time: Aug 7, 2018 at 5:19pm (CEST)
Duration: 30s, Total samples = 110ms ( 0.37%)
Entering interactive mode (type "help" for commands, "o" for options)
(pprof) top
Showing nodes accounting for 110ms, 100% of 110ms total
Showing top 10 nodes out of 135
      flat  flat%   sum%        cum   cum%
      20ms 18.18% 18.18%       30ms 27.27%  encoding/json.(*Decoder).readValue
      20ms 18.18% 36.36%       20ms 18.18%  runtime.futex
      10ms  9.09% 45.45%       10ms  9.09%  encoding/json.simpleLetterEqualFold
      10ms  9.09% 54.55%       10ms  9.09%  path.Clean
      10ms  9.09% 63.64%       10ms  9.09%  runtime.(*gcSweepBuf).push
      10ms  9.09% 72.73%       20ms 18.18%  runtime.gentraceback
      10ms  9.09% 81.82%       10ms  9.09%  runtime.step
      10ms  9.09% 90.91%       10ms  9.09%  syscall.Syscall
      10ms  9.09%   100%       10ms  9.09%  time.NewTimer
         0     0%   100%       10ms  9.09%  bufio.(*Writer).Flush

@ianvernon I'm merging this as this is already incredibly useful and provides amazing visibility.
@eloycoto Can you explain why the prof files are only generated for 1.11 and some of the runtime tests?

@tgraf thanks for providing the output. The pprof files are only generated for some of the runtime tests because the creation of them is not done on a per-test basis, but is on a timed-trigger (every 5 minutes) throughout the test suite.

authors: eloycoto ianvernon tgraf


text:
fileflush lock before header insert loop

When inserting a large number of headers into the block tree, flushing the block tree on every
header insertion is very slow and results in very high disk i/o activity. By locking before the for loop
we delay the file flush until all headers are inserted.

@mnaamani good catch!

authors: CodeShark mnaamani

repo: ciphrex/mSIGNA

license: mit

license_source: bigquery


text:
Update scala-library to 2.12.16

Updates org.scala-lang:scala-library from 2.12.15 to 2.12.16.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #282.

repo: circe/circe-optics


text:
Badges

Add badges to README

Current coverage is 100% (diff: 100%)

Merging #13 into master will not change coverage

@@           master   #13   diff @@
===================================
  Files           4     4
  Lines          98    98
  Methods        93    93
  Messages        0     0
  Branches        5     5
===================================
  Hits           98    98
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 0cdbdfa...835a2c6

authors: codecov-io jeremyrsmith

repo: circe/circe-yaml


text:
Update scalafmt-core to 3.7.6

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.2 to 3.7.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #376.


text:
Empty Aware Encoder

Hello.
I have a common problem in my company with objects with only Optional fields. Example bellow:
case class Documentation(userInstruction: Option[String] = None, quickTips: Option[String] = None)

If other class uses this Documentation object, in order to be able to represent the associated key as null and don't write a custom Encoder for Documentation, it have to represent it as a Option[Documentation] Making the code more complex. Also making possible to represent a Empty documentation in two ways:
case class ItemOptDoc(name: String, documentation: Option[Documentation])
ItemOptDoc("item 1", None)
ItemOptDoc("item 2", Some(Documentation()))

I made a class that transforms a Regular encoder in a EmptyAwareEncoder. Representing objects where all the keys are empty as null. I documented it there, please read:
https://github.com/opbokel/circe-empty-aware/
Basiclly allows to represent a item like this:
implicit val docEncoder = deriveEncoder[Documentation].asEmptyAware()
case class Item(name: String, documentation: Documentation)

And will automatically represent Documentation as null if all keys are empty. Without boilerplate
Using it in conjunction with the io.circe.Printer option of dropNullValues = true we have the final output to the item 1 bellow:
{
  "name" : "Item 1"
}

I really want to add this functionality to circe, I am not sure it it should be a new module, or a small change to the core. A configuration maybe?
I am open to suggestions, I will also accept if the community decide that circe should not have this functionality.
Thanks a lot!

Hi @opbokel! I like this idea, although I'm reluctant to introduce it into circe-core. I've thought about introducing a new circe-extras module that would be like circe-generic-extras in that it represented functionality that was more experimental or less widely needed than we'd expect something in circe-core to be (but not specific to generic derivation like circe-generic-extras). This could also include pieces like #725 and #647. What do you think?

Hello, I saw that bouth pull requests mentioned as good candidates for a new extra module were not merged. I was going to start merging it into circe and could not find any module that would fit this small functionality. Also it might be overkill to create a module just for this functionality.
Is there already a extra module that I am overlooking?
Should I create a new module?
Can it be merged into the core for simplicity?
Should we close this issue?
Thanks.

source: gharchive/issue

authors: opbokel travisbrown

repo: circe/circe


text:
Update sbt-scoverage to 2.0.2

Updates org.scoverage:sbt-scoverage from 1.9.3 to 2.0.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scoverage", artifactId = "sbt-scoverage" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #2026.

Superseded by #2039.


text:
feat: origin use unique-id from host & port; fix: peer-count count co…

…nnected peer

orgin use u64_hash(ip+port)
rpc peer-count only count connected peer


text:
Document citus_tools

Why are we implementing it? (sales eng)
People really want to use the lower level functions to run SQL on all worker nodes etc. We end up repeating ourselves a lot explaining these functions.
What are the typical use cases?
Communication goals (e.g. detailed howto vs orientation)
Good locations for content in docs structure
How does this work? (devs)
Example sql
Corner cases, gotchas
Are there relevant blog posts or outside documentation about the concept/feature?
Link to relevant commits and regression tests if applicable

Came up in 3 customer engagements.

+1

@saicitus my original notes in this issue from our meeting somehow got erased, so I reconstructed some from memory. In any case please help me fill in the list of utility functions available, the use cases, and sql examples.

@begriffs : For exact usage/arguments you could refer the following links(starting/around the highlighted lines):

Code path
Regress tests

authors: begriffs saicitus


text:
Add job to trigger a performance test on demand

This has been extracted from #24 and depends on #38, #253 and #301:

this should run one or several performance test suites against the test environment
beside active performance assessments, it's supposed to provide fast, automated feedback on the production readiness of [the] systems any time somebody makes a change to them (see Continuous Delivery) down the road
performance tests can be generated & orchestrated via the fantastic record and replay in JMeter functionality @dpb587 has implemented already, see https://github.com/cityindex/logsearch/issues/253#issuecomment-29952987 ff.

Closed as Won't Fix due to project being retired to the CityIndex Attic.

repo: cityindex/logsearch


text:
Show toast / notification to admin when they delete or update questions or blocks

When the user deletes a question from a block, updates a block, or deletes a block, display a toast to show them that their action was successful. (This type of feedback isn't necessary for "add" operations, since the user can see that a new element was added to the UI.)

Hi, I'm working with a group of 2 other CS students from Florida International University. We are part of the Tech Talent Academy program where we are required to join an open source project and make a contribution. We were wondering if we could tackle this issue.

Hi @amilcarjose9, here is some guidance for how to get started contributing to CiviForm:  Technical contribution guide.  You'll find an invite there for our CiviForm Slack, which you're welcome to join.
If you decide this is the issue that you want to work on, please confirm in another comment on this issue and I'll assign it to you.  Thanks for you interest in CiviForm!

authors: amilcarjose9 melanie-exygy neel-a-mehta

repo: civiform/civiform


text:
Add Flux version 2

This issue is a:

[ ] Bug Report
[ ] Enhancement suggestion
[x] Feature request

Enhancement suggestions / feature requests
Flux2 is a widely used, extensible open-source continuous delivery solution powered by GitOps Toolkit.

Hello @ChipWolf  , Thank you for Request. Our marketplace is open to community to make contributions, and as we have updated our market place to support HELM3 and Install.sh files ( example -> https://github.com/civo/kubernetes-marketplace/blob/master/kubevious/install.sh) It is extremely easy. You are most welcome to make a Pull Request.

Done with #183

@saiyam1814 can we re-open this? I don't think Flux is implemented yet in a useful format yet, probably worth making the scope here a little clearer.

@ChipWolf can you elaborate here ? we have Flux maintainer @stefanprodan who is working on making the best one-click install experience via the marketplace.

Hi @saiyam1814, I elaborate a little further in the comments on the PR.

@stefanprodan who is working on making the best one-click install experience via the marketplace.
Is there a different issue for this open or behind the scenes? If so, I apologise.

Oops I might have missed the PR comment!
Have replied there to put it as a suggestion

authors: ChipWolf DoNnMyTh saiyam1814

repo: civo/kubernetes-marketplace

license: MIT


text:
Fix Issue #29

Immediately shutdown can throw an OperationCancelException. We should wait the first 100ms and then check if it is Completed and wait again if not.

I believe this will fix the issue #29 @cjbhaines

The question still remains, does the issue you are trying to fix resolve if you put in LogManager.shutdown() in the Application_End event? If so, this introducing an arbitrary and unnecessary delay.

You're right, at the beginning I was trying to solve my issue which looks very similar to this one. It works for me and the delay was there before the immediate shutdown change. Also, I have just tried replacing the 'Act' part in my tests by just LogManager.Shutdown(); and it is still working with my changes.

I'm a bit lost, does LogManager.Shutdown() fix your issue and mean we can cancel this PR? I don't like the look of the change because as Richard says it introduces unnecessary delays if there are no messages in the buffer.

LogManager.Shutdown() doesn't fix the issue. My issue and I think it is linked to this one is that Shutdown is somehow called even when the application starts. It is not really a problem but there is no event at this point and the subscriber loop is trying to get the next one while the Immediate shutdown is called at the same time. Wait 100ms allows the loop to finish before we do the Cancel and the exception is not raised. I didn't come up with the 100ms, it was already there. I didn't change the behaviour and it will still wait longer if needed or shutdown straight after.
Sorry if it is not clear enough but It is something you cannot see during debug as a breakpoint is leaving time for the loop to finish. You will see that the test fail without my changes and pass with.

Hi, I can offer another solution that will not add any delays. By checking that we have some events in _loogingEvents before trying to get them in the foreach we can avoid the exception. I will create an new pull request so you can review it and cancel this one. Log4Net.Async is great and very helpful for my project, I just want to have it working without throwing this exception when there is no error behind. Thank you.

Actually merged into this one... Let me know if you want me to start again with a clean branch. Thank you.

You could not have possibly run this.    You are exiting the subscriber loop whose purpose is to sit there waiting for the for entries to come in.   The count can absolutely be zero when the loop starts.
Perhaps you might want to try checking the collection count when the OperationCanceled exception is caught in the subscriber loop.  If the collection size is zero at that point then the exception might not need to be forwarded.  Give that a try.

(Was about to post this when @rcollette replied):
I can confirm LogManager.Shutdown() doesn't fix the issue (@rcollette my apologies for not responding sooner).
@Djiu13 _loggingEvents.Count check doesn't seem to work with a BufferingForwardingAppender. When the logging task starts there are no logging events, so it will end the task prematurely and nothing is ever logged. When the app pool recycles I get "The buffer was not able to be flushed before timeout occurred".
The 100ms delay (7c78798) does seem to have fixed the issue.

Sorry for the last commit, of course it won't work... I got lost. I have actually already tried to put the if condition in the catch and it was working fine. I will commit this change then and hopefully it will be ok with everyone. Thanks for your help and feedback.

This looks good.   @cjbhaines Just doing a mental exercise on version numbers with this.   If the task is ended without LogManager.shutdown(), it will no longer error if there are no entries in the queue.   It's a slight behavior change but probably still a patch?

Hi, any progress on merging this change? Thank you :)

Merged but would like agreement from @cjbhaines about the release being patch, point or major.  Personally I am inclined to call it a patch.

Hey guys, really sorry about delayed response. I'm happy to release this as a patch, pushing major updates is a pain for consumers so I would like to reserve those for breaking changes.

authors: Djiu13 cjbhaines lbras rcollette


text:
Fake timers should trigger on restore

I was experiencing the weirdest error (reproducable test case) yesterday, where wrapping one test in sinon.test and exchanging sinon.stub for this.stub would cause all subsequent tests using Promises to fail in IE9.
I finally tracked it down to having to do with the es6 promise implementation using setTimeout to shim the Promise implementation in older browsers missing a native Promise implementation. The point of a sandbox is that changes in the sandbox should not propagate outside of the sandbox, and therefore I was curious to what might cause this.
Turns out that the ES6 Promises shim uses a queue of functions of setTimeout(fn, 1) to simulate async execution, and that any Promises created in the sinon.test function will cause subsequent Promise creations to hang, unless the timers are triggered somehow.
Real timers trigger at some point, so would it not be right if Sinon also triggered its timers when restoring the global state created by the sandbox to its previous state?
--
Of course one can hack around this when one is aware of what is going on (either ticking the clock a few millis, or simply setting sinon.config = {     useFakeTimers : false }, but that assumes everyone knows the setTimeout abstraction is leaking.
I could try and look into how to do this and propose a PR, but I won't bother starting until I know the idea is sound :-)

@fatso83 thank you for reporting this :+1:
This issue looks a lot like https://github.com/cjohansen/Sinon.JS/issues/246, where the library authors haven't cached setTimeout.
I imagine that adding var setTimeout = setTimeout somewhere in the beginning of that file would make the issue go away.
Does that solve the issue for you?

That should fix this specific issue, but that wasn't why I raised the issue. I think the callbacks that are still queued at restore time should then be triggered by default, as that would avoid having to make changes to third-party libraries that expect them to fire at some point.
Since you already have access to the queue of callbacks this would not be a big change in terms of LOC, but I am unsure if this could somehow break existing behaviour.


text:
🛑 Home Assistant is down

In 9279712, Home Assistant ($HA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Home Assistant is back up in abf88e6.


text:
Media attachments on comments?

If someone attaches an image or other multimedia to a reply they send on Mastodon, or even just includes a URL in their post, should we render that? And how would we support caching the media locally? Do we need to include some kind of S3 bucket (or compatible service) support?

I'm reluctant to support this for now because it raises a lot of technical questions about price, maintenance, expiration, etc, but also gets into dangerous territory with illegal content etc. If you don't sufficiently protect yourself from bad actors on the network, you can get yourself into some serious trouble, and for what benefit? images in comments? Lots of platforms don't support embedded images in comments.
Closing it for now; we can always revisit if the demand is sufficient and we feel like our trust & safety situation is in a better place.

repo: ckolderup/postmarks


text:
I'm compiling with JDK 11 and it seems like Onehouse doesn't support it.

{"exception":{"stacktrace":"java.io.IOException: Could not load transformer class(es) [tr0:org.onehouse.TaxiTransformer, tr1:com.onehouse.transformers.DataValidationWithQuarantine]\n\tat org.apache.hudi.utilities.UtilHelpers.createTransformer(UtilHelpers.java:228)\n\tat org.apache.hudi.utilities.streamer.StreamSync.<init>(StreamSync.java:321)\n\tat org.apache.hudi.utilities.streamer.HoodieStreamer$StreamSyncService.<init>(HoodieStreamer.java:741)\n\tat org.apache.hudi.utilities.streamer.HoodieStreamer$StreamSyncService.<init>(HoodieStreamer.java:761)\n\tat com.onehouse.hudi.OnehouseDeltaStreamer$MultiTableSyncService$StreamSyncService.<init>(OnehouseDeltaStreamer.java:1237)\n\tat com.onehouse.hudi.OnehouseDeltaStreamer$MultiTableSyncService$StreamInfo.reInitIngestionService(OnehouseDeltaStreamer.java:1033)\n\tat com.onehouse.hudi.OnehouseDeltaStreamer$MultiTableSyncService$StreamInfo.access$1400(OnehouseDeltaStreamer.java:499)\n\tat com.onehouse.hudi.OnehouseDeltaStreamer$MultiTableSyncService.lambda$null$2(OnehouseDeltaStreamer.java:405)\n\tat java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat java.lang.Thread.run(Thread.java:750)\nCaused by: java.lang.UnsupportedClassVersionError: org\/onehouse\/TaxiTransformer has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0\n\tat java.lang.ClassLoader.defineClass1(Native Method)\n\tat java.lang.ClassLoader.defineClass(ClassLoader.java:756)\n\tat java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)\n\tat java.net.URLClassLoader.defineClass(URLClassLoader.java:473)\n\tat java.net.URLClassLoader.access$100(URLClassLoader.java:74)\n\tat java.net.URLClassLoader$1.run(URLClassLoader.java:369)\n\tat java.net.URLClassLoader$1.run(URLClassLoader.java:363)\n\tat java.security.AccessController.doPrivileged(Native Method)\n\tat java.net.URLClassLoader.findClass(URLClassLoader.java:362)\n\tat java.lang.ClassLoader.loadClass(ClassLoader.java:418)\n\tat java.lang.ClassLoader.loadClass(ClassLoader.java:351)\n\tat java.lang.Class.forName0(Native Method)\n\tat java.lang.Class.forName(Class.java:264)\n\tat org.apache.hudi.common.util.ReflectionUtils.lambda$getClass$0(ReflectionUtils.java:53)\n\tat java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)\n\tat org.apache.hudi.common.util.ReflectionUtils.getClass(ReflectionUtils.java:51)\n\tat org.apache.hudi.common.util.ReflectionUtils.loadClass(ReflectionUtils.java:62)\n\tat org.apache.hudi.utilities.transform.ChainedTransformer.<init>(ChainedTransformer.java:87)\n\tat org.apache.hudi.utilities.transform.ErrorTableAwareChainedTransformer.<init>(ErrorTableAwareChainedTransformer.java:43)\n\tat org.apache.hudi.utilities.UtilHelpers.lambda$createTransformer$0(UtilHelpers.java:224)\n\tat org.apache.hudi.utilities.UtilHelpers.lambda$createTransformer$1(UtilHelpers.java:226)\n\tat org.apache.hudi.common.util.Option.map(Option.java:108)\n\tat org.apache.hudi.utilities.UtilHelpers.createTransformer(UtilHelpers.java:226)\n\t... 11 more","exception_class":"java.io.IOException","exception_message":"Could not load transformer class(es) [tr0:org.onehouse.TaxiTransformer, tr1:com.onehouse.transformers.DataValidationWithQuarantine]"},"source_host":"ds-job-multiple-tables-86862c1a-0225-4293-driver","method":"reInitIngestionService","level":"ERROR","message":"Failed to initialize deltaSync for the table s3a:\/\/onehouse-customer-bucket-f66106d2\/hudi_configs\/adhoc-lake\/adhoc_lake_default\/taxi2\/29283f84-cd14-4c85-bfac-b11c145060d5\/source_specific.properties","mdc":{"thread_name":"{thread_name=pool-35-thread-5}","thread_id":"{thread_id=583}","database.table":"{database.table=adhoc_lake_default.taxi2}"},"@timestamp":"2024-07-11T18:18:55.677Z","file":"OnehouseDeltaStreamer.java","line_number":"1037","thread_name":"pool-35-thread-5","@version":1,"logger_name":"com.onehouse.hudi.OnehouseDeltaStreamer$MultiTableSyncService","class":"com.onehouse.hudi.OnehouseDeltaStreamer$MultiTableSyncService$StreamInfo"}

Yes, it needs to be Java 8

Found the requirement.  https://docs.onehouse.ai/docs/product/ingest-data/transformations/custom-transformers

authors: alberttwong ckonehouse


text:
Install fails: file INSTALL cannot find

-- Installing: /usr/ports/multimedia/musikcube/work/stage/usr/local/share/musikcube/locales/ru_RU.json
-- Installing: /usr/ports/multimedia/musikcube/work/stage/usr/local/share/musikcube/libmusikcore.so
-- Installing: /usr/ports/multimedia/musikcube/work/stage/usr/local/share/musikcube/musikcube
CMake Error at cmake_install.cmake:119 (file):
  file INSTALL cannot find
  "/usr/ports/multimedia/musikcube/work/musikcube-0.51.0/src/musikcube/musikcube".

Hmm, not sure what's going on here. I've never had an INSTALL file in the repo. Building from source then doing a make install on FreeBSD (which I believe is the OS you're using) seems fine to me.
Can you provide some more context?

It might be the same problem: https://stackoverflow.com/questions/25272866/cmake-make-install-fails-with-file-install-cannot-find-myfile

OK, so, I'm still not able to repro, but this seems to be a problem with the wrapper shell script that starts the actual musikcube executable. This script is generated at build time. I seem to remember you also had problems with cmake because it was using ninja instead of standard unix makefiles. I have a feeling that may have been related, which caused the input musikcube.in to not get processed/generated properly.
In investigating this I also discovered a slight "out of the box incompatibility" with the wrapper script on FreeBSD; it seems FreeBSD does not ship with bash, only sh, which means these scripts may not work properly for some users.
I updated the scripts to use sh instead, and pushed some other minor changes related to BSD compatibility.
If you get a chance, can you try pulling the latest from git and rebuilding?

cd ~/path/to/musikcube/
git pull
./clean-nix.sh
cmake -G "Unix Makefiles" .
make
make install

I tried this on a clean FreeBSD install and it seems to work fine.

@yurivict thanks for the repro steps! You were correct in your original suggestion, the fix required using CMAKE_CURRENT_BINARY_DIR as suggested in that SO thread. I've pushed changes to the master branch that should get you up and running... let me know if it fixes things on your end!
Also, I noticed the license specified in musikcube.shar is incorrect -- musikcube uses a standard 3-clause BSD, not GPLv2! :)

authors: clangen yurivict

repo: clangen/musikcube


text:
raspberry pi cannot install in right way or execute musikcube

i have a rpi 3b+ with fresh rpi os 64 bit desktop. I've tried to install musikcube 3.0.0 and 0.9.0 .
3.0.0 :
wget https://github.com/clangen/musikcube/releases/download/3.0.0/musikcube_linux_rpi_armhf_3.0.0.tar.bz2
 tar -jxvf ./musikcube_linux_rpi_armhf_3.0.0.tar.bz2
 cd musikcube_linux_rpi_armhf_3.0.0/
./musikcube

output:
Failed to execute process './musikcube'. Reason:
The file './musikcube' does not exist or could not be executed.

0.99.9 :
wget https://github.com/clangen/musikcube/releases/download/0.99.0/musikcube_standalone_0.99.0_rpi_armhf.deb
sudo dpkg -i ./musikcube_standalone_0.99.0_rpi_armhf.deb

(Reading database ... 110786 files and directories currently installed.)
Preparing to unpack .../musikcube_standalone_0.99.0_rpi_armhf.deb ...
Unpacking musikcube:armhf (0.99.0) over (0.99.0) ...
Setting up musikcube:armhf (0.99.0) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...

sudo apt-get install -f

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfuse2
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

musikcube

/usr/bin/musikcube: 6: exec: ./musikcube: not found

can musikcube be installed on rpi or is it my fault?

Unfortunately the Raspberry Pi binaries I generate are 32-bit -- I don't currently have a 64-bit rpi environment setup at the moment.

I have the same issue on a raspberry zero 2, is there a 64-bit environment in the queue?

authors: Gerodote Jo131313 clangen


text:
Fix Hound CI behavior

Hound is reporting too much things when people send PR's. It would be great if we configure it to behave the right way.

sounds like 44ff6cd74eb34bf7756288d270e6fa4ad3aebf1b fixed this

repo: clappr/clappr


text:
Any Gutenberg-specific examples?

Thanks for this great component!
I was previously using the original react-sortable-hoc for use inside a wordpress Gutenberg plugin and it worked really well!
But, since mid-2021, that component stopped working and as per the note on this component, we have been recommended to update with this one. But it's not a straightforward drag-drop replacement and I was wondering if there's any Gutenberg-specific example here that I can implement?
More specifically, I am trying to setup a very basic implementation for testing using the following code. But I keep getting an error, even after stripping the code down to the minimum. Please help!
import './editor.css';
//import React from 'react';
//import React, {useState} from 'react';

const { __ } = wp.i18n;

const {
	registerBlockType
} = wp.blocks;

const {
	Button,
	PanelBody,
	ToggleControl,
	TextControl,
	Dashicon,
} = wp.components;

const {
	RichText,
  MediaUpload,
  InspectorControls,
} = wp.blockEditor;

const { Component, Fragment, useState, useEffect, forwardRef } = wp.element;

import { DndContext } from '@dnd-kit/core';

import {CSS} from '@dnd-kit/utilities';

registerBlockType( 'integrated/photo-gallery', {
    title: __( 'Photo Gallery' ),
    icon: 'format-gallery',
    category: 'photo-features',
	description: __( 'Insert an formatted Image Carousel.' ),
    keywords: [
        __('photos'),
        __('gallery')
    ],
    attributes: {
        slides : {
			type: 'array',
			default:[],
		},
		descriptions : {
			type: 'array',
			default:[],
		},
		autoplay:{
			type: 'boolean',
			default: false
		},
		delay: {
			type: 'number',
			default: 5
		},
		loop: {
			type: 'boolean',
			default:false
		},
		darkmode:{
			type: 'boolean',
			default: false
		},
	},
	edit: (props) => {

         console.log(props);
        return (
         <Fragment>
           <DndContext>
             this is a test
           </DndContext>
         </Fragment>
        );
      },
       save: () => {
		return null;
	},
} );

package.json:
{
  "name": "integrated-platform",
  "version": "0.0.3",
  "private": "true",
  "dependencies": {
    "@automattic/vip": "^1.7.0",
    "@babel/cli": "^7.16.0",
    "@babel/core": "^7.0.0",
    "@babel/plugin-transform-react-jsx": "^7.0.0",
    "@dnd-kit/core": "^5.0.1",
    "@dnd-kit/sortable": "^6.0.0",
    "@wordpress/block-editor": "^8.0.12",
    "@wordpress/components": "^19.1.6",
    "@wordpress/core-data": "^2.12.0",
    "animate.css": "3.4.0",
    "array-move": "^2.1.0",
    "babel-loader": "^8.0.0",
    "classnames": "^2.2.6",
    "components-font-awesome": "4.4.0",
    "core-js": "^3.20.3",
    "cross-env": "^5.0.1",
    "css-loader": "^1.0.0",
    "foundation-icon-fonts": "*",
    "foundation-sites": "5.5.3",
    "hover.css": "2.0.2",
    "lodash": "^4.17.21",
    "main-bower-files": "2.9.0",
    "react": "^16.13.1",
    "react-dom": "^16.13.1",
    "react-select": "^3.0.8",
    "react-sortable-hoc": "^1.10.1",
    "select2": "4.0.0",
    "slick-carousel": "1.5.8",
    "style-loader": "^0.23.1",
    "webpack-dev-server": "^2.5.1"
  },
  "scripts": {
    "build": "cross-env BABEL_ENV=default webpack",
    "dev": "mode=development webpack  --watch"
  },
  "devDependencies": {
    "@babel/plugin-proposal-class-properties": "^7.16.7",
    "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
    "@babel/plugin-transform-classes": "^7.16.5",
    "@babel/preset-env": "^7.16.5",
    "@babel/preset-react": "^7.16.5",
    "@wordpress/babel-preset-default": "^6.4.1",
    "babel-plugin-lodash": "^3.3.4",
    "babel-plugin-react-auto-binding": "^1.0.5",
    "babel-plugin-transform-object-rest-spread": "^6.26.0",
    "babel-plugin-transform-react-jsx": "^6.24.1",
    "webpack": "^5.65.0",
    "webpack-cli": "^4.9.1"
  }
}

Error in console:
Uncaught Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at j (blocks.build.js?ver=1644327052:formatted:7290:27)
    at t.useReducer (blocks.build.js?ver=1644327052:formatted:7462:24)
    at blocks.build.js?ver=1644327052:formatted:8979:26
    at renderWithHooks (react-dom.js?ver=17.0.1:15015:20)
    at updateFunctionComponent (react-dom.js?ver=17.0.1:17386:22)
    at updateSimpleMemoComponent (react-dom.js?ver=17.0.1:17245:12)
    at updateMemoComponent (react-dom.js?ver=17.0.1:17122:16)
    at beginWork (react-dom.js?ver=17.0.1:19165:18)
    at HTMLUnknownElement.callCallback (react-dom.js?ver=17.0.1:3942:16)
    at Object.invokeGuardedCallbackDev (react-dom.js?ver=17.0.1:3991:18)

Thanks very much!

OK - after hrs of trying, I was able to get dnd-kit to integrate with Gutenberg! Here's a partial version of the code, but ping me if anyone needs a more complete version. Thanks again for an excellent component!
import './editor.css';

// dnd imports
import {
  closestCenter,
  DndContext,
  TouchSensor,
  MouseSensor,
  DragOverlay,
  DragStartEvent,
  useSensor,
  useSensors,
  PointerSensor,
  KeyboardSensor,
  useDndContext,
  LayoutMeasuringStrategy,
  DragEndEvent
} from "@dnd-kit/core";

import {
  arrayMove,
  SortableContext,
  sortableKeyboardCoordinates,
  verticalListSortingStrategy
} from "@dnd-kit/sortable";

import {
  restrictToVerticalAxis,
  restrictToWindowEdges,
} from '@dnd-kit/modifiers';

// wp imports
const { __ } = wp.i18n;

const {
	registerBlockType
} = wp.blocks;

const {
	Button,
	PanelBody,
	ToggleControl,
	TextControl,
	Dashicon,
} = wp.components;

const {
  RichText,
  MediaUpload,
  InspectorControls,
} = wp.blockEditor;

const { Component, Fragment, useState, useEffect } = wp.element;

import { Droppable } from "./Droppable";
import { Draggable } from "./Draggable";
import { SortableItem } from "./SortableItem";

function SortApp( props ) {

  const {
    setAttributes,
    attributes,
  } = props;

  const {
    slides = [],
  } = attributes;

  const sensors = useSensors(
    useSensor(MouseSensor, {
      // Require the mouse to move by 10 pixels before activating
      activationConstraint: {
        distance: 10
      }
    }),
    useSensor(TouchSensor, {
      // Press delay of 250ms, with tolerance of 5px of movement
      activationConstraint: {
        delay: 250,
        tolerance: 5
      }
    }),
    useSensor(KeyboardSensor, {
      coordinateGetter: sortableKeyboardCoordinates
    })
  );

  const [isDropped, setIsDropped] = useState(false);
  const [parent, setParent] = useState(null);

  const draggableMarkup = <Draggable id="draggable">Drag me</Draggable>;

  const handleDragStart = (props) => {
    //console.log(props);
  };

  const handleDragEnd = (event) => {
    const { active, over } = event;

    if (active?.id !== over?.id) {

      let active_index = slides.findIndex(function(slide) {
        return slide.id == active.id
      });

      let over_index = slides.findIndex(function(slide) {
        return slide.id == over.id
      });

      let _slides = arrayMove(slides, active_index, over_index);

      //Saves the new state
      setAttributes({
        slides: _slides,
      })

    }
  };

  const handleDragCancel = () => {};

  return (

    <Fragment>

      <InspectorControls>
        <PanelBody title="Slider Settings">
          <ToggleControl
            label={__( 'Loop' )}
            onChange={
              ( value ) => {
                setAttributes( { loop: value } );
              }
            }
            checked={attributes.loop}
          />
          <ToggleControl
            label={__( 'Autoplay' )}
            onChange={
              ( value ) => {
                setAttributes( { autoplay: value } );
              }
            }
            checked={attributes.autoplay}
          />
          { attributes.autoplay &&
            <TextControl
              label={__( 'Autoplay Duration in seconds (default 5 seconds)' )}
              onChange={
                ( value ) => {
                  setAttributes( { delay: value } );
                }
              }
              value={attributes.delay}
            />
          }
          <ToggleControl
            label={__( 'Dark Mode' )}
            onChange={
              ( value ) => {
                setAttributes( { darkmode: value } );
              }
            }
            checked={attributes.darkmode}
          />

        </PanelBody>
      </InspectorControls>

      <div className="gallery-grid">

        <DndContext
          sensors={sensors}
          onDragStart={handleDragStart}
          onDragEnd={handleDragEnd}
          onDragCancel={handleDragCancel}
          modifiers={[restrictToVerticalAxis, restrictToWindowEdges]}
        >
          <SortableContext items={ props.attributes.slides } strategy={verticalListSortingStrategy}>
            {props.attributes.slides.map((slide, index) => (
              <SortableItem key={index} index={index} props={props} slide={slide} id={index} />
            ))}
          </SortableContext>
        </DndContext>

        <MediaUpload
          onSelect={(media) => {
            setAttributes({
              slides: [...slides, ...media],
            });
          } }
          type="image"
          multiple={true}
          value={slides}
          render={({open}) => (
            <Button className="select-slides-button is-button is-default is-tertiary is-large" onClick={open}>
              Add slides
            </Button>
          )}
        />

      </div>

    </Fragment>

  );

}

registerBlockType( 'integrated/photo-gallery', {
    title: __( 'Photo Gallery' ),
    icon: 'format-gallery',
    category: 'features',
	description: __( 'Insert a formatted Image Carousel.' ),
    keywords: [
        __('photos'),
        __('gallery')
    ],
    attributes: {
        slides : {
			type: 'array',
			default:[],
		},
		descriptions : {
			type: 'array',
			default:[],
		},
		autoplay:{
			type: 'boolean',
			default: false
		},
		delay: {
			type: 'number',
			default: 5
		},
		loop: {
			type: 'boolean',
			default:false
		},
		darkmode:{
			type: 'boolean',
			default: false
		},
	},
	edit: SortApp,
        save: () => {
		return null;
	},

} );

The above was used to build a custom photo gallery block in my WP editor.

repo: clauderic/dnd-kit


text:
Range Calendar does not obey rowHeight

The Range Calendar does not render correctly when rowHeight is set

This seems to help:
.Cal__Day__range.Cal__Day__selected.Cal__Day__start:after, .Cal__Day__range.Cal__Day__selected.Cal__Day__end:after {
  height: 100%;
  margin-top: -33.333%;
}

But I am noticing this appears to assume you provide your own stylesheet if you tweak rowHeight. So I'll close this.

repo: clauderic/react-infinite-calendar


text:
Some suggestions to Euler_compare.ipynb

I think this is a useful notebook.
For the Sod problem it is stated that the "fine grid" solution can be viewed as the exact solution, but as computed (especially in the first example where the clawpack solver is used with only 1000 points) the contact discontinuity is quite smeared out, which could lead to confusion on the part of the reader.  I tried changing to sharpclaw with 2000 points and it looks a bit better, maybe go to an even finer grid?  Or hardwire the exact solution since we have it?
I added some comment about the fact that a single Riemann problem is solved numerically to perhaps avoid confusion with the exact Riemann problem.
The initial data used for the blast wave problem seems to be specified as
q_l = Euler.conservative_to_primitive(1.,0.,1.)
q_r = Euler.conservative_to_primitive(1./8,0.,1./10)

but then these values are ignored in the blastwave function invoked in
roe_bw = blastwave(q_l,q_r,riemann_solver='Roe')

since this problem has 3 initial states that are hardwired into the function definition.  Am I missing something?  Can we remove q_l, q_r from this example?
It would be good if the plots could be titled something like Density at t = 0.038 so the reader knows which variable is being plotted, and for comparison with e.g. Figure 15.5 in FVMHP.  Maybe add a bit more discussion of the blast wave problem?
Would it be useful to also plot u and p for these examples?
Many of the examples in this notebook threw a warning such as,
/Users/rjl/clawpack_src/clawpack-rbook2/clawpack/riemann/euler_1D_py.py:298: RuntimeWarning: invalid value encountered in sqrt
  rhsqrtl = np.sqrt(q_l[0,...])

Thanks!  I will merge this and work on cleaning up the other issues you've pointed out.

authors: ketch rjleveque


text:
🛑 livevault is down

In 63c9534, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 6f76d13.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

In d1df47f, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in b8537ab.


text:
🛑 offsitedatasync.com is down

In 4994f11, offsitedatasync.com (https://offsitedatasync.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: offsitedatasync.com is back up in 9072e70.


text:
🛑 livevault is down

In cef21c9, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 6df14b0.


text:
🛑 livevault is down

In 35fe815, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in b0404eb.


text:
Remove unittest package and use test

unittest is deprecated: https://pub.dartlang.org/packages/unittest.

@greglittlefield-wf Can this be closed now?

Yessir! FIxed in #110

repo: cleandart/react-dart


text:
Fix error handling

Error handling is broken for single error cases.
This PR fixes it.

hi @ofpiyush thanks for the PR. are the tests passing locally for you? it looks like they are failing on Travis CI.

@harlow check the error logs. The tests ask for authentication.

any update on this one? happy to push up fix but was curious if this is still being maintained...caused some issues for us today in not realizing we were hitting 429 errors

I am not sure if it is being maintained either. We're using our fork with the bugfix. 🤞

Hi all, sorry for the lack of response here. I'm gonna get this merged and then i'll create a sep PR to fix the auth issues on Travis.

authors: harlow ofpiyush sdalezman

repo: clearbit/clearbit-go


text:
functional: ginkgo/gomega: use Expect not Ω

When using ginkgo (technically, the gomega pattern matcher with ginkgo) in our tests, can we stick to using the Expect API call, and not the Ω call.
Ω is just going to cause us issues later on searching, parsing, or some similar general confusion, and Expect is functionally identical and tbh 'says what it does on the tin' more for me.
http://onsi.github.io/gomega/#making-assertions

Ω is just going to cause us issues later on searching, parsing, or some similar general confusion, and

I don't think so, Ω and Expect are the same thing

It's obviously not going to cause technical run issues - as I said, they are functionally equivalent (as noted in the gomega docs). But, adding basically a non-ascii character into our codebase, particularly when it is not necessary, is horrid. Don't do it. Undo it.

ehmm nop, the use of non-ascii characters is one of the advantages that Go offers us and is not horrid if it was then why ginkgo implement it? why Go support this? - This is one of the cool features of Go.

If so @devimc, why did they also supply an ascii named fully equivalent function as well?
I have to say, I love the phrase from the gomega docs On OS X the Ω character should be easy to type, it is usually just option-z: ⌥z - that, to me, really says it is a non-standard char, and you probably shouldn't do it.
It it doesn't appear on my 101 key UK or US keyboard then I don't think it belongs in the code.
If I have to, I'll go do the sed change and submit a PR to change them all...

go for it, but then you have to change Should and ShouldNot with To or NotTo or ToNot to make it clear

authors: devimc grahamwhaley

repo: clearcontainers/tests


text:
fix(nextjs): Only ignore paths that have a '.' in the final path segment

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[x] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

Updates our middleware default matcher and IGNORED_ROUTES pattern to allow matching of paths that contain a . that is not in the last path segment, but does not match paths that contain a . in the last segment (presumably this would be a static asset).

Fixes JS-694

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

authors: BRKalow clerk-cookie

repo: clerk/javascript


text:
fix(clerk-js): Fix layout shifts

Description
This PR fixes layout shifts in <UserButton/>, <OrganizationSwitcher/> components and for the OTP input.

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[X] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!preview

Hey @panteliselef, your preview is currently deploying and should be available shortly.

Status
Preview
Updated (UTC)

:cook: Deploying...
Inspect
Dec 21, 2023 08:03 AM

authors: clerk-cookie octoper panteliselef


text:
🛑 UMASNet is down

In 41e7936, UMASNet (https://twk.umas.cl/umasnet) was down:

HTTP code: 503
Response time: 608 ms

Resolved: UMASNet is back up in 071aafb.

repo: cleyan/status-umas


text:
[0.5pt] Find external API - group task

Find an API to base the development of the webapp around it. The API should allow you to

Get a list of items with a unique item id (or generate the unique id).
For a given item, get detailed information about it.
choose an APIs that doesn't need authentication. if you select an API that requires authentication, you should implement it on your own. Also, if you select an API that provides image resources your webapp will be more visual.

Hi @clintonjosephs
I found that TvMaze is a good choice and it has all wanted functionality

authors: ahmedtaa clintonjosephs

repo: clintonjosephs/MovieSpot


text:
Pas de connexion rtorrent et rutorrent

Salut,
Super script seulement j'ai un soucis avec....
rutorrent ne parvient pas à établir de connexion avec rtorrent comment faire ?
Merci, Valentin

C'est un peu short comme description de problème ;)
Combien as-tu d'utilisateur ? (de ligne dans htpasswd.txt)
Si t'as plusieurs utilisateurs, as tu le problème pour tous ?

authors: cloneMe valounours

repo: cloneMe/turbo-seedbox


text:
Render OAS schemas

Right now, in addition to the OAS info not being rendered as an initial page (see #8), the OAS schemas section is not rendered ass well. It would probably be a single sidebar category called "Schemas" with each model underneath it (and the demo panel would be disabled for these pages). Here is an example.

In the link provided, the schema seems to be part of the normal operation page as part of the request body table. I believe this is the default behavior for docusaurus-plugin-openapi?
Am I missing something?

This feature request is actually to allow non-operations to appear in the sidebar. Specifically, a new section (like Introduction, but at the bottom) called Schemas whose sub-items are ALL the schemas ONLY, whether used in any operation or not. These schema pages wouldn't have an execute panel since they just display data type + example object info.

Oh okay, is this like the "Models" section of Swagger UI: https://petstore.swagger.io?
Couple UX questions:

Will this just render schemas listed under components.schemas or should it also collect schemas that are defined inline from all of the requests?
Should all of the schemas be part of one Schemas page or should it be a Schemas category, with a page for each schema?

Yep! That's the same idea. I think it should only render components.schemas and it would be a Schemas category with one page per schema.

Hi!
I have the same issue that components.schemas is not rendered in docusaurus (I am also using redocusaurus in addition) and I am just wondering if there is any progress?
Thanks in advance for any replies :)

No progress has been made, but happy to accept a pull request :)

repo: cloud-annotations/docusaurus-openapi


text:
add ocp_network_type var from vault

Description
Get network type var from vault to override in case we need to run test on a particular network type in shift-on-stack CI

why do you need to add this logic via secret instead of just making a profile for each network type, similar to how we do it for the cloud deployments?

@whitleykeith currently shift on stack is running on a scale lab LTA allocation and we have just one deployment of OSP. we can't run the jobs parallelly on it. but still, we need to test all the three SDNs(Kuryr, OpenshiftSDN, and OVNKubernetes). so we thought choosing the SDN using the days logic is easier comparatively having three jobs and synchronizing between them. The SDN is chosen automatically based on the date for any job triggered by a cron job. this vault variable is used only if we want to test any particular SDN manually.

authors: amitsagtani97 masco whitleykeith

repo: cloud-bulldozer/airflow-kubernetes


text:
[RFE] Add more metadata to metric data

From : https://gist.github.com/jtaleric/e2d2b23fcd856d6dd5f5a88ff4b328bc#how-to-trend
We would want to capture some metadata, which would allow us to properly parse the result

platform (string)
version (string)
workload (string)
total node count (int)
encryption (bool)
ipsec (bool)

There are potentially more fields we would want to add.

Agreed.
machine architecture is good to add also. Can be retrieved from the node label: kubernetes.io/arch=arm64

After more kicking of the tires, I noticed we also do not index the iterations as part of the metadata, we should add this too... it is however part of the jobSummary, but iterations should also be something we collect.

also, since some of our benchmarks implement the ability to churn we need to also collect the churn data as that can impact the results.

PR #253 is only a partial fix.. @rsevilla87 is working on another patch to add clusterMetadata.

authors: afcollins jtaleric

repo: cloud-bulldozer/kube-burner


text:
Refactor filter components for reusability

Context
Overview
We would like to reuse our filter components on the recommendations page. To do so, we must refactor them a bit so that they can be used in a more generic sense.
Out of Scope:
Related issues/Dependencies:
Acceptance Criteria

[x] When I am trying to add a new filter to a page, I see there is a generic filter component that can be used with both the estimates and recommendations API responses

Tech Tasks

[x] Refactor Filter Bar component into a common component
[x] Separate filter utilities and emissions utilities
[x] Move any specific filters into the emissions page and extract any common filters
[x] Run Changesets, bump any packages that have been updated/changed
[x] Did you make changes to the client, api or cli package? If so, considering updating the create-app templates.
[x] If any create-app templates have been updated, make sure to run the test-create-app script to ensure it still works properly.

Tech Notes
Review Tasks

[x] eg. specific QA details, update methodology, or update microsite

I pushed a small refactor to packages/client/src/common/FilterBar/FilterBar.tsx to reduce the number of props it requires, but other than that it's looking good! Closing this off.

authors: dtoakley ericksod


text:
Create CP4D layered BOMs

Break apart data fabric BOM to a set of layered boms that can be used for general purpose cp4d, db2, use case, etc...
The layers can be reused for maximo, and other epics
possible layers

cp4d instance
db2
data fabric
demo

https://github.com/cloud-native-toolkit/software-everywhere/issues/61 is related but not exactly the same


text:
Added -busybox switch to handle busybox/alpine containers

Habitus will now correctly run commands in a busybox or an Alpine container as they use /bin/sh for the shell rather than /bin/bash. In addition updated the stat command to get perms of artifacts to execute correctly under busybox.

Also, how does one join your Slack channel? I can not find a link anywhere on habitus.io to allow one to get an invitation to the Slack channel. Might be something you want to put up there if you want to build a community.

Hi @hickey
Thank you very much for the PR. I updated the link to our Slack channel in the github repo's README.
As for the PR content, I think it's better to remove the explicit reference to Busybox and instead allow overriding the shell command with default being /bin/bash while the option would allow the user to switch it to something like /bin/sh if they need. This way we'd have a more inclusive approach.
Would you be able to make that minor adjustment please?

Well, I started out that way by first starting to write a --shell switch to just override the shell being used. That worked until I hit the stat call that was being made and I had to put some more conditional logic to account for the two different arguments that need to be sent to stat. That is when I changed the switch over to --busybox. I can also foresee where there may be another time or two that there will need to be other conditional logic put in place depending on what features Habitus develops.
I briefly considered using --alpine as it was Alpine images that I was working with when I discovered the issue. But the more that I thought about it and started to realize that the common element that was driving the change was Busybox, it made sense to create the switch as --busybox.  This also give a pretty good indication to others as to when the switch is needed.
Maybe you have a suggestion that is escaping me. One thing I would want to avoid (and I would think you would too) is to have 6 different command line switches needing various settings to configure for a specific OS.

I completely agree with your point about not having to configure 6 different things for each OS permutation.
How about making things a bit more generic by introducing a param called --os with a valid value of busybox for now and extending later? This way we won't have to keep adding new params for each of the permutations.

Oh, that would work pretty well.
How about I engineer it so that there is a default of 'linux' (I would like a better label, but can not think of one right now) that has the current functionality and then one can specify busybox or alpine to customize for that style of OS. A similar idea is instead of using 'linux' actually specify the family type of debian or redhat (proably default to debian since it is the most widely used base image) so that if at some point Habitus does use a OS specific command like yum or apt then the changes down the road would be easier and less disruptive.
I will wait to hear back before making any changes. No use having to continually revise code :-)

I like your idea of using the OS type (ie debian or suse). Let's go with that. Thanks!

Hi @hickey have you made any progress on this one? Would love to have it in the next release if we can.

Sorry, I have been retasked on a bunch of things and it got put to the side. I have a good portion of it done. Let me see if I can get it finalized for the early part of next week. Does that work for your schedule?

Absolutely! Thank you for the help @hickey

Sorry, I forget what I was doing that weekend, but never even thought about getting the changes complete. It occurred to me this weekend that there was work to be done. In any event, here is the final changes for the --os switch.

authors: hickey khash


text:
visibility problem

Please include the following information in your ticket.

my CloudantClient is the 0.0.1
i'm using java 8
not using okhttp dependency.
public InputStream queryForStream(String query) {
key(query);
URI uri = databaseHelper.build();
HttpConnection get = Http.GET(uri);
get.requestProperties.put("Accept", "application/json");
return client.couchDbClient.executeToInputStream(get);
}
in this method i've just shown, the problem is that tha visibility of the value "couchDbClient" doesn't let me use it in my class that is in another package. Do you know why this appends?

Closing ticket; user is on an old, unsupported version.

repo: cloudant/java-cloudant


text:
Rename HttpFilters to HttpInterceptors

Rename HttpFilters to HttpInterceptors as per slack discussion. This is to Remove confusing between this API and the changes filter API.
reviewer @tomblench
reviewer @mikerhodes

I think we're good now. Squash into the first commit, and note in the body of the first commit's comment the reason why we renamed, to avoid the clash with replication filter functions.
Then +1.

+1, did an rgrep for filter and couldn't spot any that you missed

authors: mikerhodes rhyshort tomblench

repo: cloudant/sync-android


text:
Cherry-pick VACUUM stats & Vacuum progress related commits.

Cherry-pick some GPDB commits.
This is part 1 of my native Yezzey support for CBDB plan https://github.com/yezzey-gp/yezzey/issues/40#issuecomment-2321149779

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 7 committers have signed the CLA.:x: haolinw:x: Stolb27:x: linxuh:x: AJR-VMware:x: l-wang:x: kainwen:x: huansongYou have signed the CLA already but the status is still pending? Let us recheck it.

UPD: cherry-pick a6fdc27246e46bf3b72d43420c1454a37e68e273 from gp7 to fix incorrect regression test results

Thanks for your Merge Request. I think We'd better revert the last commit which have been merged and squash the last two commit together.

Thanks for your Merge Request. I think We'd better revert the last commit which have been merged and squash the last two commit (refac and 993d11e) together.

Hi, many thanks for your review.
did exacly as you suggested.

Applied all review comments as suggested

hm... it seems that make breaks after this patch...
 > [cloudberry 8/8] RUN locale-gen en_US.utf8 \
 && ./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/gpdb_src > /dev/null \
 && make -j8 > /dev/null \
 && make -j8 install > /dev/null

0.379 Generating locales (this might take a while)...
0.381   en_US.UTF-8... done
1.244 Generation complete.
29.97 appendonlyam.c: In function 'appendonly_insert':
29.98 appendonlyam.c:3052:9: error: unused variable 'firstSequence' [-Werror=unused-variable]
29.98  3052 |   int64 firstSequence = GetFastSequences(aoInsertDesc->segrelid,
29.98       |         ^~~~~~~~~~~~~
30.38 cc1: all warnings being treated as errors
30.38 make[4]: *** [<builtin>: appendonlyam.o] Error 1
30.38 make[4]: *** Waiting for unfinished jobs....
30.64 make[3]: *** [../../../src/backend/common.mk:39: appendonly-recursive] Error 2
30.64 make[3]: *** Waiting for unfinished jobs....
31.84 make[2]: *** [common.mk:39: access-recursive] Error 2
31.84 make[2]: *** Waiting for unfinished jobs....
34.40 make[1]: *** [Makefile:44: all-backend-recurse] Error 2
34.40 make: *** [GNUmakefile:11: all-src-recurse] Error 2

Good news - it works fine with
./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/gpdb_src --enable-debug

hm... it seems that make is broken (for me) after this patch...
 > [cloudberry 8/8] RUN locale-gen en_US.utf8 \
 && ./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/gpdb_src > /dev/null \
 && make -j8 > /dev/null \
 && make -j8 install > /dev/null

0.379 Generating locales (this might take a while)...
0.381   en_US.UTF-8... done
1.244 Generation complete.
29.97 appendonlyam.c: In function 'appendonly_insert':
29.98 appendonlyam.c:3052:9: error: unused variable 'firstSequence' [-Werror=unused-variable]
29.98  3052 |   int64 firstSequence = GetFastSequences(aoInsertDesc->segrelid,
29.98       |         ^~~~~~~~~~~~~
30.38 cc1: all warnings being treated as errors
30.38 make[4]: *** [<builtin>: appendonlyam.o] Error 1
30.38 make[4]: *** Waiting for unfinished jobs....
30.64 make[3]: *** [../../../src/backend/common.mk:39: appendonly-recursive] Error 2
30.64 make[3]: *** Waiting for unfinished jobs....
31.84 make[2]: *** [common.mk:39: access-recursive] Error 2
31.84 make[2]: *** Waiting for unfinished jobs....
34.40 make[1]: *** [Makefile:44: all-backend-recurse] Error 2
34.40 make: *** [GNUmakefile:11: all-src-recurse] Error 2

Thanks for your feedback! will take a look soon

hm... it seems that make is broken (for me) after this patch...
 > [cloudberry 8/8] RUN locale-gen en_US.utf8 \
 && ./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/gpdb_src > /dev/null \
 && make -j8 > /dev/null \
 && make -j8 install > /dev/null

0.379 Generating locales (this might take a while)...
0.381   en_US.UTF-8... done
1.244 Generation complete.
29.97 appendonlyam.c: In function 'appendonly_insert':
29.98 appendonlyam.c:3052:9: error: unused variable 'firstSequence' [-Werror=unused-variable]
29.98  3052 |   int64 firstSequence = GetFastSequences(aoInsertDesc->segrelid,
29.98       |         ^~~~~~~~~~~~~
30.38 cc1: all warnings being treated as errors
30.38 make[4]: *** [<builtin>: appendonlyam.o] Error 1
30.38 make[4]: *** Waiting for unfinished jobs....
30.64 make[3]: *** [../../../src/backend/common.mk:39: appendonly-recursive] Error 2
30.64 make[3]: *** Waiting for unfinished jobs....
31.84 make[2]: *** [common.mk:39: access-recursive] Error 2
31.84 make[2]: *** Waiting for unfinished jobs....
34.40 make[1]: *** [Makefile:44: all-backend-recurse] Error 2
34.40 make: *** [GNUmakefile:11: all-src-recurse] Error 2

Does this PR make a fix for you https://github.com/cloudberrydb/cloudberrydb/pull/674 ?

thanks! Build & test from main branch works fine now.

authors: CLAassistant lss602726449 ostinru reshke

repo: cloudberrydb/cloudberrydb


text:
🛑 exabytes.co.id is down

In 84045d7, exabytes.co.id (https://exabytes.co.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: exabytes.co.id is back up in ce28c4d.

repo: cloudbip/upptime


text:
🛑 cbn.id is down

In 5600930, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 3ff14e4.


text:
🛑 cbn.id is down

In f1a281c, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in fac04f6.


text:
🛑 cbn.id is down

In 11ecc96, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in edbf440.


text:
🛑 cbn.id is down

In 2641a81, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in b1230ea after 38 minutes.


text:
🛑 lintas.net.id is down

In b784f0f, lintas.net.id (https://lintas.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lintas.net.id is back up in c28c2b3 after 41 minutes.


text:
🛑 cbn.id is down

In 2e6dcff, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in da2c7ec.


text:
Best place for custom joins?

I was wondering where is the best place to add some custom joins to the index query?
Currently, I am overwriting the queryAll method in the Adapter but it doesn‘t feel right.
Is there any function or hook which is better suited?
Thanks in advance!

Hey! queryAll would seem like the right place. The thing to be aware of is that method is also used when the resource appears in a to-many relationship (the $query will be an Eloquent relationship query).
Do you have any suggestions as to how it would be better to add joins? What is your join being used for?

Thank you! I would like to query relationship counts and for example the customer_value (the sum of all related orders for a customer) in an efficient way. Additionally, sometimes it is more efficient to add the customer_name as an attribute directly to the order. That way I don't need a separate query for the related customer when I only need the name. I'd love to see a function, like the filter() function, where I can easily extend the query without overwriting anything.

Hey! Do you have any update to this issue or do you plan to include a separate function? Because it seems like the queryAll() or with() method does not affect the read request for a single resource. I would like to avoid to duplicate my logic for the read method.

Hi! I'm not adverse to adding a new hook in, but I'm not sure what this hook would be, and under what circumstances it would get called? That would need to be clear for me to add it in - do you have any suggestions?
One thing to mention is that in these kind of scenarios, we've implemented it by putting all these values in a related resource that the client can choose to include or not. So for example, we'd have customers resource, and that would have all the attributes to do with the order's customer. Then that gets included only if the client asks for it to be included. Resources don't need to match your Eloquent models. The thing that makes me think that might apply in your scenario is this comment:

Additionally, sometimes it is more efficient to add the customer_name as an attribute directly to the order.

The purpose of the JSON API spec is to give the client control over what it is asking for. How are you determining when to put the customer name attribute on the order or not? Whether attributes are in the response or not is defined in the spec using the fields query param.
(Sorry for all the question - just trying to figure out what the best way to approach this use case is!)

Hey @lindyhopchris,
we would need a function (e.g. join()) which is called from the AbstractAdapter's query() and the find() function and should have the $query as an argument. You would then override the join() method in the Adapter and like:
public function join($query) {
$query->join('customers', 'orders.customer_id', '=', 'customers.id')
->addSelect(DB::raw("CONCAT(customers.given_name, ' ', customers.family_name) AS customer_name"));
}

To use the newly selected attribute, you can simply add the customer_name to the Schema and the fieldset selection from the client will work just fine. The client would even be able to sort by those new columns after adding them to the $sortColumns array and implementing #303 .
Another important use case for me is to add custom selection, like concatenating the customer name to the full_name on the fly or add counts to my resource. Therefore the method could also be named addSelect().

Ok. I think that join is too specific a use-case name for a hook that could be used for multiple use-cases.
It's more about how you are querying the resource, so the hooks I think should be:

querying: always called
queryingOne: called only one querying a single resource e.g. /comments/123
queryingMany: called when querying zero-to-many resources, e.g. /comments and /posts/1/comments

I totally agree with you. The naming and separation of the hook looks perfect.
Thank you in advance for the implementation! 🙏

Hi @lindyhopchris, are there any updates on this issue?
Would really appreciate a querying hook.

No update I'm afraid - combination of too much other work going on, and me being in two minds about adding these querying hooks, or supporting them in some other way.
Let me have another think about these.

repo: cloudcreativity/laravel-json-api


text:
Add DESCRIBE to MySql dialect autocomplete

Reusing https://github.com/cloudera/hue/pull/1684

@agl29 Another one where we could see for adding "describe/describe_table.jison", in the mysql dialect

@agl29 Another one where we could see for adding "describe/describe_table.jison", in the mysql dialect

repo: cloudera/hue


text:
Update conda recipes for Ibis 0.6.0

Built and tested with Python 2.7 and Python 3.4 on osx-64, linux-64, and win-64.
Conda packages for Ibis 0.6.0 can be installed using:
conda install ibis-framework -c koverholt

The first commit contains recipes for Ibis 0.6.0 from PyPI, and the second commit restores the edits from #712 to pull from trunk (apologies, I initially didn't see those edits).
Either way, the conda packages for Ibis 0.6.0 are available at the above conda channel.

These changes also allow py34 / 35? builds

I only tested with and built py27 and py34 packages at the moment.

Sorry I've been slow on this. Will merge, but are some Python 3.x issues with the library stack (API changes in thriftpy as far as I can tell), but we can address those after I get everything working

@mariusvniekerk I've moved to 3.5 for my primary development environment finally, so should have better ongoing support for 3.x. Lot of Hadoop users are still stuck on 2.x though.

Yeah 3.5 is much nicer. I'm still stuck on 2.7 myself. (Thrift dependencies
using protocols not in thriftpy yet). I'll update the recipes to make
Thrift a 2.x only requirement.
On Mon, Jan 18, 2016 at 18:17 Wes McKinney notifications@github.com wrote:

@mariusvniekerk https://github.com/mariusvniekerk I've moved to 3.5 for
my primary development environment finally, so should have better ongoing
support for 3.x. Lot of Hadoop users are still stuck on 2.x though.
—
Reply to this email directly or view it on GitHub
https://github.com/cloudera/ibis/pull/753#issuecomment-172678818.

authors: koverholt mariusvniekerk wesm

repo: cloudera/ibis


text:
bug with request

when i'am try to create new zone by example:
$ python2 example-create-zone-and-populate.py examol.biz
Create zone examol.biz ...
/zones.post examol.biz - request() got an unexpected keyword argument 'json'
Python 2.7.11
system: os x 10.11

please open this issue in https://github.com/cloudflare/python-cloudflare/issues

authors: Dolbager gnowxilef


text:
Change downloads beta availability wording

@zaidf

super, thank you @kodster28!

repo: cloudflare/cloudflare-docs


text:
fix: update cname_name to cname

The CustomHostname struct is different from api
{
  "result": {
    "id": "x",xxxx
    "hostname": "draveness.me",
    "ssl": {
      "id": "x",xxx
      "type": "dv",
      "method": "cname",
      "status": "pending_validation",
      "cname": "_ca3-xxxxx.draveness.me",
      "cname_target": "dcv.digicert.com"
    }
  },
  "success": true
}

Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[x] Bug fix (non-breaking change which fixes an issue)

here are the docs https://api.cloudflare.com/#custom-hostname-for-a-zone-properties

authors: draveness sevki

repo: cloudflare/cloudflare-go


text:
HTTP DDoS cannot change General Action

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform version: 1.0.4
cloudflare/cloudflare v3.7.0
Affected resource(s)
cloudflare_ruleset
Terraform configuration files
resource "cloudflare_ruleset" "zone_level_ddos" {
  for_each    = { for ddos_rule in var.ddos_rules : ddos_rule["name"] => ddos_rule }
  zone_id     = each.value["zone_id"]
  name        = each.value["name"]
  description = each.value["description"]
  kind        = "zone"
  phase       = "ddos_l7"

  rules {
    action = "execute"
    action_parameters {
      id = "4d21379b4f9f4bb088e0729962c8b3cf"
      overrides {
        action = "log"
      }
    }
    expression  = "true"
    description = "override HTTP DDoS ruleset rule"
    enabled     = true
  }
}

Debug output

  # module.cloudflare.cloudflare_ruleset.zone_level_ddos["DDoS"] will be updated in-place
  ~ resource "cloudflare_ruleset" "zone_level_ddos" {
        id          = "07b5e455e4c341ccbefa3f6230ef52ae"
        name        = "DDoS"
        # (4 unchanged attributes hidden)

      ~ rules {
          ~ description = "Execute DDoS L7 Ruleset on my zone-level phase entry point ruleset" -> "override HTTP DDoS ruleset rule"
            id          = "951da5a671d24fe5862fc10b853393b4"
            # (3 unchanged attributes hidden)

          ~ action_parameters {
                id        = "4d21379b4f9f4bb088e0729962c8b3cf"
                # (5 unchanged attributes hidden)

              ~ overrides {
                  ~ action  = "block" -> "log"
                    # (1 unchanged attribute hidden)
                }
            }
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.
2022-01-25T10:07:37.305Z [DEBUG] command: asking for input: "\nDo you want to perform these actions?"

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

2022-01-25T10:07:47.473Z [INFO]  backend/local: apply calling Apply
2022-01-25T10:07:47.473Z [INFO]  terraform: building graph: GraphTypeApply
2022-01-25T10:07:47.475Z [DEBUG] adding implicit provider configuration provider["terraform.io/builtin/terraform"], implied first by data.terraform_remote_state.cloudflare_org (expand)
2022-01-25T10:07:47.476Z [DEBUG] ProviderTransformer: "module.cloudflare.cloudflare_ruleset.zone_level_managed_waf (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/cloudflare/cloudflare"]
2022-01-25T10:07:47.476Z [DEBUG] ProviderTransformer: "module.cloudflare.cloudflare_ruleset.zone_level_ddos[\"DDoS\"]" (*terraform.NodeApplyableResourceInstance) needs provider["registry.terraform.io/cloudflare/cloudflare"]
2022-01-25T10:07:47.476Z [DEBUG] ProviderTransformer: "data.terraform_remote_state.cloudflare_org (expand)" (*terraform.nodeExpandApplyableResource) needs provider["terraform.io/builtin/terraform"]
2022-01-25T10:07:47.476Z [DEBUG] ProviderTransformer: "module.cloudflare.cloudflare_ruleset.zone_level_ddos (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/cloudflare/cloudflare"]
2022-01-25T10:07:47.476Z [DEBUG] ProviderTransformer: "module.cloudflare.cloudflare_firewall_rule.firewall_rule (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/cloudflare/cloudflare"]
2022-01-25T10:07:47.477Z [DEBUG] ProviderTransformer: "module.cloudflare.cloudflare_filter.filter (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/cloudflare/cloudflare"]
2022-01-25T10:07:47.478Z [ERROR] AttachSchemaTransformer: No provider config schema available for provider["terraform.io/builtin/terraform"]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.cloudflare_filter.filter (expand)" references: [module.cloudflare.var.firewall_rules (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.var.ddos_rules (expand)" references: [local.ddos_rules (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.firewall_rules_hivebrite (expand)" references: [local.firewall_rules_map (expand) data.terraform_remote_state.cloudflare_org (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.waf_rules (expand)" references: [local.waf_rules_hvbrt (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.waf_rules_map (expand)" references: []
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "data.terraform_remote_state.cloudflare_org (expand)" references: []
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.cloudflare_ruleset.zone_level_ddos (expand)" references: [module.cloudflare.var.ddos_rules (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.cloudflare_firewall_rule.firewall_rule (expand)" references: [module.cloudflare.var.firewall_rules (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.ddos_rules_map (expand)" references: []
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "provider[\"terraform.io/builtin/terraform\"]" references: []
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.account_id (expand)" references: [data.terraform_remote_state.cloudflare_org (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.var.account_id (expand)" references: [local.account_id (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.firewall_rules_hvbrt (expand)" references: [local.firewall_rules_map (expand) data.terraform_remote_state.cloudflare_org (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.waf_rules_hvbrt (expand)" references: [local.waf_rules_map (expand) data.terraform_remote_state.cloudflare_org (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare (expand)" references: []
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.var.firewall_rules (expand)" references: [local.firewall_rules (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "module.cloudflare.var.waf_rules (expand)" references: [local.waf_rules (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.firewall_rules (expand)" references: [local.firewall_rules_hvbrt (expand) local.firewall_rules_hivebrite (expand)]
2022-01-25T10:07:47.478Z [DEBUG] ReferenceTransformer: "local.ddos_rules_hvbrt (expand)" references: [local.ddos_rules_map (expand) data.terraform_remote_state.cloudflare_org (expand)]
2022-01-25T10:07:47.479Z [INFO]  ReferenceTransformer: reference not found: "each.value"
2022-01-25T10:07:47.479Z [INFO]  ReferenceTransformer: reference not found: "each.value"
2022-01-25T10:07:47.479Z [INFO]  ReferenceTransformer: reference not found: "each.value"
2022-01-25T10:07:47.479Z [DEBUG] ReferenceTransformer: "module.cloudflare.cloudflare_ruleset.zone_level_ddos[\"DDoS\"]" references: [module.cloudflare.var.ddos_rules (expand)]
2022-01-25T10:07:47.479Z [DEBUG] ReferenceTransformer: "provider[\"registry.terraform.io/cloudflare/cloudflare\"]" references: [local.account_id (expand)]
2022-01-25T10:07:47.479Z [DEBUG] ReferenceTransformer: "module.cloudflare (close)" references: []
2022-01-25T10:07:47.479Z [DEBUG] ReferenceTransformer: "module.cloudflare.cloudflare_ruleset.zone_level_managed_waf (expand)" references: [module.cloudflare.var.waf_rules (expand)]
2022-01-25T10:07:47.479Z [DEBUG] ReferenceTransformer: "local.firewall_rules_map (expand)" references: []
2022-01-25T10:07:47.479Z [DEBUG] ReferenceTransformer: "local.ddos_rules (expand)" references: [local.ddos_rules_hvbrt (expand)]
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: module.cloudflare.cloudflare_ruleset.zone_level_managed_waf (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: module.cloudflare.cloudflare_firewall_rule.firewall_rule (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: module.cloudflare.cloudflare_filter.filter (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: module.cloudflare.var.account_id (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: module.cloudflare.var.waf_rules (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: module.cloudflare.var.firewall_rules (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.waf_rules (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.firewall_rules (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.firewall_rules_hivebrite (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.firewall_rules_hvbrt (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.waf_rules_hvbrt (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.firewall_rules_map (expand) is no longer needed, removing
2022-01-25T10:07:47.479Z [DEBUG] pruneUnusedNodes: local.waf_rules_map (expand) is no longer needed, removing
2022-01-25T10:07:47.480Z [DEBUG] Starting graph walk: walkApply
2022-01-25T10:07:47.481Z [DEBUG] created provider logger: level=debug
2022-01-25T10:07:47.481Z [INFO]  provider: configuring client automatic mTLS
2022-01-25T10:07:47.519Z [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.7.0/linux_amd64/terraform-provider-cloudflare_v3.7.0 args=[.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.7.0/linux_amd64/terraform-provider-cloudflare_v3.7.0]
2022-01-25T10:07:47.519Z [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.7.0/linux_amd64/terraform-provider-cloudflare_v3.7.0 pid=138
2022-01-25T10:07:47.519Z [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.7.0/linux_amd64/terraform-provider-cloudflare_v3.7.0
2022-01-25T10:07:47.523Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: configuring server automatic mTLS: timestamp=2022-01-25T10:07:47.523Z
2022-01-25T10:07:47.532Z [DEBUG] provider.terraform-provider-cloudflare_v3.7.0: plugin address: address=/tmp/plugin3324601428 network=unix timestamp=2022-01-25T10:07:47.532Z
2022-01-25T10:07:47.532Z [DEBUG] provider: using plugin: version=5
2022-01-25T10:07:47.566Z [WARN]  ValidateProviderConfig from "provider[\"registry.terraform.io/cloudflare/cloudflare\"]" changed the config value, but that value is unused
2022-01-25T10:07:47.566Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: 2022/01/25 10:07:47 [INFO] Cloudflare Client configured for user:: timestamp=2022-01-25T10:07:47.566Z
2022-01-25T10:07:47.566Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: 2022/01/25 10:07:47 [INFO] Using specified account id f0c9334a714988fdfcf85a0c4d1b2406 in Cloudflare provider: timestamp=2022-01-25T10:07:47.566Z
2022-01-25T10:07:47.566Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: 2022/01/25 10:07:47 [INFO] Cloudflare Client configured for user:: timestamp=2022-01-25T10:07:47.566Z
2022-01-25T10:07:47.571Z [WARN]  Provider "registry.terraform.io/cloudflare/cloudflare" produced an invalid plan for module.cloudflare.cloudflare_ruleset.zone_level_ddos["DDoS"], but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .rules[0].action_parameters[0].products: planned value cty.SetValEmpty(cty.String) for a non-computed attribute
      - .rules[0].action_parameters[0].rules: planned value cty.MapValEmpty(cty.String) for a non-computed attribute
      - .rules[0].action_parameters[0].ruleset: planned value cty.StringVal("") for a non-computed attribute
      - .rules[0].action_parameters[0].rulesets: planned value cty.SetValEmpty(cty.String) for a non-computed attribute
      - .rules[0].action_parameters[0].increment: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .rules[0].action_parameters[0].overrides[0].enabled: planned value cty.False for a non-computed attribute
module.cloudflare.cloudflare_ruleset.zone_level_ddos["DDoS"]: Modifying... [id=07b5e455e4c341ccbefa3f6230ef52ae]
2022-01-25T10:07:47.572Z [INFO]  Starting apply for module.cloudflare.cloudflare_ruleset.zone_level_ddos["DDoS"]
2022-01-25T10:07:47.572Z [DEBUG] module.cloudflare.cloudflare_ruleset.zone_level_ddos["DDoS"]: applying the planned Update change
2022-01-25T10:07:47.575Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: 2022/01/25 10:07:47 [DEBUG] unknown key encountered in buildRulesetRulesFromResource for action parameters: products: timestamp=2022-01-25T10:07:47.575Z
2022-01-25T10:07:47.575Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: 2022/01/25 10:07:47 [DEBUG] Cloudflare API Request Details:
---[ REQUEST ]---------------------------------------
PUT /client/v4/zones/e23ded7d7fb96271f13f24c728ebda7e/rulesets/07b5e455e4c341ccbefa3f6230ef52ae HTTP/1.1
Host: api.cloudflare.com
User-Agent: terraform/1.0.4 terraform-plugin-sdk/2.10.1 terraform-provider-cloudflare/3.7.0
Content-Length: 278
Authorization: Bearer 6fZsNW7R23Ef-g7ne3Rql8Z9wnWAQa4fT-3BvBCd
Content-Type: application/json
Accept-Encoding: gzip

{
 "description": "Enables DDoS ruleset",
 "rules": [
  {
   "action": "execute",
   "action_parameters": {
    "id": "4d21379b4f9f4bb088e0729962c8b3cf",
    "overrides": {
     "enabled": false,
     "action": "log"
    },
    "version": "latest"
   },
   "expression": "true",
   "description": "override HTTP DDoS ruleset rule",
   "enabled": true
  }
 ]
}
-----------------------------------------------------: timestamp=2022-01-25T10:07:47.575Z
2022-01-25T10:07:49.274Z [INFO]  provider.terraform-provider-cloudflare_v3.7.0: 2022/01/25 10:07:49 [DEBUG] Cloudflare API Response Details:
---[ RESPONSE ]--------------------------------------
HTTP/2.0 400 Bad Request
Cf-Cache-Status: DYNAMIC
Cf-Ray: 6d30b255899c0487-CDG
Content-Type: application/json; charset=UTF-8
Date: Tue, 25 Jan 2022 10:07:49 GMT
Expect-Ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
Set-Cookie: __cflb=0H28vgHxwvgAQtjUGU56Rb8iNWZVUvXheFepa87165j; SameSite=Lax; path=/; expires=Tue, 25-Jan-22 12:37:50 GMT; HttpOnly
Set-Cookie: __cfruid=e7d001383ec23a539d9dec1595c4c53d58396d24-1643105269; path=/; domain=.api.cloudflare.com; HttpOnly; Secure; SameSite=None
Vary: Accept-Encoding
X-Envoy-Upstream-Service-Time: 137
X-Version: 4866-75a0cc67c02c

{
  "result": null,
  "success": false,
  "errors": [
    {
      "message": "DDoS L7 overrides cannot use the enabled field"
    }
  ],
  "messages": null
}

-----------------------------------------------------: timestamp=2022-01-25T10:07:49.273Z
╷
│ Error: error updating ruleset with ID "07b5e455e4c341ccbefa3f6230ef52ae": HTTP status 400: DDoS L7 overrides cannot use the enabled field
│
│   with module.cloudflare.cloudflare_ruleset.zone_level_ddos["DDoS"],
│   on .terraform/modules/cloudflare/ddos_rules.tf line 1, in resource "cloudflare_ruleset" "zone_level_ddos":
│    1: resource "cloudflare_ruleset" "zone_level_ddos" {
│
╵
2022-01-25T10:07:49.785Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-01-25T10:07:49.788Z [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/cloudflare/cloudflare/3.7.0/linux_amd64/terraform-provider-cloudflare_v3.7.0 pid=138
2022-01-25T10:07:49.788Z [DEBUG] provider: plugin exited
[terragrunt] 2022/01/25 10:07:49 Hit multiple errors:
exit status 1
Makefile:42: recipe for target 'apply' failed
make: *** [apply] Error 1

Panic output
No response
Expected output
I expected the Ruleset action changed to "log"
Actual output
I expected the Ruleset action changed to "log"
Steps to reproduce

Create the cloudflare_ruleset per code provided above
Run a terraform plan/apply

Additional factoids
In addition to this, also the "default" state should be a possibility to put in the "action" variable.
Related to this. I didn't find the way to change the sensitivity_level for all the rules in the ruleset. Is this implemented?

Thanks,
Miquel
References
https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/ruleset
https://github.com/cloudflare/terraform-provider-cloudflare/pull/1212/files

could you please try the master branch? #1405 should have addressed this.

Related to this. I didn't find the way to change the sensitivity_level for all the rules in the ruleset. Is this implemented?

only as an override - https://github.com/cloudflare/terraform-provider-cloudflare/blob/276302a83bf23528e800f1116724445f0f84be79/cloudflare/resource_cloudflare_ruleset_test.go#L1928. you can check what the UI is doing and attempt to emulate it in the resource and it may work.

Thanks @jacobbednarz

authors: jacobbednarz mcatany


text:
Add header + caching to runtime type generation

What this PR solves / how to test
Fixes #[insert GH or internal issue number(s)].
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Included
[ ] Not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required / Maybe required
[ ] Not required because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[ ] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[ ] Not necessary because:

Converting to draft because this feels like it is not yet ready for review.

authors: penalosa petebacondarwin

repo: cloudflare/workers-sdk


text:
[dev] fix: properly route to new preview id after reload

Fixes #1082 and might fix #1107
We keep preview_id in an Arc<Mutex so that when a reload is detected on another thread, the dev server can properly route new requests to the new preview_id. Previously, the server would only attempt to acquire the lock every couple of minutes. After moving the lock acquisition to service_fn from make_service_fn, the lock is acquired on every request, making sure that each request is going to the right version of the script.

Previously, the server would only attempt to acquire the lock every couple of minutes

That would explain why small changes sometimes would not take.

Yup! We're going to try to get this fix into a point release today.

authors: EverlastingBugstopper tomByrer

repo: cloudflare/wrangler