KeyError: 'instruction'

I have successfully run python run.py --exp-config vlnce_baselines/config/nonlearning.yaml --run-type train and got "data/checkpoints/ckpt.x.pth".
But an error occurred when I run python run.py --exp-config vlnce_baselines/config/nonlearning.yaml --run-type eval ,
I0414 23:24:12.502465 9994 simulator.py:146] Loaded navmesh data/scene_datasets/mp3d/2azQ1b91cZZ/2azQ1b91cZZ.navmesh
2021-04-14 23:24:12,506 Initializing task VLN-v0
2021-04-14 23:24:16,634 Loaded weights from checkpoint: data/checkpoints/ckpt.0.pth
2021-04-14 23:24:16,635 Finished setting up actor critic model.
Traceback (most recent call last):
  File "/home/wangzihao/VLN-CE/run.py", line 86, in <module>
    main()
  File "/home/wangzihao/VLN-CE/run.py", line 41, in main
    run_exp(**vars(args))
  File "/home/wangzihao/VLN-CE/run.py", line 80, in run_exp
    trainer.eval()
  File "/home/wangzihao/hab015/lab/habitat_baselines/common/base_trainer.py", line 109, in eval
    checkpoint_index=prev_ckpt_ind,
  File "/home/wangzihao/VLN-CE/vlnce_baselines/dagger_trainer.py", line 807, in _eval_checkpoint
    observations, config.TASK_CONFIG.TASK.INSTRUCTION_SENSOR_UUID
  File "/home/wangzihao/VLN-CE/vlnce_baselines/common/utils.py", line 25, in transform_obs
    instruction_sensor_uuid
KeyError: 'instruction'
Exception ignored in: <bound method VectorEnv.__del__ of <habitat.core.vector_env.VectorEnv object at 0x7f4415a2d9e8>>
Traceback (most recent call last):
  File "/home/wangzihao/hab015/lab/habitat/core/vector_env.py", line 518, in __del__
    self.close()
  File "/home/wangzihao/hab015/lab/habitat/core/vector_env.py", line 400, in close
    write_fn((CLOSE_COMMAND, None))
  File "/home/wangzihao/.conda/envs/hab015/lib/python3.6/multiprocessing/connection.py", line 206, in send
    self._send_bytes(_ForkingPickler.dumps(obj))
  File "/home/wangzihao/.conda/envs/hab015/lib/python3.6/multiprocessing/connection.py", line 404, in _send_bytes
    self._send(header + buf)
  File "/home/wangzihao/.conda/envs/hab015/lib/python3.6/multiprocessing/connection.py", line 368, in _send
    n = write(self._handle, buf)
BrokenPipeError: [Errno 32] Broken pipe

When I debugged, I found that the dict variable observations in line 806 of "dagger_trainer.py" had no key instruction, only keys rgb,depth in it.
Further，I found that the dict variable observations_spaces line 139 of "habitat/core/vector_env.py" differed between train and eval, keys rgb,depth,instruction,progress,vln_oracle_action_sensor in train but keys rgb,depth in eval.
What's wrong with the command？

have you figured it out?


Enable switch between checkpoint copies in webui

Set ckpt-dir so that user can switch between checkpoint copies using webui.
Also colab removed trailing white spaces.

pretty, mind if i add to my fork, trying to assemble a bunch of qol/accessibility options to bens

pretty, mind if i add to my fork, trying to assemble a bunch of qol/accessibility options to bens

Sure, feel free to use it as you wish.

Much appreciated. I'll add It tonight
On Sat, Dec 24, 2022, 4:11 AM zuencap @.***> wrote:

pretty, mind if i add to my fork, trying to assemble a bunch of
qol/accessibility options to bens
Sure, feel free to use it as you wish.
—
Reply to this email directly, view it on GitHub
https://github.com/TheLastBen/fast-stable-diffusion/pull/1094#issuecomment-1364503151,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZPYLSGV5LCDS7BUXMBJUE3WO3D6TANCNFSM6AAAAAATER3ZKM
.
You are receiving this because you commented.Message ID:
@.***>


support(menu): Fix cycle up

Solves #314
Problem: When moving on the menu (MenuPreviousItem & MenuNextItem) going for last to first did work but going from first to last didn't.
Solution: Updated the helper used to get the new position on any of the actions that change menu position to cycle up and down.

There were no tests for the store so I added some to cover the cases of my changes. While writing the tests I found that MenuPosition could set the position out of range so also added the necessary changes to prevent that.

NOTE: this is the first time I work with Native Reason and also my first contribution to the project. I'm not sure the tests follow the approach the team likes so please let me know what could be improved :sweat_smile:

This is my first PR. I have a few questions general questions.

Is there some format that should be followed for the branch names (since it's a fork maybe it's not relevant) and commit messages?
Is there a format for the PR? Maybe is worth adding a template :smile:

And also a question about this particular PR. I did not see any tests for src/editor/Store, should I tests for this changes? Is adding tests for src/editor/Store planned? If so maybe is worth adding and issue for that.

@gillchristian thanks for the PR :+1: , re. commit messages and branching we don't have any strict rules around that.
Re the format of the PR there's some guidance re contributing in general like how to go about tackling a problem but if you mean the content of your pr message, nope no strict guidance.
I'm personally a fan on reducing friction as much as possible @bryphe might have some other thoughts.
Re. tests, I think we'd be all for any tests tests you add :rocket:

if you mean the content of your pr message

Yes I meant the message.

I think we'd be all for any tests tests you add

Great! I'm new to Reason and Revery, I'll check the other tests and see what I can add. Most probably I'll propose something here before adding anything.

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

This is ready for review :sweat_smile:

@gillchristian is a friend of mine @bryphe, so you can blindly merge the pr 😆
In all seriousness, i'm really happy that people are contributing here! (sorry for the spamy comment, i'm just happy about this)

I see tests failing on MacOS for a different suite. I don't have a Mac to reproduce. On my machine (Ubuhtu 18.04) all run fine so I cannot check if my changes did break something.

Sorry for the delay on my end @gillchristian ! The change looks great - thank you for going the extra mile and figuring out how to wire up tests for the Store - that will be very useful as we focus on stability.

In all seriousness, i'm really happy that people are contributing here! (sorry for the spamy comment, i'm just happy about this)

@lpalmes me too! 👍 Awesome that you guys know each other 😄

I see tests failing on MacOS for a different suite. I don't have a Mac to reproduce. On my machine (Ubuhtu 18.04) all run fine so I cannot check if my changes did break something.

I kicked off the build again to see if it's an intermittent failure. I'll check out on my Mac if it's still failing - otherwise, will bring this in once its green. Thank you very much for the contribution!

No worries. Whenever this can move forward is fine to me.
I'm happy you liked the tests, if there's anything that could be improved let me know. Now that I have an idea of how to write these tests I think I will work on increasing the coverage of Store tests.

No worries. Whenever this can move forward is fine to me.

Cool! I'm a bit short on time at the moment (heading to Paris for ReactEurope), but will look again when I come back. Unfortunately, this reproduced consistently on the build machine - I think there is some interaction with the textmate tests (which host their own service).
Once we have a native version of vscode-textmate - https://github.com/onivim/oni2/issues/161 - these tests should, as a side effect, get more reliable too!

@bryphe it's been a while since I opened this PR, even the first release happened :tada:
I rebased with master and there are two problems.
First I force pushed to my branch without your changes :face_with_head_bandage:
Also I tried to run the tests again but I get an error when building, maybe it's better to ask in Discord about this :thinking:
$ esy '@test' build
info building reason-libvim@github:onivim/reason-libvim#5c81c76@d41d8cd9
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: reason-libvim@github:onivim/reason-libvim#5c81c76
    # esy-build-package: pwd: /home/gillchristian/.esy/3____________________________________________________________/b/reason_libvim-445ec134
    # esy-build-package: running: 'refmterr' 'dune' 'build' '-p' 'libvim'
        discover src/c_flags.sexp,src/cxx_flags.sexp,src/flags.sexp
    -L/home/gillchristian/.esy/3/i/libvim-8.10869.19-49bdd02b/lib
        ocamlopt src/vim.cmxs (exit 2)
    (cd _build/default && /home/gillchristian/.esy/3/i/ocaml-4.7.1004-a6ae015e/bin/ocamlopt.opt -w -40 -g -shared -linkall -I src -o src/vim.cmxs src/vim.cmxa)
    /usr/bin/ld: cannot find -lacl
    collect2: error: ld returned 1 exit status
    File "caml_startup", line 1:
    Error: Error during linking
    error: command failed: 'refmterr' 'dune' 'build' '-p' 'libvim' (exited with 1)
    esy-build-package: exiting with errors above...

  building reason-libvim@github:onivim/reason-libvim#5c81c76
esy: exiting due to errors above

If you are on Ubuntu, to build now you also need the libacl1-dev package, which should fix that linker error.

Unfortunately this is pretty out-of-date and seems like it would be superseded by the work @glennsl is doing on the menu - will close out.


Uses app name, not short name

Opsworks uses the short_name for the directory under /srv/www, whereas it appears omc is using the app's "long" name.
Observed using the console command on an app whose short name does not match the long name.

 Must be an Amazon bug then (argh)...


feat(airflow): Add s3fs python package, needed for pandas S3 access

Description
Please add a description here.
Definition of Done Checklist

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
Please make sure all these things are done and tick the boxes

- [ ] Changes are OpenShift compatible
- [x] All added packages (via microdnf or otherwise) have a comment on why they are added
- [ ] Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
- [ ] All packages should have (if available) signatures/hashes verified
- [ ] Does your change affect an SBOM? Make sure to update all SBOMs

This enables us to e.g.
    @task
    def write_repos_to_s3(df: pandas.DataFrame):
        staging_table_name =''.join(random.choice(string.ascii_lowercase) for i in range(32))
        df.to_parquet(
            f"s3://{S3_BUCKET}/staging/github/{staging_table_name}/repos.parquet",
            storage_options={
                "key": S3_ACCESS_KEY_ID,
                "secret": S3_SECRET_ACCESS_KEY,
                "client_kwargs": {'endpoint_url': S3_ENDPOINT}
            }
        )
        return staging_table_name

Also see here
https://github.com/stackabletech/docker-images/pull/411/files :)

I was thinking about the same, but I did not want to clog up the Dockerfile, so I put the reason in the commit message ;)
Added it to Dockerfile as well

Hmm, if think technically I can't check the other boxes. Do we want to make some exceptions for pip? Is there any guide regarding the boms yet?

No SBOM guide yet. I'm working on that.
So, this will need to change again but good enough for now

As always. Those are just templates. Leave the boxes that make sense, remove the others.
I think this is good to go. I'm only on my phone but I believe I approved it as well

Yeah you did, thanks!


Allow configuring websocket port

Sometimes I need to run multiple recordings on the same machine
Or just use random port (preferably)

Also running into an issue with it.


Update GPIO settings for A+/B+ boards

The A+ and B+ boards have a few more GPIO pins that we need to account for.

Closing since there was no response, to pull this off my PR queue. The code is still available here for those interested.


Can this work for Godot 4+ games with multiplayer and open world chunks?

Test chunks link: https://github.com/WithinAmnesia/ARPG/discussions/15
I'm trying to find a way to seamless load and unload chunks for a 2D multiplayer game project to make an open world with a working server using Godot 4.2.1.NET.
How can this work for multiplayer and what is needed for this to potentially work? What options can be used for chunk loading and unloading seamlessly in Godot 4.2.1.NET? Please give feedback.

Also https://github.com/Zylann/voxelgame/issues/101#issuecomment-1958792464 + https://github.com/WithinAmnesia/ARPG/discussions/16#discussioncomment-8550378 Big 2D/3D hybrid progress update! It all works!


Compress accessions.tsv

Description of proposed changes
Compress accessions.tsv to avoid single-file size limits on GitHub.
Cc: @emmahodcroft @AngieHinrichs for visibility.
Related issue(s)

Related to #263
Testing
Todo.

[x] Locally by hand
[x] On CI

Looks great, thanks @tsibley!

@AngieHinrichs This is now merged, so you'll need to update your references to accessions.tsv → accessions.tsv.gz. :-)

Awesome, thanks @tsibley!  Speaking of which, it's time to roll another one here...


Add files via upload

https://www.fls-wiesbaden.de
https://bg.fls-wiesbaden.de/informatik.html
https://bg.fls-wiesbaden.de/kontakt.html

@aburkard-ksh First stage of verification passed, official domain is fls-wiesbaden.de as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@aburkard-ksh Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Change state of request to Open

As an Intake Analyst
I want to change a request from Intake in Progress to Open
so that the request can be actioned

Assumptions & Scope
What are the assumptions for this story?
What is in and not in scope?
Closing and redirecting a request are not in scope.
Out of scope: fields within the request are out of scope.
Assigning a request?
Acceptance Criteria
Scenario 1: Open a request

GIVEN a flex team analyst is on a request in Intake in Progress:
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/663873012
AND all the mandatory fields are filled
WHEN the analyst clicks on the dropdown menu for state
THEN the options will be Open, Redirect, Closed

Scenario 2: Click on Open

GIVEN has clicked the State update dropdown
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/663873013
WHEN the analyst clicks Open
THEN a modal will open:
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/768088424
AND the assignee will be selected
AND the options will be to 'Save Change' or 'Cancel'
AND the analyst will see who is assigned (i.e. Flex Team/Flex analyst)

Scenario 3: Cancel to Call for Records

GIVEN the Flex Analyst has opened the modal for 'Open'
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/768088424
WHEN ... I select "Cancel" in the modal
THEN the state of the request will remain "Intake In Progress"
AND the drop menu and modal will close
AND the request will remain in the the Flex Team queue under 'Intake in Progress' state

Scenario 4: Save request into 'Open' state

GIVEN the Flex Analyst has opened the modal for 'Open'

https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/768088424

WHEN ... I select "Save Change" in the modal
THEN the state of the request will become "Open"
AND the drop menu and modal will close
AND the request will remain in the the Flex Team/analyst queue under Open state
AND the request will be assigned to the Flex Team/flex team analyst
...

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
@xxx - please link the Design here
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

Please reference scenarios for the main source of truth, as some designs are outdated

Open button at bottom will be removed

Estimate factors in view change, stage management in front end, rule changes, data capture spread between two components

Design Update of Modal with removed dropdowns as discussed earlier this week


Bluetooth improvements

Adds:

async pairing process,
passkey pairing,
numeric comparison pairing,
legacy/pin-code pairing,
EIR parsing (name, class, supported uuids retrieving),
local device class setting,
UUID code extracted to a separate unit,
bugfixes.

https://jenkins.code.rdkcentral.com/job/github-triggered/868/ started

Copyright scan failure
Commit: 2837c7ebed75b885a45992d7028af349c38fa1c7
Report detail: https://gist.github.com/78a39e4a88968cde02491eb0638e2216

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/Thunder/81/rdkcentral/Thunder

Commit: 2837c7ebed75b885a45992d7028af349c38fa1c7

Report detail: gist

https://jenkins.code.rdkcentral.com/job/github-triggered/870/ started

Copyright scan failure
Commit: b1c98bcd066e17c7ed67413ea486abd459fc99b0
Report detail: https://gist.github.com/0f76ece8caeaedcb92d6b01fbe530894

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/Thunder/81/rdkcentral/Thunder

Commit: b1c98bcd066e17c7ed67413ea486abd459fc99b0

Report detail: gist

"&copy" flagged by protex :)

https://jenkins.code.rdkcentral.com/job/github-triggered/879/ started

Copyright scan failure
Commit: fb88f3ff1d96b9290b11efca97a3f7dcaf61da01
Report detail: https://gist.github.com/81c240e1dd41a7b708a473e411adb6a2

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.


api-docs: Update docs to reference max lengths in register response.

Updates areas in the API documentation that reference the maximum length of a stream message topic to note the max_topic_length.
Updates areas in the API documentation that reference the maximum length of a stream name to note the max_stream_name_length and areas that reference the maximum length of a stream description to note the max_stream_description_length.
All of these maximum values are sent by the POST /register response.
See relevant CZO conversations:

#api documentation > direct message search operators
#api documentation > max size

Notes:

In #24401, we landed on documenting the units for the message length as "Unicode code points". I used that same language for these properties as well. Previously, either "characters" or nothing was used to denote the unit for the integer value.

Screenshots and screen captures:

Register queue - max_X_length.
Current documentation

Send a message
Current documentation

Edit a message
Current documentation

Subscribe to a stream
Current documentation

Update a stream
Current documentation

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

This is great, merged, thanks @laurynmm!


emails are imported more than once

Describe the bug
I run mail2most as a systemd service. In the config file i use the following filter section:
  [Profile.Filter]
		Folders = ["Inbox"]
		Unseen = true
		From = [""]
		To  =<EMAIL_ADDRESS>		Subject = [""]
		TimeRange = "24h"
		IgnoreMailErrorNotifications = true

After an E-Mail gets imported it is still marked as unread. I don't know whether the idea is that the email gets marked as unread or whether mail2most is supposed to keep track of what it already imported in some other way. However, the effect is that the same email gets imported with every time mail2most runs ( every TimesInterval ).
To Reproduce
Steps to reproduce the behavior:

configure mail2most with an imap email account and a mattermost account
send email to said account
watch target channel in mattermost
See duplicate of same email getting posted to target channel every time mail2most looks for new emails

Expected behavior

Email gets sent to configured email account
gets imported once
further runs of mail2most ignore same email because it was "seen" before

Release version
v1.11.9
Architecture
linux amd64

My email provider is hostpoint.ch. I do not know what they are using as an MTA, I just know they run everything on FreeBSD.
A data.json file was created,  but it only contains
[
  null
]

Here is the systemd service definition that I am using:
# mail2most
[Unit]
Description=mail2most

[Service]
Type=simple
WorkingDirectory=/opt/mail2most
ExecStart=/opt/mail2most/mail2most -c conf/mail2most.conf
Restart=always
RestartSec=60

[Install]
WantedBy=multi-user.target

Hm interesting. That seems to be the issue. Do you see anything in the logs that mail2most can not write the data.json?

Mar 08 15:22:09 mattermost mail2most[1098456]: time="2024-03-08T15:22:09+01:00" level=info msg="unseen mails" ids="[2 3 4 5]"
I noticed that when I delete the data.json file that it gets re-written when mail2most finds and imports an email that fits the filter critera, but it contains again just the empty array.

Are the messages send to mattermost? Can you provide the full log output (don't forget to remove any security relevant information)?

i have the same issue it drains the vps bandwith

tl;dr: configure mattermost user email instead of username worked for me.
I see the same behavior.
time="2024-05-26T15:50:12+02:00" level=info msg="found mail" subject="Redmine to mattermost support channel test" uid=984539465
time="2024-05-26T15:50:12+02:00" level=debug msg="user not found in system" error=": Unable to find the user., failed to find User: resource: User id<EMAIL_ADDRESS>time="2024-05-26T15:50:12+02:00" level=debug msg="mattermost post" bytes=556 channel=o4jdaq598py4xdcifymtfosimy subject="\n>_[Mattermost] Your password has been updated_\n\n"
time="2024-05-26T15:50:12+02:00" level=error msg="Mattermost Error" Error=": Invalid or missing email parameter in request URL., "
time="2024-05-26T15:50:12+02:00" level=debug msg="mattermost post" bytes=412 channel=o4jdaq598py4xdcifymtfosimy subject="\n>_Redmine to mattermost support channel test_\n\n"
time="2024-05-26T15:50:12+02:00" level=error msg="Mattermost Error" Error=": Invalid or missing email parameter in request URL., "

The problem might be "Invalid or missing email parameter in request URL"
I set the mattermost log level to debug to see if this is an error coming from mattermost, but there is no trace of this.
The messages are read from the mailserver, the posting to the mattermost channel happens successful. The only think not happening is the writing of the data.json, and therefore the emails are not remembered as read.
I played around a bit and even though my mattermost server is configured to allow usernames or emails as login, apparently the api does not. I had to change the username in the mail2most.conf to the mattermost email address. Then the data.json is properly written.


Reference management(DBRefs) and performance

Currently the ODM makes reference performance a bit of a pain. Loading a full object in a state recognizable via the documentIdentifiers hash table seems to be required for a reference to be correctly stored. Is there a specific reason not to allow referencing via a holder document by ID field type, thus removing the need for merge/refresh?
I'd gladly submit a pull request, but I'd like to know if there is an intention behind this choice as the trade off doesn't seem to be worth it.

Closing as this issue seems to be not relevant now in 2017. Please re-open if it's still valid


Using options API

Hey there,
I'm trying to use the library as recommended by just adding the main js file my project instead of installing it as a dependency. The rest of my codebase I'm using the options API though and I'm having trouble getting this to work with the options API. (Works fine using composition API).
What's giving me trouble specifically is the watcher. I've tried two different ways (and many more actually) but none of these seem to work. The watcher is never triggered:
<script>
export default {
  data(){
    return {
    }
  },
  props: ['options', 'list', 'itemKey', 'tag'],
  emits: ['choose', 'unchoose', 'start', 'end', 'add', 'update', 'sort', 'remove', 'filter', 'move', 'clone', 'change'],
  mounted(){
    this.$watch(
      () => {
          return this.$refs.containerRef
      },
      (val) => {
        console.log(val)
        alert('App $watch $refs.containerRef: ' + val)
      }
    )
  },
  unmounted(){
    if (this.$refs.sortable) {
      this.$refs.containerRef = null;
      this.$refs.sortable = null;
    }
  },
  watch: {
    containerRef(newDraggable, oldDraggable){
      if (newDraggable) {
        this.$refs.sortable = new Sortable(newDraggable, {
          ...props.options,
          group: "shared",
          onChoose: (event) => this.$emit("choose", event),
          onUnchoose: (event) => this.$emit("unchoose", event),
          onStart: (event) => this.$emit("start", event),
          onEnd: (event) => this.$emit("end", event),
          onAdd: (event) => this.$emit("add", event),
          onUpdate: (event) => this.$emit("update", event),
          onSort: (event) => this.$emit("sort", event),
          onRemove: (event) => this.$emit("remove", event),
          onFilter: (event) => this.$emit("filter", event),
          onMove: (event, originalEvent) => this.$emit("move", event, originalEvent),
          onClone: (event) => this.$emit("clone", event),
          onChange: (event) => this.$emit("change", event),
        });
      }
    }
  }
}
</script>

Any thoughts on how to implement the watcher using options?
And thanks for the great work, this has been super useful!

Hmmm -- well, this isn't a fix but is there a reason you need to use the options API? I personally much prefer the composition API after using it, and at least this component seems fairly easy to convert over.
In terms of the problem, I'm not sure why it's occurring, but I think it's due to trying to watch containerRef. At least with the composition API you're supposed to watch for a data item belonging to the ref. https://stackoverflow.com/questions/39035498/vuejs-watch-refs has some more info.
Is containerRef(newDraggable, oldDraggable) never firing at all?

Closing without more information


make install error 2

help2man -N --name='Print checksum of important database fields.  Useful for quickly determining whether several KSMs are in sync.' --version-string=1.16 ./ykksm-checksum > ykksm-checksum.1
help2man: can't get `--help' info from ./ykksm-checksum
Try `--no-discard-stderr' if option outputs to stderr
Makefile:109: recipe for target 'ykksm-checksum.1' failed
make: *** [ykksm-checksum.1] Error 2

ykksm-checksum has a dependency on the DBI perl module. This should probably be made clearer.


custom_command example

Can we get an example of custom_command I couldn't figure it out so easily. thanks

Sorry, yeah. I'll try and explain it better. I've also updated the docs  slightly. The function will receive a dictionary as its first argument which contains helper functions. Optionally, it can also accept a second argument, which will be whatever you pass to custom_command as the second argument when you call it.
Here's an example of one I use.
from squeezebox_controller import commands

def morning(helper, details):
      if "player" not in details:
        raise Exception("Player not specified")
      mac_addresses = helper['player_lookup']
      player_mac = mac_addresses[details['player']]
      # turn on squeeebox
      helper['make_request'](player_mac, commands["POWER ON"])
      # make custom request that plays my favourite radio show
      action_url = helper['base_url'] + "/plugins/Favorites/index.html?action=play&index=1&player="
      helper['requests'].get(action_url+player_mac)

x.add_custom_command("morning_radio", morning, True)
x.custom_command("morning_radio", {"player": "kitchen"})
x.simple_command({"command": "VOLUME UP"})

Note, because I set the caching flag to True on add_custom_command, the player was remembered for the subsequent VOLUME UP command.

I was looking to just add a simple command. I wanted a command to pause and another to unpause not the standard pause which toggles. in the end I cheated a bit and added to the commands dict  because it was easier for me.
from squeezebox_controller import SqueezeBoxController as SBC, commands

commands.update({"PAUSE on": ["pause", "1"],"PAUSE off": ["pause", "0"]})

x=SBC('LMServer',9000)

params = {
    "player": 'piCorePlayer',
    "command": 'PAUSE on'
}
x.simple_command(params)

Also if I can ask why do you need a custom command for playing favorites? can't it all be done using simple commands in its own function?
I added favorites by: commands.update({"FAV1":["favorites","playlist","play","item_id:0"]})  so it can use the jsonrpc interface.
def morning(player)
    player 'power on'
    player 'play fav #1'
    player 'vol up'

yes, that works too!


[Skeleton] Add resnet application skeleton

[Skeleton] Add resnet application skeleton

This patch adds resnet application skeleton

**Self evaluation:**
1. Build test: [X]Passed [ ]Failed [ ]Skipped
2. Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1334. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

I wonder about #941.

I wonder about #941. Do you think you can work on top of it or discuss once with @jijoongmoon about it.

We've discussed offline to make a new PR. Thanks for sharing the concern :)

So what about #941 then?

Some part of it will be copied and pasted from #941 with author.


NETOBSERV-602 Fix query stats computed for topology

https://issues.redhat.com/browse/NETOBSERV-602 (follow-up)
The biggest issue was stats being picked up only for the first metric, which obviously could not produce correct global statistics
On top of that, I did the following changes:

Use the already computed rates instead of computing it again
Decouple FlowsQuerySummary vs MetricsQuerySummary (separation of concerns; the two resulting components end up being quite different)
For overview, add more info in stats tooltip to help user understand what the 2 compared values are.

@memodi stats between flow table and topology are much more consistent:

/ok-to-test

/ok-to-test

/retest

/ok-to-test

/approve

merging (@jpinsonneau previously approve, it was just rebased)


edb.materials.load_amat(material_file) loading wrong material

🔍 Before submitting the issue

[x] I have searched among the existing issues

🐞 Description of the bug
Loading Amat files provides wrong material values in EDB
✅ Expected behavior
get correct values
📝 Steps to reproduce
NA
📃 Relevant log output
NA

@svandenb-dev Is it related to the discussion we had last friday ? If not, can you show me a reproducer so that I could help you on that ?

@SMoraisAnsys this was reported by users. Loaded material values are wrong. To reproduce we just need to load the file and check material properties

I'm not able to reproduce the problem but there is something that we should rework with the way materials are currently handled. Sometimes their names are handled as they are provided, e.g. "FR4_epoxy", and other times the names are "lowered", e.g. "fr4_epoxy". This is an issue when one is trying to perform multiple actions mixing those concepts, e.g. materials duplicate, _load_materials.
How would you like to work on this issue ?

Recent refactoring and features should have handled this issue, see #290 and #361.
Closing issue but feel free to open it back with extra information if recent updates were not sufficient enough.