updated airdrop request values

The current example of requesting an airdrop of 10 sol three times results in failed transactions due to the current airdrop limit of 2 sol per request and 24 sol per account per day. This PR updates the example to work within those constraints.

wdyt of making docs airdrop entry more robust and linking out to that instead of replicating the information here?
Adding an example that fails due to too large a request, then demonstrates how to discover the cause of the failure by looking up the memo and finally making an appropriate request would be awesome!

@t-nelson see updates! Is this along the lines of what you had in mind?


Added danger-plugin-jest

Hi,
This PR address #1221 . Please review.
Thanks,
Apoorv

Could not read test results.

Hi @mxstbr , running npm test automatically generates test-results.json. Though I have already added it, is it required to push it anyway?


COMMAND PROMPT

just opens command prompt saying hack can be broken or smth that

Update Geometry Dash to the latest version


Allow to use spring by setting SPRING in .env

I decided not to document it in .env.example because it can cause the strangest errors, and everyone who wants to use spring knows where to look for it :smile:

Looks good.  I've been bitten enough times by weird Spring eagerload bugs that I don't use it, but you're welcome to. :smile:


Usage of RNPM when linking the binaries.

You could update the readme saying that developers can install https://github.com/rnpm/rnpm and link the package up a lot quicker and easier.

@jamesone But does it work?

Did it work? @jamesone

any update?


Preloading for spark interpreter

Spark interpreter takes significant time to load. If user opens a notebook with no spark interpreter running, it would save a lot of time if it starts to load at the moment the notebook opens.
It would be also good to have a preloading indication somewhere on the page.

The current status - working prototype. Preloading is working, but goes in conflict with %spark.conf. Needs additional optimization.
Preloading indicator is still in TODO.

The feature is implemented on the UI-side. Added indicator and %spark.conf workarounds. Might need some UX polishing.

The feature is tested and does suffice the current requirements.


Viewing the event queue

Using the displayQueue function would make it possible to see the upcoming events as well as their order.

Thank you for adding the displayQueue() function to the API.


Json Schema Validation is currently invalid

Creating an ObservationForm is currently not possible because the CamelCaseJSONParser parser is executed before the serializer and validator. This means that any fields the validator sees are transformed to snake_case while the current Json Schema clearly states camelCasefor the form field definitions.

To solve this add the following to the REST_FRAMEWORK configuration:
'JSON_UNDERSCOREIZE': {
    'no_underscore_before_number': True,
    'ignore_fields': ('definition', 'data',),
},

Additionally the schema currently states that the step widgetAttribute is expected to be a number while the app-kit outputs it as a string.

implemented in v13.7


Using Sagas like middleware to reduce boilerplate, and putting actions to only other Sagas

Hey so I was following along with your real world example, but there was a whole bunch of repeated logic:
For example in your actions file:
export const USER = createRequestTypes('USER')
export const REPO = createRequestTypes('REPO')
export const STARRED = createRequestTypes('STARRED')
export const STARGAZERS = createRequestTypes('STARGAZERS')

// ....other stuff

export const user = {
  request: login => action(USER.REQUEST, {login}),
  success: (login, response) => action(USER.SUCCESS, {login, response}),
  failure: (login, error) => action(USER.FAILURE, {login, error}),
}

export const repo = {
  request: fullName => action(REPO.REQUEST, {fullName}),
  success: (fullName, response) => action(REPO.SUCCESS, {fullName, response}),
  failure: (fullName, error) => action(REPO.FAILURE, {fullName, error}),
}

export const starred = {
  request: login => action(STARRED.REQUEST, {login}),
  success: (login, response) => action(STARRED.SUCCESS, {login, response}),
  failure: (login, error) => action(STARRED.FAILURE, {login, error}),
}

export const stargazers = {
  request: fullName => action(STARGAZERS.REQUEST, {fullName}),
  success: (fullName, response) => action(STARGAZERS.SUCCESS, {fullName, response}),
  failure: (fullName, error) => action(STARGAZERS.FAILURE, {fullName, error}),
}

and then in your actual sagas file
const fetchUser       = fetchEntity.bind(null, user, api.fetchUser)
const fetchRepo       = fetchEntity.bind(null, repo, api.fetchRepo)
const fetchStarred    = fetchEntity.bind(null, starred, api.fetchStarred)
const fetchStargazers = fetchEntity.bind(null, stargazers, api.fetchStargazers)

There's a lot more too, but I think it would be redundant to post it.
I used that as a guide for my own personal project since I had something really similar, but I realized that I could cut down on a lot of that by writing an apiCall saga and a promise Saga much like how one would have written middleware:
// Create lifecycle of a promise
const createPromiseLifecycle = (base) => ({
  PENDING:  `${base}_PENDING`,
  RESOLVED: `${base}_RESOLVED`,
  REJECTED: `${base}_REJECTED`
})

function* apiCall() {
  while(true) {
    // Grab all actions with the API intention
    const { type, payload: { method, options } } = yield take((action) => action[actions.API])

    // Pass on the pending API call to the promise saga
    yield put({
      [actions.PROMISE]: true,
      type,
      payload: {
        promise: call(api[method], options)
      }
    })
  }
}

function* promise() {
  while(true) {
    // Grab all actions with the PROMISE intention
    const action = yield take((action) => action[actions.PROMISE])
    const lifecycle = createPromiseLifecycle(action.type)

    // Put out the fact the promise is pending
    yield put({ type: lifecycle.PENDING })

    // Try to resolve the promise
    try {
      const result = yield action.payload.promise
      yield put ({
        type: lifecycle.RESOLVED,
        payload: {
          result
        }
      })
    } catch(err) {
      yield put ({
        type: lifecycle.REJECTED,
        payload: {
          err
        }
      })
    }
  }
}

I have two questions about this:

Is this against what sagas are about? I've just interpreted them as middleware with much more advanced capabilities.
Is there any equivalent to next from middleware in sagas? If you noticed I do a put in my apiCall, but it has an undesired behavior as it also sends that action to the reducers. I want to be able to do a put that only my sagas can receive basically.

Is this against what sagas are about? I've just interpreted them as middleware with much more advanced capabilities.

Against no I dont think. But sagas can do more than that. See
http://stackoverflow.com/questions/34930735/pros-cons-of-using-redux-saga-with-es6-generators-vs-redux-thunk-with-es7-async

Is there any equivalent to next from middleware in sagas? If you noticed I do a put in my apiCall, but it has an undesired behavior as it also sends that action to the reducers. I want to be able to do a put that only my sagas can receive basically.

As long as the action types arent of any meaning to the reducer. It will ignore them. But you can if you want create a filter middleware that intercept all saga actions and put it after the redux-saga middleware in the middleware chain

@yelouafi: what do you think of what @AriaFallah wrote, as a pattern? I too am put off by the repetitive boilerplate.

@braco not really sorry. I haven't worked on that project where I was using redux-saga in a while.

I found this issue after looking for solutions to reduce the amount boilerplate. For example, to an API call like login you have three LOGIN_* actions, a login action creator, a login saga, and a login API utility function.
I haven't spent much time abstracting this although I did write an API request saga factory that looks something like the code posted above.
I'm eager to see what other users are doing.

I had the same issue, so I just created a small gist with my own implementation of an action creator factory: https://gist.github.com/jiayihu/811f2dc704d6ce6308d679a987348b20
Can be used as following:
export const addInvoice = createAction('ADD_INVOICE', {
  request: (invoice) => ({ invoice }),
  success: (invoice, result) => ({ invoice, result }),
});


feat: de-duplicate form dialog component

Description

Deduplicate the FormDialog component.
All the Share application & Invite Dialog de-duplicated.

Add a TL;DR when description is extra long (helps content team)

Fixes #22312

if no issue exists, please create an issue and ask the maintainers about this first

Media
https://www.loom.com/share/2f4238e412b346cf8d616ec08ca9e8e5
Type of change

Please delete options that are not relevant.

Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/deploy-build-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview skip-tests="true"

/build-deploy-preview skip-tests="true"

/build-deploy-preview skip-tests="true"

/build-deploy-preview skip-tests="true"

/build-deploy-preview skip-tests="true"

/build-deploy-preview skip-tests="true"

/build-deploy-preview skip-tests="true"


Fix Typo in Staging Options

Proposed changes
Change three to two.
It said that there were three options for staging docs. Only two were listed.

Deploy preview for docsdocker ready!
Built with commit 8884af061f585282c829e1154e4bc0d3d69d5b01
https://deploy-preview-7386--docsdocker.netlify.com


Allow celery and rdkit coexist in Python 2.7

Using celery and rdkit.Chem.Descriptors in Python 2.7 fails due to problems with print_function in the isCallable test. This fix removes print_function before the isCallable test.
Fixes #1434

Though the fix is small and won't break anything, this seems to me like we're adding a hack to the RDKit in order to workaround a bug in Celery. That doesn't seem really right.

I can see your point, however I wouldn't call it a bug - just a lot of incompatibilities.

RDkit uses wild cards imports. Something that isn't so great, however simplifies the descriptor setup immensly
RDkit in general doesn't control the export of modules. That's why the print_function, os, numpy, and a few other things leak into the Descriptors module. Usually, not a problem, but due to the wildcard import, it has consequences here.
print_function uses objects that are old-style classes. As the __future__ module supports Python 2.6, there is no way around it. Moving everything to python 3, will resolve it (but that is not for here to discuss).
celery support 2.7 and 3.x only. That's why there code relies on __mro__ here: http://docs.celeryproject.org/en/latest/_modules/celery/utils/abstract.html.

So how do we resolve the problem.

We can leave the code as-is and move what we learned into our collective knowledge so that if anyone has the problem in the future, we know the solution.
We apply the fix (and hope that we remove it should we ever stop supporting Python 2.
We file a bug report with the celery team (hahaha - I'm not really serious here).
We address the wild card import / export (not worth it in my opinion)

I can't  say I completely understand, but you could omit the test for all feature names in future which may be a tad less hacky.
https://docs.python.org/2/library/__future__.html

Brian Kelley

On Jun 4, 2017, at 11:58 AM, gedeck<EMAIL_ADDRESS>wrote:
I can see your point, however I wouldn't call it a bug - just a lot of incompatibilities.
RDkit uses wild cards imports. Something that isn't so great, however simplifies the descriptor setup immensly
RDkit in general doesn't control the export of modules. That's why the print_function, os, numpy, and a few other things leak into the Descriptors module. Usually, not a problem, but due to the wildcard import, it has consequences here.
print_function uses objects that are old-style classes. As the future module supports Python 2.6, there is no way around it. Moving everything to python 3, will resolve it (but that is not for here to discuss).
celery support 2.7 and 3.x only. That's why there code relies on mro here: http://docs.celeryproject.org/en/latest/_modules/celery/utils/abstract.html.
So how do we resolve the problem.
We can leave the code as-is and move what we learned into our collective knowledge so that if anyone has the problem in the future, we know the solution.
We apply the fix (and hope that we remove it should we ever stop supporting Python 2.
We file a bug report with the celery team (hahaha - I'm not really serious here).
We address the wild card import / export (not worth it in my opinion)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, that logic makes sense to me.


Notice a different between jax.image.resize and F.interpolate when using "bicubic"

Description
Hi, I am trying to convert a Pytorch model to JAX model, and I find there are some implementations different in "bicubic".
Here is a script I have used to confirm that the outputs are different.
import torch
import torch.nn as nn
import jax.numpy as jnp
import jax
import numpy as np

input_arr = jnp.array([
    [0, 1, 2, 3, 4],
    [5, 6, 7, 8, 9],
]) / 9

torch_input_arr = torch.from_numpy(np.array(input_arr)).unsqueeze(0).unsqueeze(0)
output = jax.image.resize(
    image=input_arr,
    shape=(4,10),
    method="bicubic")

interpolate_without_align_corners = torch.nn.functional.interpolate(
    torch_input_arr.float(),
    size=(4, 10),
    mode="bicubic",
    align_corners=False,
)

print("jax: ", output)
print("torch interpolate without align corners",interpolate_without_align_corners)

from the prints I get:
jax:  [[-0.05882353 -0.03036592  0.0298608   0.08986928  0.14542481  0.20098035
   0.25653598  0.31654444  0.37677112  0.40522873]
 [ 0.10527544  0.13373306  0.19395977  0.25396827  0.30952382  0.36507937
   0.42063496  0.48064342  0.54087013  0.5693277 ]
 [ 0.4306723   0.45912993  0.5193566   0.57936513  0.6349207   0.69047624
   0.74603176  0.8060403   0.86626697  0.89472455]
 [ 0.5947712   0.62322885  0.6834555   0.74346405  0.79901963  0.85457516
   0.9101307   0.9701392   1.0303658   1.0588235 ]]
torch interpolate without align corners tensor([[[[-0.0703, -0.0373,  0.0156,  0.0855,  0.1306,  0.1966,  0.2418,
            0.3116,  0.3646,  0.3976],
          [ 0.1141,  0.1471,  0.2001,  0.2700,  0.3151,  0.3811,  0.4262,
            0.4961,  0.5490,  0.5820],
          [ 0.4180,  0.4510,  0.5039,  0.5738,  0.6189,  0.6849,  0.7300,
            0.7999,  0.8529,  0.8859],
          [ 0.6024,  0.6354,  0.6884,  0.7582,  0.8034,  0.8694,  0.9145,
            0.9844,  1.0373,  1.0703]]]])

I tried some other resizing methods. e.g., linear and bilinear, and they look fine. Does anyone have a workaround for it?
What jax/jaxlib version are you using?
No response
Which accelerator(s) are you using?
No response
Additional system info
No response
NVIDIA GPU info
No response

I'm not sure what's up here. The output of JAX exactly matches Pillow and TensorFlow for the same bicubic resize, so I don't think we're doing something wrong here, but PyTorch must be using a different convention for something as opposed to all the other systems.

@johnpjf I could use your input here.
I looked into this a bit more. There are two groups of behaviors for cubic upsampling:

pillow, JAX, Tensorflow all agree (almost exactly)
PyTorch (with align_corners=False) and OpenCV agree (almost exactly)

I think there are two different things happening here:
JAX and PyTorch use different cubic interpolation kernels
JAX/pillow/TF use the Keys cubic kernel with A = -0.5 (https://en.wikipedia.org/wiki/Bicubic_interpolation#Bicubic_convolution_algorithm).
PyTorch/OpenCV uses a cubic kernel with A = -0.75. At least some users consider this a bug (https://github.com/opencv/opencv/issues/17720 ), and
that set of parameters suffers from ringing artifacts [^mitchell].
[^mitchell]: Mitchell, D.P. and Netravali, A.N., 1988. Reconstruction filters in computer-graphics. ACM Siggraph Computer Graphics, 22(4), pp.221-228.
It's actually quite easy to get JAX to use the PyTorch/OpenCV kernel, if we use:
def _fill_pytorch_cubic_kernel(x):
  out = ((1.25 * x - 2.25) * x) * x + 1.
  out = jnp.where(x >= 1., ((-0.75 * x + 5*0.75) * x - 8 * 0.75) * x + 4*0.75, out)
  return jnp.where(x >= 2., 0., out)

in place of https://github.com/google/jax/blob/e51d12cdef0fd118e6f8cc3357cd8f95a68a79fa/jax/_src/image/scale.py#L36
This solves the mismatch except for a band of 3-4 pixels near the edge of the image. This is because:
JAX and PyTorch use different approaches for edge padding
Cubic interpolation requires sampling pixel values from outside the original input image. JAX/pillow/TF handle this by truncating the convolutional kernel and rescaling it to keep its total weight 1. I believe PyTorch handles this by edge-padding (i.e., repeating the value on the edge). This leads to slightly different values in a 3-4 pixel band near each edge.
I'll look into this a bit further, we can probably replicate the PyTorch behavior (optionally) with a bit more work.

Hi @hawkinsp Thanks for digging into these differences! I actually tried to reproduce some research works in JAX and noticed there are some performance degrades, then I started to look into some lower-level implementations and found out this : )

@hawkinsp I don't know about pytorch but your description of JAX's resize sounds correct, and yes there are different choices for the bicuibic kernel. The other thing to keep in mind is that when downsampling JAX's resize will do anti-aliasing by default.

@johnpjf I'm particularly curious about the edge padding behavior. How do the OpenCV/PyTorch behaviors compare with what JAX/TF/pillow do?

I should add: it's actually slightly annoying to mimic the PyTorch edge padding behavior because of the antialiasing we do on downsampling. The antialiasing means the kernel can be of an arbitrary width measured in input pixels.

TF is the same:
https://chromium.googlesource.com/external/github.com/tensorflow/tensorflow/+/refs/heads/master/tensorflow/core/kernels/image/scale_and_translate_op.cc#103
I think we could mimic the PyTorch edge behavior if we wanted to, no, we'd just shift the kernel weight to that last pixel and make it zero outside? That said, I'm skeptical this will cause large enough differences to break models.

Hi @hawkinsp , thanks for digging into this and the great write up.
I have a similar issue but I want to replicate JAX's behaviour in Torch.
Based on your findings, is it possible to do this with an appropriate set of args?
Thanks!

@johnpjf I could use your input here.
I looked into this a bit more. There are two groups of behaviors for cubic upsampling:

pillow, JAX, Tensorflow all agree (almost exactly)
PyTorch (with align_corners=False) and OpenCV agree (almost exactly)

I think there are two different things happening here:
JAX and PyTorch use different cubic interpolation kernels
JAX/pillow/TF use the Keys cubic kernel with A = -0.5 (https://en.wikipedia.org/wiki/Bicubic_interpolation#Bicubic_convolution_algorithm).
PyTorch/OpenCV uses a cubic kernel with A = -0.75. At least some users consider this a bug (opencv/opencv#17720 ), and that set of parameters suffers from ringing artifacts 1.
It's actually quite easy to get JAX to use the PyTorch/OpenCV kernel, if we use:
def _fill_pytorch_cubic_kernel(x):
  out = ((1.25 * x - 2.25) * x) * x + 1.
  out = jnp.where(x >= 1., ((-0.75 * x + 5*0.75) * x - 8 * 0.75) * x + 4*0.75, out)
  return jnp.where(x >= 2., 0., out)

in place of
https://github.com/google/jax/blob/e51d12cdef0fd118e6f8cc3357cd8f95a68a79fa/jax/_src/image/scale.py#L36
This solves the mismatch except for a band of 3-4 pixels near the edge of the image. This is because:
JAX and PyTorch use different approaches for edge padding
Cubic interpolation requires sampling pixel values from outside the original input image. JAX/pillow/TF handle this by truncating the convolutional kernel and rescaling it to keep its total weight 1. I believe PyTorch handles this by edge-padding (i.e., repeating the value on the edge). This leads to slightly different values in a 3-4 pixel band near each edge.
I'll look into this a bit further, we can probably replicate the PyTorch behavior (optionally) with a bit more work.
Footnotes

Mitchell, D.P. and Netravali, A.N., 1988. Reconstruction filters in computer-graphics. ACM Siggraph Computer Graphics, 22(4), pp.221-228. ↩

Hi @hawkinsp, it would be really nice if this work is continued. I'm trying to convert a pytorch model to flax and this "Bicubic interpolate" layer is the only part that prevents the exact replication of the model.
Thank you.


Document grammar for device IDs

The spec is currently missing any definition of the grammar for a device ID. While it is implied that they should just be a random string of characters, at least the following should be explicit:

Minimum and maximum character (or byte) lengths
Allowed and disallowed characters
Any expected patterns, such as starting with a letter followed by N digits

There needs to be some UX consideration beyond considering them opaque byte sequences, since they are displayed visually to users in some cases.
Though not specific to the grammar of the ID, the spec should also address what the scope of uniqueness is for device IDs. Do they need to be universally unique? Or only unique to the user the device belongs to? Or unique to the user's homeserver?
This may be considered part of #666.

https://matrix.org/docs/spec/intro.html#devices says:

Devices are identified by a device_id, which is unique within the scope of a given user.

beyond that, I'm not sure there is anything here which isn't already covered by #666 (which explicitly mentions device ids)?

Perhaps this is an issue with having important information that exists only in the intro document. I'd expect the intro to explain general concepts of how Matrix works, but that any details useful to an implementer be available within the main document for that API, perhaps with an explicit link to other documents when information would otherwise be duplicated between documents. As is, I would've had to guess to go check the introduction for the information I wanted while looking at the client-server spec, which obviously wasn't something that occurred to me. :}

What is the current guidance on what a device ID should and/or can be, from an "implementing a homeserver" perspective? #666 is about 'completely opaque identifiers', but that clashes with the * wildcard character usage in some device_id fields, so evidently it can't just be any byte sequence.
Even just some practical data on what major clients currently do or allow, would be useful here.


nightMode not toggling or reading gpios on hi3518ev100

Required information

Camera board id: hi3518ev100
OpenIPC version: <IP_ADDRESS>
Commit:
Branch:
Tag:
installation method: (by manual https://github.com/OpenIPC/openipc-2.1/wiki/install_hisi or another)
modified majestic.yaml: yes
cat /dev/kmsg

root@openipc-hi3518ev100:~# cat /dev/kmsg
cat: read error: Invalid argument

Issue description
when attempting to use night mode controls with majestic, the gpio reading or toggling does not seem to occur until I run ipctool gpio mux X for each of the pins (sensor, cut filter pins, illuminator pins), while majestic is running e.g.
ipctool gpio mux 73
ipctool gpio mux 76
ipctool gpio mux 77
ipctool gpio mux 79

then toggling night mode again
at this point my suspicion is that there is some issue with gpio pinmux setup in majestic, or perhaps there is somethign else going on with the way hi3518ev100 pinmuxes are setup by default
Information to attach
root@openipc-hi3518ev100:~# cat /etc/majestic.yaml
system:
  webAdmin: enabled
  buffer: 2048
image:
  mirror: false
  flip: false
  rotate: none
  contrast: 50
  hue: 50
  saturation: 30
  luminance: 40
osd:
  enabled: false
  template: "%a %e %B %Y %H:%M:%S %Z"
  posX: 16
  posY: 16
nightMode:
  enabled: true
  nightAPI: true
  irSensorPin: 77
  backlightPin: 73
  irSensorPinInvert: false
  irCutPin1: 76
  irCutPin2: 79
  dncDelay: 5
records:
  enabled: false
  path: /mnt/mmcblk0p1/%F/%H.mp4
  maxUsage: 95
video0:
  enabled: true
  gopMode: normal
  rcMode: vbr
  bitrate: 1024
  fps: 15
video1:
  enabled: false
jpeg:
  enabled: true
mjpeg:
  size: 640x360
  fps: 5
  bitrate: 1024
audio:
  enabled: false
  volume: auto
  srate: 8000
rtsp:
  enabled: true
  port: 554
hls:
  enabled: false
youtube:
  enabled: false
motionDetect:
  enabled: false
  visualize: false
  debug: true
ipeye:
  enabled: false
watchdog:
  enabled: true
  timeout: 16
isp:
  blkCnt: 6
  lowDelay: false
  sensorConfig: /etc/sensors/ov9712_i2c_dc_720p.ini
  slowShutter: low
  antiFlicker: disabled
  memMode: reduction
  rawMode: slow
onvif:
  enabled: true

ok after a bit more experimentation, this is certainly a pinmux'ing issues
when majestic starts, and I'm assuming it opens gpio ports, the pinmuxing is reset to 0 for the pins, which is wrong (at least for hi3518ev100) for gpio. Per datasheet, these should be set to 1 to use gpio function of these pins.
root@openipc-hi3518ev100:~# #GPIO9_1, GPIO73
root@openipc-hi3518ev100:~# devmem 0x200F00CC
0x00000000
root@openipc-hi3518ev100:~# #GPIO9_4, GPIO76
root@openipc-hi3518ev100:~# devmem 0x200F00D8
0x00000000
root@openipc-hi3518ev100:~# #GPIO9_5, GPIO77
root@openipc-hi3518ev100:~# devmem 0x200F00DC
0x00000000
root@openipc-hi3518ev100:~# #GPIO9_7, GPIO79
root@openipc-hi3518ev100:~# devmem 0x200F00E4
0x00000000

Interestingly, after majestic is started, if I manually set the pinmuxes on these, it works. But when majestic is restarted, the pinmuxes are reset to 0 (non-working). I.e. this makes it work:
root@openipc-hi3518ev100:~# devmem 0x200F00CC 32 0x1
root@openipc-hi3518ev100:~# devmem 0x200F00D8 32 0x1
root@openipc-hi3518ev100:~# devmem 0x200F00DC 32 0x1
root@openipc-hi3518ev100:~# devmem 0x200F00E4 32 0x1

I'm not sure what the convention is for these - if the pinmuxing is supposed to be set as a default on the OS, or if this is something the application (majestic) is supposed to do when opening gpio ports (but I have no idea how majestic is interacting with gpios, e.g. sysfs, devmem, syscalls, etc)

also possibly interesting
with majestic running a fresh config with no nightMode pins defined:
ipctool reginfo:
...
muxctrl_reg50 0x200f00c8 0x1 reserved [GPIO9_0]
muxctrl_reg51 0x200f00cc 0x1 reserved [GPIO9_1]
muxctrl_reg52 0x200f00d0 0x1 reserved [GPIO9_2]
muxctrl_reg53 0x200f00d4 0x1 reserved [GPIO9_3]
muxctrl_reg54 0x200f00d8 0x1 reserved [GPIO9_4]
muxctrl_reg55 0x200f00dc 0x1 reserved [GPIO9_5]
muxctrl_reg56 0x200f00e0 0x1 reserved [GPIO9_6]
muxctrl_reg57 0x200f00e4 0x1 reserved [GPIO9_7]
...

after setting majestic settings:
.nightMode.irSensorPin: 77
.nightMode.irCutPin1: 76
.nightMode.irCutPin2: 79
.nightMode.backlightPin: 73

when majestic restarts, output of ipctool reginfo:
muxctrl_reg50 0x200f00c8 0x1 reserved [GPIO9_0]
muxctrl_reg51 0x200f00cc 0x1 reserved [GPIO9_1]
muxctrl_reg52 0x200f00d0 0x1 reserved [GPIO9_2]
muxctrl_reg53 0x200f00d4 0x1 reserved [GPIO9_3]
muxctrl_reg54 0x200f00d8 0 [reserved] GPIO9_4
muxctrl_reg55 0x200f00dc 0x1 reserved [GPIO9_5]
muxctrl_reg56 0x200f00e0 0x1 reserved [GPIO9_6]
muxctrl_reg57 0x200f00e4 0 [reserved] GPIO9_7

it seems that something about the way majestic opens/configures the gpios/regs is causing the pinmux to get reset for the irCutPin1 & irCutPin2 pins

ok after a bit of exploration into the majestic binary w/ cutter, I can see that there is some function which sets up the pin mux according to some configuration table in the code. (set_mux_reg, mux_gpio, ?).
If I patch the table for my muxctrl register addresses it works.
So I'm sure that this has to do with some hardcoded pinmux table in majestic codebase.
At least for hi3518 it seems like all the GPIO9_0 through GPIO9_7 should certainly have a pinmux value of 1, selecting the alternate "gpio" pin function, rather than the primary "nand flash data pins" function.

Thanks for your research, it looks impressive.
We will try to fix the issue soon and give you the information for testing.
In any case, we are very happy to have you with us.

looks like this has been resolved on recent builds of majestic master branch

Done


Choosing a command with Tab causes suggestions to disappear

Summary
Bolt suggests commands, but requires extra input to complete a command and then show suggested arguments for the command. I think it should show arguments immediately.
To reproduce

type bo
Hit Tab to choose boltprompt
Hit space, or backspace followed by space

Expected results
After 2, I expect bolt to show a list of suggested parameters for boltprompt.
Actual results
After 2, suggestions disappear. They only reappear when I "nudge" it by entering a space.

Showing suggestions without selecting one automatically could help here. I think in the case of Tab, though, I interpret it to mean “yes, and…” so I think I’d expect to have the first suggested argument selected after step 2. If I changed my mind, I’d hit Escape.

Pushed a change which should improve this, let's see if this is intuitive in a while.


Allow for use with sass-rails or sassc-rails

This is an awesome gem! I was wondering if there was a way to specify the dependencies so that you could choose to use sass-rails or sassc-rails as your SASS engine, since this is the only part of my project that requires sass-rails.
Thanks!

Γεια σου Γιάννη!
I have submitted a pull request (#26) to replace sass-rails as a dependency, as it has been tagged as EOL.
Would you consider merging this?

Hey there. Any chance this could be merged?


modhtp converts empty string to NULL pointer, then dereferences it

I have a crash which I've traced to modhtp_htp_request_headers:
(1)     /* Update the hostname. */
if (tx->parsed_uri != NULL) {
itx->hostname = (const char *)bstr_util_strdup_to_c(tx->parsed_uri->hostname);
}
I have a case where tx->parsed_uri is non-null but fields are unset, with tx->parsed_uri being an empty string (this looks like a bug elsewhere, but I haven't figured out where parsed_uri is set).  The above code then sets itx->hostname to NULL.
This NULL string is then dereferenced in ib_state_notify_request_headers, with at the top of the backtrace:
#0  __strlen_sse2 () at ../sysdeps/i386/i686/multiarch/strlen.S:99
#1  0x00744d4f in ib_context_siteloc_chooser (ctx=0xb2bb0748,
type=IB_CTYPE_TX, ctxdata=0x8981fe8, cbdata=0xb2b8f1e8) at engine.c:2049
#2  0x00741402 in _ib_context_get (ib=0xb2b8af80, type=IB_CTYPE_TX,
data=0x8981fe8, pctx=0x8981ff8) at engine.c:98
#3  0x00743393 in ib_state_notify_request_headers (ib=0xb2b8af80, tx=0x8981fe8)
at engine.c:1200
#4  0x007c9e2f in modhtp_htp_request_headers (connp=0x896c950) at htp.c:347

May be related to #3 as well.


A way to explicitly stop a Receiver

If you stop reading from a channel, you will get an overflow warning message after a short while.
Sometimes, however we want to properly stop and not get spammed with log warnings, so a convenient and explicit way to do that would be nice.

There is usually a way to stop receiving data from a channel, by stopping the channel, but I think this issue is about stopping a single receiver, not shutting down a whole channel, so I updated the subject.
BTW, the logging of overflow only applies to Broadcast channels, Anycast doesn't have a per-receiver buffer so there are no warnings, at least at the receiver level.
In any case I think a stop() and a async context manager interface would be a good addition for Receiver in general.


Removed crypto intraday reference, added daily and exchange rate funt…

Added daily and exchange rate functionality

Woot woot! Thanks!
On Fri, Aug 23, 2019 at 3:06 AM Romel Torres<EMAIL_ADDRESS>wrote:

Merged #137 https://github.com/RomelTorres/alpha_vantage/pull/137 into
develop.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RomelTorres/alpha_vantage/pull/137?email_source=notifications&email_token=AM6DPJPNJEUJ6DCS3LSDG2TQF6D65A5CNFSM4IOZPZDKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTG2GJDY#event-2578736271,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM6DPJI4CRBM5GS3HYHTPQLQF6D65ANCNFSM4IOZPZDA
.


Use factory namespace expected by Laravel.

This fixes #18 by assigning the namespace Laravel expects when calling Model::factory().
I'm a bit confused about #1 because it only mentions that factory classes should be put in nested folders, which they already are.
By the way, I tried to run the tests. Can you confirm that they need to be updated before they will work, or is it just in my environment?

@mortenscheel, I think the test cases for this package are pretty minimal. This looks good to me, so I'm going to go ahead and merge it. We can resolve any errors which may arise.


"Building a gRPC service with Node.js" CodeLab does not work

I tried the mentioned codelab. At step3, I Git cloned the example and installed gRPC package with "go get google.golang.org/grpc" command.  However, when I try "go run client.go", this is the error I'm getting on Cloud Shell:
atameldev@codelab-grpcwithnodejs:~/io2015-codelabs/gRPC/start$ go run client.go
# _/home/atameldev/io2015-codelabs/gRPC/start/books
books/books.pb.go:252: cannot use _BookService_List_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) as type grpc.meth
odHandler in field value
books/books.pb.go:256: cannot use _BookService_Insert_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) as type grpc.me
thodHandler in field value
books/books.pb.go:260: cannot use _BookService_Get_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) as type grpc.metho
dHandler in field value
books/books.pb.go:264: cannot use _BookService_Delete_Handler (type func(interface {}, context.Context, grpc.Codec, []byte) (interface {}, error)) as type grpc.me
thodHandler in field value
atameldev@codelab-grpcwithnodejs:~/io2015-codelabs/gRPC/start$

Same thing here

Same thing here also


Does not work on raspberry pi 3

The program starts but prints the following message
[0209/223559.090393:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

Are you sure that it does not work? That log message is quite common (it is not from Browservice, but from Chromium/CEF), and Browservice usually works even if it prints that. Does the program terminate after the message? What else does it print?

It does not print anything else, and trying to connect to the server does absolutely nothing on the client side. The program does not terminate after the message.
The program overall prints
INFO @ src/xvfb.cpp:60 -- Starting Xvfb X server as child process _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running INFO @ src/xvfb.cpp:131 -- Xvfb X server :2 successfully started INFO @ src/http.cpp:280 -- HTTP server listening to <IP_ADDRESS>:8080 [0210/194949.116043:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

This output seems completely normal. In your case, it seems that the server has been configured to only listen to local connections (HTTP server listening to <IP_ADDRESS>:8080). Are you sure you are connecting from localhost? If you run curl localhost:8080 on the machine running Browservice, what do you get as output?

I get
<html>
<head>
<title>Browservice</title>
<script type="text/javascript">
window.onload = function() {
    window.location.href = "/2541567326046024394/prev/";
};
</script>
</head>
<body>
</body>
</html>

So the problem might be with my connection instead.

:facepalm: I was connected to another network.
Sorry for the waste of time.
The CEF error threw me off so I immediately jumped to conclusions.


Update CI workflows

Codecov Report

Merging #19 (b0a372c) into main (dcf31f0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   91.68%   91.68%
=======================================
  Files          22       22
  Lines         529      529
  Branches       51       51
=======================================
  Hits          485      485
  Misses         44       44

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Outdated versions on Firefox, Edge & Opera extension stores

As stated in title, on those stores the version is still 1.0.2, instead of 1.0.5 of Chrome Web Store.
Is there any reason they're not updated to the latest as well yet?

Chrome started requiring manifest V3 a long time ago, and Firefox did not support it. It only added support about a month ago and there are some compatibility differences between them, it's not as simple as zipping the file and uploading it to Mozilla's addon store

Understandable. Are there any chances/possibility of backporting 1.0.2-1.0.5 changes to the Firefox version?
Also it probably shouldn't have much problems with Edge and Opera stores (especially Edge), because the upstream project has started to use Manifest v3, I guess.

They're just going to drift even further apart - the fact that Zoom issued a takedown request against the Chrome store and caused a name change is already causing maintainability issues for me. I'd rather not spend the time on it and just let Firefox and the other browsers catch up


Private room : discussion between 1 user from eimis and 1 user from Pandalab native IM

actually it works locally we will deploy to staging soon


Update jpeg_camera.js

createObjectURL doesnt accept stream on chrome any more.
this fix works

Please read about project status on the main page.


CLI: Plugin Reinstall

Added option (-r) to also remove the plugins data upon reinstallation. Previously it was hard set to false.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-14048.
Please use this issue to track the state of your pull request.

Merged with commit https://github.com/shopware/shopware/commit/f677f6f695f6eefa0f12156ad2ea92fc982935d3.
Thank you @elpollitodiablo :+1:


Recursive message definitions are broken

I work on Protobuf, and I'm currently trying to add a new recursive field definition to descriptor.proto.  This is being blocked by https://github.com/nanopb/nanopb/issues/493, which causes infinite recursion in nanopb.  We're currently using an older version of nanopb in Google, but AFAICT from that issue, these types of protos still aren't supported.  It seems like the resolution there was to provide a nicer error message, but not actually support recursive messages.
Is there a reason this isn't possible in nanopb?  Recursive messages are valid in Protobuf, so this is a major deviation between the two libraries.  Specifically, I would expect the following message to work just fine:
message Foo {
  optional Foo foo = 1;
}

First question would be, do you actually need nanopb access to descriptor.proto structures? It's quite rare to process them in the kinds of tasks nanopb is used for.
But regarding recursive messages, they work if you define options (nanopb).type as either FT_CALLBACK or FT_POINTER (or FT_IGNORE, but that just skips the field). See tests/cyclic_messages.

nanopb needs access to descriptor.proto IIUC.  You currently have a fork of it in your repo, but within google we use a shared version.  We also can't define custom options without taking on a dependency to nanopb, which would cause cyclic dependency issues.

Sure, descriptor.proto is used by the nanopb generator to parse the .proto files. However, this uses the python-protobuf library and happens on a regular computer.
The C library as used on embedded systems usually does not see the descriptor.proto structures at all. But if there was a specific purpose to parse them on the embedded side, that is possible, it just needs a callback or pointer at some point of the cycle. Static allocation cannot by its very nature represent cyclic structures.

Yeah, automatic detection of cycles & conversion to FT_CALLBACK sounds reasonable. Maybe even worth a backport to 0.3.9.x series if that is what you are on. It's just a question on which reference to convert to callback - would need some reasonable heuristic, and also need to check whether there are already options specified. I'm not very eager to work on this myself currently.
Normally nanopb_generator excludes google/protobuf/descriptor.proto from the generated includes, so that there is no need to generate a .pb.h for it. Possibly if you have descriptor.proto in a different relative path, it doesn't get matched? It can be added to excludes manually with the -x option.
For cases where someone would have actual need to access descriptor.proto structures using nanopb, they would want to use options anyway - using the defaults for every field is just not reasonable. For that case, the options would be placed in a separate file and --options-file used to apply them.

hah yep you were correct, we weren't properly excluding our internal descriptor.proto.  Adding that does seem to fix the issue I'm seeing, so at least this is unblocked.  Leaving the bug open since the (lower priority) root issue is still there though

Hah, using an options file is a solid workaround!  That unblocks us, but I think this is still a reasonable feature request for the future

Fix published in nanopb-0.4.8.


[WR-346] alert ribbon

Looks good to me. I haven't tested locally so I guess we can test on DEV once it's merged to master. Please make sure to squash and merge.


Import CSS Modules styles into StyleX

Describe a solution you'd like:
CSS Modules style sheet import into StyleX structure to modify and it on a fly and take instant result.
One of the coolest feature which provided StyleX is style compilation in JS, It is useful when calculation of our style runs in JS. We need it for in such cases as animation.

Please try explaining what you're asking for again, maybe with code examples? If you're asking for StyleX to consume CSS modules, that's not possible.

This feels like a discussion topic for now.


Relative/absolute record name conversions

Hi,
Over in the libdns repo, we're discussing standardizing the use of relative or absolute record names in libdns.Record structs. The current consensus is that they should be made relative (i.e. for a record named sub.example.com in a zone called example.com, the name should become sub). This may affect your provider implementation.
When you have a chance, would you please check out this issue? This is the last call for feedback before we decide and I push the changes, and I want to make sure we get it right for the majority of DNS provider implementations so we don't have to change it again.
Link: https://github.com/libdns/libdns/issues/12#issuecomment-756135908
Thank you!

Duplicate of #5 😉

Oops, derp. That was bound to happen


Conversion error - pH casting to INT

I was playing with conversion in OB and every conversion I tried failed due to that error

Traceback (most recent call last):
File "/galaxy-central/lib/galaxy/jobs/runners/init.py", line 163, in prepare_job
job_wrapper.prepare()
File "/galaxy-central/lib/galaxy/jobs/init.py", line 858, in prepare
self.command_line, self.extra_filenames = tool_evaluator.build()
File "/galaxy-central/lib/galaxy/tools/evaluation.py", line 427, in build
raise e
ValueError: invalid literal for int() with base 10: '-1.0'

@mwojcikowski thanks for the bug report! This was already fixed in: https://github.com/bgruening/galaxytools/commit/6771efaef517caf423c8b38ef46f861cf26cee89
I need to update the packages. Do you run CTB with the Docker container or did you installed it on your own?

Ok, updated the Tool Shed package. Thanks!

It's docker container.

I will rebuild this one. Thanks a bunch!


fixed #3474 : change the sliceTake and sliceSkip behavior

fixed #3474 :
they will not throw for a  n < 0  and  n > list.Length. they return []
instead.
this make arr.[..a] always the same with arr.[0..a]
arr.[a..(arr.Length-1)]   === arr.[a..]

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@syeerzy, @dsyme
Whilst I believe this is not really a breaking change, there is really a conceptual difficulty with this change.  Whether an API so should fix and go with bad input, or whether it should signal an error.
I am sure we can all produce examples of each type of behavior in FSharp.Core and and the base class libraries, however, I believe that in the main we tend to signal with an exception on input error.  For a developer who wants these APIs to behave in this way it is very relatively easily wrap them.
I am inclined to reject this change, what are your thoughts?

And yes, I realize I have flip-flopped since March.  It's a good job I'm not a language designer. :-)

@KevinRansom Definitely best to discuss on an RFC thread, but unfortunately that hasn't been created yet
Looking through https://github.com/Microsoft/visualfsharp/issues/2643 I am inclined to accept the change - the argument based on consistency under reasonable change is a sensible approach to design.
For example, the argument that    l.[..x] is defined to be the same as l.[0..x] is quite sensible. Or, as the issue puts it, "l.[..x] does not currently satisfy any reasonable definition"

Actually RFC is here: https://github.com/fsharp/fslang-design/issues/217 and discussion is linked from there

@dsyme ...
Oh it seems like we currently do the wrong thing on invalid indexes anyway.  So yes ... this makes things more consistent and easier to reason about.
@dotnet-bot test this please

@syeerzy You have to update this Slicing test which is now failing, e.g. at this line, perhaps others too https://github.com/syeerzy/visualfsharp/blob/master/src/fsharp/FSharp.Core.Unittests/FSharp.Core/Microsoft.FSharp.Collections/ListType.fs#L235

@dotnet-bot test this please

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

build failing on Ubuntu14.04 Release Build ,  the log said:
./autogen.sh --prefix=/usr
Please install autoconf
./autogen.sh: 4: ./autogen.sh: autoreconf: not found
Error: ./autogen.sh failed
Build step 'Execute shell' marked build as failure
what does it mean, and how to fix it?

Does this PR only affect lists? So the work on arrays (1D and 2D), strings is still to be done?


fix(rowGroup): rename parent to $parent to avoid deep-watchers

Fix #533

the issue this relates to is no closed. does this mean this PR is no longer needed?

Hi @ceolter,
As stated in the issue, this is trying to solve an specific angular $digest cycle issue.
I temporarily solved it in my project by using my own fork.
Nevertheless I noted that this needs to be fixed in a more robust way
If you want to keep your lib 100% framework-agnostic and you think renaming a var is not worth the hazzle, then we might need to come up with a different approach to solve this.
Otherwise i think this is a simpler workaround imho

yes it is a simple workaround, that is true. it just doesn't make sense to me that the grid should have to use angular convention inside it.
the grid doesn't use this parent value, it's just there for the clients sake, if it wants to navigate the tree. what about a property 'suppressParentInNode', which when true, makes the nodes a unidirectional tree with no cyclic dependencies?

@ceolter fair enough :sweat_smile:
I will try to elaborate on a cleaner fix, thanks for your feedback and patience :smile:
Closing the PR

well if you don't actually need the parent reference, i think that's the cleanest. i can appreciate sometimes it is better to have a non-cyclic tree.

i have just implemented a property 'suppressParentsInRowNodes', if set to true, the parent variable will not be set in the row nodes. the grid didn't use this property, it was just for the client to use if it needed to navigate the tree, so having it optional is not a problem for the grid.

@ceolter wow thanks! gonna try it asap

@ceolter I set suppressParentsInRowNodes: true to gridOptions but apparently parent is still added to children nodes.
File Browser Example: http://jsbin.com/naviji/1/edit?html,js,console,output
*disclaimer: I'm using dist/ files from my own repository since ag-grid's is not updated

i just tested locally, and it's working in my test drive. can you try after the release? easier for me than look at your repository (sorry, everyone is trying to get some of my time!!)

Absolutely, I appreciate your help! a lot :tada:
Unfortunately I'm still getting parent references with latest release (3.1.0): http://jsbin.com/naviji/3/edit?html,js,console,output

I think the clue is that rowsAlreadyGrouped is set to true true ?

@ceolter I found thi issue, gonna update my PR asap :smile:

new PR: https://github.com/ceolter/ag-grid/pull/657

ah, missed that. cool, thanks :)


 While your local system is more than fast enough to load the extension very quickly, the remote Linux system you're connected to has only 2GB of memory and a much less powerful CPU.
This can lead to longer activation times, so a delay of around 3083ms isn't unusual. If necessary, consider upgrading the remote server's resources for better performance.

Ok well, it is a Raspberry pi microcontroller
Now I messaged you because literally nothing will work on running C++
files.  It’s been like 2 years of struggle and using other IDE’s….can you
help me with that?
On Wed, Oct 30, 2024 at 11:27 PM Nate @.***> wrote:

Thanks for bringing this up! While your local system is more than fast
enough to load the extension very quickly, the remote Linux system you're
connected to has only 2GB of memory and a much less powerful CPU.
This can lead to longer activation times, so a delay of around 3083ms
isn't unusual. If necessary, consider upgrading the remote server's
resources for better performance.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/232696#issuecomment-2449086353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYXIMM4BOQZ2OGOVZZOKA2DZ6HET3AVCNFSM6AAAAABQ5Q2ZZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBZGA4DMMZVGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok well, it is a Raspberry pi microcontroller Now I messaged you because literally nothing will work on running C++ files. It’s been like 2 years of struggle and using other IDE’s….can you help me with that?

That makes sense! To improve your development experience I'd suggest doing your development locally then, and then running the final code on your Raspberry Pi.
Regarding C++, by default VS Code doesn't know how to interact with your C++ project's build system. To enable the "Run" feature, you'll need to create a tasks.json file to define your build task..
Further, to enable C++ Intellisense, you'll need a compile_commands.json file as well. Whether you're using Make/CMake or some other build system, bear should pretty much be able to generate you a compile_commands.json that should work out of the box:
bear -- <your-build-command>

well tbh i have not been able to run anything on the pi bc json prevents me
from running any .cpp file.  Even a simple hello world without a
microcontroller won’t run without json blocking it.
Not sure how to build a task or compile commands
bear --
What should I put in the your build command ?
On Wed, Oct 30, 2024 at 11:50 PM Nate @.***> wrote:

Ok well, it is a Raspberry pi microcontroller Now I messaged you because
literally nothing will work on running C++ files. It’s been like 2 years of
struggle and using other IDE’s….can you help me with that?
That makes sense! To improve your development experience I'd suggest doing
your development locally, and then running the final code on your Raspberry
Pi.
Regarding C++, by default VS Code doesn't know how to interact with your
C++ project's build system. To enable the "Run" feature, you'll need to
create a tasks.json file to define your build task.
https://code.visualstudio.com/docs/editor/tasks.
Further, to enable C++ Intellisense, you'll need a compile_commands.json
file as well.
https://code.visualstudio.com/docs/cpp/configure-intellisense#_compilecommandsjson-file
Whether you're using Make/CMake or some other build system, bear
https://github.com/rizsotto/Bear should pretty much

able to generate you a compile_commands.json that should work out of the

box:
bear --
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/232696#issuecomment-2449144565,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYXIMM6RJGK6E7KMTSLAIVLZ6HHLDAVCNFSM6AAAAABQ5Q2ZZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBZGE2DINJWGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

well tbh i have not been able to run anything on the pi bc json prevents me from running any .cpp file. Even a simple hello world without a microcontroller won’t run without json blocking it. Not sure how to build a task or compile commands bear --  What should I put in the your build command ?

It sounds like an extension is misconfigured or interfering with your build process. I would suggest disabling all installed extensions:

Bring up the Command Palette: On macOS, ⌘+Shift+P; on Windows, Ctrl+Shift+P.
Enter in >Extensions: Disable All Installed Extensions

Then, follow the steps in Using C++ on Linux in VS Code to set up your development environment on your Raspberry Pi.

Please start by following this guide to diagnose this issue and collect relevant logs so we can investigate. Thanks!


Added SQUARED_DIFFERENCE to ops resolver

Add support for the SQUARED_DIFFERENCE op in the ops resolvers

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.

I've now signed the CLA and this check now passes


[Makefile:1567: digital-ls-B] Error 1

I am trying to build skywater pdks with open pdk.
I just ran these commands.
./configure --enable-sky130-pdk
make

After hours these errors occured at the end. What can I do about these?
---------------------------------------------------------------------------

make[3]: *** [Makefile:1567: digital-ls-B] Error 1
make[3]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make[2]: *** [Makefile:1120: digital-ls-build-B] Error 2
make[3]: *** [Makefile:1567: digital-ls-A] Error 1
make[3]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make[2]: *** [Makefile:1120: digital-ls-build-A] Error 2
make[3]: *** [Makefile:1457: digital-lp-A] Error 1
make[3]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make[3]: *** [Makefile:1457: digital-lp-B] Error 1
make[2]: *** [Makefile:1102: digital-lp-build-A] Error 2
make[2]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make[3]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make[1]: *** [Makefile:740: all-A] Error 2
make[2]: *** [Makefile:1102: digital-lp-build-B] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make[1]: *** [Makefile:740: all-B] Error 2
make[1]: Leaving directory '/usr/share/pdks/open_pdks/sky130'
make: *** [Makefile:130: tech-sky130] Error 2

It appears that the LS and LP digital libraries did not build correctly.  If that's all that happened, then you could just ignore the errors because those libraries are not very well supported, anyway.
I will need to build the sky130 PDK from scratch to see if the issue is in the skywater-pdk repository.  There should have been directories in open_pdks/sources/sky130_pdk/libraries/sky130_fd_sc_ls (and lp).  But I can't tell what the actual error is from the end of the "make" output.


Create derive_var_bvcacritxfl function

Background Information
Create function derive_var_bcvacritxfl which can create criterion flags for CBVA gain/loss of x letters. Functionality could be as follows:
derive_var_bcvacritxfl <- function(
  ...
  gain_values,
  lose_values,
  ....
){
<function code>
}

which could be called like this:
adbcva <- adbcva %>%
    derive_var_bcvacritxfl(
        gain_values = c(10,15),
        lose_values = c(5,10)
     )

to generate an updated ADBCVA dataset containing criterion flags CRIT1FL, CRIT2FL, CRIT3FL, CRIT4FL for gaining 10 letters, gaining 15 letters, losing 5 letter and losing 10 letters respectively, along with associated variables CRIT1, CRIT2, CRIT3, CRIT4 encoding the criterion for the flag (eg, CRIT1 = "10 letter BCVA gain" for BCVA records and blank otherwise).
Proposed convention:

CRITxFL with 1<=x<=10 used for BCVA gain categories
CRITxFL with 11<=x<20 used for BCVA loss categories

This will be quite a central function in {admiralophtha}, so we should aim to provide:

many examples in the function roxygen code
vignette
example in the ADBCVA template.

Note: we should also add avoidloss_values and avoidgain_values corresponding to avoiding a loss/gain of x letters. An appropriate convention can also be considered like the one suggested above.

Sorry for my delay coding. I missed push my branch so copy my code here.
I have some questions.
i) Do gain_values and loss _values always have 2 vectors? If not, I need to modify code which.
ii) Sorry for I am not famillier with ADBCVA, how to define gain_values or loss _values. Do we usulally use minus numbers?
I will confirm with our in-house ophthalmologist tomorrow, and will modify.
`derived_var_bvcacritxfl <- function(
adbcva_1,
x,
gain_values,
lose_values
){
adbcva_1 %>%
mutate(CRIT1FL = ifelse((!!as.name(x) >= gain_values[1] & !!as.name(x) < gain_values[2]),
paste(gain_values[1], " letter BCVA gain"), "" )) %>%
mutate(CRIT2FL = ifelse((!!as.name(x) >= gain_values[2]),
paste(gain_values[2], " letter BCVA gain"), "" )) %>%
mutate(CRIT3FL = ifelse((!!as.name(x) <= -(lose_values[1] & !!as.name(x) < -(lose_values[2])),
paste(lose_values[1], " letter BCVA loss"), "" )) %>%
mutate(CRIT4FL = ifelse((!!as.name(x) <= -(lose_values[2])),
paste(lose_values[2], " letter BCVA loss"), "" ))
}`

Thanks for this Yuki. A couple of notes:

We really should be working in a separate branch, so I will make a new branch and copy the code across.
We should be following the programming strategy listed here, which has info about variable names and formatting.
I think it would make sense to loop over gain_values and lose_values rather than having many mutate statements.

I am happy to implement the above myself and then circle back with you to show you what I've done and how I've done it 😄


[DONT MERGE] Testing Travis

Testing Travis in this PR.
Our Travis builds have suddenly started to fail and none of the mentioned workarounds are working (like https://github.com/travis-ci/travis-ci/issues/6193). The exact issue being reported in lint report:
The SDK platform-tools version (23.0.1) is too old to check APIs compiled with API 25; please update
Here's the Travis job's log: https://api.travis-ci.org/jobs/294869249/log.txt?deansi=true
The link to my original PR: edx/edx-app-android#1019
platform-tools revision 26.0.2 was recently released whose download is finishing with the wrong checksum, thus Travis is using the fallback platform-tools revision 23.0.1 for running lint on my project causing the issue.
Here's the error excerpt from the job's log (https://api.travis-ci.org/jobs/294869249/log.txt?deansi=true):
Installing Archives:

  Preparing to install archives

  Downloading Android SDK Platform-tools, revision 26.0.2

  Download finished with wrong checksum. Expected b8130e7c390496cff12bf9355739bd41eed6a0a5, got 668ff8e319715175ff628ad52b124f154275fe2d.

  Done. Nothing was installed.

Link to issue created on Travis Github: https://github.com/travis-ci/travis-ci/issues/8676

cc @staubina
p.s. This PR is just here to track the issue on Travis we've been facing from last week.

Ticket to track this issue:
https://openedx.atlassian.net/browse/LEARNER-3115

Seems like the issue is fixed at Travis's end now. I'll create a follow up PR and revert the changes in this commit https://github.com/edx/edx-app-android/pull/1019/commits/63d9e078bf38ef9cb6938382e2fff6f63631d271.

PR #1104 created for reverting the temporary fix.


DictationInputManager and focus do not play well together

Overview
InputManager is architected to only send events to focused objects. This is fine for things like air-tapping, but speech is different. You may start to speak, move your cursor away from the object, and the object will never receive the dictation. It is unrealistic to expect the user to keep his/her head on a small microphone target all through dictation.
Adding a globalEventListener is not a good solution either. In this case, the object will receive all events from other objects, too, so to mitigate this, the developer has to add tons of checks all over the place.
Steps to reproduce

Open up the keyboard sample in HoloLens or the editor.
Air-tap on the microphone icon
move the cursor off the keyboard

Actual Behavior
What you speak doesn't get shown in the input field.
Expected Behavior
The keyboard (and anything using the DictationInputSource) should receive dictation text until the dictation finishes, even if the gameobject is no longer in focus.
Suggestions for fixing
:

Consider whether DictationInputManager is a good candidate to being an InputModule at all or if it should be handled differently
If it is to stay an InputModule, provide a mechanism for gameobjects that initiated the dictation to keep receiving dictation events regardless of focus as long as the dictation session is active. E.g. StartDictation should have an optional IDictationHandler parameter, and if not null, dictation events should be passed to this object until dictation is complete.

Unity Editor Version
2017.3
Mixed Reality Toolkit Release Version
2<IP_ADDRESS>

Seems to have solved my issue for now. Thanks!


Box initializing multiple times after registration

When registering a box, the box is being initialized multiple times over the course of the first 5 - 10 minutes. The number of initializations seems to vary, but is mostly three in my experience.
I attached a log file that shows the registration process for a device where you can see that the installer was pushed three times with about 2 minutes of normal operation in between.
log.txt
It's also interesting to watch the box page during that process, because it switches back and forth multiple times between the "Please connect your device to an Internet connection" screen and the regular device page.

I saw this today. Not sure what's happening. Might move to the backend though...

Marking as won't fix in anticipation of the new SM version.


⚠ ClamAV has degraded performance

In ac75414, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 122 ms

Resolved: ClamAV performance has improved in 50757f3.


Topic request: Ordinals

supported in multiple wallets, marketplaces, open source projects. Love it or hate it, it's a non-trivial part of bitcoin software development and transaction volume

Added here: https://github.com/bitcoinops/bitcoinops.github.io/issues/721#issuecomment-1889792144


uv pip compile should include python version in the header like pip-compile

I think this issue is a duplicate of issue https://github.com/astral-sh/uv/issues/3588.
However, issue https://github.com/astral-sh/uv/issues/3588 has been around for quite some time, so I personally suggest letting the UV team decide whether to close this issue.

Thanks @FishAlchemist
Let's track in #3588
@karthiknadig please don't use screenshots in issues, they're bad for discoverability. See #9452


Release 0.1.0

Release a newer version of the collection to the Galaxy. We didn't bump metadata in https://github.com/stackhpc/ansible-collection-pulp/pull/17.

Holding off until https://github.com/stackhpc/ansible-collection-pulp/pull/16 is merged.


CONTRIBUTING.md file added

Fixes #28.
This pull request is created for the addition of CONTRIBUTING.md file to the project.

@kaiiyer Please have a look at it.

@kaiiyer Please have a look at it.


Multiple modules

Handle cases like:
declare module 'test/one' {
  // ...
}

declare module 'test/two' {
  // ...
}

Right now we get the name from the first module and flatten declarations.

I can pick this up. What did you have in mind if there's a clash? That is, if eg there's a test/one.foo and a test/two.foo and we can't just create external foo?

Prefix the reason name with the module name? Eg one_foo and two_foo?
Emit separate files for separate modules?

I think the best option is to have nested modules inside the file, like:
module One = {
  /* ... */
};

module Two = {
  /* ... */
};

That way addressing library/component becomes Library.Component.
The issue comes where we have something like:
declare module 'a' {
  // ...
}

declare module 'b' {
  // ...
}

Maybe just throw an error for now if there's multiple modules and more than one doesn't contain / or -. What are your thoughts?


Enable Gor on cache-1 Staging only

This will allow us to test a newer version of Gor without impacting on Deployments. Enabling on only a single cache machine shouldn't provide enough traffic to impact on Integration.
This is dependent on https://github.com/alphagov/puppet-gor/pull/8

I guess the tests might fail until the new version of puppet-gor is pulled in.

The new .tar.gz file needs to be committed as well (and the old one deleted).

Oooooooh

This looks good to me :+1:. Added one comment about something I'm unsure of.

Once the default file path is the packaged one rather than undef merge away.


Add Postgresql considerations

Under considerations-before-applying-your-locks, add

For Postgresql:
The virtual network shouldn't have any resource lock set at the VNET or subnet level, as locks may interfere with operations on the network and DNS. Make sure to remove any lock (Delete or Read only) from your VNET and all subnets before creating the server in a virtual network, and you can set it back after server creation.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4e7af209-7240-dd2a-7130-e7fb3143986a
Version Independent ID: a653b0d1-877d-09f7-17fa-11bf06c37cc9
Content: Protect your Azure resources with a lock - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/lock-resources.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@esjmun1 Thanks for your feedback! We will investigate and update as appropriate.

@GennadNY please can you review

#sign-off

@tfitzmac - I believe tjis is assigned to you, but from Postgres networking lock side its a good addition

#assign:mumian
@GennadNY - thank you for your comments.  I will update the article.


Querying Firestore

Once we can add books to the Firstore database in a principled manner, we will have to think of an effective way to query it.
We will need to do this in multiple places, e.g. in the searchbar in the navbar and in the filters on the /books page.
Firestore has good documentation, however, its functionality is more limited than SQL databases.
Therefore, we might want to look for an extension.
One option would be to use ElasticSearch with Firestore.
I have found two interesting articles on Medium that could be of help:

https://medium.com/@acupajoe/wondering-how-to-get-elasticsearch-and-firebases-firestore-to-play-nice-1d84553aa280
https://medium.com/joolsoftware/extending-firebase-with-cloud-functions-elasticsearch-129fbbb951e0

Sorry I never noticed that..hahah


Command timed out after 8 seconds: /usr/bin/ddev describe --json-output

Is there an existing issue for this?

[X] I have searched the existing issues

Are you sure that this bug is related to this DDEV Integration Plugin?

[X] I am sure

Enter your error report ID (If available)
15350a86612d4954bec79423a0d3e5ac
Describe the bug
I'm just using PHPSTORM IDE and suddenly the error appears. I have the last version
de.php_perfect.intellij.ddev.cmd.CommandFailedException: Command timed out after 8 seconds: /usr/bin/ddev describe --json-output in \wsl.localhost\Ubuntu\home\xxx\Wordpress\projectname
at de.php_perfect.intellij.ddev.cmd.DdevImpl.execute(DdevImpl.java:70)
at de.php_perfect.intellij.ddev.cmd.DdevImpl.describe(DdevImpl.java:39)
at de.php_perfect.intellij.ddev.state.DdevStateManagerImpl.checkDescription(DdevStateManagerImpl.java:155)
at de.php_perfect.intellij.ddev.state.DdevStateManagerImpl.checkChanged(DdevStateManagerImpl.java:90)
at de.php_perfect.intellij.ddev.state.DdevStateManagerImpl.updateDescription(DdevStateManagerImpl.java:74)
at de.php_perfect.intellij.ddev.state.StateWatcherImpl.lambda$startWatching$0(StateWatcherImpl.java:34)
at com.intellij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
at com.intellij.util.concurrency.SchedulingWrapper$MyScheduledFutureTask.run(SchedulingWrapper.java:275)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:735)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:732)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:400)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:732)
at java.base/java.lang.Thread.run(Thread.java:1583)
It also happens that it does not update the new port for the database, I must modify the port manually every time I start the project
Steps to reproduce

Using PHPSTORM IDE and suddenly the error appears.

Additional context
No response

The 8 seconds timeout allowed for commands to finish in is currently not configurable. That time should generally be plenty for the command to return.
The automatic configuration of the DB port depends on this command succeeding.
Is this happening every time, or randomly? What's the last line of the output when running time ddev describe --json-output in your project directory within WSL?

The 8 seconds timeout allowed for commands to finish in is currently not configurable. That time should generally be plenty for the command to return.
The automatic configuration of the DB port depends on this command succeeding.

Is this happening every time, or randomly?
Randomly and when I open the project folder
What's the last line of the output when running time ddev describe --json-output in your project directory within WSL?
{"level":"info","msg":"┌──────────────────────────────────┐\n│ Project: pergub ~/Sites/Laravel/ │\n│ pergub https://pergub.ddev.site  │\n│ Docker platform: docker-desktop  │\n│ Router: traefik                  │\n├─────────┬──────┬──────────┬──────┤\n│ SERVICE │ STAT │ URL/PORT │ INFO │\n├─────────┼──────┼──────────┼──────┤\n└─────────┴──────┴──────────┴──────┘\n","raw":{"approot":"/home/alex/Sites/Laravel/pergub","database_type":"mariadb","database_version":"10.4","dbimg":"ddev/ddev-dbserver-mariadb-10.4:v1.23.4","docroot":"public","fail_on_hook_fail":false,"hostname":"pergub.ddev.site","hostnames":["pergub.ddev.site"],"httpURLs":["http://pergub.ddev.site","http://<IP_ADDRESS>:52194"],"httpsURLs":["https://pergub.ddev.site","https://<IP_ADDRESS>:52195"],"httpsurl":"https://pergub.ddev.site","httpurl":"http://pergub.ddev.site","mailpit_https_url":"https://pergub.ddev.site:8026","mailpit_url":"http://pergub.ddev.site:8025","mutagen_enabled":false,"name":"pergub","nodejs_version":"20","performance_mode":"none","php_version":"8.2","primary_url":"https://pergub.ddev.site","router":"traefik","router_disabled":false,"router_http_port":"80","router_https_port":"443","router_status":"stopped","router_status_log":"","services":{"web":{"exposed_ports":"443,80,8025","full_name":"ddev-pergub-web","host_http_url":"http://<IP_ADDRESS>:52194","host_https_url":"https://<IP_ADDRESS>:52195","host_ports":"52195,52194","http_url":"http://pergub.ddev.site","https_url":"https://pergub.ddev.site","image":"ddev/ddev-webserver:v1.23.4","short_name":"web","status":"running","virtual_host":"pergub.ddev.site"}},"shortroot":"~/Sites/Laravel/pergub","ssh_agent_status":"exited","status":"unhealthy","status_desc":"db: stopped\n","type":"laravel","urls":["https://pergub.ddev.site","https://<IP_ADDRESS>:52195","http://pergub.ddev.site","http://<IP_ADDRESS>:52194"],"webimg":"ddev/ddev-webserver:v1.23.4","webserver_type":"nginx-fpm","xdebug_enabled":false},"time":"2024-08-29T10:43:53-05:00"}

I changed the ddev binary path in DDEV Integration, and everything works fine. I updated to the latest version of ddev and the binary path changed. I'm closing this issue because it seems to be a configuration problem in the project.


[v4l2loopback] Failed to recognize file format

When I try to record the screen to a v4l2loopback device, something gets mixed up and I cannot successfully open the device:
crw-rw----+ 1 root video 81, 2 Jun 15 09:48 /dev/video2

The user is in the video group. I start recording via:
wf-recorder --muxer=v4l2 --codec=rawvideo --file=/dev/video2                                         ~
Please select an output from the list to capture (enter output no.):
1. Name: eDP-1 Description: Unknown 0x1536 0x00000000 (eDP-1)
2. Name: HDMI-A-1 Description: Dell Inc. DELL U2715H ... (HDMI-A-1)
Enter output no.:1
selected region 0 0 0 0
Choosing pixel format bgr0
Output #0, video4linux2,v4l2, to '/dev/video2':
    Stream #0:0: Unknown: none (rawvideo)
[video4linux2,v4l2 @ 0x7f9038000d00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.

I try to open the device via mpv:
mpv /dev/video2                                                                                ~
Failed to recognize file format.

If I try the same on my integrated camera, it works:
mpv /dev/video0                                                                                ~
 (+) Video --vid=1 (rawvideo 640x480 30.000fps)
[autoconvert] Converting yuyv422 -> yuv422p
VO: [gpu] 640x480 yuv422p
V: 00:00:02 / 00:00:02 (89%)

Have you tried doing ffplay /dev/video2 ?

It does work but I don't get any output:
ffplay /dev/video2                                                                                ~
ffplay version 4.2.3 Copyright (c) 2003-2020 the FFmpeg developers
  built with gcc 9.3.0 (GCC)
  configuration: --disable-static --prefix=/nix/store/0n61jivjai7zp2bsykjhmrz8xq2rqccd-ffmpeg-full-4.2.3 --target_os=linux --arch=x86_64 --enable-gpl --enable-version3 --disable-nonfree --enable-shared --enable-pic --disable-small --enable-runtime-cpudetect --disable-lto --enable-gray --enable-swscale-alpha --enable-hardcoded-tables --enable-safe-bitstream-reader --enable-pthreads --disable-w32threads --disable-os2threads --enable-network --enable-pixelutils --enable-ffmpeg --enable-ffplay --enable-ffprobe --enable-avcodec --enable-avdevice --enable-avfilter --enable-avformat --enable-avresample --enable-avutil --enable-postproc --enable-swresample --enable-swscale --enable-doc --disable-htmlpages --enable-manpages --disable-podpages --disable-txtpages --enable-bzlib --enable-libcelt --enable-libdav1d --disable-libfdk-aac --disable-libflite --enable-fontconfig --enable-libfreetype --enable-frei0r --enable-libfribidi --enable-libgme --enable-gnutls --enable-libgsm --enable-ladspa --enable-libmp3lame --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libdc1394 --enable-iconv --enable-libjack --enable-libmfx --enable-libmodplug --enable-libmysofa --enable-libopus --enable-librsvg --enable-libssh --enable-libtheora --enable-libv4l2 --enable-vaapi --enable-vdpau --enable-libvorbis --enable-libvmaf --enable-libvpx --enable-libwebp --enable-xlib --enable-libxcb --enable-libxcb-shm --enable-libxcb-xfixes --enable-libxcb-shape --enable-lzma --enable-nvenc --enable-openal --enable-libopencore-amrnb --disable-opengl --enable-libopenjpeg --disable-openssl --enable-libpulse --enable-librtmp --enable-sdl2 --enable-libsoxr --enable-libspeex --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-zlib --disable-debug --enable-optimizations --disable-extra-warnings --disable-stripping
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, video4linux2,v4l2, from '/dev/video2':B sq=    0B f=0/0
  Duration: N/A, start: 5715.449393, bitrate: 3538944 kb/s
    Stream #0:0: Video: rawvideo (BGR[0] / 0x524742), bgr0, 2560x1440, 3538944 kb/s, 30 fps, 30 tbr, 1000k tbn, 1000k tbc

I also tried to configure the source in Firefox/Wire and did run into issues leading to the device disappearing in firefox.

Try setting the output format to yuv420: wf-recorder --muxer=v4l2 --codec=rawvideo --pixel-format=yuv420p --file=/dev/video2

This works better, at least I could see something on at least one test page. But after a while, the camera disappeared in firefox. Probably a browser issue. I'll try how it works in chromium.

Ok, I think I found the issue. It did not work in chrome, as it did not appear to begin with.
After fiddling around, I found an answer:
According to
https://github.com/umlaeute/v4l2loopback/issues/78
You need to use exclusive_caps to be able to use the driver. After doing so, it works in both browsers.
Fix:
modprobe v4l2loopback exclusive_caps=1

Alright, I assume the issue is fixed then? Closing, reopen if there is another bug in wf-recorder.

I still get the issue, that the device disappears in all browsers :( But I don't think this is due to wl-recorder. Probably more of an issue of the underlying technology, e.g. v4l2loopback


Binary data stored as escaped string with postgresql adapter

Hi!
I recently upgraded my gem set with both Rails 2.3 => 3.1 and ARJDBC to 1.2.2
Since then file uploads have broken.  I have found that the files are stored as escaped strings in the database.  Unescaping them before use works, but I really want the actual binary data stored in the DB.
I do a plain file.read on the file presented by Rails like I have always done which complies with all examples I can find.  I sthere anything else I should be doing when storing the file?
The column type is :binary in migration/schema dump and bytea in the database.

Hmm. We've had a bunch of postgresql changes in the last couple of releases. Any chance you could bisect back to the last release that works for you so we can figure out what broke this?

Yes, I'll have a look.  The issue was confused by the jruby-rack file upload error also.


Allow terminals to be reused

From @dbaeumer:

Reuse of a terminal. Not necessarily the terminal process more the terminal pane. If the user executes a task and the task finishes and runs the task again it would be cool if the output of the task could show up in the same terminal. Constantly pressing a key to close and old terminal might not be very intuitive.

For January we decided to keep the task in the core. So there is no need to make this 'public' API now. May be it would be good to first experiment a little with the new API.

@dbaeumer just to make sure, were you thinking of using a waitOnExit prompt (press any key to close) that can be reused? Or a terminal that executes something, the pty process dies and just sits there ("dead") until another task command is sent?

@Tyriar I would like to achieve the following:

create a new terminal and allow terminal reuse (could be an additional option) without actually running a terminal right away (if necessary we could run it as well)
run a command in the terminal. This will create the actual shell process. Usually the shell would be started with /c
receive an exit event when the shell exists
reuse the terminal to run another command in the terminal which creates a new shell process.

Use case if for a build task: if the user runs the build tasks 3 times in a row I would like to have one terminal (e.g. on entry in the drop down in the terminal pane) which contains the output of all three task runs.

@Tyriar I have one additional question. Does the terminal require to run a shell or would the terminal be able to run any other arbitrary process (for example a node.exe).

@Tyriar I got it working to run an arbitrary program. Only drawback is that I needed to specify the full path to the program (e.g. "C:\\Program Files\\nodejs\\node.exe"). Any idea why this is the case?

@dbaeumer do you mean the shell path you're using is node and it's not working like that? I guess the PATH resolution stuff is contained within cmd, I would think it would probably be safest to always wrap the command within cmd /c or sh -c.
Wrapping the command means the process will die when it finishes so I don't see a downside?

@Tyriar the only problem is argument passing with spaces contained. If you call node directly then you pass the args as a string[]. If you call the cmd.exe for example you need to construct a single string with proper arg quoting to ensure everything works when for example the command to call contains spaces.
And you save a process :-)

@DonJayamanne could this be useful for Python terminal execution?


best way to extend time on an not expired object?

is there a helper function?

It would be great to have complementary Increment and Decrement methods that refresh the expiration.  Unfortunately, it's not safe to do a Replace(Get(), ...) as that would be a race (another goroutine could change the value between the time the Get() and the Replace() happens).
Perhaps just a new method to UpdateExpiration on a key would be sufficient, here?  If passed nil, it uses the defaultExpiration, otherwise 0 to never expire?  So:
func (c Cache) UpdateExpiration(k string, d time.Duration)

Related: PR #20.

Any update on this one? Is the project dead?

As far as I know Patrick is no longer maintaining this @g-rad; I made a compatible fork which adds some commonly requested features over here: https://github.com/zgoat/zcache
v1 is designed to remain compatible with go-cache; so you can use it as a drop-in replacement. It adds Touch() to update expiry times.


Is license really "all rights reserved?"

This file is posted with a copyright "all rights reserved," which means that people may not incorporate it into any other program. Did you intend that license?

+1

+1

Thanks for commenting on this issue, everyone! Sorry I haven't really been responsive to these requests – this project had unfortunately fallen off my radar. I'm happy to make this project available under the MIT License. I hope that suits your needs!

Thanks!


App Transport Security has blocked a cleartext HTTP (http://) resource load since it is insecure .

Hi Team ,
I have the error below
2015-09-24 00:37:25.949 edX[20106:8581305] App Transport Security has blocked a cleartext HTTP (http://) resource load since it is insecure. Temporary exceptions can be configured via your app's Info.plist file.
May i know how i config my "edx-info.plist" file.
BTW, I have my own host website .
Big Thanks.
Best regards,
MOH

Hi, I just uploaded a work around for this. It's because of some changes Apple made in iOS 9.

Also, I don't particularly recommend working with the tip of master. We have stable release branches named "release/" These are far more likely to be stable than whatever's on master.

hi @aleffert ,
Big thanks for your reply , and may i know which release/xxx package is more stable,
cause when i switch the branch to release/1.0.6 it showed the package changed from 6months ago .
Thanks,
MOH

@chimlam91 release/1.0.6 is the last released version. It's a bit of an awkward time for us. We're winding down a major iteration of the app with a bunch of new features, but it's not quite ready yet - we're still finalizing endpoint responses and things like that. We expect to lock it down pretty soon.
After that point, we hope to do smaller, more regular releases and make sure unfinished features are hidden behind config flags. We've been trying to use flags for our current update too - everything is behind the NEW_COURSE_NAVIGATION_ENABLED config flag, but in practice no one here is testing the old one and I'm sure some bugs have snuck in over the last several months.

HI aleffert, very big thanks to your replied . I will try the release/1.0.6 version .BTW, is that i need to change the branch and git clone again the repository ?
So sorry about reply to late, cause i'm from Taiwan .
Hope i can fixed my problem .
Thanks,
MOH

You need to switch branches, but you shouldn't need to clone the repository again. You might want to do git pull to make sure you have the latest changes. Though since that branch hasn't changed in a while, it probably shouldn't be a concern.

Hi alerffert,
Big thanks for your replied.
MOH


Update @azure/core-http to latest @azure/ms-rest-js

This change updates @azure/core-http to take the fix from azure/ms-rest-js#358 which addresses an issue caused by a recent update of the Axios library.
@weshaggard can you do your merge magic to get this one in?  Thanks!

After discussing this with @weshaggard, we decided it was best to just move these changes over manually since they're pretty minimal.  I'll roll the changes into PR #3449 since that work depends on the fix to ms-rest-js.


fix typo in content/en/docs/concepts/workloads/pods/_index.md

wrong spelling for comunicate, it should be communicate

/kind cleanup
/lgtm
/approve
Thanks @willseeyou


maximum/minimum of all fail

I notice that depending on the build type (debug vs release) the way maximum and minimum of all are done fail.
This happen during when we re-alocate the temporary buffer as the source of the next kernel in the Execution method.
Both kernel have the same issue. Need to do something cleaner, like using the copy kernel, when time allows it.

fixed f5f0e26
we will need a proper Buffer class copy and reassignment operation to avoid heap pointer declaration.


 Support for Firefox

Support for Firefox would be a nice innovation.

There already is an issue open for this  Issue #14 . I looked into it but as Firefox does not support the Chrome Devtools Protocol fully, the MediaSession API is not available. I was able to get it to work somewhat by starting the browser through Selenium but this adds overhead to the user experience and no guarantee it will work on all browser versions.


[WIP] M3-2 Authentication and Persistent Sessions

Adds authentication and authorization with the following core components:

Refresh logic for persistent sessions, using the concept of "silent authentication" within an iframe
Removal of all thunks for session-related action creators, porting them to plain action creators with types
Our first typed reducer in M3 for storing the OAuth token and scopes
Our first typed action creators in M3, for authorization and logout
The typed AuthenticationWrapper, which redirects to login service with the appropriate parameters if the user is not authenticated
The typed OAuthCallbackPage, which parses the response from the login server and begins the session

Coverage decreased (-33.1%) to 30.372% when pulling 81b6de31959124a0f4b2806f70dc590f7645f9ea on asauber:M3-2-authentication-and-persistent-sessions into a1843bd668ecdd3c7fa6120ce3b4ece2cac1f931 on linode:voldemort.


Updated the travis settings and commited the comoser.lock

I added some more PHP version to travis and updated the tasks according to the travis docs.
I did also (I know it is controversial) commit the composer.lock file. Why would I do such awful thing? Nils Adermann had a presentation in FOSDEM where he said this is actually recommended. Now we can be sure that if the bundle fails it wont be because some of our dependencies fails.
(Yes, if everyone was strictly following Semver we wound not have this problem... but we can't rely on that.)

I agree about committing composer.lock


publish distrib and 2FA

I have 2FA enabled, and I basically never use the https auth for github (I always go through ssh).
When trying to use publish distrib, I get a 401 that ends with this:
{
"message": "Must specify two-factor authentication OTP code.",
"documentation_url":
  "https://developer.github.com/v3/auth#working-with-two-factor-authentication"
}

I guess there is an extra step needed.
Alternatively, dune-release could direct me to the page for creating personal access tokens.

Should be fixed by #7
The tool will now ask you to create the token with GitHub web UI.


The setting defaultPipelineOn should be renamed to defaultPipeline

Instead of defaultPipelineOn = true, we should use defaultPipeline = on.

Please also make sure we change the documentation and clearly show defaultPipeline = on is part of the squbs-meta.conf. Just show it in the example.


Merge pull request #1 from drone/master

Merging upstream provider

 You should sign our Contributor License Agreement in order to get your pull request merged.


Sections do not update when DisableAnimations = true

How to reproduce?
Set a binding value to a section, and update it. The section moves along the chart to the new value. Set the Chart DisableAnimations to True, now change the section value and note it doesn't change until DisabledAnimations is again set to false
Extra notes
I wanted a Mouse Crosshair that snapped to datapoints, so am using a hacky-updating Axis Section to accomplish this. When I zoom out the chart turns off animations to maintain speed.
I am using

Live-Charts version
.WPF 0.9.5Geared 1.2.7

This is not an issue with the library, this is how normally animation work in WPF, you cant play like this, it is whether animated or not 😟

I am closing this for now, since this issue is not with the library, LiveCharts is built in the top of WPF.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 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.:x: Surenderpagidimarry-Devops sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

done

done


Fix reading of mesh network from configmap

Fixes https://github.com/istio/istio/issues/32962
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@howardjohn: new pull request created: #33150

In response to this:

/cherrypick release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


How do i even use this

Why are the installation instructions so complicated?

What part about it so you not understand?

What are you trying to do exactly?
If you only plan on using models on your on images/videos, then it's probably better to use simpler projects made for that purpose: https://github.com/victorca25/traiNNer#for-simple-testing.
If it's training your own models, installing is really just making sure you have the dependencies and  cloning this repo (or downloading the zip archive). Alternatively, after downloading this repo you can run:
pip install -r requirements.txt optional_requirements.txt

to install all the dependencies automatically and you can start using everything, which in most cases using the defaults and following the instructions: https://github.com/victorca25/traiNNer#training will be enough to get you started, this is one of the easiest (if not the easiest) project to get working models with the least effort, but more details about what part you don't understand would be more useful if you need help.


Remove the use of realpath in tests

The //lib/tests/transitions tests fail on macOS unless coreutils package is installed. Even if in this particular the realpath is not necessary, we should avoid relying on optional packages in tests.

 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.Konstantin Zadorozhny 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.

Thanks! Looks like this doesn't work on linux unless we pass -L to file. Otherwise it won't deference the symlink. I hope file on osx has the same option?

Looks like -L is supported on both. Could you make that change? Actually, the long name --deference would be more readable.


Harmful to edit dconf with nix

At least 6 times I mistook to edit the dconf path, and it takes long minutes... :angry:
https://github.com/kachick/dotfiles/blob/3dd20d99043cb991edf275a28441302e482be65f/home-manager/gnome.nix

wrong delimiter for / => .
missing directory
duplicated /
Wrong switched to another directory
etc...?

https://github.com/nix-community/home-manager/blob/b3d5ea65d88d67d4ec578ed11d4d2d51e3de525e/modules/misc/dconf.nix#L71
https://github.com/NixOS/nixpkgs/blob/92d9df3af6b892b94fdb54b2027dab9ef1fa6f6c/nixos/modules/programs/dconf.nix
https://github.com/nix-community/dconf2nix 👀

I might implement the validator, but I can close this for now.
Because of

Added zellij layout for this purpose
I don't actively touch dconf in these days (Almost done and stable)

[ ] Enable home-manager CI for All related PRs again
[ ] Add linter for dconf


Stack overflow/deep recursion when using liftM/MonadFinally with a custom monad

Description
I stumbled across this while bumbling through the standard library, attempting to implement MonadFinally/MonadExcept for a custom monad.
The following MWE, when loaded into Visual Studio code, will (correctly) cause a type checking error due to the inability to locate a MonadExcept instance. However, uncommenting the IO.println call on line 20 will instead cause the interpreter to explode. The blast radius of the detonation is so large it even causes the vscode integration to break and become completely unresponsive, requiring a restart of the whole editor process. This is 100% reliable and reproducible for me.
namespace TryCatchWithAutolift

structure M (α : Type) where
  σ : ExceptT String IO α

instance : Monad M where
  pure x   := { σ := pure x }
  bind x f := { σ := do (f (← x.σ)).σ }
  map f x  := { σ := do f (← x.σ) }

instance : MonadLiftT IO M where
  monadLift {α : Type} (act : IO α) : M α :=
    { σ := monadLift act }

instance : MonadFinally M where
  tryFinally' := fun x h => M.mk do
    tryFinally' x.σ fun e => (h e).σ

def t : M Unit := do
  -- liftM $ IO.println "bad" -- ← uncomment this line to have a bad time
  try do pure ()
  catch ex : IO.Error => do pure ()
  finally do pure ()

end TryCatchWithAutolift

The output log of vscode:
libc++abi: terminating with uncaught exception of type lean::stack_space_exception: deep recursion was detected at 'replace' (potential solution: increase stack space in your system)
[Error - 10:25:43 AM] Request textDocument/semanticTokens/full failed.
  Message: Server process for file:///Users/aseipp/t/bug.lean crashed, likely due to a stack overflow in user code.
  Code: -32603

Versions
aseipp@navi ~ % uname -a
Darwin navi 20.4.0 Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:41 PDT 2021; root:xnu-7195.101.2~1/RELEASE_ARM64_T8101 arm64
aseipp@navi ~ % lean --version
Lean (version 4.0.0-nightly-2021-05-08, commit 4675817a9e89, Release)
aseipp@navi ~ % code --list-extensions --show-versions | grep lean4
<EMAIL_ADDRESS>

After a little more investigation, I thought this only occurred with autoLifting, but I was wrong, and ordinary liftM causes it too. Sorry for the noise!