Area#removeRoomFromMap

Currently if you Area#addRoom() it adds the room to the floor map, but you if call Area#removeRoom, it removes it from the area, but leaves it in the floor map. Resulting in bad things, like crashes when a player tries to view adjacent rooms that lookup their implied exits through the floor map. Any suggestions on how this could better?

Code looks solid, I'd really like a unit test for it though

I have absolutely no idea how to do that, but I'm willing to try =) Any examples I can look at?

https://github.com/RanvierMUD/core/blob/master/test/unit/Attribute.js is a super simple example. I'm been really bad about adding tests so there aren't many but that's a good base to work off of, it's using mocha


Add @category tag

Sometimes globally-scoped things can get pretty cluttered, so I was wondering if you all can add a @category tag to sort documented objects into groups.

I actually did this as part of our TypeDoc implementation. If you're curious, see https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73. Alongside these changes, I updated our theme to sort our index page by category.
Excuse the organization, I usually push things to GitHub in batches.
The relevant changes are:
https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73#diff-0d149f9b1469c3c2f367a941af1b0945
https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73#diff-bd337a93cb6b55ec5c687ea8a327720e
https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73#diff-739b66d6abaf9c587a31ae9909a64903
https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73#diff-ebc8b0bc65bb184ea94b7734503a15f3
https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73#diff-09c50b8d3de6159296d213ab8664a22a
https://github.com/jonchardy/typedoc/commit/c12381beb66eda7f415f6d8673f4b355d8e91c73#diff-431f5355945bc08849278b194d39a0df

Pr? @jonchardy

Created PR #566. Feel free to take a look, discuss, and make any changes you feel will improve it.

Closed by #566

Regarding closing this bug: I didn't try the changes yet, but my understanding is that the PR which was pulled, according to its author "won't really do much without some accompanying changes to a theme". So I'm not sure this feature is really complete now. Is changing the theme documented?

@emmanueltouzery I think you are right. I'll reopen this. PRs are welcome to update the themes.

I opened #1158 to track multiple categories, closing this as there is base functionality for categories already, and the themes have been updated.


Permission denied error on model upload

Rasa version: 1.2.2
Rasa X version (if used & relevant): 0.20.1
Python version: 3.6
Operating system (windows, osx, ...): Ubuntu 18.04 and CentOS 7.6
Issue:
I am trying to upload a model via Rasa-x on two different installations, one on Ubuntu and the other on CentOS, both are throwing the same error of permission denied.
Error:
rasa-x_1           | Exception occurred while handling uri: 'http://localhost/api/projects/default/models?api_token=3518637d2fc37ac6eb504894e749e64105f5ca1e'
rasa-x_1           | Traceback (most recent call last):
rasa-x_1           |   File "/usr/local/lib/python3.6/shutil.py", line 550, in move
rasa-x_1           |     os.rename(src, real_dst)
rasa-x_1           | OSError: [Errno 18] Invalid cross-device link: '/tmp/tmpkpa18idb/model.tar.gz' -> '/app/models/model.tar.gz'
rasa-x_1           |
rasa-x_1           | During handling of the above exception, another exception occurred:
rasa-x_1           |
rasa-x_1           | Traceback (most recent call last):
rasa-x_1           |   File "/usr/local/lib/python3.6/site-packages/sanic/app.py", line 917, in handle_request
rasa-x_1           |     response = await response
rasa-x_1           |   File "/usr/local/lib/python3.6/site-packages/rasax/community/api/decorators.py", line 176, in decorated_function
rasa-x_1           |     return await await_and_return_response(args, kwargs, request)
rasa-x_1           |   File "/usr/local/lib/python3.6/site-packages/rasax/community/api/decorators.py", line 106, in await_and_return_response
rasa-x_1           |     response = await response
rasa-x_1           |   File "/usr/local/lib/python3.6/site-packages/rasax/community/api/blueprints/models.py", line 55, in upload_model
rasa-x_1           |     saved = await model_service.save(project_id, model_name, tpath)
rasa-x_1           |   File "/usr/local/lib/python3.6/site-packages/rasax/community/services/model_service.py", line 164, in save
rasa-x_1           |     stored_path = self._store_zipped_model(model_name, path)
rasa-x_1           |   File "/usr/local/lib/python3.6/site-packages/rasax/community/services/model_service.py", line 264, in _store_zipped_model
rasa-x_1           |     shutil.move(file_path, zpath)
rasa-x_1           |   File "/usr/local/lib/python3.6/shutil.py", line 564, in move
rasa-x_1           |     copy_function(src, real_dst)
rasa-x_1           |   File "/usr/local/lib/python3.6/shutil.py", line 263, in copy2
rasa-x_1           |     copyfile(src, dst, follow_symlinks=follow_symlinks)
rasa-x_1           |   File "/usr/local/lib/python3.6/shutil.py", line 121, in copyfile
rasa-x_1           |     with open(dst, 'wb') as fdst:
rasa-x_1           | PermissionError: [Errno 13] Permission denied: '/app/models/model.tar.gz'

Command or request that led to error:
Rasa X - Model Upload UI

Content of configuration file (config.yml) (if relevant):
# Configuration for Rasa NLU.
# https://rasa.com/docs/rasa/nlu/components/
language: "en"

pipeline:
- name: "SpacyNLP"
- name: "SpacyTokenizer"
- name: "SpacyFeaturizer"
- name: "RegexFeaturizer"
- name: "CRFEntityExtractor"
- name: "EntitySynonymMapper"
- name: "SklearnIntentClassifier"

# Configuration for Rasa Core.
# https://rasa.com/docs/rasa/core/policies/
policies:
  - name: MemoizationPolicy
  - name: KerasPolicy
  - name: MappingPolicy
  - name: TwoStageFallbackPolicy
    nlu_threshold: 0.3
    core_threshold: 0.3
    fallback_core_action_name: "action_default_fallback"
    fallback_nlu_action_name: "action_default_fallback"
    deny_suggestion_intent_name: "out_of_scope"

Content of domain file (domain.yml) (if relevant):
intents:
- impact
- inform
- greet
entities:
- above_below
- operation
- period
templates:
...
slots:
...

@erohmensing I think you have been looking into this right?

I've seen someone run into it. @dhwanils95 what does your deployment setup look like?

The rasa_x container already has a /tmp/ directory in it with some files. Would mounting a directory explicitly help? If you want I will try and check as soon as possible.
Thanks!

Hm I'm not quite sure, we're trying to debug the problem currently. How did you go about installing (manual, script, openshift instructions, etc.) and what is your deployment setup? I haven't reproduced it yet, that information could help.

I used both the script and manual installation. Since there is not automated script for CentOS, I did a manual installation using my custom action server which was replaced in the app service. I am using docker containers (Following are the versions I am using right now):
bitnami/rabbitmq    3.7.17              c79793bf81b2        3 days ago          202MB
rasa/rasa           1.2.3-full          1705d8edd332        11 days ago         2.7GB <--
python              3.6-slim            547f7a923796        12 days ago         174MB
rasa/rasa-x         stable              1cb17941f09d        2 weeks ago         1.45GB <--
rasa/nginx          stable              fe1f85d1cda2        2 weeks ago         87.1MB
rasa/duckling       latest              b7785de7a33a        3 months ago       5.55GB <--
rasa/logger         stable              515e477dcfc7        3 months ago        93.4MB

I did mount an empty directory to /tmp/ but there is no change. The issue is still there and I am not able to upload my model file.
Also in a unrelated context, where can I get your dockerfiles? I think I will be able to drastically reduce your image size since right now rasa, rasa-x and duckling are very bulky (as you can see in the above output), it will become a problem for a lot of people in the coming future for production deployments as everyone wants to reduce their resource consumption.
Let me know how I can help.
Thanks and regards.

Great, thank you for the info! As for the image size, there's already a PR about reducing the rasa size via multi-stage docker images. Feel free to give your input here: https://github.com/RasaHQ/rasa/pull/3332
The duckling dockerfile can be found here: https://github.com/RasaHQ/duckling/blob/master/Dockerfile

Great, I will look into it and see how I can help out.

@dhwanils95 are you sure that you ran the permission commands in step 10 (also 11?)
So for e.g. the models folder, you would run
sudo chgrp -R root /etc/rasa/models && sudo chmod -R 770 /etc/rasa/models

Hey @erohmensing ,
So, I had changed the permission of the directory but the docker user which ran the containers was different and was not in the group with the same permissions and hence it was throwing that error. Your solution pointed me to the right direction to check out that and I was able to solve it.
Closing the issue.
Thanks.

Hi @dhwanils95,
can you please specify what line and where did you add it to solve this issue?

Hi @dhwanils95,
can you please specify what line and where did you add it to solve this issue?

Hello @tpinju00,
It was not a line that I had to edit. The docker user which runs my docker containers did not have sufficient permissions even though I had changed the permissions of the directory as pointed out by @erohmensing. You will need to check to which groups does your docker user belongs to and whether that group has the required (770) rights on those directories.
Add your docker user to the group and you should be good to go.

@dhwanils95 , I did this:

sudo passwd root
added my pw
docker exec -u root -t -i CONTAINER_ID /bin/bash
su -  (typed in pw)
apt-get install sudo -y
sudo groupadd docker
sudo usermod -aG docker $USER

But the error still persists, any advice?


Chocolatey GUI does not start if the config folder is missing from C:\ProgramData\Chocolatey GUI

Checklist

[X] I have verified this is the correct repository for opening this issue.
[X] I have verified no other issues exist related to my problem.
[X] I have verified this is not an issue for a specific package.
[X] I have verified this issue is not security related.

What You Are Seeing?
While troubleshooting another issue, we noticed that after deleting the Config folder from C:\ProgramData\Chocolatey GUI and the data.db file from C:\Users\<USER>\AppData\Local\Chocolatey GUI that the data.db file was recreated in the Users directory, but the Config folder was not recreated in the ProgramData directory upon trying to start Chocolatey GUI.
Without the Config folder present, Chocolatey GUI will not start.
What is Expected?
If the Config folder is not present, Chocolatey GUI should recreate it upon startup.
How Did You Get This To Happen?

Deleted the Config folder from C:\ProgramData\Chocolatey GUI and the data.db file from C:\Users\<USER>\AppData\Local\Chocolatey GUI.
Tried to launch Chocolatey GUI from the Start menu and from the CLI and it would not start.
Witnessed the data.db file being recreated in the User directory, and noticed that the Config folder was not recreated in the ProgramData directory.

System Details

Operating System: Windows Server 2019
Windows PowerShell version: 5
Chocolatey CLI Version: 1.3.1
Chocolatey Licensed Extension version: 5.0.2
Chocolatey License type: Business

Installed Packages
Chocolatey GUI 1.1.2
Chocolatey GUI Extension 1.0.2

Output Log
N/A

Additional Context
Found while troubleshooting for #995

:tada: This issue has been resolved in version 2.1.1 :tada:
The release is available on:

GitHub Release
Chocolatey Package

Your GitReleaseManager bot :package: :rocket:


not issue, but about the function of "read all" button on web unit UI

I want to know the function about "read all" button on web unit UI.
I intuitively thought that web UI would display the latest values about parameters of a CWMP after clicking the button of "read all".
But web UI did not display the latest values about parameters sent from the CWMP but display the previous values.
I had checked out the values in database(acs) of mysql and figured out that the values was not updated though FreeACS received the latest values in inform message sent from the CWMP.
I checked the below url that your team shared.
https://github.com/freeacs/readme/blob/master/Fusion System Parameter Reference.pdf
Above document says "read all" button is for DEBUG.
I do not understand what it means.
Please let me know how to use for DEBUG through using "read all" button.
In detail, when clicking "read all" button, the CWMP processed below steps.

A CWMP based on EasyCwmp receives the kick of it from stun.
: Does the CWMP should reply to the stun message sent from FreeACS's stun server as stun response additionally?

The CWMP sends inform message to FreeACS as the event of "6 CONNECTION-REQUEST".
: 6 CONNECTION-REQUEST event, is it the event for inform message triggered from "read all" button? Do I have to use other event.

Above inform message includes the latest values of parameters on the CWMP.

FreeACS does not update the latest values of parameters of the CWMP to database.
: is it correct?

Anyone here to help?

I will check it tomorrow on our production.

Ok, I've checked source code.

I must check it with device.
Yes, you are initiate connection from ACS

Read All is only for debug. Values are stored in cache. Provisioning must be in "REGULAR" mode to write changes to database. Devices doing Inform requests periodically with "2 PERIODIC" event code to ACS. Then ACS responses with GetParameterValues Request to read all parameters.


Source URL Not allowed with V3 and multiple sources

Hi,
Somehow the logic on  IMGPROXY_ALLOWED_SOURCES is broken with the update on V3.
We are having multiple allowed sources, for example:
    IMGPROXY_ALLOWED_SOURCES: s3://,https://*.example.com/,https://example.com/
upgrading to v3 (Docker:latest) we are getting "Source URL is not allowed" as error message in the logs.
Downgrade to docker:v2 and delivery works as expected.
is there a config change needed or something else on multiple sources when upgrading to v3?
Thanks!

Hey @shakalandy!
Just checked your example, and everything works as expected. If you could reveal your real IMGPROXY_ALLOWED_SOURCES value and the URL that doesn't work, I'd help you better.

Hey @DarthSim,
The Domains are api.kruu.com and kruu.com.
The following error appears in V3 in the log:
{"log":"\u001b[33mWARNING\u001b[0m [2021-12-03T15:25:25Z] Completed in 427.258µs /RwB0fpLImw6vOCql_0pvePKtARF-N2OrlrTzhM_TMhU/fit/400/276/sm/0/aHR0cHM6Ly9hcGkua3J1dS5jb20vdXBsb2Fkcy9sb2NhdGlvbi1tZWRpYXMvMi81LzMvVHJhZm93ZXJrLU1hbm5oZWltLXJ1bmRlLVRpc2NoZS5qcGc  \u001b[1mrequest_id\u001b[0m=1DC4fBh3rxW-OQabUEXfA \u001b[1mmethod\u001b[0m=GET \u001b[1mstatus\u001b[0m=404 \u001b[1mclient_ip\u001b[0m=\"2a00:fb8:2077:3000:2833:7e81:e52b:93e2\" \u001b[1merror\u001b[0m=\"Source URL is not allowed: ~+x\\xd3M\\xbb\\xeaɴhttps://api.kruu.com/uploads/location-medias/2/5/3/Trafowerk-Mannheim-runde-Tische.jpg\"\n","stream":"stderr","time":"2021-12-03T15:25:25.918031557Z"}

Everything works fine with the same settings and just a downgrade to imgproxy:v2 docker image.
Will try again and may the force be with you.

You're using the deprecated basic URL format. v3 supports only the advanced one: https://docs.imgproxy.net/generating_the_url

Oh narf, thanks very much!
not an easy error message for that, but this will be it.
closing.

Yeah, I probably should add some kind of detection of the basic format with a proper error message. Too many users are confused with this.


add(front-back):forgot password

Add a forgot password function

Working forgot password function in 1f751f1454a5bbc630f448cf2131f11cf76359d8 and 2678555a3517b1647ecb2e847b9c41a9223f6ad6
--> Need refacto
--> Need check security

Secure and fix forgot-password in --> f8eff4280f84623ac60561e92212f06b3a7e29a5 & 01cbac1d6b66e54e79abc795d745053fc0c8f0c9
--> Need to add limiter and type test on endpoint
--> Need to refacto

Fully working forgot password --> b354344fedc1a39875ace2a08c942075d393915c
--> Need refacto


Unicode problem, can't remove item with an accent

Hello, I have a problem to remove an item in the dock that the name is 'Mise à jour de logiciels'.  This is the french translation for the software Munki.
This is the command that I do and the result:
bash-3.2$ dockutil --remove 'Mise à jour de logiciels' --allhomes
/usr/local/bin/dockutil:605: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if dock_item['tile-data'].get('file-label') == item_name:
/usr/local/bin/dockutil:616: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if dock_item['tile-data'].get('file-label') == item_name:
item Mise à jour de logiciels was not found in /Users/pilier/Library/Preferences/com.apple.dock.plist
I tried the command with the version 1.4 and 2.0 of dockutil.  If I do the command dockutil --list, the item is showed like this:
Mise à jour de logiciels	/Applications/Utilities/Managed Software Update.app/	persistent-apps	/Users/pilier/Library/Preferences/com.apple.dock.plist
How can I remove it?  Thanks

Same problem here.

$ dockutil --version
2.0.2

$ dockutil --remove 'Geführte Softwareaktualisierung'
/usr/local/bin/dockutil:618: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if dock_item['tile-data'].get('file-label') == item_name:
item Geführte Softwareaktualisierung was not found in /Users/dkf/Library/Preferences/com.apple.dock.plist

Same problem here.
dockutil --version
2.0.2
dockutil --remove 写真
/usr/local/bin/dockutil:618: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if dock_item['tile-data'].get('file-label') == item_name:
/usr/local/bin/dockutil:629: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
if dock_item['tile-data'].get('file-label') == item_name:
item 写真 was not found in /Users/whitesiroi/Library/Preferences/com.apple.dock.plist

This should be fixed in 2.0.4
This worked for me.
dockutil --remove 'Héllo 😀'


missing documentation

I am looking at this library in the context of https://github.com/westnordost/StreetComplete/issues/1651 (potentially using it in StreetComplete).
Is it in active use/development? For example, is it used in a Vespucci? I see recent updates, but https://github.com/simonpoole/OpeningHoursFragment/blob/master/build.gradle seems to not be depending on it what leaves me a bit confused especially as https://github.com/simonpoole/OpeningHoursFragment/blob/master/lib/documentation/docs/help/en/Opening hours.md specifically refers to it. I see it in https://github.com/MarcusWolschon/osmeditor4android/blob/master/build.gradle#L460 but I worry that OpeningHoursFragment is in process of replacing it or there is some other valid reason for not using it.
Something along "is actively developed as a part of the Vespucci" or "used in the Vespucci, getting replaced by an alternative solution" would be nice. Info how it relates to OpeningHoursFragment would be great. I am guessing that OpeningHoursFragment may depend on parser interface, not specific parser - but I am not sure.

What kind of dependencies it requires? Looking at https://github.com/simonpoole/OpeningHoursParser/blob/master/build.gradle#L125 it seems to be a standalone project, not pulling in avalanche of dependencies - what is a good feature and increase chance that it is going to work well on Android. It may be worth stating in README.
Is there somewhere documentation how Rule from ArrayList<Rule> rules = parser.rules(strict); is structured? Would it be potentially welcomed to make PR adding this info?

...but I worry that OpeningHoursFragment is in process of replacing it or there is some other valid reason for not using it.

OpeningHoursFragment is an Android library project and as customary has two sub-projects, the library and an example app. You are looking at the top level build file which is however not relevant for the individual dependencies of the sub projects.

Something along "is actively developed as a part of the Vespucci" or "used in the Vespucci, getting replaced by an alternative solution" would be nice. Info how it relates to OpeningHoursFragment would be great. I am guessing that OpeningHoursFragment may depend on parser interface, not specific parser - but I am not sure.

Given that it, while quite mature, still get fixes should make it clear that it is in active development, as I pointed out above you are simply looking in the wrong place wrt use in OpeningHoursFragment (which is simply an UI) and Vespucci (which uses it in multiple places).

What kind of dependencies it requires?
None.

Is there somewhere documentation how Rule from ArrayList<Rule> rules = parser.rules(strict); is structured? Would it be potentially welcomed to make PR adding this info?

You don't really need to know the internal structure, there are getters and setters for all the internal fields, you should simply generate the javadoc locally from a clone of the repo. if javadoc is missing somewhere (in some cases it is a bit skimpy), pls feel free to make a PR with improvements.

Thanks for a reply! Would it be welcomed to make a PR with explicit "developed as a part of the Vespucci" note in the Readme?

Well no, because there are other people using it. If anything "... originally developed for use in Vespucci" (with a link to the Vespucci repo).

Addressed in https://github.com/simonpoole/OpeningHoursParser/commit/9962f78b78928237f8e1a7b099ec2870bb3bbbe2

Addressed in https://github.com/simonpoole/OpeningHoursParser/commit/9962f78b78928237f8e1a7b099ec2870bb3bbbe2


feat(tier4_perception_launch): update cam/lidar detection architecture

Signed-off-by: Kaan Çolak<EMAIL_ADDRESS>Description
#2659
This PR must be merge after : #2844

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[X] I've confirmed the contribution guidelines.
[X] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kaancolak Thank you for PR 👍

@kaancolak I just noticed that there is a typo in the launch PR here, and it doesn't seem to match the arg on the node launch file.
thrust_distance in launch files, but trust_distance is correct.

@kaancolak I just noticed that there is a typo in the launch PR here, and it doesn't seem to match the arg on the node launch file.
thrust_distance in launch files, but trust_distance is correct.

Thanks for correction, I will create quick fix PR.

Shunsuke-san @miursh, I created PR, please look into it.
https://github.com/autowarefoundation/autoware.universe/pull/2926


Frozen in MacOS 12.2.1 (M1 Pro)

CPU keeps high and nothing shown in the menu bar:

Chip: Apple M1 Pro

Unfortunately I have no idea what could be the problem... 😢
Do you have a Xcode environment to build and test the app locally?

I try to run it locally in Xcode and the frozen can be reproduced. I noticed that if the following are commented out then high CPU issue is relaxed (but no menu item will be displayed obviously):
        setupStatusItem()
        setupMenus()

Unfortunately I'm not familiar with Swift and that's what I can go so far. I will try to dig deeper when I'm free.

So here is what I got so far. Actually this is combine with two issues:

CPU is high
Icon is not shown

I resolved the problem 2 by changing my menu bar cleaning app. Now I can see the menu bar item.
For the CPU high issue, I see some one reported similar problems in MacOS: https://www.youtube.com/watch?v=VufEEmuiAy8
I can reproduce the high CPU (and resolve the high CPU) by switching different wallpapers :/ Maybe we met similar issues here.


Response Functions as Member Functions?

Hi,
are there some ideological reasons why the response functions are not available as member functions for the respective system classes like they are in sicpy.signal? I feel like this would make the library a bit nicer to use.
I am willing to implement this myself, I just want to ensure that it would actually have a change of getting merged before putting in the effort.
Just to be clear, I mean forwarding the calls or aliasing the methods, not refactoring the code.

Seems easy enough to implement.  Note that frequency_response is already a method for all LTI systems, so the following works to generate a Bode plot:
import numpy as np
import control as ct
sys = ct.rss(4, 1, 1)
sys.frequency_response(np.linspace(-3, 3)).plot()

One thing that is missing from the sys.frequency_response() method versus the ct.frequency_response() function is automatic computation of the frequency range.  So that would be something to fix/update as well.
Time respones (forced_response, impulse_response, initial_response, input_output_response, step_response) could be implemented fairly simply, as you suggest.
If you or someone else wants to take a pass at this, it would be a nice contribution.  It will require some refactoring, at least for frequency_response since right now ct.frequency_response computes the default frequency range and then calls the class method.  Also, I think that initial_response should only be allowed on systems with an explicit state (so not transfer functions), since there is no well-defined notion of the initial state.

Thank you for quick response and the hints regarding frequency_response. I will take a closer look and get back to you / this thread.


[ISSUE] list_clusters_api_integration example is incorrect

Description
The example at https://github.com/databricks/databricks-sdk-py/blob/main/examples/clusters/list_clusters_api_integration.py is incorrect
There is no ListClustersRequest object in databricks.sdk.service.compute at 0.8.0
Reproduction
Run the example code linked above.
Other Information
DBR 13.3 but I doubt it matters.

https://github.com/databricks/databricks-sdk-py/blob/main/examples/pipelines/list_pipelines_pipelines.py is also incorrect in the same way.


Setup procedure not clear

Hi, what is not clear with the setup instructions? I find it pretty straightforward.

Well, it seems to assume familiarity with node.js (which I wasn't familiar
with at all at the time I opened the issue), which can make it pretty
confusing for the unfamiliar. Something that could be done would be to
directly state that it requires node.js, like "Use of this tool requires
node.js, if you don't have it installed then please install".
On Tue, Sep 11, 2018, 6:02 PM The Only Rida<EMAIL_ADDRESS>wrote:

Hi, what is not clear with the setup instructions? I find it pretty
straightforward.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cstoquer/pixelbox/issues/7#issuecomment-420440945,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aj3PCwwGfAcwVXoDIEvy7h2mkQhTGtY0ks5uaDLigaJpZM4VT225
.

I made some huge modifications to address the issue that you and some other users gave me at the time. From version 2.0.0, Pixelbox is now split in two components: this library, and a GUI editor available on itch.io.
If you are still interested by this project, please give it another try.

I think this is still a valid question. I've been around node a while, but I'm no node expert and it seems incomplete.
The readme here says "Building is done using browserify" but there's no build script in the package.json from this repo. As a matter of fact, there's only one script there, and it's for building the docs, which comes back with an error FATAL: Unable to load template: Cannot find module './doc/templates/ink-docstrap/publish' because the ./doc dir didn't setup with the node install.
Then there's the question: which is the DL to use for a new project? The repo, or the itch download?
I'd love to give it a whirl, but there's a need for more starter docs.


OCM-9457 | ci: Fix oc command issue on ubi8

What this PR does / why we need it:
oc command is failing on CI due to glibc needed by the command line
Which issue(s) this PR fixes
https://issues.redhat.com/browse/OCM-9457
Change type

[ ] New feature
[ ] Bug fix
[ ] Build
[x] CI
[ ] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[ ] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/lgtm
/approve

@ciaranRoche @robpblake could you please approve ?


Load the sub "env" file in the "env" file.

Thanks. I'm not sure I really like the idea though. What's the use case?


Lost connection and CPU drain

Sometimes after some time online, or more often after speedtest connection is lost, and I'm unable to ping mobile device from other nodes.
But also it starts to use more CPU, and device gets some heat.

There is no useful logs. And the problem goes away only by switching it off and on again.

Yep, the speedtest definitely triggers something in Yggdrasil ,and it is stuck somewhere.
Tried to revert to commit e824c73e (before ironwood updates) - nothing, same behavior.

Fixed long time ago.


Pymethods no longer callable from other pyfunctions?

Bug Description
Don't know what's happened, but upgraded to newest pyo3.
Getting this problem
41  | pub struct Aligner {
    | ------------------ function or associated item `new` not found for this struct
...
385 |     let mut aligner = Aligner::new();
    |                                ^^^ function or associated item not found in `Aligner`
    |

But ::new is defined for Aligner in the #[pymethods] impl. This is from an ergonomic function to call it. Worked in the previous version.
Steps to Reproduce
Error can be reproduced by using this library in the
https://github.com/jguhlin/minimap2-rs/blob/minimap2.26/minimappers2/
Specific code is here:
https://github.com/jguhlin/minimap2-rs/blob/minimap2.26/minimappers2/src/lib.rs
Backtrace
No response
Your operating system and version
Ubuntu
Your Python version (python --version)
Python 3.10.8
Your Rust version (rustc --version)
rustc 1.71.0-nightly (c4190f2d3 2023-05-07)
Your PyO3 version
0.18.3
How did you install python? Did you use a virtualenv?
conda under asdf
Additional Info
No response

This is definitely still possible and I think the problems of the linked code are elsewhere, e.g. your branch builds after applying the following diff
diff --git a/minimappers2/src/lib.rs b/minimappers2/src/lib.rs
index 5a8881c..0f45c2c 100644
--- a/minimappers2/src/lib.rs
+++ b/minimappers2/src/lib.rs
@@ -1,3 +1,4 @@
+use std::mem::take;
 use std::num::NonZeroI32;
 use std::sync::{Arc, Mutex};

@@ -82,7 +83,7 @@ impl Aligner {
                     r.query_name = Some(seq.id.clone());
                     mappings.push(r)
                 });
-            }spawn
+            }

             return Ok(PyDataFrame(mappings.to_df().unwrap()));
         }
@@ -161,12 +162,6 @@ impl Aligner {
         }
     }

-    fn rustnew() -> Self {
-        Aligner {
-            aligner: minimap2::Aligner::builder(),
-        }
-    }
-
     /// Set the number of threads for minimap2 to use to build index and perform mapping
     fn threads(&mut self, threads: usize) {
         self.aligner.threads = threads;
@@ -179,7 +174,10 @@ impl Aligner {

     /// Use a sequence instead of a file for an index
     fn with_seq(&mut self, seq: &Sequence) {
-        self.aligner.with_seq_and_id(&seq.sequence, &seq.id);
+        let aligner = take(&mut self.aligner);
+        self.aligner = aligner
+            .with_seq_and_id(&seq.sequence, seq.id.as_bytes())
+            .unwrap();
     }

     /// Index and save index to output

here.
The compiler errors for the missing new are triggered by the invalid rustnew as far as I can see as those prevent us from produce a valid expansion of the pymethods section.


issue while selecting quantity more than 1 on buy now

on the product page, there should be an increase-decrease option for quantity so that user can select a quantity and click on buy now, so it will be redirected on shipping page with selected quantity!!!!!

This is a duplicate of already closed issue https://github.com/bagisto/bagisto/issues/197

Framework Version: 0.1.5
Not fixed

Framework Version: 0.1.5

Fixed

Framework Version: 0.1.6

Again getting this issue

Framework Version: 0.1.6
Still same issue

Framework Version: 0.1.8
issue fixed


[BUG] Better roll tables is preventing Media Optimizer from converting media files

BRT: 2.0.34
FVTT: V11.315
System (irrelevant) dnd5e 3.0.2
Media Optimizer (any version)
All other modules disabled.
For unknown reasons, when Better Roll Tables is enabled, the dynamic import for the FFMPEG module that media optimizer uses fails
    await import("https://unpkg.com/@ffmpeg/ffmpeg@0.10.0/dist/ffmpeg.min.js");
    const createFFmpeg = FFmpeg.createFFmpeg;

After the import it's expected a window.FFmpeg - if BRT is enabled this is undefined.

I've tried recreating the issue, but to no avail, I've generally had these problems on aplications hosted on the forge, I've cleaned up a lot of code with 2.1.0 let me know if the issue persists.


Add styling possibilities to StyleBoxFlat + poly count optimization

Borders can be styled using separate colors, thus allowing effects such as beveled buttons or partial frames
See https://github.com/godotengine/godot-proposals/issues/6910
This is a partial rewrite of the StyleBox drawing code. Includes:

Addition of simple gradients to the border and fill (2-point, strictly horizontal or vertical)
Addition of bevel and inset modes - it's just a different way to calculate border colors according to a simulated light source angle, and you get those bevel effects that were present in many of the classic operating systems
Support for styling the four borders separately
Choice of how two borders are joined together at the corners (gradient or straight cut; the angle of the latter can be set)
Reduction of the triangle count. For instance, each rendering of the center fill still had a useless ring of zero-sized triangles, easily removing 72 useless triangles per drawn StyleBox with rounded corners and the default parameters!

I did the trick by vertices coloring only. No shaders & textures involved. Hence the limitation on the orientation & number of color points in gradients.
Actually, to get the gradients, shaders are the ultimate method and the technique is actually used in web browsers. It would allow any orientation, multiple color stops, radials... without having to worry about how to split the rectangle into triangles. But there would be a conflict if the Control node that renders the StyleBox already has a shader applied to it. Unless there is a way of appying 2 shaders on top of each other in such case, which I am not aware of AFAIK.
Properties tree is rearranged, while keeping the same names for the already implemented ones such as the bg color, not to break compatibility with existing projects. This is the reason I could not put it into the new Background subcategory, for instance.
Open for discussion if I missed something!
And there are high chances we can cherry-pick this into Godot 3.

Support for styling the four borders separately

I remember seeing this feature in the initial StyleBoxFlat PR, but it was removed when the implementation was changed to use polygons.

This is a lot of different features bundled into the same PR. While rendering improvements are likely welcome, the demand for new features is debatable and needs to be evaluated individually. It's also problematic that this PR introduces conflicting properties (such as two ways to set the border color). Yes, we can't break compatibility, but this is bad API design and is not user-friendly.
For gradients specifically, if this feature is needed, we should use our existing gradient resources instead of an ad hoc and very limited re-implementation.
Overall, my recommendation is to limit the scope and work on this in steps, starting with rendering improvements.

Thanks for the feedback. This opens up a lot of questions and I would like some guidance on how to do those things a bit more like you suggest.
We can discuss in the related proposal, definitely!
Interdependency of the features
Some of the features depend on the changes implemented for others.
For instance, setting border gradient is built on top of setting the four border colors separately.
Thus, I would have to wait for the first one to be discussed and merged before proposing the second one and so on. Is there a way to avoid this bottleneck and comply with the idea to separate the features?
Balance between good API design and backwards compatibility
I made a compromise in my proposal between the two, whis is not perfect. How would you change it, better consistency at the expense of backwards compatibility? Or, perhaps, some features of the property system that may allow using the old property identifiers while showing different names for them in the editor I may not be aware of?
The gradient algorithm
The proposed implementation is a bit less complete in possibilities, but has a performance bonus because it does not need a texture. In the case of a StyleBox that can be frequently drawn for buttons, frames, progress bars... for instance, it can be an advantage. I would say that the simplified algorithm covers most use cases, and we may add the possibility to use the texture for advanced ones. My initial thought was to internally use a shader, but I am stuck with the possible conflicts.
If I use a GradientTexture2D to apply the gradient instead, I need to specify a fixed rendering size for it. It can be problematic if the StyleBox is larger as rendering artifacts can appear.
The way to set borders:
I thought of the possibility to

set an overall style for all four edges
override the setting for specific edges for more customization.

It maintains the possibility to fully customize the edges, while providing some shortcuts to try out styles without having to set up the four border colors separately. Initially I added the possibility to style each separate border only, and I found out that it is tedious just to try out different gradient colors.
Same goes for the bevel effect. It does the color mixing for you and applies it to the edges.
Would you suggest a different approach?

Thus, I would have to wait for the first one to be discussed and merged before proposing the second one and so on. Is there a way to avoid this bottleneck and comply with the idea to separate the features?

That's right, you would have to wait for the work to be approved. That's the whole point of splitting your work, to remove inherent interdependency and make changes in sensible steps, discussing and evaluating each of them. Otherwise you put us in a position where we have to accept or reject everything at once. And in that case, this should be rejected, because it contains a lot of changes massively extending the API surface without a lot of evidence that there is a demand for it.
Smaller, clearly beneficial changes are better than betting everything at once.

How would you change it, better consistency at the expense of backwards compatibility?

Well, to discuss that we would need to see which features are actually needed and how their use-cases look like. All the planning would start there. As an arbitrary suggestion, a new stylebox type can be added. In fact, it can probably be added as an addon first, and then we would see if it's niche or if it's something most users would benefit from.

In the case of a StyleBox that can be frequently drawn for buttons, frames, progress bars... for instance

Nothing is drawn more frequent than it is updated, and a few textures shouldn't be an issue for a game engine. If there are some reasonable performance benefits, they need to be benchmarked and provided. But you also don't have to use a GradientTexture. I was talking about the Gradient resource, a type that holds a collection of colors and some interpolation information, and it also has an inspector plugin for easy editing. How you'd use that information is up to your implementation, but at least we wouldn't be sacrificing usability.
But that can be discussed in a dedicated PR in more detail.

Let's go for splitting the features and proposing smaller PRs. Makes sense.
How could something as massive as the tilemap system rewrite be approved if everything should be done in small iterations only? How do you conduct reviews for reworks that require syncing the progress on multiple parts together?
Because I see some cases to be better implemented all at once, especially if an API is changing, so that there is only one moment where the backwards compatibility breaks instead of multiple successive ones.
Also, let's see the following situation.

I implement feature A for proposal
I implement feature B for proposal independently, Don't want to wait for A to be merged. So I copy part of the logic of feature A which is useful for B to have the discussion started on it.
Feature A gets accepted and merged.
Now there is a conflict with feature B, I have to resolve it (the main thing I want to avoid).

In software engineering, I find it much easier to plan well rather than handle conflicts.
On the other hand, implementing an empty shell "just in case" by thinking of the other features in separate PRs could be interpreted as dead code in the scope of the related PR. How to strike a good balance according to the project governance?

How to strike a good balance according to the project governance?

I strongly recommend joining the Godot Contributors Chat and participating in relevant channels if you're working on significant features.

Thanks! Just found out all the feature-specific channels there.
I visited the chat before but the place to find channels other than new-contributors and devel is not straightforward IMHO. Perhaps drop a note in the docs about that?

How could something as massive as the tilemap system rewrite be approved

It was discussed and approved before the work has even started, whereas you're coming with an implementation first. You made the proposal the same day, there was no discussion, no consensus on the feature set, no opinions of stakeholders or users shared to guide you to the most viable, most useful implementation. You say

In software engineering, I find it much easier to plan well rather than handle conflicts.

And this is why we ask everyone to follow the proposal process, submit an idea first, and through discussion to arrive to a path that makes sense and doesn't waste your time. We do not advise anyone to work on a feature that hasn't been discussed first. It's just a bad idea, unless you're very much aware of the possibility and ready for your work to be rejected.

Also, let's see the following situation.

In this situation you would include the commit from PR A into PR B, mark B as a draft, and be ready to rebase it once A is merged. You wouldn't include changes from A into the same commit as changes from B. That's actually a pretty normal thing many contributors do, submitting connected PRs where one contains commits from the other, ready to be rebased.
And once again, "to have a discussion started" you open a proposal, not a PR. PR is the final step of the feature implementation, even though it's often tempting to jump ahead or just arrive to an implementation through experimenting and creating a PoC.

On the other hand, implementing an empty shell "just in case" by thinking of the other features in separate PRs could be interpreted as dead code in the scope of the related PR.

You should not implement anything unrelated to the PR, not unless you've been approved ahead of time to build a framework for future expected changes. In this case you have rendering optimizations and you have several new features. Features may depend on your changes to the rendering code, but that doesn't mean that you should open a PR making rendering optimizations and adding some "empty shell" for the features. Your PR should only include optimizations, and the rest of the changes should come with their corresponding features in dedicated PRs.

It was discussed and approved before the work has even started, whereas you're coming with an implementation first. You made the proposal the same day, there was no discussion, no consensus on the feature set, no opinions of stakeholders or users shared to guide you to the most viable, most useful implementation.

I opened some proposals about that change, knowing that all features require discussion, exactly for the reasons you mention. There are two of them - the one specific to the new features of this PR was very young, and a more general one with some screenshots that was opened before.
Definitely I prefer to have an open discussion and get those opinions.
Here are the related proposals.
https://github.com/godotengine/godot-proposals/issues/6910
https://github.com/godotengine/godot-proposals/issues/6812
Perhaps the links were not mentioned clearly enough in the description.

even though it's often tempting to jump ahead or just arrive to an implementation through experimenting and creating a PoC

Making a PoC is how I can evaluate the technical feasibility in many cases and quickly see if there are corner cases or quirks that would make the idea not practical. And, if it works, I can visually experiment with its results and see what can be created with it, explain it with screenshots that are 1:1 accurate with what you get.
The code here is an "expanded proof of concept" indeed, and I thought the process of collaborating on the PR would be a good place to make the reviews to turn it into something suitable for our quality standards, with the corresponding discussion about features in the attached proposal.

Your PR should only include optimizations, and the rest of the changes should come with their corresponding features in dedicated PRs.

It's done now. For the optimizations only, see #77278
For the features, it's back to the drawing board for more proper discussion!


Migrations

Add deactivate genesis.
Minor fixes in some migrations.
Update generate deployments.

Deprecated caused issues with folder name.


Filtering crates by the nesting level

Describe the solution you'd like
I would like to have an overridable option in config / CLI which gives an opportunity to specify a maximum acceptable node level that can be captured and processed by the cargo-deny.
It could be something like cargo-deny list --layout=crate  --max-level=1, so that command will output / check the crates on root (defined in Cargo.toml) plus one level for each core dependency.
Describe alternatives you've considered
Currently the desired group of the checked crates can be show with the usage of the grep command:

Do a regular call with CLI, for example cargo-deny list --layout=crate
Pass the output with | to the grep command with desired regular expressions / keywords.
Write the output into the file.

Additional context
Let's look on the following example to get the whole idea. We want to output licenses of all core dependencies declared in the Cargo.toml. It could something like this (the output was taken for my own terraform-sage project):
=> cargo-deny list --layout=crate
<EMAIL_ADDRESS>(2): Unlicense, MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(2): Unlicense, MIT
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(2): Apache-2.0, MIT
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
<EMAIL_ADDRESS>(2): MIT, Apache-2.0
// ... and many more

With the usage of the --max-level option (or any other desired name) the cargo-deny filters crates by the certain nested level, so that it will output:
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
<EMAIL_ADDRESS>(1): MIT
// ... the rest of the group

Are you interested in that flag only for the list subcommand or for check as well?

Currently I'm mostly interested in this functionality for the list subcommand. But it could be used as a part of the check subcommand for sure :)

Cool. Let me know if you have ideas for other improvements to the list subcommand, it was kind of added just because we have all of the information available and it was easy to add, but we don't really use that much ourselves so it hasn't gotten much attention.


add swcli dataset diff command to diff dataset two versions

related: https://github.com/star-whale/starwhale/issues/777

https://github.com/star-whale/starwhale/pull/1051


Are test failures actually failing the build?

Take a look the these two builds:

Gradle build for java 14:

1115 tests completed, 6 failed, 47 skipped

Maven build from a merge prior to Gradle merge:

2022-02-15T16:08:20.6424291Z [WARNING] Tests run: 1084, Failures: 0, Errors: 0, Skipped: 27, Flakes: 2

There are two issues here:

Test numbers are different
6 tests failed on gradle build, but the build still passed. Is this expected behaviour?

Steps to investigate:

Look into the latest build on main.
Check if any tasks have failed tests.
Verify whether these failures were reported for a flaky test that eventually passed or is it actually failing but is not enough for BUILD to be marked as "FAILED"

There are two possible outcomes of this:

If the behavior is expected, then no further action is required. Can comment as such and close this issue.
If it is not expected, then further investigation in a follow-up issue, with steps to address it, will be needed.

Tests do fail the CI checks. There is retry logic that retries a test up to 5x until the test passes and will fail the suite if all 5 retries fail. Closing this issue.


Rename error trace to the more user friendly Counterexample

Not sure if it's worth it because from docs and code we refer to this section as Error Trace.

Renaming “Error Trace” to “Counterexample” also aids in distinguishing “Counterexamples” from specific errors (which cause TLC to throw an error or exception).

I think this is a good idea if we can make it distinguish between property/assertion violations and TLC errors, like adding a string to an integer. Basically, if this could still be "error trace":

To me, the error trace, called stack trace elsewhere, is the call chain of expressions that led to the error.  The error trace is not an object in the theory of TLA or TLA+.


Can't make openvdbi plugin :[

Hi , It's 3 day I'm trying to build openvdbi , I get 773 error , I installed everything and followed up wiki.
I installed boost , openvdb lib , openexr lib and etc.
Can't you just ship it with library ?
Is anyplace I can get it ?

+1 for a package that can just be imported into Unity


Add "Security disclosures" section

As like other AWS-led open source projects, we don't use GitHub issues
for security issues.
Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hmm, sorry. We have this section in https://github.com/awslabs/soci-snapshotter/blob/main/CONTRIBUTING.md#security-issue-notifications already.


selfDestroying doesn't destroy the service worker

So, we got into a pickle with our web app. I migrated from Webpack to Vite, and because it previously had a web manifest and a service worker, I set one up again with vite-pwa.
This caused a problem, because vite-pwa was returning 404 for a /blog route, because it wasn't a defined route in the router. HOWEVER, it was proxied using NGINX to go to another Wordpress site. But the service worker wouldn't even check, it just returned 404.
After thinking about it, I realized we didn't really need any kind of offline capability and really it was more trouble than it was worth. We've now tried every strategy we can think of to remove it, and we simply cannot.
If I do a Vite production build, for example, with the service worker. And then I change the service worker setup to:
    VitePWA({
      selfDestroying: true,
      // Destroy in dev mode too
      devOptions: {
        enabled: true
      }
    }),

...and then we run Vite in dev mode, this does not destroy the service worker at all. Refreshing the page loads the service worker, and the service worker throws a ton of errors saying that a bunch of files have 404s (like .svg assets), yet all those 404s are for files that should not be retrieved in dev mode. (It's adding hashes to them.)
If we tell users to completely clear the cache, our production site works again. But we can't do that in every case. We just want vite-pwa to not exist anymore, and we can't seem to do anything to remove it. In fact, we tried code like:
void navigator.serviceWorker.getRegistrations().then(function(registrations) {
  for (const registration of registrations) {
    void registration.unregister()
  }
})

...which we got from MDN, and tried using this with vite-pwa not loaded, and the service worker seemed to only re-create itself. I guess, because it was cached, it loaded a cached root HTML file, which loaded the cached service worker?
Please, how do we delete this and never think about it again? Right now it's the zombie that never dies.

@matthew-dean @Zavim have you read the docs? You MUST not change anything in the configuration, just add selfDestroying: true, check the DANGER entry: https://vite-pwa-org.netlify.app/guide/unregister-service-worker.html

I hadn't changed anything in the configuration, just removed localhost:3000 from my browser history. Either way, my case was a practice PWA, not client-facing.

I have the same issue and I didn't change anything in the config.

I think of adding a script to GTM to unregister a service worker, bust the cache and refresh the page for the user. Super hacky and ugly, but I am out of options.

I am also trying to play with downgrading vite-plugin-pwa version, because I have a feeling that something was added to the config on the plugin side, and because of that service workers names or something else don't match.

We haven't change anything about the sw name, check it in local without selfDestroying and then add it again, maybe you have some old tests on your local.
Ensure your original sw precache manifest doesn't include the sw itself.

Downgrading from ^0.16.4 to 0.12.8 helped. It worked!

uhmm, I'll check changes between those versions, are you using injectManifest strategy?

Yes, I have the following config:
VitePWA({
        strategies: 'injectManifest',
        registerType: 'autoUpdate',
        injectManifest: {
          maximumFileSizeToCacheInBytes: 5_000_000,
        },
        selfDestroying: true,
      }),

Look, maybe it was something else, I didn't do a thorough investigation.

I had version 0.11.13 installed. Then I updated to the latest version of the plugin and added the flag. It didn't work (or maybe I did something incorrectly). Then I downgraded to 0.12.8 and it worked.


Getting good contrast with 1602 display

Great extension, thank you. Not related to your code, but I wonder if you managed to get good contrast on the 1602 LCD at 3.3V. Did you find a way? My 1602 with the PCF8475 I2C backpack gives very low contrast.

Hi,
The voltage level will affect the contrast of the LCD.  If the voltage is low, it is not easy to obtain good results.Therefore, it is necessary to increase the power supply voltage of the LCD.
The voltage of SDA/SCL cannot be lower than 0.7VDD, so the maximum voltage of the LCD power supply is 3.3/0.7=4.7V.
You can try to provide about 4V power to the LCD separately, or connect 1 or 2 1N4001 diodes in series to the USB 5V to power the LCD, which can reduce the voltage by 0.6-1.2V.
Note that the power supply limit voltage of the microbit is 3.9V, and exceeding the chip may permanently damage it. And remove the I2C pull-up resistor on the LCD first.
--
Best regard!
Shao ziyang
@.***
2023年11月24日
At 2023-11-23 18:19:59, "Rob Wilson" @.***> wrote:
Great extension, thank you. Not related to your code, but I wonder if you managed to get good contrast on the 1602 LCD at 3.3V. Did you find a way? My 1602 with the PCF8475 I2C backpack gives very low contrast.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Thank you, that's a very clear explanation!
On Fri, 24 Nov 2023, 02:51 shaoziyang, @.***> wrote:

Hi,
The voltage level will affect the contrast of the LCD. If the voltage is
low, it is not easy to obtain good results.Therefore, it is necessary to
increase the power supply voltage of the LCD.
The voltage of SDA/SCL cannot be lower than 0.7VDD, so the maximum voltage
of the LCD power supply is 3.3/0.7=4.7V.
You can try to provide about 4V power to the LCD separately, or connect 1
or 2 1N4001 diodes in series to the USB 5V to power the LCD, which can
reduce the voltage by 0.6-1.2V.
Note that the power supply limit voltage of the microbit is 3.9V, and
exceeding the chip may permanently damage it. And remove the I2C pull-up
resistor on the LCD first.
--
Best regard!
Shao ziyang
@.***
2023年11月24日
At 2023-11-23 18:19:59, "Rob Wilson" @.***> wrote:
Great extension, thank you. Not related to your code, but I wonder if you
managed to get good contrast on the 1602 LCD at 3.3V. Did you find a way?
My 1602 with the PCF8475 I2C backpack gives very low contrast.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/makecode-extensions/i2cLCD1602/issues/7#issuecomment-1825086648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE6VELN35TDX7BXY4WYLG73YGADTZAVCNFSM6AAAAAA7XQYOIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVGA4DMNRUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Getting Unexpected value of a Boolean variable in multi index Table.

Hi,There
While creating a smart contract today, I have encounter a peculiar bug i.e.  I create a Multi Index Table, and initialize three Boolean variables in it and did initialize them to false. When  I run get table command the table was printed but one of the three Boolean variable had the weird garbage value instead of 0.
I am here posting the struct that I have created in my Smart Contract.
`  /// @abi table chal12 i64
struct challenges
{
account_name to;
account_name from;
uint64_t noofdays;
asset balance;
uint64_t id=0;
bool accepted = false;
bool completed = false;
bool decline = false;
time cgt=now();
time taccept;
     uint64_t primary_key() const {return id;}

     EOSLIB_SERIALIZE(challenges,(to)(from)(noofdays)(balance)(id)(accepted)(completed)(cgt)(taccept)(decline))

 };

 typedef eosio::multi_index<N(chal12), challenges> challenge_table;`

When running command get table I got the following output -:
{   "rows": [{       "to": "amar1",       "from": "test1",       "noofdays": 5,       "balance": "20.0000 EOS",       "id": 0,       "accepted": 0,       "completed": 0,       "decline": 244,       "cgt": 5988348,       "taccept": 0     },{       "to": "amar1",       "from": "test1",       "noofdays": 5,       "balance": "20.0000 EOS",       "id": 1,       "accepted": 0,       "completed": 0,       "decline": 51,       "cgt": 5988349,       "taccept": 16777216     }   ],   "more": false }

Would you try to use uint8_t instead? It consumes same amount of memory.

It returns 0 because eos takes 0 as false and 1 as true.

You got this error because you have to arrange it in EOSLIB_SERIALIZE as you have arranged in struct
The correct order will be
EOSLIB_SERIALIZE(challenges,(to)(from)(noofdays)(balance)(id)(accepted)(completed)(decline)(cgt)(taccept))
Try this...

Thanks for the support , issue is solved now. Closing this.

What was the fix? @ghost


feat(Slider): introduce Slider component

Tickets: DATAUI-1616, UXRFC-199

@Arucard89 Do we want it to be part of v6?

@Arucard89 Do we want it to be part of v6?

Actually I don't know. What's plan?
This component corresponds to the design. And I'm waiting for decision.
It would great if you can review it and we introduce Slider with v6.
Also it is fine if we add it in some minor version.
But I need Slider in uikit to create RangeInputPicker

@amje , hi. I've fixed all comments. Check them, please

@amje hi. I fixed all comments. Could you review it?


Dataloader is super slow

Hi,
Thanks for the awesome framework for NeRF! I have a question about the data loader speed, what would be the expected time for loading shiny blender dataset for example?
I'm using a NVIDIA T4 device with a single GPU and cuda 11.7, and the estimated loading time for testing data loader is around 4.5 hours. Here is the command I used to load your provided checkpoints, the config file is unchanged:
python3 run.py --ginc configs/nerf/shiny_blender.gin --scene car --ginb run.run_train=False --ckpt_path logs/nerf_shiny_blender_car_220901/best.ckpt
I created the conda environment as suggested in README, then also tried to upgrade to latest cuda toolkit, torch and torch lightning version for cuda11.7, in both cases the testing data loader needs more than 4 hours to load.
I would really appreciate it if you can shed some light on this issue. Please let me know if you need more information. Thanks in advance!

I do not think this is a problem.
NeRF takes more than a minute to generate an image with a resolution of [800, 800] due to the computationally expensive volumetric rendering process.
When evaluating on ShinyBlender, the code will evaluate an entire scene, which consists of more than a hundred frames. Accordingly, it should take more than several hours for testing.
To handle this issue, I recommend the options below

Reduce the number of points to sample while rendering.
Use a test_skip option to evaluate partial scenes.

Please reopen the issue if you have any further items to discuss.

Thanks a lot for your explanations and suggestions! I thought the process bar is only the data loading, now it makes sense if it's the evaluation pipeline.


Use multiprocess in diff tool (#546)

What was wrong?
Related to Issue #546
How was it fixed?
Use the multiprocessing package to parallelize the diff generation process.
On my machine, the doc build took:
real	36m14.936s
user	35m47.537s
sys	0m17.459s

With these changes:
real	19m23.582s
user	62m1.858s
sys	0m59.292s

So a wall clock savings of ~17 minutes.
Cute Animal Picture

Since you're in this area a lot lately @gurukamath, would you mind taking a peek?

LGTM!


odh-7074-b create wb - qe comment

addressing QE comment for prereq of creating a workbench

another commit - qe comment - remove duplicate paragraph (7074)


Add KH1.5+2.5 & KH2.8

Add support for KINGDOM HEARTS HD 1.5+2.5 ReMIX and KINGDOM HEARTS HD 2.8 Final Chapter Prologue.

Also, this is a wonderful script! Thanks for writing it!

Glad it's useful for you and thanks for the contribution!


Composing generators: good idea or great idea?

Part of what I dig about pescador (and leveraging generators for data sampling) is that it's easy to build pipelines of well-encapsulated transforms. They could be used from anything from data augmentation, e.g. additive noise, to glue layers, e.g. "I need one-hot encoded vectors from integer indexes". While pumpp aims to achieve this, I imagine the pescador audience will be more broad, and some simple tools would be good to help outline (what we think are) good design practices.
For example, I've been thinking for sometime about having a pescador.transforms submodule which provides some decorators to turn sample-wise functions into iterable transforms, like...
def stateless(func):
     def wrapped(gen, *args, **kwargs):
         for samp in gen:
            yield func(samp, *args, **kwargs)
     return wrapped

This could allow for some easy fixes, like for #76 ...
@stateless
def newaxis(sample, *keys):
    for key in keys:
        sample[key] = sample.pop(key)[np.newaxis, ...]
    return sample

# Given a sample generator `stream`...
pescador.buffer_batch(newaxis(stream, 'x_in', 'y_true'), 10)

I'd want to disable the decorator for testing, but I'm not sure that's possible (and it's not the end of the world). This would also allow for some other reshaping / renaming that goes on regularly, such as transforming dicts to tuples:
@stateless
def values(sample, *keys):
    return [sample[key] for key in keys]

thoughts? Is this a good idea?

Generally 👍 . I have built things somewhat in this direction for work already, but this is slightly more elegant.
I definitely agree that there are a number of transforms that are likely to be common use cases and useful.

thoughts? Is this a good idea?

This sounds slick.  I'm not 100% sure I understand your example though: is the idea to make a decorator that can wrap simple functions as generators?  Or as streamers?

so here's a few thoughts...
after mulling over other issues (namely #75), I think transforms would process arbitrary data streams, i.e. an "online" pipeline. So, yea, this decorator would make a function iterable.
The decorator is one possible way of abstracting iteration from processing ... otherwise every transform is going to have the same for x in stream: yield fx(x) block. This could also be achieved with a class for stateful processing, or if you needed to have a transform upstream of a mux.
This could also help solve some statistics problems I've had in the past, e.g. count class occurrence in the data stream for likelihood scaling.
A note on ordering: I think the party line on the architecting streams is ...

Define a data sampler
Build Streamers seeds over samplers
Multiplex Streamer seeds
Apply transforms to mux'ed stream
Stick it behind a ZMQ interface

This basically sounds like map (mapcar if you're nasty), except without the target iterable of the map.
What I'm not quite getting is how this would shake out in practice.  Where do the inputs to the function/streamer come from?
Maybe it would help if you could mock up an example in the syntax that you have in mind?

note: motivated by this PR comment here, so that it'll be easier to find in the future (rather than bury it in a PR thread).
Definition: A transform is an iterable function that transforms a data streams on an item by item basis.
One piece of functionality I think is ripe for a stream transform is the tuples functionality of a Streamer. The rationality for this is two-fold:

I've previously argued that Streamers should transparently yield data streams (as convention) to help avoid situations where data is implicitly (and / or unexpectedly) modified, i.e. idempotence is nice.
The tuples functionality can only work if the data stream owned by the Streamer consists of data, i.e. dicts of key: np.ndarray pairs. To keep the tuples method in the interface of Streamer, we would need to implement dynamic type checking or throw errors on bad data streams. This feels like an anti-pattern.

But good news! We could implement tuples as a transform:
def tuples(stream, keys):
    for data in stream:
        yield tuple(data[key] for key in keys)

Which could be used as follows.
def data_generator():
    yield {'X': np.array([1]), 'Y': np.array([5])}

stream = pescador.Streamer(data_generator)
for data in tuples(stream(max_iter=20), keys=['Y', 'X']):
    print(data)  # Displays (array([5]), array([1]))

Added bonus, this resolves the kwarg parsing (and possible conflicts) currently handled by the Streamer.tuples method.
starting to be clearer @bmcfee ?

PEDANTRY ALERT @ejhumphrey the usual terminology for this kind of operation is map .. maybe things would be clearer to me if we tried to stick to common functional programming practices.
I don't understand what the problem of keeping the tuples method of streamer is though.  It would only ever be called by the user.  None of the internal methods would ever use it, for exactly the reasons you describe above.
OTOH, I guess I'm okay with your proposed example.  The question-mark for me has been how tuples would interact with buffering.  But, I guess buffer can easily become a streamer map (just with slightly different semantics than other maps that generate data), so you could have something like
raw_stream = pescador.Streamer(data_generator)
stream = pescador.Streamer(buffer, raw_stream, n=3)

for data in tuples(stream, keys=['X', 'Y']):
    print(data)    # Displays (array([[1],[1],[1]]), array([[5],[5],[5]])

yes! it's a map! My experience with truly functional languages is academic (aware of but haven't used), and my knowledge falls somewhere between rusty and spotty. Consider it successful pedantry in the spirit of (re)education, and I thank you for your patience.
Now, to the matter at hand, working backwards from your two comments:
re: OTOH...
yes, I'm proposing that tuples and buffer to be map operations (similar to enumerate and zip). The way I was imagining this was like the following:
def data_generator():
    yield {'X': np.array([1]), 'Y': np.array([5])}

def tuples(stream, keys):
    for data in stream:
        yield tuple(data[key] for key in keys)

def buffer_data(stream, buffer_size):
    buff = []
    for data in stream:
        buff.append(data)
        if len(buff) == buffer_size:
            yield {key: np.array([x[key] for x in buff])
                   for key in for key in data}
            buff = []

stream = pescador.Streamer(data_generator)
batches = buffer_data(stream, n=3)

for data in tuples(batches, keys=['Y', 'X']):
    print(data)    # Displays (array([[5],[5],[5]]), array([[1],[1],[1]])

Reflecting for a second, I think the reason that I've advocated for a different idiom for map operations is two-fold:

I don't think that those functions (e.g. tuples, buffer_data) need the core functionality that a Streamer provides (rebooting generator functions / iterables). I say this in the spirit of "do one thing well" / encapsulation.
A Map is fundamentally a generator function, in that it should only take iterables, and any args / kwargs control it.

Interestingly, the Streamer(buffer, streamer, buffer_size=3) example you give satisfies both points: (a) buffer doesn't need to know about Streamer functionality, but you can get that functionality if you need it by combining them, and (b) Maps, being generator functions, are compatible with Streamers by design.
This is elegant / makes sense, so I 👍 .
re: the problem of keeping tuples in Streamer
Consider the following:
values = [0, 1, 2]
streamer = pescador.Streamer(values)
for x in streamer.tuples(0):
    print(x)

Which would raise something like IndexError, int has no getitem method or whatever. Yes, this is a dumb example; but, I use it to demonstrate that this method is invalid for an otherwise perfectly fine streamer. This feels wrong to me from a OOP / class design perspective, since the user can put the class instance in a potential failure mode without knowing it. I couldn't quickly find a reference to support my claim, but would expect there to be some guideline like:

A successfully initialized instance should be able to call all of its methods.

That said, I'm willing to concede that this is more LBYL than EAFP, and if we leave Streamer.tuples I'd want a more informative error about what "data" objects are and how the user effed up.

I don't think that those functions (e.g. tuples, buffer_data) need the core functionality that a Streamer provides (rebooting generator functions / iterables). I say this in the spirit of "do one thing well" / encapsulation.

Countering this, I could imagine situations in which you'd want to multiplex over batches.  But you could easily do that if buffer is a generator that can be wrapped in a Streamer.  It's just a question of how cumbersome it is do pull that off.

Which would raise something like IndexError, int has no getitem method or whatever. Yes, this is a dumb example;

... yeah, I'm not buying it. 0 is a valid dictionary key, so there's no reason it would know to fail until you go to access the data dict.

This feels wrong to me from a OOP / class design perspective, since the user can put the class instance in a potential failure mode without knowing it.

Just because an object is constructed well does not mean that any method call is fair game.  You can always throw garbage into any method that accepts parameters.
To be clear: I think I'm on board with moving tuples out to its own function, but this isn't a great argument.
Actually, I'd like to expand tuples a little to support tuples of lists for keras's multi-input/output mode.  This is easy though.

(re: Streamer(buffer...)) It's just a question of how cumbersome it is do pull that off.

After this deprecation PR is out the door, I suppose I'll find out 😄

To be clear: I think I'm on board with moving tuples out to its own function, but this isn't a great argument.

Fair enough.

Actually, I'd like to expand tuples a little to support tuples of lists for keras's multi-input/output mode. This is easy though.

I'm not sure what you mean at present, but I look forward to learning about it later.

After this deprecation PR is out the door, I suppose I'll find out

We could figure this out now.  My main concern here is that I want buffering to play nicely with the zmqstreamer, given that it's a high-latency operation.
raw_stream = [some nonsense]
buf_stream = Streamer(buffer_samples, 32, raw_stream)
parallel_stream = ZMQStreamer(buf_stream)

for batch in parallel_stream:
    do some stuff

That doesn't seem too bad.

I'm not sure what you mean at present, but I look forward to learning about it later.

Oh, basically just that if you have multiple inputs or outputs, they get packed in the tuple as ([input1, input2, ...], [output1, output2, ...]).  I agree that this is "hella dum", but that's how it works.  The tuples function can support this pretty easily though, eg:
train_gen = tuples(streamer, inputs=['X1', 'X2'], outputs=['Y1', 'Y2', 'Y3'])

Three quick things:
I agree, that code-block seems fine. I guess I was proposing that we modify / implement buffer_data (or whatever) in a subsequent PR; however, since that change would deprecate some functionality, sure, I can do it now.
Multiple I/O -- I get it.

given that it's a high-latency operation.
fwiw, I suspect buffering is high-latency at the moment because of how __split_batchis implemented, not the inherent act of buffering. That is mostly speculation though, and I look forward to benchmarking it.

I guess I was proposing that we modify / implement buffer_data (or whatever) in a subsequent PR

Eh, I think it's easiest to leave the current stuff in place, deprecate it later, and replace it with a similarly named function that behaves the way you want.

I suspect buffering is high-latency at the moment because of how __split_batchis implemented

I'm not sure.  There's a lot of weird control flow in there, but i think the biggest hit comes from all the memory copies.

😳  what if I've already done it...?

closed with #88


Lanbon L8 Display Settings "Long Idle Setting Not Retained"

Lanbon L8 Switch
Firmware: lanbon_l8_full_8MB_v0.4.0.bin
Home Assistant custom component

Describe the bug
Long idle setting in "Display Settings" is not retained, resulting in the display remaining on indefinitely.
To Reproduce
This happens after home assistant restarts. Not always immediately, but eventually after 3 or 4 restarts the setting is lost.
Expected behaviour
Setting retained.

Try a newer build from https://github.com/HASwitchPlate/openHASP/actions

@nagyrobi  thank you
short idle 60s
long idle 120s
ok , ive installed the latest and will advise.
I noticed this version already has the relay state at hasp/platexx/state/relay12
thank you.
But whats the command topic?
tried hasp/plate01/command/relay12 with payload 1 or 0 but no luck.

Are you using the openHASP custom component or some automation to control the dimming of the backlight on idle?
The openHASP firmware doesn't dim the screen by itself, so there is an outside entity sending the dim commands.
My guess is that when you reboot HA while the plate is in state idle long, the states get out-of-sync.
Try connecting to the plate using telnet and reboot HA a couple of times to see what shows up in the logs.

@fvanroie Thank you
I am using the custom component and the sample automation which dims the backlight after a few minutes.
I'll try your suggestion and revert.
As mentioned I noticed you now added a state topic for the relay but the previous output command tonturnnit on off doesn't work anymore.
Can you tell me the new topic to turn the relay on or off?
Thank you

I'll check with @dgomes is we need to implement an idle command to get the currect idle state of the plate.
That way the custom component can retrieve it when HA reboots. The current idle state can be requested via statusupdate but this might not be as straight-forward.
The issue regarding the gpio outputs will be followed up in #40. I'm trying to keep this issue list topical.
Keep in mind that v0.4.1 from the actions tab is a work-in-progress version and thing can (will) be broken in these nightly builds.

@fvanroie looking at the automation, i think it's my mistake. below it's the automation.
effectively when elevation is up i'm sending idle2 to zero.
apologise for wasting your time.
`- id: lights_lanbon_night_day
alias: Lights lanbon night day
initial_state: true
trigger:

platform: numeric_state
entity_id: sun.sun
attribute: elevation
below: -1
platform: numeric_state
entity_id: sun.sun
attribute: elevation
above: 1
condition:
condition: template
value_template: "{{ (as_timestamp(now()) - as_timestamp(states('sensor.hass_uptime'))) / 60 > 2 }}"
action:
choose:

conditions: '{{state_attr("sun.sun","elevation") > 1}}'
sequence:

service: mqtt.publish
data:
topic: hasp/plate01/config/gui
payload: '{"idle2":0}'
default:

service: mqtt.publish
data:
topic: hasp/plate01/config/gui
payload: '{"idle2":120}'`

understand on the nightly build. I'm actually not using the switch in it's intended place as I need the relay control.
It's on a bench for testing, so i'll wait until relay is controllable.

Has this issue been resolved and can this issue be closed?

@fvanroie
Sorry yes. Thank you

No worries, glad this has been fixed! 😃

Hello there, sorry to open this issue, but i have same problem. When i restart HA the backlight can not disable, only if i restart my Lanbon L8. Any idea why to do this?

@vampywiz17
Did you recently upgrade the openhasp hacs component  to 7.2?
If yes it may be the cause.
I upgraded  to 7.2 and my backlights started acting faulty.
I went back to 6.6, which is where my plates are and issue solved.

@juan11perez
Yes! it happen, when i update it to 7.2!
try to downgrade it.


Typo, minor whitespace changes

Description
Before / After typo fix:

Also includes minor whitespace formatting to conform to our typical style.
This pull request is categorized as a:

[x] Other

Checklist

[x] I’ve run pytest and made sure all unit tests pass before sumbitting the PR

If you modified or added functionality/workflow, did you add new unit tests?

[x] N/A

I have tested this PR on the following platforms/os:

[ ] Raspberry Pi OS Manual Build
[ ] SeedSigner OS on a Pi0/Pi0W board
[x] Other

ACK

ACK


Implement CLI method(s): StarterKits

braindump, intended to start discussion. nothing here is prescriptive.

At any time, a user should be able to ask the PL CLI what starterkits are available for download.
Current exposed command on editions:

https://github.com/pattern-lab/patternlab-node/blob/dev/core/lib/patternlab.js#L528-L530
https://github.com/pattern-lab/edition-node-gulp/blob/master/gulpfile.js#L115-L118

Proposed CLI command:
patternlab starterkit --install
With no additional parameters, perhaps it suggest like https://github.com/pattern-lab/patternlab-node-cli/blob/master/bin/init.js#L236
Proposed option:
patternlab starterkit --install --starterkit-mustache-demo
With this option, it reaches out to install from npm if needed, and then installs similar to

https://github.com/pattern-lab/patternlab-node/blob/dev/core/lib/patternlab.js#L531-L533
https://github.com/pattern-lab/edition-node-gulp/blob/master/gulpfile.js#L120-L123

I have those implemented but took them out to have a minimal set of features to start with. I will reintroduce them.


updating to latest version of ng-file-upload

HI, is there any interest in updating ng-file-upload ?
ng-admin uses an old and buggy version (7.0.4) . Current version is 12.0.4 with lots of improvement and bug fixes.

Could be looked at with https://github.com/marmelab/ng-admin/issues/1230


Issue 937: add CommandGetLastMessageId to make reader know the end of topic

This is the first version to collect suggestion to achieve it.
Motivation
We have recently introduced the concept of topic "Reader" as an alternative to the traditional pub-sub consumer abstraction.
A common followup request has been to have a way to identify when the reader has reached the last published entry on the topic.
There is no currently direct way to achieve that and using readNext(timeout) doesn't help because in case the client is not connected to broker, it doesn't mean that there are no more messages to read.
There are a few workaround that are not easy or desirable (eg: terminating the topic, or using HTTP admin API to check the backlog on the reader).
Since this is a common theme, we should have a good way to handle this.
Modifications

add CommandGetLastMessageId in PulsarApi.proto;
implementation CommandGetLastMessageId;
add a testcase in TopicReaderTest

Result
A new command CommandGetLastMessageId  added in binary protocol

/cc @merlimat for review

retest this please

retest this please

@zhaijack : can you address @merlimat and @ivankelly 's comments? we need this change for function worker.

Thanks, have resolved all the comments, and fixed rebase conflict.


addressing issue 30

I was seeing the same errors that jamesw05 described in issue 30, so I changed a few of the sql queries in the osm2pgsql template. There have been a number of updates to the imposm template recently, and I know that these two changes don't bring the two templates in line entirely, but I have stopped seeing the error messages.

Thanks :)


Finalize application and web interface for ports scan detection

Update branch  "detections-portscan" by BC thesis: https://is.muni.cz/auth/th/433592/fi_b/

Also transform detection script to the current format (by the template).

Done


Attempted import errors in external libraries

Describe the bug
Some external libraries causing compilation failures.
Ex.

Attempted import error: 'CalendarContainer' is not exported from 'react-datepicker'.

./node_modules/draft-js-utils/esm/getEntityRanges.js
Attempted import error: 'OrderedSet' is not exported from 'immutable'.

(just few examples)
It is most likely I have set swc-loader incorrectly for the node_modules folder.
Input code
No response
Config
//Using Craco to modified CRA and remove babel

// add swc-loader for non app code
    addAfterLoader(webpackConfig, loaderByName('babel-loader'), {
      test: /\.(js|mjs)$/,
      exclude: paths.appSrc,
      loader: require.resolve('swc-loader'),
      options:{
              jsc: {
                externalHelpers: true,
                target: 'es5',
                parser: {
                      syntax: 'ecmascript',
                      jsx: true,
                      dynamicImport: true,
                      exportDefaultFrom: true
                    }
              },
            },
    });
// Add swc-loader for app code
    addAfterLoader(webpackConfig, loaderByName('babel-loader'), {
      test: /\.(js|mjs|jsx|ts|tsx)$/,
      include: paths.appSrc,
      loader: require.resolve('swc-loader'),
      options:{
              jsc: {
                externalHelpers: true,
                target: 'es5',
                parser: {
                      syntax: 'typescript',
                      tsx: true,
                      dynamicImport: true,
                    }
              },
            },
    });

    // remove the babel loaders
    removeLoaders(webpackConfig, loaderByName('babel-loader'));

Playground link
No response
Expected behavior
Compilation is successful.
Version
1.2.66
Additional context
No response

It looks like to fix this issue I had to install the @types version of certain packages. Is there some config I can modify to not have to replace every package that has this issue?
Ex. for react-scroll-sync I had to install @types/react-scroll-sync.

Is there any verification that this is a bug? Or can we close the issue?

Thanks!


Typescript2 @types not being recognized by the compiler (still throwing errors)

VSCode Version: 1.3.1
OS Version: Win7

Steps to Reproduce:

Install any @types that would normally replace a typings (let's say @types/core-js)
TS Errors will be thrown for things such as require / Promise etc, that shouldn't.

If you manually implement /// <reference<EMAIL_ADDRESS>/> on top of a page, the errors will go away for that page. Of course this shouldn't have to be done, @types should be globally seen by the compiler.
For example:

@MarkPieszak did you configure VS Code to use the latest version of TypeScript (will indicate in the status bar)?

Adding     "typescript.tsdk": "node_modules/typescript/lib" to the settings.json fixed this for me

Forgot to respond yes this fixed it for me as well needed to update tdsk to point to TS globally installed. Apologies.

@types must be resolved according to the nearest tsconfig.json relative to the file. I don't know what vscode does right now, but I know that it does wrong. If it's the tsdk, then by default tsdk should be ./node_modules/typescript/lib relative to each tsconfig.json.


Added options and getAccount(). Removed getAccessToken()

This is quite a big chunk of code which includes several significant changes. I couldn't stop refactoring and it ended up with:

new options for login methods (defined in README)
removed getAccessToken() which was replaced by getAccount() (which now returns email or phoneNumber)
fixed bug for iOS return value
error strings are now consistent in between platforms

Resolves #12


Creating a pull request for v4-dev and v4-dev-xmr

Creating a pull request for v4-dev and v4-dev-xmr branch

What is this supposed to be/do?


Can this be integrated with Django?

Do you mean like displaying this GUI inside a web page built on Django?
I have no experience with Django so I probably won't do this, but if anyone wants to take a stab at it I'll accept a PR as long as its modular and not cluttering the core code. This seems like a good starting point: https://wiki.python.org/moin/PyQt/Embedding Widgets in Web Pages


Getting RC of 1245184 while executing the DFSRRC0 program

We are encountering with Return code of 1245184 when running an step using DFSRRC0 program under OMVS
We are able to run the same steps successfully under the TSO directly.
Can you please help us on how to look at the JES logs for investigation ?

@sbjugali
DFSRRC0 is basically the interface to IMS.  The MVSExec is not loading a full TSO environment, so most likely, this is why it is failing, when loading some specific.
So, maybe a JCLExec or a JobExec is a better way to implement this step.
To troubleshoot it: 1245184 looks like a Decimal value - when converting this Hexadecimal, it turns into 13000.
The System Completion Codes give us more insight:  https://www.ibm.com/docs/en/zos/2.5.0?topic=zmsc-system-completion-codes

Looking at the programmer response, we expect that there is a message in the system log about IEC141I
So, let's look up the IEC message in : https://www.ibm.com/docs/en/zos/2.5.0?topic=iee-iec-messages, which takes us to:
https://www.ibm.com/docs/en/zos/2.5.0?topic=messages-iec141i
The RC in the system log, will then tell us the reason why it failed.

There is a lot lacking in the DBB API with regards to information coming out of any of the IExecute interface classes:
https://www.ibm.com/docs/api/v1/content/SS6T76_2.0.0/javadoc/com/ibm/dbb/build/IExecute.html
So I am all for improving this.  A mind blowing idea would be to tie in the results to Fault Analyzer for easy lookup :)


Fix dynamic require breaking after updating to v8

Changing dir to context breaks dynamic requires. Reverted to fix.
Fixes: #6469

@ijjk could you add an integration test for this so that we don't break it in the future 🙏


Add forth exercise

Add forth exercise

@kytrinyx - question for you. The Travis CI build is failing on my pull request. The problem is that in the src/main/scala directory I have a .scala file that needs to be filled out by the user. The file contains a couple of class definitions that define the interface needed by the unit tests.
In the root is the example.scala file that has a "real" solution. The build.sbt is written to compile the file in src/main/scala, since this is what the user will want. The example.scala is ignored by build.sbt.
Travis CI is trying to compile and run the unit tests, which will fail since the example.scala is ignored.
Any suggestions on how to deal with this case?  I could add Ignore flags on all the unit tests. I'm not sure if there is a better way.
Thanks

Is there a a way to make the build ignore the stub file when running the tests against examlpe.scala?

@kytrinyx - I was making this harder than I needed to. I changed the stub to include traits instead. So, now the user will have a couple of traits to implement. And, the CI build should pass.
Thanks

That sounds good.


Recognise all contributors in README

Use the following application to recognise all contributors to the repo:
https://allcontributors.org/docs/en/overview
Example:

@funbeedev I can take this

@Mogakamo  of course :)


Add chart building + ensure BINDIR is created when running targets

Adds make chart to generate a local helm chart for testing
Creates $(BINDIR) and subdirectories using order only dependencies (see details in the cert-manager repo)
Use $@ where possible
Adds release version, similar to what we have in cert-manager

I'd probably also advocate changing $(BINDIR) to default to _bin for the same reasons we did that in cert-manager but that seemed maybe a change too far for this PR

/test pull-cert-manager-trust-smoke

/test pull-cert-manager-trust-verify
/test pull-cert-manager-trust-smoke

/test pull-cert-manager-trust-smoke

/test pull-cert-manager-trust-smoke

/lgtm


Add editable lastmod&changefreq&priority to SitemapContext

Background
Lastmod, changefreq, and priority attribute values are fixed like below currently.

lastmod: The day site to be accessed
changefreq: "daily"
priority: "0.8"

If they are editable, users may be happier.
What changed

Adding RouteProps param to SitemapContext@add method then user can select their preferred attribute values.
Adding set method to SitemapContext then user can edit existing routes' attribute values.
Adding relevant tests

Note
I did use deno fmt but some formats have been changed.
I was only in purpose of changing sitemap.ts, types.ts and sitemap.test.ts

Thank you for looking through my code and testing it! Really appreciated it.
If you got time, please have a look on my another PR https://github.com/xstevenyung/fresh-seo/pull/17.


Code example causes an error

I'm using .net 4.0 in an asp.net application. I pasted the named caches configuration into my system.runtime.caching node of config verbatim and got an error:
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unrecognized attribute 'physicalMemoryPercentage'. Note that attribute names are case-sensitive.

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

ID: a67406db-e7fe-e4d3-1d5c-9a4d581f5ff6
Version Independent ID: e70febe8-b1c1-187d-19f9-88f8c26cf07a
Content: <system.runtime.caching> Element (Cache Settings)
Content Source: docs/framework/configure-apps/file-schema/runtime/system-runtime-caching-element-cache-settings.md
Product: dotnet-framework
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

Thanks for pointing this out, @DarthDerrr. The example fails because the correct name of the attribute is physicalMemoryLimitPercentage. I've opened #8021 to correct the documentation.


Improving The OTP functionality

Issue Summary
Inhancing the OTP fucntionality implemented for forgot password
Issue Description
Currently the OTP is generated by random string, replace it by using an npm package otp-generator
Also implement feature for expiration of otp currently the otp code is saved but its should be erased after 2 minutes  (changes should be done in frontend + database)
Proposed Solution (Optional)
No response
Priority
High - Requires urgent attention
Category

[X] Enhancement
[ ] Refactor
[X] Security
[ ] Design
[ ] Other

Additional Context (Optional)
No response

i would like to contribute on this

Sure, Will add labels on 1st Jan

is the otp sending feature added ? i have tried to reset the password but i doesnt got any email with code

It was previously working but because nodemailer module is now deprecated it's not sending mails

Should I make that change? Should I use EmailJS as a third-party tool, or do you have any other recommendations?

Yah sure you can do that, just create an issue regarding that I will assign you

ohk  i will create the issue


Migrating from Sharepoint 2013 On-Premise

I used to be able to use previous Version from this Tool. Bur now i can't seem to login to my On-Premise anymore. It keeps asking for my credentials. I have a TMG as a reverse Proxy whith ("No delegation, but client may authenticate directly") - is that the problem?

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

ID: 36d01d11-eea9-7f49-693d-25c3fecc6253
Version Independent ID: 6749a619-2b75-1561-81e9-b45888c58c4b
Content: How to use the SharePoint Migration Tool
Content Source: migration/how-to-use-the-sharepoint-migration-tool.md
Product: sharepoint-server-itpro
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@Lephas thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close


Adding github action for automated submission and dependabot upkeep

Hi @vict0rsch!
Love PaperMemory!!! It makes note taking on arxiv to another level. I'm spreading it to my friends :D Also, I was looking for ways to contribute, and found that since your codebase doesn't have automated ci, I thought adding that might be helpful.
First, I added a dependabot config for you so it should bump dependencies version automatically. Then, I created 2 workflows in this PR:

automerge: automate the dependabot merging to reduce PR noise, using https://github.com/fastify/github-action-merge-dependabot
submit: automate the zip submission process to the Chrome/Firefox/Edge stores automatically, using bpp . It is set to run manually from the github action tab, but we can tweak it to run as frequent as you wish! The only thing you would need to create is a SUBMIT_KEYS github repository secret.

The SUBMIT_KEYS secret is a json, with the schema defined here.
Here's a sample key for you:
{
  "$schema": "https://raw.githubusercontent.com/plasmo-corp/bpp/v1/keys.schema.json",
  "chrome": {
    "clientId": "123",
    "refreshToken": "789",
    "extId": "abcd"
  },
	"firefox": {
		"apiKey": "123",
		"apiSecret": "789",
		"extId": "abcd"
	}
}

You can find instructions on how to get those keys in the schema, or if you use vscode, the schema should provide hint/intelisense when hovering over the json properties. If you need any help in setting up the keys, feel free to @ me! Otherwise if this doesn't seem necessary, feel free to close the PR :)

That's amazing @louisgv. Thanks so much. It's a personally challenging moment so sorry for being a little laggy to respond and I'll probably take a few more days to check everything out and merge but it's great to have you contribute! We can discuss further contributions if you wish to, I've been driving this alone and mostly for my own sake so feel free to make suggestions too!

That's amazing @louisgv. Thanks so much. It's a personally challenging moment so sorry for being a little laggy to respond and I'll probably take a few more days to check everything out and merge but it's great to have you contribute! We can discuss further contributions if you wish to, I've been driving this alone and mostly for my own sake so feel free to make suggestions too!

I'm glad it was helpful :D


Don't fatal on epoll wait

This removes a log fatal on epoll wait for OOM events.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Was this used as an exit condition before or was the loop never supposed to exit?

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2471   +/-   ##
=======================================
  Coverage   44.76%   44.76%
=======================================
  Files          92       92
  Lines        9483     9483
=======================================
  Hits         4245     4245
  Misses       4555     4555
  Partials      683      683

Flag
Coverage Δ

#linux
48.98% <ø> (ø)
:arrow_up:

#windows
41.03% <ø> (ø)
: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 02579c8...8956b1b. Read the comment docs.

@dmcgowan updated

I may have missed context here but what error is returned from epoll wait if the fd gets closed?

LGTM

LGTM