text:
[Bug]: Content-Security-Policy blocks access.

What happened?
I guess this is a CORS issue with my React app? But some guidance on this would be helpful.
GET https://cdn.paddle.com/paddle/v2/paddle.js net::ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep 200 (OK)
I've tried modifying my Content-Security-Policy to this:
<meta http-equiv="Content-Security-Policy" content="script-src 'self' https://cdn.paddle.com/; worker-src 'self' blob:;">
But it doesn't seem to help. Any thoughts? Could the code that downloads the script in the package be marked specifically with some modifier that CORS allows? I've seen that done elsewhere.
Steps to reproduce
Use the package via yarn install in a React app that has a strict Content-Security-Policy.
What did you expect to happen?
No response
How are you integrating?
No response
Logs
No response

Hi @zachwhelchel,
We are more than happy to help.
Looking at the error code NotSameOriginAfterDefaultedToSameOriginByCoep, I am guessing you have a Cross-Origin-Embedder-Policy header set as require-corp.
If yes, can you please change it to credentialless along with the Content-Security-Policy change you already had in your question to allow scripts from https://cdn.paddle.com/
if not, please share all the security headers you have in your application so that we can check further.
Thank you.

@vijayasingam-paddle thanks for the response. I set the Cross-Origin-Embedder-Policy as you suggested and it gets further now... but when I try to initialize a checkout the window shows this:

There are no errors given in the console so I'm not sure what to do next.

@vijayasingam-paddle I just checked the documentation for my code base and apparently there are restrictions on the CORS changes I can make:
In addition to the HTTPS requirement, the Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy headers must be set to require-corp and same-origin respectively.
Is there any way around this from your all's end? Does Paddle provide a hosted checkout page? Where I could direct users to with some prefilled options? Any way I try this I can't seem to get paddle to load on my app.

Hi @zachwhelchel,
Sorry, we do not provide hosted checkout pages in Paddle.
Changing CORS headers is a very common approach to include third party scripts (Including Google Analytics or Cookie consent popup providers) to our applications.  So it should be alright to change the CORS headers to allow downloading scripts from our domain.
Unfortunately, I don't see any other option to make it work.

but when I try to initialize a checkout the window shows this:
This is strange, we suspect a firewall or some other issue in your end.

What happens when you open https://buy.paddle.com/ in your browser? it should throw a Something went wrong as it is missing some input not relevant to our test to see if you have a problem on your end.

@vijayasingam-paddle this is what I see when I go to that url. So it seems to load in another tab but in my app it's still giving the "refused to connect" error I posted above. Is there some other security setting that needs to be set that we haven't covered?

@vijayasingam-paddle I thought it might be due to a "frame-src" in the Content-Security-Policy but that doesn't seem to be the case.

I also tried adding this and it didn't change anything:
frame-ancestors 'self' https://sandbox-buy.paddle.com/;

@vijayasingam-paddle welp... it turns out that Safari is still not pleased with my changes to "credentialless". We use the Shared Array Buffer and "credentialless" removes access to it for security purposes.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer
Is there any chance I can set up a developer support call or something? I really want to implement Paddle but I just can't seem to get it working!

Hi @zachwhelchel,
I am sorry to hear that you are getting stuck while integrating with Paddle.
Can you please reach out to us at sellers@paddle.com and one of our support specialist will be able to help you with the integration.
Thank you.

@thomasdondorf thanks for jumping in here. Just an update from my end. I was never able to get this working... I had to opt to sending users to a page on my marketing site to process the payment. Not ideal. Would love to see this fixed.

@zachwhelchel Sure, I was happy someone had already reported the problem :)
The only way to solve this currently is to redirect from the "main page" to some special page with the policy disabled...

Hi @zachwhelchel,
I am so sorry, i was with the impression that our support team was working with you to solve the problem. I didn't know that it was still open.
Hi @thomasdondorf,
Thank you for sharing a very detailed report.
I will check with our support team to find why it was not addressed and move the ticket back to engineering to fix this problem.
Thank you for your patience, I am really sorry for the inconvenience.

This one is super interesting for me 😃 I hope we can get it working soon

Hi everyone,
Sorry for the long silence on this issue.
I am working with our security team internally to come with the best solution that works for everyone and will update you once i have something concrete.
Thank you for waiting patiently.

I'm seeing a CSP issue too. Not sure if it's the same problem as that discussed here but I'll report just in case it's related.
I have paddle integrated into an electron app that has the following CSP:
 <meta
            http-equiv="Content-Security-Policy"
            content="default-src 'self' https://describo.github.io https://stamen-tiles-a.a.ssl.fastly.net/ https://api.github.com https://raw.githubusercontent.com https://api.ror.org;
            script-src 'self' https://cdn.paddle.com/paddle/v2/paddle.js https://public.profitwell.com/js/profitwell.js;
            style-src 'self' 'unsafe-inline' https://sandbox-cdn.paddle.com/paddle/v2/assets/css/paddle.css https://cdn.paddle.com/paddle/v2/assets/css/paddle.css;
            connect-src https://www2.profitwell.com;
            img-src * crate-file: data:;
            media-src crate-file:;
            frame-src https://buy.paddle.com https://sandbox-buy.paddle.com;"
        />

In dev, connecting to the paddle sandbox works fine but when the app is built, it refuses to connect to paddle prod.
In the console I see:
[Report Only] Refused to frame 'https://buy.paddle.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors ". Note that '' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'https:' must be added explicitly.
[Report Only] Refused to frame 'https://buy.paddle.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors ". Note that '' matches only URLs with network schemes ('http', 'https', 'ws', 'wss'), or URLs whose scheme matches self's scheme. The scheme 'https:' must be added explicitly.

Hi @marcolarosa,
You are seeing a different error and not related to this GH issue.
As the log says, the message you see is [Report Only] and should not be blocking your request. With that said, we found that our checkout doesn't open within an electron app because of the domain checks.
Our Checkouts can be launched only from approved domains in Production. However, as electron apps do not have a domain, our validation is failing and throwing an error.
I am sorry that you are running into this issue.
I am checking with the team about fixing this issue. Meanwhile, please open a different issue in GH to track this independently.
Thank you.

@vijayasingam-paddle Ahh sorry! Thanks for the advice.

Hi @zachwhelchel / @thomasdondorf / @pedrovgs,
Thank you for being patient while we were looking into this issue.
Unfortunately, I have some bad news. I am afraid we won't be able to make our checkouts work with cross-origin isolation.
Changing the CORS headers in the Paddle side of things was the easier change. However, we quickly found that the problems don't stop there.
In a cross-origin isolated environment, all the iframes loaded into the browser will inherit the same COEP and should either be from the same domain or include appropriate CORS headers. Even though we could fix the headers on our end, we rely on other payment partners and their servers do not send any CORS headers.
Due to this, with the correct CORP and COEP headers we will be able to run Paddle.js and launch checkout. However, it will fail when it reaches the 3DS payments screen with the same error.
There is a proposal to allow iframes to act independently, though browser support is minimal as it works only with Chrome at the moment. We cannot choose this solution as we will have to support all the browsers.
Sadly, there is very little we can do about this issue. We will keep tabs on the proposal and we could get it working once every major browsers start supporting it.
Please let us know if we can help you with anything else.
Thank you

@vijayasingam-paddle would it be possible to allow opt-in for using the credentialless iframes?

Hi @lowkahonn,
That is something we can do. However, we would probably not recommend this for most users because this will hit the conversion rate drastically.
I will get this working in a couple of weeks and maybe we could run some beta tests to see real-world impact.
Thank you.

Hi @reknih,
We would like to keep the library pure and move away from any side effects based on the browser. We won't be auto-detecting this property based on the browser and would like our integrators to pass the value when they need it.
I found this snippet to detect if an element supports a property.
You can use this to detect if iframe supports credentialless and pass it to the new attribute we will add to PaddleJS.
Thank you.

I was able to integrate the payment process relatively smoothly in the following way. I added an exception in my server configuration to not serve the "Cross-Origin" headers for the one page that integrates Paddle.js (/checkout in my example).
Here is my (simplified) nginx config.
location = /checkout {
    try_files /checkout.html =404;
}

location / {
    add_header Cross-Origin-Opener-Policy "same-origin";
    add_header Cross-Origin-Embedder-Policy "require-corp";

    try_files $uri.html =404;
}

Note for Next.js users (like myself): Make sure to use actual links (a instead of Link) and "real" redirects (location.assign/location.replace instead of router.push/router.replace) when linking to the Paddle page as otherwise the headers will not be loaded.
Maybe this helps someone else.

As someone reached out to me for help, I'll give more details below:
You can see it in action here: https://www.chessmonitor.com/pricing, but you have to create a (free) account.
I hope it's okay that I link it here (if you are a chess player, check it out 😉).
Basically there are two pages:

/pricing

This page does not interact with Paddle. It only presents the data to the user.
When the user wants to subscribe to a plan, I call location.assign(`/checkout?plan=${PADDLE_PRICE_ID}`) to send the user to the checkout page.

/checkout

This is the only page in the frontend that interacts with Paddle.
In contrast to /pricing this page is not linked anywhere and users should only be redirected here. If a user opens /checkout on his own, he will simply be redirected back to the pricing page.
The page can do two things:

Users can "order" (via /checkout?plan=[PADDLE_PRICE_ID])
Users can "update their payment information" (via /checkout?_ptxn=[SOME_INTERNAL_PADDLE_DATA])

Case "Order":

The checkout page then initializes Paddle and calls Checkout.open(...) with the priceId from the URL.

Case "Update payment information":

When your user uses the URL provided in data.management_urls.update_payment_method via the subscription API, it will send him to the Default payment link (set in your Checkout Settings), together with a parameter _ptxn. That page is /checkout here. So it looks like this: /checkout?_ptxn=[SOME_INTERNAL_PADDLE_DATA]
In this case, the checkout only initializes Paddle and Paddle.js will take care of the rest. Just make sure you don't open the checkout again if that parameter exists.

And of course, you should setup an event listener to listen to events like checkout.completed/checkout.closed to forward the user back.
Hope that makes it more clear!

import { initializePaddle, Paddle } from '@paddle/paddle-js';

export const PaddleCheckoutButton = ({ user, className }: { user: User, className?: string }) => {
  const [paddle, setPaddle] = useState<Paddle>();
  const email = user.email ?? '';

  useEffect(() => {
    initializePaddle({ environment: process.env.NEXT_PUBLIC_PADDLE_SANDBOX == 'true' ? 'sandbox' : 'production', token: process.env.NEXT_PUBLIC_PADDLE_CLIENT_TOKEN ?? '' }).then(
      (paddleInstance: Paddle | undefined) => {
        if (paddleInstance) {
          setPaddle(paddleInstance);
        }
      },
    );
  }, []);

  const openCheckout = () => {
    paddle?.Checkout.open({
      customer: { email: email }, //after add this line , won't work
      items: [{ priceId: process.env.NEXT_PUBLIC_PADDLE_PAYMENT_PRICE_ID ?? '' }],
    });
  };

  return (
    <Button variant={'default'} onClick={openCheckout} className={className ?? ''} >Add funds</Button>
  );
}

here is my basic Paddle check button to show a overlay checkout , if add customer email it wont't , but if hard code a email@domain.com ,it's works, mean i cannot pass any parameters to checkout open just because cross-origin issue ?

I've faced the same issue at https://insightvox.net, so I had to disable the CSP for the  where the Paddle iframe is shown.
Since I'm using Ruby on Rails, this method https://api.rubyonrails.org/classes/ActionController/ContentSecurityPolicy/ClassMethods.html#method-i-content_security_policy_report_only
allows setting the CSP as report only.
So in your controller, you would add:
 content_security_policy_report_only only: :new
to ensure only the affect route is disabled.
In my case the subscription page is under authentication, so the risk is limited, but ensure you know what you're doing.
Hope this helps other people landing here!

authors: eggcaker fidalgo lowkahonn marcolarosa pedrovgs thomasdondorf vijayasingam-paddle zachwhelchel

repo: PaddleHQ/paddle-js-wrapper


text:
缕清几个Android 应用Paddle时的概念

示例程序提到的生成merged model（也就是 *.paddle文件）要准备好准备好模型配置文件（.py）和参数文件（.tar.gz）。
问题：
1.参数文件（.tar.gz）是经过PC训练生成的吧？
2.模型配置文件mobilenet.py，是个啥东东？超链接打不开，看不到是啥
3.在PC上使用模型预测时，不需要这个“模型配置文件”吧？
4.Android APP我在Windows环境下用过Android Studio开发过，请问将paddle库、merge生成的 *.paddle文件分别放到对应的文件夹下，之后就可以在Android Studio 调api了，最后打包成apk，是这样吗？还是要像[示例程序]第4步？
谢谢。。。

亲，我很想请教你移植paddlepaddle到安卓上的问题，有空能不能回复一下我，谢谢！！！！！

source: gharchive/issue

repo: PaddlePaddle/Mobile

license_type: permissive

license_source: github-api


text:
gpu下预测的结果都是正常的，但切换到cpu下预测，结果全是nan

您好，这个是哪个模型呢？paddle的版本是？

您好，这个是哪个模型呢？paddle的版本是？

最新的版本，2.6.0

您使用的模型链接是？我们复现下

repo: PaddlePaddle/PaddleClas


text:
关于训练数据的不同尺寸差异较大的问题

你好，我在用MobileNetV3_large_x1_0模型训练自己的分类模型时，发现识别的准确率并不理想，猜想可能我使用的训练数据的尺寸差异较大是其中一个原因，有的小的不到100 * 100，大的会到1000 * 1000多，请问这种情况对于分类效果会有影响吗？
如果有影响的话，是否需要我对该网络结构进行修改？或者是否支持多尺度训练？

你好，

目前还不支持多尺度训练，训练的时候会做resize，前景所占原图比例差异太大的话，尺度确实会有一定影响
如果机器允许的话，可以尝试一下hrnet、se-resnext这些结构，或者试着在你的网络里面加上一些attention结构

你好，

目前还不支持多尺度训练，训练的时候会做resize，前景所占原图比例差异太大的话，尺度确实会有一定影响
如果机器允许的话，可以尝试一下hrnet、se-resnext这些结构，或者试着在你的网络里面加上一些attention结构

clas里面也总结了一些训练预测方面的faq，可以参考一下
https://github.com/PaddlePaddle/PaddleClas/blob/dygraph/docs/zh_CN/faq_series.md

clas里面也总结了一些训练预测方面的faq，可以参考一下
https://github.com/PaddlePaddle/PaddleClas/blob/dygraph/docs/zh_CN/faq_series.md

你好，

目前还不支持多尺度训练，训练的时候会做resize，前景所占原图比例差异太大的话，尺度确实会有一定影响
如果机器允许的话，可以尝试一下hrnet、se-resnext这些结构，或者试着在你的网络里面加上一些attention结构

谢谢建议，请问hrnet、se-resnet结构是否支持端侧部署？

你好，

目前还不支持多尺度训练，训练的时候会做resize，前景所占原图比例差异太大的话，尺度确实会有一定影响
如果机器允许的话，可以尝试一下hrnet、se-resnext这些结构，或者试着在你的网络里面加上一些attention结构

谢谢建议，请问hrnet、se-resnet结构是否支持端侧部署？

hrnet静态图是支持的，动态图目前有一个op还不支持，预计下个月就会支持

hrnet静态图是支持的，动态图目前有一个op还不支持，预计下个月就会支持


text:
[Question]: 文档抽取任务Label Studio 数据转换出现异常

请提出你的问题
参考文档:https://github.com/PaddlePaddle/PaddleNLP/blob/develop/applications/information_extraction/label_studio_doc.md
在执行数据转换脚本时执行脚本:

python label_studio.py  --label_studio_file ./document/data/label_studio.json --save_dir ./document/data --splits 0.8 0.1 0.1 --task_type ext

出现如下异常:

上图红色框选区域为我手动打印的数据内容,修改D:\ProgramData\Anaconda3\lib\site-packages\paddlenlp\utils\tools.py代码增加 print("8888", line["data"])用于数据输出:

def process_text_tag(self, line, task_type="ext"):
items = {}
print("8888", line["data"])
items["text"] = line["data"]["text"]
if task_type == "ext":
items["entities"] = []
items["relations"] = []
result_list = line["annotations"][0]["result"]
for a in result_list:
if a["type"] == "labels":
items["entities"].append(
{
"id": a["id"],
"start_offset": a["value"]["start"],
"end_offset": a["value"]["end"],
"label": a["value"]["labels"][0],
}
)
else:
items["relations"].append(
{
"id": a["from_id"] + "-" + a["to_id"],
"from_id": a["from_id"],
"to_id": a["to_id"],
"type": a["labels"][0],
}
)
elif task_type == "cls":
items["label"] = line["annotations"][0]["result"][0]["value"]["choices"]
return items

  本机paddle相关包版本为:

错误原因，是我在数据标注的时候把Use image from field修改成了$ocr,用默认的$image就可以了

repo: PaddlePaddle/PaddleNLP


text:
tts python服务怎样设置cpu_threads

rt, 在application.yaml中添加了cpu_threads: 但是不起作用

开发者你好，感谢关注 PaddleSpeech 开源项目，抱歉给你带来了不好的开发体验，目前开源项目维护人力有限，你可以尝试通过修改 PaddleSpeech 源码的方式自己解决，或请求开源社区其他开发者的协助。飞桨开源社区交流频道：飞桨AI Studio星河社区-人工智能学习与实训社区

repo: PaddlePaddle/PaddleSpeech


text:
Win11，GUI RC2报错，1.17正常

问题类型：PaddleX可视化客户端
PaddleX GUI版本
PaddleX GUI  RC2版本
问题描述
===================================

This log file path is D:\paddlex_workspaceRC2\projects\P0006\T0008\err.log
注意：标志为WARNING/INFO类的仅为警告或提示类信息，非错误信息
D:\PaddleX2.0.0rc2_windows10\paddle\distributed\parallel.py:120: UserWarning: Currently not a parallel execution environment, `paddle.distributed.init_parallel_env` will not do anything.
  "Currently not a parallel execution environment, `paddle.distributed.init_parallel_env` will not do anything."
D:\PaddleX2.0.0rc2_windows10\paddle\tensor\creation.py:125: DeprecationWarning: `np.object` is a deprecated alias for the builtin `object`. To silence this warning, use `object` by itself. Doing this will not modify any behavior and is safe.
Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  if data.dtype == np.object:
D:\PaddleX2.0.0rc2_windows10\paddle\tensor\creation.py:125: DeprecationWarning: `np.object` is a deprecated alias for the builtin `object`. To silence this warning, use `object` by itself. Doing this will not modify any behavior and is safe.
Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  if data.dtype == np.object:

import numpy as np
from paddle.io import DataLoader, Dataset

class RandomDataset(Dataset):
    def __getitem__(self, idx):
        data = np.random.random((2, 3)).astype('float32')

        return data

    def __len__(self):
        return 10

dataset = RandomDataset()
loader = DataLoader(dataset, batch_size=1)
data = next(loader())

In Paddle <= 2.0, data is in format '[Tensor(shape=(1, 2, 3), dtype=float32)]', and in Paddle >= 2.1, data is in format 'Tensor(shape=(1, 2, 3), dtype=float32)'

Process Process-1:2:
Traceback (most recent call last):
  File "multiprocessing\process.py", line 297, in _bootstrap
  File "multiprocessing\process.py", line 99, in run
  File "paddlexui\pms\model_tasks\tasks.py", line 71, in _call_paddlex_train
  File "paddlexui\pms\model_tasks\train\detection.py", line 225, in train
  File "D:\PaddleX2.0.0rc2_windows10\paddlex\cv\models\detector.py", line 286, in train
    use_vdl=use_vdl)
  File "D:\PaddleX2.0.0rc2_windows10\paddlex\cv\models\base.py", line 337, in train_loop
    loss.backward()
  File "<decorator-gen-123>", line 2, in backward
  File "D:\PaddleX2.0.0rc2_windows10\paddle\fluid\wrapped_decorator.py", line 25, in __impl__
    return wrapped_func(*args, **kwargs)
  File "D:\PaddleX2.0.0rc2_windows10\paddle\fluid\framework.py", line 227, in __impl__
    return func(*args, **kwargs)
  File "D:\PaddleX2.0.0rc2_windows10\paddle\fluid\dygraph\varbase_patch_methods.py", line 239, in backward
    framework._dygraph_tracer())
OSError: (External)  Cudnn error, CUDNN_STATUS_EXECUTION_FAILED  (at C:/home/workspace/Paddle_release2/paddle/fluid/operators/conv_cudnn_op.cu:790)

GUI RC2报错，
1.17 反而正常
目录设置home地址是
D:\PaddleX2.0.0rc2_windows10
报错的地址是
C:/home/workspace/Paddle_release2/paddle/fluid/operators/conv_cudnn_op.cu
不存在这个目录

PaddleX2.0.0rc2需要cuda 11.2，cudnn8。
可以先试下paddlex api开发模式。

nvidia-smi

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 471.68       Driver Version: 471.68       CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ... WDDM  | 00000000:01:00.0 Off |                  N/A |
| N/A    0C    P8    10W /  N/A |    164MiB /  6144MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Wed_Jul_14_19:47:52_Pacific_Daylight_Time_2021
Cuda compilation tools, release 11.4, V11.4.100
Build cuda_11.4.r11.4/compiler.30188945_0
cudnn-11.4-windows-x64-v8.2.2.26
系统是 cuda 11.4   cudnn8.2.2.26
是这个问题导致 ？

已经解决
NVIDIA-SMI 465.89       Driver Version: 465.89       CUDA Version: 11.3
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Nov_30_19:15:10_Pacific_Standard_Time_2020
Cuda compilation tools, release 11.2, V11.2.67
Build cuda_11.2.r11.2/compiler.29373293_0

authors: FlyingQianMM monkeycc

repo: PaddlePaddle/PaddleX


text:
没有为 model_infer.exe 加载的符号文件

https://github.com/PaddlePaddle/PaddleX/issues/913
以上链接有类似问题，但是解决问题的关键链接打不开了。
环境：
win10   cuda11.0  cudnn8.0   TensorRT-7.1.3.4均已安装。
用delevop版本，v2.0.0版本的deploy\cpp可以生成解决方案。运行代码时在model->Predict(imgs, &results, 1);
这句代码报错： 没有为 model_infer.exe 加载的符号文件。
另外的尝试：模仿链接所说的：https://github.com/PaddlePaddle/PaddleX/issues/913
在deploy\cpp\tools\build_lib中把CMakeList替换掉deploy\cpp的CMakeList。但是生成解决方案就报错了。
报错如下：

@heliqi 麻烦有空帮忙看看，谢谢。

解决了。没有为 model_infer.exe 加载的符号文件
解决方法：  用paddlex训练的话，string model_type = "seg";要设成"paddlex"。
另外的尝试不管了。


text:
PaddleDetection训练的模型怎么支持用paddleX进行导出部署

目前paddleDetection的模型有: model_final.pdopt 、  model_final.pdparams ； 没有json文件 和 model.xml
可以将这个模型 用paddleX 导出 并部署不

需要先参照PaddleDetection的导出文档https://github.com/PaddlePaddle/PaddleDetection/blob/release/2.5/deploy/EXPORT_ONNX_MODEL.md 将模型导出为部署模型。
此外PaddleX的部署代码我们已经重构升级，开源了新的部署产品FastDeploy，支持CPU/GPU以及更多硬件，同时支持不同推理引擎，包括Paddle Inference/Paddle Lite/ONNX Runtime/OpenVINO/TensorRT, 示例参考 https://github.com/PaddlePaddle/FastDeploy/tree/release/1.0.2/examples/vision/detection/paddledetection

需要先参照PaddleDetection的导出文档https://github.com/PaddlePaddle/PaddleDetection/blob/release/2.5/deploy/EXPORT_ONNX_MODEL.md 将模型导出为部署模型。
此外PaddleX的部署代码我们已经重构升级，开源了新的部署产品FastDeploy，支持CPU/GPU以及更多硬件，同时支持不同推理引擎，包括Paddle Inference/Paddle Lite/ONNX Runtime/OpenVINO/TensorRT, 示例参考 https://github.com/PaddlePaddle/FastDeploy/tree/release/1.0.2/examples/vision/detection/paddledetection

好的 谢谢老师, 我去了解下fastDeploy ;

可是不对啊，楼上所说的链接是PaddleDetection在fastDeploy上的部署啊，和paddlex有啥关系，刚去看了fastD的git简介，还是不支持paddlex啊。。。

可是不对啊，楼上所说的链接是PaddleDetection在fastDeploy上的部署啊，和paddlex有啥关系，刚去看了fastD的git简介，还是不支持paddlex啊。。。

意思就是跳过paddlex，直接用fastDeploy来部署就可以了

authors: NeTChengGH fanruifeng jiangjiajun lingdujunshang


text:
Implemented a housing price prediction case and Handwritten digit recognition

…ognition

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

source: gharchive/pull-request

authors: CLAassistant sqle-github

repo: PaddlePaddle/awesome-DeepLearning


text:
add fp16 support to diag test=document_fix

fp16 任务中增加 diag 中文文档 float16 支持
关联任务：https://github.com/PaddlePaddle/Paddle/issues/50832
关联PR：https://github.com/PaddlePaddle/Paddle/pull/50848

@sunzhongkai588 孙师傅记得审pr

repo: PaddlePaddle/docs


text:
add chapter 1 5 6

添加入门课第1，5和6章节的内容

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

PR 中的.DS_store文件删掉
readme太简陋了，参考计算机视觉-分类部分改下

签一下这个协议

authors: 1649759610 CLAassistant LDOUBLEV

repo: PaddlePaddle/tutorials


text:
how to test after following the deploy steps?

Hi,
I've configured all the steps up to step number 5, but i'm not sure if it's working, i tried change the on-call schedules from PagerDuty but there are no alerts that pop-up.
Is there a way to test this from AWS Lambda or DynamoDB?
Thanks, hope to hear from you soon...

forgot to add the bot into the slack channel , sorry about this...

repo: PagerDuty/pd-oncall-chat-topic


text:
UUID empty on first run on ios9, true device

When I first run this code  (simplified for reading purposes) after an install on true device, I get a blank uuid. On second run it does work though.
Iphone 5s ios9 on my side.
testuuid.txt

can't understand what your true mean
please use the simple code to see if wverytime will get the uuid
// Get UUID
window.plugins.uniqueDeviceID.get(success, fail);
Success callback function:

function success(uuid)
{
    console.log(uuid);
};

if yes，I think it is the "testuuid.txt" problem

+1
same issue on iPhone 6 (9.2) and iPhone 5s (8.3)

authors: bau720123 kozzztya monxas

repo: Paldom/UniqueDeviceID

license: mit

license_source: bigquery


text:
MDX v2 support

Description

Changed the a tag in the createContactInfo markdown function to follow the markdown link syntax of [text](url).
Removed the mdx-code-block code blocks in the markdown templates for the generateApiDocs function.
Added a new line before and after every tag in the create markdown util function.

Motivation and Context

I am upgrading my Docusaurus site to use MDX v2 and Code Hike and ran into several errors associated with the changes that this PR makes.

Without adding a new line before and after every tag in the create function, I get an error like this when spinning up the development server:

# Lots of these errors
Expected a closing tag for `<div>` (16:686-16:691) before the end of `paragraph`

# And then lots of these errors
[webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'Compilation/modules|/Users/janessa.garrow/dev/openapi-docusaurus/node_modules/babel-loader/lib/index.js??ruleSet[1].rules[8].use[0]!/Users/janessa.garrow/dev/openapi-docusaurus/node_modules/docusaurus-mdx-loader-v2/lib/index.js??ruleSet[1].rules[8].use[1]!/Users/janessa.garrow/dev/openapi-docusaurus/node_modules/@docusaurus/plugin-content-docs/lib/markdown/index.js??ruleSet[1].rules[8].use[2]!/Users/janessa.garrow/dev/openapi-docusaurus/docs/platform-api/aggregate-member.api.mdx': No serializer registered for VFileMessage
<w> while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> webpack/lib/ModuleBuildError -> VFileMessage

After updating the create markdown util to add a new line in between the tags, I ran into this error:

Error: Unknown language: mdx-code-block

Since the blocks flagged with mdx-code-block are just importing other components and using the JSX in the generated MDX files, I removed the code block syntax entirely and the components rendered as expected.

Finally, after making the above 2 changes, I get an error with the a tag in the contact info:

Expected a closing tag for `</a>` (54:1-54:7) before the end of `paragraph`

Changing that a tag to use markdown link syntax resolved the error.

How Has This Been Tested?

Screenshots (if appropriate)

Types of changes

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

Checklist

[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

I am not sure if this is related. docusarus doesn't support MDX v2. https://github.com/facebook/docusaurus/pull/8288

Ok, I think I was able to reproduce some or all of what you encountered @jgarrow, by followed the docs here: https://codehike.org/docs/installation/docusaurus
Still debugging the errors but I'll use your changes in this PR as a guide.

@jgarrow I think we're on the same page now although I reproduced on v2.3.1 and might be seeing something slightly different.
Here's what I am seeing:
Unexpected character `=` (U+003D) before name, expected a character that can start a name, such as a letter, `$`, or `_`
Expected a closing tag for `</a>` (241:1-241:7) before the end of `paragraph`

I think we could work toward escaping the comparison operators but replacing  tags with []() doesn't seem to work currently. I wonder if the markdown just needs to be on a separate line from the inline HTML.

Yup, confirmed that this allows the markdown URL to render:

 URL: [https://github.com/Redocly/redoc](https://github.com/Redocly/redoc)

@sserrata I do know with MDX v2, any inline content inside of a JSX tag that would be turned into an inline HTML element will still be interpreted as markdown (see this section on their docs)

We might need additional leading and trailing new lines to allow the markdown to render:

Yeah, MDX v1 will need it in order to render. MDX v2 knows how to handle it inline.

Thanks @jgarrow - in your opinion, do you see a way for both MDXv1 and v2 to be supported with a common MDX output/format from this plugin?

@sserrata as much as I hate having a p tag inside of a span, this might be the only way to have it work with both MDX v1 and v2. Maybe we an add some inline styling to the span so that it removes the bottom margin from the child p tag that ends up wrapping around the text?

 URL: [https://github.com/Redocly/redoc](https://github.com/Redocly/redoc)

Just wanted to mention that afaik it is planned to support MDX 2 with Docusaurus 3.0, which should be the next release

authors: Dr-Electron guitaoliu jgarrow sserrata

license: MIT


text:
HOW TO GET HIT COUNT

Hi all,
Is there a method to get hit count value?
Thanks

I have also looked around but cant find anything

You can get rule hit count using 'op'.
Build the base object:

pandev = base.PanDevice.create_from_device(<panorama/firewall>, api_username=, api_password=)
dg = 'My Device Group'
rule = 'My Rule Name'
cmd_rule-hit-count = ''.format(dg, rule)
resp_rule-hit-count = pandev.op(cmd=cmd_rule-hit-count, cmd_xml=False)
This will pull the rule hit count data for each firewall in the device group and the tree will look like:

yes

yes

authors: EdoardoMDP ishuguru rebelfish

repo: PaloAltoNetworks/pandevice

license: ISC


text:
feat(examples/cloudngfw_isolated_design): introduce cloudngfw isolated design

Description
The CloudNGFW example with appropriate module was introduced in this PR. This is the first reference architecture published and it is related to our roadmap - Issue #9
Motivation and Context
Easy to use module should support all referenced architecture related with CloudNGFW.
How Has This Been Tested?
On dev environment the traffic was inspected against simple any - any and any -deny rule.
Screenshots (if appropriate)

Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

Great work so fat @lstadnik 👍🏽

authors: lstadnik migara


text:
[FEATURE] Faster pip install for inference

Is your feature request related to a problem? Please describe.
It takes 5 mins to do:
!pip install -q -U auto-gptq

in a free google colab notebook. This means it adds 5 mins before inference can start.
Describe the solution you'd like
Provide a slimmed down way to install only what is needed to run inference.
Describe alternatives you've considered
Perhaps there are other packages I can use to run the GPTQ quantised model, but it's hard to find info.
Additional context
Here is the inference code I'm using:
from auto_gptq import AutoGPTQForCausalLM, BaseQuantizeConfig

os.environ["SAFETENSORS_FAST_GPU"] = "1"

model_name_or_path = "TheBloke/Llama-2-7b-Chat-GPTQ"
model_basename = "gptq_model-4bit-128g"

use_triton = False

model = AutoGPTQForCausalLM.from_quantized(model_name_or_path,
        model_basename=model_basename,
        use_safetensors=True,
        trust_remote_code=True,
        device="cuda:0",
        use_triton=use_triton,
        quantize_config=None,
        cache_dir=cache_dir)

Hi, there are bunch of pre-build wheels provided in each release, you can use one of them to fast install if cuda version is match

Cheers thanks @PanQiWei - I see that now as well in the ReadMe

authors: PanQiWei RonanKMcGovern

repo: PanQiWei/AutoGPTQ


text:
New update turns the view black after closing the view

Hi
I just updated my app with the newest update to this project.
Now, when i close a card, the screen turns black.
I also tried it with the demo app, and it also turns itself black.
I am looking into the issue. And will post update as soon as i have found the bug.
But if you have found it, let me know.

Check out bug #131 && #121
find shouldPresent function and I replace detailVC.isFullscreen = fullscreen with
detailVC.modalPresentationStyle = .fullScreen

Check out bug #131 && #121
find shouldPresent function and I replace detailVC.isFullscreen = fullscreen with
detailVC.modalPresentationStyle = .fullScreen

let card = CardHighlight(frame: CGRect(x: 10, y: 30, width: 200 , height: 240))
card.backgroundColor = UIColor(red: 0, green: 94/255, blue: 112/255, alpha: 1)
card.icon = UIImage(named: "flappy")
card.title = "Welcome \nto \nCards !"
card.itemTitle = "Flappy Bird"
card.itemSubtitle = "Flap That !"
card.textColor = UIColor.white
card.hasParallax = true
let cardContentVC = storyboard!.instantiateViewController(withIdentifier: "CardContent")
card.shouldPresent(cardContentVC, from: self, fullscreen: false)
view.addSubview(card)
Xcode 11.4.1
Project Deployment Target iOS13.0
Target Deployment iOS 13.0
Device iOS 13.3.1

Check out bug #131 && #121
find shouldPresent function and I replace detailVC.isFullscreen = fullscreen with
detailVC.modalPresentationStyle = .fullScreen

Hello, after modifying according to your method, the problem remains
Xcode 11.4.1
Project Deployment Target iOS13.0
Target Deployment iOS 13.0
Device iOS 13.3.1

can confirm this solved the problem.
still had it in iOS 14 Thanks!

In the function "shouldPresent" of file Card.swift add the following code:
under detailVC.isFullscreen = fullscreen
need add
if fullscreen {
detailVC.modalPresentationStyle = .fullScreen
}
else {
detailVC.modalPresentationStyle = .currentContext
}
it worked for me

repo: PaoloCuscela/Cards


text:
Color Transformer

Hi and TnQ for this awesome lib.
issue #80 is closed. but i didnt know how this feature added to lib and how we can use it now.
can anyone help?

Reopened #80.

repo: PaoloRotolo/AppIntro


text:
hide-itemmeta-with-visual-effects docs

Docs for PaperMC/Paper#8561.

Controls whether item information that affects how an item is displayed (such as lodestone compass positions) should be sent to other players' clients. This information could be used by cheat clients to give another advantage to the cheating player. However, this may affect small details about how an item looks when held by another player.

Might be better? I feel like the first sentence was just way too long :)

That sounds a lot better, thanks :)

repo: PaperMC/docs


text:
Create fails at Remove the hdd0 device w/ sudo requirement

When trying to create a new machine, VM creation fails and requests admin os credentials:
Errors:
Failed to register the VM: The operation failed. To perform this operation, you must enter the host OS administrator's credentials.
Failed to create the virtual machine.

Debug Output:
docker-machine create -d parallels --parallels-boot2docker-url https://github.com/boot2docker/boot2docker/releases/download/v1.8.2/boot2docker.iso test-parallels --debug
executing: prlctl --version
executing: prlsrvctl info --license
Downloading boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.8.2/boot2docker.iso...
Creating SSH key...
Creating Parallels Desktop VM...
executing: prlctl create test-parallels --distribution boot2docker --dst /Users/arod/.docker/machine/machines/test-parallels --no-hdd
Creating the virtual machine...
Generate the VM configuration for boot2docker.
Remove the hdd0 device.
Failed to register the VM: The operation failed. To perform this operation, you must enter the host OS administrator's credentials.
Failed to create the virtual machine.
Error creating machine: prlctl create test-parallels --distribution boot2docker --dst /Users/arod/.docker/machine/machines/test-parallels --no-hdd failed: exit status 255
You will want to check the provider to make sure the machine and associated resources were properly removed.

Any ideas on how to resolve this?

I've answered on the similar issue with vagrant-parallels: https://github.com/Parallels/vagrant-parallels/issues/67#issuecomment-32774326
Please, open the window "Parallels Desktop -> Preferences -> Security" and
disable the option "Require password to: Create a new virtual Machine"

Awesome! Issue resolved. Thanks!

repo: Parallels/docker-machine


text:
Consider migrating to Maplibre

We'd migrate from Leaflet to https://maplibre.org.
MapLibre is vector-based, which should be faster to load than Leaflet's raster-based approach. It also reduces our data usage from Stamen Tiles.
However, this might be a big rewrite, especially wtih CSS. So I'm not sure it's worth it.

I'm voting no. We're only using half of our data allotment for map tiles, and it's not very expensive if we have to upgrade more.
Regarding performance, https://blog.locationiq.com/vector-or-raster-maps-which-one-is-best-for-you/ doesn't make it sound like it's that dramatic of an improvement for user experience. It can actually be worse for low compute devices. Either way, the biggest issue with our map is the size of the lots data set, not the map tile itself.
Our engineering time would be better spent on other projects.

repo: ParkingReformNetwork/parking-lot-map


text:
The ability to upload maps.

Users should be able to upload maps.

Added: 31feb8d3774239301718b8363ddc7472307041c2

repo: ParretLabs/fortunatemaps


text:
Parse.User.logIn from Cloud Code fails

Hi,
I implemented a custom login function in cloud code which was working fine but as I tried it out yesterday I get "invalid login parameters" and I'm definitely sending the right credentials. On my way down to find the issue I even tried the most simple approach in a Parse.Cloud.define("user_login", .. block i called:
Parse.User.logIn(request.params.username, request.params.password, {
success: function(user) {
// Get user profile
callback.success(user)
},
error: function(user, error) {
callback.error(error);
}
})
but it still leaves me with the error.
I saw there was a change in the SDK 3 days ago maybe it's somehow connected
Btw I'm not really sure if the JavaScript and the Cloud functionality are connected in Parse, please feel free to update me ;)
Regards Daniel

FYI:
When I call the function from the API Console with Run as ... current user with valid session and send the user credentials I get:
{
"code": 141,
"error": "undefined"
}

Which version of the SDK is your cloud code using? You can find out by viewing your app's logs, and looking at the header of the page, or by running parse jssdk in your app's directory.

E2016-01-27T17:11:00.941Z]v1168 Ran cloud function user_login with:
Input: {"password":"...","username":"..."}
Result: invalid login parameters
E2016-01-27T17:11:37.678Z]v1168 Ran cloud function user_login for user ... with:
Input: {"password":"...","username":"..."}
Result: undefined
v1168
Thanks

Sorry, I meant the version of the SDK, not the current deployment. In the header of the logs page, it tells you when the last deploy was, and what JS SDK version is used.

Latest deploy: v1175 - Wednesday January 27th 2016 at 7:30:09pm (+0100) - Parse JavaScript SDK Version: 1.6.14

Cool, then we can not worry about the changes to login that went out with 1.7.0.
If you can provide a small, complete test case that reproduces this error reliably, we might be able to help. Otherwise, we're in the dark, as it's probably not tied to the SDK, but we'll do our best.

Ok will do asap,
thanks in advance

EDIT: I edit on top cause it's good new ;)
I just had the idea creating another app and upload the CloudCode for my user login there. Actually it worked so maybe my DB/App seems kind of corrupted. Might consider clean up everything and give it another try.
// Actual message
Actually I don't know how u normally conduct your tests but as far as it concerns my case following approach fails 100% and that's the minimal setup possible:
I created a user: which works fine doing it with the API Console, in the data browser or a custom register function I created in cloud code do validate parameters and execute further steps on signUp.
Anyway after creating the user, for simplicity I used username="username", password="password", I call the cloud function user_login (from API Console or from my App)  passing username and password but to simplify it even more and eliminate any errors that might be occur on the transmission, I hardcoded the values into the cloud function:
Parse.Cloud.define("user_login", function(request, response) {
                   Parse.User.logIn("username", "password", {
                                    success: function(user) {
                                    esponse.error(user)
                                    },
                                    error: function(object, error) {
                                    response.error(error.message)
                                    }
                                    })
                   })

RESPONSE
{
    "code": 141,
    "error": "invalid login parameters"
}

I discovered the problem after I switched to an implementation using Promises, but even restoring the above code the result was the same. Been working on other stuff lately but the code was defiantly working before as I used it quite often to run my app
Anyway I gonna call the Parse.User.LogIn method directly now and might do my other setup in the afterSave method which seems to work.
Thanks for your efforts, from my side no critical issue ;) but keep me posted if something comes up
Regards Daniel

Last post for sure:
Remove all cloud code but my login routine and it's working again ... who know what it was

authors: andrewimm dnyle

repo: ParsePlatform/Parse-SDK-JS


text:
Flow typing

Restore stable typing to the JS codebase

[Current coverage][cc-pull] is 86.99%

Merging [#312][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.23%

@@             master       #312   diff @@
==========================================
  Files            42         42
  Lines          3814       3853    +39
  Methods         659        660     +1
  Messages          0          0
  Branches        796        812    +16
==========================================
+ Hits           3327       3352    +25
- Misses          487        501    +14
  Partials          0          0

Powered by Codecov. Last updated by [c96e8dd...43172fe][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ParsePlatform/Parse-SDK-JS/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ParsePlatform/Parse-SDK-JS/compare/c96e8dd990e7e031f790d86bb3b92fb78bcd1cfe...43172fe4d526d079b1e9166215053e2fd53a32ea?src=pr
[cc-pull]: https://codecov.io/gh/ParsePlatform/Parse-SDK-JS/pull/312?src=pr

authors: andrewimm codecov-io


text:
Bolts.framework issue

parseStarterproject is not have Bolts.framework

Hey @wangdayewjf, any chance you can point to which one of the 3 possible references to parse starter project you are referencing here.

Package downloaded from https://parse.com/docs/downloads (double checked, it explicitly includes Bolts.framework)
Package downloaded from the releases on this repository (double checked, it explicitly includes Bolts.framework)
To the ParseStarterProject.xcodeproj in source of this repo?

The latter one could be built by using Parse.xcworkspace. Since we are building from source - there is no need of having Bolts.framework, as it will be compiled from scratch and cross-referenced.

authors: nlutsenko wangdayewjf

repo: ParsePlatform/Parse-SDK-iOS-OSX


text:
PFRelation not working I think

I just updated from 1.6.2 to 1.12.0 besides my collection views loosing performance, it looks like the relations aren't being created.
error response:
2016-03-01 15:24:29.415 Fashun[3408:883978] [Error]: PFKeychainStore failed to get object for key 'currentUser', with error: -34018
2016-03-01 15:24:29.421 Fashun[3408:883978] [Error]: PFKeychainStore failed to set object for key 'currentUser', with error: -34018
like obejct saved for Optional("bubbles")
Code:
let like = Like(photo: photo, user: user)
    like.saveInBackgroundWithBlock({ (success:Bool, error:NSError?) -> Void in
        if error == nil {
            let likeCreatedAtRelation = user.relationForKey("like_createdat")
            likeCreatedAtRelation.addObject(like)
            user.saveInBackgroundWithBlock({ (success:Bool, error:NSError?) -> Void in
                self.photo.saveInBackgroundWithBlock({ (success:Bool, error:NSError?) -> Void in
                    self.transitionInProgress = false
                    print("like obejct saved for \(user.firstName)")
                })
            })
        } else {
            print("error.userInfo: \(error!.userInfo)")
        }
    })

Any ideas?

Hey @alexrmacleod, let's debug this together!
Few questions that would be help uncover the truth:

Are you using Local Datastore?
How does the fact that relations are not being created surface? Is it Local Datastore query or query caching or it doesn't show up on the dashboard?
Since you are saving objects directly - this should convert into a network request, meaning that we can debug it together! Whee! Any chance you can instrument your app with client-side Network Debug Tool and paste the output of these network requests into this issue. The process is described on this repo wiki here.

Let me know how it goes, I am confident we'll uncover what is going on.

A response from @nlutsenko I feel blessed! After more digging I found #437 could be the same problem.
I have a feeling that PFKeychainStore isn't working as it should, so when I try to use PFRelation to save a objects to a PFUser account it can't find the user I am trying to save to. but sometimes the error message: " [Error]: PFKeychainStore failed to set object for key 'currentUser', with error: -34018" doesn't even show up. but every time the object doesn't save.
Are you using Local Datastore?

no not using enableLocalDatastore
How does the fact that relations are not being created surface? Is it Local Datastore query or query caching or it doesn't show up on the dashboard?
I press a like button on a viewcontroller which runs the "like.saveInBackgroundWithBlock", then when I move to the users profile viewcontroller to perform a relation query of all their likes, the like that should have been saved doesn't show up.
**Since you are saving objects directly - this should convert into a network request, meaning that we can debug it together! Whee! Any chance you can instrument your app with client-side Network Debug Tool and paste the output of these network requests into this issue. The process is described on this repo wiki here.
**
when a users presses a like button
URL : https://api.parse.com/1/batch Method : Optional("POST") Headers : Optional(["X-Parse-Installation-Id": "d8521f2b-6adb-40bf-aed6-0d54b146d9e1", "X-Parse-Session-Token": "g36UP66cvvbKfk8cZ5ZMaOvHe", "Content-Type": "application/json; charset=utf-8"]) Request Body : Optional({"requests":[{"path":"\/1\/classes\/Photo\/GKJv3IYTWj","method":"PUT","body":{"app_likes_count":{"amount":1,"__op":"Increment"},"lovedBy":{"objects":[{"__type":"Pointer","className":"_User","objectId":"UffHHSeUzH"}],"__op":"AddRelation"}}}]}) URL : https://api.parse.com/1/batch Status Code : 200 Headers : [Access-Control-Allow-Methods: *, Content-Type: application/json; charset=utf-8, Server: nginx/1.6.0, X-Parse-Platform: G1, Connection: keep-alive, Date: Tue, 01 Mar 2016 11:30:35 GMT, X-Runtime: 1.217524, Content-Length: 75, Access-Control-Allow-Origin: *] Response Body : Optional([{"success":{"app_likes_count":2,"updatedAt":"2016-03-01T11:30:34.735Z"}}] ) URL : https://api.parse.com/1/classes/Like Method : Optional("POST") Headers : Optional(["X-Parse-Installation-Id": "d8521f2b-6adb-40bf-aed6-0d54b146d9e1", "X-Parse-Session-Token": "g36UP66cvvbKfk8cZ5ZMaOvHe", "Content-Type": "application/json; charset=utf-8"]) Request Body : Optional({"photo":{"__type":"Pointer","className":"Photo","objectId":"GKJv3IYTWj"},"user":{"__type":"Pointer","className":"_User","objectId":"UffHHSeUzH"}}) URL : https://api.parse.com/1/classes/Like Status Code : 201 Headers : [Server: nginx/1.6.0, Content-Type: application/json; charset=utf-8, Access-Control-Allow-Methods: *, Location: https://api.parse.com/1/classes/Like/MOJgcs6jq2, X-Parse-Platform: G1, Connection: keep-alive, Date: Tue, 01 Mar 2016 11:30:35 GMT, X-Runtime: 0.012480, Content-Length: 65, Access-Control-Allow-Origin: *] Response Body : Optional({"createdAt":"2016-03-01T11:30:35.773Z","objectId":"MOJgcs6jq2"} ) URL : https://api.parse.com/1/classes/_User/UffHHSeUzH Method : Optional("PUT") Headers : Optional(["X-Parse-Installation-Id": "d8521f2b-6adb-40bf-aed6-0d54b146d9e1", "X-Parse-Session-Token": "g36UP66cvvbKfk8cZ5ZMaOvHe", "Content-Type": "application/json; charset=utf-8"]) Request Body : Optional({"like_createdat":{"objects":[{"__type":"Pointer","className":"Like","objectId":"MOJgcs6jq2"}],"__op":"AddRelation"},"authData":{"facebook":{"id":"10152639114171574","access_token":"CAAUCSRZCIXqUBAGov4IXKTFv7L5UUSQZALgoxNdIirh66ZAR4wCctRXuN8JZAZBQU6Jk6Rx8dUoykeRDcqYMXJy9rZC0SMDOQSdHfXqBF1hZAUwTr3ZAwKKj0hQD8nJVOZB6ZC0yzdUsvqdRobOlJ38cEEZBMRcyjn9Rc3E0wHDmfy3hYNiJoL7X5Hc20e1b0FgYu2MIQPsfJb7rGTXG1fKRgDOtbv5lWRuZBiuBgDUFiOIfZBQZDZD","expiration_date":"2016-04-30T07:20:58.863Z"}}}) URL : https://api.parse.com/1/classes/_User/UffHHSeUzH Status Code : 200 Headers : [Access-Control-Allow-Methods: *, Content-Type: application/json; charset=utf-8, Server: nginx/1.6.0, X-Parse-Platform: G1, Connection: keep-alive, Date: Tue, 01 Mar 2016 11:30:36 GMT, X-Runtime: 0.025931, Content-Length: 403, Access-Control-Allow-Origin: *] Response Body : Optional({"authData":{"facebook":{"access_token":"CAAUCSRZCIXqUBAGov4IXKTFv7L5UUSQZALgoxNdIirh66ZAR4wCctRXuN8JZAZBQU6Jk6Rx8dUoykeRDcqYMXJy9rZC0SMDOQSdHfXqBF1hZAUwTr3ZAwKKj0hQD8nJVOZB6ZC0yzdUsvqdRobOlJ38cEEZBMRcyjn9Rc3E0wHDmfy3hYNiJoL7X5Hc20e1b0FgYu2MIQPsfJb7rGTXG1fKRgDOtbv5lWRuZBiuBgDUFiOIfZBQZDZD","expiration_date":"2016-04-30T07:20:58.863Z","id":"10152639114171574"}},"updatedAt":"2016-03-01T11:30:36.099Z"} ) like obejct saved for Optional("peony")

I couldn't figure out how to convert this

NSLog(@"Status Code : %ld", (long)response.statusCode);
to swift: the (long) part I just did
print("Status Code : (response!.statusCode)")

Put this on the Network debug tool wiki page for all the swift coders:
   Parse.setLogLevel(PFLogLevel.Debug)     NSNotificationCenter.defaultCenter().addObserver(self, selector: "receiveWillSendURLRequestNotification:", name: PFNetworkWillSendURLRequestNotification, object: nil)     NSNotificationCenter.defaultCenter().addObserver(self, selector: "receiveDidReceiveURLResponseNotification:", name: PFNetworkDidReceiveURLResponseNotification, object: nil)
`    func receiveWillSendURLRequestNotification(notification:NSNotification) {
let request = notification.userInfo![PFNetworkNotificationURLRequestUserInfoKey];
print("URL : (request!.URL!!.absoluteString)")
print("Method : (request!.HTTPMethod)")
print("Headers : (request!.allHTTPHeaderFields)")
print("Request Body : (NSString(data: request!.HTTPBody!!, encoding: NSUTF8StringEncoding))")
}
func receiveDidReceiveURLResponseNotification(notification:NSNotification) {
    let request = notification.userInfo![PFNetworkNotificationURLRequestUserInfoKey];
    let response = notification.userInfo![PFNetworkNotificationURLResponseUserInfoKey];
    let responseBody = notification.userInfo![PFNetworkNotificationURLResponseBodyUserInfoKey];
    print("URL : \(request!.URL!!.absoluteString)")
    print("Status Code : \(response!.statusCode)")
    print("Headers : \(response!.allHeaderFields)")
    print("Response Body : \(responseBody)")
}

`

Thanks for the Swift code snippet - will update.
The Request/Response actually looks absolutely correct as you can see there are __op: AddRelation in the body which add the objects to the relation of like_createdat.
Any chance you can log the request/response that you perform via relation query?
Since data is properly getting saved, I think there might be a problem in this space.

After some query investigation I realised the
query.cachePolicy = PFCachePolicy.CacheElseNetwork
should be:
query.cachePolicy = PFCachePolicy.NetworkElseCache
That was the reason why the newly saved relations weren't showing up on the users profile viewcontroller
So relations are working fine sorry for the confusion, thanks for the help, please check out this though #842

Great!
Glad you found the solution!

authors: alexrmacleod nlutsenko


text:
Losing my committed offsets

Hi all,
I have some strange behavior I can't quite get to the bottom of.  I have a consumer listening on a topic in a consumer group like so (I'm using Kafka 0.8.2):
    client = KafkaClient(hosts=kafka_hosts)
    input_topic = client.topics[topic_in]
    consumer = input_topic.get_simple_consumer(consumer_group=group_id,
                                               auto_offset_reset=OffsetType.EARLIEST,
                                               auto_commit_enable=False)

    for message in consumer:
        # Do some work....
        consumer.commit_offsets()

This works great most of the time, e.g. I can restart the consumer and it picks up after the last successfully processed message.
However, I've found that if I restart my consumer after its been idle for quite some time, it occasionally loses its mind and starts processing all the messages in the topic that have already been committed!  It's as if Kafka has reset the offsets on me.
Could it be something to do with where the offsets are being stored (not sure if they're being stored in ZooKeeper or Kafka)?  I came across this guy,
http://kafka.apache.org/documentation.html#offsetmigration
I'm using the defaults for 0.8.2...
Thanks for any tips on getting to the bottom of this!  It's hard for me to reproduce!

Hi @youngpm, thanks for checking this in. I've actually seen behavior like this before in my local testing, but I've never gotten to the bottom of it. We've never seen it in production, so it hasn't been a super high priority to fix, but it's good to know I'm not the only one who's seen this. Pykafka only knows how to store offsets in kafka itself, so offsets in zookeeper should not be a factor here.
There are two things I recommend changing about your test script to see if/how they affect the results you're seeing. First, I'd use auto_commit_enable=True with auto_commit_interval_ms=1000. Committing the offset after each message as you're doing should work, but the tests I've run are all using autocommitting since it's slightly more performant in production. Second, I'd change auto_offset_reset to OffsetType.LATEST. It's possible that your consumer is resetting itself to the beginning of the topic because of this setting, so it would be good to remove that variable.

This excerpt from the documentation strikes me as a possible cause:
In case the offset manager was just started or if it just became the offset manager for a new set of consumer groups (by becoming a leader for a partition of the offsets topic), it may need to load the offsets topic partition into the cache. In this case, the offset fetch will fail with an OffsetsLoadInProgress exception and the consumer may retry the OffsetFetchRequest after backing off.

Though the SimpleConsumer does handle this case here.

Hey @emmett9001,
I avoided using auto_commit_enable=True because my client launches a pretty long running compute job (image processing), and I didn't want the message marked as consumed if it failed.  Same with auto_offset_reset being set to OffsetType.EARLIEST; I wanted the client to pick up where it left off if it died on me, I think when set to latest you'd miss any messages that came in while you were down.  Might be wrong though, pretty new to Kafka!  Maybe there's a better way to deal with a failure?
I've upped the verbosity on my logs, so next time it happens, maybe I'll have more info!

Restarting from EARLIEST can actually result in repeated messages, since it sets the consumer offset to the earliest offset available for each partition. This means that if you've consumed some messages on a partition and then the consumer resets its offsets, it will go back to the earliest offset still held on that partition - probably one of the ones you just consumed. Neither EARLIEST nor LATEST will actually guarantee that the consumer will pick up where it left off after a failure - the best way to ensure this is to commit offsets regularly, as you're doing.

I got some more info with a better logging level on!
I had a consumer listening on a topic, no activity on the topic for days.  A message came in, it processed it, but died trying to commit the offsets:
Traceback (most recent call last):
  File "/home/ubuntu/whackstack/metadata_matsel_service.py", line 190, in <module>
    consumer.commit_offsets()
  File "/home/ubuntu/whackstack/venv/local/lib/python2.7/site-packages/pykafka/simpleconsumer.py", line 340, in commit_offsets
    self._consumer_group, 1, 'pykafka', reqs)
  File "/home/ubuntu/whackstack/venv/local/lib/python2.7/site-packages/pykafka/broker.py", line 309, in commit_consumer_group_offsets
    return self._offsets_channel_req_handler.request(req).get(OffsetCommitResponse)
  File "/home/ubuntu/whackstack/venv/local/lib/python2.7/site-packages/pykafka/handlers.py", line 55, in get
    raise self.error
pykafka.exceptions.SocketDisconnectedError

This process is running under supervisord, so it restarted and I see this:
INFO:2015-07-27 22:12:17,426:cluster.py:_update_brokers:Discovered 1 brokers
INFO:2015-07-27 22:12:17,428:cluster.py:_update_topics:Discovered 15 topics
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,429:topic.py:update:Adding 1 partitions
INFO:2015-07-27 22:12:17,430:cluster.py:get_offset_manager:Attempting to discover offset manager for consumer group 'matsel'
INFO:2015-07-27 22:12:17,432:cluster.py:get_offset_manager:Found coordinator broker with id 1
INFO:2015-07-27 22:12:17,436:simpleconsumer.py:_setup_fetch_workers:Starting 1 fetcher threads
INFO:2015-07-27 22:12:17,438:simpleconsumer.py:_reset_offsets:Resetting offsets for 1 partitions

So the last line there says it reset the offsets!  I would guess that the failure to commit the offsets in the first place is related.  The consumer actually processed everything correctly up until the commit_offsets call.  In fact, it posted a message on another topic, where another service died in the same exact way!
That's about all I know, any ideas what would cause the restart?

Just realized I was on version 1.0.3, looks like _reset_offsets doesn't exist anymore.  I've got the latest from pip and will keep monitoring the logs!

@emmett9001, So moving to the latest version on pip (pykafka 1.1.0), I haven't seen any more resetting of offsets!
However, I am now getting quite a number of these fellows when calling commit_offsets() when the consumer has been idle for a few hours:
Traceback (most recent call last):
  File "/home/ubuntu/whackstack/refine_matsel_service.py", line 230, in <module>
    consumer.commit_offsets()
  File "/home/ubuntu/whackstack/venv/local/lib/python2.7/site-packages/pykafka/simpleconsumer.py", line 349, in commit_offsets
    self._consumer_group, 1, 'pykafka', reqs)
  File "/home/ubuntu/whackstack/venv/local/lib/python2.7/site-packages/pykafka/broker.py", line 308, in commit_consumer_group_offsets
    return self._offsets_channel_req_handler.request(req).get(OffsetCommitResponse)
  File "/home/ubuntu/whackstack/venv/local/lib/python2.7/site-packages/pykafka/handlers.py", line 55, in get
    raise self.error
pykafka.exceptions.SocketDisconnectedError

The consumer still gets the message and does its thing, but dies at the very end on the commit.  supervisord restarts and it succeeds on the second go around with the commit, not sure what's up!

I wonder if your losing stored offsets previously could be related to the topic having been idle for days, which in combination with your brokers' retention settings may have caused them to get cleaned up by the time you hit this SocketDisconnectedError (which triggered the restart then, too, right?).

Good point, @yungchin.  Unlike previous versions of Kafka where offsets were stored forever in Kafka, offset storage rotates after a defined TTL which is offsets.topic.retention.minutes in the broker config. link.  The default for this is 24h, so if you weren't saving offsets for a few days and it crashed before you saved new values, it makes sense that the old values would be lost.

@kbourgoin Well the offsets were being committed every time a message came in (maybe a few minute delay from getting the message and committing it), its just that no messages were delivered to the topic for a while.
Basically it was idle for long periods of time in the for message in consumerloop.  I'm not sure if the offset reset is a red herring now, I was on pykafka 1.0.3 when I encountered the offset resets, but the logic has changed in 1.1.0.  Now I'm getting what's described in #224, but I haven't seen a reset of the offsets since I upgraded versions.

Closing this issue. @youngpm feel free to reopen if you see this behavior again.

Haven't seen the issue again since moving to the new version, so I think this will stay closed.

authors: emmett9001 kbourgoin youngpm yungchin

repo: Parsely/pykafka


text:
New method for assigning cpu affinity

Description
This provides a new method for setting cpu affinity via a method similar to setting thread binding in mpiexec calls.
In the config object, users can now pass a string of this type:
cpu_affinity="list:<worker1_threads>:<worker2_threads>:<worker3_threads>"
Each worker's threads can be specified as a comma separated list or a hyphenated range:
thread1,thread2,thread3
or
thread_start-thread_end
An example for Sunspot/Aurora:
cpu_affinity="list:0-7,104-111:8-15,112-119:16-23,120-127:24-31,128-135:32-39,136-143:40-47,144-151:52-59,156-163:60-67,164-171:68-75,172-179:76-83,180-187:84-91,188-195:92-99,196-203"
This example assigns 16 threads each to 12 workers. Note that there are threads that are skipped; this is because the total number of hardware threads is not evenly divisible by the number of GPUs.
This will give a user more flexibility in setting cpu affinity and also allows them to leave idle certain threads if they choose (currently required by all cpu-affinity strategies in parsl).
If the number of thread "ranks" (colon separated thread lists/ranges) doesn't match the total number of workers an exception will be raised.
Changed Behaviour
No current behavior is changed
Type of change
Choose which options apply, and delete the ones which do not apply.

New feature

This looks good. Given the fragility of htex process worker pool changes in the past (for example, spawn method and worker restarts both didn't work at all), I'd like to figure out how to test this more automatically - I guess that would need at least a two core system so tests could play around with pinning?

Other random bits:
CI is broken because of code formatting (flake8 parsl/).
The description of the PR is pretty good documentation and it would be good to paste it pretty much as-is into the main documentation somewhere - for example the "Multi-Threaded Applications" section of docs/userguide/configuring.rst, or the cpu_affinity docstring in parsl/executors/high_throughput/executor.py

This is failing with type checking error:
parsl/executors/high_throughput/process_worker_pool.py:595: error: Value of type "str | bool" is not indexable  [index]

which is saying, basically, what if someone passed in a bool here, not a string...
because part of the existing code says you are allowed to do that, even though in practice that doesn't happen and I think is probably broken.
I'll make a PR to remove that code, and then this type error should go away.

Okay, thanks.  I also realized that I unintentionally did away with the argparse check, so I tried to fix that.

@cms21 I added a rough test here, that checks that when htex is launched with a single worker / single core affinity, then the worker sees that same single core affinity.

@cms21 or @WardLT can you have a look at the test I added and check it makes sense. Aside from that, I'm fine with merging the rest of this PR.

Is there a reason that the test is just for one worker/thread?

Hey, is there anything I can help with so that we can wrap up this PR?

repo: Parsl/parsl


text:
Onsite Payments Notification: cell_number not returned

After making an Onsite Payment, the Customer's cell_number is not in the POSTed notify_url

Thank you, will let you know when there is a resolution.

authors: clairepf tjhunkin

repo: PayFast/payfast-php-sdk


text:
Referral new schema

@lkysow @arvandtiv take a look at this. it's almost there but note totally. still some issues with the arabic side.

:+1: nice, so what are the issues with the arabic?

On the services view, the fields are not being displayed correctly. Heres what
![Uploading Screen Shot 2015-12-19 at 9.47.21 PM.png…](mine looks like)

@tuckerbuchy closing this since I merged everything into master

authors: lkysow tuckerbuchy

repo: PeaceGeeksSociety/services-advisor


text:
[Snyk] Security upgrade golang from latest to 1.23rc2

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

owasp-top10-2021-apps/a3/comment-killer/deployments/api.Dockerfile

We recommend upgrading to golang:1.23rc2, as this image has only 87 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

CVE-2024-37370 SNYK-DEBIAN12-KRB5-7411314
  ****

CVE-2024-37371 SNYK-DEBIAN12-KRB5-7411315
  ****

Link Following SNYK-DEBIAN12-GIT-6846203
  500

Link Following SNYK-DEBIAN12-GIT-6846203
  500

Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963
  500

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
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 fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – 7b0da2d2-e8fa-421e-a03e-269e38027507
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2020-28458
Npm-datatables.net-1.10.19
Vulnerable Package

CVE-2020-28458
Npm-datatables-1.10.21
Vulnerable Package

CVE-2021-32050
Npm-mongodb-3.3.2
Vulnerable Package

CVE-2022-26592
Npm-node-sass-4.9.3
Vulnerable Package

CVE-2022-26592
Npm-node-sass-4.11.0
Vulnerable Package

CVE-2022-37620
Npm-html-minifier-3.5.21
Vulnerable Package

CVE-2022-43357
Npm-node-sass-4.9.3
Vulnerable Package

CVE-2022-43357
Npm-node-sass-4.11.0
Vulnerable Package

CVE-2022-43358
Npm-node-sass-4.9.3
Vulnerable Package

CVE-2022-43358
Npm-node-sass-4.11.0
Vulnerable Package

CVE-2023-24998
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20210226172049-e18ecbb05110
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20180724234803-3673e40ba225
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20190404232315-eb5bcb51f2a3
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20220412020605-290c469a71a5
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20190620200207-3b0461eec859
Vulnerable Package

CVE-2023-42282
Npm-ip-1.1.5
Vulnerable Package

CVE-2023-44487
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2023-44487
Go-google.golang.org/grpc-v1.21.1
Vulnerable Package

CVE-2023-45133
Npm-@babel/traverse-7.18.0
Vulnerable Package

CVE-2023-45133
Npm-@babel/traverse-7.11.5
Vulnerable Package

CVE-2023-45133
Npm-@babel/traverse-7.4.5
Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20220412020605-290c469a71a5
Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20210226172049-e18ecbb05110
Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20190620200207-3b0461eec859
Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20180724234803-3673e40ba225
Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20190404232315-eb5bcb51f2a3
Vulnerable Package

CVE-2023-45311
Npm-fsevents-1.2.7
Vulnerable Package

CVE-2023-45311
Npm-fsevents-1.2.4
Vulnerable Package

CVE-2023-46136
Python-Werkzeug-0.14.1
Vulnerable Package

CVE-2023-46234
Npm-browserify-sign-4.2.1
Vulnerable Package

CVE-2023-46589
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2023-6378
Maven-ch.qos.logback:logback-classic-1.2.3
Vulnerable Package

CVE-2023-6378
Maven-ch.qos.logback:logback-core-1.2.3
Vulnerable Package

CVE-2023-6481
Maven-ch.qos.logback:logback-core-1.2.3
Vulnerable Package

CVE-2024-22243
Maven-org.springframework:spring-web-5.2.9.RELEASE
Vulnerable Package

CVE-2024-22259
Maven-org.springframework:spring-web-5.2.9.RELEASE
Vulnerable Package

CVE-2024-22262
Maven-org.springframework:spring-web-5.2.9.RELEASE
Vulnerable Package

CVE-2024-23672
Maven-org.apache.tomcat.embed:tomcat-embed-websocket-9.0.38
Vulnerable Package

CVE-2024-23672
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2024-24549
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2024-24792
Go-golang.org/x/image-v0.0.0-20190802002840-cff245a6509b
Vulnerable Package

CVE-2024-27088
Npm-es5-ext-0.10.53
Vulnerable Package

CVE-2024-27088
Npm-es5-ext-0.10.47
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-5.3.3
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-3.7.2
Vulnerable Package

CVE-2024-31573
Maven-org.xmlunit:xmlunit-core-2.7.0
Vulnerable Package

CVE-2024-33883
Npm-ejs-2.6.1
Vulnerable Package

CVE-2024-33883
Npm-ejs-3.1.8
Vulnerable Package

CVE-2024-34069
Python-Werkzeug-0.14.1
Vulnerable Package

CVE-2024-34750
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2024-37890
Npm-ws-6.1.4
Vulnerable Package

CVE-2024-37890
Npm-ws-3.3.3
Vulnerable Package

CVE-2024-37890
Npm-ws-7.3.1
Vulnerable Package

CVE-2024-37890
Npm-ws-8.6.0
Vulnerable Package

CVE-2024-37890
Npm-ws-6.2.1
Vulnerable Package

CVE-2024-37890
Npm-ws-7.5.7
Vulnerable Package

CVE-2024-37890
Npm-ws-5.2.2
Vulnerable Package

CVE-2024-38355
Npm-socket.io-2.1.1
Vulnerable Package

CVE-2024-38355
Npm-socket.io-2.3.0
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

CVE-2024-4068
Npm-braces-1.8.5
Vulnerable Package

CVE-2024-4068
Npm-braces-3.0.2
Vulnerable Package

Client_DOM_XSS
/owasp-top10-2021-apps/a8/amarelo-designs/app/static/User/vendor/raphael/raphael.js: 6006
Attack Vector

Client_DOM_XSS
/owasp-top10-2021-apps/a6/cimentech/app/html/modules/overlay/overlay-parent.js: 610
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/app.js: 154
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/app.js: 89
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/scram.js: 242
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/scram.js: 242
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/app.js: 153
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/app.js: 88
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/app.js: 163
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/scram.js: 133
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/app.js: 111
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/db.js: 103
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/db.js: 95
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a1/tictactoe/src/db.js: 76
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/mongocr.js: 18
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/mongocr.js: 17
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/mongocr.js: 17
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb/lib/operations/db_ops.js: 88
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb/lib/operations/db_ops.js: 88
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/connection/connection.js: 126
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb/lib/operations/db_ops.js: 96
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb/lib/operations/db_ops.js: 96
Attack Vector

Insecure_Storage_of_Sensitive_Data
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/mongodb-core/lib/auth/mongocr.js: 35
Attack Vector

MongoDB_NoSQL_Injection
/owasp-top10-2021-apps/a3/mongection/src/app.js: 59
Attack Vector

Passwords And Secrets - Generic Password
/docker-compose.yml: 31
Query to find passwords and secrets in infrastructure code.

Second_Order_SQL_Injection
/owasp-top10-2021-apps/a1/tictactoe/src/db.js: 13
Attack Vector

Absolute_Path_Traversal
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/send/index.js: 613
Attack Vector

Absolute_Path_Traversal
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/send/index.js: 613
Attack Vector

Absolute_Path_Traversal
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/send/index.js: 613
Attack Vector

Absolute_Path_Traversal
/owasp-top10-2021-apps/a5/stegonography/app/node_modules/dotenv/config.js: 8
Attack Vector

Broken_or_Risky_Hashing_Function
/owasp-top10-2021-apps/a6/cimentech/app/html/modules/openid/openid.inc: 520
Attack Vector

Broken_or_Risky_Hashing_Function
/owasp-top10-2021-apps/a6/cimentech/app/html/modules/openid/openid.inc: 462
Attack Vector

Broken_or_Risky_Hashing_Function
/owasp-top10-2021-apps/a6/cimentech/app/html/modules/openid/openid.inc: 461
Attack Vector

Broken_or_Risky_Hashing_Function
/owasp-top10-2021-apps/a6/cimentech/app/html/modules/openid/openid.inc: 455
Attack Vector

CSRF
/owasp-top10-2021-apps/a6/cimentech/app/html/modules/simpletest/drupal_web_test_case.php: 1815
Attack Vector

CVE-2019-11841
Go-golang.org/x/crypto-v0.0.0-20181112202954-3d3f9f413869
Vulnerable Package

CVE-2019-11841
Go-golang.org/x/crypto-v0.0.0-20190103213133-ff983b9c42bc
Vulnerable Package

CVE-2019-11841
Go-golang.org/x/crypto-v0.0.0-20181203042331-505ab145d0a9
Vulnerable Package

CVE-2019-18799
Npm-node-sass-4.9.3
Vulnerable Package

CVE-2019-18799
Npm-node-sass-4.11.0
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.15.0
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.5.7
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.13.0
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.7.0
Vulnerable Package

CVE-2023-29407
Go-golang.org/x/image-v0.0.0-20190802002840-cff245a6509b
Vulnerable Package

CVE-2023-29408
Go-golang.org/x/image-v0.0.0-20190802002840-cff245a6509b
Vulnerable Package

CVE-2023-34055
Maven-org.springframework.boot:spring-boot-2.3.4.RELEASE
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20190404232315-eb5bcb51f2a3
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20190620200207-3b0461eec859
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20210226172049-e18ecbb05110
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20220412020605-290c469a71a5
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20180724234803-3673e40ba225
Vulnerable Package

CVE-2023-41080
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2023-42795
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.4.14
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.39
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.35
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.32
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.21
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.14
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.2
Vulnerable Package

CVE-2023-45648
Maven-org.apache.tomcat.embed:tomcat-embed-core-9.0.38
Vulnerable Package

CVE-2023-45857
Npm-axios-0.20.0
Vulnerable Package

CVE-2023-45857
Npm-axios-0.17.1
Vulnerable Package

CVE-2023-45857
Npm-axios-0.21.4
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20190103213133-ff983b9c42bc
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20181203042331-505ab145d0a9
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20201002170205-7f63de1d35b0
Vulnerable Package

More results are available on AST platform

authors: svc-pe-appsec vrangsr

repo: PearsonAppsec/secDevLabs


text:
Database/firebase

fixes #6 e #5

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: PedroHenry-Santos/form


text:
[BUG] High module counts causing stuck mic, repeating initialization, and Easy Comms read issues

Describe the bug
As discussed in discord, having a high module count (38) will cause vaicom behavioral issues such as reinitialization with PTT press, PTT getting stuck open or closed, and failure to read in game easy comms.
To Reproduce
Install 38+ DCS modules.
Expected behavior
No change in behavior.
Screenshots
See Discord
Additional context
Issue being tracked via thread in discord and actively worked on. Fixes in PRs should be mentioned here for tracking.

Closed, fixed in V2.8.1.0

authors: Penecruz rcflyinghokie

repo: Penecruz/VAICOMPRO-Community


text:
Sarasa Gothic: add TTC version

Saves valuable bandwidth and space😎

It‘s better to new a manifest file for using ttc format fonts.

Closing in favor of https://github.com/matthewjberger/scoop-nerd-fonts

authors: Pengxn kidonng

repo: Pengxn/xn

license: Unlicense


text:
Prepackaged Recon Spec Starting Incorrect Workflow

Hello,
I just started using QSIPrep (0.9.0beta1) yesterday; I am very excited by the notion of a fully automated and reproducible pipeline, so thank you for your continued efforts in developing this!
I am testing on two subjects with single-shelled (b=1000) acquisition and no reverse PE b0 image available (so I cannot do SDC). Since the program I use for tractography, TractSeg, expects peaks exported from MrTrix, this seems to leave me with one recon option, which is mrtrix_singleshell_ss3t_noACT. I run qsiprep with the singularity command:
singularity exec -B /DATA --nv -e  /PATH/TO/qsiprep.img \
qsiprep /PATH/TO/BIDS \
/PATH/TO/DERIVATIVES \
participant \
-w /PATH/TO/DERIVATIVES \
--output-resolution 1 --hmc_model eddy \
--recon-spec mrtrix_singleshell_ss3t_noACT --fs-license-file /PATH/TO/license.txt  \
--unringing_method mrdegibbs --force-spatial-normalization
However, when reconstruction starts, I see the following message:

[Node] Setting-up "qsirecon_wf.sub-reader001_mrtrix_multishellmsmt_noACTmsmt.recon_wf.qsiprep_preprocessed_dwi_data" in "/om2/vast/gablab/smeisler/qsiprep_testing/derivatives/qsirecon_wf/sub-reader001_mrtrixmultishell_msmt_noACTmsmt/recon_wf/dwi_file..om2..vast..gablab..smeisler..qsiprep_testing..derivatives..qsiprep..sub-reader001..ses-pre..dwi..sub-reader001_ses-pre_run-1_space-T1w_desc-preproc_dwi.nii.gz/qsiprep_preprocessed_dwi_data".

So it appears that it is starting the multishell workflow. Of note, the recon description text that proceeds the processing does correctly describe the MrTrix3Tissue single shell protocol.
Also, why does ACT require SDC? I thought only having the 5tt T1 (and multishell acquisition, but dhollander seems to suffice for single-shell) was sufficient for ACT.
Thanks again for your help,
Steven

The pipeline is correct, it just has the wrong workflow name in the json file. This will be fixed soon #150

Got it, thanks! I'll close this issue since you opened the fix request. Also, incase anyone was curious about the last question I posed regarding why ACT requires SDC, it is answered here: https://community.mrtrix.org/t/act-and-no-reversed-phase-encoding-information/1122

authors: mattcieslak smeisler

repo: PennBBL/qsiprep


text:
Add new bug rules to rules.bugs

Here are the rules:
If you find a new bug during a tournament/league game:

Play on, if both players agree.
Otherwise the player with the bugged cards must swap out the bugged cards (only) from their decklist, restart the match, players concede games in the correct order until the record matches the record before the bugged game. Sideboarding then takes place if it was not game 1 and the rest of the match plays out.

7f132ff5.

repo: PennyDreadfulMTG/Penny-Dreadful-Tools


text:
Feature/cu m3ccc9 adapt scripts to use colliders

Player and enemies colliders working.
All raycast-based hits removed.
There is a bug which melee grunt inflicts damage two times in the same hit. It will be fixed with the new tesseract build.
Fixed PlayerController bugs (shoot attack speed, old externalized variables)
Fixed enemies animation bugs (They got stuck in some cases and some animations were running badly)
Fixed some sounds problems.

Task linked: CU-m3ccc9 Adapt scripts and prefabs to use colliders Fang & Onimaru

repo: PenteractStudios/Penteract


text:
Add note about the input values

The input values to use are not obvious for newbies on noise generation or procedural generated content

https://godotdevelopers.org/forum/discussion/comment/20915/#Comment_20915

tnks

El domingo 08 de julio del 2018 a las 0721 horas, PerduGames escribió:

tnks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

You're welcome!
👋 Pax et bonum.
Jorge Javier Araya Navarro
http://www.esavara.cr

authors: PerduGames shackra

repo: PerduGames/SoftNoise-GDScript-


text:
ManualConfig.Add(IConfig config) does not add the validators.

Bench.Net 0.9.5.
I've a benchmark test where some parameters are set via [Config()] attribute and some are passed as a  parameter of the benchmark runner.
This setup does not allow to pass any validators into the benchmark. The BenchmarkConverter.GetFullConfig() method uses ManualConfig.Union() to merge the configs and it does not copies the validators at all.
Looks like a bug : )

@ig-sinicyn And yet again, thank you for very well described bug reports!

@adamsitnik , de nada:)

authors: adamsitnik ig-sinicyn

repo: PerfDotNet/BenchmarkDotNet


text:
🛑 Landing is down

In ee14196, Landing (https://thepetra.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Landing is back up in 0622fc2.

repo: PetraHQ/status


text:
Can't get results

Hello when I run the following code, I get the following error.
        $push = new Sly\NotificationPusher\Model\Push($adapter, $devices, $message);

        $pushManager->add($push);
        $pushManager->push();

        foreach($push->getResponses() as $token => $response) {
            var_dump($token);
            var_dump($response);
        }

Call to undefined method Sly\NotificationPusher\Model\Push::getResponses()

anyone try to sort this issue?

It looks like an autoloading configuration issue. Also, please be sure to use the latest version.

authors: muzafarali seesoe seyfer


text:
use multi-stage feature to minimize final image size

The development npm modules are not installed in the final image, the static files are copied over.

ping @eosrei

Interesting! I'll try it out. The only concern is this requires the newest build of Docker: https://github.com/moby/moby/releases/tag/v17.05.0-ce-rc1

I need to setup a VM to test since don't want to install a release candidate when I actually need Docker on this system. That being said, this isn't a solution yet. Bleeding edge features need some time to propagate. I'm closing #2 since you are aware of the issue with the RUN layer commands, the existing implementation works even if it is inefficient. No need to leave two PRs sitting open.

You may want to add a note to the readme about the strict Docker version requirements.
The Dockerfile is multi-stage. This feature requires Docker v17.05.0+.

If you build on GCB, no need of docker locally :)
On Fri, 19 May 2017 at 20:07 Brad Erickson notifications@github.com wrote:

You may want to add a note to the readme about the strict Docker version
requirements.
The Dockerfile is multi-stage. This feature requires Docker v17.05.0+.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Philmod/google-container-gulp/pull/3#issuecomment-302836454,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx8hg6s93gdK_-7fZBDvAxoTQkYitkjks5r7i6qgaJpZM4NDjso
.

Ah ha! Solves that problem. Haha!

authors: Philmod eosrei

repo: Philmod/google-container-gulp


text:
proof prints 5x5

remove 5x5 option from 135 on:

print services
film services
online ordering

em already removed from printed order form

@digijim need to remove from online ordering. rest done.


text:
🛑 Static Files is down

In 4619831, Static Files (https://static.phyrone.de/) was down:

HTTP code: 522
Response time: 15441 ms

Resolved: Static Files is back up in 4e93890.


text:
Edit and Clean non-functional files

This sits on top of #66 therefore merge against this branch to see the changes. This can be reviewed before and I will than rebase when #66 is merged.
Goals:

Clean CMakeLists.txt files
use Apache 2.0 license in all packages (this is mostly compatible with BSD used before in one package)
edit authors and maintainers lists
Add one license file and Contribution guidelines.

Became part of #71.


text:
Upgrade org.kordamp.maven:pomchecker-maven-plugin 1.10.0 -> 1.11.0

This PR contains the following updates:

Package
Type
Update
Change

org.kordamp.maven:pomchecker-maven-plugin
build
minor
1.10.0 -> 1.11.0

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade pomchecker-maven-plugin 1.10.0 -> 1.11.0

Yes, I think I forgot about one that I would also add a Renovate PR for, do you remember which one? Will do that in the following days.

Thx! I think it's these three:

org.kordamp.maven:pomchecker-maven-plugin (#1112)
jp.skypencil.errorprone.slf4j:errorprone-slf4j (#1111)
io.swagger:swagger-annotations (#1100)

Filed 3 PRs internally, will follow up there next week.

authors: Picnic-Bot Stephan202 rickie

repo: PicnicSupermarket/error-prone-support


text:
General question

@kenarsa
Hi, thank you very much for this awesome project. I'd very much like to get this up and working with my rpi zero w, but I wanted to ask some general questions first. I hope you don't mind me opening an issue for that purpose.
I did try to 'install' (clone) this project, but it failed twice (probably a network error). When I looked into the cause, I found out that my rpi was trying to download over 1,5GB of content when cloning. Is this normal?
Next, I wanted to ask you if it's possible to make a user-friendly installer. It's probably because I'm not an expert, but I think it's a little bit difficult to understand how to set this up and use it correctly. As an example of what I mean, you can take a look here (see file: 'Installer-with-debug.sh'). The advantage would be a faster installation, better set-up and ease-of-use.
If you are interested, I can help you create an installer (at least for the raspberry pi).

yes, we are aware of the size of the repo. we do have a long-term plan to fix it. I encourage any effort towards packaging pip, npm, maven. But it needs to work across platforms (RPI, Mac, Windows, etc) and also be part of repo so it is maintained. Let me think about this and figure out the best way to attack it.

@kenarsa
Thanks for your comment. It's good to hear you'll be working on the size of the repo soon.
You are right, the installer would work well with the Raspberry Pi but not on Mac & Windows. Unfortunately, I don't know how to create pip, npm or maven packages yet, but maybe someone else could help you with that.

authors: aceisace kenarsa

repo: Picovoice/Porcupine


text:
"Computer" Keyword file

Hello,
would it be possible to add a free to use Keyword file for "computer"?
Thanks slot
Carl

You can generate that for x86_64 using console.picovoice.ai

yes, I`ve done that, but that only works for 30 days... I need a solution that works without an expiration date...

yes, I`ve done that, but that only works for 30 days... I need a solution that works without an expiration date...

To be more specific... I would need that Keyword file for raspberry... Just saw that it is already available for Linux (but not for other platforms)
@kenarsa

authors: CobraCalle kenarsa

repo: Picovoice/porcupine


text:
YouTubePlayerView flickering

I have a ScrollView and inside it a YoutubePlayerView with Custom Play Button and Preview Image centered on it. This Player works just fine.
But further down the ScrollView i've got a horizontal RecyclerView inside a FrameLayout (so the Videos dont go outside of the screen). And the items of this RecyclerView consist again of a YouTubePlayerView with Custom Play Button and Preview Image centered on it, inside a CardView.
The problem now is that the Videos inside this "Gallery" are flickering. They just resize to a small window and go back to their normal size again.
My Adapter is nearly identical to yours and is used by a Fragment that also initializes the adapter identical to your example. Except that i also use a LinearSnapHelper.
The wierd thing is that the flickering is not visible when i use the setWebUi=true instead.
You can see the two states of the flicker in the attached images.

Hi, if you manage to replicate the problem on a small example problem I can take a look at it.

Hello,
i have figured out the problem now, it seems that the player keeps refreshing the UI when nested in two constraint layouts.
I removed one of those and it works just fine.

authors: JohScho PierfrancescoSoffritti


text:
ModuleNotFoundError: No module named 'netbox_ipcalculator'

ModuleNotFoundError: No module named 'netbox_ipcalculator'
Following the process and got this error.!  ;)

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/netbox/netbox/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/management/init.py", line 446, in execute_from_command_line
utility.execute()
File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/management/init.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/management/base.py", line 414, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/management/base.py", line 460, in execute
output = self.handle(*args, **options)
File "/opt/netbox/venv/lib/python3.10/site-packages/django/core/management/base.py", line 95, in wrapped
saved_locale = translation.get_language()
File "/opt/netbox/venv/lib/python3.10/site-packages/django/utils/translation/init.py", line 210, in get_language
return _trans.get_language()
File "/opt/netbox/venv/lib/python3.10/site-packages/django/utils/translation/init.py", line 65, in getattr
if settings.USE_I18N:
File "/opt/netbox/venv/lib/python3.10/site-packages/django/conf/init.py", line 87, in getattr
self._setup(name)
File "/opt/netbox/venv/lib/python3.10/site-packages/django/conf/init.py", line 74, in _setup
self._wrapped = Settings(settings_module)
File "/opt/netbox/venv/lib/python3.10/site-packages/django/conf/init.py", line 183, in init
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/opt/netbox/netbox/netbox/settings.py", line 658, in
raise ImproperlyConfigured(
django.core.exceptions.ImproperlyConfigured: Unable to import plugin netbox_ipcalculator: Module not found. Check that the plugin module has been installed within the correct Python environment.

You solved it?


text:
Allow for dynamic descriptions on customReward, customObjective, customRequirement

What does your feature do?
At the moment the requirement has no ability to display anything other than what is placed into the set name spot by the developer. Not the person making the quests. So it looks a bit off when your requirement cannot be explained to a user since it could be a vast array of things.
How would people use it?
This would just make the quests for intuitive for players.

Thanks for your request, but I'm a little confused. Are you asking for a description to be shown when selecting/creating the custom rew/obj/req, or when requirements are listed upon failing to meet them, per the picture you shared?

Sorry for the delay.  When we create an Addon for Quests, the admin will enter the npcdest curloc (Current location). However, when this is a requirement it shows to the user the command name. Others like Objectives you can change that display (Example:  See line 25 for example).  You can also set this on Rewards (Example: Line 25 - SetRewardName)

Compiling against the above commit will net you a setDisplay() method for the constructor of your custom requirement.
You'll also notice that setRewardName() has been deprecated in favor of a setDisplay() for custom rewards as well (functionally identical, but done for consistency).

You are so awesome. Thank you!!!

repo: PikaMug/Quests


text:
Spotify and Deezer no found

Hello, good day, Spotify and Deezer are not compatible or are not working in this latest update that I sent.

Hello ! Thank you for your interest in my project. Can you provide me with links that don't work? I can't reproduce errors with these sources.

authors: GonsanZ Pilgrimeru

repo: Pilgrimeru/Pilzic


text:
chore(binlog): use internal harbor image

use internal harbor image to avoid dockerhub pull rate limit.

/lgtm
/approve

authors: purelind wuhuizuo

repo: PingCAP-QE/ci