text:
test/k8sT: wait for DNS to be ready in Kafka pods

We have observed that while DNS lookups succeed from the host for the various
services used in the Kafka Policies test, the CI has failed with errors like the
following:
"Removing server kafka-service:9092 from bootstrap.servers as DNS resolution
failed for kafka-service"
To prevent this issue, ensure that "nslookup" succeeds within each Kafka pod
itself for "kafka-service".
Signed-off by: Ian Vernon ian@cilium.io
Fixes: #4951

This change is

Quick question, why the DNS check should happening in the Pods? we already wait on lines L125-L130.
Can be merged, but I think that something is weird here that we need to deep a bit further!

We test that the DNS domain name resolves from the host, but not from within the pod. It may not resolve yet within the pod, e.g. if no policy has yet been generated for the pod, so we're still dropping all traffic. This PR makes sure that the pod both has connectivity and can resolve the DNS domain name.

Maybe we need to do the endpoint Ready on the BeforeAll function.
err := kubectl.CiliumEndpointWaitReady()
Expect(err).To(BeNil(), "Endpoints are not ready after timeout")

Microscope failed, not related to this one I'll merge this one.
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/5219/testReport/k8s-1/11/K8sValidatedMicroscope_Runs_microscope/

@ianvernon was this backported? I don't see any reference from a backport PR and the label still says pending.

authors: eloycoto ianvernon joestringer rlenglet


text:
v1.5: backports 19-07-03

Backported PRs:

PR: 8402 -- pkg/kvstore: fix nil pointer in error while doing a transaction in etcd  (@aanm) -- https://github.com/cilium/cilium/pull/8402
PR: 8408 -- operator: add warning message if status returns an error (@aanm) -- https://github.com/cilium/cilium/pull/8408
PR: 8416 -- maps/lbmap: protect service cache refcount with concurrent access (@aanm) -- https://github.com/cilium/cilium/pull/8416
PR: 8417 -- pkg/k8s: do not parse empty annotations (@aanm) -- https://github.com/cilium/cilium/pull/8417
PR: 8427 -- pkg/kvstore: add etcd lease information into cilium status (@aanm) -- https://github.com/cilium/cilium/pull/8427
PR: 8388 -- daemon: Change loglevel of "ipcache entry owned by kvstore or agent" (@brb) -- https://github.com/cilium/cilium/pull/8388
PR: 8444 -- test: set 1.15 by default in CI Vagrantfile (@aanm) -- https://github.com/cilium/cilium/pull/8444
PR: 8443 -- Change nightly CI job label from fixed to baremetal (@nebril) -- https://github.com/cilium/cilium/pull/8443
PR: 8453 -- pkg/k8s: hold mutex while adding events to the queue (@aanm) -- https://github.com/cilium/cilium/pull/8453
PR: 8462 -- Retry provisioning vagrant vms in CI (@nebril) -- https://github.com/cilium/cilium/pull/8462
PR: 8449 -- cli: fix panic in cilium bpf sha get command (@fristonio) -- https://github.com/cilium/cilium/pull/8449

When you have backported the above commits, you can update the PR labels via this command:
$ for pr in 8402 8408 8416 8417 8427 8388 8444 8443 8453 8462 8449; do contrib/backporting/set-labels.py $pr pending 1.5; done

This change is

test-me-please

test-missed-k8s

test-docs-please

test-upstream-k8s

Will re-run the failed tests once the CI provisioning errors have been fixed.

test-me-please

test-missed-k8s

Normal Gingko tests failed in a variety of ways: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/13466/

test-me-please

Upstream K8s tests failed due to provisioning error: https://jenkins.cilium.io/job/Cilium-PR-Kubernetes-Upstream/1385/execution/node/42/log/

test-upstream-k8s

Runtime egress policy tests are failing? https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/13479/

test-me-please

test-missed-k8s

test-docs-please

test-upstream-k8s

I reverted the Envoy log reduction commits and the L3-dependent L7 egress tests started passing. Given that this is not a critical bugfix for v1.5, I removed it from this PR.

Cilium-Ginkgo-Tests failed: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/13489/testReport/junit/Suite-k8s-1/15/K8sIstioTest_Istio_Bookinfo_Demo_Tests_bookinfo_inter_service_connectivity/
Istio pods couldn't get ready. Investigating while triggering build again.

test-me-please

Cilium-Ginkgo-Tests-K8s failed as well: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/2268/

FQDN restart test failed (this is a known issue - https://github.com/cilium/cilium/issues/8234 .
Istio test failed too - it looks like kube-apiserver and kube-scheduler restarted, which is cause for concern (and hopefully unrelated to Cilium!).

Will triage, and yet again, I am trying again!

test-missed-k8s

K8s tests failed: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/2270/
Pod got stuck in ContainerCreating state:
2019-07-09T17:40:49.196188634Z level=warning msg="Error changing endpoint identity" containerID=9f429b53af datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=3767 error="unable to resolve identity: key allocation cancelled: context canceled" identityLabels="k8s:io.cilium.k8s.policy.cluster=default,k8s:io.cilium.k8s.policy.serviceaccount=default,k8s:io.kubernetes.pod.namespace=default,k8s:zgroup=testDSClient" ipv4=10.10.1.57 ipv6= k8sPodName=default/testclient-sm9jn subsys=endpoint

Identity could not be resolved for the endpoint. This might be due to etcd-operator connectivity being disrupted :(

test-missed-k8s

I've given up on the upstream K8s tests, they appear to be broken in the provisioning stages.

source: gharchive/pull-request

authors: brb ianvernon

repo: cilium/cilium

license_type: permissive

license_source: github-api


text:
bpf, nat: initially try snat by preserving source port

Originally we moved the prandom call out of the unrolled port collision
loop in order to reduce verifier complexity but it seems better if we
first try to preserve as much as possible before doing any rewrites. For
latter we need to reduce the retry loop on older kernels when v4 + v6 is
enabled as a trade-off between 4.19.57 and 5.3.
Signed-off-by: Daniel Borkmann daniel@iogearbox.net

This change is

test-me-please

Coverage increased (+0.06%) to 45.915% when pulling 3a3f4e1815f22003aaaa0eb1024c5bf02f1fa5b3 on pr/nodeport-retry-sport into 0c01497a35ecf16fa7bf5d412afc41c11893b27f on master.

authors: borkmann coveralls


text:
USB inconsistantly mounts in Model 3

I have had intermittent issues with the usb drive not showing up when plugged into my Tesla.  Almost 100% of the time if I unplug/plug back in the PI the car recognizes the drive and everything works fine.
The issue happens both in range and out of range of the archive server.  If I connect to the pi and look at the logs it goes through the unmounting/mounting process fine and shows no errors.
I have noticed from time to time if I plug the PI into my Mac I will get a drive not recognized error, but on the PI everything looks ok from what I can tell.
Is there a way for the PI to know if files are being written to the TeslaUsb drive, and if not have it remount it?

I noticed this issue as well but curiously, this issue did not occur with the original code.  I happened after I updated the setup on 31Oct.

source: gharchive/issue

authors: RogerNorth lolento

repo: cimryan/teslausb

license: MIT


text:
🛑 Collection Analysis Datasette is down

In b9cd344, Collection Analysis Datasette (https://collection-analysis.cincy.pl/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Collection Analysis Datasette is back up in 082ad69 after 1 hour, 1 minute.

repo: cincinnatilibrary/uptime-reports


text:
Unhandled Promise Rejection in Safari

The Example doesn't play in Safari 11 on Mac, it print the following exception, any idea?

[Error] Unhandled Promise Rejection: NotAllowedError (DOM Exception 35): The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.
(anonyme Funktion)
rejectPromise
play
tryToUnwrap (vast-player.js:2607)
tryCatch (vast-player.js:2619)
safelyResolveThenable (vast-player.js:2610)
Promise (vast-player.js:2484)
startAd (vast-player.js:889)
callMethod (vast-player.js:227)
(anonyme Funktion) (vast-player.js:2534)
nextTick (vast-player.js:2774)

Further investigations: Safari requires "click to play", this Error is caused by autoplay. The following article explains how to handle it:  http://2ality.com/2016/04/unhandled-rejections.html.
By adding a button with an onclick=... below the container I was able to start the video inside an onclick-Handler ... but player.startAd() still raises above handler. I had to poke behind the private with: player.private.player.video.play();
Maybe the eventhandler and an auto-click-to-play-button could be integrated somehow?

I don't want to add a button in this library as it leaves the user interface entirely up to the user. However, it should be possible to modify the code so that player.private.player.video.play() is called synchronously from player.startAd(), which should allow the video to play as long as player.startAd() is called synchronously within a click handler.
However, just from looking at the code, I can't see where the async-ness would be sneaking in. Are you sure you were calling player.startAd() synchronously and not in a callback? For example:
element.onclick = () => {
  player.load('tag.xml').then(() => {
    player.startAd(); // won't work because this is an async callback.
  });
};

If you could post a jsfiddle that demonstrates your issue, I'd be happy to check it out!

You're right ... I've setup a fiddle here and it works well on Safari too. Sorry, my issue must be somewhere else.

authors: hwde minznerjosh

license: mit

license_source: bigquery


text:
⚠ Cioos National CKAN has degraded performance

In 5cbd850, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 21536 ms

Resolved: Cioos National CKAN performance has improved in dc12ef1 after 5 minutes.

repo: cioos-siooc/cwatch-upptime


text:
Alarm card as panel

Correct sizing when using with panel: true

This will need migration of fixed size tovw and vw units.

Now card supports 'scale' parameter

repo: ciotlosm/custom-lovelace


text:
the "pageSizeOptions" inAPI should be changed to "pageSizeSelectorValues"

Bug Report or Feature Request

The parmas "pageSizeOptions" seems is not exist , when I try to use it to change the pageSize Options , the browser gave me a error , but "pageSizeSelectorValues" works !!!
What is expected?

use "pageSizeOptions" to change the pageSize Options
What is actually happening?

the browser hints mistake

ng-alain version: 0.7.1
Angular version: 5.0.0
Browser:
- Chrome (desktop) version 58.0.3029.110

ng-alain.com currently at version 1.0.0-beta, i will publish 0.8.x version document.

authors: Miss-violet cipchk

repo: cipchk/ng-alain


text:
problem building openh264 for android platform

I'm trying to build openh264 for android with following command :
$ make OS=android NDKROOT=/Users/nazmulhasan/android-ndk-r10d TARGET=android-17 ARCH=x86

And getting the following error:
/Users/nazmulhasan/android-ndk-r10d/toolchains/x86-4.8/prebuilt/darwin-x86/bin/../lib/gcc/i686-linux-android/4.8/../../../../i686-linux-android/bin/ld: error: codec/common/cpu-features.o: incompatible target
codec/common/src/WelsThreadLib.o:WelsThreadLib.cpp:function WelsQueryLogicalProcessInfo: error: undefined reference to 'wels_getCpuCount'

Hi, can you try:

make OS=android NDKROOT=/Users/hfvideomac/wspace/bin/android-ndk-r9d TARGET=android-19

It sounds to me like your build environment is unclean (e.g. codec/common/cpu-features.o exists but is for a different architecture). To clean it properly, do make OS=android NDKROOT=/Users/nazmulhasan/android-ndk-r10d TARGET=android-17 ARCH=x86 clean, not just make clean, since the latter will probably miss removing the android specific object files.

another method is, to add explicit file removing command for "clean_Android", i.e., add "codec/common/src/cpu-features.o" in "clean_Android".
@mstorsjo is it OK, as we have already defined "clean_Android" in Makefile?

I got the following error. Any suggestion? Thanks.
nasm -DX86_32 -f elf -I./codec/common/x86/   -o codec/common/x86/cpuid.o codec/common/x86/cpuid.asm
codec/common/x86/cpuid.asm:196: error: symbol `XGETBV' redefined
make: *** [codec/common/x86/cpuid.o] Error 1

@jpxiong Don't hijack others' issue reports just to get attention to your own.

@huili2 That doesn't really help, since clean_Android is only called if you do "make OS=android clean". If you just do "make clean", it won't do clean_Android.

thanks all i solved it using @mstorsjo  solutions.

@mstorsjo 's solution is work for me, thanks!

i have add "clean after "OS=android" and it worked!

authors: etworker huili2 jpxiong mcjambi mstorsjo riazhasan93 sijchen


text:
access to tainted state on server-side

I have a Boolean form field (e.g., shared).
On server-side, I need to do some custom business logic if its value is changing from false to true.
I have to add an extra form field (e.g., originalShared) to tract if its value is change from  false=> true
Is there a better option to know precious value of a form field on server-side?

That kind of state management is outside the scope of Superforms, I'm afraid. Perhaps you can serialize the $tainted store in onSubmit and send it to the server.

authors: ciscoheat xmlking

repo: ciscoheat/sveltekit-superforms


text:
Refactor multi-arch build options

Instead of specifying the build platform directly, use the special value local to specify the local environment rather than hard-coding amd64.
This will possibly help with https://citizensadvice.atlassian.net/browse/CP-249
I will test this once merged before updating the tagged version.

This does not seem to help with CP-249 but it does work


text:
TypeError: cannot unpack non-iterable Phase object

hi bro.i meet another problem when i transfer the sumo map .xml to the cityflow map .json.it says TypeError: cannot unpack non-iterable Phase object  when the convert.py process the function named "node_to_intersection".the same problem with the examples file atlanta_sumo.net.xml. i dont know if i get something wrong?

Please check the naming of your intersection 'edges' or roads in sumo,
if the name of an edge is with an underscore eg edge_1 , the issue appears.

@wnzhang @soodoshll @zyr17 @shuan19920309 more documentation is required!

Hi,i checked my sumo, and theres no edge named  with an underscore. And i try the provided
 file "atlanta_sumo.net.xml" .the issue also appears. That wonders me. Could you please give me more guidance? thanks a lot~
------------------ 原始邮件 ------------------
发件人:                                                                                "cityflow-project/CityFlow"                                                                                @.>;
发送时间: 2021年4月3日(星期六) 晚上6:38
@.>;
@.@.>;
主题: Re: [cityflow-project/CityFlow] TypeError: cannot unpack non-iterable Phase object  (#122)
Please check the naming of your intersection 'edges' or roads in sumo,
if the name of an edge is with an underscore eg edge_1 , the issue appears.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

The edges naming in that file include underscore;
'''

''''
if you replace the underscore by another character or remove it, it will work.

Hi bro. thanks a lot for your guidance. and i try but i still failed by replacing the underscore in name of edges.
finally i try to replace these code in converter.py
for phase,duration in tls_dict[nodeid]._programs['0']._phases:
lane_list = []

for i,alpha in enumerate(phase):

if (alpha == 'G' or alpha == 'g') and i in G_to_lane_dict.keys():

by
for phase in tls_dict[nodeid]._programs['0']._phases:
lane_list = []
duration=phase.duration
for alpha in enumerate(phase.state):
if (alpha == 'G' or alpha == 'g') and i in G_to_lane_dict.keys():
and it works.
i dont know if this problem is related to the version of python.because i use python3. hope it will be useful to you.
------------------ 原始邮件 ------------------
发件人:                                                                                "cityflow-project/CityFlow"                                                                                @.>;
发送时间: 2021年4月8日(星期四) 下午4:08
@.>;
@.@.>;
主题: Re: [cityflow-project/CityFlow] TypeError: cannot unpack non-iterable Phase object  (#122)
The edges naming in that file include underscore;
'''
''''
if you replace the underscore by another character or remove it, it will work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks!
Your solution helps a lot!

Welcome

repo: cityflow-project/CityFlow


text:
🛑 AppCheck is down

In 2d14e78, AppCheck (https://www09.8f7.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AppCheck is back up in a1eb7e5 after 34 minutes.

repo: civcicd/uptime-monitor-commercial


text:
GDPR - Politica de Confidentialitate

hei, cred ca ar trebui sa adaugam si in VoluntApp un link catre Politica de Confidentialitate
Ca sugestie unde sa punem link-ul: Footer sau direct in Meniu / Documente
(https://civictech.ro/administrativ/politica-de-confidentialitate )

Absolutely I agree.

Absolutely I agree.

can you make a PR?

Absolutely I agree.

can you make a PR?

I'm only interested in security research (:

authors: LigiaAdam cezarneaga ismailtasdelen

repo: civictechro/volunt-app


text:
Translation explaining that the page isn't fully translated is incorrect

Describe the bug
If you switch languages while filling out an application and we're missing translations for the new language, we display a toast that's supposed to say that the page isn't fully translated into the new language. However, this translation is incorrect for Spanish and instead says that the page isn't fully translated into English:

I checked the messages file and the translation is incorrect there. We should check the other languages to see if the translation is incorrect for those as well.
To Reproduce
Steps to reproduce the behavior:

Log in as guest
Set language to English
Click Apply on a program
Change language in dropdown to Spanish
See the toast and observe that it says "al inglés" (to English)

Expected behavior
Should say "al español"

Based on Google Translate, the following seem to be incorrect:

Spanish
Korean
Amharic

And the following are fine:

Somali
Filipino
Vietnamese
Chinese

The English version is "We're sorry, this program is not fully translated to your preferred language."

I added this to the translations spreadsheet to get re-translated.

repo: civiform/civiform


text:
Cleanup - delete references to vars in cloud-deploy-infra that are now being autogenerated

Once server var auto-generation is complete and variable names match (issue #5245), delete extra terraform code that was used to set vars previously

re-opening while I figure out what went wrong with the staging values


text:
Fix login in tests on AWS staging

Auth0 added a hidden Continue button in addition to the actual, visible Continue button for some reason. This changes the selector to only click the visible button.


text:
add local blink camera temperature support

add ability to connect to blink camera on local net for camera temperature reading.

added 3 new env secrets to Azure DevOps secrets

repo: cjkrolak/ThermostatSupervisor


text:
Refactor code into modular files

Currently, all the code related to the modals and feedback functionality exists in a single file, exercise_functions.html. This approach can make the codebase harder to maintain and update in the future. It would be beneficial to refactor the code into seperate files, following a more modular approach.
Proposed solution

Create seperate HTML and Javascript files for each modal and functionality.
Abstract out common code, such as modal open/close functions, into a shared utility file.
Place these files in the relevant directories.

Related files
exercise_functions.html
Note:
Consider backward compatibtility and ensure any neccessary changes to existing code references are addressed during the refactoring process.
Include placeholder data types for the dummy variables, since these will eventually be connected to the backend

have decided to leave this until later on, can make our code modular after we have all of the functionality (e.g. API calls, handlers) implemented


text:
fix: correct alias target for firing events

just a small documentation fix on README

Thanks!

authors: cklmercer emrox

repo: cklmercer/vue-events


text:
fix typos causing type mismatch in examples

This resolves a minor compiler warning because the accidental use of %u means that an unsigned  long is being passed when an unsigned int is expected.
(I felt that fixing this directly in a PR would be more efficient than opening an issue about it. I hope that it is alright.)

This change is

Thank you; this is merged manually in the develop branch, please issue future PR against develop branch of clFFT

authors: JCount bragadeesh

repo: clMathLibraries/clFFT


text:
GotoReferences in label: and highlight not accessed variable

Press GotoDefinition in label, I can jump to label: XXX.
But press GotoReferences in label:, I cannot jump to goto label.
It is a missing feautre?
And if a label is not used in any goto or switch, Can clangd highlight as a not accessed variable?

But press GotoReferences in label:, I cannot jump to goto label.
It is a missing feautre?

This was actually implemented recently in https://reviews.llvm.org/D150124. It will be in clangd 18.

And if a label is not used in any goto or switch, Can clangd highlight as a not accessed variable?

Try adding -Wunused-label to your compile flags.

It will be in clangd 18.

Thanks, I wait new version of clangd :smile:

repo: clangd/clangd


text:
refactorin wit coc-rename don't work across project

refactorin wit coc-rename don't work across project (symbol is used outside main file).

Please provide clangd logs, preferably by passing -log=verbose to clangd. See http://clangd.llvm.org/troubleshooting.html#gathering-logs for details.

i have set :   "clangd.arguments": ["-log=verbose"], il my coc config but i don't know where is the log file

cross-file rename is enabled by default in clangd 11. From the error message (symbol is used outside main file), I believe you are using  clangd10 (you try it with command-line flag cross-file-rename=true, you may hit bugs as this feature is experimental in clangd10).

thank you. that s work.
But  command  clangd.install don't work behind proxy with   "http.proxy" correctly configured in coc-setting.json (test with coc-marketplace).

authors: grimgort hokein kadircet

repo: clangd/coc-clangd


text:
Using the new MSG_SET_SETTINGS_INFO crashes Clarius app

Hi, I am facing the following issue and it seems the issue is with the Clarius app itself.
Mobile API version: 9.0.0
Installed Clarius App: 9.1.0-287+372b0f17e0
Issue
When sending the new MSG_SET_SETTINGS_INFO with an argument, bundle of me.clarius.mobileapi.SettingsInfo(), the Clarius app crashes.
Here's my code:
   val defaultSettings = me.clarius.mobileapi.SettingsInfo()
            defaultSettings.autoConnect = true
            defaultSettings.autoScan = true
            defaultSettings.autoFreeze = DEFAULT_AUTO_FREEZE
            defaultSettings.keepAwake = DEFAULT_KEEP_AWAKE

            defaultSettings.buttonUp = SettingsInfo.BUTTON_USER
            defaultSettings.buttonDown = SettingsInfo.BUTTON_USER

            sendMessage(
                MobileApi.MSG_SET_SETTINGS_INFO,
                bundleOf(
                    MobileApi.KEY_SETTINGS_INFO to defaultSettings,
                )
            )

Here's the crash in the Logcat:
2022-03-29 11:57:10.706 E: Class not found when unmarshalling: me.clarius.mobileapi.SettingsInfo
    java.lang.ClassNotFoundException: me.clarius.mobileapi.SettingsInfo
        at java.lang.Class.classForName(Native Method)
        at java.lang.Class.forName(Class.java:454)
        at android.os.Parcel.readParcelableCreator(Parcel.java:3402)
        at android.os.Parcel.readParcelable(Parcel.java:3336)
        at android.os.Parcel.readValue(Parcel.java:3238)
        at android.os.Parcel.readArrayMapInternal(Parcel.java:3635)
        at android.os.BaseBundle.initializeFromParcelLocked(BaseBundle.java:292)
        at android.os.BaseBundle.unparcel(BaseBundle.java:236)
        at android.os.Bundle.getParcelable(Bundle.java:1002)
        at me.clarius.mobileapi.MobileApiService$IncomingHandler.handleMessage(MobileApiService.java:303)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at android.app.ActivityThread.main(ActivityThread.java:8633)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1133)
...

please see the latest app pilot with latest code here to get fix for reported issue

This was fixed in version 9.3.0, thanks again for reporting.

authors: clariusk julien-l nnaskov

repo: clariusdev/mobileapi


text:
🛑 Main is down

In cb9e96e, Main (https://www.nsercresnet.ca) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Main is back up in 2906e7c after 6 minutes.

repo: clarkwrks/resnet-status


text:
nginx relative root problem

I'm using NGINX with jingo. First I defined a server block:
server {
    listen 8080;
    server_name wiki;
    location / {
        proxy_pass http://127.0.0.1:6067/;
    }
}

Now if I browse to http://<server domain>:8080 everything works fine. I'd like to move this to http://<server domain>/wiki, however. But when I do this:
server {
    listen 80;
    server_name <server name>
    ...
    location /wiki {
        proxy_pass http://localhost:6067/;
    }
}

All of the urls in the jingo page are relative to the server root, and so no css/js files are loaded. Additionally it defaults to http://<server domain>/wiki/Home instead of http://<server domain>/wiki/wiki/Home.
Is there a way around this?
Thanks

I suppose we can safely assume serving Jingo from non-root URL fragment is just not supported. One way for Jingo to be aware of such setups and be able to render different URLS could be an environment variable. This would be in accordance with http://12factor.net.
Also I remember fiddling around with some baseUrl variable once, too.
On the other side, seperating different applications by subdomains is not only helpful regarding CSRF or XSS attacks. I propose not to support this scenario.

It'd probably enough to make Jingo aware of being served ("mounted") in a subdirectory, the way WordPress does with WP_SITEURL configuration variable. As @almereyda mentioned, I am not really sure about all the consequences (WP introduced that option only from version 2.2), so I am not thinking to implement it right now. It should be easy to hack something in your local setup though.

I propose to close this issue. nginx supports rewrite rules for proxy_pass. See https://raymii.org/s/tutorials/NGINX_proxy_folder_to_different_root.html for details.

I re-tried using rewrite rules:
location /wiki/ {
    rewrite ^/wiki(/.*)$ $1 break;
    proxy_pass http://127.0.0.1:6067/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_redirect off;
}

The wiki pages are served correctly as far as I can tell, but the resources still fail to load (*.css, *.js, etc.). I guess this makes sense... I don't think there's a way to do this from NGINX.
I have another idea: could you add a config variable to specify the location of static files? A lot of other frameworks do this (e.g. Django).

Closed in favor of #124

authors: almereyda claudioc creynold

repo: claudioc/jingo


text:
🛑 livevault is down

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

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 31b5333.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

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

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 245bebf.


text:
🛑 www.offsitedatasync.com is down

In 2b3381b, www.offsitedatasync.com (https://www.offsitedatasync.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.offsitedatasync.com is back up in f25f5da after 13 minutes.


text:
🛑 livevault is down

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

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in eace95a.


text:
(Seems to be a) @keyframes name parsing issue

Environment

clean-css version: 5.3.0
node.js version: 16.10.0
operating system: Windows 10

Configuration options
The ones clean-css-cli uses when run with no arguments.
Input CSS
@keyframes Toast--spinner {
  from { transform: rotate(0deg); }
  to { transform: rotate(360deg); }
}
/*!
 * Released under MIT license.
 */
.h0 {
  font-family: -apple-system;
}

Actual output CSS
It prints the following warning:
WARNING: Invalid selector '/*!
 * Released under MIT license.
 */
.h0' at x.css:7:0. Ignoring.

And then the CSS is as follows:
@keyframes Toast--spinner{from{transform:rotate(0)}to{transform:rotate(360deg)}}

Expected output CSS
@keyframes Toast--spinner{from{transform:rotate(0)}to{transform:rotate(360deg)}}/*!
 * Released under MIT license.
 */.h0{font-family:-apple-system}

What seems to be the issue
I noticed that when I rename Toast--spinner to say Toast-spinner (one hyphen), the bug doesn't reproduce.
At first I though that I've hit a CSS spec edge case, but it doesn't seem to be the case:
@keyframes <keyframes-name> {
  <keyframe-block-list>
}
<keyframes-name> = <custom-ident> | <string>

And the custom-ident cannot start with double hyphen, but can seemingly include double hyphens (or at least I couldn't find what forbids it).
Also, making it a string @keyframes "Toast--spinner" doesn't help either.
(The CSS in question is GitHub's own Primer.css)

Found it! This happens because the isVariable flag is set when encountering -- and never reset, which affect comment parsing.
I've got a simple workaround, will make a PR soon.

repo: clean-css/clean-css


text:
削除したカスタムフィールドの単語を検索時、エラー

1.カスタムフィールド（リスト形式）を登録し、チケットにて値を選択。
2.カスタムフィールドごと削除した際
3.値にしていた単語を検索→下記エラーとなります。
Page not found
The page you were trying to access doesn't exist or has been removed.
production.logよりエラー内容。
ActiveRecord::RecordNotFound (Couldn't find CustomValue with 'id'=1476):
custom_valueにて記載IDが削除されていることを確認。
カスタムフィールド削除時、設定されていた値の検索でエラーとならないよう、
ご対応いただくことは可能でしょうか。
（カスタムフィールドを削除する際に気を付けていればよかったのですが。。。）
プラグインのバージョン：1.0.4

手元で問題を再現させたいので、下記の情報をいただけますか？

Redmineのバージョン
Rubyのバージョン
Ruby on Railsのバージョン
MySQL(MariaDB) or PostgreSQL のバージョン
Mroonga or PGroonga のバージョン

手元でも再現することが確認できました。
一旦再現環境の情報を頂かなくても大丈夫そうです！

ありがとうございます。
念のため、当環境をお伝えしておきます。
よろしくお願いいたします。
・Redmine：4.2.2
・Ruby：2.6.8
・Ruby on Rails：5.2.6
・MariaDB：10.2
・Mroonga：11.0.6

対応しました。
ゴミレコードはRAILS_ENV=production bin/rails full_text_search:synchronizeで消えるのでそれを実行すれば検索時のエラーもなくなるはずです。

検索時にエラー発生しないことが確認できました。
対応ありがとうございます。


text:
SKIPME: Apply different memory fraction configuration on driver and executor

This is an attempt to apply different memory fraction configuration on driver and executor. This approach passes in a flag to indicate whether the configuration is for driver, if it is for driver, it will look for a configuration from spark conf, otherwise, it will use the spark.memory.fraction setting.
I have tested this out on a single node cluster. I will also look for junit tests to add if this approach sounds reasonable.

jmwg

authors: davidnavas yeweizhang

repo: clearstorydata/spark


text:
refactor(elements): Fix loading oddities

Description
Sign In

Rename route: to step: for consistency.
Clean up loading logic thus negating the need for context

Fast-Follow: Apply similar changes/logic to sign-up.

Fixes SDK-1863
Checklist

[x] npm test runs as expected.
[x] 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

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

!snapshot

Hey @tmilewski - the snapshot version command generated the following package versions:

Package
Version

@clerk/elements
0.10.0-snapshot.vd1e7a32

gatsby-plugin-clerk
5.0.0-beta.45

@clerk/remix
4.2.0-snapshot.vd1e7a32

@clerk/ui
0.1.6-snapshot.vd1e7a32

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/elements
npm i @clerk/elements@0.10.0-snapshot.vd1e7a32 --save-exact

gatsby-plugin-clerk
npm i gatsby-plugin-clerk@5.0.0-beta.45 --save-exact

@clerk/remix
npm i @clerk/remix@4.2.0-snapshot.vd1e7a32 --save-exact

@clerk/ui
npm i @clerk/ui@0.1.6-snapshot.vd1e7a32 --save-exact

authors: clerk-cookie tmilewski

repo: clerk/javascript


text:
stuck at cline wants to use the browser:

Which API Provider are you using?
OpenRouter
Which Model are you using?
sonnet-3.5
What happened?
can't use the browser action
Steps to reproduce
1.Trying out cline for the first time.
2.Added my openrouter key

Asked for the weather in seattle
3: when asked to approve i clicked approve
Just spins

Relevant API REQUEST output
No response
Additional context
Ubuntu OS

I'm having the exact same issue, but running on windows 11 and using the anthropic as provider.

+1 on osx with anthropic. It eventually timed out.
The tool execution failed with the following error:
<error>
Error executing browser action: {"name":"Yle","message":"Page.captureScreenshot timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.","stack":"Yle: Page.captureScreenshot timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.\n    at zAe.<instance_members_initializer> (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:91505)\n    at new zAe (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:91569)\n    at vUe.create (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:90716)\n    at wUe._rawSend (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:95662)\n    at yUe.send (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:92630)\n    at t._screenshot (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:591:71630)\n    at t.screenshot (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:75265)\n    at t.<anonymous> (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:579:10905)\n    at Y1e.doAction (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:1541:13319)\n    at nK.presentAssistantMessage (/Users/mjd/.vscode/extensions/saoudrizwan.claude-dev-2.1.6/dist/extension.js:1594:4632)"}
</error>

+1 on this; can repro on macOS

There was a few days where the nightly build of chromium it downloads automatically was broken. Then it gets cached and Cline will never try to download an open one on its own. I'm on mobile so I can't find the exact path right now it's somewhere under Library Support on Mac where all VSCode extensions get to store stuff. Delete it and restart to get a fresh chromium build

authors: MatthewDailey andrewkmin byjlw steiner385 themightychris

repo: cline/cline


text:
StopIteration & RuntimeError fix for Python >= 3.7

Since Python 3.7, all StopIteration exceptions raised inside a generator are transformed into RuntimeError (see PEP-0479 and this answer from StackOverflow). This new behavior made pattern unusable for all Python3.7+ users and all packages depending on it (gensim for instance: https://github.com/RaRe-Technologies/gensim/issues/2438).
This PR fixes the _read generator by removing the StopIteration exception raised in it. It solves the following issues :

https://github.com/clips/pattern/issues/243
https://github.com/clips/pattern/issues/282
https://github.com/clips/pattern/issues/283
https://github.com/clips/pattern/issues/288
https://github.com/RaRe-Technologies/gensim/issues/2438

Coverage decreased (-0.3%) to 68.022% when pulling 66ab34453a3443c06a4ebda092c8d1947c83b17a on NicolasBizzozzero:master into 5b85d998c30ddc6772b56310713530224466083a on clips:master.

Thank you for all the work @NicolasBizzozzero !
Seems like the CI build is based on python=3.6 and causing the check failures? Who can help to fix this issue as it seems stupid to not able to fix this for quite a while...

Meanwhile you can monkey patch around this issue by calling this method in your module:
def patch_pattern():
    from pattern import text

    original_read = text._read

    @functools.wraps(original_read)
    def patched_read(*args, **kwargs):
        try:
            for r in original_read(*args, **kwargs):
                yield r
        except RuntimeError:
            pass

    text._read = patched_read

authors: NicolasBizzozzero coveralls jonathanc42 tuky

repo: clips/pattern


text:
Required Link headers missing on content distribution requests

Hi there - thanks for https://websubhub.com/
One thing I noticed is that your content distribution requests are missing the required Link http headers.
You can either add two Link headers:
e.g.
Link: <http://topic/url>; rel=self
Link: <https://websubhub.com/hub>; rel=hub

Or a single one with multiple values (like google's hub does, and is the preferred way according to the spec)
e.g.
Link: <http://topic/url>; rel=self, <https://websubhub.com/hub>; rel=hub

From the spec: https://www.w3.org/TR/websub/#x7-content-distribution

The request MUST include at least one Link Header [RFC5988] with rel=hub pointing to a Hub associated with the topic being updated. It MUST also include one Link Header [RFC5988] with rel=self set to the canonical URL of the topic being updated. The Hub SHOULD combine these headers into a single Link Header [RFC5988]. All these URLs are those resulting from the discovery process (Section 3). The subscriber MUST NOT use these Link headers to identify the subscription corresponding to the content distribution request, because the Link headers are metadata associated with the topic content, not with any particular subscription. For example, the topic URL in the content distribution request may be different from the topic URL that was originally subscribed to.

Hey there! Thanks for letting me know, I can probably get this in sometime this week. Will keep you updated!


text:
AWS Velociraptor Enrollment is Broken

Operating System Version: NA
Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): AWS
Vagrant Version (if applicable):  NA

Please verify that you are building from an updated Master branch before filing an issue.
aws_instance.dc (remote-exec): Copy-Item : Cannot find path 'C:\vagrant\resources\velociraptor\Velociraptor.config.yaml' because it does not exist.
aws_instance.dc (remote-exec): At C:\Users\vagrant\AppData\Local\Temp\install-velociraptor.ps1:32 char:3
aws_instance.dc (remote-exec): +   Copy-Item "c:\vagrant\resources\velociraptor\Velociraptor.config.ya ...
aws_instance.dc (remote-exec): +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
aws_instance.dc (remote-exec):     + CategoryInfo          : ObjectNotFound: (C:\vagrant\reso...tor.config.yaml:String) [Copy-Item], ItemNotFoundExce
aws_instance.dc (remote-exec):    ption
aws_instance.dc (remote-exec):     + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

Fixed in https://github.com/clong/DetectionLab/commit/93572348c231042e82b0aae7cc84df6dae934433

repo: clong/DetectionLab


text:
Run CCF using Serverless Lambas Rather than EC2 Instance

Feature Suggestion
Run ccf app as serverless lambda(s) instead of requiring an ec2 instance.
Describe the solution you'd like
Not pay for an ec2 instance to run ccf app.
Describe alternatives you've considered
Integrate this algorithm directly with our serverless project rather than using the ccf directly.
https://github.com/rollthecloudinc/verti-go
Additional context
Example of project that uses lambdas instead of ec2.
https://github.com/TimothyJones/github-cognito-openid-wrapper
Possible Implementation
I will have to become more familiar with the algorithm to provide any direction.

I've been reviewing the code.
So you use this.
https://docs.aws.amazon.com/cur/latest/userguide/cur-s3.html
To write cost and usage reports.
Then have a node api around it to run the Athena queries.
Have you considered using KeySpaces for data storage instead to reduce the cost of querying that data?
There could be a lambda set-up that triggers when a usage report is written to s3. The lambda could write it to Key Spaces table instead of perhaps even aws open search. AWS Open search adds some really powerful capabilities like advanced search,  anaomly detection, etc. which these kind of KPIs could benefit.

Hi @ng-druid, sorry for the delayed response! We will triage the original feature suggestion, the additional suggestion on keyspaces may be a bit outside our roadmap for now, but we would welcome a PR if you would like to contribute this!

authors: ccasher ng-druid


text:
Create Staging environment for testing container hardening

As an assurance engineer I need an environment to test out any hardening changes made to the current container scanning pipeline. This is a predecessor to Demonstrate gating an image on late CVE#2540
Acceptance Criteria

[ ] When the container scanning pipeline is run, a staging environment is created with two staging tasks, one for concourse and another for s3 hardening.

Security considerations
This will aid in improving security as it is a predecessor to a ticket that will add gating
Implementation sketch

[x] Update terraform in ecr.tf to add the new tasks
[x] Update pipeline to utilize the new tasks

Closing this in favor of scanning containers in pipeline before they are pushed. Will make another ticket to update ADR.

authors: jameshochadel rcgottlieb

repo: cloud-gov/product


text:
66% Annual Assessment Provide Artifacts to 3PAO

In order to meet the March 17, 2024, Annual Assessment delivery for cloud.gov to the Joint Authorization Board (JAB) and maintain our Provisional Authority to Operate (P-ATO), we must provide artifacts to the third-party assessment organization (3PAO) SecureIT to validate our cloud.gov controls settings.
Security considerations
None

This is overcome by events (OBE) we will not be starting annual assessment until April.


text:
Snake case fields are converted to camel case

I'm not sure if this is expected behaviour but:
Given this proto file
message Document {
  required string mime_type = 1;
}

and this object:
{ mime_type: "text/html" }
The field is ignored. However if I use this object it works, even if the proto file is unchanged
{ mimeType: "text/html" }
It seems like the library is converting snake case fields to camel case?
I'm using snake case for field names as this is recommended in the style guide

Sorry, wrong project!


text:
Cloudant query sample code not correct

The Cloundant query sample snippet code below is not correct:
List movies = db.findByIndex("{
"Movie_year": {"$gt": 1960}, "Person_name": "Alec Guinness"
}",
Movie.class,
new FindByIndexOptions()
.sort(new IndexField("Movie_year", SortOrder.desc))
.fields("Movie_name").fields("Movie_year"));
I tried something similar:
String Selector="{"Place_id": {"$gt": 100}}";
List p1 = db_use.findByIndex(Selector,places.class);
and got a JSON exception:
org.lightcouch.CouchDbException: Bad Request{"error":"bad_request","reason":"invalid UTF-8 JSON"}
After adding "selector" to the query it then worked:
String Selector=""selector": {"Place_id": {"$gt": 100}}";

Thanks for spotting this, where is the incorrect snippet located in the docs?

It is here https://github.com/cloudant/java-cloudant#cloudant-query
Just scroll down a bit and you will see the code about List movies.

I corrected the doc, thanks for the report!
https://github.com/cloudant/java-cloudant#cloudant-query

authors: adasilva70 mikerhodes rhyshort

repo: cloudant/java-cloudant


text:
🛑 rad.net.id is down

In c698016, rad.net.id (http://rad.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: rad.net.id is back up in 5ffe722.

repo: cloudbip/upptime


text:
🛑 my.domainesia.com is down

In 436a13c, my.domainesia.com (https://my.domainesia.com) was down:

HTTP code: 403
Response time: 38 ms

Resolved: my.domainesia.com is back up in 0ff4b44 after 9 minutes.


text:
🛑 niagahoster.co.id is down

In c058a42, niagahoster.co.id (https://niagahoster.co.id) was down:

HTTP code: 403
Response time: 82 ms

Resolved: niagahoster.co.id is back up in 9ac0467.


text:
🛑 hostingan.id is down

In 75f8e68, hostingan.id (https://hostingan.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hostingan.id is back up in 6bd50f4.


text:
🛑 cbn.id is down

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

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 4f05e64.


text:
🛑 cbn.id is down

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

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in e92ae68.


text:
Rewrite and restructure developer eaas documentation #2

anvil app tests, migration guide, new and better images, webapp ui guidelines, etc.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Stan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant munashige

repo: cloudblue/connect-eaas-core


text:
Add User limit objects to the queue in the config

cleanup and doc of config
extend validator to check user limit object on partition and queue
extend config tests to include user limits

Major update based on the discussions we have had earlier:

rebase on top of the current head
move to a generic limit object
use same yaml structure as for filters

Documentation update is pending and should be added before commit

Hi @wilfred-s
The changes in this PR looks good to me, as long as it declares general user/group limits, I am fine to merge it. But the only thing I think we add to our document, that is to say, we are not recognizing users/groups in the scheduler yet, that is something in our roadmap. I don't want to give users the impression they can actually use these now, this feature can be complete only when we build the shim to send correct user/group info.

Added comment to the documentation to state that shim work is outstanding for functionality to work correctly.

authors: wilfred-s yangwwei

repo: cloudera/yunikorn-core


text:
chore: fix axios dependency

Somehow axios had been completely removed from the dependencies in package.json. I guess our tests still worked because @types/axios must have a dependency on axios, and by the transitive power of npm dependencies it was there. But we actually have axios in the package itself. So, users who want to use the axios emitter that we ship will have to know to also install axios without this change.
Signed-off-by: Lance Ball lball@redhat.com

I didn't realize we still had an axios emitter.  I thought we were trying to move away from including any specific protocol libraries.

I didn't realize we still had an axios emitter.

https://github.com/cloudevents/sdk-javascript/blob/cc43f3bd10caffbc47b9ce42df71782177176001/src/transport/http/index.ts#L1-L17

I thought we were trying to move away from including any specific protocol libraries.

Yes we are. But we forgot to actually remove it for 4.0.

The BEFORE functionality still exists until the release of 4.x at which time it will be removed.

https://github.com/cloudevents/sdk-javascript/pull/342
I mean, I guess we could leave it as-is and consider it "removed" - though it is still accessible, and could work fine as long as the user declares the axios dependency themselves.

Closing this for now. We can revisit later if we need to.

authors: lance lholmquist

repo: cloudevents/sdk-javascript


text:
[Speed] Deprecation notices

PCX-10713

Please do not merge until PMs review in the PCX!

repo: cloudflare/cloudflare-docs


text:
[Docs Site] Fix footnotes with multiple references

Summary
Fix footnotes with multiple references

Got an example of where this is used?

Got an example of where this is used?

https://developers.cloudflare.com/durable-objects/platform/limits/ vs. https://kian-pcx-14165.cloudflare-docs-7ou.pages.dev/durable-objects/platform/limits/

authors: GregBrimble KianNH


text:
DS-10200 Add new logstream-only fields to Logs docs Log fields

This adds new logstream-only fields to Logs docs Log fields, synced from internal repo.

Sorry I've been backlogged. I would like to review this and suggest a few changes. Will try to review tomorrow!

@crwaters16 Let's update the templates in the internal logshare-api repo.
This PR is merely just syncing from there, and I can refresh after all updates are done there.

Regenerated from internal logshare-api repo.
This is ready to merge.

authors: soheiokamoto tlozoot


text:
[Pages] limit update

https://github.com/cloudflare/cloudflare-docs/pull/3333

Thanks for taking care of this Kate!


text:
Update worker-variables.md fix broken function example

The email variable is passed to the digestMessage() function. The  text variable would be undefined.
As requested here: https://discord.com/channels/595317990191398933/917505178016579605/1093902711231086632

Confirming this fix is correct!

authors: bjesus mountainash


text:
Added CustomID to UploadImageParams

Description
I added support for CustomID when we upload images to Cloudflare images which I hope is supported by CF API: https://developers.cloudflare.com/images/upload-images/upload-custom-path/
Please correct me if I'm wrong but Custom ID means that we can select which ID to have for the image right?
Has your change been tested?
Yes. I tested this in my own app and seems to be working
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented in cloudflare/api-schemas
and relies on stable APIs.

The reason for the failed CI is
go: downloading golang.org/x/exp/typeparams v0.0.0-20221212164502-fae10dda9338
go: golang.org/x/tools/cmd/goimports@latest (in golang.org/x/tools@v0.25.0): go.mod:3: invalid go version '1.22.0': must match format 1.23
internal/tools/tools.go:22: running "go": exit status 1

Do you want me to fix this?

unfortunately, this isn't documented in the API schemas so it is not yet something we can add support here for - https://developers.cloudflare.com/api-next/resources/images/subresources/v1/methods/create/

unfortunately, this isn't documented in the API schemas so it is not yet something we can add support here for - https://developers.cloudflare.com/api-next/resources/images/subresources/v1/methods/create/

Got ya, Do you might know when this will be added to the docs?

i do not. that is a question for the service team or CSUP.

i do not. that is a question for the service team or CSUP.

Got ya!
Should I close this PR so we can open this if this becomes something you want in the future?

Thank you for answering btw! :D

up to you but this will go stale within 2 weeks and be closed automatically.
now that we're codegen'ing the libraries, this will automatically be picked up when it does land.

Okay, Then I close this issue. Thank you for the answers

authors: emilpriver jacobbednarz

repo: cloudflare/cloudflare-go


text:
Feature request: Connection migration

According to #698, connection migration isn't supported.
I think supporting connection migration would need an API change, as quiche would need to be made aware of IP addresses, in order to do address validation etc.
Would PRs going in such a direction be accepted? I guess a design decision would be warranted first.

Connection migration is a nice feature of QUIC and it would be great for quiche to support it but for now it is still a TBD. Adding it requires some upfront design to make sure the feature aligns with the API paradigms, and really needs some upfront thinking about how to test and validate it. If you have ideas or PoC then we could consider them but you given the potential complexity I can't so how hard or easy that is.

Fixed by #1223.

authors: LPardue tbu-

repo: cloudflare/quiche


text:
error creating cloudflare pages project, could not read response body: %!w()

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 v1.3.8
on windows_amd64

provider registry.terraform.io/cloudflare/cloudflare v4.0.0-rc2

Affected resource(s)
cloudflare_pages_project
Terraform configuration files
resource "cloudflare_pages_project" "hugo_deploy" {
  account_id        = var.cloudflare_account_id
  name              = "hugo-test-1"
  production_branch = "main"
  build_config {
    build_command   = "hugo"
    destination_dir = "public"
    root_dir        = "/"
  }
  source {
    type = "github"

    config {
      owner                         = "kdpuvvadi"
      repo_name                     = "hugo-test-cf"
      production_branch             = "main"
      deployments_enabled           = true
      production_deployment_enabled = true
      pr_comments_enabled           = false
      preview_branch_excludes       = ["main"]
    }
  }
  deployment_configs {
    production {
      environment_variables = {
        ENVIRONMENT  = "production"
        HUGO_VERSION = "v0.109.0"
      }
    }
    preview {
      environment_variables = {
        ENVIRONMENT  = "preview"
        HUGO_VERSION = "v0.110.0"
      }
    }
  }
}

Link to debug output
https://gist.github.com/kdpuvvadi/52a78ed5480e3d4e4f11c1df89eccdbf
Panic output
No response
Expected output
Deploy a page project
Actual output
Plan: 1 to add, 0 to change, 0 to destroy.
cloudflare_pages_project.hugo_deploy: Creating...
cloudflare_pages_project.hugo_deploy: Still creating... [10s elapsed]
cloudflare_pages_project.hugo_deploy: Still creating... [20s elapsed]
cloudflare_pages_project.hugo_deploy: Still creating... [30s elapsed]
╷
│ Error: error creating cloudflare pages project "hugo-test-1": could not read response body: %!w()
│
│   with cloudflare_pages_project.hugo_deploy,
│   on pages.tf line 1, in resource "cloudflare_pages_project" "hugo_deploy":
│    1: resource "cloudflare_pages_project" "hugo_deploy" {
│
╵
Steps to reproduce

terraform init
terraform plan
terraform apply

Additional factoids
Initial version: 3.33.1
failing on 4.0.0.rc2
And Also checked the API Token with env var  $ENV:TF_VAR_cloudflare_api_token and in var file.
References
No response

thanks for trying out the RC! we appreciate it.
this looks to be an internal server error on the service. can you try again in a little while and if the issue persists, post back here?

this looks to be an internal server error on the service. can you try again in a little while and if the issue persists, post back here?

getting same error from yesterday. After internal error, waited few hours. tried same error.

thanks for trying out the RC! we appreciate it.

Getting same error on stable version. I can switch and get back with debug log.

this isn't related to the Terraform Provider version; the service is returning a 5xx error either due to a configuration issue or an unhandled server side issue.
@WalshyDev do you mind having a poke around and letting me know if you need anything here?

I'm not seeing any errors for your account in our service, if this is persisting could you join the community Discord (https://discord.gg/cloudflaredev) and tag me over there (Walshy#9709)?
Thanks!

closing this off as there isn't anything for the provider to do here.

only facing this issue if we use cloudflare_pages_project. Other services are working fine.

getting this on cloudflare_notification_policy tried providers versions from 3.33 to 4.0.0-rc, anyone else ?

working fine from 4.5.0. Closing this.

authors: WalshyDev jacobbednarz kdpuvvadi tcrst


text:
🐛 Bug Report — Runtime APIs TextDecoder

TextDecoder does support new TextDecoder("utf-8") but does not support TextDecoder("UTF-8")

Thank you for reporting! You're right, based on the Spec upper-case labels are to be supported too.

Fix has been merged – unfortunately I'm not sure if this will make it to the next production environment release, so deployment might take a while.

Update: The fix has been deployed to the production environment since Tuesday 7/2. Thanks again for reporting this!

repo: cloudflare/workerd


text:
[CI] Fix miniflare build

The issue is a re-edition of #2168, no longer defining the version directly
should stop this from reappearing.

@petebacondarwin @penalosa Was about to ask for ideas on coupling CI better to avoid issues like this in the future, but looks like there's a simple solution 😌.


text:
🐛 BUG: Starting inspector on 0.0.0.0:9229 failed: address already in use

What version of Wrangler are you using?
2.0.26
What operating system are you using?
Pop!_OS 22.04 LTS
Describe the Bug
run pnpm wrangler pages dev -- next dev in next.js project folder.
trying to run with --inspector-port and different port, same result.
checked with netstat, port 9229 and any different ports that i tried not in use.
wrangler did working (serve proxy next dev and /functions).
other software version details:
node 16.17.0 with nvm 0.39.1
pnpm 7.9.3

Hey there! Thank you for submitting this bug report.
I can definitely reproduce this issue. I'm not sure why it's occurring yet though. @petebacondarwin Any ideas?

@threepointone I appreciate you!

FYI: The related bug for plain workers seems to be #1777 and was fixed in #1786.

I'm also seeing this error in the latest wrangler 2.1.8.

Same issue with wranger 2.0.27

2.1.9 issue still here
Doesn't work on Linux, WSL2, Docker (Alpine,Ubuntu)
Works only on Windows (

2.1.10 issue still here
Macos

still seeing with wrangler 2.1.11 on macOS 12.6

same bug on 2.1.13, Ubuntu, node v.19.0.0

i'm still seeing this on wrangler dev --local on 2.2.1. no matter the port supplied either via --inspector-port or the inspector_port value in the wrangler.toml, the address is always considered in use when there is nothing running on the provided port

I'm seeing this issue on 2.4.0. i made some comments in #1864 that I think might help in debugging this. I suspect it's simply that the inspectPort is passed to the miniflare cli command on top of the pages dev command so they both are unable to start.

Running --inspect-port 0 doesn't fix the issue. Just FYI this blocks development if using the cloudflare/pages template in remix-run.

I'm experiencing this issue (or similar?) on 2.4.2 when using --experimental-local. I don't have this issue with --local.
*** Fatal uncaught kj::Exception: kj/async-io-unix.c++:945: failed: ::bind(sockfd, &addr.generic, addrlen): Address already in use; toString() = 127.0.0.1:9229
stack: /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b55fca /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b55d6f /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b54105 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14f6295 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b1f0f6 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14f6570 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14c584d /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14c4e48 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14c4bec /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b8b298 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b8ae89 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b6f6a8 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2b88fc8 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14ba289 /usr/lib/libc.so.6@2328f /usr/lib/libc.so.6@23349 /home/redacted/node_modules/@cloudflare/workerd-linux-64/bin/workerd@14ba024
✘ [ERROR] local worker: MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

      at Miniflare.#waitForRuntime
  (/home/redacted/node_modules/@miniflare/tre/dist/src/index.js:6121:13)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async Miniflare.#init
  (/home/redacted/node_modules/@miniflare/tre/dist/src/index.js:6011:9)
      at async Mutex.runWith
  (/home/redacted/node_modules/@miniflare/tre/dist/src/index.js:2284:16)
      at async startLocalWorker
  (/home/redacted/node_modules/wrangler/wrangler-dist/cli.js:144106:11)
  {
    code: 'ERR_RUNTIME_FAILURE',
    cause: undefined
  }

The port wasn't already running, and changing the port number with the flag didn't change anything. Wrangler doesn't immediately terminate, and during that time, the port is in use until it exits. I'm not able to run the worker at all during this, unfortunately.
If easy to implement, could we possibly get a flag to disable the inspector entirely to avoid such issues? There's one to change the port, after all.

I've just re-run the command on 2.4.2 (no special flags or anything) and it is working without error.

I solved it with add  --ip '127.0.0.1'.
wrangler pages dev . --ip '127.0.0.1'

Seeing this issue with Wrangler 3 as well.  Exact same issue and message that @FunPineapple described.  Windows, WSL.
npx wrangler dev pages public results in:
*** Fatal uncaught kj::Exception: kj/async-io-unix.c++:945: failed: ::bind(sockfd, &addr.generic, addrlen): Address already in use; toString() = 127.0.0.1:87881502024

stack:
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2e82fda
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2e82d7f
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2e80fe5
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@154ba55
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@154c3d0
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@150cfdd
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1511d47
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1511ac4
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1511aac
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2eb9858
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2eb9449
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2eb7708
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@2eb74ca
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1502293
/lib/x86_64-linux-gnu/libc.so.6@29d8f /lib/x86_64-linux-gnu/libc.so.6@29e3f
/home/project/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1502024

I too am having the same issue when attempting to attach a debugger to the existing process.

hi folks, are y'all still experiencing this issue with latest wrangler version?

hi folks, are y'all still experiencing this issue with latest wrangler version?

yes

@gregory - thanks for responding. Can you provide some details of your setup so that we can debug?

What version of wrangler?
What version of node?
What is in your wrangler.toml and what command line args are you passing to wrangler dev?
Also do you have multiple instances of wrangler running at the same time?

I fixed it by manually fixing the inspector port through the wrangler option --inspector-port

We haven't heard from you in while so I'm going to close this issue for now. If you're still running into problems feel free to comment with more details and we can investigate further.

authors: CarmenPopoviciu DevinWinata FunPineapple Izdatyi antscript code-poel f5io gregory houmark ibrown-epic-games jaitaiwan jfsiii justinnoel orstavik penalosa petebacondarwin sidharthachatterjee superorange wedelgaard

repo: cloudflare/workers-sdk


text:
🐛 BUG: globalThis.MINIFLARE not set

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
9.5.1
What operating system are you using?
Mac
Describe the Bug
In my worker, the variable globalThis.MINIFLARE should return true when running npx wrangler dev index.js
But if index.js =
export default {
  fetch() {
    if (globalThis.MINIFLARE){
      return new Response("globalThis.MINIFLARE is TRUE");
    } else {
      return new Response("globalThis.MINIFLARE is FALSE");

    }
  },
};

launching via
npx wrangler dev index.js

returns page at http://127.0.0.1:8787 that says globalThis.MINIFLARE is FALSE

My misunderstanding. The command required to set this variable to true is:
npx wrangler dev index.js --local


text:
Document wasmpack/webpack configuration behaviour for building Rust

💡 Feature request
Overview and problem statement
#724 only documented custom webpack behaviour, in lieu of that also document how a rust wasm module is built and packaged for cloudflare workers.
This will allow people to combine custom webpack configuration with wasm builds.
Basic example
For example having both typescript and rust in the same worker.

Any progress on this? It would be great.
If I want to use webpack and rust in the same worker, am I best to use the webpack loader for wasm or do something else?

👋  - hi, we don't have plans on prioritizing documenting this functionality at the moment. that being said, I believe this npm module may help with what you're looking to do.

this tool also demonstrates how to create a hybrid project

@EverlastingBugstopper Yes using wasm-pack-plugin allows achieving the required functionality.
However setting type = "webpack" in wrangler.toml and a custom webpack with the above plugin does results in a wasm module being built but not being uploaded to cloudflare worker.
The wasm module gets uploaded only when type= rust or similar. This means we have to rely on hacks to make sure the final artifacts result in the correct directory and filename, etc that are prone to changes with newer wrangler version.
The only reasonable solution I see in the long term is allowing the use of webpack_config with type=rust as well.  (The user has to make sure to have the wasm pack plugin)

cc @xtuc

@shalzz what hacks are you using to get this to work?

Cancel that, I have it working. I don't know what hacks @shalzz was referring to, I've played around with this a lot and didn't find any hacks I had to implement to get workers to work with wasm-pack-plugin. The only negative change I saw was that I now get the warning
✨  Built successfully, built project size is 1 MiB. ⚠  Your built project has grown past the 1MiB size limit and may fail to deploy. ⚠

But the size hasn't actually changed - I assume the warning was just muted for type = "rust" projects as the size always exceeds 1MB?
It's working here in case it helps anyone.
This change also fixed this bug which I asked about on the community forum but never got any help with.

Hi, are there no plans to work on this?

hey @shalzz !
sorry for the dead air. if i understand correctly, the ask is for a more flexible approach which would support both a rust wasm module and typescript in the worker. I think that's a great goal; we don't have cycles in the near term for this, however I do want to keep it on the roadmap.

Wow! Thank you. I'm honored.

authors: EverlastingBugstopper ashleymichal samuelcolvin shalzz

repo: cloudflare/wrangler


text:
Use Built-In TestContainer Support from Spring Boot 3.1

Evaluate https://www.atomicjar.com/2023/05/spring-boot-3-1-0-testcontainers-for-testing-and-local-development/ and - if it works - replace https://github.com/cloudflightio/springboot-testresources

we need to wait for https://github.com/cloudflightio/cloudflight-platform-spring/issues/63 first


text:
getServices(spec) ?

getServices() returns all services.
Could it take an optional spec parameter with a regex?
Then if I bind against a bunch of MyService-abc, MyService-bcd, ... I can do getServices(/MyService-.*/) to use a user-provided service to set a list.

That seems like it makes sense; it would be extending the functionality of getServices(), and fills a niche of finding services that match some kind of spec.  Should it be the same kind of spec as getService()?

Yes, I'd think the same kind of spec.

I guess it would be useful for you to see if just filtering the result is easy enough.  See https://tonicdev.com/pmuellr/get-services-spec for an example of filtering the results with underscore.pick().
Here's the code from the tonic:
const us = require("underscore")

const services = {a:"1", b:"2", c:"3"}

console.log(us.pick(services, (val,key)=>key.match(/a|b/)))
console.log(us.pick(services, ["b", "c"]))

I don't really have the cycles for this.  If someone does want to add it, submit a PR:

code should be in existing style
update the doc
add test cases
squash PR to a single commit (be prepared to squash more if more changes are required)

@pmuellr looks easy enough wiht pick(), thanks.

repo: cloudfoundry-community/node-cfenv


text:
Migrating routeless apps to Diego doesn't disable health-check

As described in https://github.com/cloudfoundry/diego-design-notes/blob/master/migrating-to-diego.md#running-route-less-applications-such-as-workers-and-schedulers, a DEA --no-route is analogous to a Diego --no-route --set-health-check none
cf-migrate-apps diego should disable the health check on routeless DEA applications
Thanks,
-David

@socalnic @ematpl Wdyt? Kinda relates to the discussion we had a while back about whether cf push --no-route should imply health-check none.

/cc @SocalNick

If the plugin can properly determine whether or not to add --set-health-check none, would make it more useful.

My principal concern would be that there could be a stopped app that when started and routable should have a port-based health-check, but when migrated doesn't happen to have a route mapped to it right then (maybe it's the inactive half of a blue-green deploy pair, and the blue-green deploy technique is being parsimonious with route mappings). The health-check inference on cf push has a similar issue. An appropriate mitigation for that concern might be for the migration commands to report warnings about all apps with their health-checks set to none, so that the migrator can more easily discover the subset of apps for which to verify that this is the correct health-check type.
Also, can we use the clearer process instead of none for this?
Thanks,
Eric

Hi all, thanks for considering this.
I can offer that as a user, I wouldn't have had any problem with it dropping me into an interactive (yes/no/yes-to-all/no-to-all) mode to quickly set the appropriate health-checks per app/space. It's essentially what I had to end up doing.
Thanks,
-David

On Oct 7, 2016, at 20:37, Eric Malm notifications@github.com wrote:
My principal concern would be that there could be a stopped app that when started and routable should have a port-based health-check, but when migrated doesn't happen to have a route mapped to it right then (maybe it's the inactive half of a blue-green deploy pair, and the blue-green deploy technique is being parsimonious with route mappings). The health-check inference on cf push has a similar issue. An appropriate mitigation for that concern might be for the migration commands to report warnings about all apps with their health-checks set to none, so that the migrator can more easily discover the subset of apps for which to verify that this is the correct health-check type.
Also, can we use the clearer process instead of none for this?
Thanks,
Eric
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

We explored interactive prompts when previously enhancing this plugin, but gave up because of its technical complexity (the plugin itself runs in a separate process).  We'll need a lot more demand before we'd want to revisit that.
So it seems the safest solution would be to display a warning for each app being migrated to Diego that has no mapped routes that health-check-type is set to none.
(Will look at the stories to support process for the cf CLI and app manifest separately):
WARNING: Assuming process health check (type "none") for app with no mapped routes; use `cf set-health-check` to change this: App my-app to Diego/DEA in space myspace / org myorg as diesk

@dmarmugi We have released v1.2.3 of the plugin with the warning as described above.
Thanks for bringing it up!

authors: SocalNick dkoper dmarmugi ematpl

repo: cloudfoundry-incubator/Diego-Enabler


text:
Fix smoke with initial/empty DB

Signed-off-by: Stoyan Gradev stoyan.gradev@sap.com

Coverage remained the same at 90.871% when pulling 9cbda4f1cfe920e32fa797ed89fa44494196f3f9 on SAP:fix_initial_state_smoke_test into 0c2344a088d7c11481bd69b3d0e3b4050bebe04d on cloudfoundry-incubator:master.

Coverage remained the same at 90.871% when pulling 9cbda4f1cfe920e32fa797ed89fa44494196f3f9 on SAP:fix_initial_state_smoke_test into 0c2344a088d7c11481bd69b3d0e3b4050bebe04d on cloudfoundry-incubator:master.

Coverage remained the same at 90.871% when pulling 9cbda4f1cfe920e32fa797ed89fa44494196f3f9 on SAP:fix_initial_state_smoke_test into 0c2344a088d7c11481bd69b3d0e3b4050bebe04d on cloudfoundry-incubator:master.

authors: coveralls hsiliev

repo: cloudfoundry-incubator/cf-abacus


text:
Split locket into a separate pod

Is your feature request related to a problem? Please describe.
Diego-api pod has both BBS and locket.  The bbs is currently only talking using 127.0.0.1 which is not standard and causes custom certs to be created for kubecf to add that as an alternative name.
There is no reason locket and bbs should be in the same pod and would allow them to be more separate and make this issue https://github.com/cloudfoundry-incubator/kubecf/issues/25 also work better.
Describe the solution you'd like
Have locket a separate pod from Diego-api
Describe alternatives you've considered
Need to add 127.0.0.1 to the locket certs when this is not defined in cf-deployment.

With more investigation this is worse than I thought!   Right now locket.service.cf.internal will ONLY return the "active" diego-api.  This is incorrect.   locket server is not active/passive.  it is active/active and should as long as the locket container is running this DNS needs to return all of the diego-apis.
This is bad because we are no longer balancing this locket server load.  in a larger env we are stuck sending all locket requests to the same pod.  Which is poor use of resources.   I think this should be up the priority list as this is a regression from how bosh works for the locket server.

I'm in favour of this change. It is pretty much the same reason we split routing-api away from the api instance group, so api could be active/active while routing-api is active/passive.
And as already mentioned, it helps with Eirini: we can get rid of bbs and silk-controller jobs, and have locket in an instance group that doesn't have diego in its name.
I would prefer to do this using the quarks-specific qmove op instead of doing all the manual deployment manifest editing we do at build time currently. That would require https://github.com/cloudfoundry-incubator/quarks-operator/issues/1122 to be completed though; otherwise scripts/image_list.rb is going to break.
According to the Quarks team tracker this is scheduled for the sprint at the end of the month, but given that they dealt with a lot of unscheduled work lately, I suspect this might slip a bit. I would still prefer to wait for that.

authors: andrew-edgar jandubois

repo: cloudfoundry-incubator/kubecf


text:
memory leak when network ranges are incorrect

If you have a broken network range, like:
        static:
          - 10.20.4.10 - 10.10.4.50

(note it starts in 10.20.x.x and ends in 10.10.x.x). Currently, that causes spiff to use all available memory and die. Detecting that as a problem and spitting out an error would be a more ideal outcome.

Closing, spiff is not under active development, and no non-critical issues are being fixed.

authors: Amit-PivotalLabs teancom

repo: cloudfoundry-incubator/spiff


text:
Add file path of the stub in the errors

Fixed old cover repo
Added stub file path to the errors for diff & merge
Cleaning the path

The errors now look like this:
2015/02/19 10:55:12 error parsing stub [../diego-release/templates/jobs.yml]: yaml: [while scanning a simple key] could not find expected ':' at line 410, column 11

@onsi @vito Which tracker should receive spiff stories? Diego? Runtime? Concourse?

Also, thanks, @hsiliev, this change looks super useful!

authors: ematpl hsiliev


text:
service plan cost truncated in 1st service display

Frontend Deployment type

[x] Cloud Foundry Application (cf push)
[ ] Kubernetes, using a helm chart
[ ] Docker, using docker compose
[ ] Docker, single container deploying all components
[ ] npm run start
[ ] Other (please specify below)

Backend (Jet Stream) Deployment type

[x] Cloud Foundry Application (cf push)
[ ] Kubernetes, using a helm chart
[ ] Docker, using docker compose
[ ] Docker, single container deploying all components
[ ] Other (please specify below)

Expected behaviour
Service plan costs display is consistent over time
Actual behaviour
Service plan costs display is initially truncated, and then properly displayed once a service instance creation screen has shown
Steps to reproduce the behavior

Deploy a service broker which returns the following V2/catalog payload

{
  "services": [
    {
      "id": "noop-ondemand-service",
      "name": "noop-ondemand",
      "description": "On demand noop dedicated cluster",
      "bindable": true,
      "plans": [
        {
          "id": "noop-ondemand-plan",
          "name": "default",
          "description": "Default plan (beta).",
          "metadata": {
            "key1": "value1",
            "costs": [
              {
                "amount": {
                  "eur": 48
                },
                "unit": "Monthly"
              }
            ],
            "key2": "value2",
            "displayName": "noop plan display name",
            "bullets": [
              "2GB storage",
              "50 concurrent connections"
            ]
          },
          "free": false
        }
      ],
      "tags": [
        "noop",
        "document"
      ],
      "metadata": {},
      "requires": []
    }
  ]
}

Go to marketplace
Display service plans for a given service : the cost is truncated

Start service instance creation workflow: service plan displays correctly

Cancel service instance creation
Display service plans for the service: cost is not truncated

Log output covering before error and any error statements
Insert log hereCopy

Detailed Description

Following https://github.com/cloudfoundry-incubator/stratos/pull/2959
 the costs are properly displayed.
Context

Why is this change important to you? How would you use it?

our users see broken costs display in their marketplace. This triggers support requests.

Reproduced with current stable stratos with commit hash https://github.com/cloudfoundry-incubator/stratos/commit/a728011a79e47be7eb017394542b8816efc5a596
Possible Implementation
Suspecting the create service instance workflow is modifying/normalizing the service catalog data, and that this logic is missing when only displaying service plans
/CC @ldangeard-orange

Good spot! I think we use a common component to show all, so it could be that the data is missing in one instance. We'll look into this

@gberche-orange Found the issue! We failed to register the fr locale, which it used to format the currency value, at the service plan table level. This already happens when we show the service plan card in the create service stepper, which explains why after visiting it the amount is shown correctly. I've created a PR and the fix will be in the next release

great, thanks @richard-cox !

authors: gberche-orange richard-cox

repo: cloudfoundry-incubator/stratos


text:
Support non-public Azure Clouds

This change allows the bosh-azure-storage-cli to handle objects in Azure Storage Accounts within Azure Clouds that are non-public, such as AzureChinaCloud.

@s4heid thanks for this contribution. Could you pleas sign the CLA because it is required in case the PR gets accepted.

@beyhan completed! good to see you're still around.

@s4heid, can you rebase the commit (due to changes in go.mod) and I'll merge this?

@jpalermo I appreciate this. branch is rebased.

authors: beyhan jpalermo s4heid

repo: cloudfoundry/bosh-azure-storage-cli


text:
add vim-runtime to jammy

this would solve #239

i removed the commit related to the gitingore issue

Thanks! @ramonskie

authors: ramonskie rkoster


text:
Cannot clone git repositories when system buildpacks are present

Disclaimer: We do not think this repo is at fault here, but we were asked to place it here to start the conversations.
This issue is present with multiple buildpacks that contain both custom git buildpacks and system buildpacks.
When CloudController sends a staging task to Diego, we run the builder with the following arguments:
"run": {
  "path": "/tmp/lifecycle/builder",
  "args": [
    "-buildpackOrder=https://github.com/cloudfoundry/ruby-buildpack,a1d04795-b3c5-4e25-bdad-52d8d1375536_17d67a7a0ac5ddb34107bf1058e9e2b37a7146e1a54b32c551f13760fee91fe0",
    "-skipCertVerify=true",
    "-skipDetect=true",
    "-buildDir=/tmp/app",
    "-outputDroplet=/tmp/droplet",
    "-outputMetadata=/tmp/result.json",
    "-outputBuildArtifactsCache=/tmp/output-cache",
    "-buildpacksDir=/tmp/buildpacks",
    "-buildArtifactsCacheDir=/tmp/cache"
  ]
}

Here, the buildpackOrder contains a custom buildpack and a reference to a system buildpack. The UUID corresponds to the md5 of an asset downloaded via a different section of the staging task known as cached_dependencies. Here is an example of how this looks:
{
  "name": "go_buildpack",
  "from": "https://blobstore.service.cf.internal:4443/read/cc-buildpacks/a1/d0/a1d04795-b3c5-4e25-bdad-52d8d1375536_17d67a7a0ac5ddb34107bf1058e9e2b37a7146e1a54b32c551f13760fee91fe0?md5=gcf6IvatmS0wQO1Vh5dn6Q&expires=1500947864",
  "to": "/tmp/buildpacks/62cdbebce85c4a0f1960ec2c70e09009",
  "cache_key": "a1d04795-b3c5-4e25-bdad-52d8d1375536_17d67a7a0ac5ddb34107bf1058e9e2b37a7146e1a54b32c551f13760fee91fe0",
  "log_source": "",
  "checksum_algorithm": "sha256",
  "checksum_value": "17d67a7a0ac5ddb34107bf1058e9e2b37a7146e1a54b32c551f13760fee91fe0"
}

With this snippet, Diego will download that cached dependency to /tmp/buildpacks/62cdbebce85c4a0f1960ec2c70e09009. (Note: the md5 of a1d04795-b3c5-4e25-bdad-52d8d1375536_17d67a7a0ac5ddb34107bf1058e9e2b37a7146e1a54b32c551f13760fee91fe0 is 62cdbebce85c4a0f1960ec2c70e09009)
Our theory
In the process it created the /tmp/buildpacks in a way that disallows vcap write permissions. Therefore, when the builder attempts to clone to /tmp/buildpacks/<some-uuid> as vcap, it lacks the permissions necessary.

@ematpl Is this an executor issue?

@sclevine I think it's really a Garden issue: to my recollection, any intermediate directories in a bind-mount path will be created with root ownership. The bind-mount directives are also specified at container creation, so unless those directories are already present in the rootfs there's no way for the Garden client to create them before the bind-mount would.

@sclevine We have a plan, which is to create a new directory for Downloading buildpacks to.

@dgodd cherry-picked your commit and confirmed that this fixes the issue for us, thanks!

Awesome @ljfranklin, I'm closing this issue

authors: aashah dgodd ematpl ljfranklin sclevine

repo: cloudfoundry/buildpackapplifecycle


text:
Removing loggregator endpoints from advertised endpoints when unavailable

Issue
As operators adopt the shared nothing logging and metrics architecture they may at the same time want to disable the older firehose loggregator architecture. We're not sure how this should affect which endpoints the Cloud Controller should advertise.
Context
Currently the Cloud Controller advertises endpoints for the Loggregator Traffic Controller and Reverse Log Proxy Gateway in the root controller:
$ cf curl / | jq -r '.links | [.logging, .log_stream][] | .href'
wss://doppler.sys.example.com:443
https://log-stream.sys.example.com

The Traffic Controller endpoint is also advertised under /v2/info:
$ cf curl /v2/info | jq -r '.doppler_logging_endpoint'
wss://doppler.sys.yarn-519593.cf-app.com:443

As operators may choose to no longer deploy these components we're wondering what the Cloud Controller should serve in these responses.

The Cloud Controller could stop having entries for these endpoints altogether when they are not deployed.
The Cloud Controller could have entries but with null values as may be already the case for some endpoints.
The Cloud Controller could continue to return these endpoints even though they are not actually available.

We believe currently the Cloud Controller always advertises these endpoints.
We'd think we'd like to not return endpoints that don't exist. However we're not sure what the impact of doing so might be on clients that are looking at these fields?
CC @rroberts2222

Looks like we already have a pattern for returning null for the root (/) endpoint:
https://github.com/cloudfoundry/cloud_controller_ng/blob/41f6344663b048e79c9279d8786d3645ad096262/app/controllers/runtime/root_controller.rb#L83-L93

authors: Gerg acrmp


text:
RemoteTokenServices does not return the "issu" from the JWT

Hi,
We need to get the "issu" from the JWT but the RemoteTokenServices does not return it. We have to modify the code to extract the "issu" from JWT and set it in the loadAuthentication method as following:
    if (map.containsKey("iss")) {
        Map<String, String> requestParameters = new HashMap<String, String>();
        requestParameters.put("iss", (String) map.get("iss"));
        clientAuthentication.setRequestParameters(requestParameters);
    }

Can you include this in the future version/release?
Thanks,,
Dave

Fixed.
https://www.pivotaltracker.com/story/show/90296800

authors: dave-chen fhanik

repo: cloudfoundry/uaa


text:
SecurityGroup GroupName should default to instance-id

Look for other resources that do not have this behavior.

This issue  solved

authors: EarthmanT mabuaisha


text:
jquery.cloudinary.js cannot be minified

Steps to Reproduce

Install the YUI-compressor gem
Run the following command on jquery.cloudinary.js, and you should be able to reproduce the error. (Adjust the path to yuicompressor-2.4.8.jar file if you are not using rbenv)

java -jar ~/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/yui-compressor-0.12.0/lib/yuicompressor-2.4.8.jar --type js --charset utf-8 --nomunge jquery.cloudinary.js
```

## More Details

I am using Cloudinary in a Rails application.

Recently I upgraded the cloudinary gem from 1.1.0 to 1.1.2, and the application javascripts were no longer compiling when doing `rake assets:precompile`. Version 1.1.1 of the gem exhibited the same problem. Version 1.1.0 continue to work as expected.

As part of the asset pipeline compilation process, I am using the [YUI-compressor gem](https://github.com/sstephenson/ruby-yui-compressor) to minify the application Javascript.

I am reporting the issue in this repository and not in the [cloudinary_gem](https://github.com/cloudinary/cloudinary_gem) repo, because I eventually tracked the issue down to the `jquery.cloudinary.js` file in this repository, which throws errors when being minified.

The last version of `jquery.cloudinary.js` that is minifiable appears to be in the `1.0.25` release of `cloudinary_js`, with the SHA of `109ff78056b161e8260b52b779554750f533e3d1`, which appears to be the version present in version 1.1.0 of `cloudinary_gem`.

Below are the error messages that appear when trying to minify `jquery.cloudinary.js`:

```
vagrant@www:/vagrant/tmp/temp_repos/cloudinary_js/js$ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
vagrant@www:/vagrant/tmp/temp_repos/cloudinary_js/js$ java -jar ~/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/yui-compressor-0.12.0/lib/yuicompressor-2.4.8.jar --type js --charset utf-8 --nomunge jquery.cloudinary.js
[ERROR] in jquery.cloudinary.js
  679:33:missing formal parameter
[ERROR] in jquery.cloudinary.js
  679:33:missing } after function body
[ERROR] in jquery.cloudinary.js
  680:30:missing ; before statement
[ERROR] in jquery.cloudinary.js
  681:20:syntax error
[ERROR] in jquery.cloudinary.js
  688:13:missing ) after argument list
[ERROR] in jquery.cloudinary.js
  688:14:syntax error
[ERROR] in jquery.cloudinary.js
  694:19:missing name after . operator
[ERROR] in jquery.cloudinary.js
  711:12:missing ) in parenthetical
[ERROR] in jquery.cloudinary.js
  711:13:syntax error
[ERROR] in jquery.cloudinary.js
  712:14:syntax error
[ERROR] in jquery.cloudinary.js
  713:15:invalid return
[ERROR] in jquery.cloudinary.js
  714:7:syntax error
[ERROR] in jquery.cloudinary.js
  727:24:missing name after . operator
[ERROR] in jquery.cloudinary.js
  728:28:missing name after . operator
[ERROR] in jquery.cloudinary.js
  729:15:missing ; before statement
[ERROR] in jquery.cloudinary.js
  731:9:syntax error
[ERROR] in jquery.cloudinary.js
  795:13:invalid return
[ERROR] in jquery.cloudinary.js
  797:5:syntax error
[ERROR] in jquery.cloudinary.js
  814:38:missing formal parameter
[ERROR] in jquery.cloudinary.js
  814:38:missing } after function body
[ERROR] in jquery.cloudinary.js
  815:26:missing ; before statement
[ERROR] in jquery.cloudinary.js
  816:16:syntax error
[ERROR] in jquery.cloudinary.js
  817:9:syntax error
[ERROR] in jquery.cloudinary.js
  818:14:syntax error
[ERROR] in jquery.cloudinary.js
  819:64:identifier is a reserved word
[ERROR] in jquery.cloudinary.js
  820:7:syntax error
[ERROR] in jquery.cloudinary.js
  822:18:syntax error
[ERROR] in jquery.cloudinary.js
  824:23:missing name after . operator
[ERROR] in jquery.cloudinary.js
  825:18:syntax error
[ERROR] in jquery.cloudinary.js
  827:19:invalid return
[ERROR] in jquery.cloudinary.js
  843:19:invalid return
[ERROR] in jquery.cloudinary.js
  843:30:missing name after . operator
[ERROR] in jquery.cloudinary.js
  845:9:syntax error
[ERROR] in jquery.cloudinary.js
  847:9:syntax error
[ERROR] in jquery.cloudinary.js
  858:13:invalid return
[ERROR] in jquery.cloudinary.js
  860:5:syntax error
[ERROR] in jquery.cloudinary.js
  876:47:missing formal parameter
[ERROR] in jquery.cloudinary.js
  876:47:missing } after function body
[ERROR] in jquery.cloudinary.js
  877:18:identifier is a reserved word
[ERROR] in jquery.cloudinary.js
  878:18:syntax error
[ERROR] in jquery.cloudinary.js
  879:9:syntax error
[ERROR] in jquery.cloudinary.js
  880:26:missing ; before statement
[ERROR] in jquery.cloudinary.js
  881:16:syntax error
[ERROR] in jquery.cloudinary.js
  882:9:syntax error
[ERROR] in jquery.cloudinary.js
  883:14:syntax error
[ERROR] in jquery.cloudinary.js
  884:73:identifier is a reserved word
[ERROR] in jquery.cloudinary.js
  885:7:syntax error
[ERROR] in jquery.cloudinary.js
  887:27:syntax error
[ERROR] in jquery.cloudinary.js
  890:17:invalid return
[ERROR] in jquery.cloudinary.js
  894:19:invalid return
[ERROR] in jquery.cloudinary.js
  894:30:missing name after . operator
[ERROR] in jquery.cloudinary.js
  896:19:invalid return
[ERROR] in jquery.cloudinary.js
  907:42:missing name after . operator
[ERROR] in jquery.cloudinary.js
  920:17:invalid return
[ERROR] in jquery.cloudinary.js
  922:7:syntax error
[ERROR] in jquery.cloudinary.js
  933:13:invalid return
[ERROR] in jquery.cloudinary.js
  935:5:syntax error
[ERROR] in jquery.cloudinary.js
  951:38:missing formal parameter
[ERROR] in jquery.cloudinary.js
  951:38:missing } after function body
[ERROR] in jquery.cloudinary.js
  952:30:missing ; before statement
[ERROR] in jquery.cloudinary.js
  953:20:syntax error
[ERROR] in jquery.cloudinary.js
  954:9:syntax error
[ERROR] in jquery.cloudinary.js
  955:20:syntax error
[ERROR] in jquery.cloudinary.js
  956:7:syntax error
[ERROR] in jquery.cloudinary.js
  958:18:syntax error
[ERROR] in jquery.cloudinary.js
  965:15:invalid return
[ERROR] in jquery.cloudinary.js
  966:7:syntax error
[ERROR] in jquery.cloudinary.js
  968:13:invalid return
[ERROR] in jquery.cloudinary.js
  970:5:syntax error
[ERROR] in jquery.cloudinary.js
  974:36:missing formal parameter
[ERROR] in jquery.cloudinary.js
  974:36:missing } after function body
[ERROR] in jquery.cloudinary.js
  975:30:missing ; before statement
[ERROR] in jquery.cloudinary.js
  976:20:syntax error
[ERROR] in jquery.cloudinary.js
  977:9:syntax error
[ERROR] in jquery.cloudinary.js
  978:18:syntax error
[ERROR] in jquery.cloudinary.js
  979:7:syntax error
[ERROR] in jquery.cloudinary.js
  981:16:syntax error
[ERROR] in jquery.cloudinary.js
  983:7:syntax error
[ERROR] in jquery.cloudinary.js
  985:13:invalid return
[ERROR] in jquery.cloudinary.js
  987:5:syntax error
[ERROR] in jquery.cloudinary.js
  994:11:invalid return
[ERROR] in jquery.cloudinary.js
  995:3:syntax error
[ERROR] in jquery.cloudinary.js
  997:1:syntax error
[ERROR] in jquery.cloudinary.js
  1:0:Compilation produced 83 syntax errors.
org.mozilla.javascript.EvaluatorException: Compilation produced 83 syntax errors.
	at com.yahoo.platform.yui.compressor.YUICompressor$1.runtimeError(YUICompressor.java:172)
	at org.mozilla.javascript.Parser.parse(Parser.java:396)
	at org.mozilla.javascript.Parser.parse(Parser.java:340)
	at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:315)
	at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:536)
	at com.yahoo.platform.yui.compressor.YUICompressor.main(YUICompressor.java:147)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.yahoo.platform.yui.compressor.Bootstrap.main(Bootstrap.java:21)
```

However, it worked on version `109ff78056b161e8260b52b779554750f533e3d1`:

```
vagrant@www:/vagrant/tmp/temp_repos/cloudinary_js/js$ git checkout 109ff78056b161e8260b52b779554750f533e3d1
Note: checking out '109ff78056b161e8260b52b779554750f533e3d1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 109ff78... Update version to 1.0.25
vagrant@www:/vagrant/tmp/temp_repos/cloudinary_js/js$ java -jar ~/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/yui-compressor-0.12.0/lib/yuicompressor-2.4.8.jar --type js --charset utf-8 --nomunge jquery.cloudinary.js
(function(factory){if(typeof define==="function"&&define.amd){define(["jquery","jquery.ui.widget","jquery.iframe-transport","jquery.fileupload"],factory)}else{var $=window.jQuery;factory($);$(function(){if($.fn.cloudinary_fileupload!==undefined){$("input.cloudinary-fileupload[type=file]").cloudinary_fileupload()}})}}(function($){var CF_SHARED_CDN="d3jpl91pxevbkh.cloudfront.net";var OLD_AKAMAI_SHARED_CDN="cloudinary-
.... (the rest of the minified file) ...
```

So, something happened after the `109ff78056b161e8260b52b779554750f533e3d1` version of the file after September 1 that broke `jquery.cloudinary.js`, as far as its ability to be minimized goes.

This probably breaks a lot of Rails applications as minimization is routinely done as part of asset compilation!

@fredngo Thanks for the detailed report!
We'll look into it.

Any ideas about this? We are essentially locked to the increasingly outdated version 1.1.0 of the cloudinary gem due to this...

Confirmed. The issue is with the name of the Param() argument short. We'll fix it.
If in a rush, issue the following command:
sed -i  's/\bshort\b/shortName/g' jquery.cloudinary.js

and then run yui-compressor again.

@fredngo Please update your cloudinary gem to version 1.2.1:
gem 'cloudinary', '~> 1.2', '>= 1.2.1'

It should solve the issue.

@tocker Thank you so much for the followup!

@tocker Unfortunately it's too huge of a jump to go from 1.1.0 to 1.2.1/2... Nothing works anymore. :) The underlying JS probably changed a lot from 1.1.0 to 1.2.2. Thanks for the fix though, I'll slowly debug to see where the problem might be.

@fredngo if your error is on the UI, it may be due to the initialization of the JavaScript upload plugin. Simply call $.cloudinary_file_upload() after the page loads. Otherwise 1.2.1 should be backward compatible with 1.1.0.

@tocker Appreciate the pointer, I'll definitely check that out!

authors: fredngo tocker


text:
Add 64Bit support for floats

On 64Bit systems the doubleValue is being truncated when being sent to properties of 'float' type.   Example being CALayer.shadowOpacity.
This PR creates a dedicated primitive conversion for Float types to handle this truncation

:+1:

@cloudkite Sorry for the big PR.   The float / double fix turned out to break some tests, then I noticed some other tests were failing as well, so I went ahead and cleaned those up.   Let me know if you've got any questions

@flippinjoe21 No problem, at first glance looks great. Will hopefully review in next couple of days

@flippinjoe21 looks great, Thanks!

repo: cloudkite/Classy