5.1.1 マージモデルと画像スタイル:  TypeError: 'bool' object is not iterable

I got error.  I change the merge model from andite/pastel-mix to andite/pastel-mix because of 401 Error(ref: Diffusersでモデルマージをする.  In fact, I got same error by the blog's code 😢 ).
Do you know how to fix it 🙏 ?

code: https://github.com/koshian2/ai-art-book/blob/master/local_codes/cp05/01_merge_embedding.py
execution environment: Google Colab(t4)

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-2-01daa371d555>](https://localhost:8080/#) in <cell line: 106>()
    104     plt.show()
    105
--> 106 main()

2 frames
[/usr/local/lib/python3.10/dist-packages/diffusers/pipelines/stable_diffusion/pipeline_stable_diffusion.py](https://localhost:8080/#) in __call__(self, prompt, height, width, num_inference_steps, guidance_scale, negative_prompt, num_images_per_prompt, eta, generator, latents, prompt_embeds, negative_prompt_embeds, output_type, return_dict, callback, callback_steps, cross_attention_kwargs, guidance_rescale)
    704             do_denormalize = [True] * image.shape[0]
    705         else:
--> 706             do_denormalize = [not has_nsfw for has_nsfw in has_nsfw_concept]
    707
    708         image = self.image_processor.postprocess(image, output_type=output_type, do_denormalize=do_denormalize)

TypeError: 'bool' object is not iterable

libraries(versions)
!pip install transformers
!pip install diffusers
!pip install compe

Collecting transformers
  Downloading transformers-4.31.0-py3-none-any.whl (7.4 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.4/7.4 MB 58.2 MB/s eta 0:00:00
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from transformers) (3.12.2)
Collecting huggingface-hub<1.0,>=0.14.1 (from transformers)
  Downloading huggingface_hub-0.16.4-py3-none-any.whl (268 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 268.8/268.8 kB 27.9 MB/s eta 0:00:00
Requirement already satisfied: numpy>=1.17 in /usr/local/lib/python3.10/dist-packages (from transformers) (1.22.4)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.10/dist-packages (from transformers) (23.1)
Requirement already satisfied: pyyaml>=5.1 in /usr/local/lib/python3.10/dist-packages (from transformers) (6.0.1)
Requirement already satisfied: regex!=2019.12.17 in /usr/local/lib/python3.10/dist-packages (from transformers) (2022.10.31)
Requirement already satisfied: requests in /usr/local/lib/python3.10/dist-packages (from transformers) (2.27.1)
Collecting tokenizers!=0.11.3,<0.14,>=0.11.1 (from transformers)
  Downloading tokenizers-0.13.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (7.8 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.8/7.8 MB 107.3 MB/s eta 0:00:00
Collecting safetensors>=0.3.1 (from transformers)
  Downloading safetensors-0.3.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 71.9 MB/s eta 0:00:00
Requirement already satisfied: tqdm>=4.27 in /usr/local/lib/python3.10/dist-packages (from transformers) (4.65.0)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from huggingface-hub<1.0,>=0.14.1->transformers) (2023.6.0)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from huggingface-hub<1.0,>=0.14.1->transformers) (4.7.1)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests->transformers) (1.26.16)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests->transformers) (2023.7.22)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/local/lib/python3.10/dist-packages (from requests->transformers) (2.0.12)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests->transformers) (3.4)
Installing collected packages: tokenizers, safetensors, huggingface-hub, transformers
Successfully installed huggingface-hub-0.16.4 safetensors-0.3.1 tokenizers-0.13.3 transformers-4.31.0
Collecting diffusers
  Downloading diffusers-0.19.2-py3-none-any.whl (1.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 12.7 MB/s eta 0:00:00
Requirement already satisfied: importlib-metadata in /usr/lib/python3/dist-packages (from diffusers) (4.6.4)
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from diffusers) (3.12.2)
Requirement already satisfied: huggingface-hub>=0.13.2 in /usr/local/lib/python3.10/dist-packages (from diffusers) (0.16.4)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from diffusers) (1.22.4)
Requirement already satisfied: regex!=2019.12.17 in /usr/local/lib/python3.10/dist-packages (from diffusers) (2022.10.31)
Requirement already satisfied: requests in /usr/local/lib/python3.10/dist-packages (from diffusers) (2.27.1)
Requirement already satisfied: safetensors>=0.3.1 in /usr/local/lib/python3.10/dist-packages (from diffusers) (0.3.1)
Requirement already satisfied: Pillow in /usr/local/lib/python3.10/dist-packages (from diffusers) (9.4.0)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from huggingface-hub>=0.13.2->diffusers) (2023.6.0)
Requirement already satisfied: tqdm>=4.42.1 in /usr/local/lib/python3.10/dist-packages (from huggingface-hub>=0.13.2->diffusers) (4.65.0)
Requirement already satisfied: pyyaml>=5.1 in /usr/local/lib/python3.10/dist-packages (from huggingface-hub>=0.13.2->diffusers) (6.0.1)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in /usr/local/lib/python3.10/dist-packages (from huggingface-hub>=0.13.2->diffusers) (4.7.1)
Requirement already satisfied: packaging>=20.9 in /usr/local/lib/python3.10/dist-packages (from huggingface-hub>=0.13.2->diffusers) (23.1)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers) (1.26.16)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers) (2023.7.22)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers) (2.0.12)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers) (3.4)
Installing collected packages: diffusers
Successfully installed diffusers-0.19.2
Collecting compel
  Downloading compel-2.0.1-py3-none-any.whl (29 kB)
Requirement already satisfied: diffusers>=0.11 in /usr/local/lib/python3.10/dist-packages (from compel) (0.19.2)
Requirement already satisfied: pyparsing~=3.0 in /usr/local/lib/python3.10/dist-packages (from compel) (3.1.0)
Requirement already satisfied: torch in /usr/local/lib/python3.10/dist-packages (from compel) (2.0.1+cu118)
Requirement already satisfied: transformers~=4.25 in /usr/local/lib/python3.10/dist-packages (from compel) (4.31.0)
Requirement already satisfied: importlib-metadata in /usr/lib/python3/dist-packages (from diffusers>=0.11->compel) (4.6.4)
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (3.12.2)
Requirement already satisfied: huggingface-hub>=0.13.2 in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (0.16.4)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (1.22.4)
Requirement already satisfied: regex!=2019.12.17 in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (2022.10.31)
Requirement already satisfied: requests in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (2.27.1)
Requirement already satisfied: safetensors>=0.3.1 in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (0.3.1)
Requirement already satisfied: Pillow in /usr/local/lib/python3.10/dist-packages (from diffusers>=0.11->compel) (9.4.0)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.10/dist-packages (from transformers~=4.25->compel) (23.1)
Requirement already satisfied: pyyaml>=5.1 in /usr/local/lib/python3.10/dist-packages (from transformers~=4.25->compel) (6.0.1)
Requirement already satisfied: tokenizers!=0.11.3,<0.14,>=0.11.1 in /usr/local/lib/python3.10/dist-packages (from transformers~=4.25->compel) (0.13.3)
Requirement already satisfied: tqdm>=4.27 in /usr/local/lib/python3.10/dist-packages (from transformers~=4.25->compel) (4.65.0)
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.10/dist-packages (from torch->compel) (4.7.1)
Requirement already satisfied: sympy in /usr/local/lib/python3.10/dist-packages (from torch->compel) (1.11.1)
Requirement already satisfied: networkx in /usr/local/lib/python3.10/dist-packages (from torch->compel) (3.1)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.10/dist-packages (from torch->compel) (3.1.2)
Requirement already satisfied: triton==2.0.0 in /usr/local/lib/python3.10/dist-packages (from torch->compel) (2.0.0)
Requirement already satisfied: cmake in /usr/local/lib/python3.10/dist-packages (from triton==2.0.0->torch->compel) (3.25.2)
Requirement already satisfied: lit in /usr/local/lib/python3.10/dist-packages (from triton==2.0.0->torch->compel) (16.0.6)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from huggingface-hub>=0.13.2->diffusers>=0.11->compel) (2023.6.0)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.10/dist-packages (from jinja2->torch->compel) (2.1.3)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers>=0.11->compel) (1.26.16)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers>=0.11->compel) (2023.7.22)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers>=0.11->compel) (2.0.12)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers>=0.11->compel) (3.4)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.10/dist-packages (from sympy->torch->compel) (1.3.0)
Installing collected packages: compel
Successfully installed compel-2.0.1

Please change the model repository as follows.

Before : andite/pastel-mix
After : JamesFlare/pastel-mix

Looks like the PastelMix link has changed.
https://huggingface.co/JamesFlare/pastel-mix

After changing to amesFlare/pastel-mix , same error occurs....


Can't create issues - "Creating issue failed: Issues are disabled for this repo" although enabled

Extension version: GHPRI Nightly, v2021.3.42303
VSCode Version: Codespaces
Version: 1.55.0-insider
Commit: c185983a683d14c396952dd432459097bc7f757f
Date: 2021-03-30T12:43:45.267Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.82 Safari/537.36
OS: Windows 10, Chrome browser

Steps to Reproduce:

Create a Codespace on https://github.com/bamurtaugh/communication-services-web-calling-hero

Attempt to create an issue

Fails with "Creating issue failed: Issues are disabled for this repo"

Check my repo, issues are enabled. However, I noticed they're disabled for the upstream from which I forked https://github.com/burkeholland/communication-services-web-calling-hero (although issues are enabled for the upstream from which Burke forked, https://github.com/Azure-Samples/communication-services-web-calling-hero)

Here are my remotes when using git remote -v:

I ran into this as the "owner" of the fork, and a collaborator I added to the fork also experienced this same behavior.
I saw https://github.com/microsoft/vscode-pull-request-github/issues/1517, which seems to be related here.

We try to be smart and when a repo is a fork, we figure that you are most likely to want to create an issue on the upstream.
Looks like we should fallback to the fork for creating the issue if we encounter this error.

@alexr00 What if we want to edit issues onto the fork/origin repo? Can we configure that somewhere? My Fork is the continuation of a disbanded project.

@nathansegers we should also add a way for you do that :)

I have a similar issue, but slightly different symptom. Issues are enabled on the origin repo, I forked that repo and enabled issues on my own fork. If I add an issue to my fork via GitHub it does not appear in VSCode. If I add an issue via VSCode it logs under the origin, not my fork.

@alexr00 Did we fix this issue?

Did anything come of this?  My fork will stay independent of the upstream and I want my issues create in my fork (origin), not in upstream.

If your fork is always going to remain independent of the upstream, then you can remove upstream from the setting githubPullRequests.remotes to solve this.


Add Curies Support

Hi. Thought I'd have a stab at adding Curies support to your excellent library. The RFC is a little vague on whether the curies should be a JSON array or not (it just describes the curies relations as a 'set') but the canonical examples seem to include it as an array, even if it's a single item.

Coverage increased (+3.8%) to 85.987% when pulling 4fc225dfd8f21375d1ae736dd6192584e855a6fc on justasitsounds:master into 08af269b06ba828cf9b3177a3667b8c868269f3d on nvellon:master.


Add guix.scm build target

Thanks!

@Millak I'm going to work on setting up the build to optionally ignore the submodules and use system libraries, to help unbundle things. I think this is basically as simple as adding some if statements around the ExternalProject_Add incantations in the CMakeLists.txt, modulo a few other tweaks.

@ekg That would be really helpful for the Bioconda distribution of freebayes.  I've hacked together a very ugly build that has worked, but being able to rely on system libraries will greatly simplify the build and increase update frequencies.


Automatically Target BOSH in hook scripts

As it stands, we are relying on the hook scripts to use the bosh CLI properly and we give them an alias name.  This is sub-optimal.
I'd much rather hook scripts operate connected to BOSH already, via the environment variables:

BOSH_ENVIRONMENT - Director URL
BOSH_CA_CERT - Contents of or path to CA that signed the director's certificate
BOSH_CLIENT_ID - UAA Client ID for authentication
BOSH_CLIENT_SECRET - UAA Client Secret for authentication

We can support this today without ripping all the alias-centric guts out of Genesis itself.  The hooks are more durable and long-lived than the genesis script anyway.
The gist of the idea is this:
spruce json ~/.bosh/config  | jq -r '.environments[] | select(.alias == "lab")'
{
  "alias": "lab",
  "ca_cert": "-----BEGIN CERTIFICATE-----\n... etc ...\n-----END CERTIFICATE-----\n\n",
  "password": "sekrit",
  "url": "https://<IP_ADDRESS>",
  "username": "admin"
}

In general, we conflate users/clients and make sure that the admin user/client have the same password/secret, so this should work in the short-term.
The primary benefit is that it allows hook scripts to just run bosh ... if they need access to the deploying BOSH director (for example, to look up dynamic IPs, or run errands)

Fixed in #278


[Feature] Store joined players on Bungee

What type of feature is it?

[ ] New Command
[X] Config option
[X] Other

Describe your feature
I have the use-case for my network where we want global (Bungee) join and leave messages, and NONE on the Spigot side. So this would go for welcome messages as well. In the plugin's current state, it does not support welcome messages on the Bungee side. So I would like to request the ability for the plugin to store the joined players' UUID's in BungeeCord's RocketJoin directory (something to the effect of plugins/RocketJoin/players.csv/dat/other/etc).
This will allow the RocketJoin-Bungee WrappedPlayer https://github.com/Lorenzo0111/RocketJoin/blob/d245c74d16e3249ceb93f8508ce759f608034b97/bungeecord/src/main/java/me/lorenzo0111/rocketjoin/audience/WrappedPlayer.java#L35-L37 to check for existence in that datastore of previously joined UUIDs while in the area of https://github.com/Lorenzo0111/RocketJoin/blob/d245c74d16e3249ceb93f8508ce759f608034b97/bungeecord/src/main/java/me/lorenzo0111/rocketjoin/listener/JoinListener.java#L58-L61
To determine if the non-disabled welcome message should be broadcast.
Thanks and have a great day.

Added


nonce attribute should be added only in production?

What version of HonoX are you using?
0.1.16
What steps can reproduce the bug?
app/routes/_middleware:
import { createRoute } from 'honox/factory'
import { secureHeaders, NONCE } from 'hono/secure-headers'

export default createRoute(
  secureHeaders({
    contentSecurityPolicy: {
      scriptSrc: [NONCE],
      styleSrc: [NONCE]
    }
  })
)

app/routes/_renderer:
import { jsxRenderer } from 'hono/jsx-renderer'
import { Script } from 'honox/server'

export default jsxRenderer(({ children }, c) => {
  return (
    <html lang="en">
      <head>
        <Script src="/app/client.ts" async nonce={c.get('secureHeadersNonce')} />
      </head>
      <body>{children}</body>
    </html>
  )
})

Run the dev server locally:
npm run dev

What is the expected behavior?
The browser does not throw an error.
What do you see instead?
Throwing the error:

This is because the script element importing /@vite/client has no nonce.

Additional information
I think it does not need nonce in local development. <Script /> should have it only in production.

I think this is not a Script component issue, but rather "how to apply secureHeaders middleware in production and development environments?"
I think it's a similar issue to this, but I don't want to deal with it in such a complicated way.
https://github.com/vitejs/vite/issues/11862
It would be good to have default values (automatically distinguishing between development and production environments and appropriately selected values) that can be easily set by the user.
Prerequisite
This script element is 'sha256-skbsb8aC0J3t64Itv3lSwl9/M7LOJglCR99BjSMntzI='.
<script>import("/@vite/client")</script>

Managing with the current honox specifications
None of these are very pretty, but within the current specification they can be specified as follows.
Only in the development environment, add a setting
"'sha256-skbsb8aC0J3t64Itv3lSwl9/M7LOJglCR99BjSMntzI='" may be exported from honox.
import { createRoute } from "honox/factory";
import { secureHeaders, NONCE } from "hono/secure-headers";

export default createRoute(
  secureHeaders({
    contentSecurityPolicy: {
      scriptSrc: [
        ...(import.meta.env.PROD
          ? []
          : ["'self'", "'sha256-skbsb8aC0J3t64Itv3lSwl9/M7LOJglCR99BjSMntzI='"]),
        NONCE,
      ],
    },
  })
);

Only in the production environment, use NONCE
Set secureHeaders only in the production environment.

@usualoma Thank you for your valuable input.

I think this is not a Script component issue, but rather "how to apply secureHeaders middleware in production and development environments?"

AH, yes. You are right. I agree it!

None of these are very pretty, but within the current specification they can be specified as follows.

Cool. Or super simply, if we can allow it not to be enabled in local development env, we can turn on CSP completely, as you said at the bottom of your comment:
import { createRoute } from 'honox/factory'
import { secureHeaders, NONCE } from 'hono/secure-headers'

export default createRoute(
  secureHeaders({
    contentSecurityPolicy: import.meta.env.PROD
      ? {
          scriptSrc: [NONCE]
        }
      : undefined
  })
)

Ah yes, that's good.
  secureHeaders({
    contentSecurityPolicy: import.meta.env.PROD
      ? {
          scriptSrc: [NONCE]
        }
      : undefined
  })

This can be resolved by the above way.


MSL: Unflatten complex composite input variables.

There are a few missing cases for when the implementation un-flattens composite types.
Particularly array-of-array inputs in tessellation shaders.

Fixed as part of UE4 merge.


Fix Markdown format - remove 4 spaces before code block

Readme + docs/

Why?  This makes reading the plain-text documents much more difficult?

Because on the Github is formatting broken and when I copy block of the code, i have 4 spaces before. I dont think, that is more difficult to read in plain text. You can use four spaces in the code block, but it doesnt work in the lists.

Not trading plain-text readability for saving 4 spaces.


Unable to run the pod delete experiment in LinkerD (emojivoto)

What happened: I tried running the generic chaos experiments in linkerd, specifically in emojivoto which the sample application provided by linkerd itself. Starting with pod-delete, the experiment is taking around 3 min for completion and still resulting in an unsuccessful run of the experiment. Tried deleting the exact pod (voting, which I am working on) to see if it is taking time to recreate but that's not the case too.
What you expected to happen: The experiment should be successful without any issue and in the specified time being.
How to reproduce it (as minimally and precisely as possible): Logs for the experiment pod

kubectl logs -f pod-delete-mvy8mn-9f2pz -n emojivoto
W0807 03:16:46.228093       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2020-08-07T03:16:46Z" level=info msg="[PreReq]: Getting the ENV for the  experiment"
time="2020-08-07T03:16:46Z" level=info msg="[PreReq]: Updating the chaos result of pod-delete experiment (SOT)"
time="2020-08-07T03:16:46Z" level=info msg="The application informations are as follows" Ramp Time=0 Namespace=emojivoto Label="name=voting"
time="2020-08-07T03:16:46Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (pre-chaos)"
time="2020-08-07T03:16:46Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-08-07T03:19:46Z" level=error msg="Application status check failed due to Unable to get the pod, err: \n"

Logs for runner pod

kubectl logs -f chaos-runner -n emojivoto
W0807 03:16:37.874529       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0807 03:16:37.881911       1 runner.go:21] Experiments List:  [pod-delete]   Engine Name:  chaos   appLabels :  name=voting   appKind:     Service Account Name:  pod-delete-sa Engine Namespace:  emojivoto
I0807 03:16:38.686628       1 experimentHelpers.go:46] Getting the ENV Variables
I0807 03:16:39.089694       1 runner.go:50] Preparing to run Chaos Experiment: pod-delete
I0807 03:16:39.488341       1 configMapUtils.go:17] Validating configmaps specified in the ChaosExperiment & ChaosEngine
I0807 03:16:39.886848       1 secretsUtils.go:18] Validating secrets specified in the ChaosExperiment & ChaosEngine
I0807 03:16:40.088438       1 hostFileVolumeUtils.go:25] Validating HostFileVolumes details specified in the ChaosExperiment
I0807 03:16:50.103869       1 runner.go:66] Started Chaos Experiment Name: pod-delete, with Job Name: pod-delete-mvy8mn

cc @ispeakc0de @uditgaurav


Return error on AcquireError in uploader

Currently we have the following code in the uploader:
let permit_guard = {
    let _guard = ctx.protect_zone();
    Semaphore::acquire_owned(self.concurrent_upload_permits.clone()).await
};

We don't handle the case where the acquire_owned returns an AcquireError which seems weird to me. I'm not super familiar with this kind of stuff so not sure how to report that as a bug or not.

@fulmicoton the AcquireError is raised if the semaphore has been closed. I think we can propagate the error.


Fix load theme sections

Fixes a Theme Editor issue where JS errors were triggered and Section JS failed to reload after modifying section setting, adding a block, reordering, or any other event that triggers shopify:section:load.

Fixed null container and type values with a new method to get the section type inside the Theme Editor #34
Added a new _onLoad method to trigger the onLoad of Section js when the shopify:section:load event is fired #37

This approach should replace the open PR #36

@jonathanmoore data-theme-editor-section-36545666210 is only intended for internal use for the editor and should not be relied on for external scripts. The editor team does not guarantee it won't change.
I recommend we still for the hard-coded data-attributes.

@t-kelly Going through and testing a bit more it does seem like typo PR did the trick.  The first pass of testing the typo PR it didn't seem to work because of issues I had in the theme's code.
https://github.com/Shopify/theme-scripts/pull/36


Feature request handling RECONNECT

thanks for this great package.
it would be awesome if this package also has a reconnect feature.

This library is just to port the protoo client similar to javascript check here
So building an automatic reconnect into this library would steer it away from being a port of js proto client.
I think the intended way to implement reconnect is to just listen for peer.on('close' ...) and re-create the connection.


merge from template-sync/template-arlac77-github

.github/workflows/ci.yml

chore: (jobs.test-node.steps)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.807%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
436

Relevant Lines:
461

💛  - Coveralls


Requires react-native >=0.36?

It would be nice to state somewhere that this requires react-native version at least 0.36 (or whenever was overflow: "scroll" introduced). On react-native 0.32, you get the infamous red box screen stating that View doesn't support overflow: "scroll", only "visible" or "hidden".

Replacing "scroll" by "hidden" in TabBar.js on line 20 fixes the issue. But, I'm guessing this'll have some side effects?

@jankalfus Hey, yeah, this is noted in release notes, but I should add to README too. PR welcome.

@satya164 Where are the release notes located?

https://github.com/react-native-community/react-native-tab-view/releases

Ah, right. Sorry, it's late :D Here's the PR: #67


Fix linkage for two functions in clang backend

Small fix for two functions defined in clang backend header that cause linker errors when compiling more than one translation unit.

Whoopsie, thanks! :)


feat: add dropdown menu component

add dropdown menu component. this component will be used for user/login menu

Pushed several tweaks:

Used --radix-dropdown-menu-content-available-width and --radix-dropdown-menu-content-available-height to ensure that the menu doesn't extend outside the viewport. Added a vertical scroll in case it needs one.

Rearranged some styling, removed .contentWrapper which sounded like a wrapper of the .content element rather than a wrapper of the menu item content.

Made the item focus effect more pronounced (it doesn't match the reference design, but it's actually visible now). Changed it from :focus-visible to :focus, :hover since sometimes Radix doesn't add focus state to hovered elements.

Changed the trigger type to ReactElement instead of ReactNode, since it's rendered asChild and Radix cannot render plain text nodes with that attribute since it's indicates that props are passed to the child, and text nodes don't accept props.

Added a comment explaining onCloseAutoFocus={(e) => e.preventDefault()}

Removed redundant property spreading from MenuItem.

In Radix docs they mention that components must forward ref:
https://www.radix-ui.com/primitives/docs/guides/composition#your-component-must-forward-ref
I can't say that I fully understand why and when. everything seems to work fine here without it.

In Radix docs they mention that components must forward ref:
https://www.radix-ui.com/primitives/docs/guides/composition#your-component-must-forward-ref
I can't say that I fully understand why and when. Everything seems to work fine here without it.

the same. I didn't see this in documentation, but component actually works without any issues.
also, RadixDropdownMenu.Root does not accept ref property. RadixDropdownMenu.Content and RadixDropdownMenu.Trigger does, but it is not clear where should we forward ref from root component


Jekyll Integrated version

This page only has this single event , that's why it looks empty

Solved


Error on FunctionType Conversion

i'm getting the following error: TypeError: Property parameters expected type of array but got object when trying to convert some flow files. i've narrowed it down to the following code
// @flow

export type RolesProps = {
  roles: Array<Role>,
  activeRoles: Array<string>,
  accountGuid: string,
  setError: (string) => void,
  setTooltip: (string) => void,
}

i think it is related to this line in the plugin: https://github.com/Kiikurage/babel-plugin-flow-to-typescript/blob/master/src/converters/convert_flow_type.ts#L330
commenting out those two function definitions results in a successful compilation

Hi @TomPridham
it looks issue is already fixed in master, but the version in npm is outdated
as a workaround, you can try using my fork  @zxbodya/babel-plugin-flow-to-typescript (latest version there should be the same as current master)
@Kiikurage can you publish a new version to npm?

great, that worked. thanks! should i close this or wait until a new version has been published?

I ran into the same problem today with this test code:
type xType = {|
  data: number,
  onClick: (e: string) => void // this is the problem line
|}


Initializing Header Stacks

Personnel

[x] Owner: @vgurevich
[x] Supporters: @mbudiu-vmw

Design

[ ] Document: See below

Implementation

[ ] p4-spec:
[ ] p4c:

Process

[ ] LDWG discussed:
[ ] LDWG approved:
[ ] Merged into p4-spec:
[ ] Merged into p4c:

Hello,
I was wondering if it is possible to initialize header stacks, and if yes, how.
Obviously, we can initialize headers using tuples:
vlan_tag_t vtag = { 3w5, 1w0, 12w100, 16w0x0800 };

However, it is not clear what to do with a stack. I tried a tuple of tuples, which didn't go well:
vlan_tag_t[2] vtag = {
    { 3w5, 1w0, 12w100, 16w0x0800 },
    { 3w5, 1w0, 12w100, 16w0x0800 }
};

The compiler said: "Cannot unify Tuple(2) to header vlan_tag_t[]"
I tried to flatten the initializer, by removing the internal braces. In that case the compiler could not unify Tuple(8) to vlan_tag_t[].
Casting didn't work either.
Is there any kind of tuple that can be unified with a header stack?
Thanks,
Vladimir

There are no array initializers, you have to initialize each element by hand.

This is definitely an inconsistency, (since other compound types can be initialized),  but the one we can live with. Something for the future?

Let's punt this until after the release. It would be good to have, but the
interaction with next and last could be subtle. And we wouldn't be able
to initialize stacks with holes...
On Wed, May 10, 2017 at 8:16 PM, Vladimir Gurevich<EMAIL_ADDRESS>
wrote:

This is definitely an inconsistency, (since other compound types can be
initialized), but the one we can live with. Something for the future?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/p4lang/p4-spec/issues/198#issuecomment-300671299, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABwi0i3LpsPNcsWksDyz58WkCBhoy4qaks5r4n2GgaJpZM4NXb-9
.

Let's implement something.

In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open it in the future if there is interest in resurrecting it.


Possible bug with the min-lines option

Describe the bug
This is not a bug report but a report of dead code which might create a potential bug (although I am not sure of that).
In detector.ts clones.filter() is called but not assigned not returned. Array.filter() does not modify its arguments. Instead it creates a new array, i.e. clones.filter() is a noop here. I think this is probably not intended.
To Reproduce
I cannot reproduce because I'm not sure what the bug is (if there is any).

Excellent! Thank you for deep dive in the code.
It is really dead code and I've seen the result in a report with one line of duplication.

fixed in<EMAIL_ADDRESS>


Various fixes for aarch64

Why?
I was trying to run parca-agent on my new work laptop which has Fedora 39 in a VM on a mac host, i.e. aarch64. I encountered various problems trying to do so, which this PR fixes.
Probably the reason nobody has fixed this before is that Fedora is building their OS using some special compiler flags for security hardening.
Note that this PR contains two logically distinct changes in separate commits (plus one commit for a minor logging fix).
What?
Please see the individual commit messages for details.
How?
Please see the individual commit messages for details.
Test Plan
parca-agent works on my machine now and generates reasonable-looking output.

 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.

It fixes Ruby failure on arm64 🙌🙌 There are still some more issues we need to track down for some Python versions.

Thanks for the quick review. I pushed a new version which should get rid of the unused function warning on x86.


Handling of null values in uniqueKeys

Environment
Trying to implement uniqueKeys in a separate project.
How can I help you today?
I'm not clear on the handling of null or non-existing values with the uniqueKeys. Reading https://json-everything.net/json-schema#the-uniquekeys-keyword it is not clear to me:

equality of null values
equality of the placeholder values for a non-existing locations

Given this schema:
Schema:
{
  "$schema": "https://json-schema.org/draft/2019-09/schema",
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "a": {
        "type": "string"
      },
      "b": {
        "type": "string"
      }
    }
  },
  "uniqueKeys": [
    "/b"
  ]
}

And considering this data:
Data:
[
  {"a": "A", "b": null},
  {"a": "X", "b": "B"},
  {"a": "A", "b": null},
]

The resulting collection after evaluating the JSON paths could to be:
[
  {"b": null},
  {"b": "B"}
  {"b": null}
]

Are the two {"b": null} considered equal?
Concerning the placeholder for non-existant values, if the uniqueKeys constraint was defined as "uniqueKeys": ["/a","/c"] the resulting collection after evaluating the JSON paths could be:
[
  {"a": "A", "c": <placeholder>}, // or perhaps {"a": "A"}?
  {"a": "A", "c": <placeholder>},
]

Are the two {"a": "A", "c": <placeholder>} considered equal?
And finally, if the uniqueKeys constraint was defined as "uniqueKeys": ["/c"] the resulting collection after evaluating the JSON paths could be:
[
  {"c": <placeholder>}, // or perhaps {}?
  {"c": <placeholder>},
]

Are the two {"c": <placeholder>} considered equal?
Thank you for your time :)

The placeholder is mentioned specifically because a naive implementation of this would just use null to represent a missing value.  However JSON null is a valid value distinct from a key missing.  To that end, missing keys need to be represented in another way.
In my implementation, which you can play with here, the placeholder does count as a value (just that it's hidden), so your
[
  {"a": "A", "c": <placeholder>}, // or perhaps {"a": "A"}?
  {"a": "A", "c": <placeholder>},
]

would not be considered unique, and validation would fail.

To summarize: all placeholder values are considered to be equal with one another and all null values are considered to be equal with one another. Thanks, that clears things up!


library resolution does not work on linux

As reported on Reddit, for me this openscad language server does not resolve modules that are contained in libraries, whereas dzhu's language server does find my libraries just fine.
I am running on linux, my libraries are installed in the built-in location $HOME/.local/share/OpenSCAD/libraries/
I do not normally use OPENSCADPATH, however, I also tried setting this and it could still not resolve the modules in libraries.

@Lenbok Is it work if included file is in same directory?

Yes, it does seem to work for finding definitions in files that are in the same directory, or found in subdirectories relative to the current file.

Yes, it does seem to work for finding definitions in files that are in the same directory, or found in subdirectories relative to the current file.

So the problem is that the directory of the libraries cannot be found correctly, I will check it.

BTW, I was trying to see in the code where to put some debugging (not that I am familiar with rust), but the naming of the library location functions are inconsistent with the terminology in the descriptions at https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Libraries:

user_library_location should probably be called built_in_library_location
env_library_locations should probably be called user_defined_library_locations

It's a minor thing, but it helps to be consistent when describing bugs etc.

BTW, I was trying to see in the code where to put some debugging (not that I am familiar with rust), but the naming of the library location functions are inconsistent with the terminology in the descriptions at https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Libraries:

user_library_location should probably be called built_in_library_location
env_library_locations should probably be called user_defined_library_locations

It's a minor thing, but it helps to be consistent when describing bugs etc.

That is a good suggestion, and I don't have a Linux development environment, may not be able to fix this soon, if you can fix it, please submit a PR.

@Lenbok I don't know why it doesn't work on Linux, I added the log to print the search paths to std out, you can try again to see if your library path is included.

I had to change your log_to_console function to send to stderr, since emacs only logs that (I guess stdout is just used for those servers using stdio), but I see it does have my library path:
[server] start sucess
[server] search paths:
[server] file:///home2/len/.local/share/OpenSCAD/libraries/
[server] file:///usr/share/openscad/libraries/

My built-in library folder contains libraries such as:
len@tron:openscad-LSP master(+4/-4)+  ls -l /home2/len/.local/share/OpenSCAD/libraries/
total 84
drwxrwxr-x  2 len relaxo  4096 May 24  2018 bezier
drwxrwxr-x  9 len len     4096 Apr  7 12:17 BOSL2
drwxrwxr-x  2 len relaxo  4096 Mar 10  2018 etc
-rw-r--r--  1 len relaxo  4016 Jan 22  2014 gear_rack.scad
drwxrwxrwx  2 len relaxo  4096 May 20  2017 Knurled_Surface
drwxr-xr-x  3 len relaxo  4096 Nov  6  2021 Lenbok_Utils
drwxrwxr-x  4 len len     4096 Sep 24  2019 list-comprehension-demos
drwxr-xr-x  6 len relaxo  4096 Mar 12  2014 MCAD
drwxrwxr-x  2 len relaxo  4096 Mar 10  2018 node_modules
drwxrwxr-x 11 len len     4096 Apr  3 16:36 NopSCADlib
-rw-r--r--  1 len relaxo 17668 Jan 22  2014 parametric_involute_gear_v5.0.scad
drwxrwxr-x  2 len relaxo  4096 Mar 22  2017 Parametric_Molds
drwxrwxr-x  3 len len     4096 Oct  9  2019 pulleys
drwxrwxr-x  5 len relaxo  4096 Feb 13  2016 relativity.scad
lrwxrwxrwx  1 len relaxo    50 May 11  2011 ruler.stl -> /home/len/objects/thingiverse/ruler-6823/ruler.stl
drwxrwxr-x  3 len relaxo  4096 May  3  2017 scad-utils
drwxrwxr-x  3 len relaxo  4096 Jul 12  2014 syvwlch
drwxrwxr-x  3 len relaxo  4096 Mar  7  2018 threads

Is it also possible to log when the server tries to search within the library path?

@Lenbok Your include statement is like <BOSL2/somthing> or not include the subdirectory "BOSL2"?

Yes, my include statement includes the library name.
I added logging at 1146 to print inc and also at 1184 to log the value of text, but neither log statement gets triggered.

Ahhh, I narrowed it down, include is working, but use is not. I remember seeing something in the tree-sitter-openscad about treating those as separate node types, and checking now I see 0.3.0 you are using does do that (I also see there is now a 0.4.0). So there needs to be handling of use_statement node kind. I changed the handling at:
https://github.com/Leathong/openscad-LSP/blob/ba27b42c1d45cb2a3b55e743a17f222ef26b3ab4/src/main.rs#L1062
to:
                    match node.kind() {
                        "use_statement" | "include_statement" => {
                            code.get_include_url(&node).map(|inc| {
                                include_vec.push(inc);
                            });
                        }
                        _ => (),
                    }

(remember, I don't know rust, I just copied the matching structure that was in the next section). And now my modules are being found! If you want I can open a PR, or you can just make the fix yourself.
Now that is solved, the other thing I noticed was that in dzhu's implementation, autocomplete candidates contain several extra candidates, both prefix matches and fuzzy matches (e.g. typing poly can suggest a modules named test_polyhole()). At least in emacs, the prefix matches come before the substring matches. Actually maybe dzhu's is returning all possible modules/variables, leaving the matching to emacs, while yours is doing some server side filtering?

@Lenbok I fixed it yesterday

Actually maybe dzhu's is returning all possible modules/variables, leaving the matching to emacs, while yours is doing some server side filtering?

Yes, I did not return all symbols.

@Lenbok I changed the server's behavior, just return all symbols.

Nice job, thanks!


Web example

Description
I created an example project for the web. It's live at https://robertherber.github.io/react-native-device-info/. It serves both the purpose of verifying that the web implementation is working well and also obviously a good example for starting using the library. I uses the default Expo TypeScript setup as a base.
I think somebody with proper repository rights should publish it to https://react-native-community.github.io/react-native-device-info/ or similar, and I'm thinking automate it with the publishing of new packages :) Just update the homepage in package.json and run yarn deploy.
Sorry for the heavy pull request - it builds on top of #933! The example project is the only difference.
Compatibility

OS
Implemented

Web
✅

Checklist

[x] I added a new Example project for web

sorry this is sitting still guys - been busy with other things but it won't be forgotten!


cannot get IMU data on a Mac OS platform

Hello, recently I tried to develop on a D435i, unfortunately, I could not obtain IMU data(including accel and gyro) in realsense-viewer(Mac version), although RGB and depth images could be displayed normally.
It could be sure that the D435i itself did not have any problems as the IMU data could be obtained normally on a windows10 platform.
Then I tried the API of python on the Mac platform, the codes are as follows:
`import pyrealsense2 as rs
pipeline = rs.pipeline()
config = rs.config()
config.enable_stream(rs.stream.accel)
config.enable_stream(rs.stream.gyro)
pipeline.start(config)
try:
while True:
frames = pipeline.wait_for_frames()
accel = accel_data(frames[0].as_motion_frame().get_motion_data())
gyro = gyro_data(frames[1].as_motion_frame().get_motion_data())
print("accelerometer: ", accel)
print("gyro: ", gyro)
finally:
pipeline.stop()`
I got an error showed that 'RuntimeError: Frame didn't arrived within 5000'.  I suspected that there's no accel and gyro data in the stream.

Hi @fanofpal
This is a limitation of the SDK, documented in release notes and support matrix document.
The source of the issue is that Mac OS is preemptively locking any new HID device preventing Linux-style access.
There is good progress re-writing IMU backend using Apple-specific APIs, but it is not complete yet.

@dorodnic Thank you for the reply!

Hi @fanofpal   The new librealsense version 2.42.0 has introduced IMU support for MacOS.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.42.0


ci/test/scaffolding: fix hybrid operator dependency resolution

Description of the change:
Updates scaffolding for hybrid operator images so that branch resolution in go.mod is not required.
Motivation for the change:
Since -mod=vendor is enabled, Go is unable to resolve a psuedo-version for the operator-sdk dependency. Since we use a replace line for operator-sdk anyway, we can set the operator-sdk require version to v0.0.0

/lgtm

/cherry-pick release-4.3

/cherry-pick release-4.3


Path aliases

If I have several independent microservices is it somehow possible to alias them to different paths on a domain?
Example:
first-microservice => https://example.com/v1/first-microservice
second-microservice => https://example.com/v1/second-microservice
I've tried:
{
  "name": "first-microservice",
  "stages": {
    "production": {
      "domain": "example.com",
      "path": "/v1/first-microservice"
    }
  }
}

and
{
  "name": "second-microservice",
  "stages": {
    "production": {
      "domain": "example.com",
      "path": "/v1/second-microservice"
    }
  }
}

but, it does not seem to work.

Multiple on a domain don't work quite yet, but it's on the list. Dup of #106


backend: remove redundant nil checks around loop

What is the purpose of this change?
It simplifies the code by removing unnecessary nil checks.
Was the change discussed in an issue or in the forum before?
No, the change is cosmetic.
Checklist

[x] I have read the contribution guidelines.
[x] I have added tests for all changes in this PR if appropriate.
[x] I have added documentation for the changes if appropriate.

[x] I'm done, this Pull Request is ready for review :-)

Good catch @teresy

Thank you very much - looks good to me :-)


The handshake operation timed out (poloniex)

Hello I am using this bot with poloniex (I am on the latest version via git pull). I am getting this ssl handshake error with various requests and it appears that the bot is not working properly. Is this a backend issue or a bot issue? BTW: I also used the search for "The handshake operation timed out" before posting this issue. If there is any code that needs to be written, I'm pretty good with JS.
2017-10-12 10:46:35 Error <urlopen error ('_ssl.c:574: The handshake operation timed out',)> Requesting returnActiveLoans
2017-10-12 10:43:52 Error <urlopen error ('_ssl.c:574: The handshake operation timed out',)> Requesting returnLoanOrders
2017-10-12 10:41:10 Error <urlopen error ('_ssl.c:574: The handshake operation timed out',)> Requesting returnTicker

Hey David. It's all python. This error typically indicates issues between you and the exchange. Make sure you can resolve api.poloniex.com and that you don't have any proxy's in between. Also make sure your SSL certificates are up to date. You can test like this:
$ openssl s_client -connect api.poloniex.com:443

daxxog$ openssl s_client -connect api.poloniex.com:443

here is the output of the openssl command you posted:
CONNECTED(00000003)
depth=1 C = BE, O = GlobalSign nv-sa, CN = AlphaSSL CA - SHA256 - G2
verify error:num=20:unable to get local issuer certificate
---
Certificate chain
 0 s:/OU=Domain Control Validated/CN=*.poloniex.com
   i:/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2
 1 s:/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2
   i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIE1DCCA7ygAwIBAgISESFfq81vFEmL6UBYWDM4pSNXMA0GCSqGSIb3DQEBCwUA
MEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIwIAYD
VQQDExlBbHBoYVNTTCBDQSAtIFNIQTI1NiAtIEcyMB4XDTE1MTIwNDE5NTA0OVoX
DTE4MTIwNDE5NTA0OVowPDEhMB8GA1UECxMYRG9tYWluIENvbnRyb2wgVmFsaWRh
dGVkMRcwFQYDVQQDDA4qLnBvbG9uaWV4LmNvbTCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBALmPyvmC3dsgxxZDGVaPZ2xhNpuoEVwF3Uwjh/zg4qa5qoEY
opCI+9FQML78Byn2EwwARVb7iF/kVHYGuxaT2QOCQ36Lk39DMUTWAzaprly8UY7j
wzSBhUZk6oQpH9/POl+sMNy8aUixby1hlxV0K7WYSyBPC9MbMqTMVQ9o1onj7/pf
KVHGE5eRyQ8WuHPusBzQSdqbft5Q+QjjMiMKTjXXYczew7uVFObzU6cNTIBbLQvU
fzJ8xd8eSmTgBjKgposrmliIwwjKFYMaSCpDByhO3qc96H/+nyeKmDelyKM0WNT9
UPLeHxGFh2fZmfWcyV+7IgSP93zukbNU/aN8zNkCAwEAAaOCAb4wggG6MA4GA1Ud
DwEB/wQEAwIFoDBJBgNVHSAEQjBAMD4GBmeBDAECATA0MDIGCCsGAQUFBwIBFiZo
dHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzAnBgNVHREEIDAe
gg4qLnBvbG9uaWV4LmNvbYIMcG9sb25pZXguY29tMAkGA1UdEwQCMAAwHQYDVR0l
BBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9jcmwyLmFscGhhc3NsLmNvbS9ncy9nc2FscGhhc2hhMmcyLmNybDCBiQYIKwYB
BQUHAQEEfTB7MEIGCCsGAQUFBzAChjZodHRwOi8vc2VjdXJlMi5hbHBoYXNzbC5j
b20vY2FjZXJ0L2dzYWxwaGFzaGEyZzJyMS5jcnQwNQYIKwYBBQUHMAGGKWh0dHA6
Ly9vY3NwMi5nbG9iYWxzaWduLmNvbS9nc2FscGhhc2hhMmcyMB0GA1UdDgQWBBRr
tMsE2FvCLFkN2Az5I5xw6io9nTAfBgNVHSMEGDAWgBT1zdU8CFD5ak86t5faVoPm
adJo9zANBgkqhkiG9w0BAQsFAAOCAQEAqv5xBDvuaF/y+zll0tfECLPXw0ENmbiC
C6ABmiPDIB/RQG5+xIXRfbGipomR0dbetgaBv3xCW5DGLp+0jr6S4+URMmTh0zIX
eqczV045unR7VKeyrADb+/6cXfSa88606YIvbPML2iIRQklff/7TNCjLedIL4IWz
33hNO5JIqje4lnKPVSKzYpcooUTGuCSih68o7uoCakmPVqvzL9rfjAAwpnHBMsxZ
xOMak5h2cmJ+/9wLod9ijg85mBy23RL94/JCwWqIOUHjV4ElWVjnBQWy0X+fdGs6
9O69LUxkGe2jcnZIA92wLh1vDj1KeTAx3VXbJawaHoCNJ/nxzxmKLg==
-----END CERTIFICATE-----
subject=/OU=Domain Control Validated/CN=*.poloniex.com
issuer=/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2
---
No client certificate CA names sent
Peer signing digest: SHA256
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3016 bytes and written 474 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-GCM-SHA256
    Session-ID: 39CB1F7F9E1D01983F6652AD09B7B381BEA712DAB5DD04478A14DEC7AD577617
    Session-ID-ctx:
    Master-Key: 83370921C6FA4274112B3987B48CDD1459F3162B30261305FF06B00773CEAD7F20C2451709FED1A89CD54F73802A8773
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 64800 (seconds)
    TLS session ticket:
    0000 - 35 13 90 ac 2a 0c 20 0b-ee 66 57 30 0b ee 90 c0   5...*. ..fW0....
    0010 - cc d5 db bc 4c 37 63 a5-83 17 fb c1 7a 85 6c 5d   ....L7c.....z.l]
    0020 - bd e4 d4 41 c5 15 03 5a-13 89 a7 96 54 14 42 38   ...A...Z....T.B8
    0030 - 9e 07 ef 54 c2 c9 3b e1-68 03 88 f4 b0 ac 98 1a   ...T..;.h.......
    0040 - cc d6 2a e3 2f 2b 8a f2-c7 47 d5 f9 5b b9 42 65   ..*./+...G..[.Be
    0050 - 9c fa 4d 51 b3 f2 77 6e-60 8a aa 62 81 b0 81 48   ..MQ..wn`..b...H
    0060 - 98 78 f6 c1 0b b1 b6 36-e2 6c d2 83 fd 65 dc 43   .x.....6.l...e.C
    0070 - d7 60 19 bf c3 cd 35 1f-9d da d1 5e fc f2 66 2a   .`....5....^..f*
    0080 - 13 41 b8 73 67 85 0a d4-c8 9e dc 18 19 10 7a 5b   .A.sg.........z[
    0090 - ef b8 f4 92 4d 26 40 7f-6c f3 37 68 dc ee cf 08<EMAIL_ADDRESS>    00a0 - d6 9b 6b a0 92 0b 02 b5-2b c6 33 6e e0 2a d7 57   ..k.....+.3n.*.W

    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 20 (unable to get local issuer certificate)
---
closed

Mine says almost the same thing. Biggest concern is at the bottom where my verify return code is OK. Can you try from another system? Have you updated ca-certs package recently?
SSL handshake has read 2517 bytes and written 456 bytes
---
New, TLSv1/SSLv3, Cipher is AES128-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1
    Cipher    : AES128-SHA
    Session-ID: F72F1862AFE531B5137C51FFD6CA5686F2B91F5E7C8D9F236944E7CEF90A03D8
    Session-ID-ctx:
    Master-Key: 27043880A875554933850123BBE286FF7970A651D0B46459E4BEEBF9FAABB3042ADD5797524ADB1091F6B07ED4A17AB3
    Key-Arg   : None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)

I tried from my linux box and I got the 0 (ok) code. How would I update my ca-certs package on MacOS?

NOTE: I am still getting 'The handshake operation timed out' when running from my linux box.

Oh, this is on mac? I'm on mac too, 10.12.6 and I'm not getting any issues. This is odd but not an issue with the bot itself.

Yes, on my mac I get the "Verify return code: 20 (unable to get local issuer certificate)" with openssl, and on linux I get "Verify return code: 0 (ok)". Both systems get 'The handshake operation timed out' when running the python script.

Do you have proxy or VPN running perhaps? My mac, ReadyNAS, and CentOS 7 VPS all showing 'Verify return code: 0 (ok)' None of them giving me handshake issues when running bot. Since this is all Python, make sure your python is all up to date. I'm on 2.7.9 on ReadyNAS (which runs my bots) 2.7.13 on mac.

Python 2.7.12 is installed on linux machine. This machine is running my bots and is using latest commit from repo.
This machine says 'The handshake operation timed out' most of the time, but periodically is able to function for brief periods of time. Verify return code: 0 (ok) is returned from openssl.
Python 2.7.9 is installed on my MacBook Pro. This machine doesn't run my bots, but I have a copy of lending bot on here with latest commit from repo. This machine says '<urlopen error [Errno 60] Operation timed out'. Verify return code: 20 (unable to get local issuer certificate) is returned from openssl.

Well, if it only happens periodically, this is probably an ISP/connectivity issue much like DNS failures or straight up timeouts. I get the timeouts frequently during busy exchange periods.

The bot is only able to function properly periodically, most of the time it is receiving timeouts. I using the fastest cable service in my area, all other websites work fine 24/7. If this is an issue with poloniex, I guess I should contact their support. If this an issue with the bot, I would like to help fix it.

Well, from personal experience, you won't ever get a response from their support. I've got 3 tickets over 5 months old with no activity since submitting. You aren't the only one getting timeouts. I get them too; but the bot handles them just fine and continues on working when there is a response. As another personal note, Poloniex's lending rates are sh*t these days with very low volume. I'm considering pulling out of Polo alltogether and concentrate on Bitfinex. However, this is a dangerous proposition since Bitfinex has announced they are stopping all US-based operations in November. As long as you haven't submitted personal info to them (I have not), you may be fine. You just can't lend USDT.

Thanks.

Hi,
I have the same error :
Error during new loans notification: <urlopen error ('_ssl.c:645: The handshake operation timed out',)> Requesting returnActiveLoans
But the test from openssl work fine :
Start Time:<PHONE_NUMBER>
Timeout   : 300 (sec)
Verify return code: 0 (ok)

WTF ?


Rule214BlindWriteLocalRecord exception with rule AA0214

Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 5.0.235548
Publisher: Microsoft
Analyzer 'Microsoft.Dynamics.Nav.CodeCop.Design.Rule214BlindWriteLocalRecord' threw an exception of type 'System.InvalidCastException' with message 'System.InvalidCastException: Unable to cast object of type 'Microsoft.Dynamics.Nav.CodeAnalysis.BoundFieldAccess' to type 'Microsoft.Dynamics.Nav.CodeAnalysis.IInvocationExpression'.
at Microsoft.Dynamics.Nav.CodeCop.Design.Rule214BlindWriteLocalRecord.ProcessingInvocation(SyntaxNode syntaxNode, PooledDictionary2 processInvocations, SyntaxNodeAnalysisContext syntaxNodeAnalysisContext)    at Microsoft.Dynamics.Nav.CodeCop.Design.Rule214BlindWriteLocalRecord.<>c.<Analyze>b__5_0(SyntaxNodeAnalysisContext syntaxNodeAnalysisContext) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule214BlindWriteLocalRecord.cs:line 46    at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.<>c__DisplayClass52_1.<ExecuteSyntaxNodeAction>b__1() in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 742    at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock(DiagnosticAnalyzer analyzer, Action analyze, Nullable1 info) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 1079'

The error still exists with AL Language 5.0.236243 (latest available version).
It is thrown for the app.json a hundred times (not kidding), as soon as CodeCop is activated.

VS Code Problems output (1 of 100):
app.json	AD0001	Analyzer 'Microsoft.Dynamics.Nav.CodeCop.Design.Rule214BlindWriteLocalRecord' threw an exception of type 'System.InvalidCastException' with message 'System.InvalidCastException: Unable to cast object of type 'Microsoft.Dynamics.Nav.CodeAnalysis.BoundFieldAccess' to type 'Microsoft.Dynamics.Nav.CodeAnalysis.IInvocationExpression'.
   at Microsoft.Dynamics.Nav.CodeCop.Design.Rule214BlindWriteLocalRecord.ProcessingInvocation(SyntaxNode syntaxNode, PooledDictionary`2 processInvocations, SyntaxNodeAnalysisContext syntaxNodeAnalysisContext)
   at Microsoft.Dynamics.Nav.CodeCop.Design.Rule214BlindWriteLocalRecord.<>c.<Analyze>b__5_0(SyntaxNodeAnalysisContext syntaxNodeAnalysisContext) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule214BlindWriteLocalRecord.cs:line 46
   at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.<>c__DisplayClass52_1.<ExecuteSyntaxNodeAction>b__1() in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 742
   at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock(DiagnosticAnalyzer analyzer, Action analyze, Nullable`1 info) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 1099'	0	0

Still happens in build 5.0.249661

This seems to happen for me, when I refer to a field that has the words "get" or "find" in the name.
Like "Target" or "MessageType".
Steps to reproduce:

Create a codeunit.
Create a procedure and type:        Message('%1', Customer."Budgeted Amount");
build the project and change to the problems pane

Having the same issue... is it possible to deactivate the underling "Rule214".
I tried to add to my custom ruleset but with no success.

Any progress on this issue. Currently when there is a "runtime" error in the CodeCop Analyzer referencing app.json the CodeCop stops working and we will not see the error before our build pipeline fails. At the moment we have a lot over overhead due to this issue.

@MarcHansenMicrosoft can you provide an update?

We have a bug on it but not gotten to it yet

I can provide an al project with the problem if you setup a private file transfer workspace and send this link to the workspace to<EMAIL_ADDRESS>

Not sure that I can do that due to you code rights.
Could you make it as a pull request on GitHub?
Or is it all of your codebase?

It's "my" codebase, so a PR is a no-go

Can you trim it to app.json and a source file?

app.json is no problem, but I don't know which .al file that causes the CodeCop to crash!
As additional info, the CodeCop works in my DevOps pipeline - where there is no UI.

@atoader could you have a look at what in the VSCode UI could be the reason for this?

@MarcHansenMicrosoft the stacktrace above indicates an invalid cast. It doesn't have anything to do with the UI. The exception is most likely swallowed in the CI/CD pipeline. @kasperdj can you run alc from the commandline while using the -log:"Path to log file.json"  -loglevel:Warning arg to write the output to a file. I am curious if that captures it.

@MarcHansenMicrosoft here is the output of your request. It does not seam to reveal a lot of additional details.

Thanks
We will investigate

Having the same exact warning here while upgrade my codebase from 15 -> 16. Our app is very large, so I do not know which file is the cause. I checked my app.json and launch.json to make sure it matches up to what AL:GO produces

Could you please disable this rule until it works? It's going to be great when it does something, but right now it constantly fails in all of our projects.
As an example, I just disabled our ruleset to check if had finally been fixed in the version of the AL extension released this morning, and I got 207 errors, in a single project.  Half of them crashes from the analyzer, half of them pieces of code were no record has been updated, yet the analyzer complained that the record should be updated before writing to disk (!).

As a simple example of code that fails with this analyzer (this one does not crash):
local procedure GetNextPurchCommentLineNo(PurchHeader: Record "Purchase Header"): Integer
var
    PurchCommentLine: Record "Purch. Comment Line";
begin
    PurchCommentLine.SetRange("Document Type", PurchHeader."Document Type");
    PurchCommentLine.SetRange("No.", PurchHeader."No.");
    PurchCommentLine.SetRange("Document Line No.", 0);
    if PurchCommentLine.FindLast() then
        exit(PurchCommentLine."Line No." + 10000)
    else
        exit(10000);
end;

This code finds the last purchase line for a document, and returns the last line no + 10000 or 10000. It does not modify the line, it does no inserts, it just reads a single value. The result:
The record PurchCommentLine should be modified before saving to the database.AL(AA0214)

In one project, I get this error if I add this one line of code:
MdmMasterChange.SetRange("Target Type", MdmMasterChange."Target Type"::Global);
where
MDMMasterChange is a record
"Target Type" is an option field defined as: Option undefined, Global, Subscription, Client

@Jeeve65 I re-enabled the rule again on the project I mentioned yesterday, and I can confirm that all of the variables (that I've checked) where the analyzer threw a warning by mistake, had a SetRange or SetFilter done to them (not necessarily with an option/enum field).
I don't know whether that will be the only case in which it fails, but I'm sure that's what causes the high number of false warnings in some of our apps.

Any progress on fixing this issue?
I think the main root cause is missing backward compability as our DevOps uses a compiler version (VSIX) matching our target platform - and here the CodeCop works fine - but it's very late in the process to get the warnings and this is causing a lot of additional overhead on our projects!

It is being worked on :-)

fixed in master

Hi @MarcHansenMicrosoft
I can see that this issue should have been fixed based on you update late June.
However not all issue have been resolved as we can still "provoke" the CodeCop compiler runtime error in our projects and below is an example of this using the latest AL Language extension and working on a BC 15 OnPrem project:

So in my opinion, the issue still exists. I can share a private link to Microsoft with the customer project in which we have this issue - to ease your analysis.
Furtermore, if we activate the AppSourceCop in the same project, then the compiler bugs related to the CodeCop goes away - maybe it's a priority in the compiler:

Hi @kasperdj,
Nice details, I like the twist about the AppSourceCop.
I quite sure we fixed the first issue.
Having issues the might crash the analyzer is a general problem and it will be to messy if we keep reopening the same github item.
Could I get you to create a new bug with your details?
please also add link to this item as well thanks.
/Marc

New issue created regarding my last post: https://github.com/microsoft/AL/issues/6116

Still getting this:


Update easy-arceuus-runecrafting

Super small change; just lowers default config settings for flashing speed.
(Someone brought up epilepsy concerns.)

converting to draft until build failures are resolved

closing as the above comments have not been resolved yet. feel free to resubmit when they are


Can't install gaze with Node.js 4.1

Looks like current implementation of the module doesn't work with Node.js 4. At least I've got this amount of compiling errrors:
><EMAIL_ADDRESS>install /Users/varankinv/Workspace/luster-guard/node_modules/gaze
> node-gyp rebuild

  CXX(target) Release/obj.target/pathwatcher/src/main.o
In file included from ../src/main.cc:21:
In file included from ../src/common.h:26:
../node_modules/nan/nan.h:339:13: error: no member named 'New' in 'v8::String'
    return  _NAN_ERROR(v8::Exception::Error, errmsg);
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
                                     ~~~~~~~~~~~~^
../node_modules/nan/nan.h:343:5: error: no member named 'ThrowException' in namespace 'v8'
    _NAN_THROW_ERROR(v8::Exception::Error, errmsg);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR'
      v8::ThrowException(_NAN_ERROR(fun, errmsg));                             \
      ~~~~^
../node_modules/nan/nan.h:343:5: error: no member named 'New' in 'v8::String'
    _NAN_THROW_ERROR(v8::Exception::Error, errmsg);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR'
      v8::ThrowException(_NAN_ERROR(fun, errmsg));                             \
                         ^~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
                                     ~~~~~~~~~~~~^
../node_modules/nan/nan.h:348:9: error: no type named 'ThrowException' in namespace 'v8'
    v8::ThrowException(error);
    ~~~~^
../node_modules/nan/nan.h:355:53: error: no member named 'New' in 'v8::String'; did you mean 'v8::TypeSwitch::New'?
    v8::Local<v8::Value> err = v8::Exception::Error(v8::String::New(msg));
                                                    ^~~~~~~~~~~~~~~
                                                    v8::TypeSwitch::New
/Users/varankinv/.node-gyp/4.1.1/include/node/v8.h:4705:28: note: 'v8::TypeSwitch::New' declared here
  static Local<TypeSwitch> New(Local<FunctionTemplate> type);
                           ^
In file included from ../src/main.cc:21:
In file included from ../src/common.h:26:
../node_modules/nan/nan.h:355:69: error: calling a private constructor of class 'v8::Local<v8::FunctionTemplate>'
    v8::Local<v8::Value> err = v8::Exception::Error(v8::String::New(msg));
                                                                    ^
/Users/varankinv/.node-gyp/4.1.1/include/node/v8.h:326:13: note: declared private here
  V8_INLINE Local(S* that)
            ^
In file included from ../src/main.cc:21:
In file included from ../src/common.h:26:
../node_modules/nan/nan.h:357:65: error: too few arguments to function call, expected 2, have 1
    obj->Set(v8::String::New("code"), v8::Int32::New(errorNumber));
                                      ~~~~~~~~~~~~~~            ^
/Users/varankinv/.node-gyp/4.1.1/include/node/v8.h:2499:3: note: 'New' declared here
  static Local<Integer> New(Isolate* isolate, int32_t value);
  ^
In file included from ../src/main.cc:21:
In file included from ../src/common.h:26:
../node_modules/nan/nan.h:357:26: error: no member named 'New' in 'v8::String'
    obj->Set(v8::String::New("code"), v8::Int32::New(errorNumber));
             ~~~~~~~~~~~~^
../node_modules/nan/nan.h:369:12: error: no member named 'New' in 'v8::String'
    return _NAN_ERROR(v8::Exception::TypeError, errmsg);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
                                     ~~~~~~~~~~~~^
../node_modules/nan/nan.h:373:5: error: no member named 'ThrowException' in namespace 'v8'
    _NAN_THROW_ERROR(v8::Exception::TypeError, errmsg);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR'
      v8::ThrowException(_NAN_ERROR(fun, errmsg));                             \
      ~~~~^
../node_modules/nan/nan.h:373:5: error: no member named 'New' in 'v8::String'
    _NAN_THROW_ERROR(v8::Exception::TypeError, errmsg);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR'
      v8::ThrowException(_NAN_ERROR(fun, errmsg));                             \
                         ^~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
                                     ~~~~~~~~~~~~^
../node_modules/nan/nan.h:377:12: error: no member named 'New' in 'v8::String'
    return _NAN_ERROR(v8::Exception::RangeError, errmsg);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
                                     ~~~~~~~~~~~~^
../node_modules/nan/nan.h:381:5: error: no member named 'ThrowException' in namespace 'v8'
    _NAN_THROW_ERROR(v8::Exception::RangeError, errmsg);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR'
      v8::ThrowException(_NAN_ERROR(fun, errmsg));                             \
      ~~~~^
../node_modules/nan/nan.h:381:5: error: no member named 'New' in 'v8::String'
    _NAN_THROW_ERROR(v8::Exception::RangeError, errmsg);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR'
      v8::ThrowException(_NAN_ERROR(fun, errmsg));                             \
                         ^~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
                                     ~~~~~~~~~~~~^
../node_modules/nan/nan.h:406:13: error: no member named 'smalloc' in namespace 'node'
    , node::smalloc::FreeCallback callback
      ~~~~~~^
../node_modules/nan/nan.h:141:71: note: expanded from macro 'NAN_INLINE'
# define NAN_INLINE(declarator) inline __attribute__((always_inline)) declarator
                                                                      ^
../node_modules/nan/nan.h:416:12: error: no matching function for call to 'New'
    return node::Buffer::New(data, size);
           ^~~~~~~~~~~~~~~~~
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:28:40: note: candidate function not viable: no known conversion from 'char *' to 'v8::Isolate *' for 1st argument
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, size_t length);
                                       ^
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:31:40: note: candidate function not viable: no known conversion from 'char *' to 'v8::Isolate *' for 1st argument
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:43:40: note: candidate function not viable: requires 3 arguments, but 2 were provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:36:40: note: candidate function not viable: requires 5 arguments, but 2 were provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
In file included from ../src/main.cc:21:
In file included from ../src/common.h:26:
../node_modules/nan/nan.h:420:12: error: no matching function for call to 'New'
    return node::Buffer::New(size);
           ^~~~~~~~~~~~~~~~~
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:28:40: note: candidate function not viable: requires 2 arguments, but 1 was provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, size_t length);
                                       ^
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:31:40: note: candidate function not viable: requires at least 2 arguments, but 1 was provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:43:40: note: candidate function not viable: requires 3 arguments, but 1 was provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/varankinv/.node-gyp/4.1.1/include/node/node_buffer.h:36:40: note: candidate function not viable: requires 5 arguments, but 1 was provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
In file included from ../src/main.cc:21:
In file included from ../src/common.h:26:
../node_modules/nan/nan.h:427:26: error: no member named 'Use' in namespace 'node::Buffer'
    return node::Buffer::Use(data, size);

           ~~~~~~~~~~~~~~^
../node_modules/nan/nan.h:727:49: error: too few arguments to function call, single argument 'isolate' was not specified
    v8::Local<v8::Object> obj = v8::Object::New();
                                ~~~~~~~~~~~~~~~ ^
/Users/varankinv/.node-gyp/4.1.1/include/node/v8.h:2933:3: note: 'New' declared here
  static Local<Object> New(Isolate* isolate);
  ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [Release/obj.target/pathwatcher/src/main.o] Error 1

I guess the main issue here is the old version of Nan, which doesn't support current v8 used in nodejs>=4. Switching to Nan 2.x might help, but I haven't looked close on the problem.
Tested on MacOS 10.10 with XCode 7 installed if it's matter.

Same here (OS X, Node 4.2). From what I can tell this module hasn't worked since Node 0.10 unless (possibly) you roll back to an older version of it. See related issue here: https://github.com/shama/gaze/issues/175

This lib no longer uses native addons.


Change exit code to 1 on podman rm nosuch container

Make it easy for scripts to determine if a container removal
fails versus the container did not exist.
If only errors were no such container exit with 1 versus 125.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

I have certainly felt the need for this in the toolbox. Thanks!

23 failing tests - probably because of the different exit code?

LGTM

/lgtm

Code changes LGTM, still not happy with the man page secondary title.

oops, missed the title change, thanks @rhatdan!


https service not starting after enabling tls strict ciphers

lvl=error msg="Failed https service" log_id=0rroPim0000 error="http2: TLSConfig.CipherSuites is missing an HTTP/2-required AES_128_GCM_SHA256 cipher (need at least one of TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 or TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256)."

I think you may be running an older version of influxd and/or built it yourself with modified list of ciphers. Please upgrade and the error should resolve.
The error is from http2
https://github.com/golang/net/blob/f88258d67e0f0f144c79964ca05bb81d51ee8411/http2/server.go#L271-L286
but influxd 2.7 includes the required ciphers in its list here:
https://github.com/influxdata/influxdb/blob/f302d9730c3c66577bea7bc7199cfae773bf308e/cmd/influxd/launcher/launcher.go#L1156-L1166


Mistaken authorship rendering in a bibliographic entry with multiple authors

presently this is a question:
if i create the .adoc bibliography file and add a bibliographic entry like below

[[[ferre-bigorra,1]]],
span:initials[J.] span:surname[Ferré-Bigorra],
span:initials[M.] span:surname[Casals],
span:initials[G.] span:surname[Gangolells],
span:type[book]
span:title[The adoption of urban digital twins].
span:type[inproceedings]
In: span:in_title[Cities].
vol. span:volume[131],
pp. span:pages[103905],
span:date[2022].
doi: span:uri.doi[10.1016/j.cities.2022.103905].

will metanorma reformat the entry based on the correct "flavor" (in this case IEEE styling) or do i need to specifically modify the content in the "spans" to reflect a specific style requirement?
i am having some difficulty understanding the formatting output of the entries after the first author, and i am wondering if this is something i need to do, or if metanorma will do that automatically?
PDF (20230621 document generate: IEEE P2874)

any advice or links to document would be most helpful. thank you

Thank you @ReesePlews for raising this!
The problem here is with:

"Ferré-Bigorra, J. M., G. Casals, and Gangolells,"

It should have been:

"Ferré-Bigorra, J., M. Casals, and G. Gangolells,"

The problem is that both the "J" and "M" was assigned to be the initials of "Ferré-Bigorra".
@opoudjis can you please help with this? Thanks.

I will post updated advice on Metanorma.org. The story is simply, surname must always precede initials and given names. (It is implicit in the present wording, "After the first instances of surname and either initials or givenname," but I will make it explicit.) The relative ordering of initial and surname for the first and for subsequent names is determined by Metanorma's citation stylesheet.
So:
> * [[[ferre-bigorra,1]]],
> span:surname[Ferré-Bigorra], span:initials[J.]
> span:surname[Casals], span:initials[M.]
> span:surname[Gangolells], span:initials[G.]
> span:type[book]
> span:title[The adoption of urban digital twins].
> span:type[inproceedings]
> In: span:in_title[Cities].
> vol. span:volume[131],
> pp. span:pages[103905],
> span:date[2022].
> doi: span:uri.doi[10.1016/j.cities.2022.103905].

@opoudjis thank you for the explanation. i am sorry i would like to confirm a bit more...
you said:  span:surname[Ferré-Bigorra], span:initials[J.]
Q1 with surname before initials, however you have also added a comma between them and removed the comma at the end of the line; are those changes critical?
Q2 and is this format is for any bibliographic entry (with an author) in metanorma (across any template flavor)? i would assume any template flavor, but just want to confirm.
i will update my current bibliography after hearing from you.
thank you for checking this, and the other items.

Q1 with surname before initials, however you have also added a comma between them and removed the comma at the end of the line; are those changes critical?

No. Anything not contained inside a span:[ ] macro is in fact thrown out completely. The spans are there to convey the real information; extraneous text like punctuation are to make the input human-readable, but the actual formatting is completely governed by the organisation's bibliographic stylesheet.

Q2 and is this format is for any bibliographic entry (with an author) in metanorma (across any template flavor)? i would assume any template flavor, but just want to confirm.

Yes, correct.
Once again, sorry it's taken me so long to respond, I've been on a semi-break from Metanorma last couple of weeks.

@opoudjis thank you for the confirmation on these two questions.  i will have a look to make sure the bibliography i am working on follows the structure guidelines.


tests showing what is wrong with startDate queries

Please see https://bugzilla.redhat.com/show_bug.cgi?id=1260881 for more details; basically:
yy-MM-dd_HH:mm:ss - fails with "bad request" as the '.SSS' part is missing
yy-MM-dd - fails because it doesn't provide the exact start time (including miliseconds)

@mrietveld is this still valid taking into consideration just merged PRs (https://github.com/droolsjbpm/droolsjbpm-integration/commit/00edb8d4545de8d3b8545ca2498ee8f7615b6c58)

@mrietveld shall we merge this or close it?

closing as it did not have any attention for a while, feel free to reopen


Add leaderboard metadata

Users should be able to specify when creating a leaderboard:

The column names for player and score.
What blockchain(s) the leaderboard is associated with, if any.
If associated with an EVM chain, what the network configuration for that chain should be (to add to Metamask) only if the chain isn’t supported by Moonstream.
Whether they want to display the Metamask component.

PR
https://github.com/moonstream-to/api/pull/968

resolve https://github.com/moonstream-to/api/pull/968

Think through address normalization


Uncaught RangeError: Maximum call stack size exceeded

When i try to 'append '14 'pmd-card' i get this error with 'Propeller v1.3.1' but it not happen with 'Propeller v1.1.0'.
Here screenshot for more details.

@developer-mahmoud,
One of the community members have provided a solution to this in the thread - #81
Hope that helps.

@developer-mahmoud
Can you please share the step by step procedure you are doing and the list of technologies you are using with their versions?
Also if possible please share a link to your page for our better understanding.

@developer-mahmoud posted another solution for this problem


keepassxc: enable ssh agent sockets

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I am mainly interested in macOS:
@GrahamcOfBorg build keepassx-community

Failure on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/9avjr40zgds5rycm2ndw9imrfpkb3vga-CF-osx-10.10.5-private/Library/Frameworks/CoreFoundation.framework/Headers/CFUserNotification.h:123:78: error: use of old-style cast [-Werror,-Wold-style-cast]
CF_INLINE CFOptionFlags CFUserNotificationPopUpSelection(CFIndex n) {return ((CFOptionFlags)(n << 24));}
                                                                             ^              ~~~~~~~~~
11 errors generated.
make[2]: *** [src/CMakeFiles/keepassx_core.dir/build.make:519: src/CMakeFiles/keepassx_core.dir/core/ScreenLockListenerPrivate.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:197: src/CMakeFiles/keepassx_core.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
builder for '/nix/store/bdzif384690l72s636hp08pkix2a96db-keepassxc-2.3.0.drv' failed with exit code 2
error: build of '/nix/store/bdzif384690l72s636hp08pkix2a96db-keepassxc-2.3.0.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/bin/keepassxc-cli
shrinking /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/bin/keepassxc
shrinking /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/lib/keepassxc/libkeepassx-autotype-xcb.so
gzipping man pages under /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/lib  /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/bin
patching script interpreter paths in /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0
checking for references to /tmp/nix-build-keepassxc-2.3.0.drv-0 in /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0...
postPatchMkspecs
postPatchMkspecs

@LnL7 so clang complains about os x standard includes?

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0/bin/keepassxc-cli
shrinking /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0/bin/keepassxc-proxy
shrinking /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0/bin/keepassxc
gzipping man pages under /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0/share/man/
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0/lib  /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0/bin
patching script interpreter paths in /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0
checking for references to /build in /nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0...
postPatchMkspecs
postPatchMkspecs

Success on aarch64-linux (full log)
Partial log (click to expand)
/nix/store/ldp9djck0isa889kic4m59v3fa9hi4z4-keepassxc-2.3.0

Failure on x86_64-darwin (full log)
Partial log (click to expand)
                                                                              ^              ~~~~~~~~~~~~~~~~~
/nix/store/9avjr40zgds5rycm2ndw9imrfpkb3vga-CF-osx-10.10.5-private/Library/Frameworks/CoreFoundation.framework/Headers/CFUserNotification.h:123:78: error: use of old-style cast [-Werror,-Wold-style-cast]
CF_INLINE CFOptionFlags CFUserNotificationPopUpSelection(CFIndex n) {return ((CFOptionFlags)(n << 24));}
                                                                             ^              ~~~~~~~~~
11 errors generated.
make[2]: *** [src/CMakeFiles/keepassx_core.dir/build.make:519: src/CMakeFiles/keepassx_core.dir/core/ScreenLockListenerPrivate.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:197: src/CMakeFiles/keepassx_core.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
builder for '/nix/store/6syn4nlzb1n0jvsrbrs1xs57r69mskjr-keepassxc-2.3.0.drv' failed with exit code 2
error: build of '/nix/store/6syn4nlzb1n0jvsrbrs1xs57r69mskjr-keepassxc-2.3.0.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/bin/keepassxc
shrinking /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/bin/keepassxc-proxy
shrinking /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/lib/keepassxc/libkeepassx-autotype-xcb.so
gzipping man pages under /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/lib  /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0/bin
patching script interpreter paths in /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0
checking for references to /tmp/nix-build-keepassxc-2.3.0.drv-0 in /nix/store/vrjh4h32mw8ffnjx5kgy6w3k08gwg1gr-keepassxc-2.3.0...
postPatchMkspecs
postPatchMkspecs

@Mic92 that's cf-private
Clang is generally more pedantic about things compared to gcc, I usually add something like this.
{
  NIX_CFLAGS_COMPILE = stdenv.lib.optionalString stdenv.cc.isClang "-Wno-old-style-cast";
}

@GrahamcOfBorg build keepassx-community

Failure on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/9avjr40zgds5rycm2ndw9imrfpkb3vga-CF-osx-10.10.5-private/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:363:5: error: '__LLP64__' is not defined, evaluates to 0 [-Werror,-Wundef]
#if __LLP64__
    ^
3 errors generated.
make[2]: *** [src/CMakeFiles/keepassx_core.dir/build.make:519: src/CMakeFiles/keepassx_core.dir/core/ScreenLockListenerPrivate.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:197: src/CMakeFiles/keepassx_core.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
builder for '/nix/store/cvvkpa96znwpjljf8pszvfqw8ar04cda-keepassxc-2.3.0.drv' failed with exit code 2
error: build of '/nix/store/cvvkpa96znwpjljf8pszvfqw8ar04cda-keepassxc-2.3.0.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0/bin/keepassxc-cli
shrinking /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0/bin/keepassxc
shrinking /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0/lib/keepassxc/libkeepassx-autotype-xcb.so
gzipping man pages under /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0/lib  /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0/bin
patching script interpreter paths in /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0
checking for references to /tmp/nix-build-keepassxc-2.3.0.drv-0 in /nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0...
postPatchMkspecs
postPatchMkspecs

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0/bin/keepassxc-cli
shrinking /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0/bin/keepassxc-proxy
shrinking /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0/bin/keepassxc
gzipping man pages under /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0/share/man/
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0/lib  /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0/bin
patching script interpreter paths in /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0
checking for references to /build in /nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0...
postPatchMkspecs
postPatchMkspecs

Seem like some other header is missing:
/nix/store/9avjr40zgds5rycm2ndw9imrfpkb3vga-CF-osx-10.10.5-private/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:363:5: error: '__LLP64__' is not defined, evaluates to 0 [-Werror,-Wundef]

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/hbrsnv9r13hngd0hc0s6ag3zxjfxlacx-keepassxc-2.3.0

Success on aarch64-linux (full log)
Partial log (click to expand)
/nix/store/l8ciizcv8xwmp6yvch85pf40v2bxxj7y-keepassxc-2.3.0

Failure on x86_64-darwin (full log)
Partial log (click to expand)
#if __LLP64__
    ^
[ 34%] Building CXX object src/CMakeFiles/keepassx_core.dir/core/Translator.cpp.o
3 errors generated.
make[2]: *** [src/CMakeFiles/keepassx_core.dir/build.make:519: src/CMakeFiles/keepassx_core.dir/core/ScreenLockListenerPrivate.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:197: src/CMakeFiles/keepassx_core.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
builder for '/nix/store/cvvkpa96znwpjljf8pszvfqw8ar04cda-keepassxc-2.3.0.drv' failed with exit code 2
error: build of '/nix/store/cvvkpa96znwpjljf8pszvfqw8ar04cda-keepassxc-2.3.0.drv' failed

I have no idea how to fix this.


Feature: Data View - Add icons showing data type of columns

Similar to Power Query, the columns show the data type in the headers themselves with an icon. You could have rollover titles on them to be more specific about ones with the same icon (ex: Double vs Float)
It would be useful in quickly identifying the underlying DuckDB data types being returned
Examples (I highlighted in red):

Love the idea. Any other top features from powerBI you would like?

Clicking the dropdown to filter on a column, it reveals the distinct values held in that column to help with exploring the dataset to immediately see the possible values. Especially as you apply different filters and the distinct values adjust accordingly.
Example: I could have a food table and the columns could be FoodType, FoodName, and StoreName. The dropdowns would show all the distinct values for each column. Then I filter for FoodType Berry. FoodName distinct values would show when I use the dropdown on the column like Strawberry, Raspberry. I filter for Raspberry, and now when I do dropdown on Store it will show all of the stores that have it. All quick analysis without me solving it through SQL.


[Bug] Fix doris spark sink return sucess when error occurs

Purpose of this pull request

Fix doris spark sink always return success when an exception occurs.
For example , doris spark sink return success when you configure the wrong IP or port using doris spark sink , even when sink wrong data.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

example configure file: fenodes="x.x.x.x:80301"  with wrong ip or port or wrong data
env {
spark.sql.catalogImplementation=hive
spark.app.name=test_seatunnel_doris_sink
}
source {
hive{
result_table_name=result_table_name
pre_sql="select * from testdb.testtable "
}
}
sink {
doris{
fenodes="x.x.x.x:80301"
database="test"
table="user"
user="doris"
password="doris"
batch_size=10000
doris.column_separator="\t"
doris.columns="c1,c2,..."
}
}
Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Hi @wwzhe007 , we do not push commit to branch which after we released. If you want to fix some bug, please create a PR for push to dev branch.

Hi @wwzhe007 , we do not push commit to branch which after we released. If you want to fix some bug, please create a PR for push to dev branch.

ok, I got it.


Update README.md

Add status for travis

Thanks for the PR.
I fixed the Travis configuration, if you rebase your version, Travis should no longer not be failing.


Callback support/Delivery Receipt Processing

The golang client we are currently using has implemented Delivery Receipts. In moving to this client implementation it appears that callbacks are on the TODO list. Is there a timeline for when this client will support processing delivery receipts? We have that on our roadmap. Additionally if this is already supported if there is an example then we can use that as well.

No timeline yet but I hear this request and will see what I can do!

I'm not sure when we'll be adding webhook support into the library but in case you or anyone else finds it helpful, here's a minimal example that doesn't rely on the library.
package main

import (
	"log"
	"net/http"
)

func handleDlrWebhook(w http.ResponseWriter, r *http.Request) {
	log.Println("Delivery status for message to " + r.FormValue("msisdn") + ": " + r.FormValue("status"))
}

func main() {
	log.Println("server started")
	http.HandleFunc("/webhook/dlr", handleDlrWebhook)
	log.Fatal(http.ListenAndServe(":8080", nil))
}

This code starts a server on port 8080 - then you can use ngrok or a similar tool to make it available publicly (so that Nexmo's servers can send callbacks to it). If you then send an SMS with a parameter callback set to [your ngrok url]/webhook/dlr, this code will log the destination of the SMS message and its status.
Hope this helps to bridge the gap but rest assured that this issue will also stay open and we will work on this feature being in the library itself when we can.

Update to say that with a new library release, we have the models in place to support this. Next is to work up a code sample showing the delivery receipts being received using this library and sharing it


error running new version of import_realtime_ops.py

Traceback (most recent call last):
  File "import_realtime_ops.py", line 8, in <module>
    import api
ImportError: No module named api

seems that needs an __init__.py or something in the postgres directory to make it work. @knaperek ?

As I mentioned earlier (in PR#8) you need to add the absolute path to the source code into PYTHONPATH environment variable.

thank you, i missed that. still, seems to don't work exactly as that:
root@alfredo:~/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend/postgres# PYTHONPATH=/root/bitshares-munich/explorer/repo/lastv/bitshares-python
-api-backend
root@alfredo:~/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend/postgres# echo $PYTHONPATH
/root/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend
root@alfredo:~/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend/postgres# python import_realtime_ops.py
Traceback (most recent call last):
  File "import_realtime_ops.py", line 8, in <module>
    import api
ImportError: No module named api
root@alfredo:~/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend/postgres#

need to add this to the main README as i tried the docker but i had a hard time with it probably caused by my server configuration so i had to run it in the traditional way :)
thanks again.

What's in your $PYTHONPATH? The api.py module is obviously there (check the source tree), so it should not crash when importing it (as long is your PYTHONPATH is set correctly).

i have the root of the porject in $PYTHONPATH:
root@alfredo:~# cd $PYTHONPATH
root@alfredo:~/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend# ls
Dockerfile  README.md  api.py   config.py   docker-compose.override.yml  explorer_config.env  requirements  wsgi.py
LICENSE     api.ini    api.pyc  config.pyc  docker-compose.yml           postgres             uwsgi.ini     wsgi.pyc
root@alfredo:~/bitshares-munich/explorer/repo/lastv/bitshares-python-api-backend#

Try adding __init__.py into the root folder.

I think this could be closed as there is no more  import_realtime_ops.py as they are taken directly from Elastic Search.


Short solution needed: "Insert Excel data (xlsx) into table" (clickhouse)

Please help us write most modern and shortest code solution for this issue:
Insert Excel data (xlsx) into table (technology: clickhouse)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Insert XLSX (Excel) into Clickhouse table


The application safari is not open anymore

Got this error message:

The application "Safari" is not open anymore.

I am unable to reproduce the issue you encounter. I run 1.3.0 on macOS 12.3.1 with Xcode 13.3. The extension essentially makes use of NSWorkspace.shared.open and tries to open a URL. You have to have an app for handling and opening http URLs.
Please check if Safari generally works on your machine, if this AppKit API works for you and you might want to check out resources like How to Fix "The Application Preview/Safari Is Not Open Anymore" for help.


Close update window after clicking link

Sometimes Windows will hide the popup under the main window after the browser pops up. The update check window should close after you click the link, so it can't get buried.

Will be in the next release.