MSID: 87271 Version: 1 DOI: osf.io/mgn32

"msas": "Neuroscience"
"msid": "87271"
"preprintDoi": "10.31234/osf.io/mgn32"
"Reviewed Preprint posted": "2023-06-12"
"Sent for peer review": "2023-03-29"
"Posted to PsyArXiv": "2023-02-28" (link: "Go to PsyArXiv": "https://psyarxiv.com/mgn32")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87271)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/87271/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: https://github.com/elifesciences/enhanced-preprints-data/pull/102
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.31234/osf.io/mgn32)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/87271/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/87271)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/87271

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/87271

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/87271/v1/87271-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/87271)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

(Reviews not on Sciety)

I've messaged Sciety for an answer.

Hi @acollings
We had a quick look this morning, and although Sciety does support ingestion of reviews from OSF it seems that OSF have more than one DOI prefix and this particular one isn't support on Sciety yet. So this will need a bit of work from the Sciety team to be added in.

Beat me to it @BlueReZZ! @acollings can you share the expected volume of OSF articles?

Hi @QueenKraken, I estimate around 1/100 Reviewed Preprints will be from OSF (or the servers they support/provide).

Thank you @acollings  :)

Hi @QueenKraken FYI, a second one using the same preprint server is due for publication on June 30:
https://github.com/orgs/elifesciences/projects/16/views/1?pane=issue&itemId=31155492

Hi @acollings this is in the Sciety queue: https://miro.com/app/board/o9J_ksVfD4E=/?moveToWidget=3458764557410855107&cot=14

@QueenKraken super!

Reviews are on Sciety!

@hazalCiplak, Is any extra work required in dataHub to support OSF reviews? I can't see them at
https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87271
or https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=87271

Ah thank you Fred for letting me know. It appears that there is a need for further development to properly represent OSF in the DocMaps API. I have created this ticket to follow the case.

Thanks!

(From the authors: Could you please give an update as to when this will be pubished? We are
waiting to submit a revised version but were told to wait until the first version had been published.
Additionally, we paid the fees several weeks ago and our funders are waiting for confirmation that the manuscript was indeed published.)
@fred-atherden would you be able to see if this is now unblocked? Thanks!

Here is the corresponding DocMaps link for the manuscript. I managed to close related ticket yesterday so today it should be unblocked. Please let me know if there is anything else I can help with.


Symlink header files

Motivation:
On some platforms swift build is failing with error:
 public headers ("include") directory path for 'CDataStaxDriver' is invalid or not contained in the target

Modifications:
Copying https://github.com/swift-server/swift-kafka-client's structure, adding CDataStaxDriver/include and symlinks to header files under datastax-cpp-driver/include.
rdar://123389483

@swift-server-bot test this please

Turns out the said problem is due to missing git submodules. I won't merge this PR then.


control menuView as subView of navigationBar

an answer from stackoverflow
it seems to be the system's bug, control its show up or hidding via viewController's life cycle methods will be hacky solution for it. It works in my new PR test. what do you think?

Still considering to set it as the titleview, in order to allow the system to manage the alpha correctly during navigation.
I tried to override menuview frame's setter, and make the menuview's scrollView center(it's width is larger than menuview's).
It still will cause a problem if someone want menuView.layer.masksToBounds = true(or clipsToBounds = true), but may no one has this need.....
I just push the commit, what do you think?

I have tried your new commit version. It works well, your solution maybe
the best currently. Perhaps, Apple will fix this bug future. Thanks  bro!
2016年4月19日星期二，Wang Ming<EMAIL_ADDRESS>写道：

Still considering to set it as the titleview, in order to allow the system
to manage the alpha correctly during navigation.
I tried to override menuview frame's setter, and make the menuview's
scrollView center(it's width is larger than menuview's).
It still will cause a problem if someone want menuView.layer.masksToBounds
= true(or clipsToBounds = true), but may no one has this need.....
I just push the commit, what do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/wangmchn/WMPageController-Swift/pull/9#issuecomment-211714282

thanks


LicenseScout needs a logo

Feature request
Expected Behavior - What where you expecting to happen?
LicenseScout needs a logo to distinguish our various projects.
Current Behavior - What happens?
LicenseScout has no logo.
Possible Solution
Somebody to sketch a text based logo.
Context
Marketing
Notes and further information

we decided to take this into account.
Contributions for this feature are highly welcome!

Maybe, a combination of a magnifying glass and a libra?

I played around with Looka and like those ...

Attention: these logos are not for free!

i really like the "scout" -> i will try to find/create something similar which is compatible for us

What about this? Logo is from icons8.com

i like it :-)

Maybe something like this?

Also a nice one. Maintainers, decide for a logo!

for me it's too much connected to a Safari trip haha

Thanks for all your ideas! We will have our next maintainer meetup in the upcoming week. @aposin/maintainers There we will take a decision.

we decided to go with the "tent" as a blueprint, i will create a more detailed one

Beautiful. 👍

+1 for https://github.com/aposin/LicenseScout/issues/17#issuecomment-538653675

like it too - Looks cool

+1


SUR with three-dimensional exog

Thanks @bashtage for introducing me to SUR and linearmodels over at stackoverflow.
I'm having a bit of trouble with using the SUR model in the way I would like to, and I hope you can help. I'm sorry that this issue has become quite long. I'm happy to ask elsewhere, but if you have the time, I'd be very happy to hear your thoughts.
I'm trying to fit a number of linear components to a number of spectra. Each spectrum is a one dimensional array (typically of length 1024) that has been taken by a microscope. The microscope does this across a number of pixels (lets say a grid of 64 by 64) on a sample. So my raw data, my dependent variable has numpy shape (64,64,1024). Later on in this post I'll take the product of the pixels, changing the shape into (64*64, 1024).
My components can be a variety of things, but for the sake of argument, let's say I'm trying to fit a second order polynomial as a background. So we have three components, x**2, x and 1. I compute each one for the spectrum which results in three arrays, or a ndarray of shape (3,1024).
Normally, I would now either (functions timed with jupyter notebook):
A) loop over the 64x64 pixels, and run np.linalg.lstsq() on each spectrum:
%%timeit
rawdata = np.random.random((64,64,1024)).reshape(64*64,1024)
components = np.random.random((3,1024))

for i in range(rawdata.shape[0]):
    np.linalg.lstsq(comps.T, rawdata[i])
664 ms ± 25.7 ms per loop

or B) use the "not-really-designed-for-this" OLS:
%%timeit
rawdata = np.random.random((64,64,1024)).reshape(64*64,1024)
components = np.random.random((3,1024))

sm.OLS(rawdata.T, components.T)
57 ms ± 1.78 ms per loop

OLS is much faster, especially when I increase the number of pixels. That's great.
Unfortunately, my problem is ideally a little bit more complicated. In addition to simple components like x**2, we often want to use Gaussians or similar expressions, but where all the parameters are fixed. However, these components will not always be equal in every pixel. In some pixels the component has been pre-fitted in some manner - perhaps the centre of the gaussian is shifted a little to the right or to the left.
This means that I have increased the number of dimensions of my components so my new component shape is now (64,64,3,1024). Around now I think you'll be seeing my problem. Trying to feed my component data as the exog variable, I get the ValueError: exog_0 has too many dims.  Maximum is 2, actual is 3.
This leads me to think that I've got the wrong model, or at least a problem which is not suitable to be solved in this manner.
I should add that I wasn't able to fit the first case (like I do with numpy and statsmodels) with SUR - I'm not sure where I go wrong, but it's definitely my syntax:
from linearmodels import SUR
import numpy as np

rawdata = np.random.random((64,64,1024)).reshape(64*64,1024)
components = np.random.random((3,1024))

equations = {
    'test':{
        'dependent':rawdata,
        'exog':comps
    }
}

SUR(equations)
ValueError: Array required to have 4096 obs, has 3

Thanks for reading. Sorry that the post became so long, but I feared giving too little information, and since we work in very different fields and with very different "languages", I thought it better to fully explain. If you have any suggestions or advice, I'll gladly take them.

I think you are after a multivariate OLS.  If I understand your intention correctly, you want something like
from linearmodels import SUR
import numpy as np

rawdata = np.random.random((64,64,1024)).reshape(64*64,1024)
components = np.random.random((3,1024))
mod = lm.SUR.multivariate_ls(rawdata.T, components.T)
res = mod.fit()

The inputs should be nobs by nseries for the dependent and nobs by nvar for the regressors.
In terms of performance, you should not use this if you only want parameter estimates.  The fastest want to get estimates is to directly call np.linalg.lstsq.  The utility of this approach, if any, is if you need to perform inference on coefficients across the multiple OLS models.


Geo.test

http://scratch.mit.edu/projects/228823295
http://phosphorus.github.io/#228823295
Error: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The source height is 0.
    at Sprite.touching (https://phosphorus.github.io/phosphorus.js:1643:37)
    at eval (eval at scopedEval (https://phosphorus.github.io/phosphorus.js:4014:14), <anonymous>:2:31)
    at Stage.P.runtime.P.Stage.step (https://phosphorus.github.io/phosphorus.js:3938:15)

this is happening to me everytime i load a project :/


Custom Graphical Elements?

With the available graphical elements all created via the theme interface it seems that applications wanting/needing to provide custom elements will be difficult.  Is it possible for a client to design their own widget, add it to a layout, and have it rendered?  I haven't yet wrapped my head around the mixin architecture enough to determine if a compliant object just needs to meet a set of interfaces.  If it's possible, this might make for a good, simple example.

Is it possible for a client to design their own widget, add it to a layout, and have it rendered?

Yes, completely. There's really nothing special about the mixin implementations, but I completely understand that the whole structure is really confusing. We're thinking about how we can clean this lot up, and make it more idiomatic.
To very briefly describe the current layout:

The top level is the theme. This is really just a factory for a number of control types that implement the interfaces in the GXUI root. The theme can tweak the control's colors and styling by changing fields and overriding some of methods of the mixins.
The mixins directory holds full, un-styled implementations of the various controls. They usually 'derive' from one of the types in the base package.
The mixins\base package provides the bulk of the implementation for Control and Container types.
The mixins\parts package holds partial implementations of controls. i.e. Layoutable implements the SetMargin, Margin, Bounds, Layout, and Relayout methods the way most of controls would want. You can cherry-pick these parts into your new control to remove boilerplate code.

If it's possible, this might make for a good, simple example.

I agree more samples are usually good, but I'm wary of giving examples at this stage for things that are very likely to significantly change. I don't think anyone is happy with the way Component are currently built (the whole mixin and FooOuter stuff are like hammering a square-peg in a round hole). If we can sort this out, then I'm more than happy to create step-by-step tutorials.
If you'd like any more information on any of this, please ask away. The more information I can share, the higher chance there is that someone can offer a far better and cleaner approach to solve the same problems. :)


feat(dart_frog): Expose shelf's additional Response constructors

closes https://github.com/VeryGoodOpenSource/dart_frog/issues/594
Do not covered with tests, because it's covered in the shelf itself. Or I still need to duplicate tests for 100% coverage?
Status
READY
Description
Expose shelf's additional Response constructors:

badRequest
forbidden
found
internalServerError
movedPermanently
notFound
notModified
ok
seeOther
unauthorized

Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

@Spiritcow would you like to make the amendments to the PR to fit with https://github.com/VeryGoodOpenSource/dart_frog/issues/594#issuecomment-1551710795?

I'm closing this issue due to inactivity of the original author 💙 . Feel free to re-open or create a new Pull Request to address the isssue.


Initializing libiomp5.dylib, but found libomp.dylib already initialized.

🐛 Describe the bug
The issue appears on MacOS py3.8, it started after updating to the latest nightly 1.13.0.dev20220525-py3.8_0 from core (previously I was at 1.12.0.dev20220309-py3.8_0, so the issue could have been introduced earlier than May 25th). I'm receiving the following after importing numpy and pytorch together:
$ python -c "import numpy;import torch"
OMP: Error #15: Initializing libiomp5.dylib, but found libomp.dylib already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.

Strangely, importing first torch works:
python -c "import torch;import numpy;print('works')"
works

Setting KMP_DUPLICATE_LIB_OK=TRUE as env var solves the issue while invoking from console:
KMP_DUPLICATE_LIB_OK=TRUE python -c "import numpy;import torch;print('works')"
works

Sometimes I get segfaults thought, this doesn't seem like a stable solution.
Versions
Latest Core nightly (20220525).

I've ended "fixing" the issue by wiping my conda setup, moving to py3.10 and reinstalling dependencies. The issue was definitely not related to TorchVision as I managed to reproduce it only using Core. It could be related to some weird dependency on my system though.
As discussed with @atalman I'll leave the issue open just in case this is something suspicious that needs to be investigated on the future. I know there were a bunch of macOS changes recently on OK. Feel free to close or move to Core.

@datumbox you should have run python3 -mtorch.utils.collect_env and posted results here. What I suspect has happened: in your env you've installed PyTorch from wheels, but numpy from conda-forge

Here they are
(base) atalman-mbp:Downloads atalman$ python3 -mtorch.utils.collect_env
Collecting environment information...
PyTorch version: 1.13.0.dev20220525
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 12.3.1 (x86_64)
GCC version: Could not collect
Clang version: 13.1.6 (clang-13<IP_ADDRESS>.3)
CMake version: Could not collect
Libc version: N/A

Python version: 3.9.7 (default, Sep 16 2021, 08:50:36)  [Clang 10.0.0 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.20.3
[pip3] numpydoc==1.1.0
[pip3] torch==1.13.0.dev20220525
[pip3] torchaudio==0.12.0.dev20220525
[pip3] torchvision==0.14.0.dev20220525
[conda] blas                      1.0                         mkl
[conda] mkl                       2021.4.0           hecd8cb5_637
[conda] mkl-service               2.4.0            py39h9ed2024_0
[conda] mkl_fft                   1.3.1            py39h4ab4a9b_0
[conda] mkl_random                1.2.2            py39hb2f4e1b_0
[conda] numpy                     1.20.3           py39h4b4dc7a_0
[conda] numpy-base                1.20.3           py39he0bd621_0
[conda] numpydoc                  1.1.0              pyhd3eb1b0_1
[conda] pytorch                   1.13.0.dev20220525         py3.9_0    pytorch-nightly
[conda] torch                     1.12.0                   pypi_0    pypi
[conda] torchaudio                0.12.0.dev20220511          pypi_0    pypi
[conda] torchvision               0.13.0.dev20220511          pypi_0    pypi

@malfet I've updated the issue with the requested output. In my case your suspicion seems correct which is different from what @atalman reports. Hope it helps. Feel free to move this issue on PyTorch core if you want, as this is not related to TorchVision.

Ok, can we please clarify the following: what conda package provides libiomp5.dylib? If it's provided by MKL base, that we do not need to bundle it with the package, but rather take it from conda, i.e. following function should not be called when building conda packages for MacOS https://github.com/pytorch/pytorch/blob/18d46ea9fd5071820cdbe7595b99396a9153f716/setup.py#L432


Spawn killing suicide.

More chi translation.
It doesn't make any sense to ban player if they tried to damage themselves.

Eh. Maybe ignore that subplugin I wrote.


refactor: group Open Graph module by feature dirs

Issue or need
Same as recent PRs but for Open Graph module

Proposed changes
Same as recent PRs but for Open Graph module
The image metadata provider setter factory is now not exported
Features have been grouped by Open Graph verticals + basic and optional main one

Quick reminders

🤝 I will follow Code of Conduct
✅ No existing pull request already does almost same changes
👁 Contributing docs are something I've taken a look at
📝 Commit messages convention has been followed
💬 TSDoc comments have been added or updated indicating API visibility if API surface has changed.
🧪 Tests have been added if needed. For instance, if adding new features or fixing a bug. Or removed if removing features.
⚙ API Report has been updated if API surface is altered.

#865  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


event["Host"] empty

Hello,
Looks like event["Host"] is always empty if we have only IP addresses in the slow query log.
For example, if running MySQL with skip_name_resolve=ON, the slow log will contain only IPs and no hostnames.
Cheers,

https://github.com/Preetam/mysqllog/releases/tag/v0.3.0 addresses this.


Fix hamburger menu (fixes issue #11)

As indicated in issue #11 , the hamburger menu does nothing when clicked. It looks as if Bootstrap is supposed to include code that toggles this menu, but other than CSS styling I see nothing else in the project that uses Bootstrap. So I wrote a listener that would listen for clicks to the hamburger menu and toggle the menu.
This fixes #11 . (And this should link the two?)
This may not apply cleanly with #12 because both modify incudes to router.js .This should be relatively easy to resolve, however.
I am also not certain where my listener code should be invoked, so I put it in router.js.

I have been reading into the issue of where to structure Backbone code some more. I think the Backbone Primer has some clues: https://github.com/jashkenas/backbone/wiki/Backbone%2C-The-Primer#getting-view-support:

View management is by far the least regulated component of Backbone, and yet is ironically among the most disciplined roles in front-end engineering. While Backbone.View provides some very useful low-level utility features, it provides few high-level workflow features. As a result, major Backbone extensions including Marionette and LayoutManager have become popular. Also see ContainerView for a minimalist extension of core Backbone.View features.

Adding this listener properly may require incorporating one of these extensions. Given the structure of the code thus far, that seems like a hassle. My preference would be to continue initializing the listener in router.js , but if that is unacceptable then we can look at refactoring the code.

Backbone is pretty open with how to accomplish things. I use it professionally, so have developed my own style and would like to stick with that.
For the hamburger menu specifically, we shouldn't have to do anything, Bootstrap should handle it itself. I'd like to upgrade to the latest bootstrap and try and fix it from there. We definitely don't need to add a backbone view for the hamburger menu.

I agree that Bootstrap should handle the hamburger menu, but we are
not invoking the Javascript Bootstrap anywhere. I think we are just
using the CSS parts.
The view I wrote is minimal, with the idea that if we do not need full
Bootstrap functionality then we can get by with just that listener.
But using full Bootstrap is okay too.
On Fri, Jun 09, 2017 at 06:32:46AM -0700, Will Spaetzel wrote:

Backbone is pretty open with how to accomplish things. I use it professionally, so have developed my own style and would like to stick with that.
For the hamburger menu specifically, we shouldn't have to do anything, Bootstrap should handle it itself. I'd like to upgrade to the latest bootstrap and try and fix it from there. We definitely don't need to add a backbone view for the hamburger menu.


boards: arm: stm32f4i_disc1: Fix LED color

Fix wrong LED color in STM32F4I_DISC1 devicetree.
Signed-off-by: Thien Nguyen<EMAIL_ADDRESS>

could you make it just one commit?

Hi, I have squashed them into one commit

could you make it just one commit?

Hi, I have squashed them into one commit

Yes, thanks! This will get merged soon :)


About paper results

Thanks for your great work. I want to know how you train DS-NeRF from a single view. DS-NeRF needs structure-from-motion to aquire 3D sparse points. Thanks in advance!

We use a dense depth map instead of sparse points for all experiments. In the original implementation of DS-NeRF, depth supervision is implemented as a list of rays with depth loss. In our experiments, we simply add depth supervision on all the rays.


Can't read input until after the output has been configured once when using circuits_gpio

In below code, GPIO pin 26 is D18 of Grove Base Hat for Raspberry Pi.
iex(1)>  {:ok, gpio} = Circuits.GPIO.open(26, :input)
{:ok, #Reference<0.1962860034.377356295.248080>}
iex(2)> Circuits.GPIO.read(gpio)
0 # button is not pushed
iex(3)> Circuits.GPIO.read(gpio)
0 # button is pushed, but can't read its value
iex(4)>  {:ok, gpio} = Circuits.GPIO.open(26, :output)      # once configure with output
{:ok, #Reference<0.1962860034.377356295.248081>}
iex(5)>  {:ok, gpio} = Circuits.GPIO.open(26, :input)       # make it back to input
{:ok, #Reference<0.1962860034.377356295.248082>}
iex(6)> Circuits.GPIO.read(gpio)
0 # button is not pushed
iex(7)> Circuits.GPIO.read(gpio)
1 # button is pushed, now can read its value

This doesn't happen with debian which boots with same kernel and same dtb.
debian@arm:~$ gpioget gpiochip1 10
0
debian@arm:~$ gpioget gpiochip1 10
1

So, this might be a contribution chance to circuits_gpio.

I confirmed below,  also works
iex(3)> cmd "echo 26 > /sys/class/gpio/export"
0
iex(4)> cmd "echo in > /sys/class/gpio/gpio26/direction"
0
iex(5)> cmd "cat /sys/class/gpio/gpio26/value"
0
0
iex(6)> cmd "cat /sys/class/gpio/gpio26/value"
1
0

Once a version containing https://github.com/elixir-circuits/circuits_gpio/pull/119 is released, this issue is fixed.

https://github.com/elixir-circuits/circuits_gpio/releases/tag/v1.0.1, includes above fix, is released.
Now we can close this, yey!

what a fantastic contribution!!


clarify "Compare that to docker layers"

readme says

Smart caching: It uses smart crate by crate caching so that nix rebuilds exactly the crates that need to be rebuilt. Compare that to docker layers...

please clarify "Compare that to docker layers..."
 Nix caching is not similar to Docker layers, which have a linear dependency chain (based on where in the stack the layer appears), rather than a graph. Docker layers are deltas that linearly depend on each other, and as such are fairly less powerful in their caching capability.


Manual Build part is broken

Clone the repo.
Read the Readme, "Manuals Builds" part
run ./docker-make
get full buch of outdated warnings and eventually errors that break the build
Seems like totally outdated, at least what is Node-related

This is what I get.

./docker-make

+ sudo docker build -t mattermost-plugin-jitsi-builder .
[+] Building 0.3s (2/3)
[+] Building 0.4s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 74B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [internal] load metadata for docker.io/library/golang:1.13                                                                                0.3s
------
 > [internal] load metadata for docker.io/library/golang:1.13:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: ``

{
  "name": "jitsi",
  "version": "1.1.0",
  "description": "Jitsi audio and video conferencing plugin for Mattermost",
  "main": "src/index.tsx",
  "scripts": {
    "build": "webpack --mode=production",
    "debug": "webpack --mode=none",
    "webpack-stats": "webpack --profile --json > stats.json",
    "bundle-analyzer": "webpack-bundle-analyzer stats.json",
    "lint": "eslint --ignore-pattern node_modules --ignore-pattern dist --ext tsx --ext ts . --quiet",
    "fix": "eslint --ignore-pattern node_modules --ignore-pattern dist --ext tsx --ext ts . --quiet --fix",
    "test": "LANG=C TZ=UTC jest --forceExit --detectOpenHandles --verbose",
    "test:watch": "LANG=C TZ=UTC jest --watch",
    "test-ci": "LANG=C TZ=UTC jest --forceExit --detectOpenHandles --maxWorkers=2"
  },
  "author": "",
  "license": "",
  "devDependencies": {
    "@types/enzyme": "3.10.12",
    "@types/jest": "29.4.0",
    "@types/node": "18.13.0",
    "@types/react": "18.0.28",
    "@types/react-dom": "18.0.10",
    "@types/react-redux": "7.1.25",
    "@types/react-router-dom": "5.3.3",
    "@types/react-transition-group": "4.4.5",
    "@typescript-eslint/eslint-plugin": "5.52.0",
    "@typescript-eslint/parser": "^5.52.0",
    "enzyme": "3.11.0",
    "@cfaester/enzyme-adapter-react-18": "0.6.0",
    "enzyme-to-json": "3.6.2",
    "eslint": "8.34.0",
    "eslint-import-resolver-webpack": "0.13.2",
    "eslint-plugin-import": "2.27.5",
    "eslint-plugin-react": "7.32.2",
    "file-loader": "6.2.0",
    "html-webpack-plugin": "5.5.0",
    "identity-obj-proxy": "3.0.0",
    "jest": "29.4.2",
    "jest-canvas-mock": "2.4.0",
    "jest-junit": "15.0.0",
    "mattermost-webapp": "github:mattermost/mattermost-webapp#23f5f93d9f12a7e2b5623e5cee6814366abd9a0f",
    "ts-jest": "29.0.5",
    "ts-loader": "9.4.2",
    "typescript": "4.9.5",
    "webpack": "5.75.0",
    "webpack-bundle-analyzer": "4.8.0",
    "webpack-cli": "5.0.1"
  },
  "dependencies": {
    "core-js": "3.28.0",
    "mattermost-redux": "5.33.1",
    "prop-types": "15.8.1",
    "react": "18.2.0",
    "react-intl": "6.2.8",
    "react-redux": "8.0.5",
    "redux": "4.2.1",
    "redux-thunk": "2.4.2"
  },
  "jest": {
    "preset": "ts-jest",
    "globals": {
      "ts-jest": {
        "isolatedModules": true
      }
    },
    "snapshotSerializers": [
      "<rootDir>/node_modules/enzyme-to-json/serializer"
    ],
    "testPathIgnorePatterns": [
      "/node_modules/",
      "/non_npm_dependencies/"
    ],
    "clearMocks": true,
    "collectCoverageFrom": [
      "src/**/*.{ts,tsx}"
    ],
    "coverageReporters": [
      "lcov",
      "text-summary"
    ],
    "moduleNameMapper": {
      "^.+\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$": "identity-obj-proxy",
      "^.+\\.(css|less|scss)$": "identity-obj-proxy",
      "^.*i18n.*\\.(json)$": "<rootDir>/tests/i18n_mock.json",
      "^bundle-loader\\?lazy\\!(.*)$": "$1"
    },
    "moduleDirectories": [
      "",
      "node_modules",
      "non_npm_dependencies"
    ],
    "reporters": [
      "default",
      "jest-junit"
    ],
    "transformIgnorePatterns": [
      "node_modules/(?!react-native|react-router|mattermost-webapp)"
    ],
    "setupFiles": [
      "jest-canvas-mock"
    ],
    "setupFilesAfterEnv": [
      "<rootDir>/tests/setup.ts"
    ],
    "testURL": "http://localhost:8065"
  }
}

gives
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^9.0.0 || ^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^9.0.0 || ^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^9.0.0 || ^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^9.0.0 || ^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0-beta || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ~0.14.x || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0-alpha but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.3.0 || ^16.0.0-rc || ^16.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.

4 changes in Package.json are needed:
    "enzyme-adapter-react-16": "1.15.7",
    "eslint-import-resolver-webpack": "0.13.2",
    "eslint-plugin-import": "2.27.5",
    "html-webpack-plugin": "4.5.2",

The first three are to get the disappeared versions, and html-webpack-plugin was missing.
Dockerfile needs 2 changes:
FROM golang:latest

RUN curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin v1.51.1

Just bump to the latest, because it's just for building.
Result:

plugin built at: dist/jitsi-2.0.0.tar.gz


fix: drop the number of shots for the VQE ising example to 500

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Expectation calculation complexity reduced in #371.


Using UNION in a subquery leads to a syntax error in Sqlite

Hi, I'm attempting to use a UNION in a subquery, and that is leading to a syntax error when executing the query against a Sqlite backend. Based on attempting to understand the issue, I believe it is a bug in the ORM similar to this other project.
https://github.com/gocraft/dbr/issues/167
Apparently MySQL and Postgres tolerate (SELECT ...) UNION (SELECT ...), but this is not correct syntax. There should be no parenthesis around the individual selects around a union. It should be SELECT ... UNION SELECT ....
The code I'm running is,
        val files = this.session
                .from( Objects )
                .select( Objects.object_id )
                .where { Objects.object_type eq TYPE_FILE }

        val albums = this.session
                .from( Objects )
                .select( Objects.object_id )
                .where { Objects.object_type eq TYPE_ALBUM }

        val all_children = this.session
                .from( Relations )
                .select( Relations.child_id )
                .where { Relations.parent_id inList albums }

        val free_files = files.where { Objects.object_id notInList all_children }

        val select_ids = free_files.union( albums )

        val query = this.session
                .from( Objects )
                .select()
                .where { Objects.object_id inList select_ids }
                .orderBy( randOrder() )

Which yeilds the following query:
SELECT *
FROM objects
WHERE objects.object_id IN (
  (
    SELECT objects.object_id AS objects_object_id
    FROM objects WHERE objects.object_id NOT IN (
      SELECT relations.child_id AS relations_child_id
      FROM relations
      WHERE relations.parent_id IN (
        SELECT objects.object_id AS objects_object_id
        FROM objects WHERE objects.object_type = ?
      )
    )
  )
  UNION (
    SELECT objects.object_id AS objects_object_id
    FROM objects
    WHERE objects.object_type = ?
  )
)
ORDER BY RANDOM();

Both when executed via the code, and directly into sqlite3 this query fails with,
Error: near "UNION": syntax error
Manually removing the extra parenthesis such that the query reads as follows, works.
SELECT *
FROM objects
WHERE objects.object_id IN (
    SELECT objects.object_id AS objects_object_id
    FROM objects WHERE objects.object_id NOT IN (
      SELECT relations.child_id AS relations_child_id
      FROM relations
      WHERE relations.parent_id IN (
        SELECT objects.object_id AS objects_object_id
        FROM objects WHERE objects.object_type = ?
      )
    )
  UNION
    SELECT objects.object_id AS objects_object_id
    FROM objects
    WHERE objects.object_type = ?
)
ORDER BY RANDOM();

Thank you, will fix in next version


Better file lookups to Fix #74 (Breaking Change)

Hello @rochacbruno! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file dynaconf/contrib/__init__.py:

Line 2:63: E261 at least two spaces before inline comment

In the file example/django_example/foo/settings.py:

Line 110:10: E401 multiple imports on one line


build(deps): bump upper version of convert to 3.1.0

convert 3.0.1 has been released. This commit ensures that future patch releases of convert will be supported until 3.1.0.

Thanks for your contribution!

@haarts Would you mind releasing a new version when you have the time to do so? Thanks in advance :smiley:

done


enable travis

@chrissimpkins could you enable travis ci for this repo ? Should be just a toggle in the repo configuration somewhere : https://travis-ci.org/getting_started

Done.  Should be all set.
https://travis-ci.org/source-foundry/java-glyph-tester

Let me know if the current settings do not work

👍

awesome thanks 👍

@jorgheymans : Added Codecov coverage access if you are interested in it for your CI testing:
https://codecov.io/gh/source-foundry/java-glyph-tester


0.3.0 upgrade breaks truffle's own test suite

Running npm test with the current master branch returns this error:
$ npm test

><EMAIL_ADDRESS>test /Users/danfinlay/Documents/Development/ethereum/truffle
> ./test.bash

Your dapp is meant for an older version of Truffle. Don't worry, there are two solutions!

1) Upgrade you're dapp using the followng instructions (it's easy):
   https://github.com/ConsenSys/truffle/wiki/Migrating-from-v0.2.x-to-v0.3.0

   ( OR )

2) Downgrade to Truffle 0.2.x

Cheers! And file an issue if you run into trouble! https://github.com/ConsenSys/truffle/issues

That's embarrassing. :) There's so little tests I forgot to run them. I'll
update them tomorrow.
On Jan 6, 2016 10:19 PM, "Dan Finlay"<EMAIL_ADDRESS>wrote:

Running npm test with the current master branch returns this error:
$ npm test

<EMAIL_ADDRESS>test /Users/danfinlay/Documents/Development/ethereum/truffle
./test.bash

Your dapp is meant for an older version of Truffle. Don't worry, there are two solutions!

Upgrade you're dapp using the followng instructions (it's easy):
https://github.com/ConsenSys/truffle/wiki/Migrating-from-v0.2.x-to-v0.3.0
( OR )

Downgrade to Truffle 0.2.x

Cheers! And file an issue if you run into trouble! https://github.com/ConsenSys/truffle/issues
—
Reply to this email directly or view it on GitHub
https://github.com/ConsenSys/truffle/issues/71.

Fixed! Thanks for pointing this out.


Add template file (coordinates source) for Emlid Studio

Attached are template that I did - should be verified, and sample of POS file generated from Emlid Studio
25-EmLidStudioPOS.zip
Reach-Rover_raw_20230624202211.zip

Fixed in release 1.0.6


Volatile documents don't get deleted at all

No idea why this happens

Alright, I used the wrong ID after implementing server-side encryption. This works now.


Update readme instructions & version

Hello,
I'd like to contribute a small readme update with the following changes:

package version is bumped to 2.0.0, since the current version is at 2.3.0
target dependency snippet is now a one-liner, so users can simply copy & paste it
added an extra code section with a sample Package.swift file, using ServiceLifecycle

Best,
Tib

Thanks for updating this. Do you mind adding this to the index document of our Docc article as well?

I just did that too, using v2.3.0, I hope this is what you were thinking about.

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please


composer.phar does not exist

In the readme, the setup instructions say to run composer.phar. This file doesn't exist, so instead you'll either need to add composer.phar or update the instructions to use a global composer and add it as a prerequisite.

This has been fixed in the recent release for the Slim 4 version


tab-complete case insensitivity

Fairly straightforward, doesn't make sense to have it case sensitive anyways

There are several things I want to change w/ this (upon further usability tests/feedback) before this is ready for a PR, I will resubmit at that time

You can leave it open and push to that branch until you say it's good to merge.


Material You theme option

Hey there, thank you for this amzaing app, using daily as video journal :)
One feature i would line to suggest is to use Material you themeing in the app, it will make app more beautiful and user friendly ✨

Hey there, thank you for this amzaing app, using daily as video journal :)
One feature i would line to suggest is to use Material you themeing in the app, it will make app more beautiful and user friendly ✨

Thank you for the kind words 😊
Agreed, it shall be done in v2.0


Selecting "new folder" and then immediately selecting "new file" in the explorer tab will create a blank but dangerous file

Type: Bug
Steps to reproduce:

Using File Explorer, create a new folder anywhere you'd like.
Open that folder using VS Code.
Create another folder inside using the "New folder..." button, call it whatever you want.
Create some files. Inside these files, write some code in it.
Click on the "New folder..." button, but don't name the folder anything and don't press Enter.
Instead, press the "New file..." button.

Observed behavior: This will create a new file with no name and no file extension. Removing this file will literally remove the folder it is in. It will also  permenately delete all code inside the file, So even if you try to restore the file from Recycle bin, the code inside then has already been deleted.
Expected behavior: The process of creating a new folder should have been cancelled and instead shoud have gone to creating a new file.
VS Code version: Code 1.93.0
OS version: Windows 10 x64

Am I mising a step?

Same here !

Actually I myself wan't able to replicate it. It looks like there needs to be some situation going on for that to happen.
I will include more information later...

Closing as no info has been provided in the past few months


Absolute expiration time is not preserved during recovering from distributed cache to in-memory cache

The current implementation does not take into account the AbsolutExpiration set during the addition of the entry to the IDistributeCache
https://github.com/jodydonetti/ZiggyCreatures.FusionCache/blob/f1380b7c562eeb610c58490fd7e7f63bf69e0569/src/ZiggyCreatures.FusionCache/FusionCache_Sync.cs#L145
This may lead to the extension of the hidden extension of the lifetime of the entry (especially for the TryGet[Async] method).
As IDistributedCache does not return back the expiration time, it's possible to extend the Metadata payload with the calculated absolute expiration and use it during the creation of the entry in the in-memory cache.
Also, it is worth reflecting in the documentation that the current implementation uses FusionCacheEntryOptions for the restored entires.

Hi @yzhoholiev , and thanks for considering FusionCache!
Honestly I think you probably have a point here, but I also remember reasoning about this aspect back at the time when I did it.
Anyway let me look a little bit more into this in the next few days, and I will come back to you.
Thanks!

Hi @yzhoholiev , I've looked more into this.
Here are some random things I'm thinking about:

currently FusionCache already saves the LogicalExpiration into the metadata
I may be able to use that LogicalExpiration as the expiration for the local memory cache, so to have everything aligned (+/- some jittering, if configured)
the metadata though is (currently) saved only if fail-safe is enabled, to not waste resources (memory + bandwidth)
therefore to proceed this way I would be forced to always save the metadata (consuming more resources)
that would ok to have a better, more precise behavior
also I can limit this change only for the distributed cache (so that the expiration will flow through different nodes) and not for the memory cache

The thing is not super straightforward when considering all possibilities, since it involves all possible cases of entries that are from memory or distributed, that are fresh or stale, that are with or without fail-safe enabled, etc...
I'll take some more time to marinate all these thoughts, experiment with some changes and will come back to you as soon as possible.

Hi @yzhoholiev , I just pushed a change that should fix what you reported.
A couple of notes regarding the change:

now, when creating a memory cache entry from a distributed cache entry, the logical expiration will be used if there's metadata, even if fail-safe is not enabled for that specific call
to allow for the logical expiration to be there even when fail-safe is not enabled, FusionCache now always includes the metadata in the distributed cache entry
if specified, jittering will still be added locally on top of the logical expiration from the distributed cache, so to respect that settings (which btw is disabled by default)

This allows us to have a more precise local expiration in case an entry is coming from the distributed cache, on top of not consuming more memory in case there's no distributed cache involved.
Please let me know what you think: in case everything looks good also to you, I'll push a new release asap.
Thanks!

Hi @yzhoholiev , I just saw your 👍 reaction: just so I know what to do, the thumbs up was like "ok I'll take a look at that and let you know" (so I'll wait) or "I looked at that and it is good to me" (so I move on and release a new version)?
Thanks!

@jodydonetti sorry for the uncertainty. We will spend some time testing the implementation.

Got it, thanks!

The fix seems to be working!

Awesome, thanks for testing it!
I'll release a new version in the next days, will update you.

Hey @yzhoholiev , I just released v0.13.0 which contains this fix, hope this helps.
Closing this issue.


Bug: Not Contains does not return blank or null values

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

Current behavior
When I have a column with blank or filled values, if I type a value and select not contains, blank values do not return despite the fact that they do not contain the typed in value.
Expected behavior
When I filter by not contains, I should see all values that do not contain the value including the blank values.
Minimal reproduction of the problem with instructions
This can be seen on the documentation for the text filter: https://www.ag-grid.com/javascript-grid-filter-text/?framework=all#gsc.tab=0
in order to get it to happen,

sort the athletes (there are 3 with no names)
change sort to "not contains"
type a value (i.e. "aaron")
the values with nothing in them will also fail to show despite not containing "aaron"

What is the motivation / use case for changing the behavior?
I am using the grid to display data for a variety of document sources and some of the fields have the possibility of not being populated
Please tell us about your environment:
Windows 7/10, IE11 (though I can replicate it in Chrome).

ag-Grid version: 10.0.0 & 12.0.0

Browser:
IE11, Chrome 58

Language: ES5

This has been fixed and it will be available in the next release


Fix the error of create-ksplat.js

fix: THREE is not defined & TypeError

Thanks for finding this bug and providing the fix! I went ahead and re-made the fix in a different branch to include with several other updates that went into release v0.3.8, so I'll close this PR.


Complete months + exposing convinient period selection

Added:

Clearer error messages
Bug fix: monthly did a partial month on the same month last year
Ability to get data per period
Factorized code for different periods with a global config map

can you add simplejson in requirements.txt and setup.py

It's done. Thanks for the great library !


Fix bug #254 with comment "Preview of this file is not supported". ext2a...

...pp.txt - correspondence table extensions and templates of highlights. Add new rule in .gitignore (add ext2app.txt to white list)

Thanks for the PR. I thought about it, but I'd prefer hard coding the value in the existing C# file, instead of dynamically loading ext2app.txt.
The reasons are mostly security (opening a file on the server), performance (opening a file every time someone browse a file in repository browser) and I don't think the list is going to change a lot in the future - if there is something missing, let's just add it to the code and do the release.
Would you mind changing it?

Hardcode is not good idea. In real life we have identical extentions for different application (example, *.p, *.m, *.pl, *.rb and etc.)

I can transfer the contents of a file into the database, but then need to make an interface for editing associations. It's mostly security, but slowly.
I can place a bug on highlight.js, but it is not clear how to describe it with the possibility of repetition


Added system certs unit test

This PR just adds a first unit test for security module when the TLS configuration is created without providing certs but using the system ones.
Other PRs will follow with provided certs.

Yes I wrote that in the description to open another PR for that.

@ppatierno Sorry, my mistake ... I complain when description is empty and don't read it when its not :-o


[JS] docs: Updated README to for updated deployment instructions

#minor
Updated README to for updated deployment instructions on assigning cognitive services openai user role after the bot resources are deployed to azure.
Attestation Checklist

[x] My code follows the style guidelines of this project

I have checked for/fixed spelling, linting, and other errors

I have commented my code for clarity

I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient)

My changes generate no new warnings

I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

Local testing
E2E testing in Teams

New and existing unit tests pass locally with my changes

@corinagum and @aacebo can you please review this pull request for updating the README to have the correct directions for setting up permissions to the deployed bot


Google drive link not working

This link is not working ?
download backend from below and place yolo_weights.h5 in model_data folder
https://drive.google.com/drive/u/0/folders/1Qj46bDCBWMbIXm7rPZCIjCVIczxaj2l

I think this link could help you
https://github.com/qqwweee/keras-yolo3/blob/master/README.md
This part of code is from this project(maybe the other one) and then I copy some of the words from README and now the link is not working
I am very sorry to reply you so late.


[Bug]: ListBot app bot is throwing error whenever a command is provided

Language
C#
Version
latest
Description
After installing the app and whenever a command is provided the bot is throwing error saying "Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')".

Reproduction Steps
1.Run the sample as per the readme
2.Install to teams
3.Try to provide any command to the bot

@AjayJ-MSFT : I tried but the issue is not reproducible for me.
Can you check with latest version in repository and let me know if issue is reproducible. Do we have any specific steps to reproduce the issue?

@SubbaReddi : I’m following the steps outlined in the README to run the sample with the latest repository, but I’m still encountering the same issue.

Can you ping me in teams to validate the issue?

@SubbaReddi : We have verified that the sample is working for us with a paid OpenAI API key.


[bug] Non sheet select box has a hard dependency on DOM code

Describe the bug
The inline dropdown select seems to have a hard dependency on DOM code -- when the sheet implementation is not used it uses this file https://github.com/tamagui/tamagui/blob/8969917be9f2a6f1f6e751946ee432aa2727186f/packages/select/src/SelectImpl.tsx which utilises DOM specific code, causing the app to crash
To Reproduce
Implement a Select box as desribed in the docs but without a sheetBreakpoint

System Info (please complete the following information):
  System:
    OS: macOS 13.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
    Memory: 61.30 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.13.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Firefox: 107.0
    Safari: 16.1
  npmPackages:
    @manypkg/cli: ^0.19.1 => 0.19.2
    @types/react: ^18.0.15 => 18.0.25
    @types/react-native: ^0.69.6 => 0.69.15
    eslint: ^8.21.0 => 8.28.0
    prettier: ^2.7.1 => 2.7.1
    react-native: 0.69.7 => 0.69.7
    turbo: ^1.4.2 => 1.6.3
    typescript: ^4.7.4 => 4.9.3

Yep, Select/Popover don't work native yet they need breakpoints. Popover isn't a native concept really, and Select likewise is totally different on each platform typically. Plan is to add native prop to both eventually though with something that renders a bit closer.

Added warning here 6390b1e87
We'll eventually make it work as a sheet always on native, and then eventually could have a native prop to adapt to native sheet implementation.


Match catch-all operator

The chapter about match catch-all operator is not so clear as it talks about enums and felt252 while it is only supported for felt252 in Cairo 2.4.
As match will be strongly improved in Cairo 2.5 according to the roadmap, I think it would be better to just mention how it works for felt252 for the moment, and then deeply update this chapter for Cairo 2.5.
As I'm a Cairo newbie, I may have missed some information about match and so this PR may be not fully correct.

This change is

can you cd into no_listing_06_match_zero and run scarb fmt ?

This is perfect 💯 thank you for the initiative, feel free to add improvements in any section you feel that should be improved!

ok, thanks ! Yes, if I see something not easy to understand, I will do a PR ;-)
And thanks for the rewards on OnlyDust ❤


compute environment for gpu

I used the module (v0.5.0 and master) to deploy the infrastructure (thanks for this great module!). But my impression is that currently I cannot use @batch(gpu=1) for a step. The corresponding task gets stuck in runnable. Metaflow instantiates a p2-instance if i request it but the tasks with @batch(gpu=1) never leaves the state runnable. (Note that when i terminate that task manually, then other "pure cpu-tasks", i.e. not decorated with @batch(gpu=1), get executed on that p2-instance)
My best guess so far is that the terraform module simply does not create a gpu compute environment. There is a very old commit 91a8f26 in this repo but the gpu related parts disappeared two commits later and now only one cpu-ami and cpu-compute-environment is created.
Are there any plans to integrate gpu compute environments back into the module? Or is there an obvious way to enable gpu compute environment i missed?

Changing "/aws/service/ecs/optimized-ami/amazon-linux-2/recommended" in modules/computation/data.tf to "/aws/service/ecs/optimized-ami/amazon-linux-2/gpu/recommended" works, i.e. a p2-instance is started, torch.cuda.device_count() returns 1 and nvidia-smi also returns the expected output.
I have no idea what the full implications of this change is. At least regular dummy-cpu-tasks are executed on c4-instance. On the surface, it looks like it serves the purpose for my personal use.
However, my gut feeling tells me that this is a bad solution :-)

Just did another experiment by replacing the image in the batch-decorator with "763104351884.dkr.ecr.us-east-1.amazonaws.com/pytorch-training:1.6.0-gpu-py36-cu101-ubuntu16.04" and now the tensor can be placed on the gpu:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla K80           Off  | 00000000:00:1E.0 Off |                    0 |
| N/A   30C    P0    72W / 149W |      3MiB / 11441MiB |     54%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+
tensor([[0.7153, 0.1191, 0.5467],
        [0.8921, 0.7313, 0.6024]])
tensor([[0.8088, 0.7170, 0.1789],
        [0.7452, 0.6927, 0.6914]], device='cuda:0')

Any idea why it is working now? What I find  confusing is that the output of nvidia-smi states cuda-version 11.4 and not 10.1?!?
(BTW: Also just to double check I use the image that I used yesterday, I again see the error.)

Good call, let me try to reproduce. I think we may even be able to omit image_id there and let Batch choose the right one. In the meantime, if you haven't yet, feel free to open a thread in our slack http://slack.outerbounds.co/ . I know for sure there are at least a few folks using Metaflow with GPUs on Batch.

More findings:

Re: image id, just omitting it works https://github.com/outerbounds/terraform-aws-metaflow/pull/30 . I'll merge this after a bit more testing
CUDA version: it seems like its expected and nvidia-smi would report the version of the CUDA runtime from the host. The documentation on this is a little confusing, see this StackOverflow answer.
The exact combination of AMI and docker image you tried and got a CUDA error works fine for me with p3 instances, I can create tensors on CUDA device. So I'm suspecting its some kind of bug with CUDA either baked in the docker image or the host. May be worth contacting AWS support for that. Some comments on SO seem to suggest that it is safe(r) to use an older CUDA toolkit with a newer (host) runtime, but the official doc seems to imply that it should be fine either way with CUDA 11.x

Great! Please let us know if you run into anything else, I'm going to close this one for now


Transactions across models

Whilst methods like bulkCreate allow multiple items of the same model to be created in one transaction, a really useful feature would be to perform CRUD actions against multiple items of different models.
E.g. Upsert a user account & create a new session in a single transaction.
const users = dynazord.createModel({
  tableName: 'dynazord-example-users',
  keySchema: {
    hash: 'email',
  },
  properties: {
    email: {
      type: String,
      required: true,
      validate: {
        notNull: true,
        notEmpty: true,
      },
    },
    name: {
      type: String,
      required: true,
      validate: {
        notNull: true,
        notEmpty: true,
      },
    },
  },
  options: {
    createdAtTimestamp: true,
    updatedAtTimestamp: true,
  },
});

const sessions = dynazord.createModel({
  tableName: 'dynazord-example-sessions',
  keySchema: {
    hash: 'email',
    range: 'accessToken',
  },
  properties: {
    email: {
      type: String,
      required: true,
      validate: {
        notNull: true,
        notEmpty: true,
      },
    },
    accessToken: {
      type: String,
      required: true,
      default: () => uuid(),
      validate: {
        notNull: true,
        notEmpty: true,
      },
    },
  },
  options: {
    createdAtTimestamp: true,
    updatedAtTimestamp: true,
  },
});

const [ user, session ] = await dynazord.transaction([
  users.transaction.upsert({ email: 'jdrydn.github.io', name: 'James' }),
  sessions.transaction.create({ email: 'jdrydn.github.io' }),
]);
console.log({ user, session });
// { user: { email<EMAIL_ADDRESS>... },
//   session: { email<EMAIL_ADDRESS>accessToken: "...", ... } }

First look with https://github.com/jdrydn/dynazord/commit/5c93f39c865eaa1d6befdc24d550307729ab3aef however since each model could have it's own DynamoDB instance how the hell do you handle transactions across multiple DynamoDB clients? Answer, you can't!

First look with https://github.com/jdrydn/dynazord/commit/5c93f39c865eaa1d6befdc24d550307729ab3aef however since each model could have it's own DynamoDB instance how the hell do you handle transactions across multiple DynamoDB clients? Answer, you can't!

Finished in #5

Finished in #5


screenshots

Patterns found in testing, resulting from vertex accuracy or geometry updates.

Reconsidered approach, fixed development bugs, and improved code quality.

iterations (1-10)

views (1-3)

cubemap 1

cubemap 2

normal raycast on torus


Fix Travis config to test against legacy PHP 5.3 again

Just noticed that legacy PHP 5.3 does not show up in the Travis build log any more while working on #161. I'm not suggesting this is a particularly important version, but then again fixing this was somewhat trivial. Apparently, this was caused by a duplicate YAML definition in #130 (yey).

I've just updated this to fix the test case failing on PHP 5.3 only introduced via #146 :shipit:


Add driver for the port expander PCAL6416A

Generalizes the driver for PCAL6408A and implements a driver for PCAL6416A.

I was only able to test these changes with a PCAL6416A. Unfortunately, I do not have a PCAL6408A available.

@henrikbrixandersen @cfriedt Looks like @mnkp hasn't been too active in the past few months, maybe one of you could take care of this pull request?

@benediktibk - I would say much of my comments from #54433 apply here as well. Thanks for all of your work though - I think you may be breaking some ground, which is much appreciated.

@cfriedt Okidoki, I will put this PR back into a draft state and focus on the other PR first. Probably more efficient to work on for both of us.

Correct me if I'm wrong, but the pcal1608a and pcal6416a differ only in the number of pins and the register layout.
It would be ideal if it has some internal ID register to identify which part it is, but barring that, it might be better to provide a DT binding that enumerates which part it is - e.g. 0 = pcal1608a, 1 = pcal6416a.

You are absolutely correct, only the number of pins and the registers are different. But personally I would consider it to be confusing to differ between two different chips in the device tree via another magic property instead of the type via

Device tree properties aren't really magic. I mean, you can simply call it whatever you like - even an integer like max_gpios.

Another approach I could think of would be using the same binding, but detecting the difference for the driver via different values for ngpios.

The issue is that ngpios is not linked to the number of pins supported by a particular GPIO controller, but it is linked to the number of pins physically used in a board implementation. It's actually in the description of the devicetree binding for gpio-controller.

But still, my preferred method, as possible user of this driver and binding, would be two different bindings. I could still extract the similar stuff into a base pcal64xxa binding and include it in the specific ones, just to get rid of some redundancy.

Personally, I feel that adds a bit of unnecessary bloat - why have two separate drivers for the same chip family? The drivers themselves are practically identical.

I applied now all the requested changes, except for the binding related stuff. There I tried to reduce the bloat via including the base binding in the driver specific ones. I still think having two different bindings is less confusing for the user, which has to write the device tree for a specific board design. Would this be acceptable for you?

I applied now all the requested changes, except for the binding related stuff. There I tried to reduce the bloat via including the base binding in the driver specific ones. I still think having two different bindings is less confusing for the user, which has to write the device tree for a specific board design. Would this be acceptable for you?

Two separate bindings is good. That would make it backwards-compatible for whatever boards are using the existing nxp,pcal6408a bindings.

Two separate bindings is good. That would make it backwards-compatible for whatever boards are using the existing nxp,pcal6408a bindings. That should be fair enough to keep for the future too.

Totally forgot about the backwards compatibility, nice catch.


Feat: include security context

This pull request allows adding security context to both pod and containers in all the deployments/statefulsets.
@matrixji @klesh @IronCore864 Kindly take a look :)

Local tests to make sure all the images work fine with the security context:

@JorgeGar Thanks for your contribution! ❤

I think we should add more context in the values file's comments or in the HelmSetup.md to explicitly state that if security context is used, uid/fsgroup must be 101 (and the reasons behind it) so that users won't waste time debugging if they set another value for them.

Completely agree. Maybe in the HelmSetup.md?


Tests for SimpleConsumer.reset_offsets

This adds tests for reset_offsets (which I'm also looking to use to ensure the implementation of reset_offsets in #176 will be conformant), and fixes some issues with that method which I encountered in the course of writing tests.

@emmett9001 I ran into an issue that came in with 4cbe0a1 (see commit message of 50561ee for details), and have put in an alternative fix here with 3cea51c, and some more changes in 3e76c15. I'd be grateful if you can check on those two commits in particular, because reset_offsets logic is just so complex, so there's a real chance I'm missing the point.

The tests look great, and as far as I can tell the important invariants of reset_offsets are maintained. The code is also cleaner, which is good. It would be great if you could explain a bit more what issue commit https://github.com/Parsely/pykafka/commit/50561eeb793f0a72edfe41c71f80e457f30020ab is meant to solve, since I don't fully understand it. I'll also let @kbourgoin weigh in if he's interested.

Thanks for checking this! So 50561ee is the result of a git revert 4cbe0a1 - which was needed because the latter's owned_partition_offsets = {} caused an error, when this line tried to access it after it got emptied: https://github.com/Parsely/pykafka/blob/feature/test_reset_offsets/pykafka/simpleconsumer.py#L464
I then tried to do the same thing with 3cea51c, but wanted to check with you that that really does all the things it should do.

I'm afraid I've one or two more commits coming up, because the last test is now so strict that there's no good way for RdKafkaSimpleConsumer to satisfy it :)
(The difference in behaviour is, that when you hand SimpleConsumer an invalid offset, it almost immediately detects that, through the fetcher thread, and so a split second afterwards you've already got an auto-resetted valid offset. Whereas in RdKafkaSimpleConsumer, the held offsets only get updated once you've consumed from that partition, so it takes until after a consume() before the valid offset appears.)

Thanks for the explanation, the error case makes sense now.

Ok, apologies for slapping on more commits, I missed some problems jumping back and forth between this branch and the rdkafka branch. Should now be really actually totally ready.
The additional changes affect OwnedPartition.flush and test_reset_offsets (in particular, the part where it tries invalid offsets).


Version of slam on anaconda

( following some discussion with @gauzias )
I am running the packaging of your package macapype, because of the newly added dependancy of the package to slam:
https://github.com/Macatools/macapype/blob/master/macapype-conda/macapype/meta.yaml
so I have seen some solutions with recompiling from the .whl file (~the files created from pip install) but it would be easier if the brain-slam is also packaged on anaconda.
Do not hesitate if you need my help on that !

Thank you very much @davidmeunier79  for your suggestion and help. Indeed we plan to implement conda installation in a near future. I ll let you know as soon as I have visibility on this

Thank you very much @davidmeunier79  for your suggestion and help. Indeed we plan to implement conda installation in a near future. I ll let you know as soon as I have visibility on this


Color Order In GetPalette

only on Xamarin.forms nuget package:
//var pal = _colorThief.GetPalette(pictureBoxSpectrum.Image, 6, 10, false).ToList();
all the colors are correct, but Red and Blue color Bytes are swapped.
I was porting an app from windows forms app to Xamarin iOS, and noticed that all the colors are not the same, after some investigation turns out only instead of using RGB of your values, used them as BGR.

Hi, thx for you issue!
It's only for iOS?

I have tested the Windows Forms Application version and I couldn't find the same problem, my issue was only faced using Xamarin forms iOS, didn't test any other platforms, its only a matter of bytes ordering, I've confirmed the problem by testing 3 images each filled with a major single color, result is red is swapped with blue, temporarily fixed by using .R as the blue byte, . .B as the red byte.
Again.. i gotta say .. great work .. and thanks for your efforts.
Sent from my iPhone
On Jun 28, 2017, at 9:27 PM, ksemenenko <notifications<EMAIL_ADDRESS>wrote:
Hi, thx for you issue!
It's only for iOS?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/KSemenenko/ColorThief/issues/6#issuecomment-311746446, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOHydJBc-_RZaY5H7CdOsMxI6cDeeZFDks5sIpr6gaJpZM4OIU2e.

Hi @Houri93 please check it on version <IP_ADDRESS>

hello again, just updated to the latest version via nuget, the problem still exists as it has been previously

@Houri93 Thank you. I will then continue to fix this.

Hello! You could give me a picture and colors that should be the result?
@Houri93

yes .. have a look here, also sorry for being late .. and here's the code im extracting the colors with .. all thanks to you ofcourse ..
` var pal = _colorThief.GetPalette(AlbumArtImage.Image, 10, 10, false).ToList().OrderByDescending(a => a.Population).ToList();
this.View.BackgroundColor = UIColor.FromRGBA(pal.First().Color.B, pal.First().Color.G, pal.First().Color.R, pal.First().Color.A);
        UIColor newtint = null;
        for (int i = 1; i < pal.Count; i++)
        {
            var huediff = Math.Abs(pal.First().Color.ToHsl().H - pal[i].Color.ToHsl().H);
            var lightdiff = Math.Abs(pal.First().Color.ToHsl().L - pal[i].Color.ToHsl().L);
            var satDiffer = Math.Abs(pal.First().Color.ToHsl().S - pal[i].Color.ToHsl().S);
            if (huediff * (100 / 360.0) > 5 ||
                lightdiff * 100 > 5
               || satDiffer == 0)
            {

                newtint = UIColor.FromRGBA(pal[i].Color.B, pal[i].Color.G, pal[i].Color.R, pal[i].Color.A);

                break;
            }
        }

        waveformL = new CGColor((nfloat)(pal[1].Color.B / 255.0), (nfloat)(pal[1].Color.G / 255.0), (nfloat)(pal[1].Color.R / 255.0));
        waveformR = new CGColor((nfloat)(pal[2].Color.B / 255.0), (nfloat)(pal[2].Color.G / 255.0), (nfloat)(pal[2].Color.R / 255.0));

        if (newtint != null)
        {
            this.timeLB.TextColor =
              this.titleLB1.TextColor =
              this.titleLB2.TextColor =
              this.View.TintColor =
              this.loading.Color =
                      newtint;

            if (pal.First().IsDark)
            {
                UIApplication.SharedApplication.SetStatusBarStyle(UIStatusBarStyle.LightContent, true);

            }
            else
            {
                UIApplication.SharedApplication.SetStatusBarStyle(UIStatusBarStyle.Default, true);
            }
        }`


CLOUD-42308 it fix

@schfeca75

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1714/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1715/


[Bug]: Invalid error reporting when git-pull fails

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When git-pull fails due to some unknown reason server is not reverting with the correct error please check the screenshot for ref. This is originating from the import flow as we are using this under the hood.
https://github.com/appsmithorg/appsmith/blob/c7fc7cf7a9cf345d4f7e3b9053cc50e0d3f3528b/app/server/appsmith-server/src/main/java/com/appsmith/server/solutions/ce/ImportExportApplicationServiceCEImpl.java#L1227

Steps To Reproduce
This is not easily reproducible as there might be some edge case that is causing import flow to result in an erroneous state. But we have seen this happening with different users.
https://app.frontapp.com/open/msg_1fmff26k?key=https://app.frontapp.com/open/cnv_s8tpln0?key=MVxr9a-AGjSoqs2WnZP6YgWqDda09yqM
https://community.appsmith.com/t/an-error-404-page-not-found-appeared-while-trying-to-connect-a-new-branch-in-the-github-repository/1794/3?u=abhvsn
Public Sample App
No response
Issue video log
No response
Version
Cloud: v1.8.14
 Front conversations

Failed to reproduce this. However, improved the following logs so that debugging is easier:

When a plugin in missing, added the name of the plugin to the error message as well as in the error log.
When plugin is missing, the list of available plugins are printed in the error log.

Closing as per above comment.


Issue with NPM install

To notify you as you request; I attempted a few of the commands from your readme but they didn't work. And have tried restarting:
Skipping 0.x cruft clean
npm ERR! Error: EPERM, operation not permitted '/usr/local/bin/npm'
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR!
npm ERR! System Darwin 10.8.0
npm ERR! command "/usr/local/bin/node" "/private/var/folders/xr/xrA5zUMXHS843Uptf6LQPU+++TM/-Tmp-/npm.582/package/cli.js" "rm" "npm" "-gf"
npm ERR! cwd /private/var/folders/xr/xrA5zUMXHS843Uptf6LQPU+++TM/-Tmp-/npm.582/package
npm ERR! node -v v0.6.10
npm ERR! npm -v 1.1.1
npm ERR! path /usr/local/bin/npm
npm ERR! code EPERM
npm ERR! message EPERM, operation not permitted '/usr/local/bin/npm'
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /private/var/folders/xr/xrA5zUMXHS843Uptf6LQPU+++TM/-Tmp-/npm.582/package/npm-debug.log
npm not ok
npm ERR! error installing<EMAIL_ADDRESS>npm ERR! error rolling back<EMAIL_ADDRESS>Error: EPERM, operation not permitted '/usr/local/bin/npm'
npm ERR! Error: EPERM, operation not permitted '/usr/local/bin/npm'
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR!
npm ERR! System Darwin 10.8.0
npm ERR! command "/usr/local/bin/node" "/private/var/folders/xr/xrA5zUMXHS843Uptf6LQPU+++TM/-Tmp-/npm.582/package/cli.js" "install" "-gf"
npm ERR! cwd /private/var/folders/xr/xrA5zUMXHS843Uptf6LQPU+++TM/-Tmp-/npm.582/package
npm ERR! node -v v0.6.10
npm ERR! npm -v 1.1.1
npm ERR! path /usr/local/bin/npm
npm ERR! code EPERM
npm ERR! message EPERM, operation not permitted '/usr/local/bin/npm'
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /private/var/folders/xr/xrA5zUMXHS843Uptf6LQPU+++TM/-Tmp-/npm.582/package/npm-debug.log
npm not ok

Getting an EPERM there is interesting.  Is /usr/local/bin read-only or something?  Are you running it as root?

Hi Isaac - yes, I tried it running as sudo and no fix. I ended up uninstalling the node.js framework that I had downloaded from their site as a pkg, and instead following a sequence of commands (which came up in Google):
https://gist.github.com/791890
Then I had to move changes from bashrc to bash profile
It works fine now. Thanks for coming back -)
On 9 Feb 2012, at 17:28, Isaac Z. Schlueter wrote:

Getting an EPERM there is interesting.  Is /usr/local/bin read-only or something?  Are you running it as root?

Reply to this email directly or view it on GitHub:
https://github.com/isaacs/npm/issues/2140#issuecomment-3891575

I just ran into this error on Mac OSX, it turns out that npm is included with the node .pkg now - so trying to install npm via the curl was failing with this error. Type npm into terminal, you probably already have it installed.

I resolved this issue by simply changing curl http://npmjs.org/install.sh | sh to sudo curl http://npmjs.org/install.sh | sudo sh


Per-request proxy configuration

One of my projects uses a couple of API client gems which are developed on top of rest-client. Everything worked great (thank you btw :-) until I needed to set a proxy for the calls going to one API but not to the others.
Since the proxy is configured via the global setting RestClient.proxy, I figured it would be nice to be able to set the proxy for a specific RestClient::Request (or bypass the globally configured proxy if necessary).
That way, I wouldn't need to resort to "dirty" tricks like this:
old_proxy = RestClient.proxy

begin
  # Change or bypass proxy
  RestClient.proxy = new_proxy

  # Do work
ensure
  RestClient.proxy = old_proxy
end

I added test cases for the new parameter and updated the README accordingly.

+1 for this


Add Inventory::hash() method

I'm not positive we won't ever had inv items that are not sha256d::Hash, though. I would expect them to stay like that, but we never know.
Would accept that as a reasonable objection against this helper.

Well, tbh before the Inventory refactor, the type was simply a tuple of (InvType, sha256d::Hash) which I think it's also kinda how it's represented in Core. (Even though Core has uint256..)

What if we compromised and just called the method network_hash(), which would no longer use the hash name which tends to collide in Rust, and maybe hints to the user that this is a weird sort of "hash" which might be all zeros?

Addressed comments and rebased.

If we're returning an Option anyway would it make sense to return an actual hash type rather than a [u8; 32] array?
Alternately, since this is an object that users expect might be represented as all-zeroes, would it make sense to return a [u8;32] that might be all zeroes rather than an Option?
I'd be fine either way.

If we're returning an Option anyway would it make sense to return an actual hash type rather than a [u8; 32] array?

I think not because there is no guarantee that we won't have inventory items in the future that use different hashes. Like single sha256 instead of double.

Alternately, since this is an object that users expect might be represented as all-zeroes, would it make sense to return a [u8;32] that might be all zeroes rather than an Option?
I'd be fine either way.

Hmm, not sure what users expect here. Tbh if you want all zeroes in the Error variant, you can simply do unwrap_or_default. Maybe I could document that it only returns None for the Error variant, but I would expect that to be trivial..

Yeah I don't think a newtype makes much sense. Protocol-level it could mean anything. I would be something like InventoryItemInner which is kinda silly.


#42 Element not found and Element found handling restructuring

New Syntax

You can now decide to use the old syntax or new style by using the flag parameter use_exceptions.
This is by default ${TRUE} to avoid this breaks for checkups if a ui element is displaying delayed.

# This throws a flaui exception and stop test exeuction
Element Should Exist      /WRONG/XPATH
Element Should Not Exist  /VALID_XPATH

# Usage with Wait Until Keyword Succeeds
Wait Until Keyword Succeeds  Element Should Exist      /VALID_XPATH
Wait Until Keyword Succeeds  Element Should Not Exist  /VALID_XPATH

# If you want to check the return value by your own syntax.
# Wait Until Keyword Succeeds will not work anymore because this keyword will always Return True or False now
${RESULT}  Element Should Exist  /VALID_XPATH  ${FALSE}
${RESULT}  Element Should Not Exist  /WRONG/XPATH  ${FALSE}


Clean and refactor code

As a programmer
I want to have clean and simple code
Requirements:

[ ] 1. Use ClipPath to create shapes in views

Resources:

ClipPath: https://www.youtube.com/watch?v=xuatM4pZkNk


macOS Catalina

Dear @jcarpent,
Thanks a lot for the homebrew formula.
But when trying on a mbp using Catalina I got the following error:
==> Downloading https://homebrew.bintray.com/bottles-science/cddlib-094h.sierra.bottle.tar.gz
##O=#  #
curl: (22) The requested URL returned error: 404 Not Found
Error: Failed to download resource "cddlib"
Download failed: https://homebrew.bintray.com/bottles-science/cddlib-094h.sierra.bottle.tar.gz

It seems that the reference to cddlib is wrong. The problem may come from the fact that homebrew-science seems to be deprecated. It is indicated in the GitHub repository that most of the formula have migrated to homebrew-core but I did not find cddlib in this repository.
Is the formula in homebrew gepetto still supported ?
Thanks a lot for your time.

Yes, it is still supported. Homebrew is evolving very rapidly, making hard to track it.
I will reintegrate the cddlib inside homebrew-gepetto.
One other way to get Pinocchio working on OSX, is to rely on Conda, which very well done ;)

Dear Justin, I fixed my problem by compiling from source:
brew install cddlib ---build-from-source


test suite on windows?

hi,
we've been trying with @massich to  migrate our build system to the matio conda packages for the OpenMEEG project.
So far we build everything from source using CMake external project mechanism but it makes our CI really slow and makes us maintain a lot of code. Also we would like to make soon a conda package based on the matio one.
while we thought we were almost there as it was working on mac and linux, we hit test errors on windows that only appear when we allow support for matlab IO. So it's matio related. See CIs status at the bottom of : https://github.com/massich/findmkl_openmeeg/pull/32
before digging into this we wanted to know if tests were run on windows by appveyor or some continuous integration? if someone tells us that all tests pass on windows then it's a bug in our code:
https://github.com/massich/findmkl_openmeeg/blob/master/OpenMEEGMaths/include/MatlabIO.H
that is specific to windows....
could there be any compiler definition / option that we may have missed on windows?
thanks a lot for any feedback or hint.
thanks

I run the restsuite manually on my Win machine using MinGW (as it supports autotools). But it is not on Appveyor CI.
Sorry, I cannot see the error you ate pointi g to.

so the tests are not run using visual studio?
let's see if we can provide with @massich a small example to replicate the windows pb we observed using the windows conda package.

so the tests are not run using visual studio?
I do all the debugging and development on MSVC.
But you are right, before running the testsuite in MinGW I could replace the MinGW binaries by the MSVC binaries to check how it performs. Let's see.

another question: why is there no matio_test_cases_compressed_hdf_be.mat?

another question: why is there no matio_test_cases_compressed_hdf_be.mat?

Because I have no BE machine with MATLAB application. See #25.

Sorry, the compressed one is called matio_test_cases_hdf_be.mat and is there.

ok and this file corresponds to : matio_test_cases_uncompressed_hdf_le.mat
or matio_test_cases_compressed_hdf_le.mat in be mode?

File matio_test_cases_hdf_be.mat corresponds to matio_test_cases_compressed_hdf_le.mat in BE mode. Uncompressed HDF5 was first available with MATLAB R2017a. See #62.

ok thanks. Any success running the tests with visual studio binaries?

Any success running the tests with visual studio binaries?

Yes, 100% test success running the MSVC binaries through the testsuite in a Cygwin64 environment.
I noticed a small configuration improvement though, similar as c7805c970aa31625d25688905f727c0a5a22f901 and will fix the test for the diff command later on:
https://github.com/tbeu/matio/blob/5c2d85b68bf379fd179e7efdb8741a90f4ce17e2/test/testsuite.at#L55-L62

ok then we'll have to dig into it but for now just changing in our code
this line:
https://github.com/massich/findmkl_openmeeg/blob/master/OpenMEEGMaths/include/MatlabIO.H#L218
so it uses MAT_FT_DEFAULT and not MAT_FT_MAT73 makes our test suite pass
using the windows conda packages... is it possible that we may need to
change of usage of matio just changing this variable?
thanks a lot

is there the possibility to add .appveyor.yml running the tests so that we can inspect and make sure we replicate properly?
We have created a cmake project to build matio without touching a single line of matio's codebase. But we don't seem to be able to include the testsuit without breaking the CI. (see this PR)

I exported the appveyor.yml from https://ci.appveyor.com/project/tbeu/matio/settings/yaml:
appveyor.zip

it says: Project not found or access denied.

I know. But I attached the exported config.

I see. If you upload this .appveyor.yml to my fork and do test: on won't work because you are testing using Cygwin64 in your local machine and to export the tests to MSVC is not feasible.

Alexandre and Joan, I'm working to integrate our OpenMEEG/matio cmake "fork" into the main matio repo. The new testsuite (when fully operational, which is not yet the case) will be able to run on windows. I hope to have a fully working prototype soon.
@tbeu: I'm working on the testsuite to complete the work. This is also why I did (and still polishing)  the autoconf simplifications (my newest branch), to make this a little bit easier.... So in the end, no codebase change will not totally be true. But minimal code base change (and common codebase for autoconf and cmake versions) is true.

If you upload this .appveyor.yml to my fork and do test: on won't work because you are testing using Cygwin64 in your local machine and to export the tests to MSVC is not feasible.

True. This was only a local test I run for you after you asked for it. It is not part of any CI.

is there the possibility to add .appveyor.yml running the tests so that we can inspect and make sure we replicate properly?

Check 7560022e33a43354192b5b3d836d9e405a86a0e2.

thanks. So you are testing the 32bits version.

Yes. Neither I succeeded in running the 64-bit build nor the MinGW build. Sorry for that. If you are luckier than me I would be glad to update.

The cmake branch will probably help here.... Some more patience is needed as I have some personal problems right now. Give some more weeks to polish things up......

Sure let's make it happen! I'm OOO, but this just got on the top of my
todolist
On Tue, Apr 17, 2018, 22:20 Alexandre Gramfort<EMAIL_ADDRESS>wrote:

@massich maybe you can help here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tbeu/matio/issues/84#issuecomment-382128979, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGt-44phF8q2lkM6vCAVTWMp9SFm9LL9ks5tpk6mgaJpZM4SlVNo
.

Yes. Neither I succeeded in running the 64-bit build nor the MinGW build. Sorry for that. If you are luckier than me I would be glad to update.

Finally, test suite on Windows is available for cygwin, cygwin64 and mingw-w64 by 809af56b150f73e9cad590b256979ff528ea6b21.


feat: add component name to overlay

To get the ball rolling on #4.
Also, modified colors a bit to match the current theme 💅

Looks good to me!


add linkify to detail text

Closes: https://github.com/hbarang/React-Cv-Template/issues/1

Seems great, thanks!


Multiple inheritance and code cleanup

Includes changes from https://github.com/EntityGraphQL/EntityGraphQL/pull/139/

Cleanup SchemaType to use an enum instead of lots of boolean type variables (controversial? i tried to not break any public api)
Allow types to inherit from multiple base classes/interfaces
Cleanup Interfaces api a bit - added a "AddAllBaseTypes, AddBaseType and AddBaseType(string)" which provides a lot more flexiblity (there were issues when a type was auto detected before you could add its base type)

Also updated docs