html-like labels

digraph G {
  "Welcome" [ shape=box, label=<

left	mid dle	right

> ];
    "Welcome" -> "To";
    "To" -> "Web";
    "To" -> "GraphViz!";
  }

results in the error:
Warning: Not built with libexpat. Table formatting is not available. in label of node Welcome
(sorry can't work out how to stop Markdown intepreting the table).
I'm up for helping implement this if it makes sense.

Which build of Viz.js are you using? The example you quoted should be supported -- it works for me on the demo site: http://mdaines.github.io/viz.js/
I've edited your issue to fix the Markdown formatting. You need to use backticks on both sides of the code block, and put them on lines by themselves, like this:
```
digraph G {
...
}
```

Thanks, you are right. I had some problems with the latest build which I have now resolved so the experiments I did where the html-like labels did not work were the version here: http://webgraphviz.com/


Builder not available

I would like to use the tool to build the definition file (def-builder.mikepenz.com) but your domain is expired.

@JordanGout thanks :D had activated auto renew. Strange that it did not inform me.
Will be live gain within a few hours (after the domain renewal was processed)


Delete the concentrated liquidity feature flag

Now that CL has been live for almost a year, I think the feature flag should be removed. Will help save code complexity and prevent an accidental toggle of it

It's already been removed in many places, but yes we need to do a full cleanup and remove everywhere.

opened a bounty


Fixes issue when previewing linked content items

Had previews failing to match up the content when, using a Multi node picker on the grid block to select its content that is rendered. This is how we are creating reusable blocks, so no content would show on a preview.
Setting the variation context resolved this.

Thanks!


fix the x and y axes on the heatmap to be consistent with generated matrix

Change the axes to be consistent in the error analysis heatmap: the y-axis dropdown only leads to a 1d vertical heatmap, and x-axis dropdown only leads to a 1d horizontal heatmap.  When both are selected, a 2d heatmap is creates with the y-axis feature on the vertical side and the x-axis feature on the horizontal side.  Note x and y axis order in dropdowns were flipped to be more consistent with matrix notation (rows, columns, where y-axis corresponds to rows and x-axis to columns)

when I select feature 2 only it still renders a matrix instead of a single row
is this caused by test data or code issue?

@xuke444 this is just bad test data, it doesn't happen in the actual widget


JNDI prepStmtCache + can't register mbean

Environment
HikariCP version: 2.6.0
JDK version     : 1.8.0_111
Database        :  MySQL 5.6
Driver version  : 5.1.38

I found an example using ds object, but do these properties work in JNDI configuration?
ds.addDataSourceProperty("prepStmtCacheSize", 250);
ds.addDataSourceProperty("prepStmtCacheSqlLimit", 2048);
ds.addDataSourceProperty("useServerPrepStmts", true);
And also I can't register MBean
18-May-2017 02:25:37.269 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class com.epam.heroes.rest.util.ApplicationListener
org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [HikariDataSource (MyDataSource)] with key 'dataSource'; nested exception is javax.management.InstanceAlreadyExistsException: MXBean already registered with name com.zaxxer.hikari:type=PoolConfig (MyDataSource)
at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625)
at org.springframework.jmx.export.MBeanExporter.registerBeans(MBeanExporter.java:550)
at org.springframework.jmx.export.MBeanExporter.afterSingletonsInstantiated(MBeanExporter.java:432)
When I remove "registerMBeans=true" property from JNDI config,
I'm still getting MBean with statistics for dataSource.
Tried to setExcludedBeans and change registrationPolicy on MBeanExporter, but it didn't help.

Here are some JNDI examples.
Regarding the JMX name conflict, this implies that you have two pools in the same JVM with the same "poolName" configured.  Either configure two different names, or leave the poolName property unset, in which case HikariCP will auto-number them.

I gave JNDI resources different names, but it didn't help.

http://stackoverflow.com/questions/28607506/disabling-jmx-in-a-spring-application

Finally, I found the problem.
There was @EnableMBeanExport annotation which exported PoolConfig bean for the first time,
and registerMbeans="true" option did it once again.
But, another question is:
How can I set up prepared statements pool within JNDI xml config?


[MIEB] Add more image classification and zero shot classification datasets

Second batch of image classification datasets, which covers

MNIST

[x] Linear probe
[x] zero shot

FER2013

[x] Linear probe
[x] zero shot

Stanford Cars

[x] Linear probe
[x] zero shot

BirdSnap

[x] Linear probe
[x] zero shot

EuroSAT

[x] Linear probe
[x] zero shot

Checklist

[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

For EuroSAT, it might be due to the class label names not having a space in between words (AnnualCrop vs annual crop land in the paper). It's hard to tell beyond the 5 examples in the paper though (i.e. what should something like Industrial be formatted to).
In [1]: from datasets import load_dataset
In [2]: ds = load_dataset("timm/eurosat-rgb")
In [3]: ds["test"].features
Out[3]:
{'image': Image(mode=None, decode=True, id=None),
 'label': ClassLabel(names=['AnnualCrop', 'Forest', 'HerbaceousVegetation', 'Highway', 'Industrial', 'Pasture', 'PermanentCrop', 'Residential', 'River', 'SeaLake'], id=None),
 'image_id': Value(dtype='string', id=None)}

This commit fixes the issue and matches the paper's performance with B/32 @ 49.7.


Intention of Converting Entities in RadGraph into Non-sensitive Numbers

Hi, I have a question about the code in preprocessing of RadGraph. What's the intention of converting all entities' names into non-sensitive numbers? I am also working on the same dataset and wondering if there are some special concerns.
Thank you and look forward to hearing from you!

Hi Yating,
It simply means making text labels to number for training i.e. lung -> 0, plural -> 1, left -> 2. No more special concerns :)

Thanks for quick answer! Is there any advantages to do this instead of directly feeding the text labels to training? To save training time or memory?

Thank you for answering! Now my confusion is solved. Thanks a lot!


Struggling to get detail in final LOD

Hello,
I am attempting to upload a 6.5 billion point cloud and I am struggling to get the quality I am looking for. The point cloud is a combination of terrestrial laser scan data and photogrammetry data generated using PhotoScan. It was all imported into Cyclone, aligned, and exported out as one dataset. It is a large dataset attempting to digitally document petroglyphs, which are frequently only a few inches long, so the detail is important. I am using Potree 1.5RC
I have tried quite a few conversion settings starting with the basics:
PotreeConverter.exe d:\projects\2017_projects\lavabedspotree\Photogrammetry_Final_043017.pts -o d:\projects\2017_projects\lavabedspotree\potree_conversions\final\ -p combined_data -f xyzirgb
This gave me near the quality I was hoping for, and wrote 100% of the points, but point spacing wasn't quite close enough and was not uniform at the final level.
I have attempted to manually set the levels and spacing, but I have only got worse results:
 c:\PotreeConverter_1.5RC_windows_64bit>PotreeConverter.exe D:\Projects\2017_Projects\LavaBedsPotree\Photogrammetry_Final_043017.pts -o D:\Projects\2017_Projects\LavaBedsPotree\potree_conversions\final3 --generate-page combined_data -f xyzirgb -s .5 -l 8
My understanding is that the above settings should yield 8 LoDs, with a final level point spacing of around 2mm, but resulted in only 5 LoDs and roughly 6cm point spacing. Most of the LoDs seem to be spent on viewing from extreme distances.
The latest attempt can be found here.
And here is the contents of the cloud.js file:
    "version": "1.7",
    "octreeDir": "data",
    "projection": "",
    "points":<PHONE_NUMBER>,
    "boundingBox": {
        "lx": -374.268753,
        "ly": -150.593033,
        "lz": -2.77626,
        "ux": 356.381638,
        "uy": 580.057358,
        "uz": 727.874131
    },
    "tightBoundingBox": {
        "lx": -374.268753,
        "ly": -150.593033,
        "lz": -2.77626,
        "ux": 356.381638,
        "uy": 135.152145,
        "uz": 62.325241
    },
    "pointAttributes": [
        "POSITION_CARTESIAN",
        "COLOR_PACKED"
    ],
    "spacing": 0.5,
    "scale": 0.01,
    "hierarchyStepSize": 5
}

I have been struggling with this for a few weeks now and any insight would be greatly appreciated. I probably should have asked for help sooner!

I am having a similar problem
instead of having a detailed hierchy I only get
"hierarchyStepSize": 5
in the cloud.js file, no information on hierarchy
how do I get something like that?
`	"hierarchy": [
	["r", 8376],

	["r0", 16089],

	["r2", 9061],

	["r4", 542],

	["r00", 10625],

	["r02", 9626],

	["r04", 5448],

	["r06", 2554],

            ...`

do I have to enter these levels manually in the js file?
I am guessing that the information should be in the r.hrc file but I don't how how to retrieve it
the other option is that I running a previous version of potree (1.3) that took the hierarchy from the js file and that the current  version (1.8) takes it from the hrc files
That means that I have to update my potree version and convert again all the pointclouds that I have loaded (10, it is not that much for the moment)...or install the 1.3 version, but then I loose all the bug fixes.
Am I understanding everything correctly? what do you recommend?
thank you


Runtime issues with dynamic properties in App types

Here's a small example:
struct TokamakDemoApp: App {
  @ObservedObject var count = Count(value: 0)

  var body: some Scene {
    WindowGroup("Tokamak Demo") {
        Text("\(count.value)")
    }
  }
}

crashes with:
RuntimeError: memory access out of bounds
    at strlen (<anonymous>:wasm-function[47490]:0xb8643d)
    at $sSS7cStringSSSPys4Int8VG_tcfCTf4nd_n (<anonymous>:wasm-function[20390]:0x556bae)
    at $sSS7cStringSSSPys4Int8VG_tcfC (<anonymous>:wasm-function[20389]:0x556b68)
    at $s7Runtime19NominalMetadataTypePAAE11mangledNameSSyF (<anonymous>:wasm-function[8313]:0x2150cb)
    at $s7Runtime13ClassMetadataV10toTypeInfoAA0eF0VyF (<anonymous>:wasm-function[8168]:0x20e6a9)
    at $s7Runtime13ClassMetadataVAA19TypeInfoConvertibleA2aDP02todE0AA0dE0VyFTW (<anonymous>:wasm-function[8192]:0x20f2e3)
    at $s7Runtime8typeInfo2ofAA04TypeC0VypXp_tKF (<anonymous>:wasm-function[8660]:0x223bcd)
    at $s11OpenCombine16ObservableObjectPA2A0cD9PublisherC0d10WillChangeE0RtzrlE06objectfG0AEvg (<anonymous>:wasm-function[1705]:0x88986)
    at $s11TokamakDemo5CountC11OpenCombine16ObservableObjectAadEP16objectWillChange0giJ9PublisherQzvgTW (<anonymous>:wasm-function[16762]:0x443ce3)
    at $s11TokamakCore14ObservedObjectV16objectWillChange11OpenCombine12AnyPublisherVyyts5NeverOGvg (<anonymous>:wasm-function[11415]:0x2b6422)

This occurs in Views as well.
Update:
@State also has some issues. Here's a small example:
struct TokamakDemoApp: App {
  @State private var count: Int = 0
  var body: some Scene {
    WindowGroup("Tokamak Demo") {
      Button("\(count)") { count += 1 }
    }
  }
}

The count starts with the number 207884. 🤨

Thanks, I'm looking into it.

The state becomes corrupt within the injectEnvironment function. Making it generic instead of operating on Any fixes for the first injection, which is called from makeMountedApp where the generic type of the app still known, but as soon as it's wrapped in _AnyApp it's erased completely. I'm looking for a solution/workaround now, but lmk if you have any ideas.

The current signature I use is func injectEnvironment<T>(from environmentValues: EnvironmentValues, into element: inout T), it doesn't require changing anything in the body.

I'm still not sure if it's a bug in the Runtime library or Swift runtime metadata itself. I'm seeing weird behavior with type(of:) API too, which is a part of the standard library. I haven't got good ideas how to diagnose or reproduce it outside of Tokamak for a good test case, but thinking of a workaround, I wonder if adding another generic argument to StackReconciler of App type would help. We then would always have the app type known statically. It is already known, we just type-erase it when wrapping in _AnyApp. We probably wouldn't even need _AnyApp type to exist then.
What remains a mystery to me is why this doesn't happen to AnyView and View types. The bigger problem will be if this is reproducible for _AnyScene and DynamicProperty fields on custom scenes, I'll try to verify this in my mounted-scene branch tomorrow.

I actually have seen this issue with ObservedObject in Views while working on Toolbars, but I haven’t been able to replicate it on a smaller scale.


Convert some missing layers

Patch to convert more Lora layers, however there are still missing layers and I'd like some help for this!
There is an example PEFT lora model that is not loading all its layers:
https://www.dropbox.com/scl/fi/30y9yn26ao8pnwch7z1ex/test_lora.zip?rlkey=r6kvgzwvrqm9tnw4jz8ctgu2f&st=7rootbqk&dl=0

Tested and the seems to work fine.
If you mean these:
PixArt: LoRA conversion has missing keys! (probably)
['csize_embedder.mlp.0.lora_down.weight', 'csize_embedder.mlp.0.lora_up.weight', 'csize_embedder.mlp.2.lora_down.weight', 'csize_embedder.mlp.2.lora_up.weight', 'ar_embedder.mlp.0.lora_down.weight', 'ar_embedder.mlp.0.lora_up.weight', 'ar_embedder.mlp.2.lora_down.weight', 'ar_embedder.mlp.2.lora_up.weight']

Those you can safely ignore if your LoRA is for PixArt sigma. They're the keys for micro conditioning which sigma doesn't actually use. That's why the warning very creatively says "(probably)" lmao
One missing link is support for LoRAs that train the text encoder. That's something that doesn't seem feasible in terms of support at the moment, unless the entirety of the LoRA loader function gets rewritten OR we use/enforce the PixArtT5FromSD3CLIP node with the comfy built-in T5 model/LoRA logic when loading.

I still believe there are missing weights, i.e. I see there are biases in the lora that the code is not taking, is there something we can do to support that?


Get all rules, skus etc for a single product does not seem to be supported

get_products_rules(options={}) returns all rules for all products.  Is this intentional, as I don't see it documented in API docs?
Shouldn't there be a get_product_rules(product_id) method (and similar for sku and other product related data)
If you think those should be included I will send pull request.  Please let me know.
Alex

This has been added on the new 1.0.0.beta release. Please give it a try!


Fix finding headers when cross compiling

When cross-compiling extension modules using build_ext, get_python_inc() may be called to return the path to Python's headers. However, it uses the sys.prefix or sys.exec_prefix of the build Python, which returns incorrect paths when cross-compiling (paths pointing to build system headers).
To fix this, we use the INCLUDEPY and CONFINCLUDEPY conf variables, which can be configured to point at host Python by setting _PYTHON_SYSCONFIGDATA_NAME. The existing behavior is maintained on non-POSIX platforms or if a prefix is manually specified.
This was originally submitted to stdlib distutils as https://github.com/python/cpython/pull/22440, but unfortunately they are no longer accepting patches to it even though setuptools still uses stdlib distutils by default.
I tested this with the netifaces package, which compiles an extension module and fails with the following error if it is cross-compiled from x86_64 to armv7l without this patch, due to the word size difference:
  In file included from /nix/store/c84d97qz2x7yfaijcjwapvrnbwlkljs0-python3-3.8.7/include/python3.8/Python.h:63,
                   from netifaces.c:1:
  /nix/store/c84d97qz2x7yfaijcjwapvrnbwlkljs0-python3-3.8.7/include/python3.8/pyport.h:726:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
    726 | #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
        |  ^~~~~
  error: command 'armv6l-unknown-linux-gnueabihf-gcc' failed with exit status 1

After applying this patch and setting _PYTHON_SYSCONFIGDATA_NAME and SETUPTOOLS_USE_DISTUTILS appropriately, the build succeeds.
The stdlib distutils version of this patch is currently applied in nixpkgs (https://github.com/NixOS/nixpkgs/pull/98915) and we have not observed any breakage.

Thanks for the contrib.
I don't have a lot of experience with the sysconfig module. Right now, there's a lot of work going on right now to refactor sysconfig to enable better configurability by different platforms, so it's possible this change will conflict with some of those efforts.
Is there a test that could be added to this PR that would help capture the missed expectation (and thus fail before and pass after the patch)?

Would you be willing to take another look at this patch? I have rebased it and reworked it a bit (not visible unless the PR is reopened). I will also explain more thoroughly how we (nixpkgs) use this patch to enable cross-compilation of Python packages with extension modules, as well as the challenges involved in developing an automated test.
We use the following techniques to make cross-compilation work:

Apply this patch to either stdlib distutils (before setuptools 60) or the bundled distutils in setuptools.
Add the directory containing the _sysconfigdata module for the host platform Python installation to PYTHONPATH, so that it can be imported from build platform Python.
Set _PYTHON_HOST_PLATFORM to the correct value for the host platform (e.g. linux-armv7l)
Set _PYTHON_SYSCONFIGDATA_NAME to the appropriate value for the host platform (e.g. _sysconfigdata__linux_arm-linux-gnueabihf).

setup.py is executed using build platform Python (by necessity, since the build machine can't normally run host platform binaries), but the sysconfig module returns data from the host platform Python installation, due to _PYTHON_SYSCONFIGDATA_NAME.
If the package contains extension modules, eventually distutils.sysconfig.get_python_inc() will be called to get the location of the Python headers. Without this patch, the build platform headers will be returned, since get_python_inc() returns paths relative to sys.base_prefix or sys.base_exec_prefix. This causes problems when the build platform word length doesn't match the host platform, resulting in errors like the following:
In file included from /nix/store/01kia41csjia67pry1rv828i9pvnnqfq-python3-3.9.12/include/python3.9/Python.h:50,
                 from btrfsutilpy.h:27,
                 from error.c:20:
/nix/store/01kia41csjia67pry1rv828i9pvnnqfq-python3-3.9.12/include/python3.9/pyport.h:741:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
  741 | #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
      |  ^~~~~

This patch avoids this problem by relying on sysconfig to provide the include paths. With _PYTHON_SYSCONFIGDATA_NAME set appropriately, the include directories will be returned from host platform Python.
The latest version of the patch will always use sysconfig on posix if the relevant config variables are defined, otherwise it will fall back to the current behavior.
I have been having trouble coming up with an effective and simple automated test due to the amount of infrastructure required. I think you would need multiple Python installations in order to demonstrate how _PYTHON_SYSCONFIGDATA_NAME can affect the return value of get_python_inc(). IMO, the most important thing is ensuring that existing (non-cross) use cases are not affected by this change.


feat: Liquibase Dialect

https://contribute.liquibase.com/code/

[x] Initial module liquibase + started develop (create YdbDatabase.java + CreateIndexGeneratorYdb.java) #32
[x] CreateTable sql generator https://github.com/ydb-platform/ydb-java-dialects/pull/33
[ ] impl LockService using Coordination Service YDB.
[x] Support YDB Types (e.g CHAR change to Text, integer change to Int32) https://github.com/ydb-platform/ydb-java-dialects/pull/34
[ ] Full alter table support
[ ] Integration test using https://github.innominds.com/liquibase/liquibase-test-harness
[ ] README.md

[ ] Initial module liquibase + started develop (create YdbDatabase.java + CreateIndexGeneratorYdb.java) #32

The world needs this stuff! Commoooon let's goo

Done!


Collector should cope with cache volumes missing

Cache volumes can be missing from the Apache traffic server stats (this can be controlled via config). But the collector does not cope with this very well.
Traceback (most recent call last):
File "/usr/bin/trafficserver_exporter", line 9, in
load_entry_point('trafficserver-exporter==0.0.1', 'console_scripts', 'trafficserver_exporter')()
File "build/bdist.linux-x86_64/egg/trafficserver_exporter/trafficserver_exporter.py", line 61, in main
File "build/bdist.linux-x86_64/egg/prometheus_client/core.py", line 50, in register
File "build/bdist.linux-x86_64/egg/prometheus_client/core.py", line 86, in _get_names
File "build/bdist.linux-x86_64/egg/trafficserver_exporter/collector.py", line 45, in collect
File "build/bdist.linux-x86_64/egg/trafficserver_exporter/collector.py", line 486, in parse_metrics
UnboundLocalError: local variable 'volume' referenced before assignment
Submitting an (minor) issue to fix this, a check required to make sure we have volumes.

Thank you for the report!  Fixed in https://github.com/gdvalle/trafficserver_exporter/pull/8.
Please re-open if you still have issues!


Fraud detection

[Enter feedback here]

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

ID: cd37bcea-463c-a743-8755-8909ec4768c9
Version Independent ID: 1869b0bd-27b8-3ffc-ccfe-71ad2a2bcc8c
Content: Real-time fraud detection - Azure Example Scenarios
Content Source: docs/example-scenario/data/fraud-detection.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @alexbuckgit
Microsoft Alias: pnp

To help us understand your ask better, can you please share more details on what more information you would like to be added to this document? Thanks.

This azure-docs repository deals about feedback ((like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions, etc.) related to particular Azure document page so if issue is intended to update / correct / enhance anything in an Azure document then please share Azure document link / URL and share the feedback related to it.

We will now close this issue. Please share the details when you get a chance and tag me in a comment. I will reopen it and we will gladly continue the discussion.


 We still need to test the effect of camera distortion and the precision of the calculations.

I've added a sub task for this (:

I have written test result in overleaf

I added detection to the cross in the middle of the course frame.


now where do i set the server settings, termux still wont start in acode

Question, do we add the server in the settings.json?
Originally posted by @webmaster-exit-1 in https://github.com/bajrangCoder/acode-plugin-acodex/issues/56#issuecomment-2052433462

I don't think questions are being answered anymore, there's like 6 open issues. Sigh, womp womp

oh.


Error in two methods in TestNetCoreConsole ---> C# Tutorial (Desktop)

Describe the bug
"LocalAudioTrack" and "LocalVideoTrack" does not contain a definition for "CreateFromDeviceAsync".
To Reproduce
Steps to reproduce the behavior:

Run the code:
`// Record video from local webcam, and send to remote peer
if (needVideo)
{
Console.WriteLine("Opening local webcam...");
localVideoTrack = await LocalVideoTrack.CreateFromDeviceAsync();
videoTransceiver = pc.AddTransceiver(MediaKind.Video);
videoTransceiver.DesiredDirection = Transceiver.Direction.SendReceive;
videoTransceiver.LocalVideoTrack = localVideoTrack;
}
         // Record audio from local microphone, and send to remote peer
         if (needAudio)
         {
             Console.WriteLine("Opening local microphone...");
             LocalAudioTrack.
             localAudioTrack = await LocalAudioTrack.CreateFromDeviceAsync();
             audioTransceiver = pc.AddTransceiver(MediaKind.Audio);
             audioTransceiver.DesiredDirection = Transceiver.Direction.SendReceive;
             audioTransceiver.LocalAudioTrack = localAudioTrack;
         }`

See errors:
Error CS0117 "LocalAudioTrack" does not contain a definition for "CreateFromDeviceAsync".
Error CS0117 "LocalVideoTrack" does not contain the definition for "CreateFromDeviceAsync".

Expected behavior
I wanted to run and debug the code.
Screenshots

There's not even that method!
Environment

Platform: [e.g. Windows Desktop]
Architecture: [e.g. Debug Any CPU]

Additional context

I have the latest version of the package installed: 2.0.0-preview.1.
If you install any version before that, VERY many methods will not be visible!!!

Neither the C# Desktop tutorial nor the TestNetCoreConsole are using the code you pasted. Where is that from?
This is the old 1.0 API you are trying to use; see the Migration Guide for details.

https://github.com/microsoft/MixedReality-WebRTC/blob/0b26ccdcd4abaee38e57c0c46c144d05d0793f06/examples/TestNetCoreConsole/Program.cs#L52-L57

Ни в учебнике по C # Desktop, ни в TestNetCoreConsole не используется вставленный вами код. Откуда это?
Это старый 1.0 API, который вы пытаетесь использовать; подробности смотрите в Руководстве по миграции .

https://github.com/microsoft/MixedReality-WebRTC/blob/0b26ccdcd4abaee38e57c0c46c144d05d0793f06/examples/TestNetCoreConsole/Program.cs#L52-L57
I think I figured it out. Thank you for your help :)

https://microsoft.github.io/MixedReality-WebRTC/manual/cs/helloworld-cs-signaling-core3.html


how to- connect to ipam with token

Hello,
I've installed appsvcs-templates with version 1.10.
I'm trying to connection fast templates into an generic ipam provider- NetBox.
When accessing to Netbox API I need to provide a token (which I've already created) as authorization header, instead of username and password.
is there any way that I can use an Authorization header instead of username and password in the ipam settings ?

Authorization token in url is not supported by netbox.


Handle protocol errors from the screensaver extension

Was getting:
thread 'main' panicked at 'internal error: entered unreachable code: Could not match extension event', /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/xcb-1.1.1/src/error.rs:301:17

After some poking, found that the error was coming from the screensaver extension, which I am trying to use.

Realized this doesn't work; opened issue #177 instead.


[bug] berry harvester has no specified tool

describe the bug
The berry harvester has no specified tool. This makes it extremely slow to mine, and it doesnt drop anything either. It should probably use a pickaxe or an axe.
reproduction
Steps to reproduce the behavior:

place berry harvester
attempt to mine it with pickaxe, axe, shovel, sword, etc...
mine it very slowly, and then recieve nothing when it does break

version
bodaciousberries-1.3.3+mc1.18.2

this issue has been fixed in version 1.4.0 which will be released today. The berry harvester is mined with an axe and the juicer is mined with a pickaxe. I've also added a particle texture to the juicer so that particles don't show up as missing textures when breaking. Thank you for reporting!


Frequent crash on <IP_ADDRESS> when running multiple cameras

Run 2-4 cameras at once on <IP_ADDRESS> and it will crash with a variety of errors withing 1 minute....

I think this is related to using right mono sensor through a NN node.


Remove container plan

Signed-off-by: Nikolay Maslarski<EMAIL_ADDRESS>It seems to be identical to linux-rating-plan.

Coverage remained the same at 93.244% when pulling 56a3c4a6784320f30da5c8db47392fb1de82e45f on SAP:remove-container-plan into 2827750af1d164e11668fc2bfdf3f3054c543949 on cloudfoundry-incubator:master.

Coverage remained the same at 93.244% when pulling 56a3c4a6784320f30da5c8db47392fb1de82e45f on SAP:remove-container-plan into 2827750af1d164e11668fc2bfdf3f3054c543949 on cloudfoundry-incubator:master.

Yeah, this is a duplicate that was probably used for testing. Thanks for catching it.


Use correct syntax for adding label in dockerfile

Why:
Docker labels are specified in Dockerfiles with an equals sign as per official documentation (already linked in the docs).
The currently documented method for linking GitHub repositories to GHCR packages isn't valid.
Ref https://github.com/github/docs/issues/2587
What's being changed:

Check off the following:

[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks so much for opening a PR for this fix @hardbyte! I'll update the branch and get this merged once tests are passing 🍏

Thanks so much for opening a PR for this fix @hardbyte! I'll update the branch and get this merged once tests are passing 🍏

Thanks so much for opening a PR for this fix @hardbyte! I'll update the branch and get this merged once tests are passing 🍏

Thanks so much for opening a PR for this fix @hardbyte! I'll update the branch and get this merged once tests are passing 🍏


MNT: Re-rendered with conda-smithy 3.1.12 and pinning 2018.10.01

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.


Fix test run_diskless2.sh with LARGE_FILE_TESTS

ret: https://github.com/Unidata/netcdf-c/issues/1162
The test nc_test/run_diskless2.sh fails
when LARGE_FILE_TESTS is enabled.
Since the goal of the test was to test out
diskless+persist on a reasonably large file,
I fixed by just limiting the file size to
1000000000L bytes.

Merging into the 4.6.2 branch, which will find its way upstream into master.

This fixed the test for me as well. I believe the important change for my issue is https://github.com/Unidata/netcdf-c/pull/1175/files#diff-a439789174da533fb46301fe425e8f86R94


Slack Channel Engagement 11/21

Hi @channel! We are excited to announce our Pathways to Open Science program will be back in 2025!! (Save the date and registration to come.) Thank you for being here and a part of our community (star emoji)
We'll be sharing a tool, tip, or resource every Thursday until our program begins! This week I attended the Data for Black Lives Conference in Miami, FL. It was an incredible and inspiring gathering of activists, movement builders, and researchers using data to revolutionize our world while centering justice and equity. Today I want to point you towards their website and youtube channel where you can check out the live streams from the meeting and learn more about their resources and work. It is such an honor to be in a community with you all, we need it now more than ever. Looking forward to gathering soon!

[ ] post to slack channel


[Segment Replication] Ensure replica's store always contains the previous commit point.

Description
This change:

Updates the cleanup and validation steps on replicas after a replication event occurs to prevent deleting files that are still required by the latest commit point.
Computes and sends replicas a list of recently merged away files that are still referenced by the primary's latest commit point.  This allows replicas to fetch these files if not present locally.  This can happen when a replica falls multiple commit points behind or if it starts after a primary has already existed and is in this state.
Update initial recovery sequence of replicas to copy from primary before lighting up as active.  This fixes bug where replicas could not be added after primary.
Prevent replicas from attempting to a force merge if segrep is enabled.

Issues Resolved
closes #2331
Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Outside of my review comments and the changes in this PR specifically, I wanted to put a high-level question - should we make the seg-rep tests more rigorous to validate the file structure on replica nodes to make sure they are consistent with the primary?
Our current asserts are around hit count, which seems largely sufficient given that our test case is checking if newly indexed documents show up on the replica. But it doesn't validate that the shards are point-in-time consistent

Good call.  I think we can do a decent comparison with the results of _cat/segments.


Passphrase-protect keys

The tuf command should default to saving keys in encrypted form using a passphrase. The passphrase should be passed interactively by default with an option to pass it via an environment variable (as a very weak attempt to prevent it from leaking to observers of ps). An option to disable encryption (like --insecure-plaintext-key or similar) should be provided as well.
The encryption steps are as follows:

Retrieve a 32 byte random salt using crypto/rand
Pass the salt and passphrase to scrypt with the following parameters:

N=32768
r=8
p=1
length=32

Retrieve a 24 byte random nonce using crypto/rand
Encrypt the entire key JSON (in the same format that the plaintext key is stored) using nacl/secretbox
Persist the salt, parameters, nonce, and ciphertext to the JSON file

The N parameter was chosen to be ~100ms of work using the default implementation on the 2.3GHz Core i7 Haswell processor in my late-2013 Apple Retina Macbook Pro (it takes 113ms).
The JSON should probably look something like this:
{
  "_type": "encrypted-key",
  "kdf": {
    "name": "scrypt",
    "params": {
      "N": 32768,
      "r": 8,
      "p": 1
    },
    "salt": "<base64 encoded bytes>"
  },
  "algorithm": {
    "name": "nacl/secretbox",
    "nonce": "<base64 encoded bytes>"
  },
  "ciphertext": "<base64 encoded bytes>"
}

The encryption code now exists in the encrypted package, all that's remaining is modifications to the CLI.

So I'm thinking of having something like this in local_store.go:
type persistedKey struct {
	Encrypted bool            `json:"encrypted"`
	Key       json.RawMessage `json:"key"`
}

then Key either gets unmarshaled directly into *data.Key, or is passed to encrypted.Decrypt and then the result unmarshaled.
To get the passphrase from the CLI to the local store, I'm thinking of adding a passphrase package and the second arg to FileSystemStore will be a passphrase.Reader or similar (which the CLI will set here), meaning the local store is responsible for the encryption / decryption, and the Repo always handles unencrypted keys (i.e. here).
Thoughts welcome on this approach before I start implementing.

This strategy sounds good! One thing to consider is that the encrypt/decrypt operation takes 100ms to derive the key so putting all the keys in a single encrypted blob might be better, but I haven't thought about the implications. If it's easy enough, a command to toggle encryption and change the passphrase would also be useful. Also, if there is no encrypted data, we might want to read a confirmation of the passphrase.

@titanous so currently CLI commands only need keys for a single role (e.g. tuf add needs targets keys, tuf snapshot needs snapshot keys etc.) so having them all in one file wouldn't really save any time.
It probably makes sense to have multiple keys for the same role in one encrypted file though as they are fetched together, so a workflow could look like this:
$ tuf gen-key root
No existing root keys found
Generating new root keys file
Enter passphrase:
Repeat passphrase:
Added 1 key to root keys file

$ tuf gen-key targets
No existing targets keys found
Generating new targets keys file
Enter passphrase:
Repeat passphrase:
Added 1 key to targets keys file

$ tuf gen-key targets
Existing targets keys found
Unlocking encrypted targets keys...
Enter passphrase:
Added 1 key to targets keys file

$ tuf add file.txt
Detected local targets keys, attempting to sign targets.json...
Enter passphrase:
Signed targets.json with 2 targets keys

$ tuf gen-key timestamp --insecure-plaintext
No existing timestamp keys found
Generating new timestamp keys file
Are you sure you want to store keys in plaintext? (y/n):
Added 1 key to timestamp keys file

For changing passphrase / disabling encryption:
$ tuf change-passphrase root
Enter current passphrase:
Enter new passphrase:
Repeat new passphrase:

$ tuf disable-encryption targets
Are you sure you want to disable encryption? (y/n):
Enter passphrase:
Encryption disabled

$ tuf enable-encryption targets
Enter passphrase:
Repeat passphrase:
Encryption enabled

WDYT?

SGTM

Closing in favour of #60


[Bug] Call getCurrentEntry() on setupUpdateOperation breaks update operation

Bug report
What I did
call
dump($this->crud->getCurrentEntry());
on
setupUpdateOperation
What I expected to happen
can save edited entry
What happened
return 404 page
What I've already tried to fix it
??
Backpack, Laravel, PHP, DB version
"require": {
"php": "^7.2.5",
"backpack/crud": "^4.1",
"backpack/filemanager": "^1.1",
"backpack/permissionmanager": "^6.0",
"fideloper/proxy": "^4.2",
"fruitcake/laravel-cors": "^2.0",
"guzzlehttp/guzzle": "^6.3",
"laravel/framework": "^7.0",
"laravel/tinker": "^2.0",
"owenmelbz/https-enforcement": "^0.0.5"
},
"require-dev": {
"backpack/generators": "^3.1",
"facade/ignition": "^2.0",
"fzaninotto/faker": "^1.9.1",
"laracasts/generators": "^1.1",
"laravel/ui": "^2.0",
"mockery/mockery": "^1.3.1",
"nunomaduro/collision": "^4.1",
"phpunit/phpunit": "^8.5"
},
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.7 (cli) (built: Jun  9 2020 13:36:15) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
LARAVEL VERSION:
v7.17.1@6633c4017b311d3aaae842edabd567c637afc39c
BACKPACK VERSION:
4.1.11@acc4df836505a612d1dd15a39ce02be87e36577d

if($this->crud->getRequest()->request->get("id") == null ){
dump($this->crud->getRequest()->request->get("id"));
}
solve issue


USB PD Source

Can this library be used to transfer power bidirectionally? For example, a power bank with one USB port as an input (for charging) and an output (to charge).

The library currently implements USB PD monitoring and USB PD power sink mode. It does not yet support power source mode and role-swapping. (I'm not sure if the latter is required in your case.)
I'm happy to accept contributions if you want to write the additional code for power sinks.


Add a Gitter chat badge to README.md

Vincit/objection.js now has a Chat Room on Gitter
@elhigu has just created a chat room. You can visit it here: https://gitter.im/Vincit/objection.js.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

duplicate

Coverage remained the same at 97.302% when pulling 1466bee5f145307c8df15524039fd223dd9b67d7 on gitter-badger:gitter-badge-1 into 2874434df6f189c66caa45deb48e165d99bfcae0 on Vincit:master.


Created additional semver container tags

Describe the feature:
Right now attu container images are not fully semver. There is 2.3.0-2.3.10 all the way up in between, but no 2.3 tagged image.  Can you please update to include additional tagged/hosted images on Docker hub that conform to major.minor?
Describe a specific use case for the feature:
Our framework uses some image tags as defaults and we'd rather not update every release to 2.x.x and rather would use major.minor binding if possible.  This would help keep revisions updated for our consumers as well.

Hi, v2.3 has been pushed.

We will update the release script later.

https://github.com/zilliztech/attu/releases/tag/v2.4.0
v2.4.0 has been released. please try it.


Joins

How to perform an inner join?

How about direct associations?

I don't want to add columns to my models only to perform a join.
I managed to do it with a raw query, but that would be great to have a built-in method in the future, like in ActiveAndroid.
Maybe something like:
selectFromMyModel().innerJoin(myOtherModelRelation).on(clause, args).where(...)...


Create an official biologist-friendly version of CHEBI that conflates protonation groups to a representative member

Currently CHEBI has individual classes for protonated forms of chemical entities, but oddly does not create grouping class. This would be like an anatomy ontology including terms for "left hand", "right hand", but not "hand".
Groups like GO and RHEA have developed workarounds for this, where the ph7.3 stable form is taken as representative. This needs to be documented:

#3823

(Note that RHEA goes further and essentially relabels the chemical entity to a protonation-neutral term. So for example, lysynium(1+) is relabeled to lysine and L-glutamate(1-) is relabeled to L-glutamate.)
Unfortunately, this strategy is not sufficient for making a subset. To see why, look at the is-a ancestry of the representatives for Lysine and L-Glutamate:

The common ancestor of these terms is "polyatomic ion". There is no common amino acid parent. This is because there is no protonation neutral term for amino acid!
Really what CHEBI should be doing is making new IDs that represent protonation neutral forms. These are analogous to terms like "hand" and "foot" in an ontology like Uberon. This would massively simplify the ontology and eliminate long-standing issues of inconsistent classification such as #4207.
In the absence of this, the next best thing is a CHEBI subset that collapses all protonation groups into a single representative, and fills in correct is-as, as if this were the representative.
In the above example, there would be one term for lysine and its conjugates, one term for glutamate and its conjugates, and one term for amino acid and its conjugates, one term for alpha amini acid and its conjugates, and simple is-as between them making a simple tree:

amino acid

alpha amino acid

lysine [using the ID for "lysinium(1+)" as representative]
glutamate [using the ID for "glutamate(1-)" as representative]

(omitting L and D forms for simplicity here but this is a whole other issue)
The algorithm for going from CHEBI to CHEBI-simple would be

create a mapping between every CHEBI term and a ConjSet consisting of that term and everything reachable by the 2 conjugate predicates (many terms form degenerates sets of size 1, this is fine)
select a representative for each ConjSet

use ph73 if available (e.g. lysinium(1+))
if not available for that term, use the RHEA mapping
if not available for that term, use the generic acid form (e.g. amino acid)

relabel the representative using UNIPROT_SYNONYM if available
For each pair of ConjSets S1 and S2, if there exist any member m1 in S1, m2 in S2, such that m1 is-a m2, then make an is-a axiom `repr(S1) is-a repr(S2)
Discard all non-representative members
remove all charge annotations on the representative members

This will create a biologist friendly version of CHEBI that will just work without doing any of the complicated procedures in place in RHEA or GO. It will look much more similar to the ontologies in use by MetaCyc, KEGG.
Note that this subset will still be problematic. It's like making an ontology like Uberon that has laterality-neutral terms like "hand" from an ontology that has laterality-only terms by arbitrarily picking left or right forms. It will include is-a relationships that are inconsistent with the source CHEBI file, where differently charged molecules are in SubClassOf relationships. But CHEBI already has these and no one seems to care (#4393).
Just to emphasize: this should never have been necessary. CHEBI is meant to be "Chemical entities of biological interest". No biologist ever asked for the current protonation strategy in CHEBI. Protonation-neutral forms should be first-class CHEBI IDs. However, in the absence of this, the "representative conjugate set member" approach is the best that can be done.

I couldn't agree more with Chris' suggestions. This would be a straightforward approach to start to fix some of the more glaring problems for biologists trying to use Chebi. I am not adding anything new, but wanted to emphasize how important this is beyond a thumbs-up.

@amalik01 I was wondering if you or other members of the CHEBI team have had time to consider this proposal?

@cmungall
I agree with you – there are a lot of inconsistencies in the way the ChEBI hierarchy is built for the neutral and ionised molecules.
At the database level, this would be difficult to do as we also have the conjugate acid/base relationships that exist between the neutral and ionised molecules. A quick solution would be to fill in the missing conjugate acid/base relationships between the terms higher up in the ontology.
If you and others just require a biological friendly OWL/OBO file laid out using the set of rules described, then this can be done and made available. I will discuss this with the ChEBI team this Thursday and get back to you.  We may need to arrange a Zoom call with you to discuss further.

Thanks! A call would be great

Any chance of this happening?

From the NFDI4Chem perspective, the fixes proposed by @cmungall from slide 46 onwards would help a lot in the reuse of ChEBI.

Hi @cmungall I think you summarised your Jun 27 call with CheBI on an GO editors call, but could you list the main outcomes/next steps here? Thanks!


Promise.then doesn't wait

i.e.:
require(['bootstraps/standard'])
    .then(() => (
        new Promise(resolve => setTimeout(() => resolve(), 500))
            .then(() => console.log('foo')))
    )
    .then(() => console.log('bar'))

bar will fire before foo.
I'm happy to cast the promise using Promise.resolve, but can this be documented?

How's this, @OliverJAsh?

Could it be that you're not returning the promise?
Try this:
require(['bootstraps/standard'])
    .then(() => (
        return new Promise(resolve => setTimeout(() => resolve(), 500))
            .then(() => console.log('foo')))
    )
    .then(() => console.log('bar'))

In the original version, nothing is returned, so that nothing gets passed immediately into the second "then".  But if you return a promise from a "then", it kind of replaces all of the following "then".
I think that's the way the spec says it should wrok.

@Earl-Brown I am using an arrow function which has an implicit return.

Ah ... that makes sense, then.

when you use  arrow function like this (e)=>{//code here}
it doesn't return the data inside by default only when you use
(e)=>//code here
its the same as
(e)=>{return //code here}


feat: Bad mod formatting warnings

While loading mods, this checks if a mod.json file is present in mods directories; if not, this will display a warning message, telling user mod hasn't been installed properly.
This does not analyze hidden directories (with a filename beginning with a .).

@GeckoEidechse if you want to keep doing your shenanigans, this will ignore your git folders 😁

@GeckoEidechse if you want to keep doing your shenanigans, this will ignore your git folders grin

Depending on how fast VTOL switches to using enabledmods.json we might also have to ignore the disabled folder it uses to hide the mod.json.
@BigSpice is there an ETA on the fix in VTOL? ^^

Actually I just realised that this might also cause issues for players where there is a leftover disabled folder in the mods dir. Not sure if Viper ever cleaned that up after switching to enabledmods.json.
It might make more sense to check folder recursively for mod.json and only warn if there is actually one in a subdirectory.

It might make more sense to check folder recursively for mod.json and only warn if there is actually one in a subdirectory.

What about mod folders with no mod.json file? (quite unlikely, I know)

What about mod folders with no mod.json file? (quite unlikely, I know)

For that to occur, the player must have manually deleted that file, given that a mod author wouldn't release a mod with missing mod.json cause that mod would have never loaded on their end in the first place. I'd argue that this would be a rarer occurrence then a player accidentally creating an empty folder. ^^

It might make more sense to check folder recursively for mod.json and only warn if there is actually one in a subdirectory.

Addressed in c0e44c9.

concept is good, but would be nicer if this was exposed to script and shown in ui, rather than than shown as a messagebox? messagebox would be annoying in cases where mod formatting isn't an issue since it'd block execution

What method would you use to show error message in UI? All cool UI methods I know are callable from Squirrel VM.

something on the title screen to display warnings would work, would need to expose all messages to squirrel on reload and do some ui stuff in script to display them

Yeah that's also cool, because this way we're sure user knows some of their mods are fucked (in comparison with a notification that closes automatically without user noticing it)

it'd be very annoying for developers in situations where they know they'll get the warning and don't want to wait for a blocking textbox every startup, is what i'm thinking

Marking this as draft while I refactor to address comments.

What method would you use to show error message in UI? All cool UI methods I know are callable from Squirrel VM.

Define a global function in the UI that displays a dialog / menu / submenu that explains what's going on and call that function from native after the UI VM is initialized and mods that are formatted wrong are detected

Do note that this changes the function signatures of some script methods as they are currently incorrect. https://github.com/R2Northstar/NorthstarMods/pull/597 fixes those issues as well.

Wait, how does this depend on https://github.com/R2Northstar/NorthstarMods/pull/597 ?
Isn't it the other way round or do both depend on each other?
As in can this launcher PR not be added alone without breaking something in mods?

As in can this launcher PR not be added alone without breaking something in mods?

It definitely can, but you won't see any displayed errors, which is the point of both PR 😃

As in can this launcher PR not be added alone without breaking something in mods?

It definitely can, but you won't see any displayed errors, which is the point of both PRs 😃

Oh yeah, that's totally fine and expected :P
The "Depends on" just threw me off, updating PR description accordingly ^^

Wait, how does this depend on R2Northstar/NorthstarMods#597 ?
Isn't it the other way round or do both depend on each other?
As in can this launcher PR not be added alone without breaking something in mods?

No, this introduces compile errors (without the mods pr) because I corrected some signatures of functions exposed to squirrel.

Mb, I forgot about the ornull part.
Off to bed!

Aight, updating PR description again xD

Feature is still working as expected after newer changes.

What's your issue with smart pointers?

What's your issue with smart pointers?

The fact we don't use them anywhere else ( apart from logging, but that dont count ). Also the fact that a few lines up there is a std::vector<Mod>.
My personal opinion is that this can be merged as is since ill probably get to cleaning this up ( and possibly including some of bobs changes from mod loading refactor ) sooner or later.

@Alystrasz just a heads-up that this PR sadly has merge conflicts now ^^"

@Alystrasz just a heads-up that this PR sadly has merge conflicts now ^^"

Done :)

@Alystrasz would this need a rework to check packages as well? We already have basic format requirements for packages already so maybe not but want your opinion

@Alystrasz would this need a rework to check packages as well? We already have basic format requirements for packages already so maybe not but want your opinion

About packages, currently we only check if directory names match the AUTHOR-MOD-VERSION pattern, not checking if the mod manifest is at the right place; this has been added in e398b5cb5a40ed08b0fff20ed78df9dddf51170e and 0d6b62491326bbf764bbb5ad32fad5dc8772cb9d.
I removed the "READY TO MERGE" label since the diff shows this is deleting functions such as NSGetModNames (probably some merge operation failed), I need to address that.

Waiting for @uniboi to re-add the NSGetInvalidMods function with new syntax since they've done it in the first place :)


Sub-array definitions

For the analysis of sub arrays from simulations, we usually pick a sub-set of the existing telescopes for the analysis.
How are those sub-arrays defined?
I am asking because:

a large number of subarrays have been defined for different studies with Eventdisplay and Mars. This information should be accessible for ctapipe (and other systems)
telescope IDs used in the simulations change with productions (e.g., is MST5 not the same telescope in prod3, prod2, or prod4-MST)
reconstruction should start using the same telescope IDs as colleagues on the ground (i.e., we should already now make sure that a discussion about MST5 is the same telescope in simulations as on the architects drawings).

I am currently make sure to have consistency with the engineers and propose for now (as this will be replaced by a data base) the following two schemes:

a list of telescopes with their names, positions, and IDs in the different simulation sets (see attached example). This file needs to be updated after each new simulation

a list of (sub arrays), which allows then to simply map the telescope numbers in the subarrray definitions for the different simulation production.

Would that work? The above scheme would allow to 'hide' all the messy details about telescope IDs in the simulations from ctapipe.
(and somehow github doesn't allow to attach yaml or ecsv files, this is why I've added a .txt)
telescope_positions_south.ecsv.txt
layouts_south.yaml.txt

Following #738 , we will at some point move to having a set of configuration data per "prod", and then we can just include these subarray definitions as a table that one loads.  Since we have so many different types of simulation files right now, it's a bit tough -even in Prod3B, I seems to have files with very different telescope subsets and locations (at least as test files - perhaps the bulk of the data is not like that?)

The best would be to have a way to query a simulation file and know what prod number or variant it is, and then we can map things easily.  Is that stored anywhere?  If not, I worry this is a fragile system and would break easily if somebody uses a file where the tel-ids are not as expected.

I don't think there is an explicit identifier for the production in the simulation files, although it is for all grid produced files encoded in the file names (e.g., /gamma_20deg_0deg_run103___cta-prod3-lapalma3-2147m-LaPalma.simtel.gz).
The idea here is that as soon as you know the prod number,  you are able to retrieve any pre-defined sub arrays (the simulations files usually are for at least the baseline configuration) without having the figure out again how the telescope identifiers are. You are also able to retrieve data for a certain telescope (e.g. MST5).
Again, I assume that this is a temporary solution to make the subarrays available currently considered. At some point we will only simulate those telescopes which will actually be built and we introduce the same telescope ids/names in the whole CTA world (to my knowledge is system engineering still discussing how components should be called).

Would it be possible to encode this in the simtel runheader in the future?
Some kind of production identifier.
There are two string fields in the run header that could be used for this, target and observer.
These are in the moment set to
 'target': b'Monte Carlo beach',
 'observer'<EMAIL_ADDRESS>
Cerntainly target could contain something more useful than "Monte Carlo Beach". Although that sounds like a nice place to be :rofl:

What is 'it' in your question?

we certainly should encode the production number into the header
subarrays cannot be encoded, as this is a 'subset' of telescopes chosen after the simulation is done

I meant something identifying production. Like the string in the filename or something similar.

Yes, this should be done (but this point is mostly independent of my questions on subarray definitions).

So there are currently no subarray definitions inside ctapipe or ctapipe extra I think.
The way to select a subarray is to set the allowed_tels for the event sources and I think people manually looked up which tel ids they wanted to analyze for this.
I know Kai needed to reprocess a fair amount of data because he selected a non-sensical subarray (8 LSTs or something)

So there are currently no subarray definitions inside ctapipe or ctapipe extra I think.
The way to select a subarray is to set the allowed_tels for the event sources and I think people manually looked up which tel ids they wanted to analyze for this.

yes, so far in Protopipe, there is a lookup table for mapping the subarrays, it's not done in ctapipe.  But that is also a bit of a hack and will break when we change prods (or try to analyze some other variant of the current prods), so having a prod identifier other than "Monte Carlo beach" would be great and simplify life, at least for future prods.

Would it be possible to encode this in the simtel runheader in the future?
Some kind of production identifier.
There are two string fields in the run header that could be used for this, target and observer.
These are in the moment set to
 'target': b'Monte Carlo beach',
 'observer'<EMAIL_ADDRESS>
Cerntainly target could contain something more useful than "Monte Carlo Beach". Although that sounds like a nice place to be 🤣

Gernot pointed me to this point in the issue, so I thought I would comment.
There are a few ways to tell which production the file comes from (I am sure Konrad has more more), but none of them is "pretty":

In Prod5, Konrad added the release to this field
'target': b"Monte Carlo beach, version='2020-06-28 15:07:23 CEST (konrad@wizard4)', release='2020-06-28 (candidate for full prod5 baseline setup)', eventio_version='2020-05-12 17:01:23 CEST (konrad@wizard4)'"
You could extract the production info from there and if empty assume it's prod3b (or prod4). Very ugly and breaks easily, but provides some information.

Konrad added a parameter "ARRAY_CONFIG_NAME". It's not included in the info read out as far as I can tell (i.e., hessioxxx/include/io_hess.h), but it's in the header of each output simulation file, so I assume it can be added also to the i/o. Not very useful now, but could be in the future.

The safest bet is probably the parameter "detector_prog_vers" in hessio/pyeventio. This returns the sim_telarray version (times a 1000?). The version number changes also when the configuration changes, so the value should be exclusive and exact for each production. You could, for now, hardcode a dictionary that translates between the version and the production. For example,

Prod3b - detector_prog_vers =<PHONE_NUMBER>

Prod5 - detector_prog_vers =<PHONE_NUMBER>

SO to summarize here:

yes, please add a configurable prod name to the data format (that can be chosen by the person configuring simtelarray)
for now, we can make a "guess" function like we do with camera types (using the detector_prog_vers" to start with)
yes, also please provide some structured file (JSON, YAML) that has the mapping of subarray_name to tel_ids_in_subarray for each PROD.    We can put that on the data server just like other test files, and then we can add a functions like  get_tel_ids_for_subarray(prod="PROD2", subarray_name="H1BFQ2") → List[int], and get_subarray_names_for_prod(prod="PROD2") → List[Str]

Another related question: there are some runs from e.g. Prod3b that have a "super array" in them, and some where there are only a subset of telescopes (La Palma Reference Sims, for example).  Those would both identify as "Prod3b", but I guess the telescope-IDs are not the same, so subarray mappings would not work.  Is that correct? We could consider using detector_prog_version + num_tels as part of the guess_prod() function, I guess. Is there a list somewhere?


Unable to 'go get' this package

The apidoc.go file imports a private repository, github.com/cosiner/golib, which I'm unable to access.
I'd love to try out your tool but at this point I'm unable to do so.  Could you please expose this 'golib' dependency? Thanks!

I'm sorry, i change the name of 'golib' package yesterday, but forgot push it to github.
Now it was fixed, thanks for your attention.

No problem, I had this in my TODO list for projects to look into.  I'll give it a shot today!  Thanks for the quick response!


Enable proper versioning for message objects

Right now, any significant proto change means existing database objects cannot be re-serialized and returned via the API. We need a strategy to work around this because we cannot simply stop serving data stored in a previous format just because the spec evolved.
Most of the problems here arrive when receiving the data matching the CosmosDB query - the objects simply cannot be de-serialized because they match the old format, but the new format has either changed, eliminated, or added new properties.
Per our contacts in Azure, it might make more sense to tag documents with the API version used to store them, then come up with a way to map the old document to the new API format (and vice versa). Considering AutoMapper and somehow versioning the generated .proto. Or, we could just version the generated Protobuf C# classes and use that somehow in the query.

Resolved in #40


define default tab

thank you for this extension
my chrome goes to setting after i close it...
i want to go to specific page?
is it possible?

Google Chrome Help: Set your homepage and startup page


Functions std_BS, std_IS, std_CF to be updated

For std_BS function to check:

[x] name of excel standardized_BS.xlsx within the code;
[ ] general check of the code against filing

For std_IS function to check:

[x] appropriate use of std_CFfunction code chunks
[x] general check of the code against filing

Verified df_std_BS.
Error to address in ## Step 1 - Check key financial Concepts  line 294 when it verifies essential financial concepts exist.

std_BS completed. c6b4eb2


updated get method to public

Fixes
Access type for interface method Cloudflare\Contracts\ResponseInterface::get() must be public error

Hi @necenzurat
Thanks for the PR, but I wanted to keep this method protected, because is something only for Response ( get items from array using dots)
Where this error is being thrown?

When using the api after the request.
I ran it out of the box and did not work until i’ve change the protected,
maybe try private?
--
Costin Moise aka necenzurat
Dev-at-large 💻
Find me: +4 0726 459 188 <+4+0726.459.188> | Github
https://github.com/necenzurat | Linkedin
http://www.linkedin.com/in/necenzurat
On Sat, Aug 24, 2024 at 17:44 Sergkei Melingk @.***>
wrote:

Hi @necenzurat https://github.com/necenzurat
Thanks for the PR, but I wanted to keep this method protected, because is
something only for Response ( get items from array using dots)
Where this error is being thrown?
—
Reply to this email directly, view it on GitHub
https://github.com/SergkeiM/php-cloudflare-api/pull/25#issuecomment-2308417699,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABDQKJXALPRVOSGK77B72DZTCL4TAVCNFSM6AAAAABNBLQ67OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGQYTONRZHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@necenzurat can you share the code you used?

This part
use Cloudflare\Client;

$client = new Client('CLOUDFLARE_TOKEN');

$response = $client->accounts()->list();

$results = $response->json();

latest laravel and php 8.2


HDDS-9512. Datanode in ozone share a same port with datanode in HDFS.

What changes were proposed in this pull request?
Change Ozone Datanode client port default value from 9864 to 19864.  This port was added since the last release (1.3.0) to support dynamic reconfiguration protocol, but it conflicts with HDFS Datanode web port.  Thus it makes sense to change it before the conflicting port gets into any Ozone release.
https://issues.apache.org/jira/browse/HDDS-9512
How was this patch tested?
Tested the port in ozone compose environment:
$ ozone admin reconfig --address <IP_ADDRESS>:19864 properties
DN: Node [<IP_ADDRESS>:19864] Reconfigurable properties:
hdds.datanode.block.delete.threads.max
hdds.datanode.block.deleting.limit.per.interval
ozone.block.deleting.service.workers

CI:
https://github.com/adoroszlai/ozone/actions/runs/6934881675

@xichen01 can you please review?

The IntelliJ application also uses port 19864, which may cause the IntelliJ Ozone to fail to start due to a port conflict.
https://github.com/apache/ozone/blob/945e8bfdcfe0be1fecbca3716d41305c4ae23d00/hadoop-ozone/dev-support/intellij/runConfigurations/Datanode2.xml#L21C398-L21C398

The IntelliJ application also uses port 19864

Thanks @xichen01 for pointing that out.

@adoroszlai , thanks for working on this.  HDFS(HDFS-9427) once changed from default ephemeral to non-ephemeral ports,  can we also use a non-ephemeral port here?

can we also use a non-ephemeral port here?

According to Wikipedia different systems use different ranges for ephemeral ports.  Considering the ranges "used by many Linux kernels" and Solaris / AIX, 19864 is not an ephemeral port.  (RFC 6335 and IANA suggest a smaller range than that.)  Considering some other range definitions, mostly related to Windows, all Ozone ports are ephemeral, too.

can we also use a non-ephemeral port here?

According to Wikipedia different systems use different ranges for ephemeral ports. Considering the ranges "used by many Linux kernels" and Solaris / AIX, 19864 is not an ephemeral port. (RFC 6335 and IANA suggest a smaller range than that.) Considering some other range definitions, mostly related to Windows, all Ozone ports are ephemeral, too.

Okay.  The overall change looks good.  And I tested it locally with intellij.

LGTM+1, Thanks

Thanks @ChenSammi, @xichen01 for the review.


test(transformer): add test for arrow function transform 2

#5939  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Fix secure coding bugs in MFA

Fixes #10632

Thanks @igor-makarov !
Here's a diff to fix the style CI problem:
diff --git a/FirebaseAuth/Sources/MultiFactor/FIRMultiFactor.m b/FirebaseAuth/Sources/MultiFactor/FIRMultiFactor.m
index 3ef2ad469..8cd66b9bc 100644
--- a/FirebaseAuth/Sources/MultiFactor/FIRMultiFactor.m
+++ b/FirebaseAuth/Sources/MultiFactor/FIRMultiFactor.m
@@ -178,8 +178,9 @@ static NSString *kUserCodingKey = @"user";
 - (nullable instancetype)initWithCoder:(NSCoder *)aDecoder {
   self = [self init];
   if (self) {
-    NSSet *enrolledFactorsClasses =
-        [NSSet setWithArray:@[ [NSArray class], [FIRMultiFactorInfo class], [FIRPhoneMultiFactorInfo class] ]];
+    NSSet *enrolledFactorsClasses = [NSSet setWithArray:@[
+      [NSArray class], [FIRMultiFactorInfo class], [FIRPhoneMultiFactorInfo class]
+    ]];

Thanks @igor-makarov! Please apply the fix as @paulb777 suggests and I'll approve this PR.

@paulb777 @renkelvin I've applied the style fixes


refactor: remove unused ClusterRole

The training-operator charm is always deployed using trust because it needs elevated permissions to apply k8s resources using lightkube, so there is not an actual need for a Role or a ClusterRole. This commit removes the unused ClusterRole, keeping just the aggregated roles (for them to be applied to the Kubeflow Profile namespace) when needed.

Closing because of #159 we will be refactoring the charm and these files will be required.


Gui task

GUI show due date
Upcoming task no longer show overdue task

Codecov Report

Merging #96 into master will decrease coverage by 3.09%.
The diff coverage is 3.96%.

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


Any plans for supporting status?

One of the things that was missing from Java Abstract operator was support for status. I am not sure its implemented in Fabric-8, but last time I checked was about 6 month ago. Are you planning to support status?

@blublinsky Thank you for your question.
Fabric-8 client now supports Status Update since yesterday release :-)
https://github.com/fabric8io/kubernetes-client/issues/1548
Yes, I can add this feature now to Freya. Quick idea to let the controller to return F[Option[Status]] instead of F[Unit]. That means, the returned Status will be used to set the CR object status and applied by Freya automatically.
Do you have any particular use-case or requirements as for the status feature that may help to design this better?

Thanks Alexey,
I do not have any specific use case in mind, but F[Option[Status]] seems like a much better option. In Flink implementation, for example, I was thinking about returning back pods statuses and URL of the master, So setting Status directly in CR would give you the best flexibility.

Understood, thanks for feedback. Let's see if this feature is easy to implement.

@blublinsky Status feature has been already added. However, its behaviour is quite strange. I am not sure if it is fabric8 issue or my kubernetes version has some bug in status update. I am trying to clarify expected behaviour here: https://github.com/fabric8io/kubernetes-client/issues/1548#issuecomment-579470177.
Anyway, latest Freya version can already update CR status, the issue itself is a side-effect Modify event sent right after the status update. It should not be a problem when operator is idempotent.


Add Editing Documentation page

Purpose / why
Adds a new page walking through how to edit the documentation using the GitHub in-browser GUI, including the soon-to-be option to directly commit small fixes.
What changes were made?
One new page, one new menu entry so it'll be linked in the docs, and five new screenshots.
Verification
mkdocs build and review. This PR is not yet ready for merge because it is written for a world where some upcoming changes to loosen the workflow on this repo have been implemented. Once those changes are real, this can be merged.
Interested Parties
@rosiel @dannylamb @eldonquijote does this seem in line with what was agreed for the new workflow?

Checklist

Pull-request reviewer should ensure the following

[ ] Does this PR link to related issues?
[ ] Does the proposed documentation align with the Islandora Documentation Style Guide?
[ ] Are the changes accurate, useful, free of typos, etc?

Person merging should ensure the following

[ ] Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
[ ] If pages are renamed or removed, have all internal links to those pages been fixed?
[ ] If pages are added, have they been linked to or placed in the menu?
[ ] Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

I meant to put this out there as a Draft pull request, but I messed up and it doesn't seem to be an option after-the-fact. DO NOT MERGE. This documentation lies, until some other stuff goes through.

I think this should be paired with a "how to create documentation" page, and there's enough difference (editing the index, adding new assets, how to start a new .md file in the GUI) for them to be seperate, but I'm not wedded to having them be two different pages.

Yeah there could maybe be a Documentation section... how's this for a start?

How to contribute documentation (the intro to this, also mention that it's in Mkdocs flavoured markdown, follow our style guide (link to page), that we use pull requests (link to new Docs PR workflow page), code of conduct (link to page)).
Tutorial: Edit Documentation using the Github GUI (most of this page)
Documentation Style Guide
Documentation Structure (where stuff lives, how to edit menus, how to add pictures, etc. Maybe also mention 'this repo has the entire islandora history and so if you clone it locally it's big')
Documentation Pull Request Workflow (/Policy?) (describe who is allowed to do what and when and the pr template etc. This kind of stuff, the Policy stuff, seems like it could get its own page instead of being part of a tutorial or something? (do you need a CLA to contribute a PR? This is not clear from contributing.)
Tutorial: Build and serve the documentation locally with Mkdocs

This would be a bit of a resturcturing - moving existing pages into a 'documenation' section/folder

Oof. You do indeed need a CLA to make a PR. I'll stick that in the "Before you start" of this draft for now, but I like the approach you've outlined for a more comprehensive documentation section.

It needs to sit until policy & settings get updated anyhow, since the process described here is not yet real.
For policy, I'm not sure. I wouldn't consider accepted suggestions to be a contribution barring a merge, since there's no commit, but I guess I did copy and paste some of your wording directly. I thought saying "anyone who contributed a commit" might be too opaque for new users who aren't marinated in GitHub concepts, but if "collaborated with you on writing the changes" is misleading, maybe it needs the more technical explanation.

Thanks @eldonquijote and @rosiel ! This "General Member" merge demonstrates that the instructions in this doc are now true 😄

Thank you @eldonquijote !!


Unclear error message when generated folder is missing

If the folder defined in resgraph.json doesn't exist, ResGraph fails to compile.
This is the error message if /src/schema/__generated__ doesn't exist:
Error: Command failed: /path/to/repo/node_modules/resgraph/bin/darwin/resgraph.exe generate-schema
  /path/to/repo/src  /path/to/repo/src/schema/__generated__ true

This error could be a common mistake for new users and the message could be improved

Fixed in https://github.com/zth/resgraph/commit/3e404b01758e02c41b4b3c6b312a8c73e6cf1d27.


chore: Test on node 12 and 14 in travis

Also use latest version of coveralls with npx

Coverage remained the same at 100.0% when pulling 2212b735098beebdc91dbcfd2aaad8223df25967 on danez:patch-1 into 2b9b06c5c24230668e3606d745c99c24041def42 on pebble:master.

Coverage remained the same at 100.0% when pulling 2212b735098beebdc91dbcfd2aaad8223df25967 on danez:patch-1 into 2b9b06c5c24230668e3606d745c99c24041def42 on pebble:master.


Error when trying to perform full restart (Hot Reload - Caps R)

When I press Caps R to perform a full restart the app crushes. I'm using firebase database and the error is related to firebase_core. When I comment the line 66 (//assert(await existingApp.options == options);) on firebase_app.dart file it works fine and I'm able to perform full restart. Please see bellow the error:
Before I comment the line on firebase_app.dart file
Performing full restart...
Restarted app in 1,675ms.
[VERBOSE-2:dart_error.cc(16)] Unhandled exception:
'file:///Users/josemboa/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.2.3/lib/src/firebase_app.dart': Failed assertion: line 66 pos 14: 'await existingApp.options == options': is not true.
#0      _AssertionError._doThrowNew (dart:core/runtime/liberrors_patch.dart:37:39)
#1      _AssertionError._throwNew (dart:core/runtime/liberrors_patch.dart:33:5)
#2      FirebaseApp.configure (file:///Users/josemboa/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.2.3/lib/src/firebase_app.dart)
<asynchronous suspension>
#3      main (file:///Users/josemboa/Documents/UPA/flutter/DezContos/lib/main.dart:17:43)
<asynchronous suspension>
#4      _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:279:19)
#5      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:165:12)

After I comment the file on firebase_app.dart
Performing full restart...
Restarted app in 1,733ms.

@Josemboa
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/816. Any further collaboration will be done there.


Domain range on bspline creation

If I create a BSpline in this way
BSpline(nbasis=6, order=4, knots=[0, 0.3, 0.3, 1])
It throws an error , but I think it should take de domain_range from the first and last knot
https://github.com/GAA-UAM/fda/blob/9893dccf16a5742399dfa5c9af0ffdc32697b668/fda/basis.py#L549-L566

I will stay on in until Monday 24. If nobody says anything else, I'll change it.


[Support] <I can ping ip vnp client (10.8.0>

In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}

[] I have read and understood the contributors guide.
[] The issue I am reporting can be replicated.
[] The issue I am reporting can be is directly related to the pivpn installer script.
[] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
Have you searched for similar issues and solutions?
(yes/no / which issues?)

Console output of      curl -L install.pivpn.dev | bash
  Output Here

Console output of      pivpn add or pivpn add nopass
  Output Here

Console output of      pivpn debug
  Output Here

Have you taken any steps towards solving your issue?
  which?

Empty issue template, closing.


Failing test Aspire.Azure.Security.KeyVault.Tests.ConformanceTests.HealthCheckReportsExpectedStatus

This test seems to be flaky, and failing on both internal, and public pipelines.
Assert.Equal() Failure
Expected: Unhealthy
Actual:   Healthy

at Aspire.Components.ConformanceTests.ConformanceTests`2.HealthCheckReportsExpectedStatus(String key) in /_/tests/Aspire.Components.Common.Tests/ConformanceTests.cs:line 314
--- End of stack trace from previous location ---

cc @joperezr

cc @eerhardt @sebastienros

This has been fixed.


Request: Add git tag with each version

It would be great if whenever the project version changes (i.e. version in bower.json), the repository was tagged, so that navigation was easier and external tools could handle this package's versioning as well (in my case, I want to use it via Rails Assets but the package cannot be added unless it includes tags for versions [please see https://github.com/FezVrasta/bootstrap-material-design/issues/57 as an example]).
Maybe tags aren't needed for every single patch but maybe minor and major version changes should be tagged IMO.

Thank you @K1N5L4Y3R, I'm on it!

Hi @K1N5L4Y3R, I tagged the version 0.30.3 and I think I added the package to Rails Assets. Tell me if you need something more.
Thank you very much!

That's all I needed. Gracias!


Submitted tx on cardano-node testnet is not propagated

Pls note transaction is submitted via cardano-wallet.
cardano-node 1.8.0
To reproduce:

start cardano-node testnet

cd cardano-node/
git fetch --tags && git checkout tags/1.8.0
nix-build -A scripts.testnet.node -o testnet-node-local && ./testnet-node-local

start cardano-wallet
restore a wallet and submit transaction.
transaction lands in mempool
in the log there is:
node.log

Current result:

transaction is infinitely pending on the wallet backend
transaction never appears on the testnet explorer: http://byron-testnet-develop-explorer.s3-website-ap-southeast-2.amazonaws.com/en/no-search-results/?query=3f9fbbe6f7515a9da91fb13b7623c09c65d4808219149d0780f0ec8083ee477d

Expected result:

transaction should be submitted and propagated successfuly

Cardano-wallet requests
Start wallet:
cardano-wallet-byron serve --node-socket ~/wb/cardano-node/state-node-testnet/node.socket --testnet /nix/store/7106qjwral616j6p5049m7hhi5ih0r33-testnet-genesis.json --database ./testnet

Restore wallet:
curl  -vX POST http://localhost:8090/v2/byron-wallets \
  -H "Content-Type: application/json; charset=utf-8" \
  -d '{
"style": "random",
"name": "Byron",
"mnemonic_sentence": ["recycle","august","horse","awesome","shuffle","agent","almost","cheap","fury","speak","duty","enemy"],
"passphrase": "Secure Passphrase"
}' --http1.1  |  jq

Submit tx:
curl  -vX POST http://localhost:8090/v2/byron-wallets/d3358ac0fc699784af021710e7aba2a3e31fbbd1/transactions \
  -H "Accept: application/json; charset=utf-8" \
  -H "Content-Type: application/json; charset=utf-8" \
  -d '{
	"payments": [
		{
			"address": "37btjrVyb4KFcfEEYyBU8j4VazP5he8iktF5uyD95avRpUHU6aWuLhuhGMmyFiJjtinJQPSjgGmh5w8qmuxDpHjK2JmCnPALuA4dyUkMpHF5Rf4PBd",
			"amount": {
				"quantity": 40,
				"unit": "lovelace"
			}
		}
		],
	"passphrase": "Secure Passphrase"
}' --http1.1  |  jq

@piotr-iohk if you want to put details here, include the local node log, and the relay log when you get it.

This issue can be closed. It is no longer seen since upgrading cardano-node relays to 1.9.3.


Help at top of Graph page

Are there operations you can perform on the Graph view? How about a short summary of the keyboard shortcuts available at the top? I see that , and . navigate commits, but guessing there are other things you can do here - and now way to discover them. (Obvious things to want to do are diff, checkout, reset...)

If you open gitsavvy help while in the Graph view it will show contextual information (somewhat), at the bottom of that help page you can see the section on "Graph" which lists the available shortcuts.
There was some discussion in the past on showing more contextual help in some views.
А possible solution would be to somehow add a reminder that contextual help is available for pages where keyboard shortcuts aren't listed by default.

Hmm. I did spend a few moments looking to see if there was some help somewhere - didn't occur to me to do Cmd-P "gitsavvy help" though. (And even after reading your tip above, I still didn't twig for a while that the results of "gitsavvy help" are dependent on the current view you're in - very unintuitive IMHO).
One of the things I love about GitSavvy (and why I despise Git) is it gives you easy prompts to what to do next, without having to think a lot.
Is there particular resistance to the idea of a brief summary of the available commands? Something like:
[,], [.]   navigate commits                  [m] toggle commit info
[enter] view commit                          [cmd-enter] checkout commit

I'm open to the idea.  In some of the views (like inline-diff) it is difficult to add extra content.  However, that's not really the case here, if we use regions correctly.  Is there anything beyond what's in the text snippet above that you'd find useful?

Oh, cool. Well, I'm not aware of anything else you can do on that screen - but if there is, then yes. :) Oh, and probably Tab/Shift-Tab.

Ok, I now discover (by looking at the source) that there is both a single-branch and all-branch mode, and that the view you get by cycling dashboards is single-branch. So I'd probably suggest including that information in the header, possibly with a keystroke to switch:
SHOWING: current branch (master)
[,], [.]   navigate commits                  [m] toggle commit info
[enter] view commit                          [cmd-enter] checkout commit
[b] alternate current/all branches

Some tentative work here: https://github.com/divmain/GitSavvy/compare/master...stevage:316-graph-ui?expand=1
Suspect that it should be refactored as a UI class.

Yes, would like this to be a UI subclass.  But this initial work is good.  Would you like to keep at it, or should I put it into my own queue?

Realistically, I won't get to this again until January, so very happy for
you to take it over before then.

@stevage, this probably went off your radar. You still interested in adding this functionality?

Yeah, sorry about that. I'm pretty terrible at picking things back up once I put them down. I'm about to head off for another 5 weeks of inactivity, so if someone else is willing to take this over, that would be better.

Than we will keep the issue open, we will look at this issue later.

I'm on it.


Update dependencies

Description
Routine update of dependencies.
Notable changes:

typescript updated to 4.3.x
redux-toolkit updated to version 1.6 (includes RTK Query)

Other important notes
The latest version of d3 is 7, in which they switched to using ESM modules. This breaks our tests, because Jest, with babel-jest to transpile our typescript files, on the one hand, tries to avoid the transpilation of the files in the node_modules folder (because that's slow), but on the other hand fails to import proper ES6 modules. I've tried updating jest.config.js with the following settings:
   ],
   testEnvironment: 'jsdom',
   transform: {
-    '.+\\.tsx?$': 'babel-jest',
+    '.+\\.[t|j]sx?$': 'babel-jest',
     '.+\\.(css|scss|png|jpg|svg|gif|eot|ttf|otf|woff|woff2)$':
       'jest-transform-stub'
-  }
+  },
+  transformIgnorePatterns: [
+    'node_modules/(?!(d3.*)/)'
+  ]
 };

but that only moved the problem one step further, because all d3 modules, in their turn, depend on some other modules, which are also in ES6 module format. Don't know how to deal with this situation.
Deployment URL
http://update-packages.review.ensembl.org

Noticed some issues with this update:

Sass can't be installed in the latest stable version of Node.js, however it can be with the latest LTS version.
The fonts don't load properly
The external link for Training in the Help page doesn't work

@imransl

Sass can't be installed in the latest stable version of Node.js, however it can be with the latest LTS version.

I am running the LTS, but I also tested the latest current release (16.5.0) after you mentioned that there's a problem with one of the dependencies. Worked fine (npm ci completed without a hitch).

The fonts don't load properly

Looks fine over here 🤷♂

The external link for Training in the Help page doesn't work

Was fixed in https://github.com/Ensembl/ensembl-client/pull/531

Sequence download doesn't work locally (not sure if this a known issue or not)

The client-side problem is the whole reason PR https://github.com/Ensembl/ensembl-client/pull/524 exists (and is now merged into dev)
Refget-proxy on staging is broken, and since we normally proxy our requests to the apis on staging in development, sequence download may also feel broken. Pointing the proxy at production apis should result in a successful download.

I've rebased the branch on dev, so all new commits from dev should now be in this branch as well.

@azangru Yes can confirm all of them work now after I pulled in the latest code. As for the build and fonts failure, maybe it was related to my Node.js version. I was using 16.3.0 while testing this PR. After I updated to 16.5.0 and tested again, those issues disappeared.


Update examples on website for v2.0

fixes #1309
This adds a package.json to the gh-pages branch that installs dependencies and runs commands.
After a new release, run:
npm update
npm install

to update to latest wavesurfer.
Now update the examples and api docs with:
npm run update

This will generate the api docs, inject CDN url, regenerate examples index page, and sync the example directory.

Awesome work, thank you @thijstriemstra!


rocAL -  ltrb changes

Convert the Absolute Bounding box co-ordinates to Normalized co-ordinates
Convert the Bounding Boxes from "xywh" format to "ltrb" format

@swetha097 can you review #521 and make sure this PR is captured there and close this PR.

@swetha097 can you review #521 and make sure this PR is captured there and close this PR.

yes, this PR#513 is captured in PR#521


typo fix on README

Also worth discussing is the organization of the README.
It seems very cluttered right now.


Contract upload feature

[ ] Is it okay if we continue to say "Pending signed contract by Contracting team" here? or should we say "Pending signed contract by OTF" or "Pending signed contract by the project lead" tagging @fourthletter for confirmation

[ ] Also do we still want for the compliance team to be able to upload the contract if they wanted to? or should they be restricted from uploading the contract? in the latter case, we will have to hide the 'upload contract' button for compliance team.

You're right, we need to update it as well. How about "Pending signed contract by Staff/Contracting team"? "Pending signed contract by OTF" is a public message right now we are using it only for applicants, and I think we should show the exact user group to the staff or internal members.
Actually, it depends on the second question whether we want to restrict the contracting team or if it is fine to have it optional for both contracting and staff(as it is right now). With restriction, "Pending signed contract by Staff" makes sense and without restrictions(current implementation), "Pending signed contract by Staff/Contracting team" makes more sense.
@fourthletter @frjo What do you think about the restriction of the contracting team from uploading the contract, is there any issue if they have an option available but no need to use it(they can use it if they want) and staff can also upload the contract(both user groups having the option)?

@sandeepsajan0 Contracting group should still be able to upload contracts. It just that it will not be their responsibility at OTF.
OTF will activate the setting to allow staff to upload contracts.

@sandeepsajan0 - no restrictions on which user role could upload the contract. Thanks!


Error encountered while registering Beacon in "Beacon Tools" iOS app

I am currently working on iOS application which includes functionality on Beacons. I used google nearby API's for searching Beacon. While integrating Nearby API i am facing below issues.
I am trying to register Beacon (minewtech Eddystone) through "Beacon Tools" iOS application using Broadcast Profile "EID". But i got error while registering. I have  installed Beacon Tools application on iPhone 5 (10.3.1 (14E304)).
Same beacon registration succeed from Android version of "Beacon Tools".
I have followed all steps given in https://developers.google.com/nearby/messages/ios/get-started tutorial but unfortunately application don't found any beacon even if beacons are registered(registered from android app) on google beacon dashboard.
I have downloaded sample application from
https://github.com/googlesamples/ios-nearby and run it, but in this app also registered beacon was't detected. Where as in Android app it works fine.
I have created APP_Key from console project and used it while creating GNSMessageManager object.
Let me know if any additional setup require for iOS.

Hi!
We haven't ever seen a minewtech beacon before.  What error are you seeing when trying to register it?

We have also similar kinda issue with EID registration using beacon tools App.
Don't know what is going wrong Beacon tools app not even detecting the Eddystone EID beacon.
Can Anyone ease help me about the same.
Thanks in Advance.

We have also similar kinda issue with EID registration using beacon tools App.
Don't know what is going wrong Beacon tools app (Android) not even detecting the Eddystone EID beacon.
Can Anyone ease help me about the same.
Thanks in Advance.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
16 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
15 seconds
sanity-inspect-image

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
56 seconds
clamav-scan

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
6 seconds
sanity-label-check

✅ Succeeded
8 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


Rob: Watch iqinfotech.co.in

Rob requests the watch of the watch_keyword iqinfotech\.co\.in. See the Metasmoke search here and the Stack Exchange search here.

iqinfotech\.co\.in has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Spam post: https://stackoverflow.com/questions/49854510/do-you-need-a-crm-for-sales

!!/approve

!!/approve

Coverage remained the same at 65.087% when pulling 3eac79aa0025e99a92d145ae31f56650113876b0 on auto-blacklist-1523873008.274288 into b820a54b289efc685cb8df95b60701603f4004dd on master.


1.6 + DIND + Pid Host == Container Serial Killer

I've been troubleshooting this issue for a bit and managed to get a small test case for it.  Basically if you are running Docker as PID 1 (for example Docker in Docker) and you use --pid=host, it will fail.  I don't really know why though.  I have confirmed that this does work in Docker 1.5 just fine.  You can see in the script below that if you uncomment the line that downloads the current Docker, and run it, everything works.
What seems to happen is that when Docker launches the container PID, which is a reexec of Docker itself to the "initializer" that process just dies immediately.  Something is very quickly killing the process.  What or how I don't know.  You can see in the Docker daemon output level=warning msg="signal: killed".  This is getting returned from https://github.com/docker/docker/blob/b9be50b578f86e858113b9c334e1748e15b63263/vendor/src/github.com/docker/libcontainer/container_linux.go#L102.  I've put printf statements all through out the initializer code and basically it's not even getting into the main process really.
I changed the Docker code and made it so that it always passed NEWPID to the clone flags and then things worked.    Now that I have a smaller test case I'll probably continue to debug this, but please help me because this one is just odd to me.  Does docker have some signal handler that is accidentally getting triggered and then it just kills the container??
Again, this only happens when Docker is PID 1.  If you change the script below and remove "exec", everything will work just fine.
Test case below:
#!/bin/bash

curl https://test.docker.com/builds/Linux/x86_64/docker-1.6.0-rc2 > docker
#curl https://get.docker.com/builds/Linux/x86_64/docker-latest > docker

cat > docker.sh << "EOF"
#!/bin/bash
mkdir -p /sys/fs/cgroup
mount -t tmpfs none /sys/fs/cgroup

for i in perf_event net_cls freezer devices blkio memory cpuacct cpu cpuset; do
mkdir -p /sys/fs/cgroup/$i
    mount -t cgroup -o $i none /sys/fs/cgroup/$i
done

exec docker -d -s overlay -H <IP_ADDRESS>:1234
EOF

cat > Dockerfile << "EOF"
FROM debian:jessie
RUN apt-get update && apt-get install -y iptables
RUN apt-get install -y ca-certificates
COPY docker /usr/bin/docker
COPY docker.sh /docker.sh
CMD ["/docker.sh"]
EOF

chmod +x docker docker.sh
docker build -t test .
docker run --privileged -p 1234:1234 test &
sleep 2 # because 2 is better than 1

docker rm -f test
docker -H <IP_ADDRESS>:1234 run -i --pid=host busybox echo please work

https://www.youtube.com/v/aEQw79tKm6I&start=39&end=48
@jfrazelle @icecrime I think this should be in 1.6
@LK4D4 @crosbymichael please help :)
Like batman, I need a light I can shine in the sky and then the core Docker team comes running to the rescue.

@ibuildthecloud Thank you very much for reproduction case. I'll try to fix tomorrow.

omg this image

DARREN!!!!

Is it a bird? Is it a plain? :smile:
@ibuildthecloud (you probably tried this, but..) I see the repro-case is on 1.6-rc2; rc3 was also released yesterday, not sure if anything was changed in that that resolves this?

nah its still there

Thanks @jfrazelle ...just stating the obvious; ya never know

@ibuildthecloud what's yo kernel version?


Feature/heroku browser tests

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

Reviewed the range https://github.com/SalesforceFoundation/Cumulus/pull/2802/files/3e57d6b06a13ed5d2ee3a220afdacb32935f6cad..9680bca3ce04c4c6d3ad825ae76c4629e00f5d62 provided by Jess, looks good.


How to access private IP servers and agents

On following the best practices for cloud-enabled example of main.tf
module rke2 and agent has subnet with public IP on changing to private-subnet, I get private IP
subnets      = module.vpc.public_subnets
Question is how to access private IP server/agent , there should be code for bastion host when using private_subnet.
Any feedback please?

Our current approach is to be as minimal and secure as possible.  We have had discussions about building a bastion host, but nothing that would be long-lived.  At this time, we recommend that you build your own bastion/jumpbox that you can use to connect.