text:
Error starting provider *kubernetes.Provider: endpoint missing for external cluster client

Do you want to request a feature or report a bug?
bug

What did you do?
Deployed Træfik to Kubernetes as a DaemonSet.

What did you expect to see?
I expected all instances (Pods) of Træfik to have the same configuration.
What did you see instead?
One of the pods had the following console log error message and no other configuration:
Error starting provider *kubernetes.Provider: endpoint missing for external cluster client

Output of traefik version: (What version of Traefik are you using?)

v1.3.3

What is your environment & configuration (arguments, toml, provider, platform, ...)?
checkNewVersion = false

logLevel = "WARN"

InsecureSkipVerify = true

defaultEntryPoints = ["http", "https"]

[entryPoints]
  [entryPoints.http]
  address = ":80"

  [entryPoints.https]
  address = ":443"
    [entryPoints.https.tls]
      [[entryPoints.https.tls.certificates]]
      CertFile = "**REDACTED**.pem"
      KeyFile = "**REDACTED**.key"

[web]
address = ":8181"

[web.metrics.prometheus]
Buckets=[0.1,0.3,1.2,5.0]

If applicable, please paste the log output in debug mode (--debug switch)
(paste your output here)

Traefik only tries to create an out-of-cluster client connection if it does not find one of the KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT environment variables. Can you make sure they are available?
What version of Kubernetes are you running?

Restarting solved the problem, but it was very scary that it remained running and did not exit when it hit this error. I'll try setting the variables you mentioned for my Træfik deployment.
Kubernetes version 1.6.7

The variables should be injected by Kubernetes. There should be no need to set them manually.
My best guess is that some control loop hadn't finished yet so the node wasn't quite ready.
Making a decision to exit can be tricky: there might be other providers running just fine, so we'd be stopping them as well. It's not a no-go but it's something to be considered carefully. A better approach is often to retry; unfortunately, environment variables are only injected during process startup.
If you have a chance to determine the root cause of your problem, we can further consider ways to mitigate / solve the issue.

@Starefossen did you manage to determine the reason for your problem by now?

I haven't been able to reproduce this error with any of the versions since v.1.3.3. Closing this. Thanks for all the help and making Træfik so awesome ❤

@timoreimann I'm sorry to respond on a closed ticket, but I don't want to open a new one just yet (I'd be happy to do so if you prefer that). I just had the same problem with traefik version 1.4.6 on kubernetes 1.8.3.
This happened after restarting each of the nodes in the cluster for OS updates. Strangely, only 1 of the 3 daemonset ingress controllers was affected with this problem. I've seen the same happen before on older versions of traefik and kubernetes but back then it was only a 1 time thing, now it's becoming a pattern.
I don't mind if traefik breaks, but because the pod continued running and did not show an error to the outside world (only the entry in the log), this would be very hard to detect by our monitoring systems. Would it perhaps be possible for traefik to exit when it comes upon this error? I'm not sure what providers would be running in the same pod that would be considered ok, but in my mind if one component in a pod is not ok, the whole pod is not ok. Safety in numbers (more than 1 traefik instance) will make sure the cluster remains available while the pod terminates.

@mvernimmen prior to thinking about any potential changes to Traefik, I'd still like to understand first why the problem occurs. As I have explained before, the error should only manifest in an in-cluster usage if certain environment variables provided by Kubernetes are not injected for whatever reason. My best guess continues to be that the node wasn't fully ready yet or something along those lines. (FWIW, we restart Traefik multiple times a day sometimes, and I haven't run into the issue myself.) Do you have a chance to investigate to hopefully figure out the root cause?
It should still be possible to detect the scenario described, at least if you're using Prometheus: We expose metrics on the latest configuration update, so you could alert if a configuration update has never happened or there's too much of a divergence between multiple Traefik instances.
I'll reopen for the time being.

I am going to go ahead and close this issue, since it apparently hasn't occurred since.
@mvernimmen If you run into this issue in the future, please let us know, as with the latest release (1.6) we have implemented hundreds of new features, and may have fixed the issue you encountered.
Please open a new ticket if you re-encounter this issue.
Thanks!

Hi,
We are experiencing the same issue with traefik 1.7.8 on gke 1.12.5. We are also running traefik as daemonset (30-65 nodes).
it seems to occur during rapid autoscaling usecases (Nodes with high pressure) - and not on all nodes. Any suggestions on how to mitigate this issue?

authors: Starefossen dtomcej mvernimmen recet timoreimann

repo: containous/traefik


text:
Error: Protocol error, got "H" as reply type byte

config as below:
[log]
  level = "debug"
  format = "json"

[accessLog]
  filePath = "./traefik.log"
  format = "json"

[entryPoints]
  [entryPoints.aq_proxy]
    address = ":6388/tcp"
[tcp]
  [tcp.routers]
      [tcp.routers.Router-1]
        rule = "HostSNI(`*`)"
        service = "my-service"
      [tcp.routers.Router-1.tls]
  [tcp.services]
    [tcp.services.my-service.loadBalancer]
       [[tcp.services.my-service.loadBalancer.servers]]
         address = "127.0.0.1:6379"

get title error, I  have gone through the doc but I can't find the reason out.

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
No IP in backend in shared network namespaces using –net=container:

I have a container that is running in shared network namespaces with another container (by using the option --net=container:another-container)
In that case, the new container will have the same network stack (and same IP) as the old container it is being linked to.
When traefik picks it, the backend's URL is set to http://:5050, the IP is missing
A docker inspect of the new container has no values in the Network part of the output (so i assume this is why traefik does not pick the IP).
In that case, traefik should observe the NetworkMode value, which in that case is:
"NetworkMode": "container:LINKED_CONTAINER_NAME",
so it can get the network settings of the new container from the network settings of the LINKED_CONTAINER_NAME

See also: https://github.com/containous/traefik/issues/1076

@Nossnevs I don't think that it is related.
I have the same issue. I think that it is related to the fact that NetworkSettings are empty when you start a container with this context.
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {}
        }

An example of docker-compose that trigger the same bug (based on get started config): https://gist.github.com/sapk/94de150b3639692242803b9b2bdfa526

It could be fixed by checking if container.NetworkSettings.NetworkMode start with container: like :
https://github.com/containous/traefik/blob/d97309646483aa39ecd0db160e68b46315077a1d/provider/docker/docker.go#L600
and chainload to look ipaddress of container id after the string container:.
I could try to fix this if this solution look goods to you.

Closed by #2331.

authors: Nossnevs amatsoukas sapk traefiker


text:
Pass through certain forward auth negative response headers

This alters forward authentication allowing servers to set cookies and redirect clients to other locations if needed.
Description
The current version of httpClient automatically follows redirects, so if a forward auth server decides to redirect the original client to a different page to continue authentication, Go will simply follow the redirect rather than passing the redirection back to the original client.
This is problematic when the forward auth function returns an unexpected success if it was able to follow a redirection chain until it encountered a 200 response. This PR alters the httpClient to stop following redirects automatically and pass a Location header from a negative forward auth response, if one exists.
Additionally, the forward auth server is not able to set any cookies (other than including JavaScript in the response body, I suppose). This PR also passes the Set-Cookie header on a negative forward auth response.

@emilevauge @wheresmysocks any ETA on this one❓

Should now be back up to date with master.

source: gharchive/pull-request

authors: jkaberg wheresmysocks


text:
Don't pass the Authorization header to the backends

What does this PR do?
Add an option to remove the Authorization header for the basic and the digest authentication for the following providers :

[x] File
[x] k8s
[x] Docker
[x] Rancher
[x] Consul Catalog
[x] Marathon
[x] Mesos
[x] ECS
[x] KV

Motivation
Fixes #3448
More

[x] Added/updated tests
[x] Added/updated documentation

Additional Notes

Fix the authentication documentation for the mesos and the marathon providers.
Add a unit test for the authentication configuration with segment labels for the marathon provider.

Auth.Basic.Removeheader:true works for Firefox, Chrome does not work for me.

authors: jbdoumenjou lukasmrtvy


text:
Refs 1918: Update Readme to include install step for nvm

Summary
Updated the Readme to include an install step for nvm
Testing steps
Check the new step in the Readme do give feedback if you find a better way to say this.

/retest

https://issues.redhat.com/browse/HMS-1918

/retest

/retest

authors: jlsherrill kwarnerredhat swadeley


text:
fix: change container/columns default Margin value [ALT-1388]

Purpose
Changes the Container and Columns default margin value back to 0 0 0 0 and added a comment to mention that the UI overrides the value to 0 Auto 0 Auto when these components are added at the root/top-level

Why are we doing this? And why is the UI not just applying this defaultValue? I feel like there is a good reason but I can't remember

@ryunsong-contentful, When you drop a new Columns or Container component on the canvas, the ComponentAddedAction in the UI calls applyNodeModifications() and if the component is dropped on the root level it will override the defaultValue from the component definition with 0 Auto 0 Auto to set left/right margin auto.
We need the defaultValue to be 0 0 0 0 for these two components here so that when that override doesn't occur on the UI side (such as dropping these two components into a nested structure instead of the root level) it will not add the left/right margin auto.

repo: contentful/experience-builder


text:
Unable to upgrade to 0.2.5

The following error is given when trying to install v0.2.5 via pip:
Collecting rich_text_renderer==0.2.5
  Using cached rich_text_renderer-0.2.5.tar.gz (4.7 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "C:\Users\kramr\user\Local\Temp\pip-install-2sfr66oo\rich-text-renderer_d782b3a986f848dbbc2fb95938f41401\setup.py", line 22, in <module>
          with open('README.rst', 'r') as f:
      FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Hi @kramrm, thanks for reporting the issue. We are taking a look at it.
Cheers

Hi @rubydog - thanks for the new release, but I'm afraid this is still an ongoing glitch. The README isn't in the collected assets to read:
$ pip install rich-text-renderer==0.2.6
Collecting rich-text-renderer==0.2.6
  Using cached rich_text_renderer-0.2.6.tar.gz (4.7 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/private/var/folders/xh/n4lvfgnn48195r6tt0jx_8fh0000gn/T/pip-install-1caexk75/rich-text-renderer_be7363acdbe6420b9dd662a772535620/setup.py", line 63, in <module>
          long_description=open('README.rst').read(),
      FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

And the source package (here)[https://files.pythonhosted.org/packages/d1/c5/6d5be555bff6e202205975a642625bb5d9c5b86a44372559e8971a9d4b2f/rich_text_renderer-0.2.6.tar.gz} seems to still lack the README:
$ tree rich_text_renderer-0.2.6
rich_text_renderer-0.2.6
├── PKG-INFO
├── rich_text_renderer
│   ├── __init__.py
│   ├── base_node_renderer.py
│   ├── block_renderers.py
│   ├── document_renderers.py
│   ├── null_renderer.py
│   ├── rich_text_renderer.py
│   └── text_renderers.py
└── setup.py

I think this issue is worth re-opening.

@stevejalim I agree the issue still exists. The problem was with the old packaging strategy, we have switched to twine now (PR #22). Hopefully, it should be fixed in the next release.
Cheers

Fixed in #22

authors: kramrm rubydog stevejalim


text:
[Snyk] Upgrade adm-zip from 0.5.15 to 0.5.16

Snyk has created this PR to upgrade adm-zip from 0.5.15 to 0.5.16.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.

The recommended version was released on 25 days ago.

Release notes

Package name: adm-zip

0.5.16 - 2024-08-30What's Changed

Fixing preserving linux file permissions by @ NickAllmakerOpsCompass in #531
fix: totalEntries is not defined by @ sidartaveloso in #535

New Contributors

@ NickAllmakerOpsCompass made their first contribution in #531
@ sidartaveloso made their first contribution in #535

Full Changelog: v0.5.15...v0.5.16

0.5.15 - 2024-08-05What's Changed

Fix utils canonical to valid posix by @ skoniks in #499
addFile backslash test by @ 5saviahv in #500
added addLocalFolderAsync2 by @ 5saviahv in #501
fixed windows paths by @ roosipuu in #503
Add Windows build by @ 5saviahv in #504
inital "decoder" functionality by @ 5saviahv in #505
Bump braces from 3.0.2 to 3.0.3 by @ dependabot in #506
Write out Electron original-fs auto loading by @ 5saviahv in #502
using writeZip() twice throws "Invalid LOC header (bad signature)" error by @ 5saviahv in #507
Descriptor check & Main Header locating by @ 5saviahv in #508
House keeping by @ 5saviahv in #509
typo by @ 5saviahv in #510
Allow interoperability files with non-UTF-8 (bit 11 = 0) name by @ yfdyh000 in #450
package lock update by @ 5saviahv in #511
small updates by @ 5saviahv in #513
CodeQL check by @ 5saviahv in #514
Keep local extra data by @ 5saviahv in #515
Update old test by @ 5saviahv in #516
make all errors a function by @ 5saviahv in #517
Update date time functions by @ 5saviahv in #518
Add a length check when extra field parsed by @ code-sunbo in #520
deleteFile is too eager by @ 5saviahv in #525

New Contributors

@ skoniks made their first contribution in #499
@ roosipuu made their first contribution in #503
@ code-sunbo made their first contribution in #520

Full Changelog: v0.5.14...v0.5.15

    from adm-zip GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Since using adm-zip@0.5.16 version, closing this PR.

repo: contentstack/contentstack-apps-cli


text:
protobuf option optimize_for = LITE_RUNTIME

The helper function GetProtoMessageDescription uses a google::protobuf::Message-reference to get some information about the protobuf message.
This works fine with generated files using the protobuf default settings. However, when generating the protobuf source files with the option optimize_for = LITE_RUNTIME;-option activated, it seems like the generated messages does not use the google::protobuf::Message as base class anymore. Thus the build ends in compiler errors.
I think this is a bug and I guess to fix this you have to provide templated functions checking for the right base class. Currently I am fine with removing this option from my protobuf-file.
To reproduce the error, you have to add  option optimize_for = LITE_RUNTIME; to one of your protobuf files and use the generated classes with the eCAL::protobuf::CSubscriber.

I reproduces the error using eCAL Hello World Protobuf. For future reference, here is the error:
[ 25%] Running C++ protocol buffer compiler on /home/florian/Desktop/hello world proto/proto_messages/hello_world.proto
Scanning dependencies of target protobuf_snd
[ 50%] Building CXX object CMakeFiles/protobuf_snd.dir/main.cpp.o
In file included from /home/florian/Desktop/hello world proto/protobuf_snd/main.cpp:2:
/usr/include/ecal/msg/protobuf/publisher.h: In instantiation of ‘std::string eCAL::protobuf::CPublisher<T>::GetDescription() const [with T = proto_messages::HelloWorld; std::string = std::__cxx11::basic_string<char>]’:
/usr/include/ecal/msg/protobuf/publisher.h:71:97:   required from ‘eCAL::protobuf::CPublisher<T>::CPublisher(const string&) [with T = proto_messages::HelloWorld; std::string = std::__cxx11::basic_string<char>]’
/home/florian/Desktop/hello world proto/protobuf_snd/main.cpp:13:90:   required from here
/usr/include/ecal/msg/protobuf/publisher.h:127:53: error: invalid initialization of reference of type ‘const google::protobuf::Message&’ from expression of type ‘proto_messages::HelloWorld’
  127 |         return(protobuf::GetProtoMessageDescription(msg));
      |                                                     ^~~
In file included from /usr/include/ecal/msg/protobuf/publisher.h:28,
                 from /home/florian/Desktop/hello world proto/protobuf_snd/main.cpp:2:
/usr/include/ecal/protobuf/ecal_proto_hlp.h:130:82: note: in passing argument 1 of ‘std::string eCAL::protobuf::GetProtoMessageDescription(const google::protobuf::Message&)’
  130 |   inline std::string GetProtoMessageDescription(const google::protobuf::Message& msg_)
      |                                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
make[2]: *** [CMakeFiles/protobuf_snd.dir/build.make:71: CMakeFiles/protobuf_snd.dir/main.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/protobuf_snd.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

I haven't done a lot of research about protobuf-lite, but to my understanding it is the same as protobuf minus some features like reflection, right? Because the eCAL Protobuf Publisher and Subscriber both rely on the reflection description string, as their main advantage over a raw byte-blob Subscriber and Publisher is that they include that string. The reflection allows you to dynamically deserialize and inspect the data in the eCAL Recorder (and other tools).
Why did you initially set the LITE_RUNTIME option? Are there some advantages (or disadvantages over "real" protobuf) that I am missing at the moment?
Regards
Florian

LITE_RUNTIME optimizes the generated code for fast accessors and omits reflection code:
https://stackoverflow.com/questions/4438977/which-protobuf-optimization
I did not know that ecal depends on protobufs reflection. I only want the fastes code protobuf can generate, i.e. I could stick on option optimize_for = SPEED;. However, I did not try the SPEED option yet.

eCAL itself is not depending on the protobuf reflection. The LITE_RUNTIME option will not generate functions that do provide the so called protobuf file descriptors. These descriptors are then forwarded by the high level templated protobuf publisher class as common "topic description". This topic description then can be used by apps like the eCAL monitor to provide reflection for live data monitoring.
So one option to use LITE_RUNTIME and eCAL pub/sub is to not use the eCAL::protobuf::CPublisher|CSubscriber classes but to use the lower level binary API eCAL::CPublisher|CSubscriber instead or the string variant eCAL::string::CPublisher|CSubscriber and do the serialization and deserialization yourself on both sides.

Yes, with "Rely on reflection string" I meant rely on the method returning the reflection string being present.
The best example of what the reflection is used for is the eCAL Monitor. The content of a message can only be displayed using the reflection string, as the Monitor would not know how to interpret the data otherwise:
https://continental.github.io/ecal/getting_started/monitor.html#topics
Btw, I checked whether the eCAL Hello World Protobuf example compiles with the SPEED option. It does. The reflection works fine.

authors: FlorianReimold rex-schilasky xR3b0rn

repo: continental/ecal


text:
Update eqeqeq rule

I'd like to propose adding "allow-null" to the eqeqeq rule. This would allow for checks for values of null or undefined to be done like:
function (value) {
  if (value == null) {
    console.log('value is null or undefined');
  }

While it's generally not a great idea to let JS do whatever it wants during coercion, in this one instance, I think the trade off is worth it as checking == null is a pretty common and understood pattern.

why not if (!value) or if (value === null || value === undefined) ?

if (!value) is not strictly equivalent.
I'm personally -1 on this, but it doesn't really matter anyway. This would have to get cleared in the hapi style guide.

Why are you -1 on this? I agree though, this would have to go up the ladder.

I don't like it because it is more consistent to just use === everywhere. This one exception only saves you a few characters. I think foo === undefined || foo === null is faster too.

How about taking this up with the style guide (in hapijs/contrib I think), and if it gets OKed, I'll reopen this.

authors: AdriVanHoudt arb cjihrig

repo: continuationlabs/eslint-config-hapi

license: mit

license_source: bigquery


text:
[CON-230] .continueignore doesn't respect negations

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS:*
- Continue:*
- IDE:*

Description
A pattern such as
**/*.*
!**/*.ts

should tell Continue only to index .ts files. But instead the effect is to index no files
To reproduce
No response
Log output
No response
CON-230

Can confirm behavior on the current version v0.8.29. Using this continueignore/gitignore file:

!*/
!.h
!.c
Negates everything but does not unnegate the specified strings.

@sestinj any activity on this?

*.*
!*.go

@Iceburgino
I've found this pattern works in .continueignore

authors: Iceburgino sestinj shannonrdunn

repo: continuedev/continue


text:
Updates to running the doc server locally

Description
CONTRIBUTING.md

changed 'navigate to project root directory' to 'navigate to docs subdirectory'

It seems like the process has changed, since you can't run npm from the root directory, there's no package.json there.  So I updated the instructions to start from the 'doc' subdir.

Added 'npm install' to instructions

This is required for new installs, right?
package.json

Changed npm start script to use double quotes for Windows compatibility

'nodemon' has some limitations using --exec on windows.  Double quotes are required for Windows users.
Checklist

[x] The base branch of this PR is dev, rather than main
[x] The relevant docs, if any, have been updated or created

Testing

Viewed CONTRIBUTING doc in browser on my fork.
Tested 'npm run start' in Windows 11 and MacOS Sonoma environments.

Follow the instructions in the updated doc to test:

Open your terminal and navigate to the docs subdirectory of the project.  The docusaurus.config.js file you'll see there is a sign you're in the right place.

Run the following command to install the necessary dependencies for the documentation server:
npm install

Run the following command to start the documentation server:
npm run start

I didn't fork the dev branch ... let me do that and try again.


text:
🛑 MPS - TESTPROCESS is down

In 27ce39e, MPS - TESTPROCESS ($TESTPROCESS_URL) was down:

HTTP code: 200
Response time: 847 ms

Resolved: MPS - TESTPROCESS is back up in b9bcc49 after 11 hours, 40 minutes.

repo: conuti-das/status-nbsap


text:
Heroku Crashed

Hi,
I tried your buildpack and this is the result :

I added the two env vars into my project :

Do you have any idea of what's going wrong ?
Thx

Hi @antoninlanglade!
It seems like you haven't added the node buildpack to your app, which has nothing to do with this Google Cloud buildpack! Adding the node buildpack should do the trick.

Thanks man.

authors: antoninlanglade petterhh


text:
VTOL_canard changes to Modular file

This is for a tri-copter canard configuration.

Can one of the admins verify this patch?

repo: convexopt/gpkit


text:
onVolumeChange event needed

Current Behavior
Player does not have volume change event listener.
Expected Behavior
Player fires event every time volume control changes of the native player ( tag).
Steps to Reproduce

Enable controls in Demo: https://cookpete.com/react-player/
Choose HLS (m3u8) source
Change volume in the native player
Custom volume range element does not change its value.

Environment

URL attempting to play: https://cookpete.com/react-player/
Browser: Safari/Chrome
Operating system: MacOS

Other Information
volumechange event has support in all browsers: https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/volumechange_event
My case: I have a custom player controls. Switching player to fullscreen, the native player controls are shown. Changing volume there and returning back from fullscreen the volume control value is wrong, because it cannot be updated.

Duplicate of https://github.com/cookpete/react-player/issues/1109

I see, but thought it is not related. I'm talking about built-in  tag functionality which is cross-browser supported. Do you really think that if some CUSTOM player does not support common functionality, the player should not support it at all?

authors: cookpete seleckis

repo: cookpete/react-player


text:
Add flvjs error handling, pass it to props onError method.

When flvjs instance emits error it is not passed to the react player instance.
Expected behavior
Error should be passed to onError handler
Steps to Reproduce
git clone https://github.com/CookPete/react-player.git
cd react-player
npm install # or yarn
npm start
open http://localhost:3000

In Custom URL write file.flv
> events.js:62 Uncaught (in promise) Error: Uncaught, unspecified "error" event. (NetworkError)
    at i.emit (events.js:62:1)
    at i.<anonymous> (flv-player.js:236:27)
    at i.emit (events.js:84:1)
    at transmuxer.js:189:27

After fix
> onError NetworkError

Published in 2.10.1

authors: cookpete mjankovskis


text:
Offer of more queues!

Hey @coolbutuseless, in case you're interested in offering more queues, my dodgr package wraps a bunch of them in a src sub-directory. Feel free to adapt, integrate, use to compare, whatever. They're mostly coded for strictly internal C/C++ usage, but easy enough to expose directly to R. They're also much faster than the collections ones, mostly because being internal they don't need the constant PROTECT/UNPROTECT calls and the likes. There's a compare_heaps() function to do benchmarking on a given network - especially intended to highlight that different queues/heaps perform differently for different tasks.

Thanks for the offer. I'm not adding anything else to priorityqueue at this stage, but will keep this in mind for when my needs change.

authors: coolbutuseless mpadge

repo: coolbutuseless/priorityqueue


text:
Set function to allows to set Logger level dynamically from the environment

Addition of an extra function to allow users to dynamically set the logs, and creating errors.go, reusable error that can be used for validating the function return.

I love the initiative, and with some tweaks, this looks look to be merged. Could you also please add some unit-tests that use this new logger-option? :)

authors: alfredosa bendiknesbo

repo: coopnorge/go-logger


text:
placeholder with no default does not force the user to answer

Describe the problem
According to the docs, default should be left empty to force the user to answer.  However, even with no default, if placeholder is set then the user is not forced to answer the prompt.
Template
# copier.yml
---
required_var:
  placeholder: foo

_message_after_copy: |
  required_var is {{ required_var }}

To Reproduce
Run copier with the copier.yml from the previous section.  When prompted for required_var, simply hit enter.
Example:
copier copy -n . dir
🎤 required_var (yaml)
   foo

Copying from template version None
    create  .

required_var is None

Logs
No response
Expected behavior
When prompted, the user should be forced to enter a value and not be able to just hit enter, which effectively sets the value to None, "", etc. depending on the type.
Screenshots/screencasts/logs
No response
Operating system
macOS
Operating system distribution and version
Sonoma 14.6.1
Copier version
copier 9.3.1
Python version
Python 3.12.4
Installation method
pip+pypi
Additional context
This behavior can be worked-around with something like this:
validator: >-
  {% if not required_var %}
  INVALID - you must enter a value
  {% endif %}

... but that is a lot of boilerplate to add.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Interactive prompting is a little tricky because at for type: str/type: yaml questions there is no clear distinction between no answer and an empty answer.
Let's assume the following copier.yml file:
str_1: ""

str_2:
  default: ""

str_3:
  type: str

All three questions are (implicit or explicit) type: str questions. When you enter no answer during interactive prompting, the answer will be an empty string because there is no way provide no answer (when you hit Enter, the answer is an empty string in all cases).
It's similar for type: yaml questions:
yaml_1: null

yaml_2:
  default: null

yaml_3:
  type: yaml

All three questions are (implicit or explicit) type: yaml questions. When you enter no answer during interactive prompting, the answer will be null because an empty string gets parsed as null by the YAML parser and there is no way to provide no answer (same as above).
So, your discovery is in fact not related to the use of placeholder with no default but rather the behavior of type: str/type: yaml questions with an implicit default value during interactive prompting.
I don't see how we could change the current behavior, but I'm all ears if you have an idea. Your proposed workaround using a validator does not precisely catch an unanswered question but constrains the answer to not be falsy, which coincidentally means it must not be "" or null.

I've done some more testing, and I see what you are saying now.  It works as I would expect for types other than yaml or str.  I guess my confusion was mainly because I assumed "force the user to answer" also meant "with a non-empty response".
I don't have a better idea other than adding a new supported key for advanced prompts such as mandatory: False or allow_empty: True.  I could see why you would be hesitant to do that though since the same could be achieved with validators.
I really liked the idea of placeholders to show example answers, but I can always hard-code examples in help where it makes sense.
Thanks

I think the MVP would be to document this behavior, and how validators can be used for this use case, so it's not surprising to users.

authors: JohnLyman Saschl sisp yajo

repo: copier-org/copier


text:
[Tracker] Event refactoring

To make things clear and organized (and mainly to avoid making a giant PR) I will make this issue to track this integration by pieces.
This is part of https://github.com/coppolaemilio/dialogic/discussions/751

The goal is to replace current event format from JSON to Godot Resource and, in a different integration, to JSON (or whatever format you like) again. This was discussed previously in https://github.com/coppolaemilio/dialogic/issues/10
Integration part

[x] https://github.com/coppolaemilio/dialogic/pull/871 This class serves as an abstract class for every event that can be executed in the timeline
[x] https://github.com/coppolaemilio/dialogic/pull/873 This class works as an event container, and the dialog node uses it to iterate over the events.
[x] Rebuild events with the new integration.

Verification part

[x] Make sure that editor uses the new event class
[x] Make sure that editor uses the new timeline class
[x] Reorganize dialogic dialog node to use the timeline and event class.

Cleanup part

[ ] Remove scripts that may be deprecated by this integration. I'll need help verifying this one.

Event and Timeline class are based on EventSystem scheme.

As far as I can tell this is basically done, even if the event class will probably see changes, Dialogic 2.0 now fully works with these resources.

authors: AnidemDex Jowan-Spooner

repo: coppolaemilio/dialogic


text:
When is the release date for Version 0.31.0?

Hello,
I'm eagerly anticipating the release of version 0.31.0 of Anchor and was wondering if there is any estimated timeline for its release?  As solana  has its stable  v2, when does anchor support it in the next anchor stabe version?

It has been ready for over 3 months now (https://github.com/coral-xyz/anchor/pull/3259), but I guess we're still waiting for an audit to publish it.

As solana has its stable v2, when does anchor support it in the next anchor stabe version?

Next version will support Solana v2 (https://github.com/coral-xyz/anchor/pull/3219). This is also mentioned in the Recommended Solana version section of the (unpublished) release notes. We'll probably change the recommended Solana version to v2.1.0 (https://github.com/coral-xyz/anchor/pull/3339) because v2.0's Rust version is quite outdated at this point.

To be honest, the speed of this release is really frustrating.

Before the audit passes, maybe we can have a 0.31.rc

authors: acheroncrypto jasl lingcoder

repo: coral-xyz/anchor


text:
🛑 Guangdianyun Consoles is down

In 8e27eb5, Guangdianyun Consoles (https://consoles.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun Consoles is back up in 2747764.

repo: corcd/charlotte


text:
🛑 Guangdianyun Consoles is down

In 2510227, Guangdianyun Consoles (https://consoles.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun Consoles is back up in f2d99d7.


text:
🛑 Guangdianyun is down

In 116671f, Guangdianyun (https://www.guangdianyun.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guangdianyun is back up in 6cdbf1f.


text:
Documentation: add note about cluster startup delay

/cc @philips @robszumski

As one of the users, I feel this very helpful.
In early days, I had been running around checking my /etc/hosts and AWS console, running processes on EC2 instances, until I realize it takes some time after cfn stack got created 😄

LGTM

authors: aaronlevy mumoshu robszumski

repo: coreos/coreos-kubernetes


text:
How can I associate the key with the client_id？

How can I associate the key with the client_id. A client_id generates a fixed key. Return the public key to the client. However, I discovered that the public key will change periodically. Is it possible to store client_id and public and private keys together in the database?

Keys aren't associated with clients they're global to dex. Keys rotate occasionally in accordance with http://openid.net/specs/openid-connect-core-1_0.html#RotateSigKeys

authors: Victoryship ericchiang

repo: coreos/dex


text:
raft: add RawNode test case for #6866

Hi,
This PR adds the test case in #6866 for RawNode.

Current coverage is 63.82% (diff: 100%)

No coverage report found for master at f99c76c.

Powered by Codecov. Last update f99c76c...aaa739a

I cannot open the link for details of jenkins-ci build failure. I don't know what is wrong there.

lgtm. The CI failure is irrelevant.

repo: coreos/etcd


text:
etcdctl/ctlv3/command: enable gRPC WARNING logs by default

Fixes https://github.com/coreos/etcd/issues/9619
Before
$ ETCDCTL_API=3 etcdctl --cert tls/etcd-client.crt --key tls/etcd-client.key get keys --endpoints=https://etcd-1.local:12379 get keys
Error: context deadline exceeded

After
$ ETCDCTL_API=3 etcdctl --cert tls/etcd-client.crt --key tls/etcd-client.key get keys --endpoints=https://etcd-1.local:12379 get keys
WARNING: 2018/04/24 15:34:04 Failed to dial etcd-1.local:12379: connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"; please retry.
Error: context deadline exceeded

Way down in the depths of the gRPC package, their global logger swallows TLS errors unless you enable at least WARNING errors.
https://github.com/coreos/etcd/blob/f1b3b327459810465c712beb5d7859e7198d0dd8/vendor/google.golang.org/grpc/clientconn.go#L696
By default, etcdctl silences these log messages, and it seems like others have hit this with things other than TLS configuration:
https://github.com/coreos/etcd/issues/9610
https://github.com/coreos/etcd/issues/8793
INFO would definitely be too high by default, but if we hit a warning or an error, this seems worth displaying to the user.
cc @gyuho @xiang90

lgtm

What's jenkins-ppc64le? Can we ignore it?

@ericchiang Yeah, it has been broken for awhile (being tracked in a separate issue).

Wow this is spammy :(
$ etcdctl user list
WARNING: 2018/04/25 13:06:05 Failed to dial etcd-2.local:22379: grpc: the connection is closing; please retry.
WARNING: 2018/04/25 13:06:05 Failed to dial etcd-1.local:12379: grpc: the connection is closing; please retry.
$ etcdctl user list
WARNING: 2018/04/25 13:06:05 Failed to dial etcd-1.local:12379: grpc: the connection is closing; please retry.
$ etcdctl user list
WARNING: 2018/04/25 13:06:06 Failed to dial etcd-3.local:32379: grpc: the connection is closing; please retry.
WARNING: 2018/04/25 13:06:06 Failed to dial etcd-2.local:22379: grpc: the connection is closing; please retry.

@ericchiang Now I remember why WARNING was disabled. Those logs are from gRPC internal balancer, and happens when etcd balancer closes two other endpoints after pinning the first one.

Opened an issue on gRPC here https://github.com/grpc/grpc-go/issues/2025

authors: ericchiang gyuho xiang90


text:
flanneld run with -listen option can not be run as a service

Hi,
When running flanneld with -listen option, it does not notify systemd of its readiness. Without -listen option and without multinetwork, initAndRun function is called which calls daemon.SdNotify("READY=1"). When -listen option set, remote.RunServer function is run and there is not execution path leading to daemon.SdNotify("READY=1").
Is it intended or is it bug/missing notification? Running with 0.5.3.
Thanks
Jan

I guess it is a missing feature that should be added. However in server mode, flannel does support systemd's socket activation. This way you can achieve the same "non-waiting" startup as with with notify. Just create a .socket file and launch flannel with --listen=fd://

Thanks Eugene. I am not familiar with creating the socket file. Can you help enlighten me how to do that? Or maybe what would be the correct place to put daemon.SdNotify("READY=1")? From my point of view I see it as a one liner. What about https://github.com/coreos/flannel/blob/master/remote/server.go#L278 ?

@ingvagabund Sure, feel free to submit a PR.
Also, here's some info on socket activation:
http://0pointer.de/blog/projects/socket-activation.html
http://www.freedesktop.org/software/systemd/man/systemd.socket.html

Thanks for the links. Here is the PR https://github.com/coreos/flannel/pull/326.

One minor glitch. When -listen is not specified, flanneld creates /run/flannel directory as a consequence of creating /run/flannel/subnet.env file. If -listen is not specified, it does not created /run/flannel. Running mk-docker-opts.sh with -d /run/flannel/docker fails is the directory does not exists. Thus by default, /run/docker_opts.env is used. This is service file issue related, not the flannel itself.

@eyakubovich, I suppose client-server feature is still not stable, right?

@ingvagabund When flannel is running with -listen, it should not be used with mk-docker-opts.sh. You would need to write a separate service file for the server mode.

Fixed by #326

authors: eyakubovich ingvagabund

repo: coreos/flannel


text:
Semantic versioning

Right now the version for jetcd is hard coded at 0.1.0-SNAPSHOT. All of the code changes are getting lumped under that version. When I upgrade to the latest code, there are build breakages because classes have been renamed and signatures have changed.
For people like me who would like to use jetcd in my projects it's difficult to experiment with because upgrading means that I am potentially hit by breaking changes. Implementing Semver would help early adopters like myself use jetcd with less fear that an upgrade is going to break my build.

It is too early to even use Semver. We will start using semver when we feel it is alpha quality software at least...

@nbrauer sorry for all the changes going on right. we are trying hard to get the alpha version out; so a lot changes are being made to make sure that the interfaces and implementations are good.

@nbrauer push first release to maven central https://search.maven.org/#search|ga|1|coreos

authors: fanminshi nbrauer xiang90

repo: coreos/jetcd


text:
Add simple usage example

Fixes #53

LGTM

authors: Quentin-M jzelinskie

repo: coreos/jwtproxy


text:
Grafana roadmap

In reference to #115
The current behavior of grafana-watcher relies on a ConfigMap as the master dashboard repository.
When you design a new dashboard in Grafana you need to manually export it and merge it into the ConfigMap manifest, which is quite tedious to do. Is there a plan to automate this process ?
In addition, while going through this process, I noticed that we were using the Grafana /api/dashboards/import API, which seems to be undocumented in the Grafana API reference. Why aren't we using the documented API?

The [POST] /api/dashboards/db endpoint was also undocumented at the time of implementing the grafana-watcher :slightly_smiling_face: . As far as I can tell they have the exact same functionality, so it should just be replaceable.

Is there a plan to automate this process ?

Glad you ask, because it already is. It is part of kube-prometheus and the scripts to do that can be found in hack/scripts. You are particularly looking for the generate-dashboards-configmap.sh script executed from the generate-manifests.sh script.

Now using the documented API and he workflow is already automated :)

It turns out, that the /import endpoint actually slightly differs, and does not allow templating, this didn't show in my tests, but in more complex dashboards it does appear. Will have to revert to the /import endpoint again.

authors: brancz nirdothan

repo: coreos/prometheus-operator


text:
helm:* remove all helm

Remove all helm now that Prometheus Operator is in the official helm chart repo.
cc @metalmatze @ant31 @brancz

Need to scope this down to the one helm chart that was moved


text:
apply: symlink in systemd files

Fixes #25

It looks fine as a first step. It would probably need heavy changes once we settle on https://github.com/coreos/torcx/issues/29. Mind rebasing on current master to make travis happy?

Rebased!

authors: lucab squeed

repo: coreos/torcx


text:
Files: Open images in shared folder

When accessing a publicly shared folder via link and trying to open an image inside, the following FP is produced:
ModSecurity: Warning. Match of "within %{tx.allowed_request_content_type}" against "TX:content_type" required. [file "/etc/modsecurity/crs/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "1012"] [id "920420"] [msg "Request content type is not allowed by policy"] [data "|text/plain|"] [severity "CRITICAL"] [ver "OWASP_CRS/4.0.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/255/153"] [tag "PCI/12.1"] [uri "/public.php/webdav/img.jpg"].
I was able to fix it with the following exclusion rule, without guarantee of safety:
# File manager: Public share
# Fix FP when opening photo
# Allow the data type 'text/plain'
# Since the content is actually XML, we switch on the XML parser
SecRule REQUEST_FILENAME "@beginsWith /public.php/webdav/" \
    "id:9508954,\
    phase:1,\
    pass,\
    t:none,\
    nolog,\
    ver:'nextcloud-rule-exclusions-plugin/1.1.0',\
    chain"
    SecRule REQUEST_HEADERS:Content-Type "@beginsWith text/plain" \
        "t:none,\
        ctl:requestBodyProcessor=XML,\
        setvar:'tx.allowed_request_content_type=%{tx.allowed_request_content_type} |text/plain|'"

Thanks for sharing @mhastu. We'll see where we can integrate this.

@mhastu I've taken a look and I can confirm this is an issue on 27.1.0, and that rule should be perfectly safe, CRS blocks text/plain content mainly because ModSecurity can't parse it(since it doesn't know what the content is), you've enabled the appropriate parser (in this case xml parser) for text/plain so it should be perfectly fine. I opened a PR here #68

authors: EsadCetiner mhastu theseion


text:
Checkbox checked state instead of event.

How can I get the checked state from checkbox instead of Event?
<CInputCheckbox :label="$t('front.test')" value="1" name="test" :size="size" v-model="test" ></CInputCheckbox>

test in this case always gets the Event I just want it to have true/false instead?

Instead of v-model use :checked.sync (both v-model and .sync are only shortcut syntax for binding value and receiving event, we use .sync version)

authors: buzzclue woothu

repo: coreui/coreui-vue


text:
Rwang.fixrate

Change default to .txt since .txt won't be rate limited.

@Rexwang8 you need to resolve some merge conflicts before we can merge this.

repo: coreweave/dataset-downloader


text:
Update sbt-scalajs, scalajs-compiler, ... to 1.3.1

Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler
org.scala-js:scalajs-library
org.scala-js:scalajs-test-bridge

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

labels: library-update, semver-patch

@mergifyio update

authors: fdietze scala-steward

repo: cornerman/colibri


text:
Translation Delivery

Translation Delivery

This pull request is for translation delivery. Please review and approve them.

repo: corona-warn-app/cwa-app-android


text:
"Data is being downloaded.." is shown every time you navigate back to the homescreen

Description
Prevent package downloading if trace warning metadata is empty. No need to try discovering anything.
Link to Jira
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-6608

Approvals were given in: https://github.com/corona-warn-app/cwa-app-ios/pull/2527

authors: freshking marcussc

repo: corona-warn-app/cwa-app-ios


text:
Feature/10313 port request key submission

Description
Porting the submission request to new http service.
Link to Jira
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-10313

I think you missed to remove URLRequest.keySubmissionRequest() and the submissionURL in the HTTPClient+Configuration?

Good catch. I removed it now.


text:
Certificate issue through pharmacies

Where to find the issue
For instance:
https://www.coronawarn.app/en/faq/#vac_cert_invalid
Describe the issue
There have been some postings in other CWA repositories referring to security issues with pharmacies issuing EU Digital COVID Certificates and that pharmacies have stopped issuing certificates.
In the newsroom of ABDA - Bundesvereinigung Deutscher Apothekerverbände e. V. it first said on
July 22, 2021
https://www.abda.de/aktuelles-und-presse/newsroom/detail/statement-zur-ausstellung-von-impfzertifikaten/
that issuing of certificates had been temporarily halted
then on
July 23, 2021
https://www.abda.de/aktuelles-und-presse/newsroom/detail/impfzertifikate-wieder-schrittweiser-zugriff-auf-dav-portal/

Der Deutsche Apothekerverband (DAV) und das Bundesgesundheitsministerium erklären in einem gemeinsamen Statement (23.07.21), wie es mit der Ausstellung von Impfzertifikaten weitergeht:
"Aufgrund eines Hinweises auf eine potentielle Schwachstelle beim Zugang zum Webportal des Deutschen Apothekerverbands (DAV) wurde die Ausstellung von Impfzertifikaten über dieses Webportal vorübergehend deaktiviert. Potentiell betroffen sind nur die wenigen hundert Apotheken, die nicht Mitglied des DAV sind. Alle erteilten Zugänge werden bereits überprüft und verifiziert. Nach aktuellem Kenntnisstand ist es zu keinem Betrug bei der Erstellung von Impfzertifikaten gekommen. Ein solcher wäre im Übrigen eine Straftat. Alle Apotheken, die dies wünschen, erhalten in der nächsten Woche schrittweise wieder Zugriff auf das DAV-Portal, so dass sie auch wieder Impfzertifikate ausstellen können. DAV, IBM, gematik und BMG arbeiten zudem gemeinsam daran, die Sicherheit bei der Ausstellung von Impfzertifikaten durch eine Einbindung dieses Prozesses in die sichere Telematikinfrastruktur insgesamt noch weiter zu erhöhen."

Suggested change
It looks like no change is currently necessary to the information in the FAQs. It would be good however to monitor the situation with the pharmacies.

My nearest pharmacy has a notice in the window (afternoon of Jul 27, 2021):

Covid Impf-Pass:
Impfportal
derzeit
deutschlandweit
geschlossen
(wegen einer Daten-Sicherheitslücke)

ABDA (Bundesvereinigung Deutscher Apothekerverbände e. V.) reports they are beginning to resolve the issue:
https://www.abda.de/aktuelles-und-presse/pressemitteilungen/detail/digitale-impfzertifikate-schrittweise-wieder-in-apotheken-erhaeltlich/
Any further status communication should be coming from them, therefore closing this issue.

https://www.abda.de/aktuelles-und-presse/newsroom/ is a good place to follow further announcements on the subject of certificate issue through pharmacies.

repo: corona-warn-app/cwa-website


text:
[ios]Remove permissions

Hello,Because the camera, microphone, and positioning are not used in my game, I need to remove the permissions related to these.But I uploaded the application to the ios platform for review, it needs the following related descriptions.
NSPhotoLibraryUsageDescription
NSMicrophoneUsageDescription
NSCameraUsageDescription
NSLocationWhenInUseUsageDescription

I want to know whether solar is useful for these content, and whether there is a way to remove the relevant content.

Did you all got rejected? Can you provide an email of rejection with exact working please. This is not common and usually it works fine.

Dear Developer,
We identified one or more issues with a recent delivery for your app, "**" 3.5.10071457 (2112281804). Please correct the following issues, then upload again.
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSPhotoLibraryUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSMicrophoneUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).
Though you are not required to fix the following issues, we wanted to make you aware of them:
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSLocationWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).
Best regards,
The App Store Team
Contact Us | App Store Connect
One Apple Park Way, Cupertino, CA 95014 Privacy Policy | Terms of Service

We had the same issue with one of our apps a year ago. Although we did not use camera, location, microphone and photo library, the app got rejected with the same message PaoUNetWork mentioned. We couldn't find any solution to this, so we ended up adding the purpose strings in Info.plist although these permissions are not actually needed. There must be a reason behind this, any ideas?

Please see #324 for explanation

authors: PaoUNetWork Shchvova elpida-v

repo: coronalabs/corona


text:
Patient centric app for CARE

Context:
Currently, Care is only used by nurses, doctors, or generally hospital staff where the patient has direct access to the application.
Idea:
Build an app where the patient can access their records in care.
Consider using ABDM for this.
Needs further discussions before getting started

React Native?

Hi @balaji-sivasakthi, these are just ideas being filed, the stack and further details have to be discussed with the team. If you are looking for issues, please feel free to checkout:

https://github.com/coronasafe/care_fe
https://github.com/coronasafe/care
https://github.com/coronasafe/leaderboard
https://github.com/coronasafe/ayushma
https://github.com/coronasafe/ayushma_fe
https://github.com/coronasafe/teleicu_middleware

@khavinshankar
Practically speaking this would be a rewrite of coronasafe/citizen as an ABDM enabled Next App on Typescript

authors: balaji-sivasakthi gigincg khavinshankar

repo: coronasafe/docs


text:
Time range for leaderboard

Deploy Monthly leaderboard.
Option to add custom time range is also desirable

Being worked on #52

authors: aparnacoronasafe rithviknishad

repo: coronasafe/leaderboard


text:
Adding a custom variable creating error during evaluation

Code
import { ComputeEngine } from "@cortex-js/compute-engine";
let exp = computingEngine.parse('speed+10');
computingEngine.set({ speed : 10 });
console.log(exp?.N().valueOf());  // cannot be evaluated

I am using mathlive virtual keyboard there I have created a custom button named as speed so when from that keyboard I click on speed then add then 10 it must give the output of 20 as I am using computing engine for setting the value of speed to 10 then evaluating the value
showing this console.log
["Add",["Multiply","7.389056098930650227230427460575007813180315570551847324087127822522573796079057763384312485079121792","d","p","s"],10]
Expected Output
20

You need to wrap the multi-character identifier: \mathrm{speed}+10

I have added custom variables using the method you showed but when i am pressing delete option it is deleting character by character but i need that it must delete the complete character at once means delete  \mathrm{speed}  when i press backspace

To do this, define a macro and set captureSelection to true. See https://cortexjs.io/mathlive/guides/macros/

repo: cortex-js/compute-engine


text:
sql: unknown driver "goracle" (forgotten import?)

In version 0.6.8, when I connect to an oracle instance, the log outputs an error message. How do I fix this：
I1115 19:26:46.802025       1 promhttp.go:39] Error gathering metrics: 4 error(s) occurred:

[from Gatherer 1] [job="oracle", target="orcl-192.168.0.1:1521/orcl"]
sql: unknown driver "goracle" (forgotten import?)

I recompiled v0.6.8 and made a docker image as follows:
registry.cn-hangzhou.aliyuncs.com/hd2020/ka:database_exporter0.6.8

测试支持:mysql8,oracle11,pg15,sqlserver2019


text:
SigningStargateClient.signAndBroadcast when a node has transaction indexing disabled

apparently most public RPCs turn of transaction indexing. it's on by default in config.toml (per node setting)
I was using the https://cosmos.directory/ proxy (which proxies available chain-registry endpoints)
If you sign and broadcast
    const response = await stargateClient.signAndBroadcast(address, [msg], fee);

It does successfully broadcast a TX, which I could verify via mintscan, but the response was this error message:
{"code":-32603,"message":"Internal error","data":"transaction indexing is disabled"}

@webmaster128,  @czarcas7ic mentioned there is a way to get a successful response even if transaction indexing is disabled. I'm wondering if we should look into using this solution so regardless if nodes have this enabled or disabled, we can avoid the errors.
It may involve a new function that is a variant of signAndBroadcast so it doesn't fail. @czarcas7ic can you explain the solution briefly so we can figure out solution on the cosmjs end?

Interesting. So the thing is we want DeliverTx responses. The submit and wait for block broadcast mode is deprecated. So what we currently do is submit and wait for CheckTx only, then search for the transaction. If there are better ways to implement that, I'm happy for suggestions.

Ah, yeah my recommendation was to utilize submit and wait for block broadcast mode, this way if the response returned a code 0 you could be confident it was included in a block and do not need to rely on tx hashes. I was unaware this was deprecated though. Once there is a way to easily prune tx indexer this wont be an issue, but until then it will be hard to find a public RPC that also maintains a reliable tx index since the tx index bloats the size and does not prune with the rest of the db

repo: cosmos/cosmjs


text:
Allow toggling of SDK logs in e2e's

Summary
Similar to how you can change the cometbft logs from info to debug, I'd like to be able to switch sdk logs from info to debug

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Slightly looking into it, sdk config doesn't have a log level option to toggle like comet does, maybe we should bring it up to em.

I think you can control the log level with cli flags, but would be nice if it was in the config as well

authors: DimitrisJim colin-axner

repo: cosmos/ibc-go


text:
test: refactor used expected errors

Description

closes: #6214

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

Tests

Enhanced the TestOnChanOpenInit to improve error handling by using specific error types instead of boolean values, refining test validation processes.

Thanks, @hoank101. This PR would partially address #6214. Do you plan to refactor the rest of the tests in this file in follow-up PRs?

thank you for feedback, I updated


text:
Supply app version to contract keeper

Description

closes: #6977
This PR adds the underlying application version to the callback data and propagates it to the contract keeper interface fns.
Added the backport label since it seems like a valuable feature, happy to remove before merging (and update docs) if there's a good reason not to.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

No backport necessary, this should be included in the callbacks release branch (when created)

Thanks @chatton for an elegant solution here!

authors: chatton colin-axner


text:
[POC] Cian & Nikolas Retreat Week

Description

Details can be discussed in the engineering call
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

This PR updates the existing eureka logic to perform a conversion on a Packet to internally use the PacketV2 commitment structure.
This and an alternate approach using a different message server were explored during the retreat week here #7302

Closing in favour of https://github.com/cosmos/ibc-go/pull/7302


text:
Critical dependency: the request of a dependency is an expression

Thank you for filing an issue!

Version

Commit 89705fd7bd667aee5be5cbfbe1ed81228e2c806c
Description

Webpack still shows some warnings while building:

unable to reproduce this bug after running:
git checkout 89705fd
rm -r node_modules
yarn
COSMOS_NODE=localhost yarn testnet

@mappum can you reproduce?

I confirm this error does not longer appear.

Happened again when building inside docker

Confirmed this happens inside docker when building the app:

But I'm wondering, why is this warning an issue? (Just because it's ugly to look at?) It's not actually causing any problems, and it's coming from the code in a dependency, not our own code (https://github.com/lukechilds/keyv/blob/master/src/index.js#L18).
Would it be acceptable to just hide the warning somehow?

this is on the repo's issue tracker. they recommend closing your eyes when the warning appears:
https://github.com/lukechilds/keyv/issues/45

So the proposal is to ignore the issue? (I am fine with it)

closing

authors: faboweb mappum okwme

repo: cosmos/voyager


text:
'image has no src or srcset attribute (line 0)' for categories

Checklist

[x] I have read the tutorials and know the correct effect of the functional design.
[x] There are no similar question on existing issues (including closed ones).
[x] I searched the Internet for related problems, but still couldn't solve it.
[x] My question is based on the latest code of master branch.

Description

I've recently rebased your repo, ran the blog locally, but on GitHub CI/CD I get:
Run bash tools/test.sh
Running ["ScriptCheck", "LinkCheck", "ImageCheck", "HtmlCheck"] on ["_site"] on *.html...

- _site/blog/404.html
Ran on 45 files!
  *  image has no src or srcset attribute (line 0)
- _site/blog/categories/blogging/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/categories/dc/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/categories/dmv/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/categories/jekyll/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/categories/life/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/categories/vulnhub/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/dc1-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/dc3-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/dc4-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/dmv1-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/how-to-create-your-own-blog-using-jekyll-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/is-this-blog-dead-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/posts/why-you-should-start-your-own-blog-en/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tabs/about/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tabs/archives/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tabs/categories/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tabs/tags/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/beginner/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/blog/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/cms/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/crontabs/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/free/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/growth/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/hydra/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/jekyll/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/john-the-ripper/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/joomla/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/kernel-exploit/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/nginx/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/plans/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/python-requests/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/reverse-shell/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/sql-injection/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/sudoers/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/tee/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/waf-bypassing/index.html
  *  image has no src or srcset attribute (line 0)
- _site/blog/tags/wfuzz/index.html
  *  image has no src or srcset attribute (line 0)

HTML-Proofer found 39 failures!

Error: Process completed with exit code 1.

I have to add, that I'm setting it as a project site.
I've also had issues with setting up an avatar. I've set attribute
avatar: assets/img/avatar.jpg

Which is where my avatar is placed. Though again, on GitHub actions this image cannot be found.
EDIT: I see that locally the tags are placed in _site/tags directory, when on CI/CD it's  trying to see these tags in _site/blog/tags
But I also see that the problem is still the same even without baseUrl.
 - _site/tags/wfuzz/index.html
  *  image has no src or srcset attribute (line 0)

Maybe you can consider naming a specific issue title: because at first glance, it looks like spam.
This problem is caused by incorrect generation of the avatar url when site.baseurl exists.

Maybe you can consider naming a specific issue title: because at first glance, it looks like spam.
This problem is caused by incorrect generation of the avatar url when site.baseurl exists.

Thank you cotes, it seems you're in good mood as always ;_;
For me, it seems logical to name an issue by an error message, as in the end, this is what a user ends up searching

Thank you cotes, it seems you're in good mood as always ;_;
For me, it seems logical to name an issue by an error message, as in the end, this is what a user ends up searching


text:
🛑 Mainnet tez.ie is down

In 3862bdd, Mainnet tez.ie (https://api.tez.ie/rpc/mainnet/chains/main/blocks/head) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mainnet tez.ie is back up in 0381f09.

repo: cotezos/teznodes


text:
LiteServ app for Java

It would be great to have a command lite utility app to start the Listener. Flags could be passed to perform different tasks (https://github.com/couchbase/couchbase-lite-ios/blob/master/Listener/LiteServ.m#L165-L181).

Note to Self:
ATTN: @sethrosetter
Implementing LiteServ for Java and operating mobile-testkit on all three platforms (Windows, Linux and OSX) could find issue like sqlcipher.dll missing on windows. Need higher priority for this task.

@hideki @michaelkwok We need to add this to CI as part of closedown of this task.

authors: hideki jamiltz sethrosetter

repo: couchbase/couchbase-lite-java-core


text:
Best upgrade strategy for Couchbse+XDCR+ES

Hi, I have a Couchbase v2.2 community edition cluster using XDCR to sync data to an Elasticsearch v1.0.1 cluster. I am wondering if I can do online upgrade to Couchbase v3.x by swap rebalance method while making less impact to the Elasticsearch cluster as possible. It seems upgrading v2.2 to v3 is complicated when XDCR is in place. Is there any step-by-step guide for this? Or does anyone have experience on this?
BTW, are the version numbers of Couchbase in the 'Version Compatibility' table in READEME.md ones of Enterprise Edition? Or the version numbers are compatible between Enterprise and Community edition?

The version numbers are the same for community and enterprise versions of Couchbase.
Regarding the upgarde process of Couchbase itself, it might be best to ask on the Couchbase forums. If you can disable replication while you're doing the upgrade, that would probably be best. If not, it should still work fine through the swap rebalances.

authors: Branor nextofsearch


text:
tabbed formatting is currently inconsistent

I noticed you're using tabs instead of spaces.  Currently, that's leading to pretty jagged rows of code as you can see here:

Generally I prefer spaces instead of tabs, but it's up to you.  If you're using tabs, it'd be good to line up the columns correctly.

Should be resolved in the latest commit. Please tell me if the change has worked for you. One API has also been updated, so pull for the new changes.

authors: ingenthr pranavmayuram

repo: couchbaselabs/touchbase


text:
Update sbt-ci-release to 1.3.1

Updates com.geirsson:sbt-ci-release from 1.2.6 to 1.3.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.geirsson", artifactId = "sbt-ci-release" } ]

labels: semver-minor

Handled from https://github.com/coursier/coursier/pull/1353.

authors: alexarchambault scala-steward

repo: coursier/coursier


text:
feat(collapsible): disabled

add disabled state
add new props to set a custom icon
Proposed Changes
Collapsible

add disabled state
add props to override the default collapsible button

Potential Breaking Changes
none
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Code is nice, :wave:  me once you have your build.

Same - looks good but there's conflicts preventing the demo. Can check and approve once fixed 😄

authors: dmgauthier j-mcgregor pochretien

repo: coveo/react-vapor


text:
Saml Client for Ping ID

We are trying to use this client for Ping ID. How can we use it for Ping ID? If it already works, could you please share some examples.
Thank you

I don't have a sample handy, but I know it's been used with Ping already, yes.

authors: abhishekupadhyaya malaporte

repo: coveo/saml-client


text:
ci: getting go version from go.mod

The actions/setup-go action can extract the go version from go.mod. This will ensure consistency of the go version.

@jonapich My inattention! Fixed

repo: coveooss/gotemplate


text:
Password recovery

Password Recovery
Big PR for a tricky feature. The goal here was to make it so that when a user requests a password reset (by clicking forgot password), they're sent an email with a link which they click, which automatically brings them to our bespoke password reset interface.
Backend
Added a new endpoint ("callable") named initiatePasswordRecovery. This endpoint consumes an email address, updates the associated user document to have a field called passwordResetRequested set to true, and sends a password recovery email with an email sign-in link.
Frontend
The bulk of the complexity in this feature comes in the frontend state management. The naive implementation of this feature is to pop up the ChangePasswordModal for any user that's signed in and has props.store.data.user.passwordResetRequested === true. However the problem with this implementation is that it opens the legitimate user up to getting locked out of their account, by a malicious actor who simply incessantly requests password resets with the legitimate user's email address. By necessity, initiatePasswordRecovery can be called by unauthenticated users.
To account for this, we instead check for that both props.store.data.user.passwordResetRequested === true and that the user signed in via the email link before popping up the ChangePasswordModal. This ensures that the user actually actively clicked the link in the password recovery email, which we're taking to mean that they indeed do want a password reset. If the password reset was a mistake, or requested by another person, they can simply delete the email and continue signing in to the app as normal.
See trySignInWithEmailLink in Login.js as a jumping off point for how we handle this.
Other substantial changes are in ChangePasswordModal.js and the store. I moved all the direct firebase calls from ChangePasswordModal.js into functions in the store (we should stick to this paradigm as much as possible in general). I also eliminated some of the complexity associated with error handling -- now, if we encounter a Firebase error we just ask the user to retry . This eliminates the difficulty of testing states associated with specific errors (like 'auth/requires-recent-login'). It additionally makes it much simpler to use this same ChangePasswordModal.js component for all of the different password changes (firstTimeUser/recovery/change), without having to design and maintain tricky component state logic.
closes https://github.com/covid19risk/permission-portal/issues/243

Walking through the workflow at a high level makes sense and no red flags jump out at me.
I did, however, attempt to reset my password within the dev Firebase and got a 'insufficient permissions' error message in the console. See video here showing this. Any ideas why this would happen to a typical user @ibeckermayer ? (the user is my covidwatch email address). The error message points to the function onSnapshot defined in model.js.
Coming up to speed a bit here having not been too involved in email password set up workflow.

Yes, that's https://github.com/covid19risk/permission-portal/issues/227.


text:
Remove date from dataset name

We should remove the date from the sample name and append it automatically from the submit script if it's needed.

I tend to disagree with this one... I prefer to include the date of the release of the json file instead of the date of the submission of the jobs ?

authors: OlivierBondu blinkseb


text:
feat: [DRAFT] OpenAI-compatible assistant API

Please describe the purpose of this pull request.
This allows users to interact with MemGPT agents in the same way as OpenAI's assistants API .
How to test
TODO
Is your PR over 500 lines of code?
No
Todos:

[ ] Assistants API (creating a preset)
[ ] Threads API (creating an agent instantiation)
[ ] Messages API
[ ] Runs

[ ] Allow buffering of multiple user messages before executing .step()

@sarahwooders Would be happy to help with this one, I think this is a great addition. After paying 120$ dollars for Assistants API calls.

@sarahwooders Would be happy to help with this one, I think this is a great addition. After paying 120$ dollars for Assistants API calls.

That's great to hear! I should be close to wrapping this up in the next 1-2 days but would be great to get your help with testing it out :)

authors: Maximilian-Winter sarahwooders

repo: cpacker/MemGPT


text:
Added sensitive information bit

I added a few phrases about posting sensitive information.
I'm also trying the PR from gitkraken, just to spice it up

Summary by Sourcery
Update the contributing documentation to include guidelines on handling sensitive information, emphasizing the importance of not including sensitive data directly in the public guide.
Documentation:

Add guidelines to the contributing documentation about handling sensitive information, advising contributors to avoid including sensitive data directly in the guide and suggesting alternatives.

LGTM, feel free to merge

authors: fcerpe marcobarilari


text:
Fix issue with Microsoft's checked iterators

After grabbing the latest 0.13-release to sync up with Boost 1.67, I ran into a big issue in my debug build.
I constantly hit an assert in the checked iterators so had to track it down and fix it.
The current code casts iterators from the partial_parsed buffer (which can be quite large) to iterators for the small temporary std::array buffer. MS implemented their checked iterators using the statically-declared size of the array (which is much smaller than partial_parsed) so they hit all the time.
Also, that static_cast likely only worked because compilers likely use char* as the iterator type for both containers, but I don't think assuming that is portable.
I changed chunk_encoding_parser so that its operator() and update_chunk_size can take any compatible iterator_range type as arguments.

LGTM -- thanks @LoopinFool!

authors: LoopinFool deanberris

repo: cpp-netlib/cpp-netlib


text:
Resolve service using internal (short) name?

Given a svc with the following FQDN:
foo.default.svc.cluster.local
is there a configuration option that will allow me to resolve using the "short" name:
foo.default

@austinnichols101 not currently. any concerns over conflicting with public domains (eg app.dev could be a legitimate site)?
can try adding as as an optional feature though, lmk.
Sent from my iPhone

On Nov 15, 2018, at 7:57 AM, M notifications@github.com wrote:
Given a svc with the following FQDN:
foo.default.svc.cluster.local
is there a configuration option that will allow me to resolve using the "short" name:
foo.default
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I can work around it by specifying a dns search domain on the local host.  A name conflict with a public domain is possible, but is typically the exception and not the rule.
As background, I have been using telepresence with vpn-tcp mode which allows this type of lookup.  This allows me to use the same naming that the pods use within the cluster.

@austinnichols101 do you typically configure it to deal with shortest names as well (just the svc name, eg foo)?

@cppforlife no, typically I use the svc name + namespace.

all righty, i ll give it a try next week.

@austinnichols101 you can also setup bespoke routes via VirtualService resource https://starkandwayne.com/blog/adding-a-custom-domain-for-knative-services/

authors: austinnichols101 cppforlife drnic

repo: cppforlife/kwt


text:
apt-get package does not work with CMake find_package on Ubuntu

I'm trying to create a new Docker image for our CI environment.
Rather than compiling CppUTest every time in our pipeline, I want to add a precompiled version of it.
Our Docker image is based on ubuntu:jammy which has an apt-get package available for CppUTest.
Unfortunately it seems that there's something wrong with the CMake modules it provides for find_package support, as it provides the following error during the CMake configuration phase:
#6 40.21 -- The CXX compiler identification is GNU 11.2.0
#6 40.23 -- Detecting CXX compiler ABI info
#6 40.32 -- Detecting CXX compiler ABI info - done
#6 40.33 -- Check for working CXX compiler: /usr/bin/c++ - skipped
#6 40.33 -- Detecting CXX compile features
#6 40.34 -- Detecting CXX compile features - done
#6 40.34 -- Configuring incomplete, errors occurred!
#6 40.34 See also "/tmp/build/CMakeFiles/CMakeOutput.log".
#6 40.35 CMake Error at /usr/lib/x86_64-linux-gnu/CppUTest/cmake/CppUTestConfig.cmake:11 (message):
#6 40.35   File or directory /usr/lib/include referenced by variable
#6 40.35   CppUTest_INCLUDE_DIRS does not exist !
#6 40.35 Call Stack (most recent call first):
#6 40.35   /usr/lib/x86_64-linux-gnu/CppUTest/cmake/CppUTestConfig.cmake:27 (set_and_check)
#6 40.35   CMakeLists.txt:7 (find_package)

In order to reproduce it, you can grab the Dockerfile and CMakeLists.txt from this Gist and run docker build -t cpputest . in the same directory.

Did a test where I build my own CppUTest deb package using CPack.
This package does seem to work, so I guess it has something to do with how the package is created.
FROM ubuntu:jammy
ENV CMAKE_MAKE_PROGRAM=ninja
ENV CMAKE_GENERATOR=Ninja
RUN apt-get update && \
   apt-get install --no-install-recommends -y git cmake ninja-build gcc g++ ca-certificates && \
   apt-get clean autoclean && \
   apt-get autoremove --yes && \
   rm -rf /var/lib/apt/lists/* && \
   rm -rf /var/cache/apt/archives && \
   rm -rf /usr/share/doc/ && \
   rm -rf /usr/share/man/ && \
   rm -rf /usr/share/locale/ \
   gcc --version && \
   cmake --version && \
   ninja --version
RUN git clone https://github.com/cpputest/cpputest.git /tmp/cpputest/ && \
   cd /tmp/cpputest/ && \
   echo "include(CPack)" >> /tmp/cpputest/CMakeLists.txt && \
   cmake -S /tmp/cpputest/ -B /tmp/build/ -DCPACK_GENERATOR=DEB -DCPACK_DEBIAN_PACKAGE_MAINTAINER="itavero" && \
   cmake --build /tmp/build/ --target package

FROM ubuntu:jammy
COPY CMakeLists.txt /testproject/
COPY bla.cpp /testproject/
COPY --from=0 /tmp/build/*.deb /tmp/
ENV CMAKE_MAKE_PROGRAM=ninja
ENV CMAKE_GENERATOR=Ninja
RUN apt-get update && \
   apt-get install --no-install-recommends -y nano git cmake ninja-build gcc g++ ca-certificates && \
   apt-get clean autoclean && \
   apt-get autoremove --yes && \
   dpkg -i /tmp/CppUTest*.deb && \
   rm -rf /var/lib/apt/lists/* && \
   rm -rf /var/cache/apt/archives && \
   rm -rf /usr/share/doc/ && \
   rm -rf /usr/share/man/ && \
   rm -rf /usr/share/locale/ \
   gcc --version && \
   cmake --version && \
   ninja --version && \
   ls -hal /testproject/ && \
   cmake -S /testproject -B /tmp/build

I recommend submitting an issue against the Ubuntu package: https://launchpad.net/ubuntu/+source/cpputest/+bugs.

I recommend submitting an issue against the Ubuntu package: https://launchpad.net/ubuntu/+source/cpputest/+bugs.

Thanks for the suggestion. I've also created a bug report on Launchpad

@basvodde are we involved in packaging for Ubuntu at all? If not, can we close this?

Let me try to check this today or this week. I'll need to check this as I remember somewhat had changed.

I think this is the same as #1563 that I opened a while back.

authors: Arrowbox basvodde itavero thetic

repo: cpputest/cpputest


text:
Update pygame example

Hi!
I updated the pygame example to better match ModernGL 5.
I somehow had to move to GL ES 3.10 to please my computer so change that if needed.
Have a nice day

Thank you! :)


text:
Mobile app support ( Android & IOS )

We will use Electrum-CPU as an alternative for other bitcoin based mobile wallet applications ( Coinomi, Bitcoin Wallet ( Java ), etc.)
Android build is available but they don't work properly ( Maybe y-chan will be able to handle this issue )
IOS build is being developed and used by Electron-Cash and the PR for electrum is available here ( https://github.com/spesmilo/electrum/pull/4795 )

Android build is fixing now.
But, iOS build is I think we should not build until electrum's thing is formally merged.

Ah....
I fixed Android build.
But, operation is very slowly...

Closing as per https://github.com/cpuchain/electrum-cpu/pull/4

authors: minkcrypto y-chan

repo: cpuchain/electrum-cpu


text:
?size=48

The ?size=48 parameter has broken and now it just returns a stave skin for all users.

This isn't broken, you're just getting an uncached response and hitting the issues of #260.

repo: crafatar/crafatar


text:
🚧 Client v2

[x] Drop support for python v2
[x] Remove six
[x] Migrate to poetry
[x] Get rid of deprecated functions/features
[x] pandas v1
[ ] Rebase once #180 is merged

Testable using the release candidate using pip install craft-ai==2.0.0rc2

@yleprincecraft @sperretcraft @PaulineMCraft @juliencraftai please test and give feedback ! It's also the right time to make big changes.

repo: craft-ai/craft-ai-client-python