How to implement Redux?

Hi guys, any idea how to implement Redux? where can I find example Redux + React Server?

Here's a basic example, a reimplementation of the Redux counter app in react-server:
https://github.com/hzhu/react-server-redux-basic
Now how you structure a react-server, Redux application is up to you.

Whoa! @hzhu that's awesome!
We should link to that example from our docs.  Leaving this open as a reminder.

@hzhu @gigabo what about pulling it into react-server-examples?

Yeah I was planning on that! How about I submit a PR for review in a day or two?

Even better!  Thanks @hzhu!

@hzhu thanks a lot!!

@incubus8 I realized that the Counter example isn't too useful once one introduces data fetching & user interaction. Here's a better use case with react-server & redux. It's still a work in progress, but seems to work. https://github.com/hzhu/react-server-redux
It's a bit messy, but once I learn how to cleanly setup a redux project with react-server, I'll make the PR to react-server-examples

@hzhu Any chance you've had any luck using the RootElement's 'where' with Redux?  I'd like to render a component only when an async data call has completed, but 'where' requires a Promise, and my dispatch will no longer work if I return a promise instead of a function.
https://react-server.io/docs/guides/understanding-rendering

@woomike, did you mean RootElement's when attribute?
You can try representing your async data fetching as a promise, and put that, as the value to when.
For example..
const myPromise = new Promise((resolve, reject) => {
  // data fetch
  // async stuff here
})

<RootElement when={myPromise} />

Or more likely you might want to use ReactServerAgent.get() to fetch data from an api.
ReactServerAgent is a promise that represents the eventual result of the fetch.
I have a working demo of rendering async data using redux and react-server. The specific line you might want to check out is https://github.com/hzhu/react-server-redux/blob/master/src/pages/explore/index.js#L35
Note: I'm finding it very difficult to structure a redux app properly in react-server, i.e. how to manage store/stores & reducers. Let me know if you have some tips :)

@hzhu Thanks so much for getting back to me.  My apologies on the typo, yes I meant when.  I ended up being able to properly implement when and dispatch by using the handleRoute built into react-server.
	handleRoute(next) {
		this.data = Promise.resolve(store.dispatch(getFoo()));
		return next()
	}

	<RootElement key={0} when={this.data}>


External error while infer capture

  When I run 'infer capture' with sam2p-0.49.4, the unknown external error is occurred. The 'make' and 'make clean' commands work fine without Infer. So I want to get some help to know what caused this error.

[x] The version of infer from infer --version.

$ ../infer-linux64-v1.0.0/bin/infer --version
Infer version v1.0.0
Copyright 2009 - present Facebook. All Rights Reserved.

[x] Your operating system and version, for example "Debian 9", "MacOS High Sierra", whether you are using Docker, etc.

Ubuntu 18.04.4 LTS

[x] Which command you ran, for example infer -- make.

../infer-linux64-v1.0.0/bin/infer capture -- make

[x] The full output in a paste, for instance a gist.

Capturing in make/cc mode...
g++ -s -O2 -DHAVE_CONFIG2_H   -fsigned-char -fno-rtti -fno-exceptions -ansi -pedantic -Wall -W -Wextra -c ps_tiny.c
g++ -s   ps_tiny.o -o ps_tiny
Created executable file: ps_tiny (size: 22672).
<l1zip.psm >l1g8z.pst.tmp.h perl -pe0
g++ -E -DCFG_FMT_ZLIB_ONLY=1 -DNDEBUG=1 -DCFG_NO_VAR_S=1 -DUSE_NO_BIND=1 -DUSE_SHORT_NAMES=1 -DUSE_CURRENTFILE=1 -DUSE_NO_EOF=1 -DUSE_UNITLENGTH_8 -DUSE_EARLYCHANGE_1 -DUSE_LOWBITFIRST_FALSE -DUSE_NO_NULLDEF=1 -DUSE_PIN=1 -DUSE_A85D=1 l1g8z.pst.tmp.h >l1g8z.pst.tmp.i
<l1g8z.pst.tmp.i >l1g8z.pst.tmp.pin perl -ne's@/\s+(?=\w)@/@g;print if!/^#/&&!/^\s*\Z/'
<l1g8z.pst.tmp.pin >l1g8z.pst.tmp.ps0 ./ps_tiny
ps_tiny: error at 1.2.1: tag %<Head or %<Open expected
Makefile:145: recipe for target 'l1g8z.pst' failed
make: *** [l1g8z.pst] Error 3
External Error: *** capture command failed:
*** make
*** exited with code 2

Error backtrace:
Raised at Stdlib__scanf.bad_input in file "scanf.ml" (inlined), line 444, characters 18-40
Called from Stdlib__scanf.scanf_bad_input in file "scanf.ml", line 1164, characters 4-75
Called from IBase__Utils.get_available_memory_MB.scan_for_expected_output in file "src/base/Utils.ml", line 439, characters 10-86
Re-raised at IBase__Die.raise_error.do_raise in file "src/base/Die.ml" (inlined), line 26, characters 8-56
Called from IBase__Logging.die.(fun) in file "src/base/Logging.ml", line 347, characters 6-39
Called from Integration__Driver.capture in file "src/integration/Driver.ml", line 148, characters 6-40
Called from IBase__Utils.timeit in file "src/base/Utils.ml", line 421, characters 16-20
Called from IBase__ScubaLogging.execute_with_time_logging in file "src/base/ScubaLogging.ml" (inlined), line 79, characters 29-44
Called from Integration__Driver.capture.(fun) in file "src/integration/Driver.ml", line 180, characters 2-233
Called from Backend__GCStats.log_f in file "src/backend/GCStats.ml" (inlined), line 90, characters 10-14
Called from Integration__Driver.capture in file "src/integration/Driver.ml", line 178, characters 2-288
Called from Dune__exe__Infer.run in file "src/infer.ml" (inlined), line 20, characters 2-36
Called from IBase__Utils.timeit in file "src/base/Utils.ml" (inlined), line 421, characters 16-20
Called from IBase__ScubaLogging.execute_with_time_logging in file "src/base/ScubaLogging.ml" (inlined), line 79, characters 29-44
Called from Dune__exe__Infer.run in file "src/infer.ml", line 25, characters 22-94

Run the command again with `--keep-going` to try and ignore this error.

Hello @kangwoosukeq. The error is because Infer cannot understand the situation that g++ is used as a preprocessor.
Background: infer-capture hooks g++ compilation commands by adding path to wrappers
g++ -E -DCFG_FMT_ZLIB_ONLY=1 -DNDEBUG=1 -DCFG_NO_VAR_S=1 -DUSE_NO_BIND=1 -DUSE_SHORT_NAMES=1 -DUSE_CURRENTFILE=1 -DUSE_NO_EOF=1 -DUSE_UNITLENGTH_8 -DUSE_EARLYCHANGE_1 -DUSE_LOWBITFIRST_FALSE -DUSE_NO_NULLDEF=1 -DUSE_PIN=1 -DUSE_A85D=1 l1g8z.pst.tmp.h >l1g8z.pst.tmp.i

This line was not able to write l1g8z.pst.tmp.i correctly since g++ was hooked by infer.
A quick workaround is to change g++ -E in Makefile to use absolute path, eg /usr/bin/g++ -E, which will prevent infer to  hook the preprocessing command.

Now it works fine! Thanks for your kind reply.


Bluetooth: Mesh: Config Client timeout setting

Adds a Kconfig option for setting the Config Client timeout and
updates the default to allow reception of full sized message
from a similar peer device at zero hops.
Signed-off-by: Omkar Kulkarni<EMAIL_ADDRESS>

What about the health client? Do we want to have a common option for both?

Most health model status messages are fairly short. The only message that can probably become 2-3 segment message is - Health Fault Status. Although the fault table is big, not all faults can occur simultaneously since many of them are application-specific.
Because the functionality and scope of these two models are quite different, I would go for a separate option for health client.


bug: Sending message crashes because of calling function in lua's loop

Describe the bug
I'm using this config
return {
  "yetone/avante.nvim",
  event = "VeryLazy",
  lazy = false,
  version = false,
  opts = {
    provider = "openai",
    openai = {
      endpoint = "http://shiralad:11434/v1",
      model = "yi-code",
      temperature = 0,
      max_tokens = 4096,
      ["local"] = true,
    },
  },
  build = "make",
  dependencies = {
    "stevearc/dressing.nvim",
    "nvim-lua/plenary.nvim",
    "MunifTanjim/nui.nvim",
    {
      -- Make sure to set this up properly if you have lazy=true
      "MeanderingProgrammer/render-markdown.nvim",
      opts = {
        file_types = { "markdown", "Avante" },
      },
      ft = { "markdown", "Avante" },
    },
  },
}

then I do <leader>aa and call ask a question, as soon as I sent I get this error:
Error executing luv callback:
...g/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:19: E5560: nvim_buf_get_name must not be called in a lua loop callback
stack traceback:
        [C]: in function 'nvim_buf_get_name'
        ...g/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:19: in function 'filename'
        ...g/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:36: in function 'get'
        ...g/.local/share/nvim/lazy/avante.nvim/lua/avante/path.lua:53: in function 'save'
        ...local/share/nvim/lazy/avante.nvim/lua/avante/sidebar.lua:1270: in function 'on_complete'
        ...fg/.local/share/nvim/lazy/avante.nvim/lua/avante/llm.lua:150: in function '_user_on_exit'
        .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:241: in function '_shutdown'
        .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:48: in function <.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:39>

To reproduce
No response
Expected behavior
No response
Environment
nvim --version
NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1713773202
Run "nvim -V1 -v" for more info

Looks like save needs to be vim.scheduled

Also running in this issue. No idea why.
{
        "yetone/avante.nvim",
        enable = false,
        event = "VeryLazy",
        build = "make",
        opts = {
            -- add any opts here
        },
        dependencies = {
            "echasnovski/mini.icons",
            "stevearc/dressing.nvim",
            "nvim-lua/plenary.nvim",
            "MunifTanjim/nui.nvim",
            --- The below is optional, make sure to setup it properly if you have lazy=true
            "zbirenbaum/copilot.lua", -- for providers='copilot'
            {
                -- support for image pasting
                "HakonHarnes/img-clip.nvim",
                event = "VeryLazy",
                opts = {
                    -- recommended settings
                    default = {
                        embed_image_as_base64 = false,
                        prompt_for_file_name = false,
                        drag_and_drop = {
                            insert_mode = true,
                        },
                    },
                },
            },
            {
                "MeanderingProgrammer/render-markdown.nvim",
                opts = {
                    file_types = { "markdown", "Avante" },
                },
                ft = { "markdown", "Avante" },
            },
        },
    }

Ok after trying to fix this issue for literal days, I think I found a workaround.
plenary uses XDG_RUNTIME_DIR for some curl things, as outlined here: https://github.com/nvim-lua/plenary.nvim/blob/ec289423a1693aeae6cd0d503bac2856af74edaa/lua/plenary/curl.lua#L81
(if XDG_RUNTIME_DIR env var exists)
Now the problem on my side was, that XDG_RUNTIME_DIR was set to a folder which does not exist (because I'm a poor soul needing to use WSL for my job and Windows messed this up for me).
Solution: Before starting neovim:
export XDG_RUNTIME_DIR="/tmp/"

This is actually either a plenary problem or even a WSL-or-whatever-distro-you-use-problem. I think we can let the avante-folks off the hook 😄

Weird, for me the error happens in nvim_buf_get_name which is not a plenary function. And my XDG_RUNTIME_DIR exists.

Weird, for me the error happens in nvim_buf_get_name which is not a plenary function. And my XDG_RUNTIME_DIR exists.

Hm ok, just to be safe, did you try setting the var to /tmp before entering nvim? My error also happened in nvim_buf_get_name. But if you look at the stack trace, it starts with plenary (you also see it in your initial description, the very last line in the exception you posted).
So my error message was exactly the same as yours. Even with the same line numbers.

I just tried that and it didn't work.

I have the same problem, the environment is Windows+GitBash.

I'm on nixos, so the problem is not because of the OS.

I have the same issue on macos.

Anyone figured this out yet? I'm seeing it on NeoVim 0.10.2.

@retarpt I made a pr weeks ago, no Idea why is it not merged.

Same error in MacOS; I've seem the pr is approved in https://github.com/yetone/avante.nvim/pull/560.
However, there are still some conflicts; I would appreciate it if you could merge this pr! @aarnphm

This PR has been merged, everyone can try updating: https://github.com/yetone/avante.nvim/pull/560

Is this fixed for everyone? I still have the same error.


Feature/onlog

Codecov Report
Base: 99.69% // Head: 99.69% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (a49f7b4) compared to base (2a678a1).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #65   +/-   ##
=======================================
  Coverage   99.69%   99.69%
=======================================
  Files          46       46
  Lines        2260     2277   +17
  Branches      438      435    -3
=======================================
+ Hits         2253     2270   +17
  Misses          7        7

Impacted Files
Coverage Δ

flagship/src/config/FlagshipConfig.ts
100.00% <100.00%> (ø)

flagship/src/enum/FlagshipConstant.ts
100.00% <100.00%> (ø)

flagship/src/main/Flagship.ts
98.49% <100.00%> (ø)

flagship/src/utils/utils.ts
100.00% <100.00%> (ø)

flagship/src/visitor/DefaultStrategy.ts
99.69% <100.00%> (+<0.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Restore worker release env var

This env var is still used by the leviathan-worker project for e3e tests against draft worker releases.
Change-type: patch
Signed-off-by: Kyle Harding<EMAIL_ADDRESS>

@balena-ci I self-certify!


Difference to https://github.com/testcontainers/testcontainers-java ?

Hi, nice project but does https://github.com/testcontainers/testcontainers-java not the same ?

Yes and no.
With test containers the docker container lifecycle is somewhat designed around the test code (before, after etc used to explicitly control the lifecycle of the docker containers).  We can do that with this project ebean-test-docker and some people not using Ebean do that rather than using test containers (known ports etc). Ebean users generally don't do that though and instead the desire is to keep the docker containers running for the duration of all the tests.  In fact, we typically only stop and remove containers on CI servers, developers would generally keep the containers running so that testing is really fast.
So this is more orientated to ... testing like we do with H2 in memory database but with docker database containers ( + redis, + elasticsearch etc).
The lifecycle of the docker containers was originally oriented to support the maven lifecycle but then that wasn't transparent when as developers we want to run a single test via the IDE.  Now, the docker container lifecycle hooks into Ebean's lifecycle (via ebean-test-config) meaning as developers we can just run a single test in the IDE and it just works and is fast because typically the container is in fact already running (plus it then works for any command line builds via maven, gradle etc).
On top of the lifecycle difference the database containers are featured to be setup with database(s), user(s), schema, seed sql etc and with ebean-test-config the configuration such as url, username, password etc for testing is automatically set as well.
So in these ways when combined with ebean-test-config is is reasonably different.

@rbygrave  thanks for explanation

I'll close this for now.


Can't use both file and string parameters

When invoking a build that takes both file and string parameters, this error is raised:
ValueError: Builds with file parameters are not supported by this jenkinsapi version. Please use previous version.
When using only strings and only the file it works fine. Also, when commenting the code raising this exception, the build is triggered and works fine, but the python function never returns.
Are there any reasons why this combination of parameters have been deactivated ?

This was deactivated because Jenkins doesn't support this though QueueItem API. At the same time the use of QueueItem API is encouraged by Jenkins developers because it provides ability to find exact build that was triggered by particular job invocation.
I hope that if somebody raises that in Jenkins issue log, the issue will be fixed.

The error is on Jenkins' side, however it seems to work quite well for me when guessing the next QueueItem with get_next_build_number().
The down side is that if a build gets triggered between our build and the guess, we will wait for this build...except if we check the parameters to see if they match.
I submitted this PR (https://github.com/salimfadhley/jenkinsapi/pull/364) to allow querying Jenkins with this method.
Is it acceptable to do like this or should the API be enforced ?

As you can see pull request failed in the method that you have changed, so I can't accept that pull request.
And yes, you are correct about the downside - it could lead to inconsistent result.


MapTileApproximater OutOfMemoryError when zooming out deep

Issue Type
[x] Bug
Description and/or steps/code to reproduce the problem
With wi-fi turned on, pinch zoom out a large amount quickly and do not lift fingers (say, with fingers going from the screen corners to the center fast). The following exception occurs, because too many tiles are being loaded and scaled at the same time. Note that, until you lift up the fingers, the tiles will be loaded at the higher resolution (before the zoom started), and that makes hundreds of tiles being loaded and scaled and the same time at the lower zoom level, beforel you lift the fingers. And this throws this exception, causing the app to crash and vanish. I suggest that the resolution at which the tiles are being loaded should be updated during pinch zoom, to avoid loading hundreds of high res tiles simultaneously.
Anyway, congratulations for the MapTileApproximater - it greatly increased UX for offliners!
12-10 22:19:26.961 6813-6965/? I/art: Waiting for a blocking GC Alloc
12-10 22:19:26.968 6813-6968/? I/OsmDroid: Error downloading tile: /17/62449/50269
java.lang.OutOfMemoryError: Failed to allocate a 262156 byte allocation with 0 free bytes and 3GB until OOM
   at dalvik.system.VMRuntime.newNonMovableArray(Native Method)
   at android.graphics.Bitmap.nativeCreate(Native Method)
   at android.graphics.Bitmap.createBitmap(Bitmap.java:831)
   at android.graphics.Bitmap.createBitmap(Bitmap.java:808)
   at android.graphics.Bitmap.createBitmap(Bitmap.java:775)
   at org.osmdroid.tileprovider.modules.MapTileApproximater.getTileBitmap(MapTileApproximater.java:250)
   at org.osmdroid.tileprovider.modules.MapTileApproximater.approximateTileFromLowerZoom(MapTileApproximater.java:206)
   at org.osmdroid.tileprovider.modules.MapTileApproximater.approximateTileFromLowerZoom(MapTileApproximater.java:184)
   at org.osmdroid.tileprovider.modules.MapTileApproximater.approximateTileFromLowerZoom(MapTileApproximater.java:148)
   at org.osmdroid.tileprovider.modules.MapTileApproximater.approximateTileFromLowerZoom(MapTileApproximater.java:130)
   at org.osmdroid.tileprovider.modules.MapTileApproximater$TileLoader.loadTile(MapTileApproximater.java:111)
   at org.osmdroid.tileprovider.modules.MapTileModuleProviderBase$TileLoader.run(MapTileModuleProviderBase.java:317)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
   at java.lang.Thread.run(Thread.java:818)
12-10 22:19:26.968 6813-6968/? I/art: Waiting for a blocking GC Alloc
12-10 22:19:26.973 6813-6970/? I/art: Waiting for a blocking GC Alloc
12-10 22:19:26.978 6813-6823/? I/art: Waiting for a blocking GC Alloc

Environment
If it's a bug, version(s) of android this affects:
API 23 at least
Version of osmdroid the issue relates to:
6.0.0-SNAPSHOT

thanks for the report, glad it was discovered before we cut the release

Seems related to #757, and potentially to be fixed by #790.

@miguel-porto Should be fixed by #800. Could you give it a try?

Yep, it does work now without problems!
However, this change brought a slight decrease in UX: the pinch zoom is not totally smooth any more, you can notice breaks every time the tile resolution changes during pinch zoom.

@miguel-porto I'm glad it helped!
About the UX issue you mentioned: do you mean that the pinch gesture is smooth in itself but that you notice a break in the display of the tile every time the tile resolution changes (e.g. from 5.9 - which is tile 5 multiplied by 1.9 - to 6 - which is tile 6)?
What happens if you zoom in and out and in and out on the same location: do you still experience that little break?

Thank you!
Yes, it is exactly as you describe - the pinch zoom is smooth except for those little breaks when tiles from a higher resolution are loaded. It happens also when doing as you say, zooming in and out repeatedly in the same location. However, this does not happen on pinch zoom out - when pinch zooming out, the gesture is smooth all throughout the tile resolutions, tiles are replaced by lower resolution ones without any noticeable break.
But this is just a minor detail that is not of much importance.

well it's merged, i'll open a new ticket to describe the new issue and we'll move on

Let's focus on #812 now!


Refactor Player into Singleton | improve Interaction system | set framework for NPC Interaction | update Bridge-representation

Its been long, its been late, I'm sorry.
This PR primarily wants to resolve #134 --> the conversion from the whole player and its state into a globally accessible singleton structure.
This restructure allows different scenes to access the current state of the player ( inventory / animals in inventory and similar ) or to query information from it.
Furthermore it centralizes saving and loading a world-state into this single position.
resolves: #137  as every bridge is now denoted by its starting and destination node ( being an edge so to say ). We save the progress and state of the graph in an adjacency list within the player singleton.
Upon interaction with a bridge its status is checked and thus it will notify us whether we have solved it or not.
resolves: #180
-> although this needs refinement, I will link further information in a new issue soon
sets adaptable framework for representation of a bridge level #91
-> we use BridgeEdge structures that contain a starting and destination point ( denoting an island ) which are then stored in our player and also within each node itself. They  query their status upon initialization of the world
More information here: https://github.com/mango-gremlin/arch-enemies/wiki/04-Overworld-Navigation
resolves: #186
Changes :
I will list a large block of changes that were made and added / implemented in this PR.
I am aware that this is too much for one PR and makes it difficult to review and check. I apologize for this behavior and will try to reduce the amount of work done in a single PR for the next part.
I tried commenting everything I've added / changed and hope that it makes the code readable and useable.
| Changes |
overworld:

created a new overworld scene where we can play and test changes overworld_test_scene

helps not to collide with more up to date implementations of our game, yet provides an area to test scenarios and more

Player:

disallowing Player to move when in dialogue
mostly refactored to singleton that loads and manages those information
loading/storing saves not done yet
updating the ui was moved to Player and is not contained in the add_to_inventory() of the singleton_player anymore

Bridges:

added system to denote connections between island ( via bridges)

bridges are described as (startID,destID)  structures and encapsulated in class "BridgeEdge" --> for ease of usage

Bridge-Connections are stored in an adjaceny-list, which is symmetrical (by implementation, not design) because of undirected graph
querying status for a given edge (bridge) requires an instance of BridgeEdge
methods for bridge_interaction were added

visualize_status() checks solved-status and either shows / hides all parts contained in $bridge_parts (which is and ought to be a child of bridge_interactionspots!)
set_passability() checks solved-state and either lets player pass or block walking along bridge

both methods described are run upon instantiation  of the object itsefl

ISSUES with that:
The following is not an issue per se, however it makes creating new bridges a little tedious. Its another issue denoted here: #TODO

linking two bridge-parts to contain the same child parts

can be solved by creating new node which contains those (( and links them accordingly))!

implementing a bridge connection requires one to

set two individual bridge-elements  ( and set their ids to be the same)
adding a child-node which contains the collision ( which also ought to be shaped!)
updating the amount of bridge-parts and positioning them correctly to connect the island

NPC:

created new class denoting an NPC
static func init_animal_inventory(): was added to singletonPlayer might be moving once we have converted / adapted initializing the inventory correctly

UI:

update requesting / getting information about UI
added ui for animal inventory
unused elements were removed

Testing
Most interactions are the same as before.
We ought to update and change the way the UI is updated / fed so here the initial bug of the inventory not loading is back #100  --> However its tracked in a new issue and easy to resolve again.
Whenever entering a dialogue now you will be stuck until you press "Q" which will release the in_dialogue state from the player.
There are some additional issues with the NPC Interaction:
The animal_inventory is not implemented yet and thus does not increase upon receiving a new animal from somewhere.
The UI is not tracking any animals either --> because they have not been implemented accordingly yet.
| Whats to be done |
To complete the implementation some changes are necessary:

removing most code from npc_interaction to its own class NPC which then acts as interface for the interaction itself
creating a representation for Animals such that we can easily track the amount of them we have stored
implementing the npc dialogue system which is intertwined with the player class and the npc class.
maybe refactoring portions from singleton_player to a new fraction that coordinates overworld/bridgelevel state management

further resolves #186

Most interactions are the same as before.
We ought to update and change the way the UI is updated / fed so here the initial bug of the inventory not loading is back https://github.com/mango-gremlin/arch-enemies/issues/100 --> However its tracked in a new issue and easy to resolve again.

This has been resolved with commit 0260f8e

I already worked on it while solving the dialogue issues and it does the job. There are some points I'm unsure of, e. g. the necessarity for NPC_interaction.
Regarding the singleton configuration, this looks like a DerSimi Job. I will do it, as soon as the dialogue system is finished.

@DerSimi  could you elaborate on this comment?

Regarding the singleton configuration, this looks like a DerSimi Job. I will do it, as soon as the dialogue system is finished.

Do you mean the 4. point of the "whats to be done" section?

While resolving the merge conflict - caused by the newly implemented tilemap - I added some basic npcs to interact with again, to allow showcasing the interaction and quests with them.


TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["x-ms-qps-machine-name"]

After updating my dependency to "applicationinsights": "^2.2.2" I see an error because os.hostname() has an apostrophe and this value is not sanitized before being put into a header. I fixed this only by changing my machine's hostname with scutil --set HostName rob
Full stack trace
(node:8275) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["x-ms-qps-machine-name"]
    at ClientRequest.setHeader (_http_outgoing.js:564:3)
    at new ClientRequest (_http_client.js:262:14)
    at Object.request (https.js:370:10)
    at Object.https.request (/Users/rob/workspace/partner-inventory-service/node_modules/applicationinsights/AutoCollection/HttpDependencies.ts:115:74)
    at QuickPulseSender.<anonymous> (/Users/rob/workspace/partner-inventory-service/node_modules/applicationinsights/Library/QuickPulseSender.ts:114:27)
    at step (/Users/rob/workspace/partner-inventory-service/node_modules/applicationinsights/out/Library/QuickPulseSender.js:33:23)
    at Object.next (/Users/rob/workspace/partner-inventory-service/node_modules/applicationinsights/out/Library/QuickPulseSender.js:14:53)
    at /Users/rob/workspace/partner-inventory-service/node_modules/applicationinsights/out/Library/QuickPulseSender.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/rob/workspace/partner-inventory-service/node_modules/applicationinsights/out/Library/QuickPulseSender.js:4:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:8275) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:8275) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@robadurbin-gp which version of Node.js are you using?, can you share some hostname example, I tried apostrophes and tons of other ASCII characters and I'm not getting any error. Is this error triggered when looking at Live Metrics?

I can reproduce this on Windows using the same version -  2.2.2. I triggered the error by renaming a VM's computer name to include a unicode symbol: ¢ -- so something like mycomputer¢
No visible effects to the user, but these errors are flooding our cloud telemetry.

@hectorhdzg I'm using node v16.14.2 and as it turns out, mac default computer names like Rob's Computer do not use a standard apostrophe ascii code 39, of course they went with the fancy unicode character 8217 so use this character and you should be able to reproduce this.

@robadurbin-gp I was able to connect to Application Insights (specifically QuickPulse which appears to be throwing the error from your stack trace) on a macOS machine with a machine name including Unicode (tested with a few different characters). From my testing it appeared to be sanitizing the machine name input at some point since the machine name displayed on the Azure Portal didn't contain any of the unicode characters.
Could you ensure that you're on the latest version of Application insights and send me the headers on your request that's generating your error?


More reminders about right to protection about retaliation

some people are afraid to even mention their landlord's name

Might even want to allow the tenant to leave the landlord's name blank.

Make LL's address optional.


Coprocessor default read pool size may not taking effect

For the following config, it works:
# intentionally leave empty.

For the following config, it breaks:
[readpool.coprocessor]

Opened an issue in serde: https://github.com/serde-rs/serde/issues/1254
If serde can solve this issue it would be great. However if it is "won't fix", we need workarounds.

That's why there are three different structs for three rocksdb cfs' configuration.

Looks like some tests are missing.

@busyjay Yes, I'm proposing a PR to fix this with some tests for default values.


[OOZIE-3590] Fix missing log expression parameters in SLACalculatorMemory

[OOZIE-3590] has been resolved, link is https://issues.apache.org/jira/browse/OOZIE-3590.


False Usage Query Count

Affected module
Ingestion Framework
Describe the bug
The count of queries during usage keeps getting increased after running the usage pipeline even though no queries have been executed.

To Reproduce
run the usage pipeline multiple times and see the count getting increased even though no queries have been actually executed in DB.

@ulixius9 is this done?

we need to start with this yet


updating hail version to 0.2.74 EVERYWHERE for deployment

Updated cluster name
Updated Hail version
Upload jar from maven
Resolved conflicts with master branch


RSocketResumableTransport with RSocketWebSocketClient and spring backend?

Hi, I tried following the example for the ResumableTransport, but subscribing to the connection never hits onComplete. The main difference is that I'm using the RSocketWebSocketClient and a spring backend which means my setup for the client looks like this
	serializers: {
		data: JsonSerializer,
		metadata: IdentitySerializer
	},
	setup: {
		keepAlive: 60000,
		lifetime: 180000,
		dataMimeType: 'application/json',
		metadataMimeType: 'message/x.rsocket.routing.v0',
	},

No errors in server logs or browser console logs.
Thanks!
EDIT: Was poking around rsocket-java issues and found https://github.com/rsocket/rsocket-java/issues/602 which seems to be referring to the same issue. Feel free to close if you feel my post is redundant.

I believe this issue is a duplicate of #49, as routing and composite metadata frames will be covered there. Also, it's not clear from your description which Spring and RSocket Java versions you are using.
If you're using the latest ones, the server should fail while parsing the routing metadata since the client will not be writing it correctly. The routing metadata must be parsed and written in a specific way and the IdentitySerializer won't work here.
Here's a custom serializer you can use in the meantime:
import {
    createBuffer,
    byteLength
} from 'rsocket-core';

/**
 * Serializer for Routing metadata
 * @see https://github.com/rsocket/rsocket/blob/master/Extensions/Routing.md
 */
export class RoutingMetadataSerializer {

    deserialize(data) {
        if (data == null) {
            return null;
        }
        return data.toString('utf8', 1, data.length);
    }

    serialize(data) {
        if (data == null) {
            return null;
        }
        let dataLength = byteLength(data, 'utf8');
        let outBuffer = createBuffer(1 + dataLength);
        outBuffer.writeUInt8(dataLength, 0);
        outBuffer.write(data, 1, data.length, 'utf8');
        return outBuffer;
    }
}

RoutingMetadataSerializer.MIME_TYPE = "message/x.rsocket.routing.v0";
RoutingMetadataSerializer.MIME_TYPE_ID = 0x7E;

Sorry if I wasn't clear enough. I am using spring 2.2m4 so the metadata setup I posted works fine for now.
It works just fine when I give the RSocketClient an RSocketWebSocketClient for the transport. The problem I am facing is when I give the RSocketClient an RSocketResumableTransport that has been supplied with an RSocketWebSocketClient.
The current example rsocketjs provides in packages/examples/ResumeClient is quite different from my use case and I was questioning my config.

@jeisea  rsocket-js needs a new version released - we are hoping to get that done shortly and then it should work with java resumption.

Hi @jeisea  rsocket-js 1.1 has been released. Can you try it and see if it fixes your issue?
https://www.npmjs.com/package/rsocket-core

Hi @robertroeser , I tried upgrading to 0.0.11 today and I think the package that was published might have been missing something.
After my npm install, my app no longer found the rsocket dependencies and when I checked node_modules, rsocket-core and rsocket-websocket-client only contained package.json.
Thanks!

@stevegury do you need to release other packages as well?

@robertroeser @jeisea I released a new version, I think this one should be ok. Apologies for the trouble.

Hello @stevegury . Issue with release still exists. There is a mention here also:
https://github.com/rsocket/rsocket-js/issues/58
Thanks!

@maxim-bandurko-lsvt sorry for the trouble, could you try again with 0.0.16?

@stevegury It worked well, thank you!
Have on more question, there are 2 versions at npm:
https://www.npmjs.com/package/rsocket-websocket-client/v/0.0.16
https://www.npmjs.com/package/rsocket-websocket-client/v/0.1.0-alpha.0ddeeafe
Wanted to check, what version is most recent one? and what differences can be? May be it make sense to start using v0.1.0?

Please use 0.0.16, v0.1.0-alpha is an experimental version based on 0.0.13 codebase.

@stevegury I see. ok, thank you!

@robertroeser I've tried 'message/x.rsocket.routing.v0' with latest release and it works perfect! Thank you!

Thanks!

Thanks!


Proper implementation of ACCESS-OM3 SPD

This now builds and install the OM3 executables and is aware of the different variants.

Apologies on the failing syntax check, it is an issue with the syntax checking action, rather than your code! It should still be fine to merge with approval.

This has successfully been used to install and run OM3 on gadi using the COSIMA spack instance.

Neat!
(This is not a review)

Thanks!


Zod errors from 2.1.0 from 2.0.3

In local dev mode I am seeing the following zod errors
  {
    "code": "invalid_string",
    "validation": {
      "startsWith": "https://"
    },
    "message": "Invalid input: must start with \"https://\"",
    "path": [
      "project",
      "link"
    ]
  }

Is this meant to rule out http://localhost...
With
sidebar: {
      defaultMenuCollapseLevel: 0
    }

I see this zod error
{
    "code": "too_small",
    "minimum": 2,
    "type": "number",
    "inclusive": true,
    "exact": false,
    "message": "Number must be greater than or equal to 2",
    "path": [
      "sidebar",
      "defaultMenuCollapseLevel"
    ]
  }

This is related to
sidebar: z.object({
      defaultMenuCollapseLevel: z.number().min(2).int(),
     ...
    }),

Although, docs state defaultMenuCollapseLevel can be set to 0

I'm using default toc settings (i.e. no toc object), but getting this error. Looks like default docs theme does not populate toc.extraContent
  {
    "code": "custom",
    "message": "Must be React.ReactNode or React.FC",
    "path": [
      "toc",
      "extraContent"
    ]
  }

See my comment https://github.com/shuding/nextra/issues/1210#issuecomment-1374912682

@B2o5T thanks - overlapping opening issues!


Fix unable to Activate inactivated issue in the workplan

Overview
An error occurs when trying to activate an inactivated issue
Steps to reproduce
Go to workplan
Go to Issue tab
Edit an issue by clicking the pen icon in the accordion
Deactivate the issue and hit save
Edit the issue again and activate it
Expectation
The issue should be activated
Actual
An error happens

closing this one becasue it is solved in this ticket:
https://app.zenhub.com/workspaces/epictrack-63891ea941d309001fa292cf/issues/gh/bcgov/epic.track/2258


[WFCORE-591] NPE in revertReloadRequired

Prevent revertReloadRequired (resp. revertRestartReloadRequired) to
throw a NPE if reloadRequired (resp. restartRequired) as not been called
beforehands.
JIRA: https://issues.jboss.org/browse/WFCORE-591

Core - Full Integration Build 625 is now running using a merge of 36645e8d7c8715e5e7c19418daf909ffa6acb0ef

Windows Build 1045 is now running using a merge of 36645e8d7c8715e5e7c19418daf909ffa6acb0ef

Linux Build 1374 is now running using a merge of 36645e8d7c8715e5e7c19418daf909ffa6acb0ef

Linux Build 1374 outcome was SUCCESS using a merge of 36645e8d7c8715e5e7c19418daf909ffa6acb0ef
Summary: Tests passed: 3074, ignored: 64 Build time: 0:18:46

Windows Build 1045 outcome was SUCCESS using a merge of 36645e8d7c8715e5e7c19418daf909ffa6acb0ef
Summary: Tests passed: 3074, ignored: 64 Build time: 0:18:59

Core - Full Integration Build 625 outcome was SUCCESS using a merge of 36645e8d7c8715e5e7c19418daf909ffa6acb0ef
Summary: Tests passed: 2830, ignored: 412 Build time: 0:49:01

I'm tempted to say we should have asserts there, as this sounds like a programming error. But this is fine.


resource group doesn't exits

I'm trying to create monitor with following provider
required_providers {
    betteruptime = {
      source = "BetterStackHQ/better-uptime"
      version = "0.5.1"
    }

terraform version
Terraform v1.7.1
on linux_amd64

error
POST https://betteruptime.com/api/v2/monitors returned 422: {"errors":{"resource_group":["doesn't exist"]}}
resource "betteruptime_monitor" "xx-xx" {

}

Hello @Ashutoshkale, apologies for the late reaction 🙌
I've tried to recreate you config (better-uptime provider in v0.5.1, using a slightly higher version of TF v1.8.0):
terraform {
  required_version = ">= 0.13"
  required_providers {
    betteruptime = {
      source  = "BetterStackHQ/better-uptime"
      version = "0.5.1"
    }
  }
}

resource "betteruptime_monitor" "xx-xx" {

}

With this config BETTERUPTIME_API_TOKEN=XXX terraform apply fails on missing required arguments:
╷
│ Error: Missing required argument
│
│   on main.tf line 11, in resource "betteruptime_monitor" "xx-xx":
│   11: resource "betteruptime_monitor" "xx-xx" {
│
│ The argument "monitor_type" is required, but no definition was found.
╵
╷
│ Error: Missing required argument
│
│   on main.tf line 11, in resource "betteruptime_monitor" "xx-xx":
│   11: resource "betteruptime_monitor" "xx-xx" {
│
│ The argument "url" is required, but no definition was found.
╵

I've added the required arguments:
terraform {
  required_version = ">= 0.13"
  required_providers {
    betteruptime = {
      source  = "BetterStackHQ/better-uptime"
      version = "0.5.1"
    }
  }
}

resource "betteruptime_monitor" "xx-xx" {
  url          = "https://example.com"
  monitor_type = "status"
}

Now, BETTERUPTIME_API_TOKEN=XXX terraform apply  succeeded:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # betteruptime_monitor.xx-xx will be created
  + resource "betteruptime_monitor" "xx-xx" {
      + check_frequency  = 180
      + created_at       = (known after apply)
      + email            = true
      + follow_redirects = true
      + http_method      = "GET"
      + id               = (known after apply)
      + last_checked_at  = (known after apply)
      + monitor_type     = "status"
      + paused_at        = (known after apply)
      + push             = true
      + recovery_period  = 180
      + remember_cookies = true
      + request_timeout  = 30
      + status           = (known after apply)
      + updated_at       = (known after apply)
      + url              = "https://example.com"
      + verify_ssl       = true
    }

Plan: 1 to add, 0 to change, 0 to destroy.
betteruptime_monitor.xx-xx: Creating...
betteruptime_monitor.xx-xx: Creation complete after 1s [id=2320154]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Are you still encountering the issue? Maybe you've omitted part of your configuration which is the reason behind the issue you're mentioning.
Also, I'd recommend to upgrade our provider to v0.10.0 or higher, as there were a few fixes, tweaks and new features added since than 🙌


Bug in Grid .png

Occasionally I notice the grid .png has a bug where it either didn't render the full image and some of it is gray, or the dimensions are wrong.

have not seen this since, closing for now


Docker plugin will not include the built JAR in the image

Hi,
Looks like when we run docker:build the JAR with the app artifacts is not included in the image. Please see this project: https://github.com/jesuino/java-ml-projects/tree/748db8648eeb8ff39b39191b4a01d2bf89e18788
When I build the image I see the content but I can't find image-classifier-microservice,jar in the image directory (I use docker exec to check the image content), hence the image is working perfectly (great plugin, thanks), but my app is not starting.
Checking runt.sh I found the following:
APP_DIR=$ROOT_DIR/app
APP_CP=$APP_DIR/*.jar

Hence I think that a workaround is copy my JAR to target/image-classifier-microservice-bin/app and it works. Hence why I am not opening this on the fabric8 plugin.
Please let me know if I am missing something! I am sorry in advanced if I am doing something n00b 0_0

It’s the mode=thin causing that. It intentionally excludes the app artifact
from the staging dir layout.
If you remove that then your jar will appear in the app directory. In
theory.
On Fri, May 25, 2018 at 10:01 PM William Antônio Siqueira <
<EMAIL_ADDRESS>wrote:

Hi,
Looks like when we run docker:build the JAR with the app artifacts is not
included in the image. Please see this project:
https://github.com/jesuino/java-ml-projects/tree/748db8648eeb8ff39b39191b4a01d2bf89e18788
When I build the image I see the content but I can't find
image-classifier-microservice,jar in the image directory (I use docker exec
to check the image content), hence the image is working perfectly (great
plugin, thanks), but my app is not starting.
Checking runt.sh I found the following:
APP_DIR=$ROOT_DIR/app
APP_CP=$APP_DIR/*.jar
Hence I think that a workaround is copy my JAR to
target/image-classifier-microservice-bin/app and it works. Hence why I am
not opening this on the fabric8 plugin.
Please let me know if I am missing something! I am sorry in advanced if I
am doing something n00b 0_0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thorntail/thorntail/issues/951, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA-T4zQ04u5uz4tZCYedpqnrCXtAMikks5t2LdogaJpZM4UOvYl
.

Thanks, that made it! I knew I was missing something ^_^


Add ability to list relpaths to dtool ls when giving it a dataset

Add ability to list relpaths to dtool ls when giving it a dataset.
This will make it easier to understand what a dataset is.

Fixed in 14d2d70 a6711a2 37ba6e5


Sends message once per second

I am trying to send a message each 100 ms but client accepts only one message per second. I checked my code. There is no sleep code around. What could be the reason?
Thank you.

make sure you call dyad_setNoDelay on your stream to disable nagle's algorithm for your stream.


How to download puppeteer manully?

In china, Most people cannot download the Chromium because of GFW, How to download puppeteer chromium manully and setting properly after download?

https://github.com/GoogleChrome/puppeteer/issues/1597#issuecomment-351945645


[Question] Does a sample client targeting netstandard exist?

I'm wondering whether a netstandard implementation of a websocket client exists. The sample in the current codebase only targets net451.
@Tratcher can you point me in the right direction? Cheers

There wasn't any support for a netstandard client until recently. See https://github.com/dotnet/corefx/blob/d0dc5fc099946adc1035b34a8b1f6042eddb0c75/src/System.Net.WebSockets.Client/src/System/Net/WebSockets/ClientWebSocket.cs

Awesome, thanks for the pointer!

So close, yet so far...
https://github.com/dotnet/corefx/blob/master/src/System.Net.WebSockets.Client/src/System/Net/WebSockets/WebSocketHandle.Unix.cs
@Tratcher do you know whether support on linux will be coming? It's super sad to see a netstandard lib that's not netstandard :(

No idea, that's a question for corefx.


Property * does not exist on type '{}'.

Hi,
I just create a new project with npm create vite@latest and tried to test Volar with Vue 3 for the first time. However, seems like there's something wrong, or I may have done something incorrect.
I have changed the initial Composition API to Options API and created some component and store states. After that, I have these errors

The only thing that doesn't get affected is the setVisibility action.
I'm not sure if this related to Pinia either.
Here's the MRE repo https://github.com/seahindeniz/volar-vue-js-issue
Version: 1.70.0-insider
Commit: 1cd90cceddf3c413673963ab6f154d2ff294b17c
Date: 2022-07-15T05:32:19.076Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.5.0

Had same issue, downgraded Volar to 0.38 to make the error go away.

I didn't want to downgrade, and the only workaround I have found so far was creating the component via defineComponent function.
Here's the commit https://github.com/seahindeniz/volar-vue-js-issue/commit/2618789b5da21d49ba2e04e55fc4cca20dbdc178


add charset(String charset)  in Request

add charset(String charset) method in Request,so can set encode charset to encode request data

Thanks - similar implementation got merged a while back


mypy does not check anything

Hello,
Are you sure that you are invoking mypy correctly?
If i add incorrect types to some function, e.g. def create(     env_dir: int = DEFAULT_ENV_DIR, *, scm_ignore_files: int = frozenset(["git"]) ) -> int: the mypy does not complain.
E.g. mypy . invocation is wrong.
I believe you need to give mypy the files directly because it does not recurse into dirs.

Do have an invocation that shows a different result? I used nox -s lint to make mypy happy when it was raising errors.

If i make the change shown above and run mypy with the affected file argument like this: mypy microvenv/_create.py
i get the following errors:
❯ mypy microvenv/_create.py
microvenv\_create.py:41: error: Missing return statement  [return]
microvenv\_create.py:42: error: Incompatible default for argument "env_dir" (default has type "str", argument has type "int")  [assignment]
microvenv\_create.py:42: error: Incompatible default for argument "scm_ignore_files" (default has type "frozenset[str]", argument has type "int")  [assignment]
microvenv\_create.py:48: error: Argument 1 to "Path" has incompatible type "int"; expected "str | PathLike[str]"  [arg-type]
microvenv\_create.py:81: error: Name "__spec__" is not defined  [name-defined]
microvenv\_create.py:84: error: Name "__spec__" is not defined  [name-defined]
microvenv\_create.py:91: error: No overload variant of "frozenset" matches argument type "int"  [call-overload]
microvenv\_create.py:91: note: Possible overload variants:
microvenv\_create.py:91: note:     def [_T_co] frozenset() -> frozenset[_T_co]
microvenv\_create.py:91: note:     def [_T_co] frozenset(Iterable[_T_co], /) -> frozenset[_T_co]
microvenv\_create.py:95: error: Unsupported operand types for - ("int" and "set[str]")  [operator]
Found 8 errors in 1 file (checked 1 source file)```

Any interest in submitting a PR to fix it?

On second thought it works as expected.
According to https://mypy.readthedocs.io/en/stable/running_mypy.html#how-imports-are-found
mypy prefers .pyi files first.
And if you delete _create.pyi file then your normal invocation mypy . will find the _create.py file and report the error.
I learned something new.


add 'Sample Name' to MIxS core

New term details
For us to assess a new term request we require the following details:
Term name - sample name
Structured comment name - [a less than 20char no spaces version of the name]: sample_name
Definition - [a clear and concise description of the term including ]
   INSDC definition: Sample Name is a name that you choose for the sample. It can have any format, but we suggest that you make it concise, unique and consistent within your lab, and as informative as possible. Every Sample Name from a single Submitter must be unique.

Expected value - [e.g. text or EFO and/or OBI etc...]
Value syntax - [e.g. {float} {unit}|{termLabel} {[termID]}|{text}|{timestamp} etc...]
   {text}
Example - [provide and example value]
Preferred unit - [if appropriate]
Package(s) - [list any packages that should include the new term]
MIxS core

Additional context
Add any other context about the new term here.

AI: add to the core, add to each package for MIXS v6.0

Will sample_name be a mandatory or optional core term in V6?

source material id = intended to be their globally unique identifier
- encourage usage of globally unique identifier
sample name,  yes, make it a mandatory field

could you define what a "sample" means? Does this refer to 1) an physical object (i.e. a piece of tissue or a chunk of soil in a laboratory's freezer or that was destroyed to extract and sequence the DNA), or 2) a digital object resulting from the analysis of a physical object (i.e. the DNA sequences stored on a hard drive)?
I think it is important to distinguish between these things, as DNA can be extracted and sequenced from different subsamples of a physical sample (e.g. a nested design of 'replicates' from an environmental soil sample to look at micro-scale differences bacterial community composition => in this case there are multiple (digital) DNA "samples" related to a single (physical) soil sample). I'm not sure the term sample_name could capture this complexity and may cause confusion when confronted with such cases...
Would it be a solution to do something in the line of dwc:event/dwc:eventID (http://rs.tdwg.org/dwc/terms/Event) and dwc:parentEventID (http://rs.tdwg.org/dwc/terms/parentEventID) in DarwinCore?
There, an "event" (e.g. a sampling campaign, environmental sample or DNA sequences from the bacterial community in that environmental sample) can be embedded in a parent event. Each parent event can in turn be listed as an event with it's own parent event. For example the DNA sequences (event A1) can come from an environmental soil sample (S1) collected during a campaign (C1), the relation between these events would then be C1:S1:A1.

added to MIxS core, checklists and packages

@ramonawalls , I have updated the definition in the all Tabs of the spreadsheet as per your suggestion above, using the find and replace all option in google-sheets, it said it did 26 replacements in total.


[Not bug, but Enhancement]Rename Machine won't change the name's record in [nodes ls]

I changed my kali(ID:2) to pi.
It says success and it was changed in my clients.
But it is still the old name in headscale's command output.

I noticed there is a given_name in DB, so why not make it list in the output of cli?

Observe same issue, it's pretty confusing, I'd suggest add a Hostname column in the nodes ls outputs.
And the mapping is:
machine.Name -> Hostname
machine.GivenName -> Name
I've implemented this enhancement, @kradalby if you think this is ok, I can open a PR

Yes please

@huskyii we are very much looking for the PR :)


added CCS <-> 1/k0 conversion functions to CompassData interface an…

…d implemented them in TimsData; SpectrumList_Bruker::ionMobilityToCCS/ccsToIonMobility return the value from the vendor API but throws an exception if the value doesn't match the value from the builtin calculation
@bspratt DLLs not yet included (they're prerelease AFAIK), so I'll need to send updated 7z file separately.

Can we revive this PR and get it to the point that it can be merged?

@bspratt You think we should strip out the built-in calculation and validation logic?

Maybe retain for test purposes to detect any shifts in the DLL behavior,
but otherwise yeah, let's be clear on where that calculation is formally
implemented.
On Wed, Jul 1, 2020 at 10:40 AM Matt Chambers<EMAIL_ADDRESS>wrote:

@bspratt https://github.com/bspratt You think we should strip out the
built-in calculation and validation logic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/871#issuecomment-652556446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJFE6PLMUEOMQAZHAQMY3TRZNYHVANCNFSM4KJYPLBA
.


PVC not working with K3S

Describe the bug
Pods using PVCs are not starting.
To Reproduce
Do a kubectl apply -f busypvc.yaml where busypvc.yaml is:
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: busyboxpv
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: busyboxpv
spec:
  selector:
    matchLabels:
      app: busyboxpv
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: busyboxpv
    spec:
      containers:
      - image: busybox
        name: busyboxpv
        command: ["sleep", "60000"]
        volumeMounts:
        - name: busyboxpv
          mountPath: /mnt
      volumes:
      - name: busyboxpv
        persistentVolumeClaim:
          claimName: busyboxpv

With another cluster, it takes 10s to have a running busybox container, but here it is in a pending state forever:
/ # kubectl get pods
NAME                                                    READY   STATUS     RESTARTS   AGE
busyboxpv-77665c79f4-f2fhp                              0/1     Pending    0          3m44s

A describe over the pvc give:
/ # kubectl describe pvc busyboxpv
Name:          busyboxpv
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        <none>
Annotations:   kubectl.kubernetes.io/last-applied-configuration:
                 {"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{},"name":"busyboxpv","namespace":"default"},"spec":{"accessMo...
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Events:
  Type       Reason         Age                  From                         Message
  ----       ------         ----                 ----                         -------
  Normal     FailedBinding  9s (x19 over 4m20s)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set
Mounted By:  busyboxpv-77665c79f4-f2fhp

Expected behavior
That the busybox pod is running with the defined pvc mounted.

Has a StorageClass been set up?

You must add storage class before create pvc, k3s is support storage class like ceph, heketi ???
i don`t know it, it need be test...  I will do it.

@ibuildthecloud yeah I tried that local-storage class this morning, could not get it to work...

@ibuildthecloud, I was able to confirm that it works using the local-path storageClass. After following the installation instructions in the README.md, I tested it by passing it this and it worked; I have a running SonarQube instance up now:
helm install --name mytest2 stable/sonarqube --set=postgresql.persistence.storageClass=local-path,persistence.storageClass=local-path

Both my helm and k3s were installed via the provided "curl-pipe-to-bash" scripts in the quick-start instructions for each tool.
I also followed Rancher instructions for setting up Tiller after installing Helm:
https://rancher.com/docs/rancher/v2.x/en/installation/ha/helm-init/
Additionally, I symlinked the rancher kube config install location over to the default location at: ~/.kube/config just in case. It seemed to have trouble finding it early on in my testing.
Here is my Helm version:
helm version
Client: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}

I am running PopOS (System76's Ubuntu 18.04 spin) with kernel version 4.18.0-15-generic.
Recommend shipping updating the docs to prescribe the use of the custom storageClass for persistent volumes, and maybe creating some flags in the curl-pipe-to-bash installation script that afford the user the option to install Helm and the local-path storageClass separately to keep the binary tiny.
An Ansible playbook/role that performs the installation of both k3s plus some common ancillary tools might not be a bad idea either. Just so people aren't fighting with it to get a hello world app running.

I can't also use PVCs using StorageOS:
I've installed the StorageOS control plane following the guide at https://docs.storageos.com/docs/platforms/kubernetes/install/1.13 and NOT using helm. It seems that the pods are correctly running:
kubectl get pods --all-namespaces
NAMESPACE            NAME                                        READY   STATUS      RESTARTS   AGE
default              d1                                          0/1     Pending     0          24m
default              ds4m-0                                      1/1     Running     0          29m
kube-system          coredns-7748f7f6df-lxpxx                    1/1     Running     0          29m
kube-system          helm-install-traefik-gkjr7                  0/1     Completed   0          29m
kube-system          svclb-traefik-55f697fb45-dhbb2              2/2     Running     0          29m
kube-system          svclb-traefik-55f697fb45-jpm5j              2/2     Running     1          29m
kube-system          traefik-6876857645-z4glc                    1/1     Running     0          29m
storageos-operator   storageoscluster-operator-64cbc948b-4867v   1/1     Running     0          27m
storageos            storageos-daemonset-bz4gd                   1/1     Running     0          26m
storageos            storageos-daemonset-d52fc                   1/1     Running     0          26m

Then I've created a Secret and a Cluster. Now to test it, I went to https://docs.storageos.com/docs/platforms/kubernetes/firstvolume/ to deploy my first volume and pod but it can't get the persistent volume created:
# kubectl describe pod d1
Name:               d1
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               <none>
Labels:             <none>
Annotations:        <none>
Status:             Pending
IP:
Containers:
  debian:
    Image:      debian:9-slim
    Port:       <none>
    Host Port:  <none>
    Command:
      /bin/sleep
    Args:
      3600
    Environment:  <none>
    Mounts:
      /mnt from v1 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-j5n7q (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  v1:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  pvc-1
    ReadOnly:   false
  default-token-j5n7q:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-j5n7q
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  106s (x32 over 27m)  default-scheduler  pod has unbound immediate PersistentVolumeClaims (repeated 2 times)

Looking at the Persistent Volume Claim, there is an error there:
kubectl describe pvc pvc-1
Name:          pvc-1
Namespace:     default
StorageClass:  fast
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-class: fast
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Events:
  Type       Reason              Age                  From                         Message
  ----       ------              ----                 ----                         -------
  Warning    ProvisioningFailed  2m2s (x19 over 28m)  persistentvolume-controller  no volume plugin matched

The StorageClass fast seems to be created correctly:
kubectl describe storageclass fast
Name:                  fast
IsDefaultClass:        No
Annotations:           <none>
Provisioner:           kubernetes.io/storageos
Parameters:            adminSecretName=storageos-api,adminSecretNamespace=default,fsType=ext4,pool=default
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

The StorageOS cluster seems to be running correctly too:
# kubectl describe storageoscluster example-storageos
Name:         example-storageos
Namespace:    default
Labels:       <none>
Annotations:  <none>
API Version:  storageos.com/v1alpha1
Kind:         StorageOSCluster
Metadata:
  Creation Timestamp:  2019-03-05T17:44:24Z
  Generation:          32
  Resource Version:    1426
  Self Link:           /apis/storageos.com/v1alpha1/namespaces/default/storageosclusters/example-storageos
  UID:                 50ae68d2-3f6e-11e9-ab2e-22738ce9a901
Spec:
  Csi:
    Device Dir:
    Driver Registeration Mode:
    Driver Requires Attachment:
    Enable:                           false
    Enable Controller Publish Creds:  false
    Enable Node Publish Creds:        false
    Enable Provision Creds:           false
    Endpoint:
    Kubelet Dir:
    Kubelet Registration Path:
    Plugin Dir:
    Registrar Socket Dir:
    Registration Dir:
    Version:
  Debug:                              false
  Disable Telemetry:                  false
  Images:
    Csi Cluster Driver Registrar Container:
    Csi External Attacher Container:
    Csi External Provisioner Container:
    Csi Liveness Probe Container:
    Csi Node Driver Registrar Container:
    Init Container:                          storageos/init:0.1
    Node Container:                          storageos/node:1.1.3
  Ingress:
    Annotations:  <nil>
    Enable:       false
    Hostname:
    Tls:          false
  Join:           <edited_ip>,<edited_ip>
  Kv Backend:
    Address:
    Backend:
  Namespace:            storageos
  Node Selector Terms:  <nil>
  Pause:                false
  Resources:
  Secret Ref Name:       storageos-api
  Secret Ref Namespace:  default
  Service:
    Annotations:    <nil>
    External Port:  5705
    Internal Port:  5705
    Name:           storageos
    Type:           ClusterIP
  Shared Dir:
  Tolerations:      <nil>
Status:
  Node Health Status:
    <edited_ip>:
      Directfs Initiator:  alive
      Director:            alive
      Kv:                  alive
      Kv Write:            alive
      Nats:                alive
      Presentation:        alive
      Rdb:                 alive
    <edited_ip>:
      Directfs Initiator:  alive
      Director:            alive
      Kv:                  alive
      Kv Write:            alive
      Nats:                alive
      Presentation:        alive
      Rdb:                 alive
  Nodes:
    <edited_ip>
    <edited_ip>
  Phase:  Running
  Ready:  2/2
Events:
  Type     Reason         Age   From                       Message
  ----     ------         ----  ----                       -------
  Warning  ChangedStatus  31m   storageoscluster-operator  0/2 StorageOS nodes are functional
  Warning  ChangedStatus  30m   storageoscluster-operator  1/2 StorageOS nodes are functional
  Normal   ChangedStatus  30m   storageoscluster-operator  2/2 StorageOS nodes are functional. Cluster healthy

I've edited my IPs but they are correctly set to my master and slave.
Is there something extra that needs to be done in order to enable Persistent Volumes in k3s? I tried the same example in a kubernetes cluster installed through kubeadm and it works but since it contains lots of components extra I don't know if there is anyone missing here.

I can confirm PVCs work with the localPath provisioner as described above, following the instructions in the corresponding Readme works just fine. For very small deployments, this may be all you ever need (it is for me).
As long as this another solution isn't included and enabled by default, could this be mentioned in the k3s Readme, at least in brief? I'd envision lots of people will be hitting this particular obstacle.

Hey guys, I was able to create dynamic pv/pvc in my k3s using external-storage (https://github.com/kubernetes-incubator/external-storage/tree/master/nfs), I ran the tests with helm install --name my-release stable/consul, but I got an issue when I tried to restart my k3s cluster, like docker-compose down, my nodes stuck in finishing state, so I had to restart docker service. Does anybody had some advance about this ?

I can confirm PVCs work with the localPath provisioner as described above

Not on Arm64 it doesn't.  The local-path-provisioner pod reports "exec format error".

local-path-provisioner doesn't work for me because it isn't built for ARM

I was able to get the local provisioner working. It'd be great if it enabled by default.

Create directory that's needed by local provisioner: sudo mkdir /opt/local-path-provisioner
Install local provisioner: kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/deploy/local-path-storage.yaml
Set the local provisioner as default: kubectl patch storageclass local-path -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

Just adding my 2 cents. I was able to get my PVC's working using NFS (required for my specific case). I have followed https://github.com/kubernetes-incubator/external-storage/tree/master/nfs and even after doing all the steps I was still getting errors when bounding. The solution was to install nfs-commons on my Ubuntu 18.04 nodes.    "sudo apt-get install nfs-common" .

@saturnism I can confirm it works for busypvc.yaml, but step1 one was not necessary for me...

@optimuspaul I have an updated branch of local-path-provisioner that builds binaries for multiple arch and a multi-arch docker image in https://github.com/rancher/local-path-provisioner/pull/24
I have a pv+pvc working on armv7l using the helm chart to deploy the StorageClass, with a custom image name:
-        image: rancher/local-path-provisioner:v0.0.9
+        image: tamsky/local-path-provisioner:562d008-dirty

at: https://github.com/rancher/local-path-provisioner/blob/master/deploy/local-path-storage.yaml#L63
Feedback solicited.

Any recommendations on what to use if "ReadWriteMany" is required? This doesn't seem to support that access mode.

I got Rook working rather well on k3s, but it was too RAM-hungry for my RPi3B cluster 😬

@jbhannah How did you manage to get it working? Did you use the standard installation method?

@jose-sanchezm Yeah, it was largely a standard install via helm template. I did have to wait until the OSDs were created before the blockpool, otherwise the blockpool wouldn't initialize, but that may have been more a matter of horsepower than anything to do with k3s.

Still the same in release v0.9.1, let's hope the next release will fix it...

FWIW, I am able to successfully run rook-ceph in a k3s-provisioned cluster (0.9.1).  It may be related to setting the proper CSI path and installing rook using CSI instead of flexvolume (CSI is now the default in rook v0.9.x +):
csi.kubeletDirPath: /var/lib/rancher/k3s/agent/kubelet
See https://github.com/billimek/k8s-gitops/blob/master/rook-ceph/chart/rook-ceph-chart.yaml#L15-L17 for context.

Related: https://github.com/rancher/k3s/issues/840

with k3s v0.10.0-rc1, we have pvc working using local-path
# k get pods -A|grep busybox
default       busyboxpv-69f6d7dd5d-wlw28                1/1     Running     0          50m
# k get storageclass
NAME                   PROVISIONER             AGE
local-path (default)   rancher.io/local-path   83m
# k get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM               STORAGECLASS   REASON   AGE
pvc-e62f84c4-75f4-45b4-8472-3044acc66e30   10Mi       RWO            Delete           Bound    default/busyboxpv   local-path              50m
# k get pvc
NAME        STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
busyboxpv   Bound    pvc-e62f84c4-75f4-45b4-8472-3044acc66e30   10Mi       RWO            local-path     51m

does K3S support readwritemany if so how to enable it ..???
is there any way to do it ?

It does if the volume driver does... there's nothing special about K3s's storage support.


Travis PR build has been failing lately

On our PRs, we have not had a single full green build lately. In particular, the Travis "PR" job errors, while the "Push" job is fine. (Note that the Push build actually runs on Sauce, so we are still okay on older browsers).
The builds show the following error:
$ node ./node_modules/.bin/polymer test --npm --module-resolution=node -l firefox
Installing and starting Selenium server for local browsers
Selenium server running on port 42773
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
firefox 61               Beginning tests via http://localhost:8081/components/@polymer/polymer/generated-index.html?cli_browser_id=0
firefox 61               Tests failed: Timed out
firefox 61               Failed to quit: {"message":"[quit()] Error response status: 33 Selenium error: Tried to run command without establishing a connection\nBuild info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T15:15:08.936Z'\nSystem info: host: 'travis-job-polymer-polymer-418334737', ip: '<IP_ADDRESS>', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.12-041412-generic', java.version: '1.8.0_151'\nDriver info: driver.version: unknown","status":33,"cause":{"sessionId":null,"state":"session not created","hCode":188...
Test run ended in failure: Timed out
firefox 61 (113/0/0 error)
Error: Timed out
error: [cli.main]   cli runtime exception: Error: Timed out
error: [cli.main]   Error: Timed out
    at /home/travis/build/Polymer/polymer/node_modules/polymer-cli/node_modules/web-component-tester/runner/steps.js:170:27
    at Generator.next (<anonymous>)
    at fulfilled (/home/travis/build/Polymer/polymer/node_modules/polymer-cli/node_modules/web-component-tester/runner/steps.js:4:58)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:182:7)
The command "node ./node_modules/.bin/polymer test --npm --module-resolution=node -l firefox"

We have been manually restarting these builds, to get over this Firefox hickup. Chrome seems to be working just fine.
To limit the chance that Selenium fails twice in a row, could we maybe run Chrome and Firefox with the same command again? E.g. node ./node_modules/.bin/polymer test --npm --module-resolution=node -l firefox -l chrome

It always seems to be around test 100 +/- 10 or so... Haven't gotten it to timeout locally like that.


upgrade guava to 27.0.1

closes #1120

Also fixes #1167 (which was opened to replace #1120 which was closed as stale)


Merge pull request #1 from tensorflow/master

pull all without selection

Can one of the admins verify this patch?

pull


Return value for column ordering from REST API inconsistent: "asc"/"desc" vs "ASC"/"DESC"

Looks like "order" property of ClusteringExpression returned when requesting Table definition (via Stargate REST v1 or v2 API) is defined and used inconsistently.
Documentation in general (and for ClusteringExpression in particular) claims lower-case values ("asc", "desc") to be used, but implementation and (some of the) integration tests seem to produce/expect upper-case variants ("ASC", "DESC"). Implementation seems to be due to Stargate internal schema enum type Column.Orderdefining valuesASCandDESC`; this gets converted to a String and returned.
I am not sure what is the correct change here: since upper-case values are actually used I am guessing it is better to change the documentation to match implementation?

Looks like documented values are upper-case, but case-insensitive usage is implemented. Will close for now; may be re-surfaces as part of bigger documentation upgrade if need be.


Strange behavior of sol::overload

Hey. I want to bind a set of overloaded c++ methods to a set of overloaded lua methods.
However, running this code yields in some kind of permaloop and the program has to be shut down.
struct TestMe
{
    void print(int i) { std::cout << "Integer print: " << i << std::endl; }
    void print() { std::cout << "No param print." << std::endl; }
};

int main()
{
    auto test = std::make_unique<TestMe>();
    sol::state lua;
    lua.new_usertype<TestMe>("TestMe", sol::constructors<>(),
                              "print", sol::overload(static_cast<void (TestMe::*)(int)>(&TestMe::print),
                                                     static_cast<void (TestMe::*)()>(&TestMe::print)));
    lua.set("test", std::move(test));

    sol::protected_function protFunc = lua.load("test:print()");
    auto res = protFunc();
    if(!res.valid())
    {
        sol::error err = res;
        std::cout << "Something went wrong in the execution of a script!" << std::endl << "What: " << err.what() << std::endl;
    }

    return 0;
}

Note that you can swap the arguments in sol::overload and it works fine:
    lua.new_usertype<TestMe>("TestMe", sol::constructors<>(),
                              "print", sol::overload(static_cast<void (TestMe::*)()>(&TestMe::print),
                                                     static_cast<void (TestMe::*)(int)>(&TestMe::print)));

Is there a 'order restriction' when using sol:overload? It seems like sol dont like it when methods with no param are registered after methods with one or more param.

No repro with lua 5.3.2/5.3.3 and VC++. Which compiler, platform, build flags, etc...

Gcc 5.3, Win7 64bit, occurs even with -std=c++14 only.

Found the bug that's causing it to not find the right function, but I haven't gotten it to go into an infinite loop, ordered in any way. Will have to try with MinGW sometime.

Well I cant describe it better then that: Program simply does not terminate when encountering this issue. Just displaying empty terminal. What is your output? An error? Just false print call? I have the feeling that generally calling a (member-) method with wrong argument count in lua - not especially overloaded ones - triggers that behavior for me. So it seems like that "infinite-loop" does not directly related to the overload issue and is more a "function with wrong argument number called"-thing.
Basically your bugfix should at least fix my permaloop in this situation.

@Ung0d Give it a go now with the latest commit, you should be all set.


HOW TO DRAG HOT-SPOT

how to drag hotspot,
All I need to drag the hotspot from one place to another, just like we drag the icon in google-map
I did this seeing this --> https://github.com/mpetroff/pannellum/issues/1163
but it didn't work.
My code is:
    var newHotspot = {
      id: currenHSiD,
      pitch: pitch,
      yaw: yaw,
      cssClass: "custom-hotspot",
      createTooltipFunc: addTagHotspot,
      // createTooltipArgs: "New Hotspot",
      createTooltipArgs: {
        pitch, yaw, currenHSiD
      },
      isAddInfoEnable: true,
      dragHandlerFunc : dragHandlerFunc,
      dragHandlerArgs : {id: 0}
    };
    if(previousHSiD){
      viewer.removeHotSpot(previousHSiD);
    }

    // Add hotspot
    viewer.addHotSpot(newHotspot);

   function dragHandlerFunc(e, args, hs) {
    alert()
    console.log("mouseupmouseup >>", args.id, hs.yaw, hs.pitch);
    if (e.type == "mouseup") {
        // Here I can update the hotSpot in my database by using args.id and hs.yaw, hs.pitch for the new position
    }

    <div
      className="panorama"
      ref={panoramaRef}
      onMouseDown={handleMouseDown}
      onMouseUp={handleMouseUp}
      draggable= {true}
    ></div>

here's function dragHandlerFunc didn't get a call

You're referencing the dragHandlerFunc function in the newHotspot object before you define the function. You can't reference something you haven't yet defined.

Ok got it


Build CI/CD pipeline

This task is for creating a basic build CI/CD pipeline for this project on Eclipse infrastructure. More information is here: https://ci.eclipse.org/.

Jobs:

master branch: https://jenkins.eclipse.org/jaxws/job/saaj-api-master-build/
EE4J_8 branch: https://jenkins.eclipse.org/jaxb/job/jaxb-api-ee4j8-build/
Both are passing.


Suggestion: show sequential init container logs first, then pod logs

Currently the logs from all containers + init containers are mashed together.
We know that init containers were run before main containers, and we know that init containers were run sequentially.
Would it make sense for stern to look up the init container names, their sequence, and show those logs first; and then show normal containers' logs mashed together?

I assume this is for retrospective logs? As the natural order of operations for realtime monitoring tends to show in this order since that's the order things run in

Or pods who are running, or some init containers have completed.
Dr Nic Williams
Stark & Wayne LLC
http://starkandwayne.com
+61 437 276 076
twitter @drnic


Could you add the termcolors for two-firewatch-dark?

Or point me to a place where I can find them? Thank you

Hi @synergistics,
Thanks for opening the issue, but can you be a little bit more specific as this can be understand in a plenty of different ways, are you looking for:

iTerm2 theme, if that's the case this repo contains the two themes that I'm using (under the term folder)
Native Mac Terminal theme, I haven't looked at that yet as I'm not using this app that often
Adding 16 or 256 colors support to the theme itself, I'm currently looking at ways to improve the maintenance of this colorscheme and add a more accurate approximation for terminals that do not support true color.

Thanks for your reply.

Oh, I meant the .itermcolors file for two-firewatch-dark. The file for firewatch light is in the term folder but the itermcolors for the dark version are not there.

OK got it, for the dark version I'm currently using one-dark.itermcolors that you'll find in my repo.
I did not took the time to create a specific version to match the colorscheme, but it is in my todo.


Fix provider.region in serverless.yml and pin serverless version.

Fixes issue encountered in https://github.com/covid-projections/covid-data-model/runs/8100141218?check_suite_focus=true
It seems like serverless v3 broke us.  I fixed one issue, but hit a different issue, so I'm pinning at 2.72.3.

Ah interesting, pinning the serverless version sounds good to me!
thanks for digging into this 🙏 🙏


cannot access org.kordamp.ikonli.Ikon   class file for org.kordamp.ikonli.Ikon not found

Hey @aalmiray, What is missing here ?

Did you include the ikonli-core dependency?

Ah, it was like it resolved it already but I overlooked it.
I've needed 4 dependencies;
        <dependency>
            <groupId>org.kordamp.jipsy</groupId>
            <artifactId>jipsy</artifactId>
            <version>0.4.0</version>
        </dependency>
        <dependency>
            <groupId>org.kordamp.ikonli</groupId>
            <artifactId>ikonli-core</artifactId>
            <version>1.7.0</version>
        </dependency>
        <dependency>
            <groupId>org.kordamp.ikonli</groupId>
            <artifactId>ikonli-javafx</artifactId>
            <version>1.7.0</version>
        </dependency>
        <dependency>
            <groupId>org.kordamp.ikonli</groupId>
            <artifactId>ikonli-fontawesome-pack</artifactId>
            <version>1.7.0</version>
        </dependency>

What do you think to resolve some of them transitively ?
Thank you!

AFAIK ikonli-javafx pulls in ikonli-core as a transitive dependency. jipsy is only needed if you intend to build your own icon packs. Icon packs OTOH only pull in ikonli-core as they do not target an specific UI toolkit such as swing or javafx.
I'm a bit surprised that the transitive dependencies did not work, I haven't encountered a problem when defining just ikonli-javafx and an icon pack with Gradle.

Aha! I think I see where the problem lies, ikonli-javafx defines the following dependency
<dependencies>
  <dependency>
    <groupId>org.kordamp.ikonli</groupId>
    <artifactId>ikonli-core</artifactId>
    <version>1.7.0</version>
    <scope>runtime</scope>
  </dependency>
</dependencies>

Notice the usage of runtime scope. This is a side effect of the default POM marshalling that the maven-publish Gradle plugin applies to a POM file.

I suppose it is because ikonli-core's scope is runtime and Ikon class is needed at compile time, at least in maven.

Yup, the fix is to publish new POMs that do not have runtime scope.

Thank you! In addition ikonli works without jipsy dependency, FYI.

Indeed, jipsy is a compile only dependency. In Maven speak it's in provided scope.

:+1:


Bump go version to 1.20

ref: https://github.com/kubesphere/kse/pull/878
/cc @wansir

/lgtm
/approve


CLI support

What do you think?
hi from python slack chat!

Hi! =)
I think it's a great idea. And the CLI is implemented in the dev version.

pip install -U git+https://github.com/constverum/ProxyBroker.git@dev
proxybroker -h


[tasks/pipeline] Change usage example: remove obsolete 'pipeline.run …

What does this PR do?
Change usage example of tasks/pipeline

Motivation
Command
% inv --help=pipeline.run
shows output:
...
Run a pipeline without kitchen tests on the current branch:
inv pipeline.run --here --no-kitchen-tests
...
When trying to run it:
% inv pipeline.run --here --no-kitchen-tests
No idea what '--no-kitchen-tests' is!
Option --no-kitchen-tests is obsolete.
Another available option --no-kmt-tests does not appear in usage example.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


About the model size

Hi, thanks for your cool work!
The released resnet18 checkpoint ' resnet18_imagenet_aux_best.pth.tar' has a size of about 452M, which is much larger than the original one (44.7M). What is the difference between them?
Thanks!

Thanks for your attention! The original resnet18 checkpoint (44.7M) is downloaded from the official torchvision lib corresponding to the original ResNet-18 architecture. Our released 'resnet18_imagenet_aux_best.pth.tar' contains the weights of our training graph including the original ResNet-18 and its auxiliary branches.


[doc] Architecture diagram

Trying to get an overlook of the whole picture.
This is not intended to stay in this readme, we can move it, but I would like to use this PR as a way to discuss how to represent the architecture.

Fyi there is also a discussion board for discussing such items.
Is the intention to show how the different Open-RMF packages are used? What do the arrows signify?


text module does not implemented ?

Windows 10 x64
installation via chocolatey.
OpenCV version: 0.60.0
rustc version (rustc --version): 1.56.1

are Module opencv::text not implemented ? I'm trying to use ocr functions but I can't access the text module which are written in rust docs.

The OpenCV version from chocolately doesn't contain the "text" module, so that's why. You should either install OpenCV from vcpkg or build it manually.


How to UnitTest a FutureProvider.autoDispose()?

Describe what scenario you think is uncovered by the existing examples/articles
I successfully tested my FutureProvider adapting this code from riverpod.de
test('override repositoryProvider', () async {
  final container = ProviderContainer(
    overrides: [
      // Override the behavior of repositoryProvider to return
      // FakeRepository instead of Repository.
      repositoryProvider.overrideWithProvider(Provider((ref) => FakeRepository()))
      // We do not have to override `todoListProvider`, it will automatically
      // use the overriden repositoryProvider
    ],
  );

  // The first read if the loading state
  expect(
    container.read(todoListProvider),
    const AsyncValue<List<Todo>>.loading(),
  );

  /// Wait for the request to finish
  await Future<void>.value();

  // Exposes the data fetched
  expect(container.read(todoListProvider).data.value, [
    isA<Todo>()
        .having((s) => s.id, 'id', '42')
        .having((s) => s.label, 'label', 'Hello world')
        .having((s) => s.completed, 'completed', false),
  ]);
});

In my case, it looks like this:
test('contactProvider should provide Contact for id', () async {
    final loading = container.read(contactProvider(42));
    expect(loading, const AsyncValue<Contact>.loading());
    await Future<void>.value();
    final contact = container.read(contactProvider(42)).data.value;
    expect(contact, isNotNull);
    expect(contact.id, 42);
    expect(contact.name, 'contact-name-42');
});

However, since the contact with the id ultimately comes from a db, I don't want to cache the result. When I modify my provider with autodispose, the test fails with NoSuchMethodError: The getter 'value' was called on null.
3 hours of googling and stackoverflowing and experimenting were unsuccessful.

Your "await" isn't actually waiting for the future to complete.
Since this provider is an autoDispose, the provider was destroyed during the "await" because there are no listeners.  So the second container.read creates a new future, which wasn't awaited.
Similarly, you may want to read provider.future as it is more adapted to "awaiting" the completion
Do:
FutureProvider provider;

final container = ProviderContainer(...);

// as opposed to "read", this will keep the provider alive until the subscription is closed
final subscription = container.listen(provider);

await expectLater(
  subscription.read(),
  completion(
    isA<Contact>()
      .having((c) => c.id, 'id', 42)
      .having((c) => c.name, 'name', 'contact-name-42')
  ),
);

Thank you very much for your fast reply. As far as I am concerned this answers my question perfectly.
I am unsure whether I can / should close this issue or whether you want to keep it open as a reminder to perhaps enhance the documentation.
Have a good start into the New Year :)

Thank you very much for your fast reply. As far as I am concerned this answers my question perfectly.
I am unsure whether I can / should close this issue or whether you want to keep it open as a reminder to perhaps enhance the documentation.
Have a good start into the New Year :)

Done in 5eceb2b934d3ba6b5783df284be7213a131e2e7b


1.3.3 not released to Clojars

I want to use version 1.3.3 for the STS feature (thanks!), but it isn't released on Clojars yet. I'm fetching it via -SNAPSHOT now ([s3-wagon-private "1.3.3-20190626.232501-1"] to be precise)

I've just released 1.3.3 now. Thanks!


atom considers my fr-layout as an us/en one for keybinds

Prerequisites
Using archlinux 4.8.11
fr-layout
Atom : 1.12.7
Electron : 1.4.12
Chrome : 53.0.2785.143
Node : 6.5.0
Description
Atom seems to use an en/us layout for keybinds, ctrl+q acts like ctrl+a and vice-versa, same for ctrl+w/z
That has been like this for 1 or 2 updates.
Steps to Reproduce

use a fr layout ?

feel free to ask me anything.
Regards,
Piczel

Electron : 1.4.12

Thanks for reaching out!
We've determined that this issue is being caused by the use of an unofficial build or distribution of Atom. Often these customized versions of Atom are modified versions of the Stable branch of Atom with mismatched versions of built-in components. These updated components are taken from the Beta channel or master branch and then injected into the Stable version and a new Atom package is generated. Because of the way Atom is constructed, using these mismatched components can cause mysterious and hard-to-diagnose problems. You can find out more about why we chose to not support unofficial distributions here.
You may want to subscribe to https://bugs.archlinux.org/task/50357 for updates.

Same goes for me, from webupd8 repo, guess it's the same issue here !


How to connect with user credentials??

I have tried:
var db = mongojs("username:password@mydomain.com:8080/dbname", []);
but did not work.

Is this still a problem? What error do you get? What exactly means "not working"?


Why multipart.DataFields use map[string]string to contain the request form?

Normally, a form key only  has single value, but it's also right with multiple values .
Why not use url.Values ?

If we use Body or BodyString method to make 1:n key-value pair, we need define the proper Content-Type header representing the real content MIME type.

Clearly, this is an interface limitation. It should be map[string][]string, such as url.Values:
https://golang.org/pkg/net/url/#Values
If you want a fast fix, would you mind providing a PR? I will merge it asap!

I'm still reviewing and testing the code. I will try to contribute code later.

I had a few time tonight to fix this. See: https://github.com/h2non/gentleman/commit/b8321b809b88815e5d58c56cc0fdf376f84f0640
The fix will be shipped in<EMAIL_ADDRESS>soon.

Fix was shipped in<EMAIL_ADDRESS>You can upgrade it running:
go get -u gopkg.in/h2non/gentleman.v1


[request]: Migrate to Rust 2021 edition

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Tell us about your request
Migrate to Rust 2021 edition.
Looks lots of examples works under 2021 edition now.
Tell us about the problem you're trying to solve.
modernize.
Are you currently working around this issue?
Yes.
Additional context
No response

Hey @overheat, this isn't currently a high-priority issue for us and we don't expect to get to it soon but we encourage you to submit a PR if this is important to you.

I had some free time and implemented this in smithy-rs#1268. It'll go out in the next release

released in v0.10.1


post*Handlers are not invoked for google (and likely for linkedin)

handlers are retrieved from the application, but there is no trace of them being ever set Let's get them from the config.

Thanks for the PR! Looks great, merging in now.


Failed to modify StatefulSet

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
I tried to deploy the MariaDB chart from the Rancher Library with my self signed SSL certificates. But I failed to mount the certificates into the pod in the Rancher UI.
Steps to reproduce:

Deploy MariaDB from Rancher library
Got To Catalog Apps and click on MariaDB
Edit Workload (MariaDB Master)
Add new mount from secrets source
Click on save and get following error

Validation failed in API: StatefulSet.apps "maria-mariadb" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
If I do the same via "Edit YAML", and configure the secret mount manually it works like expected. The volume is part of the template field. So I guess the validation is wrong or Rancher modifies more than just the volume part.
Environment information

Rancher version 2.1.3

I guess it's because of the k8s design. The statefulset can only be upgraded  in several limited areas such as containers and replicas.  Edit the yaml meas redeploy i think.
Please see the source code.

Of course, this is what the validation error says. Only following fields can be updated:

Replicas
Template
UpdateStrategy

But if I add a secret volume mount, this should only affect the template.containers.volumeMounts.* and the template.spec.volume.* field, right?
If I modify these values directly in the YAML file, the workload is upgraded as expected.

Close in favor of https://github.com/rancher/rancher/issues/17283


Communication microservice authentication and encryption

We need to implement authentication and encryption for the browser to mobile communication protocol. This should be done using the public-private keys of their account
Authentication could be: DIDComm, VCs, simple challenge request, JWT
Definition of done
this

[ ] Message sent from website to mobile is Authorised by the private key in browser, and encrypted with the public key from the Tonomy ID public key
[ ] messages are sent from Tonomy ID mobile app are authorised with the private key from the mobile app, and encrypted with the public key from the browser

check this first:
https://github.com/Tonomy-Foundation/Tonomy-ID-Management/issues/104

lets do authentication only for now

a task needed for writing more integration tests and unit tests

there is a know bug about the logging into the microservice and expected to be fixed in task #464
the logging in sometimes doesnt happen correctly or slower then sending a message

a task need to be added to add the verify guard to the socketGateway in the  communication service:

the microserviice now doesn't check if each message is verified and it needs to check it there is an auth guard ready to be used