Error in adding Qna maker in bot composer

Describe the bug
When I try to add qna maker subscription key and add existing qnamaker in bot composer, It is throwing an error saying "
Cannot read property 'primaryEndpointKey' of undefined"
Version

v2.0.0
Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior

Screenshots

Additional context

Hi @vinaysopinti
Are you using the QnAMaker dialog action from an Empty templated bot (or similar)? Or are you using the CoreWithQnA template?
At which point are you getting the error? I assume that's not just when entering the subscription key in the bots settings.

Closing due to inactivity.


always restarting

Hey,
I'll try to add Your image.
In /opt/AutoDelete/ are directories : data and config.yml
Shouldn't the config.yml be a file?
How I can fix this?

Yes. I was try to create file befroe pulling image - it always restarting.
If i delete directory config.yml and add file config.yml not start because not found directory.
Now I compiled it from source and run outside docker.


Group Monitor: DataTable header and row disjointed

They scroll independently.

Can't reproduce on my setup. Works flawlessly on Linux/Chrome on all breakpoints.

Still happening on my phone in the HA companion app.

New data tables don't show header in narrow mode, and it isn't horizontal scrollable anymore. So I guess we are good.


Add some random prefix to split ids.

S3 creates partitions based on a prefix of the object keys.
Because we use ULID, splits coming from the same day end up on the same servers.
On the search side, most of the queries tend to target the last few days, and end up hitting the same servers.
For this reason, in some case, we can hit the per-prefix rate limiting.

https://aws.amazon.com/blogs/aws/amazon-s3-performance-tips-tricks-seattle-hiring-event/


Validate that the auctioneer role is granted on OEV Network (at OevAuctionHouse) and target chains (at Api3ServerV1OevExtension)

Will be done after contracts-qs is merged

Done in https://github.com/api3dao/contracts-qs/commit/bbdd6ab9010f9f6b177006ecd6134b2372f2d312, will be merged later


Latest Update Broke Markdown CSS

I just updated my Home Assistant instance on a Raspberry Pi 4B:
Core
2024.8.3
Supervisor
2024.08.0
Operating System
13.1
Frontend
20240809.0
I cleared the cache and reloaded home assistant and noticed that the markdown CSS classes for non functional styling (.header-contained, .middle-contained etc) are no longer styled specifically.  They are all just single color divs with no detail as you can see in the image here:

I did the most recent update to HA-LCARS-2.3.0 at the same time as the Home Assistant update and then noticed these issues.

Hi,
this seems to be a duplicate of #103 and #104.
The root cause lies within card-mod (used by this theme): Issue here
I am also waiting for a fix :-)

I wonder if there would be a different way of implementing this skinning without depending on card-mod. The last commit on card-mod was 6 months ago and there doesn't seem to be a lot of activity over there anymore.

I still see the class there and I can target it using cardmod and add a pink border for example.  I think the issue is probably in the CSS itself and how it is selecting the pseudo elements.  It may not be applying the styles to the shadow root like it should be.  That's my guess.

Looking at the HTML: the class is not added to the ha-card:

Manually adding the middle class to the <ha-card> element fixes the look:

Please see https://github.com/thomasloven/lovelace-card-mod/issues/392
We have tested outside of HA-LCARS with the same result. card-mod is unable to target markdown cards on initial load of the page. If you subsequently call the reload themes action after a page has loaded (I mapped it to a button card), it will apply the class to the card.
Oddly, just applying a style to the card via card mod works every time.

Sorry about that, I forgot to add that the reloading of the theme does not help in this case (hence why I thought it was unrelated).
I've added the automation that was suggested in that card-mod ticket (to reload the theme every 10 seconds). This fixes the headers, but not the other cards.
I do see that there is a difference in behavior:
My header card is a simple markdown card. When the page is loaded, this gets the proper classes, however the style tag created by card-mod is empty.

This resolves itself by calling the reload themes action.
On the other hand, the other cards do not have the correct classes, but their style tag contains all necessary CSS.

This is not fixed by reloading the theme.
If this too is related to the card-mod issue, I'll gladly post this update there as well.


Accordions - Expanding an accordion item should collapse others

Current default behaviour of modus web components accordion is that it has mutually exclusive collapsible accordion items. We should provide the users an option to collapse existing items when expanding one,
example:
https://modus-bootstrap.trimble.com/components/accordions/?q=acc#collapsible-cards
https://modus-react-bootstrap.trimble.com/components/accordions/#CollapsibleCards

Close this issue until somebody needs it.


Add social badges

@code-asher how's that?

I think it looks awesome!

Our checks don't seem to run when they're from another repo. Gonna go ahead and merge this though.


mediabackup to Dropbox fails but dbbackup is working

I upgraded from v2.5.0 to v3.0.2 and since then mediabackup to Dropbox has not worked anymore.
I get ReadTimeoutError
Here are the logs :
2016-09-19 14:31:59 DEBUG: Backup size: 68.1 MiB
2016-09-19 14:31:59 INFO: Writing file to ssh-2016-09-19-143154.tar.gz
2016-09-19 14:31:59 DEBUG: Writing file ssh-2016-09-19-143154.tar.gz
2016-09-19 14:31:59 INFO: Starting new HTTPS connection (1): api.dropbox.com
2016-09-19 14:32:02 INFO: Starting new HTTPS connection (1): api-content.dropbox.com
2016-09-19 14:33:03 WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api-content.dropbox.com', port=443): Read timed out. (read timeout=60.0)",)': /1/files_put/auto/ssh-2016-09-19-143154.tar.gz?overwrite=False
2016-09-19 14:33:03 INFO: Starting new HTTPS connection (2): api-content.dropbox.com
2016-09-19 14:34:03 WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api-content.dropbox.com', port=443): Read timed out. (read timeout=60.0)",)': /1/files_put/auto/ssh-2016-09-19-143154.tar.gz?overwrite=False
2016-09-19 14:34:03 INFO: Starting new HTTPS connection (3): api-content.dropbox.com
2016-09-19 14:35:04 WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api-content.dropbox.com', port=443): Read timed out. (read timeout=60.0)",)': /1/files_put/auto/ssh-2016-09-19-143154.tar.gz?overwrite=False
2016-09-19 14:35:04 INFO: Starting new HTTPS connection (4): api-content.dropbox.com

dbbackup is working perfectly.
I have no idea whether the problem is coming from me, django-dbbackup, django-storages, or dropbox.
Can you please help ?
Thanks !

Hello @juliensalinas
Thank to report this issue.
Could you try to curl api-content.dropbox.com from your host ?

Thanks @ZuluPro for your answer.
curl api-content.dropbox.com returns {"error": "Not Found"}
and here is my console traceback when I launch python manage.py mediabackup :
Backup size: 77.9 MiB
Writing file to ssh-2016-09-19-191115.tar
Writing file ssh-2016-09-19-191115.tar
Writing file ssh-2016-09-19-191115.tar
Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/home/python2.7/site-packages/django/core/management/init.py", line 338, in execute_from_command_line
utility.execute()
File "/home/python2.7/site-packages/django/core/management/init.py", line 330, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/python2.7/site-packages/django/core/management/base.py", line 390, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/python2.7/site-packages/django/core/management/base.py", line 441, in execute
output = self.handle(*args, **options)
File "/home/python2.7/site-packages/dbbackup/utils.py", line 106, in wrapper
body = reporter.get_traceback_html()
File "/home/python2.7/site-packages/django/views/debug.py", line 384, in get_traceback_html
return t.render(c)
File "/home/python2.7/site-packages/django/template/base.py", line 209, in render
return self._render(context)
File "/home/python2.7/site-packages/django/template/base.py", line 201, in _render
return self.nodelist.render(context)
File "/home/python2.7/site-packages/django/template/base.py", line 903, in render
bit = self.render_node(node, context)
File "/home/python2.7/site-packages/django/template/debug.py", line 79, in render_node
return node.render(context)
File "/home/python2.7/site-packages/django/template/debug.py", line 89, in render
output = self.filter_expression.resolve(context)
File "/home/python2.7/site-packages/django/template/base.py", line 674, in resolve
new_obj = func(obj, *arg_vals)
File "/home/python2.7/site-packages/django/template/defaultfilters.py", line 771, in date
return formats.date_format(value, arg)
File "/home/python2.7/site-packages/django/utils/formats.py", line 136, in date_format
return dateformat.format(value, get_format(format or 'DATE_FORMAT', use_l10n=use_l10n))
File "/home/python2.7/site-packages/django/utils/formats.py", line 110, in get_format
for module in get_format_modules(lang):
File "/home/python2.7/site-packages/django/utils/formats.py", line 82, in get_format_modules
modules = _format_modules_cache.setdefault(lang, list(iter_format_modules(lang, settings.FORMAT_MODULE_PATH)))
File "/home/lib/python2.7/site-packages/django/utils/formats.py", line 51, in iter_format_modules
if not check_for_language(lang):
File "/home/python2.7/site-packages/django/utils/translation/init.py", line 181, in check_for_language
return _trans.check_for_language(lang_code)
File "/home/python2.7/site-packages/django/utils/lru_cache.py", line 125, in wrapper
result = user_function(*args, **kwds)
File "/home/python2.7/site-packages/django/utils/translation/trans_real.py", line 409, in check_for_language
if not language_code_re.search(lang_code):
TypeError: expected string or buffer

What is your Django version ?
Do you have a specific configuration ?

I am running Django 1.8
django-dbbackup 3.0.2
django-storages 1.5.1
dropbox 6.4.0
urllib3 1.16
requests 2.9.0
requests-oauthlib 0.6.2
Here are 3 other third-party apps I'm using in Django:
hijack
compat
localflavor
I am wondering whether the problem could come from urllib3 package ? Or requests ?
I tried to have a look to the django-dbbackup code as well as the django-storages code and it seems the dbbackup and mediabackup commands are very similar. So it is really surprising one is working and the other isn't...

Hi @juliensalinas, we are also facing the same issue. db backup works but media backup to dropbox is not working. Have you found a fix?
@ZuluPro our configuration is
Django 1.9
django-dbbackup 3.0.3
django-storages 1.5.1
dropbox 6.9.0
urllib3 1.18
requests 2.9.1
requests-oauthlib 0.6.0
Media backup in the local storage works great btw.

Hi @bahar, unfortunately I had to go back the previous version of dbbackup. I know it is not a sustaining solution though...
I spent quite a lot of time reviewing the django-dbbackup source code as well as django-storages and dropbox code, but I could not find where the problem is coming from.

Hello @ZuluPro,
Issue Scenario for our case:
While trying to upload media backup on Dropbox as normal.tar or compressed.tar.gz, we faced the same issue mentioned above.
After one hours of searching and testing, I have found an weird solution.
Solution:
We have updated the method named _create_tar of dbbackup/management/commands/mediabackup.py in following way:
We have used NamedTemporaryFile instead of default SpooledTemporaryFile like this way,
fileobj = tempfile.NamedTemporaryFile() And then in backup_mediafiles method we have updated the starred line,
if self.path is None:
**self.write_to_storage(open(tarball.name, 'rb'), filename)**
else:
self.storage.write_file(tarball, filename)
What we did, is just sending the file content rather sending the file object as a whole.
So, please take a look at our solution and let us know if it's feasible solution or not. If the solution is ok, can we just make a pull request so that it will help us to keep pace with your plugin.
Thanks in Advance

@juliensalinas
Really sorry for my latency and thank you very much for your troubleshooting. I started to review the 3 projects too, but haven't a lot of time, sorry...
The main difference is the following:

dbbackup try to write a `SpooledTemporaryFile``
mediabackup try to write a  SpooledTemporaryFile opened & closed by tarfile.open

I'll look at it soon, sorry again...
@shamilbuzz
tempfile.NamedTemporaryFile isn't used here, because we want to speed up operations. But does your solution upload to Dropbox ?

@ZuluPro [replying on behalf of @shamilbuzz, both of us are working in the same project] yes it does.

@ZuluPro : no worries, I do understand ;) Your tool is great anyway !

+1

I have the same issue. evaluated if adding a timeout to the storage options, but that was not accepted. what should I do?

I just learned that django-storages is using the deprecated Dropbox v1 API. is that known? can this be causing the problem? (ticket here https://github.com/jschneier/django-storages/issues/227)

alright, I ventured to fork and migrate (in a rush, don't ask for extensive testing) to dropbox v2. it worked for my simple needs. fork is here: https://github.com/patroqueeet/django-storages
pr to dbbackup maintainer was issued.

@patroqueeet
Thank your very much for this informations.
I'll fix it soon.

my bad. pr went to django-storages. sry for the typo.

@patroqueeet I'm in both ;)

ha! didn't know :)

Hello all,
DBBackup V3.0.4 should now fix this error.


add KubeStellar to CNCF landscape based on sandbox admission 12-19-2023

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

What am I doing wrong?

@Cmierly can you advise me on what I am doing wrong in this PR to cause a failure?

I don't have access to the logs but asked an admin, here's the error:
The issue: 7:56:11 PM: FATAL: No cached entry, and KubeStellar has issues with logo: kubestellar.svg, SVG file embeds a png. Please use a pure svg file

I don't have access to the logs but asked an admin, here's the error:
The issue: 7:56:11 PM: FATAL: No cached entry, and KubeStellar has issues with logo: kubestellar.svg, SVG file embeds a png. Please use a pure svg file

Thank you, I have updated with a different version of the SVG.  I hope this one is native.

Sweet, @castrojo - this will help us out with one missing project!

@castrojo @amye ready for merge

Alright, thanks for your patience on that svg thing, let's gooooooo!

@castrojo when should we expect to see the output on landscape.cncf.io?


Mount/Unmount button becomes disabled indefinitely

Technical data
WinSshFS

[x] stable
[ ] prerelease
[ ] custom build
Version: <IP_ADDRESS>

Dokan driver

[x] stable
[ ] prerelease
[ ] custom build
Version: Dokan 0.7.4

Enviroment

Windows version: 10
Architecture: x64

Support

Usage: personal - development
Your personal priority to solve this issue: high
Support ability: programming including .NET, can create pull request

Mount buttons for both the server virtual drive often remain disabled indefinitely after being clicked. I haven't found a consistent reason for it other than something about the mount operation being incorrectly configured. The rest of the GUI is not blocked, and seems to function normally. Changing the configuration, waiting for a while, and reopening the manager window do not re-enable either button. The only solution I've found so far is closing win-sshfs, killing its process in Task Manager, and restarting the app.

Same thing for me :(


Sorting is not applied on start, or always default sorting is applied on start.

Sorting is not applied on start, or always default sorting is applied on start.

VSCode Version: 1.31
OS Version: Windows 10

Steps to Reproduce:

Change "explorer.sortOrder" setting to "filesFirst", or other than default.
Close VSCode.
Open VScode, default sorting is applied. If we perform action, which trigger explorer refresh everything sorting back to our first choice.

Does this issue occur when all extensions are disabled?: Yes

dup of https://github.com/Microsoft/vscode/issues/68323

Yes, you are right it's duplicate. My apologies for that.

np, will be fixed in tomorrow's vscode insiders


About c++11 Using smart Pointers causes source code error protection problems

In this file onnxruntime_cxx_api.h
If I use version 1.12.x and below
char* LookupCustomMetadataMap(const char* key , OrtAllocator* allocator )const;
///< Wraps OrtApi :: ModelMetadataLookupCustomMetadataMap
This may allow the current source code to compile correctly
However, when the Onnxruntime version is greater than 1.13.0, the version number is different. For details, see the official website
In most cases, version number 6 will be used,1.12.x or later cannot be loaded effectively, and Android will run in a flash.
For instance, terminating with uncaught exception of type Ort::Exception: inference_session.cc:1086 LoadOrtModel The ORT format model version [6] is not supported this build 1.12.1
no member error occurs when I try to upgrade
Because the functions I mentioned above have been deprecated in the new version
// namespace wekws
/home/xiao/apk_example/android/app/src/main/cpp/kws/keyword_spotting.cc:38:35: error: no member named 'LookupCustomMetadataMap' in 'Ort::ModelMetadata'
AllocatedStringPtr LookupCustomMetadataMapAllocated(const char* key , OrtAllocator* allocator) const; ///< Wraps
OrtApi :: ModelMetadataLookupCustomMetadataMap
This made me very upset and tried to change the source code to
cache_dim_ = std::stoi(metadata.LookupCustomMetadataMapAllocated("cache_dim", allocator).get());
To my regret, an error that I suspect is out of memory was reported
terminating with uncaught exception of type Ort::Exception: Got invalid dimensions for input: input for the following indices
index: 2 Got: 80 Expected: 40
Sent from PPHub

)

The first image is Onnxruntime 1.12.x and below, and the second image is version 1.13.x and above


When use delay to export service, catch the exception and log it.

What is the purpose of the change
when use delay export service, the log info won't be print.
how to test it?
in dubbo-demo-xml-provider, modify the registry address to redis://<IP_ADDRESS>:6379?registry-type=service and run it.

Codecov Report

Merging #8584 (d426761) into 3.0 (0382a6b) will decrease coverage by 0.14%.
The diff coverage is 62.59%.

@@             Coverage Diff              @@
##                3.0    #8584      +/-   ##
============================================
- Coverage     63.00%   62.86%   -0.15%
+ Complexity      312      310       -2
============================================
  Files          1117     1117
  Lines         46754    46796      +42
  Branches       7038     7025      -13
============================================
- Hits          29459    29417      -42
- Misses        14026    14090      +64
- Partials       3269     3289      +20

Impacted Files
Coverage Δ

...ient/metadata/store/RemoteMetadataServiceImpl.java
70.42% <0.00%> (ø)

.../registry/zookeeper/ZookeeperServiceDiscovery.java
82.14% <0.00%> (+4.61%)
:arrow_up:

...nfig/bootstrap/builders/MetadataReportBuilder.java
92.68% <33.33%> (-4.69%)
:arrow_down:

.../report/support/AbstractMetadataReportFactory.java
63.15% <46.15%> (-10.18%)
:arrow_down:

.../apache/dubbo/config/bootstrap/DubboBootstrap.java
69.68% <46.66%> (-0.18%)
:arrow_down:

.../java/org/apache/dubbo/config/ReferenceConfig.java
75.22% <50.00%> (-1.94%)
:arrow_down:

...apache/dubbo/registry/ListenerRegistryWrapper.java
57.97% <50.00%> (-1.74%)
:arrow_down:

...ubbo/registry/support/AbstractRegistryFactory.java
70.88% <61.90%> (-5.51%)
:arrow_down:

...e/dubbo/registry/integration/RegistryProtocol.java
59.69% <71.42%> (-0.19%)
:arrow_down:

...registry/zookeeper/util/CuratorFrameworkUtils.java
84.78% <75.00%> (-8.25%)
:arrow_down:

... and 39 more

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 3c08fd2...d426761. Read the comment docs.


Support parameter SQLITE_CONFIG_MEMSTATUS in runtime

Is your feature request related to a problem? Please describe.
When enabling the parameter SQLITE_CONFIG_MEMSTATUS at compile time, the performance (read/write) is more than 2x slower
Describe the solution you'd like
I would like to have a way to disable this parameter at runtime as the native code already support it by sqlite3_config(SQLITE_CONFIG_MEMSTATUS,0)
Describe alternatives you've considered
Have different versions, two different jars. one compiled with this option enabled and one while it disabled
Additional context
Add any other context or screenshots about the feature request here.

We currently compile with -DSQLITE_DEFAULT_MEMSTATUS=0.
SQLite website mentions for SQLITE_CONFIG_MEMSTATUS:

Memory allocation statistics are enabled by default unless SQLite is compiled with SQLITE_DEFAULT_MEMSTATUS=0 in which case memory allocation statistics are disabled by default.


submission failed with: invalid & submission failed with: bad-cb-payee

I have 2 ghostrider coins on my miningcore.
Log gives me 2 errors when block found.
submission failed with: invalid & submission failed with: bad-cb-payee
How to fix if? Thank you

This is not a bug i think , use proper flag please


Complete Wiki

Wiki is substandard considering how much you have developed this module <3

You are not wrong about the wiki. But instead of remarking the obvious you could try to help :P
Any suggestions on what should be documented with priority?

Well, I'm dyslexic and do not have English as my mother tongue. But of course I can help but someone has to go through the text to fix grammar, spelling etc.


Rethink gcp package

Should we rename airflow.gcp to airflow.google?

Seems that Feng chose airflow.alphabet :)


[GHSA-5p52-j8pw-j7x5] Improper Restriction of XML External Entity Reference in bedework:bw-webdav

Updates

Affected products

Comments
According to Patch, vulnerability function did not exist before 4.0.1, and I have verified that this vulnerability could not be triggered before 4.0.1.

@SunBK201 do you have any evidence to support the change to affected versions for this advisory? The commit listed is not sufficient.

Reference:
https://sca.analysiscenter.veracode.com/vulnerability-database/security/xml-external-entity-xxe-/java/sid-8000/summary


GEOMESA-972 Remove DataStore Edit Panels

Removes datastore panels.
Adds some datastore parameters to the getParametersInfo.

Signed-off-by: Jim Hughes<EMAIL_ADDRESS>

Passwords are still plaintext fields for the Accumulo (GeoMesa) vector data store

@jdk2pq Thanks for the catch!  @anthonyccri don't merge:)

Looks good to me! Tested and working. The old version of the datastore also has:

writeThreads
queryThreads
recordThreads
collectStats
caching
for connection params. Do we want to keep those?

@jdk2pq @jnh5y those options are no longer present? we want to keep those.

The Kafka Data Store now has the zkPath automatically populated with "/geomesa/ds/kafka". Don't know if that's expected or not.

We have both an "Accumulo Coverage Format" and a "GeoMesa Coverage Format". I'm not sure of the differences between the two, but we should probably only have one. @AndrewAnnex, any input?

EDIT: Whoops, collectStats and caching are still there, now just checkboxes instead of input fields.

Is this PR ready to merge?

e775ca2895f574264c05079dbac0d19e3490391a


psycopg2 as a dependency

Installing queries via pip install psycopg2 as a dependency. However on many platforms now psycopg2-binary package must be used because of lack of PG dev packages available. For instance, AWS Lambda, Azure Functions etc.
Therefore I believe that either psycopg2 should be removed as a direct dependency and let the user manually add the approprate package or offer a queries-binary variant.

Same issue for me @gmr

@gmr what do you think about this Pull Request https://github.com/gmr/queries/pull/39 ?


WIP: release at beamline

Codecov Report

Merging #96 into master will decrease coverage by 0.29%.
The diff coverage is 63.15%.

@@            Coverage Diff            @@
##           master      #96     +/-   ##
=========================================
- Coverage   97.43%   97.14%   -0.3%
=========================================
  Files           6        6
  Lines        2261     2275     +14
  Branches      514      514
=========================================
+ Hits         2203     2210      +7
- Misses         26       33      +7
  Partials       32       32

Impacted Files
Coverage Δ

shed/event_streams.py
92.87% <63.15%> (-0.93%)
:arrow_down:

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 e3b005e...b86374f. Read the comment docs.


Square at the end of the info message

I tried another ending for the msg but a square was displayed, that's why I opened an issue in the Ionic repo
https://github.com/ionic-team/ionic/issues/16608

This popup doesn't exist anymore therefore no problem anymore ;)


md-table performance in IE issue #6727

Bug, feature request, or proposal:
Its a duplicate issue of  https://github.com/angular/material2/issues/6727. The original one was closed after some discussion.
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

Reproduction?

Hey WillShowell...
The Slowness issue is only coming in IE(tried on edge), otherwise, it works well for other browsers
i tried hosting the code in plunker and the response in IE is very slow(for 1000 records). Please follow below links. Also please recommend what approach to use in order to make this table responsive - Flex or Bootstarp. It seems like when we are trying to make this table responsive the slowness increases, especially in IE
https://run.plnkr.co/s93Shf2hMGUUcoBl/
https://plnkr.co/edit/LpCiKGSShFJw58eUYEwr?p=preview

Any updates of this Please?

@vikas-verma
Can you provid metrics of the slowness you are seeing?  Upon loading the example you gave, I was not able to see the slowness that you referenced, though it could be a perception issue.  I loaded the example on both Chrome and Internet Explorer.

Closing because no clarification was provided.


Remove expired blacklisted tokens from revoked tokens list

From what I can tell, keys (e.g. jwt-blacklist-userid) are paired with a list of revoked tokens and the key's expiration is based on the latest token's exp. This would make it possible (though probably unlikely) for this list to grow rather large for long-lived JWTs or in the case of frequent revocation (where a user's token is revoked before the previously revoked token for that same user has expired).
Also, given that the default expiration is based on the latest token's expiration and issued-at times, isn't it possible for a previously revoked token with a expiration that exceeds that of user.exp - user.iat to become re-validated?
A possible solution to this for redis is to use a sorted set and ZREMRANGEBYSCORE to remove expired revocation tokens prior to checking for their existence. And ZREVRANGEBYSCORE to ensure the expiration of the key matches that of the token with the latest expiration date.

This sounds like a worthy improvement to me! Would you have time to work on a PR?

Actually, the second issue you raise above seems actually an important dangerous issue.
It also likely affects purges, such that a purge will be wiped after the first revoked token reaches its expiration and is automatically removed. I am not currently relying on this library in production, but I think the suite of tests needs to be considerably expanded

After further reflection, it seems to me that purges are unlikely affected, as any additional revoked token should have been issued after the purge, and once that token has expired, presumably all purged tokens should also have expired.
Issue still affects single tokens being revoked in opposite order of issuance as per Palisand.
To be safe, I suggest storing individual revoked tokens and purges as separate keys. Working on PR for this.


subscript out of bounds

Dear,
I am getting this error. is there any idea how to fix it
Error in [<-(*tmp*, unassigned_cells, cell_type_num[i], value = GetScore(activation_prob_to_use,  :
subscript out of bounds
Best regards,
afshin

Hi, we have fixed the issue with the unassigned cells. Please try it again.

Hi
I've just received the same problem.
Error in [<-(tmp, unassigned_cells, cell_type_num[i], value = GetScore(activation_prob_to_use,  :    subscript out of bounds

If possible, could you please share your inputs so that we can take a look (input expression data and input signature matrix)?

yes, I take another data, but still have  'Error in current_pri_matrix[i, ] : subscript out of bounds'
[countmatrix.csv](https://github.com/plevritis-lab/CELESTA/files/1277
markers.csv
7180/countmatrix.csv)

markers.csv
countmatrix.csv

markers.csv countmatrix.csv

There are some minor errors in the input signature matrix. I have made the corresponding changes and highlighted them in a excel file attached. You can save it as a .csv file and run it with CELESTA. Please note that the first number in the lineage should represent the round number in the lineage, and the second number should represent the cell type number in the previous lineage. I managed running your data using the default parameters, which may need some tuning with respect to your images. I attached some results for your reference.
markers_modified.xlsx

Looks great
Many thanks!


use uniformed VERSION file for both scala and python

Use the same file to specify version for both scala (sbt) and python (setup.py).
It also fixes the python setup.py build on Mac using sbt in homebrew

Fancy ;) sure, lets do it

Fancy ;) sure, lets do it


Won't step beyond breakpoint

PHP version:  7.2.6
XDebug version:  php_xdebug-2.6.1-7.2-vc15-x86_64.dll
Adapter version: 1.12.6
Your launch.json:  {
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000
},
{
"name": "Launch currently open script",
"type": "php",
"request": "launch",
"program": "${file}",
"cwd": "${fileDirname}",
"port": 9000
}
]
}
XDebug php.ini config:
[xdebug]
zend_extension="c:/wamp64/bin/php/php7.2.6/ext/php_xdebug-2.6.1-7.2-vc15-x86_64.dll"
xdebug.remote_enable = 1
xdebug.profiler_enable = off
xdebug.profiler_enable_trigger = Off
xdebug.profiler_output_name = cachegrind.out.%t.%p
xdebug.profiler_output_dir ="c:/wamp64/tmp"
xdebug.show_local_vars=0
XDebug logfile (from setting xdebug.remote_log in php.ini):
Adapter logfile (from setting "log": true in launch.json):
Code snippet to reproduce: None

This is a very recent problem.  The debugger will stop at the breakpoint but will not continue.  Even if I tell it to just continue.  Step Over, Step Into and Step Out do nothing.  Restart works as does Stop.  This has been running like a champ.  I haven't debugged anything for a day or two but no longer than that.  I did restart VCS this morning due to a Win 10 update (ugh) so that may have started the problem.  Perhaps a recent update?
I also have PHPStorm and tried the exact same situation there and it works as expected.  In fact, I was able to find my issue.  So, that does act as a work around for right now but I'd rather keep using VSC and your great extension.
Sorry I don't have more information.  I know this can be annoying to find.  Perhaps others will see this and be able to add to the discussion.
Thank you!

Same here.

Same here. Windows 10, worked great for a while suddenly doesn't. Turned on logging and I can see the this in the logs when I push "step over". Nothing happens.
-> nextRequest { command: 'next',   arguments: { threadId: 1 },   type: 'request',   seq: 31 }

There is nothing I can do here without even having an XDebug logfile (see the issue template). Even if there was, it is unlikely I would be able to reproduce the problem, because I am not seeing this issue myself. If you care about this, why not debug it? Here are the instructions how you can step through the debugger itself: https://github.com/felixfbecker/vscode-php-debug#contributing

You can also download any previous version from the the releases page: https://github.com/felixfbecker/vscode-php-debug/releases
If you find one that works, you can look at what change was done in the following release that broke it, inspect the linked pull request and contact the author.

So, I tried your suggestion and attempted to install two previous
versions.  Not sure they ever installed properly since the extension
display still showed 1.12.6.  And, neither worked.  I understand that you
probably can't duplicate.  However, it would've been nice to get this
information earlier.  BTW, I did try the Devsense version (pay for) and it
did work properly.  And, I'm trying to decide if it's worth the $179 to
have a good debugger.  Probably is.
I wish I had the time to get into yours and figure out what's wrong.  I
appreciate all the effort you put into this.
On Wed, Nov 14, 2018 at 11:07 AM Felix Becker<EMAIL_ADDRESS>wrote:

You can also download any previous version from the the releases page:
https://github.com/felixfbecker/vscode-php-debug/releases
If you find one that works, you can look at what change was done in the
following release that broke it, inspect the linked pull request and
contact the author.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/felixfbecker/vscode-php-debug/issues/314#issuecomment-438717619,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGu5ERcqI70VSrBRmBmskFO12fesQ5njks5uvD-4gaJpZM4XWV1X
.

That’s funny because if you look at the source code in the devsense vsix you can see that it’s just this extension’s code obfuscated.

The instructions from VS Code were not very clear.  It's basically a two
step process.  Turn off the auto update and then install from a file that
you've downloaded.  Then when you reload the editor it doesn't just
overwrite the file you installed.
I tried both 1.12.5 and 1.12.4.  Both failed.  As I said in the original
post, I believe this was a change that was made to VS Code and not your
extension.  Unfortunately, it is effecting your extension.
Have you tried debugging anything?  I suspect any attempt would fail.  I'm
more than willing to create a simple test that I can send to you if you'd
like.
On Wed, Nov 14, 2018 at 12:05 PM Felix Becker<EMAIL_ADDRESS>wrote:

That’s funny because if you look at the source code in the devsense vsix
you can see that it’s just this extension’s code obfuscated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/felixfbecker/vscode-php-debug/issues/314#issuecomment-438739184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGu5EcQ__uGHUsymhX0d5Fzc8wKe8_jgks5uvE1HgaJpZM4XWV1X
.

Were you able to find a solution to this?

No.  I've got a copy of PHPStorm and I just use that.
On Fri, Nov 30, 2018 at 8:55 AM bryandandan<EMAIL_ADDRESS>wrote:

Were you able to find a solution to this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/felixfbecker/vscode-php-debug/issues/314#issuecomment-443210370,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGu5EeI-SHa1s_SW0JQ1npvZTT3z4GiXks5u0TjlgaJpZM4XWV1X
.

i also had this issue but just now i updated vs code to 1.30.0 and the problem disappeared. not sure if they are related

So, when I first started programming in 1977 I learned quickly that any problem I was sure was in the language I was using (Basic at that time) was probably with me.  Over the years, making sure I didn't forget that was a helpful way to solve problems I had.  Unfortunately, this time I seem to have forgotten that.
To get to the point, my problem was a variable in the Watch box that didn't exist.  My code would execute a require_once command which looked like it worked just fine but the next command, a curl_init stopped the debugger.  I couldn't get beyond.  I finally noticed that I was getting a error in the Variables -> Locals -> $errstr: "Undefined variable: subaccts".  Of course, I hadn't named that variable in anything I was running so it took me some time to realize that it was the Watch that was causing the problem.
IMHO, this shouldn't have caused the debugger to stop.  However, I suspect this has nothing to do with Felix's code but with VSC.
Bottom line, I found my problem.  Removed the Watch for $subaccts and the debugger works just fine.  A great way to start the New Year.
Hopefully this might help someone else who has run into the same problem.  Make sure you clear your Watches if you no longer need them and especially if the values aren't defined!
Thanks for hanging in there Felix.  Hope you have a great New Year.

Thanks @PhilMDev I removed my watch statements and now the debugger steps properly. I don't know that we should close this issue, as there's still a bug here obviously.

@wshaver - Glad this worked for you also!  I think we should let Felix comment on this, if he wants to.  Perhaps the issue should be moved to VSC instead?


[turborepo] prune removing env var dependencies from turbo.json

What version of Turborepo are you using?
1.7.1
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Describe the Bug
Since i upgraded turbo to 1.7.1, env variables are not listed as dependencies in the out/full/turbo.json  generated by the command prune with --docker argument.
Theese variables are set in the turbo.json at the root of my monorepo but in pipelines > env instead of globalEnv
If i downgrade to 1.7.0 it works again.
Also, i say that this file is now minified on prune.
Expected Behavior
The out/full/turbo.json contains my environment variables set in pipelines > env.
To Reproduce

Set at least one env variable in pipeline > env of your root turbo.json, like bellow:

  "gql#build": {
      "dependsOn": [
        "^build"
      ],
      "outputs": [
        "dist/**"
      ],
      "env": [
        "API_URL"
      ]
    },

Prune the project with pnpm turbo prune --docker
Show output out/full/turbo.json file

Reproduction Repo
No response

Not working on 1.7.4 for me too. Juste it stopped working from 1.7.1

@yangshun Can you provide a reproduction? I quick tested adding an env key to regular tasks and workspace specific tasks and I'm seeing them in the resulting turbo.json

@chris-olszewski you tagged the wrong person. Probably meant to tag @yovanoc

I'm on holidays so I can't do nothing for next 2 weeks. But if it's still a thing I can try to narrow to a minimal reproduction but actually this is a 50+ apps/packages monorepo so will see

I tried today to do a minimal reproduction without success. It's really weird. Can't find the thing that make me reproduce this

I'm also running into this issue right now in my Dockerfile which causes the subsequent turbo build to fail due to the turbo/no-undeclared-env-vars tslint rule:
RUN yarn global add turbo
COPY . .
RUN turbo prune --scope="app" --docker

# further down

RUN REACT_APP_ENV_VAR="..." yarn turbo run build --filter=app...

I'll try to come up with a minimal reproduction.

I was able to reproduce over here: https://github.com/wbobeirne/turbo-env-bug. I checked in the out directory so you can see it on github, but you should be able to pull and reproduce.

@wbobeirne, looking at your repro the only tasks in the original turbo.json that have non-empty env are app#build and app2#build. Both of these tasks are pruned from the turbo.json as those workspaces don't exist. If I add an "env": ["REACT_APP_ENV_VAR"] to the standard build task definition then I see that "env" key preserved along with it's value.

Ah yeah I see now that they're missing the @namespace/ prefix. However, their settings seem to get picked up for @namespace/app and @namespace/app2. Is there maybe some inconsistency of some systems allowing "fuzzy" matching of package names, and some systems requiring exact matches? Everything works in my real repo (not this reproduction) with those partial names.

Sorry for the large delay, this got lost in my notifications.
I quick tested your reproduction with turbo 1.13.4 and changing this line to @namespace/app#build and the env var was persisted to the out/full/turbo.json as expected.

Is there maybe some inconsistency of some systems allowing "fuzzy" matching of package names, and some systems requiring exact matches?

There was a behavior in turbo 1 where turbo run would infer a namespace e.g. turbo run build --filter=app would run build for @namespace/app, but nothing for configuration.
Closing this as provided reproduction passed when the config was changed. Please reopen if you have a reproduction that fails with a 1.13.4 or 2.0+


Add support for Sci-Lisp programming language.

Add Sci-Lisp programming language support.
Description

This is a new programming language.
I have checked CONTRIBUTING.md

※ This programming language has just been created and is almost completely unused in GItHub, but we intend to continue to actively develop and distribute it. Is it not appropriate to add to linguist?
Checklist:

[x] I am adding a new language.

[ ] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?type=code&q=NOT+is%3Afork+path%3A*.sl+(defn

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

example.sl

Sample license(s): MIT

[x] I have included a syntax highlighting grammar: [URL to grammar repo]

[x] I have added a color

Hex value: #413385
Rationale: Language's theme color is purple, so it is chosen.

[x] I have updated the heuristics to distinguish my language from others using the same extension.

Is it not appropriate to add to linguist?

Not yet if you search results are anything to go by. They suggest you're a very very very long way from meeting our usage requirements. Your search query probably needs refining as it's definitely picking up files that don't look like your (contrived?) samples.

@lildude
Thank you for your review!
Then I would like to close this PR, and when this language becomes popular, I would like to issue another PR.

I see that many PRs are marked as "pending popularity", no need to close this PR, right?

It's entirely up to you, but I'm leaning to closing this one for now given how low usage always to be.

OK, I would close this PR.


Uncaught ReferenceError: defineAppConfig is not defined     at defu.mjs:45:2

Environment

Operating System: Windows_NT
Node Version:     v18.12.1
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, i18n, image, content
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction

Create app.config.ts File. Following code is example in my project.

export default defineAppConfig({
  blogTags: [
    'Node Js',
    'Get Started',
    'Typescript',
    'Gatsby',
    'JavaScript',
    'Next',
    'Nuxt',
    'MDX'
  ]
})

Call useAppConfig(). const appConfig = useAppConfig()
Create any plugins

Describe the bug
There is a bug when I call useAppConfig() with plugins
Additional context
No response
Logs
No response

I am getting the same error when adding plugins to my project. There is a solution for it?

@delcantao
Hey! Could you kindly open a new issue with a reproduction? 🙏

It seems like I was using the outdated version. My project was in 3.1.1 and when I tried to reproduce it in version 3.1.2 to post the result here the error doesn't happen anymore.
I updated my project and it now works.


Fix typo in README

This change is

 No need to wait for LGTM on such small changes :)

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Oh I see, you can't squash and merge because not all checks have passed


A few bug fixing

For most part this consists in running multiprocessed behind a main closure as windows spawns subprocesses independently of multiprocessing

I squashed the commit history, it should be more readable now

Merged into branch  experimental. Thx!


Naming/FileName should exclude gemspec

When gems are nested, bundler recommends using dashes to separate namespaces (i.e., bundler-console becomes Bundler::Console). As such, the gemspec is supposed to be named bundler-console.gemspec. We should ignore gemspec files when running the Naming/FileName cop.
Expected behavior
It allows dashes in gemspec names.
Actual behavior
It fails with the Naming/FileName cop.
Steps to reproduce the problem
Have a gemspec with a dash in its name. Run rubocop.
RuboCop version
0.59.0 (using Parser <IP_ADDRESS>, running on ruby 2.5.1 x86_64-darwin15)

Also .pryrc fails with:

Naming/FileName: The name of this source file (.pryrc) should use snake_case.

Fix by https://github.com/rubocop-hq/rubocop/pull/6256

@bbatsov https://github.com/rubocop-hq/rubocop/pull/6256 fixed a false positive for dotfiles (i.e., .pryrc).
However, it did not exclude gemspec files including dashes.


poetry: 1.0.3 -> 1.0.5

Motivation for this change
Also bumped poetry2nix.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@jonringer poetry (top-level) updates does not touch pythonPackages at all.

I know :). aria2p imports "poetry", so it needs to consume as a package. the format = "pyproject"; will use the executable from pkgs

really what was happening was that a single interpreter version was being passed to both, which is also not what we want.

Missed https://github.com/NixOS/nixpkgs/pull/82990


Show template syntax errors when json parse fails

$ be stacker diff VPC
VPC:
Syntax error(s) in template.
/Users/jfhamlin/Projects/teststacks/templates/VPC.json:
expected hash key, not a hash close at line 15, column 9 [parse.c:556]

This LGTM - @kainosnoema or @maraca?

Excellent. LGTM as well.

Awesome sauce.
LGTM
On Sun, Sep 11, 2016 at 3:51 PM, Evan Owen<EMAIL_ADDRESS>wrote:

Excellent. LGTM as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cotap/stacker/pull/24#issuecomment-246210152, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAW1Rzr09UwQIJpX1mHh0rcvLM3GG5fCks5qpIX1gaJpZM4J6Dk8
.


Panic in firehose while processing block

Network: BSC Test net
Firehose version: v1.3.1
Geth: bsc-v1.1.18-fh2.1-2
Steps to reproduce - start firehose sync, try doing an RPC request from substream code which results in an error like this
WARN (rpc-cache) retrying RPCCall on non-deterministic RPC call error {"error": "rpc error (code -32000): missing trie node cba260375b8a093ff89fa569a257fddee8ecec5178b4590a9238b64d71950030 (path )", "at_block": "2720c990fc3b507cd22f08ed2804f1e6c8c324e04b32e2ce70819ca40795dfe6", "endpoint": "http://localhost:8547"} and then stop  substreams process(either ctrl-c or sigkill)
Firehose log during the panic: https://pastebin.com/HLzRjZ49
Probably this error should be handled more gracefully

Could those be somehow related?
https://github.com/graphprotocol/support/issues/74
https://github.com/graphprotocol/support/issues/75

This is an error coming from your RPC node. It means mainly that you connected a non-archive node as your --substreams-rpc-endpoints value and your RPC node is no able to handle the "archive" request.
This being a non-deterministic error returned from the RPC node we have no choice to retry forever, because the error could resolved if an archive node is hit, so there is no other error to mention.
We could improve the log however to detect what seems like a non-archive node.

I see the stack printed in your logs. Indeed, context canceled should not be printed as a panic. Seems unrelated to the actual problem described.

Due to my initial misunderstanding I was pointing it to an RPC exposed by geth(that's ran by firehouse)
But no matter what - panic is a bad thing... Why do we see a panic in the log when panic can be handled gracefully?
I also don't think panic originates in geth, logs say it's in Firehose/substreams, correct me if I'm wrong

I see the stack printed in your logs. Indeed, context canceled should not be printed as a panic. Seems unrelated to the actual problem described.
Initial problem described is a step that leads to this panic... I described the exact steps to cause it my first post

But no matter what - panic is a bad thing... Why do we see a panic in the log when panic can be handled gracefully?

It's handled, we just print it fully, I just mean it's an handled panic. No panic should happen, and in this particular case, context canceled should not have generated such problem, definitely a bug.

Due to my initial misunderstanding I was pointing it to an RPC exposed by geth(that's ran by firehose)

It must point an archive node

Initial problem described is a step that leads to this panic... I described the exact steps to cause the panic in my first post

With an archive node correctly configured, nothing around this should happen anymore


Input that is not a matrix; expected matrix (rank 2), got rank 1 array

Issue description
Cannot run keras model due to an error:
Caused by: org.deeplearning4j.exception.DL4JInvalidInputException: Input that is not a matrix; expected matrix (rank 2), got rank 1 array with shape [40]. Missing preprocessor or wrong input type? (layer name: dense, layer index: 0, layer type: DenseLayer)
Model had been implemented in python, exported and imported with following code:
        MultiLayerNetwork model = KerasModelImport.
                importKerasSequentialModelAndWeights("model");

Model seems to be loaded properly as model.summary() returns:
LayerName (LayerType)      nIn,nOut   TotalParams   ParamsShape
=======================================================================
dense (DenseLayer)         40,40      1,640         W:{40,40}, b:{1,40}
dense_1 (DenseLayer)       40,24      984           W:{40,24}, b:{1,24}
dense_2 (DenseLayer)       24,5       125           W:{24,5}, b:{1,5}
dense_2_loss (LossLayer)   -,-        0             -
-----------------------------------------------------------------------
            Total Parameters:  2,749
        Trainable Parameters:  2,749
           Frozen Parameters:  0

It seems like even though my model expects 1d array of 40 features the deeplearning4j library forces input to be 2d. Code I am using for testing the model:
for (int i=0; i<inputs; i++)
    features.putScalar(new int[] {i}, Math.random() < 0.5 ? 0 : 1);

System.out.println(model.output(features));

Please advise how can I overcome this issue.
Version Information
compile group: 'org.deeplearning4j', name: 'deeplearning4j-core', version: '1.0.0-beta5'
compile group: 'org.deeplearning4j', name: 'deeplearning4j-modelimport', version: '1.0.0-beta5'
compile group: 'org.nd4j', name: 'nd4j-native-platform', version: '1.0.0-beta5'

OS: Windows x64 & Ubuntu x64, no CUDA

DL4J (MLP) models always use 2d input, with a leading minibatch dimension - shape [minibatch, nIn]
For a single example, pass in an array with shape [1, nIn]


Add man_made features

The following are features which probably get included in buildings or landuse now, but we're not including many nodes (should be added to pois layer).
When it is in building layer, we should prefer the man_made=* value for the kind (over building=*).
Format is:
LINK to osm wiki, EXAMPLE to construct test, recommended MIN_ZOOM value, and COUNT of features.

[ ] man_made=communications_tower, example - pois, zoom 14. Around 3500 pois, 185 buildings (make sure man_made value is used over building value).
[ ] man_made=observatory, example - pois, zoom 13. Around 200 pois, 180 buildings (make sure man_made value is used over building value).
[ ] man_made=offshore_platform, example, and another in Europe where they are more common - pois, zoom 12. Around 290 pois, 40 landuse/building (man_made=offshore_platform), ignore.
[ ] man_made=silo, example - pois, zoom 16. Around 6800 pois, 40000 buildings.
[ ] man_made=telescope, example - pois, zoom 14. Around 700 pois, 400 buildings/landuse (ignore).
[ ] man_made=water_tower, example - pois, zoom 15. Around 40,000 pois, 15,000 buildings (ignore).

When there's a building polygon, we should put that in the buildings layer. If it also has POI tags, those get lifted off and added as a centroid in the pois layer. That logic should not change - this is just adding some new man_made types. Please do not change the existing POI / building logic.

Sounds good, thanks for clarification.

On Apr 4, 2016, at 08:22, Matt Amos<EMAIL_ADDRESS>wrote:
When there's a building polygon, we should put that in the buildings layer. If it also has POI tags, those get lifted off and added as a centroid in the pois layer. That logic should not change - this is just adding some new man_made types. Please do not change the existing POI / building logic.
―
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Skip silos, those are almost all buildings, and the shape alone should suffice.

(Adjusted a few of the zooms after validating with more test data.)

Looking good.


[Question/Feature Request] Execute class-validation inside transaction

I use this module in combination with NestJS. I have implemented custom validators to validate e.g. parameters (@Params) in a request supplied by the user. This in order to check whether entities exist before continuing running the body of a controller method. The issue I have is that this interaction by the user is executed in two transactions: one is started and committed by the class validator, the other is started and committed after this class validator upon running the service method (Controller -> Service -> update). This could result in a situation:

entity exists during execution of the class validator
enity gets deleted by someone elses
service cannot find entity and throws exception

Would it somehow be possible to have the validator and service share the same transaction?
The structure is as follows.
Class Validator entity-exists.validator.ts
@ValidatorConstraint({name: "entityExists", async: true})
@Injectable()
export class EntityExistsRule implements ValidatorConstraintInterface {
    constructor(
        private service: EntityService,
    ) {
    }

    // <-- tried adding @Transactional here
    async validate(id: number, args: ValidationArguments) {
        return this.service.exists(id); // <-- this exists call has a @Transactional decorator
    }

    defaultMessage(args: ValidationArguments) {
        return `Entity${args.value} not found`;
    }
}

export function EntityExists(validationOptions?: ValidationOptions) {
    return function (object: any, propertyName: string) {
        registerDecorator({
            name: "EntityExists",
            target: object.constructor,
            propertyName: propertyName,
            options: validationOptions,
            validator: EntityExistsRule,
        });
    };
}

Params get-entity-by-id.params.ts
export class GetEntityById {
    @EntityExists()
    @IsInt()
    id: number;
}

Controller entity.controller.ts
@Controller("entities/:id")
export class EntityController {
    constructor(
        private readonly entityService: EntityService,
    ) {
    }

    @Patch()
    // <-- tried adding @Transactional here
    async updateEntity(
        @Param() {houseId}: GetEntityByIdParams,
        @Body() body: UpdateEntityDto,
    ) {
        return this.entityService.update(id, body);
    }
}

Service entity.service.ts
export class EntityService {
    constructor(
        @InjectRepository(Entity) private repository: Repository<Entity>,
    ) {
    }

    @Transactional()
    exists(
        id: number
        updatedEntity: Partial<Entity>,
    ) {
        // this query is executed in the first transaction
        return this.repository.exists({
            where: {
                id,
            }
        });
    }

    @Transactional()
    async update(
        id: number
        updatedEntity: Partial<Entity>,
    ) {
        // this query is executed in a second transaction
        const entity = await this.repository.findOne({
            where: {
                id,
            }
        });

        // this could cause an exception, because entity could have been deleted between the Validator transaction and this transaction
        entity.field = "ok"

        // ...
    }
}

What I have considered

I have thought of adding a second exists call in the Service.update(), but that would make the class validator obsolete. I use the validators because class-validators generate a specific error response format.

Thank you for updating the module for the latest TypeORM version by the way!

@Migushthe2nd Sorry for the late reply.
With the current implementation of this library and pipes handling (ValidationPipe handles class-validator) in Nest.js it seems impossible to me to implement this feature.
The problem is that pipes are executed separately and before the controller code is executed:
https://github.com/nestjs/nest/blob/master/packages/core/router/router-execution-context.ts#L139-L173
Roughly it looks like this:
() => {
  const pipes = executePipes();

  const response = entityController.updateEntity();
}

With @Transactional() decorator for controller method it looks like:
() => {
  const pipes = executePipes();

  await runInTransaction(async () =>
    const response = entityController.updateEntity();
  }
}

To work with pipes in same transactional context we need to wrap code that execute both pipes and controller code inside runInTransaction.
We need something like that:
() => {
  await runInTransaction(async () =>
     const pipes = executePipes();

     const response = entityController.updateEntity();
  }
}

But so far I don't see any solution other than manually handling ValidationPipe inside controller method. It seems Nest.js doesn't offer anything to handle it.


Schematics improvements

Feature Request Description
Schematics for i18n is needed
Priority

[ ] Low
[ ] Medium
[x] High
[ ] Very High

We should add ng-add question for i18n setup just like in case of the common-css


Can't run project during production mode in vue-cli3

I had created a project using vue-cli3. It running smoothly on development mode without any error but in production mode ,page is not redirecting. It shows console error as follows:
Uncaught SyntaxError: Unexpected token <
vue-router.esm.js:1905 Error: Loading chunk chunk-ccb2 failed.
(missing: http://localhost:5000/default/dashboard/js/chunk-ccb2.8d835f25.js)
    at HTMLScriptElement.c (bootstrap:176)

What will be the issue in it? Anyone knows?

output: {
publicPath: '/', // FIX: Uncaught (in promise) Error: Loading chunk # failed. async
}

I had created a project using vue-cli3. It running smoothly on development mode without any error but in production mode ,page is not redirecting. It shows console error as follows:
Uncaught SyntaxError: Unexpected token <
vue-router.esm.js:1905 Error: Loading chunk chunk-ccb2 failed.
(missing: http://localhost:5000/default/dashboard/js/chunk-ccb2.8d835f25.js)
    at HTMLScriptElement.c (bootstrap:176)

What will be the issue in it? Anyone knows?

output: {
publicPath: '/', // FIX: Uncaught (in promise) Error: Loading chunk # failed. async
}
https://blog.francium.tech/vue-lazy-routes-loading-chunk-failed-9ee407bbd58

I had created a project using vue-cli3. It running smoothly on development mode without any error but in production mode ,page is not redirecting. It shows console error as follows:
Uncaught SyntaxError: Unexpected token <
vue-router.esm.js:1905 Error: Loading chunk chunk-ccb2 failed.
(missing: http://localhost:5000/default/dashboard/js/chunk-ccb2.8d835f25.js)
    at HTMLScriptElement.c (bootstrap:176)

What will be the issue in it? Anyone knows?

output: {
publicPath: '/', // FIX: Uncaught (in promise) Error: Loading chunk # failed. async
}
https://blog.francium.tech/vue-lazy-routes-loading-chunk-failed-9ee407bbd58


Html.GetEnumSelectList   do not render properly

before my code as below but not render properly. the control does not render the enums.

                <select asp-for="FormNoType" asp-items="Html.GetEnumSelectList<FormNoType>()" class="form-control"/>

And finally, I found that the html label  need to write  in the following form
<select asp-for="FormNoType" asp-items="Html.GetEnumSelectList<FormNoType>()" class="form-control"></select>

@NTaylorMullen - any idea why this might not be working right?

The reason why it's not rendering correctly is due to the self-closed select element. Our TagHelpers do not modify the self-closed nature of the tag.

@NTaylorMullen is that will be a enhancement in next version?

@yoyoys
If you're referring to this, we have no plans to change this behavior. We plan to add warnings to tooling and publishing that will tell you about this.

Our TagHelpers do not modify the self-closed nature of the tag.

@NTaylorMullen @Eilon is this answered? close?

Answered.


Add tel_field helper

Adds a helper for input type="tel". Currently only works in Safari but it is a standard HTML form element tag.

Thanks for the PR! However we already support type=tel using telephone_field and its shorter alias, phone_field, so this change is not needed.


NAT Punch for Players Behind CGNAT

Hello,
We have been using this library for our P2P game, including a NAT Punch server. It works perfectly for the most part, but we have been receiving some issues where players cannot punch through each other. From some of the players' descriptions/logs, it looks like they are behind CGNAT (not because of symmetric NAT, that part we made some tests).
I searched about NAT Punch through CGNAT. Some say it just can't possibly work, but without explaining why. If this really is the case, is there any chance we can detect player behind CGNAT with the API? (So far what I saw is player need to login to their router and check whether their router's WAN address is the same as their IP reported from a public website)
If punch could theoretically work with CGNAT, could this line in NatPunchModule.cs line 216 be related?
_socket.Ttl = 2;

I'm not exactly sure of the actual reason of sending a short-lived packet. Found something in http://www.uni-kassel.de/eecs/fileadmin/datas/fb16/Fachgebiete/UC/papers/HWW_11-SYNI.pdf (though it's talking about TCP punch) saying something related to ICMP Destination Unreachable. But that paper also mentioned that "In case of multi-level NAT with different routes the low TTL needs to be determined for each destination individually before the hole punching attempt begins. " So I'm wondering whether it may need a greater value for player behind CGNAT (essentially double NAT)?
Thank you very much!
Library version: 0.9
Framework: Unity
OS: Windows

TTL 2 is used for some routers that will block port if message reaches other side with closed port. TTL is restored after this one message. Also there is some improvements in master branch to NAT punching. Try latest master branch

Hi yeah I adopted the NAT punching improvements already - they were indeed necessary, before the fix punching packets often had issue reaching the other side.
My question is about whether TTL=2 is enough when player is in a double NAT (Carrier-Grade NAT), since it's one extra router before packet goes "out".


Error when try to build for production

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

OS and Version?
Ubuntu 18
Versions
Angular CLI: 7.0.6
Node: 10.6.0
Ngx-linkifyjs 1.2.1
Repro steps
I tried build for producction my Angular app and I got the following error

which version are you using ? I've just fixed that yesterday... The version 1.2.1 is the latest release!

I'm using version 1.2.1. I've just updated the library!

@AnthonyNahas Having same error.
and version is "ngx-linkifyjs": "^1.2.1",

Bug found! I will solve this issue and patch the library asap! Thanks for reporting 👍

I've just patched ngx-linkifyjs v1.2.2.
I would appreciate your feedback! Please feel free to reopen the issue if that problem doesn't disappear!

@AnthonyNahas it works! Thanks!


CROC Missing Havy Laser Turet

YASB (First Edition) Bug Report
This bug report filer is for First Edition X-Wing only!
Note: If you are experiencing problems with the permalink URL when you have Maul or Bomblet Generator in your list, this is a known issue.  For more information please see https://www.reddit.com/r/XWingTMG/comments/7c4q6h/yet_another_squad_builder_problems_with_maul/
Expected Behavior
State what you expect to happen here.
Actual Behavior
State what actually happens here.
Language
State what language translation you use.

I miss the Havy Laser Turet

Mmm, perfect.


Feature Request: An option to upgrade all formulae having a specific version increment

Feature
An option (e.g. --only=major|minor|patch) to upgrade all formulae with a major, minor, or patch version increment.
brew upgrade --only=major
brew upgrade --only=minor
brew upgrade --only=patch

To combine the upgrade of two version increment types, it would also be thinkable to combine or group these with a + sign or something similar.
brew upgrade --only=minor+patch

Description
Given there are formulae with a major, minor, or patch version increment after a brew update, then it would be useful to run a brew upgrade --only=minor which only upgrades formulae meeting this specific condition. Formulae not following semver have to be ignored, as it's impossible to determine their version increment.
Prerequisite
This feature is relevant to at least 90% of Homebrew users, which is something I can't identify, and formulae maintainers tag their formulae in a serious semver-ish way.
Motivation
This is somehow based on my habit to upgrade the formulae of the packages I've installed, which is scanning through the output of brew outdated, picking the ones having a minor version increment, and providing these to brew upgrade. Having such an option would reduce this, possibly only to me, inconvenient way of upgrading only the preferred packages.

This is a cool idea, though I don't know when I personally would ever want to upgrade major versions without minor and patch versions too. For myself, I would prefer a cumulative option:
brew upgrade --no-minor # patch
brew upgrade --no-major # patch+minor
brew upgrade            # patch+minor+major

Formulae require current versions of their dependencies, so brew upgrade --no-minor and  brew upgrade --no-major would both upgrade things that fell outside the attempted scope.

For the reason @ilovezfs mentioned: passing on this, sorry.