Improve errmsgs 2

This pull requests makes some minor improvements to error messages for type errors. In particular,

it gives a good error message for the error in issue #1555. For the minimal example discussed in the comments to that issue, the error message is

ERROR: Error when compiling optex module: Type error
 6:9-18
  |
6 |        foo.append(4)
  |        ^^^^^^^^^^
?__builtin__.list[__builtin__.int] does not have an attribute append
Hint: you may need to test if foo is not None

it gives a not very good error message when compiling a branch of acton-streamer discussed in issue #1558. The error message is

ERROR: Error when compiling acton_streamer.main.main module: Type error
 586:34-39
    |
586 |actor NetconfGetPollSubscription(source: NetconfSource, dev_sub_key: Keypath, shared_schema: schema.SharedSchema, log_handler: logging.Handler):
    |                                 ^^^^^^
(NetconfSource, acton_streamer.common.mod.Keypath, acton_streamer.nsoapi.schema.SharedSchema, logging.Handler) must be castable to (_, _, _)

The first of these examples gives what we want, including a hint. But one must be aware that this was a very low hanging fruit; I do not expect it to be easy to give hints in general.
The second example at least gives a possible  location of the error, and with some careful reading one can see that there seems to be a problem with the number of arguments. But it does not say that, ca 300 lines earlier, an actor instance was created with only three args in the call... I believe that this will be what we end up with in the first round in many, many cases. We have two contradictory constraints, one is first solved and then the other is noted as in error. It is not at all obvious to me how to reorganize the code to give an error message which quotes from lines 317 and 586 and points out that they are incompatible.

@sydow nice, that looks great =)
We got pretty good errors for a mismatch in number of positional arguments to functions so it's a little surprising it's worse for actors but perhaps this is something that could improve in the actor / class unification.
At least this error gives one source code location, so it's possible to guesstimate :)

The problem with actors as compared with functions when it comes to positional arguments is as follows (for a smaller example than acton-streamer, look at test/typeerrors/ex13.act):
In the acton-streamer example (and ex13.act) the creation of an actor comes before (in the program text) the actor definition. Compile ex13.act and see that you get the same kind of error message as in acton-streamer. Then edit ex13 to move actor main after actor Act. Compile and see the nicer functional-style error message. This effect does not occur for functions (check ex14.act). I think it has to do with matchActorAssumption in Types.hs, but I gave up…
Björn

On 17 Oct 2023, at 21:44, Kristian Larsson @.***> wrote:
@sydow nice, that looks great =)
We got pretty good errors for a mismatch in number of positional arguments to functions so it's a little surprising it's worse for actors but perhaps this is something that could improve in the actor / class unification.
At least this error gives one source code location, so it's possible to guesstimate :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


chore: readd husky

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Readd husky

PR: let's add husky
also PR: remove random components
Pls open separated PR for that


Add HTTP/1.1 Response Builder

We have basic HTTP/1.1 request parsing in our fledgling HTTP server package, so now it's time to move on to response building.
That is, we want to add a ResponseBuilder class to packages/http/server.

Here's a proposed implementation plan to walk you through how I would approach it. This is a simple approach to start, and after it's done I think we'll both have ideas on how to enhance it by fiddling with the interface and/or implementation:

Create a :class ResponseBuilder in packages/http/server (in the future we may make this a :struct instead for better performance, but I'm still ironing kinks with :struct so I say avoid getting snagged on that for now)

Write a constructor for it that takes a target ByteStreamWritable (a trait/interface that has the << operator for appending chunks of Bytes to a logical stream. It can store this parameter in a field for persisting it across calls.

Add :fun ref methods for doing things like setting status codes, adding a header, or writing to the response body. Each of these methods should append Bytes chunks to the aforementioned target.

Consider using named methods for each known HTTP status code (e.g. status_not_found, status_forbidden, status_ok, etc.), since this is convenient for the caller and will let the compiler prevent mistakes with unknown status codes by complaining about a missing method for that name.

Write tests. In the tests you should find it convenient to use a Bytes.new as the target passed into the constructor, since that ByteStreamWritable is compatible with a plain Bytes because Bytes implements the << method. So you should be able to use @assert = bytes == b"[whatever content is expected]" at the end of each test to check what the written response was.

You may notice that with this approach, if you call the methods in the wrong order (like writing headers prior to writing a status code line), then you end up with a junk response content. In the future we will try out some type system tricks to prevent this, but for now I suggest leaving it simple and we can come back to this to improve it in a fancier way in the future.

Once this is in place, you may also want to update the HTTP server example in examples/http. Replace the simple bytes string literal response content with a ResponseBuilder that uses the io.write_stream as its target in its constructor.

Confirm that you can run the example it with a command like this one, which is similar to what I use for it:

make example extra_args="--backtrace --print-perf" dir="examples/http"

Confirm that while the example is running, it responds to HTTP requests on localhost port 8080. I use curl or sometimes the wrk command to hammer it with a lot of requests (although currently the performance won't be ideal because we're compiling in debug mode rather than release mode, so we're still missing LLVM optimizations - we will get this working in the future). Here's an example wrk command just as a proof of concept rather than as a serious test:

wrk -H 'Connection: keep-alive' --connections 256 --threads 1 --duration 5 --timeout 1s http://localhost:8080/example

Closing now that we merged #83


Fix broken rdrand implementation

_rdrand{32,64}_step returns 1 on success and zero on failure. See:
https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=_rdrand64_step&expand=4539
This means that the current implementation will actually hang on most processors:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=716f8f6a77ab6be76800ff7ee5d37970
This fixes the implementation to use the reccomdendation from the Intel SDM.
Signed-off-by: Joe Richey<EMAIL_ADDRESS>

bors r+

bors r+


Fix EncodeHex/DecodeHex

Fixes for the unfortunately merged #41:

add testcase for encoding (the testcase in #41 only checks roundtrip but this doesn't enforce compatibility with other implementations or protects against change in the encoding)
check bounds of decoded numbers in DecodeHex (to avoid crashing)
faster EncodeHex
faster DecodeHex
add documentation about the encoding (important as it is quite awkward: each hex digit is encoded as an int in range [16, 31])

Note: this is not an endorsement of the EncodeHex/DecodeHex feature. Instead I would prefer it would be completely removed because it is quite awkward.
Cc: @brandoneprice31

Thanks a lot.


Error socialsharing.share(...) Android 12

In Android 12 after trying to use method socialsharing.share(...) the application closes immediately, in android studio shows this error in the log:
java.lang.IllegalArgumentException: com.app-xxx: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.
    at android.app.PendingIntent.checkFlags(PendingIntent.java:375)
    at android.app.PendingIntent.getBroadcastAsUser(PendingIntent.java:645)
    at android.app.PendingIntent.getBroadcast(PendingIntent.java:632)
    at nl.xservices.plugins.SocialSharing$2.run(SocialSharing.java:274)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:920)

To solve this I had to go to android folder in the plugin, find SocialSharing.java, and replace this line:
 final PendingIntent pendingIntent = PendingIntent.getBroadcast(cordova.getActivity().getApplicationContext(), 0, receiverIntent, PendingIntent.FLAG_UPDATE_CURRENT);
With this code
        int pendingIntentValueFLAG = 0;         if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.S) {           pendingIntentValueFLAG  = PendingIntent.FLAG_MUTABLE;         }         else         {           pendingIntentValueFLAG  = PendingIntent.FLAG_UPDATE_CURRENT;         }         final PendingIntent pendingIntent = PendingIntent.getBroadcast(cordova.getActivity().getApplicationContext(), 0, receiverIntent, pendingIntentValueFLAG);
Cordova and plugin version:
"cordova": "11.0.0"
"cordova-android": "^10.1.2"
"cordova-plugin-x-socialsharing": "^6.0.3"

great stuff. This resolved the issue. Please merge this code on the next release. Thanks

@jeanluck36 @sachithd I am facing the same issue
https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin/issues/1176#issuecomment-1191642022d
@dilo99 did you resolve this?

In the plugin.xml file manually added
android:exported="true" to receiver element
    <config-file target="AndroidManifest.xml" parent="/*/application">       <receiver android:name="nl.xservices.plugins.ShareChooserPendingIntent" android:enabled="true" android:exported="true">         <intent-filter>           <action android:name="android.intent.action.SEND"/>         </intent-filter>       </receiver>     </config-file>

If you're upgrading to Capacitor 4, you may encounter this issue as I did.
As @sachithd guide above, to save people some time,  the file is in node_modules/cordova-plugin-x-socialsharing/plugin.xml

To anyone who got here recently:

There are 2PRs to fix this: #1158 #1181
Discussion continues in PR #1158
TLDR, is plugin dead? idk, if you are in rush try cordova-plugin-x-socialsharing-android12

I have the same error, and also the error about android:export=true.
The plugin seems dead. Is there any alternative with updates for the latest android?

In the plugin.xml file manually added android:exported="true" to receiver element
 <config-file target="AndroidManifest.xml" parent="/*/application"> <receiver android:name="nl.xservices.plugins.ShareChooserPendingIntent" android:enabled="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.SEND"/> </intent-filter> </receiver> </config-file>

It fix the issue for you? For me, I can't even build. I'm still seeing the message:
Apps targeting Android 12 and higher are required to specify an explicit value for android:exported when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details

@EddyVerbruggen can you please merge the pr for the solution for Android 12,13 ?

@EddyVerbruggen can you please merge the pr for the solution for Android 12,13 ?

I am also facing the same issue.
Is there any solution for the same? Please let me know if it is available.

@Topiya the fix was merged. please remove the plugin and add it again.

Thanks for the reply.
but latest plugin install didn't solve the issue for me in "cordova-android": "^11.0.0"
I got the solution by using "cordova-plugin-x-socialsharing-android12"

Same case as @Topiya, seems like the latest plugin is still not adding android:exported to the manifest. I solved it by using the forked plugin cordova-plugin-x-socialsharing-android12

@sachithd @Syahrul @timonjagi @vchabal @Topiya @pedropamn @bonjourjoel @jeanluck36
it has been fixed in my forked repo:
https://github.com/EYALIN/community-cordova-plugin-social-sharing
you can install it as an npm package:
cordova plugin add community-cordova-plugin-social-sharing --save

Does nl.xservices.plugins.ShareChooserPendingIntent actually have to be exported or could it be set to false?
I am getting the following for our app by the MobSF static analyzer:

Broadcast Receiver (nl.xservices.plugins.ShareChooserPendingIntent) is not Protected.
[android:exported=true]
A Broadcast Receiver is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device.


[FLINK-12803][python] Correct the package name for python API

What is the purpose of the change
This pull request corrects the package name of the flink-python module
Brief change log

Changes the package name from o.a.f.python -> o.a.f.api.python

Verifying this change
This change is a code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks for the PR @dianfu! 💯
@flinkbot approve all
Merging...


UI image data table

Overhauls Image Data UI

Moves from list to Table format
Adds tag value and styling based on rule action
Implements an infinite scroll
Images and tags are sorted based on rule actions and presence of unknown tags
Includes image thumbnails and a default svg when unavailable
Excludes unnecessary tags from table
Includes styling to better match Figma mockups

The color of the scroll bars

is nearly impossible for my eyes to resolve the page area from the background (if I rotate the color space I can see it).

The color of the scroll bars  is nearly impossible for my eyes to resolve the page area from the background (if I rotate the color space I can see it).

I did my best to recreate what you were seeing and adjust accordingly in 808131bfef0434c339f8feb03d57c83834784114. Can you check to see if this helps?

The color of the scroll bars  is nearly impossible for my eyes to resolve the page area from the background (if I rotate the color space I can see it).

I did my best to recreate what you were seeing and adjust accordingly in 808131b. Can you check to see if this helps?

It definitely helps.

A few other columns we shouldn't list: associated_image_count, JPEGTables, NewSubfileType, Photometric, PlanarConfig, Predictor.

Added in c10c83366dd15d4d13e3bf19ca735b2ca3d61b4b


feat(vite-node-miniflare)!: support Vite v6

Mostly copied from https://github.com/hi-ogawa/vite-environment-examples/tree/main/packages/workerd
todo

[x] add vitePluginVirtualIndexHtml
[x] replace custom rpc with service binding for __remixGetCriticalCss
[x] hmr: false mode?
[ ] deal with remix child compiler?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#594  👈
#592
#297
main

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

Join @hi-ogawa and the rest of your teammates on  Graphite

Merging everything to https://github.com/hi-ogawa/vite-plugins/pull/297 since it's messy to juggle 3 PRs


aeproject env --stop doesn't work if node is stopped

aeproject tells me the env is not running. but nginx and compiler are still running. I think we should cover all containers with this command
marc0olo@DESKTOP-B1QLEDL:~/git/aeternity/aepp-sophia-examples$ npm run env:stop

><EMAIL_ADDRESS>env:stop
> aeproject env --stop

===== Env is not running! =====
marc0olo@DESKTOP-B1QLEDL:~/git/aeternity/aepp-sophia-examples$ docker ps
CONTAINER ID   IMAGE                            COMMAND                  CREATED          STATUS                    PORTS                            NAMES
caebe103a12f   nginx:latest                     "/docker-entrypoint.…"   31 minutes ago   Up 31 minutes             80/tcp, <IP_ADDRESS>:3001->3001/tcp   aepp-sophia-examples-aeproject_proxy-1
fb1d9a285e99   aeternity/aesophia_http:latest   "/docker-entrypoint.…"   31 minutes ago   Up 31 minutes (healthy)   <IP_ADDRESS>:3080->3080/tcp           aepp-sophia-examples-aeproject_compiler-1

can you retry aeproject env, aeproject env --stop there is nothing specific to just stopping single containers in the code

can you retry aeproject env, aeproject env --stop there is nothing specific to just stopping single containers in the code

well, yeah if I restart the node with the sequence you mentioned it works. it's just like when the node crashes for some reason aeproject env --stop doesn't work.
starting it up again and then stopping the env works


ci: Aliyun Drive Test failed

https://github.com/apache/opendal/actions/runs/9566562882/job/26372216975
2024-06-18T14:14:17.2955702Z test behavior::test_delete_stream                                      ... ok
2024-06-18T14:14:17.2956375Z
2024-06-18T14:14:17.2956529Z failures:
2024-06-18T14:14:17.2956761Z
2024-06-18T14:14:17.2957113Z ---- behavior::test_list_prefix ----
2024-06-18T14:14:17.2957794Z test panicked: assertion `left == right` failed
2024-06-18T14:14:17.2958781Z   left: 0
2024-06-18T14:14:17.2959188Z  right: 1
2024-06-18T14:14:17.2959426Z
2024-06-18T14:14:17.2959764Z ---- behavior::test_list_empty_dir ----
2024-06-18T14:14:17.2960766Z test panicked: assertion `left == right` failed: only return the dir itself, but found: {}
2024-06-18T14:14:17.2961705Z   left: 0
2024-06-18T14:14:17.2962073Z  right: 1
2024-06-18T14:14:17.2962302Z
2024-06-18T14:14:17.2962596Z ---- behavior::test_list_sub_dir ----
2024-06-18T14:14:17.2964939Z test panicked: dir should be found in list, but only got: [Entry { path: "6717aa09-c611-4047-89b7-7036c6dffa0c/", metadata: Metadata { metakey: FlagSet(Complete | Mode | LastModified), mode: DIR, cache_control: None, content_disposition: None, content_length: None, content_md5: None, content_range: None, content_type: None, etag: None, last_modified: Some(2024-06-18T14:09:45.798Z), version: None } }]
2024-06-18T14:14:17.2966735Z
2024-06-18T14:14:17.2966978Z ---- behavior::test_list_dir_with_file_path ----
2024-06-18T14:14:17.2967433Z test panicked: assertion `left == right` failed
2024-06-18T14:14:17.2967819Z   left: 0
2024-06-18T14:14:17.2968052Z  right: 1
2024-06-18T14:14:17.2968183Z
2024-06-18T14:14:17.2968187Z
2024-06-18T14:14:17.2968283Z failures:
2024-06-18T14:14:17.2968530Z     behavior::test_list_prefix
2024-06-18T14:14:17.2968862Z     behavior::test_list_empty_dir
2024-06-18T14:14:17.2969201Z     behavior::test_list_sub_dir
2024-06-18T14:14:17.2969560Z     behavior::test_list_dir_with_file_path
2024-06-18T14:14:17.2969823Z
2024-06-18T14:14:17.2970207Z test result: FAILED. 110 passed; 4 failed; 0 ignored; 0 measured; 0 filtered out; finished in 274.82s

Reading data at 4K doesn't make sense:
  2024-06-18T15:04:32.588102Z TRACE opendal::services: service=aliyun_drive operation=Reader::read path=07367cad-8f97-4e24-a75c-19c507944a55 read=154902 -> read returns 4096B
    at src/layers/logging.rs:986

  2024-06-18T15:04:32.591711Z TRACE opendal::services: service=aliyun_drive operation=Reader::read path=07367cad-8f97-4e24-a75c-19c507944a55 read=158998 -> read returns 4096B
    at src/layers/logging.rs:986

Maybe aliyun drive is too slow to test from us-east-1. This read is about 1.1KiB/s.

We will also hit errors like:
>                   operator.read(f"{parent}/{path}")
E                   opendal.UnexpectedError: RateLimited (persistent) at stat, context: { service: aliyun_drive, path: random_dir_86b5bcca-098d-4190-9511-2b92cd912490/x/x/y } => 请求过快，请等待 x-retry-after 毫秒后再请求

Hello @yuchanns and @suyanhanx, thank you for your efforts in bringing the Aliyun Drive integration test online. However, it consistently fails on our main branch. The primary issue seems to be that our CI runs in us-east-1, while Aliyun Drive is located in mainland China.
I propose we disable this test until we can resolve the issue. What are your thoughts?

It looks good on #4767 tests. While AliyunDrive severely restricts concurrency access per account. Core-Test, Binding-Python, and Binding-Java consist of three parallel on one account leads to many retries.

How about disabling aliyun_drive test on bindings? cc @suyanhanx

It looks good on #4767 tests. While AliyunDrive severely restricts concurrency access per account. Core-Test, Binding-Python, and Binding-Java consist of three parallel on one account leads to many retries.

How about disabling aliyun_drive test on bindings? cc @suyanhanx

SGTM

SGTM

We can remove aliyun drive from the binding's planner. Would you like to create a PR for this?

Maybe aliyun drive is too slow to test from us-east-1. This read is about 1.1KiB/s.

Aliyun has had a limitation of speed on non-VIP accounts recently.

SGTM

We can remove aliyun drive from the binding's planner. Would you like to create a PR for this?

I'll do this.

I propose optional splittable credentials for binding tests since the limit is per account. Besides, there may be other services encountering such limitations in the future.

I propose optional splittable credentials for binding tests since the limit is per account. Besides, there may be other services encountering such limitations in the future.

Well, it's much harder...
All our services use the same setup and configuration. Allowing splittable credentials for services adds significant complexity to our current CI system.

All our services use the same setup and configuration. Allowing splittable credentials for services adds significant complexity to our current CI system.

A quick glance:

https://github.com/apache/opendal/blob/main/.github/scripts/test_behavior/plan.py
https://github.com/apache/opendal/blob/main/.github/workflows/test_behavior_bin_ofs.yml
https://github.com/apache/opendal/blob/main/.github/actions/test_behavior_core/action.yaml

Good news, the aliyun drive test seems much stable now (passed in previouse twice without retry!)

Yes. Previously before #4766, there was a logical error I misunderstood about list behavior. It is hard to understand why it passed tests, especially on one thread.

Yes. Previously before #4766, there was a logical error I misunderstood about list behavior. It is hard to understand why it passed tests, especially on one thread.

Cool, we can watch this test for sometime. We can keep the binding tests if it's stable for a while.

Opened a PR #4770 that disabled the test aliyun_drive on bindings temporarily.

Thank you all, now aliyun tests work well!


Update vim-plugin-names

Motivation for this change
Add more vim plugins
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

do you mind running the update.py, it should make a commit with changed to the generated.nix

I find it not as easy as I think, since there are many errors like
downloading 'https://github.com/xxx' HTTP Error 429: too many requests, Retrying in 12 seconds...

Seems that my requests are limited by github  :(
I'll try it again latter..

@jonringer found the doc about GITHUB_API_TOKEN, and it's done now :)

looks like someone else ran the script in the mean time, do you mind doing:
git reset HEAD^^ # undo 2 commits
git checkout .       # remove old changes
./pkgs/misc/vim-plugins/update.py --add luochen1990/indent-detector.vim
./pkgs/misc/vim-plugins/update.py --add luochen1990/select-and-search

That should create a git commit history which is able to be merged

@jonringer Thanks for your detailed help very much!  I rebased to staging and re-run the update.py script again, and there is no conflict now.

If you want to take a look at #158880, that's what the git history should look like

@jonringer Thanks, I got it that you want a clean & orthorhombic commit history,   it is done now, would you please have a review again?

you can probably drop the generated commit, looks like someone else merged
git rebase -i is a powerful command which achieves this, I created a small video demonstrating it's use here. A more indepth text tutorial can be found here

@jonringer Done againt, finally no conflict now.


Update README

Update README.rst with descriptions of runner/performance properties and performance lists.
(closes #40)

Coverage remained the same at 98.284% when pulling a2ab2f4633f71e06dde9f1de2eab286c3bfc59eb on readme into 4dab80d335d709a21e304630c5f13bc2448233fe on master.


How to add self-made annoDb?

Dear Tao,
I am wondering how can we add the self-made annoDb for peak annotations? It is common that people do not study on the model species. As I know, specific TxDb can be generated in ChIPseeker, I am not sure if it can be achieved in cisDynet. Look forward to your reply. Thanks.
xiaoli

Here I am using ChIPSeeker to do the peaking annotations.
You can build your own annotation package with AnnotationForge.

Dear Tao,
Sorry to make you confused. What I mean is shown in the below.

I understand what you mean, you can try to do it with the package I mentioned above.

Sorry, that is my mistake, what I mean is the file of gene structure annotation, which is same as  TxDb in ChiPseeker.

The gff file should be the most basic file. If the species you are studying has a genome sequence, it should have its corresponding gff annotation file.
If you have provided the gff file in addAnnotation, you can try to run this step directly.

The gff file should be the most basic file. If the species you are studying has a genome sequence, it should have its corresponding gff annotation file.
If you have provided the gff file in addAnnotation, you can try to run this step directly.

I see, I definitely forget to run these basic codes at the beginning. Is it ok to run addAnnotation right now after finish runing the Snakemake Pipeline already.  Or I have to rerun all codes orderly??

If no error is reported, you can not re-run it.
If cisDynet is indeed helpful for your research, it is recommended to read through it, some of the issues were explained when I wrote the documentation.

If no error is reported, you can not re-run it. If cisDynet is indeed helpful for your research, it is recommended to read through it, some of the issues were explained when I wrote the documentation.

That is true. I will read the documentation carefully when I get any errors. Thank you so much.

Dear Tao,
After running addAnnotation, and building annoDb, I still got the error:
Error in checkGeAnno() :
Necessary Annotation not exist. Please addAnnotation first.
Calls: annoPeaks -> checkGeAnno
Execution halted

Check that your file format matches that of the example and make sure the path is correct.

Check that your file format matches that of the example and make sure the path is correct.

I delete the comment, Sure, thanks


Suppport for setting session attributes in MockMvcRequestSpecification

SpringMockMvc supports adding custom objects to session before sending the request.  This is critical to test Controllers implementing session management. It would be really helpful to add sessionAttribute(name, Object) to MockMvcRequestSpecification interface and link with corresponding feature supported by Spring mock mvc

I already have this fixed to my local clone . Would be more than happy to check this in to master branch.

It would be great if you want to provide a pull request for this.

I created a pull request with my fix. https://github.com/jayway/rest-assured/pull/673

I did some changes to make session attributes behave the same way as the other parameters/attributes. Thanks for your help-

You are welcome. It would be nice if we could read objects (eg: userInfo)
from session after a get or post request. We need to inject userInfo into
session (session.sessionAttr(userInfo)  ) before invoking the next request.
Do we support this feature as of now ? If not, would you like to open
another issue ?
On Tue, Apr 12, 2016 at 10:21 PM, Johan Haleby<EMAIL_ADDRESS>wrote:

I did some changes to make session attributes behave the same way as the
other parameters/attributes. Thanks for your help-
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/jayway/rest-assured/issues/671#issuecomment-209231951

Perhaps you vould open another issue so that we can discuss it there?

Sure. I can open another issue if springMvc supports ability to retrieve
objects from session.
On Tue, Apr 12, 2016 at 11:00 PM, Johan Haleby<EMAIL_ADDRESS>wrote:

Perhaps you vould open another issue so that we can discuss it there?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/jayway/rest-assured/issues/671#issuecomment-209241398


Ensure there are no errors in case columns are missing in database

Ensure there are no errors in case columns are missing in database


community: Allow passing a pg connection to PostgresChatMessageHistory

Enable passing a Postgresql connection to the PostgresChatMessageHistory class. To enhance production efficiency, it can be resource-intensive to open and close multiple Postgresql connections each time the class is instantiated. A more efficient approach would be to reuse the same connection without having to close it.

The improvement is already implemented in the new package: "This class is deprecated and will be removed in a future version. "
"You can swap to using the PostgresChatMessageHistory"
" implementation in langchain_postgres. "
"Please do not submit further PRs to this class."
"See https://github.com/langchain-ai/langchain-postgres"


Consider supporting -d for use as difftool

Done as of v2.0.0.
[diff]
    tool = nvr
[difftool "nvr"]
    cmd = nvr -s -d $LOCAL $REMOTE
[merge]
    tool = nvr
[mergetool "nvr"]
    cmd = nvr -s -d $LOCAL $BASE $REMOTE $MERGED -c 'wincmd J | wincmd ='

Documented here: https://github.com/mhinz/neovim-remote#typical-use-cases


Provide support for the latest API level

Hello,
We are currently using your library in one of our application. Actually we need a favour from your side. According to the Google Play Policy, all apps have to provide support for at least API level 26 which is not satisfied in your case. We are targeting API level 28. So can you please provide us support for API level 28 in your current repository?

I'm not sure what support you are missing, but Happy Halloween! #100

Hello @Will5
Please refer the official Android docs. We need to make sure that all the libraries are having at least targetSdkVersion 26 but we are targeting targetSdkVersion 28. Thus, we require your support for the same.

Hello, I have realized a project fork and updated the depreciated parts, if you want to have a look...
https://github.com/BrasileiroGamer/android-autofittextview

Hi @ebghrimtech @Will5  , how you guys doing?
I ported this library with updated dependencies and configurations, also moved out from JCenter do use Jitpack.io:
https://github.com/thiago-you/autofittextview

Move from JCenter to Jitpack.io
Migrate do Androidx libraries
Drop jetifier support
Update dependencies and libraries
Update configurations
Kotlin compatibility

Check it out!


Rajarju/text changes

Description
Text change
Related Issue
Fix: #122

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@shazron  I believe the docs are generated/updated automatically ?


Test entity factory logic

Test needed to be added for the EntityFactory logic.

Yes I know the migration needs some additional TLC. I'll remove the migration from this PR and I will open a new PR for this so this could be merged back in a new release. It was however easier to create the migration now so during a review someone knows why it's there and it could be easily functional tested.
https://github.com/OpenConext/OpenConext-engineblock/pull/782

Lookin' good. Please rebase the final changes from upstream into your branch, and please solidify the PR description. It's not fully reflecting the changes you applied in this PR. Other than that, merge at your pleasure!


www/caddy: Fix reload/stop of caddy being infinite when websocket streams of clients are open

Fixes: https://github.com/opnsense/plugins/issues/3929
This one can cause a lot of pain. It took almost two months to track this down. I had this issue too and didn't understand for quite a while why it was happening.
I had a chat with Francis Lavoie (one of the Caddy contributers and devs) and he pointed me to the way Caddy handles open connections and streams. (but it was not straight forward that it was exactly this option at first)
Caddy, by default, tries to keep all connections and streams open, and waits for clients to close them gracefully. This means, it can wait indefinitely when a reload, or stop action happens. Which makes Caddy seem frozen, and the apply in the GUI hang forever.
https://caddyserver.com/docs/caddyfile/options#grace-period

@fichtner If this can still make it into the hotfix, I would be grateful. It can cause some real pain and took a long time to track down.

Merged, thanks!


Could not able to perform npm install

Below are the files I have
`conf.ts
import {Config} from 'protractor';

export let config: Config = {
  framework: 'jasmine',
  capabilities: {
    browserName: 'chrome'
  },
  specs: [ 'spec.js' ],
  seleniumAddress: 'http://localhost:4444/wd/hub',

  // You could set no globals to true to avoid jQuery '$' and protractor '$'
  // collisions on the global namespace.
  noGlobals: true
};`

`package.json
{
  "name": "example-typescript",
  "version": "1.0.0",
  "description": "a typescript example",
  "author": "",
  "license": "MIT",
  "scripts": {
    "tsc": "tsc",
    "pretest": "npm run tsc",
    "test": "C:/Users/u0146751/AppData/Roaming/npm/node_modules/protractor/bin/protractor tmp/conf.js",
   "debug": "node --inspect --debug-brk C:/Users/u0146751/AppData/Roaming/npm/node_modules/protractor/bin/protractor asyncAwait/conf.js"
  },
  "dependencies": {
    "@types/jasmine": "2.5.41",
    "@types/jasminewd2": "^2.0.0",
    "jasmine": "^2.4.1",
    "protractor": "C:/Users/u0146751/AppData/Roaming/npm/node_modules/protractor/bin/protractor",
    "typescript": "~2.0.0"
  },
  "devDependencies": {
    "@types/jasminewd2": "^2.0.0",
    "ts-node": "^3.0.2"
  }
}`

`spec.ts
import {browser, element, by, By, $, $$, ExpectedConditions} from 'protractor';

describe('protractor with typescript typings', () => {
  beforeEach(() => {
    browser.get('http://www.angularjs.org');
  });

  it('should greet the named user', () => {
    element(by.model('yourName')).sendKeys('Julie');
    let greeting = element(by.binding('yourName'));
    expect(greeting.getText()).toEqual('Hello Julie!');
  });

  it('should list todos', function() {
    let todoList = element.all(by.repeater('todo in todoList.todos'));
    expect(todoList.count()).toEqual(2);
    expect(todoList.get(1).getText()).toEqual('build an angular app');
  });
});`

`tsconfig.json
{
  "compilerOptions": {
    "target": "es6",
    "module": "commonjs",
    "moduleResolution": "node",
    "inlineSourceMap": true,
    "declaration": false,
    "noImplicitAny": false,
    "outDir": "tmp"
  },
  "exclude": [
    "node_modules",
    "asyncAwait",
    "plugins.ts"
  ]
}`

When I am performing npm install, it throws error
C:\MyFiles\NewTechonologies\Protractor\TypeScript\Test>npm install
npm ERR! not a package C:\Users\u0146751\AppData\Roaming\npm\node_modules\protractor\bin\protractor
npm ERR! addLocal Could not install C:\Users\u0146751\AppData\Roaming\npm\node_modules\protractor\bin\protractor
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "
install"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! path C:\Users\u0146751\AppData\Local\Temp\npm-8952-eac08724\unpack-b2acb3b1\package.json
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\u0146751\AppData\Local\Temp\npm-8952-eac08724\unpac
k-b2acb3b1\package.json'
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\u0146751\AppData\Local\Temp\npm-8952-eac08724\unpac
k-b2acb3b1\package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     C:\MyFiles\NewTechonologies\Protractor\TypeScript\Test\npm-debug.log

I have installed protractor, npm, jasmine globaly
Please guide if there is any setup needs to be done.

If you look at the stack trace you will see
not a package C:\Users\u0146751\AppData\Roaming\npm\node_modules\protractor\bin\protractor

This is because your package.json includes this as a dependency:
"protractor": "C:/Users/u0146751/AppData/Roaming/npm/node_modules/protractor/bin/protractor",

This is an invalid dependency declaration, you are saying that the module protractor exists at a path, but that path is actually just the protractor executable.
Please read the NPM documentation on declaring and installing dependencies. If you have additional issues please ask a question on StackOverflow. Thanks!

When I am running npm test, getting error as
import {browser, element, by, By, $, $$, ExpectedConditions} from 'protractor';
^^^^^^
SyntaxError: Unexpected token import
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    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.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at C:\MyFiles\NewTechonologies\Protractor\TypeScript\Test\node_modules\jasmine\lib\jasmine.js:93:5
[19:26:29] E/launcher - Process exited with error code 100
npm ERR! Test failed.  See above for more details.

May I know how to get rid of this error.

Please ask unrelated usage or debugging questions on stackoverflow. I'm going to close this thread for now. Thanks!


"data-aos-delay" not working when using animate.css with aos.js and not working with all zoom related animate.css animation.

This is:

Bug
Question

Specifications

AOS version:3.0.0 beta.6
OS: Android
Browser: Google Chrome

Expected Behavior

I want to add animation delay with "data-aos-delay" but it not working when I using animate.css while working it fine with default animation (aos.css). And another problem is all zoom related animate.css animation appearing and immediately disappeared while with wow.js it working properly.
Actual Behavior

When I using animate.css with aos.js then data-aos-delay does not work. While with default animation aos.css working it fine.
I want aos.js work fine as like wow.js especially with zoom related animate.css animations. I want to use aos.js instead wow.js because wow.js does not support reanimation while aos.js support it but it has some problems with animate.css. So please improve it.
Steps to Reproduce the Problem

I created a codepen on this problem.

"data-aos-delay" not working with animate.css.
zoom related animation of animate.css does not animate as like real animation.

Detailed Description

Codepen links below:
AOS with Animate.css not working "data-aos-delay".
AOS default working fine "data-aos-delay" with aos.css.
Possible Solution

Did you find a solution?


melody-parser does not like dynamic elements

I know this isn't necessarily related to this project, but attempting something like this
{% set elementType = 'button' %}
<{{elementType}}>I'm a button</{{elementType}}>

throws the following error:
Error: ERROR: Expected element start
(code with arrows)

Expected an element to start

This is becoming a blocker for my team because we need dynamic elements and want to run prettier as a pre-commit hook. Is there any more info I can provide to help?

We use a custom Twig tag as a workaround for anyone interested:
{# Twig template #}
{% set tag = 'p' %}
{% html_element is tag with { id: 'lorem-ipsum' } %}
  Lorem ipsum
{% end_html_element %}

{# HTML output #}
<p id="lorem-ipsum">
  Lorem ipsum
</p>

Thanks for the workaround @titouanmathis - we need to use vanilla Twig in our codebase and ended up implementing this from scratch, and ignoring only this file from Prettier
html_element.twig
    {{content}}
</{{ tag }}>

.prettierignore
path/to/twig/html_element.twig


BUG: fix codes for some terms in v2 terminology

Follow up on #38
It is easier to see the terms that were changed in this spreadsheet: https://docs.google.com/spreadsheets/d/1aeTGUjZJNxw6fd2Mu0L32m8KP2suky5iboQ8M4ocfqM/edit#gid=844414326 (sheet 1, highlighted).
Note that the mapping now contains 3 new columns:

AnatomicRegionModifierSequence.CodingSchemeDesignator
AnatomicRegionModifierSequence.CodeValue
AnatomicRegionModifierSequence.CodeMeaning

It will be important to make sure those propagate when mapping is applied.

Thanks a lot @fedorov this is great! I'll try to update the code today to use the anatomic region modifier columns as well.

You are right - I missed it! It should be split to use the modifier. Will you fix it or should I send a PR?

I'll fix it, just write me the correct code for "inferior" modifier. Thank you!

@fedorov Sorry, a couple of more questions - just for my own education and so that I can give good advice to others.

Vena cava

What is the difference between the dedicated code ("inferior vena cava") and the generic+modifier code ("vena cava" + "inferior")?
Are they equivalent?
Is one of them a preferred code for medical image segmentation?
Is it documented somewhere?
Is there a mapping table that maps less preferred codes to equivalent more preferred codes?
These all are quite important because if there were several equivalent codes for the same thing even in the same coding scheme then that would kind of defeat the purpose of using a standard terminologies. It would not make standard terminologies entirely useless, but we would need some software solutions to deal with the resulting redundancies/inconsistencies.

Costal cartilage

Do you know the difference between these?

50016007 Structure of costal cartilage
244703004 Entire costal cartilage

Why 244703004 (which is the child of 50016007) is better?
Is it documented somewhere that one is appropriate for image segmentation and other is not?
DICOM terminology in Slicer uses 50016007. Should we change that, too (and all similar cases when the "structure of..." code is used instead of "entire..." code)?

Actually, I am not sure anymore which approach is preferred. I thought the logic is always to factor our those modifiers, as documented in but the DICOM table here does not: https://dicom.nema.org/medical/dicom/current/output/chtml/part16/sect_CID_6117.html. At the same time, it did happen in the past that code selection in DICOM was not correct. I am waiting to hear back from @dclunie about this.
Now that I look again, I see there may be some more refinements. I will send another PR. I am sorry for not doing it right on the first try...

Thanks a lot, I'm looking forward to the new PR then.
The links you provided are very useful, but I wouldn't have even thought that I could find such useful notes in the DICOM standard. It would help with the adoption of terminologies if there was a simple tutorial that would explain to developers the general process and tips&tricks for determining the correct code, heavily referencing the DICOM standard.

Wrt. codes in CID 6117, these were originally introduced in the standard for use in an SR template (TID 4104 for Chest CAD, Row 2) where the anatomy itself was a potential modifier of a finding, and so there was not an option for post-coordinating these (a single concept was needed to fully convey the location). In a segmentation context, we have more flexibility, so I would not read too much into these.
In general, the subject of pre-coordination vs. post-coordination has been the subject of religious wars, and we try to take a pragmatic path. In particular, we do not used so-called "post-coordinated expressions" in SNOMED CT, if for no other reasons than that creates an unbounded space for matching and is SNOMED-specific when we use other coding schemes. Any post-coordination in DICOM has to be done with explicit modifier attributes or content items. There is a body of literature on the theoretical and practical aspects of this if you want some references to research; this is a good general start and this and this are SNOMED specific.
There is no right or wrong answer for many of these choices, but generally for a particular application, I try to maintain internal consistency within the sub-set of concepts selected for that use case (within reason).
As for entire vs. structure of, if you want to go down this rabbit hole, search for the philosophical topic of "mereology" (the study of wholes vs. parts and their relations). We are talking Plato/Aristotle here. The SNOMED folks believe in that religion, other ontologies don't. Generally in imaging we are trying to say "this is in the liver" not "this is the entire liver, no more and no less", and we are not trying to distinguish when we are doing one or the other or relate the two (one notable exception in DICOM being "entire body", for which I or someone else dubiously used the "entire body" SNOMED code, even though we know, e.g., a whole body PET doesn't always include the toes, but since the word "entire" or "whole" was used in the code meaning ... in short we almost always use "structure of" and almost never "entire" and this has been documented in the standard for a while now and updates have been made to assure this.
If I could have written a "simple" tutorial about this, I probably would have, since Andrey has been trying to convince me to do that since the beginning of the QIICR project. At that time, he made a nice Searching for codes outside DICOM page, but that doesn't really cover the subtlety of anatomy modifiers. We were also working at the time on brain tumor lesion types as discussed in the CP 1849 do I described more of my rational at the time, but I don't think Andrey was impressed.

PS. If you think selecting codes is hard, try defining them - see, for example, this diatribe on what the "abdomen" is in SNOMED CT.
This paper is actually relevant in the general context of segmenting the body (but AFAIK you are not defining regions, only parts such as organs within these regions, so that probably doesn't apply to your code table for now).

Since you mentioned SVC and IVC earlier, I wrote to Andrey earlier:
"Since these are such distinct structures In their own region, I would probably pre-coordinate these (not use a superior/inferior modifier), just as, for example, I would almost always pre-coordinate left/right ventricle, etc. in the heart."
But reiterate that this is a judgment call and there is no correct answer.

Likewise, if you were segmentating "aorta" into its distinct parts (which AFAIK you are not), I would probably recommend pre-coordinate "ascending aorta", "arch of aorta", "descending aorta" (or combine them as "thoracic aorta") and distinguish them from "abdominal aorta", rather than attempting to use modifiers.

in short we almost always use "structure of" and almost never "entire"

@dclunie for the metatarsal, there is no code that specifically starts from "structure of". There's "Entire" one (which we should not use): http://snomed.info/id/302532000, and then there is the parent of it that is "Metatarsal bone structure (body structure)" http://snomed.info/id/53884002. We should use the latter, correct? If yes, would it be correct to define a rule such as "if you see code that starts from "entire", use its parent instead, even if it does not start with "the structure of""?

It is quite common for SNOMED concepts that are structures not to have a name that begins with 'structure of" but rather to end with 'structure" or some other pattern, as you have discovered.
Working back from "entire" is a good idea, but should not be used blindly - read the FSN and synonyms of the parent and understand them and see if they makes sense, also exploring siblings and more parents if necessary.
Cross-referencing to UMLS is also a good idea (enter the code at the UMLS site  and see what it maps to in other schemes, or indeed start from there). E.g., see metatarsal in UMLS. And/or metatarsal in Bioportal.
PS. Yes, use SCT:53884002 if you want to refer to any one of those bones, and not a particular metatarsal, and not the region of the foot that contains the metatarsals, or the set of all of the metatarsals, etc.
Note that in DICOM PS3.16 we refer to the metatarsus as an anatomic region, so use SCT:280711000 "Structure of region of metatarsal (body structure)" for that (not that we wouldn't use 53884002 if/when we wanted to refer to one of the bones themselves). We are probably not terribly consistent about that, and there are not corresponding "region" concepts for every anatomic structure in SNOMED CT AFAIK.

Thank you for all the very interesting information. I'm learning a lot!


Preload doesn't work on Docker <IP_ADDRESS> [macOS Mojave]

Hi,
The preload function isn't able to start docker image on the latest stable Docker <IP_ADDRESS>, on macOS Mojave 10.14.1.
It returns:
Error starting daemon: error initializing graphdriver: driver not supported

Which seems to be an old Docker issue. I reverted to an older version of Docker and everything works like a charm (1.13.1 (15353))
To debug I also tried updating all components, which didn't resolve the issue. I updated Node (v11.4.0) and npm (6.4.1) and Belana-cli afterwards (9.4.0) hoping to get all new versions, there are no updates yet for Docker.
Full output
Building Docker preloader image. [========================] 100%

/ Creating preloader container
/ Starting preloader container
- Reading image information
1: Step 1/7 : FROM docker:17.10.0-ce-dind
 ---> 9769e0f3f9cb
Step 2/7 : RUN apk update && apk add --no-cache python3 parted btrfs-progs docker util-linux sfdisk file coreutils sgdisk
 ---> Using cache
 ---> 1ba613600810
Step 3/7 : COPY ./requirements.txt /tmp/
 ---> Using cache
 ---> 41124aaefbfb
Step 4/7 : RUN pip3 install -r /tmp/requirements.txt
 ---> Using cache
 ---> ff360f39d233
Step 5/7 : COPY ./src /usr/src/app
 ---> Using cache
 ---> 497d14a8b763
Step 6/7 : WORKDIR /usr/src/app
 ---> Using cache
 ---> 30466b3a1f39
Step 7/7 : CMD ["python3", "/usr/src/app/preload.py"]
 ---> Using cache
 ---><PHONE_NUMBER>e9
Successfully built<PHONE_NUMBER>e9
Successfully tagged balena/balena-preload:latest
Waiting for Docker to start...
Exception in thread background thread for pid 208:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3.6/site-packages/sh.py", line 1540, in wrap
    fn(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/sh.py", line 2459, in background_thread
    handle_exit_code(exit_code)
  File "/usr/lib/python3.6/site-packages/sh.py", line 2157, in fn
    return self.command.handle_command_exit_code(exit_code)
  File "/usr/lib/python3.6/site-packages/sh.py", line 815, in handle_command_exit_code
    raise exc
sh.ErrorReturnCode_1:

  RAN: /usr/local/bin/dockerd --storage-driver=aufs --data-root=/tmp/tmppe4ea8sb/docker --host=tcp://<IP_ADDRESS>:56017

  STDOUT:

  STDERR:
time="2018-12-13T09:49:44.170731602Z" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting --tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]"
time="2018-12-13T09:49:44.173455723Z" level=info msg="libcontainerd: new containerd process, pid: 227"
Error starting daemon: error initializing graphdriver: driver not supported

Traceback (most recent call last):
  File "/usr/src/app/preload.py", line 825, in <module>
    result = method(**data.get("parameters", {}))
  File "/usr/src/app/preload.py", line 785, in get_image_info
    images, supervisor_version = get_images_and_supervisor_version()
  File "/usr/src/app/preload.py", line 668, in get_images_and_supervisor_version
    return _get_images_and_supervisor_version(inner_image_path)
  File "/usr/src/app/preload.py", line 644, in _get_images_and_supervisor_version
    with docker_context_manager(driver, mountpoint):
  File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/usr/src/app/preload.py", line 511, in docker_context_manager
    running_dockerd = start_docker_daemon(storage_driver, docker_dir)
  File "/usr/src/app/preload.py", line 480, in start_docker_daemon
    running_dockerd.wait()
  File "/usr/lib/python3.6/site-packages/sh.py", line 792, in wait
    self.handle_command_exit_code(exit_code)
  File "/usr/lib/python3.6/site-packages/sh.py", line 815, in handle_command_exit_code
    raise exc
sh.ErrorReturnCode_1:

  RAN: /usr/local/bin/dockerd --storage-driver=aufs --data-root=/tmp/tmppe4ea8sb/docker --host=tcp://<IP_ADDRESS>:56017

  STDOUT:

  STDERR:
time="2018-12-13T09:49:44.170731602Z" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting --tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]"
time="2018-12-13T09:49:44.173455723Z" level=info msg="libcontainerd: new containerd process, pid: 227"
Error starting daemon: error initializing graphdriver: driver not supported

If you need help, don't hesitate in contacting us at:

  GitHub: https://github.com/balena-io/balena-cli/issues/new
  Forums: https://forums.balena.io

 Front conversations

Any updates on this? Or is the only solution to use an old version of Docker?

Does not relate to macOS only, got the same problem on Linux with docker v19.03.5-ce. Any updates on this?


Exception unreal4u\TelegramAPI\Exceptions\ClientException caught, message: Bad Request: chat not found

Hello
The get-chat-member.php example throws the above exception "Exception unreal4u\TelegramAPI\Exceptions\ClientException caught, message: Bad Request: chat not found"
My settings are correct and I am able to send messages directly to the value defined for "$A_USER_CHAT_ID": Direct messages are sent like below (after the usual includes for the autoload and the config files)
Note: i use variables with $ everywhere, that's the only difference between the example and my code

use \unreal4u\TelegramAPI\HttpClientRequestHandler;
use \unreal4u\TelegramAPI\TgLog;
use \unreal4u\TelegramAPI\Telegram\Methods\SendMessage;

$loop = \React\EventLoop\Factory::create();
$handler = new HttpClientRequestHandler($loop);
$tgLog = new TgLog($MyBotToken, $handler);

$sendMessage = new SendMessage();
$sendMessage->chat_id = $A_USER_CHAT_ID;
$sendMessage->text = 'Hello worlddddddddddd 222222!';

$tgLog->performApiRequest($sendMessage);
$loop->run();

I used the username as found in the mobile app/settings/username . I tried both with "myname" as well as "@myname"  (of course, without the quotes and with the actual name in settings instead of myname)
Any help/ thoughts will be welcome

Hi!
A user chat id is normally a number, which you will get once you start a chat with your bot in the form of an update (either retrievable via getUpdates or via Webhook). You can also send a message to the bot and this will appear as a new message which will include the user chat id as well.
This number is the one you must use: a bot can not initiate a conversation with a user.
I hope this information can help you further. Otherwise, you can always check out the wiki for some more documentation ( https://github.com/unreal4u/telegram-api/wiki/Getting-updates-via-Webhook ) or ask via our group: t.me/phpbotapi
Thanks!

Hi
Thanks for the response.
Yes, I do understand. I use the webhook.
In the webhook, for example, it included the following:
        [date] =><PHONE_NUMBER>
        [chat] => unreal4u\TelegramAPI\Telegram\Types\Chat Object
            (
                [id] => 111111111

I tried with "A_USER_CHAT_ID" set to the above (replaced actual number with a dummy number) and A_USER_ID set to both "username" as well as "@username".
Both resulted in the same error on examples get-chat-member.php and on get-user-profile-photos.php examples.
However, the example "send-message-with-keyboard-options.php" works perfectly fine with the same settings in the config
Any ideas please? THanks


QOL Features

these are obviously not necessity, but these two small things would make the experience so much better.
1.Dark Title bar Implementation.
https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/apply-windows-themes#enable-a-dark-mode-title-bar-for-win32-applications

Open F3D Window in Last closed position or Open in Center of Current Monitor.

1 should be fairly easy to implement, but it has to be done in VTK.
2 would be interesting and that's not the first time someone ask for it.

Shouldn't 2 be handled by the window manager already ? It seems implementable but i'd rather not if window manager provide the feature.

Definitely! We're always open to new ideas :)
Please share @Da3n0n

well i don't want to just keep pumping you with features and make it overwhelming, but here's a few more off the top of the head Add View options to the viewport for orthographic views.
drag and drop hdri into viewport to load it in the viewport would be really amazing or load HDRI option in the viewport would be nice either.
i will jsut leave these for now but i cna keep going
I love this project and  even if yous dony implement these features will be still using f3d  and supporting it .if I had more experience I would go ahead and try implement these features myself.

drag and drop hdri into viewport to load it in the viewport

Done in 2.1.0 release

Rework this issue into the keep window on last closed position

Amazing Stuff Guys Really well down such a Fast Implementation of the HDRI Drag and Drop feature  Honestly Amazing i Love this Project So much.


add westlake mirror

Great app!
https://mirrors.westlake.edu.cn/pypi/simple/
Could this mirror be added?

Sure, why don't you submit a PR?
Because all the mirror sources are defined in the file mirrors.py, it's easy to modify them
and you're welcome to be the app's contributors!


Track upstream dub issue 825 / PR 1002

This issue / PR are about globing in sourceFiles, which as explained here would be quite sweet for us.

This has been merged


Time stamp showing UTC instead of local timezone

First of all, thanks for publishing this python code. It is a great improvement over the performance of MotioneyeOS which I tried. The delay in the video stream is half of MotioneyeOS.
The timestamp in the video stream is showing UTC instead of local timezone. I changed the following code in picam2.py make it show my local timezone:
timestamp = time.strftime(self._fmt)  => timestamp = dt.now(tz=ZoneInfo("Asia/Singapore")).strftime(self._fmt)
Needed to import the following as well:
from zoneinfo import ZoneInfo
I hope the above is useful for other folks.

First of all, thanks for publishing this python code. It is a great improvement over the performance of MotioneyeOS which I tried. The delay in the video stream is half of MotioneyeOS.

Thank you for feedback.

The timestamp in the video stream is showing UTC instead of local timezone. I changed the following code in picam2.py make it show my local timezone:

Ok. What do you get if you open python console and entering:
import time
print (time.tzname)

I don't get UTC , but I'm not sure if strftime depends on configured system timezone.
On the other hand there is the '%z' format parameter:
Time zone offset indicating a positive or negative time difference from UTC/GMT of the form +HHMM or -HHMM, where H represents decimal hour digits and M represents decimal minute digits [-23:59, +23:59].

Thanks for your response. I didn't setup my system time in my fresh Raspberry Pi OS SD card to my own timezone. That explain why I had to add additional lines of code for the time stamp to show the correct time zone.

import time
print (time.tzname)
('GMT', 'BST')


Section for "Why Citus?"

Why are we implementing it? (sales eng)
The first page in our docs is "What is Citus." We should add a section to answer the more fundamental question of Why.
What are the typical use cases?
Communication goals (e.g. detailed howto vs orientation)
Good locations for content in docs structure
How does this work? (devs)
Example sql
Corner cases, gotchas
Are there relevant blog posts or outside documentation about the concept/feature?
Check out content in https://www.citusdata.com/use-cases
Link to relevant commits and regression tests if applicable

Also: When to Use Citus / Considerations -> Consider linking to www.citusdata.com/use-cases

@begriffs / @sumedhpathak -- Do we have a bit more background on this pull request? I'm just trying to better understand the historical context to it.
Did we want to have a separate section on "Why Citus?"
This issue is related to #791.


how to change to male voice

need to know how to change male voice?

@karthikindia this line handles the TTS. We use slt voice and these are the available voices of flite: http://www.festvox.org/flite/packed/flite-2.0/voices/
Feel free to add a command line argument to Dragonfire to change her voice and send a pull request. Any contributions are welcomed.

thanks


update Romanian language

It seems you had 2 things not proper - Line 5 and line 15. I have updated to reflect proper and constant spelling with ț everywhere it needs to.

Hello @JohnMica
Please use Crowdin to make the changes:
https://crowdin.com/project/grav-core/ro#
Thanks

Closing, core and admin translations are managed in Crowdin as @MATsxm pointed out 👍

i have done the translation on Crowdin however, it seems that even in the latest beta release the 2 errors are present, that is the only reason I have opened this issue in the first place - to correct these 2 errors until the full translation will be approved/voted.


TimePlot chart crashes the browser

Running this notebook crashes the browser:
https://pub.beakernotebook.com/#/publications/5646273b-fe04-4817-bcdf-0160687dbd84

https://github.com/twosigma/beaker-notebook/pull/2950


Migration: MS SQL alterColumnt with ->null() syntax error

What steps will reproduce the problem?
In migration if I do:
$this->alterColumn('table','column',$this->integer()->null());
What is the expected result?
IMHO the column should be created without error with:
ALTER TABLE [table] ALTER COLUMN [column] integer NULL
What do you get instead?
SYNTAX ERROR:
ALTER TABLE [table] ALTER COLUMN [column] integer NULL DEFAULT NULL
Additional info
The DEFAULT NULL should not be there!!!
Might be related to #12077 and #11158

I temporarily solve this by doing:
$this->alterColumn('table','column',$this->integer().' NULL');

which DBMS is that? MySQL?

MSSQL as said in the title.

I also have this issue on MySQL:
access_token varchar(100) NULL DEFAULT NULL


When switching nodes, the relay repeats packets in its queue that have been already sent by a previous node

I found this bug when switching between my tlora (connected via serial & network) and my rooftop rak (connected via ble).  If I connect the relay to my tlora and use the relay as I do normally, then change nodes and connect to the rooftop rak, the rak will have stored packets in its queue that it will then send to the mapped matrix channels as diplicates.
I do like that it sends packets that it received while disconnected (for example, as a result of a temporary network issue), but we need to check the Matrix room to see if the same packets have been sent previously, either by itself or by another node.

This has since been resolved.


Improve the COLLECTIVE_MEMBER_CREATED Webhook Message

This is related to the comment; https://github.com/opencollective/opencollective/issues/6482#issuecomment-1471551668 by, @josesimoes

Hi,
Since my comment on the PR opencollective/opencollective-api#8608 hasn't had any reply I'm re-posting it here.
Thank you for the quick fix. However I have a concern: this hook used to generate a more meaningful message which included the contribution amount. This is something that's pertinent to the announcement of a new contributor joining the open collective. If there is no interface to customize the message, I suggest this is added to the default message.
For reference this is how it used to look like:

Which later evolved to:

Just today we've received a new contribution on the collective and this is how it looks on Discord:
Any chance you can improve this please?

I am okay with bringing back the older message if there's no objection to this. However I think we need to do this conditionally as creating a new member on an Event might not involve a contribution (free ticket for example).
cc: @Betree

@SudharakaP understood and yes, that makes sense.
Maybe it's simple just adding a new event instead. Which would be triggered when a new contribution/contributor occurs...


README readability improvements

I got an opportunity to use a UR hardware robot for the first time in ROS2  :+1:   These are some README improvements that would have helped me figure it out faster, I think.

Add a Network Settings section with a good default setup.
The URCap program is not located in the Resources folder, so delete that bit.
Describe how to modify Host IP of the external_control URCap.
Prompt the user to launch the URCap after the appropriate launch files. It's very easy to forget.

Fixes #182

Codecov Report

Merging #184 (7623495) into main (1b121b7) will decrease coverage by 0.13%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##            main    #184      +/-   ##
========================================
- Coverage   3.59%   3.45%   -0.14%
========================================
  Files         13      13
  Lines        947     983      +36
  Branches     152     152
========================================
  Hits          34      34
- Misses       843     879      +36
  Partials      70      70

Flag
Coverage Δ

unittests
3.45% <0.00%> (-0.14%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ur_controllers/force_torque_sensor_broadcaster.hpp
0.00% <ø> (ø)

...controllers/scaled_joint_trajectory_controller.hpp
0.00% <0.00%> (ø)

...ontrollers/src/force_torque_sensor_broadcaster.cpp
0.00% <0.00%> (ø)

ur_controllers/src/gpio_controller.cpp
0.00% <0.00%> (ø)

...rollers/src/scaled_joint_trajectory_controller.cpp
0.00% <0.00%> (ø)

...ontrollers/src/speed_scaling_state_broadcaster.cpp
0.00% <0.00%> (ø)

...ver/include/ur_robot_driver/hardware_interface.hpp
0.00% <ø> (ø)

ur_robot_driver/src/hardware_interface.cpp
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

@AndyZe I had some problems making a PR for this PR. So I have send you an email.

@urrsk Received and updated. Thanks


Removing specific beta4 build and fixing assembly loading issue on vnext

Prevents error for people who don't have 11566.

Probably. I didn't even know we had a DNX branch. I guess the CI build hasn't been updated to be able to build for DNX.

We do (obviously) but it is very much a WIP. Let's ping @jchannon on this one and get it merged or closed.

Thanks!!