updated instructions for .env and compose files when using non standard port in redis

Redis might require passing port value in commands section (in compose file) when using non standard ports. Added instructions for achieving the same. Should not be a breaking change. Tested with both configs works as expected.

Is it possible for the user to only change the port in the .env file and not touch the docker compose file?

Unfortunately both files are required to be edited.
Here is the output when i try with just updated .env file:

[+] Running 33/33
✔ jesse 14 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled      132.3s
✔ 7d63c13d9b9b Pull complete                                  32.0s
✔ 6ad2a11ca37b Pull complete                                  31.6s
✔ 8076cdef4689 Pull complete                                  39.3s
✔ 0ba90f5a7dd0 Pull complete                                  37.4s
✔ 27c191df269f Pull complete                                  38.9s
✔ 18aabdb8a4ca Pull complete                                  62.6s
✔ b26edd9e0452 Pull complete                                  55.9s
✔ ba258fce2cfd Pull complete                                  48.7s
✔ 4aa46db1a17f Pull complete                                  61.9s
✔ bdd4c2bcdd9b Pull complete                                  61.6s
✔ 7195f0c15a62 Pull complete                                  63.1s
✔ f30dd2bf6594 Pull complete                                  98.1s
✔ edcd463cc2f3 Pull complete                                  71.4s
✔ 24204799b598 Pull complete                                  69.5s
✔ postgres 8 layers [⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled          123.0s
✔ e54d40fa3899 Pull complete                                  80.2s
✔ 63bba88902c4 Pull complete                                  80.2s
✔ 895cde69c46d Pull complete                                  95.1s
✔ f283b4aaa3dc Pull complete                                  81.6s
✔ e1dfb80fbe96 Pull complete                                  88.1s
✔ cab9af40886f Pull complete                                  89.9s
✔ 0008d7ccfed1 Pull complete                                  91.5s
✔ 5f53a735edbf Pull complete                                  98.7s
✔ redis 8 layers [⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled              53.1s
✔ 4abcf2066143 Pull complete                                   7.1s
✔ 2c3a1d240687 Pull complete                                   6.8s
✔ 643f361aa308 Pull complete                                   7.0s
✔ a693cf0e318c Pull complete                                  18.4s
✔ ade57efb0b22 Pull complete                                  19.0s
✔ 2fa2e1566407 Pull complete                                  18.4s
✔ 4f4fb700ef54 Pull complete                                  29.5s
✔ 4464e0709769 Pull complete                                  29.5s
[+] Running 4/3
✔ Network docker_default  Created                                0.1s
✔ Container redis         Created                                0.1s
✔ Container postgres      Created                                0.1s
✔ Container jesse         Created                                0.0s
Attaching to jesse, postgres, redis
redis     | 1:C 16 Apr 2024 09:36:45.880 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis     | 1:C 16 Apr 2024 09:36:45.880 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started
redis     | 1:C 16 Apr 2024 09:36:45.880 # Configuration loaded
redis     | 1:M 16 Apr 2024 09:36:45.880 * monotonic clock: POSIX clock_gettime
redis     | 1:M 16 Apr 2024 09:36:45.881 * Running mode=standalone, port=6379.
redis     | 1:M 16 Apr 2024 09:36:45.881 # Server initialized
redis     | 1:M 16 Apr 2024 09:36:45.881 * Ready to accept connections
postgres  |
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  |
postgres  | 2024-04-16 09:36:45.962 UTC [1] LOG:  starting PostgreSQL 14.11 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
postgres  | 2024-04-16 09:36:45.962 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres  | 2024-04-16 09:36:45.962 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2024-04-16 09:36:45.964 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2024-04-16 09:36:45.967 UTC [22] LOG:  database system was interrupted; last known up at 2023-07-27 15:14:25 UTC
postgres  | 2024-04-16 09:36:46.073 UTC [22] LOG:  database system was not properly shut down; automatic recovery in progress
postgres  | 2024-04-16 09:36:46.074 UTC [22] LOG:  redo starts at 0/1742AC0
postgres  | 2024-04-16 09:36:46.074 UTC [22] LOG:  invalid record length at 0/1742BA8: wanted 24, got 0
postgres  | 2024-04-16 09:36:46.074 UTC [22] LOG:  redo done at 0/1742B70 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
postgres  | 2024-04-16 09:36:46.083 UTC [1] LOG:  database system is ready to accept connections
jesse     | Traceback (most recent call last):
jesse     |   File "/usr/local/bin/jesse", line 33, in
jesse     |     sys.exit(load_entry_point('jesse', 'console_scripts', 'jesse')())
jesse     |   File "/usr/local/bin/jesse", line 25, in importlib_load_entry_point
jesse     |     return next(matches).load()
jesse     |   File "/usr/local/lib/python3.9/importlib/metadata.py", line 77, in load
jesse     |     module = import_module(match.group('module'))
jesse     |   File "/usr/local/lib/python3.9/importlib/init.py", line 127, in import_module
jesse     |     return _bootstrap._gcd_import(name[level:], package, level)
jesse     |   File "", line 1030, in _gcd_import
jesse     |   File "", line 1007, in _find_and_load
jesse     |   File "", line 972, in _find_and_load_unlocked
jesse     |   File "", line 228, in _call_with_frames_removed
jesse     |   File "", line 1030, in _gcd_import
jesse     |   File "", line 1007, in _find_and_load
jesse     |   File "", line 986, in _find_and_load_unlocked
jesse     |   File "", line 680, in _load_unlocked
jesse     |   File "", line 850, in exec_module
jesse     |   File "", line 228, in _call_with_frames_removed
jesse     |   File "/jesse-docker/jesse/init.py", line 13, in
jesse     |     from jesse.services.redis import async_redis, async_publish, sync_publish
jesse     |   File "/jesse-docker/jesse/services/redis.py", line 23, in
jesse     |     async_redis = asyncio.run(init_redis())
jesse     |   File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
jesse     |     return loop.run_until_complete(main)
jesse     |   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
jesse     |     return future.result()
jesse     |   File "/jesse-docker/jesse/services/redis.py", line 12, in init_redis
jesse     |     return await aioredis.create_redis_pool(
jesse     |   File "/usr/local/lib/python3.9/site-packages/aioredis/commands/init.py", line 188, in create_redis_pool
jesse     |     pool = await create_pool(address, db=db,
jesse     |   File "/usr/local/lib/python3.9/site-packages/aioredis/pool.py", line 58, in create_pool
jesse     |     await pool._fill_free(override_min=False)
jesse     |   File "/usr/local/lib/python3.9/site-packages/aioredis/pool.py", line 383, in _fill_free
jesse     |     conn = await self._create_new_connection(self._address)
jesse     |   File "/usr/local/lib/python3.9/site-packages/aioredis/connection.py", line 111, in create_connection
jesse     |     reader, writer = await asyncio.wait_for(open_connection(
jesse     |   File "/usr/local/lib/python3.9/asyncio/tasks.py", line 442, in wait_for
jesse     |     return await fut
jesse     |   File "/usr/local/lib/python3.9/site-packages/aioredis/stream.py", line 23, in open_connection
jesse     |     transport, _ = await get_event_loop().create_connection(
jesse     |   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
jesse     |     raise exceptions[0]
jesse     |   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
jesse     |     sock = await self._connect_sock(
jesse     |   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
jesse     |     await self.sock_connect(sock, address)
jesse     |   File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect
jesse     |     return await fut
jesse     |   File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb
jesse     |     raise OSError(err, f'Connect call failed {address}')
jesse     | ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 6380)
jesse exited with code 1

From what i have tested editing both files should also have no impact for both use cases of standard and non standard ports as the port value by default is always 6379. Additional info/command is included for folks that may want to run on non standard ports. This is very beneficial when there is already a redis instance running for some other application.


Redirect site to canonical URL

Redirect to Setting.site_url. Avoid issues with .herokuapp.com URLs still working even though site is in 'live' mode

Hey @jamiew! What do you mean by redirecting to Setting.site_url? And when do you want to redirect to it?


apps: add emacs support

finally amirite?

Yuck, gonna need to get a different highlight.js theme I think. This is barely readable:


.plt files recognized as "Gnuplot", but they're also unit test files for Prolog

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
As per the title.

Prolog is the most used logic programming language
SWI-Prolog is the most widespread compiler and framework for Prolog
.plt files are unit test files in SWI-Prolog (and maybe other Prolog systems)

I get "Gnuplot" for .plt files. I would like them to be listed as Prolog.
These are the current extensions for Prolog in languages.yml:

".pl"
".pro"
".prolog"
".yap"

Reference (point 3): https://www.swi-prolog.org/pldoc/doc_for?object=section('packages/plunit.html')
Expected language:

Prolog
Detected language:

Gnuplot

As you've already found, the reason for this is the .plt extension is not associated with Prolog and is only associated with Gnuplot, hence your files are being identified as Gnuplot. In order for these files to be identified as Prolog, the extension needs to be added to Prolog too. As there is already a language associated with this extension, we'd also need a heuristic to differentiate the two.
Please review the CONTRIBUTING.md and feel free to submit a pull request adding support.
Until then, you can use an override to force the language to Prolog.

I've used an override and it is okay with me for now (although I have to set it in every Prolog repo I create).
I'll consider asking for support as you say. Thanks.


Updates definition of events so its elements extend from Event

Updates events definition in Recipe, JRecipe and SRecipe
Updates existing code to comply to new requirement for events
Removes validation test that became irrelevant

@bekiroguz The requested Pull Request :)

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   80.68%   80.68%
=======================================
  Files          32       32
  Lines         849      849
  Branches       44       44
=======================================
  Hits          685      685
  Misses        164      164

Impacted Files
Coverage Δ

.../scala/com/ing/baker/compiler/CompiledRecipe.scala
90.9% <ø> (ø)
:arrow_up:

...c/main/scala/com/ing/baker/scala_api/SRecipe.scala
33.33% <0%> (ø)
:arrow_up:

...rc/main/scala/com/ing/baker/java_api/JRecipe.scala
68.75% <100%> (ø)
:arrow_up:

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 b7468d6...0ec286f. Read the comment docs.

Any news about this? This has been opened 5 days ago :angel:

Yay, happy me :+1:


Add CloseTx cost benchmark to tx-cost and similar test suites

I like our test suite is steadily growing, I am considering publishing it on our documentation website.

I like our test suite is steadily growing, I am considering publishing it on our documentation website.

What bit of it? The testing strategy?

@ch1bo No, the whole output of tests run. Like we publish benchmarks output, publishing tests output


Add GCP scope for microsegmentation policy

Description
Add GCP as a scope for microsegmentation policies.
Contribution Checklist:

[x] The pull request does not introduce any breaking changes
[x] I have read the contribution guidelines.
[ ] Create an issue and link to the pull request.

Attach Screenshots (Optional)

minor comment but looks good otherwise!


separate web-pages created for each nav-bar elements

here i have created separate webpages for each navbar items.
please review this: https://deploy-preview-188--drifty.netlify.app/

i think still we need to work on each nav elements like adding more features.

@anantnipunge Please resolve the branch conflicts.

Also, please make the animation as it is now. @anantnipunge

Ok @SaptarshiSarkar12

@anantnipunge Please resolve the branch conflicts and also fix this bug. The color of dark and light mode is same for more info section.

is there any tool in github or maybe external to see where this conflicts exists in the file? @SaptarshiSarkar12  i'm unable to find conflicts.

i have deleted about.css file, but still its showing it's a conflict file.

is there any tool in github or maybe external to see where this conflicts exists in the file? @SaptarshiSarkar12 i'm unable to find conflicts.

Sorry @anantnipunge I was busy, so I couldn't reply.
You can refer this : https://stackoverflow.com/a/49382772/19187952
This might work.

i have deleted about.css file, but still its showing it's a conflict file.
i think it will take time to resolve conflicts. once done, i will submit it soon.

at first you delete the conflicting files, pull the latest changes in your local repo and then, make the required changes. This should work.

Ok 😊

hello @SaptarshiSarkar12 please review the changes

hello @SaptarshiSarkar12 please review the changes

Please fix this for mobiles.

https://deploy-preview-188--drifty.netlify.app/index.html#contact

Please see if you can fix this bug @anantnipunge .

can you please check it now in your mobile. i made changes and reviewed for 4 to 5 devices on chrome, it's working well  and already it was also working well. please review this @SaptarshiSarkar12

@anantnipunge Now, after adding 5 </br> tags, the buttons no more coincide with the footer part in my mobile. I shall check on my laptop and inform you if it works fine. Also, I need to check other pages as well. I shall inform you then.

@anantnipunge Please fix this bug. Change the background colour as the dark mode button is not properly visible or you can change the color of the dark mode button, and add Download Here... as it is now. Also, make All releases option as a span as the website length will increase as the number of releases increases.

Sure i will submit it soon working on it

please check this do you like this?? @SaptarshiSarkar12

@anantnipunge The icon size in bout section is not the same s in the other sections. also, change the moon color to black / dark grey and keep the sun as tomato (it looks nice). also contribute page does not have distinct background colours for dark and light mode. also make all releases a span like Learn More.
Icon size in bout pages:

Icon size in other pages:

Contribute page in dark mode:

Contribute page in light mode:

Ya okay

made required changes. plz review this.
@SaptarshiSarkar12

working on darkmode toggle button to change color according to dark and light

@anantnipunge Please remove the shadow for light mode in contribute page. Also change the button colour for light mode (you may keep it white).

Please make this as span. It will display the releases only when it is clicked.

ok

ok

How far is the work completed @anantnipunge ?

Working on it. My exam and submission is there i will submit it soon.

@SaptarshiSarkar12

Working on it. My exam and submission is there i will submit it soon.

Ok you can push the changes after you are done. @anantnipunge

Sure 😊 no worries.

hello @SaptarshiSarkar12 , shadow is removed but i'm unable to provide required feature to the all release section.

hello @SaptarshiSarkar12 , shadow is removed but i'm unable to provide required feature to the all release section.
i think release section code is written somewhere else, i'm not getting that.

Ok shall check after my laptop is fixed. @anantnipunge . It might take a week.

Ya ok @SaptarshiSarkar12 . I will be available for other contribution anytime. 😊

Ya ok @SaptarshiSarkar12 . I will be available for other contribution anytime. 😊

👍

hello @SaptarshiSarkar12 , shadow is removed but i'm unable to provide required feature to the all release section.
i think release section code is written somewhere else, i'm not getting that.

@anantnipunge Yes, the releases section code is written in script.js file starting from line 161. Please check if you can make the All releases section just like Learn More text.

Ok i will see.

Ok i will see.

Have you seen it @anantnipunge ?

Sorry for the late. But till friday i'm so busy as there is my exam going on. Till the saturday i will update you for sure.

Okay 👍.

Thanks for understanding!

Thanks for understanding!

Welcome @anantnipunge 😄

If you are free, you may resume with the task. @anantnipunge

Ok @SaptarshiSarkar12  Apologize for such a long delay. I will look into the website today and will update you.

Ok @SaptarshiSarkar12 Apologize for such a long delay. I will look into the website today and will update you.

It's okay, take your time. Shall wait for your update, thank you :slightly_smiling_face: .

hello @SaptarshiSarkar12 , shadow is removed but i'm unable to provide required feature to the all release section.
i think release section code is written somewhere else, i'm not getting that.

@anantnipunge Yes, the releases section code is written in script.js file starting from line 161. Please check if you can make the All releases section just like Learn More text.

hello @SaptarshiSarkar12 i'm back to project.
i'm facing bit difficulties and errors about this section. but i think i can do it by resolving errors, just need some time till tomorrow night. if it is not possible from me i will update you and i will work on the new feature/ issue.

hello @SaptarshiSarkar12 , shadow is removed but i'm unable to provide required feature to the all release section.
i think release section code is written somewhere else, i'm not getting that.

@anantnipunge Yes, the releases section code is written in script.js file starting from line 161. Please check if you can make the All releases section just like Learn More text.

hello @SaptarshiSarkar12 i'm back to project. i'm facing bit difficulties and errors about this section. but i think i can do it by resolving errors, just need some time till tomorrow night. if it is not possible from me i will update you and i will work on the new feature/ issue.

Okay, @anantnipunge you can take your time.

@SaptarshiSarkar12 i'm facing issue here: can't resolve it. tried all the way but no success.😥

can you help me or should i work on another issue?

can you help me or should i work on another issue?

@anantnipunge I am a bit busy now, leave this for now. Work on making the different pages for each nav elements. Make sure that you remove all unnecessary CSS from each of the CSS files.

Ok exactly i was thinking abt this 😊. Will ipdate soon.

Ok exactly i was thinking abt this blush. Will ipdate soon.
@SaptarshiSarkar12 if you don't mind. can we have general discussion on discord?

Yeah, sure @anantnipunge .

Ok exactly i was thinking abt this blush. Will ipdate soon.
@SaptarshiSarkar12 if you don't mind. can we have general discussion on discord?

Yeah, sure @anantnipunge .

Ok 😇

@anantnipunge How much work is done? Have you removed unnecessary CSS lines from the files? Have you faced any problem? Feel free to share, shall try to help.

Ok exactly i was thinking abt this 😊. Will ipdate soon.
@SaptarshiSarkar12 if you don't mind. can we have general discussion on discord?

@anantnipunge Have you removed unnecessary CSS lines from the files? Has the task been completed? If you have any problem, let me know.

Closing this due to inactivity. Moreover, the website is going to be revamped via #196 , so this PR is no more required.


Program crash problem

Hi, thank you for sharing. But I have a problem. Can you give me some suggestions?
When I import an image, an error will appear after executing the following functions：
FLandscapeHeightmapInfo FLandscapeHeightmapFileFormat_Geotiff::Validate(const TCHAR* HeightmapFilename) const
Unhandled exception at0x00007FFF056515EF (UE4Editor-GeotiffLandscapeEditor.dll) (UE4Editor.exe 中）: 0xC0000005: Write into 0x000001DA568CACC0  An access conflict occurred。

Have you ever encountered this problem？
Or can you tell me which part of the code should be executed after the function is executed under normal circumstances？

Hm, haven't encountered this in a while. Does the error message state a line number where the crash occurs?
FLandscapeHeightmapFileFormat_Geotiff::Validate opens the file and performs some checks to verify it can be imported correctly. If that succeeds it should map the height values of the file to the landscape using the ::Import method.
A possible error source could be the geo-reference system of the file, as there are loads of them and i have concentrated on reference systems with units in meter.


Autocomplte doesn't work when it's inside dialog

Hello, thank you for making this wonderful repository! However, I've problem using Autocomplte within a dialog.
The bug is, the dropdown doesn't work. Instead of showing dropdown of places to choose from, it shows nothing at all. And when I press enter on input, it couldn't find the location.
This happens regardless of having another autocomplete on the main component (page itself). At first I thought it has to related to ref problem but couldn't quite really figure out.
To Reproduce
Steps to reproduce the behavior:

Create Autocomplete inside a dialog
Type in on the search
See error (no visual dropdown)

Expected behavior
I expected the dropdown to occurs.
Screenshots

Desktop (please complete the following information):

OS: MacOs
Browser: Chrome
Version: 103.0.5060.114 (Official Build) (arm64)

NPM

16.15.1

I'm using Nuxt3

Have you included places library? https://vue-map.netlify.app/components/autocomplete.html#load-google-maps-places

Yes I did, the autocomplete is working fine outside of the dialog.

Can you create a reproducible sandbox ?

same issue if autocomplete is called in a child component it's notworking, but it work in the parent component

actually after verification it works fine, the issue is when you use modal you have a z-index higher then the dropdown, the default google map dropdown index is 1000,
to solve this just override the google map class z-index
.pac-container{
z-index:9999999 !important;
}


Release 0.1.15

r? @jamesmunns
(rust_highfive has picked a reviewer for you, use r? to override)

@reitermarkus When the qemu-system supporting was added in https://github.com/rust-embedded/cross/pull/153 and https://github.com/rust-embedded/cross/pull/166 no documentation was provided... It would be great if some documentation could be add before a new release (I can't write it myself now, but maybe someone can).
By the way, thanks for moving the project forward, you are doing a great work!

Actually I'd rather prefer the good old fashioned ASCII quotes...

I think typographic quotes should be preferred for prose.

I can't write it myself now

I'm not using the cross run functionality myself so I can't either. And I don't think this should be blocking a new release, which is long overdue. Would be great if you could do it if you have time in the future.

When the qemu-system supporting was added in #153 and #166 no documentation was provided..

@malbarbo Yep sorry about that. The prs were dragging on for too long so didn't want to drag it further

bors r+

Actually I'd rather prefer the good old fashioned ASCII quotes...

I think typographic quotes should be preferred for prose.

These are english text files, often processed on the command line.  Until there's a very good reason to deviate I'd rather we stick to plain ASCII.

These are english text files

And that's exactly the reason why we should use quotes appropriate for English text.
This is a Markdown file, there is no good reason why this file would ever be processed by a tool which doesn't support UTF-8 or HTML escape codes.

Let's not waste time bike-shedding such small things, it's a release note, we can always modify it later

bors: r+

Let's not waste time bike-shedding such small things, it's a release note, we can always modify it later

No, we cannot. If it's released it will part of the release. Apart from that the point is not to include a change that was not there but to NOT make an incorrect change.

@Dylan-DPC Also I'd appreciate if you did not simply dismiss a members concern.


Autocompletion for emojis shortcode

Wherever emoji shortcodes are supported, autocompletion for them would be very nice to have. There are a lot of emojis, and most of their shortcodes are hard to guess.

This is probably closed by  #100. It is now possible to auto-complete shortcodes both in :react and the message bar.


Use framework2 for pilot tests

Recreated the Pilot testing infra based on the new test framework

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: louiscryan
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: nmittler
If they are not already assigned, you can assign the PR to them by writing /assign @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I've merged this PR directly. I'll fix the defer issues and other synchronization stuff. I want to get this in now, as I'll heavily focus on this refactoring next week to get it out of the door.


Cannot update mac address to an exsisting Interface

I am sharing an example below with an error while updating mac_address.
Interface Nic 1 is an existing interface without any mac address.
id used is interface id.
def update_device(device, mac_address, nic_name):
       nb = pynetbox.api(netbox_url, token=netbox_token)
       nic_id = nb.dcim.interfaces.get(device='server02', name='Nic 1').id
       print("Nic id: ",nic_id)

       mac_address = nb.dcim.interfaces.create(device='server202', name='Nic 1', mac_address= 'xx:xx:xx:xx:xx:xx', id= '21562')
       print(mac_address)
if __name__ == '__main__':
    update_device('server202', 'xx:xx:xx:xx:xx:xx', 'Nic 1')

output
Nic id:  21562
The request failed with code 400 Bad Request: {'device': ['Related objects must be referenced by numeric ID or by dictionary of attributes. Received an unrecognized value: server202'], 'type': ['This field is required.']}

Looking forward to fixing the mistake in my script

Worked like a charm @markkuleinio


inference failure with np.empty on bool type

import numpy as np
import numba
def f(n):
    return np.empty(n, np.bool)
print(f(10))
print(numba.njit(f)(10))

The last line fails during type inference.
Interestingly, it works if we change to a non-bool types.

Related to https://github.com/numba/numba/issues/1311. np.bool_ works as expected.


Specify topology for n-ary chain tests

Closes: #4038
Description

This PR refactors the bootstrapping of n-ary chain tests in order to use the specified topology. Only linear and fully connected are currently supported, and if the topology is not specified the linear one is used.
This also facilitates the implementation of new topologies if required.

PR author checklist:

[x] Added changelog entry, using unclog.
[ ] ~Added tests: integration (for Hermes) or unit/mock tests (for modules).~
[x] Linked to GitHub issue.
[x] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Excellent work! Any insights on how much time this buys us on CI?

The test which received the most impact is the packet forward test:

Gaia went from 1h30 to 1h11
Juno went from 1h31 to 1h06
Injective went from 1h18 to 58min

The other chains went down a few minutes only as the other main test impacted is the ternary_transfer
The remaining very long job is for simapp v8, as it runs the highest number of tests, 86 tests but does not run forward tests. So it went down only from 1h31 to 1h25.

Very nice, thanks for the report :)


docs: unify code block formatting

I noticed that when using the shell script markdown hint, the code blocks are broken on GitBook (example: https://docs.lightning.engineering/advanced-best-practices/lnd-docs/psbt).
This PR fixes all code blocks.
We also use @Roasbeef's favorite unicode character ⛰ as a the representation of the shell prompt.
Finally, a commit fixes up the contribution guide by using state of the art markdown syntax for intra document links.

We also use @Roasbeef's favorite unicode character mountain as a the representation of the shell prompt.

When reviewing this commit, I found this quite confusing.  The reason documentation uses $ as the shell prompt character is to distinguish commands run as an ordinary user account from those run as the root administrative user account, which are prefixed with #.  As an experienced Unix user looking at the updated documentation (or the older documents where @Roasbeef used this prefix previously), ⛰ looks to me like the name of a command or a shell alias or some sort of rendering artifact.  It does not give me the impression of being a shell prompt.
For any Unix newbies, I think this is worse.  They may not be aware of the $ convention, but if they search for or ask for help, they should soon get an answer.  Or, if they look closely at their default shell prompt, they may figure it out on their own.  But their confusion will be prolonged, perhaps by a significant amount, if they have to figure out why there's a mountain emoji in all their examples.
I believe y'alls goal in publishing this documentation is to help your users setup and use their software with a minimum amount of confusion.  I could just be a curmudgeon who doesn't like change, but it seems to me that using an alternative prompt character takes you further way from that goal.

We also use @Roasbeef's favorite unicode character mountain as a the representation of the shell prompt.

When reviewing this commit, I found this quite confusing.  The reason documentation uses $ as the shell prompt character is to distinguish commands run as an ordinary user account from those run as the root administrative user account, which are prefixed with #.  As an experienced Unix user looking at the updated documentation (or the older documents where @Roasbeef used this prefix previously), ⛰ looks to me like the name of a command or a shell alias or some sort of rendering artifact.  It does not give me the impression of being a shell prompt.
For any Unix newbies, I think this is worse.  They may not be aware of the $ convention, but if they search for or ask for help, they should soon get an answer.  Or, if they look closely at their default shell prompt, they may figure it out on their own.  But their confusion will be prolonged, perhaps by a significant amount, if they have to figure out why there's a mountain emoji in all their examples.
I believe y'alls goal in publishing this documentation is to help your users setup and use their software with a minimum amount of confusion.  I could just be a curmudgeon who doesn't like change, but it seems to me that using an alternative prompt character takes you further way from that goal.

I tend to agree with Harding here, it is more common in docs indeed. What
do you think, @guggero @roasbeef?
On Sat, 23 Jan 2021 at 16:43, David A. Harding<EMAIL_ADDRESS>wrote:

We also use @Roasbeef https://github.com/Roasbeef's favorite unicode
character mountain as a the representation of the shell prompt.
When reviewing this commit, I found this quite confusing. The reason
documentation uses $ as the shell prompt character is to distinguish
commands run as an ordinary user account from those run as the root
administrative user account, which are prefixed with #. As an experienced
Unix user looking at the updated documentation (or the older documents
where @Roasbeef https://github.com/Roasbeef used this prefix
previously), ⛰ looks to me like the name of a command or a shell alias or
some sort of rendering artifact. It does not give me the impression of
being a shell prompt.
For any Unix newbies, I think this is worse. They may not be aware of the
$ convention, but if they search for or ask for help, they should soon
get an answer. Or, if they look closely at their default shell prompt, they
may figure it out on their own. But their confusion will be prolonged,
perhaps by a significant amount, if they have to figure out why there's a
mountain emoji in all their examples.
I believe y'alls goal in publishing this documentation is to help your
users setup and use their software with a minimum amount of confusion. I
could just be a curmudgeon who doesn't like change, but it seems to me that
using an alternative prompt character takes you further way from that goal.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/pull/4926#issuecomment-766100931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4XLZHQCOFG275IGKJJB7DS3LVAJANCNFSM4WHNOE7Q
.

I tend to agree with Harding here, it is more common in docs indeed. What
do you think, @guggero @roasbeef?
On Sat, 23 Jan 2021 at 16:43, David A. Harding<EMAIL_ADDRESS>wrote:

We also use @Roasbeef https://github.com/Roasbeef's favorite unicode
character mountain as a the representation of the shell prompt.
When reviewing this commit, I found this quite confusing. The reason
documentation uses $ as the shell prompt character is to distinguish
commands run as an ordinary user account from those run as the root
administrative user account, which are prefixed with #. As an experienced
Unix user looking at the updated documentation (or the older documents
where @Roasbeef https://github.com/Roasbeef used this prefix
previously), ⛰ looks to me like the name of a command or a shell alias or
some sort of rendering artifact. It does not give me the impression of
being a shell prompt.
For any Unix newbies, I think this is worse. They may not be aware of the
$ convention, but if they search for or ask for help, they should soon
get an answer. Or, if they look closely at their default shell prompt, they
may figure it out on their own. But their confusion will be prolonged,
perhaps by a significant amount, if they have to figure out why there's a
mountain emoji in all their examples.
I believe y'alls goal in publishing this documentation is to help your
users setup and use their software with a minimum amount of confusion. I
could just be a curmudgeon who doesn't like change, but it seems to me that
using an alternative prompt character takes you further way from that goal.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/pull/4926#issuecomment-766100931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4XLZHQCOFG275IGKJJB7DS3LVAJANCNFSM4WHNOE7Q
.

I don't have a strong preference either way, my main concern is to use the same character everywhere.
It's an easy search/replace now, so whatever we end up choosing can be switched out quickly.

I don't have a strong preference either way, my main concern is to use the same character everywhere.
It's an easy search/replace now, so whatever we end up choosing can be switched out quickly.


Return 503 from ext_authz on network failures

Description: Return 503 from ext_authz on network failures
Risk Level: Low
Testing: CI
Docs Changes: n/a
Release Notes: n/a
Discussion thread: https://github.com/envoyproxy/envoy/issues/6119

@hanyu-liu thanks for this, but I think you need to put this in the doc too? WDYT @gsagula?

@hanyu-liu Thanks for this contribution. It looks good overall.

Does this only apply for gRPC authorization servers? I kind of have the same issue but for HTTP authorization servers, would really like to have a proper error code when auth. requests are failing and not a 403 (this issue/question is related to this https://github.com/envoyproxy/envoy/issues/5974)

Does this only apply for gRPC authorization servers? I kind of have the same issue but for HTTP authorization servers, would really like to have a proper error code when auth. requests are failing and not a 403 (this issue/question is related to this #5974)

This fix only applies to gRPC. But I can see the same issue for http.

I can look into this as soon as I finish some other priorities. Can't promise when.

@dio @gsagula any updates on it?


[Snyk] Upgrade vue-router from 3.6.5 to 4.5.0

Snyk has created this PR to upgrade vue-router from 3.6.5 to 4.5.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠ Warning: This PR contains major version upgrade(s), and may be a breaking change.

The recommended version is 91 versions ahead of your current version.

The recommended version was released a month ago.

[!IMPORTANT]

Warning: This PR contains a major version upgrade, and may be a breaking change.
Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery
Enhancements:

Upgrade vue-router to improve application performance and security.

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)

yarn.lock changes

Click to toggle table visibility

Name
Status
Previous
Current

@babel/eslint-parser

-
7.25.9

@nicolo-ribaudo/eslint-scope-5-internals

-
5.1.1-v1

@vue/devtools-api

-
6.6.4

babel-eslint

10.1.0
-

eslint-visitor-keys

1.3.0
2.1.0

express-rate-limit

-
7.5.0

vue-router

3.6.5
4.5.0


Duplicate file exception occurs when packing graal vm

Hi, I trying to use graal vm in my Scala project as JS engine.  When I run project in IDEA, everything goes well, but when I try to pack it using sbt assembly, file duplicate exception occurs:
If the project only add dependency of "org.graalvm.js" % "js-scriptengine" % "1.0.0-rc14", the error will be (ignore many output in ... ):
[error] java.lang.RuntimeException: deduplicate: different file contents found in the following:
[error] /Users/zhiruili/.ivy2/cache/org.graalvm.js/js-scriptengine/jars/js-scriptengine-1.0.0-rc14.jar:module-info.class
[error] /Users/zhiruili/.ivy2/cache/org.graalvm.sdk/graal-sdk/jars/graal-sdk-1.0.0-rc14.jar:module-info.class
......

If the project only add dependency of
"org.graalvm.js" % "js" % "1.0.0-rc14",
"org.graalvm.sdk" % "graal-sdk" % "1.0.0-rc14",
"org.graalvm.truffle" % "truffle-api" % "1.0.0-rc14",

the error will be (ignore many output in ... ):
[error] deduplicate: different file contents found in the following:
[error] /Users/zhiruili/.ivy2/cache/org.graalvm.js/js/jars/js-1.0.0-rc14.jar:module-info.java
[error] /Users/zhiruili/.ivy2/cache/org.graalvm.regex/regex/jars/regex-1.0.0-rc14.jar:module-info.java
[error] /Users/zhiruili/.ivy2/cache/org.graalvm.truffle/truffle-api/jars/truffle-api-1.0.0-rc14.jar:module-info.java
[error] /Users/zhiruili/.ivy2/cache/org.graalvm.sdk/graal-sdk/jars/graal-sdk-1.0.0-rc14.jar:module-info.java
[error]         at sbtassembly.Assembly$.applyStrategies(Assembly.scala:143)
...

Can anyone know how to solve this problem?

You need to set merge strategy for these dependencies
assembly / assemblyMergeStrategy := {
  case PathList("module-info.java") => MergeStrategy.discard
  case PathList("module-info.class") => MergeStrategy.discard
  case "META-INF/truffle/language" => MergeStrategy.discard
  case x =>
    val oldStrategy = (assemblyMergeStrategy in assembly).value
    oldStrategy(x)
}

This worked for my case with java 8 and Graal 19.0.0

Thanks！

I had to change
"META-INF/truffle/language" => MergeStrategy.discard to
"META-INF/truffle/language" => MergeStrategy.rename
I also had to create resources/META-INF/truffle/language file containing
language1.charactermimetype.0=application/javascript
language1.charactermimetype.1=application/javascript+module
language1.charactermimetype.2=text/javascript
language1.classname=com.oracle.truffle.js.lang.javascriptlanguage
language1.defaultmimetype=application/javascript
language1.dependentlanguage.0=regex
language1.filetypedetector0=com.oracle.truffle.js.lang.jsfiletypedetector
language1.id=js
language1.implementationname=graalvm javascript
language1.interactive=true
language1.internal=false
language1.name=javascript
language1.version=inherit

language2.charactermimetype.0=application/tregex
language2.classname=com.oracle.truffle.regex.regexlanguage
language2.id=regex
language2.implementationname=
language2.interactive=false
language2.internal=true
language2.name=regex
language2.version=0.1

otherwise library couldn't find languages

You need to set merge strategy for these dependencies
assembly / assemblyMergeStrategy := {
  case PathList("module-info.java") => MergeStrategy.discard
  case PathList("module-info.class") => MergeStrategy.discard
  case "META-INF/truffle/language" => MergeStrategy.discard
  case x =>
    val oldStrategy = (assemblyMergeStrategy in assembly).value
    oldStrategy(x)
}

This worked for my case with java 8 and Graal 19.0.0

This does not work.
[error] 1 error was encountered during merge
[error] 1 error was encountered during merge
[error] 1 error was encountered during merge
[info] Strategy 'discard' was applied to 48 files (Run the task at debug level to see details)
[info] Strategy 'rename' was applied to 7 files (Run the task at debug level to see details)
[error] java.lang.RuntimeException: deduplicate: different file contents found in the following:
[error] /Users/dave/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.12.0/jackson-annotations-2.12.0.jar:module-info.class
[error] /Users/dave/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.12.0/jackson-core-2.12.0.jar:module-info.class
[error] /Users/dave/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.12.0/jackson-databind-2.12.0.jar:module-info.class

This does not work.
[error] /Users/dave/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.12.0/jackson-annotations-2.12.0.jar:module-info.class
[error] /Users/dave/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.12.0/jackson-core-2.12.0.jar:module-info.class
[error] /Users/dave/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.12.0/jackson-databind-2.12.0.jar:module-info.class

Looks like it's not related to graalvm


Subchilds does not trigger detachedCallback in IE11 when removed through innerHTML

Found out today that there is a bug in IE11 MutationObserver  where childnodes to directly removed nodes are missing: https://connect.microsoft.com/IE/feedback/details/817132/ie-11-childnodes-are-missing-from-mutationobserver-mutations-removednodes-after-setting-innerhtml
I've put together a quick jsfiddle with an examle using the latest CDN-version of your polyfill: https://jsfiddle.net/qfmLvdyw/4/
Chrome, Firefox and Edge handles the case correctly as expected. Using .removeChild() instead of .innerHTML() seems to be working correctly in all browser. I couldn't find any information on the known caveats, so I'm not sure which approach you consider most valid. Should we look into a complete polyfill for MutationObserver or do you think it is something reasonable that the registerElement polyfill should handle?

I don't think I want to overload this repo with an overkilling MutationObserver polyfill only because IE11 is broken, it sounds more trouble than solution.
I rather force IE11 to use the fallback based on Mutation events like it is for older browsers, including IE9 and 8.
I'll try to use your test case and see what I can do to degrade IE11 and make it reliable.
Thanks so far.

Since the issues is regarding innerHTML, is it something that could be complemented to the innerHTML helper function instead? As I understand it only dealt with the createdCallback?

I need to investigate the issue first. I will try to find some time over the weekend. If you solve through the innerHTML helper though, please let me know.
Thanks.

On a side note, as I read through the source for the innerHTML helper function, it looks like there could be a potential side effect as it calls createdCallback before the children are moved to the upgraded element. Depending on the registered code in the callback, they may make an assumption that there are valid children during createdCallback.
So unless I missunderstand it, shouldn't the children be moved to the new element and after that call createdCallback?

The same logic could also apply that the createdCallback references the parentElement, meaning that the createdCallback should be the last thing that occurs.

can you eventually file a completely different bug? thank you

Sure thing, will see if I can fix a quick test case for it!

I ran into the same IE 11 + innerHTML + MutationObserver missing child nodes issue in another project and cooked up a workaround: https://github.com/javan/mutation-observer-inner-html-shim. Sharing in case it's useful here.

@javan Your fix looks awesome. Thanks a lot for sharing.

@javan do you include that before this poly, or after? and do you also use this file at all?
Thanks.

@WebReflection, a Google search for the MutationObserver IE 11 bug lead me here, and I haven't actually tested with this poly. I imagine my shim could be included before or after. It just needs to be included before any code that removes nested nodes using innerHTML.
Here's where I'm using it: https://github.com/stimulusjs/stimulus/pull/133

@javan a slightly different version of your fix went into 1.8 and there is a link to your original implementation. AFAIK we are both under MIT so I hope that is OK.
I haven't just included your fix because I already have most of the utilities/references in scope + I needed it in scope for the ponyfill anyway.
Please let me know if that's OK with you.

Totally 👌
Thanks for asking!

Great! Thanks both of you!


Add Specific License

The README says that this implementation is open source, but not specific license is provided. Would you mind adding a LICENSE file to clarify the terms that you'd like to share this code under?

I added MIT license. Thanks!


Update index.html

Should prepare css in folder

Thanks for contributing!
Why is this change needed exactly?


fix docs gen

Wait for circle to finish

See https://github.com/facebook/react-native/commit/eb3360b02ab82d20bc3c3f38f543b0d742598346#diff-f048d92ca0be679bc38d38147b311100R1581


Cannot subclass Context in v23

One can no longer subclass zmq.Context in a simple way. This worked in 22.x:
import zmq

class Context(zmq.Context):
    x = None
    def __init__(self, *args, x=7, **kwargs):
        self.x = x
        super().__init__(*args, **kwargs)

ctx = Context(x=6)

But raises an exception in 23.x:
Traceback (most recent call last):
  File "/home/bilbo/Documents/Scratch/980.py", line 9, in <module>
    ctx = Context(x=6)
  File "zmq/backend/cython/context.pyx", line 36, in zmq.backend.cython.context.Context.__cinit__
TypeError: __cinit__() got an unexpected keyword argument 'x'

This is due to this change, which modified the cython class for Context's __cinit__ method to no longer ignore additional keyword arguments passed to a subclass.
-     def __cinit__(self, int io_threads=1, size_t shadow=0, **kwargs):
+     def __cinit__(self, int io_threads=1, size_t shadow=0):

One can still make a subclass, but it now requires overriding __new__ to ensure the extra arguments aren't passed to the parent's __new__ (which is where __cinit__ gets called - I admit I'm a little hazy on the details). This seems to work:
class Context(zmq.Context):
    x = None
    def __new__(cls, *args, x=7, **kwargs):
        return super().__new__(cls, *args, **kwargs)

    def __init__(self, *args, x=7, **kwargs):
        self.x = x
        super().__init__(*args, **kwargs)

I can of course modify my subclasses as above,. but thought you might want to know about this in case you consider it a regression.

I think I was wrong about what belongs in cinit when I started many years back. #1718 moves this to __init__ so that subclasses can be more flexible in their signatures.


Use reference style link

Fix link in readme.md:105 and refactor all trunks.io links to reference link at the end.

Fix check failed, running trunk fmt and committing the changes.


mqtt-sn Gateway not working

I played around with the emq_sn plugin. I am trying to publish some messages using mqtt-sn-tools.
./mqtt-sn-pub -d -d -d -h <IP_ADDRESS> -p 1884 -q 0 -r  -t world -m hello
However as the below output shows, i do not receive  meaningful topic id:
2017-04-11 13:37:25 DEBUG Debug level is: 3.
2017-04-11 13:37:25 DEBUG Connecting...
2017-04-11 13:37:25 DEBUG Sending CONNECT packet...
2017-04-11 13:37:25 DEBUG Sending  24 bytes. Type=CONNECT on Socket: 3.
2017-04-11 13:37:25 DEBUG waiting for packet...
2017-04-11 13:37:25 DEBUG Received  3 bytes from <IP_ADDRESS>:1884. Type=CONNACK on Socket: 3
2017-04-11 13:37:25 DEBUG CONNACK return code: 0x00
2017-04-11 13:37:25 DEBUG Sending REGISTER packet...
2017-04-11 13:37:25 DEBUG Sending  11 bytes. Type=REGISTER on Socket: 3.
2017-04-11 13:37:25 DEBUG waiting for packet...
2017-04-11 13:37:25 DEBUG Received  7 bytes from <IP_ADDRESS>:1884. Type=REGACK on Socket: 3
2017-04-11 13:37:25 DEBUG REGACK return code: 0x00
2017-04-11 13:37:25 DEBUG REGACK topic id: 0x0000
2017-04-11 13:37:25 DEBUG Sending PUBLISH packet...
2017-04-11 13:37:25 DEBUG Sending  12 bytes. Type=PUBLISH on Socket: 3.
2017-04-11 13:37:25 DEBUG Disconnecting...
2017-04-11 13:37:25 DEBUG Sending DISCONNECT packet...
2017-04-11 13:37:25 DEBUG Sending   2 bytes. Type=DISCONNECT on Socket: 3.

Subscribing to a topic does also not work for me. I get a topic id that is unequal to 0x0000. So far so good. But no packages arrive at the subscriber:
mqtt-sn-sub -d -d -d -h <IP_ADDRESS> -p 1884  -V -t world
2017-04-11 13:44:47 DEBUG Verbose level is: 2.
2017-04-11 13:44:47 DEBUG Network timeout is: 5 seconds.
2017-04-11 13:44:47 DEBUG Connecting...
2017-04-11 13:44:47 DEBUG Sending CONNECT packet...
2017-04-11 13:44:47 DEBUG Sending  24 bytes. Type=CONNECT on Socket: 3.
2017-04-11 13:44:47 DEBUG waiting for packet...
2017-04-11 13:44:47 DEBUG Received  3 bytes from <IP_ADDRESS>:1884. Type=CONNACK on Socket: 3
2017-04-11 13:44:47 DEBUG CONNACK return code: 0x00
2017-04-11 13:44:47 DEBUG Sending SUBSCRIBE packet...
2017-04-11 13:44:47 DEBUG Sending  10 bytes. Type=SUBSCRIBE on Socket: 3.
2017-04-11 13:44:47 DEBUG waiting for packet...
2017-04-11 13:44:47 DEBUG Received  8 bytes from <IP_ADDRESS>:1884. Type=SUBACK on Socket: 3
2017-04-11 13:44:47 DEBUG SUBACK return code: 0x00
2017-04-11 13:44:47 DEBUG SUBACK topic id: 0x0001
2017-04-11 13:44:47 DEBUG Registering topic 0x0001: world
2017-04-11 13:44:57 DEBUG Sending PINGREQ packet...
2017-04-11 13:44:57 DEBUG Sending   2 bytes. Type=PINGREQ on Socket: 3.
2017-04-11 13:44:57 DEBUG waiting for packet...
2017-04-11 13:44:57 DEBUG Received  2 bytes from <IP_ADDRESS>:1884. Type=PINGRESP on Socket: 3
2017-04-11 13:45:07 DEBUG Sending PINGREQ packet...
2017-04-11 13:45:07 DEBUG Sending   2 bytes. Type=PINGREQ on Socket: 3.
2017-04-11 13:45:17 ERROR Keep alive error: timed out while waiting for a PUBLISH from gateway.

Even though i can see the client in the webinterface of the EMQ broker with the correct timeout set to 10, the client times out after the first successful PINGREQ.
Any idea?

@pritstift
mqtt-sn-pub has bug which use topicIdType=0 in publish message. Only topicIdType 1 or 2 is allowedin publish message. To get round this issue, you may use 'short topic'(2 byte topic), for example:
./mqtt-sn-pub -d -d -d -h <IP_ADDRESS> -p 1884 -q 0 -r -t Hi -m world
For the mqtt-sn subscribe issue, a bug is found. You may try the latest emq-sn develop branch, or wait for next official emqtt release.
You may try my fork of mqtt-sn-tools, which has fixed bugs mentioned above:
https://github.com/grutabow/mqtt-sn-tools

Okay. I fiddled a bit around with Version 2.1.1 and 2.1.2. Regarding the subscription everything seems to work.
I'm still having problems with publishing. Reading the MQTT-SN specification v.1.2  i found:

TopicIdType: indicates whether the field TopicId or TopicName included in this message contains a normal topic id (set to “0b00”), a pre-defined topic id (set to “0b01”), or a short topic name (set to “0b10”). The value “0b11” is reserved. Refer to sections 3 and 6.7 for the definition of the various types of topic ids.

Only for QoS = -1, the restriction on topicIdType = {1,2} is actually imposed, as far as i know.
Therefore, I don't think that TopicIdType = 0x00 is a bug in mqtt-sn-pub, when the topic is something long (i.e. more than 2 bytes) and qos ≠ -1. Please correct me if i am wrong at this point.
Furthermore EMQ is printing som errors when i publish a message with mqtt-sn (i don't know whether that is important for this topic):
16:34:23.218 [error] MQTT-SN(<IP_ADDRESS>:55355): UNEXPECTED INFO: emit_stats
16:34:23.218 [error] MQTT-SN(<IP_ADDRESS>:55355): UNEXPECTED INFO: {subscribe,[{<<"$client/mqtt-sn-tools-62490">>,1}]}

Regarding MQTT-SN specification v.1.2:
In "5.3.4 Flags", present a general description of TopidIdType:

TopicIdType: indicates whether the field TopicId or TopicName included in this message contains a normal topic id (set to “0b00”), a pre-defined topic id (set to “0b01”), or a short topic name (set to “0b10”). The value “0b11” is reserved. Refer to sections 3 and 6.7 for the definition of the various types of topic ids.

In "5.4.15 SUBSCRIBE", following rule is defined:

TopicIdType: indicates the type of information included at the end of the message, namely “0b00”topic name, “0b01” pre-defined topic id, “0b10” short topic name, and “0b11” reserved.

In "5.4.12 PUBLISH", following rule is defined:

TopicIdType: indicates the type of the topic id contained in the TopicId field.
TopicId: contains the topic id value or the short topic name for which the data is published.

That is to say:

SUBSCRIBE allows 3 types of topic: normal topic, pre-defined topic and short topic.
PUBLISH allows 2 types of topic: pre-defined topic and short topic.

As you know, PUBLISH is too short to held a normal topic which may be tens bytes long. As a tradeoff, MQTT-SN use a TopicId to represent such a long topic.
Till now, emq-sn does not support Qos -1 which may be implemented later.
These two 'UNEXPECTED INFO' are advanced features of emqttd, and emq-sn does not support them right now. Please ignore them which has no relation with basic subscribe/publish function.
Please don't be hesitate to report any problems you found.

Ok that clears some things up. Thanks!

Hi, I also have this problem.
All of the MQTT-SN implementation that I have tried so far interpret the specification so that PUBLISH accept 3 topic ID types:  normal topic name, pre-defined topic id and short topic name.  That is how RSMB, mosquitto, and the official eclipse/paho mqtt-sn libraries (originally written at IBM) work.
Would you please reconsider your interpretation of the specification, and implement the gateway in a manner that is compatible with all other available tools?  Otherwise it will create headaches for people trying EMQ for the first time.

@jpmzometa   Next official release will be compatible with "normal topic id" in publish message.

This change will be released in version 2.2-rc.1.


Couldn't check if release exists.

I have the same problem, after success running git push --tags, the release still return this message:
Error! Couldn't check if release exists.
And my node version is 7.4.0 and release version is 1.1.7.  Anyone could help me?
ps: I found the same issue which is already closed, cause I can not reopen that one, so create this new on.
#20

my mistake, my repo is a private one, and release does not have the right to access. closing


feat: add support for fieldmask to documentreference

Codecov Report

Merging #6 into master will decrease coverage by 0.41%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master       #6      +/-   ##
============================================
- Coverage     73.01%   72.59%   -0.42%
+ Complexity     1035      994      -41
============================================
  Files            64       64
  Lines          5443     5317     -126
  Branches        618      598      -20
============================================
- Hits           3974     3860     -114
+ Misses         1271     1267       -4
+ Partials        198      190       -8

Impacted Files
Coverage Δ
Complexity Δ

.../com/google/cloud/firestore/DocumentReference.java
73.56% <100.00%> (+0.30%)
32.00 <1.00> (+1.00)

...cloud/firestore/collection/ImmutableSortedMap.java
13.95% <0.00%> (-1.96%)
1.00% <0.00%> (ø%)

.../java/com/google/cloud/firestore/Precondition.java
68.18% <0.00%> (-1.39%)
12.00% <0.00%> (-3.00%)

...com/google/cloud/firestore/v1/FirestoreClient.java
76.28% <0.00%> (-0.86%)
31.00% <0.00%> (-6.00%)

...oogle/cloud/firestore/v1beta1/FirestoreClient.java
76.28% <0.00%> (-0.86%)
31.00% <0.00%> (-6.00%)

...a/com/google/cloud/firestore/FirestoreOptions.java
36.44% <0.00%> (-0.54%)
7.00% <0.00%> (ø%)

...ain/java/com/google/cloud/firestore/FieldMask.java
83.87% <0.00%> (-0.51%)
12.00% <0.00%> (-2.00%)

...loud/firestore/v1/stub/GrpcFirestoreAdminStub.java
94.32% <0.00%> (-0.46%)
15.00% <0.00%> (-1.00%)

...gle/cloud/firestore/v1/stub/GrpcFirestoreStub.java
96.04% <0.00%> (-0.36%)
19.00% <0.00%> (-1.00%)

...loud/firestore/v1beta1/stub/GrpcFirestoreStub.java
96.04% <0.00%> (-0.36%)
19.00% <0.00%> (-1.00%)

... and 10 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 9ae0d14...e9f55c3. Read the comment docs.


Inconsistent Linker flags and ICache usage

    // ideally these should be configurable
    const CONFIG_ESP32S3_INSTRUCTION_CACHE_SIZE: u32 = 0x4000; // ESP32S3_INSTRUCTION_CACHE_16KB
    const CONFIG_ESP32S3_ICACHE_ASSOCIATED_WAYS: u8 = 8; // ESP32S3_INSTRUCTION_CACHE_8WAYS
    const CONFIG_ESP32S3_INSTRUCTION_CACHE_LINE_SIZE: u8 = 32; // ESP32S3_INSTRUCTION_CACHE_LINE_32B

    // Configure the mode of instruction cache: cache size, cache line size.
    rom_config_instruction_cache_mode(
        CONFIG_ESP32S3_INSTRUCTION_CACHE_SIZE,
        CONFIG_ESP32S3_ICACHE_ASSOCIATED_WAYS,
        CONFIG_ESP32S3_INSTRUCTION_CACHE_LINE_SIZE,
    );

But in memory.x:
/* reserved for ICACHE */
RESERVE_ICACHE = 0x8000;

Yes, it should be configurable and the linker script should honor that configuration. Currently the linker script is configured for the "worst case"

If it's not currently configurable, should we just go ahead and align the two values? We may as well use the full 0x8000 as a cache if we're reserving it?

I guess yes, we can change the code to configure the whole reserved area as cache. However, that is only done when using PSRAM currently. Probably we should configure the cache for all chips always before running the user code

Yes, it should be configurable and the linker script should honor that configuration. Currently the linker script is configured for the "worst case"

I also think configuring the linker script for the "worst case" is what we need until it's configurable since we don't know what settings the 2nd stage bootloader is using (even we can know how the default bootloaders in espflash are built - users can bring their own)

Closed by #1169 (I think)


Add ability to add tasks

Is your feature request related to a problem? Please describe.
We need the ability to add tasks
Describe the solution you'd like
Use jquery in handling the add task input. Input should be checked, empty input is not allowed. Use Materialize toast for event messages. Use the method provided in adding the tasks, it is already in the code any you only have to call it to add the said task. Aside from adding make sure to refresh the list of uncompleted todos to reflect the added task. Use minimal, simple and straighforward logic as possible. If possible to decouple functions, you may do so.
Describe alternatives you've considered
N/A
Additional context
N/A

Hey, Can i do this?


Replace random function with randomIndex

Hi,
While experimenting with cm-chessboard, I found it useful to replace a separate random function in this example page with a random index like this:
const randomIndex = Math.floor(Math.random() * possibleMoves.length);
const randomMove = possibleMoves[randomIndex];

Since it's not explicitly mentioned when readers view the documentation page, it could potentially add a bit of confusion to first time users. Besides, the replacement makes inputHandler a more modular block of code (plug and play).

You are right, this makes it easier. Thanks for your contribution.

Thanks, my pleasure :-)


Cannot scan on linux

Perhaps I'm missing something, but the following doesn't work:
>>> import pywifi
>>> iface = pywifi.PyWiFi().interfaces()[0]
>>> iface.scan()
>>> iface.scan_results()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.5/site-packages/pywifi/iface.py", line 39, in scan_results
    return wifiutils.scan_results(self.__raw_obj)
  File "/usr/lib/python3.5/site-packages/pywifi/linux/wifiutils.py", line 48, in scan_results
    security += tmp_rsn['KeyMgmt']
TypeError: unsupported operand type(s) for +=: 'bool' and 'dbus.Array'

@awkman any idea?

Yes it doesn't. I just tried it too. Can u please help

I pull a new commit to fix this issue, please try it again.

Fixed!


Avoid exceptions caused by chat preview code

Fixes CommandAPI#305, where pre-1.19 servers would throw the following exception when a player joined or left:
[Server thread/ERROR]: Could not pass event PlayerJoinEvent to CommandAPI v8.4.1
org.bukkit.event.EventException: null
	at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:310) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:589) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:576) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.players.PlayerList.a(PlayerList.java:274) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.network.LoginListener.a(LoginListener.java:192) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.network.LoginListener.c(LoginListener.java:179) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.network.LoginListener.tick(LoginListener.java:74) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.network.NetworkManager.a(NetworkManager.java:246) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.network.ServerConnection.c(ServerConnection.java:172) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:1319) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.dedicated.DedicatedServer.b(DedicatedServer.java:436) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:1200) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.MinecraftServer.x(MinecraftServer.java:1027) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at net.minecraft.server.MinecraftServer.lambda$0(MinecraftServer.java:307) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	at java.lang.Thread.run(Thread.java:831) [?:?]
Caused by: java.lang.NoSuchMethodError: 'boolean org.bukkit.Bukkit.shouldSendChatPreviews()'
	at dev.jorel.commandapi.CommandAPI$1.onPlayerJoin(CommandAPI.java:206) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:567) ~[?:?]
	at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:306) ~[spigot-1.17.jar:3170-Spigot-a483d2c-ec116f6]
	... 15 more

This was fixed by moving the if(Bukkit.shouldSendChatPreviews()) code into the NMS_1_19_R1 methods that do the chat preview hooking and unhooking.
This also avoids some test code from throwing an uncaught exception on non-paper servers by surrounding it with a try/catch statement. This code example is planned to be removed anyway, but this allows testing to happen error-free on non-paper servers.

Closing PR due to my implementation in bd9c50e452d241d7dcbbe0c26b345dc6d9264812. I wanted to split the player listener because chat previewing shouldn't be under EventPriority.MONITOR, and the event listener shouldn't be registered unless it's possible to use chat previewing in the first place to save on server runtime performance.
I've (re)moved the chat preview test into the test suite.


help me, can't download the referit_splits.tar.bz2

According to link of download_data.sh . I can't download referit_splits.tar.bz2，can you offer it to me ？thanks a lot. I hope you can link to the network disk or send it to my email. Thank you again<EMAIL_ADDRESS>

me too

See https://github.com/BCV-Uniandes/DMS/issues/37#issuecomment-1276608715


ChatRoom

Added Chat Room, A GUI based application

@sonumahajan  I have added the GUI based Chat Room Please do Merge it.
Thankyou.

Follow me on Github

Hey there, I’ve also added one cpp program, Linear search Array, Please do merge it
From: Sonu @.>
Date: Monday, 11 October 2021 at 12:37 PM
To: sonumahajan/All_Program_helper @.>
Cc: AASTHA SINHA @.>, Author @.>
Subject: Re: [sonumahajan/All_Program_helper] ChatRoom (#215)
Merged #215https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsonumahajan%2FAll_Program_helper%2Fpull%2F215&data=04|01||b8cfabb7a83449c991e408d98c85c917|2c5bdaf48ff24bd9bd547c50ab219590|0|0|637695328501902508|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lyQk0FSmS4NITgHrYCfDz5RKHoaGGRKabKZTu3RomTM%3D&reserved=0 into main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsonumahajan%2FAll_Program_helper%2Fpull%2F215%23event-5441168055&data=04|01||b8cfabb7a83449c991e408d98c85c917|2c5bdaf48ff24bd9bd547c50ab219590|0|0|637695328501912463|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6g4n%2BJhnDxrpOa6bVQAXLmrz4EPoo2qqedcrVkgORs4%3D&reserved=0, or unsubscribehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAR3PYRVXYCR52TZEQQXTMU3UGKEK3ANCNFSM5FXQAYSA&data=04|01||b8cfabb7a83449c991e408d98c85c917|2c5bdaf48ff24bd9bd547c50ab219590|0|0|637695328501912463|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=NBXWz%2B1P%2FTIZWKypaUd6d7HC0BOLv4KlObH9v90W8Zw%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||b8cfabb7a83449c991e408d98c85c917|2c5bdaf48ff24bd9bd547c50ab219590|0|0|637695328501922421|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=fHfDGe27tS4iFt96F0UD557rhIPql0ivHns4GcRe3q4%3D&reserved=0 or Androidhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||b8cfabb7a83449c991e408d98c85c917|2c5bdaf48ff24bd9bd547c50ab219590|0|0|637695328501922421|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=uGQDmopcoWLT4A7SmdzbPGvCsyJt5Rvl1jn%2Bhl%2BdxDc%3D&reserved=0.


Spike: Define behavior for non-default woodwork logical types

We have good coverage for what I would call the "default" woodwork types like Double, Boolean, Datetime, NaturalLanguage but how should we handle non-default types that represent more specific data types, e.g.

Other logical types with string physical type -- Address, EmailAddress, Filepath, PersonFullName, PhoneNumber, URL
Other categorical types with category semantic tag -- PostalCode, SubRegionCode, CountryCode
LatLong
Ordinal
Timedelta

The outcome of this spike is a document detailing

How we currently handle these logical types -where does AutoMLSearch fail and where does it not.
A proposal for how to handle these types in AutoMLSearch, e.g. detect them and add specific components to handle them, modifying our existing components to handle them

After discussing this with @Cmancuso, we think EmailAddress and URL are highest priority.

Update - Using https://github.com/alteryx/evalml/issues/2444 to track work related to EmailAddress and URL

@dsherry @chukarsten I don't think this is as high priority anymore. We defined behavior for URL and EmailAddress which were the highest priority items.
I think we can table the other logical types until a pressing use case arrives. I also imagine we'll refine our thoughts based on @jeremyliweishih 's #2439 .
I'm removing from this sprint but down to talk about it!


⚠ Bofrost.at has degraded performance

In 9be44a2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1918 ms

Resolved: Bofrost.at performance has improved in a3223ec after 27 minutes.


enable redis and postgresql endpoint in virtual network for airflow

In current network module, we don't have the configurations to support Azure services in virtual network.

@catweisun -- Can you define what the requirements of the network module would have to be please.

This feature/code has fully migrated to GitLab.


Helm chart is missing tolerations on agent deployment

Describe the bug
Helm chart (version 7.3.2) supports tolerations value but only applies it on the deployment for regular pods, but not for agent.
Expected behavior
Tolerations are applied to all deployments or provide separate values to specify tolerations for each deployment.

Hi, any status updates on this? We are looking forward to using this feature. I see that #4256 is approved, anything blocking from merging that? Happy to contribute if required

@alexgervais will this do? https://github.com/emissary-ingress/emissary/pull/4880


Functional tests for  “Do it “ button of all detail items

Functional tests for  “Do it “ button of all detail items

https://github.com/fabric8io/fabric8-planner/pull/1003


ApplicationInsights:Sender [ 'Ingestion endpoint could not be reached 1245 consecutive times. There may be resulting telemetry loss. Most recent error:',

Hi,
I'm using<EMAIL_ADDRESS>for nodejs in azure appservice, using linux docker getting this error, and unable to see any data in appinsights, how to solve this ?
ApplicationInsights:Sender [ 'Ingestion endpoint could not be reached 1245 consecutive times. There may be resulting telemetry loss. Most recent error:',
2019-07-29T23:58:12.305328780Z   { Error: getaddrinfo EAI_AGAIN dc.services.visualstudio.com dc.services.visualstudio.com:443
2019-07-29T23:58:12.305336781Z       at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
2019-07-29T23:58:12.305341981Z     errno: 'EAI_AGAIN',
2019-07-29T23:58:12.305346781Z     code: 'EAI_AGAIN',
2019-07-29T23:58:12.305351481Z     syscall: 'getaddrinfo',
2019-07-29T23:58:12.305356281Z     hostname: 'dc.services.visualstudio.com',
2019-07-29T23:58:12.305361382Z     host: 'dc.services.visualstudio.com',
2019-07-29T23:58:12.305366182Z     port: 443 } ]

The problem was because the machine was not able to resolve the DNS to ip because of connectivity, unrelated to the sdk so closing it

It occurred to me when I didn't connect to the internet. Once I connected to the internet, it works well, so that means debugging the office addin can't be in an offline state? I also notice that Script Lab can't work well offline.


contrib: use env vars instead of yaml in systemd unit file

using environment vars simplifies the setup and avoids storing secrets on disk
use secure defaults: default to listen on localhost only

Reading credentials from files is usually safer than reading them from environment variables. You are able to set very restrictive permissions on files containing credentials, making sure that only the user who needs them can actually read them. You can also use mounts that are not backed by any disk storage (usually some form of tmpfs) if you want to avoid writing credentials to a disk.
Adding the documentation link to the service unit is a good idea, though. We can repurpose the PR for that, if you like.


Issue with flashing BFUS

Hi:
I am having issues flashing yi 1080p bfus. The cam is new.
Problem: camera boots up without doing the flash.

Windows 10 OS
I have tried two different Sandisk SD cards (16GB)
Formatting the SD via the YI App
Copied over the extracted files to root (Factory dir, newhome, home_y20gam.stage
Boot up the camera. Light goes yellow, makes a click sound, flashes blue and then goes solid blue. This takes about 1min.
Attempted to access CAM-IP:8080. No page displays but the camera is available via the YI APP.

Please could you advise?

Current cam firmware <IP_ADDRESS>.202007141512

I see Im on the wrong repo and should be on allWinner-2 repo. Closing this.


todoist-electron : App doesnt open browser while login

Describe the bug
A clear and concise description of what the bug is.
Browser doesn't pop up when clicked on "Continue in Browser" button
Steps To Reproduce
Steps to reproduce the behavior:

... Open the App
...Try logging in
...

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Do you have xdg-utils installed? Todoist uses xdg-open from your PATH to open a browser for login.

Does not work even with xdg-utils installed.
I found this post on the forum mentioning the issue
➜ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.75, NixOS, 23.11 (Tapir), 23.11.20240131.53fbe41`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`


resources: Add Loot Land

Loot Land
Etherscan link: https://etherscan.io/address/0x8575B7dFE18F4c9A872253bB4f557AD02e94C3A5
Website: https://opensea.io/collection/landproject
Loot Land are parts of the world in Loot metaverse. LAND is divided into parcels that are referenced using unique x,y cartesian coordinates. Feel free to use Loot Land in any way you want.

Could you please resolve the conflict?

@zhew2013  ok, all is ok an all checks have passed.

@zhew2013  updated

All LGTM after you fix the conflict.

sorry, I will close and reopen.


Unable to open files.

Description
What steps will reproduce the problem?

Open Spyder
Look for and select the .py file to open
Open the file

What is the expected output? What do you see instead?
The selected file in the editor, but instead it just shows an error and no change in the environment
Please provide any additional information below
Spyder 3, using Python 3.6, installed from the command line on ubuntu.
File "/usr/lib/python3/dist-packages/spyder/plugins/editor.py", line 1922, in load
current_editor = self.set_current_filename(filename, editorwindow)
File "/usr/lib/python3/dist-packages/spyder/plugins/editor.py", line 1501, in set_current_filename
return editorstack.set_current_filename(filename)
File "/usr/lib/python3/dist-packages/spyder/widgets/editor.py", line 1352, in set_current_filename
index = self.has_filename(filename)
File "/usr/lib/python3/dist-packages/spyder/widgets/editor.py", line 1346, in has_filename
if fixpath(filename) == fixpath(finfo.filename):
File "/usr/lib/python3/dist-packages/spyder/widgets/editor.py", line 1344, in
fixpath = lambda path: osp.normcase(osp.realpath(path))
File "/usr/lib/python3.6/posixpath.py", line 388, in realpath
path, ok = _joinrealpath(filename[:0], filename, {})
File "/usr/lib/python3.6/posixpath.py", line 422, in _joinrealpath
if not islink(newpath):
File "/usr/lib/python3.6/posixpath.py", line 171, in islink
st = os.lstat(path)
UnicodeEncodeError: 'ascii' codec can't encode character '\xdc' in position 41: ordinal not in range(128)
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.5
Qt Versions: 5.9.5, PyQt5 5.10.1 on Linux

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  None (NOK)
numpy >=1.7      :  1.14.3 (OK)
sphinx >=0.6.6   :  1.6.7 (OK)
rope >=0.9.4     :  0.10.5 (OK)
jedi >=0.9.0     :  0.11.1 (OK)
psutil >=0.3     :  5.4.2 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  None (NOK)
cython >=0.21    :  None (NOK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  5.5.0 (OK)
pylint >=0.25    :  1.8.4 (OK)

Thanks for reporting. What is the name of the file you're trying to open in Spyder?

Hey, it was called pegboard.py
On Mon, 30 Apr 2018, 23:40 Carlos Cordoba<EMAIL_ADDRESS>wrote:

Thanks for reporting. What is the name of the file you're trying to open
in Spyder?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/7044#issuecomment-385537176,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHqbpkiPRSU9oPC3gbUuyZzd4R1M1QpLks5tt4S1gaJpZM4Ts4uN
.

And what's the name of the directory this file is placed in?

~/github/UNI_AI/blatt01/
On Tue, 1 May 2018, 03:01 Carlos Cordoba<EMAIL_ADDRESS>wrote:

And what's the name of the directory this file is placed in?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/7044#issuecomment-385573244,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHqbpoKd4I2qHMD_VglLyZH4AnYNppO4ks5tt7PYgaJpZM4Ts4uN
.

I really don't understand why this is happening, sorry. What happens if you use Anaconda, instead of the packages provided by your distribution?

No worries. I just didn't really find Anaconda on Ubuntu, tried installing
Spyder from the main packages, from pip and from pip3 and none of them
worked. :(
On Tue, 1 May 2018, 17:41 Carlos Cordoba<EMAIL_ADDRESS>wrote:

I really don't understand why this is happening, sorry. What happens if
you use Anaconda, instead of the packages provided by your distribution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/7044#issuecomment-385703241,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHqbpsk_W3lfXwv07OGcAH-qNTfrVS9Zks5tuIIlgaJpZM4Ts4uN
.

Anaconda is a Python distribution:
https://www.anaconda.com/download/#linux

Will do! Thanks a lot :)
On Tue, 1 May 2018, 18:00 Carlos Cordoba<EMAIL_ADDRESS>wrote:

Anaconda is a Python distribution:
https://www.anaconda.com/download/#linux
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/7044#issuecomment-385708684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHqbpk0Eoyw3kKN2XNgdhsBGBVbnHh_Aks5tuIa5gaJpZM4Ts4uN
.

Hey @tuto193 , any news? If we don't hear from you, we'll assume you've fixed it and close this issue after a few more days. Thanks!

Hey!
Well, it is half-fixed. The whole process works... But only on Windows.
Linux still doesn't really respond much to it.
I have the latest version on both of them, and on Windows I'm even able to
use anaconda for autocomplete on VSCode, but on Linux it doesn't work
(neither Spyder nor the autocomplete)
On Wed, 9 May 2018, 07:28 C.A.M. Gerlach<EMAIL_ADDRESS>wrote:

Hey @tuto193 https://github.com/tuto193 , any news? If we don't hear
from you, we'll assume you've fixed it and close this issue after a few
more days. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/7044#issuecomment-387624221,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHqbpm5-7U8PJ__d-oZlx34SDjMCts9nks5twn6EgaJpZM4Ts4uN
.

Okay, thanks for the update.

on Linux it doesn't work

We're going to need to know a lot more detail about what doesn't work, how it fails, anything specific about your system, any error messages, what does work, etc. However, if it seems like its something with Anaconda itself rather than Spyder specifically, there's probably not much we can do from here as it wouldn't really be a Spyder issue.
Also, please try the steps listed in the Spyder Troubleshooting Guide, specifically the Basic First Aid and Emergency CPR sections, which resolve the great majority of Spyder installation issues.


Crash after pausing playback

Play any song, then press Pause. When the fade-out ends, the program crashes by reading from 0xffffffff.

As soon as debugging outputs are added, the bug doesn't replicate, indicating this is a tight threading issue.


project node not work

Describe the bug
it does not work
Link to the blitz that caused the error
https://stackblitz.com/edit/node-vfzjtl?file=app.js
Steps to reproduce
111111111
Expected behavior
11111111111
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
1
Platform
Browser name  = Chrome
Full version  = 102.0.5005.61
Major version = 102
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 76870396,
  "usedJSHeapSize": 69475796,
  "jsHeapSizeLimit": 888143872
}
Hash = 670e941965b7233a68cb924e1ca43e6a0f35bf71

Additional context
1

Closing this issue as it's unclear what goes wrong and none of the required details are filled in. Feel free to open a new issue and fill in all the necessary details so we have enough information to have a look ourselves. The more information we have, the better we can help you 🙏 .


[ruff] Teach autofix for used-dummy-variable about TypeVars etc. (RUF052)

Summary
For some bindings, such as assignments where the right-hand-side is a TypeVar constructor call, renaming the binding can result in invalid code. For example, this diff that renamer.rs might make would take code that mypy (or any other spec-compliant type checker) would have accepted, and turns it into something a type checker will reject:
  from typing import TypeVar

- _T = TypeVar("_T")
+ T = TypeVar("_T")

This is because the first argument to the TypeVar constructor must be the same as the variable the typevar is being bound to. Detecting this issue in general is impossible (there are lots of classes where this pattern is required), but it seems reasonable to special-case several standard-library classes where this pattern is required.
Fixes #14798
Test Plan
Added some more fixtures to RUF052 to check that the new logic in renamer.rs works as expected.

Do you know what editors do when you rename a variable that's a TypeVar declaration?

Do you know what editors do when you rename a variable that's a TypeVar declaration?

VSCode just does this, so we'll do a better job than them with this change ;)
-_T = TypeVar("_T")
+T = TypeVar("_T")


Update clippy.toml to work with recent versions of clippy

Without this, running cargo clippy on a crate that depends on mongodb = "0.3.12" fails with:
error: error reading Clippy's configuration file `/home/cdyer/.cargo/registry/src/github.com-1ecc6299db9ec823/mongodb-0.3.12/clippy.toml`: found deprecated field `cyclomatic-complexity-threshold`. Please use `cognitive-complexity-threshold` instead.

error: aborting due to previous error

error: Could not compile `mongodb`.

(Running rust 1.37)

Test failure seems pretty unrelated.

Fixed in another branch.


example values for parameters

add a new field: example values for parameters for all interfaces

use them to generate synthetic sentences for bootstrapping
as hints in slot filling ui

I was thinking we could actually store them inside the example sentences (with some new syntax), which would avoid changing the db schema.
But either way is fine.
One question: do we need more than one example value per argument?
I feel like we should ask for at least 3 or something. But I don't want to clutter the already ugly JSON editor...

@gcampax
I don't think that's a good idea to store them in examples:

one parameter appears in different examples
some parameters don't appear in the examples but should have example value
maybe there are some parameters you don't really want users to use them (like "link" in bing search), so in this case, no example value can indicate that we should not randomly generate value for that in synthetic sentences

I also feel like we should ask for more, but I don't know exactly why that will be useful though.
yeah, the current editor is truely ugly.... but consider we gonna have more things in the json, it probably won't be a good idea to use text editor to replace the buttons.

The fact that the same parameter appears in many examples is why I would like to see the values in the examples: it might be that different sentence structures yield different example values to keep the sentence "natural".
In fact, I'm thinking more about the grayed out suggestion text in slot filling than the synthetic sentences for paraphrasing, which have slightly different requirements, to make sure they get paraphrased to the right thing.
Now, I can't think of a specific example in my mind. It might be more prevalent in languages like German, where you have cases and you need different articles for different adjuncts. But I wonder how we would fare with those cases, or if those cases matter at all, given that we're talking about quoted strings / direct speech, not coreferences.
As for parameters that don't appear in the examples, the intention is that those parameters would benefit from contains/greater than/less than comparison instead of equal comparison. How would you choose the meaningful operators in that cases? Randomly as now?
I think asking for more will be useful just because it will give more variety to the turkers. More variety in the synthetic should cause more variety in the output. That's why we have usually more than one hardcoded value in the script.
In any case, the biggest argument for not putting them in the examples is that for synthetic generation we don't use the examples at all.
(And in fact I wonder if we should use the thingpedia examples instead of the confirmations, and have even more synthetic variety. Heck, maybe we would find even meaningful synthetic data to directly train on).
Are you going to work on this, or shall I do it? I can help you get started if you want.
(It's tricky because the storage format for the JSON is not exactly intuitive)

As it happens, we will need some form of this for the quote removal project (so far, it's been hacked)

Upping this. We need to work on this because we're pushing the quote-free models to prod, and many Thingpedia functions are not covered by the lists of parameter values we have.


feat: port Data.Complex.Exponential

Lean seems pretty buggy around line 1618. I can't figure out how to get it to even display the right tactic state.

Somebody who understands positivity can fix the extension for exp

@YaelDillies said they could fill in the positivity stuff on Wednesday. There's no huge rush to merge this, so I guess this can wait until Wednesday


ctrl-c no longer ends script run while paused at breakpoint for node debugging

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

VS Code Version: 1.76.2
OS Version: WIN(host),Linux(Remote)

Steps to Reproduce:

start debugging nodejs & run to breakpoint
select debug terminal, ctrl-c
the program run should end, but debug session should still be active (debug bar stays visible)

Connecting to a remote dev env - linux, from a win10 host.
In previous versions, hitting ctrl-c at a breakpoint would interrupt the process and exit the debug terminal to a prompt, allowing the script to be restarted and reconnect to debug session.
With the latest version the ctrl-c does not now interrupt while paused at a breakpoint, you need to press run to next breakpoint and then if enough time is between breakpoints the current script will then exit to prompt .
is this expected behavior?

/jsDebugLogs

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to<EMAIL_ADDRESS>

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


In operator from righthand side for SortedRange.

For consistency with #5629

I recall somebody saying that D's in operator is reserved for O(1)-algorithms. SortedRange.contains is O(log(n)).

@nordlow according to http://dlang.org/phobos/std_container (see at the end) in taking O(log(n)) is absolutely acceptable and expected.


v2.14.0

🐛 Bug Fixes

webpack

#7667 Fallback for empty chunk name

🚀 Features

vue-app

#7611 Add web-types.json for better code insight in WebStorm

cli

Install @nuxt/static by default

💅 Refactors

server

ExternalsWhitelist ~> externalsAllowlist

🇹 Types

general

#7670 Fix module options type

💖 Thanks to

Piotr Tomiak
Simon Tretter

Codecov Report

Merging #7691 into 2.x will decrease coverage by 0.04%.
The diff coverage is 34.78%.

@@            Coverage Diff             @@
##              2.x    #7691      +/-   ##
==========================================
- Coverage   70.18%   70.13%   -0.05%
==========================================
  Files          88       88
  Lines        3756     3764       +8
  Branches     1019     1025       +6
==========================================
+ Hits         2636     2640       +4
- Misses        911      913       +2
- Partials      209      211       +2

Flag
Coverage Δ

#unittests
70.13% <34.78%> (-0.05%)
:arrow_down:

Impacted Files
Coverage Δ

packages/vue-renderer/src/renderers/spa.js
0.00% <0.00%> (ø)

packages/webpack/src/config/client.js
61.17% <0.00%> (-1.48%)
:arrow_down:

packages/webpack/src/config/server.js
2.27% <0.00%> (ø)

packages/utils/src/route.js
96.66% <100.00%> (+0.09%)
:arrow_up:

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 e3821ba...124cb09. Read the comment docs.


Error running dotnet tutorial

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
'dotnet' is not recognized as an internal or external command error,

Have you closed and started a new command prompt after installing .NET?

Make sure that "C:\Program Files\dotnet" is part of the "path" system environment variable. If not, after adding, the problem should be resolved. :)


Belindas-closet-nextjs-Create Admin Page

_Added the code to the Admin Page
_The changed didn't show up on the Admin Page. Please help me to take a look at the code. Thank you

This is a bad branch. It was already used for PR https://github.com/SeattleColleges/belindas-closet-nextjs/pull/178. You can still use the code that you have for the admin-page but you should create a new branch from main so you have all the most recent changes. Open up a new PR from the new branch after you copy over your code.


/components/ClientAccountSummary

User story: as a client, I want to see a summary of my account

Outline set up


How to implement DefaultPartioner on HAProxy / nginx side?

@rs22
Do you have any insight on how to implement the DefaultPartioner from "/processors" on HAProxy or nginx?
Is it dynamical?

I haven't implemented this myself, but I think this should be possible with the OpenResty variant of nginx and its builtin lua scripting capabilities.
According to here and here you would mainly need a murmur2 function to be able to derive the partition id from the hash value of your keys.
There even is such a hash function built into nginx, which you could access using a small wrapper, but unfortunately it does not accept a seed, as is used by the DefaultPartitioner -- so probably you'll have to re-implement it in lua...
There might be alternatives to lua scripting as well, but the additional ability to make http requests, parse json and cache the mapping of partitions to stream processors in redis from within lua seem quite well suited for this use case.

Hi @Grabber, you can find an example implementation in our follow-up blog post and the corresponding repository.

@torbsto, thank you so much for sharing!
How do you update the partitions variable as soon as a new partition is available without having to re-init the nginx frequently?

Instead of scheduling the initalization with ngx.timer.at, you could use ngx.timer.every to continously update the mapping.
I haven't looked into it in detail, but there is also the option of a push-based approach. By implementing the StateListener interface, the applications can notify the proxy about changes whenever the state transitions from rebalancing to running.


Server crashes with an interface -> external storage -> autocrafting setup

Issue description:
Server crashes with an exception after setting up a "keep-in-stock" interface with crafting card and an external storage.
What you expected to happen:
The system crafts items to keep them in stock.
Steps to reproduce:
I have set an external storage to the bottom side of an Interface. Added a crafting card to the Interface and added some items to the external part to keep them in stock (processors and so on). The items show up in the grid. After I took some processors (half, richt click) from a grid, the server crashes and is now unable to start again. I was able to reproduce it in a creative world.
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>9
Refined Storage: 1.1.3

Does this issue occur on a server?
Yes. Modpack: "FTB HermitPack"
If a (crash)log is relevant for this issue, link it here:
http://pastebin.com/qQMRduMC

@raoulvdberge you fixed this in dev right? (#539)

Oh, seems like I overread that ticket. Sorry.

already fixed indeed