"sleep pause" commands is anti pattern in procfile ?

this is working very well on mac . really useful tool.
I was wondering about startup dependency ordering, and am looking for advice.
I read in the issues about users wanting a sleep function to force the procfile processing to wait for something to start.
But it seems like an anti pattern.
Better to design your calling binaries to try to connect to something else and then back off and try again ?

Procfile is a very simple format that doesn't support health checks. Applications that use it can't determine the readiness of processes and thus can't make processes wait for their dependencies' readiness.
In this situation, sleep is the easiest solution, yet it's not ideal.
Changing your application so it retries connection to its dependency is a good solution, yet it's not always possible to change your application like this.
So I think the best solution is to use some kind of tool or wrapper that waits for dependency readiness before starting a process. For example, the wait-for-it script can wait until it can connect to the requested port.

A golang equivalent o wait for it would be good.
Can then wrap any program with it.
Sort of like a proxy ..
I used aqua proxy for this once and it might work well with overmind.
it’s gets a binary if it’s not there and then let’s the caller call it. Basically serverless pattern.
The same sort of thing for a socket is needed. Caller asks and proxy waits for the socket to be there and then lets the call through .

Golang equivalent
https://github.com/roerohan/wait-for-it

Also
https://github.com/atkrad/wait4x


Model Setting

Hi, I have a question regarding your nice work. A task is to use 5 frames to predict next 10 frames. The ground truth of next 10 frames are available. I want to use the ground truth as supervision, in other words, the model should learn to make the predictions to be same as ground truth. It means the model should be deterministic. In this case, does your model work for this task?

This model is not deterministic, i.e. for the same input, it will sample different predictions in each evaluation run. However, if the future is clearly determined by the input frames it still might work


exploit

If you close the window at the item you wanna, you will get it, u can choose what prize to get :))

Please update your plugin. This is an issue with CustomCrates < 3.0.0

CustomCrates 4.4.0


CAD-517 | chainsync nightly:  fix

Fix the nightly chainsync benchmark -- convert the affected pieces to structured logging.

closing in favor of #557 which builds on structured logging and selects the correct fields.


Fix error when saving to system

Hi, I made a mistake trying to translate something that wasn't meant to be translated, sorry.
This results in an error when trying to save settings / system and affects formatting buttons.

thank you, I will test again and update the version on typemill.net


Certain CSS classes in syntax tokens cause issues

Reported in https://github.com/atom/highlights/issues/2
Having a token with a close scope generates a .close class which makes the text render incorrectly since Bootstrap defined a .close class for dialogs.

@nathansobo can we close this now?

Yeah. It's still possible to turn the shadow DOM off but it's not recommended.


Only getting .map and .js files

I'm trying to get the manifest to include files from the /static folder (including fonts, videos and images), but I can't seem to get it to work. My webpack installation outputs all the files in a stats script, to Webpack is aware of my files. I tried with no options as well.

Can you try v2?

I tried v2.0.0-rc.1 and now I get CSS as well, but not the files in the static folder.
Is there any way to specify folders to include?

Which plugin are you using to generate your /static folder?

It's just a static directory, created with the OS.

My webpack installation outputs all the files in a stats script, to Webpack is aware of my files.

How does webpack know those file?

closing this due to inactivity, feel free to reopen


Please provide a Usage readme

I don't forciblt mean an user usage but at least a description of what it does.

Fixed:
230537f26f2d6606ab3e940df59dce163fee815f


Expand missing shorthand

--config=android_arm is defined in tensorflow/BUILD
where it resolved to --crosstool_top=//external:android/crosstool --cpu=armeabi-v7a
seems like this cannot be referenced here

Can one of the admins verify this patch?

Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build

Now, I am a bit confused about all the flags ...

Andrew, could you take a look at this and comment on the flags?

@andrewharp any luck?

It seems like some related tools are kinda messing up configs as well, e.g. building the inference library. This seems to be due to BUILD files not in proper location and/or invalid toolchain names.
ERROR: No toolchain found for cpu 'armeabi-v7a'. Valid cpus are: [
  k8,
  piii,
  arm,
  darwin,
  ppc,
].

The next best thing I got to compile properly is:
bazel build -c opt --copt="-DSELECTIVE_REGISTRATION" \
--copt="-DSUPPORT_SELECTIVE_REGISTRATION" \
//tensorflow/contrib/android:libtensorflow_inference.so \
--host_crosstool_top=@bazel_tools//tools/cpp:toolchain \
--cpu=arm

The nightly build of libtensorflow_inference.so for armeabi-v7a is 9.7 MB and has issue #8897.
The builds with -DTENSORFLOW_DISABLE_META and/or -DSELECTIVE_REGISTRATION are 120 MB - 180 MB and are not found by System.loadLibrary("tensorflow_inference") even under the exact same conditions.

Context for this is #10299, building the inference library yourself and doing selective registration is really nasty and hard to do without opening X new issues. Why is such a central tool so error-prone and poorly documented? Most should be covered if the various prepared bazel commands would just work.

@tensorflow-jenkins test this please

@vrv What about the erroneous flag?

@vrv Could you replace the command by
bazel build -c opt --copt="-DSELECTIVE_REGISTRATION" \
--copt="-DSUPPORT_SELECTIVE_REGISTRATION" \
//tensorflow/contrib/android:libtensorflow_inference.so \
--host_crosstool_top=@bazel_tools//tools/cpp:toolchain \
--cpu=arm

@Androbin I'm afraid I have no idea how this system works -- @andrewharp do you understand?
@Androbin should I revert this PR, did I merge by mistake?

Which ARM level does --cpu=arm target? Almost all Android devices out there should be v7 or above, so that seems like a reasonable default to leave it at.

@vrv It seems like neither the previous nor the current version works. The only command that runs without error is the last one I posted here. This may be committed for now instead.
@andrewharp Most scripts I have seen here do indeed use that without further note. And according to some BUILD files, arm should just resolve to armeabi-v7a


Flesh out models with validations and tests

This adds validations to the models for fields that are marked as NOT NULL; fixes #6. It doesn't enforce any length requirements yet, we can add that after we switch to PostgreSQL in #7. This also adds a couple unique indices.

Sounds good! Closing this in favor of landing with RSpec in #26.


Help info on plugins such as spin cloud don't display top-level spin command

On Spin v1.2.0, spin cloud --help states usage as spin cloud <SUBCOMMAND>
$ spin cloud --help

spin-cloud
Commands for publishing applications to the Fermyon Platform

USAGE:
    spin cloud <SUBCOMMAND>

OPTIONS:
    -h, --help    Print help information

SUBCOMMANDS:
    deploy    Package and upload an application to the Fermyon Platform
    help      Print this message or the help of the given subcommand(s)
    login     Log into the Fermyon Platform

However, since Spin v1.3.0 uses the cloud plugin for the command, it displays usage as cloud <SUBCOMMAND>:
$ spin cloud --help

cloud-plugin 0.1.1
Fermyon Engineering<EMAIL_ADDRESS>
USAGE:
    cloud <SUBCOMMAND>

OPTIONS:
    -h, --help       Print help information
    -V, --version    Print version information

SUBCOMMANDS:
    deploy       Package and upload an application to the Fermyon Cloud
    help         Print this message or the help of the given subcommand(s)
    login        Login to Fermyon Cloud
    variables    Manage Spin application variables

Is this an issue? Is there a way to update the usage to display spin as the top-level command?

I think this would need to be addressed on the cloud-plugin side.  I think by adding a doc comment to the app struct at https://github.com/fermyon/cloud-plugin/blob/eeb5339623d6c42f11807fcbde9f1d8506f360ba/src/main.rs#L23 - that seems to be how Spin does it.

@itowlson I changed the binary name in the plugin. I wonder if we want to set this as a precedent/recommendation for plugins executed from the Spin CLI?

We could, but the help presentation is going to be very variable per plugin anyway (like a plugin written using that Go CLI library might present its help quite differently from one written using clap), so I'm not sure there's a lot of value in trying to standardise.  It's something to keep in mind for "seamless" plugins like Cloud though.


How to connect the Android app to it?

I want to try to the project but how can I connection my phone to it?
On my app, I only the following limited list of servers:

beeper.com
beeper-staging.com
beeper-dev.com

So, I have the server but I don't have a way to connect to it.

@tulir thank you for your answer.
Got it. I thought the bridge itself was the server.


mdl-js-layout conflicts with TinyMCE

Hello,
It seems that something in mdl-js-layout conflicts with TinyMCE.
When that class is applied to the body tag, TinyMCE cannot open its menus anymore.
In some other cases, you may also end up with non-editable text areas, but I have not been able to reproduce that bug on its own so I'll check later if this one gets fixed.
Tested with MDL 1.0.5 and MDL 1.0.6.
A JSFiddle is available here: https://jsfiddle.net/2zrcf0uf/1/ . Try clicking the File, Edit, View, Format and Formats menu.
It fails with Chrome 43 and Firefox 41 at least.

I think I figured it out. You need to apply the layout on a div, not on the body.
I would still keep this issue open in order to clarify the documentation. From the current phrasing, it's not clear that some things may break when the layout is applied on the body.

The docs include clear instructions as to how to structure markup. If you deviate, that is on you. We can't warn about everything.

glad you figured it out @The4thLaw :)

From the current phrasing, it's not clear that some things may break when the layout is applied on the body.

How do you think we can improve this? More than willing to improve the docs in this area (patches welcome :smile:  )..
Thanks again!

The docs include clear instructions as to how to structure markup. If you deviate, that is on you. We can't warn about everything.

Ah, I feel like my own customer :smile:
No, they don't. They include clear samples. In most of my projects, the body tag is just the semantic top-level div. There's nothing special about it.
MDL "fails" in my example because it tries to insert an element before the body (if I understood the source correctly). That's not wrong, but that's not immediately clear either.
I also think you can't warn about everything. But I'm not using such an uncommon setup. What's wrong about trying to remove an element from the markup because it brings no semantic value?

How do you think we can improve this? More than willing to improve the docs in this area (patches welcome :smile: ).

I'll see how this could be improved in the docs. Should I just foresee a patch for the layout/README.md files? Or is the website documentation generated from elsewhere?

The component docs are generated from each components README file.
Although, it already states:

Required on outer div element

In the remarks for the mdl-layout and mdl-js-layout classes in the configuration options section. If that isn't clear enough, then perhaps that is the place to look at improving the context.

I've just submitted a pull request. I thought the summary at the end, where it says

Required on outer div element

was good as it was: a concise summary. So my pull request proposes a change on the "tutorial" :)

I am developing a asp.net core webapplication, the same problem shows up, that the textarea is not editable. as long as i comment out js of mdl, tinymce works again
and i am not applying mdl-layout/mdl-js-layout on body, any ideas? THX!

Could you post some code?
I have tinyMCE and MDL doing ok together, with inline editing.

here is the related code

You could try the solution described in #1369 .
Here's a excerpt:
document.addEventListener('mdl-componentupgraded', function(e) {
	//In case other element are upgraded before the layout
	if (typeof e.target.MaterialLayout !== 'undefined') {
		tinymce.init({
			selector: "textarea.richtext"
		});
	}
});

Please see this: http://stackoverflow.com/questions/15509484/multiple-tinymce-textareas.
Also, you can try:

If you´re dynamically adding the textarea to the DOM after the tinymce.init call, it won´t work right away
Delay - a lot - the init call (setTimeout) so you can be sure it fires after MDL has upgraded the DOM. If It works, there´s your problem.
Check if specific selector work, instead of mode: textareas

You could try the solution described in #1369 .

I will try this, thx!

Please see this: http://stackoverflow.com/questions/15509484/multiple-tinymce-textareas.
Also, you can try:
If you´re dynamically adding the textarea to the DOM after the tinymce.init call, it won´t work right away
Delay - a lot - the init call (setTimeout) so you can be sure it fires after MDL has upgraded the DOM. If It works, there´s your problem.
Check if specific selector work, instead of mode: textareas

The editor did shows up, but not able to edit

You could try the solution described in #1369 .
Here's a excerpt:
document.addEventListener('mdl-componentupgraded', function(e) {
//In case other element are upgraded before the layout
if (typeof e.target.MaterialLayout !== 'undefined') {
tinymce.init({
selector: "textarea.richtext"
});
}
});

adding that does solve the problem, thx!

How to solve this problem by using the tinymce as a component in angularjs.
Note: I can not edit the textarea tag.
code:
HTML
<form ng-controller="TinyMceController">
   <textarea ui-tinymce="tinymceOptions" ng-model="tinymceModel"></textarea>
 </form>

SCRIPT
var myAppModule = angular.module('myApp', ['ui.tinymce']);
myAppModule.controller('TinyMceController', function($scope) {
   $scope.tinymceOptions = {
     plugins: 'link image code',
     toolbar: 'undo redo | bold italic | alignleft aligncenter alignright | code'
   };
});

#1862

@ArleyOliveira Please use StackOverflow for support and integration assistance. This tracker is for problems relating to the code provided by MDL.
Thank you.

I know this issue has been closed, but i faced the same issue, a tinymce loaded with mdl, the textbox wont be editable.
I found previous solution highly suspicious, because i m not sure how often this handler will run and init the tinymce instance document.addEventListener('mdl-componentupgraded',
I d like to suggest instead to listen to the container element event mdl-componentupgraded
something like this, depending your code,
  <div class="mdl-textfield mdl-js-textfield
  {{if .Field.GetError}}is-invalid{{end}}
  {{if not .Field.IsPlaceHolderOnly}}mdl-textfield--floating-label{{end}}
  ">
     <textarea class="mdl-textfield__input"
     type="text"
     rows= "3"
     id="{{.Field.GetId}}">{{.Field.GetValue}}</textarea>
  </div>
  <script type="text/javascript">
    (function () {
      var container = document.getElementById("{{.Field.GetId}}").parentNode;
      container.addEventListener('mdl-componentupgraded', function(){
        tinymce.init({
          selector: '#{{.Field.GetId}}',
        });
      }, false);
    })();
  </script>

But thanks for the aforementioned solution, it put me on track!

I have this problem with another jQuery WYSIWYG editor, SCEditor while coding a theme for MyBB.
Can someone help me with it?

try on stackoverflow instead.

I did and got help. I'll leave it here just for reference. http://stackoverflow.com/questions/40656975/how-to-fix-material-design-light-sceditor-conflict


Should we have to install LaTeX software before using this tool?

The following errors occurred at runtime：
$ python2 analyze_trajectory_single.py --png ./laptop_vio_mono_MH_01/
Going to analyze the results in ./laptop_vio_mono_MH_01/.
The plots will saved in ./laptop_vio_mono_MH_01/plots.

Calculating errors...
Find evaluation configuration, will overwrite default.
The current evaluation configuration is {'align_type': 'posyaw', 'align_num_frames': -1}
Loading trajectory data...
loading dataset in ./laptop_vio_mono_MH_01/
Loading cached relative (odometry) errors from ./laptop_vio_mono_MH_01/saved_results/cached_rel_err.pickle
Loaded odometry error calcualted at [8.0, 16.0, 32.0, 24.0, 40.0]
...done.
Computing preset subtrajectory lengths for relative errors...
Use percentage [0.1, 0.2, 0.3, 0.4, 0.5] of trajectory length.
...done. Computed preset subtrajecory lengths: [8.0, 16.0, 24.0, 32.0, 40.0]
Aliging the trajectory estimate to the groundtruth...
Alignment type is posyaw.
To align all frames.
... trajectory alignment done.
Calculating RMSE...
Trajectory already aligned
...RMSE calculated.
Computing the relative errors based on preset subtrajectory lengths...
Relative error at sub-trajectory length 8.0 is already computed or loaded from cache.
Relative error at sub-trajectory length 16.0 is already computed or loaded from cache.
Relative error at sub-trajectory length 24.0 is already computed or loaded from cache.
Relative error at sub-trajectory length 32.0 is already computed or loaded from cache.
Relative error at sub-trajectory length 40.0 is already computed or loaded from cache.
Plotting absolute error...
sh: 1: latex: not found
Traceback (most recent call last):
File "analyze_trajectory_single.py", line 69, in
fig.tight_layout()
File "/usr/lib/python2.7/dist-packages/matplotlib/figure.py", line 1754, in tight_layout
rect=rect)
File "/usr/lib/python2.7/dist-packages/matplotlib/tight_layout.py", line 349, in get_tight_layout_figure
pad=pad, h_pad=h_pad, w_pad=w_pad)
File "/usr/lib/python2.7/dist-packages/matplotlib/tight_layout.py", line 126, in auto_adjust_subplotpars
tight_bbox_raw = union([ax.get_tightbbox(renderer) for ax in subplots])
File "/usr/lib/python2.7/dist-packages/matplotlib/axes/_base.py", line 3679, in get_tightbbox
bb_xaxis = self.xaxis.get_tightbbox(renderer)
File "/usr/lib/python2.7/dist-packages/matplotlib/axis.py", line 1075, in get_tightbbox
renderer)
File "/usr/lib/python2.7/dist-packages/matplotlib/axis.py", line 1058, in _get_tick_bboxes
extent = tick.label1.get_window_extent(renderer)
File "/usr/lib/python2.7/dist-packages/matplotlib/text.py", line 961, in get_window_extent
bbox, info, descent = self._get_layout(self._renderer)
File "/usr/lib/python2.7/dist-packages/matplotlib/text.py", line 352, in _get_layout
ismath=False)
File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_agg.py", line 229, in get_text_width_height_descent
renderer=self)
File "/usr/lib/python2.7/dist-packages/matplotlib/texmanager.py", line 675, in get_text_width_height_descent
dvifile = self.make_dvi(tex, fontsize)
File "/usr/lib/python2.7/dist-packages/matplotlib/texmanager.py", line 422, in make_dvi
report))
RuntimeError: LaTeX was not able to process the following string:
'lp'
Here is the full report generated by LaTeX:

Yes, by default we need that for plotting, or you can switch it off as described in this issue #1

I had latex install but got this similar error as above but saying at the end:
OSError: [Errno 2] No such file or directory: 'dvipng'
I installed dvipng package
sudo apt install dvipng
and it worked afterwards


Do not delete branch if it is a base branch of another PR

I think this is separate case from #6 and arguably it could be more common.
Let's say we have branch master, feature-x and feature-y (branched from feature-x).
And we have the following pull requests:

PR 1:
Base: master
Head: feature-x

PR 2:
Base: feature-x
Head: feature-y

Then if we merge PR 1 first before merging PR 2 and before changing the base on PR 2, GitHub does not show you the "Delete branch" option in the UI on PR 1.
However, this GitHub action does not check for that and through the API manages to delete the branch.
This results in closing PR 2 and if you then force-push into feature-y, you can change the base to master, but GitHub does not allow even reopening this PR again after it was force-pushed.
My suggestion is to follow the GitHub UI and do not delete a branch when it is a base branch for another PR, even if the PR where this branch is the head of the PR is merged.
I believe we could check this through a GitHub API call. I could try submitting a patch, but I wanted to get some feedback first.

Here's a diagram:
        ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
       │            PR 1
       ▼                              │
┌────────────┐                 ┌────────────┐
│   master   │                 │ feature-x  │◀ ─ ─ ─ ─ ─ ─
└────────────┘                 └────────────┘             │
          •◀────────────•◀───────────•
                                     ▲               PR 2 │
                                     │
                                     │                    │
                                     │             ┌────────────┐
                                     └──────•◀───• │ feature-y  │
                                                   └────────────┘

So if PR 2 is opened before merging PR 1 and PR 2 is still open at the time PR 1 is merged, feature-x should not be deleted when PR 1 is merged.


ITK 5.1.0 : Can't build because of ITKInternalEigen3

On Windows 7 64b
With Visual Studio 2019+Windows 10 SDK installed
With CMake 3.17.3
I can't build ITK 5.1.0, here is the CMake log :
`Setting build type to 'Release' as none was specified.
Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.
The CXX compiler identification is MSVC 19.26.28806.0
The C compiler identification is MSVC 19.26.28806.0
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe - works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Detecting CXX compile features - done
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe - works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Detecting C compile features
Detecting C compile features - done
Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.26.2.windows.1")
Performing Test C_HAS_WARNING-Wno-uninitialized
Performing Test C_HAS_WARNING-Wno-uninitialized - Failed
Performing Test C_HAS_WARNING-Wno-unused-parameter
Performing Test C_HAS_WARNING-Wno-unused-parameter - Failed
Performing Test C_HAS_WARNING-W3
Performing Test C_HAS_WARNING-W3 - Success
Performing Test C_HAS_WARNING-Wno-long-double
Performing Test C_HAS_WARNING-Wno-long-double - Failed
Performing Test C_HAS_WARNING-Wcast-align
Performing Test C_HAS_WARNING-Wcast-align - Failed
Performing Test C_HAS_WARNING-Wdisabled-optimization
Performing Test C_HAS_WARNING-Wdisabled-optimization - Failed
Performing Test C_HAS_WARNING-Wextra
Performing Test C_HAS_WARNING-Wextra - Failed
Performing Test C_HAS_WARNING-Wformat_2
Performing Test C_HAS_WARNING-Wformat_2 - Failed
Performing Test C_HAS_WARNING-Winvalid-pch
Performing Test C_HAS_WARNING-Winvalid-pch - Failed
Performing Test C_HAS_WARNING-Wno-format-nonliteral
Performing Test C_HAS_WARNING-Wno-format-nonliteral - Failed
Performing Test C_HAS_WARNING-Wpointer-arith
Performing Test C_HAS_WARNING-Wpointer-arith - Failed
Performing Test C_HAS_WARNING-Wshadow
Performing Test C_HAS_WARNING-Wshadow - Failed
Performing Test C_HAS_WARNING-Wunused
Performing Test C_HAS_WARNING-Wunused - Failed
Performing Test C_HAS_WARNING-Wwrite-strings
Performing Test C_HAS_WARNING-Wwrite-strings - Failed
Performing Test C_HAS_WARNING-funit-at-a-time
Performing Test C_HAS_WARNING-funit-at-a-time - Failed
Performing Test C_HAS_WARNING-Wno-strict-overflow
Performing Test C_HAS_WARNING-Wno-strict-overflow - Failed
Performing Test CXX_HAS_WARNING-W3
Performing Test CXX_HAS_WARNING-W3 - Success
Performing Test CXX_HAS_WARNING-Wno-long-double
Performing Test CXX_HAS_WARNING-Wno-long-double - Failed
Performing Test CXX_HAS_WARNING-Wcast-align
Performing Test CXX_HAS_WARNING-Wcast-align - Failed
Performing Test CXX_HAS_WARNING-Wdisabled-optimization
Performing Test CXX_HAS_WARNING-Wdisabled-optimization - Failed
Performing Test CXX_HAS_WARNING-Wextra
Performing Test CXX_HAS_WARNING-Wextra - Failed
Performing Test CXX_HAS_WARNING-Wformat_2
Performing Test CXX_HAS_WARNING-Wformat_2 - Failed
Performing Test CXX_HAS_WARNING-Winvalid-pch
Performing Test CXX_HAS_WARNING-Winvalid-pch - Failed
Performing Test CXX_HAS_WARNING-Wno-format-nonliteral
Performing Test CXX_HAS_WARNING-Wno-format-nonliteral - Failed
Performing Test CXX_HAS_WARNING-Wpointer-arith
Performing Test CXX_HAS_WARNING-Wpointer-arith - Failed
Performing Test CXX_HAS_WARNING-Wshadow
Performing Test CXX_HAS_WARNING-Wshadow - Failed
Performing Test CXX_HAS_WARNING-Wunused
Performing Test CXX_HAS_WARNING-Wunused - Failed
Performing Test CXX_HAS_WARNING-Wwrite-strings
Performing Test CXX_HAS_WARNING-Wwrite-strings - Failed
Performing Test CXX_HAS_WARNING-funit-at-a-time
Performing Test CXX_HAS_WARNING-funit-at-a-time - Failed
Performing Test CXX_HAS_WARNING-Wno-strict-overflow
Performing Test CXX_HAS_WARNING-Wno-strict-overflow - Failed
Performing Test CXX_HAS_WARNING-Wno-deprecated
Performing Test CXX_HAS_WARNING-Wno-deprecated - Failed
Performing Test CXX_HAS_WARNING-Wno-invalid-offsetof
Performing Test CXX_HAS_WARNING-Wno-invalid-offsetof - Failed
Performing Test CXX_HAS_WARNING-Wno-undefined-var-template
Performing Test CXX_HAS_WARNING-Wno-undefined-var-template - Failed
Performing Test CXX_HAS_WARNING-Woverloaded-virtual
Performing Test CXX_HAS_WARNING-Woverloaded-virtual - Failed
Performing Test CXX_HAS_WARNING-Wstrict-null-sentinel
Performing Test CXX_HAS_WARNING-Wstrict-null-sentinel - Failed
Performing Test have_avx_extensions_var
Performing Test have_avx_extensions_var - Success
Performing Test have_avx2_extensions_var
Performing Test have_avx2_extensions_var - Success
Performing Test CXX_HAS_DISABLE_OPTIMIZATION_FLAG
Performing Test CXX_HAS_DISABLE_OPTIMIZATION_FLAG - Failed
CMake Warning at CMake/itkExternal_Eigen3.cmake:58 (find_package):
By not providing "FindITKInternalEigen3.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"ITKInternalEigen3", but CMake did not find one.
Could not find a package configuration file provided by "ITKInternalEigen3"
with any of the following names:
ITKInternalEigen3Config.cmake
itkinternaleigen3-config.cmake

Add the installation prefix of "ITKInternalEigen3" to CMAKE_PREFIX_PATH or
set "ITKInternalEigen3_DIR" to a directory containing one of the above
files.  If "ITKInternalEigen3" provides a separate development package or
SDK, be sure it has been installed.
Call Stack (most recent call first):
CMakeLists.txt:466 (include)
CMake Error at CMake/itkExternal_Eigen3.cmake:60 (message):
ITKInternalEigen3 configuration faileed
REPORT:
-- Selecting Windows SDK version 8.1 to target Windows 6.1.7601.
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe -
broken
-- Configuring incomplete, errors occurred!
See also
"E:/InsightToolkit-5.1.0/build/vs2019/x64/ITKInternalEigen3-build/CMakeFiles/CMakeOutput.log".
See also
"E:/InsightToolkit-5.1.0/build/vs2019/x64/ITKInternalEigen3-build/CMakeFiles/CMakeError.log".
CMake Error at C:/Program
Files/CMake/share/cmake-3.17/Modules/CMakeTestCCompiler.cmake:60 (message):
The C compiler

  "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe"

is not able to compile a simple test program.

It fails with the following output:

  Change Dir: E:/InsightToolkit-5.1.0/build/vs2019/x64/ITKInternalEigen3-build/CMakeFiles/CMakeTmp

  Run Build Command(s):C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/MSBuild/Current/Bin/MSBuild.exe cmTC_74442.vcxproj /p:Configuration=Debug /p:Platform=x64 /p:VisualStudioVersion=16.0 /v:m && Microsoft (R) Build Engine version 16.6.0+5ff7b0c9e pour .NET Framework
  Copyright (C) Microsoft Corporation. Tous droits rÃ©servÃ©s.

    Compilateur d'optimisation Microsoft (R) C/C++ versionÂ 19.26.28806 pour x64
    testCCompiler.c
    Copyright (C) Microsoft Corporation. Tous droits rÃ©servÃ©s.
    cl /c /W3 /WX- /diagnostics:column /O2 /D WIN32 /D _WINDOWS /D "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /MD /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo"cmTC_74442.dir\Debug\\" /Fd"cmTC_74442.dir\Debug\vc142.pdb" /Gd /TC /errorReport:queue "E:\InsightToolkit-5.1.0\build\vs2019\x64\ITKInternalEigen3-build\CMakeFiles\CMakeTmp\testCCompiler.c"
  LINK : fatal error LNK1104: impossible d'ouvrir le fichier 'ucrt.lib' [E:\InsightToolkit-5.1.0\build\vs2019\x64\ITKInternalEigen3-build\CMakeFiles\CMakeTmp\cmTC_74442.vcxproj]

CMake will not be able to correctly generate this project.

Call Stack (most recent call first):
CMakeLists.txt:1 (project)

Call Stack (most recent call first):
CMakeLists.txt:466 (include)
Configuring incomplete, errors occurred!
See also "E:/InsightToolkit-5.1.0/build/vs2019/x64/CMakeFiles/CMakeOutput.log".
See also "E:/InsightToolkit-5.1.0/build/vs2019/x64/CMakeFiles/CMakeError.log".`

I don't think its related to Eigen, but it happens that Eigen is the first thing ITK is trying to compile.
There are problems passing the compiler to the Eigen sub-project.
The error is:
The C compiler

  "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.26.28801/bin/Hostx64/x64/cl.exe"

is not able to compile a simple test program.

Why are the differences between this report and our green CI in windows?

@chacha21 Could you provide the CMake options that you are using to compile ITK?

Since I have installed VS 2019 and Windows 10 SDK, I can't use Windows SDK 8.1 any more.
Thus before configuring anything in CMake, I set the CMAKE_SYSTEM_VERSION to 10.0, then run "Configure".
It fails with the above message before I access to second-stage customizing options.

This looks like either Visual Studio problem, or installation problem, or possibly a CMake problem, but not an ITK problem. Closing - reopen if you have some arguments as to why ITK should handle this.

After unsucessful uninstall/reinstall or "repairing" of Windows 8.1 SDK only, I finally "repaired" the while VS2017 installation, and now CMake  works.
Maybe CMake still has problems with the W10 SDK, but indeed that was not an ITK problem

Thanks for reporting @chacha21


Unable to create messaging project with different name then default

Describe the bug
I'm unable to create messaging project with random name
To Reproduce
Steps to reproduce the behavior:

Deploy enmase
Create infra
Create namespace
Create messaging project with metadata.name "test"

Expected behavior
Messaging project will be created
> oc get msgp -n app -o yaml
apiVersion: v1
items:
- apiVersion: enmasse.io/v1
  kind: MessagingProject
  metadata:
    creationTimestamp: "2020-07-20T11:33:32Z"
    generation: 1
    managedFields:
    - apiVersion: enmasse.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:status: {}
      manager: okhttp
      operation: Update
      time: "2020-07-20T11:33:32Z"
    name: default-1
    namespace: app
    resourceVersion: "1884274"
    selfLink: /apis/enmasse.io/v1/namespaces/app/messagingprojects/default-1
    uid: 9349dec0-4c15-44cd-a325-4b79bb0c1cd5
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Not a bug.   We want the messaging project to be a singleton within the namespace.  Fixing the name (we chose default), is the mechanism to achieve that.


@audacia/eslint-config - Angular 17

@audacia/eslint-config is not compatible with Angular ~17 because it references older versions of typescript-eslint/eslint-plugin and typescript-eslint/parser. I managed get around by having two versions of the said packages in the package.json like below
"@typescript-eslint/eslint-plugin": "^6.19.0 || ^5.13.0",
"@typescript-eslint/parser": "^6.19.0 || ^5.0.0",

I encountered this as well. Thanks for the workaround.

Resolved by #57 - v3.0.0 is now available


optimize Abacus

optimized result:
./openroad   ../../src/mdm/test/ICCAD/2022/reproduce/ipl-case3-gp.tcl
HPWL is: 27,479,632
HPWL is: 31,273,952
cost real time 0m4.627s

Is anyone still in charge of this repository？


add the program_name to logs

          I am thinking, given that we are going to publish the logs for all the node in a centralized space (like for metrics and influxdb) we could add the `program_name` here that we can get with something like:

auto getProgramName() -> std::string {
  /// \note This implementation only works for Linux
  char path[PATH_MAX + 1] = { '\0' };
  const auto path_length = readlink("/proc/self/exe", path, PATH_MAX);
  return ((path_length > 0) ? std::string(path) : (""));
}

Originally posted by @filippobrizzi in https://github.com/olympus-robotics/hephaestus/pull/201#discussion_r1836171979

I am not sure if this is needed. probably with the module and the source the point where the log is happening should be clear right?
if the overhead of adding this field later on is not too big, I would postpone this to a point where we feel that we need it...


Add social channel menu for easy access to all PWR social media

Links are in discord, add them as a menu thanks.

https://github.com/PWRcoin/PWRcoin/commit/7842699be1a66230bfada03799bd24dbdeffc55b


combine "palette selector", "pipeline properties" and "node properties" menus

Currently, we have menus on both sides of the pipeline editor canvas, this can be confusing for users, and severely reduce the available space when all menus are expanded.
I think we should try and combine the palette selector, pipeline properties and node properties menus into a single location, to help reduce clutter and improve clarity, I can see a couple of ways to do this.

OPTION 1: keep the menus "inside" the canvas, but group them on the same side

we would use a tabbed approach to swap between them, similar to how  pipeline properties and node properties behave right now

OPTION 2: create JupyterLab sidebar widgets for each (like our "Runtimes", and "Runtime Images" widgets)

a widget's position can be swapped between the left and right-side, allowing 2 widgets to be open at the same time (for example, the default JupyterLab "Property Inspector" widget is on the right side by default)

OPTION 3: move the pipeline properties and node properties into the JupyerLab "Property Inspector", and the palette selector into its own new sidebar widget

I don't know how we can hook into the "Property Inspector" but the PR which added it seems to imply that it's pluggable by implementing IPropertyInspectorProvider
If it's actually possible, this is probably the cleanest option, as it uses the existing "Property Inspector" widget, which is currently unused by elyra right now, and was designed for "cell/node" properties

Current Menu Locations:

Example with all menus expanded
(including "JupyterLab's native "Property Inspector", which does nothing on an Elyra canvas)

Addressing your options as listed:
Option 1 is actually how we originally wrote the palette and is supposedly still able to be switched to with a boolean value in when creating the PipelineEditorWidget. We could surface that value as a setting to allow users to switch back to that view, we would nee to see how well it's supported now though since it's been hard coded as true for so long the old view may not render correctly anymore. This would be the most realist option available to use.
Option 2 was raised and solidly shot down early in Elyra development for a couple of key UX issues. By moving that functionality out of the editor it can cause confusion. The sidebar widgets could be open without an editor open, thus causing confusion. If a user has multiple editors open (could be open side by side), which editor it's currently tied to would be confusing.
Option 3 has the same issues as option 2, but leveraging a core sidebar widget rather than making our own.
Overall I don't think there's a real issue here. The problem is some users try to use lab in a very small screen/window/resolution. This can cause the issue noted, but at the same time all of the side bars described are able to be collapsed and there are very few reasons (I can't think of any myself) where all of them would be open at once. I do think making the option I described in option 1 surface as a user setting would allow users to remove a sidebar if they have a use case that would warrant it though. This would mean taking the hard-coded value at https://github.com/marthacryan/elyra/blob/792319f93401e4e77b30ead23fa3229bd48f24fb/packages/pipeline-editor/src/PipelineEditorWidget.tsx#L996 and moving it to a user defined setting, then checking if the UI/UX is still fully featured when it is disabled (I'm 100% sure it's not fully featured even it is functional)

We should  probably revisit after the impact of https://github.com/elyra-ai/elyra/issues/2300 is understood

Note that the main reason to have the current UX is that the editor is and should be independent of Lab (which is one place where the pipeline editor is embedded). If we create a distributed UI, when we go to places like VSCode for example, or another application that needs to embed the pipeline editor, then things will not work consistently.

Note that the main reason to have the current UX is that the editor is and should be independent of Lab (which is one place where the pipeline editor is embedded). If we create a distributed UI, when we go to places like VSCode for example, or another application that needs to embed the pipeline editor, then things will not work consistently.

@lresende I understand the idea of allowing the canvas to be portable, but we already have links out to places that only exist in the Jupyterlab sidebar (e.g. "open runtimes", "open runtime images", "open component catalogs"):

@thesuperzapper Those buttons are actually not part of pipeline editor code, they are defined outside the editor and passed to it on creation. In fact that entire toolbar is an optional UI component (The old VSCode POC didn't have it).
Also note that those buttons open an outside tool, but that tool doesn't itself affect the pipeline in the way the canvas sidebars do.

The buttons were also added to establish (for the user) an association between the VPE and related metadata panels,  which, as you point out in https://github.com/elyra-ai/elyra/issues/2525, don't include a hint which JupyterLab extensions take advantage of the metadata.

Just had a chat with @ajbozarth - from a UX perspective I very much like the tabbed version like you have in the git extension

(changes, history, ...) in this case,
also icons with tool tips could be used to safe space, please let me know your thoughts...


Pseudorandom number generator ran2() is not thread-safe

I was trying to run the Kelvin-Helmholtz problem with OpenMP (kh.cpp with a modified athinput.kh-slip). The simulation would immediately terminate (Terminating with Terminate Signal, or something like that). Then I compiled with the -debug flag and got a segfault before any other output. I traced the segfault to the random number generator (line 72 in ran2.cpp). I suspect that the random number generator is not thread-safe.
A quick fix is to remove the #pragma omp on line 1342 of mesh.cpp, i.e. the following fixes the issue for me:
    if (res_flag == 0) {
//#pragma omp parallel for num_threads(nthreads)
      for (int i=0; i<nmb; ++i) {
        MeshBlock *pmb = pmb_array[i];
        pmb->ProblemGenerator(pin);
        pmb->pbval->CheckUserBoundaries();
      }
    }

Thanks for the repot. We are aware that ran2() is not a concurrent PRNG. It is compatible with MPI, but each rank iterates over the same sequence produced by rseed.
We should add an explicit trap to prevent this routine from being called inside a threaded region, and document it in the code and Wiki.
And eventually a thread-safe PRNG (Mersenne twister?) should be added to the code.

Std:: already have thread-safe RNGs
you can do
std::mt19937 rng;
std::uniform_real_distribution ran2(0.0, 1.0);
rng.seed(something_uint);
and sample numbers as value=ran2(rng)

@jlippuner can you post your modified input file and exact configure/run commands?

In terms of preventing runtime errors for those who call ran2() within their problem generator, I believe that we could simply make the 3x static variables in the function threadprivate. Or we could put a #pragma omp critical around the body of the function. Thoughts @jmstone ?

@felker Thanks for your quick response and I apologize for my delayed one. Here is my config:
./configure.py --prob kh -omp -hdf5 --include /usr/include/hdf5/serial/ --lib_path /usr/lib/x86_64-linux-gnu/hdf5/serial/
Your Athena++ distribution has now been configured with the following options:
  Problem generator:          kh
  Coordinate system:          cartesian
  Equation of state:          adiabatic
  Riemann solver:             hllc
  Magnetic fields:            OFF
  Number of scalars:          0
  Special relativity:         OFF
  General relativity:         OFF
  Frame transformations:      OFF
  Self-Gravity:               OFF
  Super-Time-Stepping:        OFF
  Shearing Box BCs:           OFF
  Debug flags:                OFF
  Code coverage flags:        OFF
  Linker flags:                -L/usr/lib/x86_64-linux-gnu/hdf5/serial/  -lhdf5
  Floating-point precision:   double
  Number of ghost cells:      2
  MPI parallelism:            OFF
  OpenMP parallelism:         ON
  FFT:                        OFF
  HDF5 output:                ON
  HDF5 precision:             single
  Compiler:                   g++
  Compilation command:        g++  -O3 -std=c++11 -fopenmp -I/usr/include/hdf5/serial/

My modified athinput.kh-slip is:
<comment>
problem   = Kelvin-Helmholtz instability
reference =
configure = --prob=kh

<job>
problem_id = kh-slip_8   # problem ID: basename of output filenames

<output1>
file_type  = hdf5       # Binary data dump
variable   = prim      # variables to be output
dt         = 0.1       # time increment between outputs

<time>
cfl_number = 0.4       # The Courant, Friedrichs, & Lewy (CFL) Number
nlim       = 100000    # cycle limit
tlim       = 5.0       # time limit
integrator  = vl2      # time integration algorithm
xorder      = 2        # order of spatial reconstruction
ncycle_out  = 1        # interval for stdout summary info

<mesh>
nx1        = 128       # Number of zones in X1-direction
x1min      = -1.0      # minimum value of X1
x1max      =  1.0      # maximum value of X1
ix1_bc     = periodic  # inner-X1 boundary flag
ox1_bc     = periodic  # inner-X1 boundary flag

nx2        = 64        # Number of zones in X2-direction
x2min      = -0.5      # minimum value of X2
x2max      = 0.5       # maximum value of X2
ix2_bc     = periodic  # inner-X2 boundary flag
ox2_bc     = periodic  # inner-X2 boundary flag

nx3        = 8        # Number of zones in X3-direction
x3min      = -0.125      # minimum value of X3
x3max      = 0.125       # maximum value of X3
ix3_bc     = periodic  # inner-X3 boundary flag
ox3_bc     = periodic  # inner-X3 boundary flag

refinement     = adaptive
numlevel       = 3
deref_count    = 5

num_threads = 48

<meshblock>
nx1 = 8
nx2 = 8
nx3 = 8

<hydro>
iso_sound_speed = 1.0
gamma           = 1.4       # gamma = C_p/C_v

<problem>
iprob = 1
amp   = 0.2
drat  = 2.0
vflow = 0.5
thr = 0.5

Here is the output I get:
./athena -i athinput.kh-slip
### Warning in Mesh::Initialize
The number of MeshBlocks increased more than twice during initialization.
More computing power than you expected may be required.
### Warning in Mesh::Initialize
The number of MeshBlocks increased more than twice during initialization.
More computing power than you expected may be required.
### Warning in Mesh::Initialize
The number of MeshBlocks increased more than twice during initialization.
More computing power than you expected may be required.

Setup complete, entering main loop...

cycle=0 time=0.0000000000000000e+00 dt=6.3237907014130560e-04
cycle=1 time=6.3237907014130560e-04 dt=6.3204117213331874e-04

Terminating on Terminate signal
time=6.3237907014130560e-04 cycle=1
tlim=5.0000000000000000e+00 nlim=100000

Number of MeshBlocks = 2368; 2240  created, 0 destroyed during this simulation.

zone-cycles = 1212416
cpu time used  = 1.5651121000000000e+01
zone-cycles/cpu_second = 7.7465122146841750e+04

omp wtime used = 3.3088790100009646e-01
zone-cycles/omp_wsecond = 3.6641291396134989e+06

With this small change, it works (this is a naive solution of just turning off OpenMP when calling the problem generator):
diff --git a/src/mesh/mesh.cpp b/src/mesh/mesh.cpp
index c97ce9e..7d0ce0a 100644
--- a/src/mesh/mesh.cpp
+++ b/src/mesh/mesh.cpp
@@ -1339,7 +1339,7 @@ void Mesh::Initialize(int res_flag, ParameterInput *pin) {
     }

     if (res_flag == 0) {
-#pragma omp parallel for num_threads(nthreads)
+//#pragma omp parallel for num_threads(nthreads)
       for (int i=0; i<nmb; ++i) {
         MeshBlock *pmb = pmb_array[i];
         pmb->ProblemGenerator(pin);

I like this solution.  Thanks Kyle!

On Oct 30, 2019, at 11:24 AM, Kyle Gerard Felker<EMAIL_ADDRESS>wrote:
Fixed upstream in the private repository for the next public release. Here is the patch that you can apply locally:
diff --git a/src/utils/ran2.cpp b/src/utils/ran2.cpp
index defedf1..18b99b6 100644
--- a/src/utils/ran2.cpp
+++ b/src/utils/ran2.cpp
@@ -45,6 +45,7 @@ double ran2(std::int64_t *idum) {
static std::int64_t idum2=123456789;
static std::int64_t iy=0;
static std::int64_t iv[NTAB];
+#pragma omp threadprivate(iy,iv,idum2)
double temp;
if (*idum <= 0) { // Initialize
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/PrincetonUniversity/athena-public-version/issues/28?email_source=notifications&email_token=ABB3XTUMVSSDMG3PT452YOTQRGRMHA5CNFSM4JEUDBWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECUTYRA#issuecomment-547961924, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABB3XTVHP6XRXSQML5H7FKTQRGRMHANCNFSM4JEUDBWA.

Actually, using threadprivate is extremely tricky and is normally avoided. For example, in the manual https://www.openmp.org/wp-content/uploads/OpenMP4.0.0.pdf you can find "The address of a threadprivate variable is not an address constant" - the program can create or destroy these variables depending on the number of currently running threads. These are not static variables in an ordinary sense. And if the threads are dynamic it is explicitly prohibited to use threadprivate (page 151 line 26).
Why use this particular RNG implementation in the problem generator? Just copy one from GSL or use standard library.

For @jlippuner's particular case, all calls to ran2() occur in the same parallel construct, and the omp parallel for uses the implementation-defined default scheduling type (probably static), so I dont think it is an issue here.
I agree with you that a different PRNG should be used , in general. But we leave that to application users with that specific, more complex need. Here, I just wanted to ensure that the simple problem generator compiles and runs correctly with OpenMP.


missing go.sum entry, error while importing

I keep getting this error
/home/anuj/go/pkg/mod/github.com/libsql/libsql-client-go@v0.0.0-20231116123136-ff4e46c3d3a1/libsql/internal/http/shared/statement.go:10:2: missing go.sum entry for module providing package github.com/antlr/antlr4/runtime/Go/antlr/v4 (imported by github.com/libsql/libsql-client-go/libsql/internal/http/shared); to add:
        go get<EMAIL_ADDRESS>/home/anuj/go/pkg/mod/github.com/libsql/libsql-client-go@v0.0.0-20231116123136-ff4e46c3d3a1/libsql/internal/http/shared/statement.go:11:2: missing go.sum entry for module providing package github.com/libsql/sqlite-antlr4-parser/sqliteparser (imported by github.com/libsql/libsql-client-go/libsql/internal/http/shared); to add:
        go get<EMAIL_ADDRESS>/home/anuj/go/pkg/mod/github.com/libsql/libsql-client-go@v0.0.0-20231116123136-ff4e46c3d3a1/libsql/internal/http/shared/statement.go:12:2: missing go.sum entry for module providing package github.com/libsql/sqlite-antlr4-parser/sqliteparserutils (imported by github.com/libsql/libsql-client-go/libsql/internal/http/shared); to add:
        go get<EMAIL_ADDRESS>/home/anuj/go/pkg/mod/github.com/libsql/libsql-client-go@v0.0.0-20231116123136-ff4e46c3d3a1/libsql/internal/ws/websockets.go:12:2: missing go.sum entry for module providing package nhooyr.io/websocket (imported by github.com/libsql/libsql-client-go/libsql/internal/ws); to add:
        go get<EMAIL_ADDRESS>/home/anuj/go/pkg/mod/github.com/libsql/libsql-client-go@v0.0.0-20231116123136-ff4e46c3d3a1/libsql/internal/ws/websockets.go:13:2: missing go.sum entry for module providing package nhooyr.io/websocket/wsjson (imported by github.com/libsql/libsql-client-go/libsql/internal/ws); to add:
        go get<EMAIL_ADDRESS>
Edit: i am using go version go1.21.4 linux/amd64 on Fedora

Sorry, my mistake. Running go mod tidy fixed it. Closing issue.


RTC-13831 Stop/restore C9Shell process when entering/leaving sleep/hibernation mode

This will improve battery consumption and fix C9 issues (can't call, hang up, change DND mode...)
https://perzoinc.atlassian.net/browse/RTC-13831

Closing because: "they are no more taking prs into 23.1.x branch"

This PR can be closed in favor of https://github.com/finos/SymphonyElectron/pull/1713


[ar] Translate multiple tiny files to Arabic

Translate to arabic tiny files at once
Fix part of : #37546

/lgtm
^ For Arabic, and I will defer to @sftim for the final approval/lgtm

/approve

/area localization

Hi @adowair,
Could we have LGTM on this please?
Thanks.

/lgtm

Hi @tengqm,
Could you please help us to approve this PR?
The Arabic localization team does not have permission to approve changes in the file static/_redirects. We made a minor change to it, and that's why we are currently blocked.
The PR has already LGTMed for the Arabic, but please don't hesitate if you have any questions or need any information that can help.
We really appreciate it,
Thank you.

The advice in https://github.com/kubernetes/website/pull/46172#issuecomment-2108995942 is useful but not the whole story.
SIG Docs leads are usually happy to add approval, but: as well as LGTM, please add an approval (using /approve) from an Arabic approver.
The PR won't merge, but Prow will still note the approval and that signifies to leads that it's OK to make the Arabic changes that are part of this PR. I don't think any SIG leads speak Arabic.

SIG Docs leads are usually happy to add approval, but: as well as LGTM, please add an approval (using /approve) from an Arabic approver.

@adowair already added /approve but as you know because of the external file _redirects that's out of our scope of approve the bot did not add the approve label so that's need of the leads to approve
https://github.com/kubernetes/website/pull/46172#issuecomment-2108995942

D'oh! You're right.

@sftim Can please help approve since the Ar community cannot approve changes in the file static/_redirects

@sftim Can please help approve since the Ar community cannot approve changes in the file static/_redirects

You've got the wrong contributor I'm afraid. With the mechanism we use today, you should ask a tech lead or SIG chair to approve this change.

@natalisucks @salaxander Can you help with this we are blocked

Given reviews from @sftim and at least one Arabic owner approving these changes (@adowair), I'm adding my approval as a SIG Co-Chair to unblock this localization work 🤝
/approve

@mboukhalfa @adowair In future, please feel free to use the alias @kubernetes/sig-docs-leads to ping all tech leads/chairs when you need an admin-level change. You can also ping our subproject owners @seokho-son and @a-mccarthy who can help triage 😸


Cannot read property 'then' of undefined

Python won't run as a jupyter notebook.  Jupyter itself work on computer, just not in vscode through python extension.  Don't know how to reproduce, it just stopped working one day.
Cannot read property 'then' of undefined

Dup of https://github.com/microsoft/vscode-jupyter/issues/4976


Try fixing CI

At first I was fixing the CI with setting the env variable: NODE_OPTIONS: --openssl-legacy-provider. But this only fixes the CI, not installing from source on user machine.
The second approach is taken from https://github.com/jupyterlab/jupyterlab/pull/11249

meeseeksdev please backport to 0.12.x


Alaska SPC Zone 1 issue

Steps to reproduce

I am trying re-project from state plane coordinates to lat/long values, and having issue with Alaska Zone1 coordinates. here is an example:

double[] xy = new double[2];

xy[0] = 0;
xy[1] = 0;
ProjectionInfo pStart = KnownCoordinateSystems.Projected.StatePlaneNad1927.NAD1927StatePlaneAlaska1FIPS5001;
ProjectionInfo pEnd = KnownCoordinateSystems.Geographic.NorthAmerica.NorthAmericanDatum1927;

Reproject.ReprojectPoints(xy, null, pStart, pEnd, 0, 1);
Console.WriteLine("converted: " + xy[0] + " " + xy[1]);

which converts state plane 0,0 to long/lat

114.22308156564786 45.31003150497525

but this coordinate do not belongs to US. US longitude should be negative value
projection works fine with other Alaska zones but having issue with Zone1 only

DotSpatial version: 4.0.656
Please let me know if I am using DotSpatial projection in wrong way

Are you sure its v4.0.656?

yes I am using the latest version from nuget

ok I must be way behind on updates. :) sorry.

@sindizzy is it working correctly on some previous version of the library for you?

I have been working with the 2.0 release for some time. I just realized there is now a v3 and a v4.


Fix owntracks test using libsodium

Description:

Move test to class with custom config setups and with config
validation.

Related issue (if applicable): fixes #
Fixes #3958
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Makes sense, I did not have libsodium installed during my last device_tracker cleanup so the test did not execute


react native ios manual plugin issue

It builds fine in local system but fails in dev ops when built through CI, error attached. Its probably because in manual integration we use npm run mm_build and Carthage which is not there in azure. Please help how can we do this manual integration in azure.

Hi @tarunasharma089, thank you for your question.
Could you please try following solution:

build MobileMessaging.framework locally as described in Manual integration - step 3 (Build MobileMessaging.framework).
copy MobileMessaging.framework to project you are trying to build in CI environment.
Perform 4,5,6 steps of Manual integration (Build MobileMessaging.framework) according to path to MobileMessaging.framework in your project.


feat: support zip command  #571

https://github.com/user-attachments/assets/aea84e72-9f49-4028-bcbd-550e5408a60d
@Jonghakseo I haven't reproduced the bug you said.

@Jonghakseo It was my negligence. Ha ha, it has been corrected now.


Adds a popup for CMItemSlots cooldown

Resolves #2328

I need to check how this works in CM13 since there is no popup there for magazine boxes (which is what prompted the github issue to be created), but there is still a cooldown.
The popup was originally intended for the knife rig, handled in line 315.
Either way, putting this in the handler for ItemSlotEjectAttemptEvent wouldn't work, since that would trigger any time CanEject is called, even if a null popup is passed, which includes when interaction verbs are created upon right clicking an entity.

alright

We made magazine boxes have no cooldown in the end since It would have affected every player. In the future the cooldown stuff probably needs to be moved to the cm holster component or its own since I don't think we are going to be using it in any other case, but for now it's fine staying in cm item slots component


Methods to draw on a Image

We should get inspiration from https://github.com/reneschulte/WriteableBitmapEx

I think a drawing/rastering API is out of the scope of an image read/write library. It should be separate. It can live in the same repository, but the base library should be architectured in a way that allow different drawing API over it (safe raw access to buffer data).

One thing the library could support is sub buffer manipulation.
For example if I set a single pixel in the image, it should only have a small buffer. And many format allow efficient modification of the image with chunks avoiding full image manipulation.
This would put the bases for a drawing library.
--
Nicolas Goy
https://www.kuon.ch
-------- Original Message --------
From: Guillaume Derex @.>
Sent: October 5, 2022 4:29:15 PM GMT+02:00
To: zigimg/zigimg @.>
Cc: Nicolas Goy @.>, Mention @.>
Subject: Re: [zigimg/zigimg] Methods to draw on a Image (#32)
I agree with @kuon , drawing methods might make the library much bigger, and would be bloat for anybody not needing that


[bug]: no invoke.bat or update.bat

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
6GB
What happened?
I have already tried to reinstall multiple times but invoke.bat and update.bat won't be created at the end of the installation (I'm using the 2.2.3 installer)
Screenshots
https://live.staticflickr.com/65535/52556638454_5c1077f9f9_o.png
Additional context
No response
Contact Details
No response

nvm


Using the component multiple times in the same parent

First of all, kudos for you work as this is a very simple yet fully working component. It's slim and I like it much more that those bloated ones :+1:
It is generally working well but when I use it in a v-for directive.
Context:
I have multiple articles in my form and each of them have a wysiwyg component. They are added and removed dynamically. So each form component can have 0+ wysiwyg content at any time.
<el-form-item
         v-for="(article, index) in campaign.articles"
         :key="index"
         :prop="'articles.' + index + '.value'"
         :id="`form_campaign_article_${index + 1}`"
       >

<wysiwyg :ref="wysiwyg_article_${index + 1}" v-model="article.content" />
...
Issue:
When I add a link to one of the wysiwyg all others get that link too.

Expected behavior:
The link should be added only to the current wysiwyg I'm writing on
I'd like to help if you can give me some directions on what I should look for to fix the issue

Same Issue here. Would be great if there is any solution for multiple Instances at one page

For those looking PR is in #24


Fix issue #50: Run integration test in integration-test phase, not test

introduce failsafe-plugin
-- surefire-junit47 is optional, but may be helpful later

integration test now uses the already packaged jar instead of
rebuilding the entire project which leads to strange
NoClassDefFoundErrors regarding StaticLoggerBinder$1
-- introduction of separate maven repo is required for this
which is cleaner anyway

Thanks for the review, @vackosar!


Handle non-existent apps gracefully.

Need to add ability to add non-existent applications' paths or bundle IDs.

Resolved in #40.


threadpoolctl 3.5.0

threadpoolctl 3.5.0
Destination channel: Defaults
Links

PKG-5068
dev_url:        https://github.com/joblib/threadpoolctl/tree/3.5.0
conda_forge:    https://github.com/conda-forge/threadpoolctl-feedstock/blob/main/recipe/meta.yaml
pypi:           https://pypi.org/project/threadpoolctl/3.5.0
pypi inspector: https://inspector.pypi.io/project/threadpoolctl/3.5.0

Explanation of changes:

...

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_52a3q1bre4/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:35: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: BSD-3-Clause
===== Final Report: =====
1 Error and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_583nxdq3xf/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:34: missing_pip_check: For pypi packages, pip check should be present in the test commands
===== Final Report: =====
1 Error and 0 Warnings were found


[folly/fbthrift/proxygen/wangle/fizz] update to 2<IP_ADDRESS>

Fixes https://github.com/microsoft/vcpkg/issues/32373
All feature test pass on the following triplets:

x64-windows
x64-windows-static

Usage test pass on x64-windows.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thank you!


Unable to connect 22621.2428

I tried running update as well

Duplicate of https://github.com/stascorp/rdpwrap/issues/2345


Split Out Instructions

The Bytecode.lean file is going to very quickly get big.  I think it makes sense to split out the various instruction groups into their own files.  Then, examples can be included for each instruction within each file.

Following EELs structure would make sense btw


Base&head parameters should not be required for pull_request.getAll

I don't think base and head parameters should be required.
https://github.com/mikedeboer/node-github/blob/master/api/v3.0.0/routes.json#L1628

This was fixed a while ago.


unexpected room display name

reported by @dandellion:dodsorf.as
https://github.com/matrix-org/riot-android-rageshakes/issues/880
riot chatroom named  and 4k others

it means the room name displayname was not retrieved : it might be a client or a server issue


use nodesource ppa for node 0.12

nodesource made a separate ppa for nodejs 0.12 to not force people to upgrade

Thanks!


Correcting Wrong Extension of Verilog Language file extension in programming-languages-to-file-extensions.json

Currently Extension for Verilog Language file on master branch is wrong
So Updated Verilog Language File extension in file-extension.json
"Verilog": [".veo"] to "Verilog": [".v",".vh",".vlg"]
Reference : https://www.intel.com/content/www/us/en/programmable/quartushelp/17.0/reference/glossary/def_v.htm#:~:text=v%2C .,any other standard text editor.
https://en.wikipedia.org/wiki/Verilog

@loubnabnl, @liyongsea @lingjzhu  , Please review and merge if you think this is ok


[improve][broker] make split namespaces bundle async

(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #15043
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #
Motivation
make split namespaces bundle async
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

see https://github.com/apache/pulsar/issues/15043

#16411 has been merged ..


Spec: Comments on Cryptographic Sig Questions

Hello.. attached are some comments / thoughts on the crypto aspect.   I think the overall goal should probably be secure, flexible, avoid really opinionated decisions, but also be decisive enough to avoid implementation ambiguity.
The most sensible way forward on this part of the standard I think it to make this optional until it's been reviewed and is mostly supported.   It might make sense here to use Digests as a stepping stone to Digital Signatures.

-## 3 Cryptographic signatures
-NOTE: I know this is sounding crazy, but it just might work! The main problem is that this is very slow.
Every file in the container’s root filesystem must be read. It is, however, very flexible and quite portable. Some things to decide here:

-* How carefully do we specify the digest file? (bad, but accurate name)

Well that's easy ....I think.. just make the container digest manifest recommended but optional like the .asc digital sig in rocket for the time being, that way it doesnt break anything existing.
like...
container.img (container file / archive format for distribution)
container.sig (digital signature)
container.sha256 (sha digest)
There's a few options overall when speaking of signatures, hashes, etc...  I'd think:
(1) Do Nothing
(2) Digest: SHA2 / SHA3 sum of container file  (only provides very basic integrity , but low barrier to implementation)
(3) HMAC:  (not really useful in this context , so this is probably out)
(4) Digital Signature: (this is the gpg style sigs like in Ubuntu PPA, Rkt, etc. Integrity + Authentication + Non-Repudiation)
I'd say at minimum you need SHA2/SHA3 digest of the container file, and probably very important to get to a digital signature in the standard sooner than later.  But Digest could be a step along the way to Signatures... Anyway the digital signature should support open standards either way, which brings me to...
Digital Signature Formats:
You've got two or three options here I'd think for the sigs.  Basically you can put them in CMS (aka PKCS#7 aka RFC 5083) format, or you can put them in OpenPGP format (aka RFC4880).  Both formats are equally annoying.

CMS / PKCS#7 / RFC 5083
OpenPGP / RFC4880
TUF / The Update Framework

I noticed TUF got mentioned as well, so I included that... Here is the link to the standard for TUF...
https://github.com/theupdateframework/tuf/blob/develop/docs/tuf-spec.txt
The CMS format is ASN.1 while OpenPGP is ascii armor.  The former is used in S/MIME, the latter in OpenPGP.  Regarding TUF, while I like how it uses JSON and I love how it's in Python....  However.. if you look at the TUF standard you can see (A) the project doesn't seem to be quite production-ready yet , though it is promising, and (B) the TUF standard does not have the million implementations that the former two have.
But I would definitely say pick one digital signature format, rather than allow users to implement all three.  That'd be a mistake ...  I think for digital signatures anyway, there's just so much that can go wrong already, best to keep it concise and clear.   Honestly I'd vote for OpenPGP here.
So either way I suppose .... you're gonna have to use an external lib or tool in either case.  Probably better just to make it like SHA256 or SHA512 and/or OpenPGP.

-To ensure that containers can be reliably transferred between implementations and machines, we define a flexible hashing and signature system that can be used to verify the unpacked content. The generation of signatures is separated into three different steps, known as "digest", “sign” and “verify”.

K... If you verify (digital signature and/or authenticated encryption) the packed content, you also verify the unpacked content.  They are the same as far as I'm aware, at least for a given instant in time.
Meaning:  If an attacker flips any one bit in the compressed container image, the uncompressed container will fail validation just the same as if the attacker flips any one bit in the uncompressed filesystem.  So there only really needs to be one validation here I'd think, at the container level , but I certainly could be missing something ...
Unless we are talking about protection of data-at-rest or files-in-a-container-on-my-laptop-from-day-to-day
Okay, first, let's separate the two mentions above about digest, sign, verify...  I like how they are seperated into steps ... I actually support that ...
So first we separate  what are Digests/Hashes from Digital Signatures..   Then we can separate them again based on whether they are at the Container Level (single container file) or at the internal filesystem level (within the container uncompressed filesystem).
I'd suggest going for the low hanging fruit and define these in regards to the container first, in light of the idea that a bit flip in either the container or the filesystem is one and the same .  That's the really important part.
Adding filesystem-level hashes is probably a good idea, but might be a bit much at this point.  I can already  (maybe?) see issues arising with OverlayFS etc. . . I wonder if you've got multiple layers there might be a bit of interpretation about when to calculate the changes, how to perform the merge, whiteout files, etc in regard to sigs and digests.
On top of that .... as much as I like the digest-of-all-files idea personally (having hashes/digests and/or digital sigs of all files in the container filesystem)... this seems like it's almost a re-implementation of something like Tripwire.

-The purpose of the "digest" step is to create a stable, summary of the content, invariant to irrelevant changes yet strong enough to avoid tampering. The algorithm for the digest is defined by an executable file, named “digest”, directly in the container directory. If such a file is present, it can be run with the container path as the first argument:

Well , running a digest/hash AND/OR digital signature on a compressed container image is the sort of critical juncture.  Meaning:  If I get owned...  it's gonna be when I download and run a container image from a host somewhere in the Russian Business Network autonomous system , heh.
Not when I start the same container for the second time in a day.
Anyway,  the point at which I first run teh container... that's (I think) where malicious code is most likely to enter my system , my container network, etc -- when I grab a container image someone made from a repository .
If I download that image and it does no harm, and then a week later I create a file on the filesystem... I don't see how that's the same risk as when I first obtain the container archive...  So again, I like the idea of having a digest of the files in the container ... buuttttt
There's just alot of questions with maintaining a list of hashes within the container's filesystem... .I suppose it wouldn't hurt to make it optional. . . Anyway .. with a digest / signature of the packed container , it's pretty straightforward to unpack and verify, and it's also straightforward for me to repack and/or sign if I want to share the image.
Maintaining the digest manifest of some or all container files is not a bad idea at all, but it's gonna be slowww in the event of a large filesystem, especially considering we can't use SHA1 anymore, so we have to use SHA2 or SHA3 , and that could be painful with really large files....
Another issue I'm wondering is at what point do we overwrite the 'digest manifest' , to say "Yes, I modified some file like /etc/blah.conf, and I want to update it's SHA2 digest AND it's digital signature"... It just seems like it could create a lot of headache for users , but not really offer much in terms of security ...  Like the standards would have to define the conditions on which to overwrite the digest manifest with user approval...
Anyway, so I suppose what I'd say is that I'd be opposed to a digest of the entire container filesystem on a file-by-file basis... it might make sense to include a digest of certain key directories and binaries, but even still , the concern I'd have there is "How do you present to the user such that they are warned about filesystem changes , but they can also accept or reject them as line-items?"   That's really what integrity would mean here, and it'd be way granular and in the weeds.
As opposed to just 'container matches' or 'container does not match'  like how OpenSSH works with signatures.
I mean maintaining user-friendliness is not the responsibility of this standard, but it just seems like it'd be creating a nightmare scenario up the stack in terms of repackaging a container back into an image, or warning a user about fileysstem changes one-by-one etc.  I think if file-level digest is included, it's got to be optional or else really really restricted by default.  But I just think it's not any additional security, not in the context of what a digest does... and that's provide integrity in the event of malicious 'bit-flip' type attacks...

I think that approach gives a strong compromise between implementation headache, usability, simplicity, etc.

-$ $CONTAINER_PATH/digest $CONTAINER_PATH
-```
-The nature of this executable is not important other than that it should run on a variety of systems with minimal dependencies. Typically, this can be a bourne shell script. The output of the script is left to the implementation but it is recommend that the output adhere to the following properties:

-* The script itself should be included in the output in some way to avoid tampering

This is a good idea and important, but gotta remember that digest will only ensure integrity in relation to some __external trust anchor that might even be malicious. __.  We really need digital signatures to really prevent tampering... Because otherwise how do we know we haven't gotten a fake SHA-sum
Really we need to start with digest, but make digital signatures recommended but not required... this way we can achieve authentication + integrity.
-* The output should include the content, each filesystem path relative to the root and any other attributes that must be static for the container to operate correctly
Sure , this make sense as far as making like a Tripwire-like feature for containers.  Which I think is cool, and I wouldn't complain personally if it was in there... But I sure wouldnt' want to implement this, nor would I want to wait for my slow container to load b/c it's running filesystem checksums that are probably redundant...  I'm just not 100% sure filesystem-level digests are necessary if you add in a SHA2/SHA3 digest and digital sigs of the container archive file...
-* The output must be stable
I think this might be a challenge ....  heh... but I suppose if you limit the directories we are adding to the digest this could work...
Again, I don't see what benefit this approach has over simply just calculating a digest and digital sig over a squashfs compressed container...  People probably are not going to be distributing 'loose-files' (aka non-tgz) uncompressed containers for the most part I'd think, so the security threat inherent in distribution is the main problem...
Data-at-rest can be secured using all the existing solutions already available , ala Tripwire, Snort, DM-Crypt, TrueCrypt, etc.
This all looks good below besides just the main objection... I definitely agree with the use of GPG / OpenPGP.  X509 might not be an appropriate choice unless we all want to ride on top of the crappy CA infrastructure.  I definitely do not want to do that , heh. . X509 kind of brings with it the rot of OpenSSL I'd fear.
I'd just say use GPG / OpenPGP keys, that's a tested and proven solution without the bloat of OpenSSL.
Sign

-The output, known as the container’s digest, can be signed using any cryptography system (pgp, x509, jose). The result of which should be deposited in the container’s top-level signatures directory.
-To sign the digest, we pipe the output to a cryptography tool. We can demonstrate the concept with gpg:
- -$ $CONTAINER_PATH/digest $CONTAINER_PATH | gpg --sign --detach-sign --armor > $CONTAINER_PATH/signatures/gpg/signature.asc -
-Notice that the signatures have been added to a directory, "gpg" to allow multiple signing systems to coexist.
-### Verify
-The container signature can be verified on another machine by piping the same command output, from the digest to a verification command.
-Following from the gpg example:
- -$CONTAINER_PATH/digest $CONTAINER_PATH | gpg --verify $CONTAINER_PATH/signatures/gpg/signature.asc - -
The rest of this all looks good to me;  thanks for reading my comments

@bitshark Thank you for the commentary.
We've taken this part of the specification in a slightly different direction, mostly due to many of the points you've brought up here. After some research, we found that several transports fail to properly transmit file system meta data. The need for a transport-agnostic manifest addresses this issue while also providing a signable target.
Check out #5 and #11 for some more background.
Let me know if we can close this issue.

Yeah let's close it , this was just to share some thoughts .  This is a non-issue for sure --  I'll close this out and I'll go read the update info in #5 and #11


Seperate storage into assigments and permissions/roles

In yii/yii2 it always bothered me that the 3 entities assigment, role and permission are all stored in the same backend: it's either all PHP or all DB.
But in my experience it would be much more convenient to split these up and even make it a bit more flexible:

Roles and permissions to me are semi-static. They only change if you write a new controller or action or modify other parts of your app. So they are strongly coupled to your app code. That's why I prefer to also hardcode them in PHP e.g. in an array structure in a file or in a class (instead of calling $manager->addPermission() which feels unnessecary tedious)
Assigments are dynamic data. They are different for each instance of the app, depend on the user base and can frequently change. There's usually an admin UI to manage them. They are perfect to be stored in DB just like the user table.

It would be great if the package would make it easier to support this kind of separation or even provide a base implementation for this.

Thanks for reminder, @mikehaertl. That is, indeed, great to have RBAC roles, rules and permissions in a PHP files but assignments in DB.

Side effects with case:
Add role 'test'
Add assignments for role
Remove role 'test'
Add role 'test'
One Storage - all ok, assignments on role - empty.
Two storage - assignments exists

In work...

Completed


"Ziduri", "Costieni", "Cuculeasa", "Heliade Rădulescu", "Lanurile" and "Zoița" are listed in the drop-down menu

Description:
"Ziduri", "Costieni", "Cuculeasa", "Heliade Rădulescu", "Lanurile" and "Zoița" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Ziduri" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Ziduri, BUZĂU (Ziduri)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Costieni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Costieni, BUZĂU (Ziduri)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Cuculeasa" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Cuculeasa, BUZĂU (Ziduri)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Heliade Rădulescu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Heliade Rădulescu, BUZĂU (Ziduri)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Type "Lanurile" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Lanurile, BUZĂU (Ziduri)".

Step 10
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 11
Type "Zoița" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Zoița, BUZĂU (Ziduri)".


Add access to settings through tray menu

Hello,
Here is a small change to allow settings from tray menu. It's really usefull when your using frameless window (coming in another PR) to gain space.
I've tested on Linux Mint 17.
Regards,

Thanks for your PR.
To everyone willing to test, the builds can be found here:
https://circleci.com/gh/St-Ex/desktop/22#artifacts

Working nicely on Windows 10 btw

Tested on Windows 10. Thanks!


Change Language Mode at the top level menu

I use Change Language Mode a lot, but Simply  > C# doesn't work, you have to select > Change Language Mode and then the language, this is too cumbersome to do every time. Any suggestion?

Used a separate key binding. But would be nice to support it at the top level.


Players can't connect to server (You are already connected to this network)

Stacktrace
https://gist.github.com/pauhull/77fbb0070b66a903ad84edc70c3b78e2
Actions to reproduce
Error appears randomly
CloudNet version
[17.01 16:24:10.550] INFO:
[17.01 16:24:10.550] INFO: CloudNet Blizzard 4.0.0-RC5 4ec2a84d
[17.01 16:24:10.550] INFO: Discord: <https://discord.cloudnetservice.eu/>
[17.01 16:24:10.551] INFO:
[17.01 16:24:10.551] INFO: ClusterId: b524d946-****-45c6-****-4a8fcdf47225
[17.01 16:24:10.551] INFO: NodeId: Node-1
[17.01 16:24:10.551] INFO: Head-NodeId: Node-2
[17.01 16:24:10.552] INFO: CPU usage: (P/S) 1.84/6.4/100%
[17.01 16:24:10.552] INFO: Node services memory allocation (U/R/M): 4096/4096/25600 MB
[17.01 16:24:10.552] INFO: Threads: 70
[17.01 16:24:10.553] INFO: Heap usage: 135/456MB
[17.01 16:24:10.553] INFO: JVM: Debian 17 (OpenJDK 64-Bit Server VM 17.0.4+8-Debian-1deb11u1)
[17.01 16:24:10.553] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: beta
[17.01 16:24:10.553] INFO:

Other
Issue uniqueness

[X] Yes, this issue is unique. There are no similar issues.

Might be related to the thrown exception - other listeners that are listening for the event are not executed if one listener throws an exception. In general this is the first report of issues with player connections in v4, so I doubt that there is an issue in the general player handling process that is related to the issue.

same problem here. Happens when you timeout

Also it‘s already reported :)

#982

I think this can be closed as outdated and not reproducable


Removing binding at service account creation

The setup helper (/helpers/setup.sh), in line 86 has a remove iam policy binding for a newly created service account, which didn't have that policy in the first place, This causes the script to complain that the service account doesn't have the relevant permissions. I believe it should be replaced by an add like all the other bindings in the file:
86 gcloud projects remove-iam-policy-binding ${PROJECT_ID} \
87    --member="serviceAccount:${SERVICE_ACCOUNT_ID}" \
89    --role="roles/iam.serviceAccountUser" \
90    --user-output-enabled false

Thanks for catching this, it looks like we resolved this typo in 31b12194c7b4153cb8f3ce7a422bd058381734cd. Since it looks like this issue was resolved I'm going to close out this issue; if this is still a problem please comment on this pull request and we can continue this conversation.


DD4T.ViewModels

This pull request is to merge in Josh Einhorn's Domain View Models For Tridion Library, now renamed DD4T.ViewModels.
The code is dependent on new changes made to the .NET Content Model, specifically the addition of ITemplate as well as the addition of PublicationNumber to the IModel interface. PublicationNumber is used to streamline the XPM support code. I couldn't use PublicationId as the property name because there was at least one other inheriting class (RepositoryLocalItem) that already had this property as a string.
The major change that was made to the original DVM4T library is to use the native DD4T Content model instead of an intermediary content model. The actual functionality should remain unaltered though it has not been tested.
Currently, the DD4T.ViewModels namespace is somewhat isolated from the other code, requiring implementers to pass a valid IModel object to the IViewModelFactory. I suspect this can be best done within a Controller, or the IViewModelFactory may be merged into the DD4T.Factories assembly so implementers can use it more seamlessly.

I wrote this in the pull request -- but just wanted to remind again that this is dependent on a change to the Content Model which is not actually part of this repo and the dependency appears to happen through a NuGet package, so that's going to have to get updated to actually build this!

Hi Josh, I'm trying to merge your pull request, and release a new DD4T.Model in the process. There has to be a better way than 'PublicationNumber'. It's not clear to me why we couldn't use ITemplate.Publication.Id for example.
Maybe you can find me on Skype today or tomorrow?

Hey Quirijn,
Sorry didn't get to this until just now, replying here because you're likely sleeping.
Great question -- I do agree there must be a better option. It really just comes down to XPM support and the way that I set up IViewModel. So IViewModel just has one property and it's an IModel which was chosen since it's the only common base class (besides IRepositoryLocal) that was shared between all the interfaces that I believe would be valid to build a View Model on. For example, Component Presentation, Component Page, Keyword, etc.
The problem is that IModel doesn't actually have any properties so it required a whole lot of type checking to do anything. PublicationNumber was merely a shortcut for XPM to check if XPM was enabled for that model.
The other way besides tons of type checking is to create a new base interface (or modify existing IModel) to really contain some meaningful data. Either that, or I could switch IViewModel to use IRepositoryLocal instead of IModel since it contains everything I need -- I guess I just thought the "IModel" fit better :smile:

So I just tried switching my use of IModel to IRepositoryLocal -- it nearly worked but ran into just one road block: IComponentPresentation extends IModel but not IRepositoryLocal since of course a Component Presentation doesn't technically have a Title and Id . . .
So 2 possible ideas:

Move the Publication property from IRepositoryLocal to IModel
Allow IComponentPresentation to extend IRepositoryLocal

The actual implementation can just direct everything to the properties of the Component e.g. the Id of the CP is the Id of the Component

Of course I could do away with all of that and just use type checking before attempting to access something like Publication ID -- just seems wasteful since it's so close to working.

We've just merged the code into the core using a separate pull request on the new core.

:+1:


TinyMCE error 500 on displayable links that prevents from creating links

Hello people,
I'm having an issue with TinyMCE that I can't create links inside the editor. Whenever I attempt to create a link, it throws an Error 500 in console.
I have looked around in Google and found this two links:
https://github.com/stephenmcd/mezzanine/issues/1365
https://stackoverflow.com/questions/2492452/problem-with-insert-update-links-with-tinymce
I used both suggestions but it doesn't work on production, only in localhost.
The project runs Mezzanine 4.2.3, uses Django 1.11 and has HTTPS.
Any suggestions?
Thanks in advance.
Melvin
PD: Posted this on the Mezzanine Google Group

This is already reported in #1634


Switch string concatenation to interpolation.

I'm holding this for the moment as I'm introducing lots of changes (including new folder structure) with the new PR  (customization) and some of these changes already include string interpolation syntax.

I'm holding this for the moment as I'm introducing lots of changes (including new folder structure) with the new PR  (customization) and some of these changes already include string interpolation syntax.

Closing to re-evaluate it after v5 is solid.


How to get the initial_state of GRU

I have already defined a GRU using Keras, How to get the initial_state (h_0) of the GRU? Any help will be appreciated！

Hi @danieljf24 , have you found a way to find out h_0 of GRU? With initialization of "zeros" it's simple. How about "orthogonal"? Thanks!


typing: Fix errors related to typing notifications.

Commit 1: Fix "Missing stream_id" server error.
Commit 2: Fix assertion error when narrowed to a non existing stream.

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

Merged, thanks @prakhar1144!
It's possible the actual bug here is that narrowed_by_topic_reply should not return true with an invalid stream ID; but that's probably going to be a lot easier to fix once we've done search pills.
@evykassirer @amanagr FYI just since you've been working on somewhat adjacent things.


featureDocker example hive-broker-doris

Proposed changes
add new docker example: hdfs-broker-doris

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Sign in with Azure - Page Not Found

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
Emulator 4.14.1
Platform: Windows 10
Describe the bug
Attempting to login to Azure to access various services for a bot configuration file
To Reproduce

Steps to reproduce the behavior:
Start the Emulator
Go to File > Sign in with Azure
The "Sign in with an Azure" panel appears.
Click on "Sign in with Azure" button
A window appears "Page not found."

Expected behavior
There should be the Azure authentication window
Screenshots
Additional context
This has worked on this specific machine in the past.
Things that I've tried:

Reinstalling emulator
Verifying azure account - Full access via chrome & portal.azure.com & powershell
Reviewed other similar bug reports
Cleared the cache (emulator)

[bug]

Hi @dinobrago,
Could you try clearing the Emulator state (File -> Clear state) and try signing in again? I was able to sign-in to Azure on version 4.14.1 on Windows.

Yes, I tried that and it did not work. Tried it again per your request with no effect. Same “Page not found” result.
From: Anish Prasad @.>
Sent: Wednesday, July 20, 2022 10:04 AM
To: microsoft/BotFramework-Emulator @.>
Cc: Dean Goddette @.>; Mention @.>
Subject: Re: [microsoft/BotFramework-Emulator] Sign in with Azure - Page Not Found (Issue #2393)
Hi @dinobragohttps://github.com/dinobrago,
Could you try clearing the Emulator state (File -> Clear state) and try signing in again? I was able to sign-in to Azure on version 4.14.1 on Windows.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/BotFramework-Emulator/issues/2393#issuecomment-1190531987, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJ2N2V3BJK3CJSV6LWTZO5LVVAWRXANCNFSM54BERL4A.
You are receiving this because you were mentioned.Message ID: @.***>

Strange. We're unable to reproduce this scenario. Could you check the dev console when you try to sign in and show us what errors appear there?

When I open the console, I see the attached image. When I attempt to log in to Azure, I do not see any additional entries in the console.

I installed the emulator on another machine (a vm on the same machine actually) and I can log into Azure fine.

I understand. Any documentation on how to do a complete wipe?

To finish up:

I tried uninstalling and doing a deep clean of all emulator references. Reinstalled, same problem.

Finally some success:
2. Uninstalled 4.14. Downloaded 4.8 (picked a random). With this version, I can login to azure.
I may spend some time working up through different versions but is that of any value?


Algolia search not returning matches

I've configured Algolia search with GitHub Pages via Travis CI.
I can see in the Algolia dashboard that my site is being indexed:

Searching my site (with a matching string) doesn't return any results, nor does it say "No results":

However, if I search with a string that doesn't match any string in my site, I do get the "No results" message:

Finally, if I type a matching string in the search box after I've entered in a non-matching string, the "No results" message persists and I still get no search results:

Environment

Basically Basic version: 1.4.1
Ruby gem or remote theme version:
Jekyll version:
Git repository URL: https://github.com/RobertsLab/sams-notebook
GitHub Pages hosted (if yes provide URL to site): https://robertslab.github.io/sams-notebook/
Operating system: Ubuntu 16.04
Browser: Firefox

Expected behavior
Return matching search results.

I've seen this before on my personal site. Don't think it has anything to do with the theme.
If you log into your Algolia account and click on the index, there are many configurations you can make. I've never messed with them, but there are all sorts of things related to what sort of attributes are indexed, returned, synonyms, stop words, typos, etc etc etc.
It probably needs to be configured some.

OK, thanks for the info.
Also, I wouldn't be surprised if it was related to Issue #81. Haven't had time to test since I made those changes.


Feature review

Edit and add your description here @namnguyen20999

Also:

Please reindent line 19 in OccupantReview.h and line 21 in HouseReview.h
(Best practices) On line 20 in OccupantReview.h and line 22 in HouseReview.h, add  // <namespace_name> at the end of the line, like on line 62 of DatabaseFIle.h:

You also created this branch from main instead of dev, please rebase this branch on to dev. If you don't know how to, let me know and I can do it for you, or give you the instructions if you want to do it yourself.


Add backend capabilities to chat and generate

This commit refactors the backend selection and server initialization
process for both the generate and chat functionalities within the
application. The changes include:

Abstracting the backend selection logic by utilizing the backends
module, which dynamically determines the appropriate backend based on
the configuration file or auto-detection if no configuration is set in
the serve section of config.yaml (serve.backend)

Encapsulating the conditional logic for checking if the selected
backend is LLAMA

Streamlining the exception handling for backend determination and
server initialization, ensuring that any failures in these processes
are clearly communicated to the user and result in a graceful exit.

These modifications enhance the code's structure, making it easier to
understand and extend in the future, especially as new backends or
initialization requirements are introduced.
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>ON-TOP of https://github.com/instructlab/instructlab/pull/1415
Checklist:

[x] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

It looks like we need to resolve this design doc first?  https://github.com/instructlab/dev-docs/pull/81
From the looks of that PR, it doesn't look like we have consensus on how to incorporate the backends into the CLI commands.

Closing for https://github.com/instructlab/instructlab/pull/1442.


white line

https://i.imgur.com/BMSJ3vi.png
I keep getting a white line every time take a pic.... the dimension of the white line generally remains the same however the position of the line is random...
(i just noticed while looking at the pic again it could do with the fact i dragged a selection, paused the drag, then continued to get a full screen  pic.....hope that makes sense....)

Read https://github.com/jomo/imgur-screenshot/issues/32 and https://github.com/jomo/imgur-screenshot/issues/75


Use !capabilities("long.double") to handle gamma converging on noLD systems

In particular
  # gamma converging on noLD systems!
  #  expect_error(
  #    ssd_fit_dists(data, dists = "gamma"),
  #    "^All distributions failed to fit[.]$"
  #  )

see https://github.com/r-lib/testthat/issues/940 for more information

use to skip where necessary