Implement methods and properties for events

I'd be happy to help fill out some of the DOM APIs. Here's my first attempt at filling out the properties for the various Events that have been defined.
Some thoughts/questions:

I've mostly avoided adding any API marked as "obsolete/deprecated/non-standard."
What would be a good way to test these properties? Just a simple test that creates the object and gets+sets the properties?
Most properties follow the simple forwarding pattern of js!( return @{self}.foo; ).try_into().unwrap(). Would it be worthwhile to make a macro for getters/setters to reduce this boilerplate?

Apart from a few minor issues this looks great, thanks a lot!

I've mostly avoided adding any API marked as "obsolete/deprecated/non-standard."

Yep. I don't think such APIs should be added; if the user really wants to use a non-standard API he/she can do it manually with the js! macro.

What would be a good way to test these properties? Just a simple test that creates the object and gets+sets the properties?

That's a very good (and still pretty much open) question! There are a few problems/issues concerning running tests in this crate:

Currently my Travis job runs the tests with Node.js, so it will blow up on any tests that use Web-specific APIs. (Basically anything which isn't implemented by Node.) So for now any tests for Web APIs would have to be temporarily annotated with something like #[cfg(web_api_tests)] to disable them by default.
What we really need is a way to run the tests in a real web browser.
cargo-web has some support for running tests under Chrome/Chromium, but it's very hacky, and requires a non-headless Chrome/Chromium. One could, however, run them locally for now, and as long as they would be #[cfg]'d away they wouldn't be a problem on Travis.
What we really need is to rework cargo-web to use headless Chrome/Chromium for running tests, and use a different (better) approach to communicate with it. (Currently cargo-web injects some JS code and uses AJAX to talk with itself; ideally we want to replace it with something like Chrome's debugger protocol.)
Currently it's not possible at all to test stuff like setTimeout, or anything else which is asynchronous for that matter. I haven't thought too deeply how we could fix that yet; it would probably require support from cargo and Rust to handle asynchronicity in tests.

Most properties follow the simple forwarding pattern of js!( return @{self}.foo; ).try_into().unwrap(). Would it be worthwhile to make a macro for getters/setters to reduce this boilerplate?

Hmm... I don't see why not!

Thanks for the thorough + helpful review! I tried to fix the issues mentioned.

Added tests. They are hidden behind a web_api_tests cfg.
Fixed some bugs that the tests caught.
Switched MouseEvent::buttons() to return an opaque type instead of a Vec.
Decided to remove experimental web APIs for now.

Some more possible todo:

Implement the Event constructors. Not sure how the design will look exactly for this (Builder pattern for each event subtype?)
Now that associated constants are stable, use them for static_event_type.

Looks good to me; thanks!

Now that associated constants are stable, use them for static_event_type

Yep!

Implement the Event constructors. Not sure how the design will look exactly for this (Builder pattern for each event subtype?)

Hmm... yeah, since we definitely want to do it in a forward-compatible way something like that would probably be the way to go, e.g. fn new() -> KeyboardEventBuilder< KeypressEvent > defined on KeypressEvent. (Having a generic builder would allow us to reuse it for similar events, like keypress and keyrelease.)


Add at serializer to_slice

This change removes the buffer size generic on the serializer.
For my firmware that uses the simcom grps driver here, the build size is reduced from:
   text    data     bss     dec     hex filename
 318432     120   52888  371440   5aaf0 urcc

to
   text    data     bss     dec     hex filename
 316732     120   52888  369740   5a44c urcc

Nice! Thanks :+1:


Can't move to first slide with moveToSlide

Hi @sheikalthaf,
When changing the value for the input moveToSlide, jumping to the first slide with index 0 doesn't work.
I assume this is because 0 gets evaluated as falsy when using logical operators.
In ngx-carousel.components.ts, line 253:
ngOnChanges(changes: SimpleChanges) {
  // tslint:disable-next-line:no-unused-expression
  this.moveToSlide &&
    !changes.moveToSlide.firstChange &&
    this.moveTo(changes.moveToSlide.currentValue);
}

Changing line 255 to: this.moveToSlide != null && would solve the problem.
Did you have something special in mind, when writing this code, or is this maybe a bug?

@ejahn good spot. Some propper testing should have picked this up. For now setting to -1 works for my usecase.

@ejahn   Fixed the bug in Build v1.3.4
Big thanks to @iamlothian for the solution
Thanks


NO rendering in visdom?

I run this  example script with wisdom==True, but there is no rendering in wisdom:

`import gym
from smarts.core.agent_interface import AgentInterface, AgentType
from smarts.core.agent import Agent
from smarts.zoo.agent_spec import AgentSpec
class SimpleAgent(Agent):
def act(self, obs):
return "keep_lane"
agent_spec = AgentSpec(
interface=AgentInterface.from_type(AgentType.Laner, max_episode_steps=None),
agent_builder=SimpleAgent,
)
agent_specs = {
"Agent-007": agent_spec,
"Agent-008": agent_spec,
}
env = gym.make(
"smarts.env:hiway-v0",
scenarios=["scenarios/sumo/loop"],
agent_specs=agent_specs,
)
agents = {
agent_id: agent_spec.build_agent()
for agent_id, agent_spec in agent_specs.items()
}
observations = env.reset()
for _ in range(1000):
agent_actions = {
agent_id: agents[agent_id].act(agent_obs)
for agent_id, agent_obs in observations.items()
}
observations, _, _, _ = env.step(agent_actions)`

Hi @SHITIANYU-hue,
Try the following instructions with the corrected code below.
$ cd <path/to>/SMARTS
$ python3.8 -m venv ./.venv
$ source ./.venv/bin/activate
$ pip install --upgrade pip wheel setuptools
# Install camera dependency which is required for visualization
$ pip install -e .[camera_obs]
# Build the scenario
$ scl scenario build-all ./scenarios/sumo/loop/
# Launch Visdom in the background
$ visdom &
# Run the example code
$ python3.8 <path to example code>
# Navigate to http://localhost:8097

import gym

from smarts.core.agent_interface import AgentInterface, AgentType
from smarts.core.agent import Agent
from smarts.zoo.agent_spec import AgentSpec

class SimpleAgent(Agent):
    def act(self, obs):
        return "keep_lane"

agent_spec = AgentSpec(
    interface=AgentInterface.from_type(
        AgentType.Laner,
        max_episode_steps=None,
        rgb=True, # Enable RGB image rendering
    ),
    agent_builder=SimpleAgent,
)

agent_specs = {
    "Agent-007": agent_spec,
    "Agent-008": agent_spec,
}

env = gym.make(
    "smarts.env:hiway-v0",
    scenarios=["scenarios/sumo/loop"],
    agent_specs=agent_specs,
    visdom=True, # Enable Visdom
)

agents = {
        agent_id: agent_spec.build_agent()
        for agent_id, agent_spec in agent_specs.items()
    }

observations = env.reset()

for _ in range(100):
    agent_actions = {
        agent_id: agents[agent_id].act(agent_obs)
        for agent_id, agent_obs in observations.items()
    }
    observations, _, _, _ = env.step(agent_actions)

env.close()

We hope the above addresses your question and thus this issue is being closed. Please feel free to reopen this issue if your problem persists or open a new issue for other questions.


Fix eye rotation on suicide command

It attaches you to the map always but now we'll do grid / map.
:cl:

fix: Your eye rotation will now already be adjusted upon ghosting.

Can you fix rotation after you ghosting, please? IDK if you detached from grid after death


Compile error related to gloo (class gloo::xxx::xxx has no member named xxx)

I'm getting this compile error:
[ 13%] Building CXX object caffe2/CMakeFiles/Caffe2_CPU.dir/core/blob_serialization.cc.o
In file included from /storage/linux/abs/caffe2-git/src/caffe2-git/caffe2/contrib/gloo/common_world_ops.cc:1:0:
/storage/linux/abs/caffe2-git/src/caffe2-git/caffe2/contrib/gloo/common_world_ops.h: In member function ‘bool caffe2::gloo::CreateCommonWorld<Context>::RunOnDevice()’:
/storage/linux/abs/caffe2-git/src/caffe2-git/caffe2/contrib/gloo/common_world_ops.h:72:26: error: ‘class gloo::transport::Device’ has no member named ‘getTimeout’
                 device_->getTimeout()) {
                          ^
/storage/linux/abs/caffe2-git/src/caffe2-git/caffe2/contrib/gloo/common_world_ops.h: In instantiation of ‘bool caffe2::gloo::CreateCommonWorld<Context>::RunOnDevice() [with Context = caffe2::CPUContext]’:
/storage/linux/abs/caffe2-git/src/caffe2-git/caffe2/contrib/gloo/common_world_ops.cc:33:1:   required from here
/storage/linux/abs/caffe2-git/src/caffe2-git/caffe2/contrib/gloo/common_world_ops.h:71:13: error: ‘class gloo::Context’ has no member named ‘getDevice’
             backingCommonWorld->getDevice()->getTimeout() <
             ^
make[2]: *** [caffe2/CMakeFiles/Caffe2_CPU.dir/build.make:159: caffe2/CMakeFiles/Caffe2_CPU.dir/contrib/gloo/common_world_ops.cc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:561: caffe2/CMakeFiles/Caffe2_CPU.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

A git bissect shows that it's being caused by commit e4be658fd4591cd38fbefb2abd3acaa59f4823c3, but maybe this is wrong because other different errors appeared during the bisect compile tests. Maybe this is related to gloo being updated to git master by commit 3a31edb1bfcae07dff2194f044382a197584fe95?
This happens on both gpu-enabled and cpu-only builds.
System information:
OS: Arch Linux x86_64
caffe2: git master (currently at 0.8.0.r148.g9f46ce87)
compiler: gcc 5.4.0

I met the same problem.

Hi @Yangqing Can you help fixing this? Thx a lot!

Recent commits have fixed this error for me. The most recent git master source code at the time of this writing (0.8.1.r19.gf0ea8046) is now building fine.
@StatML
I will be closing this issue because I have opened it and it's now solved for me. If you still have such an issue like this, please open a new topic.
You did not mentioned your operating system, but if you are on Arch Linux I have updated the Caffe2 packages on the AUR and all of them are building fine now.

@dbermond Thanks! This issue is still not solved for me. My platform is Ubuntu 16.04.4, G++5.4.0, Python3.5.2. I will open a new topic.


Add support for attribute blocks

As the title suggests, this pull adds support for attribute blocks.
The implementation allow both for plain attribute blocks, but also support nested blocks as showcased in the added test.

ta :+1:


Add docker as an runnable environment

I've migrated all my servers (and roles) on my homelab to docker and thus been porting all servers to be able to run on docker.
This PR adds docker as an additional environment.
Using docker-compose only requires one copy action and changes to the docker-compose.override.yml file to have a local running instance

Adding WIP tag as i've discovered some small issues which i'm adressing

That's pretty nice, I'm not a docker guy myself, but let me know once you've worked out all the kinks and I'll take a look at merging this in.

Yes, i've got most kinks worked out locally and in my swarm. The biggest challenge was Sphins Search, mostlikely because of lack of experience.
At this moment i'm running manual tests on the docker stack, missing extensions, cronjobs not getting picked up, small stuff like that

@Sn0wCrack
Done

[x] Import SQL file on first run using docker-compose
[x] Implement Linux instructions to dockerfile
[x] Crontab in app and sphinx
[x] Create config.json based on environment variables

Notes:
I half arsed the setup for cron in the sphinx container which will run the install with every start, which is no biggy. I didn't want to add extra dockerfiles for an external dependency.

Sweet, looks good to me.
Should be fine with the Sphinx setup there honestly so long as it's not touching the data directories you should be right.
Just a couple things:

Would you be able to just squash your commits to keep things a little nicer looking.

With the two small code changes, could you just split those out into a different PR? Once again, like to just keep things a bit better manage (which is rich coming from me with my commit history). I'll put comments on the lines I mean in your PR.

commits squashed. Opening new PR with code changes.

All merged in now 👍


Endogenise choice for low-T heat

Adapt build_industry_sector_ratios.py
Cement, pulp production, paper production, food, transport equipment, machinery, textiles, wood/wood products, other industrial sectors

Solved in commit # 13e29a4b2e064afa4a7a5fcd4cca319cb11a7573.
Still need to adapt nomenclature in the industry scripts from biomass to process steam

Check emissions handling and adapt if solid biomass is handled as zero emission

Add biomass emissions to totals in build_energy_sector_ratios.py!

Biomass emissions are already included!


Npm package updates

Fix missing json config file
Update descriptions
Closes #50

Coverage increased (+0.03%) to 28.143% when pulling de58ea62fc202c319690c64695c006723a67aa63 on dpetev/npm into d4b5bcd80b8191cb67c7bb1cf1af26214ced7e4c on master.


Need new DOI for transition-scenarios

This issue can be closed when :

[x] a new DOI has been created for the software associated with the paper.
[ ] A PR is merged such that the new DOI replaces the old DOI in the bibliography

Closed with #27


Make NetworkInterface public

In other case it is impossible to implement Stats() method from
interface outside libcontainer.

LGTM

LGTM


VMwareFusion Driver cannot recover from pause/suspend state

docker-machine -version: docker-machine version 0.5.0-rc4 (952539d)
Steps to reproduce:

Create a VM machine: docker-machine create -d vmwarefusion vmfuse
Check the VM is working properly: docker-machine env vmfuse
Suspend/Pause the machine from the VMWareFusion App:

Try to start/restart the machine from terminal: docker-machine start vmfuse
Notice the machine will not be started even though docker-machine ls reports it as such.

@frapposelli

@FrenchBen There's no way with vmrun to find out that a vm is suspended. And when a suspended vm is asked to start, it falls into a strange state. I don't think we can do anything. Any ideas?

There is no support for suspend/resume in docker-machine, hence no support for it, theoretically, a VM in a suspended state can be powered on without issues, but it's not tested as part of the driver.

The issue is that a VM in a suspended state will not come back to life via the start/stop issued by docker-machine. Does the driver not allow for this to happen?

Hi @FrenchBen, it is not supported by the driver.
The driver uses vmrun and vmrun has couple of flaws:

It cannot detect that a vm is paused/suspended, it is assumed to have two states: stopped, everything else.
Calling vmrun start on a paused/suspended machine somehow tries to take it out of paused state but fails at really starting it.

thanks for the breakdown of what's going on - Is there a plan to get the driver/vmrun updated in order to resurrect a VM from suspended mode?


add repo package flink2

add flink 1.3.0-1.0 to packages

@luoomu Could you please put a PR with an updated example here: https://github.com/dcos/examples ?

@OhRobin No

Updated with https://github.com/mesosphere/universe/pull/1252


input-date: accessibility changes

Opening as draft in case there are bigger changes to how we want to do this.
To do:

[ ] add offscreen-description to input-text readme

Problem:
Support for having both aria-describedby and title and reading both was mixed, so there wasn't a good way to have the empty-text read.
Solution:
[see user story for more info] Use d2l-tooltip for what is currently in title and put the empty-text as an aria-describedby on the input in input-text.
Notes:

The tooltip has a 1 second delay on hover
If user opens then closes the dropdown, the tooltip should not reappear until they remove focus and return

I'm a little concerned that this having tooltips in a bunch of different levels within the nested form element tree is going to become impossible to manage safely. An example of this is that in d2l-input-range the info tooltip will open overtop of the validation tooltip because the info tooltip only gets suppressed by errors in validating itself or its children, not parents. Thoughts?

Ah right, so it should probably be checking for this.invalid instead of the validation error but I do see your point about it being potentially unsustainable. Should input-text be managing its own tooltips instead?

Ah right, so it should probably be checking for this.invalid instead of the validation error but I do see your point about it being potentially unsustainable. Should input-text be managing its own tooltips instead?

I think this.invalid will fix this case but if we were to ever add info tooltips to other date input components suddenly those would start overlapping as well. I don't know if there really is a good way to handle it since we're trying to build independent components that need to peer into each others internals to prevent tooltip overlap.


no  *.ts files not found warning in xzing/library

hello awesome hook
but i have problems, this is my package.json
{
"name": "pwa-app-lectorqr2",
"version": "0.1.0",
"private": true,
"dependencies": {
"@testing-library/jest-dom": "^5.16.5",
"@testing-library/react": "^13.4.0",
"@testing-library/user-event": "^13.5.0",
"@types/jest": "^27.5.2",
"@types/node": "^17.0.45",
"@types/react": "^18.0.26",
"@types/react-dom": "^18.0.9",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-scripts": "5.0.1",
"react-zxing": "^1.0.5",
"typescript": "^4.9.3",
"web-vitals": "^2.1.4",
"workbox-background-sync": "^6.5.4",
"workbox-broadcast-update": "^6.5.4",
"workbox-cacheable-response": "^6.5.4",
"workbox-core": "^6.5.4",
"workbox-expiration": "^6.5.4",
"workbox-google-analytics": "^6.5.4",
"workbox-navigation-preload": "^6.5.4",
"workbox-precaching": "^6.5.4",
"workbox-range-requests": "^6.5.4",
"workbox-routing": "^6.5.4",
"workbox-strategies": "^6.5.4",
"workbox-streams": "^6.5.4",
"zxing-typescript": "^0.1.2"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
many warnings appear, that it does not find the files in xzing *.ts
Still open the app.
thank you very much for your help

It looks like you are using the wrong peer dependency. Instead of using zxing-typescript, you should use @zxing/library. This will ensure that you have the correct dependencies and that everything functions properly. Please update your dependencies and try again.

Strangely enough, I also have the same warnings without installing any peer dependencies (neither zxing-typescript nor @zxing/library). I have only followed installing react-zxing like in the README

@TheTimeWalker I'm sorry, neither zxing-typescript nor @zxing/library are necessary peer dependencies like you say. I'm not really sure what could be causing this. Are you using windows? Have you got any clue? Thanks!

Yes, that's how I understood as well. I meant that I have only followed the single installation step npm i react-zxing and am receiving these errors. e.g. I'm running the default react-scripts start command:
WARNING in<EMAIL_ADDRESS>Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from<EMAIL_ADDRESS>file: Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>
My hunch is that it's this issue in the zxing library: https://github.com/zxing-js/library/issues/512
My tech specs:
OS: Arch Linux
TypeScript: 4.9.4
ReactJS: 18.2.0

I am getting the same warnings.

Looks like @zxing/library was updated to 19.2 to fix this problem. https://github.com/zxing-js/library/pull/546

Looks like @zxing/library was updated to 19.2 to fix this problem. zxing-js/library#546

Thanks! I've updated this dependency in 1.1.1. Could anyone please confirm that this issue is resolved with 1.1.1?

Looks like @zxing/library was updated to 19.2 to fix this problem. zxing-js/library#546

Thanks! I've updated this dependency in 1.1.1. Could anyone please confirm that this issue is resolved with 1.1.1?

I've tested it and this fixes it for me. Thank you!

Cool! I'll close this - please reopen if this issue persists!


An actor/token with Blindsight when the scene goes dark (night time)

Hello,
I could well be doing something wrong but a character in my game has blindsight 10 feet, however when the sun goes down on a scene, the 10 foot radius goes dark too. With Blindsight the scene going darker shouldn't make any difference, right?
In Magical Darkness it dims a little but due to it dimming a little when the scene is dark and they are in Magical Darkness, they cannot see much. :-(
V12.331
DND5e v 4.0.4
Vision 5e v 2.5.3

Looks like I might have accidentally changed the brightness of the Blindsight vision mode to -1 when it should be 1. I'll investigate further in the coming days if I don't forget.

https://github.com/dev7355608/vision-5e/releases/tag/v2.5.4


Soil contig tax

Added a python notebook to look out how the taxonomic distribution of contigs differ by soil layer (mineral vs. organic) in Colorado. This uses NMDC metadata to access and analyze metagenome data.

@brynnz22  Overall, an impressive feat to pull together all these API calls and merges in a consumable way.  Wow!  The notebook rendered fine without running the calls or accessing the pkl files, so I think we are good on that front; though we should add to the readme for the google colab that rerunning this in an interactive environment is not recommended and will likely break for these reasons.
Do you use the 'taxonomic_dist_by_soil_layer/python/mongodb_query.txt.js' file?  Maybe I'm missing it, but if not please remove from the branch.
In first Markdown cell, the word 'object' is misspelled.
Once we have the tsv urls, I think it would be useful to show a single sample's results before concatenating them all together.  That dataframe should have soil horizion, biosample id, geo_loc, taxa, and count.
Biologically, its not correct to add together counts between samples, so I think we need to revisit the last couple code chunks to make a bit more sense.  I have a couple ideas for this that shouldn't be too painful (hopefully!).

@kheal addressing your points above, I:

edited the readme to explain that running in the interactive environment is not recommended

We should the mongodb_query.txt.js file because this helped inform the API request traversals. Also, this is helpful to inform the endpoint being created.

I fixed the mispelling of object

I printed a snippet of a TSV to show what it looks like

Finally, we discussed the last point and that the way I did it was correct.

Thanks for the feedback :)

In md cell 35 "Example of what the TSV contig taxa file looks like"; we decided the third column is not percent (otherwise it would add up to > 100%), so that text should be edited.  How about something along the lines of "The first column is the identifier of a single contig, the second is the taxonomic placement of the contig, the third is a simple count".  In py cell 36; I would rename the percent column to count.  Also, we will need to calculate relative abundance per sample per taxa, and then calculate average relative abundance per horizon, as we discussed.

Okay! I think we are good! Thanks again for all of your help!!

@kheal I believe I got the nbviewer to work now: https://nbviewer.org/github/microbiomedata/notebook_hackathons/blob/soil-contig-tax/taxonomic_dist_by_soil_layer/python/taxonomic_dist_soil_layer.ipynb .

closes #8!


[vcpkg_configure_make][vcpkg_build_make] Use prefix without DESTDIR

Because vcpkg requires packages to be relocatable, there's no functional difference between DESTDIR and --prefix. By assigning --prefix to packages\, we can simplify the build process and avoid doubling path lengths.

cc @Neumann-A for review this PR.

/azp run

/azp run

/azp run

/azp run

@cenit As part of this, I've run into the non-relocatability of openmpi -- I believe I've built a solution using wrapper scripts, but if you have time I'd appreciate a second opinion.
https://github.com/microsoft/vcpkg/pull/16313/files#diff-f81251de4b55e635fe558a125065447ca8c81e9f5e916f6ff6341a3d9996a082

@cenit As part of this, I've run into the non-relocatability of openmpi -- I believe I've built a solution using wrapper scripts, but if you have time I'd appreciate a second opinion.
https://github.com/microsoft/vcpkg/pull/16313/files#diff-f81251de4b55e635fe558a125065447ca8c81e9f5e916f6ff6341a3d9996a082

thanks for asking. Tomorrow i will look into it :)

This PR has been inactive for a long time, please reopen it if there is any progress.


Decisions' support

A decision and, potentially, various actions (such as arrest, enslaving, freeing a slave, attack against another faction, trade with another faction etc.) can be supported or opposed by pawns.
Pawn's support level is affected by, among other things:

Action itself (some are more popular than the others)

Pawn's position (e.g. the incumbent leader will like expansion of his/her power and will hate impeachment)

Pawn's relationship with the target of the action and their faction

Pawn's thoughts and needs (e.g. a hungry pawn may support buying food even from a faction they dislike)

Pawn's political views (see #22 ), traits and backstories

Every reason has a numerical value, either positive (pro) or negative (contra). The values can be static or can change with underlying stats. If the sum is positive, the action will be supported.
Leader's support or opposition affects the governance cost of the decision (reduces or increases it, respectively) and availability of an action.
Citizen's support or opposition may affect their mood and opinion of the leader.

Implemented in v1.2 for some decisions (succession types, impeachment, some reforms).

Additionally, Leader's support for the action may be a hard or soft requirement. For hard requirements, the action may not be taken without his/her support. For soft requirements, there will be a Governance hit if it's taken over his/her opposition. This will create incentives for the player to modify their play style in accordance with the current Leader and therefore will make the Leader's personality and interests more important.

Possible actions to require support from the leader and/or citizens:

[ ] Decisions
[ ] Arrest
[ ] Execution
[ ] Release of a prisoner
[ ] Banishment
[ ] Buying and selling slaves
[ ] Attacking a faction
[ ] Trade with a faction
[ ] Butchering a human, cannibalism etc.


Can't load any achievements RPCS3

Describe the bug
I'm having trouble integrating RPCS3 with SuccessStory. I've checked the RPCS3 box and filled in the path to my folder, but it doesn't show any trophies. The logs indicate that the plugin loads but doesn't find any trophies.
To Reproduce
Steps to reproduce the behavior:

Open Playnite.
Go to SuccessStory settings.
Check the RPCS3 integration box.
Fill in the path to the RPCS3 directory: C:\Games\rpcs3\dev_hdd0\home\00000001
Try to view trophies for a game (e.g., LittleBigPlanet or Deadpool).

Expected behavior
Trophies and achievements for RPCS3 games should be displayed in Playnite through the SuccessStory extension.
Screenshots
N/A
Extensions log
extensions.log

Not loading RPCS3 achievements again #347


Firmware cannot be upgrade via web interface any longer

On my WNDR3700v2 (ar71xx, 16MB flash) I am no longer able to update the firmware using the LUCI web interface. I only get a "Bad gateway" response, whereas before I would get to the overview page showing me the size & hash and asking me to proceed. As far as I can tell a recent change (something after Oct 13) must have broken this, so it should be not too much of a hassle to find out what the issue is.

Every now and then I'm also getting the following trace rather than a "Bad gateway" response:
not enough memory
stack traceback:
/usr/lib/lua/luci/http/protocol.lua:123: in function '__appendval'
/usr/lib/lua/luci/http/protocol.lua:320: in function 'store'
/usr/lib/lua/luci/http/protocol.lua:397: in function 'snk'
/usr/lib/lua/luci/ltn12.lua:300: in function 'step'
/usr/lib/lua/luci/ltn12.lua:309: in function </usr/lib/lua/luci/ltn12.lua:305>
(tail call): ?
(tail call): ?
/usr/lib/lua/luci/http.lua:95: in function '_parse_input'
/usr/lib/lua/luci/http.lua:39: in function </usr/lib/lua/luci/http.lua:37>
(tail call): ?
/usr/lib/lua/luci/dispatcher.lua:183: in function 'require_post_security'
/usr/lib/lua/luci/dispatcher.lua:410: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:169: in function </usr/lib/lua/luci/dispatcher.lua:168>

The not enough memory message is worrysome, since I should have something around 40 MB of free RAM and ~12 MB of free flash.

Bisecting through the recent changes, I've found the culprit: b5826f1ffb19288b8bfdc63f4b77700cfabe1181
The commit message clearly states that you've changed things around and wanted to make it resistent against CSRF. Unfortunately I'm not too familiar with Lua, so I will have to take a deeper look.

I'm working on it, needs a further bit of restructuring.

I close the issue as to my kwnoledge the problem has been solved with the commit 94ab57f48c9a8704a0a7da87bfa6ced9e73ca9be where Jow referenced this issue. I have since then updated my own WNDR3700 several times in Luci.
But if you currently have the problematic Luci version, you need to either

download a new firmware to the router (e.g. with wget) and use "sysupgrade" to flash it, or
download the fix commit to the router as a patch and use "patch" to apply it to Luci.
https://github.com/openwrt/luci/commit/94ab57f48c9a8704a0a7da87bfa6ced9e73ca9be.patch


[Feature Request]: Add laravel-echo-server package

Since realtime applications become more popular the websocket protocol is getting more important.
Laravel has a great implementation with broadcasting and the package laravel-echo-server  would it make possible to use websockets with socket.io at the client. So you are independent from external services like pusher.
I found a docker image for that https://github.com/tlaverdure/laravel-echo-server and wanted to ask if it's possible to integrate this into the laradock. I am new to docker so I am not able yet to build a perfect image and pull it by myself. But I think someone with the knowledge can do it in under an hour :)

closed by #983


Show failed tests at the top

Currently, we order the tests alphabetically in the HTML report. Would be nice to see the failed errors at the top (ideally with a copyable details).

do you mean inside the html report? I think it is very reasonable.
What details do you want to be copied? Last assertion message?

Yup - updated the original comment. And yes, the assertion message + some details that would help someone trying to quickly troubleshoot

Not sure I follow the details part. Workflow I had in mine was around sharing failures was to share a link. As you navigate around issues and tabs link is updated to point to that place.
All that information is useful to investigate, but copying it in a clipboard may not make sense.
I would rather copy report url (will only work when we have Jenkins that hosts them, or S3).

A sharable link works!

should be closed by #77


No output example in documentation

Type of issue
Missing information
Feedback
Articles like this shows all inputs but does not provide any example output, making it hard for developers to understand which information is provided by each command.
Page URL
https://learn.microsoft.com/en-us/cli/azure/storage/queue?view=azure-cli-latest
Content source URL
https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/latest/docs-ref-autogen/storage/queue.yml
Author
@dbradish-microsoft
Document Id
95cdc341-ac11-4709-ee41-0323e07e8750

This article provides example output, which is useful to understand the capabilities of each endpoint.
Notwithstanding, it would be better if output be documented the same way the paremeters (inputs), with an explanation of each attribute

@ltouro
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@ltouro, I understand your viewpoint, and agree that output code blocks would be extrememly helpful. Right now, only some of our conceptual docs have output, like you see in Populate variables for use in scripts.
I've fowarded your feedback to the project manager for the Azure CLI, and although you might not see an immediate result, your suggestion has impact and will be further considered. Please continue to send us suggestions that will help you to use the Azure CLI successfully.


Add support for PINK token

Name of the asset: PINK
Origin blockchain of the asset: Polkadot Asset Hub
Is it available on other blockchains? Moonbeam
Metadata of the asset (symbol, decimals, smart contract address, on-chain metadata like assetId,...)
PINK on Polkadot Asset Hub: https://assethub-polkadot.subscan.io/assets/23?tab=holders
PINK on Moonbeam: https://forum.moonbeam.network/t/referendum-36-proposal-to-register-asset-xcpink/1435
Logo of the token: https://www.figma.com/file/PxPvXw5woBernBu3BtwxkX/SubWallet-Project-Logo?type=design&node-id=3025-23&mode=design&t=z1pnWV2LIGm9tiaR-4
Is your asset transferable? yes (available at launch)

Resolve in https://github.com/Koniverse/SubWallet-Extension/issues/2570


Add support for CIP-57: Plutus Contract Blueprint

Introduction
Hey there! My name is Kylix and I'm a software engineer at Liqwid Labs, the team behind Liqwid Finance and Agora.
Summary
This issue intends to start discussion on supporting a CIP-57 ledger data enrichment layer directly in Cardano DB Sync.
Implementation examples
Some examples of useful solutions that could be built into Cardano DB Sync using CIP-57 I can think of include:

Decoding output datum directly in DB Sync, moving a considerable amount of the computational work, that is currently being ran on middleware services and applications, to the SQL server while also settling on a single source-of-truth for this "enriched"/higher-level data.
Adding metadata fields to Plutus script describing tables, like for example name and description, allowing users of Cardano DB Sync to join on relations based on this metadata instead of forcing those users to join on those same relations based on script hashes and PostgreSQL auto-generated IDs.

There's a very good chance I haven't covered all use-cases of this integration in this items placed above. I tried to stick the scope of the examples to some of our known use cases.
Context
At Liqwid Labs, we aim to expose a considerable amount of metrics and analytics about Liqwid Finance and its' deployment of Agora that require computation based on historical ledger data (namely based on output datum fields). Since our first iteration (Liqwid V1: https://v1.liqwid.finance/) we've struggled with building systems that reliably provide this data without requiring a large amount of service deployments and maintenance. With this issue we aim to solve this problem by moving the workload to a service we already work with on a day-to-day (Cardano DB Sync being the service) while also making the solution generic enough as to where it can benefit others (namely dApps and DeFi protocols building on top of Cardano DB Sync in the Cardano ecosystem).
Conclusion
First off all, I want to thank you, the reader, for reading this issue. I'm eager to hear back from developers maintaining and introducing features/improvements to Cardano DB Sync and from community members / entities who could be impacted by the implementation of a solution to the problem stated above.

I apologize to the maintainers as I did not intend to label this issue as a bug.


unsupport Diablo IV Twitch Drop

Release v15 Version NOT support Diablo IV/WarThunder/World of Tank Twitch Drop.
It can provide a list of Twitch live that ENABLED drop, but displays X on gift icon column.
Development build version resolved the problem, but errors are frequently reported in the log.

The release version does not work anymore, yes. The development version is waiting for #234 to complete before I can declare the next stable version. For now, you can use the development one.
What errors are you experiencing? I'll need the tracebacks to be able to help you in any way.

Thanks for your reply!
I have closed the DropMiner before, the log window has been emptied.
When I see the error code again, I will paste it in this post.
The software is very easy to use, thank you for keep maintenance!

@DevilXD Error in the log window:
21:32:59: Fatal error encountered: 21:32:59:  21:33:00: Traceback (most recent call last): 21:33:00:   File "main.py", line 174, in <module> 21:33:00:   File "asyncio\base_events.py", line 647, in run_until_complete 21:33:00:   File "twitch.py", line 768, in run 21:33:00:   File "twitch.py", line 787, in _run 21:33:00:   File "twitch.py", line 1458, in get_auth 21:33:00:   File "twitch.py", line 516, in validate 21:33:00:   File "twitch.py", line 544, in _validate 21:33:00:   File "twitch.py", line 299, in _oauth_login 21:33:00:   File "contextlib.py", line 181, in __aenter__ 21:33:00:   File "twitch.py", line 1483, in request 21:33:00:   File "gui.py", line 2054, in coro_unless_closed 21:33:00:   File "aiohttp\client.py", line 1125, in send 21:33:00:   File "aiohttp\client.py", line 536, in _request 21:33:00:   File "aiohttp\connector.py", line 540, in connect 21:33:00:   File "aiohttp\connector.py", line 901, in _create_connection 21:33:00:   File "aiohttp\connector.py", line 1175, in _create_direct_connection 21:33:00:   File "aiohttp\connector.py", line 980, in _wrap_create_connection 21:33:00:   File "asyncio\base_events.py", line 1050, in create_connection 21:33:00:   File "asyncio\base_events.py", line 961, in _connect_sock 21:33:00:   File "asyncio\proactor_events.py", line 703, in sock_connect 21:33:00: RuntimeError: await wasn't used with future 21:33:00:  21:33:00: Exiting... 21:33:00:  21:33:00: Application Terminated. 21:33:00: Close the window to exit the application.

@DevilXD Error code in the log window:
`21:32:59: Fatal error encountered:
21:32:59:
21:33:00: Traceback (most recent call last):
21:33:00:   File "main.py", line 174, in
21:33:00:   File "asyncio\base_events.py", line 647, in run_until_complete
21:33:00:   File "twitch.py", line 768, in run
21:33:00:   File "twitch.py", line 787, in _run
21:33:00:   File "twitch.py", line 1458, in get_auth
21:33:00:   File "twitch.py", line 516, in validate
21:33:00:   File "twitch.py", line 544, in _validate
21:33:00:   File "twitch.py", line 299, in _oauth_login
21:33:00:   File "contextlib.py", line 181, in aenter
21:33:00:   File "twitch.py", line 1483, in request
21:33:00:   File "gui.py", line 2054, in coro_unless_closed
21:33:00:   File "aiohttp\client.py", line 1125, in send
21:33:00:   File "aiohttp\client.py", line 536, in _request
21:33:00:   File "aiohttp\connector.py", line 540, in connect
21:33:00:   File "aiohttp\connector.py", line 901, in _create_connection
21:33:00:   File "aiohttp\connector.py", line 1175, in _create_direct_connection
21:33:00:   File "aiohttp\connector.py", line 980, in _wrap_create_connection
21:33:00:   File "asyncio\base_events.py", line 1050, in create_connection
21:33:00:   File "asyncio\base_events.py", line 961, in _connect_sock
21:33:00:   File "asyncio\proactor_events.py", line 703, in sock_connect
21:33:00: RuntimeError: await wasn't used with future
21:33:00:
21:33:00: Exiting...
21:33:00:
21:33:00: Application Terminated.
21:33:00: Close the window to exit the application.`

That error is a duplicate of #80. Please refer to that issue instead. Closing this one.


Closing File Explorer Closes Desktop on Windows

Using this library to close the 'File Explorer' app causes the Windows desktop to disappear.

Yes, but you can also start it like:
from AppOpener import open
open("explorer", match_closest=True)

Yes that is true, but that still does not resolve the issue. If at any point the close() method is used on file explorer, the Windows desktop disappears. The ability to close file explorer should either be removed or fixed. Opening it right after closing it does not resolve the issue.

Okay, next version fixes this!! 🥰

AppOpener v1.7 just released!! ✌
Install AppOpener v1.7:
pip install AppOpener==1.7

Close File Explorer without closing the windows
from AppOpener import close
close("file explorer")

Lots of love,
athrv.


Changes to make padl python 3.7 compatible

Description

Some changes needed to make PADL compatible 3.7

Main problems were

missing ast.get_source_segment
missing ast.AST.end_lineno and ast.AST.end_col_offset

Fixed by using the asttokens library if needed in new module dumptools/ast_utils.py.

[ ] can we live with the slowness? (tests ~3 times slower, only affects creating and loading transforms, not execution)

[ ]  can we live with the slowness? (tests ~3 times slower, only affects creating and loading transforms, not execution)

Is this slowness only occur when python 3.7 is used? If so, I'd say better to have the support than not even if it is slower in building and loading.

@wuhu I also ran through one of our notebooks and I did not notice the slowness when creating the transforms.

I've continued to play around with padl in a notebook and I am beginning to think the slowness is linked to running in the pytest environment. When running test_pd_splits_rollout using pytest -k test_pd_splits_rollout --durations=0 the test takes about 9 sec to run vs 1 sec normally. However, if I copy this test over into a jupyter notebook running python 3.7 and run it there it takes less than 1 sec.

Is this slowness only occur when python 3.7 is used? If so, I'd say better to have the support than not even if it is slower in building and loading.

Yes, the way I refactored it everything is basically the same as before for python >= 3.8.

I've continued to play around with padl in a notebook and I am beginning to think the slowness is linked to running in the pytest environment. When running test_pd_splits_rollout using pytest -k test_pd_splits_rollout --durations=0 the test takes about 9 sec to run vs 1 sec normally. However, if I copy this test over into a jupyter notebook running python 3.7 and run it there it takes less than 1 sec.

My understanding is that the larger the files the transforms come from, the slower this is. Seems like for finding out where statements end asttokens goes through the whole file and counts the characters, basically. This makes test_transforms slow as the module is rather long.
So it could become a problem for larger codebases (like tenen), but notebooks I should be fine. Also the critical code is isolated in dumptools/ast_utils.py thus if we find something more efficient we can easily replace.

So it could become a problem for larger codebases (like tenen), but notebooks I should be fine. Also the critical code is isolated in dumptools/ast_utils.py thus if we find something more efficient we can easily replace.

I see, that makes sense. I think it's fine to merge then. We could consider adding a warning to the docs about this when using 3.7.

I see, that makes sense. I think it's fine to merge then. We could consider adding a warning to the docs about this when using 3.7.

Agree.
@blythed, what do you think?
Summary is:

we can make it work for 3.7
this ads an extra dependency for 3.7 only ("asttokens")
it's relatively slow if transforms come from large files (also, only 3.7 no difference for other versions)
in notebooks basically no difference

Should we use this or not use this or look for a more efficient fix?


Support multi update's argument

We should support update's multi argument and improve our tests.

I would like to work on this issue

Picket up by @fcoury at #790


Provide instructions for how to run and test error scenarios

Only applicable for provider Evolution (SID-generation)?
No PAM-errors for timeout and connection lost-cases?


Redo adapter inheritance

This PR is on top of #190.
This PR slightly refactors the adapter inheritance for Slack-like adapters.
It adds in an intermediary SlackLikeAdapter for the Slack-like providers. This should make it easier to use DefaultAdapter methods in subclasses, like with what is done in SparkAdapter.formatData and SlackLikeAdapter.normalizeCommand.
This makes things a bit easier:
-ThisAdapter.super_.prototype.customMethod.call(...)
+DefaultAdapter.customMethod(...)

I also removed the normalizeAddressee from the MS Teams adapter, since it was an override of the same function from DefaultAdapter (and the MS Teams adapter inherits from DefaultAdapter). The two functions were identical, however, so it makes no sense to override that function. And since the two functions were identical, I didn't need to change the tests at all for this fix.
~Once #190 is merged, I will either rebase and merge this with GitHub, or I will manually rebase this branch on that one, force push, and merge it.~ Done.

I fixed a few things in the changelog, and added PR references to the most recent changes, including #190.


is there an change planed on Custom Messages functionality in near feature?

Hi in Wiki you mentioned that Custom Messages functionality will be replaced in version 0.2.0.
Is it still correct or something changed in original planing?

Hi, @mmishalov, We stick to the plan.
The custom messages will use Cha message template engine by @keke

@keke any update on this?

Conversation moved to github.hpe we can close this issue.


change bib2json method, fix }} bug in Issue #52

I have simplified the bib to json function using tracking of opened and closed braces.  Have tested on my bib file consisting of 288 entries. It works fine.
Also, this fixed the bug I mentioned in the Issue #52 , which happened in line:
elif line.strip().endswith("}}"):
Since some journal may ends with }} such as {{PMLR}} in my example.

Thank you!


dependency on torchvision, but missing when installed

I reproduced this with:
mamba create -n vollseg python=3.9
mamba activate vollseg
pip install tensorflow
pip install vollseg-napari

Attempting to open a sample image or the vollseg plugin resulted in RuntimeError: Failed to import command at __command location__: No module named 'torchvision'

Yes in the newer version of vollseg there are dependencies on pytorch that I have not included in the setup file, in your current environment if you do
pip install torch pip install torchvision pip install torchaudio
Your code should start working, I will update the setup file in the meantime for the next release, thanks for pointing this out.


Timezone

Thanks for your module.
What about adding timezone? Inspired by https://github.com/kelektiv/node-cron.
Timezone is important because you can execute jobs on machines with a timezone different with respect to the job.
RFC for cron API: cron(schedule, job, timezone):
// Run Job at 9a.m. NY time
cron('0 0 9 * * *', () => {
    checkStock();
}, "America/New_York"});

export const cron = (schedule: string = '', job: JobType, timezone: string) => {
// I suppose we need to change `schedules` Map, adding timezone info
...

Then in executeJobs the validation is done for the following date:
 schedules.forEach((jobs, schedule, timezone) => {
   const date = new Date().toLocaleString("en-US", {timeZone: timezone});
...

What do you think?
I noticed toLocaleString doesn't work. See https://github.com/denoland/deno/issues/1636
Compare the following snippet in deno and in node:
var asiaTime = new Date().toLocaleString("en-US", {timeZone: "Asia/Shanghai"});
console.log('Asia time: '+ (new Date(asiaTime)).toISOString());

@albertosantini Thanks for creating this Issue, I will expose API to pass time zone. As you also referred Deno initially doesn't support TimeZone to  toLocaleString but I have noticed the created a bug ticket and they are working on it in the V8 level. So I am assuming the issue will be fixed soon. Thanks

I have created a separate branch where I implemented TimeZone. Since Deno does not has support yet for the toLocalString() this feature not working as expected in Deno but works well with Nodejs. But Deno is working on it. Hopefully, it will be fixed soon in their upcoming update.

Hey. I hope you are fine.
Since Deno 1.8.0 ICU support has landed and now the test snippet above works correctly.
See https://github.com/denoland/deno/issues/1968
Great!


Links for code style and review

@daxian-dbw @adityapatwardhan I collected from PR discussions useful links for possible future additions in our guidelines. Feel free to close after read.

Sorts class elements according to StyleCop guidance https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1201.md
Sorts within the same elements by access type according to StyleCop guidance https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1202.md
https://smartbear.com/learn/code-review/best-practices-for-peer-code-review/
https://www.codefactor.io

If someone could figure out how to get StyleCop.Analyzers working in our project, that would be great. I gave it a full days worth of effort and came back empty handed. It is supposed to be as simple as adding the package reference, but I ran into weird dependency conflicts. We would need to ignore some of the rules unless we are willing to change some of our guidelines. (for example, separating private fields backing properties from the properties). And maybe it doesn't need to be in every assembly. Or maybe it can be added through some empty project trickery and run ad hoc instead of every build.

I agree with @markekraus to rather use the stylecop linter because then you get errors in Visual Studio (and you can even do Ctrl+'.' to auto-fix it). I have used that already in a .Net Core solution but remember that there were some gotchas and limitations (e.g. one could only have one global stylecop.json instead). I can take a stab on it if you want to. I don't know if it integrates well with VSCode or if it only works with Visual Studio because of the way it hooks into .Net Core MSBUILD under the hood. Maybe it requires PR 5209, because at the moment, compilation is disabled for all *.cs files in the csproj files.

@bergmeister Thanks!
If we can at least get it hooked into the Microsoft.PowerShell.Commands.Utility assembly as a start. That is where the heaviest amount of community contributions seem to go (by my impression only and no solid analytics 😏 ). And I have WIP for refactoring/organizing the web cmdlets (that's where much of this is stemming from).
For vscode, I believe the only current support is for compile time warnings, which is why I suggested possibly a pseudo-project... or maybe even a build configuration? I dunno.. I'm very new to this so whatever makes it work without impacting normal build processes until we can get the code to a state where we CAN flip it on for builds and serve as a fail detector.

StyleCops.Analyzers depends on Net452 😕

what about this https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/DotNetCli.md is that the same thing?

ASP.NET Core depends on Net452 too. 😕

@iSazonov I was able to get it to work with this https://carlos.mendible.com/2017/08/24/net-core-code-analysis-and-stylecop/ in a netcoreapp2.0 targeted app.
modifying it slightly to
dotnet add package Microsoft.CodeAnalysis.FxCopAnalyzers -v 2.3.0-beta1
dotnet add package StyleCop.Analyzers -v 1.1.0-beta004

after some toying around with it... I was able to get a beautiful sea of red StyleCop errors when running
Start-PSBuild -Clean -Configuration Style

https://github.com/PowerShell/PowerShell/compare/master...markekraus:StyleCop

@markekraus Great news! Do this work on Unix too?

I tried doing a very basic console project in Ubuntu and it failed with Feature 'IOperation' is disabled. errors, so I'm guessing it would only work on Windows. that means we could have it run only in the Windows CI and adjust Start-PSBuild to error when Style is used on linux.
Right now... it would be painful to have it run at all. For just the files in the Web Cmdlets folder there are over 1419 issues. But.. some of these may not really apply. For example
.\commands\utility\WebCmdlet\Common\BasicHtmlWebResponseObject.Common.cs(5,1): error SA1200: Using directive should appear within a namespace declaration

We don't enforce that in this project, In fact our guidance says to do the opposite.

Namespace imports should be specified at the top of the file, outside of namespace declarations.

I read through SA1200 and tend to agree with it. *shrugs

actually.. after some google-fu I was able to get StyleCop working on linux on a simple console project (needed <Features>IOperation</Features> added to a property group). But, I have no clue how to make this work with our project. Supplying Style as the configuration results int Linux configuration being chosen. I don't understand our build internals well enough to try this manually. One would think you could just run dotnet build in the assembly directory, but that doesn't work.

@markekraus : Haha, that brings back memories of a question that I asked about the roslyn analyzers half a year ago: https://github.com/dotnet/roslyn-analyzers/issues/1151#issuecomment-303509027
I am not sure if it is worthwhile just waiting until the whole build system has switched to MSBUILD per the PR that I mentioned above.

@markekraus Thanks for great research! If MSFT team approve this we'll continue to resolve minor problems.
I like the idea to turn on some StyleCops.Analyzers rules in the PowerShell repo.

We enabled StyleCop.Analyzers package in #13963 and I have submitted PRs for various rules.
There are a huge number of issues though, see https://www.codefactor.io/repository/github/powershell/powershell/issues, any help would be appreciated!


Notifications: room_one_to_one push rule does not consider m.direct flag

I'm talking about the following four global push rules (Underride Rules):

".m.rule.encrypted_room_one_to_one"
".m.rule.room_one_to_one"
".m.rule.message"
".m.rule.encrypted"

For example these rules are visible in the parameters of the Element-web client:

For the end user point of view one-to-one refers to the DM (Direct Messages). The problem is the server ignores the actual m.direct event defined in the user account data. The server only considers the room members count during the notifications handling.
Problem:

If you have a room (not DM) with just 2 people inside it behave from the notification side like a DM
If you have a DM with more than 2 people inside it behave from the notification side like a group chat

How it should work for the end user point of view
When sending out notifications the direct message flag should be respected:

When it is a "normal" room, use notification settings for group chats. No matter if 2, 3 or more people are in the room
when it is a "DM flagged" room, use notification settings for DM

for onlookers: this is because of the push rule conditions quite literally only checking member count (in a complicated and annoying way). From the looks of it, the push rules predated m.direct, which is why that might not have been considered. Encryption was bolted on after the fact and ended up duplicating the rules.

Agree with making this spec change - but we will need to ensure that the settings then reflect the fact that the setting is based on the m.direct flag and not on a user count, as otherwise the text of the settings will contradict reality.

Direct Messages
Encrypted Direct Messages
Messages in group chats
Encrypted messages in group chats

@gaelledel FYI

This has a big impact in bridged chats, because usually those have 3 users on the room (matrix user, bridge puppet and bridge bot). This "forces" the user to set the default notification for groups to "noisy" (in Element), and then change the notification preference individually for each group room to "silent".
I think that the new rule could be added after (lower priority) the current one-to-one rules, so that current clients would not break while still using those one-to-one rules.


⚠ Orpheus has degraded performance

In abb3419, Orpheus ($OPS) experienced degraded performance:

HTTP code: 504
Response time: 20586 ms

Resolved: Orpheus performance has improved in 91e8ed2.


additional failing heredoc tests

10 of these 11 new tests show tabs getting replaced with spaces when they shouldn't be.

Comments from IRC:
not a fan of those super-long lines. Even on github they don't fit on screen and require scrolling :/

well, the PR looks good to me. Just merge it (after getting the RT number? and maybe after making line lengths shorter? :))


Errors on startup without explanations, sth about fonts

I'm setting up a new instance. I'm using misi/mm:latest (docker images reports ID: 243eb2cd8f8b).
My directory layout:
$ find certs/
certs/
certs/.gitignore
certs/privkey.pem
certs/cert.pem
$ find configs/
configs/
configs/server
configs/server/config.js
configs/app
configs/app/config.js
$ cat run.sh
#/bin/bash
source .env
docker run \
        -v ${PWD}/configs/app:${BASEDIR}/${MM}/app/config \
        -v ${PWD}/configs/server:${BASEDIR}/${MM}/server/config \
        -v ${PWD}/certs:${BASEDIR}/${MM}/server/certs \
        -e BASEDIR=${BASEDIR} -e MM=${MM} \
        --network host \
        --restart unless-stopped \
        --name mm \
        --detach \
      misi/mm

In the config, I've only set rtcAnnouncedIPv4 and TURN settings.
When starting the image with Misi's run.sh, I'm getting:
Container starting up...
- process.env.DEBUG: undefined
- config.mediasoup.logLevel: warn
- config.mediasoup.logTags: [ 'info', 'ice', 'dtls', 'rtp', 'srtp', 'rtcp', 'rbe', 'rtx' ]
[opening Readline Command Console...]
cmd> [12:12:30] NODE_ENV: production
[12:12:30] Using gulpfile /opt/multiparty-meeting/app/gulpfile.js
[12:12:30] Starting 'dist-watch'...
[12:12:30] Starting 'clean'...
[12:12:30] 'clean' errored after 18 ms
[12:12:30] Error: EINVAL: invalid argument, rmdir '/opt/multiparty-meeting/server/public/resources/fonts'
[12:12:30] 'dist-watch' errored after 22 ms
/
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/chooseRoom.html'
/
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/chooseRoom.html'
/
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/chooseRoom.html'
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/index.html'
/
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/chooseRoom.html'
/
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/chooseRoom.html'
/
Error: ENOENT: no such file or directory, stat '/opt/multiparty-meeting/server/public/chooseRoom.html'

The page in the browser returns "Not Found" only.
How to track more details of these errors?

See:
git diff 4db338..4eb355
e.g. You have a
+RUN git checkout tags/1.1
Would it be possible to put all customization in misi/mm?
So not fork for up2u but customize from configs and volume mount everything.
I don't know if it is possible or not. I hope it is.
It would be for me easier to update and you (and any other user) will also benefit of a customizable image..
I mean make misi/mm ready to any user can customize it very well, so give you the tools and hooks that you need for up2u.
In such case we could avoid such code skew.

But this error is strange...
I will try to build your branch.
How did you build the image? docker-compose up --build?
I never had problem with the clean..
I have just rebuilt and tested and misi/mm.
I don't have such issue with it.
I fully understand that for you I guess more simple and preferred to use this forked model that we used with knockplop, but it may adds such complication.
e.g. Recently as you wrote I moved and renamed config and cert dirs and so I changed in both multiparty-meeting and misi/mm the configs simultan.
Maybe that is causing the issue? I am not sure...
But anyhow I think you should remove the line that checks out the branch 1.1.

Yes, we can customize instances via configs and volume mounts as you said. That will be easier, sure.
But the issue here is rather not because of the forking model. I've not been building the image on my own. I have just pulled from misi/mm. So ,the +RUN git checkout tags/1.1 should have not been a problem, but I just removed it, thanks.
Maybe I could give you the access to the problematic host to have a deeper look? Please send me your public SSH key.

centos + docker issue..
https://github.com/moby/moby/issues/27214

I finally found a solution by digging though the mess of related issues. Commenting here since this was my starting point, and maybe it will help someone else.
I installed the latest 4.12 kernel, and it didn't make a difference. This is actually a problem with the overlay fs in centos. The solution was to reformat the filesystem where the docker config is stored (/var/lib/docker) with some flags: mkfs -t xfs -n ftype=1 /PATH/TO/DEVICE
The problem is better described in #27358, but the solution is best explained in #29873.
More details from RedHat

@misi, how to reproduce the error from moby/moby#27214 on the host? I'm only seeing the errors I provided above.

try to docker exec -it mm bash and try to remove a directory it will fail..


FW-466. implemented light sensor functions for TelosB platform

I created all functions to implement the sensor on TelosB. Only light sensors are working at this time, but it will be easy to extend the implementation to other sensor later.

@pedrohenriquegomes , That's great! Thanks a lot for implementing this! I will merge this now!


fix: {"error": "xxx"} format error

Return an error even in the case of an error response in the {"error":"xxx"} format.
https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/errors
The above link introduces the following formatting error, It turns out that there is indeed {"error": "error message"} .
{"errors": [{"field": "identifier1", "message": "error message explained"}]}

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (80ec8ee) 68.70% compared to head (84d3872) 67.92%.

Files
Patch %
Lines

misc.go
75.00%
2 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
- Coverage   68.70%   67.92%   -0.79%
==========================================
  Files          13       13
  Lines         997     1007      +10
==========================================
- Hits          685      684       -1
- Misses        218      230      +12
+ Partials       94       93       -1

Flag
Coverage Δ

unittests
67.92% <75.00%> (-0.79%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Adds Beatroot News: Text-only

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the GTMetrix report
[x] The domain is in the correct alphabetical order
[x] This site is not a ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: news.tatooine.club
  url: https://news.tatooine.club/
  size: 31.5
  last_checked: 2023-06-09

GTMetrix Report: https://gtmetrix.com/reports/news.tatooine.club/YbePXoWm/

Thanks!


alloc counter test: better recursive malloc

Motivation:
The allocation counter integration tests previously used a pretty crude
malloc implementation for the case that malloc is needed whilst we
resolve malloc from libc using dlsym. This implements a much better
version and also allows us to actually use free. Previously we just
leaked all the memory (which is okay as its just a test but in
constrained environments this wouldn't scale as we might actually run
out of memory). The reason we used to leak the memory is that given a
pointer we couldn't figure out if that pointer was alloated using libc's
malloc or our crude malloc implementation so we didn't know how to free.
The new version fixes that as all the pointers vended from
recursive_malloc live in one global block. That makes it trivial to
check if a given pointer is allocated by recursive_malloc (lives in that
block) or libc's malloc (doesn't live in the recursive_malloc block).
Modifications:

implemented a better recursive_malloc function
make the allocation counter test actually free memory that can be
freed

Result:
Less memory use in the allocation counter test.

Late LGTM


Teach Forseti Explainer about roles/iam.serviceAccountUser

When listing who has access to e.g. a bucket, explain can:

list users added directly
list groups
list groups of groups

but there is (at least) one further way to have access:

Have yourself (or your group) assigned the role roles/iam.serviceAccountUser  on a serviceaccount with access to that bucket.

Because with that role I can impersonate that SA, and access anyway.

We are not looking at adding new, non-critical features to Forseti Explain at this time.


Addition of LaTeX Resources

Contribution to #65
Added LaTeX Resources to AlgoWiki

Thanks for contributing to AlgoWiki. 👍


ESX host not being pulling in

It seems if sync cannot do a DNS lookup it will add not the esx host
 ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx3.blah.com)
 [root@zronetbox1 ]# host <IP_ADDRESS>
<IP_ADDRESS>.in-addr.arpa domain name pointer lonesx3.blah.com.

is there a way to force this?

Can you try switching off the netbox caching and try again?

Can you try switching off the netbox caching and try again?

Hi,
Sorry but how do i do that?
Thanks
Adam
On Mon, Jan 25, 2021 at 7:03 PM Ricardo<EMAIL_ADDRESS>wrote:

Can you try switching off the netbox caching and try again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/30#issuecomment-767041791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXAE7T43MQ4MZSI6LQKR3S3W565ANCNFSM4WSEPBXA
.

--
Adam Barnett

Hi,
Sorry but how do i do that?
Thanks
Adam
On Mon, Jan 25, 2021 at 7:03 PM Ricardo<EMAIL_ADDRESS>wrote:

Can you try switching off the netbox caching and try again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/30#issuecomment-767041791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXAE7T43MQ4MZSI6LQKR3S3W565ANCNFSM4WSEPBXA
.

--
Adam Barnett

Your config file, Line 87!

Your config file, Line 87!

Still the same i'm afarid

Still the same i'm afarid

and if you delete the cache folder inside the netbox-sync folder?

and if you delete the cache folder inside the netbox-sync folder?

Still the same
2021-01-28 09:02:50,151 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,151 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmk0 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmk1 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,153 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,153 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,153 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,154 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,154 - ERROR: Unfortunately updated item device for object vmk0 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,155 - ERROR: Unfortunately updated item device for object vmk1 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,155 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,156 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,156 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,156 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,157 - ERROR: Unfortunately updated item device for object vmk0 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,157 - ERROR: Unfortunately updated item device for object vmk1 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,158 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,158 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,158 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,159 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,159 - ERROR: Unfortunately updated item device for object vmk0 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,160 - ERROR: Unfortunately updated item device for object vmk1 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,160 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,161 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,161 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,162 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,162 - ERROR: Unfortunately updated item device for object vmk0 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,162 - ERROR: Unfortunately updated item device for object vmk1 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,164 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx2.blah.com)' at<PHONE_NUMBER>25200>
2021-01-28 09:02:50,164 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx5.blah.com)' at<PHONE_NUMBER>22088>
2021-01-28 09:02:50,165 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx1.blah.com)' at<PHONE_NUMBER>14520>
2021-01-28 09:02:50,165 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx4.blah.com)' at<PHONE_NUMBER>24304>
2021-01-28 09:02:50,165 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx3.blah.com)' at<PHONE_NUMBER>80304>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx1.blah.com)' at<PHONE_NUMBER>14464>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx2.blah.com)' at<PHONE_NUMBER>98808>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx3.blah.com)' at<PHONE_NUMBER>90904>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx4.blah.com)' at<PHONE_NUMBER>26992>
2021-01-28 09:02:50,167 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx5.blah.com)' at<PHONE_NUMBER>35848>

Still the same
2021-01-28 09:02:50,151 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,151 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmk0 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,152 - ERROR: Unfortunately updated item device for object vmk1 (lonesx4.blah.com) could not be fully resolved: <NBDevice instance 'lonesx4.blah.com' at<PHONE_NUMBER>23744>
2021-01-28 09:02:50,153 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,153 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,153 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,154 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,154 - ERROR: Unfortunately updated item device for object vmk0 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,155 - ERROR: Unfortunately updated item device for object vmk1 (lonesx3.blah.com) could not be fully resolved: <NBDevice instance 'lonesx3.blah.com' at<PHONE_NUMBER>79760>
2021-01-28 09:02:50,155 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,156 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,156 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,156 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,157 - ERROR: Unfortunately updated item device for object vmk0 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,157 - ERROR: Unfortunately updated item device for object vmk1 (lonesx5.blah.com) could not be fully resolved: <NBDevice instance 'lonesx5.blah.com' at<PHONE_NUMBER>20128>
2021-01-28 09:02:50,158 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,158 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,158 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,159 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,159 - ERROR: Unfortunately updated item device for object vmk0 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,160 - ERROR: Unfortunately updated item device for object vmk1 (lonesx2.blah.com) could not be fully resolved: <NBDevice instance 'lonesx2.blah.com' at<PHONE_NUMBER>98472>
2021-01-28 09:02:50,160 - ERROR: Unfortunately updated item device for object vmnic0 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,161 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,161 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,162 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,162 - ERROR: Unfortunately updated item device for object vmk0 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,162 - ERROR: Unfortunately updated item device for object vmk1 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>12336>
2021-01-28 09:02:50,164 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx2.blah.com)' at<PHONE_NUMBER>25200>
2021-01-28 09:02:50,164 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx5.blah.com)' at<PHONE_NUMBER>22088>
2021-01-28 09:02:50,165 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx1.blah.com)' at<PHONE_NUMBER>14520>
2021-01-28 09:02:50,165 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx4.blah.com)' at<PHONE_NUMBER>24304>
2021-01-28 09:02:50,165 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx3.blah.com)' at<PHONE_NUMBER>80304>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx1.blah.com)' at<PHONE_NUMBER>14464>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx2.blah.com)' at<PHONE_NUMBER>98808>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx3.blah.com)' at<PHONE_NUMBER>90904>
2021-01-28 09:02:50,166 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx4.blah.com)' at<PHONE_NUMBER>26992>
2021-01-28 09:02:50,167 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx5.blah.com)' at<PHONE_NUMBER>35848>

Can you test if the branch for the other issue #29 solves this issue as well?

I checkout the new branch,
(venv) [root@zronetbox1 netbox-sync]#   git branch
* feature/strip-domain-from-name

but still got the same error
2021-02-04 20:24:05,874 - ERROR: Unfortunately updated item device for object vmnic1 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>19792>
2021-02-04 20:24:05,874 - ERROR: Unfortunately updated item device for object vmnic2 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>19792>
2021-02-04 20:24:05,874 - ERROR: Unfortunately updated item device for object vmnic3 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>19792>
2021-02-04 20:24:05,875 - ERROR: Unfortunately updated item device for object vmk0 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>19792>
2021-02-04 20:24:05,875 - ERROR: Unfortunately updated item device for object vmk1 (lonesx1.blah.com) could not be fully resolved: <NBDevice instance 'lonesx1.blah.com' at<PHONE_NUMBER>19792>
2021-02-04 20:24:05,877 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx2.blah.com)' at<PHONE_NUMBER>50408>
2021-02-04 20:24:05,877 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx5.blah.com)' at<PHONE_NUMBER>82088>
2021-02-04 20:24:05,877 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx1.blah.com)' at<PHONE_NUMBER>19344>
2021-02-04 20:24:05,878 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx4.vlah.com)' at<PHONE_NUMBER>03024>
2021-02-04 20:24:05,878 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk1 (lonesx3.blah.com)' at<PHONE_NUMBER>85944>
2021-02-04 20:24:05,878 - ERROR: Unfortunately updated item assigned_object_id for object <IP_ADDRESS>/24 could not be fully resolved: <NBInterface instance 'vmk0 (lonesx1.blah.com)

And these are the only ERRORs you get? No other Errors? Can you send me a full log with log option "DEBUG2" to my mail address?
https://github.com/bb-Ricardo/netbox-sync/blob/fef5188f62800170f2603f424d2614e319db9314/netbox-sync.py#L30

Thanks i have sent the full logs
On Thu, Feb 4, 2021 at 8:32 PM Ricardo<EMAIL_ADDRESS>wrote:

And these are the only ERRORs you get? No other Errors? Can you send me a
full log with log option "DEBUG2" to my mail address?
https://github.com/bb-Ricardo/netbox-sync/blob/fef5188f62800170f2603f424d2614e319db9314/netbox-sync.py#L30
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/30#issuecomment-773586168,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXAE2EBLCC6DVDX5D2NTDS5L76FANCNFSM4WSEPBXA
.

--
Adam Barnett

Were you able to figure out the issue?

Not yet, i was having trouble using the swagger API to POST it complained
about the tags
On Mon, Feb 8, 2021 at 2:52 PM Ricardo<EMAIL_ADDRESS>wrote:

Were you able to figure out the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/30#issuecomment-775203642,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXAE4XZ6TCUYUIT6OL7GLS573CHANCNFSM4WSEPBXA
.

--
Adam Barnett

really? Usually works for me. 🤔

any updates?

Sorry no, but you can close this case for now
On Fri, Feb 26, 2021 at 4:41 PM Ricardo<EMAIL_ADDRESS>wrote:

any updates?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bb-Ricardo/netbox-sync/issues/30#issuecomment-786758503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXAEZ23CNOKRRNLOTQATLTA7FKLANCNFSM4WSEPBXA
.

--
Adam Barnett

Thanks for the feedback. Will close this for now.

@bb-Ricardo
I had exactly the same issue. In my case was the problem, that my device config I had an mandatory field and no default value. The exception comes when the script will create a new device.


fix: 修复在维值缺失场景下导出数据占位符未解析的问题

👀 PR includes

🐛 Bugfix

[x] Solve the issue and close #0

📝 Description

背景见: https://github.com/antvis/S2/pull/2829/files
这个是 1.x 已经修复过的, 当时同步过来由于 2.x 整体导出链路变了, 忘记修改了.
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

:tada: This PR is included in version @antv/s2-v2.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


compiler crash TypeError: Cannot read property 'type' of undefined when allowJs=true

TypeScript Version: 2.5.0-dev.20170616
Attempting to compile with allowJs = true crashes the compiler.
No crash with allowJs = false
I'm not able to localize which .js file causes the problem, as there are a lot.
Expected behavior:
No crash, many code problems reported
Actual behavior:
Compiler crashes, nothing reported, just a stack trace.
% tsc
/usr/lib/node_modules/typescript/lib/tsc.js:55789
                throw e;
                ^

TypeError: Cannot read property 'type' of undefined
    at resolveBaseTypesOfClass (/usr/lib/node_modules/typescript/lib/tsc.js:22130:73)
    at getBaseTypes (/usr/lib/node_modules/typescript/lib/tsc.js:22089:25)
    at checkClassLikeDeclaration (/usr/lib/node_modules/typescript/lib/tsc.js:34332:33)
    at checkClassDeclaration (/usr/lib/node_modules/typescript/lib/tsc.js:34302:13)
    at checkSourceElement (/usr/lib/node_modules/typescript/lib/tsc.js:35211:28)
    at Object.forEach (/usr/lib/node_modules/typescript/lib/tsc.js:289:30)
    at checkSourceFileWorker (/usr/lib/node_modules/typescript/lib/tsc.js:35280:20)
    at checkSourceFile (/usr/lib/node_modules/typescript/lib/tsc.js:35265:13)
    at Object.forEach (/usr/lib/node_modules/typescript/lib/tsc.js:289:30)
    at getDiagnosticsWorker (/usr/lib/node_modules/typescript/lib/tsc.js:35330:16)

Config:
    "compilerOptions": {
        "module": "es6",
        "target": "es5",
        "outDir": "lib",
        "noImplicitAny": false,
        "sourceMap": true,
        "declaration": false,
        "pretty": true,
        "skipLibCheck": false,
        "strictNullChecks": true,
        "allowJs": true
    },

If you can provide a minimal repro, or potentially if you're willing to let us sign an NDA for the code, we can  take a look.

OK, I was able to reduce the case down to a handful of mostly empty files importing each other.
Here's an interesting tidbit, possibly a clue:
Removing this comment in file app/core/models/Role.js makes the crash go away:
/**

@augments Base
*/

tc-16585.zip

Reproduced the same issue (allowJs option enabled) with the following stack track:
TypeError: Cannot read property 'type' of undefined
    at Object.getEffectiveTypeAnnotationNode (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:7350:17)
    at assignContextualParameterTypes (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:34465:25)
    at checkFunctionExpressionOrObjectLiteralMethod (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:34717:29)
    at checkExpressionWorker (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35590:28)
    at checkExpression (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35534:42)
    at checkBinaryLikeExpression (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35183:29)
    at checkBinaryExpression (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35175:20)
    at checkExpressionWorker (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35611:28)
    at checkExpression (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35534:42)
    at checkBinaryLikeExpression (C:\Users\hidden\AppData\Roaming\npm\node_modules\typescript\lib\tsc.js:35183:29)

Running into the same problem. I couldn't locate the file that crashes it unfortunately.
<EMAIL_ADDRESS>

I've just faced the same problem. Fortunately I was able to create a small reproducer: https://github.com/stas-vilchik/ts-reproducer.
Actually the failure happens only when "allowJs" is true.
Hope this will help!

Thanks @stas-vilchik, I will work from that repro.

The crash happens because using arguments in JS causes a synthetic rest parameter to be created. But the parameter doesn't have a declaration (it's not actually declared). assignContextualParameterTypes assumes that all rest parameters have a declaration, which causes the crash when parameter.valueDeclaration is passed to getEffectiveTypeAnnotationNode.
I think the correct fix is to just make assignContextualParameterTypes know that transient symbols (1) have no declaration (2) should be contextually typed anyway. But I could instead find a node to serve as the "declaration", similar to the way that = is the declaration node for this.prop = value inside a javascript constructor. Then getEffectiveTypeAnnotationNode would need to return undefined for this node.
I'll have a fix up shortly, as soon as I make the repro even smaller.

Fix is up at #18392


Added support for linux and osx testing.

Damn, this wasn't so easy that I though. Will close this one for now and make this working...


How to submit form data along with files?

I have a simple registration form, and I would like to add support for images using ng-flow:

 User REGISTRATION

<form class="form-horizontal" enctype="multipart/form-data">
    <input ng-model="user.name">
    <input ng-model="user.email">

        <input type="file" flow-btn/>

                {{$index+1}}
                {{file.name}}
                {{file.msg}}

      <button ng-click="submitForm()">Submit Form</button>
</form>

My controller has these things:
$scope.user = {};
$scope.upload = {};
$scope.submitForm = function() {
    $http.post('/formSubmit', { "user_data": $scope.user });
}

The controller currently just POSTs the user object that contains the name and email. How can I POST  all the data including the images files to the server at once? Or is this not recommended? If it's not recommended, how should I handle user registration with files?
I'm confused because I have ng-submit="upload.flow.upload()", but how will that work to submit the other data in the form like how I have it in submitForm()?

Got an answer ?

I have the same problem.
I have an image on a form with multiple object properties (ng-model). I don't know how can i save that image into my object... and send it on submit form.

probably, you may setup the query function . see #33

I am struggling with the same, please suggest solution.

ngFlowQuery: function(flowFile, flowChunk) {
return {
yourParam: value
};
},

thanks a lot