Workers or master may not start when other tasks exit in async distributed training

System information
== cat /etc/issue ===============================================
Darwin mbp-2.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
Mac OS X 10.13.4
== are we in docker =============================================
No
== compiler =====================================================
Apple LLVM version 9.1.0 (clang-9<IP_ADDRESS>)
Target: x86_64-apple-darwin17.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
== uname -a =====================================================
Darwin mbp-2.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
== check pips ===================================================
numpy                              1.14.2
protobuf                           3.5.2.post1
tensorflow                         1.8.0
tensorflow-hub                     0.1.0
tensorflow-model-analysis          0.6.0
tensorflow-serving-api             1.8.0
tensorflow-tensorboard             1.5.0
tensorflow-transform               0.6.0
tensorflowjs                       0.1.0
tensorflowonspark                  1.0.0
== check for virtualenv =========================================
False
== tensorflow import ============================================
tf.VERSION = 1.8.0
tf.GIT_VERSION = v1.8.0-0-g93bc2e2072
tf.COMPILER_VERSION = v1.8.0-0-g93bc2e2072
Sanity check: array([1], dtype=int32)
/usr/local/lib/python2.7/site-packages/h5py/init.py:36: FutureWarning: Conversion of the second argument of issubdtype from float to np.floating is deprecated. In future, it will be treated as np.float64 == np.dtype(float).type.
from ._conv import register_converters as _register_converters
== env ==========================================================
LD_LIBRARY_PATH is unset
DYLD_LIBRARY_PATH is unset
== nvidia-smi ===================================================
tf_env_collect.sh: line 106: nvidia-smi: command not found
== cuda libs  ===================================================
== cat /etc/issue ===============================================
Darwin mbp-2.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
Mac OS X 10.13.4
== are we in docker =============================================
No
== compiler =====================================================
Apple LLVM version 9.1.0 (clang-9<IP_ADDRESS>)
Target: x86_64-apple-darwin17.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
== uname -a =====================================================
Darwin mbp-2.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
== check pips ===================================================
numpy                              1.14.2
protobuf                           3.5.2.post1
tensorflow                         1.8.0
tensorflow-hub                     0.1.0
tensorflow-model-analysis          0.6.0
tensorflow-serving-api             1.8.0
tensorflow-tensorboard             1.5.0
tensorflow-transform               0.6.0
tensorflowjs                       0.1.0
tensorflowonspark                  1.0.0
== check for virtualenv =========================================
False
== tensorflow import ============================================
tf.VERSION = 1.8.0
tf.GIT_VERSION = v1.8.0-0-g93bc2e2072
tf.COMPILER_VERSION = v1.8.0-0-g93bc2e2072
Sanity check: array([1], dtype=int32)
/usr/local/lib/python2.7/site-packages/h5py/init.py:36: FutureWarning: Conversion of the second argument of issubdtype from float to np.floating is deprecated. In future, it will be treated as np.float64 == np.dtype(float).type.
from ._conv import register_converters as _register_converters
== env ==========================================================
LD_LIBRARY_PATH is unset
DYLD_LIBRARY_PATH is unset
== nvidia-smi ===================================================
./tf_env_collect.sh: line 106: nvidia-smi: command not found
== cuda libs  ===================================================
Describe the problem
We have implement the async distributed TensorFlow training and find some issues. Once all the master(the worker with index 0), ps and workers start, the master will start training. And sometime(not always) one of the workers will halt and have no chance to end the progress.
Here is the test distributed script .
Here is the log of master which is normal and successfully finished.

Here is the log of ps which is normal and join for all workers finished.

Here is the log of worker which is abnormal. It failed to run since master has been finished. If the epoch is larger and master need more time to run, this worker may run and finish as well.

Source code / logs
Above.

Moreover, we have test in multi-node with unstable network. The worker may finish before master starting which results in master could never exit and export the model.
I don't think it's what we expect. Is there any way to guarantee the master will finish at any situation?

@mrry this seems like a "distributed training" issue. Can you please comment?

I can see two possibilities here:

If one task depends on another then you need some mechanism to ensure that all tasks eventually come up at the same time, and retry in the event of failure. A cluster manager like Kubernetes or Slurm would be helpful here.
If a task can run independently, then try setting ConfigProto.device_filters to contain only the device name prefixes for the devices it needs (e.g. the filters for the master task could be ["/job:master", "/job:ps"] if the master task does not need to use the worker tasks).

I've run into the same issue. As suggested by @mrry , I was able to resolve this by using device filters.
For example,
def _get_session_config_from_env_var():
  """Returns a tf.ConfigProto instance that has appropriate device_filters set.
  """

  tf_config = json.loads(os.environ.get('TF_CONFIG', '{}'))

  if (tf_config and 'task' in tf_config and 'type' in tf_config['task'] and
      'index' in tf_config['task']):
    # Master should only communicate with itself and ps
    if tf_config['task']['type'] == 'master':
      return tf.ConfigProto(device_filters=['/job:ps', '/job:master'])
    # Worker should only communicate with itself and ps
    elif tf_config['task']['type'] == 'worker':
      return tf.ConfigProto(device_filters=[
          '/job:ps',
          '/job:worker/task:%d' % tf_config['task']['index']
      ])
  return None

(originally from https://github.com/GoogleCloudPlatform/cloudml-samples/blob/master/census/estimator/trainer/task.py)
Outside of an estimator, you can use a MonitoredTrainingSession:
session = tf.train.MonitoredTrainingSession(config=_get_session_config_from_env_var(), ...)

With an estimator, instead, this just involves using
config = tf.estimator.RunConfig(session_config=_get_session_config_from_env_var())

Nagging Assignee @mrry: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@tobegit3hub Hi, please try using ConfigProto.device_filters and see if you are able to resolve this issue.
Note : Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

Sorry for the late response.
The ConfigProto.device_filters works work me as well. Thanks @mrry and @mattkindy-praetorian 😃


[PackageLoading] Fix linux XCTest module name

This was colliding with main package module name if there is only one
module. It got broken during the transition from TestSuite to Tests
suffix.
Fixes SR-2244

...all the more reason to have some functional test for swifttest on linux

can we create a symlink to xctest during bootstrap and then pass it when running swift test from tests?

/cc @abertelrud ah, this probably explains the other part of the failure on the swift-integration-tests builder.

@aciidb0mb3r Is it possible to at least test the module names don't collide at the PackageBuilder or PackageGraph level?

@ddunbar ah I think it should be, will check and add test case

added

I think something needs to be normalized, I get:
/home/ddunbar/public/swift-project/swiftpm/Tests/PackageLoadingTests/ConventionTests.swift:657: error: ConventionTests.testTestsProduct : XCTAssertEqual failed: ("["BarTests", "FooTests"]") is not equal to ("["FooTests", "BarTests"]") -

fixed

Thanks @aciidb0mb3r.  I don't fully understand what's going on here, because I also did Linux tests of the PR before landing it.  Is this a collision that happens all the time or just some times?

It only happens when the package has a target with the same name as the package, I think.


Update user story in to user stories template

User story for epic - 1
As a web developer, I want to use Agile and CI/CD methodologies to efficiently and collaboratively develop a website that meets the customer's requirements.
As a customer, I want a website to be developed using Agile and CI/CD methodologies to ensure efficient collaboration and high-quality delivery.
Acceptance Criteria:

The website must be developed using Agile and CI/CD methodologies.
The website must meet all of the customer's requirements and specifications.
The website must be tested thoroughly to ensure high quality and functionality.
The website must be deployed to production without any issues or errors.
The development team must collaborate effectively throughout the development process.
The development team must provide regular updates and progress reports to the customer.
The website must be delivered on time and within budget.
The development team must provide documentation and support to the customer after the website is delivered.
The customer must be satisfied with the final product and the development process.

User story for  epic - 2
As a website administrator, I want to improve the user experience and ensure legal compliance with ADA, COPPA, and GDPR standards by implementing Google Analytics.
As a customer, I want the website to provide a positive user experience while also complying with legal requirements such as ADA, COPPA, and GDPR standards. I request the implementation of Google Analytics to help improve the user experience and ensure legal compliance.
Acceptance Criteria:

Google Analytics must be implemented on the website to collect user data and analytics.
The website must comply with ADA, COPPA, and GDPR standards for user privacy and data protection.
The user experience on the website must be improved based on insights gathered from Google Analytics data.
The website must be regularly monitored and updated based on Google Analytics data to ensure ongoing improvements to user experience and compliance.
The implementation of Google Analytics must be documented and shared with relevant stakeholders.
The implementation must be completed within a specified timeline and budget.
The website must be tested to ensure that Google Analytics is implemented correctly and functioning properly.
The data collected by Google Analytics must be analyzed and reported to stakeholders on a regular basis.
The website administrator must be trained on how to use Google Analytics effectively and make data-driven decisions to improve the website.
The website must provide a positive user experience while also complying with legal requirements.


unix, win: consistently null-terminate buffers

libuv has multiple functions which return buffers. Make them consistent
with the following rules: the returned size does not include the null
byte, but the buffer is null terminated.
There is only one exception to the above: Linux abstract sockets,
because null bytes are not used as string terminators in those.
Refs: https://github.com/libuv/libuv/pull/674
R=@bnoordhuis, @sam-github, @cjihrig
CI: https://ci.nodejs.org/job/libuv+any-pr+multi/233/

LGTM

I  may be wrong but now when we get: UV_ENOBUFS we should malloc size + 1 now.
This is a breaking change, right?
It should return size + 1 directly, so no change in user code.

I think it's a semver major change, but the point of the change is consistency in the API.

I may be wrong but now when we get: UV_ENOBUFS we should malloc size + 1 now.

For the functions that have been modified, yes.

This is a breaking change, right?
It should return size + 1 directly, so no change in user code.

If you follow the analysis on #674 you'll see that the only consistent thing across all APIs was that the returned size did not include the terminating NULL byte. Some of them null-terminated the buffers, some others didn't. Now they all behave the same.
It is true that you actually need size+1 space, but this was already the case on most of the APIs. The reason for this change is for users to use string APIs as @sam-github mentioned, so "foo" is 3 chars long, but we add the \0 in case you use strlen or printf without length qualifiers.
It would have been nice if we had designed this APIs where designed so you could call them with a NULL buffer and they would tell you how much space is needed, but that boat has sailed, I'm afraid.

I think it's a semver major change, but the point of the change is consistency in the API.

See above, I'd rather not bump the major for this... :disappointed:

Alternatively, we could return size + 1 when giving a UV_ENOBUFS error, and size when succeeding.

Still a behavior change, but seems a lot less likely to break existing code.

Alternatively, we could return size + 1 when giving a UV_ENOBUFS error, and size when succeeding.

That was what I was missing. I think this is the way to go... So no overflow with existing code.

I like @saghul's suggestion, it avoids having to poll repeatedly to guess the right size.

Added a new patch implementing what I suggested here. PTAL everyone :-)
CI: https://ci.nodejs.org/job/libuv+any-pr+multi/237/

Still LGTM :+1:

Folks, can I get some more reviews? Thanks!

@bnoordhuis can you PPPTAL? :-)

Alea iacta est. Landed in 2606ba22a7012d0ed0ebb4464eec8fca9042c51e and 2606ba22a7012d0ed0ebb4464eec8fca9042c51e.


Mapping /.well-known for mailserver

I’m using poste.io as an email server behind npm but I’m having trouble with it generating it’s needed certs. In this document:
https://poste.io/doc/faq
it states I need to “ map /opt/www/.well-known folder to your web server to /.well-known relative path.” But I’m not exactly sure how to do that since I haven’t found .well-known anywhere in the data structure of npm.
Any assistance would be great. Otherwise this is a fantastic app and thanks for building it!

NPM should be used to generate the LetsEncrypt certificate.  So poste.io doesn't need to do it.  Is it something mandatory ?

Closing this issue.  Please re-open if needed.


Extension of paymaster feature to NFTs

The paymaster feature should be extended to minting and selling of NFTs too on zkSync, where people can decide to mint and sell NFTs with any token on zkSync network.

You can also buy using paymaster features too.

Ok

The paymaster feature should be extended to minting and selling of NFTs too on zkSync, where people can decide to mint and sell NFTs with any token on zkSync network.

Paymasters already work this way on zkSync. You can sponsor pretty much any kind of smart contract interaction. I already built one for minting and listing NFTs over 9 months ago.

Paymasters already work this way on zkSync. You can sponsor pretty much any kind of smart contract interaction. I already built one for minting and listing NFTs over 9 months ago.

The paymaster feature should be extended to minting and selling of NFTs too on zkSync, where people can decide to mint and sell NFTs with any token on zkSync network.

Paymasters already work this way on zkSync. You can sponsor pretty much any kind of smart contract interaction. I already built one for minting and listing NFTs over 9 months ago.


#39 contributing guidelines

Closes #39

Code of Conduct
Contributing Guidelines

Styleguide
Issue guide
PR guide
Development env setup
Using Sandbox

Tips and Tricks documentation for wrapping MDC modules

@OliverO2 I'd appreciate your feedback on the docs once you're back from holidays.

@OliverO2 I've merged this PR to unblock some further work, but I'd very much be interested to hear your thoughts for a potential separate PR with improvements.

@mpetuska I've just completed reviewing the new documentation. Excellent work! I've placed a PR with slight corrections as #56.
Need some more time to check the new Gradle setup and familiarize myself with docs/CONTRIBUTING.md.

Still investigating the new Gradle setup with Kotlin 1.6.10 plugin changes:
It seems that my sandbox/kotlin-js-store/yarn.lock changed automatically during a Gradle build. This implies that new/updated packages were downloaded from NPM, installed and run, re-opening the door for immediate execution of hijacked code via Node. Could we return to a setup that

requires explicit manual invocation to update kotlin-js-store/yarn.lock and
validates yarn.lock before proceeding to execute anything?


Addon isn't active for x.com domain

Addon "can't read or change data on this site" probably because x.com domain is not supported?

I remember that the update to support the x.com domain was made in 3.2.5.
Here is the corresponding commit that fixed the issue: https://github.com/Flkalas/TwitterMediaAssist/commit/0762c24062b6155f21a328166144b2f1a6991aa1
Is this problem still reproducible? Can you provide a screenshot or other information?

actually that was only my problem. im on 3.2.4 but checking for updates doesn't do anything. but on the firefox addons page there is already 3.2.6.

Re-added the addon and now it works!

Thank you for checking. Close the issue.


Errordescription on Select input

Is your feature request related to a problem? Please describe.
Select Input does not have an errorDescription
Describe the solution you'd like
Just like Textfield (and all other inputs) it should have an errorDescription

This was added in v6.4.0


executor(engine): support fast fail on business unretryable error

What problem does this PR solve?

Issue Number: ref #6915
task-2
What is changed and how it works?

Check error message in master meta before creating a new job, in executor side only, for two reasons

tiflow master is not business awareness, which means it doesn't handle business logic via registry.
Add this check in executor to unify the un-retryable message mechanism. ref: #6925

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/run-check-issue-triage-complete

/run-check-issue-triage-complete

Codecov Report

Merging #7061 (4e9fbe9) into master (9398176) will decrease coverage by 5.8357%.
The diff coverage is 61.4645%.

Additional details and impacted files

Flag
Coverage Δ

cdc
?

dm
51.8248% <33.3333%> (-0.1231%)
:arrow_down:

engine
60.4709% <65.0000%> (-1.7913%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #7061        +/-   ##
================================================
- Coverage   59.8253%   53.9896%   -5.8358%
================================================
  Files           791        425       -366
  Lines         90221      52925     -37296
================================================
- Hits          53975      28574     -25401
+ Misses        31498      21610      -9888
+ Partials       4748       2741      -2007

/run-engine-integration-test

/merge


ArrayLike should not have a readonly index signature

TypeScript Version:  2.0.0
Code
// from lib.d.ts
interface ArrayLike<T> {
    readonly length: number;
    readonly [n: number]: T;
}

Expected code:
// from lib.d.ts
interface ArrayLike<T> {
    readonly length: number;
    [n: number]: T;
}

The change to ArrayLike to be read-only breaks lots of existing code.

Can you share a sample of what breaks? ArrayLike is mostly used in argument position, and not return type position in the library, so the change in this context is benign.

This would be problematic for other people because if ArrayLike demands write access, many functions that don't perform mutation on the array will now fail to accept ReadOnlyArray parameters. It seems much more likely that anyone accepting an ArrayLike isn't mutating the array than is.

I would recommend having another type that has the desired shape under a different namespace, e.g glMatrix.ArrayLike that would be writable. your type will be assignable to the global ArrayLike but not the opposite.


request to add flag to ollama serve to

What are you trying to do?
my GPU is unsupported and I used to run it in CPU-only mode. After reinstalling, however, it thinks my 6700 is a Nvidia card and won't let me run Ollama serve.
`ollama serve                                                                                 ✔  23s 
time=2024-03-23T22:00:19.302-07:00 level=INFO source=images.go:806 msg="total blobs: 0"
time=2024-03-23T22:00:19.302-07:00 level=INFO source=images.go:813 msg="total unused blobs removed: 0"
time=2024-03-23T22:00:19.302-07:00 level=INFO source=routes.go:1110 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.29)"
time=2024-03-23T22:00:19.302-07:00 level=INFO source=payload_common.go:112 msg="Extracting dynamic libraries to /tmp/ollama156389064/runners ..."
time=2024-03-23T22:00:21.954-07:00 level=INFO source=payload_common.go:139 msg="Dynamic LLM libraries [cpu cpu_avx cpu_avx2 cuda_v11 rocm_v60000]"
time=2024-03-23T22:00:21.954-07:00 level=INFO source=gpu.go:77 msg="Detecting GPU type"
time=2024-03-23T22:00:21.955-07:00 level=INFO source=gpu.go:191 msg="Searching for GPU management library libnvidia-ml.so"
time=2024-03-23T22:00:21.980-07:00 level=INFO source=gpu.go:237 msg="Discovered GPU libraries: [/usr/lib/libnvidia-ml.so.550.54.14 /usr/lib64/libnvidia-ml.so.550.54.14 /opt/cuda/targets/x86_64-linux/lib/stubs/libnvidia-ml.so]"
time=2024-03-23T22:00:21.996-07:00 level=INFO source=gpu.go:249 msg="Unable to load CUDA management library /usr/lib/libnvidia-ml.so.550.54.14: nvml vram init failure: 9"
time=2024-03-23T22:00:22.011-07:00 level=INFO source=gpu.go:249 msg="Unable to load CUDA management library /usr/lib64/libnvidia-ml.so.550.54.14: nvml vram init failure: 9"
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING:
You should always run with libnvidia-ml.so that is installed with your
NVIDIA Display Driver. By default it's installed in /usr/lib and /usr/lib64.
libnvidia-ml.so in GDK package is a stub library that is attached only for
build purposes (e.g. machine that you build your application doesn't have
to have Display Driver installed).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Linked to libnvidia-ml library at wrong path : /opt/cuda/targets/x86_64-linux/lib/stubs/libnvidia-ml.so
time=2024-03-23T22:00:22.054-07:00 level=INFO source=gpu.go:249 msg="Unable to load CUDA management library /opt/cuda/targets/x86_64-linux/lib/stubs/libnvidia-ml.so: nvml vram init failure: 9"
time=2024-03-23T22:00:22.054-07:00 level=INFO source=cpu_common.go:11 msg="CPU has AVX2"
time=2024-03-23T22:00:22.054-07:00 level=WARN source=amd_linux.go:53 msg="ollama recommends running the https://www.amd.com/en/support/linux-drivers: amdgpu version file missing: /sys/module/amdgpu/version stat /sys/module/amdgpu/version: no such file or directory"
time=2024-03-23T22:00:22.055-07:00 level=INFO source=amd_linux.go:88 msg="detected amdgpu versions [gfx1031]"
time=2024-03-23T22:00:22.055-07:00 level=WARN source=amd_linux.go:350 msg="amdgpu detected, but no compatible rocm library found.  Either install rocm v6, or follow manual install instructions at https://github.com/ollama/ollama/blob/main/docs/linux.md#manual-install"
time=2024-03-23T22:00:22.055-07:00 level=WARN source=amd_linux.go:99 msg="unable to verify rocm library, will use cpu: no suitable rocm found, falling back to CPU"
time=2024-03-23T22:00:22.055-07:00 level=INFO source=routes.go:1133 msg="no GPU detected"
`
How should we solve this?
please add a flag to ollama serve to start in CPU only mode until more gpus are supported
What is the impact of not solving this?
ollama won't run at all and from another issue ticket the solution I found was '/set parameter num_gpu 0'. unfortunately, I cant run that because ollama won't even run.Ollama
Anything else?
No response

Those messages look normal for an unsupported GPU, and it should fallback to CPU mode automatically.  Can you explain what you mean by "won't let me run Ollama serve"

The process hangs indefinitely at the end of the no GPU detected line whenever I run Ollama serve. it never switches to CPU mode. just sits there incomplete until I kill it 20 mins later

What behavior do you see in the other terminal window where you run the client ollama run llama2 or whatever model you're trying to load into the CPU?  Does it show the spinner indefinitely?

I think it'd be helpful to be able to specify some override. I'm passing HSA_OVERRIDE_GFX_VERSION=9.0.0 to have my gfx9012 be used. So if the installer can ask or use this environment variable when installing on a machine with AMD GPU/iGPU, that would be very helpful.

Error: could not connect to ollama app, is it running?

I haven't been able to reproduce this failure mode.  I'm guessing that you didn't use our install script, which is why we didn't install the ROCm library, and none is found.  The gfx1031 card isn't supported automatically, but you might have luck with HSA_OVERRIDE_GFX_VERSION=10.3.0 once you get ROCm v6 installed on the system through some means.
We might be able to tell what's going wrong with OLLAMA_DEBUG=1  set on the server to generate more verbose logging.

Please give the above suggestions a try, and if you're still having problems, share your server log with OLLAMA_DEBUG=1 enabled so we can take a look.


Restore types property with raw proto contents

This issue inspired by https://github.com/googleapis/nodejs-vision/issues/17
As explained in the issue above, in pre-GAPIC Node.js API client libraries, we had a types property exposed directly from the module:
const types = require('@google-cloud/vision').types;

Expand to see the contents of types:

{ Vertex:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  BoundingPoly:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Position:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  TextAnnotation:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function],
     DetectedLanguage:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function] },
     DetectedBreak:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function],
        BreakType: [Object] },
     TextProperty:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function] } },
  Page:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Block:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function],
     BlockType: { UNKNOWN: 0, TEXT: 1, TABLE: 2, PICTURE: 3, RULER: 4, BARCODE: 5 } },
  Paragraph:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Word:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Symbol:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  WebDetection:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function],
     WebEntity:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function] },
     WebImage:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function] },
     WebPage:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function] } },
  Feature:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function],
     Type:
      { TYPE_UNSPECIFIED: 0,
        FACE_DETECTION: 1,
        LANDMARK_DETECTION: 2,
        LOGO_DETECTION: 3,
        LABEL_DETECTION: 4,
        TEXT_DETECTION: 5,
        DOCUMENT_TEXT_DETECTION: 11,
        SAFE_SEARCH_DETECTION: 6,
        IMAGE_PROPERTIES: 7,
        CROP_HINTS: 9,
        WEB_DETECTION: 10 } },
  ImageSource:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Image:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  FaceAnnotation:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function],
     Landmark:
      { [Function: Message]
        encode: [Function],
        decode: [Function],
        decodeDelimited: [Function],
        decode64: [Function],
        decodeHex: [Function],
        decodeJSON: [Function],
        Type: [Object] } },
  LocationInfo:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Property:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  EntityAnnotation:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  SafeSearchAnnotation:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  LatLongRect:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  ColorInfo:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  DominantColorsAnnotation:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  ImageProperties:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  CropHint:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  CropHintsAnnotation:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  CropHintsParams:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  ImageContext:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  AnnotateImageRequest:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  AnnotateImageResponse:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  BatchAnnotateImagesRequest:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  BatchAnnotateImagesResponse:
   { [Function: Message]
     encode: [Function],
     decode: [Function],
     decodeDelimited: [Function],
     decode64: [Function],
     decodeHex: [Function],
     decodeJSON: [Function] },
  Likelihood:
   { UNKNOWN: 0,
     VERY_UNLIKELY: 1,
     UNLIKELY: 2,
     POSSIBLE: 3,
     LIKELY: 4,
     VERY_LIKELY: 5 },
  ImageAnnotator:
   { [Function: ServiceClient]
     super_: [Function: Client],
     service: { batchAnnotateImages: [Object] } } }

We can restore similar functionality by adding a loop over the proto file from the generated file (e.g. https://github.com/googleapis/nodejs-vision/blob/master/src/v1/index.js):
const ImageAnnotatorClient = require('./image_annotator_client');
const grpc = require('google-gax').grpc();
const path = require('path');

module.exports.ImageAnnotatorClient = ImageAnnotatorClient;

module.exports.types = grpc.loadProto(
  path.join(__dirname, '..', '..', 'protos'),
  `google/cloud/vision/v1/image_annotator.proto`
).google.cloud.vision.v1;

This gives us a bit weirder of a response, though:

{ ImageAnnotator:
   { [Function: ServiceClient]
     super_: [Function: Client],
     service: { batchAnnotateImages: [Object] } },
  Feature:
   { Type:
      Enum {
        options: undefined,
        name: 'Type',
        parent: [Type],
        resolved: false,
        comment: null,
        filename<EMAIL_ADDRESS>        valuesById: [Object],
        values: [Object],
        comments: [Object],
        reserved: undefined } },
  ImageSource: {},
  Image: {},
  FaceAnnotation: { Landmark: { Type: [Enum] } },
  LocationInfo: {},
  Property: {},
  EntityAnnotation: {},
  SafeSearchAnnotation: {},
  LatLongRect: {},
  ColorInfo: {},
  DominantColorsAnnotation: {},
  ImageProperties: {},
  CropHint: {},
  CropHintsAnnotation: {},
  CropHintsParams: {},
  ImageContext: {},
  AnnotateImageRequest: {},
  AnnotateImageResponse: {},
  BatchAnnotateImagesRequest: {},
  BatchAnnotateImagesResponse: {},
  Likelihood:
   Enum {
     options: undefined,
     name: 'Likelihood',
     parent:
      Namespace {
        options: [Object],
        name: 'v1',
        parent: [Namespace],
        resolved: false,
        comment: null,
        filename: null,
        nested: [Object],
        _nestedArray: null,
        ImageAnnotator: [Service],
        Feature: [Type],
        ImageSource: [Type],
        Image: [Type],
        FaceAnnotation: [Type],
        LocationInfo: [Type],
        Property: [Type],
        EntityAnnotation: [Type],
        SafeSearchAnnotation: [Type],
        LatLongRect: [Type],
        ColorInfo: [Type],
        DominantColorsAnnotation: [Type],
        ImageProperties: [Type],
        CropHint: [Type],
        CropHintsAnnotation: [Type],
        CropHintsParams: [Type],
        ImageContext: [Type],
        AnnotateImageRequest: [Type],
        AnnotateImageResponse: [Type],
        BatchAnnotateImagesRequest: [Type],
        BatchAnnotateImagesResponse: [Type],
        Likelihood: [Object],
        Vertex: [Type],
        BoundingPoly: [Type],
        Position: [Type],
        TextAnnotation: [Type],
        Page: [Type],
        Block: [Type],
        Paragraph: [Type],
        Word: [Type],
        Symbol: [Type],
        WebDetection: [Type] },
     resolved: false,
     comment: null,
     filename<EMAIL_ADDRESS>     valuesById:
      { '0': 'UNKNOWN',
        '1': 'VERY_UNLIKELY',
        '2': 'UNLIKELY',
        '3': 'POSSIBLE',
        '4': 'LIKELY',
        '5': 'VERY_LIKELY' },
     values:
      { UNKNOWN: 0,
        VERY_UNLIKELY: 1,
        UNLIKELY: 2,
        POSSIBLE: 3,
        LIKELY: 4,
        VERY_LIKELY: 5 },
     comments:
      { UNKNOWN: null,
        VERY_UNLIKELY: null,
        UNLIKELY: null,
        POSSIBLE: null,
        LIKELY: null,
        VERY_LIKELY: null },
     reserved: undefined },
  Vertex: {},
  BoundingPoly: {},
  Position: {},
  TextAnnotation:
   { DetectedLanguage: {},
     DetectedBreak: { BreakType: [Enum] },
     TextProperty: {} },
  Page: {},
  Block:
   { BlockType:
      Enum {
        options: undefined,
        name: 'BlockType',
        parent: [Type],
        resolved: false,
        comment: null,
        filename<EMAIL_ADDRESS>        valuesById: [Object],
        values: [Object],
        comments: [Object],
        reserved: undefined } },
  Paragraph: {},
  Word: {},
  Symbol: {},
  WebDetection: { WebEntity: {}, WebImage: {}, WebPage: {} } }

To use one property as an example, Likelihood, here's what we want (old functionality):
types.Likelihood;
{
  UNKNOWN: 0,
  VERY_UNLIKELY: 1,
  UNLIKELY: 2,
  POSSIBLE: 3,
  LIKELY: 4,
  VERY_LIKELY: 5
}

... and what we get with my code above:
types.Likelihood;
{
  options: undefined,
  name: 'Likelihood',
  parent: {
    options: [Object],
    name: 'v1',
    parent: [Namespace],
    resolved: false,
    comment: null,
    filename: null,
    nested: [Object],
    _nestedArray: null,
    ImageAnnotator: [Service],
    Feature: [Type],
    ImageSource: [Type],
    Image: [Type],
    FaceAnnotation: [Type],
    LocationInfo: [Type],
    Property: [Type],
    EntityAnnotation: [Type],
    SafeSearchAnnotation: [Type],
    LatLongRect: [Type],
    ColorInfo: [Type],
    DominantColorsAnnotation: [Type],
    ImageProperties: [Type],
    CropHint: [Type],
    CropHintsAnnotation: [Type],
    CropHintsParams: [Type],
    ImageContext: [Type],
    AnnotateImageRequest: [Type],
    AnnotateImageResponse: [Type],
    BatchAnnotateImagesRequest: [Type],
    BatchAnnotateImagesResponse: [Type],
    Likelihood: [Object],
    Vertex: [Type],
    BoundingPoly: [Type],
    Position: [Type],
    TextAnnotation: [Type],
    Page: [Type],
    Block: [Type],
    Paragraph: [Type],
    Word: [Type],
    Symbol: [Type],
    WebDetection: [Type]
  },
  resolved: false,
  comment: null,
  filename<EMAIL_ADDRESS>  valuesById: {
    '0': 'UNKNOWN',
    '1': 'VERY_UNLIKELY',
    '2': 'UNLIKELY',
    '3': 'POSSIBLE',
    '4': 'LIKELY',
    '5': 'VERY_LIKELY'
  },
  values: {
    UNKNOWN: 0,
    VERY_UNLIKELY: 1,
    UNLIKELY: 2,
    POSSIBLE: 3,
    LIKELY: 4,
    VERY_LIKELY: 5
  },
  comments: {
    UNKNOWN: null,
    VERY_UNLIKELY: null,
    UNLIKELY: null,
    POSSIBLE: null,
    LIKELY: null,
    VERY_LIKELY: null
  },
  reserved: undefined
}

I would guess this is due to an underlying change in protobuf-- is there any way to restore the original functionality?

cc @lukesneeringer (original implementer, I believe) && @alexander-fenster

gentle ping @alexander-fenster @timburks

one more gentle ping :) This is preventing us from upgrading to newer versions of the Cloud Vision SDK in codelabs and open source sample apps because there is no more ways to compare Likelhoods.

@alexander-fenster Would you mind responding to this issue?
Feel free to justify downgrading the priority.

OK so two issues here. @fenixsolorzano, I believe you're talking about TypeScript typings, that we are working on and expect to release the first versions this quarter :)
@andreamlin @stephenplusplus @JustinBeckwith, re: exposing Protobuf types, since we're going to replace JavaScript gapic-generator with a new TypeScript generator, I will take care of that in the scope of that new generator. We'll leave this issue open for now and I'll transfer it to TypeScript generator repository soon.

@alexander-fenster Can you update that with the timeline for the TypeScript generator to be used in production?

We plan to have alpha (= generate some APIs) by the end of Q1'18, and beta (= generate most APIs) by the end of Q2'18.

@alexander-fenster any updates based on your progress with the new generator?

@alexander-fenster About TypeScript typings, is there another issue about that? I want to subscribe to that issue to be notified about it's completion

@alexander-fenster Could you provide an update and/or lower the priority if that makes sense?

@alexander-fenster We're out of SLO for this issue. Could provide an update and/or lower the priority?

I'm going to close this now since (a) we're moving to TypeScript with all the types available, happens this/next quarter, and (b) this is going to be WONTFIX for the current generator.


better defaults

fix: we don't use .idea config
fix: better defaults

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


Book a demo page can be improved much better

Is your feature request related to a problem? Please describe.
The designing of the book a demo page can be improved to a greater extend
Describe the solution you'd like
Such as the image is compressing a little which must be improved, both in laptop and responsive views

Pease assign me this issue


MINOR: better column name error description

What changes were proposed in this pull request?
This PR aims to better column name error description.
Why are the changes needed?
If column name is count(*), it can only throw 'No field name set', it not friendly to us.
How was this patch tested?
Testing with Doris
Was this patch authored or co-authored using generative AI tooling?
No

Thank you @xiedeyantu. Could you please use the original PR template?

Thank you @xiedeyantu. Could you please use the original PR template?

@ffacs fixed.


Fix ImageLoader not being initialized with webp or pnm features

Objective
Fixes #12353
When only webp was selected, ImageLoader would not be initialized.
That is, users using default-features = false would need to add png or bmp or something in addition to webp in order to use webp.
This was also the case for pnm.
Solution
Add webp and pnm to the list of features that trigger the initialization of ImageLoader.

Nice fix! Merging as trivial.


Assignment 3

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Upload dataset, write code for statistical analysis, and visualization; compare features.
#What did you learn from the changes you have made?
I did learn that data analysis is influenced by the statistical tools used. It is important to understand the data and not to overread into it.
#Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
In bootstrapping, I could have not calculated the sample mean value, but I did decide to include it because it is almost identical with the mean of the values include in the confidence interval.
#Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Writing code and correcting my own work, but nothing unexpected.
#How were these changes tested?
Each code was run as written.
A reference to a related issue in your repository (if applicable)
No.
#Checklist

[x ] I can confirm that my changes are working as intended

A3 complete


Breaking word across elements

If the character limit ends in the middle of a word that word is split over the two  elements when the more-text is shown.
Expected behaviour would be the more-text  element would contain the whole text and the read more would toggle ng-show between both elements?

Thanks @dickieirwin! I agree that this feature would be useful. Would you be able to create a pull request for this, and I ll make sure to merge it?

Sorry they ended up as two pull requests and I only applied the changes to the /src files... but you can see what needs doing should be a 5 min job

Great directive by the way!


Keep default cursor symbol when dragging nodes

Can't find a way to influence the cursor appearance during drag and drop. Hints welcome.


Extending the Providers.md

Hi,
I'm currently working on a similar library, but for python. Therefore I appreciate your collection of providers and I'm glad I found it. The only other list I am aware of is this (german) one.
As I want to test my python client on different APIs I would be happy to submit a MR to extend or update the list by updating information or links, adding new providers or add additional information.
However, I also think that such a list of providers should in the best case be available independent of a software solution in the long term. Some places to put it could be either the VDV GitHub where the specification of TRIAs is also located or a Wiki like TransitWiki What are your thoughts on that?
For now if I find anything worth updating in the providers.md I would submit a Pull Request, if that works for you.
Regards
Max

I'm currently working on a similar library, but for python.

Is it public? It would be great to have a family of OSS clients all linking to each other!

However, I also think that such a list of providers should in the best case be available independent of a software solution in the long term. Some places to put it could be either the VDV GitHub where the specification of TRIAs is also located or a Wiki like TransitWiki What are your thoughts on that?

vkrause and I had a very similar problem before: There were >=3 HAFAS clients, each specifying details about every known HAFAS API endpoint. We ended up creating a machine-readable repo of transit APIs. – In this repo, we could add TRIAS APIs to the schema!

I'm currently working on a similar library, but for python.

Is it public? It would be great to have a family of OSS clients all linking to each other!

Not yet, but I'm just in the beginning and there is nothing working to publish yet. But as soon there is some basic functionality I will clarify the details with my employer and we publish it.

However, I also think that such a list of providers should in the best case be available independent of a software solution in the long term. Some places to put it could be either the VDV GitHub where the specification of TRIAs is also located or a Wiki like TransitWiki What are your thoughts on that?

vkrause and I had a very similar problem before: There were >=3 HAFAS clients, each specifying details about every known HAFAS API endpoint. We ended up creating a machine-readable repo of transit APIs. – In this repo, we could add TRIAS APIs to the schema!

This sounds really promising :+1: I'll have a look at that repo asap.

[…] I'm just in the beginning and there is nothing working to publish yet. But as soon there is some basic functionality I will clarify the details with my employer and we publish it.

If you can, please publish it even before it is working! I've seen so many projects that intended to publish once working, and ended up unfinished and not published.

[…] I'm just in the beginning and there is nothing working to publish yet. But as soon there is some basic functionality I will clarify the details with my employer and we publish it.

If you can, please publish it even before it is working! I've seen so many projects that intended to publish once working, and ended up unfinished and not published.

Sure, will add a license and double check for authentication tokens or similar things and will publish it probably during next week. :+1:

@1Maxnet1 Great to hear, feel free to contribute if you find any new providers. To be honest, I'm not really happy with the way the providers are currently documented and agree that a dedicated, machine-readable list would be better.

Edit: In fact, we had already created an Issue for this. public-transport/transport-apis#43

@derhuerst Thanks for potining that out. It's a great proposal, I just somehow never saw the issue before. I will definetely look into it.

I'm currently working on a similar library, but for python.

Is it public? It would be great to have a family of OSS clients all linking to each other!

It's public now: https://gitlab.com/motis-datagon/trias-py
For further questions or feedback feel free to create issues there or see my contact information on my GitHub profile

It's public now: https://gitlab.com/motis-datagon/trias-py

AFAICT the actual source code implementing the client is still missing, right?

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

2. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!superharoun, @thecatshidog, @orware, @vipultanwr, @terrah27, @vtxyer, @bo1875, @jack97p, @mikeboiko, @Genysys, @MKRNaqeebi, @quanhieu, @MorganFH, @bluebell136, @tsmilessss, @compasty, @AdolfSchwarzenegger, @shinseitaro, @madsurgeon, @installtech


[Select] set currently selected as default value

Hi,
I know about the value tag in js. So I could allways pass value: 1 or something to every element. But is it also possible to have the currently selected value as the default value?

Hi, I have the same issue as the original poster, however the last jsfiddle provided by @vitalets does not work anymore and that is what I need. Do you think it's possible to fix it.

this is what I do and it seems to work fine
html

value of selection

javascript
$('[data-xeditable="true"]').editable({
    autotext: 'always'
});

if you use the remote json array, when you specify de attribute in the HTML: data-value="1", it's going to load the selected value.
E.g.
remoteFile.php
$a = [     ['value'=>"1", 'text' => 'yes'],     ['value'=>"0", 'text' => 'no'], ]; header('Content-type: text/json'); echo json_encode($a);
HTML file:
no
When the plugin is called, it's going to show the "no" option by default at first.

Hi, can anyone help me with this one?
When using the "select" type why is the "text" passed to the success(response,newVALUE) callback? And not the value? Is there an option I can set to enable this?

Dosn't work with select2 ajax source.


make build

Building ui

<EMAIL_ADDRESS>build /home/wayne/gosrc/src/github.com/brocaar/lora-app-server/ui
react-scripts build

module.js:471
throw err;
^
Error: Cannot find module '../scripts/build'
at Function.Module._resolveFilename (module.js:469:15)
at Function.resolve (internal/module.js:27:19)
at Object. (/home/wayne/gosrc/src/github.com/brocaar/lora-app-server/ui/node_modules/.bin/react-scripts:24:14)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:389:7)
npm ERR! Linux 4.4.0-83-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'react-scripts build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     react-scripts build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ui
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/wayne/gosrc/src/github.com/brocaar/lora-app-server/ui/npm-debug.log
make: *** [ui/build] Error 1

not use docker, and use ubuntu

Did you run make requirements ui-requirements? If yes, could you try again in the docker container? If that works, please check the differences in your own setup.
See also: https://docs.loraserver.io/lora-app-server/community/source/.

yes ,I have run make requirements ui-requirements , my ubuntu is ubuntu4.04.

Just tried again using the provided docker-compose / Docker container.
docker-compose build appserver
docker-compose run --rm appserver bash

# from within the container
make requirements ui-requirements
make build

All works fine.
Versions:
root@513f7470d9c6:/go/src/github.com/brocaar/lora-app-server# node --version
v7.10.0
root@513f7470d9c6:/go/src/github.com/brocaar/lora-app-server# npm --version
4.2.0

Could you please test also from the Docker container and then try to find out what the config differences are with your own Ubuntu based setup? It should be possible to build everything without using Docker (and I'm doing so myself), but as every setup is potentially different and with different versions, I would like to keep the docker-compose / Docker way as a reference.

thank you. Now is ok


Feature/code coverage

Standardized jacoco.exec and jacoco.xml files to be writtern to [WS]/modules/<moduleName]>/target/jacoco.*, instead of [WS]/modules/<moduleName>/modules/target/jacoco.*
This is to make sure both Travis CI/Coveralls and Jenkins/Sonar find jacoco files successfully

Coverage remained the same at 75.682% when pulling cf47c7e5ff2d02af95dbbf3a7b7206824d51264e on feature/code-coverage into 53065affc24bdd2e6b25d322fd10eaf01c90be15 on develop.

👍 :shipit:


2.1 tag missing prefix "v"

not a priority issue. but it will be good to have a consistent pattern.  our sysadmin had to spend some time to figure it out why scripts are not working
git tag -l
2.1
v1.3
v2.0
v2.0-beta.2
v2.0-beta.3
v2.0-beta.4
v2.1-beta1
v2.1-beta2

The link in the Changelog file uses v2.1, so it currently 404s.

@bureddy thanks for reporting the issue
@pakmarkthub please have a look

Thank you @bureddy and @traveller42 for reporting this issue. I have fixed it. Now it should looks like this.
$ git tag -l
v1.3
v2.0
v2.0-beta.1
v2.0-beta.2
v2.0-beta.3
v2.0-beta.4
v2.1
v2.1-beta1
v2.1-beta2

Also the link in the Changelog file should work now. Can you confirm?

I can confirm that the link is working.

Fixed. Closing.

Fixed. Closing.


accept the password-hashing-algorithm adr

Description
accept the password-hashing-algorithm adr
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 6f3798ab1aab5875585dfaf8215f280703fde3bd

Processing #6678.


Use WinMerge for GitHub Windows

Found:
In C:\Users"name of user" folder open file .gitconfig and write
[merge]
tool = winmerge
[mergetool]
prompt = false
keepBackup = false
keepTemporaries = false
[mergetool "winmerge"]
name = WinMerge
trustExitCode = true
cmd = "\"C:/Program Files (x86)/WinMerge/WinMergeU.exe\" \"$LOCAL\" \"$REMOTE\" \"$MERGED\" >/dev/null 2>&1"
keepBackup=false

Done


fix error handling of onSaveRecord

https://github.com/sunfish-shogi/electron-shogi/issues/306

Codecov Report
Base: 69.49% // Head: 69.48% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (c183d3f) compared to base (f14d6ff).
Patch coverage: 62.50% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #307      +/-   ##
==========================================
- Coverage   69.49%   69.48%   -0.01%
==========================================
  Files          65       65
  Lines       12065    12062       -3
  Branches     1616     1614       -2
==========================================
- Hits         8384     8381       -3
- Misses       2087     2089       +2
+ Partials     1594     1592       -2

Impacted Files
Coverage Δ

src/store/csa.ts
71.10% <60.00%> (-0.30%)
:arrow_down:

src/store/game.ts
62.55% <66.66%> (+0.05%)
:arrow_up:

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

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


Game crashing without error message

Game runs fine until a few minutes after loading up where it crashes without an error message.
I have tried enabling UseD3D8to9 in global.ini (a solution found in another issue report) but that didn't help
Windows 11 x64, i5 9600K, GTX 1650 Super
cyber_engine_tweaks.log

Fixed in 1.19.3


Button does not work

I have problem with button. I have code:
    final line15 =
    chips.singleWhere((chip) => chip.label == 'pinctrl-bcm2835').lines[15];

    await line15.requestInput(
        consumer: "BUTTON",
        activeState: ActiveState.high,
        triggers: {SignalEdge.falling, SignalEdge.rising});

    /// Log line events for eternity.
    line15.onEvent.listen((event) {
      print("Button: $event");
    });

It doesn't work. But if i execute python ./button.py and exit, my code starts to work.
// button.py
import RPi.GPIO as GPIO # Import Raspberry Pi GPIO library
def button_callback(channel):
    print("Button was pushed!")
GPIO.setwarnings(False) # Ignore warning for now
GPIO.setmode(GPIO.BOARD) # Use physical pin numbering
GPIO.setup(10, GPIO.IN, pull_up_down=GPIO.PUD_DOWN) # Set pin 10 to be an input pin and set initial value to be pulled low (off)
GPIO.add_event_detect(10,GPIO.RISING,callback=button_callback) # Setup event on pin 10 rising edge
message = input("Press enter to quit\n\n") # Run until someone presses enter
GPIO.cleanup() # Clean up

Can you try doing a full reboot and execute your flutter code right after that? (in the best case, reboot, login and execute flutter-pi)
If it doesn't work then, can you give me the outputs of lsgpio before and while flutter is running.
You can also try running gpiomon 0 15 to listen to BCM15 from shell. (Please don't execute your python script before any of those commands either)
The Raspberry Pi has a long history of GPIO interfaces:

first, people accessed GPIO by accessing the hardware themselves (i.e. mapping /dev/mem), which is very very bad
then, the sysfs interface was used
now, the newer gpiodev / gpiod (/dev/gpiochipX) should be used

For example, I think wiringPi uses the first way, I think RPi.GPIO uses the 2nd way and flutter-pi of course uses the 3rd way, the gpiod interface.
The inter-compatibility of these interfaces isn't clear, i.e. I'm not sure you can use the sysfs and gpiod concurrently. (Accessing the raw hardware is of course the most incompatible option of them all, that'll basically result in the kernel driver and the userspace process concurrently accessing the GPIO memory)
In practice, these different interfaces will cause all sorts of strange problems. For example, I had the problem that I couldn't get any line events at all inside flutter after I ran a specific program. Turns out that program was accessing the GPIO memory directly.

Can you try doing a full reboot and execute your flutter code right after that?
Yes, afte reboot my code does not work

If it doesn't work then, can you give me the outputs of lsgpio before and while flutter is running.
You can also try running gpiomon 0 15 to listen to BCM15 from shell. (Please don't execute your python script before any of those commands either)

What about this?

@ardera

reboot.

gpioinfo
gpiochip0 - 54 lines:
	line   0:      unnamed       unused   input  active-high
// CUT
	line  11:      unnamed       unused   input  active-high
	line  12:      unnamed       unused   input  active-high
	line  13:      unnamed       unused   input  active-high
	line  14:      unnamed       unused   input  active-high
	line  15:      unnamed       unused   input  active-high
	line  16:      unnamed       unused   input  active-high
	line  17:      unnamed       unused   input  active-high
	line  18:      unnamed       unused   input  active-high
	line  19:      unnamed       unused   input  active-high
gpiochip1 - 8 lines:
	line   0:      "BT_ON"       unused   input  active-high
	line   1:      "WL_ON"       unused   input  active-high
	line   2: "PWR_LED_OFF" "led1" output active-low [used]
	line   3: "GLOBAL_RESET" unused input active-high
	line   4: "VDD_SD_IO_SEL" "vdd-sd-io" output active-high [used]
	line   5:   "CAM_GPIO"       unused   input  active-high
	line   6:      unnamed     "vcc-sd"  output  active-high [used]
	line   7:      unnamed       unused   input  active-high
gpiochip2 - 2 lines:
	line   0:      unnamed       unused   input  active-high
	line   1:      unnamed       unused   input  active-high

flutter_gpio_test - BUTTON does'n work
flutter: 15:  LineInfo(consumer: 'BUTTON', direction:  input, isUsed: true, isRequested: true, isFree: false)

gpioinfo - (Done in parallel)
gpiochip0 - 54 lines:
// CUT
	line  14:      unnamed "flutter_gpiod test" output active-high [used]
	line  15:      unnamed     "BUTTON"   input  active-high [used]
	line  16:      unnamed       unused   input  active-high
	line  17:      unnamed        "PIR"   input  active-high [used]
gpiochip1 - 8 lines:
	line   0:      "BT_ON"       unused   input  active-high
	line   1:      "WL_ON"       unused   input  active-high
	line   2: "PWR_LED_OFF" "led1" output active-low [used]
	line   3: "GLOBAL_RESET" unused input active-high
	line   4: "VDD_SD_IO_SEL" "vdd-sd-io" output active-high [used]
	line   5:   "CAM_GPIO"       unused   input  active-high
	line   6:      unnamed     "vcc-sd"  output  active-high [used]
	line   7:      unnamed       unused   input  active-high
gpiochip2 - 2 lines:
	line   0:      unnamed       unused   input  active-high
	line   1:      unnamed       unused   input  active-high

exit flutter_gpio_test

gpioinfo

gpiochip0 - 54 lines:
	line   0:      unnamed       unused   input  active-high
//CUT
	line  10:      unnamed       unused   input  active-high
	line  11:      unnamed       unused   input  active-high
	line  12:      unnamed       unused   input  active-high
	line  13:      unnamed       unused   input  active-high
	line  14:      unnamed       unused  output  active-high
	line  15:      unnamed       unused   input  active-high
	line  16:      unnamed       unused   input  active-high
	line  17:      unnamed       unused   input  active-high
	line  18:      unnamed       unused   input  active-high
	line  19:      unnamed       unused   input  active-high

python (run & exit)
gpioinfo

gpiochip0 - 54 lines:
	line   0:      unnamed       unused   input  active-high
	line   1:      unnamed       unused   input  active-high
	line   2:      unnamed       unused   input  active-high
	line   3:      unnamed       unused   input  active-high
	line   4:      unnamed       unused   input  active-high
	line   5:      unnamed       unused   input  active-high
	line   6:      unnamed       unused   input  active-high
	line   7:      unnamed       unused   input  active-high
	line   8:      unnamed       unused   input  active-high
	line   9:      unnamed       unused   input  active-high
	line  10:      unnamed       unused   input  active-high
	line  11:      unnamed       unused   input  active-high
	line  12:      unnamed       unused   input  active-high
	line  13:      unnamed       unused   input  active-high
	line  14:      unnamed       unused  output  active-high
	line  15:      unnamed       unused   input  active-high
	line  16:      unnamed       unused   input  active-high
	line  17:      unnamed       unused   input  active-high
	line  18:      unnamed       unused   input  active-high
	line  19:      unnamed       unused   input  active-high
	line  20:      unnamed       unused   input  active-high

flutter_gpio_test - WORK

flutter: Button: SignalEvent(edge: rising, time: 2020-05-22 18:05:27.935929)
flutter: Button: SignalEvent(edge: falling, time: 2020-05-22 18:05:28.065014)
flutter: Button: SignalEvent(edge: rising, time: 2020-05-22 18:05:28.065029)

PS: lsgpio

-bash: lsgpio: command not found

python
2  gpioinfo (Done in parallel)
show:

gpiochip0 - 54 lines:
	line   0:      unnamed       unused   input  active-high
	line   1:      unnamed       unused   input  active-high
	line   2:      unnamed       unused   input  active-high
	line   3:      unnamed       unused   input  active-high
	line   4:      unnamed       unused   input  active-high
	line   5:      unnamed       unused   input  active-high
	line   6:      unnamed       unused   input  active-high
	line   7:      unnamed       unused   input  active-high
	line   8:      unnamed       unused   input  active-high
	line   9:      unnamed       unused   input  active-high
	line  10:      unnamed       unused   input  active-high
	line  11:      unnamed       unused   input  active-high
	line  12:      unnamed       unused   input  active-high
	line  13:      unnamed       unused   input  active-high
	line  14:      unnamed       unused  output  active-high
	line  15:      unnamed      "sysfs"   input  active-high [used]
	line  16:      unnamed       unused   input  active-high
	line  17:      unnamed       unused   input  active-high
	line  18:      unnamed       unused   input  active-high
	line  19:      unnamed       unused   input  active-high
	line  20:      unnamed       unused   input  active-high

reboot
gpiomon 0 15
show one line afrer start:
event:  RISING EDGE offset: 15 timestamp: [1590167527.152324171]
it has no reaction to the button.

That's strange, but if it doesn't work with gpiomon this is out of my scope.
You can try getting your system up to date using sudo apt update and sudo apt upgrade, but I'm not sure that'll help.
If the issue persists, it's best opening an issue on the raspbian kernels github repo.

I think I've figured out, what went wrong here. The button probably didn't have a pull-down resistor and relied on the pull-down functionality of the GPIO controller.
Handling of pull-down resistors is a pretty new feature in gpiod, though. According to this source you need at least a kernel with version 5.5.0 and libgpiod in version 1.5. Raspbian currently has a 5.4 kernel and libgpiod is currently at v1.2. So this currently just doesn't work in Raspbian. We will have to wait for the kernel update and a newer version of libgpiod to land in Raspbian (another option should be compiling your own kernel and libgpiod).
It would be nice if this feature could be added to flutter-gpiod, when it lands in Raspbian.

It would be nice if this feature could be added to flutter-gpiod, when it lands in Raspbian.

It's actually included already. It's called Bias. The GpioLine.requestInput, GpioLine.requestOutput, GpioLine.reconfigureInput and GpioLine.reconfigureOutput functions all have a bias argument. There's FlutterGpiod.supportsBias, which returns true if bias is supported on the platform (which is the case when the linux kernel version is >= 5.5)


Tuples with a single element cause some issues

Simple example:
script;
use std::chain::*;

struct S {
    t: (u64),
}

fn main() {
    let s = S {
        t: (2)
    };
}

I get the following compile error:
 8 |
 9 |     let s = S {
10 |         t2: (2)
   |              ^ Mismatched types.
expected: (u64)
found:    numeric.

11 |     };
12 | }

Can't get it to work even if I change (2) to 2, (2u64), or 2u64.

I investigated this some and found that this Sway code passes on the #1592 branch:
script;

struct S {
    t: (u64,),
}

fn main() {
    let s = S {
        t: (2,)
    };
}

The relevant parsing code is here: https://github.com/FuelLabs/sway/blob/786413b7b7a1bc47bd73169d90fa8abd762ea103/sway-parse/src/expr/mod.rs#L907
Ultimately, I don't know if there is a good way to determine if a user wants to parse something as parens or as a one-arity tuple, without forcing the trailing comma.
Python suffers from this same problem: https://www.w3schools.com/python/gloss_python_tuple_one_item.asp
And Rust: "Table B-8: Tuples" from https://doc.rust-lang.org/book/appendix-02-operators.html
So we need to decide:

Do we want to support one-arity tuples at all?
How will they be parsed? Is the comma necessary for creating a one-arity tuple?
How should we let users know that they may have made missed the trailing comma, without just showing them a type error? Rust chooses to show a warning that the parens are not necessary around the type argument, which is a good compromise: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=4e7d46dae23194d07eb563413a678d7e


Add loader on publish offer submission

We need a loader when user clicked the "send the offer" button on publish job offer page until we get some response

@shakti97 this is not needed. The job offers and the event submissions are manually approved. Maybe it is better to just display a message saying this will be approved soon. I will review this with the team to see if it is really needed.

okay no issue


base.css Uses justify by default

When I export the document using template, paragraphs are using justify. This not only looks bad in many cases, it also does not reflect what I am authoring (during authoring left align is used). The root cause is base.css using:
.container {
  margin-bottom: 180px;
  text-align: justify;
}

You should be able to override CSS in the template (Settings>Advanced>Default template).

I know I can override the template. This issue was about fixing the default template.

It's not broken for the default template, it's just not what YOU need. That doesn't constitute a bug.

The default template attempts to mimic the default theme.  The default theme shows a preview using left justification but the default template uses justify. That is the core issue. I am sorry if I wasn't clear in my description. My personal opinion on the style is only a side matter.

I can't reproduce the problem. The theme and the template are based on the same css. It's justify in both cases on my side.

Yes, you are correct. I was looking at the wrong section of the text in my document. Thank you.


Kubernetes Service Discovery via LabelSelector

Hello and thanks for this awesome project!
We want to deploy beyla to our environments, however for us the current service discovery mechanism is not working.
In Kubernetes a common way to select services is via labels. This is how usually other operator or controllers select applicable workloads.
Would it be possible to add a label selector to the Kubernetes service discovery mechanism?
I would also be willing to contribute a PR.
Using the current structure would only allow a hack of adding a single regexp matcher on the entire labels of a pod, as the processAttrs.metadata only allows a map[string]string{}.
So we probably would have to add a new config structure to accommodate a label selector.
Another question would be if it should be an actual label selector (meaning we will use this also for filtering out pods directly from the Kube api server), or if it will be a simple regexp match on the pod labels, same as we already do with the other Kubernetes metadata attributes.
What are your thoughts on this?

this has been implemented in #694


Adding detection context for 4662 events

For https://github.com/splunk/security_content/pull/2716

@nterl0k thank you! merging this to test the detection.


PHOENIX-7223 Make Sure Tools Always Close HBase Connections on Exit

Just for running tests on the backport

merged manually


Trim passwords

Handle errors when submitting invalid passwords. Idk if that's being done rn. https://github.com/fedimint/fedimint/pull/6253

Hi @elsirion,
I was reviewing this issue along with the changes from fedimint/fedimint#6253. Do you think trimming leading and trailing whitespace for passwords on the front-end would fully address the issue?
It seems like a logical step to ensure consistency between client and server, but should we also consider adding user-facing feedback for invalid passwords (e.g., too short or missing required characters)?
Happy to read your thoughts!


[PowerToys Run] Reset search after closing

Windows build number: Version 10.0.18363.836
PowerToys version: 0.18
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run
After closing Run using escape button and also after selecting a result, when I reopen Run, the search text and search results are not cleared from last search.
Isn't it better if the last search results cleared after Run closes?

Duplicate of #3237


hang in ReadInt activity

hang in ReadInt activity, why?

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

ID: 677e14d7-3d84-0007-3d62-4302b46a8781
Version Independent ID: d4a2f845-5bcd-48d4-eae6-72854e2f6598
Content: How to: Create a Sequential Workflow
Content Source: docs/framework/windows-workflow-foundation/how-to-create-a-sequential-workflow.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

This is a dupe of #8622.


Missing metadata in some callback handler methods

Issue you'd like to raise.
I only see metadata as parameter for few callback handler methods, but I would like to have access to metadata in other methods such as on_chain_error() and on_llm_error().
Currently, I can only see the tags in these methods.
I have error handling in my callback handler using on_chain_error() and I'd like to add information in my metadata dictionary to my exceptions (such as LLM name, model, things related to my chain, etc...).
I can put a list of tags, but I'd much prefer to use a dictionary to get certain keys and have my exceptions instantiated properly.
Suggestion:
Please make both tags and metadata available for all callback handler methods.

https://api.python.langchain.com/en/stable/chains/langchain.chains.llm.LLMChain.html?highlight=llmchain#langchain.chains.llm.LLMChain.metadata
Langchain docs say that metadata is passed as arguments to the handlers, but I don't see it in all handler methods.


Possible syntax error in check-secrets.sh

Fresh clone of the latest build, commit 71eb5b5adc304c1a5541ddf025339efba5f2e2f8
Ran make local
When prompted for secrets options I think I chose the second option
After secrets are generated I get this error
Starting build/scripts/check-secrets.sh
build/scripts/check-secrets.sh: line 160: docker-compose: command not found
Read some documentation, looks like it should be docker compose (no hyphen). I changed the docker-compose command in the script to docker compose Script no longer generating the "build/scripts/check-secrets.sh: line 160: docker-compose: command not found" error
Running isle-dc on centos

My bad. On the server docker-compose was not installed. Once it was installed, the error message no longer displays.


feat: add option to cache resolved output values

:tada: This PR is included in version 7.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Package request: kdotool

xdotool-like utility for KDE Wayland using KWin's scripting API to control windows.
Metadata

homepage URL: https://github.com/jinliu/kdotool
license: Apache-2.0
platforms: linux

Add a :+1: reaction to issues you find important.

Duplicate of https://github.com/NixOS/nixpkgs/issues/303268


TTL, NT and XML views don't work

https://www.snik.eu/ontology/bb/Acid
https://www.snik.eu/ontology/Acid?output=application/rdf%2Bxml
No triples found for Acid. Did you configure the namespace correctly?

The link is incorrect, https://www.snik.eu/ontology/bb/Acid?output=application/rdf%2Bxml works.


ci: release workflow using release-automation-action

This PR:

Uses the nearform/optic-release-automation as the release workflow for the repo
Uses the manually created GCP OIDC configuration to authenticate when running the CD workflow
Uses GitHub Actions Secrets as the single source of truth for secrets in the repo

In the CD workflow, the changes were to create / update the secrets in Google Secret Manager using the values stored in GitHub, and to make the Cloud Run service pull those secrets from Secret Manager on runtime so the values won't show up plain-text in the GCP Dashboard.
Closes #326.

one thing's missing. if we stop releasing on pushes to master (which is intended), we need to set up also the notify-release action to remind us of doing releases if there are unreleased commits. inspire from the same reference repo please.

@Pehesi97 thanks and sorry for the back and forth. let's merge and I'll try to do a release


The last three columns in conll file and the method of generating the entity relationship diagram

Dear author,
I have reviewed your paper and found your code to be ingenious. I would like to cite your work in my future research; however, I have some questions regarding your methodology. Specifically, I am seeking clarification on whether the functionality part of your dataset (columns 3-5) was manually annotated or generated using a model, and I would appreciate it if you could provide any relevant code snippets for generating the last three columns in CoNLL dataset. Moreover, I am interested in learning more about how the entity relationship graph described in your paper was generated in the code and the steps required to execute the code and generate this entity relationship graph.

Hi Ning!

The columns 3-5 of the dataset is annotated using Spacy.
The entity relation graph is built using a adjacency matrix, and GNNs are used to update the representations.
I hope this helps.

Dear author,
Thank you very much for your response. It has been very helpful to me. I am currently using Spacy to annotate data (columns 2-4: ner, pos, and dep).
1.I'm not quite clear on how the fifth column of the CoNLL dataset(number) is derived.
2.Is it possible to generate entity relationship graphs using the code you provided?
Thank you!

Hi there!

The fifth column is the headword index (from the dependency tree) of the current work.
You can use the script build_graph.py to generate the entity relationship.

您好，请问这个conll文件是您自己标注的吗，当我使用中文数据集也需要这样的形式吗？label.txt影响后面的代码吗，因为我的中文数据集没有label.txt这个文件。谢谢

中文数据可以这样标注。

中文数据可以这样标注。
您好，请问是要自己一个一个标注吗，还是有这样的标注模型呀？另外请问labels.txt里的label是自己统计好的吗？可是还没有识别完，怎么确定有多少种呢？谢谢。可以的话可以加您联系方式吗？非常感谢

中文数据可以这样标注。

因为我找的数据集只是简单的BIO格式


Uploads Cleanup 400 when upload happened on a branch

In our project, we are using branching. The phrase push happens on a branch.
Now we want to cleanup the deleted keys, like mentioned in #22. But if I run phrase uploads cleanup, I'm getting an error:

Error: 400 Bad Request

Steps to reproduce:

run phrase push --branch tmp and copy the upload_id
run phrase uploads cleanup --id upload_id

I suspect it's because there is no option to pass a branch to the uploads cleanup command, and the master branch does not contain the passed upload ID.
P.S. If #22 is fixed and also working on branches, this issue would be obsolete for me.

Hey @dsimon-onventis, thanks for raising this issue. The cleanup command is right now missing the branch parameter. We will add the branch parameter to the command and I'll keep you updated once it is released.

This should be resolved with version 2.1.5 https://github.com/phrase/phrase-cli/releases/tag/2.1.5 Now you can just pass in the branch parameter --branch branch-name to the cleanup command


Mapping for changing buffer with a count

Instead of these
nmap <leader>1 <Plug>BufTabLine.Go(1)
nmap <leader>2 <Plug>BufTabLine.Go(2)
nmap <leader>3 <Plug>BufTabLine.Go(3)
nmap <leader>4 <Plug>BufTabLine.Go(4)
nmap <leader>5 <Plug>BufTabLine.Go(5)
nmap <leader>6 <Plug>BufTabLine.Go(6)
nmap <leader>7 <Plug>BufTabLine.Go(7)
nmap <leader>8 <Plug>BufTabLine.Go(8)
nmap <leader>9 <Plug>BufTabLine.Go(9)
nmap <leader>0 <Plug>BufTabLine.Go(10)

I would like to have a simple maping for <space> which would take a count parameter.
Then after invoking 5<space> I would expect vim to switch to 5'th buffer according to the ordinal numbering g:buftabline_numbers = 2.
I wouldn't bother, however I simply can't spend days reading Vim's documentation and figuring out its quirks just to do such simple thing :disappointed:
EDIT: Great plugin btw!

Voilà: nmap <expr> <Space> '<Plug>BufTabLine.Go(' . v:count . ')'

Works like a charm. I allowed myself a small tweak:
nmap <expr> <tab> v:count > 0 ? '<Plug>BufTabLine.Go(' . v:count . ')' : ':bnext<cr>'
nmap <expr> <s-tab> v:count > 0 ? '<Plug>BufTabLine.Go(' . v:count . ')' : ':bprev<cr>'

Thank you!

Gladly 😊


"act-json-mqtt":true still sends gas values in separate topics

When I enable act-json-mqtt":true gas values are still send into separate topics:
getpraut/P1-Dongle-Pro/all {"timestamp":"240216170332W","energy_delivered_tariff1":3486.242,"energy_delivered_tariff2":8765.862,"energy_returned_tariff1":0.566,"energy_returned_tariff2":0.985,"electricity_tariff":"0002","power_delivered":0.124,"power_returned":0.024,"current_l1":0,"current_l2":0,"current_l3":1,"power_delivered_l1":0.068,"power_delivered_l2":0.056,"power_delivered_l3":0,"power_returned_l1":0,"power_returned_l2":0,"power_returned_l3":0.024,"gas":8952.446289,"gas_ts":"240216160000W"}
getpraut/P1-Dongle-Pro/gas_delivered 8952.446
getpraut/P1-Dongle-Pro/gas_delivered_timestamp<PHONE_NUMBER>00W

this shouldn't be.... I changed this in the current code.


Nifi 2440 - Add Last Modified Time attribute to ListSFTP

Add last modified time  attribute to flow files generated by ListSFTP processor.
The attribute format is consistent with what is expected by downstream processors like PutFile
attribute - file.lastModifiedTime
attribute format - yyyy-MM-dd'T'HH:mm:ssZ

Hi @kirkalicious, could you please rebase and squash your PR into one single commit to ease the review process?

Yes. Sorry about that.
On Monday, August 8, 2016, Pierre Villard<EMAIL_ADDRESS>wrote:

Hi @kirkalicious https://github.com/kirkalicious, could you please
rebase and squash your PR into one single commit to ease the review process?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/nifi/pull/774#issuecomment-238391273, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABcVqHKDj9zL5gQtwqsAz8KjnepBOkzYks5qd6cGgaJpZM4JbKzu
.

--
Kirk Tarou
The 9:20 Special - Lindy Hop & Swing Dance Venue
2460 Sutter Street, San Francisco, CA, 94115
www.920special.com
Find us here: Facebook http://www.facebook.com/group.php?gid=8134453869
Twitter http://twitter.com/920special Yelp!
http://www.yelp.com/biz/9-20-special-san-francisco YouTube
http://www.youtube.com/920special


Very slow when i implement on Macos

i have implement at: https://github.com/x2team/docker-nginx-mysql-php-fpm
but seem rather it is so slow on my Macos 👍
Please help me! Request from 3->4s , tested with project laravel 8.x default

A newer version of Docker on MacOS (2.4) has been causing issues for a lot of people. Disabling gRPC FUSE in the preferences and restarting docker may help as well as downgrading to <IP_ADDRESS> https://github.com/docker/for-mac/issues/4957

@oranges13 You gave me an idea to downgrade the docker desktop version to <IP_ADDRESS> in Windows 10 Pro without WSL and it does solved the problem 👍 Thanks


To Do/Improvements

Deploy to PyPI

[ ] Complete bolded tasks below before releasing first version

Features

[ ] Add Excel support (Easy)
[ ] Add JSON support (Hard)
[ ] Add ability to connect to PostgresSQL databases not on localhost
[ ] Add ability to take subsets of columns
[ ] Add a mutate()-like function for Tables
[ ] SQLite to PostgresSQL conversion

Aesthetics

[ ] Make Tables repr() prettier and more useful, e.g. showing a summary of number of columns
[ ] Consistent text width throughout the package

Performance

[ ] Add feature so that if file is formatted "correctly", use Postgres COPY instead of bulk INSERTs for better performance
[ ] Look into more database specific optimizations

Code

[ ] Add tests for N/A value replacement
[ ] Add tests using real world data sets
[ ] Add tests for PostgresSQL
[ ] Add tests for command line interface

Bugs

[ ] Fix error when user chooses primary key via CLI

Possible Resources
https://github.com/python-excel/xlrd for reading Excel files

Starting a new list


Add 'services' command

Add 'services' command to retrieve the various services status and update error log output.

Future note: Requires /usr/local/etc/allservices.txt


Update README.md

Add yarn usage
Add various code formatting (semi-standard)
Add code-block type in code samples

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

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

Hello, @dweedon-stripe I understand, thanks. I updated the PR.


CIT 25 import data fixes and additions

Adds the new models to the data import process.
Orders the data import process to ensure that all resources are imported in the correct order.
Lakes is omited from the import process at the moment due to the data needing to be thinned down.
Still a work in progress and in development.

All the data imports correctly as far as I can tell and the communities are now linked properly.


What sensors do we need to have in the car for open pilot get working??

Refer to the wiki:
https://community.comma.ai/wiki/index.php/Main_Page#Is_my_vehicle_a_good_candidate.3F

okay, thax man...
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On 2 September 2017 at 22:45, pjlao307<EMAIL_ADDRESS>wrote:

Refer to the wiki:
https://community.comma.ai/wiki/index.php/Main_Page#Is_
my_vehicle_a_good_candidate.3F
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/commaai/openpilot/issues/132#issuecomment-326757578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL0XmWU0alNKxwsu2DgegL9EuDOzSw9mks5seY1LgaJpZM4PK8Io
.

--
Regards,
Hemang Joshi,
JETPACE Technologies.
Email<EMAIL_ADDRESS>mobile : +919409077371


Refactor profile classes

Refactor them to be more in line with AngularJS-style factories.

Commited with f1e7da3d6ae3f1f57e1e4bf43d101e76529c89d6


Auto Format dont work

Auto Format dont work

@dsweb19778
It works fine
Could you provide more information? OS, solargraph config and logs from Lapce?
Which ruby version manager do you use?

@Stanislav-Lapata
OS : linux Manjaro Kde
Version : 3.2.0
global configuration for solargraph


Fix CI

0.01s$ git config --global url."git@github.com:".insteadOf "https://github.com/"
0.12s$ go get -u github.com/golang/dep/cmd/dep
# cd .; git clone https://github.com/golang/dep /home/travis/gopath/src/github.com/golang/dep
Cloning into '/home/travis/gopath/src/github.com/golang/dep'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
package github.com/golang/dep/cmd/dep: exit status 128

Removed that git config. No need to pull any private repositories here.


Embedded

Is there a way for me to host the tour in my webpage that was created with the API and create an embedded link for me to embed it on another person's webpage?

Make it a separate page and use an <iframe>. This is how the standalone version works (as well as things like YouTube embeds).

So I should use the standalone.js too? and the API things I have for my tour should be done in that html pannellum.htm?

No, you shouldn't use standalone.js is you're using the API. I just mentioned pannellum.htm as an example of using the Pannellum API in an <iframe>. The embed code would be something like this: <iframe width="480" height="390" allowfullscreen style="border-style:none;" src="youriframe.html"></iframe>

@mpetroff: So using the iframe approach (standalone.html) is the recommended/best practice approach for putting a panorama on a web page?
For frameworks it is also possible to add the pannellum javascripts and the initialization directly (on a DIV element that should hold the pannellum viewer) - this approach may reduce issues with text leaking into search results.

It's the recommend approach if you want to allow other people to embed it, which is what this issue is about. For other use cases, it depends. The <iframe> approach is slightly simpler, while the API allows a lot more flexibility.


Fix link to promise example

Remove outdated links
Add new link to current example

TIL

I wonder if that's where "kudos" came from?

Kudos is actually also a Finnish word. Little bit different meaning though :smile:

What's the difference?

https://fi.wikipedia.org/wiki/Kudos


Make the silent script more sysprep friendly?

Would it be possible to add a switch/option somewhere to the silent script to make it sysprep friendly? Basically, sysprep will fail if any apps from the appstore are installed on the current user profile. To get around this you need to get-appxpackage | remove-appxpackage . After doing this sysprep runs and when a user is logged onto a computer is built using the prepared image, the appropriate provisioned packages will be installed (App Store).

Just doing some testing with this currently, not sure if this is the best solution to fixing sysprep.

Finished testing this. Apps weren't being provisioned, but it was due to issue https://github.com/Sycnex/Windows10Debloater/issues/3 . Once that issue is fixed, running get-appxpackage | remove-appxpackage is required for sysprep to be able to work. The store and others that are whitelisted install automatically after doing this when you image a machine and login.

I added a $SysPrep switch parameter and function on lines 7 - 17. This will run the following command: get-appxpackage | remove-appxpackage. This is required in order to be used successfully with SysPrep.
I also added a $StopEdgePDF parameter, for those who do not wish to stop Edge from being used as the default PDF viewer, or for those who worry about unintended consequences (not being able to potentially choose Edge without removing the specified registry keys).
You can now run the script with the switch parameter -SysPrep, along with -Debloat, and -StopEdgePDF.
I also changed the name of the file (it just sounds better) to Windows10SilentDebloater.ps1.


Session Energy doesn't show correct value

The correct value as shown in easee.cloud is 1.9kWh but the card shows 1937 kWh. It should probably show 1.937 kWh. However I it seems also the sensor itself doesn't show correct value. It shows 1.937 Wh no matter if I check or uncheck kWh to Wh checkbox in configuration. Also if the car is not connected shouldn't this be 0 ?

It is the same situation for Lifetime Energy.

I'll check the scaling. I remember that it is not working perfect in the integration when changing between the units, it typically worked best when removing and adding the integration and applying what one want in the first place. But I also think the card is not adapted for Wh, so I'll check that.
Session energy is reset by Easee, so nothing we can do there. I believe it is reset upon next connection or something. If I recall correctly mine reports session energy when I'm away and until I reconnect. Here's mine and I'm still not at home:

This has annoyed me since I use it to send a Telegram message to my phone each morning with charging energy during the night, but if I wasn't driving the day before it keeps same value as day before. A workaround for this may be to setup a utility meter counting the lifetime energy and have HA reset it every night (daily).

It is clear now. I have removed the integration and added back and all seems to be fine. I will close the ticket. Thanks!


UBAN and some other operator changes (fixes #1447)

This change is O(mn) in code (m subcommands, n ban types), it's a huge mess.
One non-obvious change: I stopped enforcing KLINEs against loopback (#671 for context).

From discussion: UBAN ADD <account> should send you the IP addresses of the affected sessions, as a heads-up.

From discussion: UBAN ADD <account> should send you the IP addresses of the affected sessions, as a heads-up.

I completely forgot: this needs a manual entry!

I completely forgot: this needs a manual entry!


[Fuzzing] Update Secure JSON RPC Client fuzzers to use proptest

Motivation
This PR updates the existing Secure JSON RPC Client fuzzers to use proptest, thus allowing us to perform structured fuzzing and hopefully achieve better coverage.
Currently, the fuzzers used by the Secure JSON RPC Client take the approach of generating a ureq::Response template, converting the template into a json string, allowing the fuzzer to modify the json string, and then turning the modified string back into a ureq::Response. This is not ideal, as the modified string produced by the fuzzer may not always convert back into a ureq::Response successfully (causing the fuzzer to prematurely exit). To avoid this, we instead use proptest to generate an arbitrary ureq::Response, with different fields/internals directly. This avoids the need to serialize using json (which may fail), and thus will hopefully help us to achieve better coverage.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
All tests still pass locally.
Related PRs
None.

Thanks, @mimoo! Ready for another look. Note: I've collapsed the 3 commits into 1 because the changes are much smaller with your refactor 😄

/land


Upright meaning

Hi @yl92 !
Firstly, let me thank for your great work!
Could you, please, explain, what means upright ?
I'm curious about what is it, but unfortunately, I didn't find it anywhere in the description or elsewhere... :(
Kindly thank you beforehand for explanation.
Regards

Thank you, glad you like it!
The theme started with a version that used italics for functions / keywords etc. and later I added a version for each option that does not use italics, which I called upright. Some fonts, like IBM Plex Mono, has quite distinct italic design, which was why I used them in the first place – but then some other fonts are not as nicely done for italics and looks better without.
Example with italics:

Example without:

Probably a good idea to clarify it somewhere yeah!

Thanks for explanation!

22. 4. 2022 v 10:38, Yile Ou @.***>:

Thank you, glad you like it!
The theme started with a version that used italics for functions / keywords etc. and later I added a version for each option that does not use italics, which I called upright. Some fonts, like IBM Plex Mono, has quite distinct italic design, which was why I used them in the first place – but then some other fonts are not as nicely done for italics and looks better without.
Example with italics:
Example without:
Probably a good idea to clarify it somewhere yeah!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


Update chaos-engineering.md

Corrected and simplified the last statement under principles

@frachkid : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@absheik Would you review the proposed update to your article? Thanks.

@frachkid thank you for your contribution