Change Open Liberty default profile to kernel

Summary

Changing the default Open Liberty profile from full to kernel.
Use Cases

The kernel profile contains the minimal features needed to run the Open Liberty server.  Users will need to use the BP_LIBERTY_FEATURES environment variables to list the additional features need by the application.  The buildpack will then download and install the features.  This minimizes the size of the container and avoids including unnecessary features.   The matches the process used when the WebSphere Liberty runtime is used.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

I discussed this with @dmikusa previously.   Since it is a breaking change we added this warning in August:
Warning: The default profile for Open Liberty will change from 'full' to 'kernel' after 2022-11-01. To continue using the full profile, build with the argument '--env BP_LIBERTY_PROFILE=full'")

The next Liberty release is scheduled to available around Nov 22.   We can include this change when we build then and I assume bump the version to 3.0.


Block parcel entry until all physics have loaded

We could possibly also prioritize physics/physics_url in the loading.

Fixed.


Some functions should be rewritten into methods

For example this three can be methods for *Window, *Surface and *GameController:
// CreateRenderer returns a new 2D rendering context for a window.
// (https://wiki.libsdl.org/SDL_CreateRenderer)
func CreateRenderer(window *Window, index int, flags uint32) (*Renderer, error) {...}

// CreateSoftwareRenderer returns a new 2D software rendering context for a surface.
// (https://wiki.libsdl.org/SDL_CreateSoftwareRenderer)
func CreateSoftwareRenderer(surface *Surface) (*Renderer, error) {...}

// GameControllerMapping returns the current mapping of a Game Controller.
//  (https://wiki.libsdl.org/SDL_GameControllerMapping)
func GameControllerMapping(ctrl *GameController) string {...}

You can find more with this regexp expression:
^func [A-Z][a-zA-Z_0-9]+\([a-zA-Z_0-9]+ \*[a-zA-Z_0-9]

I speak only for CreateRenderer, please don't do it. Just because renderer needs a window to draw doesn't make it window's method. It's a different animal.
A window should have methods only to manipulate that window. Any objects should have methods only to manipulate itself. Some external objects may want to use your window object, in this case a renderer, so be it. But they are not your concern. You cannot write a new method for your window every time somebody uses it to init their object.
For instance, bytes.NewBuffer is not a method of []byte.
Just look at the code, i think it looks weird.
renderer := window.CreateRenderer()

renderer.Clear(...)
renderer.Copy()
renderer.DrawRect(...)
renderer.Present(...)

renderer.Destroy(...)

Please remember i didn't check any other function, i merely talk about CreateRenderer. It might be a great proposal overall.
Thanks for great job.

@dodobyte if this is the case for object creation, then we have some rogue methods that already do this as methods.
// CreateTexture returns a new texture for a rendering context.
// (https://wiki.libsdl.org/SDL_CreateTexture)
func (renderer *Renderer) CreateTexture(format uint32, access int, w, h int32) (*Texture, error) {...}

// CreateTextureFromSurface returns a new texture from an existing surface.
// (https://wiki.libsdl.org/SDL_CreateTextureFromSurface)
func (renderer *Renderer) CreateTextureFromSurface(surface *Surface) (*Texture, error) {...}

This one is weird, not a simple getter. Though I'd rather leave is as it is now.
// GetSurface returns the SDL surface associated with the window.
// (https://wiki.libsdl.org/SDL_GetWindowSurface)
func (window *Window) GetSurface() (*Surface, error) {...}

A new surface will be created with the optimal format for the window, if necessary. This surface will be freed when the window is destroyed. Do not free this surface.
This surface will be invalidated if the window is resized. After resizing a window this function must be called again to return a valid surface.

We need to decide what to do with those.

This one definitely needs to be rewritten, since its a simple getter:
// GameControllerMapping returns the current mapping of a Game Controller.
//  (https://wiki.libsdl.org/SDL_GameControllerMapping)
func GameControllerMapping(ctrl *GameController) string {...}

@malashin, i see. Consistency is more important than anything else. SDL doesn't imply what should be a method of what. But there are some hints in documentation, namely categories.
I believe the original creator of this library also took categories into consideration. File names show that.
API's in CategoryRender should be methods of *Renderer. The creator function is CreateRenderer, so it must be a top level function, not a method.
CreateTexture and CreateTextureFromSurface functions are in the Render category, so the current configuration is correct for them.
One may argue that CreateTextureFromSurface must be a method of *Surface. In this case we must ask two questions.

What is the first parameter? Is it *Renderer or *Surface. The first parameter must be the receiver. For this case *Renderer.
What is the function's category? For this case CategoryRender.

So it should be obvious.
Window functions such as CreateWindow are found in CategoryVideo. Again, the creator function CreateWindow should be a top level.

Finally, CreateRenderer. Should it be a method of *Window or a top level function. Let's ask the questions.

Is function's first parameter a *Window? Check.
Is function in the CategoryVideo? No.

So it's not a method of *Window.
For CreateRenderer it's not hard to decide because it's the creator function of a whole category. But for less obvious ones this two questions can help you to decide.
Thanks.

I fixed the GameControllerMapping() first as it definitely needs to be made a method.
I'm not really sure about what to do about the rest. Both of you have some valid points. I think we should wait until there's a strong case for either of the options before we make further changes. If it is already working okay for everyone then we don't need to make any changes. I was thinking of providing both options (method and function) but I guess people wouldn't like that in the long run :P

First of all, the reason which @dodobyte mentioned (function's category) is not a good point to consider it seriously. Renderer has its own category just because it is big enough to have it.
Further I will try to give a reason why @malashin is right:

Renderer is actually part of Window struct (inside SDL library).
Window is not "just an argument". Renderer can't have normal functionality after destroying the Window from which it was created.
One Renderer can have output only to one Window. Window doesn't let you create more than one Renderer.
Renderer can't change/rebind/reattach/etc its Window. When Renderer loses a Window it loses functionality.
If we set Renderer's target (SetRenderTarget) to a texture. It doesn't mean that we detached it from Window. It means that we just redirected a Renderer's output to a texture. If we destroy a Renderer's Window then Renderer will lose functionality.
If we set Renderer's target to NULL then Renderer restores an output to a Window from which it was created.

I think it transparently shows up 'HAS-A' relations. I.e:

Renderer has Textures so CreateTexture is a part of Renderer.
Window has Renderer so by consistency reasons CreateRenderer should be a part of Window.


Changes preparing for a compatible release with 0.6.0

Add license. Add pyproject file. Update CI
@jpdean if you want another license, feel free to change it.

I cannot make the C++ trilinos code work with docker v0.6.0-r1 as  is missing in 0.6.x in some places in C++.
I will there not update those files in this PR, see next PR for more.


Link to librt on non-apple platforms

This breaks compilation on android. We should really be using build.rs here too.


Update metas.yml

add props : showLoading
Please makes sure the items are checked before submitting your PR, thank you!

[x] Only One commit
[x] No eslint errors
[ ] Rebase before creating a PR to keep commit history clear.

thx

my pleasure


Workflow trigger twice of same logical event

🐛 Summary
Run_PowerShell_Test workflow executes twice when Pushing a change to a PR in review.
To reproduce
Steps to reproduce the behavior:

Have branch in review for PR
Push a PowerShell change to branch

Expected behavior
Expect workflow to only run once (ignore extra trigger)
Any helpful log output or screenshots

Reviewed 12/14
I set the size to small since it seems like an easy fix. @crutchfield needs to verify and update the size if necessary.
Assuming the size is small, I put the priority as high since it is inefficient to run the tests twice.

Reviewed 12/14
I set the size to small since it seems like an easy fix. @crutchfield needs to verify and update the size if necessary. Assuming the size is small, I put the priority as high since it is inefficient to run the tests twice.

I think size is good.  Not saying this is answer but suggests it is small.

This was addressed by me several months ago.  Look in the workflows for this comment (# This condition prevents duplicate runs.), and you will see the fix.
See #805.


Add jsfiddle example with cdn and fixed the docs a little.

I added a jsfiddle example I have been working on. It works in IE > 8 and chrome and uses cdn content, font-awesome and has multiple buttons.
Also a boo boo in the docs.

Superseded by commit f0263698a4123376bb46bbd814fd968f48b9def1, which includes links for JSFiddle (etc.) "starter snippets" using the v2.x API.  These new starters also deal with JSFiddle (et al)'s recent integration of the HTML5 iframe sandboxing attribute that completely disables native plugins like Flash as best as possible.

Superseded by commit f0263698a4123376bb46bbd814fd968f48b9def1, which includes links for JSFiddle (etc.) "starter snippets" using the v2.x API.  These new starters also deal with JSFiddle (et al)'s recent integration of the HTML5 iframe sandboxing attribute that completely disables native plugins like Flash as best as possible.


Add cFE Application Behavior API functional tests

Is your feature request related to a problem? Please describe.
Need open source functional tests for certifiability
Describe the solution you'd like
Add cFE Application Behavior API functional tests
– CFE_ES_RunLoop - Check for Exit, Restart, or Reload commands.
– CFE_ES_WaitForStartupSync - Allow an Application to Wait for the "OPERATIONAL" global system state.
– CFE_ES_WaitForSystemState - Allow an Application to Wait for a minimum global system state.
– CFE_ES_IncrementTaskCounter - Increments the execution counter for the calling task.
– CFE_ES_ExitApp - Exit a cFE Application.
Describe alternatives you've considered
N/A
Additional context
N/A
Requester Info
Jacob Hageman - NASA/GSFC
EDIT by @skliper: removed CFE_ES_RegisterApp since it no longer exists.

Depending on the testing goals it may require some creativity in the test structure, such as starting a separate/dedicated app to call these APIs - or perhaps even several apps.
The general "cfe_testrunner" app already registers itself using CFE_ES_RegisterApp() and CFE_ES_WaitForStartupSync() which in turn calls CFE_ES_WaitForSystemState() (the former being just a simplified form of the latter) so attempts to call these directly in a later functional test script will result in no effect.  Likewise the CFE_ES_ExitApp will actually exit the app, so it isn't something that should be done from the context of the generalized test runner app.

Caelum test scenario/pseudo-code brainstorming (future work could enhance testing w a companion app: #1761, but not required this round):
CFE_ES_GetTaskInfo and save the ExecutionCounter
Confirm CFE_ES_RunLoop(&RunStatus) returns true with RunStatus set to CFE_ES_RunStatus_APP_RUN
NOTE - depending on #1762, may add check of RunStatus... for now though the API claims it's just input
CFE_ES_GetTaskInfo and confirm ExecutionCounter increments by 1
assert VOID macro on CFE_ES_IncrementTaskCounter
CFE_ES_GetTaskInfo and confirm ExecutionCounter increments by 1
Technically for CFE_ES_RunLoop should also send the other valid codes (EXIT/ERROR) which right now is OK from the functional test based on implementation but not really documented in the API to not actually do anything except return false... so debatable since we wouldn't want to actually trigger an exit.
Also call CFE_ES_WaitForSystemState for each possible system state, anything less than the expected current should return CFE_SUCCESS, anything greater than current should return CFE_ES_OPERATION_TIMED_OUT
Call CFE_ES_WaitForStartUp (void).  Good to check that time elapsed (before/after) is < timeout which would show it didn't time out.
Skip CFE_ES_ExitApp for now from the functional test since that would be better using #1761.  Maybe we could add a call to it from sample_app based on some criteria just to show it works?  Would be useful to provide an actual use case (if there is one) example from the sample context, since it seems somewhat questionable based on current implementation (the app could just end the main loop).

FWIW, the testcase app does call CFE_ES_ExitApp at the end of its run, but it just doesn't get into the log for obvious reasons.
Suggestions for the other APIs seem reasonable enough.
At some point, we probably will have to introduce a second test app that the main test app can start on demand, which would also help for the reload/restart cases, but hopefully that level of detail can be postponed till the next cycle.


Create SECURITY.md

Description

Resolves # (issue)
How Has This Been Tested?

Due Diligence

[x] Breaking change
[x] Requires a documentation update
[x] Requires a e2e/integration test update

Whats is the reason for SECURITY.md cc @DGBgithub ?

cc @DGBgithub I should close your PR, because there is no description of the changes and no reply.


Webpack Raw Loader for TXT files?

Hi, please,
how to add Webpack Raw Loader for TXT files?
I have tried all the tricks suggested here #433, here #1030 and here #297 and still don't know.
I would like simply import the static content of TXT files from codebase into variables.
Thank you Razzle :)

@fivethreeo can you help us with this?

Use !!raw-loader to ignore rules.
import txt from '!!raw-loader!./file.txt';

We could add a configurable razzle plugin that can add filetypes with exclusions and optionally use resourceQuery to load as raw and base64 with something like 'file?as-string-variable' , 'file?as-base64-variable’, or just move more functionality in razzle to plugins and ship with some  plugins loaded by default


configure probes

consider how to configure probes when deploying
livenessProbe:
  httpGet:
    path: /
    port: http
readinessProbe:
  httpGet:
    path: /
    port: http

Any progress on this issue? We are just trying to knctl deploy a service which has a non-standard health endpoint. It would be very helpful if we could configure the readiness and liveness probes.

@jochenehret is it just the endpoint configuration your are interested in, or other additional configuration as well (as defined in https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)?

Hi @cppforlife,
I think we need host, scheme, path and port for now.


Hotreload: Ability to update templates without recompiling

This is a continuation of #392, it adds a way to auto-reload templates to maud without going through rustc at all, for some situations.
Basic usage
Enable the hotreload feature, and the html! macro will partially evaluate at runtime. use maud::html_static! to force the "normal", fully-compiled behavior.
You can use export MAUD_ON_ERROR=exit to make maud call std::process::exit during template-rendering whenever it turns out the code changes are too severe for hot-reloading. In combination with cargo watch, this can hot-reload your web app's templates when possible, and recompile when that fails:
MAUD_ON_ERROR=exit  cargo watch --no-restart -x run --features hotreload

This has some limitations because now rust code changes unrelated to templates will not cause the application to restart. Needs further improvements.
Internals
maud+hotreload will compile your template into two parts:

a list of "formatting arguments" where all the rust code in templates is eagerly evaluated
a runtime that opens the sourcecode found via file!(), tries to parse out the original macro invocation, and attempts to use the existing "formatting arguments" with that

This means that changes such as this can be hot-reloaded:
// before
html! {
    "Hello " (world) "!"
}

// after (no recompilation needed, as only static content changed)
html! {
    "Goodbye " (world) "!"
}

but this change requires proper recompilation:
// before
html! {
    "Hello " (world) "!"
}

// after (recompilation needed, as rust code changed)
html! {
    "Hello " (other_world) "!"
}

the compiled code is very inefficient, as it re-parses rust sourcecode at runtime (still faster than rustc). there are some complications, such as the hot-reloading:

not working in doctests
not working whenever the html! macro is aliased or used from within another macro
not working when html! { } is written in a weird way, such as html! /* { */ {

Is this really for maud?
Even though there are no added dependencies, the feature is still a lot to maintain and required a lot of restructuring. I think most of the restructuring was unavoidable, and now there are three crates instead of two.
I don't necessarily have expectations that this will be merged, but on the other hand I also really want a template engine that is type-safe, has fast iteration-speeds and can be composed in a JSX-like way using regular Rust functions. I think maud+hotreload is the only standalone templating engine in the Rust ecosystem that can do that right now. So I'd be willing to fork maud and continue development there if people are interested. It seems there are a few other PRs that need attention anyway.
finally, thanks to @wrapperup for the initial prototype and architecture of hot-reloading.

This is exactly the feature I’m looking for!
Following 🍿🍿

This is a great contribution! Exactly what I'm looking for. I'm in favour of a fork with new contributors if this isn't being actively maintained.


auth: tie identities to client certificates

The new auth feature in etcd 2.1.x lets users have users and roles to control access to the key space. It would be great to be able to pin a user to a client certificate too instead of requiring a client cert and a secret token.

#3916 makes a pass at implementing this using certificate common name

closed by https://github.com/coreos/etcd/pull/5991


Possible race condition on PortStatus handler

Hi,
There is a possible race condition on the PortStatus handler, which leads to an interface/link becoming DOWN forever after a number of flaps on some interfaces. Basically, if the controller receives multiple PortStatus report a port is UP and DOWN in a very short period of time (ex: more the 6 events within a second), it might lead the controller to not correctly set the interface status.
How to reproduce: using the Mininet topology for AmLight (https://github.com/kytos-ng/kytos-end-to-end-tests/blob/master/tests/helpers.py#LL14C2-L14C2), try to force multiple events of port UP and down within a second:
ip link set down Ampath1-eth1; ip link set up Ampath1-eth1;ip link set down Ampath1-eth1; ip link set up Ampath1-eth1

In a normal situation, the links should go down and UP:
kytos $> 2023-05-12 20:05:26,688 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state 0
2023-05-12 20:05:26,693 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LINK_DOWN
2023-05-12 20:05:26,718 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state 0
2023-05-12 20:05:26,729 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LINK_DOWN
2023-05-12 20:05:26,827 - INFO [kytos.napps.kytos/mef_eline] (thread_pool_app_20) Event handle_link_down Link(Interface('Ampath1-eth1', 1, Switch('00:00:00:00:00:00:00:11')), Interface('Ampath2-eth1', 1, Switch('00:00:00:00:00:00:00:12')))
2023-05-12 20:05:26,858 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LIVE
2023-05-12 20:05:26,865 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state 0
2023-05-12 20:05:26,869 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LINK_DOWN
2023-05-12 20:05:26,876 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LIVE
2023-05-12 20:05:26,880 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state 0
2023-05-12 20:05:26,884 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LINK_DOWN
2023-05-12 20:05:26,955 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LIVE
2023-05-12 20:05:26,989 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LIVE
2023-05-12 20:05:37,158 - INFO [kytos.napps.kytos/mef_eline] (thread_pool_app_18) Event handle_link_up Link(Interface('Ampath1-eth1', 1, Switch('00:00:00:00:00:00:00:11')), Interface('Ampath2-eth1', 1, Switch('00:00:00:00:00:00:00:12')))

However, if you keep executing the command above (ip link set...), you may eventually end up in a situation where the interface is never activated again and the link_up event is never triggered.
kytos $> 2023-05-12 20:08:41,182 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state 0
2023-05-12 20:08:41,199 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LINK_DOWN
2023-05-12 20:08:41,276 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state 0
2023-05-12 20:08:41,312 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LINK_DOWN
2023-05-12 20:08:41,327 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LIVE
2023-05-12 20:08:41,357 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LIVE
2023-05-12 20:08:41,366 - INFO [kytos.napps.kytos/mef_eline] (thread_pool_app_16) Event handle_link_down Link(Interface('Ampath1-eth1', 1, Switch('00:00:00:00:00:00:00:11')), Interface('Ampath2-eth1', 1, Switch('00:00:00:00:00:00:00:12')))
2023-05-12 20:08:41,399 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state 0
2023-05-12 20:08:41,419 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LINK_DOWN
2023-05-12 20:08:41,453 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:12:1 state OFPPS_LIVE
2023-05-12 20:08:41,491 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state 0
2023-05-12 20:08:41,529 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LINK_DOWN
2023-05-12 20:08:41,537 - INFO [kytos.napps.kytos/of_core] (MainThread) PortStatus modified interface 00:00:00:00:00:00:00:11:1 state OFPPS_LIVE
2023-05-12 20:08:41,583 - INFO [kytos.napps.kytos/mef_eline] (thread_pool_app_0) Event handle_link_down Link(Interface('Ampath1-eth1', 1, Switch('00:00:00:00:00:00:00:11')), Interface('Ampath2-eth1', 1, Switch('00:00:00:00:00:00:00:12')))
2023-05-12 20:08:41,590 - INFO [kytos.napps.kytos/mef_eline] (thread_pool_app_41) Event handle_link_down Link(Interface('Ampath1-eth1', 1, Switch('00:00:00:00:00:00:00:11')), Interface('Ampath2-eth1', 1, Switch('00:00:00:00:00:00:00:12')))
2023-05-12 20:08:41,913 - INFO [kytos.napps.kytos/mef_eline] (thread_pool_app_15) Event handle_link_down Link(Interface('Ampath1-eth1', 1, Switch('00:00:00:00:00:00:00:11')), Interface('Ampath2-eth1', 1, Switch('00:00:00:00:00:00:00:12')))

The following patch seems to improve a bit the situation:
root@1534638afadd:/src/kytos-of-core# git diff main.py
diff --git a/main.py b/main.py
index b8b8dff..07c2e13 100644
--- a/main.py
+++ b/main.py
@@ -2,6 +2,7 @@

 import asyncio
 import time
+import threading
 from collections import defaultdict

 from napps.kytos.of_core import settings
@@ -45,6 +46,7 @@ class Main(KytosNApp):
         self.of_core_version_utils = {0x04: of_core_v0x04_utils}
         self.execute_as_loop(settings.STATS_INTERVAL)
         self._connection_lock = defaultdict(asyncio.Lock)
+        self._port_status_lock = defaultdict(threading.Lock)

         # Per switch delay to request flow/port stats, to avoid all request
         # being sent together and increase the overhead on the controller
@@ -604,55 +606,58 @@ class Main(KytosNApp):
         port_no = port.port_no.value
         event_name = 'kytos/of_core.switch.interface.'

-        if reason == 'OFPPR_ADD':
-            status = 'created'
-            interface = Interface(name=port.name.value,
-                                  address=port.hw_addr.value,
-                                  port_number=port_no,
-                                  switch=source.switch,
-                                  state=port.state.value,
-                                  features=port.curr)
-            source.switch.update_interface(interface)
-            try_to_activate_interface(interface, port)
-
-        elif reason == 'OFPPR_MODIFY':
-            status = 'modified'
-            interface = source.switch.get_interface_by_port_no(port_no)
-            current_status = None
-            if interface:
-                current_status = interface.state
-                interface.state = port.state.value
-                interface.name = port.name.value
-                interface.address = port.hw_addr.value
-                interface.features = port.curr
-            else:
+        intfid = f"{source.switch.id}:{port_no}"
+
+        with self._port_status_lock[intfid]:
+            if reason == 'OFPPR_ADD':
+                status = 'created'
                 interface = Interface(name=port.name.value,
                                       address=port.hw_addr.value,
                                       port_number=port_no,
                                       switch=source.switch,
                                       state=port.state.value,
                                       features=port.curr)
-            source.switch.update_interface(interface)
-            try_to_activate_interface(interface, port)
-            self._send_specific_port_mod(port, interface, current_status)
-
-        elif reason == 'OFPPR_DELETE':
-            status = 'deleted'
-            interface = source.switch.get_interface_by_port_no(port_no)
-            interface.deactivate()
-
-        event_name += status
-        content = {'interface': interface}
-
-        event = KytosEvent(name=event_name, content=content)
-        self.controller.buffers.app.put(event)
+                source.switch.update_interface(interface)
+                try_to_activate_interface(interface, port)
+
+            elif reason == 'OFPPR_MODIFY':
+                status = 'modified'
+                interface = source.switch.get_interface_by_port_no(port_no)
+                current_status = None
+                if interface:
+                    current_status = interface.state
+                    interface.state = port.state.value
+                    interface.name = port.name.value
+                    interface.address = port.hw_addr.value
+                    interface.features = port.curr
+                else:
+                    interface = Interface(name=port.name.value,
+                                          address=port.hw_addr.value,
+                                          port_number=port_no,
+                                          switch=source.switch,
+                                          state=port.state.value,
+                                          features=port.curr)
+                source.switch.update_interface(interface)
+                try_to_activate_interface(interface, port)
+                self._send_specific_port_mod(port, interface, current_status)
+
+            elif reason == 'OFPPR_DELETE':
+                status = 'deleted'
+                interface = source.switch.get_interface_by_port_no(port_no)
+                interface.deactivate()
+
+            event_name += status
+            content = {'interface': interface}
+
+            event = KytosEvent(name=event_name, content=content)
+            self.controller.buffers.app.put(event)

-        # pylint: disable=protected-access
-        state_desc = {v: k for k, v in PortState._enum.items()}
-        # pylint: enable=protected-access
-        state = state_desc.get(port.state.value, port.state.value)
-        msg = 'PortStatus %s interface %s:%s state %s'
-        log.info(msg, status, source.switch.id, port_no, state)
+            # pylint: disable=protected-access
+            state_desc = {v: k for k, v in PortState._enum.items()}
+            # pylint: enable=protected-access
+            state = state_desc.get(port.state.value, port.state.value)
+            msg = 'PortStatus %s interface %s:%s state %s'
+            log.info(msg, status, source.switch.id, port_no, state)

 def _get_version_from_bitmask(message_versions):

However, we still have some corner cases where the state is inconsistent on Kytos (no link_up event and the stored status is different from the switch status):

stored:

root@1534638afadd:/src/kytos-of-core# curl -s http://<IP_ADDRESS>:8181/api/kytos/topology/v3/interfaces | jq -r '.interfaces[] | .id + " " + (.active|tostring)' |grep false
00:00:00:00:00:00:00:12:1 false

switch status:

kytos $> controller.switches['00:00:00:00:00:00:00:12'].interfaces[12].status
Out[4]: <EntityStatus.UP: 'UP'>


Internal viewer build fix and CI updates

The most recent improvements to the internal viewer didn't make it into the v0.12.0 release due to the updated bindata not being committed to the repository. This PR updates the bindata, improves the build instructions, and adds a check to the CI to make sure generated code is always committed.

Pull Request Test Coverage Report for Build b20dc4f60-PR-718

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 45.606%

Totals

Change from base Build 91c8ea1fc:
0.0%

Covered Lines:
5382

Relevant Lines:
11801

💛  - Coveralls


Make #747 happy: Add LIST functionality for z/OS JES subsystem

Issue #747: Please read (especially at the end) or in the Wiki: here
Added FtpZOSListRealm.Jes2.
Added the capability to parse this realm.
Needed to add a listing option to deter GetListing(...) from switching to Image, we need this process to stay in ASCII.

I am closing this to make it anew, I hadn't merged the surprsingly new master, got conflicts.
I will open it again, that will be cleaner.


API method GetItems with paged CAML query does not return paging information

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Querying list items using a POST request to /_api/Web/Lists/getByTitle('MyList')/GetItems with POST data:
{
    "query": {
        "ViewXml": "<View><RowLimit Paged='TRUE'>1</RowLimit></View>"
    }
}

gives the following response:
{
    "odata.metadata": "https://savillsukdev.sharepoint.com/sites/cpa-ci/_api/$metadata#SP.ApiData.ListItems",
    "value": [
        { ... }
    ]
}

Though the results appear to be paged (only one item returned), no paging information is included in the response object. I would expect to receive alongside the list items a ListItemCollectionPosition property that would include a PagingInfo string (as per the Client Object Model) which I can then use to retrieve the next batch (if any).
The data type returned by the query is SP.ApiData.ListItems which is not mentioned in the API Index and in fact should probably return a ListItemCollection which would include the paging information.
Please can you clarify?

I am also looking for a fix for this issue.   Is there any update on a resolution or workaround to get the ListItemCollectionPosition?

+1.  I need this, too.

I need this, too… :(


Trim Trailing Zeros

I believe that the Makefile logic has the inverse effect on the behavior of the radio. When ENABLE_TRIM_TRAILING_ZEROS := 0 the trailing zeros are trimmed and when ENABLE_TRIM_TRAILING_ZEROS := 1 the trailing zeros are visible.

That can't be ??

It's set to '1' for me, the trailing zeros are gone.

Post an image if you can.

Interestingly, I've just compiled it with the option enabled and disabled and the VFO shows the trailing zeros either way.
With it set to '1'

With it set to '0'

ah, i see !
I haven't yet got to removing the trailing zeros from the bug frequency read outs, done the smaller mode ones though.

You use big font mode, I should really do that myself on and off to test things out, but never do.

And now that you say that, I see too :smiley: I noticed the trailing zeros were gone when I merged your changes (including having the BIG_FREQ disabled).
As for testing with big font mode, it's your firmware for your end user experience, you shouldn't have to! Haha

Just a question based on your experience with the code, does this feature operate such that it doesn't paint the trailing zeros on the UI (thus saving code space) or that it has additional logic to remove the trailing zeros from the UI (thus taking up more FLASH storage)?

Try it now with big font

It does take a bit more to remove trailing zeros, I have to check each trailing char until I reach a non-zero (going backwards).

Tested the changes and it works with big font, up to one digit after the decimal (440.000 changes to 440.0)
Thanks for the fix!

I could remove the last zero and decimal point but I prefer to keep them

No objections here, I like it too.
In my testing this option takes up 44 bytes, in case you want to put that in the README


rabbitmq cannot be built

RabbitMQ cannot be built with Elixir >=1.11.0, which leads to the following error:
    | ==> rabbitmqctl
    | ** (Mix) You're trying to run :rabbitmqctl on Elixir v1.11.2 but it has declared in its mix.exs file it supports only Elixir >= 1.7.0 and < 1.11.0
    | Makefile:100: recipe for target 'escript/rabbitmqctl' failed
    | make[2]: *** [escript/rabbitmqctl] Error 1
    | make[2]: Leaving directory '/var/sstate/build/raspberrypi3/poky/build/tmp-glibc/work/cortexa7t2hf-neon-vfpv4-linux-gnueabi/rabbitmq-server/3.8.3-r1/rabbitmq-server-3.8.3/deps/rabbitmq_cli'
    | erlang.mk:4433: recipe for target 'deps' failed
    | make[1]: *** [deps] Error 2

Are users supposed to fix this through a PREFERRED_VERSION_elixir directive?

Hello @zonque
Thank you for point this out. Yes, configuring PREFERRED_VERSION_elixir with 1.10.4 should work.
I'll add some docs about it.

Hello @zonque
Thank you for point this out. Yes, configuring PREFERRED_VERSION_elixir with 1.10.4 should work.
I'll add some docs about it.

After updating to the hardknott branch, the compilation of rabbitmq now fails with a different error:
|  ERLC   app_utils.erl code_version.erl credit_flow.erl delegate.erl delegate_sup.erl file_handle_cache.erl file_handle_cache_stats.erl gen_server2.erl lager_forwarder_backend.erl mirrored_supervisor.erl mnesia_sync.erl pmon.erl priority_queue.erl rabbit_amqp_connection.erl rabbit_amqqueue_common.erl rabbit_auth_backend_dummy.erl rabbit_auth_mechanism.erl rabbit_authn_backend.erl rabbit_authz_backend.erl rabbit_basic_common.erl rabbit_binary_generator.erl rabbit_binary_parser.erl rabbit_cert_info.erl rabbit_channel_common.erl rabbit_command_assembler.erl rabbit_control_misc.erl rabbit_core_metrics.erl rabbit_data_coercion.erl rabbit_error_logger_handler.erl rabbit_event.erl rabbit_exchange_type.erl rabbit_framing_amqp_0_8.erl rabbit_framing_amqp_0_9_1.erl rabbit_heartbeat.erl rabbit_http_util.erl rabbit_json.erl rabbit_log.erl rabbit_log_ra_shim.erl rabbit_misc.erl rabbit_msg_store_index.erl rabbit_net.erl rabbit_nodes_common.erl rabbit_numerical.erl rabbit_password_hashing.erl rabbit_pbe.erl rabbit_peer_discovery_backend.erl rabbit_policy_validator.erl rabbit_queue_collector.erl rabbit_registry.erl rabbit_registry_class.erl rabbit_resource_monitor_misc.erl rabbit_runtime.erl rabbit_runtime_parameter.erl rabbit_semver.erl rabbit_semver_parser.erl rabbit_ssl_options.erl rabbit_types.erl rabbit_writer.erl supervisor2.erl vm_memory_monitor.erl worker_pool.erl worker_pool_sup.erl worker_pool_worker.erl
| src/app_utils.erl: error in parse transform 'lager_transform': {badarg,
|                                              [{erlang,integer_to_list,
|                                                [{72,29}],
|                                                [{error_info,
|                                                  #{module =>
|                                                     erl_erts_errors}}]},
|                                               {lager_transform,make_varname,
|                                                2,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,271}]},
|                                               {lager_transform,do_transform,
|                                                5,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,176}]},
|                                               {lager_transform,
|                                                '-transform_statement/2-lc$^0/1-0-',
|                                                2,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,116}]},
|                                               {lager_transform,
|                                                '-transform_statement/2-lc$^0/1-0-',
|                                                2,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,116}]},
|                                               {lager_transform,
|                                                transform_statement,2,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,114}]},
|                                               {lager_transform,
|                                                '-transform_statement/2-lc$^0/1-0-',
|                                                2,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,116}]},
|                                               {lager_transform,
|                                                '-transform_statement/2-lc$^0/1-0-',
|                                                2,
|                                                [{file,
|                                                  "src/lager_transform.erl"},
|                                                 {line,116}]}]}
| make[2]: *** [erlang.mk:5361: ebin/rabbit_common.app] Error 1

Any idea how to fix this?

hmm Seems that we need to update rabbitmq. I'm planing to add the latest 3.8.x and 3.9.x
Which one best fits to you ?

Thanks! I guess I would try 3.9.x first and test that.

Closing this one.
Thanks.


enable GitHub Discussions in this repository

You are aware of the Discussions feature on GitHub.
https://docs.github.com/en/discussions/quickstart
This repository is getting so crowded with issues that it's getting hard to find the important ones.
Why not use GitHub Discussions to make it easier to find issues?

@k-miyake  thank you for the suggestion, we just enabled GitHub Discussions.


Fix common-utils installation on RHEL (and friends)

On RHEL (and derivatives) the installation of the common-utils feature
could fail if the feature ran before (i.e., PACKAGES_ALREADY_INSTALLED
is set) and if either INSTALL_ZSH is false, or zsh was installed
earlier and ZSH_ALREADY_INSTALLED is true.
In these cases the script the package_list is empty, and dnf
terminates with the following error message:
usage: dnf install [-c [config file]] [-q] [-v] [--version]
                   [--installroot [path]] [--nodocs] [--noplugins]
                   [--enableplugin [plugin]] [--disableplugin [plugin]]
                   [--releasever RELEASEVER] [--setopt SETOPTS]
                   [--skip-broken] [-h] [--allowerasing] [-b | --nobest] [-C]
                   [-R [minutes]] [-d [debug level]] [--debugsolver]
                   [--showduplicates] [-e ERRORLEVEL] [--obsoletes]
                   [--rpmverbosity [debug level name]] [-y] [--assumeno]
                   [--enablerepo [repo]] [--disablerepo [repo] | --repo
                   [repo]] [--enable | --disable] [-x [package]]
                   [--disableexcludes [repo]] [--repofrompath [repo,path]]
                   [--noautoremove] [--nogpgcheck] [--color COLOR] [--refresh]
                   [-4] [-6] [--destdir DESTDIR] [--downloadonly]
                   [--comment COMMENT] [--bugfix] [--enhancement]
                   [--newpackage] [--security] [--advisory ADVISORY]
                   [--bz BUGZILLA] [--cve CVES]
                   [--sec-severity {Critical,Important,Moderate,Low}]
                   [--forcearch ARCH]
                   PACKAGE [PACKAGE ...]
dnf install: error: the following arguments are required: PACKAGE

Fix the problem by running dnf only with a non-zero package_list.

Thank you for your PR contribution
I have approved the workflow run. We will get back with a review soon


all Heroku builds are failing

It seems that the fine folks over at Meteor.com let their CERT expire!
File-under: WTF!?

I have merger the changes from https://github.com/AdmitHub/meteor-buildpack-horse
This should be all fixed now. Please try setting BUILDPACK_CLEAR_CACHE=1 on the environment variables configuration panel if it is still a problem for you.
In case the problem persists, please reopen this issue with more info.


Deprecate ioutil

As mentioned in the document,

Deprecated: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.66%. Comparing base (3642c53) to head (f2e0a47).

Additional details and impacted files
@@            Coverage Diff             @@
##           pre-1.0.0      #14   +/-   ##
==========================================
  Coverage      91.66%   91.66%
==========================================
  Files              3        3
  Lines            168      168
==========================================
  Hits             154      154
  Misses             8        8
  Partials           6        6

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


[vm/ffi] Pointer operation optimizations

Creating a new issue for this, instead of having everything in https://github.com/dart-lang/sdk/issues/36247. We need to implement the pointer operations in IL/Dart to get rid of runtime entries.

To scope this for the MVP release: we will understand the performance of FFI operations and implement any "low-hanging" optimizations.

Originally posted by @sjindel-google in https://github.com/dart-lang/sdk/issues/36247#issuecomment-500843309
Some optimizations depend on statically knowing the type argument on Pointer. Related API changes:

Use extension methods (#37773).

On top of the extension methods listed there (for API quality and performance), Pointer.elementAt should also be made an extension method to prevent branching in hot loops.

To prepare for the switch to extension methods. (These issues are obsolete if we switch to extension methods directly.):

Remove type argument to load (#37463).
Disallow calls on dynamic and on Pointer<NativeType> (#35902).

The pointer optimizations could be implemented without doing these API changes, if loads and stores through dynamic and on Pointer<NativeType> keep working as a slow path.
What optimizations we can do, and how we can do them, might be influenced by finalizers (#35770).

The CL to address this is in review.

The low-hanging fruits have been implemented.


new select_impl breaks if requestContext not present

I'm not sure whether requestContext is always provided from lambda event, but we have a use case where we're creating the event dict ourselves which did not contain a requestContext. New code to support elb tries to access event['requestContext'] which fails in that case. Would be easy enough to use .get(), I'll submit a PR.

Hey, @chadawagner. Thank you very much for your contribution.
I have some hesitation with this approach. In the case of requestContext, I think it makes sense to choose the APIGW implementation as a default. For the other changes you've made in your PR, particularly for REQUEST_METHOD, I suspect failure is the correct thing to do as absence of some of those values indicates a bad request from which a sensible response cannot be constructed. I would rather fail than return an incorrect response.

Thanks for the quick feedback!
Ok, if APIGW for sure always sends requestContext we can just add it to our event, but since that lookup was just added and we only care whether it contains elb but aren't using it otherwise, it seemed safer to not introduce a new potential exception.
I was on the fence about the others. I wasn't going to change them but then looked at how werkzeug is handling those and borrowed their defaults. Seems like at least query params could be optional, but I'm ok with requiring all of them since it was already that way.
Either way we can work with it, so whatever you think best. Thanks!

Thanks. Would you mind resubmitting your PR, changing only select_impl?

Sure, I just updated the existing PR.

Thanks!


Command line flag aliases not working

When trying to set the max memory at launch, I can use --heap but not --mem or --memory despite claims

despite claims

It's because I am a lying liar. :smiling_imp:


Collaborator request for the project :)

Why i would like to have Collaborator Access ?
Hello  @badarshahzad  , i have a suggestion for your team . I would like you to add me as a collaborator to your project so i can publish releases and generally upgrade this repository.
What permissions a collaborator has ?
https://help.github.com/articles/permission-levels-for-a-user-account-repository/#collaborator-access-on-a-repository-owned-by-a-user-account
How you can do it ?
You can go on https://github.com/badarshahzad/Jfx-Browser , settings -> collaborators -> type my name ( goxr3plus ) and add me .
Finally
If you would like to do it , i would be very glad :) . You can remove me any time you want because you are the admin .
Can't you publish releases on your own fork ?
No as far as i know because it is just a fork , so i have to copy all the code from your project and make a new repository with the same code and name . Though people must come to your repository not my own ... you know what i mean.

Hi,
We are happy to add you as a collaborator as you are spending your precious time in this project.

Welcome to Paloos Group :wave:  :smile:

@naeemkhan12  @Hassankhan2015 @Shoaibkhan786 @RamzanShahidkhan @sanaullah786
Cheers!
Badar

Glad to hear your sound and your interest to contribute in team project.
Good luck.

sure why not :+1:

OK now I will make it the best JavaFX Browser ever.

Thanks so much
Thanks Stay Blessed.
Mohammad Hassan Iqbal Khan.
UOB# 14031263
Namal College Mianwali,
An Associate College of University of Bradford.
On 24 November 2017 at 22:02, GOXR3PLUS STUDIO<EMAIL_ADDRESS>wrote:

OK now I will make it the best JavaFX Browser ever.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/badarshahzad/Jfx-Browser/issues/60#issuecomment-346869659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APGCo0s4mymO-FBIr-SYDn7oRNi8jfoNks5s5vaVgaJpZM4QpGIJ
.

hope it would be fun to work with you 🍦


Fix the line wrapping consistency in the changelog

I'll look into linting when I have time. As you said, let's not waste it by blocking the merge.

I do remember that one of the marketplaces had some special requirements regarding markdown. We will see if that breaks it or not and if so, we will need to add a note.


Fix some /permissive- errors

Found while investigating #1942

Illegal qualified name GetElementIWithCache
Make type name PNode explicit

@Penguinwizzard @boingoing fixed another issue (only repros in a build which includes EnC functionality)
@Rastaban explained:

the C++ standard says when the base class in dependent, then the compiler should not try to look up symbols in it.  By default we look up symbols in the base class anyway.
so it was finding the symbols you would expect it to find, but it is not supposed to :)

@dotnet-bot test this please


use asyncio for concurrency

Summary by CodeRabbit

New Features

Introduced asynchronous video generation capabilities, enhancing responsiveness during video tasks.
Added new asynchronous methods for video generation across multiple tools, including text_to_video_async.
Updated polling interval for video generation tasks from 30 seconds to 10 seconds.

Bug Fixes

Improved error handling during asynchronous video generation processes.

Documentation

Updated method signatures to reflect the transition to asynchronous execution while maintaining backward compatibility.

@0xrohitgarg Getting this error with Fal.

@0xrohitgarg Getting the above Event loop is closed error again.


Ability to use NGPrime Dropdowns

As a user of Sentinel, I want to be able to identify an NGPrime Dropdown as a Dropdown so that I can use them as any other dropdown.

Need to add in React dropdown for PA.


viewMode = 'months'

When viewMode = 'months' is choden in datetimepicker, I expect that it allows use to choose only month. However, the real functionality is the following:

month selection calendar is displayed
when use chooses any date on calender, then I expect that month is choosen and calendar closes, however, the calendar doesn't close, instead it asks user to choose date (calendar with default viewMode is loaded)

the format string is what determines what parts of the picker can be used. use format: 'MM' if you only want the month to be selectable.


Support new ZADD options introduced at Redis 3.0.2

Closes #1067
We discussed many things from #1067, so please refer that issue for more details.
I didn't add javadoc for added methods for some reasons.
I'll address what thing prevents me to add javadoc to #978.
Please review and comment. Thanks!

Looks great.  Thanks for handling all of this, sorry that it had to turn into such a fuss...  Looking forward to the *Param args as well.

@HeartSaVioR PR is perfect. Let's see what we want to do with the zaddBinary thing and then merge :)

@HeartSaVioR LAGTM (Looks amazingly good to me??) :+1:

@jamespedwards42 You don't need to be sorry. It was me who can't stand with that decision. :)

Merged into master and 2.8 branch respectively.
Thanks all!


Ensure Test doesn't skip test cases or classes

Tests skip some test cases because Test#classpath is cleared.  Use workaround hack.

Gradle 6.4 now has Module support built-in. Please open an issue on https://github.com/gradle/gradle if there is still a problem.


isDart2jsNnbd prevents some tests from running outside the test runner

We usually run our tests via the test runner, but not always. In particular, a handful of tests can be run as a standalone Dart program, updating expectation files if -g is passed. These tests throw if run this way because we end up calling null.endsWith("Legacy").
Example: dart tests/compiler/dart2js/analyses/dart2js_dynamic_test.dart [-g]
/cc @sigmundch

Bump - I've been working around this by specifying DART_CONFIGURATION on the command line, but we should clean this up.

Note: now that the unfork is done and the sdk_nnbd folder moved back to sdk, we should be able to replace the variable with true and delete all prennbd expectation comments.


just copying from the input repo generates io errors in a pipeline

output of get logs, like this for pretty much every file.
2016-06-23T20:00:08Z ERROR fuse.FileRead {"file":{"file":{"commit":{"repo":{"name":"prospector_input"},"id":"723e2340a6c94630a7ecc9051fba71da"},"path":"194/digitizer/BIH310090052_T_BI348.bson.gz"},"shard":{"fileModulus":"1"}},"error":"read more than we need; this is likely a bug"} 0 | cp: error reading '/pfs/prospector_input/194/digitizer/BIH310090052_T_BI348.bson.gz': Input/output error 0 | cp: failed to extend '/inputs/prospector_input/194/digitizer/BIH310090052_T_BI348.bson.gz': Input/output error

Hey @JonathanFraser really sorry you ran into this. We have several tests that cp data from input repos so I'm guessing there's something subtly different here. Would it be possible to share the code that created this error so I can reproduce it locally and figure out what's going on?

@jdoliner sure here is the manifest file
as you can see it's executing cp as the very first command
{   "pipeline": {     "name": "prospector_preprocessing7"   },   "transform": {     "image": "generalfusion/fushim:new_base",     "cmd": [       "sh"     ],     "stdin": [       "export PACH_REPO=prospector_preprocessing", 	  "mkdir /inputs", 	  "cp -r /pfs/prospector_input /inputs",       "repo/gfpy/digitizer/preprocess.py /temp_output /inputs || exit 1",       "data-replicator -bucket-name=generalfusion-temp /temp_output/ /pfs/out/ || exit 1"     ]   },   "parallelism": 0,   "inputs": [     {       "repo": {         "name": "prospector_input"       },       "method": {         "partition": "file",         "incremental": true       }     }   ] }

@JonathanFraser thanks! Will repro on our end and figure out what's going on.

@JonathanFraser update on this. I created a test in our test suite which mimics your pipeline as best I could. You can see the test here. Unfortunately I wasn't able to get this test to fail. 1 thing that comes to mind: what do your files look like? I'm creating 100 files, each of which is 10,000 lines long I'm guessing maybe that's the difference but I'm not sure. Any chance you could share the data files? That may be the best hope for getting a faithful recreation on our end.

@JonathanFraser update on this, I tried downloading some of your specific data files in a further attempt to recreate and wasn't able to get it to show up. I think there's a decent chance that the error was caused by getting pachd into some sort of a weird state which caused pfs ops to error. It might be that this issue goes away if you do a clean deploy. Please let me know if you reproduce the error again with a fresh deploy, hopefully if that happens it'll teach us a bit more about how to reproduce the issue.
Sorry we couldn't find a better solution to this one for you.


v0.3.12 tagged images missing

It appears that there aren't any v0.3.12 tagged images available for base julia or the juliabox images even though it's highlighted as available.

Yes, I see that. Strangely, the build details show the build to have gone through successfully for the last two times.
I'm triggering a fresh build now.

I'm able to see v0.3.12 in the tags now (https://hub.docker.com/r/julialang/julia/tags/).
@ianshmean can you try?

Indeed, I can. Not in the juliabox dists but I assume julia was first to build..

Yes. Dockerhub builds do take quite a while. Building locally can be faster.

Ok. Thanks!


Add 4th chunk of Cobra Examples

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>Adds the 4th chunk of Cobra Examples to the CLI help.
One more chunk of 10 to complete.

LGTM

/lgtm


Support ORC file type in Azkaban viewer plugin #193

Adding ORCFileViewer and corresponding test cases.

Thanks @hluu for review. I have updated the diff.

LGTM

Updated the pull request.

LGTM


Topk func has static thread group size

Topk func has static thread group size now, which enables compilation on vulkan

cc: @junrushao


URL access definition minor issue

Hi All,
There is a URL in the access section for the azure portal like    *.portal.azure.com  but, this is not recognized by some firewalls as portal.azure.com so we need to add portal.azure.com also. A few customer of mine had this issue and I want to mention it here.

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

ID: 7a4a21a9-fcda-355f-6668-21cd3adf25af
Version Independent ID: 659ad43a-882f-1510-36df-dd1d994b6a09
Content: Azure Migrate appliance - Azure Migrate
Content Source: articles/migrate/migrate-appliance.md
Service: azure-migrate
GitHub Login: @Vikram1988
Microsoft Alias: vibansa

@Erdemg
Thanks for your feedback! We will investigate and update as appropriate.

@Erdemg - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Better info about "Code + Test" is needed

Regarding the "Code + Test" feature on the portal, we need clearer information about how it works and its limitations. Many users start by using it for tests successfully but, after passing to production and star using tools like Zip_Deploy, they don't understand why this feature stops working.
At the moment, the note only says this:
"In-portal editing is only supported for JavaScript, PowerShell, TypeScript, and C# Script functions.
For C# class library, Java, and Python functions, you can create the function app in the portal, but you must also create the functions locally and then publish them to Azure."
A clearer description of how "Code +  Test" works would help explaining that to the users.

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

ID: 3c4cf342-0f52-5ebb-aeb2-a1ae5a2b6133
Version Independent ID: 7c75fc5a-df94-4254-2d85-e1118f401fd7
Content: Create your first function in the Azure portal
Content Source: articles/azure-functions/functions-create-function-app-portal.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@telmocoutomsft
Thanks for your feedback! We will investigate and update as appropriate.

@telmocoutomsft I'm not sure I understand your issue with the Code + Test tab. This still works for any published function that is reachable by the portal. It's just that you can't edit the code, but the Code + Test tab still works. If you have more information about your trouble using the Code + Test tab, please open a new issue. #please-close


Make a Discord server

It would be cool to have a Discord support server.

Actually there is a Telegram group for support here

We will see. If we create a Discord server, we will make it public. Till then as @iTzVoko  mentioned, you can join our Telegram group. You can also mail us at<EMAIL_ADDRESS>or raise a GitHub issue. Thank you.


Better Dice Roller

I'd like to be able to roll different size dice:
/roll 1d6
/roll 1d20
/roll 3d6

K thanks.

Fixed, will add for ambiguity later


cmd/go: go work use panics when given a file

What version of Go are you using (go version)?

$ go version
1.18

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/ja/go/bin"
GOCACHE="/home/ja/.cache/go-build"
GOENV="/home/ja/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/ja/go/pkg/mod"
GONOPROXY="*"
GONOSUMDB="*"
GOOS="linux"
GOPATH="/home/ja/go"
GOPRIVATE="*"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/ja/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/ja/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4125566826=/tmp/go-build -gno-record-gcc-switches"

What did you do?

$ mkdir work
$ cd work
$ go work init
$ touch iamafile
$ go work use iamafile

What did you expect to see?
A graceful error around having been provided a file instead of a folder
What did you see instead?

go: stat /home/ja/work/iamafile/go.mod: not a directory
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x81d565]

goroutine 1 [running]:
cmd/go/internal/workcmd.runUse.func1({0x7ffc8a10a7ed?, 0x0?})
        /usr/local/go/src/cmd/go/internal/workcmd/use.go:97 +0x165
cmd/go/internal/workcmd.runUse({0xadc718?, 0xc000122000?}, 0xc00014c510?, {0xc00013a030, 0x1, 0x2?})
        /usr/local/go/src/cmd/go/internal/workcmd/use.go:112 +0xa8a
main.invoke(0xdb7660, {0xc00013a020, 0x2, 0x2})
        /usr/local/go/src/cmd/go/main.go:218 +0x2ee
main.main()
        /usr/local/go/src/cmd/go/main.go:175 +0x78e

This seems like a good candidate for someone's first contribution, by the way. Just make sure to look at how recent bugfixes in go work were implemented, read https://go.dev/doc/contribute, and include a test case.

I'd be interested in working on this as a first contribution

@gopherbot, please backport to Go 1.18. (This is a user-facing panic in go work use.)


Consider trying out a "balance" stream transformer

The idea roughly is to take a stream of elements and transform it into N number of new streams. If any of the new streams are polled, it polls the "main" stream and returns an element if available. Each element is always dispatched to the "first" downstream that polls() (can be some leeway in interpreting "first" the only constraint is to be fair if there are multiple available downstreams when an upstream element arrives). For example the new streams can be for example connected to different TCP outbound channels and incoming "jobs" are dispatched to the ones available.
I have read the excellent blog post http://aturon.github.io/blog/2016/09/07/futures-design/ which finally answered most of my questions about the "whys" of the current design, but it made me thinking, isn't the above combinator exercising the exact same problem as described in the "False start: the callback (aka completion-based) approach" in the end? Trying to explain:

due to the requirements of such a stream combinator, the upstream might be polled from different threads/tasks concurrently (balancing makes only sense if there is independent progress of the consumers)
hence, they need some way to coordinate and that again leads to Arc or some atomic to be shared among the poll() calls.
in essence, what I am getting at, that poll() itself can be the callback (singaling "downstream ready") in certain combinators.

Of course it might be that

this is not an issue for some reason that I don't see but you do :)
or it might turn out that you simply don't want to support it to keep things simple and fast
or, you support it but pay performance penalty and say that this is not the common usage and hence acceptable.

This sounds like a pretty nifty combinator to me! I think we could definitely have it fit the poll model, although I can't imagine a non-Arc/non-Mutex implementation off the top of my head just yet...

One concern I have with this is caching and/or NUMA. If a stream is polled from multiple threads, on multiple CPUs, you're caches are going to constantly get invalidated (assuming the underlying stream is being mutated in some way).


Use native certificates on TLS for rustls

Native certificates are installed using the following package: https://docs.rs/rustls-native-certs/latest/rustls_native_certs/index.html for a custom client.
Reference: https://docs.rs/kube-client/0.71.0/src/kube_client/client/tls.rs.html#129

superseded by #47


[Removal]: Mammoth Scarlet Pheasant

Hotspot Name
Mammoth Scarlet Pheasant
Hotspot b58 Address
112HctCLfAiVzLTUNd3VsBKTiChbncCSLRF9gN7hWRnKYGUM6QNf
Discord Handle
Marco-polo#0495
Hotspot Manufacturer
Bobcat
Removal Reason
Some-one just banned my wallet without any proof, we are telecom provider
Modifications
No
Extra forwarders
No
Extra antennas
Yes
Additional Information
External 6 dbi omni, 40m building
Great site, but all telecom towers with good earning did end up the denylist.
So i have todo this 50+ times ?
More info via PM, discord.
Regards
A 500+ telecom tower owner.

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


add validate/2, load/2, and dump/2 function generation to nested schema modules

Hello!
This is a Pull Request to add some small Quality of Life improvements to the nested schema module generation.

@punchcafe thanks for the PR. Only issue I see is the formatting of the code. Please run mix format and if CI passes I can approve

Thank you! I've updated that now, so hopefully it should be green!

thanks! Could you elaborate what problem you are facing that requires to have these functions on the nested module?
I just want to understand your problem and see if this is the best solution.

Sure! It was mostly just a matter of ergonomics. Having to call the main param each time with the Module felt a bit verbose, so we were wondering if we could make it more succinct by using the GenServer kind of approach.

Thanks for your feedback. I see your concerns about adding this as it brings in implicit function declarations.
I appreciate the solutions you've offered above but these don't really meet our use case, as our priority is to be able to declaratively define request schemas with minimal boiler plate and no extra internal macros.
Thank you for your time!


use detected locale to check if one of the common directories is present

@karlicoss btw this is likely related to the expected targets, if a users google account locale was for example in german, some of those files might not be present
will add some code todetect locale by trying each locale and returning the one with the most path matches, and then PR an update to HPI

added in 302b06f329c4cb9251a845d767fa9c1a32f88970


Update BIDS content Types

TODOs in the PR:

adding IRI to BIDS spec
updating names
adding missing content types

QUESTION: how detailed do we want to be here?
A) Each TSV and JSON type becomes its own content type?
B) Should we have one content type for all TSV and one content type for all JSONs?
@apdavison @Peyman-N and @jagru20 please advise before I continue

I'm closing this PR. I made an issue about this in the instances-repo and will create a new PR when a conclusion has been reached.


DEMO mode could lead to issue

You have an env variable for demo mode
By convention, it should be "POM_DEMO"
I'm a bit worried someone with a DEMO environment variable would have a strange behavior when using your tool.
Or you could remove the demo mode, or move it to an argument like --demo

You're totally right! It should definitely be namespaced!


Feature Req: Non-interactive with "-f force" or "-y yes"

I call t from scripts, so each update, I comment out the following line from delete.rb
#return unless yes? "Are you sure you want to remove @#{status.user.screen_name}'s status: "#{status.full_text}" from your favorites? [y/N]"
I would like to have a -f, --force flag similar to e.g. rm, and change ALL y/N questions like this to something like:
return unless (not option.force) and yes? ...
excuse the pseudocode; I don't know Ruby.

+1


"last known value"

There are a few values in the Flow frame that asks for "last known value". What does "last known value" mean?

Flow from Receiver to Sender
AmqpNetLite

deliveryCount is set to receiver's current deliveryCount
available is not set


USB connect/disconnect

Hello!  Hoping to use the lessons learned from my first attempt at building this device, I used extraordinary caution when assembling my second attempt unit.  No detail was too small.  (I actually did component-level bench repair way back when... quite a few resume entries ago)
While we can never rule out an assembly problem, I wanted to share my result on the outside chance that it indicated something in particular.  When connecting the unit to the same USB cable that works perfectly fine for off-the-shelf ESP32's, my syslog loops through the following:
Feb 16 05:11:25 3010i5 kernel: [40601.552217] usb 1-1.3: new full-speed USB device number 106 using ehci-pci
Feb 16 05:11:26 3010i5 kernel: [40601.662018] usb 1-1.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Feb 16 05:11:26 3010i5 kernel: [40601.662020] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 16 05:11:26 3010i5 kernel: [40601.662021] usb 1-1.3: Product: CP2102 USB to UART Bridge Controller
Feb 16 05:11:26 3010i5 kernel: [40601.662022] usb 1-1.3: Manufacturer: Silicon Labs
Feb 16 05:11:26 3010i5 kernel: [40601.662022] usb 1-1.3: SerialNumber: 0001
Feb 16 05:11:26 3010i5 kernel: [40601.662921] cp210x 1-1.3:1.0: cp210x converter detected
Feb 16 05:11:26 3010i5 mtp-probe: checking bus 1, device 106: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
Feb 16 05:11:26 3010i5 mtp-probe: bus: 1, device: 106 was not an MTP device
Feb 16 05:11:26 3010i5 kernel: [40601.664955] usb 1-1.3: cp210x converter now attached to ttyUSB0
Feb 16 05:11:27 3010i5 snapd[830]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Feb 16 05:11:27 3010i5 systemd[1]: Starting Manage ttyUSB0 for GPS daemon...
Feb 16 05:11:27 3010i5 gpsdctl: gpsd_control(action=add, arg=/dev/ttyUSB0)
Feb 16 05:11:27 3010i5 gpsdctl: reached a running gpsd
Feb 16 05:11:27 3010i5 systemd[1]: Started Manage ttyUSB0 for GPS daemon.
Feb 16 05:11:27 3010i5 upowerd[1403]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0
Feb 16 05:11:28 3010i5 upowerd[1403]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3
Feb 16 05:11:29 3010i5 ModemManager[812]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3': not supported by any plugin
Feb 16 05:11:34 3010i5 kernel: [40609.706944] usb 1-1.3: USB disconnect, device number 106
Feb 16 05:11:34 3010i5 kernel: [40609.707152] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Feb 16 05:11:34 3010i5 kernel: [40609.707171] cp210x 1-1.3:1.0: device disconnected
Feb 16 05:11:34 3010i5 systemd[1]: Stopping Manage ttyUSB0 for GPS daemon...
Feb 16 05:11:34 3010i5 upowerd[1403]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0
Feb 16 05:11:34 3010i5 gpsdctl: gpsd_control(action=remove, arg=/dev/ttyUSB0)
Feb 16 05:11:34 3010i5 gpsdctl: reached a running gpsd
Feb 16 05:11:34 3010i5 systemd[1]: Stopped Manage ttyUSB0 for GPS daemon.
Feb 16 05:11:35 3010i5 upowerd[1403]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3
Feb 16 05:11:36 3010i5 compiz[1408]: [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)

... by chance does anything there suggest what might be wrong?  FYI, one time it actually stayed "alive" long enough for me to upload code via the Arduino IDE and in the serial monitor, I got one quick iteration of my code's user menu.
Note that I am only using USB power.  While this works perfectly fine for any other device I use, do you think it might possibly be helpful here if I powered the unit externally?
Many thanks!
-Scott,  K4KDR

Just to follow-up, I have noticed that the CP2102 chip gets EXTREMELY hot.  I removed D1 in case I had installed that backwards but with D1 removed, the same syslog errors occur and CP2102 (U2) still gets hot.

The overheating issue is very strange, it doesn't do that on my board. How long does it take to start overheating? Can you rule out shorts on the QFN package? Also, are you using CP2102 or CP2102N? Apparently, those two are quite different.
Using only USB power should be fine for startup, it might not be enough when transmitting at 1 W but that's not the case now.
The USB/UART converter and reset circuit is copied from NodeMCU, so I hoped it would work. Which ESP32s did you try?

The overheating is immediate.  FYI, the first components installed were the USB jack and CP2102.  Connecting to the computer via USB with ONLY those two components installed gave a proper "USB device found" type of message in syslog, so I felt confident to continue the build.  No overheating was noticed at that point.
I continued this "syslog" type of testing throughout the build.  Everything was stable until the last few components were installed.  They were the SMA jack, pin header, slide switch, R3 / R5 / R7, and R14 / R15.
If no smoking gun is identified, I can certainly work backwards removing the last few components to see if the issue stops.  I would like to think I can omit the SMA jack from consideration, but the other components might be telling.
As for those components you asked about, the CP2102 is:  https://www.mouser.com/ProductDetail/634-CP2102-GM/
... and the ESP32 is:  https://www.mouser.com/ProductDetail/356-ES32WROOM32D16MB/
If I have used an incorrect CP2102, that would almost be "good" news - at least I would have an explanation.
Thank you so much for your time!

Let's go through it then, back to front:

R14/15 are I2C pullups, so that's most likely not related
R7 is just a serial resistor on ESP32's RX - again, doesn't seem like the culprit
R3/5 are serial resistors that connect to the reset and bootloader buttons. That one looks more interesting, what buttons did you use? If they're always shorted to the ground, it could mess up the BJT autoreset switches
the slide switch connects the CP2102 to power, so that one will always be suspicious
pin header doesn't seem related
SMA jack also doesn't

The CP2102 should be the correct one, as well as the ESP32.

I was hoping I had chosen the wrong CP2102... at least that would be easy to correct!
Very well, thank you so much for the detailed part functionality review.  I will start removing items until I return to a device that will connect to the computer in a stable fashion -- and without excess heat.
By chance do you have a high-resolution picture of a completed board without the OLED installed?  It would be helpful to verify the orientation of some components obscured by that display... D1 in particular.  There is a faint 'line' on one end of D1 and I am not certain whether the 'line' should face U1 or U2.
Thanks!

OK, that should be the exact same as mine, so that theory is busted then.
Here's a picture of the area beneath the dispplay, hope it helps. The diode is there just for reverse-voltage protection, so if it's mounted backwards, it still doesn't explain the overheating issue.

Thank you!  I had D1 oriented correctly, so I'll re-install it.
Where did you get that socket for the OLED?  I can't use it as my display modules have VCC & GND reversed from your build.  But it would be wonderful to have some of those for future use.

It's basically a precision pin header, originally for round pins but it can take square ones too. It's a lot more solid connection than the usual square headers. Here's a TME link, Mouser might have them too: https://www.tme.eu/cz/details/zl307-1x4/konektory-hrebinky/connfly/ds1002-03-1-4131/

Removing R5 & R7 made no difference, so I suppose that I should not overlook the obvious... that tiny CP2102 is not installed cleanly.  When I only had the USB jack & CP2102 installed, of course very few pins were in use.  Now that all of the CP2102 pins (at least those utilized on this build) are connected, a short could certainly be causing all this heat under that chip.  I suppose I should remove & try again the CP2102...

Well, after VERY carefully reinstalling the CP2102 chip (actually a new chip), I no longer am overheating.  After also reinstalling D1 and the resistors that I had removed, the device seems to be recognized by my system and does not instantly disconnect.  (see images below)    However, I'm having mixed results w/ uploading code from VSCode & the Arduino IDE.  Using ESPTOOL to completely wipe the flash worked once, but now hangs.  Is anything special needed to interact with this VROOM module that I might not have on my system?  Thanks!

An update....
Noticed the following scrolling non-stop in the Serial Monitor window in VSCode:
----------------------------
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun  8 2016 00:22:57
-----------------------------

Seems like an issue with the ESP32 flash module. Could you post the full output of esptool?

Glad to!
Is there some particular argument that might help you?  If I just run
esptool.py --port /dev/ttyUSB0
it returns the list of additional options & arguments that are available

Nothing in particular, just the output from uploading via esptool (even in Arduino IDE).

Very good - thank you!  Here is what I get when attempting to upload from VSCode:
2021-02-18--k4kdr--esptool-upload-error.txt

After going through a couple issues on esptool GitHub, I think this is most likely faulty hardware again. This seems to be supported by the esptool output:
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB

0xFF is a very typical output of a faulty SPI. My guess is that either something got damaged with the shorted CP2102, or there's some short or cold joint on the ESP32.
As a last check, could you try running espefuse.py --port PORT summary (where PORT is the serial port ESP32 is connected to)? Apparently this thing can also happen if the fuses aren't set correctly.

I have also been researching this and the internet is flooded with reports of similar issues/errors.  Apparently there is some combination of circumstances that makes this type of thing very common with ESP32s.
There seem to be many references to GPIO-2 possibly having a role in whether or not an ESP32 can be programmed successfully, but I'm not clear on that.
I saw many references to the espefuse command but have no idea what a "fuse" is in the ESP32 world.  The output of that command from my build is attached.  Many thanks!!
2021-02-19--k4kdr--espefuse-output.txt

Looking over the efuses, I don't see anything that stands out.
GPIO2 is used as LED indicator pin, I guess you could try to remove R9 to isolate it, but I don't think it's going to make a difference. So I'm afraid this really does look like a hardware fault in the ESP32 module.

Thanks so much!!  I'll remove R9 in case GPIO2 is a factor.  If nothing changes, then I'll try another ESP32 module.
Will report the results!

Very grateful for your patience to walk me through this fun project!    Removing R9 did not help, so I removed the ESP32 and installed a new one.
The device now accepts programming both from VSCode and the Arduino IDE!
Could you please confirm the pin assignments for this Ebyte 400M30S module?   I have tried several combinations that I thought were correct, but get:
Failed to initialize radio, code: -2
From the user manual for this device, if I understand correctly this is an SX1268 chip, is that right?
Finally, by chance is there any code available to "test" the various aspects of this build?  I mean, something more simple than the more complex repositories that add so many other variables into the equation?
Thanks!

Follow-up... using the new BETA tinyGS code, I seem to be ok.  Your custom 1W board is on the pick list using the initial <IP_ADDRESS> wi-fi connection, so that got me properly configured.
Further, I found that same listing in the code so that should provide what I need in regard to pin assignments (for other uses of this device)

... so thank you again.  I used the "P" key available using the tinyGS code and confirmed over-the-air transmission looking at an SDR waterfall.  So, all is well so far.

The pin assignment for the LoRa module can also be seen on the PCB itself, next to the pin header. And yes, Ebyte 400M30S is using SX1268 as the transceiver.
Since it looks like the issue is now resolved, I'm closing this. I also created #3 with a list of improvements to make the design a bit easier to assemble, so if you have any more feedback, it would be great if you could place it in that issue. Thanks!


Attack On Titan Opening - Guren No Yumiya

@Anshuman-Verma assign me this issue

The opening isn't very appealing in itself so make sure you add the anime version which is somewhere around 1:30min and not the full opening :)

Have a look now @Anshuman-Verma


fix(trait): disable NodePort by default for Service trait

Fix #3253

Release Note
fix(trait): NodePort is disabled by default for Service trait

@squakez Yes, having an E2E test is a good idea. I'm working on it.

@squakez E2E test added.

Failed E2E test is known flaky one and isn't related to this PR:
--- FAIL: TestHealthTrait (415.55s)
    --- FAIL: TestHealthTrait/Readiness_condition_with_stopped_route (408.02s)

Let me merge this.


Revert "Support async validation of device trigger"

Reverts home-assistant/home-assistant#27333
This breaks zha because we're trying to use the gateway before it exists.

@emontnemery Why is this tagged for the 0.100.1 milestone?
#27333 hasn't landed in 0.100.0...


Update blobfuse2-what-is.md

Update of data consistency issue fix with version 2.3.2

@akashdubey-ms
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

@Jak-MS @akashdubey-ms @normesta -- Can you please approve this asap. This is an important change letting customer know that the reported issues have been fixed. This should have gone out 2 weeks ago.

nudge @akashdubey-ms ... can you review this? thanks!

Looks good to me. Thank you!
#sign-off

@Jak-MS - Would you be able to merge this for us? @akashdubey-ms is away on holiday until next week. @tjvishnu is internal to MS.

#label:"missed-content-complete"
#label:"event-triaged-to-10AM"
@normesta - thanks for your approval/sign off.  we can merge this PR after the content freeze is lifted.
This PR is ready for merge. Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of the keynote address.
The PR review team will resume merging on the morning of the keynote address for the regularly scheduled daily publish cycles. You don't need to take further action on this PR; we'll merge it on the day of the keynote address.
Don't add more commits to this reviewed PR.
Thanks.

Understood. Thanks @Jak-MS!


feat: helper api route for runtime env vars

Heavily inspired by https://github.com/didx-xyz/yoma/pull/96

For now, https://github.com/didx-xyz/ssi-trust-registry/pull/190 appears to be the better solution. However, if in the future we want to explore static pages, perhaps this route would allow that.


a way to assign the result of a required css file to :global

Before using css modules, I was able to import styles from react-select defaults using the following:
require('react-select/dist/default.css');
But those styles are not required by default to :global and since they are not being referenced anywhere explicitly they are not being included in the bundle. A workaround I've made is to duplicate the default.css and prepend all selectors with :global(.class-name) but it'd be nice if I could signify that I'd like this require to be loaded into :global along the lines of:
require('global!react-select/dist/default.css');

module: {
  loaders: [
    [
      {
        test: /\.css$/,
        include: path.resolve("./node_modules/react-select"),
        loader: "style-loader!css-loader"
      },
      { test: /\.css$/, loader: "style-loader!css-loader?modules" },
  ]
}

It seems like when creating/using a global module it would be more useful to do something like
.flex,
:global .flex {
  display: flex;
}

but this throws an error in the css-loader. It seems that in the example above if you wanted to use something out of the react-select module locally, and then something globally, you would get duplicated code.

.flex,
:global(.flex) {
  display: flex;
}

@sokra thanks for the tip. I'm a little confused because when looking at this example they are able to use :global without the parenthesis, which I was assuming was "sugar".
https://github.com/css-modules/webpack-demo/blob/master/src/components/2-GlobalSelectors/GlobalSelectors.css
Confusing why that works for the scenario for only one class name, but not when two class names are associated with a given css block:
Works
.flex-row,
:global(.flex-row) {
  flex-direction: row;
}

:global .flex-column {
  flex-direction: column;
}

Doesn't Work
.flex-row,
:global .flex-row {
  flex-direction: row;
}

:global .flex-column {
  flex-direction: column;
}

What if there was a loader for importing CSS modules as global, one we could simply import like:
require('globally!react-select/dist/default.css');

Tha way would be pretty easy to just use a third-party without hacking/injecting in its CSS.

:global {
  @import '~react-select/scss/default';
}

@StevenLangbroek I'm doing this inside my app.css file
:global {
  @import 'some-vendor-component.css';
}

However, in the output css I still see classes like this:  app--vendor-class-that-i-want-to-be-global{rules...} Should this work or is something else missing?

@adamgruber Although :global { @import ... } works for most of the cases, it can sometimes break when you use a preprocessor or postcss plugin that enables the & operator. I've left a comment in https://github.com/css-modules/css-modules/pull/65#issuecomment-214221200 describing this. Is this what you're seeing as well or is there another issue causing it?

@sokra I am using postcss and extract text plugin, this does not work.


Add s390x support in FloatingPointInterchange

What's in this pull request?
Enable s390x testing in test/Prototypes/FloatingPoint.swift, extracting from https://github.com/apple/swift/pull/3193
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test and merge


feat(personne-morale.vue): improve legend add etablissements secondai…

…res actif count
https://jira-mcas.atlassian.net/jira/software/c/projects/VAO/boards/336?selectedIssue=VAO-440

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Governance updates

As the Workflows spec emerges as the second kind of specification under the OpenAPI auspices, there may be some governance issues to address.

Whether it makes sense to move from a SIG to a Working Group model that operates semi-autonomously under the TSC
Whether the CSL (Community Specification License) is more appropriate than Apache
Updating to the structure of the group, such as updating the original "champions" section of the Workflows' readme.

There may be more, in which case please add as comments.

See https://github.com/OAI/OpenAPI-Specification/issues/3774 for related topic


Testexecution PostTermination mismatch in the initial and final configuration file

Assertion failure details
In TAR Individual Services , following are the assertions that are failed because of this problem,

Provides expected properties in configuration class for 'tar-2-0-1-tcp-c-or-1-0-0-000'
Provides expected properties in configuration class for 'tar-2-0-1-http-c-cc-1-0-0-000'

Reason  :
In the test execution, the expectation is , the initial configuration file should match the final configuration.
But there is a mismatch. This mismatch are consequences of the failures of other assertions. Once the other assertion failures will be resolved , this shall also be cleared.

Closing this issue as the test-suite is not updated for version 2.1.1


Required attribute on input

Hello, thank you for the plugin it's great.
If I add the "required" attribute to the input field, the default browser error alert doesn't appear.
Is there anyway I can get this to work.
If not, how can I get an error message to appear rather than just focus on the telephone field.
Thank you very much.

I just tested it here and it seems to work: just focus the input and hit enter to submit the form.

Thank you for the response, I forgot to mention the variables I have set as I need the country code to show in the input. I have extended your example here
http://codepen.io/anon/pen/yNBmNq
Variables set
$(".tel").intlTelInput({
//autoFormat: false,
autoHideDialCode: true,
autoPlaceholder: true,
defaultCountry: "auto",
nationalMode: false,
//onlyCountries: ['us', 'ch', 'ca', 'do'],
preferredCountries: ['cn', 'jp'],
//responsiveDropdown: true
});

So the problem is related to the autoHideDialCode option. If you enable this, then focusing an empty input will automatically insert the dial code, and blurring the input again will remove it. There's no way to have the browser's required check work properly when using this option. You could either do the check yourself, or disable this option. Though I personally recommend using nationalMode so your users don't have to deal with country dial codes at all.

Ok, Thank you for your help


Source of example

Hi, really nice work on this Carousel!
I was wondering if you could provide the source of the example displayed in the README.
You have the fullscreen carousel + static elements that don't move when you swipe.
React-native beginners like me will have a better understanding of how it works with it.
Thank you.

@tomav take a look at https://github.com/appintheair/react-native-buyscreen
There is example usage of the component as sees in the gif

I saw that, but it's a more basic version. :-)
I was wondering if you could provide the exact example you display as gif.

@tomav https://github.com/appintheair/react-native-buyscreen is the exact example ;)


Screenshot in step 14 shows a field filled but we are not instructed to

Hello,
In step 14, we can see on the top screenshot that the "sign on URL" seems to have been filled with something, however nowhere we were instructed to do so. Also, the bottom screenshot shows the same field empty.

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

ID: eb39c8bf-2709-c59d-94f8-6db76d21bcfb
Version Independent ID: f7122c2c-ef68-95b6-2273-edbc4bb89464
Content: Tutorial: Azure Active Directory integration with Atlassian Cloud
Content Source: articles/active-directory/saas-apps/atlassian-cloud-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

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


a blog post for the docker machine stuff

Simon J is a product manager at Rackspace. He's responsible for Rackspace's container offerings and strategy.
Edits are perfectly fine.
Hopefully this will go public on Monday.

@simonjj @catlook is our blog copy editor. She'll suggest grammar and wording changes and then up to you whether you want to incorporate them or not.

-1
Consider edited version here:
https://github.com/rackerlabs/developer.rackspace.com/pull/1033

As per @adrianotto I'm closing this PR in favor of the he pointed out.


ISPN-5489 Remove redundant jdk 8 backport classes

https://issues.jboss.org/browse/ISPN-5489
This commit just removes the backport classes that we don't need and updates any references to use the standard JDK classes.

Pushed, thanks


build: add SHA files back

- we need the SHA files on install.sh

@bk201, @FrankYang0529, Please help review this.
https://github.com/harvester/vagrant-rancherd will use the install.sh, so we need sha files