Update our MEP infrastructure and documentation to reflect the MEP process

In our organization team compass we have the description of the MEP process that we currently follow. This is different than the process that is documented here. As we are getting close to having some MEPs merged I think we should update our docs here to reflect the new process.
Suggestions to act on:

start this repo's commit history from scratch since the current MEP structure is much shorter
copy paste the text at https://compass.executablebooks.org/en/latest/meps.html into a landing page with a brief overview of what MEPs are
Set up the proper folder infrastructure to make our current MEPs mergeable
delete the MEP page in the compass and cross link here
we can then iterate from there but this at least gives us the base to start from

I'd also recommend using a theme that is part of this project, I think it's important that we use our own infrastructure and have a consistent brand across our docs sites, especially for core projects like MEPs. I'm fine w either the book theme / jupyter book, or mystjs though.
@rowanc1 any chance you'd have a moment to get to this while you're finishing up the cross references MEP?

Yep, I can take that on -- I will try to get to this today or tomorrow!

No I will do it thanks

start this repo's commit history from scratch since the current MEP structure is much shorter

Ermm, I feel this is quite in bad faith, and don't know it fits in with the code of conduct of this organization?
You are talking about wiping out peoples contribution to the project, namely all my initial commits to set up this repository
I would note also, that in this commit: https://github.com/executablebooks/meta/commit/0377df63f5f95630488c44d0b1cf531161485531#diff-e9a11e85a944c43b1bf3dd2cdc09352dc016824279958134e45e91dbc16488c1L22
you have already previously, removed the acknowledgement of the work I did here:

I hope you can see why I'm a little unpleased with this approach?

I'm absolutely happy to work with @rowanc1 and you on this, but yeh well "rewriting history" is a little much for me to take 😬

Agreed that we should provide credit to those that participated in the MEP process bootstrap. Your initial commit in this repository was appreciated and a helpful contribution to our initial process.
Something that @rowanc1 and I discussed was cross linking that PR as part of the documentation here, and listing the team members that took part in that discussion or gave feedback on the draft. That way we credit the team of people that were involved.

The sentiment is appreciated, but still I don't see a good argument for wiping a commit history of a repository, I have never seen that happen in any project.

Re: rewriting history, the current state of main was not broadly discussed or approved, and was not an official process, so I think we should treat it as draft language.  History in this repository should "begin" with the first official MEP process that was created by the team and approved by the steering council.
I'd suggest we rename main to a new branch and cross-link that branch from the PR that we link in the MEP documentation. Then we create a new main and iterate from there. That way history isn't lost, your draft language is available for provenance, and we begin this repository history with the official MEP process that was defined.

I somewhat bemused by this sudden insistence that history in a repository should have an "official" start, but in any case...

copy paste the text at compass.executablebooks.org/en/latest/meps.html into a landing page with a brief overview of what MEPs are
That way we credit the team of people that were involved.

I suggest that this should be this text should be MEP0001, as is the case now (and for https://peps.python.org/pep-0001/, https://jupyter.org/enhancement-proposals/29-jep-process/jep-process.html, etc), and those involved credited as the authors

Yes I was thinking the same - we should treat the PR in meta as the "proposal + discussion" for MEP001

Yes I was thinking the same - we should treat the PR in meta as the "proposal + discussion" for MEP001

ok cool, if I'm on the author list for that, then we have a deal lol, and I'm not so much bothered about the commit history 😅
and again, if you do need any help than let me know, I am happy to assist

For the "bootstrap MEP", my thinking was that everybody that participated with edits, comments on draft language, or discussion in the PR will be on the author list in alphabetical order, or that we just have a single author of "The ExecutableBooks Team".
Not sure which is better given that there are no formal authorship guidelines. For subsequent MEPs we have a formal author field so this will be more explicit.

@choldgraf do you think you can take this on please. At least the initial MEP0001 commit -- I can help out once that is over the line.
For what it is worth, I am a fan of The ExecutableBooks Team, especially for the first MEP, as there were other people who also reviewed drafts and did not participate directly in the github discussions.

The team could change over time, I think it should be everyone in alphabetical order

I would note, and this is the last thing, I'm probably reacting to this so strongly, because I have already been biting my tongue on another incident where attribution of effort seems to have slipped: https://github.com/executablebooks/mystjs/pull/184
Here, essentially the entirety of the code I mainly wrote in markdown-it-docutils was copy-pasted into mystjs, without any mention
Its not the end of the world, but just a quick "hey @chrisjsewell just to let you know we are doing this because we want to integrate the code better, ..." would have been nice, rather than me having to find out second hand, as I imagine would have been the case here if I was not subscribed to the issues 🤷
I didn't mention, because I didn't want there to be negativity, but when it starts to become a trend

It was my understand that this repo was in draft as we knocked around ideas on how get the mep process up and running.
@chrisjsewell we all know you contributed extensively to this process. I fully expect it would be documented as part of this process as @choldgraf and @rowanc1 have pointed out.
FWIW - While I agree it is not common to reset history in a software repo -- I am in favour of reseting the history in this non-code repo case. I don't think it is always helpful to record everything in micro detail until the process is up and running and actively used -- in fact the opposite -- it is better not to have the history to bring focus to an agreed process.

it is better not to have the history to bring focus to an agreed process.

I honestly doubt anyone will be looking at the commit history to understand the process,
but anyhow, that's not really the primary thing here.
I hope you can see why it might be demotivating to happen across an issue that says your commits are going to be wiped, without any mention to you.

I fully expect it would be documented as part of this process

and yes, also with https://github.com/executablebooks/myst-enhancement-proposals/issues/14#issuecomment-1446663252,
where the acknowledgement was removed only a month after it was added,
I hope you can also understand that it might be difficult for me to trust that any such documentation would persist 😞
(as opposed to as an author of an MEP, which is a little more binding)

Sorry I didn't get to this yesterday, I ended up being pretty sick the last two days, I'll try to get to this today. Two quick responses to the above:

I hope you can see why it might be demotivating to happen across an issue that says your commits are going to be wiped, without any mention to you.

I can understand this. In the future the way to avoid it is to propose new processes via getting agreement from team members before taking action. Create a draft proposal (e.g., an issue, a hackmd, a google doc, etc), get a coalition of team members to support and advocate for it, make a decision w/ the team or steering council if necessary, and then implement something. (basically our new policy making guidelines). By aligning the team before implementation, we can avoid the case that a lot of work by one person is undone after a decision is made post-hoc.

and yes, also with https://github.com/executablebooks/myst-enhancement-proposals/issues/14#issuecomment-1446663252,
where the acknowledgement was removed only a month after it was added,

I removed that admonition because it's purpose was to provide informal context/acknowledgement in the discussion process when we were merging the PR, but was not meant as a long-term attribution since we do not use our meta/ documentation to provide attribution for any other specific content. For major updates to MEP process, the appropriate place for attribution is via the authorship list in the MEPs rather than in the implementation that exists in the docs. This is why you will be part of the authors list of MEP001, and why I removed that section from the meta/ docs. I did not provide attribution to myself in the team compass docs for the same reason.

Thanks for the response @choldgraf, that all sounds good. Hope you are feeling better!

Draft is up
Hey all - I've got a draft of the docs up at this branch:
https://github.com/executablebooks/myst-enhancement-proposals/tree/copy-from-meta
There are still a few things I'd like to add, like that nifty "markdown table insert" that @chrisjsewell implemented. I want to do that as a separate commit w/ him as the author though, since I'm largely just copypasting, but don't have time to figure it out right now so will get to that tomorrow.
Would love any feedback on the docs there, I think it's fine to iterate on all of this stuff in small chunks as long as we don't make any major changes to the process.

Made the switch on main
I've updated main with the new branch, and the docs are now here:
https://myst-eps.readthedocs.io/en/latest/
question: Do we want to rename the website to myst-enhancement-proposals as well? Or leave it as-is?
The previous main is now this branch: https://github.com/executablebooks/myst-enhancement-proposals/tree/chrisjsewell-mep-process-proposal . I've also cross-linked the HackMD that was originally used for it in the MEP0001 and in the top comment of the discussion PR. I can update that to something else if that's not the right link to use.
cc @rowanc1 who has a few PRs you'll need to update.
I'll let you all decide how you'd like to proceed with https://github.com/executablebooks/myst-enhancement-proposals/pull/5, but my suggestion is to hold off for a while until we have a few more targeted MEPs under our belts and a tighter process for discussion etc.

by the way, this made me think it might be useful to have that little "show the page metadata" transform as a page-level flag that comes with the myst parsers (e.g. :myst.show_metadata or something?

yep something like that could be handy indeed

Yep it's added now w you as the commit author, i did that this morning (i hope that's ok, it was basically just copy paste and tweak to match new key names)

hope that's ok, it was basically just copy paste and tweak to match new key names

yep all good

I have updated the two PRs, and rebased them on main.

Do we want to rename the website to myst-enhancement-proposals as well? Or leave it as-is?

I think that we should bring this under mep.myst-tools.org.
@chrisjsewell my readthedocs username is rowanc1 if you want to add me there please.
Exciting to see this process and website coming together. Thanks all! 🚀

my readthedocs username is rowanc1 if you want to add me there please.

Already done

(Sorry, buried in my email, 🤦 thank you!)


Change So.Da.Net endpoint to test ARIA links

Currently So.Da.Net DEV endpoint had some studies containing so called magic links to ARIA platform.
Some changes are required to CDC UI in order to be able to see the links, so step 1 in is to harvest some examples of metadata records containing them.

See also #606


hub is rendering at both www.napari-hub.org and napari-hub.org

For SEO purposes, we should make sure that the site only renders at either www.napari-hub.org or napari-hub.org, but not both.
My understanding is that www.napari-hub.org is preferable, as it will better future-proof us if we start to need other subdomains (e.g. api.napari-hub.org for #133)
Whichever we choose, we should ensure that the other has a permanent redirect (e.g. redirect napari-hub.org to www.napari-hub.org)

now the bare domain is being redirected via 301 to the www domain


Request for date and time stamp MRT when station changes

I am using MRT as a monitor to record traffic on a KOBserver Wire.
It would be really useful to have MRT display the date and time when the active station changes.
Currently it just shows the Station ID.

Would it be acceptable to have this be a command line option for MRT, rather than something in the Preferences/Configuration?
I ask, because I think it is probably something specific to MRT. I don't think people will use it with MKOB, and it doesn't apply at all to the utilities.
Something like --senderdt (sender date time).

Added '--senderdt'.

Tested revised MRT with --senderdt parameter and it works!
73
Ciao
KJ
On Tue, Apr 2, 2024 at 11:32 AM Ed Silky @.***> wrote:

Closed #335 https://github.com/MorseKOB/PyKOB/issues/335 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/MorseKOB/PyKOB/issues/335#event-12329635129, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF62ZODUMH6OISZ6JZOPNTTY3LTTTAVCNFSM6AAAAABFRTRPBSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGMZDSNRTGUYTEOI
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Kevin Jepson R.E.T.
President
4K Consulting Inc.
Si Fractum non sit, noli id reficere
Email: 4kconsulting at gmail.com
Cell:<PHONE_NUMBER>


Error when using 3, 9 or 27 as the number of steps

Trying to use 3, 9 or 27 as the number of steps will generate this error:
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/gradio/routes.py", line 247, in run_predict
    output = await app.blocks.process_api(
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/gradio/blocks.py", line 641, in process_api
    predictions, duration = await self.call_function(fn_index, processed_input)
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/gradio/blocks.py", line 554, in call_function
    prediction = await block_fn.fn(*processed_input)
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/gradio/interface.py", line 651, in submit_func
    prediction = await self.run_prediction(args)
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/gradio/interface.py", line 680, in run_prediction
    prediction = await anyio.to_thread.run_sync(
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/mnt/tera/git-repos/leszekhanusz/diffusion-ui-backend/src/diffusionui/gradio_interface.py", line 86, in gradio_run
    generated_images = run_pipe(
  File "/mnt/tera/git-repos/leszekhanusz/diffusion-ui-backend/src/diffusionui/gradio_interface.py", line 28, in run_pipe
    images = pipe(
  File "/mnt/tera/git-repos/leszekhanusz/diffusion-ui-backend/src/diffusionui/pipelines/pipeline_stable_diffusion.py", line 111, in __call__
    result = self.text2img(
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/diffusers/pipelines/stable_diffusion/pipeline_stable_diffusion.py", line 260, in __call__
    latents = self.scheduler.step(noise_pred, t, latents, **extra_step_kwargs).prev_sample
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/diffusers/schedulers/scheduling_pndm.py", line 202, in step
    return self.step_plms(model_output=model_output, timestep=timestep, sample=sample, return_dict=return_dict)
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/diffusers/schedulers/scheduling_pndm.py", line 317, in step_plms
    prev_sample = self._get_prev_sample(sample, timestep, prev_timestep, model_output)
  File "/home/leszek/miniconda3/envs/ldm/lib/python3.8/site-packages/diffusers/schedulers/scheduling_pndm.py", line 338, in _get_prev_sample
    alpha_prod_t = self.alphas_cumprod[timestep + 1 - self._offset]
IndexError: index 1000 is out of bounds for dimension 0 with size 1000

This will be solved in the next diffusers version with this commit

Fixed in release 0.4.0


Project Summary / Description

Hello,
Your project seems to be interesting, but I think it lacks summary/description.
It starts with some commands how to set up, but, what's the focus? Is it to fill what needs? What are the current limitations or planned features? (supposing it is new as the commit dates)

I'm doing the summary/description and I will commit the new read-me file and new features soon.
The focus is just simplify the Deploy using Dockerfile or Code detection. I just started the project because any friends had not permission to install or run other tools like heroku or flynn cli to deploy or manage containers. They just have a IDE and a GIT client, with git2docker is possible to deploy and manage Containers in a local standalone server, and of course learn more about Go programing.

Ok, thanks for answering my question.
Since you're doing the summary I think it can be closed.


Tiny polygons look bad in GL

GL magnifies the visibility of the coarseness of the little square polygons that are fabricated to take up the combined area of polygons that are too small to draw.
Maybe it would be better if they were at least rotated to match the orientation of the original polygon.

It looks smoother right away if they are 2 units on a side instead of 3.

The calculation is also off: it thinks holes add to the area instead of subtracting from it.

Preserving the original building shapes is probably more organic somehow but I have a hard time claiming it is actually better, even when visibly overzoomed.

I should definitely fix the hole area calculation though.

This is as close as it's going to get in the near term


Integration TAPO:Cameras Control cannot be loaded, shows error: Exception importing custom_components.tapo_control.config_flow

Description
Integration: Tapo:Cameras Control 6.0.1 has been added via HACS, but loading of Cameras Control is not possible. Always gives the error message: invalid config (see error log)
Reproduction Steps

Add Tapo: Cameras Control via HACS
Restart Home Assistant
Add Cameras Control to Config

Expected behavior
Start of Camera integration as it had work a year ago
If applicable, add error logs.
Logger: homeassistant.setup
Source: setup.py:251
First occurred: 15:29:54 (1 occurrences)
Last logged: 15:29:54
Setup failed for custom integration 'tapo_control': Unable to import component: Exception importing custom_components.tapo_control
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 822, in get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 936, in exec_module
File "", line 1074, in get_code
File "", line 1004, in source_to_code
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/tapo_control/init.py", line 961
f"Media sync ignoring {searchResult[key]["date"]}. Media sync: {enableMediaSync}."
^^^^
SyntaxError: f-string: unmatched '['
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 251, in _async_setup_component
component = integration.get_component()
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 830, in get_component
raise ImportError(f"Exception importing {self.pkg_path}") from err
ImportError: Exception importing custom_components.tapo_control
Logger: homeassistant.loader
Source: loader.py:822
First occurred: 15:29:54 (1 occurrences)
Last logged: 15:29:54
Unexpected exception importing component custom_components.tapo_control
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 822, in get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 936, in exec_module
File "", line 1074, in get_code
File "", line 1004, in source_to_code
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/tapo_control/init.py", line 961
f"Media sync ignoring {searchResult[key]["date"]}. Media sync: {enableMediaSync}."
^^^^
SyntaxError: f-string: unmatched '['
Device Firmware
320WS von tp-link Firmware: 1.3.11 Build 231117 Rel.44732n(4555)
Integration Version
HAOS 14
Using stream component
Yes
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Homeassistant in VMware
Search for similar issues
Yes
Additional information
No response

If using unsupported HA install method, python3.12 or python3.13 has to be used as that is what HA requires.

I am using HA via official install method for 3 years now. Everything is running fine except TAPO cameras control. Where do I find which python version is used in my installation? In the logs it seems to be a syntax error ( f-string: unmatched '[').

From the logs provided:
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module

Python 3.11 has been dropped in April 2024.

Thank you for this info. I have checked my versions. The HA core was outdated (version 2024.1.3). After manual update to core 2024.12.3 the camera control error was gone. Thanks for your help !

Thank you, I have modified hacs info file to ensure it cannot be installed on outdated HA versions before April going forwards.


3.1 check distributed lock success

When gaining a distributed lock if a timeout occurs the LockManager would return false, but nothing checks the return value and would bindly assume it has the lock.
This PR throws ODistributedLockException if the timeout occurs when trying to gain the lock.
Checklist

[x] I have run the build using mvn clean package command

Hi,
Will run distributed tests on this and verify no regression happen and then merge it.
Regards


Node taking 100% CPU

⚠ Please verify that this bug has NOT been reported before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
Node will take 100% cpu after a while.
I believe after starting a container and clicking to other containers, makes the node process go crazy.   But it takes a while to build up cpu %
Because of this i have to check the cpu or kill the rouge process after interacting with Dockge

👟 Reproduction steps
Seems to happen after I start a terminal connection in Dockge and quickly switch to another container.  Or I could be wrong, not entirely sure.
👀 Expected behavior
it doesn't hang like that
😓 Actual Behavior
It hangs
Dockge Version
1.1.1
💻 Operating System and Arch
Debian 12
🌐 Browser
Firefox
🐋 Docker Version
Docker version 20.10.5+dfsg1, build 55c4c88
🟩 NodeJS Version
v20.9.0
📝 Relevant log output
No response

Fixed in previous version, please update.


Move to multi-arch build

Signed-off-by: Alex Ellis (OpenFaaS Ltd<EMAIL_ADDRESS>
Description

Move to multi-arch build.
Motivation and Context
To support ARM64/armhf (Raspberry Pi) for the MQTT connector
How Has This Been Tested?

N/a - via CI build.

PR passed CI.


[FEATURE] Arbitrary Save Files

It may be beneficial to be able to load save games from either and arbitrary folder, or even an individual careerSavegame.xml / vehicles.xml / items.xml.

Update: going to write a how-to download stuff from the server "properly".  Adding the option to load random save files is going to add an entire level of error checking complexity, not to mention the complexity of "I want to add multiple arbitrary files"
So, going to lay out in the readme how you'd pull the whole savegame folder off of a server or wherever, and load the gameSettings.xml that goes with it.


Data is leaking somewhere in some undefined edge case, livelocking the GC

We're in possession of a recording that triggers this behavior:

The time cursor is paused. Data is not being ingested. This is therefore a bug: the GC is constantly trying to clean up to free space, but somehow it's not doing succeeding.
I haven't been able to reproduce this with a simplified script yet.

I'm 99% sure this is just a edge case I missed in:

https://github.com/rerun-io/rerun/pull/7182

I'll be back.

I think I know what's going on. I was looking in the wrong place: this is unrelated to https://github.com/rerun-io/rerun/pull/7182.
The problem stems from a nasty interaction between static data, latest-at query-time caching, and garbage collection.
Look at the following store stats after the recording has just loaded:
Without --memory-limit:

With --memory-limit 300MiB:

By the time the GC enters into livelock, the stats will look like this:

What's happening here is that all the temporal data that could be legally removed, has already been legally removed.
Those 39 temporal chunks left that we see in the stats can never go away, since the GC runs with protect_latest=1: we're already at the point where all that's left is one temporal chunk per (entity, timeline, component).
The livelock has started: we can run the GC all we want, from this point onwards it will never be able to remove anything.
But if we only have ~40MiB of data in the store, why are we hitting the 300MiB limit and running the GC in the first place?
The problem is that the latest-at cache is organized by query time, as opposed to data time.
That is why this cache grows a lot when you scrub the time cursor around: even though we are just caching references to chunks, all these btrees still take a lot of space on their own with this many query timestamps to keep track of.
The reason we do this is performance: the viewer runs a number of latest-at queries per frame that grows linearly with the number of entities in the recording, every microsecond we can shave off on the latest-at path matters, it all compounds very quickly by the end of the frame.
Now here's where this gets ugly: if there's nothing to GC, then there are no ChunkStoreEvents being sent, and this there is no cache invalidation going on.
The cache will therefore grow indefinitely, while the GC desperately attempts to keeps things under control: livelock.
The fix is to garbage collect the query cache directly when such a situation happens.

Can we reopen.  I am still seeing this behaviour where rerun does not maintain a memory limit with the latest development build from last night.  I am happy to provide a recording for this one if the old recording does not show it.

I haven't been able to repro using either main or the latest development build @ricpruss (that is pip install --pre --no-index -f https://build.rerun.io/commit/de49fce/wheels --upgrade rerun-sdk at the time I'm writing this).
I'm using the second RRD file you've provided (memory-too-much.rrd) with a 300MiB memory limit, and putting infinite pressure on the query cache by repeatedly looping the time cursor over the entire timeline:

What memory limit are you using in your test?
Can you take a screenshot of the information shown in the about menu?
Can you also copy the output of rerun --version?

Just to make sure, I tried the above on 0.18.2 one more time, and sure enough it very rapidly descends into madness:

Confirmed fixed, see https://github.com/rerun-io/rerun/pull/7370#issuecomment-2372629935


Determine performance hit of getting caller thread stack trace on every command execution

See #195

Not worth examining.  Closing.


upgrade to geo_concerns v0.3.1

Coverage remained the same at 100.0% when pulling f242641cd724b208f4ee501d92575fe07bdc8023 on gc-0-3-1 into 8f8ec2f08542a3f17d345724e3b062f940ffc6b7 on geo_concerns.


referencing properties of objects that are injected into a mono behaviour via construct will crash unity

when I reference properties from an object that is injected into a mono behaviour, unity crashes. I created a new empty project to confirm this is the specific issue. it took me a long time to find the cause since every time I tested unity crashed...
this is the mono behaviour I have attached, nothing depends on this so I don't attach zenject binding to the gameobject
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using Zenject;

[RequireComponent (typeof(Rigidbody2D))]
public class HorizontalMoveSystem : MonoBehaviour {

	PlayerStateComponent playerStateComponent;
	Rigidbody2D rb;

	void Start(){
		rb = gameObject.GetComponent<Rigidbody2D> ();
	}

	[Inject]
	public void Construct(PlayerStateComponent _playerStateComponent){
		playerStateComponent = _playerStateComponent;
		Debug.Log ("player state isMovingLeft: " + playerStateComponent.isMovingLeft);
	}
}

this is being injected and unity crashes. if I remove the 'isMovingLeft' from the above debug.log it runs and prints with just the playerStateComponent object
using UnityEngine;
using Zenject;

public class PlayerStateComponent {
	public bool isMovingLeft
	{
		get { return isMovingLeft = false; }
		set { isMovingLeft = value; }
	}

	public bool isMovingRight
	{
		get { return isMovingRight = false; }
		set { isMovingRight = value; }
	}
}

if I change the above (▲) class to the one below (▼) than it works
using UnityEngine;
using Zenject;

public class PlayerStateComponent {
	public bool isMovingLeft = false;
	public bool isMovingRight = false;
}

and here is my installer
using UnityEngine;
using Zenject;

public class PlayerInstaller : MonoInstaller
{
    public override void InstallBindings()
    {
	Container.Bind<PlayerStateComponent>().AsSingle().NonLazy();
    }
}

so far I am really enjoying your framework. Hopefully this is just something I'm doing wrong...

My best guess is that this is happening because of an infinite loop in PlayerStateComponent.
public class PlayerStateComponent
{
    public bool isMovingLeft
    {
        get { return isMovingLeft = false; }
        set { isMovingLeft = value; }
    }

    public bool isMovingRight
    {
        get { return isMovingRight = false; }
        set { isMovingRight = value; }
    }
}

Here, the isMovingLeft property is calling itself, so it just repeats forever.  Maybe you want to consider auto implemented properties like this?
public class PlayerStateComponent
{
    public bool isMovingLeft
    {
        get; set;
    }

    public bool isMovingRight
    {
        get; set;
    }
}


Jenayah: Watch mynewlocks.com

Jenayah requests the watch of the watch_keyword mynewlocks\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

mynewlocks\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal HQ


sqrt() approximation

Hello,
I'm not sure if it's a bug or a known rounding behavior.
If I compute the sqrt() of a complex number -9+0i the correct solution should be 0+3i
but with this module (I used num crate) I got:
0.00000000000000018369701987210297+3i
As far as I know some math lib implement hard-coded case for some exact value.
Did you considered doing the same?
Luigi

That's rounding error -- we convert to polar to perform the operation and then convert back. So -9+0i = 9eiπ, then the square root is 3eiπ/2 = 0+3i. However, those irrational angles can't be precisely represented, so the conversions are slightly inaccurate.
But yes, I think we could add a special case when the input has zero imaginary value. The principal square root of a positive real is a positive real, and for a negative real it is a positive imaginary. Then we wouldn't have any loss beyond the scalar Float::sqrt itself.


Updated setup-cloud.sh for Ubuntu 22.04

Issue #, if available:
Description of changes:
Changes to the setup-cloud9.sh script to run on Ubuntu 22.04.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you very much for your contribution @stevrobu!


Segfault on version 2.1 (MacOS)

./nvidia-clerk-darwin -region=GBR -sms -model=3080
2020/09/23 11:36:08 Erorr unmarshalling inventory XML
2020/09/23 11:36:08 Error getting Product Information retrying...
2020/09/23 11:36:09 Product ID:<PHONE_NUMBER>
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x144cf18]
goroutine 1 [running]:
main.MonitorRelease(0x15c5de0, 0xc0001940f0, 0xc000196000, 0x1)
/home/runner/work/nvidia-clerk/nvidia-clerk/main.go:164 +0x238
main.main()
/home/runner/work/nvidia-clerk/nvidia-clerk/main.go:96 +0x626

My bad. It looks like I had actually picked version 2.0. I cannot reproduce with 2.1.


Marked crosswalk lines generate generic crossing node instead of marked crosswalk node

Description
when I draw a marked crosswalk, and accept the warning to join it to the road, it just adds a generic crossing node, but not a specifically marked crossing node.
Version
2.1
What browser are you seeing the problem on? What version are you running?
Chrome 115.0.5790.173 64-bit
The OS you're using
Windows 11
Steps to reproduce
Add marked crosswalk line
Check warnings that the line crosses a road
Accept warning recommendation
check new crossing node tag
The browser URL at the time you encountered the bug
https://rapideditor.org/edit?#background=Mapbox&datasets=msBuildings&disable_features=boundaries&gpx=https://mwai-tasking-manager-production-api.mapwith.ai/api/v2/projects/147/tasks/queries/gpx/%3Ftasks%3D2555&map=18.52/32.69383/-117.17153
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response

Thanks, I'll check it - I really thought I covered all the cases with #1015  😢

Quick vid showing that we now correctly update the tags in this case:
https://github.com/facebook/Rapid/assets/1887955/363f43aa-654c-4e81-a3f1-714fa9b8e01f


Database

Gan mau tanya... Backup DB nya, share juga dong... buat belajar

Mas Bagi DB nya makasih

@baysptr @wakidanwar maaf, database nya lupa, sudah tidak ada lagi

Blastoff.zone Airdrop: Win 0.1 ETH + $100 Bonus!

Hello crypto community! Blastoff.zone is offering an exciting Airdrop for the first 10 users! You can win 0.1 ETH plus a $100 bonus just by participating and connecting your wallet.
How to participate:

Click Connect Wallet to access the Blastoff.zone website.
Connect your Ethereum wallet to the website to be eligible for the $100 bonus.
Use the "Claim Now" method to receive your tokens.

Don't miss out on this amazing opportunity! Hurry and claim your prize before the 0.1 ETH runs out.
Remember, tokens will be distributed on a first-come, first-served basis. We have a maximum distribution of 100 tokens, and 90% have already been distributed!
danieldelcore, @naher94, @eirik-L, @vizion8-dan, @vaimalaviya1233, @jy95, @SenritsuYoji, @phenax, @pythoninthegrass, @raftario, @Poseidon444, @round, @rodrigobrando, @RoestVrijStaal, @lpstandardrp, @Mx-CatsMeow, @MatejLach, @chardy, @TokyoSoichiro, @fieu


Implement unregister for Push API

Implemented unregister function for push api.
ISSUE=none

@romandev PTAL.
I did not separate indexeddb, but pass the test.


ARROW-9824: [C++] Export file_offset in RowGroupMetaData

Export the file_offset field (which already exists in RowGroupMetaDataImpl) in RowGroupMetaData.

@emkornfield Do you think this is ok to add?

Since this is simply a proxy object around the underlying metadata I think it is OK to expose but should have some documentation around the value of this field if the offset isn't present (it looks like this field is optional, but in practice I imagine it must be required to properly parse a file?).  It would be nice to use the wording from the parquet specificaiton

When you say documentation I assume you mean a comment near the method definition?
And it looks the default value of this field is 0? (https://github.com/apache/arrow/blob/d02e16646cb3ee2a568dfeeaa68a0f75986592c8/cpp/src/parquet/metadata.cc#L1249)
And when you say the wording from the parquet specification do you mean the comment in the thrift definition?

When you say documentation I assume you mean a comment near the method definition?

Yes the comment for the method definition

And it looks the default value of this field is 0?

Yes, I'm not sure if it breaks anything to make this -1 or something obviously wrong (0 should be wrong because I think all parquet files need to start with 'PAR1'

And when you say the wording from the parquet specification do you mean the comment in the thrift definition?

Yes:
Byte offset from beginning of file to first page (data or dictionary) in this row group

I updated the comments for the method declaration to address your documentation concerns. I did not change the default value of file_offset because I agree that 0 is wrong (though less obviously wrong than -1) and I did not want to chase down the unintended consequences of changing that.

+1 thank you @scober


Find a good square Icon for FinetuneLLMs and replace it at Header

This is should be some purple or blue colour, and should not be light, as our background is white.
The best way to do this is to use Fooocus, an AI that can generate images based on prompts. It's deployable locally

It would be nice to also provide the light-color version logo, as we need to support dark theme in phase 2


[cli] fix CLI problems with new json-rpc client

Motivation
CLI problems: (#6161, #6025)

It won't handle server stale response, causes client side printing error messages when received stale response.
Wait transaction execution logic is not correct, should check transaction hash for making sure the transaction got by account address and seq is the one we are waiting for.
It supports non-blocking minting coins, when minting coins, it is easy to get into problems because of Faucet service can't handle concurrent minting requests. As TC / DD accounts need to know right sequence number to submit new transactions.
Waiting for minting on testnet Faucet service is not correct: waiting for dd account by checking next account sequence may give wrong information when there is another person running CLI and requested minting coins at same time (used same account sequence).

This PR fixes above problems by the following changes:

A new json-rpc client for addressing problem 1 and 2:

Handle stale response by retrying the operation.
Implement correct wait transaction logic.

Removed non-blocking mint, this will make sure user of CLI won't submit multiple minting request in sequence which is likely to be failed and confusing to user.
Update CLI faucet minting logic to wait for minting transaction executed, instead of only checking next dd account seq.

Note: new json-rpc client is built on top of protobuf defined response types, the plan is to define jsonrpc response types once in protobuf, then generate code for all client sdk languages. Python, golang, java clients are using the protobuf definition added in this PR already. Later we will also update server side to use same protobuf generated code. After that, when server added new fields / types, client can generate response types from same definition.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Manual test.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/libra/developers.libra.org, and link to your PR here.)

This PR may have modified JSON-RPC server code.
Breaking changes policy:

Chaning JSON-RPC method signatures or removing/modifying fields
in the response in /V1 will not be accepted.
Adding fields is ok.
Adding a new JSON-RPC method is ok.

Please ensure you have also done the following to update the docs:

Update json-rpc/API-CHANGELOG.md.
Add/update type/method documentation under json-rpc/docs.

Oh man... proto? Is there no other way to do this :(
Bad memories of trying to remove proto from the code base :P
This is very clever though...
Curious, would it be possible to reuse @matbd's code generator framework for LCS?

Oh man... proto? Is there no other way to do this :(
Bad memories of trying to remove proto from the code base :P
This is very clever though...
Curious, would it be possible to reuse @matbd's code generator framework for LCS?

Had discussion related to this https://fb.workplace.com/groups/673683343488644/permalink/767450187445292/
Basically, the code generator framework still has a long way to support more languages, and @matbd has no interest to support JSON format serialize & deserialize.
Here the protobuf is used to define interface data structure for making sure client sdk languages' can get limited but good enough backward and forward compatible support, which reduces headache for anyone implementing JSON-API client with strong type for response data, and this is what protobuf built for.
I understand it maybe bring back something not ideal, but it is really exactly what we need for a PRC interface.

:exclamation: Invalid command

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.


RC test: Area Model: Multiplication 1.0.0-rc.3

@ariel-phet @amanda-phet @kathy-phet, Area Model: Multiplication 1.0.0-rc.1 is ready for RC testing.
Link to sim
Link to iFrame
Test Matrix FIRST focus on Wiin 7+ Chrome, macOS 10.11+ Chrome, iPad Air 2, Chromebook, then others when time allows.
Issues to Verify
Please test the following issues and check them off after addressing. If they are resolved, close them.  If not, they should be updated.

[x] https://github.com/phetsims/area-model-common/issues/119 (check iPad performance)
[x] https://github.com/phetsims/area-model-common/issues/128 or https://github.com/phetsims/area-model-common/issues/101 (if there are major memory leaks)

Please also verify

[x] stringTest=double (all strings doubled)
[x] stringTest=long (exceptionally long strings)
[x] stringTest=X (short strings)
[x] stringTest=rtl (right-to-left)
[x] stringTest=xss (test passes if sim does not redirect, OK if sim crashes or fails to fully start)
[x] showPointerAreas (touchArea=red, mouseArea=blue)
[x] Full screen test
[x] Screenshot test
[x] Does AR need to be notified for any LOL updates?

If any new issues are found, please note them in https://github.com/phetsims/area-model-common/issues and reference this issue. Please note which screens/sims are affected.
(Other potentially useful items)
Sim-specific query parameters useful for testing:
• ?showAnswers - Adds a button for game screens that fills in the answers when clicked.
• ?maximumCalculationSize - Fills in generic screens with values that trigger a certain maximum layout size
Sim-specific terminology: Use the glossary from https://github.com/phetsims/area-model-common/blob/master/doc/implementation-notes.md
@ariel-phet please assign and prioritize

Preempted by rc.2: https://bayes.colorado.edu/dev/html/area-model-multiplication/1.0.0-rc.2/phet/area-model-multiplication_en_phet.html
The changes on the branches were:

Changes fonts on the screen/navbar icons, see https://github.com/phetsims/area-model-common/issues/114
Fix for where a non-IE11 supported function was used, see https://github.com/phetsims/area-model-common/issues/137
Fix unreported issue where the touch area for edit buttons/readouts did not switch between vertical/horizontal.
Fix unreported issue where Ax+b dual-spinner entries on variables game challenges would report as wrong incorrectly.

Presumably verify the above fixes (see @phet-steele for details), and if there is any other testing it can be completed on rc2.

Preempted by rc.3: https://bayes.colorado.edu/dev/html/area-model-multiplication/1.0.0-rc.3/phet/area-model-multiplication_en_phet.html
The changes on the branches were:

Yellow "enter" button, see https://github.com/phetsims/area-model-common/issues/142
Don't use Number.parseInt, see https://github.com/phetsims/area-model-common/issues/141

Presumably verify the above fixes (see @phet-steele for details), and if there is any other testing it can be completed on rc3.

Deployed, closing.


[WIP] proper CPU percentage calculation

This does the real CPU % calculation from docker stats, but in jevvascript.
Gnarly one liner right now though.

:100:

so sorry for the delay


Question regarding flask

I have previously used APScheduler in Flask for some things I need to do in background.
The problem with flask is if you load it in gunicorn, or debug mode and have multiple threads, the tasks will get scheduled multiple times as its run multiple times.
Is there a workaround in red engine for this?

I'm not sure how APScheduler works under the hood but Rocketry (just renamed the library yesterday, sorry for confusion) aims that the main thread and process has the truest information and it is responsible of keeping things in sync. If you have started the app only once, you should not run in troubles.
I have successfully attached a Flask app to Rocketry and I did it with multiple threads, if I recall correctly. There were a separate FlaskAPI task which I later removed due changing focus to make the core system easy to use and as robust as possible. I'm planning on doing examples to the docs of how to integrate at least Flask and FastAPI to the scheduling engine but you could practically include anything as you have the full control on the scheduler flow also in runtime.
I think the best way to implement such APIs to the system is via metatasks (just regular tasks that take the session as an input, the execution cannot be process though). The idea is that the scheduler runs on the main thread and you launch this task on a separate thread that runs constantly and manipulates the session on runtime. At the moment I'm not exactly sure how it would be with Gunicorn though. I could give you an example perhaps today or tomorrow and I'll investigate this more when I have upgraded and exposed the built-in conditions.

appreciate it, I will do some testing on my own if I get some time next week.


XDM Docs do not show require properties correctly

The documentation does not correctly say which properties are required.
Example:
https://github.com/adobe/xdm/blob/3ddccc36df572d61b014938e230226720bff1585/docs/reference/context/experienceevent.schema.md
There are required properties
"required": ["@id", "xdm:dataSource", "xdm:timestamp", "xdm:endUserIDs"]

@kstreeter please put this in the June 15th Milestone. It is causing confusion.


Application Crashes due to malloc error in Alamofire library in Request.swift class.

Greetings,
Thanks for making awesome library in Swift. Right now, I am moving code from Objective C to Swift. I am using Alamofire library for Web service calling. It is working fine but application crashes many time. I am not sure about it's library issues or something else. Please review below console Log with attached screen shot:
Console Log:
malloc: *** error for object 0x1700075f0: Invalid pointer dequeued from free list
*** set a breakpoint in malloc_error_break to debug
(lldb)

Please let us know your comments.
Thank You,
Renish Dadhaniya

Instead of creating a support issue in Github, please open a question on Stack Overflow and tag Alamofire. The Alamofire community is very helpful and supportive. Stack Overflow is the best place to get your question answered quickly and correctly.

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


wordWrap setting by file type

I'd like the ability to control editor.wordWrap by file type.
Like this in settings.json:
"[txt]": {         "editor.wordWrap": "wordWrapColumn",         "editor.wordWrapColumn": 80     },
By default I have word wrap turned off globally but I would like to turn it on, only in certain file types such as .txt files.
If this behaviour is already intended then it isn't working for me as the settings above are copied from my editor.  I had to turn on 'editor.wordWrap' globally for the settings above to take effect.
My current VS code is:
Version: 1.41.1 (user setup)
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.17134

- "[txt]"
+ "[plaintext]"

Changing txt to plaintext has solved this.  Many thanks!


Ensure building futures-executor on no_std environments works

num_cpus is not capable of running in a no_std environment so just remove it as a dependency when building without std.

Thanks!


add changelog for v0.6.0

Summary

add changelog for v0.6.0

Ticket Link
n/a
Release Note
NONE

Codecov Report

Merging #772 (0a2d1a2) into main (72a7b00) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #772   +/-   ##
=======================================
  Coverage   48.84%   48.84%
=======================================
  Files          62       62
  Lines        5575     5575
=======================================
  Hits         2723     2723
  Misses       2557     2557
  Partials      295      295

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 72a7b00...0a2d1a2. Read the comment docs.


wallet-rpc: Expose wallet events via RPC

I converted this to a draft. Please mark it as ready for review once the readme stuff we agreed about is done.


Option to require keystroke to exit Screen Saver

Since I have Playnite opened on my third monitor (TV) at all time, the option to have some kind of slide show showing on there while I'm not playing is really great to avoid burn-in. However, since I am still using the PC in the meantime, the screensaver will never actually turn on.
Having an option to have the Screensaver trigger when there's x amount of time of inactivity in Playnite specifically (and not on the PC at large) and then requiring for the user to click on the window or some other kind of input to exit the Screen Saver when they want to use Playnite to launch a game would make it work perfectly with this use case.

While I am not sure how much information I can extract from the main app, one solution could be controlling how the plugin determines when to close i.e. only closing when the screen saver window is directly clicked may be a solution.
I'll explore both paths, but does limiting input sound like a good solution for you use case? Would you want this behavior to be specific to the playnite mode (Desktop Vs Fullscreen)?

I do have a story for supporting hotkeys (#27).
I could basically ignore inputs and display after the set amount of time when the app is minimized or deactivated. I'll convert this story for that feature.
As for a UI option, since the game & main menus in Desktop mode don't exist in Fullscreen mode, whatever I would hypothetically implement would need to be supported on a per theme basis. Given how small the added functionality would be, I can't see many theme devs supporting it. If Playnite adds generic UI support for plugins when fullscreen in the future, then it would be viable. Sadly, it's probably not worth it until then.

Ah gotcha and the would the hotkeys also work in Fullscreen mode are they also relying on the theme?
If they work in Fullscreen mode then I would ideally just need a way to turn off the automatic start of the screensaver. It might already be possible? Not sure. If not then maybe I'd setting it to 0 seconds of inactivity could be a way to disable the timer?
Then I could simply have a hotkey to start it and one to turn it off whenever needed.
Thanks a lot for the great support of my weird use case haha. No worries if it ends up not being possible.

The hotkeys would work independently of mode or theme.
Yep, it is already possible. In the addon settings there is a drop down labelled 'when to play'. Setting it to never or desktop will prevent the ScreenSaver from automatically displaying during fullscreen mode. Manual starts will still work.
No problem. Thanks for the quick feedback, helps iron out the specifics. I've honestly thought of setting up this scenario myself, just didn't apply it to the plugin. It's certainly possible to implement, it just takes time.


Examples is not running.

I'm trying to run basic example from your repo

It falls on the useTable call

Provide a minimal replication of this error on codesandbox

Yes, please provide a reproducible example in a new issue. Thanks!


Add a section for OpenSearch SQL CLI on Downloads/Getting Started page.

Add a section for OpenSearch SQL CLI on Downloads/Getting Started page. It could be

brief descriptive words for this cli tool
links to Pypi https://pypi.org/project/opensearchsql/
command to install pip install opensearchsql

@stockholmux Hi Kyle, what's the plan of adding this?

@zhongnansu Currently backlogged as we have some other pressing matters, but we'll get to it.

Is this issue still open? I will be interested to look into it.

Is this issue still open? I will be interested to look into it.

I think it's still open. We'd love to see your proposed change or PR!
@stockholmux could you involve documentation team to help or guide?

@zhongnansu  Great! Thank you.
I just need some descriptive words for this cli tool. I can PR once I get that. Thank you again.

@zhongnansu  PR added for review #1051 . Thank you

Solved with #3112 !


AL-8879 Fixed bug where the new executor gets expired tokens when the new executor registration time overlaps with the driver delegation token update time

<!--
Thanks for sending a pull request!  Here are some tips for you:

If this is your first time, please read our contributor guidelines: https://spark.apache.org/contributing.html
Ensure you have added or run the appropriate tests for your PR: https://spark.apache.org/developer-tools.html
If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][SPARK-XXXX] Your PR title ...'.
Be sure to keep the PR description updated to reflect all changes.
Please write your PR title to summarize what this PR proposes.
If possible, provide a concise example to reproduce the issue for a faster review.
If you want to add a new configuration, please read the guideline first for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
If you want to add or modify an error type or message, please read the guideline first in
'core/src/main/resources/error/README.md'.
-->

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

https://devopsjenkins.kyligence.io/job/KE4/job/Spark-UT/252/

LGTM


Support Warm pool in EKS managed nodegroup

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

Yes ✅: please list the AWS provider version which introduced this functionality

YES   warm pool related doc https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#auto-scaling-group-with-warm-pool
Is your request related to a problem? Please describe.

in my use case  a large docker image about 27G is used for CI purpose when autoscaling  i need to wait 30mins  before docker image ready   so i want to use warm pool to cache docker image in advance and reduce waiting time for ci users
i notice that warm pool is supported in self managed node group but not enable in managed node group
Describe the solution you'd like.

add an input variable to enable warm pool settting  in EKS managed nodegroup
Describe alternatives you've considered.

Additional context

Closing here since this is not supported by EKS managed node groups today https://github.com/aws/containers-roadmap/issues/1387

Don't forget to upvote the feature request in the linked issue!!


Make React components usable if installed via NPM

Currently, the react components are not usable if we install the npm package for the tool. This is because JSX is compiled (only under src) using webpack during the build process which is fine so we need to export the "built" react component from our package.
It probably requires to re-configure some webpack configuration. This might be a useful link.

Closing as we decided for a different approach!


Toolbar item for help docs

From @zlatko-minev
What is the feature being requested?
Add action toolbar items / menu to help html build docs in a browser as an alternative to the open_docs() command
What are use cases for this feature?
Users can load the docs without typing a command

Great work


Project Name and Project Path

At this moment, we're using the sbt setting name with two main purposes: create url paths/urls pointing to the project and project naming (used in different files like README, CONTRIBUTING, LICENSE, etc.).
However, we should create as many new settings as we need to be able to personalize the project configuration. For example, for the second case, orgProjectName for example, by default with the name sbt setting value.

For example: https://travis-ci.org/47deg/sbt-org-policies/builds/222830858#L3022


Sidebar size keeps increases when clicking on right edge of Explorer panel

VSCode Version: 1.7.1 stable
OS Version: Win 10

This only happens if Explorer panel is open. Other panel like Search, Extensions work as expected. But if I keep double clicking the right edge while Explorer is open the width keeps increasing.
Steps to Reproduce:

Open Explorer side panel
Double click on panel right edge
Repeat step 2

https://github.com/Microsoft/vscode/issues/15242


TypeError: Object # has no method 'release'

TypeError: Object #<Connection> has no method 'release'
    at Query._callback (/routes/autoSignIn.js:23:20)
    at Query.Sequence.end (node_modules/mysql/lib/protocol/sequences/Sequence.js:66:24)
    at Query._handleFinalResultPacket (node_modules/mysql/lib/protocol/sequences/Query.js:143:8)
    at Query.OkPacket (node_modules/mysql/lib/protocol/sequences/Query.js:77:10)
    at Protocol._parsePacket (node_modules/mysql/lib/protocol/Protocol.js:172:24)
    at Parser.write (node_modules/mysql/lib/protocol/Parser.js:62:12)
    at Protocol.write (node_modules/mysql/lib/protocol/Protocol.js:37:16)
    at Socket.ondata (stream.js:51:26)
    at Socket.EventEmitter.emit (events.js:117:20)
    at Socket.<anonymous> (_stream_readable.js:710:14)
19 Sep 15:26:13 - [nodemon] app crashed - waiting for file changes before starting...

In my code I call the release method on my connection and the program crashes telling me the above. Why? I create the pool, get connection on request, and then pass the connection to my request handler. Everything works except it tells me the connection has no method 'release'. What gives?
Thanks,
-John

It works! Thank you.

Instead of that command you should just install the latest version (not alpha anymore). If it doesn't install that perhaps means you have a specific version in package.json. You should be installing 2.7.0.


Failure to unload last round from looted magazines with "Cannot interact with .. because it is currently being modified"

General information
Project issue is for:
Server 3.8.0 BleedingEdge edd5f0
Expected result:
Ability to unload all rounds out of magazines looted from PMCs/Scavs
Actual result:
(video footage attached)
Unloading magazines on PMC/Scav bodies is successful up until 1 round remains. Attempting to unload the last round from the magazine fails with in-game error message "Cannot interact with .. because it is currently being modified". Last round remains in the magazine and further attempts result in the same outcome.
Seems to affect all magazines of both PMC and Scavs regardless of type. Seems to affect magazines from their rig and also the magazine removed from their in-hand weapon. Doesn't matter if the number of rounds contained in the magazine is examined before unloading or not.
Only occurs in-raid. If the affected magazine(s) are extracted from raid then unloading any remaining rounds is successful in the stash.
Can be avoided by moving the magazine into player inventory before unloading
How to reproduce

Kill a PMC or Scav which has a magazine-loaded weapon
Loot the body and "Unload Ammo" of a magazine
Wait until unloading reaches the last remaining round of the magazine

Screenshots

Attachments

image.png (30 KiB)
image.png (37 KiB)
2024.02.17_0-52-21_<IP_ADDRESS>.28744 traces.log (73 KiB)
LogOutput.log (54 KiB)
server-2024-02-17.log (52 KiB)
2024-02-17_02-52-57.mp4 (3690 KiB)

Originally written by R3

This is a live 0.14.1 issue, not an SPT bug

Originally written by DrakiaXYZ

EDIT: Thanks DrakiaXYZ for confirming
Figured I'd report it anyway. Could remain for reference with "Live issue"

Originally written by R3

Just as a note that after the recent 0.15 release this issue appears to be fixed in live Tarkov PVE mode (whereas just before the release it still occurred as described).
If it is verified as fixed in the next milestone version for SPT also, then it can be removed from the non-SPT issues list here: https://dev.sp-tarkov.com/SPT/Issues/wiki/Known-non-SPT-issues

Originally written by R3


fbdelay~ blows up quite easily

chorus~ example

related to #1446

actually unrelated, because this was a much older issue, not sure if it makes sense to keep this open anymore

cant see anything funny in chorus~ anymore


Add sharding manager

Because of the high numbers of servers and users the bot must handle, it is time to add the sharding manager to the bot.
This will be a breaking change leading to performance improvements and better maintenance.

Beta version of the Wikipedia Bot now features sharding.
It could come with the 1.7 update or with an minor 1.6 update.


odsole70.dll  not found

I want to make http request from sqlserver here is my SP
DECLARE @sUrl varchar(200)
DECLARE @obj int
DECLARE @response varchar(8000)
SET @sUrl='http://xxxxxx?xx='+x
EXEC sp_OACreate 'MSXML2.ServerXMLHttp',@obj out
EXEC sp_OAMethod @obj,'Open',NULL,'GET',@sUrl,false
EXEC sp_OAMethod @obj,'send'
EXEC SP_OAGetProperty @obj,'responseText',@response out
--select @response [response]
EXEC sp_OADestroy @obj
on windows servers ı was using these commands to allowing the configure
sp_configure ‘show advanced options’, 1;
GO
RECONFIGURE;
GO
sp_configure ‘Ole Automation Procedures’,1
reconfigure
I run commands without any error but when  o triggered to SP
this error occurs
"odsole70.dll  not found"
when ı write this 'sp_helptext sp_OACreate'
ı can see   odsole70.dll but ı could not achieve to sen HTTP request

Are you trying this on a SQL Server on Linux container? SQL Server on Linux does not support extended stored procedures. Please see this article.


about visualization about training

Hi, @bearpaw,
Thanks for releasing this useful package. BTW, during the training , how could I visualize the loss diagram like the Tensorboard used in Tensorflow?
THX!

Sorry that I did not integrate Tensorboard in this code. However, I write a very simple logger to save the training progress. After training, you should find the log.txt in the directory when you save your model (e.g., checkpoints/cifar10/alexnet/log.txt). The log file should look like this
Learning Rate	Train Loss	Valid Loss	Train Acc.	Valid Acc.
0.100000	1.451691	1.147165	47.110000	59.760000
0.100000	0.914918	0.928320	67.084000	68.180000
0.100000	0.719559	0.758013	74.574000	74.240000
0.100000	0.604210	0.751205	79.030000	75.660000
0.100000	0.538204	0.562017	81.564000	80.490000
0.100000	0.493776	0.669323	82.940000	77.790000
0.100000	0.465779	0.521751	83.890000	82.960000
0.100000	0.437683	0.601297	84.980000	79.930000

Then you can use the following script to visualize and compare the training process of the different models. For example, comparing the Valid Acc. for densenet-100 and densenet-190,
from utils import *
import matplotlib.pyplot as plt

paths = {
'densenet100':'/home/wyang/code/pytorch-classification/checkpoints/cifar10/densenet-bc-100-12/log.txt',
'densenet190':'/home/wyang/code/pytorch-classification/checkpoints/cifar10/densenet-bc-L190-k40/log.txt',
}

field = ['Valid Acc.']

monitor = LoggerMonitor(paths)
monitor.plot(names=field)

savefig('test.eps')
plt.show()

If you are willing to integrate Tensorboard into this code, feel free to create a PR. Thank you.

Thanks @bearpaw
FYI, tensorboard_logger


database/sql: TestTxCannotCommitAfterRollback failures on windows-amd64-2008 builder

2020-04-22T16:45:05-141b11d/windows-amd64-2008
2020-04-20T20:22:51-7004be9/windows-amd64-2008
These failures occurred just after CL 227278 for #38058 (which, coincidentally, appears to have been merged without a corresponding regression test).
Marking as release-blocker for Go 1.15, since this appears to be a regression.
CC @kardianos @odeke-em @colinking

@bcmills The commit right before is not relevant. I'm not sure a new test for that commit would be beneficial.
The flaking test is a new test merged in https://go-review.googlesource.com/c/go/+/216240 two days ago. The CL fixes a real issue, but harder to test for. I'll look into the Test to try to determine why it is flaking.

@gopherbot Please backport to Go 1.14. This is a fix for a flaky test. A flaky test makes release testing more difficult and less accurate.


Updates timestamp format to something that is recognizable.

My main reason for opening this PR is as a means of starting discussion around the usability of non-standard time formatting, and this proposed change is really just a straw-man for that discussion.
I have never seen DD.MM-HH:mm:ss before, and actually understanding what timestamp this was in the UI required me to go dig into the source code.  I see that ISO8601 is being used for the "long" format, though it is unclear why there is a desire to save ~10 characters here.  This changes it to a slightly shorter form of ISO8601 than what moment uses (Z timezone).
As a developer/user (who has seen a lot of timestamp formats in my day), I was super confused by the previous format.
Other options would be YY-MM-DD HH:mm:ss, which is ~3 characters longer than original and more clear and closely aligned with ISO8601, though it leaves out the time zone, which I believe to be critical as the time is in UTC if I am not mistaken, rather than user's local clock.  Also, it truncates the YY to two digits which makes it difficult to distinguish from DD for the next ~15 years.

What is the status of this?  Is there something I can do to push it through (other than rebasing if there is agreement on the change)?  If more discussion is needed, who should be @mentioned?

probably the only reason this was/is ignored is that github doesn't let us auto merge it b/c of merge conflicts, it seems like an obvious improvement

Rebased.


PEAR-1024: Fix for User with no controlled data access does not see proper error modal/banner

Description
Checklist

[N/A] Added proper unit tests
[N/A] Left proper TODO messages for any remaining tasks
[N/A] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

I can't test this easily unless I get all my permissions removed. If it looks good code-wise, we can merge and have Evgeniia and QA test on qa.


WIP: load all tokens into cache

This PR just shows what changes are required to load all tokens at once into the cache. This will allow us to run some tests on the performace impact.
Findings:

Lots of small requests to core services result in quite some overhead right now

Keep Alive does not solve this
Http2 is not available for services right now (we are coordinating with devops to evaluate this)

Request for unknown addresses that don't hit a known token take longer

Information is pulled from on-chain (@Uxio0 maybe we could add a query param, that disables the on-chain lookup?)

Using /v1/tokens/?limit=10000 to load all tokens into cache provides improvements

Cold load request time goes down by 50% (~15s to ~8s) - Note: I did NOT do extensive benchmarking
Uses ~1.5mb of redis cache (not really an issue) - We should probably check our REDIS eviction policy
If we want to do the same for contract info, we should filter to /contracts/ to filter out contract without a display name

Future ideas:

Predict what caches to warm/ pre-populate caches

Keep stats on what Safes interact with the gateway and have task that keps the results for these in cache up to date (e.g. when we get a webhook to invalidate them we would also reload them directly, so that they are up to date)
Create a cron-job that updates the caches (e.g. for tokens, for contracts, for safe apps, for most used safes)

Related: Add cache admin endpoint

Error cache duration: https://github.com/gnosis/safe-client-gateway/issues/246

Changes to caching:

Use cache prefixes to cleary separate cache entries for tokens from other cache entries (also to avoid that they get invalidated by webhooks)
load all tokens into cache instead of 1 by 1

Unrelated changes:

Update pre-commit hook to not format child files

Information is pulled from on-chain (@Uxio0 maybe we could add a query param, that disables the on-chain lookup?)

That could be a solution. I opened a ticket to track this https://github.com/gnosis/safe-transaction-service/issues/217

https://redis.io/topics/lru-cache
@rmeissner The docs recommend allkeys-lru for most cases, they state:

In general as a rule of thumb:

Use the allkeys-lru policy when you expect a power-law distribution in the popularity of your requests, that is, you expect that a subset of elements will be accessed far more often than the rest. This is a good pick if you are unsure.
Use the allkeys-random if you have a cyclic access where all the keys are scanned continuously, or when you expect the distribution to be uniform (all elements likely accessed with the same probability).
Use the volatile-ttl if you want to be able to provide hints to Redis about what are good candidate for expiration by using different TTL values when you create your cache objects.

We should also get away from volatile-* as it may throw an error as stated here:

The policies volatile-lru, volatile-random and volatile-ttl behave like noeviction if there are no keys to evict matching the prerequisites.

noeviction behaves like so:

noeviction: return errors when the memory limit was reached and the client is trying to execute commands that could result in more memory to be used (most write commands, but DEL and a few more exceptions).

Additional information regarding configuring redis:

We should set the maxmemory value to whatever devOps would think reasonable for the max to be used by our service.  (CONFIG GET maxmemory returns 0 in my local instance, which means unlimited)

We should set maxmemory-policy to probably allkeys-random (the default appears to be noeviction in my local machine)

See the proposal for the new timeouts. I would notify devOps for the deployment and update the spec doc for the gw.
https://github.com/gnosis/safe-client-gateway/issues/278

We would also have to agree in a cache configuration. Regarding maxmemory and maxmemory-policy.


Test the auth server via curl

Currently I got docker_auth server running properly with docker-registry v2 and openldap. I can login and set limitation to pull/push for different openldap users.
I'd like to set automation kitchen test which need test the auth server via curl access.
I follow Test the auth server , but can't make it work
It always reports auth failed. Then check the log, I found the key generated via command echo "USERNAME:PASSWORD" | base64 is different as the key i see in log
curl -H "Authorization: Basic $(echo "USERNAME:PASSWORD" | base64)" -vk "https://<IP_ADDRESS>:5001/auth?service=Docker%20registry&scope=registry:catalog:*"

If I replace the key which I got from log as below, I got token successfully.
curl -H "Authorization: Basic <KEY_IN_DOCKER_AUTH_LOG>" -vk "https://<IP_ADDRESS>:5001/auth?service=Docker%20registry&scope=registry:catalog:*"

Any hints for me to fix the curl command?

It looks like it is:
$(echo "USERNAME:PASSWORD" | base64) minus the last four characters when I checked the output vs. the auth log


[BEAM-4654] Treat timers as PCollections within proto representation in the Java SDK.

I abstracted away PTransform translation so that timers can be translated to PCollections since the existing translation mechanism required could only modify the FunctionSpec.
Note that I took this approach because changing the AppliedPTransform implementation to treat timers as an additional input and output would require updating all the non portable runners which did not seem worth the effort.
Once portability lands, we can go back and clean up several user and Runner facing interfaces which contain both user and Runner specific bindings.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

CC: @charlesccychen

Run Java PreCommit

R: @angoenka @axelmagn

Thanks!


Require to make changes in the concepts of Kubernetes

I don't think it is an issue but when I am reading this document I found that some basic concepts are not described properly.
One key concept of kubernetes is we can not create container directly, kubernetes is not restarting the container directly.
all these kind of work kubernetes do through the pod which is basic unit of kubernetes.
In Deployment, Also we are not deployed the container directly we did this by specifying pod definition for that containers.
Now read this where I thought changes are require:-

Self-healing Kubernetes restarts containers that fail, replaces containers, kills containers :- does it really restart the containers which failed or restart the pod which having the that container.
kubernetes does not replace the containers directly, it created the another pod (if fails by obvious reasons)  with same pod definition but assigning it
different IP.

/language en

/assign

/assign


description of choice hosting plan with Standard Logic App inconsistent

On the page it says, "Currently, only the Workflow Standard hosting plan is available for the Logic App (Standard) resource type and offers the following pricing tiers". How does this tie in with the option I get in VS Code, where I can choose between 'Workflow Standard' and 'App Service Plan' in the 'Select a hosting plan' dialog?
It seems to me the above quotation is also contradictory with another statement on the same page:
"When you create or deploy logic apps with the Logic App (Standard) resource type, you can use the Workflow Standard hosting plan in all Azure regions. You also have the option to select an existing App Service Environment v3 resource as your deployment location, but you can only use the App Service plan with this option. If you choose this option, you're charged for the instances used by the App Service plan and for running your logic app workflows. No other charges apply."
So what is it?
I should add that it's still unclear to me what the ramifications are if you choose for the WS hosting plan vs. the App Service. This seems to me to be vital information.
Cheers,
FerryMan-Coder

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

ID: 8d714050-c05a-cca9-ed86-fbd8ef223b4f
Version Independent ID: f02d2341-a0ad-19b1-edc1-d6f4f9cd3617
Content: Usage metering, billing, and pricing - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-pricing.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@FerryMan-Coder
Thanks for your feedback! We will investigate and update as appropriate.

@FerryMan-Coder: Thanks for your feedback! We're updating the docs to reflect that the App Service Plan applies only when you select an App Service Environment v3 for deployment, while the WS1, WS2, and WS3 plans apply when you select an Azure region for deployment.
An update should go live after 4 PM Pacific Time.


Adding Sandbox notebooks

This pull request will add notebooks developed for the DEA Sandbox to the general notebook repository for DEA.
Still to do:

test notebooks on GA-hosted sandbox to validate indexing
modify notebook content/formating to fit with needs of GA-hosted sandbox (e.g. dask_average_pixel_example.ipynb needs explanatory text).

Happy to take any other feedback and update as necessary! I'll leave this as a draft PR until we're ready.

This are fantastic notebooks, and are really the level of documentation we should try and include in all notebooks in dea-notebooks.
In the longer run (not necessary now):

We should probably add in the tags field we have in other notebooks (https://github.com/GeoscienceAustralia/dea-notebooks/blob/master/tags.rst) that allows them to show up in the index page on the DEA notebooks user guide (http://geoscienceaustralia.github.io/digitalearthau/genindex.html), so they're as discoverable as possible.
We also need to think about the best way to differentiate NCI notebooks from DEA Sandbox notebooks. Perhaps describing this clearly at the top of notebooks would be enough?

I'm now working on running the notebooks in the GA sandbox (https://app.sandbox.dea.ga.gov.au) before we perform this PR. This comment is to log data/package issues that I run into.
Case_Studies Notebooks:

Agriculture.ipynb: Sentinel-2 data are not available for the specified date/lat-lon range. Notebook relies on s2a/s2b_nrt_granule, which is listed as a product, but the data isn't appearing.
Coastal_Erosion.ipynb: Notebook relies on ls8_nbar_scene, which is not available. Could we update the notebook to use ga_ls8c_ard_3 instead, @robbibt?
Shipping_Lanes.ipynb: Dask client not working: OSError: Timed out trying to connect to 'tcp://dask-datacube-dask.odchub:8786' after 10 s: [Errno -2] Name or service not known. Might need to map to a different Dask client? Also need the s1_gamma0_geotif_scene product.
Water_Classification.ipynb: Need the s1_gamma0_geotif_scene product.

Code_Examples Notebooks:

dask_average_pixel_example.ipynb: Dask client not working: OSError: Timed out trying to connect to 'tcp://dask-datacube-dask.odchub:8786' after 10 s: [Errno -2] Name or service not known.

Dataset_Examples Notebooks:

WaterObservationsfromSpace_AnnualSummary.ipynb: WOfS annual summary data are not available for the specified date/lat-lon range. Notebook relies on wofs_annual_summary, which is listed as a product, but the data isn't appearing (Empty xarray after load).

Tutorial Notebooks:

02_Do_It_Yourself.ipynb: Sentinel-2 data are not available for the specified date/lat-lon range. Notebook relies on s2a_nrt_granule, which is listed as a product, but the data isn't appearing (Empty xarray after load).

High-level summary:

Need to check how s2a_nrt_granule, s2b_nrt_granule and wofs_annual_summary have been indexed and make sure data is available over the regions/times of interest for the relevant notebooks
Need to add the s1_gamma0_geotif_scene` product, as used in the DEA Sandbox: https://dashboard.dea-sandbox.test.frontiersi.io/s1_gamma0_geotif_scene
Rewrite of Coastal_Erosion.ipynb to use Collection 3 upgrade ls8 data (or index ls8_nbar_scene).
Fix the dask client issue

@alexgleith and @robbibt, could you please advise about how we should proceed to address each of these issues? Feel free to tag anyone else involved in the comments so we can keep track of what's happening.

@caitlinadams I'm as of the last few hours working on updating the Coastal_Erosion.ipynb notebook to work on the Collection 3 ga_ls8c_ard_3 because we need that notebook for a workshop next month. It should be ready soon, and work much more nicely as we'll have a full 30 years of data to play with. Only draw-back is that the current ga_ls8c_ard_3-style data is a test set scheduled for deletion soon, so there might be a short period between it being deleted and the final data being processed where the notebook breaks again

Regarding 02_Do_It_Yourself.ipynb with the missing Sentinel-2 data, I've also run into that same problem. I believe that @alexgleith has plans to index the threddsky Sentinel 2 data which comes from the NCI, which should make the entire Sentinel 2 time series available for the notebook

Hey folks
That notebook should be working with S2 NRT data... I'll check up on that.
It's much easier to get going than the Threddsky stuff :-)
On Tue, 30 Jul 2019 at 13:50, Robbi Bishop-Taylor<EMAIL_ADDRESS>wrote:

Regarding 02_Do_It_Yourself.ipynb with the missing Sentinel-2 data, I've
also run into that same problem. I believe that @alexgleith
https://github.com/alexgleith has plans to index the threddsky Sentinel
2 data which comes from the NCI, which should make the entire Sentinel 2
time series available for the notebook
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GeoscienceAustralia/dea-notebooks/pull/317?email_source=notifications&email_token=AA2JIXNORGL375DDVM24LW3QB63BJA5CNFSM4IHBROT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3CVPYA#issuecomment-516249568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2JIXJZRENOLVPKVM4OSJLQB63BJANCNFSM4IHBROTQ
.

--
Alex Leith
m:<PHONE_NUMBER>

@alexgleith Regarding the other required datasets that look like they're missing or not indexed on the Sandbox... should we be recording this in any official place other than here? e.g. as issues on another repository, or an email to someone specific?

@robbibt There wasn't any S2 NRT data indexed on DEA Sandbox .. I have started indexing S2 NRT along with Sentinel 2 Definitive .. will update you here once the indexing is complete

The dask issue should now be resolved. The GA sandbox is configured with a different name, so the client value is different. Dask should be working now, however, the calculation in the dask_average_pixel_example.ipynb notebook is taking much longer than it does in the FrontierSI sandbox. I'm just about to try running it again in the GA Sandbox, but it would be good if someone could check this too.

I've now confirmed that the data are available for all of the notebooks. Only remaining fixes are to get dask working on the sandbox, and to update any references of the DEA Dashboard (https://dashboard.dea-sandbox.test.frontiersi.io) to the DEA Explorer (https://explorer.dea.ga.gov.au). The Explorer needs to be updated to reflect the newly added data sets before this step can happen.
Additionally, I've added explanatory text to the Code_Examples/Dask_Average_Colour_Australia.ipynb notebook (https://github.com/GeoscienceAustralia/dea-notebooks/blob/caitlinadams/DEA_sandbox/Code_Examples/Dask_Average_Colour_Australia.ipynb). It would be great if someone could review this as part of this PR.

I've now marked this as ready for review. Happy to take any feedback on text/code inside notebooks before this is merged.

Note: we've deliberately not including some dea-notebook requirements like tags and index files because this needs some longer term thinking to work out how we want these AWS notebooks to show up on the user guide. For now, I think we can relax those rules for this pull request.

@caitlinadams I'll leave my small comments here as I go through the notebooks.
In the agricultural case study, I think this line is incorrect "It takes values from -1 to 1, with high values corresponding to dense vegetation" - it should be "It takes values from -1 to 1, with high values corresponding to healthy vegetation".
In the coastal erosion case study, the hyperlink in the description at the top doesn't work - 404 error.

@CEKrause The text is actually there, the html script that colours it in the notebook is failing to appear in github. @robbibt -- I like the colour, but should it be removed so all the text can be seen in github?

Because of how Python accesses other files, they have to be contained within the folder of the script that's accessing them. This could be fixed if utility functions were included as a Python package instead, but I think that's a significant amount of development.

@CEKrause That's a really good point... I guess the sandbox might need those scripts to run the notebooks, but it will only be reading in the dea-sandox subdirectory? Agree it's not an idea situation though

@caitlinadams  I like the text too, but I think we should probably get rid of it to reduce confusion when it doesn't render


[PE-D] Listing all members

So this is my list of members:

When I enter the command "find -mem -id 00000"
I get this:

I think since your members ids are automatically starts from 1, perhaps will be nice if user gets an error message for searching 00000. I guess this implementation is not wrong, but I think the error message will improve the overall experience.
Likewise when my entered id is > total list length, I get 0 members. Same comment as above!

Labels: type.FunctionalityBug severity.Medium
original: itsraveen/ped#4

Not a bug?
Id not equal to Index
Can indicate in the UG start from 1 if necessary

I think this issue is not related to index.
Will indicate the expected behaviour when an invalid member id in typed.


Added a new solution titled student grading

Added a solution in python.
Needs to be opened in jupyter notebook.

Thanks in advance.

Sorry, not opening pull requests at this time.


Add FAQ: fault_tolerant_name_handling

Internal Tracking ID: EXPOSUREAPP-12153

We might still add some details about the rules of the fault tolerant mechanism. Stand by.

Looks good so far!
The PR depends on the blog article blog/2022-03-16-cwa-version-2-19 which is currently absent. Until this is provided there will be a dead link.

@larswmh
It seems in Android release/2.19.x, that the literal text "DR" is ignored. I'm not sure whether "Dr." (with a dot is also ignored) - probably yes, if "." is converted to "<" though. Maybe worth checking because the test cases don't include "DR." (with a dot)?
See https://github.com/corona-warn-app/cwa-app-android/blob/a74dc73a8df7d164eac438f7210ed80658e2c015/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/common/certificate/CertificatePersonIdentifier.kt#L101-L120
/*
Function sanitize names according to the following requirements:

- dots `.` and dashes `-` shall be replaced by `<`
- the string shall be converted to upper-case
- German umlauts `Ä/ä`, `Ö/ö`, `Ü/ü` shall be replaced by `AE`, `OE`, `UE`
- German `ß` shall be replaced by `SS`
- the string shall be trimmed for leading and training whitespace
- the string shall be trimmed for leading and trailing `<`
- any whitespace in the string shall be replaced by `<`
- any occurrence of more than one `<` shall be replaced by a single `<`

Name fields shall be split into components as follows:

- the string shall be split by `<`
- components with the value `DR` shall be filtered out
 */
private fun String.sanitizeName(): List<String> {
    val filteringList = listOf("DR")
    return uppercase()

from PR https://github.com/corona-warn-app/cwa-app-android/pull/4858

@MikeMcC399 As we understand it, "Dr." is also ignored because, for example, at the beginning of the comment it is mentioned that the dot is removed, the string is converted to uppercase, and then later "DR" is removed. We think that the current wording is sufficient

@MikeMcC399 Thanks for review!


Follow a collaborator's viewport

Starting on #218

please update snapshots

Thanks!
I'm not sure how the visual regression tests are passing.
For me the map is always opening at the same initial position, not respecting the position saved in the file anymore:

It looks like view.animate is undefined at first? So the lat/lng was getting reset to 0. I'm gonna assume the regression tests are slow enough that it wasn't an issue with them. Adding a check and setCenter/setZoom as a fallback seems to work.


Missing escaping of ? in note titles in manifest.xml for tomboy-ng 0.23

I'm using tomboy-ng 0.23 on Windows. I had a note with a title like Foo "Text"?. Then I deleted it. In manifest.xml, this leads to an entry like
<note-deletions>
  <note guid="73A8C215-B3F7-4331-B449-EE8C36A9001E" title="Foo "Text"?" />
</note-deletions>

. When trying to delete another note, this leads to a crash with a message about expecting whitespace at a certain position.

Hmm, that sounds like a bad miss by me. Those double inverted commas definitely should not make it into the xml.
As a stop gap, I suggest you delete the offending note on each machine and edit their manifest files.   I'll look through the code and it should be trivial to fix but won't me in a position to do a full test and release cycle for a couple of months. I'm traveling and don't have my Mac in particular nor my build and test machine.
Thanks for spotting this Erik, its a nasty one.
Davo

Yep, the issue, I think, is more about the double quote than the question mark.
In the Tomboy Note XML, " and ' do not need to be escaped as the note data is not presented as an attribute.  And I am being quite careful to maintain compatibility with Tomboy. However, the manifest files are not in TB note format, its general XML.  I am not sure how TB would react to a note named like that, I don't have my TB install with me and won't be home for several months.
But I am using (in tomboy-ng) std  XML tools to read the manifest files and they are going to choke on finding more than two double quotes in an attribute.
I am not sure how to handle this, I don't want to extend line number 163 of syncutils -
function RemoveBadXMLCharacters(const InStr : ANSIString) : ANSIString;
to also escape ' and " because that may (or may not ? ) introduce a Tomboy incompatibility into our notes. But I must stop them getting through into the manifest file where it ends up as an attribute.
Further research is indicated .......

Erik, I have committed a fix for this (as mentioned above). But won't be releasing a version for some months. Do you want me to cut you a Linux64 binary of were we are now ?
It will be v0.23 plus your fix (well tested) and a not so well tested set of changes trying to get a dark theme for windows that "should" have no impact on Linux at all. And a couple of unnecessary debug messages silenced...
Davo

Removing the title attribute from the XML manifest file works for me as a workaround for now. I'll wait for the next regular release to get the bug fix.
Thank you.

Fixed in v0.24, thanks for report.


TimeoutException does not subclasses

TimeoutException doesn't seem to subclass ErrorReturnCode as documented, see https://github.com/amoffat/sh/blob/master/sh.py#L394
Would be good to make it a subclass of ErrorReturnCode so that when catching this exception, full_cmd is available for logging purpose.

@amoffat Would you prefer to fix the code to inherit from ErrorReturnCode (see https://github.com/amoffat/sh/blob/develop/sh.py#L406), or fix the documentation (see https://github.com/amoffat/sh/blob/gh-pages/_docs_sources/sections/command_class.rst#timeoutexception)?

With https://github.com/amoffat/sh/pull/447 merged, I say it's probably "good enough" to just fix the docs.  Do you want to take that one @ecederstrand?  There is a gh-pages-release-1.12.15 branch I've been adding to for the next release.

I agree. A process timeout is not a return code, since the process did not exit by itself.


Use of org.json incompatible with latest Selenium code

Selenium replaced its uses of org.json with gson in this revision:
https://code.google.com/p/selenium/source/detail?r=2997a70d5872ff1f228a833f062ea32af05dca6b
That breaks ios-driver pretty seriously. Now attempts to find elements result in a ClassCastException:
org.openqa.selenium.WebDriverException: Returned value cannot be converted to WebElement: {class=org.json.JSONObject, hCode=1526533815}
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:359)
...
Caused by: java.lang.ClassCastException: com.google.common.collect.Maps$TransformedEntriesMap cannot be cast to org.openqa.selenium.WebElement
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:357)

I can reproduce this problem with the Grid plugin (ios-grid-plugin-0.6.6-SNAPSHOT.jar) and Selenium 2.44.
It works with Selenium 2.43.1.

@mach6
If no one has got to it, let me see if I can give this a try.

Same exception with Selenium 2.44. I have to use 2.43.1 now


TypeError: 'NoneType' object is not iterable

Hi!
English word "organic" is giving me that error, if i use "organic ok" it work fine

other words work just fine!
any clue?
thanks in advanced!

Thanks for reporting the issue.
I did a quick fix in the repo but have yet to update pypi. It will likely take some time to update pypi since the package name will have to be changed.
In the meantime, you may try to install it directly from the repo, e.g.,
pip install  git+https://github.com/ffreemt/google-stranslate

Note the s in stranslate.
Please let me know should there be other issues.
Thanks.

Hello, I have the same issue. I installed it through git+https://github.com/ffreemt/google-stranslate, but it didn't fix the trouble

It works once, but after it, stops working.
Thanks!


WIP - Update bindings to Feb 20th 2019 gtfs-realtime.proto

Work-in-progress pull request - Please do not merge
TODO:

[X] Java bindings
[X] .NET
[x] JavaScript / Node.js
[x] Python
[x] Golang
[ ] PHP - Deprecate? See https://github.com/google/gtfs-realtime-bindings-php/pull/4
[ ] Ruby - Deprecate? See https://github.com/google/gtfs-realtime-bindings/issues/44

@barbeau will this be getting merged anytime soon and pypi version updated? Patiently waiting for the severity_level message!

@doellerbe06 Yes, goal is to merge and release this within the next few weeks.  We're dealing with some one-time administrative setup on our end to be able to re-generate the bindings and publish releases, so hopefully the process will be faster in the future.  The long-term goal is to automate this so it's always in lock-step with the gtfs-realtime.proto in https://github.com/google/transit.

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


Newtonsoft not found

in UnityMessageManager it does not find Newtonsoft.JSON
how to add this properly?

Hi macrozone,
You can see a sample with all necessary files here: https://github.com/f111fei/react-native-unity-demo

https://github.com/f111fei/react-native-unity-demo/tree/master/unity/Cube/Assets/Scripts/Newtonsoft.Json

thx guys! can we have this in the readme?

@macrozone  Sure，But I busy with other things. Can you create a PR ?


Conan new update

feel like conan got new version since i want build the project is failed check it out https://github.com/ZTzTopia/GTProxy/actions/runs/3807347178/jobs/6476949622#step:4:1224

Yes, Conan updated to version 2.0.0 and cmake-conan still not updated for Conan version 2.0.0.

Yes, Conan updated to version 2.0.0 and cmake-conan still not updated for Conan version 2.0.0.

yep is work using 1.55.0 conan version is working