New monsoon sperber code in xCDAT

I am closing this PR as it is followed up by a cleaned new PR #1022.


vmap using in_axes doesn't handle named arguments

Passing keyword arguments to a function vectorized with jax.vmap(in_axes=..., out_axes=...) does not seem to work and results in an AssertionError.
For example:
import jax
import jax.numpy as jnp

def f(a, b, c):
    return (2*a, 3*b + c)

print(jax.vmap(f, in_axes=(0, 0, None), out_axes=0)(jnp.array([1, 2]), jnp.array([2, 4]), 0.5))  # works
# (DeviceArray([2, 4], dtype=int32), DeviceArray([ 6.5, 12.5], dtype=float32))

print(jax.vmap(f, in_axes=(0, 0, None), out_axes=0)(a=jnp.array([1, 2]), b=jnp.array([2, 4]), c=0.5))  # doesn't work

results in:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
    [... skipping hidden 1 frame]

~/miniconda3/envs/lcms/lib/python3.9/site-packages/jax/_src/tree_util.py in tree_map(f, tree, is_leaf, *rest)
    166   leaves, treedef = tree_flatten(tree, is_leaf)
--> 167   all_leaves = [leaves] + [treedef.flatten_up_to(r) for r in rest]
    168   return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))

~/miniconda3/envs/lcms/lib/python3.9/site-packages/jax/_src/tree_util.py in <listcomp>(.0)
    166   leaves, treedef = tree_flatten(tree, is_leaf)
--> 167   all_leaves = [leaves] + [treedef.flatten_up_to(r) for r in rest]
    168   return treedef.unflatten(f(*xs) for xs in zip(*all_leaves))

ValueError: Tuple arity mismatch: 0 != 3; tuple: ().

During handling of the above exception, another exception occurred:

AssertionError                            Traceback (most recent call last)
/tmp/ipykernel_218392/621472192.py in <module>
      8 # (DeviceArray([2, 4], dtype=int32), DeviceArray([ 6.5, 12.5], dtype=float32))
      9
---> 10 print(jax.vmap(f, in_axes=(0, 0, None), out_axes=0)(a=jnp.array([1, 2]), b=jnp.array([2, 4]), c=0.5))  # doesn't work

    [... skipping hidden 2 frame]

~/miniconda3/envs/lcms/lib/python3.9/site-packages/jax/api_util.py in flatten_axes(name, treedef, axis_tree, kws)
    274       # message only to be about the positional arguments
    275       treedef, leaf = treedef_children(treedef)
--> 276       assert treedef_is_leaf(leaf)
    277       axis_tree, _ = axis_tree
    278     raise ValueError(f"{name} specification must be a tree prefix of the "

AssertionError:

Version used: jax: 0.2.18

Please note that named arguments work when in_axes and out_axes are not needed and not used, as was fixed in https://github.com/google/jax/pull/5387 and closed in https://github.com/google/jax/issues/912.
E.g. The following works:
import jax
import jax.numpy as jnp

def f(a, b):
    return (2*a, 3*b)

print(jax.vmap(f)(jnp.array([1, 2]), jnp.array([2, 4])))
print(jax.vmap(f)(a=jnp.array([1, 2]), b=jnp.array([2, 4])))

The issue seems to specifically related to the jax.vmap in_axes and out_axes arguments.

The bad thing here, IMHO, is not that keyword arguments are not supported. I can see that it would complicate the signature of vmap.
The problem is that it's just an assertion error which is hard to understand.

I was hit by this today. Can we have an explicit error while the behavior is not fixed perhaps?

Got the same problem today. The empty error message makes it very difficult to understand, by chance I had a snippet that did not contain named arguments so I could compare my code, otherwise it would have been very difficult.

Are there any plans on adding support for named arguments for vmap when using in_axes and/or out_axes? Right now, in one way or another, I have to use a unideal (or hacky) solution to overcome this limitation:
import jax
import jax.numpy as jnp

def foo(x, w, b):
    return jnp.vdot(x, w) + b

foo_vmap = jax.vmap(foo, (0, None, None), 0)

X = jnp.arange(5 * 3).reshape(3, 5)
parameters = {"w": jnp.arange(5), "b": 1}

# this breaks!!!
foo_vmap(X, **parameters)

# works, but clutters the code especially when many parameters are involved, it
# really defeats the purpose of using dictionaries in the first place
foo_vmap(X, parameters["w"], parameters["b"])

# works, but adds another layer of higher level function transformations, that makes
# it harder to understand the code from first glance
import functools
foo_vmap_partial = jax.vmap(functools.partial(foo, **parameters), (0), 0)
foo_vmap_partial(X)

# works, but we need to recreate the function signature each time we use vmap adding
# extra bloat
foo_vmap_lambda = lambda x, w, b: foo_vmap(x, w, b)
print(foo_vmap_lambda(X, **parameters))

Definitely agree. I sometimes wrap jax.vmap with something like this:
def named_vmap(f, axes_names, **kwargs):

    in_axes = ({k:0 if k in axes_names else None for k in kwargs.keys()},)
    return jax.vmap(lambda input_dict: f(**input_dict), in_axes=in_axes)(kwargs)

This one doesn't work with nested dicts (though it should be straightforward to extend it). Would be nice to have something like this as default behaviour!

I am joining in with another minimal example:
import jax

def f(a, *, b):
    return a @ b

a = jnp.ones((2, 4))
b = jnp.ones((4, 2))

f_batched = jax.vmap(f, in_axes=(None, 0, None))
b_batched = jnp.ones((10, 4, 2))

print(f(a, b=b).shape)  # (2, 2)

print(f_batched(a, b=b).shape)  # AssertionError


Fixed Markdown in README.md and CONTRIBUTING.md

Two of the URLs in README.md are not encoded properly and the URLs in CONTRIBUTING.md have syntax errors. It was bothering me so I fixed it. The relevant issue is #11. No unit tests needed.
Edit: Misread the style guide the first time around, just submitted a commit to fix line lengths in CONTRIBUTING.md.

Hay , thanks for your work Grand Developer


Use redis as session and cache backend

Audit sorl.thumbnail use of redis
upgrade hyperbola01 to redis > 2.4

https://launchpad.net/~chris-lea/+archive/ubuntu/redis-server
https://docs.djangoproject.com/en/1.8/topics/cache/#using-a-custom-cache-backend
http://michal.karzynski.pl/blog/2013/07/14/using-redis-as-django-session-store-and-cache-backend/

[02:11|lopopolo|li246-117] [~]
▶ date
Fri Mar 18 02:11:57 EDT 2016
[02:11|lopopolo|li246-117] [~]
▶ redis-server --version
Redis server version 2.2.12 (00000000:0)

48a292c just removed redis as a dependency. In memory caching is enough, and if it isn't, use memcached as it is natively supported by django.

reopening this. redis seems to be preferred to mysql for fresh deployments.

http://niwinz.github.io/django-redis/latest/#_configure_as_cache_backend

deployed


Box2D (R.U.B.E) scene loader

This is the first version but it works already pretty well.
There are a few things missing but they can be implemented in a following change

Pull Request Test Coverage Report for Build 68

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

Totals

Change from base Build 66:
0.0%

Covered Lines:
166

Relevant Lines:
554

💛  - Coveralls


Loading Annotations

Hi Maria,
Thank you so much for this tool!!
I just wanted to let you know that while the tutorial says the annotation file should be in CSV format, I could not get a comma separated file to load correctly. However, when I switched to a 'tab' delimited BED file, it worked.

Hi! Sorry for neglecting these issues. Do you have a small sample of the CSV file that didn't work? Then I can try to debug it. Thanks :)
Note that I left DNAnexus, and this repo will be archived soon, so I have created a fork and will attempt to maintain Dot over at https://github.com/MariaNattestad/dot. Please allow some time for me to triage the issues, but otherwise feel free to bug me with the same or new issues over there.


Not working on Android phone

What happens?
shell.duckdb.org shows a black screen on my Pixel 6a phone, and keyboard input doesn't do anything.

To Reproduce
Visit shell.duckdb.org
Browser/Environment:
Chrome 124.0.6367
Device:
Pixel 6a
DuckDB-Wasm Version:
Not clear
DuckDB-Wasm Deployment:
shell.duckdb.org
Full Name:
Soeren Wolfers
Affiliation:
G-Research

bump. still an issue


testing: benchmark timeout when benchtime set too long

What version of Go are you using (go version)?

go1.15

Does this issue reproduce with the latest release?
yes
What did you do?
When benchmark function execute time is very short, set benchtime=5s / 10s / 20s is ok.
BenchmarkNewObject-2<PHONE_NUMBER>               0.279 ns/op

But set benchtime=120s will execute time out.
*** Test killed with quit: ran too long (11m0s).

What did you expect to see?
Do not timeout
What did you see instead?
*** Test killed with quit: ran too long (11m0s).

Duplicate of #12446

Duplicate of #12446

Not the same,  see #49974,  int64 overflow, may be a bug

I agree that this might not be a duplicate - the code doesn't seem to be safe against overflows.
That said, the fix doesn't seem complete. Not all overflows will result in negative numbers.

I agree that this might not be a duplicate - the code doesn't seem to be safe against overflows.
That said, the fix doesn't seem complete. Not all overflows will result in negative numbers.

Sorry, Is there any other cases?

https://go.dev/play/p/MBFpdZOOSgx
That example also has some better overflow detection that you can enable and try for yourself.
Note that there are multiple operations involved in testing/benchmark.go, including multiplications and additions. Proper overflow checking won't be as trivial as in my example.

Also, a fix would need to come with a test :)

Also, a fix would need to come with a test :)

Done, see new PR #50023


[DRAFT] initial commit for big query extractor

Signed-off-by: SreeV<EMAIL_ADDRESS>

waiting for new sql parser.
exploring bigquery with old parser.


raster_uc.py sometimes raises TypeErrors with mis matching variable names

Description of the Feature to be Added

Very minor point, but some TypeErrors messages don't match with the variable name, e.g.:
https://github.com/datasciencecampus/transport-network-performance/blob/66663568efcd7aa7cd552f25f37c4c1302e6555d/src/transport_performance/urban_centres/raster_uc.py#L276-L280
Could be useful to revisit the type error and make sure they are consistent with the variable names to help user debugging.
This request relates to the review of PR #37.
Additionally, the variable name cell_fill_treshold should be changed to cell_fill_threshold to correct this typo (requires an update of the unit tests too). This was picked up as part of PR #104.

This issue also links with #94 and maybe able to close both issues in the same PR.


Modify all telnet reads to include a timeout. Propogate timeout setting.

Modify all telnet reads to include a timeout. Propogate a timeout setting from entrypoint sh file through juicebox udpc updater class to juicebox telnet class.

@j358  recommend catching the timeout exception explicitly for logging purposes,  around line 374

I have added explicit error catching in the latest commit.
In addition, I have added error handling to remote data handler and local data handler as I had one instance of an IndexError in local data handler that caused pyproxy to crash. Can split this out as seperate issue if need be.

{"log":"2024-03-30 02:54:00,643 INFO       UDPC IP correct\n","stream":"stderr","time":"2024-03-29T14:54:00.643980293Z"}
{"log":"Traceback (most recent call last):\n","stream":"stderr","time":"2024-03-29T14:54:25.723272044Z"}
{"log":"  File "/juicepassproxy/juicepassproxy.py", line 672, in \u003cmodule\u003e\n","stream":"stderr","time":"2024-03-29T14:54:25.723424153Z"}
{"log":"    main()\n","stream":"stderr","time":"2024-03-29T14:54:25.725247011Z"}
{"log":"  File "/juicepassproxy/juicepassproxy.py", line 664, in main\n","stream":"stderr","time":"2024-03-29T14:54:25.725429119Z"}
{"log":"    pyproxy.udp_proxy(src, dst)\n","stream":"stderr","time":"2024-03-29T14:54:25.727316977Z"}
{"log":"  File "/juicepassproxy/pyproxy/pyproxy.py", line 56, in udp_proxy\n","stream":"stderr","time":"2024-03-29T14:54:25.727719285Z"}
{"log":"    data = LOCAL_DATA_HANDLER(data)\n","stream":"stderr","time":"2024-03-29T14:54:25.729664419Z"}
{"log":"           ^^^^^^^^^^^^^^^^^^^^^^^^\n","stream":"stderr","time":"2024-03-29T14:54:25.730012357Z"}
{"log":"  File "/juicepassproxy/juicepassproxy.py", line 307, in local_data_handler\n","stream":"stderr","time":"2024-03-29T14:54:25.730095263Z"}
{"log":"    message = self.basic_message_try_parse(data)\n","stream":"stderr","time":"2024-03-29T14:54:25.73112632Z"}
{"log":"              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n","stream":"stderr","time":"2024-03-29T14:54:25.731655219Z"}
{"log":"  File "/juicepassproxy/juicepassproxy.py", line 228, in basic_message_try_parse\n","stream":"stderr","time":"2024-03-29T14:54:25.731737236Z"}
{"log":"    parts.pop(-1)  # Ending blank\n","stream":"stderr","time":"2024-03-29T14:54:25.73257537Z"}
{"log":"    ^^^^^^^^^^^^^\n","stream":"stderr","time":"2024-03-29T14:54:25.732853884Z"}
{"log":"IndexError: pop from empty list\n","stream":"stderr","time":"2024-03-29T14:54:25.732926531Z"}
{"log":"2024-03-30 02:54:30,960 INFO       UDPC IP correct\n","stream":"stderr","time":"2024-03-29T14:54:30.961300078Z"}

@snicker, this looks good to go to me.

UDPC_TIMEOUT and --udpc_timeout should also be added to the ReadMe.

Merging the PR so it can be tested using Docker edge tag. Will put into release if no issues reported in a few days.


minor grammar and readability revisions

I feel that the revisions provided in this PR make the README easier to follow.
Thanks,
James

Codecov Report

Merging #235 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #235   +/-   ##
=========================================
  Coverage     36.98%   36.98%
  Complexity       45       45
=========================================
  Files            39       39
  Lines           530      530
  Branches         27       27
=========================================
  Hits            196      196
  Misses          325      325
  Partials          9        9

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8626c5c...a9dd80a. Read the comment docs.

Looks great! Pardon my English :)

Artem, you are funny


Make PyPy wheels work

Make PyPy wheels work.

Fix PyPy 3.9 build by following SciPy's approach. oldest-supported-numpy only works for CPython. That same version is unsupported on PyPy. SciPy uses an unpinned numpy version on PyPy  so pip will download a working version.
Skip PyPy 3.10 because numpy does not support it.
PyPy 3.8 works by building numpy from source. Since it works, let it be.

Example Actions run (only PyPy enabled in this special run, with a hacked SS version hence why only macOS succeeds): https://github.com/alugowski/python-suitesparse-graphblas/actions/runs/6388091525/job/17337388925

FYI https://github.com/scipy/oldest-supported-numpy/pull/78 would make the first bullet point redundant and unnecessary.


[Enhancement] egeria-ui-components dist folder github Actions

Is there an existing issue for this?

[X] I have searched the existing issues

Please describe the new behavior that that will improve Egeria
egeria-ui-components build is created in the dist/ folder.
For the moment is pushed in the main branch with PR.
Create a github workflow that builds egeria-ui-components and publish the dist folder.
@planetf1 sugested to investigate:
Github packages also offer a repo - for containers, gems, npm, maven, gradle, nuget - not explored but all there.

not applicable anymore, dist is generated at publish time whenever a new version is merged into the main branch


let's remove the alert_*_o signals from the top file

in the cve2_top.sv there are alert_*_o signals unused at the interface

While at it, it would be also good to remove data_wdata_intg_o from top level interface - it's a signal that became dangling after removal of security features.


Avoid unnecessary loop while processing an ACK block

When processing an ack block, skip to the next PN in sentmap rather than incrementing PN one by one until the PN becomes the one in the sentmap.
This is an important optimization, as ACK frames being received will contain ranges that have been previously acked, until the peer receives an ack-ack.

Thank you for the review. I've applied most of your suggestions, leftovers are ones that are those still unresolved.
I've merged the PR, but please let me know if you have concerns.


Introduce admin and ban in group channel

In order to add the "ban" function in the group channel, the following rules have been added/adjusted:

an admin can add/remove members to/from the admin list
an admin can ban/unban members, the banned users cannot send msg to the channel
an admin can kick off members(except for other admin)
old group channels did not record admin list so every member could perform "kick-off", "ban/unban"
added APIs: "editAdmin", "admin", "editBanned", "banned"

Besides being unable to post messages, blocked members should not be able to see the messages of all other participants as well.

When it comes to ban/block in a group, I first think of twitch which just disable users to send message. Besides, ban in telegram also take this method by default(although we can set additional rights for viewing message). If we want to prevent banned users from viewing message, why not just "kick-off" them.

When it comes to ban/block in a group, I first think of "twitch" which just disable users to send message. Besides, ban in telegram also take this method by default(although we can set additional rights for viewing message). If we want to prevent banned users from viewing message, why not just "kick-off" them.

Totally agree with you! Sounds reasonable. We can just kick them off then. OK, let's leave it like it is now.
Just let me know when it's ready for review :)

@joejoe2 Is this PR ready?

No, I think the banned user shouldn't bound to member and cannot be invited/join again. This can prevent them from leaving and re-joining.

No, I think the banned user shouldn't bound to member and cannot be invited/join again. This can prevent them from leaving and re-joining.

Cool! Thanks or the clarification! Sounds reasonable.

No, I think the banned user shouldn't bound to member and cannot be invited/join again. This can prevent them from leaving and re-joining.

Cool! Thanks for the clarification! Sounds reasonable.

I will continue in next week(or weekend) because I have some interviews... Although it's different to find a job now.

Of course! It's not prod :)

@sergejsvisockis I'm back. You can review it first.

@sergejsvisockis I'm back. You can review it first.

@joejoe2 Helllooo! :) Glad to see you back! I hope you have found a new role. :)

@joejoe2 perhaps we can merge this


Quantum - Going into saved attachments and back to home does weird stuff

Seems to happen when you spam click nested folders, so nothing to do with saved attachments.


Income and expenditure chart in wallet page

Tasks

[ ] Chart of all, USDT, LIKE and HKD
[ ] Currency converter

References

Product doc
Design

Duplicate to https://github.com/thematters/matters-web/issues/2860


Choose parent page, radiobuttons overlap

Issue Summary
The 'Choose parent page' view is broken: The radio button labels overlap.
Current

Expected

Steps to Reproduce

In bakerydemo, create a new file blog/wagtail_hooks.py

from wagtail.contrib.modeladmin.options import ModelAdmin, modeladmin_register

from .models import BlogPage

class BlogAdmin(ModelAdmin):
    model = BlogPage

modeladmin_register(BlogAdmin)

Stop/start the server to pickup the hooks file.
You need multiple Blog index page items for the choose parent view to show.
Go to /admin/blog/blogpage/choose_parent/
The radio select alignment is broken.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: YES

Technical details

Python version: Python 3.9.9
Django version: 4.0.6
Wagtail version: 3.0.1
Browser version: latest Chrome, latest FireFox.

Workaround
I've created an app called adminfix the layout is:
├── adminfix
│   ├── __init__.py
│   ├── __pycache__
│   │   └── __init__.cpython-39.pyc
│   └── static
│       └── wagtailmodeladmin
│           └── css
│               └── choose_parent_page.css

It should come before wagtail in INSTALLED_APPS, so that choose_parent_page.css overrides Wagtails choose_parent_page.css.
The Wagtail contents of choose_parent_page.css file is:
#id_parent_page li { margin:15px 0 }
#id_parent_page li label{ float:none }

The override of choose_parent_page.css contains:
#id_parent_page div { margin:15px 0 }
#id_parent_page div label { float:none }

Thanks for reporting, @allcaps!
Looks like another instance of #8494 - I'm guessing this page doesn't use our standard form markup, so the CSS fixes there aren't picked up.

Do we want to fix the CSS like in the other issue? OR do we want to fix the HTML markup?
I'll submit a PR.

I’m already working on form styles for Wagtail 4 that will fix this. If you want to address it in a Wagtail 3, the CSS hack seems like a fair approach. Note the choose_parent_page.css has been removed in main, the corresponding styles are now in: https://github.com/wagtail/wagtail/blob/main/client/scss/layouts/_modeladmin-choose-parent-page.scss


pull request for e2e test at 01/09/2017 01:45:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Screen Grabber returns unexpected error message

When I click the "Save Screenshot" button on the Screen Grabber Panel generated by director.screengrabberpanel.ScreenGrabberPanel(view), the following error message appears.
Traceback (most recent call last):
  File "/home/vtjeng/director/build/install/lib/python2.7/dist-packages/director/screengrabberpanel.py", line 124, in onSaveScreenshot
    app.getMainWindow().statusBar().showMessage('Saved: ' + filename, 2000)
AttributeError: 'NoneType' object has no attribute 'statusBar'

This seems to be a reproducible error.

Thanks for the report.  I think it still saves screenshots, despite the error?

Yes, I can confirm that it still saves screenshots.

this has been fixed.


Renaming the bin-files

Hi
I am working on improving this package in guix. Right now it is packaged as is and pulls in gtk and a lot of crap.
We generally try to destinguish between cli and gui applications and when they differ a lot in size we create 2  packages. One with the gui: e.g. "octave" and one lightweight with only the cli "octave-cli".
Would you consider renaming your bin-files according to this?
youtube-viewer -> youtube-viewer-cli
gtk-youtube-viewer -> youtube-viewer

No.


train with augment

do I train the model with
python -m torch.distributed.launch --nproc_per_node=N_GPU --master_port=PORT train.py --batch BATCH_SIZE LMDB_PATH --augment

Hi @rosinality, after turning on --augment, I got the following error:
File "/home/zhule.zhl/miniconda3/envs/py37_torch160/lib/python3.7/site-packages/torch/nn/modules/container.py", line 117, in forward
input = module(input)
File "/home/zhule.zhl/miniconda3/envs/py37_torch160/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/mnt3/zhule.zhl/gitWorks/stylegan2-pytorch/op/fused_act.py", line 101, in forward
return fused_leaky_relu(input, self.bias, self.negative_slope, self.scale)
File "/mnt3/zhule.zhl/gitWorks/stylegan2-pytorch/op/fused_act.py", line 119, in fused_leaky_relu
return FusedLeakyReLUFunction.apply(input, bias, negative_slope, scale)
File "/mnt3/zhule.zhl/gitWorks/stylegan2-pytorch/op/fused_act.py", line 66, in forward
out = fused.fused_bias_act(input, bias, empty, 3, 0, negative_slope, scale)
RuntimeError: input must be contiguous
Do you know why it happened? I couldn't fix it.

@tearscoco I got the same error when training with augmentation

@tearscoco @ElektrischesSchaf It will be fixed with bb459e0.

@rosinality thank you, now it works perfectly
I also found that when training with --augmentation, this error appears
File "/workspace/gan-pytorch/stylegan2-pytorch-rosinality/non_leaking.py", line 316, in get_padding
pad = pad.max(torch.tensor([0, 0] * 2, device=device))
RuntimeError: Expected object of scalar type float but got scalar type long int for argument 'other'
whereas this trainingg without --augment does not have this error. I'm not sure it's because I'm feeding a custom dataset into the model or not.
My solution is add  dtype=torch.float32 in get_padding() from ````non_leaking.py```
pad = pad.max(torch.tensor([0, 0] * 2, device=device, dtype=torch.float32))
pad = pad.min(torch.tensor([width - 1, height - 1] * 2, device=device, dtype=torch.float32))

@ElektrischesSchaf You can fix this by changing into pad = pad.max(torch.tensor([0.0, 0.0] * 2, device=device))


Add a ListComprehender implementation

The cyclops-monad-api currently handles Collections by converting them into Streams, adding a specific Comprehender for Lists would mean less surprising behaviour when using AnyM wrapped Lists.
We should also make sure that Lists are no longer implicity or explicitly converted into Streams. This would mean updating appropriate AsAnyM methods, and also CollectionsConverter.

PR : https://github.com/aol/cyclops/pull/66


Fix: Remove accessor only used in test

This PR

[x] removes an accessor which is only used in a test

Follows #437.

Thanks @localheinz


Implement 2D instance shader parameters

Closes #62943
I wrote this a while ago and decided to rebase and test it again now. This seems to work the same as in 3D (no wonder, since it's a 1:1 copy-paste), i.e. the parameters appear in the inspector, they have correct default value etc.
The only problem is that changing the parameter has no effect. It always uses the default for the given type (not even the defined default). But it's probably the only missing bit, so if anyone can help, the feature would be finished.

Closing in favor of #87966
Maybe it will have better luck.


Local keys storage and Android

Does storing keys work with Android?
KeyStorageConfig.INSTANCE.getKeyFolderPath() is often used with requireNonNull which will fail for Android.
KeyStorage.deleteKeyFolder has a comment
// todo add android support

The Android part of the application won't be developed yet, this is postponed for the future version, hence this can be closed.


[PiranhaSwift] log error message when command fails to launch

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @atrakh for the fix. Can you please sign the CLA so that I can stamp this?

Sure thing, I just signed it. Thanks for the quick followup!
p.s. For posterity, the error I was getting was SwiftSyntax parser library isn't compatible and I had to do some digging to figure out that I needed Swift 5.1 to use piranha.
I used the instructions in this article to switch to swift 5.1: https://medium.com/xcblog/switching-swift-versions-inside-xcode-using-toolchains-755b28831c43

p.s. For posterity, the error I was getting was SwiftSyntax parser library isn't compatible and I had to do some digging to figure out that I needed Swift 5.1 to use piranha.

Indeed. Issue 68 is for upgrading PiranhaSwift to use 5.2. Haven't gotten to it yet.


"require rubygems" error on maven install

Hi,
I am trying to generate css files from sass files using "mvn install", but it fails with an error which says that it requires "rubygems". I tried sass-maven-plugin version 2.4, 2.6, and 2.12. Attached is the profile that I added to my pom.xml.
I couldn't find any good source to fix this issue. I really appreciate if someone can help me in this regard.
Thanks,
--
Shima

Please try again with a current version (2.12), run Maven with -X and post the full pom (definitely not a screen shot) and log file/output.
If you don't want to post those two here you can link to a gist that has those two files and you can delete those after this is resolved.
The plugin has all the necessary ruby gems included, your message does not make sense to me.

I got a similar (same) error, maybe this helps to debug: https://gist.github.com/Kuerten/31a22259afa6503e777a

Don't downgrade jruby, we stopped using jruby 1.7 with 2.9, also the downgrade mentioned in the FAQ is for a specific error that your trace/log does not display.
I will push a snapshot (2.13-SNAPSHOT) shortly so you can see if that helps

I don't have this issue today. The required plugins such as jruby are specified as sass-maven-plugin dependencies (right?), but they could not be downloaded to my maven local repository a few days ago. However, I tried to generate css files again today, and it worked fine. I can also see that the jruby plugin is downloaded in my local repository.
Thanks for your help.

OK,


Replace mocks with fakes wherever possible, remove Mockito

https://github.com/appifyhub/monolith/issues/182


aliases resolution is weird

I think I saw it happen a few times on my linux machine, but after merging #43, I can't seem to be able to reproduce :slightly_smiling_face:
I'm going to close this, but please reopen if you still have that bug.


Replace straight quotes with curly quotes

Automatically add quotes to a paragraph inside blockquotes. Using curly quotes (“”) instead of straight quotes ("").
Sans-serif (San Francisco):

instead of

Serif (Charter):

instead of

Thanks, but I'd rather keep the CSS free of anything that can be done as easily in HTML. I'll probably update the HTML file to use curly quotes though. Thanks for pointing this out!


Rebuild assembly on file change

It doesn't seem to do that right now. Learning this was unpleasant.

build.rs has a mean to tell cargo to do this, it can be probably implemented in nasm-rs, I'll get you something tomorrow.


Add explanation to cage struct and remove pendingsigset

Description
Fixes the issue we talked on Mon

Added explanation to cage struct and removed old RustPOSIX pendingsigset usage in RawPOSIX with @rennergade
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?

Checklist:

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] Any dependent changes have been added to a pull request and/or merged in other modules (native-client, lind-glibc, lind-project)

@JustinCappos reminder to take a look at this


fix problem

Your solution can not run some instance(like this: Jan 1 1900).And i
fixed it,please check it.Thank you.

Thx.

my code maybe has some problems,please check it,thx.


URI Link with '&' in the link won't recognized as uni link

I'm using [https scheme] and am testing
on my [Android Emulator],
which is running [Android 12].
my code is:
_sub = uriLinkStream.listen((Uri? deepLink) {
      if (deepLink != null) {
        log("has deplink when app running");
        _handleActionFromLink(deepLink);
      } else {
        log("no deplink when app running");
      }
    },

Then, try to invoke the link via adb:

adb shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d 'https://myweb.com/login' com.myweb => Redirected to app and run correctly
adb shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d 'https://myweb.com/login?token=xyz' com.myweb => Redirected to app and run correctly
adb shell am start -a android.intent.action.VIEW -c android.intent.category.BROWSABLE -d 'https://myweb.com/login?token=xyz&name=ee' com.myweb => REDIRECTED TO WEB

Is there any way to make it to redirected to app and run properly for case three like case one and two?

It is working. Please try to open that link from phone. Not from terminal.

Is there any way to get it to also work from the terminal?


this.props.fields.[field].onChange on v6

On the previous version I used
change = e => {
    this.props.fields.type.onChange(e)
    this.props.handleSubmit()
}

render() {
    return <input onChange={this.change}>
}

How should I trigger a field change and form submit at the same time? this.props.fields.type.onChange(e) on the new version?
I am working with wizard forms (multiple redux-forms with same form id) that need to go to next step when an option is selected, without submit button.

class MyForm extends Component {
  render() {
    const { handleSubmit } = this.props
    return (
      <div>
        <Field name="type" component={type =>
          <input {...type} onChange={e => {
            type.onChange(e)
            handleSubmit()
          }}/>
        }}>
      </div>
    )
  }
}

How's that?
Thank you for kicking the tires on v6.

Thanks to you!

And to get values from a "next step"?
I am using @connect:
@connect(state => ({ type: state.form.adWizard.values.type }))
@reduxForm({ form: 'adWizard' })

Previously I was getting the values from props: this.props.type

Yes, your code is correct. I'm considering exporting some selectors to make it easier.

Cool


Damping effect gone after calling ev.stopPropagation()

Checks

[X] Not a duplicate.

Version
8.8.1
Description
Just same as title.
I was trying to stop touch event bubbling， then I found If I use  ev.stopPropagation() , it will cause the scrollbar damping effect disappear.
Steps to Reproduce

create a  normal smooth-scrollbar-inited container
bind on touchend event on any element in the normal smooth-scrollbar-inited container.
in the event handler, call ev.stopPropagation()

Online Demo
No response

https://stackblitz.com/edit/vitejs-vite-natuuz?file=main.js

Please just fork it and explain with more details cause I can't reproduce it

@sadeghbarati
Sorry, I found I made a mistake, it's touchend event, not click.
If you need to check it with this stackblitz demo below, you will have to switch to mobile mode (developer tool).
you will find that the damping effect just gone after "touchend" event fire on that "stopPropagation" button.
https://stackblitz.com/edit/vitejs-vite-hglpla?file=main.js

My solution now is not to use ev.stoppropagation, but detect if the event.target  is descendant of  elements which I want to stop the event bubbling from.
But I think it's not a very good solution since it's not very intuitive, it will be nice if you guys could fix it 😭 .

you need to be cautious about using stopPropagation
just found a solution from https://github.com/idiotWu/smooth-scrollbar/issues/444
class SmoothTouchScrollPlugin extends ScrollbarPlugin {
  static pluginName = 'smoothTouchScroll';

  transformDelta(delta, fromEvent) {
    if (fromEvent.type === 'touchmove') {
      this.scrollbar.options.damping = 0.1;
    }

    return delta;
  }
}

https://stackblitz.com/edit/vitejs-vite-9e2btw?file=main.js


Captive portal: make captiveportal_disconnect_all() faster

captiveportal_disconnect_all() removes the users one at a time and in some cases, when many hundreds of users are connected, can take up to several dozens of seconds to complete.
Instead of looping through all users, send all the accounting information, reset the user database and delete all the active rules and reinit them. Use locking to prevent new users from logging in until the function ends.

I could only test a slightly different version of the patch on 2.3.2 (captiveportal_init_rules in 2.3 doesn't delete existing rules) but I'm fairly certain it should work as expected, even the locking part (tested adding a 60s delay before releasing the lock).


Fix "go get" support, once again

This fixes #144

Thanks for the quick patch @leonklingele. Before I merge and propagate to master, is there a particular reason you've export Version?


wget "403 Forbidden"; Colab: "Bad MIDI" every time

Alex,
Thank you for making this available.  However, I'm unable to get the either the wget command or the Colab to work.
$  wget 'https://1drv.ms/u/s!Ao9gnMkvUA2KgZBWDIQJIG-JS6RpPQ?e=ur8ggN' --no-check-certificate -O LAKH-MuseNet-MIDI-Dataset.zip "https://onedrive.live.com/download?cid=8A0D502FC99C608F&resid=8A0D502FC99C608F%2118520&authkey=AN-gn1ZxEnO4khE"

--2024-12-12 18:56:33--  https://1drv.ms/u/s!Ao9gnMkvUA2KgZBWDIQJIG-JS6RpPQ?e=ur8ggN
Resolving 1drv.ms (1drv.ms)... <IP_ADDRESS>
Connecting to 1drv.ms (1drv.ms)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://onedrive.live.com/redir?resid=8A0D502FC99C608F!18518&authkey=!AAyECSBviUukaT0&e=ur8ggN [following]
--2024-12-12 18:56:33--  https://onedrive.live.com/redir?resid=8A0D502FC99C608F!18518&authkey=!AAyECSBviUukaT0&e=ur8ggN
Resolving onedrive.live.com (onedrive.live.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to onedrive.live.com (onedrive.live.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2024-12-12 18:56:33 ERROR 403: Forbidden.

--2024-12-12 18:56:33--  https://onedrive.live.com/download?cid=8A0D502FC99C608F&resid=8A0D502FC99C608F%2118520&authkey=AN-gn1ZxEnO4khE
Connecting to onedrive.live.com (onedrive.live.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2024-12-12 18:56:34 ERROR 403: Forbidden.
$

When I run the Colab, every line says "Bad MIDI", as in...
Processing MIDI files. Please wait...
  0%|          | 0/178561 [00:00<?, ?it/s]Converting to MIDI. Please stand-by...
Bad MIDI: ./lmd_full/0/00000ec8a66b6bd2ef809b0443eeae41.mid
Converting to MIDI. Please stand-by...
Bad MIDI: ./lmd_full/0/0000799e8672292fe6f0fff08554ca40.mid
Converting to MIDI. Please stand-by...
  0%|          | 3/178561 [00:00<3:28:24, 14.28it/s]Bad MIDI: ./lmd_full/0/00012722c199ae2a628ebb792ccc617a.mid
Converting to MIDI. Please stand-by...
Bad MIDI: ./lmd_full/0/000203a04a64ad57329a058f11e235cb.mid
Converting to MIDI. Please stand-by...
  0%|          | 7/178561 [00:00<6:01:07,  8.24it/s]Bad MIDI: ./lmd_full/0/00032fb2047d3cdd0394b89349d858b4.mid
Converting to MIDI. Please stand-by...
Bad MIDI: ./lmd_full/0/00040ccb56352341cffe26c1f0f36577.mid
Converting to MIDI. Please stand-by...
Bad MIDI: ./lmd_full/0/00050936b34ae2e0529a7c2dbc3af36a.mid
Converting to MIDI. Please stand-by...
Bad MIDI: ./lmd_full/0/00052958bd8168f0fbb0b903a3cdcdc4.mid

...tens of thousands of lines line that, all of them saying "Bad MIDI".   Nothing in the Out/ or Output/ directories.   ...Is that normal?
I wonder if you might have any suggestions for getting either of these working?   Thanks very much.

@drscotthawley Thank you for reporting problems :)
The wget will not work because its an old link to OneDrive which does not exist anymore.
In regard to colab... I can't replicate the error. Everything works fine on my end.
Please comment try and except lines of code and please post the traceback of the actual errors. That way I should be able to tell you what may be wrong.
Sincerely,
Alex


issue with save the image in laravel

hello i just try to save the image but its give an error
Can't write image data to path
(C:\laragon\www\idealmgmt\storage/files/Certificates/123123123123-2.png)
this is my save line
$img->save(storage_path() . '/files/Certificates/' . $student->register_number . '-' . $type->id . '.png', 80);
with the response i got the image preview correctly without any issue but now iam trying to save the file

Does Laravel have the permissions to write the file? If you're on Linux try

chmod -R 777 storage/files/Certificates/
Keep in mind that you should never give your whole Laravel app 777 permissions.

Greetings


Provide access to the TagHelperDescriptor instance

When providing TagHelperDescriptor instances dynamically, for instance from a database, I am targeting the same TagHelper type. I'd like it to get the descriptor it was called for, with some contextual data that is known when the descriptor is created.

Talked to @DamianEdwards and this might be easy to do. If the descriptor is already there and just needs to be stashed into some context object, let's go ahead and do that.
If this is more complex, perhaps because the descriptor isn't available at the time we'd need it (e.g. compilation-time only, not at runtime), then we will move to Backlog.

I'd mark this as a feature instead of a bug. We'd have to do quite a bit to get this working due to the descriptors lack of availability at runtime. So notttt easy, my recommendation is to move to backlog.

No plans to do this


Cannot restore large index

Hello,
I am using Python 3.10.9 and vectordb==0.0.20 (latest as of this date), and I have a trouble when restoring saved data.
I have two large files A and B, and when I index them, snapshot them and restore them separately, everything works fine.
When I read and parse files A and B, index all the documents in both, then save them together, the snapshotting is successful. However, when trying to restore the data, I get the following error:
Traceback (most recent call last):
  ...
  File "~/.local/lib/python3.10/site-packages/vectordb/db/executors/inmemory_exact_indexer.py", line 86, in restore
    self._indexer = InMemoryExactNNIndex[self._input_schema](index_file_path=snapshot_file)
  File "~/.local/lib/python3.10/site-packages/docarray/index/backends/in_memory.py", line 68, in __init__
    self._docs = DocList.__class_getitem__(
  File "~/.local/lib/python3.10/site-packages/docarray/array/doc_list/io.py", line 810, in load_binary
    return cls._load_binary_all(
  File "~ /.local/lib/python3.10/site-packages/docarray/array/doc_list/io.py", line 608, in _load_binary_all
    proto.ParseFromString(d)
google.protobuf.message.DecodeError: Error parsing message

Given previous tests I made and explanation, I suspect the issue is that the index is too large, hence raising the error. Does anyone know what can be done to fix this issue?

hey @NicolasAlmerge , does it happen everytime u try to do so?

Hey @JoanFM, yes it does. Small / medium files work well separately, but when trying to restore from a large file (~3GB, combining multiple small files), it crashes with this error. Maybe it is because of an array index out of bounds due to a 32-bit integer overflow, since the max 32-bit int is around 2.7B, but I do not know.

can u provide some dummy example for me to reproduce? And what code exactly u are runnijg? together with jina and docarray versions?


Setup the "Publish Python Package" Github action

Goal
Setup the "Publish Python Package" Github action.
Motivation
When doing a new release via Github we should automatically publish it as a Python package to PyPI.

Resolved in 2b5845e5f760b34e331


Update dependencies

As mentioned in #5, dependencies update is needed on nightly since older version of regex doesn't compile cleanly. Other dependencies were also updated, I hope that's alright.
Closes #5.

Great!

Thanks!


Timeline Brainstorm

Week 1 (15.03. - 21.03.):

Monday: Finalising Code structure, first round of task dividing
Tue.: Finalising Code structure, first round of task dividing
AE, VAE models → all data?
LSTM model?

Week 2 (22.03. - 28.03.):

LSTM model?
DDSP Model?
Isolation Forest Model?
Visualisation

Week 3 (29.03. - 04.04.):

Visualisation
Preparing the presentation → takes a lot of days!

Day before Demo day (05.04.):

Meet in person for presentation rehearsal

Demo day (06.04):

Relax and rehearse individually at home!

I am closing this issue because it seems that it's better to follow this from the dedicated Google Doc.


Failed to make webhook authenticator request: Post "http://<IP_ADDRESS>:6440/v1/authenticate": dial tcp <IP_ADDRESS>:6440: connect: connection refused

Rancher Server Setup

Rancher version:
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:

Describe the bug

To Reproduce

Result
Expected Result

Screenshots

Additional context

That webhook is usually provided by DaemonSet named kube-api-auth running in cattle-system namespace. Is that DS up and running? Did you try restarting it?

That webhook is usually provided by DaemonSet named kube-api-auth running in cattle-system namespace. Is that DS up and running? Did you try restarting it?

i do not connect to api-server by kubectl, log:
╰─ k get ds -n kube-system
Unable to connect to the server: x509: certificate signed by unknown authority

And i checked log api-server then it show Failed to make webhook authenticator request: Post "http://<IP_ADDRESS>:6440/v1/authenticate": dial tcp <IP_ADDRESS>:6440: connect: connection refused`


Data model

Greetings code reviewer,
Here's a summary of the tasks I accomplished:

App Initialization:
Established a new application with a meaningful name.

Version Control:
Initialized the project using Git for version control.

Database Configuration:
Configured the project to use a PostgreSQL database.

Schema Development:
Constructed the project schema according to requirements.

Migration Management:
Created and executed the necessary migration files.

Consistency with ERD:
Ensured that table and column names align with the Entity-Relationship Diagram (ERD).

User Photo Link:
Set up the "photo" column in the users table as a link to an image.

Foreign Keys:
Implemented foreign keys where required, such as having the "author_id" column in the posts table as the foreign key to the users table.

Indexing:
Established corresponding indexes for all columns functioning as foreign keys.

These actions were performed to align the project structure with the specified criteria and maintain a consistent and well-organized database schema.

@Munsa1  Hey bro thanks a lot .


Feature request: Finer grained control on Clock Enable usage

Currently there is the -nodffe option but it's a bit brute force and you don't necessarily want to disable clock-enable usage globally.
Ideally what I'd like is to be able to tell yosys that if a signal would be used as a clock-enable for only 1 (or 2 or N) flip-flops, then don't do it and use mux. This is because in the ice40, clock enable is shared, having a FF with a CE that's only used once has a fairly high cost and makes the placer job much more complicated (leading to placer failing for any design that's somewhere close to to using a large part of the fabric).
In the  dff2dffe pass there seem to be no way to predict how many time a signal was going to be used. So my idea was to run dff2dffe, then do an dff2dffe -unmap  for any dffe where the ce is not used more than 1 time.
Unfortunately, I'm having a hard time counting how many times a CE is used, after the dff2dffe pass, all CE are different 'wires' AFAICT. I tried running an "opt_merge pass before doing the unmap and I see that this pass identifies redudant logic, but the wire names on the 'E' port of the DFFE hasn't changed after that pass so I'm not sure how to identify when 2 wires are in fact the same wire.

Ok, managed to make it work, using SigMap to identify connected signals after the opt_merge pass.
Now the question: Do you think it's a worthy feature / good idea ?  If so I can cleanup my code and make a pull request, but if you think it's not a good idea, I don't want to waste time cleaning up something that doesn't stand a chance of being upstreamed.

This can be closed now, as #702 is merged.


remove xml node_declaration

when i genereted xml i got this.
<?xml version="1.0"?>
<SomeDto>
          <ID>1</ID>
          <Name>Ali Duru</Name>
</SomeDto>

But iwant my xml like this:
<SomeDto>
          <ID>1</ID>
          <Name>Ali Duru</Name>
</SomeDto>

Is there any way to remove declaration on the top?

When saving the document, you should pass format flags format_default | format_no_declaration: https://pugixml.org/docs/manual.html#format_no_declaration

my code:
_doc.save_file("test.xml", "\t", pugi::format_default | pugi::format_no_declaration);
and xml file:
<?xml?>
<SomeDto>
	<ID>1</ID>
	<Name>anakara</Name>
	<Deleted>false</Deleted>
</SomeDto>

what am i missing?

Are you saying that with the code from the last comment you get the resulting XML from the last comment? <?xml?> looks like declaration that has either been parsed from the file (which may mean that you're loading the file with pugi::parse_declaration?), or - more likely? - like declaration that was explicitly added with the code, e.g. doc.prepend_child(pugi::node_declaration). The flag format_no_declaration only suppresses output of default declaration in case the source document doesn't have it.

Thank you for support!..


Textual and link fixes as followup to PR #568

Typographical and link fixes as followup to PR https://github.com/kubeflow/website/pull/568.

This change is

/assign @jlewi

Preview: https://deploy-preview-582--competent-brattain-de2d6d.netlify.com/docs/started/getting-started-gke/
And many other pages at that preview link

Fixes https://github.com/kubeflow/website/issues/583

/lgtm
/approve


updated link for this guide

fixed the invalid link referred by "this guide" in "In Kubernetes v1.11.0 and later, you can use kubeadm upgrade diff to see the changes that would be applied to static pod manifests."
this is fix for issue #13869

Thank you @shub-asa1 for this fix.
/lgtm

/lgtm
/approve


Firefox Not Recognizing Leather Wallet

User reported on ALEX Discord that they encountered an issue with Firefox not recognizing Leather. After refreshing the browser page (F5) three times, it seemed to resolve the issue.
ALEX Discord post

Did they install version 2.10.0 which is currently available on the Firefox store due to an unresolved issue? This version is 2 years old and not expected to work properly. If they have 6.5.0 or 6.5.1 this would be unexpected.
A new version was uploaded to Firefox over a week ago but is still pending review.

Hi any news on this ? I have 6.5.1 in firefox and have an issue (see pic) that is fixed in chrome v 6.9.2 ?

@radicleart the Firefox store has not yet accepted our latest build and is still serving 2.10.0 sadly. However, you can work around it by getting the .zip and installing it manually on Firefox instead. In that case grab the latest version for Firefox here 6.11.0 instead.

Thanks - will give it a go  !

@radicleart did the new version work for you in the end?


Error when inference

Hi! I really appreciate your implementation of SSD.
I'm using your code to detect concrete crack in crack images.
I finished naive training, and wanted to do inference on new crack image.
but when I do y_pred = model.predict(input_images),
2018-07-25 06:03:38.736651: E T:\src\github\tensorflow\tensorflow\stream_executor\cuda\cuda_dnn.cc:352] Could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR
pops up in anaconda cmd.
It can't be only originated from cudnn, because when training, cudnn worked properly.
So I'm suspecting whether my model loaded in model_path is wrongly constructed and trained or something else.
Since I can't assure anything, I'll upload the full code for my inference,
from keras import backend as K
from keras.models import load_model
from keras.preprocessing import image
from keras.optimizers import Adam
from imageio import imread
import numpy as np
from matplotlib import pyplot as plt

from models.keras_ssd300 import ssd_300
from keras_loss_function.keras_ssd_loss import SSDLoss
from keras_layers.keras_layer_AnchorBoxes import AnchorBoxes
from keras_layers.keras_layer_DecodeDetections import DecodeDetections
from keras_layers.keras_layer_DecodeDetectionsFast import DecodeDetectionsFast
from keras_layers.keras_layer_L2Normalization import L2Normalization

from ssd_encoder_decoder.ssd_output_decoder import decode_detections, decode_detections_fast

from data_generator.object_detection_2d_data_generator import DataGenerator
from data_generator.object_detection_2d_photometric_ops import ConvertTo3Channels
from data_generator.object_detection_2d_geometric_ops import Resize
from data_generator.object_detection_2d_misc_utils import apply_inverse_transforms

%matplotlib inline

img_height = 300
img_width = 300

model_path = 'C:\\Users\\user\keras\ssd_keras\ssd300_pascal_07+12_epoch-08_loss-0.2683_val_loss-0.2423.h5'

ssd_loss = SSDLoss(neg_pos_ratio=3, n_neg_min=0, alpha=1.0)

K.clear_session() # Clear previous models from memory.

model = load_model(model_path, custom_objects={'AnchorBoxes': AnchorBoxes,
                                               'L2Normalization': L2Normalization,
                                               'DecodeDetections': DecodeDetections,
                                               'compute_loss': ssd_loss.compute_loss})

orig_images = [] # Store the images here.
input_images = [] # Store resized versions of the images here.

img_path = 'C:\\Users\\user\Desktop\crack.jpg'

orig_images.append(imread(img_path))
img = image.load_img(img_path, target_size=(img_height, img_width))
img = image.img_to_array(img)
input_images.append(img)
input_images = np.array(input_images)

y_pred = model.predict(input_images)    #ERROR HERE

If you think this issue is just about my cudnn or nvidia software problem, then I'll strive by myself.
However, if you have seen any similar cases like mine, would you share your idea?
I appreciate it.

I can't help with that one, unfortunately. I'd say this is a question for Google / StackOverflow.

@pierluigiferrari I solved it! Thanks

@pierluigiferrari I solved it! Thanks

I had the same error. How did you solve it? Thank you so much.


Completely remove all non formatting tasks from the topiary crate

We envision a future where Topiary can be used as a formatting engine in other projects (e.g. text editors, Nickel). Such use cases do not care much about out language detection and configuration parsing stuff. They will handle that on their own.
What I would like to see

topiary should be a crate that just contains our wonderful formatting engine.
topiary-cli should be a crate that handles all IO, including parsing the topiary configuration and language detection.
topiary-query-files should be a crate that (behind the features flags) contains all the default query files as static string. Specifying the nickel and ocaml feature flags will export exactly those query files.

TODO:

[x] Create topiary-query-files (#609)
[ ] Move all configuration to topiary-cli

Resolved in #672


Feature/override ncesdatasource in formio submission

Override NewRebateForm and ExistingRebateForm's ncesDataSource to be an empty string on form submission.
The Form.io rebate form configuration still tries to send the full ncesDataSource data (~13MB string) on form submission with is too large for the Form.io server to accept. As a workaround we're overriding that field to be an empty string on submission and marking it as a backlog item to follow up with GSA to see if they can configure anything on their end to prevent us having to do this. This works fine as a workaround, but if they ever change the API field name from ncesDataSource to something else, we'd need to update our code to make that same change.

@coobr01 @dpgalloway @cschwinderg 🎉🎉🎉


Hosting firmware builds on GitHub? (fetch/CORS issues)

I am using GitHub Actions in order to automate my build process. So basically every time I push a change, it automatically creates a new build and adds a release to my GitHub repo making the binaries accessible. That in itself works great and the logical next step would be to utilize GitHub Pages in order to flash any release. But that is where I'm running into a big issue: I cannot fetch an asset from a GitHub release from the JavaScript of a GitHub Pages site because of how GitHub has set up their CORS rules.
When you search for that CORS limitation you actually quickly find other users of esp-web-tools running into the same issue.
I would like to know if anyone has found a way to make this work in some way.
The only way I could think of would be to store the builds directly in the git repository, but that would unnecessarily bloat the repo and is bad practice to begin with. Unfortunately, the only other way I see is to host on some paid storage solution, which is less than ideal for an open source project that doesn't make any money.

I think I have found a ... somewhat acceptable workaround.
The two main issues with storing binaries directly in a git repository are:

Performance (slow cloning speeds etc)
Bloating the history

In order to work around that you can use a separate branch and essentially disable the commit history on it.
I'm using the gh-pages branch to store all my firmware builds and whenever I push a new firmware into it, I write it into the first and only commit that exists on that branch.
This can be achieved quite easily like this:
git checkout gh-pages
git add ./firmware/
git commit --amend --no-edit
git push --force

In order to still have proper source control on the actual html code of the GitHub Pages site, I store my index.html on the main branch and copy it into the gh-pages branch on every push.
I am of course not doing any of this manually. I used GitHub Actions to automate it all.
I don't know if it makes sense to link my project here because it will undergo a lot of changes the coming weeks, but here it is nevertheless: https://github.com/T-vK/ShowboxInterceptor
I also managed to dynamically create manifests on the fly using unmodified esp-web-tools. The trick is to intercept the fetch request and inject a generated response. See index.html in my repo.
If anyone has a better idea on how to do all this, I'm very open to having a discussion about it.

Hi,
an alternative is to setup a little cors-anywhere web service. With this, you are able to fetch files from anywhere without cors issue. A demo can be found here: https://github.com/Rob--W/cors-anywhere
Cors-anywhere exists as docker too ;)

Yes, that is of course true, but you will have to rent and maintain a server/service in order to do that.
Keeping everything on Github eliminates all the maintainance work and ensures scalability, availability, stability and performance without you having to do anything.
But on the other hand it works perfectly with github pages without a CORS issue if you store the binary files in your Repo
I´m using the webinstaller in my repo. Binaryfiles will be stored in a sparate web-installer branch which is defined for Github pages
-> https://tobiasfaust.github.io/SolaxModbusGateway/

Yes, if you store the binaries in the branch used for github pages, then it just works and no additional cors proxy is required.
That's how I'm doing it in my project too: (Branch,  [Page] (https://t-vk.github.io/ShowboxExpansionModule/)) as mentioned in this comment.


Graphlql isn't not formatted on save

I tried graphql code as template string preceded with gql and as dedicated .graphql file but nothing happens on save.
I have set "coc.preferences.formatOnSaveFiletypes": ["*"] in my config.

You have to set the file to graphql.
Type:
:setfiletype graphql


Test tab switching and that the state of each tab is saved

Create two different reports using the backend, with names “name” and “otherName”.
Open Ladybug. Check that there are two reports.
Open the report with name “name”.
Go to its top row and press copy.
Open the report with name “otherName”.
Go to tab Test. Check that there is one report and that it has name “name”.
Go back to tab Debug.
Check that the table has reports “name” and “otherName”.
Check that there are two open reports, with name “name” and name “otherName”.
Go to tab Test.
Check that there is one report and that it has name “name”.

I think I added this test already to PR #71. I will add to #71 that the debug tab should also save which open report is selected.


Add rule: "arrow-parens": [2, "as-needed"]

The history of this seems that an identical PR was submitted as #15 almost one year ago.
There was some discussion in https://github.com/feross/standard/issues/309.
In February 5, this rule was merged in but with the "always" option, as https://github.com/feross/eslint-config-standard/commit/dd85d36d41530deac9c6036f79116f9e21966235 and released in v5.
In March 24, this rule was removed via #28.
It is now October 23 and the reasonable code style seems to me to be "arrow-parens" with "as-needed".

http://eslint.org/docs/rules/arrow-parens

Is this a hot potato, or something? I've posted this PR 25 days ago and no comments :zipper_mouth_face: ...

I don't think anything has changed since this rule was removed, so why add it back now?

@feross I'm not suggesting the same format! The rule was added with "always" and then removed. I'm suggesting "as-needed", which makes total sense to me. Doesn't it to you?
n => n + 1 vs. (n) => n + 1: the parens are totally unnecessary. Why include them?
I'm the biggest advocate of standard because of the reasonable choices. Here, at least to me, seems to be an obvious one.
Even though I've seen contributors convinced (#309) that "always" is the correct choice, because of consistency, I disagree and I feel that "as-needed" is correct.

in some cases, where the argument is one character (e.g. n => n + 1), this means three times more characters on the left side of the function.
Lambda functions are cool. n = n + 1 looks nice to me.
Consistency with other syntaxes is not an argument, because different syntaxes of the arrow function serve different purposes. In those different purposes, it is legitimate to use those different syntaxes. In the case of a one-liner, there is no question about it, in my mind and I think that this is the majority of JavaScript developers: no parens. In the case of a single argument and a multi-line code block, it is debatable. Yet, it is our duty to close the debate. I think that setting a rule that is somewhere between "as-needed" and "always" would be too complicated to to justify, for people to accept. And that's besides my personal preference for "always". I'll not be comfortable explaining that "only for one-liners you may omit the parens", just as I'll not be comfortable explaining that "for consistency, even though JS allows omitting it, you may not omit it".
"as-needed" needs no explaining. That's the beauty. "as needed"—bang. Simple, tried and tested.

@mightyiam maybe you should post this to https://github.com/feross/standard/issues/309 instead

Next step on arrow-function parens
We are software developers. We do things incrementally, while understanding also the bigger picture.
Thus my intention in this conversation is to converge on a single next step; a single and simple rule that everyone agrees on.
Background

Oct 26, 2015 #309: initial suggestion
Oct 27, 2015 https://github.com/feross/eslint-config-standard/pull/15: PR suggesting arrow-parens "as-needed" (closed)
Feb 5 2016 https://github.com/feross/eslint-config-standard/commit/dd85d36d41530deac9c6036f79116f9e21966235: arrow-parens "always" added in time for v6.
Feb 10 2016 #414: discussion flollowing release of v6 with arrow-parens "always"
Mar 24 2016 https://github.com/feross/eslint-config-standard/pull/28: arrow-parens "always" removed in time for v7
Oct 23 2016 https://github.com/feross/eslint-config-standard/pull/54: PR for arrow-parens "as-needed" again (by me) (closed)

Arrow function with no arguments: parens or placeholder
JavaScript syntax requires parens. But, there's a workaround:
items.forEach(_ => console.log('Item!'))

We declare an argument with the intention of not using it, just because we find it easier to type and/or read _ than () in this context. Note that instead of _ the placeholder can be anything that Standard will approve of (🦄 seems to not be allowed).
For the sake of moving forward with decision regarding parens for arrow functions, I suggest that we choose to postpone conversation regarding this workaround. Even though we have the intention of setting each rule once for all eternity, and even though these two matters are somewhat coupled, and even though ignoring this now might mean that it will be harder to get agreement on later, I feel that it is better to leave this for later. Also because even if it is later Standardized as _ or (), it seems to me like an easy and auto-fixable change.
Arrow function with a single argument
Parens required

The first end of the spectrum
Already implemented in ESLint
Easy to explain and understand
Minimalism over consistency (consistency with zero and multiple arguments)

Parens disallowed

The second end of the spectrum
Already implemented in ESLint
Easiest to explain and understand
Consistency over minimalism (consistency with zero and multiple arguments)

Parens when body is multi-line
This means that when the body of a single-argument arrow function is multi-line, parens are required.

What is the purpose for this? No judgement intended.
I don't know of an implementation

Arrow function with multiple arguments :white_check_mark:
JavaScript syntax chooses for us. Parens required.
Consistency with other rules
Consistency with other rules feels correct. It proves that Standard has a well-defined purpose and that the rules follow this purpose. It also helps remember what the style is, because rules "support each other" and it all kind of "connects" in the mind. That's the way I see it.
So, are there any rules in Standard that we can derive an underlying principle upon which to base this decision?
"comma-dangle": [2, "never"]
I'm guessing that if IE8 and below didn't die on trailing commas, then trailing commas would have been widespread in JavaScript long, long ago.
There is a proposal for trailing commas in function parameters.
So I'm also guessing that Standard will move in the future to trailing commas everywhere. Speculations aside, this is most likely not about minimalism, but browser support.
"curly": [2, "multi-line"]
Minimal over simple. Avoid unnecessary braces, yet, prevent confusion. Allow neat one-liners.
"eqeqeq": [2, "allow-null"]
This may seem about simplicity, but I don't think so. I think that this is about preventing coercion related bugs.
"semi": [2, "never"]
Minimal over simple. Perhaps at the heart of Standard.
Conclusion on minimal vs simple
I've found that this is a question of minimal vs simple, where minimal is sans-parens and simple is always parens. The general winds in Standard are blowing towards minimalism. And, personally, I like that.
In Standard, Mr. minimal seems to win, yet, with consideration to important things, such as preventing bugs. So, disallowing parens around the single argument of an arrow function seems consistent with other Standard rules, to me.
Recap

Long conversation
Let's postpone decision between _ => {} and () => {}
No-parens seems consistent with other rules
I find no compelling arguments towards requiring parens other than "it is easier for me to read".

@mightyiam Thanks for the writeup.
The more I think about this, the more I like "as-needed", { "requireForBlockBody": true }.
// bad
[1, 2, 3].map((x) => x * x)

// good
[1, 2, 3].map(x => x * x)

// good
[1, 2, 3].map(number => (
  `A long string with the ${number}. It’s so long that we don’t want it to take up space on the .map line!`
))

// bad
[1, 2, 3].map(x => {
  const y = x + 1
  return x * y
})

// good
[1, 2, 3].map((x) => {
  const y = x + 1
  return x * y
})

Minimalist and practical.

@feross I'm happy with all of the above except:
// good
[1, 2, 3].map(number => (
  `A long string with the ${number}. It’s so long that we don’t want it to take up space on the .map line!`
))

We don't make that exception for:
if (cond)
   really long expression

Why would we for the lambdas?

I also have cases where I have maybe 50-event handling lambda functions in a row:
emitter.on('event', () => console.log('...'))
emitter.on('event', () => console.log('...'))

I wouldn't mind requireForBlockBody. It kind of makes sense for me, as well.
@dcousens those 50 event handling lambda functions seem like they could be made with iteration.
Also, you could eslint-disable arrow-parens for that block to be consistent. That would make more sense to me. Edge cases be edge cases.

@dcousens those 50 event handling lambda functions seem like they could be made with iteration.

They aren't exactly like that,  its an example.  The events and the emitters are all completely variable.

I've added { "requireForBlockBody": true } to the branch of this pull request. I assume that the reason for it not showing up in this pull request, is that it is closed.

@dcousens Pretty sure that you would be able to keep those single-line lambdas. The given example:
[1, 2, 3].map(number => (
  `A long string with the ${number}. It’s so long that we don’t want it to take up space on the .map line!`
))

was just illustrating that you're allowed to omit the parens if you're doing number => () but not if you're doing number => {}.

@feross it turns out I was lying,  I just looked back at the code I was actually referring to... and I use as-needed there already.
:confused:

Can we not do this? - imo when we decided to move away from having parens
on "always" in https://github.com/feross/standard/issues/414 we gave up on
having this rule be consistent. Instead what's being proposed now is
complicated; if we're gonna make a change (and I'm not saying we should)
let's take the sane route and optimize again for readability and
refactoring rather than writability and cleverness.
I propose we do nothing; things are fine as they are.
On Sat, Dec 3, 2016 at 3:06 AM Daniel Cousens<EMAIL_ADDRESS>wrote:

@feross https://github.com/feross it turns out I was lying, I just
looked back at the code I was actually referring to... and I use as-needed
there already.
😕
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/feross/eslint-config-standard/pull/54#issuecomment-264608150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWleiZguCOpE7olSRFDqh8c0Tv8CuA4ks5rEM7CgaJpZM4KeE5H
.

@yoshuawuyts will you please explain what the issue with "as-needed" and refactoring is?
Is it that when adding a second argument to a single argument arrow function you'd have to add parens? I agree that's no optimal for refactoring. Yet, it does not seem to be a good enough reason to not allow absence of parens in single argument arrow functions. That's my take.


ad

ad

This item belongs to payment request #244B9E on OnlyDust:

from oscarwroche to oscarwroche
5 items included
$500 for 1 day of work


BillBl Reviews and edits

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/Cards/cards-actions.md
:warning:Warning

Details

msteams-platform/concepts/Cards/cards-reference.md
:warning:Warning

Details

msteams-platform/concepts/Cards/cards.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-channel.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-personal.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conversations.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-overview.md
:warning:Warning

Details

msteams-platform/concepts/connectors.md
:warning:Warning

Details

msteams-platform/troubleshoot/troubleshoot.md
:warning:Warning

Details

msteams-platform/concepts/Cards/cards-actions.md

Line 212: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).

msteams-platform/concepts/Cards/cards-reference.md

Line 45: [Warning] Invalid file link:(~/concepts/Cards/`/concepts/cards/cards-actions).
Line 82: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 159: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 241: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 273: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 342: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 547: [Warning] Invalid file link:(~/concepts/Cards/`/concepts/bots/auth-flow-bot).

msteams-platform/concepts/Cards/cards.md

Line 9: [Warning] Invalid file link:(~/concepts/cards/cards-actions).
Line 19: [Warning] Invalid file link:(~/concepts/connectors).
Line 21: [Warning] Invalid file link:(~/concepts/Cards/`/concepts/connectors).
Line 27: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 31: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 31: [Warning] Invalid file link:(~/concepts/messaging-extensions).
Line 35: [Warning] Invalid file link:(~/concepts/cards/cards-reference).

msteams-platform/concepts/bots/bot-conversations/bots-conv-channel.md

Line 22: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 30: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations#teams-channel-data).
Line 45: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-member-or-bot-addition).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal#starting-a-11-conversation).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bots-context#fetching-the-team-roster).
Line 56: [Warning] Invalid file link:(~/resources/design/overview).
Line 112: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 194: [Warning] Invalid file link:(~/concepts/bots/bots-context).

msteams-platform/concepts/bots/bot-conversations/bots-conv-personal.md

Line 9: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 11: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 29: [Warning] Invalid file link:(~/resources/design/overview).

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md

Line 21: [Warning] Invalid file link:(~/scenarios/bots-conv-channel).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-member-or-bot-addition).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bots-context#fetching-the-team-roster).

msteams-platform/concepts/bots/bot-conversations/bots-conversations.md

Line 17: [Warning] Invalid file link:(~/concepts/bot-conversations/bots-conv-channel).
Line 18: [Warning] Invalid file link:(~/concepts/bot-conversations/bots-conv-personal).
Line 24: [Warning] Invalid file link:(~/references/resources/schema/manifest-schema).
Line 38: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 52: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 60: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/~concepts/bots/bot-conversations/bots-message-format).
Line 63: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/`/concepts/bots/bots-text-formats).
Line 65: [Warning] Invalid file link:(~/concepts/cards/card-format).
Line 85: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 135: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel#mentions).
Line 145: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 149: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-name-updates).
Line 152: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 189: [Warning] Invalid file link:(~/concepts/cards-actions).
Line 197: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive#starting-a-11-conversation).
Line 198: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive#creating-a-channel-conversation).
Line 200: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/~concepts/bots/bot-conversations/bots-conv-proactive).
Line 269: [Warning] Invalid file link:(~/scenarios/bots-personal-conversations#starting-a-11-conversation).
Line 270: [Warning] Invalid file link:(~/scenarios/bots-channel-conversations#creating-a-channel-conversation).

msteams-platform/concepts/bots/bots-overview.md

Line 15: [Warning] Invalid file link:(~/concepts/outgoingwebhook).
Line 21: [Warning] Invalid file link:(~/references/resources/schema/manifest-schema).
Line 36: [Warning] Invalid file link:(~/references/resources/schema/manifest-schema).
Line 40: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 61: [Warning] Invalid file link:(~/get-started/get-started-nodejs).
Line 62: [Warning] Invalid file link:(~/get-started/design#designing-a-great-bot).
Line 62: [Warning] Invalid file link:(~/concepts/tabs/tabs-static).
Line 62: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 63: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 64: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations).
Line 64: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 65: [Warning] Invalid file link:(~/concepts/bots/bots-test).
Line 66: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 69: [Warning] Invalid file link:(~/get-started/get-started-app-studio).
Line 73: [Warning] Invalid file link:(~/concepts/outgoingwebhook).

msteams-platform/concepts/connectors.md

Line 35: [Warning] Invalid file link:(~/concepts/cards/cards).
Line 189: [Warning] Invalid file link:(~/concepts/apps/apps-package).
Line 189: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 189: [Warning] Invalid file link:(~/overview#apps-in-microsoft-teams).
Line 196: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 200: [Warning] Invalid file link:(~/concepts/apps/apps-package#icons).
Line 265: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/troubleshoot/troubleshoot.md

Line 16: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).
Line 48: [Warning] Invalid file link:(~/concepts/authentication/authentication).
Line 60: [Warning] Invalid file link:(~/get-started/get-started-tenant).
Line 64: [Warning] Invalid file link:(~/concepts/apps/apps-upload).
Line 72: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel#mentions).
Line 89: [Warning] Invalid file link:(~/resources/schema/manifest-schema#developer).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use splice instead of insertAt

Replace Array.insertAt by Array.splice.
Note: this make it possible to use ember-cli-mirage for addons.

thx!

My pleasure, thanks for this awesome tool :)


Get-RsSystemRole

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Command does not exist
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
What is the expected behavior?
We should have a Get-RsSystemRole that we can use in conjunction with Grant-RsSystemRole.
It is assumed that Get-RsCatalogItemRole does not provide System Roles.
Which versions of Powershell and which OS are affected by this issue? Did this work in previous versions of our scripts?
Name                           Value
----                           -----
PSVersion                      5.1.17134.228
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.228
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

I would like to have this feature too.

At the moment I'm working around this using this Powershell snippet
$ReportServerUri = 'http://localhost/MyReports/ReportService2010.asmx'
$rsProxy.GetSystemPolicies()

It gives output like this
GroupUserName          Roles
-------------          -----
BUILTIN\Administrators {System Administrator}


Retain querystring values during pagination

Hello, I love this package so much, it does not play nice with pagination options like withQueryString()

This worked as a temporary solution
$data = new \Illuminate\Pagination\LengthAwarePaginator(
$data->getCollection(),
$data->total(),
$data->perPage(),
$data->currentPage(), [
'path' => request()->url(),
'query' => $request->query()
]
);
where $data is the result from Search::new()->add(...

I Think this is the same Issue as this one posted to the Laravel-Ide-Helper Project.
https://github.com/barryvdh/laravel-ide-helper/issues/1144

I don't understand the problem. Could you give an example so I can reproduce the problem?

This solution worked for me:
$results->appends($request->query());

Here is a link to the documentation: https://laravel.com/docs/9.x/pagination#appending-query-string-values.

Hello, i was stuck in same problem, but found solution in @lucacastelnuovo comment.
example with working search query + pagination:
 Search::add(Lokale::with(['company'])->appends(), ['label', 'company.name'])                     ->paginate(10)                     ->dontParseTerm()                     ->search(Request::input('search'));


Incompatibility with Ruby 2.4.x

Ruby 2.4.x introduces TLS support for net/ftp - https://github.com/ruby/ruby/blob/ruby_2_4/lib/net/ftp.rb. The changes in the class functions caused issues with double-bag-ftps extended function.
A couple notable differences:

net/ftp only supports explicit FTPS. It doesn't support implicit FTPS
net/ftp connect() does 'AUTH TLS' if ssl option is set (conflicts with double-bag-ftps login() function)

Are there any plans to support Ruby 2.4.x ?
Thanks.

I received this NoMethodError: undefined method 'sync' for #<Net::FTP::BufferedSSLSocket:0x00000009d26578> after login method call.
Ruby version: 2.4.1

@Kitton got the same error as you:

NoMethodError: undefined method 'sync' for #Net::FTP::BufferedSSLSocket:0x00000009d26578 after login method call.
Ruby version: 2.4.1

The ftpd gem depends upon double-bag-ftps for its unit tests, so this issue is a real bother for me.  I do plan to fix this eventually, since I'm in the best place to do so (ftpd's unit tests are probably the best automated test of double-bag-ftps that exists right now).

A possible solution can be switching to the native Net::FTP https://ruby-doc.org/stdlib-2.4.0/libdoc/net/ftp/rdoc/Net/FTP.html#method-c-new from double-bag-ftps

Ruby 2.4.0 now includes SSL support - Ruby 2.3.0 didn't have this.
DoubleBagFTPS is no longer needed. Looking through the new Net::FTP source code, the change we made was:
  def connection
    @connection ||= (
      ftps = DoubleBagFTPS.new
      ftps.ssl_context = DoubleBagFTPS.create_ssl_context(ssl_context_params)
      ftps.connect(host, port)
      ftps.login(user, password)
      ftps.passive = true
      ftps
    )
  end

to
  def connection
     @connection ||= Net::FTP.new(host, connection_params)
  end

  def connection_params
    {
      port:     port,
      ssl:      ssl_context_params,
      passive:  true,
      username: user,
      password: password
    }
  end

@drn I think that is mostly true.  The last time I looked, I remember finding that the built-in classes do not do implicit TLS.  If we can make this library still do that, that would be nice.  Even nicer would be figuring out how to use the built-in classes to do implicit TLS, at which point we can thank double-bag-ftps for its long service and put it to rest.

I second the need to have implicit support.   how can I help.

I submitted a pull that is working for me on the implicit.
https://github.com/bnix/double-bag-ftps/pull/18

FWIW this is all I needed to get implicit working with 2.4.1. Feel free to use as a starting point for slimming down double-bag-ftps.
class MyFTP < Net::FTP
  FTP_PORT = 990

  def connect(host, port = FTP_PORT)
    synchronize do
      @host = host
      @bare_sock = open_socket(host, port)
      begin
        ssl_sock = start_tls_session(Socket.tcp(host, port))
        @sock = BufferedSSLSocket.new(ssl_sock, read_timeout: @read_timeout)
        voidresp
        if @private_data_connection
          voidcmd("PBSZ 0")
          voidcmd("PROT P")
        end
      rescue OpenSSL::SSL::SSLError, Net::OpenTimeout
        @sock.close
        raise
      end
    end
  end
end

I should add that the above assumes ssl: true is passed as an initialization option.

@wconrad, any chance support for Ruby 2.4.2 will be added in the next month or two? Our project has a dependency on this gem, but we don't have a good test FTPS environment where we can validate work on fixing ruby 2.4.2 support.

I don't have time to work on double-bag-ftps or ftpd right now, so sadly this issue will have to remain unsolved by me.
The real problem is that I no longer have a way to test any changes to double-bag-ftps.  Its test suite relied on an external web site that existed just for ftps testing; that web site no longer exists.  I haven't had time to come up with a suitable replacement.

Would this work?  https://ftptest.net/
It states it supports implicit FTP over TLS.
-- Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
From: Wayne Conrad<EMAIL_ADDRESS>Reply-To: bnix/double-bag-ftps<EMAIL_ADDRESS>Date: Friday, March 23, 2018 at 2:01 PM
To: bnix/double-bag-ftps<EMAIL_ADDRESS>Cc: Miles Lane<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [bnix/double-bag-ftps] Incompatibility with Ruby 2.4.x (#17)
I don't have time to work on double-bag-ftps or ftpd right now, so sadly this issue will have to remain unsolved by me.
The real problem is that I no longer have a way to test any changes to double-bag-ftps. Its test suite relied on an external web site that existed just for ftps testing; that web site no longer exists. I haven't had time to come up with a suitable replacement.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttp://cp.mcafee.com/d/2DRPoOrhvjhujuKC-rdEEFELcFLLECQkkQnCkT6kjpISrlIl-BaMVsSzF2UHHG7yG1EVtjoupp5jhOUgh5m4XS5jhOqer3xlZPTQ7m77T_QSrdCPpesRG9px6kOrp3BY8gA7UxlIwvVsxF4KXdqCiFhLWoye0Olad-KHY9BShPUVZ4sqejhOrdETvjdCXCQPrNKVJUSyrh, or mute the threadhttp://cp.mcafee.com/d/2DRPoA839J5Zd5VdWWrVISyyCyYOC--yrhhjhupjsphdCPpJmNnWkH3BPqeAbyKKEuaE6zBRdxVBAld7bx14lojLold79EVIe5nTfvgtosvv_jpISrdAVPmEBC4pj9JAenO5pOtBrpOH2CdMESgFqcy7BZrCjMg2PWOFogy1NEaI5wi9g3Eu2U2U3WnI19491dxAHh-pc4AmiewgI18SM31MU2wCrdETvjdCXCQPrNKVJUSyrh.

What are the requirements for an adequate test server for ongoing development?
Thanks,
Miles
-- Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
From: Wayne Conrad<EMAIL_ADDRESS>Reply-To: bnix/double-bag-ftps<EMAIL_ADDRESS>Date: Friday, March 23, 2018 at 2:01 PM
To: bnix/double-bag-ftps<EMAIL_ADDRESS>Cc: Miles Lane<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [bnix/double-bag-ftps] Incompatibility with Ruby 2.4.x (#17)
I don't have time to work on double-bag-ftps or ftpd right now, so sadly this issue will have to remain unsolved by me.
The real problem is that I no longer have a way to test any changes to double-bag-ftps. Its test suite relied on an external web site that existed just for ftps testing; that web site no longer exists. I haven't had time to come up with a suitable replacement.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttp://cp.mcafee.com/d/2DRPoOrhvjhujuKC-rdEEFELcFLLECQkkQnCkT6kjpISrlIl-BaMVsSzF2UHHG7yG1EVtjoupp5jhOUgh5m4XS5jhOqer3xlZPTQ7m77T_QSrdCPpesRG9px6kOrp3BY8gA7UxlIwvVsxF4KXdqCiFhLWoye0Olad-KHY9BShPUVZ4sqejhOrdETvjdCXCQPrNKVJUSyrh, or mute the threadhttp://cp.mcafee.com/d/2DRPoA839J5Zd5VdWWrVISyyCyYOC--yrhhjhupjsphdCPpJmNnWkH3BPqeAbyKKEuaE6zBRdxVBAld7bx14lojLold79EVIe5nTfvgtosvv_jpISrdAVPmEBC4pj9JAenO5pOtBrpOH2CdMESgFqcy7BZrCjMg2PWOFogy1NEaI5wi9g3Eu2U2U3WnI19491dxAHh-pc4AmiewgI18SM31MU2wCrdETvjdCXCQPrNKVJUSyrh.


"The specified entry is already present in the target Overlay." Error

I'm using the searchfield: ^1.0.3 version.
"The specified entry is ready present in the target Overlay." error occurs when tap the field again after tapping the supplement.
In debug mode, only errors occur and move on, but in release mode, the entire screen stops and does not work.
How can I fix it?
SearchField(
      controller: _searchController,
      focusNode: _searchFocusNode,
      itemHeight: MediaQuery.of(context).size.height * .06,
      suggestionState: Suggestion.expand,
      suggestionAction: SuggestionAction.unfocus,
      suggestions: ModeType.values
          .map(
            (e) => SearchFieldListItem<ModeType>(
              e.name,
              item: e,
              child: Obx(
                () {
                  bool selected = (MusicController.inst.modeType.value.level == e.level) &&
                      (MusicController.inst.modeType.value.subLevel == e.subLevel);

                  return Material(
                    color: Colors.transparent,
                    child: Padding(
                      padding:
                          EdgeInsets.only(left: e.subLevel > 0 ? 30.r : 10.r, right: 10.r, top: 10.r, bottom: 10.r),
                      child: Row(
                        children: [
                          Expanded(
                              child: CustomText(
                            e.name,
                            style: TextStyle(
                              fontFamily: pretendardFont,
                              color: selected ? Colors.white : const Color(0xFF9D9D9D),
                              fontWeight: selected
                                  ? FontWeight.bold
                                  : e.subLevel == 0
                                      ? FontWeight.w500
                                      : FontWeight.w400,
                              fontSize: e.subLevel == 0 ? 15 : 14,
                            ),
                          )),
                        ],
                      ),
                    ),
                  );
                },
              ),
            ),
          )
          .toList(),
      searchStyle: const TextStyle(
        color: Colors.white,
        fontFamily: pretendardFont,
        fontSize: 13,
      ),
      suggestionsDecoration: SuggestionDecoration(
        borderRadius: const BorderRadius.only(
          bottomLeft: Radius.circular(13),
          bottomRight: Radius.circular(13),
        ),
        color: const Color(0xFF222222),
      ),
      searchInputDecoration: InputDecoration(
        filled: true,
        contentPadding: EdgeInsets.symmetric(horizontal: 20.r, vertical: 15.r),
        fillColor: const Color(0xFF222222),
        focusedBorder: inputDecoration,
        border: inputDecoration,
        disabledBorder: inputDecoration,
        enabledBorder: inputDecoration,
        errorBorder: inputDecoration,
        focusedErrorBorder: inputDecoration,
        hintText: 'What is your current condition?',
        hintStyle: const TextStyle(
          color: Color(0xFF555555),
          fontFamily: pretendardFont,
        ),
        prefixIcon: IgnorePointer(
          child: IconButton(
            onPressed: () {},
            icon: SvgPicture.asset(
              'assets/svgs/search.svg',
              colorFilter: getColorFilter(const Color(0xFF656565)),
            ),
          ),
        ),
      ),
      onSuggestionTap: (SearchFieldListItem<ModeType> suggestion) async {
          ~
      },
      onSubmit: (text) {},

Fix)
on onSuggestionTapped()
modified this code
     suggestionStream.sink.add(null);
     if (widget.onSuggestionTap != null) {
       widget.onSuggestionTap!(item);
     }

To
     suggestionStream.sink.add(null);
     removeOverlay();
     if (widget.onSuggestionTap != null) {
       widget.onSuggestionTap!(item);
     }

It works well without any problems.

I have submittted a temporary fix, it still resurfaces but I am not able to catch it 100% of the time. The cause its unknown at this time  Unfortunately :(

thank you so much! :)

The branch you fixed works fine on my app! 😊

Thanks for the confirmation @tkddbf7348, I will go ahead and publish this version. Feel free to write back on this issue incase you encounter the error again.

@tkddbf7348 published v1.0.4


env.IsDevelopment() returns False always in latest RC2

In the following general startup code, no matter what value is specified for ‘Hosting:Environment’, env.IsDevelopment() always retusns false, that is ‘Hosting:Environment’=‘Production’ all the time.
public Startup(IHostingEnvironment env)
{
If(env.IsDevelopment())
{
//Unreachable code
}
Else
{
//...
}
}
In RC2 not so long ago (for an example, RC2 16177), no this issue exists.

See https://github.com/aspnet/Announcements/issues/108


Upgrade account roles with managed policies

If the roles have the tag rosa_managed_policies:true, verify that the managed policies are attached and exit.
Policies upgrade isn't needed for managed policies.
Related: SDA-7678
Examples:

User provides invalid prefix:

User upgrades roles with managed policies successfully:

One of the roles is missing the attached managed policy:

Managed policies are disabled on production:

/lgtm


Creating table in teradata: Error: Data Type "TEXT" does not match a Defined Type name.

Reporting an Issue with sparklyr
When I try to push iris_tbl to teradata database, I get the following error:
Error: java.sql.SQLException: [Teradata Database] [TeraJDBC <IP_ADDRESS>] [Error 3706] [SQLState 42000] Syntax error: Data Type "TEXT" does not match a Defined Type name.
spark_version <- ‘2.2.1’
Sys.setenv(SPARK_HOME = "/usr/local/spark")
config <- spark_config()
config$sparklyr.cores.local <- 20
config$spark.sql.shuffle.partitions.local <- 5
config$spark.executor.cores <- 1
config$spark.executor.memory <- "4G"
config$spark.driver.memory <- "40G"
config$`sparklyr.shell.driver-memory` <- "16G"
config$`sparklyr.shell.executor-memory` <- "16G"
sc <- spark_connect(master = "local",
                    spark_home = "/usr/local/spark",
                    deployMode="client",
                    config = config)

# your reproducible example here

iris_tbl <- copy_to(sc, iris, 'iris', overwrite = TRUE)
spark_write_jdbc('iris_tbl',
name    = dbTableName,
options = list(url      = myurl,
user     = myUserId,
password = myPassword), mode = "append")

I would try to figure out which column is introducing this issue, by saving subsets of the data. Seems like this could be a JDBC issue, the JDBC driver might provide a way to tweak the configuration for TEXT types.
Related: https://kylo-io.atlassian.net/browse/KYLO-1766


Limit the request method type

breaking change: Before this change the uppercase form of each method works as well as the lowercase. This change will cause typescript compiler errors for users that chose to use the upper case form.

Coverage increased (+1.5%) to 93.719% when pulling f6f1c28b598e73a34079d4ea1f4e634ea3ee04dd on ofirgeller:patch-1 into f31317aeca8f7fa385d6aee94ef6ec8ac9d7c072 on mzabriskie:master.

Thanks for the PR but I think it's a better idea to accept both (uppercase and lowercase). #912 is in progress for it.

@rubennorte
That can be done simply by changing the code to
method?: 'get'|'delete'|'head'|'post'|'put'|'patch'|'GET'|'DELETE'|'HEAD'|'POST'|'PUT'|'PATCH';
That would still be an improvement for the user (no errors due to misspelling).
I do think that it would be less nice for auto complete and I personally don't like to create two ways of doing the same thing but sure. ¯_(ツ)_/¯

@ofirgeller I see the point, but there's also the fact that we don't currently limit the allowed request methods. In this case, you're missing OPTIONS, CONNECT and TRACE from the spec.
@nickuraltsev you know TS better than I do. WDYT?

I don't believe we should limit the allowed request methods. If someone wants to use a non-standard HTTP method like PURGE, axios should let them do that.

@nickuraltsev
I see your point, but this is an edge case and the user can always cast to any to get around the type.
config.method = 'PURGE' as any;
Also If it's not an edge case because a none standard method is common in the real world we can include it in the type.


add comdex as host

Closes: #XXX
Context and purpose of the change

*Adds comdex as a host

Author's Checklist
I have...

[x] Run and PASSED locally all GAIA integration tests
[ ] If the change is contentful, I either:

[ ] Added a new unit test OR
[ ] Added test cases to existing unit tests

[ ] OR this change is a trivial rework / code cleanup without any test coverage

If skipped any of the tests above, explain.

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] manually tested (if applicable)
[ ] confirmed the author wrote unit tests for new logic
[ ] reviewed documentation exists and is accurate

Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md?
[ ] This pull request updates existing proto field values (and require a backend and frontend migration)?
[ ] Does this pull request change existing proto field names (and require a frontend migration)?
How is the feature or change documented?

[ ] not applicable
[ ] jira ticket XXX
[ ] specification (x/<module>/spec/)
[ ] README.md
[ ] not documented

@dhogaivannan can you please run the integration tests for Comdex? you can do so by running
make start-docker && make test-integration-docker

and updating the /stride/dockernet/tests/integration_tests.bats file