Bug: fetch in Node.js 18 results in ECONNREFUSED error

Hi, I encountered a problem when I was trying to use the JavaScript SDK with a PocketBase server run locally.
After testing, I manage to drill it down to the following minimal reproduction:
import PocketBase from<EMAIL_ADDRESS>
const url = 'http://localhost:8090'

console.log('---SDK---')

await sdk()

console.log('\n---Vanilla Fetch---')

await vanilla()

async function sdk () {
  const client = new PocketBase(url)
  return client.admins
<EMAIL_ADDRESS>'123456')
    .then(() => console.log('ok'))
    .catch(err => console.log(err))
}

async function vanilla () {
  return fetch(url)
    .then(() => console.log('ok'))
    .catch(err => console.log(err))
}

The output is as follows:
-----SDK-----
(node:52800) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
ClientResponseError 0: Something went wrong while processing your request.
    at new i (file:///.../node_modules/.pnpm/pocketbase@0.3.0/node_modules/pocketbase/dist/pocketbase.es.mjs:1:2078)
    at file:///.../node_modules/.pnpm/pocketbase@0.3.0/node_modules/pocketbase/dist/pocketbase.es.mjs:1:23237
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///.../test.js:7:1 {
  url: '',
  status: 0,
  data: {},
  isAbort: false,
  originalError: null
}

-----Vanilla Fetch-----
TypeError: fetch failed
    at Object.processResponse (node:internal/deps/undici/undici:6277:34)
    at node:internal/deps/undici/undici:6602:42
    at node:internal/process/task_queues:140:7
    at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
    at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  cause: Error: connect ECONNREFUSED ::1:8090
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16) {
    errno: -61,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '::1',
    port: 8090
  }
}

As is shown above, it seems that the PocketBase server refuses the request sent by fetch in Node.js, and thus leads to the unknown ClientResponseError with the JavaScript SDK.
However, when I tried Deno with the same code, everything worked just fine (the 400 error is expected given only sample authentication info is sent), and the output is as follows:
---SDK---
ClientResponseError 400: Failed to authenticate.
    at new i (file:///.../node_modules/.pnpm/pocketbase@0.3.0/node_modules/pocketbase/dist/pocketbase.es.mjs:1:2078)
    at file:///.../node_modules/.pnpm/pocketbase@0.3.0/node_modules/pocketbase/dist/pocketbase.es.mjs:1:23237
    at async file:///.../test.js:7:1

---Vanilla Fetch---
ok

Here is the system info if necessary:

OS: MacOS Monterey v12.4.0
Node.js: v18.7.0
Deno: v1.24.1
PocketBase: v0.3.4
PocketBase JavaScript SDK: v0.3.0

I am not sure what is happening, and hopes for an investigation from the community and, if possible, a solution. Thank you!

@gltjk Could you make sure that the PocketBase backend is running (aka. is the Admin UI accessable)?
I'm not able to reproduce the issue. Just tested with Node v18.7.0 on Fedora with the latest PocketBase app and sdk versions:
import PocketBase from "pocketbase";

const client = new PocketBase("https://pocketbase.io");

client.admins.authViaEmail(
<EMAIL_ADDRESS>  "123456"
).then((result) => {
  console.log("Result:", result)
}).catch((err) => {
  console.log("error:", err)
});

You could try connecting to the live demo (https://pocketbase.io) as shown in the above to rule out eventual issue with nodejs.
Usually ECONNREFUSED is thrown when a connection with the server cannot be established - maybe there is a firewall or missing loopback address. You could also try starting the executable with explicit ipv4 localhost address, eg.:
./pocketbase serve --http="<IP_ADDRESS>:8090"

@ganigeorgiev I am sure the backend is running, for Deno gives the correct result, and the Admin UI is accessible as well. I tried directly connecting to the live demo just now and both Node.js and Deno are working well. I suspect this might be a MacOS exclusive problem since I reproduced it on two MacBook Pros and one Mac Mini. I also tried restarting the executable with explicit ipv4 localhost address or different ports, and still got the same result: Deno worked but Node.js failed.

@gltjk Actually I was able to reproduce it when using a local PocketBase instance. Try changing the localhost part with <IP_ADDRESS> when initializing the client, eg.:
const client = new PocketBase("http://<IP_ADDRESS>:8090");

This is not specific to PocketBase, but I'm not sure why localhost in nodejs is resolved to ::1 (maybe is something related to how the underlying dns.js module resolves the host?).

Another alternative if you don't want to change your nodejs code to use the ipv4 address localhost address is to start the executable with the ipv6 equivalent:
go run main.go serve --http="[::1]:8090"

@gltjk I found the related nodejs issue - As mentioned in https://github.com/nodejs/node/issues/40537, It seems that in nodejs 17+ the default order the ip addresses are returned from the resolver/DNS has changed and ipv6 are with higher priority.
You can change this behavior by starting your node service with --dns-result-order=ipv4first.

@ganigeorgiev Replacing ‘localhost’ with ‘<IP_ADDRESS>’ works. Thanks a lot for both the workaround and helping me discover a new feature since Node.js 17 that I’ve failed to notice. Maybe it would be clearer if you could accordingly update the examples in the documentation as well as JavaScript SDK’s readme? This way future users won’t get into the same trouble trying to run the examples. Anyway, I’ll consider this issue resolved. THX.


[Enhancement] Improve Spam Detection and include more grainular options for spam filtering.

Expected behavior
Functional spam filter with reasonable detection rates.
Actual behavior
Substantial amounts of obvious spam and sexually explicate emails are making it into my unified inbox.
messages of the type that are easily caught by most desktop email clients.
marking messages as Spam does not seem to provide any benefit in terms of training or improved recognition.
Steps to reproduce
Use an IMAP email service that lacks internal server-side spam filtering.
Mark Such Messages as Spam
Environment
K-9 Mail version: 5.101
Android version: 5.1.1
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

That would be great. Eg my mail provider (posteo.de) encrypts mails and (claims) to not scan the mails. Consequently they don't have a spam filter. Since I don't want to have my PC running all yhr time - where spamadsasin could do the job - my phone is running all the time.

See issue #1508


Document site has been down for a while

The document site has been down for a while if there is a plan to fix it?
https://ngneat.github.io/elf/

Mhh maybe it is this problem #450 and #457.
Can you try to open it maybe with your handy or in a other network?

Yes, I can access the docs using data instead of home internet. It seems it has been blacklisted by my Asus router as a phishing website. Also, the status is "Detected" under SURBL using this link "https://www.urlvoid.com/scan/ngneat.github.io/". Maybe it is a good idea to host the docs site under another domain.


Question on Direct Light Sampling

Hi Erich,
First of all thanks for this beautiful repository and all the work you are doing. Your shader code helped me a lot in understand the nuances of implementing a GLSL based path tracer (https://github.com/knightcrawler25/GLSL-PathTracer). I started off quite a while ago by dismantling your code trying to understand the little details. So thanks a lot for putting up your code and helping everyone who has an interest in this field.
As for my question, I read your December 28th 2018 update where you replaced direct lighting with sending more rays towards light sources. Do you have some numbers related to the performance difference you got when trying this with BVH based scenes? It's a really nice idea and wanted to try it out myself but wanted to know what kind of improvement it would give.
Thanks,
Asif

@knightcrawler25
Hi Asif,
Thanks so much for the kind words!  And great work on your own path tracing project!  The example images are beautiful - production render quality.
As for the data supporting the switch to stochastic light sampling over the more traditional direct light sampling (shadow ray technique), I'm sorry but I don't have any numbers or performance analysis at the moment.  I have always been a visual-learner when it comes to computer graphics and I have based many decisions on how something looks, or how smooth something feels, rather than inspecting the data.  It has lead me on a good path, but sometimes my lack of total understanding of the math and algorithms behind Monte Carlo, the rendering equation (integral calculus), bdrf's, pdf's, linear algebra, etc., comes back to bite me.
What I can say for sure is that Direct Lighting (in the traditional sense) works great for low-geometry scenes, like the Cornell Box, or scenes with a few random math shapes like spheres, cones, etc.  The problems arose (for me anyway) when trying that with 4,000+ triangles.  Let's say you had a tight path tracing loop of 4 bounces (which is the minimum to get refractive glass looking correct).  On the first ray cast, half of the rays either hit the background, or hit some kind of reflective surface.  The other half hit some kind of diffuse surface like the walls of a room.  The first half are done with their work, ready to go on to the second bounce in the loop, but the latter half (diffuse rays) need to sample the point light source.  So all those rays must search through the big BVH just to get the shadow rays and diffuse lighting looking correct, while the easy rays have to wait for them to finish.  Thus you get GPU divergence and we're not even out of the 1st iteration of a 4 iteration loop.  Things can get worse on each subsequent bounce.
The brilliant insight that Peter Shirley had is: do the ray cast for the first bounce as normal, the rays that hit nothing or that are easily reflected - treat those the same.  The diffuse ones though, just bias their diffuse reflection (in the hemisphere oriented around the surface normal) towards the light.  So no sample is needed while the easy rays have to wait.  You just mark the ray direction for the next loop iteration as either going to a random spot on the light source, or bounce it in the normal fashion (with the cosWeightedDirectionInHemisphere function).  I handled this Monte Carlo-style by randomly selecting if the ray would go towards the light, or go on its usual cos-weighted random direction.  If you just have the rays go to the light every time, you end up with a flat-color comic book look (which is cool but probably not what you wanted, ha), and if you have them all go in the cos-weighted random direction, you'll have a traditional unbiased path tracer (which is also cool, but it will take forever to get rid of the noise, ha).  So my approach was to randomize those 2 different possibilities on each diffuse bounce:  if ( rand(seed) < 0.5 ) {do 1st}, else {do 2nd}
You probably noticed on my initial BVH demos that I skirted around this issue by using a huge dome sky light above the entire scene.  This allowed me to use a 4-bounce traditional path tracer with no direct light sampling, but it still converges almost instantly!  All that went down the drain when I tried rendering a small bedroom scene (table, sofa, lamp, chairs, 4 walls, 1 lightbulb).  Using the traditional path tracer without direct light sampling was still around 60 fps, but the noise was terrible - taking way too long to get a decent image.  Trying to sample the light, thus searching the BVH again on each bounce, resulted in good convergence, but the frame rate tanked at 10-15 fps.  More hefty scenes crashed my browser.
I have yet to try this new stochastic technique with the BVH.  But I will be sure to post findings here along with examples.  I'm grateful for Peter Shirley sharing his insights in his books.  I have just ordered Realistic Ray Tracing (2nd edition) and look forward to studying it.  In fact, Kevin Beason's SmallPT, which was the inspiration for my project, was based on algos presented in that book, the golden nugget being the ray-jitter tent filter inside the main() function that makes the progressive renders converge to a photo-quality result.  A lot of useful nuggets have been used from that old book (even in OTOY's Brigade path tracer), so I'm looking forward to going to the source!  ;-)
Happy new year!
-Erich

@knightcrawler25
Hi again, I'm happy to report that the initial test of new stochastic light sampling technique works great with the BVH!  BVH Point_Light_Source Demo
The light source is very small and bright and the rest of the scene is dark.  If a normal path tracer was used, the noise would be very slow to converge.  But as you can see, with the new approach, the image resolves almost instantly.  And the best part is that the cost is the same as that of a traditional path tracer - 4 bounces max through the BVH structure to get the refractive glass surfaces looking correct.
I will ramp up the triangle count and try some different light source types, like spot lights and quad lights, but from what I can see so far, things are looking good!

@knightcrawler25
Yes I wanted to be as detailed as time would allow because you have your own path tracing project and you already know the in's and out's of the algorithms.
As to the term "normal path tracer" yes I meant a traditional unidirectional unbiased path tracer.  In other words, the rays go from the camera out into the scene, bounce off of surfaces, and you hope that they bounce into the light source by the time the loop needs to be done.  If they don't find a light, their time and GPU computation is wasted, and the ray returns black , vec3(0,0,0) - hence the noise if you have a small, difficult-to-find light source in the scene.  Explicit light sampling (or shadow ray casting) mitigates this problem, but then you run into performance issues as previously discussed because you need to stall the other non-diffuse rays and search through the BVH geometry for a direct light sample.
Speaking of searching through the BVH, that's an interesting idea that you mentioned about having an intersection routine where you are only concerned with a boolean answer - if the shadow ray hit any geometry or not.  I haven't tried this with my BVH yet, but I might give it a shot.  Though I have done something similar in the past, even without a BVH, on older demos like Billiard Table and the Rendering Equation where even trying to take direct lighting samples (shadow rays) of those scenes crashed my browser.  So I made an additional special shadow ray intersection routine that returned just a boolean result, false if no hit, true if hit.  This did the trick and allowed the demo to compile without crashing.  If you go back through the code change history of those older demos, you will see the extra shadow routine; I think it's called "isLightVisible()" or something.  So I might give it a shot, although even with 2 iterations through the bounce loop with a BVH scene (let alone 4 that refractive surfaces need) it was still crashing with direct light sampling.  But it's worth a shot.

@erichlof I did try the hybrid approach initially when I was using a naive bvh builder and saw a large performance improvement for primary rays, but I had some issues with the depth buffer which I didn't know how to fix since I only started learning at that time so didn't purse that path. I still have the code so I'll try and revisit that this weekend and see if it helps in any way. I believe it should be doable with three.js as well. At the first step you would need to render the objects as usual but only output their positions, normals and material data to seperate textures (using multiple render targets). Then use these textures as input for the path tracer and shade those points and also launch rays from these positions depending on the material type. Here is an example of the first step that would be useful when it comes to implementing this (http://edankwan.com/tests/threejs-multi-render-target/webgl_mrt.html).

@knightcrawler25
Thanks for the info and reference!  I'll check it out! :)


bumping jackson to 2.14.1

Signed-off-by: Amit Galitzky<EMAIL_ADDRESS>Description
bumping jackson to 2.14.1 to align with core bump to jackson-core.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

closed in favor #740 which includes this change


version 2.7.2 - additional changes + code cleanup

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


memory cost and performance on cityscapes

i am sorry...
i have ran a different network, and get wrong results.
how can i draw back this issue....

There should be a button on the bottom saying close issue or something similar.
I'll close this one then.


High Overhead of pprint.pformat Calls During Compilation

Reporting a bug

[x] I have tried using the latest released version of Numba (most recent is
visible in the release notes
(https://numba.readthedocs.io/en/stable/release-notes-overview.html).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Based on a performance test run in issue https://github.com/numba/numba/issues/9700, we tested a larger-scale numerical algorithm using Numba and noticed that about 5% of compilation time was spent in the pprint Python module. Looking further, there are all from calls to pprint.pformat and not to pprint.pprint.
cProfile Output

cProfile output filtered for only pprint.py:
146771/73897    0.076    0.000    0.256    0.000 pprint.py:466(format)
146771/73897    0.074    0.000    0.224    0.000 pprint.py:554(_safe_repr)
    73897    0.040    0.000    0.304    0.000 pprint.py:457(_repr)
39796/1600    0.028    0.000    0.441    0.000 pprint.py:171(_format)
     1546    0.028    0.000    0.226    0.000 pprint.py:380(_format_dict_items)
    66043    0.028    0.000    0.035    0.000 pprint.py:102(_safe_tuple)
   207753    0.013    0.000    0.013    0.000 pprint.py:95(__lt__)
   132086    0.007    0.000    0.007    0.000 pprint.py:92(__init__)
2770/1402    0.003    0.000    0.025    0.000 pprint.py:416(_format_items)
     1600    0.002    0.000    0.447    0.000 pprint.py:57(pformat)
     1546    0.002    0.000    0.277    0.000 pprint.py:209(_pprint_dict)
     1600    0.002    0.000    0.443    0.000 pprint.py:159(pformat)
     1368    0.001    0.000    0.012    0.000 pprint.py:247(_pprint_tuple)
     1600    0.001    0.000    0.001    0.000 pprint.py:107(__init__)
     1402    0.001    0.000    0.026    0.000 pprint.py:239(_pprint_list)
       90    0.000    0.000    0.056    0.001 pprint.py:473(_pprint_default_dict)

Looking through the codebase, I see that:

pprint.pformat is mainly used in logging or debugging code
All of the uses in numba/core/byteflow.py use a intermediate class _lazy_pformat in order to lazily call pformat only when logging is enabled.

In more complex cases, like inside of Bodo or when the IR is larger, pformat overhead is even higher. Thus, we should use _lazy_pformat in most of the other cases.

Whenever its an argument to logging
In one situation where we pass data to ev.trigger_event, which I believe is for compiler debugging purposes only

bug.py

import numba
import cProfile
import numpy as np
import pyinstrument
import time
import logging

logger = logging.getLogger()
logger.disabled = True

def interpolate(npulses, nu, nv, k_ui, k_vi, ku, kv, phs, win1, win2):
    # Radially interpolate kx and ky data from polar raster
    # onto evenly spaced kx_i and ky_i grid for each pulse
    real_rad_interp = np.zeros((npulses, nu))
    imag_rad_interp = np.zeros((npulses, nu))
    ky_new = np.zeros((npulses, nu))
    for i in numba.prange(npulses):
        # print('range interpolating for pulse %i'%(i+1))
        real_rad_interp[i, :] = np.interp(
            # Numba code change: left/right arguments not supported
            k_ui,
            ku[i, :],
            phs.real[i, :] * win1,  # left=0, right=0
        )
        imag_rad_interp[i, :] = np.interp(
            # Numba code change: left/right arguments not supported
            k_ui,
            ku[i, :],
            phs.imag[i, :] * win1,  # left=0, right=0
        )
        ky_new[i, :] = np.interp(k_ui, ku[i, :], kv[i, :])

    # Interpolate in along track direction to obtain polar formatted data
    real_polar = np.zeros((nv, nu))
    imag_polar = np.zeros((nv, nu))
    isSort = ky_new[npulses // 2, nu // 2] < ky_new[npulses // 2 + 1, nu // 2]
    if isSort:
        for i in numba.prange(nu):
            # print('cross-range interpolating for sample %i'%(i+1))
            real_polar[:, i] = np.interp(
                # Numba code change: left/right arguments not supported
                k_vi,
                ky_new[:, i],
                real_rad_interp[:, i] * win2,  # left=0, right=0
            )
            imag_polar[:, i] = np.interp(
                # Numba code change: left/right arguments not supported
                k_vi,
                ky_new[:, i],
                imag_rad_interp[:, i] * win2,  # left=0, right=0
            )
    else:
        for i in numba.prange(nu):
            # print('cross-range interpolating for sample %i'%(i+1))
            real_polar[:, i] = np.interp(
                # Numba code change: left/right arguments not supported
                k_vi,
                ky_new[::-1, i],
                real_rad_interp[::-1, i] * win2,  # left=0, right=0
            )
            imag_polar[:, i] = np.interp(
                # Numba code change: left/right arguments not supported
                k_vi,
                ky_new[::-1, i],
                imag_rad_interp[::-1, i] * win2,  # left=0, right=0
            )

    real_polar = np.nan_to_num(real_polar)
    imag_polar = np.nan_to_num(imag_polar)
    phs_polar = np.nan_to_num(real_polar + 1j * imag_polar)

    return phs_polar

def main():
    dispatcher = numba.njit(
        (
            numba.int64, numba.int64, numba.int64,
            numba.float64[:], numba.float64[:],
            numba.float64[:, :], numba.float64[:, :],
            numba.complex64[:, :],
            numba.float64[:], numba.float64[:]
        ),
        parallel=True
    )(interpolate)

cProfile.run('main()', sort="tottime")

I have a draft implemented that gets rid of all pprint.py uses in our test script and reduces compilation time by ~5%. Will open a PR

I have a draft implemented that gets rid of all pprint.py uses in our test script and reduces compilation time by ~5%. Will open a PR

Thanks for writing this patch. Fixing this has been on the to-do list for a while. I've also observed pprint debugging/logging calls showing up relatively high in performance profiles.


[WIP] Fix endpoint tests

This PR fixes the tests of the endpoints (V1 and V2)

Will merge it once the conflicts are resolved.

Test suite is now implemented.


Flaky test: tests/chainer_tests/functions_tests/connection_tests/test_convolution_nd.py

https://jenkins.preferred.jp/job/chainer/job/chainer_pr/1493/TEST=chainer-py2,label=mn1-p100/testReport/tests.chainer_tests.functions_tests.connection_tests.test_convolution_nd/TestConvolutionND_use_chainerx_false__chainerx_device_None__use_cuda_true__cuda_device_0__use_cudnn_always__cudnn_deterministic_false__autotune_false__cudnn_fast_batch_normalization_false__use_ideep_never_param_80_{b_dtype=float32, dims=(3, 4, 3), autotune=False, cover_all=False, groups=1, dilate=1, nobias=True, contiguous='C', W_dtype=float32, x_dtype=float32}/test_backward/

I have been working into this issue and found the following.
After setting the test with the same parameters as Jenkins (copying all the random generated arrays).
I verified that the gradient of the test was similar to the one appearing on jenkins.
gradients (numeric):  -0.017547332620302745
gradients (backward): -0.017547559696397153

Gradients numeric is calculated in chainer/gradient_check.py using finite differences, while backward is obtained by calling the backward method of a function
However, in jenkins the output was:
gradients (numeric):  -0.0176546986054
gradients (backward): -0.0175476312237

This seems to indicate that the problem is actually happening in the numerical gradients.

Several things I have found:
Jenkins TEST=CHAINERX_* uses docker with cuda:9.2-cudnn7-devel-ubuntu16.04 as the base image while TEST=chainer-*  doesn't seem to rely on docker.
TEST=CHAINERX_chainerx-py3 seems to be using CuPy version 6.0.0b3 according to the output log???. Other CHAINERX tests doesnt rise that warning.
Close inspection on the TEST=chainer-* outputs shows that jenkins is installing cupy v6?
Requirement already satisfied: numpy>=1.9.0 in /usr/local/lib/python3.5/dist-packages (from cupy==6.1.0) (1.13.3)
Requirement already satisfied: six>=1.9.0 in /usr/local/lib/python3.5/dist-packages (from cupy==6.1.0) (1.12.0)
Collecting fastrlock>=0.3 (from cupy==6.1.0)

CUDNN & CUDA versions for Jenkins tests
chainer tests

chainer
CUDA
CUDNN

py2
8.0
5.0

py3
10.1
7.5

py35
9.2
7.1.4

Jenkins
In this other test (same PR!??) Jenkins gives a wrong value for the numerical gradient too:
pg00
gradients (numeric):  -0.18220901963086378
gradients (backward): -0.1822091187772657

Jenkins
gradients (numeric):  -0.181999856626
gradients (backward): -0.182209047527

Reproduced on local environment installing cuda8 & cudnn 5.0

We decided to test the numerical gradients on the cpu.

Update CuDNN to 5.1 for python2 jenkins tests should solve this issue.
@kmaehashi volunteered to do it.

Fix in https://github.com/chainer/chainer-test/pull/514

Reoccurred: https://jenkins.preferred.jp/job/chainer/job/chainer_pr/1707/TEST=chainer-py2,label=mn1-p100/console

Got the numbers in my machine, but I cant reproduce the error with cudnn 5.0 or cudnn 5.1 :(

reproduced, there was an issue with my cupy environment ...
gradients (numeric):  -0.40878489518665345
gradients (backward): -0.4084860521330623

Both cudnn 5~5.1 Fail on this test.
cudnn 7 for cuda 8 works.

@niboshi whats your opinion on the solution for this.
Should we enable numerical gradient cpu calculation only for this tests?

@emcastillo
Did you confirm there's numerical issues before cuDNN 7?
What's the probability of failure before 7? How many times did you repeated without error in 7?
If it's actually confirmed, it sounds reasonable to increase the tolerance before 7.

I am currently running 1000 test cases on backward of convolution_nd with cudnn 5.1 and cudnn 7
I will post the failure rates during the day.

Should be fixed by #7864

Reocurred https://jenkins.preferred.jp/job/chainer/job/chainer_pr/1828/testReport/

@emcastillo Let's paste the log here. Links are volatile.
18:57:11 FAIL tests/chainer_tests/functions_tests/connection_tests/test_deconvolution_2d.py::TestDeconvolution2DFunction_use_chainerx_false__chainerx_device_None__use_cuda_true__cuda_device_0__use_cudnn_always__cudnn_deterministic_false__autotune_false__cudnn_fast_batch_normalization_false__use_ideep_never_param_26_{dilate=2, contiguous=None, W_dtype=float16, x_dtype=float16, stride=1, test_outsize=True, nobias=False, groups=2}::test_double_backward
18:57:11 FAIL tests/chainer_tests/functions_tests/connection_tests/test_deconvolution_2d.py::TestDeconvolution2DFunction_use_chainerx_false__chainerx_device_None__use_cuda_true__cuda_device_0__use_cudnn_always__cudnn_deterministic_false__autotune_false__cudnn_fast_batch_normalization_false__use_ideep_never_param_8_{dilate=1, contiguous=None, W_dtype=float16, x_dtype=float16, stride=1, test_outsize=True, nobias=False, groups=1}::test_double_backward

TestDeconvolution2DFunction_use_chainerx_false__chainerx_device_None__use_cuda_true__cuda_device_0__use_cudnn_always__cudnn_deterministic_false__autotune_false__cudnn_fast_batch_normalization_false__use_ideep_never_param_26_{dilate=2, contiguous=None, W_dtype=float16, x_dtype=float16, stride=1, test_outsize=True, nobias=False, groups=2}.test_double_backward _
18:57:10
18:57:10 self = <chainer.testing._bundle.TestDeconvolution2DFunction_use_chainerx_false__chain...=1, test_outsize=True, nobias=False, groups=2} testMethod=test_double_backward>
18:57:10 args = (), kwargs = {}
18:57:10 e = FunctionTestError('double backward is not implemented correctly\n\n(caused by)...ce: 0.00103606851056\nx: -0.03715174015635242\ny: -0.03606851055800786\n\n\n',)
18:57:10 s = <StringIO.StringIO instance at 0x7f730bd39c68>, k = 'groups', v = 2

:
:

18:57:10 E           FunctionTestError: Parameterized test failed.
18:57:10 E
18:57:10 E           Base test method: TestDeconvolution2DFunction_use_chainerx_false__chainerx_device_None__use_cuda_true__cuda_device_0__use_cudnn_always__cudnn_deterministic_false__autotune_false__cudnn_fast_batch_normalization_false__use_ideep_never.test_double_backward
18:57:10 E           Test parameters:
18:57:10 E             dilate: 2
18:57:10 E             contiguous: None
18:57:10 E             W_dtype: <type 'numpy.float16'>
18:57:10 E             x_dtype: <type 'numpy.float16'>
18:57:10 E             stride: 1
18:57:10 E             test_outsize: True
18:57:10 E             nobias: False
18:57:10 E             groups: 2
18:57:10 E
18:57:10 E
18:57:10 E           (caused by)
18:57:10 E           FunctionTestError: double backward is not implemented correctly
18:57:10 E

:
:

18:57:11 E           gradients (numeric):  -0.0371517401564
18:57:11 E           gradients (backward): -0.036068510558
18:57:11 E
18:57:11 E           x: numeric gradient, y: backward gradient
18:57:11 E           Not equal to tolerance rtol=0.001, atol=0.001
18:57:11 E
18:57:11 E           (mismatch 100.0%)
18:57:11 E            x: array(-0.03715174015635242)
18:57:11 E            y: array(-0.03606851055800786)
18:57:11 E
18:57:11 E           assert_allclose failed:
18:57:11 E             shape: () ()
18:57:11 E             dtype: float64 float64
18:57:11 E             i: (0,)
18:57:11 E             x[i]: -0.0371517401564
18:57:11 E             y[i]: -0.036068510558
18:57:11 E             relative error[i]: 0.0300325569752
18:57:11 E             absolute error[i]: 0.00108322959834
18:57:11 E             relative tolerance * |y[i]|: 3.6068510558e-05
18:57:11 E             absolute tolerance: 0.001
18:57:11 E             total tolerance: 0.00103606851056
18:57:11 E           x: -0.03715174015635242
18:57:11 E           y: -0.03606851055800786


Install Issue

Trying to install. Install seems to work and shortcut is created, however nothing appears when it is run.
Have disabled virus programs but still no luck.
Am using Windows 11 Home 64 bit
thanks for any help

I had this issue when installing WinWidgets on new installations of Windows. The issue was that either .NET Framework was missing or the required MVC++ was not present.
Make sure both of them are installed. Please tell me if it worked!

I have MVSC 2015-2019 and .Net Framework 4.8 installed  so it wasnt that but I reinstalled and now it works (only thing different was I installed just for me rather than all users - but not sure if that made a difference). Thanks for the help.


Error is not getting cought when coming back to the window

Hey, great library!
I noticed that when I useQuery and it fails, go out of the page and then go back - the error will not be caught in useQuery but be raised to the UI.
How to test?

Use useQuery to a endpoint that does not work (using async await)
Let it fail one time, go out of the tab and go back in.
You should see the Ui crashes.

Thanks!

Thanks for reporting! I’ll have this fixed ASAP
Tanner Linsley
On Nov 13, 2019, 3:57 PM -0700, Amit Ripshtos<EMAIL_ADDRESS>wrote:

Hey, great library!
I noticed that when I useQuery and it fails, go out of the page and then go back - the error will not be caught in useQuery but be raised to the UI.
How to test?

Use useQuery to a endpoint that does not work (using async await)
Let it fail one time, go out of the tab and go back in.
You should see the Ui crashes.

Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I want to fix that in order to learn more about react-query, mind if you lead me on which part of the code should I look? Thanks!

Yes I can! But first, could you make a codesandbox that demonstrates the bug so we can work from there?

Well, I'm trying to mimic the issue using codesandbox, however without any success.
I'm starting to think that it happens because im in development mode in my react environment.
The issue I'm seeing is that the development environment catches the error and not react-query - only when I go out and in to the page.
I'm attaching a image that shows how it looks like.

Ah... yes. The redbox error handler for CRA dev mode is a bit overzealous sometimes. Let me look into this a bit more.

Just to be clear, you're not using Suspense are you?

Not using suspense
On Thu, Nov 14, 2019, 16:55 Tanner Linsley<EMAIL_ADDRESS>wrote:

Just to be clear, you're not using Suspense are you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerlinsley/react-query/issues/36?email_source=notifications&email_token=ACSFNTFZULMRPI3HS2A33ULQTVRFXA5CNFSM4JNC2H7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECDFEI#issuecomment-553923217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSFNTDSHMXPKN4AH2D6NADQTVRFXANCNFSM4JNC2H7A
.

So the cause of this error is that that then the window is refocused, the refetchAllQueries function is called. This function returns a promise and will throw if any of the queries on the page error. So essentially, you don't want the window focus fetcher to throw error into the window, you want to catch the error and just log it to the console.
Let me know if that's enough info for you to get started on fixing it and feel free to open a PR. I'll help you the rest of the way with a code review there :)

Thanks for the help, I created a pull request and tested it on my application and it does work!


Computation of network query for distance buffer

This article might be relevant: https://datasciencecampus.ons.gov.uk/access-to-services-using-multimodal-transport-networks/


ICMP Firewall: NAT: Port Forward issue

Under Firewall -> NAT-> Port Forward when I add ICMP to redirect to an internal ip address the webgui show the destination port as 80 (HTTP) and the redirect port as 80 (HTTP). Should probably just show * for both. Under Firewall -> Rules also shows port 80 (HTTP). I'm assuming this is just a webgui cosmetic issue. I'm using version opnsense v15.7.23-amd64.

Was just testing out ICMP rules. Something else I noticed that is wrong with creating a NAT -> Port Forward ICMP rule. If you first select create a new rule using the button "add new rule based on this one" and then select protocol ICMP the destination port will be from the rule you based the ICMP rule from. You have no option to change the destination or redirect target ip port. I don't believe the webgui should be showing an option to even select a port let alone input a port for you.

I agree with your analysis, there has been a similar patch that was added to 15.7.24 that does the same for the firewall rules. These are cosmetic issues that surfaced when we reworked the pages as we touched more than just the layout (because it needed housekeeping).


Exploring casualties by date

Depends on part of #2 as a prerequisite.
Data could be autonomously animated, or allow user to scrub through time (probably one month at a time) with a slider.  Displaying total casualties to-date would be helpful in this viewing model.
Timesteps of months would probably be best for animation purposes, but could go as granular as days.

Partially implemented by 034819d, which introduces a conflict with the photo filter selector.
TODO: build a global filtering function that takes all possible manipulations (sliders, checkboxes, etc.) into account and performs the necessary selections.

Composable filtering introduced in 741a75e69847b4b14c7b6a7576247d5cf83bc105, closes this issue


Make packaging proj generation disabled by default

Previous behavior:
-genpackaging automatically enabled when:

Any number of non-app projects are included in the vsimporter import
-genprojections is specified

New behavior:
-genpackaging disabled by default
Must set -genpackaging or -genpackaging=1 to generate packaging (nuproj) project for any vsimporter import
i.e. If you are creating middleware you should specify -genprojections AND -genpackaging. It is no longer automatic.
I'll update the wiki's vsimporter page to reflect this change.

I'm fine with this change, but, I'm curious what is the reason for the change?

nuproj's, despite using project.json, do not automatically restore properly in VS 2017. Therefore, the nuproj will not build successfully without additional intervention (must command line nuget restore).
Additionally, the packaging nuproj was added when ANY non-app was importer. For example, the case of importing an app plus a lib it depends on would add the packaging project to the solution.
Therefore, to not break regular app importers, default has been set to OFF.

In reply to: 290533234 [](ancestors = 290533234)

Looks good.

I sign off, but codflow won't let me.

In reply to: 290541570 [](ancestors = 290541570)


Excluding tests for non supported functionality from CI

Hello @kozlov-alexey! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sdc/tests/test_old_pipeline.py:

Line 775:13: E265 block comment should start with '# '

Decided to close this and make code-cleanup in a separated PR later.


[pwm, rtl] PWM RTL fix for issue mentioned in PR#13295

Fix the duty cycle state transition issue in heart beat mode mentioned in PR #13295, the previous RTL was designed to repeat the entire duty cycle patterns, so duty_cycle_a repeated twice (one at the end of the current duty cycle pattern, the other at the start of the next duty cycle pattern)
The test now passes with seed<PHONE_NUMBER>, but after running another 50 tests, two tests failed, e.g. with seed 41810794

The duty cycle state transition looks correct, the test might be failed due to the clr_blink_cntr_i pusle in the end @15,899,690.782ns, the pwm_en_i was off at the same time, so the pwm_o output stops

I checked the other failed seed, it's also failed after this clr_blink_cntr_i pulse, @dharanendrak do you have any clues about what might be the issue here?
Signed-off-by: Muqing Liu<EMAIL_ADDRESS>

Ah. Thanks Michael, though this PR is inclusive of the changes I had made.  After talking to Muqing, I had no intent of merging the  other one.   It shouldn't be too hard to merge though.

Ah got it - sorry to jump the gun here.
I did the rebase for you.


Class hierarchy clears after selection in Coder

The hierarchy used to remain so alternative classes could be selected:
https://github.com/user-attachments/assets/621b8bd1-7d62-48eb-a097-d8e718806f8d

Happens when the superclass is in another package. Also happens in the other places where the hierarchy is displayed:
https://github.com/user-attachments/assets/bb158116-b95c-439d-b7af-6f55d24c0665

Works now.


Update order in which requirements are installed

Describe changes
Previously, the requirements in the Docker images we build we installed in the following order:

The packages of the client environment
Manually defined packages
Manually defined integrations and stack integrations
Hub packages

This makes it very painful for users to override package versions that are required by the ZenML stack.
This PR swaps the installation order to now install the manually defined packages last, which means users can explicitly configure certain versions there and we make sure those get installed correctly.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

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

Requires testing, and also this might be breaking for some users. Don't merge until that's done.


REST API Documentation

The docs for the REST api do not show any end points or how to get them.  The only docs are here: https://docs.opnsense.org/development/how-tos/api.html.  The example script gives 2 end points /core/firmware/status and /core/firmware/update but nothing further is documented that I can find.  Is this all that is currently supported, or is the documentation missing?

easiest option is to look at the controller section of the source code and checkout the Api directories (same structure is used for both the plugins and core). https://github.com/opnsense/core/tree/master/src/opnsense/mvc/app/controllers/OPNsense
Api enabled pages are easy to find, all url's start with /ui/ for the user interface part, /api/ for the rest part.
There are no plans to document all api's, because of time constraints. The end points are quite easy to extract from the UI code, which uses the same logic.
For example, to get an arp listing: https://github.com/opnsense/core/blob/master/src/opnsense/mvc/app/views/OPNsense/Diagnostics/arp.volt#L41

@AdSchellevis This is not super awesome.  Can we at least have an endpoint that gives a list of registered endpoints.  That would be start instead of going on a wild goose chase through the code.

not planned either, if you would like to work on documentation on the subject, just let us know.
A service which exposes all might not be a good idea for security reasons anyway.

a fast variant: git grep 'Action('

 git grep 'Action(' | grep Api to filter the ui actions ;)

timeout due to inactivity

If its not documented, it doesn't exist. Have you considered using a framework like swagger for api documentation? https://swagger.io/tools/

Sure, but we can only work on a limited number of things and from an open source perspective API docs are not high value targets and nobody else so far helped fund them.
Cheers,
Franco

@fichtner they also would be always incomplete and maybe wrong because the plugins change frequently.

This is just ridiculous... if you offer an API, tell users how to use it. Argumenting with "either you're a nerd and can reverse engineer or code or the feature won't be usable for you at all" is the most hilarious answer I've read in a while. That's the same like "we won't tell you how all the functions of a car work unless you can decipher it's electronic blueprints".
I was considering opnsense as being a great alternative for pfsense in the way of automatic deployment and configuration, but now seeing where the project goes, it's really not...

This is just ridiculous...

No it's not. You are imposing your need over the needs and time constraints of an open source project. The only solutions are offering time, guidance or work. Ranting, contrary to popular belief, will not fix it. :)

@fichtner It's not about my needs but about how the argument of bad documentation is twisted and turned. Being not a primary goal on this project is a reason, but

A service which exposes all might not be a good idea for security reasons anyway.
clearly tells me that some of you guys either love security by obscurity or just live programs without man or --help functionality. Also, publishing the so far available api would lead to quicker bugfixes and suggestions by the community. I was making my point here and the way the peoples questions were answered left me no other way than calling this behavior "ridiculous". This wan't meant to be personally but somehow seems to be a little ignorant to me.

clearly tells me that some of you guys either love security by obscurity or just like programs without man or --help functionality

I really don't know if you're trolling or not. We've written elaborate man pages and docs and if you don't see it that's perfectly fine, but it lessens your argument by an order of magnitude: Picking the example where we lack documentation after having ourselves stated that is true is a perfectly fine way of beating a dead horse.
You could have said you would like to see this progress, maybe even asked what's needed or if this would be reopened. Some people have experience with API doc generation, great, let's get that on the table.
Truth be told, you are right about everything and I don't disagree. Though you can see how the choice of doing none of the above lessens your entry and we are not afraid of calling this out, because at the end of the day when someone asks others to do work or lessen the work of others by telling how bad or lacking it is there is not much to be gained on either side.
With all due respect,
Franco

@jzielke-nli  have you actually read all the documentation we've created over the years??? The whole concept is explained from how to build apps to how to build an entire system including lots of manual pages for the tools that we use....
As with with everything in the world.... there is always room for improvement, something like slate to document endpoints would be great to have, but takes time and maintenance, which we currently have no funding for.
If people want to use our endpoints, their usually pretty easy to find using either the available inline PHPdocs or inspect the requests the browser is doing... Historically they haven't changed very much for the core system as we tend to keep them backwards compatible.
Contributions are always more then welcome, as long as they lead to actionable results.
Best,
Ad

Ok guys let me get this straight:
I have no time nor the intention to troll anyone here.
I've been using pfsense for high productive firewall clusters running for many clients throughout a couple of years now, using complex routings and even written my own provisioning mechanism for virtual IPs. So I think I know the product quite well. So far for the question on reading the docs.
Now when I stumbled upon your fork, which i really appreciate - and (again) I understand totally understand that feature requests aren't changing you priority on development in a matter of seconds - I see this API as a feature list on your website. And yes, I've looked up the api documentation as well. But - and that's the only thing which I was complaining about here - when people ask for help, the argument I quoted above just doesn't make sense, nor does it help the community in any way.
Stating that the API is still an undocumented feature which isn't fully implemented on your website as well as here at the beginning of the discussion would have lead to the understanding of all the people here I guess. But come on @AdSchellevis you can't really belief that documenting the api endpoints is a security expose, it's the complete opposite. And that's the only point I was complaining about. I don't complain about your priorities nor about your efforts on different topics, but please, just be honest when a feature isn't really there rather than putting it on your website when in the end, users get stuck.
So hopefully I could explain my concerns and the API will be completed one day for everyone to be easy to use.

huh, I never stated that it's a security expose, nor do I think so.

Yes, thank you. I apologise for being as blunt as I have been.

A service which exposes all might not be a good idea for security reasons anyway.

So that's part of @AdSchellevis that seems to cause a bit of stir.

Right, thats the point. On the question

Can we at least have an endpoint that gives a list of registered API endpoints

The response "not be a good idea for security reasons" kinda seemed very odd.

Getting a list of available API endpoints with the required parameters is currently not really possible because the information may not exist and it depends on the the installed plugins as all OPNsense specific plugins do work with the API. You will always find the same kind of API calls for CRUD actions. If you need to automate something, you can open the page, open the network tools of Firefox, right click the request ans select copy as curl. After that you can just past it into your favourite editor and remove the unnecessary headers like the user agent, the cookies etc. and add the authentication (-u username:password where you get the credentials from the user page). That's all.

You will always find the same kind of API calls for CRUD actions. that is simply put, not true @fabianfrz .
Neither is the payload similar, nor the output or the responses.
The reasons that there is no REST documentation is, that it is not even REST, and neither a framework has been used to do that. You will not be able to use swagger or anything else. What we have in opnsense is a self made, HTTP "api" and obviously its very hard to have docs for that - since you have to write and maintain them manually. This will always be a pain point.

@jzielke-nli I see what you mean, not intended that way. Leaking endpoints to the outside world is usually not a good idea for security reasons, same reason why you don't want your attacker to know which webserver version you're running on a lot of public facing servers.
Being able to collect help from the machine itself with the usual --help option obviously isn't a security concern (our configd system for example can also output it's known commands).
My point was (and is) that providing a list of what your installation can provide in terms of services is easy, you can already do that, using grep for example. Giving context and making it useful is the hard part and requires more work then we can process at the moment. I would love to see proper endpoint documentation using something like slate (https://github.com/lord/slate) as long as the maintenance process to keep it useful is also in place.
Eventually we might end up with something in addition to what we have now, endpoints are easy to identify so if anyone want to use them, their easy to find, documentation about how to use them would be valuable and would ideally cover both the core system as the plugins.
Feel free to discuss further, I'm not going to, I see more comments flowing in while typing about what OPNsense is or isn't baring statements that are either incomplete or false.

@EugenMayer can you explain?
You will always find the same kind of API calls for CRUD actions. that is simply put, not true @fabianfrz .

In all plugins, you can find an API call for get/set if you see some grid on it where you can do CRUD actions, you find a search API call, one for get, one for set, one for delete, … - and it is very similar everywhere. I don't want to say you are wrong about REST because deleting should be DELETE and not POST and so on but there is a call to delete stuff. Maybe @AdSchellevis can explain this design decision - it was not mine. As far as I know, also rails/rails has some fallback to support (legacy) browsers, which cannot handle other methods than GET/POST. In that case, a filed _method is sent to override the used HTTP verb.
Which data you get, depends on the Model in the background. The fields do always look the same but it depends on the field.

Neither there is anything like a "resource", nor VERBs are used at all, rather any "verb" is done using some kind of custom "subresource" like api/myplugin/deleteXXX or api/myplugin/deleteYYY or createYY..update... and so on.
This is complete handmade, there is no consense and neither a pattern nor it matches anything you find out there.
Its a self-made, self-baked, hand crufted something with the exact thing when you do that. using something like slate` will be plain PITA since they respect resources, they respect verbs and they expect you to deal with that - if you dont, you basically write a hand made documentation ( with a nice interactive model though ).
And this all is not about some estethical, "RFC would be nice" kind of thing - it has directy implication of the way you can integrate it even if you have reverse engineered it. Creating something like https://github.com/EugenMayer/opnsense-cli was just as bad is it got. I had to break with every single pattern i have using from the existing plugins in https://github.com/EugenMayer/opnsense-unbound-plugin/blob/master/net/unbound/src/opnsense/mvc/app/controllers/OPNsense/Unbound/Api/HostentryController.php#L31 and the other methods. Otherwise you cannot sanely consume them or use them with any REST client at all, not to speak about anything regarding the response codes ( which is 200 in any case in OPNsense right now ) .. which i also entirely changed and not followed anything which is there. So its a real frankenstein and i would never consider extending that go based cli to the endpoints in the existing core plugins, since the boilerplate alone for consuming those endpoints is erasing any motivation to contribute.
As i have written above an API can encourage people to build third party integrations, to integrate with OPNsense, to "spread the word" and to broaden its audience. Or it does not :)

@AdSchellevis Thanks for your detailed explanation. As for the comments on the APi design itself I won't jump in since I don't know much about it's implementation from the codebase side of view.

OK, so I played around with the opnsense-sphinx-docker and got some start on the API list documentation. Now, what is the best format to represent all of this data? I'm hoping to get the page(s) auto-generated in bulk since I have a lot of the data already. Do you just want a plain big list? Maybe sorted by category or a separate page for each plug-in?
Maybe there's also a need to provide some guidelines on how to best implement new API calls in the future. This could limit the differences between developers and ease the consumption of the API by 3rd parties.
I also glanced at the MVC framework and it seems to me that it's possible for a plugin to adhere to the common REST specifications. As long as the controller implements these standard within its code (verb, headers, response code)... It would be a cool proof-of-concept to make a 'REST hello world'.

I have created PR opnsense/docs#24 with a proposal for the API reference.


Can't download main db

Tried everything, ticking 'use keystore' options then try redownloading db many times, reinstalled app. Still getting error 'HTTP error fetching URL'. Am currently running the latest version of BakaReader  using android 4.4.

Can you open the website from your phone?

Yes. Even tried clearing partition cache to see if that will change anything but still didn't work.

are you using any antivirus/firewall? can you give me the adb log file?

log.txt
is this good enough? btw im not using any antivirus/firewall of any sort on my phone and no firewalls on network either.

Also, I'd like to add that what I'm getting is an HTTP error one and not HTTPS (not sure if those are different errors) and if they're different is why does it occur if you've already set it to be always HTTPS.

I hope you can find an solution , cause i have the same problem

your log doesn't show the required part. please filter by appname = com.erakk.lnreader and try to perform the novel list refresh when logging. refer to http://stackoverflow.com/a/6854182
If you able to browse in the phone browser, ensure the use app keystore is turned off.
about http error, that one is hardcoded in the message I think.
@BoreDom9595 : Do you able to browse the bakatsuki website from browser phone? what is your device and android version?

Yeah i can Browse the Website , and androidversion is 4.4 already tried a few things i read online but none oft it helped

This is due to the Admin change the site config, will update.

try https://github.com/calvinaquino/LNReader-Android/releases/tag/1.1.42

Thank you , works great ,👍

Latest release also worked. Thanks mate :D


Launching real.launch results in crash

After the full clone and install, the launch file fails to execute on the NUC. The demo file executes successfully.

The ur3_controller still used controller.yaml form the ur3 moveit package. now it uses the controller.yaml from this package


upload product feed on sandbox.sellingpartnerapi-na.amazon.com

Hi,
Since production account is not working. I tried using sandbox and got following response while uploading products feed-
{"errors":[{"code":"400","message":"Invalid input","details":"Invalid input"}]}
Here is complete output -

About to connect() to sandbox.sellingpartnerapi-na.amazon.com port 443 (#0)
Trying <IP_ADDRESS>...
Connected to sandbox.sellingpartnerapi-na.amazon.com (<IP_ADDRESS>) port 443 (#0)
Initializing NSS with certpath: sql:/etc/pki/nssdb
skipping SSL peer certificate verification
SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Server certificate:

  subject: CN=sandbox.sellingpartnerapi-na.amazon.com

  start date: May 22 00:00:00 2021 GMT

  expire date: Jun 20 23:59:59 2022 GMT

  common name: sandbox.sellingpartnerapi-na.amazon.com

  issuer: CN=Amazon,OU=Server CA 1B,O=Amazon,C=US

POST /feeds/2020-09-04/documents HTTP/1.1
Content-Type: application/json
accept: application/json
host: sandbox.sellingpartnerapi-na.amazon.com
user-agent: spapi_client
x-amz-access-token: Atza|IwEBIKwFw4KFGQv40YR5RUveQ35x57_OWNvpvSHOuZY8epTOAGUkZcPx42t0VjxVDdE3YXiGINPMCW4E6ZRhL51ATYv_9whdOx6DNvbUXcEG1E9PpjH3EcHnAd2yMXD4PMqj5i1nagF4924Nemc8Fl42vpl-YxKeCKL9MdIxHr4bWGwQu23DTjRkXPhb7ISZ1QmDln6sbt2R-Tkf8x4ZtYOQAGO7HCq6k4hVVvdxIuKGDFDq69ybJTpenu99tkc6Ed6k9B-QOLSgyfEmRocrhlfKBsWgpAeRDXTf2OuYFnMHA6_O7JTE8K5RqOYNkOMvVjnpVIXwtBO2LswK5q2rbuvrf2CJ
x-amz-date: 20210607T083258Z
x-amz-security-token: FwoGZXIvYXdzELL//////////wEaDFjgpldc62QeANduASKsAa2HsZ2AxdZ9r3DTlmYdqRtHMRw+11vBruPDHVzG9r/ByztLMANtPUQzgsX4Gk61hE/oiP+XZ5qJ3XhHfmI8kS+ft6C3dw9B0wksyN8jmAEPrbJtOlOqBOTW2VwB59jMm1cHyXp7rVjxz7+nuECeeFv3wF+FW/LC9o4n89FYQ6st2CiOnDiGnrm7qGH+1NPLGZDa9FY7YepeRlExyM01vWSYKLwD1SEFsqVMqYkolqz3hQYyLQ/9c392nmVWaK0IufjDqtCclCToAwtNfx4gI9diK4DnMGy9k8dpagqBVMCjTw==
Authorization: AWS4-HMAC-SHA256 Credential=ASIA6PT4UXCKVZVFJVP3/20210607/us-east-1/execute-api/aws4_request, SignedHeaders=host;user-agent;x-amz-access-token;x-amz-date;x-amz-security-token, Signature=26e064abd123aac61ae9b76d5a9d92761f7d8bbf41cc1969c623dfd3fb33b345
Content-Length: 42

upload completely sent off: 42 out of 42 bytes
< HTTP/1.1 400 Bad Request
< Date: Mon, 07 Jun 2021 08:32:59 GMT
< Content-Type: application/json
< Content-Length: 79
< Connection: keep-alive
< x-amzn-RequestId: 31d913d4-9876-436c-9f7f-09d399271ae9
< x-amz-apigw-id: Ai71OFGnIAMFcoA=
< X-Amzn-Trace-Id: Root=1-60bdd9ba-47306d8a43a72d5c2b5acadd;Sampled=0
<
Connection #0 to host sandbox.sellingpartnerapi-na.amazon.com left intact
PHP Fatal error:  Uncaught GuzzleHttp\Exception\ClientException: Client error: POST https://sandbox.sellingpartnerapi-na.amazon.com/feeds/2020-09-04/documents resulted in a 400 Bad Request response:
{"errors":[{"code":"400","message":"Invalid input","details":"Invalid input"}]}
in spapi-php/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
Stack trace:
#0 spapi-php/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create()
#1 spapi-php/vendor/guzzlehttp/promises/src/Promise.php(204): GuzzleHttp\Middleware::GuzzleHttp{closure}()
#2 spapi-php/vendor/guzzlehttp/promises/src/Promise.php(153): GuzzleHttp\Promise\Promise::callHandler()
#3 spapi-php/vendor/guzzlehttp/promises/src/TaskQueue.php(48): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise{closure}()
#4 / in spapi-php/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113

Please find attached product XML feed.
split-amazon-products-1.txt

Be carefull closing tag:
document invalid error
<?xml version="1.0"?>
if you put a space between " and ? symbols, it should work.
<?xml version="1.0" ?>

Sorry for late reply. The issue was solved by providing proper input to the call. I figured this out after debugging and checking class parameters and amazon documentation.
BTW, there is another bug in the createFeed function. When you pass the json encoded string as input to the function call -
PHP Warning:  ksort() expects parameter 1 to be array, string given in /var/www/vhosts/w2bshop.com/amz.w2bshop.com/spapi-php/src/Client.php on line 69

Hi @aniruddhaad  i'm still getting same error, Can u please provide correct  Product XML Feed ? HEre is the error (i'm using production mode not Sandbox)
upload completely sent off: 200 out of 200 bytes
HTTP/1.1 400 Bad Request
Date: Fri, 08 Oct 2021 11:56:28 GMT
Content-Type: application/json
Content-Length: 117
Connection: keep-alive
x-amzn-RequestId: 27306ffa-0620-4340-8348-70b1e4ead8ef
x-amzn-RateLimit-Limit: 0.0083
x-amz-apigw-id: G4y87EeOoAMFd8Q=
X-Amzn-Trace-Id: Root=1-616031ec-04ed798a50c4d1ee67bc5462
Connection #1 to host sellingpartnerapi-na.amazon.com left intact
ETHON: performed EASY effective_url=https://sellingpartnerapi-na.amazon.com/feeds/2020-09-04/feeds response_code=400 return_code=ok total_time=0.292145
HTTP response body ~BEGIN~
{
"errors": [
{
"code": "InvalidInput",
"message": "Invalid Input",
"details": ""
}
]
}
~END~
AmzSpApi::ApiError: Error message: the server returns an error
HTTP status code: 400
Response headers: {"Date"=>"Fri, 08 Oct 2021 11:56:28 GMT", "Content-Type"=>"application/json", "Content-Length"=>"117", "Connection"=>"keep-alive", "x-amzn-RequestId"=>"27306ffa-0620-4340-8348-70b1e4ead8ef", "x-amzn-RateLimit-Limit"=>"0.0083", "x-amz-apigw-id"=>"G4y87EeOoAMFd8Q=", "X-Amzn-Trace-Id"=>"Root=1-616031ec-04ed798a50c4d1ee67bc5462"}
Response body: {
"errors": [
{
"code": "InvalidInput",
"message": "Invalid Input",
"details": ""
}
]
}
any thoughts?
-- Muhammad Ateq


[WIP]feat: add metadata api

Signed-off-by: saberwang<EMAIL_ADDRESS>Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #883
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

@halspang  Dapr grpc API is not fully implemented. Should we use HTTP API to obtain metadata? https://github.com/dapr/dapr/issues/4941


Update README for sea ice metrics

Updating the README file for the sea ice driver. This branch also has a fix that updates the demo line plots to show sea ice extent rather than sea ice area.

@acordonez Might be helpful to indicate that these metrics are based on sector area averaged results to quantify overall biases.  They do not include spatial pattern metrics (e.g., pattern correlation) which is more complicated with sea-ice.


Design class

Project requirements

Create a class Classroom with the following:

@label instance variable, should be initialized in the constructor.
Setter and getter for @label (remember about attr_accessor).
Create the has-many/belongs-to relationship between Classroom and Student. The following should be implemented:
Create the has-many side (a classroom has many students).
Create the belongs-to side (a student belongs to a classroom).
Make sure that when adding a student to a classroom it also sets the classroom for the student.
Make sure that when setting the classroom for a student it also adds it to the classrooms' students.

Create a class Book with the following:

@title and @author instance variables, should be initialized in the constructor.
Setters and getters for instance variables (remember about attr_accessor).

Create a class Rental with the following:

@date instance variable should be initialized in the constructor.
Setter and getter for @date (remember about attr_accessor).

Create the many-to-many (also has-many-through) relationship between Person and Book using the intermediate class Rental. The following should be implemented:

Create the has-many side of Book and Rental (a book has many rentals).
Create the belongs-to side of Rental and Book (a rental belongs to a book).
Create the has-many side of Person and Rental (a person has many rentals).
Create the belongs-to side of Rental and Person (a rental belongs to a person).

Modify the constructor of Rental so Book and Person are set in it.

@alexander16108 Remember when a person when he is creating a rental should say a book he/she want and the date right?

@DeliceLydia , honestly i do have to apologise because I'm still at a lose here
i still dont understand


Bad URLs should 404

By mistake, was POSTing to https://workspaces-api.dev.hubmapconsortium.org//tokens/. The response was {'message': 'Missing Authentication Token'}. More helpful to respond with a 4xx and appropriate message.

Django ignores situations where // is passed and interprets it as just / - this was just a token not actually being passed.


Fix typo in proto filename: commitedderecshare -> committedderecshare

 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.


TreeNode model inheriting from concrete class raises Operational Error

When a model subclasses another concrete model, an Operational Error is thrown using django's admin website: no such column: T.position.
I've tried with feincms3's, with concrete Page subclassing AbstractPage, and DiffusionPage subclassing Page. It seems that is because DiffusionPage holds a fk to Page table and do not contains itself the position column.
Here is a copy of the generated SQL (sqlite) expression:
('\n'
 '    WITH RECURSIVE __tree(tree_depth, tree_path, tree_ordering, tree_pk) AS '
 '(\n'
 '        SELECT\n'
 '            0 tree_depth,\n'
 '            printf("\x1f%%s\x1f", page_ptr_id) tree_path,\n'
 '            printf("\x1f%%020s\x1f", position) tree_ordering,\n'
 '            T."page_ptr_id" tree_pk\n'
 '        FROM app_diffusionpage T\n'
 '        WHERE T."parent_id" IS NULL\n'
 '\n'
 '        UNION ALL\n'
 '\n'
 '        SELECT\n'
 '            __tree.tree_depth + 1,\n'
 '            __tree.tree_path || printf("%%s\x1f", T.page_ptr_id),\n'
 '            __tree.tree_ordering || printf("%%020s\x1f", T.position),\n'
 '            T."page_ptr_id"\n'
 '        FROM app_diffusionpage T\n'
 '        JOIN __tree ON T."parent_id" = __tree.tree_pk\n'
 '    )\n'
 '    SELECT (1) AS "a" FROM "app_diffusionpage" , "__tree" WHERE '
 '("app_diffusionpage"."diffusion_id" = %s AND (__tree.tree_pk = '
 'app_diffusionpage.page_ptr_id)) ORDER BY ("__tree".tree_ordering) '
 'ASC  LIMIT 1')

Yes, that does not work right now -- the SQL would have to contain a JOIN but does not.
There are other projects trying to add CTE support to Django in a more generic way resp. in a way that better leverages the Django ORM's existing features e.g. https://github.com/dimagi/django-cte . Time would probably be better invested there; this library is probably almost too simplistic for this.

This ia a bug; TreeNode could ship with a system check or something which would detect this situation and emit a django.core.checks.Error.
Maybe the check could even be implemented on the queryset so that it also works if someone doesn't use the TreeQuerySet
I think this shouldn't be too hard to implement.

Fixed in 7bf2a32a6904a7c385b0f12704492d6642eb8553


Update to OpenSearch Dashboards 2.0.0

OpenSearch Dashboards 2.0.0 did a series of dependency updates that required changes from certain plugins to be able to build and run properly.
Please check out this issue:
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1206
Please let me know if you would like any assistance with this.
Thank you!

Hello @kavilla
Thanks, will have a look and keep you updated.


Package  avaliable on NuGet.org

Is it possible to make Lib available on NuGet.org? I have many restriction to download at Company

See https://github.com/redhat-developer/kestrel-linux-transport/issues/61#issuecomment-426617160.


Updated Bootstrap Social and remove plus from Google sign in icon

Updated the Bootstrap Social to the latest version.
Removed the unused entries that are not part of the sign in options (makes the CSS smaller).
The Sign in with Google icon will no longer have the + (No need to confuse people and it's more consistent with the rest)

(P.S. I'm the creator of https://github.com/lipis/bootstrap-social)

$ npm test
  total:     727
  passing:   727
  duration:  1.7s

:+1: Thanks for contributing!


Avoid Build Error

SimpleAnimation_impl.cs depends on UnityEditor. An error appeared at the time of build, so I fixed it.

Thanks


Legacy Certificates Not Labelled As Legacy

Describe the bug
With the first wave of v7 going live, the Information Security and Full Stack certificates have correctly moved to a "Legacy" header. The certificates, themselves, have not been labelled as "legacy", however.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
The Legacy certificates should probably say "Legacy" on them, and the URL should be updated from https://www.freecodecamp.org/certification/nhcarrigan/information-security-and-quality-assurance to https://www.freecodecamp.org/certification/nhcarrigan/legacy-information-security-and-quality-assurance, as an example, to prevent possible conflict with the new certificates.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 v. 1909
Browser: Chrome
Version: 83.0.4103.116

Additional Context
I will update this issue after I've claimed the new information security certificate to see how that behaviour is implemented.

Hey @nhcarrigan thanks for bringing this up.  As for the URLs, they're not supposed to change.  The intention is that people can link to them from outside and rely on those links continuing to point to their certificates.
Once you have the newer one it should have a unique link (and not have the word legacy in it!).

Is there an issue here? Was going to work on it, but not sure what the issue is.

Hi @nhcarrigan, thanks for catching this.
If I remember correctly, leaving the slug as /information-security-and-quality-assurance was a conscious decision so links to already claimed certificates don't break as @ojeytonwilliams mentioned. While we did change the URLs to other certificates in the past, we have to manage those redirects manually.
The new certificates have different names/versioned slugs (/information-security-v7). Going forward, the plan is to use the versioned slugs to determine whether a certificate is legacy or not. For instance, if we make a change to the information security certificate, /information-security-v7 will have the legacy header like in your screenshots, and /information-security-v8 will be the current one.
I think we can probably close this issue if all the new certificates behave the same way.

I ran into no issues when testing the certificates on the local instance with the development user. 🙂

Awesome, thanks for confirming that @nhcarrigan. I'll close this for now, but please feel free to reopen it if you notice anything else that we missed earlier.


Updating Katas to 0.6

This PR updates all katas to the 0.6 release.
The package references will be set to a suitable version after the release.

LGTM now. Waiting on QDK's CI build to confirm everything is ok.


Debugging with VsCode

This is not an issue but a help needed topic.
I was trying to understand the code and develop it further. And like most people i am using VSCode by default for javascript development. But i couldn't make debug work for me with the whole bable thing.
Can anyone suggest me, how we can utilize vscode debugging  if anyone has figured that out already.

Never Mind. I figured it out. Closing it.

@arihantdaga hey I am facing similar issues, could you please post your solution


Update remote logging screen | dev

Description of feature / user story
Update current remote logging screen to communicate clearer the risks of using remote logging, increase visual presence of Session ID, language is more plain language, and people are notified at all times when remote logging in on
Acceptance Criteria

Update the screen to match this updated screen
Add new screen with Session ID after remote troubleshooting is turned on
Update name from "remote logging" to "remote troubleshooting"

Given remote logging in enabled
When they navigate throughout the BC Wallet app
Then a banner notifying that remote logging is on is present below the header until remote logging is disabled
And there's the session ID displayed in that banner
Wireframes or relevant image assets / links

Looks good. The red banner was intended to stick to the top when scrolling but that's okay. It allows for more screen space just in case, despite it disappearing if the notifications list is long.


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
75c0136 -> 30f54d8

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.18.3 -> v1.19.0

Release Notes

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.19.0
Compare Source
Features

added the ability to add ready-for-review label by leaving comment with text "ready for review" (#629) (c60882d)

v1.18.4
Compare Source
Reverts

Revert "add label job (#627)" (#628) (bfa33a3), closes #627 #628

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

/run pipeline


Proxy settings ignored

Hi,
I'm attempting to request a new certificate (for use with IIS and RDP) and I'm unable to get the client to communicate via a Proxy server.
I've configured Proxy URL (including port number) in the Settings.json file and have left username and password as null as the port doesn't require authentication.
The following command is being ran:
wacs.exe --accepttos --target iissite --siteid 1 --certificatestore My --installation iis,script --script "Scripts\ImportRDS.ps1" --scriptparameters "{CertThumbprint}"
The output of the above command is as follows:

I've confirmed via Process Monitor that the wacs.exe process is attempting to make direct outbound connections to *.cloudfront.net instead of proxying these via our centrally hosted proxy server.

OS: Windows Server 2016 Standard, English
Version: <IP_ADDRESS>3, 64-bit, pluggable

A run with --verbose added to the command line might provide some extra insight. Also you might check if the keys in your .json file matches the documented ones, I recently figured that there was a mistake in the default file (unrelated to the proxy)
Anyway I'll look into it.

Ran through with the --verbose switch applied, and here was the output:

Also cross compared the keys in my settings.json file against those documented on the website and all appears to match.
Given the output from above, it's failing in the DomainParseService constructor and therefore within the Nager.PublicSuffix library.
Unless I'm mistaken (to which there's a chance), it looks like the Nager.PublicSuffix DomainParser/WebTldRuleProvider creates a HttpClient without proxy settings configured?

Yes this is a bug that I think got introducted in version 2.1. The build that I posted here will probably allow to work around the problem: #1294. The next release will use the proper proxy settings for the PSL download though.


Sticky scroll flashing non stop

Testing #210961

open slow.ipynb.txt
scroll "# Header<PHONE_NUMBER>111111111111989898" into view
scroll so that it gets very close the sticky scroll headers
:bug: things start flashing

https://github.com/microsoft/vscode/assets/1794099/a8b80af6-4665-4779-883c-8f69affd601a

Can repro in stable, hence not a regression.


Block_call (Clean up version of PR pull/26.)

Clean up, squashed version of https://github.com/priestjim/gen_rpc/pull/26
Trial implementation of block_call.
Implementation:

block_call(Node, M, F, RecvTO)
block_call(Node, M, F, A, RecvTO
block_call(Node, M, F, A, RecvTO, SendTO)

Basically the same as Call except for blocking the calling process, and prevent RPC server from handling other requests until current one exits.

The CallerPid acts as call correlation ID.

Ref: http://www.erlang.org/doc/man/rpc.html

Latest check-in addressing comment.
But I can't figure out how to make TraviscI check in the plt file post file generation, so future projects can just download the pt file instead of relying on travisci. Same logic applies to Erlang plt.
I am less than thrilled of Travici Github deployment provider.
https://docs.travis-ci.com/user/deployment/releases
PS:

I have a repo that uses travisci to generate plt file for otp & releases

TraviscI: https://travis-ci.org/linearregression/dialyxir
repo: https://github.com/linearregression/dialyxir


Add Pandas base extension tests for CharSpan

@frreiss I think I enabled all the Pandas tests that we could reasonably support for CharSpanArray. Some are skipped because they are not applicable, like arithmetic ops, and some could be enabled but are not too vital and require more effort, such as parsing tests that require _from_sequence_of_strings. If these changes look good to you, I'll so the same for TokenSpanArray, which should be almost identical.

Not sure what's going on with the travis build error. Some kind of mixup in pandas, will have to look at it later.

@BryanCutler those build errors were due to Pandas changing some of the internal APIs we use. The PR of mine that you just merged (thanks, BTW!) temporarily pinned Pandas at <= 1.0.5. I'm going to merge the current pull request now.
After the merge goes through, would you mind taking a look at the tests that break when you upgrade Pandas to version 1.1.0?

Thanks @frreiss , sure I will take a look with that version of Pandas


INVALID_FIELD: No such column 'type' on sobject of type Attachment

Hello, after scouring the dark recesses of stack exchange, I'm at a loss of what I'm doing wrong. I fear the problem isn't with my code.
var jsforce = require('jsforce');
var conn = new jsforce.Connection();
const fs = require('fs')
require('dotenv').config()
let deal = 'a5Id0000001Hr3d'
let project = 'a2m3o000001vDXwAAM'
conn.login(process.env.USER, process.env.PASS, function(err, res) {
    if (err) { return console.error(err); }
    conn.sobject('Attachment__c').create({
        Project__c: project,
        Type__c: 'Feasibility Analysis',
        State__c: 'CT'
    }, (err, res)=>{
        if(err){console.log(err)}
        console.log(res)
        let image = fs.readFileSync('test.PNG')
        let base64data = Buffer.from(image, 'base64')
    conn.sobject('Attachment').create({
        ParentId: res.id,
        Name: 'test.PNG',
        Body: base64data,
        ContentType: 'image/png'
    },function(err,res){
      if(err){console.log(err)}
      console.log(res)
       })
    })
})

This returns:
PS D:\JSForce Test> node index.js
{ id: 'a2b3o00000EmCYoAAN', success: true, errors: [] }
INVALID_FIELD: No such column 'type' on sobject of type Attachment
at HttpApi.getError (D:\JSForce Test\node_modules\jsforce\lib\http-api.js:250:13)
at D:\JSForce Test\node_modules\jsforce\lib\http-api.js:95:22
at tryCallOne (D:\JSForce Test\node_modules\promise\lib\core.js:37:12)
at D:\JSForce Test\node_modules\promise\lib\core.js:123:15
at flush (D:\JSForce Test\node_modules\asap\raw.js:50:29)
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
name: 'INVALID_FIELD',
errorCode: 'INVALID_FIELD'
}
undefined
I'm stumped by the "No such column 'type' on sobject of type Attachment" error. There is no 'type' field in my object, so I don't understand why it's giving me this error. I am running JSForce 1.10.0

@ppetitto1 - I tried this out and an attachment was created without any problems for me, so I don't have any advice on fixing your issue, but here is the code that I used with success:
var jsforce = require('jsforce');
const fs = require('fs');
require('dotenv').config();

async function start() {
  try {
    const conn = new jsforce.Connection({});
    await conn.login(process.env.SFDC_USERNAME, process.env.SFDC_PASSWORD);

    const base64data = fs.readFileSync('test.png', { encoding: 'base64' });
    const results = await conn.sobject('Attachment').create({
      ParentId: 'a006g00000ELWoHAAX',
      Name: 'test.png',
      Body: base64data,
      ContentType: 'image/png',
    });
    console.log(results);
  } catch (ex) {
    console.log('[ERROR]', ex);
  }
}

start();

Results: { id: '00P6g000007Bzn3EAC', success: true, errors: [] } - I confirmed the attachment was created successfully.

Holy guacamole you are my hero you beautiful man. Turns out using the buffer function was messing it up. When I tried your method, just simply setting encoding to base64 in the readfilesync, it worked like a charm. Thank you so much!


Implement one click / cli gcp deployment

Description
As Carbonable I should be able to implement one click gcp deployment
inorder to achieve solution in deploying in one click
Implement required infrastructure in GCP using proprietary Google Deployment Manager
Additional Information
[High Difficulty  - Go - Low Priority]
Acceptance Criteria

[ ]  one click gcp deployment

Contribute to Carbonable during ODHack:
Provable environmental infra

Go to the CarbonableOD Telegram: https://t.me/carbonableOD
Present yourself and tell us which issue you want to pick
Explain shortly how you want to tackle the issue
Ask a question if you need some clarity
When you're selected you will be assigned to the issue

Hey there, Khyati, could you please assign this to me?

Any update here?
I am willing to take it if not.
My Background
I’m a web developer with experience in cloud engineering and blockchain technology using Solidity and Cairo. I have contributed to open-source projects before and have some skills in deploying cloud infrastructure, I used once Google Cloud Platform (GCP) to deploy a side project and used GPS reverse geolocation. I also have used GoLang for some practice exercises, also have been reading the Google Deployment Manager for infrastructure automation. Given my background in GoLang and GCP, I am confident I can help implement a seamless one-click deployment solution, also to increase my open source contributions since I am looking for job.
How I Plan on Tackling This Issue

Understanding the Project Requirements: I’ll first review the existing project architecture and infrastructure requirements to ensure I have a complete understanding of what is needed for a one-click deployment.

Designing the Deployment: I will leverage Google Deployment Manager to define the required infrastructure as code. This will include setting up the necessary resources such as Compute Engine instances, networking components, and any other relevant GCP services, ensuring they are configured correctly for the deployment.

Implementing the Solution: The core of the solution will be to create a deployment script in GoLang that calls the GCP Deployment Manager API. The script will be designed for simplicity, with a focus on allowing users to deploy with a single click or command. I will also ensure that the script integrates smoothly with any existing code or pipelines.

Testing and Documentation: Once implemented, I’ll test the one-click deployment process to ensure everything works as expected. I will provide clear documentation so that others can easily replicate or modify the setup if needed.

By taking this approach, I aim to deliver a solution that meets the acceptance criteria of a true one-click deployment on GCP.
Please let me know if there is anything wrong in my planning, or you can contact me in my Telegram "@luisdi_mora98"

I will not continue with this. You can work on it @LuisDi98

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have a solid background in software development with a strong focus on Go and cloud technologies. Over the past few years, I have worked on several projects involving infrastructure automation and deployment, which has equipped me with a deep understanding of cloud services, particularly Google Cloud Platform (GCP). My experience includes using the Google Cloud SDK and various APIs to manage and deploy resources efficiently.
How I plan on tackling this issue
Sure! Here’s a draft for your application form that highlights your background and approach to the project:
Tell us about your background and how it can be leveraged:
I have a solid background in software development with a strong focus on Go and cloud technologies. Over the past few years, I have worked on several projects involving infrastructure automation and deployment, which has equipped me with a deep understanding of cloud services, particularly Google Cloud Platform (GCP). My experience includes using the Google Cloud SDK and various APIs to manage and deploy resources efficiently.
In my previous roles, I successfully implemented automated deployment processes that improved operational efficiency and reduced downtime. My ability to write clean, maintainable code and my familiarity with DevOps practices will be instrumental in creating a seamless one-click deployment solution.
How would you approach the problem:
To tackle the challenge of implementing a one-click GCP deployment, I would follow a structured approach:
Requirements Gathering: I would begin by gathering detailed requirements for the deployment, identifying all necessary resources and configurations.
Designing Infrastructure: Next, I would design the infrastructure using Google Deployment Manager, creating templates that define the resources needed for deployment. This would ensure flexibility and reusability.
Developing the Go Application: I would then develop a Go application that acts as a command-line interface for triggering the deployment. This tool would handle user input, manage authentication, and interact with the Deployment Manager API.
Testing and Validation: Prior to final deployment, I would conduct thorough testing to ensure that all configurations are correct and that the deployment process works flawlessly. I would also implement error handling to manage potential issues effectively.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have experience in a few languages and been trying to get issues to exploit the knowledge

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have experience in Go and GCP, specializing in automating cloud deployments. My work includes implementing one-click GCP deployments using Google Deployment Manager and writing efficient, reliable Go code for infrastructure automation.
How I plan on tackling this issue
I would create GCP deployment templates, write a Go script to automate deployment with one click, and ensure it’s reliable with error handling and clear documentation

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I’m a Software developer with 3 years of experience, and I would love
to make my first contribution to this project. I'm excited to take
on this issue to challenge myself, and contribute to the project's success.
I'm also a member of the Dojo Coding community CR.
How I plan on tackling this issue
Well First, I’ll read through the Contributor Guidelines and README to ensure I understand the project structure, coding standards, and the process you’re following.  Then review the existing project architecture and infrastructure requirements to ensure I have a complete understanding of what is needed for carbonable-labs / indexer
Using Google Deployment Manager, I will define the infrastructure as code, including key components such as Compute Engine instances, network configurations, and other essential GCP services. These components will be carefully set up to meet deployment needs.
I will implement a GoLang-based deployment script that interacts with the GCP Deployment Manager API, enabling one-click deployment by initiating all required resources in a single step
I will test the one-click deployment to ensure everything is functioning as intended. I will also write comprehensive documentation detailing the deployment process, allowing for future modifications or replication by other developers.
If I run into any problems or questions, I’ll reach out to the maintainers for assistance.
Thank you for reading my application.


Can multi-core processing be used to improve performance？

Is the current performance in the case of single core？Can multi-core processing be used to improve performance？

aec_mp.py is using multi-core. The last two columns show the performance improvement of using multi-core for AEC.

Thank you for your reply！


Is it possible to put the spinner into the second terminal column?

Hi,
Is it possible to influence the location of the spinner? I checked lib.rs, didn't find a clue.
UPD
I've got the desired effect editing two lines starting with line 147:
                    writeln!(stdout, " {} {}", emoji_to_write, self.text).unwrap();
                    should_stop_cycle_loop = true;
                } else {
                    write!(stdout, " {}{}", frame, self.text).unwrap();

adding a space at the beginning of format strings. This is not exactly what I hoped for.

Would some kind of user-defined prefix be enough for your use-case?

Most certainly!

Released v0.3.2


Periodical testing

Add periodical testing with a cron CI job

LGTM Remember to remove the on pull request before merging 6h to run is a lot of time, considering we'll eventually need to run all solidity/simple tests, maybe its a good idea to look into a custom runner for this

Alternatively (or additionally) we could use a matrix strategy to parallelize.


Fixed normalizeWhitespace option, added functionality for translation by key

Hello,
This option should be false, because when it is true 'localize' method can't find some strings.

@bitjson hi,
I added some more functionality. Please check it!

Hi @kirillkostko, I'm sorry I haven't touched this project before this weekend! Thank you for contributing your work!
There are several features I wanted to include in this plugin that were pretty difficult to do without some better structure (#3, #4, and several other features). I started a new repo, s18n, to bring the basic logic out of the gulp plugin and into a separate node module. This simplifies the plugin a lot, follows the Gulp philosophy better, allows for better testing, and makes it possible to use this localization style in other build systems.
I finally got around to reconciling the codebases together yesterday, which is now on the s18n branch in this repo. It's a full rewrite, and solves a lot of the issues I had with the original plugin.
This pull request has some great ideas, and I'd like to get them merged into the new project. I already made the change to the normalizeWhitespace option and credited you as the author in s18n commit 803ed55. Thanks for finding that!
I would love to merge the other improvements here too – you've clearly done a lot of work on this. Would you be willing to take a look at s18n and make this pull request there?


Update units-of-measure.md

Add a mention that F# can support the feature for other types, for type safety purpose (not only arithmetic), and the fact it is zero cost abstraction.

Internal previews

📄 File
🔗 Preview link

docs/fsharp/language-reference/units-of-measure.md
Units of Measure

Thanks again @smoothdeveloper
I've merged this.


Items Missing/Inaccuarcy

Hey there,
I love this mod.
Package: FTB Beyond 1.5.3
Xnet: 1.2.0 (old version but I didn't find anything relating to my issue in the patchnotes)
Issue: For Autocrafting in my ME System (smelting, pulverizing). I use interafaces hooked to Chests which feed an array of Thermal Expansion Machines ( Pulverizers, Redstone Furnace).
I replaced all Ender IO conduits with a simpler and more compact Xnet setup. The xnet setup proviedes energy to machines, pulls from chest stackwise, inserts into machines, and pulls from the machines stackwise and inserts into an ME Interface.
As I tested different crafting orders. It seems 10-20% of the items get somehow lost or deleted.
Always need to cancel my crafting orders as the chest is already empty but the ME system still waits for resulting products.
If u need any Info in reproducing this bug I'm glad to help.
Regards
Kendalor

This is likely caused by using an outdated version.  Please update first


not digitized, but on AAPB?

V_120F2A8588A84D4D9F64358518FF7C50:

This is what it will look like, when my fix for #8 is in. Do we want to message this differently? Obviously, it was been digitized, it's just not available here. Should it be playable here? Even if not, should it be faceted as digitized? Would we want to grab a still from AAPB if nothing else?
(Doing nothing is also a valid choice.)

@mccalluc: Sorry, I couldn't find this earlier.
Do we want to message this differently?

Instead, could the digitize-on-demand blurb say: This item has not been digitized. If you are interested in sponsoring the digitization of this title, Contact Us. In your message, please include the URL for this particular record.

COMMENT: Please make the text fill up the box.

Obviously, it was been digitized, it's just not available here. Should it be playable here?

Great IDEA!! We should 1) embed the video from AAPB's Sony Ci. 2) We should include a blurb below that video that says: "This video/audio was digitized by the American Archive of Public Broadcasting. To discover more content from public media stations across the country, visit americanarchive.org

Even if not, should it be faceted as digitized?

It should be faceted as digitized.

Would we want to grab a still from AAPB if nothing else?

Yes, please use the AAPB thumbnail already created for AAPB. This can be used on search results.

COMMENT: For all things that are truly not digitized, please use the icons created by Digital. They should be used on search results and on the record page where the player would go (like on AAP[&#X1f60e]

From: mccalluc<EMAIL_ADDRESS>Sent: Thursday, February 11, 2016 10:32 AM
To: WGBH/openvault3
Subject: [openvault3] not digitized, but on AAPB? (#172)
V_120F2A8588A84D4D9F64358518FF7C50:
[screen shot 2016-02-11 at 10 26 42 am]https://cloud.githubusercontent.com/assets/730388/12980337/103c07cc-d0aa-11e5-9daf-3706f490962d.png
[https://cloud.githubusercontent.com/assets/730388/12980337/103c07cc-d0aa-11e5-9daf-3706f490962d.png]
This is what it will look like, when my fix for #8https://github.com/WGBH/openvault3/issues/8 is in. Do we want to message this differently? Obviously, it was been digitized, it's just not available here. Should it be playable here? Even if not, should it be faceted as digitized? Would we want to grab a still from AAPB if nothing else?
(Doing nothing is also a valid choice.)

Reply to this email directly or view it on GitHubhttps://github.com/WGBH/openvault3/issues/172.

(@caseyedavis12 : Just a markdown style point: prefixing with '>' means quotation, so the section above is inverted, and a little hard for someone outside to read. I'll fix...)

This could get complicated, but sub-tasks:

This counts as digitized. Update pb_core.
#178 for placeholder images.
Related to that, I think we should keep the text the current width. Reasons given there.
Play media from AAPB: This could get complicated, and would require loosening the referer check in the media_controller over in that project, and having special logic here to point over there. Won't be done any time soon.
Wording changes. These seem arbitrary, and are longer than the text we have right now. I'm not going to do them right now, and with more eyes on it we can see if the current text is unclear.

@mccalluc: Can you show me a screenshot after you add the placeholder image? I think that the blank space on the text looks weird. If there is no transcript, I think it should fill up the box.
Regarding the wording changes, my primary purpose of changing it was to better communicate that it will cost the user money to digitize the tape. It may help filter the number of emails that @muraszko receives to only those who are actually willing to pay.

@caseyedavis12 You can pre-populate the subject and body of mailto links. You don't want to go too crazy (because of escaping characters and what not), but you can stub out a basic message, that could include a link to the current item.

@caseyedavis12 e.g. Contact Us

if we pre-populate the email, could the text be reduced to this?

This item has not been digitized. If you are interested in sponsoring digitization please, Contact Us.

@afred: Yes!

@Muraszko : Don't read this whole thread, but we have OV items that are not digitized, but can be viewed on AAPB. Could we just consider this a data problem? ie, copy the media files from the AAPB-Ci to the OV-S3, and update the FM records accordingly? I'd really like to avoid special purpose code for cross-site embedding.

@mccalluc It would be possible, but I'm not sure they want to have the video hosted in two places.  Plus, I'd have to process, add a watermark.  So it's up to Casey and how she wants to display or link out that information.

@mccalluc and I just decided that we will link out.
Casey will talk with @sroosa and @muraszko about how we will update Open Vault filemaker every time we add more WGBH content in the AAPB Online Reading Room.