man pages not available

In our workshop, we suggest e.g. man ogrinfo to get help for ogrinfo. On my laptop, I have that utility installed via conda and I do have a man page. On CryoCloud, the utility is installed the same way, but lacks a man page. I'm also seeing missing man pages for GNU coreutils:
(notebook) jovyan@jupyter-mattf-2dnsidc:~$ man ogrinfo
No manual entry for ogrinfo
See 'man 7 undocumented' for help when manual pages are not available.
(notebook) jovyan@jupyter-mattf-2dnsidc:~$ man find
No manual entry for find
See 'man 7 undocumented' for help when manual pages are not available.
(notebook) jovyan@jupyter-mattf-2dnsidc:~$ man  grep
No manual entry for grep
See 'man 7 undocumented' for help when manual pages are not available.

I'm trying to use the Dockerfile escape hatch to work on a fix for this. I'm hoping I can use mandb to initialize the database cache. But I'm struggling with how to convert an existing repo2docker project to use a Dockerfile. I opened a PR for some doc changes, but after making some progress I'm having more issues (commented on the PR): https://github.com/jupyterhub/repo2docker/pull/1271

Forgot to mention, running mandb as non-root doesn't seem to be having any effect:
(notebook) jovyan@jupyter-mattf-2dnsidc:~/shared-readwrite/QGreenland$ mandb
\Processing manual pages under /srv/conda/envs/notebook/man...
Updating index cache for path `/srv/conda/envs/notebook/man/man3'. Wait...mandb: warning: /srv/conda/envs/notebook/man/man3/pcre2demo.3: whatis parse for pcre2demo(3) failed
Updating index cache for path `/srv/conda/envs/notebook/man/man7'. Wait...done.
Checking for stray cats under /srv/conda/envs/notebook/man...
Processing manual pages under /srv/conda/envs/notebook/man/cat1...
Processing manual pages under /srv/conda/envs/notebook/man/cat3...
Processing manual pages under /srv/conda/envs/notebook/man/cat5...
Processing manual pages under /srv/conda/envs/notebook/man/cat7...
Processing manual pages under /srv/conda/man...
Updating index cache for path `/srv/conda/man/man1'. Wait...done.
Checking for stray cats under /srv/conda/man...
Processing manual pages under /srv/conda/man/cat1...
5 man subdirectories contained newer manual pages.
1094 manual pages were added.
0 stray cats were added.
0 old database entries were purged.
(notebook) jovyan@jupyter-mattf-2dnsidc:~/shared-readwrite/QGreenland$ man ogrinfo
No manual entry for ogrinfo
See 'man 7 undocumented' for help when manual pages are not available.
(notebook) jovyan@jupyter-mattf-2dnsidc:~/shared-readwrite/QGreenland$ man find
No manual entry for find
See 'man 7 undocumented' for help when manual pages are not available.

https://github.com/jupyterhub/repo2docker/issues/700

I think the --appendix argument could possibly solve this. Testing...

USER root
RUN yes | unminimize

..in the appendix instructions is enabling man pages for apt-installed programs, but not conda-installed programs.

RUN mandb didn't make man gdalinfo work :(

conda remove gdal && conda install gdal did not yield a working man page with the appendix above. Something's still "blocking" conda's man pages from being indexed. I'm currently out of ideas :)

Sounds like a path issue, since conda is installing to a different location than apt... a bit hard to address for things outside of the docker build since there's no sudo access to force the database to update. Might be able to fix it with environmental variables-- try MANPATH=$CONDA_PREFIX/share/man? (see this issue ) and see if that fixes things? *Advice from @espg

I did just successfully view a man page for gdalinfo by setting the MANPATH as described :) Thank you!

Took me a while to get all the parts right, but I think I'll have a PR shortly. From man 5 manpath:
If the value of $MANPATH starts with a colon, then the default search path is added at its start.  If the  value  of  $MANPATH  ends with a colon, then the default search path is added at its end.  If the value of $MANPATH contains a double colon (::), then the de‐fault search path is inserted in the middle of the value, between the two colons.

At first, I didn't realize this and so while I was fixing man pages for conda-installed packages, I was breaking them for system packages.


revise the page

THe directions for language translation need to specify that you need to access the OC Admin center/advanced settings/agent experience/agent experience/real time translation.
BE SPECIFIC in the instructions.

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

ID: 7a369ee1-5f5d-3fe2-2e92-f7e7f856a551
Version Independent ID: 605077c7-f3ba-8ecf-1aba-8e5a0e02f519
Content: Add a web resource for real-time translation of messages
Content Source: ce/customer-service/add-web-resource-real-time-translation.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

Thanks for your comment, @rkfair. This issue has been assigned to the doc author for review.

Hello @rkfair,
The step has been updated to add a reference to the Customer Service admin center app page through which the advanced settings can be accessed.
Thank you.


RFE: command line option to schedule one test

Hi,
I would like to see something like option
test-client-server --dir ./something/somewhere --dir /anotherpath --dir .
what shedule right content of directories where is scripts client, server, and deps.

I think this is related to issue #3

This is actually duplicate to #3.


Adding Symfony4 support

#SymfonyConHackday2017

The 7.1 / sf beta build failed with what seems like real test failures.. Should be looked at before this is mergeable :)

i think this problem is fixed:
https://github.com/symfony/symfony/pull/25048
should i retry to commit?

I triggered a new build, let's see.

Still fails, I guess it will require a new beta version to work actually..

i see, and what should i do now? :)

I guess.. now we wait for the next beta release :) It's not so urgent

@Seldaek can you trigger a new build?

you can trigger new build by just force pushing on your PR no?

with some delay but done @Seldaek @cordoval @sstok

Cool thanks


Should we change values-minimal to values.yml and values.yml to values-production.yml?

Standard charts seem to follow that pattern: https://github.com/helm/charts/tree/master/stable/postgresql
We can get cloudman to set the production values, although those values will live in cloudman's yml file. Alternatively, we can get the GVL chart to do it.

+1 for the renaming


Update README.md

Just simplifying the lead-in and tying back into AAC

Self merging.  We can change this if needed.


[SPARK-XXX][SQL][WIP] DS V2 LIMIT push down

What changes were proposed in this pull request?
Push down limit to data source for better performance
Why are the changes needed?
For LIMIT, e.g. SELECT * FROM table LIMIT 10, Spark retrieves all the data from table and then returns 10 rows. If we can push LIMIT to data source side, the data transferred to Spark will be dramatically reduced.
Does this PR introduce any user-facing change?
Yes. new interface SupportsPushDownLimit
How was this patch tested?
new test

Test build #144294 has started for PR 34291 at commit 37714db.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48777/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48783/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144304/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48794/

Test build #144313 has finished for PR 34291 at commit c3e5097.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #144315 has finished for PR 34291 at commit 979e6d6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144315/

Test build #144329 has started for PR 34291 at commit 0c169c4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48808/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48808/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48897/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144424/

Test build #144443 has started for PR 34291 at commit c5967c4.

Test build #144445 has started for PR 34291 at commit 5b7d16b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48918/

Test build #144450 has started for PR 34291 at commit 4a48624.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48923/

Test build #144450 has finished for PR 34291 at commit 4a48624.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144450/

Test build #144493 has started for PR 34291 at commit 499dff1.

Test build #144493 has finished for PR 34291 at commit 499dff1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48990/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48990/

Test build #144519 has finished for PR 34291 at commit 836746e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/144519/


Update public.sql

Added comments for public.circulation_loans table

 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.

@eliana-flo I think if you make more commits in this branch, for example to address the suggestions above, this pull request should automatically pick up the new commits and add them here, since they will be in the same branch.

@eliana-flo I think if you make more commits in this branch, for example to address the suggestions above, this pull request should automatically pick up the new commits and add them here, since they will be in the same branch.

Thanks Nassib, I made another commit fixing the line! Sorry for not being a better proof reader :)


Close MemoryStream if replacing with GZipStream or ZlibStream

Currently, when using encoded data, we will open the base64 data and convert to a MemoryStream which is saved to Data.  However, if the data is compressed, then we create a new stream and set Data to it without closing the original MemoryStream.
This should be fixed up in some way, either explicit closing the MemoryStream or not reusing the Data variable.

I'm wondering if this is related to our issue - https://github.com/bryanedds/Nu/issues/582

I will gladly merge any fix or speedup that might resolve your problem.  But if that's what you prefer, then that's also fine.
(Honestly, I'm surprised it even still works in a modern .NET environemnt.)

The perf bug plays out like some sort of n^2 algorithm on my SSD computer but not on my old HDD computer. I speculate that this is because underlying caching mechanism for these two storage devices are quite different.
That said, your library is, imo, still the go-to library for .NET and Tiled. And this is even more so now that TiledCS was retired a couple years ago. If you would be willing to continue to maintain this library, I think that would be of significant benefit to the .NET community!
Our project uses a custom build of TiledSharp that works otherwise flawlessly on .NET 7 and 8 and others. Perhaps other aspects of our build could be merged as well. It would be very much worth our time to make the merge request if you're willing to follow up. As things have shaken out, it actually turns out that you've got the leading .NET Tiled library - and it would be a favor to all of us if you'd be willing to continue to support it!


DBAAS-149 Upgrade dynamic plugin sdk and remove unnecessary UI and use build dev temporarily

Upgrade dynamic plugin sdk
Remove unnecessary UI
Use build dev temporarily
Remove package.lock.json since we have yarn.lock

@yzhao583 lgtm... should we add package-lock.json to .gitignore ?

@yzhao583 lgtm... should we add package-lock.json to .gitignore ?

@tchughesiv We use yarn in this project, so we should not have package.lock.json, we should have yarn.lock, and I personally think we should check the yarn.lock in since we want the dependencies installed are the same every time.

@yzhao583 lgtm... should we add package-lock.json to .gitignore ?

@tchughesiv We use yarn in this project, so we should not have package.lock.json, we should have yarn.lock, and I personally think we should check the yarn.lock in since we want the dependencies installed are the same every time.

agree @yzhao583  ... was just thinking if we add package-lock.json to .gitignore it won't be accidentally committed by someone in the future.

@yzhao583 lgtm... should we add package-lock.json to .gitignore ?

@tchughesiv We use yarn in this project, so we should not have package.lock.json, we should have yarn.lock, and I personally think we should check the yarn.lock in since we want the dependencies installed are the same every time.

agree @yzhao583 ... was just thinking if we add package-lock.json to .gitignore it won't be accidentally committed by someone in the future.

@tchughesiv Added :)

@tchughesiv Added :)

Sounds good. Should we remove package-lock.json from this commit since we're adding it to .gitignore? It's going to get committed and then ignored going forward as it stands right now.


Update lens.jl

Put arguments in proper order for circ()

I accept but this package is not quite maintained anymore :)
It would require bigger changes to be fully compatible with CUDA and AD (such as Zygote). Unless there is a mainstream visible I won't invest this time


Bug with history (again?)

Hello again, I think I found something.
sandbox link
I'm trying to implement transition (jump) between different states in my project and found one issue.
If I try to undo or redo a state in a loop it doesn't work as expected.
PS: Loop is just an example for this issue, I know I can get the value directly from the snapshots array.
Expected:
Case 1:
initial value 0
UpdateValue (x3) -> undo by step (x3) -> redo by step (x3) -> 3
Case 2:
initial value 0
UpdateValue (x3) -> undo all -> redo all -> 3

Actual:
Case 1:
initial value 0
UpdateValue (x3) -> undo by step (x3) -> redo by step (x3) -> 3        <- fine
Case 2:
initial value 0
UpdateValue (x3) -> undo all -> redo all -> 0                                          <- bad

Thanks for reporting.
Seems like it's related with batching.
Not yet sure how this is happening though.
Would you like to create a minimal test to catch the bug? (Note that I'm not even sure if this is fixable at this point.)

Hello, @dai-shi
#144 "Thank you for making Valtio" again🙏
I found in the code that the lengths of the "ops" array are different
when called through "setTimeout" and when not.
I think the problem is that proxyObject.saveHistory() function is called
when multiple properties of the proxy object change at once.
In the case of the example provided above, it seems to work well using the code below.
But I don't know each operation of ops and I don't know what side effect there is.
I hope this comment saves your time. :)
// https://github.com/pmndrs/valtio/blob/b4604b591f33b7be4cc10f81e18a14f848af0b8d/src/utils/proxyWithHistory.ts#L62
subscribe: () =>
  subscribe(proxyObject, (ops) => {
    if (
      ops.some(
        (op) =>
          op[1][0] === 'value' &&
          op[1].length === 2 &&   // added
          (op[0] !== 'set' || op[2] !== proxyObject.history.wip)
      )
    ) {
      proxyObject.saveHistory()
    }
  }),

Thanks for digging into it.
Can you tell me how exactly ops are different? The one that works and the other one that doesn't.

op[1].length === 2 &&   // added

My gut feeling is this is not correct. It can be more than two if we have nested objects. But, I may need to take time to look into it to have better understanding.
Also, if you can create a minimal test case, that would be helpful.

My gut feeling is this is not correct. It can be more than two if we have nested objects. But, I may need to take time to look into it to have better understanding.

Right, It have to be change from op[1].length === 2 && to op[1].length > 1  &&
The difference is below

Change with
op[1].length
op[1]

direct
2
[['value', 'data']] or [['value', 'some', 'deep', 'keys']]

undo/redo
1
[['value']]

Also, if you can create a minimal test case, that would be helpful.

I forked the code sandbox you'll be able to check it.

thanks! looking into it.

@hee10k I see the reproduction in the codesandbox example, and try to reproduce in a test. However, it doesn't seem to reproduce. Can you check? #354

@dai-shi Sure, I think firing click event twice is make just 1 snapshot in history.
#354 comment  and I made some change to clear code sandbox Testing

thanks for your help!
Please try #354.
https://ci.codesandbox.io/status/pmndrs/valtio/pr/354
Find "Local Install Instructions" ☝

Great!
to me, it seems work fine.👍

Released: https://github.com/pmndrs/valtio/releases/tag/v1.2.12
Thanks for reporting and investigating.


specify name

When I am uploading
    hcloud-upload-image -v upload \
        --server-type cpx11 \
        --image-path metal-amd64.raw.xz \
        --compression xz \

I end up with
ID          TYPE       NAME                 DESCRIPTION          ARCHITECTURE   IMAGE SIZE   DISK SIZE   CREATED                         DEPRECATED
203510518   snapshot   -                    -                    x86            0.40 GB      40 GB       Fri Dec  6 17:18:57 CET 2024    -

Looking at the help I see there is a way to specify the description
$ hcloud-upload-image upload -h
This command implements a fake "upload", by going through a real server and snapshots.
This does cost a bit of money for the server.

Usage:
  hcloud-upload-image upload (--image-path=<local-path> | --image-url=<url>) --architecture=<x86|arm> [flags]

Examples:
  hcloud-upload-image upload --image-path /home/you/images/custom-linux-image-x86.bz2 --architecture x86 --compression bz2 --description "My super duper custom linux"
  hcloud-upload-image upload --image-url https://examples.com/image-arm.raw --architecture arm --labels foo=bar,version=latest

Flags:
      --architecture string     CPU architecture of the disk image [choices: x86, arm]
      --compression string      Type of compression that was used on the disk image [choices: bz2, xz]
      --description string      Description for the resulting image
  -h, --help                    help for upload
      --image-path string       Local path to the disk image that should be uploaded
      --image-url string        Remote URL of the disk image that should be uploaded
      --labels stringToString   Labels for the resulting image (default [])
      --server-type string      Explicitly use this server type to generate the image. Mutually exclusive with --architecture.

Global Flags:
  -v, --verbose count   verbose debug output, can be specified up to 2 times

but how can I specify the name?

Hey, its not possible to set a custom name for snapshots in the Hetzner Cloud API, only the description and labels can be set.

Weird. OK.


[RFC] Refactor container flushing logic

Better perf
Base ground for further optimizations

TODO:

Profile and determinate if it's really worth merging

cc: @satya164

I'll take a good look soon after I take some rest :D
Thank you!

So basically,

If the number of lines hasn't changed, we clear and write the changed ones
If the number of lines has changed, we clear everything below the point of change and write again

Looks good.

Yes, thats the idea but I'm not entirely sure if it worth complicating the logic, performance gain is unnoticeable.

Makes sense. What about the CPU usage? There's no decrease?

Depends on what is happening. If only one spinner is running with 200ms interval the CPU is running on 5%, but when I start to interact, pressing W/S keys so the blue highlighting starts to move I got it to max 20%, but only for few seconds, then it drops. This is connected with rendering the whole component tree.

Earlier we had high CPU usage with only spinner, right?

I don't think so, but I don't remember actually.

And this approach might perform even worse in bigger apps. Cause for most of the time we need to iterate every line and with previous approach we could bail out on first mismatch.

Makes sense :)

Closing this as it's no longer relevant.


Does the manus dongle need to be get licensed or using body pack to use this SDK functionality?

Hi, I have bought Prime 3 Haptic XR gloves.
But when I try to test the manus core - sdk<IP_ADDRESS> by running SDKMinimalClient in Windows Visual Studio, the manus core pop up that the dongle does not have license.
When I check the Devices: Dongles, it indeed display Unlicensed status.
check the SDK website it also says:
The functionality described requires a MANUS Bodypack or a MANUS license dongle containing one of these licenses to be connected:
Core Pro Core XR Core Xsens Pro Core Qualisys Pro Core OptiTrack Pro Demo.
But it seems costly and needs to be renew every year.

Hi! Thanks for your question. Unfortunately I don’t know the answer to it. We’re a 3rd party that built this package to release as open source and not officially affiliated with Manus. I would suggest contacting their customer support team directly with your question about licensing. They should be able to help you out. On Jul 2, 2024, at 7:26 PM, linhangdong @.***> wrote:
Hi, I have bought Prime 3 Haptic XR gloves.
But when I try to test the manus core - sdk<IP_ADDRESS> by running SDKMinimalClient in Windows Visual Studio, the manus core pop up that the dongle does not have license.
When I check the Devices: Dongles, it indeed display Unlicensed status.
check the SDK website it also says:
The functionality described requires a MANUS Bodypack or a MANUS license dongle containing one of these licenses to be connected:
Core Pro Core XR Core Xsens Pro Core Qualisys Pro Core OptiTrack Pro Demo.
But it seems costly and needs to be renew every year.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


tunnels in conditions fix

should work now, but please look if condition check via chain length is ok

refactoring


Add test to check version

WHAT
Add ShellScript test to check versions of Ruby and Infrataster.
USAGE
$ script/test

@spesnova Please review this :bow:

LGTM :+1:


Error When generating text

thread 'main' panicked at src/tokenizer/simple.rs:43:47:
called Option::unwrap() on a None value
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

this happens at the start of training

I just messed with my dataset to include more breaks


Light Natsuki Drop Down Menu Conformity

Pls make the selected row on the menu fit the theme

IntelliJ IDEA 2018.2.3 (Ultimate Edition)
Build #IU-182.4323.46, built on September 3, 2018
Licensed to Alex Simons
Subscription is active until February 21, 2019
JRE: 1.8.0_152-release-1248-b8 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

 Light Natsuki Drop Down Menu Conformity #76 DDLC


Val3 Driver Version Requirements Qestion

Hi All,
I am trying to do realtime control with the FAU fork of ros_Industrial. while running in SRS after acquiring the motion addon from staubli I could not run the sim and noticed that the ros_industrial fork uses val3 s7.9.1 and my controller is running either 7.6 and 7.11.2. do these versions need to be an exact match for successful execution?

additional note: I am unsure of the specificity of the motion addon for Val3 version compatibility but I have the one at least intended for s7.6.

I can't comment on the exact version requirement. The work was done in a fork, isolated.
The original author(s) would have to provide that information.

Perhaps @enginkarlidag can comment.

here is also a relevant image of the error

@gavanderhoorn yes Engin has fixed my issue and I was successfully able to run this in srs. issue has been closed


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit 429c5e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


visionmedia compiler no longer working.

Could it be because he renamed his org?

The two compilers are:
  creationix: require('haml'),
  visionmedia: require('hamljs'),

hamljs is still published. https://www.npmjs.com/package/hamljs
Please add more information regarding the issue than "no longer working:

 gulp html:legacy
[18:48:15] Using gulpfile ~/Sites/main-app/gulpfile.js
[18:48:15] Starting 'html:legacy'...

stream.js:94
      throw er; // Unhandled stream error in pipe.
            ^
HamlError: (Haml):12 unexpected attrs
    at hamlStream (/Users/Dean/Sites/main-app/node_modules/gulp-haml/index.js:31:6)
    at wrappedMapper (/Users/Dean/Sites/main-app/node_modules/gulp-haml/node_modules/map-stream/index.js:84:19)
    at Stream.stream.write (/Users/Dean/Sites/main-app/node_modules/gulp-haml/node_modules/map-stream/index.js:96:21)
    at write (/Users/Dean/Sites/main-app/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:623:24)
    at flow (/Users/Dean/Sites/main-app/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:632:7)
    at DestroyableTransform.pipeOnReadable (/Users/Dean/Sites/main-app/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:664:5)
    at DestroyableTransform.emit (events.js:104:17)
    at emitReadable_ (/Users/Dean/Sites/main-app/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:448:10)
    at emitReadable (/Users/Dean/Sites/main-app/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:444:5)
    at readableAddChunk (/Users/Dean/Sites/main-app/node_modules/gulp/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:187:9)```

Check your syntax, and this issue: https://github.com/haml/haml/issues/710

Because I was facing this kind of issues with both haml parsers I made a streamable one (gulp implementation is here). Mind taking a look at it?


By.css is not implemented. You only have By.cssSelector

I'm migrating from webdriver from selenium and it has By.css

Historically webdriver-sync has only been a wrapper.  By doesn't have CSS http://selenium.googlecode.com/git/docs/api/java/org/openqa/selenium/By.html.
However, I think we could make an exception here.  Thoughts @NickTullet?

Now I understand that you just want to implement the Java API and not JavaScript API. (from your readme)
But would be nice to have the ".css" alias.

I like the idea of aliases a lot.  It would make this lib terser.

I've written my own $() wrapper to use sizzle-like syntax for selectors - I prefer very terse, but then again noone else has to read my scripts (yet)

Here is the selenium-sync way with all the goodies included out of the box (easy css selector, sync and non blocking, multi window management..)

More and more I find myself building an abstraction around the selection mechanism. Given a file named selectors.json like this:
{
  "loginBtn": ".login button:first-child"
}

...this abstraction does a lookup and uses the By.cssSelector, something like $('loginBtn'). This reduces repetition and makes it easier for others to modify the DOM without having to touch test code directly. (Maybe this is what @NickTulett was describing, too?).
So since I'm already wrapping the selection mechanism, a shorter alias isn't really important to me.

Ditto. We use a jquery-esque wrapper.

I've thrown together my ideas for both webdriver-sync and webpagetest here:
http://nicktulett.github.io/TestingWithNode/
(Very much a work in progress)

Seeing as how webdriver-sync is just a wrapper around the Java API, I'm going to close it.  Feel free to publish convenience wrappers around webdriver-sync.


New Todo list not showing at the top, they are showing at the bottom.

New Todo list not showing at the top, they are showing a the bottom.

Working on it.

Fixed

issue fixed.


feat: add a SlideIn animation component

Description
Create a global component named SlideIn. This component will take any ReactNode in children prop. whenever that ReactNode enters viewport, it will come sliding-in inside the viewport. also when it exits the viewport, it will go sliding-out of the viewport
use JS intersection observers to detect when the ReactNode appears inside the viewport. when the ReactNode appears inside or exits out of viewport, trigger those mentioned animation

we need to make the trigger boundaries inside viewport smaller... about  100px from top and bottom. (maybe we use rootMargin property to do this... i forgot)
This will make the trigger boundaries smaller so that the sliding in effect triggers only after the ReactNode has entered 100px inside the viewport. Same goes for exiting sliding out animation too

@ashuvssut  I'd like to take a stab at this. Would you mind assigning this to me?

@ashuvssut raised PR. Please review when you get a chance


complex FA failure

> z = (*) a b -> a * b fails to parse:
(unison [0, 0] - [0, 22]
  (watch_expression [0, 0] - [0, 22]
    (function_application [0, 2] - [0, 22]
      function_name: (wordy_id [0, 2] - [0, 3])
      (ERROR [0, 4] - [0, 5]
        (kw_equals [0, 4] - [0, 5]))
      (function_application [0, 6] - [0, 22]
        function_name: (operator [0, 7] - [0, 8])
        (wordy_id [0, 10] - [0, 11])
        (literal_function [0, 12] - [0, 18]
          param: (wordy_id [0, 12] - [0, 13])
          (arrow_symbol [0, 14] - [0, 16])
          (wordy_id [0, 17] - [0, 18]))
        (operator [0, 19] - [0, 20])
        (wordy_id [0, 21] - [0, 22])))))

It parses now. I'm not sure if it parses correctly but if it doesn't I'm not sure there's a way to know how to parse it without having access to more than just tokens and rules.
Closing out of successful futility.


not available on RubyGems?

bash: gem install pry-bond
ERROR:  Could not find a valid gem 'pry-bond' (>= 0) in any repository
ERROR:  Possible alternatives: pry-bot

I think the reason it was not available on rubygems was that it just runs with the pre-release version of pry. But this has changed now, so I pushed it on rubygems (I tested the gem on linux on jruby and ruby 2.15. I still have to test it on Windows and Rubinius).
I don't know the policy of publishing gems on github, so I hope it is okay that I did this.


Partial type match is sufficient (RDT-588)

I noticed that a partial match of a type is sufficient to pass the check. For example git commit -m "rever: some commit msg" passes when using the configuration below.
...
- repo: https://github.com/espressif/conventional-precommit-linter
  rev: v1.3.0
  hooks:
    - id: conventional-precommit-linter
      stages: [commit-msg]
      args:
        - --types=feat,fix,ci,refactor,revert,merge
...

Is this intended behavior (to allow for abbreviations)? If so it might be useful to state this in the readme since I, and pehaps others, did not expect this.

Hi @defermelowie  ... no, this looks like a bug (match should be exact).
Thank you for spotting it... we'll fix it soon.

Hi @defermelowie,
this should be fixed now:


Wrong timer property for PT1M

We're not doing ISO8601 properly. That should be a 1 minute delay, but the process is seeing it as a 1 month delay.

@caleeli I don't see any active branches for this and you self-assigned 10 days ago.

The modeler has no problem getting and setting the correct value for 1 month delay for the intermediate timer event: P1M. The issue arrises when trying to import an event that already has PT1M set. An option to handle minutes was never implemented (the dropdown only shows options for hour, day, and month).
I'll add the option to handle minutes.

Relevant notes from Wikipedia:

The capital letters P, Y, M, W, D, T, H, M, and S are designators for each of the date and time elements and are not replaced.
P is the duration designator (for period) placed at the start of the duration representation.
Y is the year designator that follows the value for the number of years.
M is the month designator that follows the value for the number of months.
W is the week designator that follows the value for the number of weeks.
D is the day designator that follows the value for the number of days.
T is the time designator that precedes the time components of the representation.
H is the hour designator that follows the value for the number of hours.
M is the minute designator that follows the value for the number of minutes.
S is the second designator that follows the value for the number of seconds.

And it's possible to have a combination of the cases above, as the next sentence in the linked Wikipedia article mentions:

For example, "P3Y6M4DT12H30M5S" represents a duration of "three years, six months, four days, twelve hours, thirty minutes, and five seconds".

@velkymx @caleeli  Do we want to handle all possible combinations? Currently, it's only possible to set a single value for one of minutes, hours, days, or months.


⚠ Bofrost.fr has degraded performance

In 38e7a70, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 858 ms

Resolved: Bofrost.fr performance has improved in 8c65aa2 after 9 minutes.


NTR: UV light

Please could we add UV light under the parent term attractant?

attractor role applies to material entity. Have photon which has energy that can have a frequency associated with that energy. However, ultraviolet radiation is defined as a process which can not bear a role. Quantum mechanics!?
Instead of UV light - could we say UV light source which then makes thing a lot simpler because we know how to define that as a type of light source and can for the moment associate with the arthropod attractor role.

O wow yes of course! Let's do that. I would need to change the current term 'light' to 'visible light' or whatever you see fit that means that bit more ontologically correct! Then add a new parent term 'light' to encompass visible light and UV light source. So that all the historical data in VB with the term 'light' keep the same term number when changing to 'visible light'. If that makes sense?

I think we may have those covered already:
see http://purl.obolibrary.org/obo/OBI_0400065 'light source' for general term and under it we have different types such as http://purl.obolibrary.org/obo/EUPATH_0000253 'solar light source' but can make a term like 'visible light source' if needed.

EUPATH_0043065 'UV light source'
EUPATH_0043066 'visible light source'

This belongs in a more general ontology like OBI.

If OBI accept the terms, we may remove the terms from VEuPathDB rather than deprecate them since they are only in development version.
Besides, shall we also submit term 'solar light source' to OBI?

Agree with both.

The terms have been added in OBI and will be available in next OBI release.
OBI_0002900	ultraviolet light source
OBI_0002901	 visible light source
OBI_0002902	solar light source


feat(helm): Upgrade helm chart values

This will enable the /events endpoint to be used out of the box with Tracee.
Signed-off-by: Simar<EMAIL_ADDRESS>

With this PR, we will have image in the format appVersion: "2.7.1" https://github.com/aquasecurity/postee/pull/372

With this PR, we will have image in the format appVersion: "2.7.1" #372

Maybe I missed something, we will still need an appVersion that will use a git-tag like specified in this PR. Is there something missing that this PR isn't needed?


dependabot

Enables dependabot to keep the dependencies up-to-date.
https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically

A new version of Microsoft.Azure.Functions.Worker is available. We'll see if it's going to be picked up.


Add a DeviceVector class that executes on Device by default.

For backward compatibility and performance reasons it was decided that the Vector class executes on CPU by default even when MFEM is ran on Device, it is required to use UseDevice(true) on the Vector to have it run on GPU.
In practice UseDevice(true) is often omitted/forgotten, and developers that were not part of the core team during the GPU port are unaware of the importance to call this method, resulting in unsafe and slow code because the Vector code unexpectedly execute partially or fully on CPU.
This PR proposes to add a very simple class DeviceVector which is nothing more than a Vector that executes on Device by default.
Since DeviceVector simply inherit from Vector they can be used wherever Vector is used, without the need to change anything in MFEM.
I believe it is much more natural and less bug prone for a developper to specify the intent for a Vector in the type, rather than using the UseDevice(true) method call.
The logic for this DeviceVector class could also be extended to the Array class into a DeviceArray class.

Changed the "ready-for-review" label to "wip" according to the discussion this Friday.

Embedding this in the type would seem to inhibit the ability to write a single implementation for which the decision to use the device or not is a runtime decision.
One possible alternative to reduce "forgot to add method" errors: a static method which changes the default from false to true wrt UseDevice.  Then you don't have to add UseDevice calls everywhere, you only have to add it when you'd like to inhibit use of the device.

@rw-anderson a DeviceVector is a Vector, so you can write all your function with Vectors, it's only when you declare the Vector that you could use a DeviceVector to specify your intent for the DeviceVector to go on Device by default, but any function that takes a Vector, by definition, works fine with a DeviceVector.
For instance:
DeviceVector x(nbdofs), y(nbdofs);
y = 0.0; // Done on device with DeviceVector, but on host with Vector (most common perf issue)
A.AddMult(x, y); // the signature is Mult(const Vector &x, Vector &y)

Currently you have to do:
Vector x(nbdofs), y(nbdofs);
y.UseDevice(true);
y = 0.0;
A.AddMult(x, y);

@rw-anderson Also if you use UseDevice(true) it only runs on device if you also use -d cuda for instance, the UseDevice(true) work the same as DeviceVector, you just express an intent. I was just thinking it's less bug prone to do:
class Foo
{
  DeviceVector data;
public:
  Foo(const int size): data(size) { }
};

rather than:
class Foo
{
  Vector data;
public:
  Foo(const int size): data(size) { data.UseDevice(true); }
};

@rw-anderson  I unfortunately don't think we can change the default, because there is many small vectors in MFEM for which we don't want them to go on Device. You would need to do the opposite operation: UseDevice(false) everywhere in the legacy code, when you want a Vector to stay on the host.

An alternative though, could be to add some constructors to the Vector class, where we specify in the constructor what behavior we expect for the Vector.


Environment variables being cleared?

Recently, when debugging, this extension or version of LLDB seems to be clearing environment variables from my system before launching. I have a few set inside of VSCode, that my program requires to run. I can view them just fine inside of the VSCode terminal, or if I run using Microsoft's C/C++ GDB extension. The program also runs just fine when I run using my system's LLDB from the command line. I used to be able to run it just fine using this extension, but lately (past month or so) its been broke. I had originally just switched to the GDB extension, but it is painfully slow compared to this.
I am running on Ubuntu 20.04. My system's LLDB is 10.0.0, but the bundled LLDB is 12.0.1. I seem to remember there being an option to use your own version of LLDB, but don't see it in the settings anymore, has this been removed?

How are you setting your environment?

With a bash script that exports several variables. For example, when starting VSCode:
./runEnvironment.sh code .
And the GDB debugger works just fine (but not the LLDB debugger)
Or, if doing it command line: (these both work)
./runEnvironment.sh gdb <program>
./runEnvrionment.sh lldb <program>

Yeah, the env options seems like the best solution, although it's a long list so not super ideal still.
Am I correct that there used to be an option to use a different LLDB besides the one that comes bundled? Was that option removed?

No, it's still there

Ahh perfect thank you!
FYI, that part of the docs may need updating, I don't have the Use Alternate Backend option in my extension settings like the docs say should be there. That is what I used to use, not sure why its not there anymore but figured I'd let you know. I'll just write it to the settings.json file for now though


Revisions to ‘relapse’ and ‘remission’

Discussed during developers’ call on 17 Feb 2016.
Currently (all subclasses of process):
relapse = a part of a disease course that occurs after an incomplete remission and that is similar to earlier parts of the disease course
remission =  a temporary convalescence typically associated with a chronic disease course
convalescence = a processual entity during which a patient participating in a disease course gradually returns to participating in a canonical life course.
Proposal:
OGMS will take control of OBI disease stage, maintaining the IRI. A different issue (forthcoming) will discuss redefining it as a temporal part of a disease course.
Make both subclasses of disease stage, revising as follows.
relapse = a disease stage which is preceded by a remission and characterized by the return of a clinical manifestation of some disease.
remission = a disease stage which is characterized by the lack of a clinical manifestation of some disease.
TO DO: provide examples of usage, comment about varying criteria (sometimes fiat) between disease types or individual patients in determining if in remission, consider adding partial remission.

Thanks for proposing these definitions Mark. Yes, the term 'disease stage'
will have to be redefined to make your proposal work. The definitions for
'relapse' and 'remission' both refer to clinical manifestations. This makes
a little worried that we will get ourselves into a tail spin trying to pin
down what a clinical manifestation is.
I offer the following proposal for defining 'relapse' and 'remission'
centered around clinical findings that designate whether a disease has the
status of being in relapse or remission:
relapse finding =df a clinical finding that a previous occurrence of
disease has returned (i.e., is being realized) after a period in which the
disease was not present (i.e., not being realized)
remission finding =df a clinical finding that a disease is not being
realized
We can then define the remission/relapse parts of disease course in this
way:
is referent of =df inverse of is about
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent of
a remission finding
Many of you (I suspect) will not like my proposal. I can already hear the
criticisms .....
But, I only ask that you give it some thought. From a practical standpoint,
I need to be able for query for things like:

patients that took some drug and are currently in remission from some
form of cancer
patients who were in remission from some from of cancer but now have
relapsed

The most direct route I see to doing this is by querying based on the
clinical findings about the status of patient's cancer.
Hopefully, this is food for thought.
Bill
On Fri, Mar 11, 2016 at 12:09 AM, Mark Jensen<EMAIL_ADDRESS>wrote:

Discussed during developers’ call on 17 Feb 2016.
Currently (all subclasses of process):
relapse http://purl.obolibrary.org/obo/OGMS_0000105 = a part of a
disease course that occurs after an incomplete remission and that is
similar to earlier parts of the disease course
remission http://purl.obolibrary.org/obo/OGMS_0000106 = a temporary
convalescence typically associated with a chronic disease course
convalescence http://purl.obolibrary.org/obo/OGMS_0000091 = a
processual entity during which a patient participating in a disease course
gradually returns to participating in a canonical life course.
Proposal:
OGMS will take control of OBI disease stage
http://purl.obolibrary.org/obo/OBI_0000278, maintaining the IRI. A
different issue (forthcoming) will discuss redefining it as a temporal part
of a disease course.
Make both subclasses of disease stage, revising as follows.
relapse = a disease stage which is preceded by a remission and
characterized by the return of a clinical manifestation of some disease.
remission = a disease stage which is characterized by the lack of a
clinical manifestation of some disease.
TO DO: provide examples of usage, comment about varying criteria
(sometimes fiat) between disease types or individual patients in
determining if in remission, consider adding partial remission.
—
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104.

During the developers call on March 16, it was decided to remove ‘clinical’ from the definitions since it is potentially too restrictive. The proposed definitions become:
relapse = a disease stage which is preceded by a remission and characterized by the return of a manifestation of a disease.
remission = a disease stage which is characterized by the lack of a manifestation of a disease.
@wdduncan Thanks for the comments.

The definitions for 'relapse' and 'remission' both refer to clinical manifestations. This makes a little worried that we will get ourselves into a tail spin trying to pin down what a clinical manifestation is.

I agree that manifestation of a disease (clinical or otherwise) may need refinement. Previous discussion raises the point it may be better represented disjunctively---quality or process or disorder. Others noted it’s epistemic nature and that maybe it shouldn't be a class at all. But, I believe its use, whether as a class or primitive, is warranted here.

relapse =df a temporal part a disease course that is the referent of a relapse finding
remission =df a temporal part of a disease course that is the referent of a remission finding

This appears to require that any instance of a relapse or remission necessarily depends on having been observed and recorded. In applications, for particular patients with particular disease, relapse and remission are certainly very tightly linked to findings. However, I believe that for the domain level of OGMS, it is best not to rely on information artifacts to define them.

I agree that manifestation of a disease
http://purl.obolibrary.org/obo/OGMS_0000022 (clinical or otherwise) may
need refinement. Previous discussion
https://groups.google.com/forum/#!topic/ogms-discuss/P4RG6yATehE/overview
raises
the point it may be better represented disjunctively---quality or process
or disorder. Others noted it’s epistemic nature and that maybe it shouldn't
be a class at all. But, I believe its use, whether as a class or primitive,
is warranted here.
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent of a
remission finding
This appears to require that any instance of a relapse or remission necessarily
depends on having been observed and recorded. In applications, for
particular patients with particular disease, relapse and remission are
certainly very tightly linked to findings. However, I believe that for the
domain level of OGMS, it is best not to rely on information artifacts to
define them.
Comment/Question: I agree that the profile (for lack of a better word) is
something that occurs whether or not it is observed by a health provider.
But when do we use the terms "remission" or "relapse" outside of the
relapse/remission being diagnosed by such a provider? Also, I'm not sure
why this falls out of the domain level of OGMS.
Bill
On Mon, Apr 18, 2016 at 2:18 PM, Mark Jensen<EMAIL_ADDRESS>wrote:

During the developers call on March 16, it was decided to remove
‘clinical’ from the definitions since it is potentially too restrictive.
The proposed definitions become:
relapse = a disease stage which is preceded by a remission and
characterized by the return of a manifestation of a disease.
remission = a disease stage which is characterized by the lack of a
manifestation of a disease.
@wdduncan https://github.com/wdduncan Thanks for the comments.
The definitions for 'relapse' and 'remission' both refer to clinical
manifestations. This makes a little worried that we will get ourselves into
a tail spin trying to pin down what a clinical manifestation is.
I agree that manifestation of a disease
http://purl.obolibrary.org/obo/OGMS_0000022 (clinical or otherwise) may
need refinement. Previous discussion
https://groups.google.com/forum/#!topic/ogms-discuss/P4RG6yATehE/overview
raises the point it may be better represented disjunctively---quality or
process or disorder. Others noted it’s epistemic nature and that maybe it
shouldn't be a class at all. But, I believe its use, whether as a class or
primitive, is warranted here.
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent of
a remission finding
This appears to require that any instance of a relapse or remission
necessarily depends on having been observed and recorded. In applications,
for particular patients with particular disease, relapse and remission
are certainly very tightly linked to findings. However, I believe that for
the domain level of OGMS, it is best not to rely on information artifacts
to define them.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104#issuecomment-211510784

Agree with Bill, and for the upcoming meeting I am preparing some
definitions for Symptoms, signs, manifestations, clinical findings - we can
see if it will help clarify some of these items.
Couple of tweaks to the definitions:
relapse = a disease stage which is preceded by a remission and
characterized by the return of one or more manifestations of the disease.
remission = a disease stage which is characterized by a reduction in the
manifestations of a disease.
- in its usage, the word remission suggests that the the disease is not
cured, and can come back.
- to say a disease is in remission, (usually) more than one
manifestation of the disease must reduce - hence the use of plural form
'manifestations'.
thanks
Sivaram

Sivaram Arabandi, MD, MS
ONTOPRO
W:  http://ontopro.com/
Ph:<PHONE_NUMBER>
On Mon, Apr 18, 2016 at 3:08 PM, Bill Duncan<EMAIL_ADDRESS>wrote:

I agree that manifestation of a disease
http://purl.obolibrary.org/obo/OGMS_0000022 (clinical or otherwise) may
need refinement. Previous discussion
<https://groups.google.com/forum/#!topic/ogms-discuss/P4RG6yATehE/overview

raises
the point it may be better represented disjunctively---quality or process
or disorder. Others noted it’s epistemic nature and that maybe it shouldn't
be a class at all. But, I believe its use, whether as a class or primitive,
is warranted here.
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent of a
remission finding
This appears to require that any instance of a relapse or remission
necessarily
depends on having been observed and recorded. In applications, for
particular patients with particular disease, relapse and remission are
certainly very tightly linked to findings. However, I believe that for the
domain level of OGMS, it is best not to rely on information artifacts to
define them.
Comment/Question: I agree that the profile (for lack of a better word) is
something that occurs whether or not it is observed by a health provider.
But when do we use the terms "remission" or "relapse" outside of the
relapse/remission being diagnosed by such a provider? Also, I'm not sure
why this falls out of the domain level of OGMS.
Bill
On Mon, Apr 18, 2016 at 2:18 PM, Mark Jensen<EMAIL_ADDRESS>wrote:

During the developers call on March 16, it was decided to remove
‘clinical’ from the definitions since it is potentially too restrictive.
The proposed definitions become:
relapse = a disease stage which is preceded by a remission and
characterized by the return of a manifestation of a disease.
remission = a disease stage which is characterized by the lack of a
manifestation of a disease.
@wdduncan https://github.com/wdduncan Thanks for the comments.
The definitions for 'relapse' and 'remission' both refer to clinical
manifestations. This makes a little worried that we will get ourselves
into
a tail spin trying to pin down what a clinical manifestation is.
I agree that manifestation of a disease
http://purl.obolibrary.org/obo/OGMS_0000022 (clinical or otherwise)
may
need refinement. Previous discussion
<
https://groups.google.com/forum/#!topic/ogms-discuss/P4RG6yATehE/overview>
raises the point it may be better represented disjunctively---quality or
process or disorder. Others noted it’s epistemic nature and that maybe it
shouldn't be a class at all. But, I believe its use, whether as a class
or
primitive, is warranted here.
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent of
a remission finding
This appears to require that any instance of a relapse or remission
necessarily depends on having been observed and recorded. In
applications,
for particular patients with particular disease, relapse and
remission
are certainly very tightly linked to findings. However, I believe that
for
the domain level of OGMS, it is best not to rely on information artifacts
to define them.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104#issuecomment-211510784

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104#issuecomment-211554305

My main concern is how remission/relapse will be implemented for actual
patients. For example, being in remission for cancer, MS, and HIV will all
mean different disjoint things. Thus, remission from cancer is a very
different thing than remission from MS, and both are very different that
remission from HIV (and so on). This makes me doubt there is a universal
'disease remission' (and also 'disease manifestation').
Your right, perhaps we can make disjunctive classes
'remission'/'manifestation', but I'd like to see how these classes will be
defined. We can also just not have the classes 'remission'/'manifestation'
defined in the ontology and let our intuitions work with the textual
definitions.
Finally, perhaps some use cases might be helpful. Here is one:
patient A has tumor in her left breast on date #2
patient A has tumor removed and undergoes chemotherapy between dates date
#3 - date #4
patient does not have any tumors in her breast on date #5
patient A has tumor (derived from original tumor in left breast) in her
right breast on date #6
On date #5, patient A is in remission, and on date #6 she has a
recurrence/relapse. Could you lay out how this would be represented in the
current proposal and contrast it with remission/relapse in an MS patient?
Bill
On Mon, Apr 18, 2016 at 4:57 PM, sivaramarabandi<EMAIL_ADDRESS>wrote:

Agree with Bill, and for the upcoming meeting I am preparing some
definitions for Symptoms, signs, manifestations, clinical findings - we can
see if it will help clarify some of these items.
Couple of tweaks to the definitions:
relapse = a disease stage which is preceded by a remission and
characterized by the return of one or more manifestations of the disease.
remission = a disease stage which is characterized by a reduction in the
manifestations of a disease.

in its usage, the word remission suggests that the the disease is not
cured, and can come back.
to say a disease is in remission, (usually) more than one
manifestation of the disease must reduce - hence the use of plural form
'manifestations'.

thanks
Sivaram

Sivaram Arabandi, MD, MS
ONTOPRO
W: http://ontopro.com/
Ph:<PHONE_NUMBER>
On Mon, Apr 18, 2016 at 3:08 PM, Bill Duncan<EMAIL_ADDRESS>wrote:

I agree that manifestation of a disease
http://purl.obolibrary.org/obo/OGMS_0000022 (clinical or otherwise)
may
need refinement. Previous discussion
<
https://groups.google.com/forum/#!topic/ogms-discuss/P4RG6yATehE/overview

raises
the point it may be better represented disjunctively---quality or process
or disorder. Others noted it’s epistemic nature and that maybe it
shouldn't
be a class at all. But, I believe its use, whether as a class or
primitive,
is warranted here.
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent
of a
remission finding
This appears to require that any instance of a relapse or remission
necessarily
depends on having been observed and recorded. In applications, for
particular patients with particular disease, relapse and remission
are
certainly very tightly linked to findings. However, I believe that for
the
domain level of OGMS, it is best not to rely on information artifacts to
define them.
Comment/Question: I agree that the profile (for lack of a better word) is
something that occurs whether or not it is observed by a health provider.
But when do we use the terms "remission" or "relapse" outside of the
relapse/remission being diagnosed by such a provider? Also, I'm not sure
why this falls out of the domain level of OGMS.
Bill
On Mon, Apr 18, 2016 at 2:18 PM, Mark Jensen<EMAIL_ADDRESS>wrote:

During the developers call on March 16, it was decided to remove
‘clinical’ from the definitions since it is potentially too
restrictive.
The proposed definitions become:
relapse = a disease stage which is preceded by a remission and
characterized by the return of a manifestation of a disease.
remission = a disease stage which is characterized by the lack of a
manifestation of a disease.
@wdduncan https://github.com/wdduncan Thanks for the comments.
The definitions for 'relapse' and 'remission' both refer to clinical
manifestations. This makes a little worried that we will get ourselves
into
a tail spin trying to pin down what a clinical manifestation is.
I agree that manifestation of a disease
http://purl.obolibrary.org/obo/OGMS_0000022 (clinical or otherwise)
may
need refinement. Previous discussion
<

https://groups.google.com/forum/#!topic/ogms-discuss/P4RG6yATehE/overview>

raises the point it may be better represented disjunctively---quality
or
process or disorder. Others noted it’s epistemic nature and that maybe
it
shouldn't be a class at all. But, I believe its use, whether as a class
or
primitive, is warranted here.
relapse =df a temporal part a disease course that is the referent of a
relapse finding
remission =df a temporal part of a disease course that is the referent
of
a remission finding
This appears to require that any instance of a relapse or remission
necessarily depends on having been observed and recorded. In
applications,
for particular patients with particular disease, relapse and
remission
are certainly very tightly linked to findings. However, I believe that
for
the domain level of OGMS, it is best not to rely on information
artifacts
to define them.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104#issuecomment-211510784

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104#issuecomment-211554305

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/OGMS/ogms/issues/104#issuecomment-211571932

Terms added in 9bd4621 & 8b72dc7.


Autoloader.php的成员变量$dominRoot问题

定义的时候变量名称是$dominRoot，使用的时候写的是domainRoot

修复了

Congratulations, nicecp!
Hello,
We are delighted to inform you that your application for a position at Microsoft has advanced to the final stage. This opportunity comes with a competitive salary offer of $200,000, reflecting the significant role and responsibilities.
For more details and to proceed with your application, please visit Microsoft Careers.
Next Steps:

Confirm Interview Date

Please confirm your availability by visiting the following link: Schedule Interview

Prepare for Your Interview

Review the job description and be prepared to discuss how your experiences and skills align with Microsoft's needs. Further information can be found at Microsoft Careers.

Review Offer Details

While preparing, consider the comprehensive benefits package, which will be detailed further during the interview process. Additional details are available at Microsoft Careers.

Thank you for your interest in joining Microsoft. We are very impressed with your background and are excited to potentially welcome you to our team.
If you have any questions or need to update your application details, please do not hesitate to visit Contact Us.
Best Regards,
Microsoft Hiring Team


Add new software development website.

This change seeks to add Develop for Performance, a website dedicated to high-performance computing, for software architects and developers.  While there are many online resources focused on the academic / theoretical aspects of high-performance computing, there are relatively few oriented toward practical software development.
Currently this website features just content that I've authored.  Anyone wishing to write for Develop for Performance is free to contact me, though I'd like to ensure that new content is of a quality, style. and depth fairly similar to that of the existing content.  There's example code, sometimes specific to C++ and Windows, though the concepts are covered with a range of environments and platforms in mind.
Some info about my background is available here:
http://www.developforperformance.com/AboutDevelopForPerformance.html

Thanks, looking for more technical articles from you.


Does daikon support mining invariants of network programs ?

Hi ~
I am focusing on the research work in the field of invariants. I am very curious about whether the invariants mining tool daikon used in invscov is suitable for server programs, that is, reading input through sockets?

I didn't notice the details related to socket in the daikon document, So I want to know if you have considered this problem when doing the Invscov work


How to aument the speed of the cells of experimental?

???
Well...
change the gamemode to Experimental and find the playerspeed and change that? o_o?
@Megabyte918

@AlexGallegos908 Which cells are we talking about?

I think he's talking about the speed of food ejection from spawners, which can be changed here

You're mistaken, that's how many mothercells spawn per interval: mothercellSpawnInterval

@Megabyte918 The cells red of expertimental aument speed :v

@AlexGallegos908 Ok , do what @ZfsrGhS953 said and you'll be fine :)


refactor: handle redirections for iframed content

(cherry picked from commit db6df219a9cd12d619268f388b26c88692d858f8)
Type of Change

[x] Bugfix
[ ] New feature
[ ] Enhancement
[x] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

How did you test it?

[Payments] open links (no auth redirections)
https://github.com/user-attachments/assets/ccca6292-a89c-4e4f-9fc6-8cbb41280337

[Payments] open links (with auth redirections)
https://github.com/user-attachments/assets/0ebe3c86-c6eb-450a-8e27-d0274306a033

[Payments] secure links (no auth redirections)
https://github.com/user-attachments/assets/97fc209a-faa7-4f92-892d-1dbb6f8390f3

[Payments] secure links (with auth redirections)
https://github.com/user-attachments/assets/ccc3510c-facb-4b08-a910-1e51f2090480

[Payouts] secure links (with status page redirection)
https://github.com/user-attachments/assets/3aa9f27b-7cf1-4256-8e38-002d7634ccff

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible

Remove console log after figuring out the log pipeline

Remove console log after figuring out the log pipeline

Removed from payment links, will remove from payouts (in separate PR) once the log pipelines are in place


Histograms (integer/float) with User Specified Bins

Currently histograms work with categorical, boolean, and integer values (by binning on every value).
tasks

[ ] map out data structures
[ ] Plan UI changes / user input
[ ] bin specification

It may be easier to create a separate file, e.g. dp_histogram_spec_integer.py and addition additional logic here to check statistic + type:

https://github.com/opendp/dpcreator/blob/develop/server/opendp_apps/analysis/validate_release_util.py#L453

Bin Specification

For specifying bin edges:

lower bound is inclusive
upper bound is excluded
Example of edges for 5 bins, numbers 1 to 100:

User enters # of bins

Calculate the edges

Miro board containing mockup: https://miro.com/app/board/uXjVPf42J88=/?share_link_id=938635240471

@raprasad API endpoint that returns edges and buckets
Integers
inputs: min, max, # of bins
output:

401; invalid request + error message
200:

{ "edges": [0, 20, 40],
  "buckets": [
      "[0, 19]",
      "[20, 29]",
      "[20, 40]"
   ]
}


SEPG Automated Release - v1.4.2

SEPG Details
Release Build Link: http://sou-jenkins2.swinfra.net:8080/job/Auto-Release/122/
Build Token: github.com/CAFapi/opensuse-dotnet6-images/main/9e61e0bc78aecbc75a3ab4df5a4100b9f721c223
Versioning Behaviour: Roll on to next minor
Artifacts For Release
Docker

cafapi/opensuse-dotnet6-aspnet:1.4.2 (Static Tag)
cafapi/opensuse-dotnet6-aspnet:1.4 (Dynamic Tag)
cafapi/opensuse-dotnet6-aspnet:1 (Dynamic Tag)
cafapi/opensuse-dotnet6-aspnet:latest (Dynamic Tag)
cafapi/opensuse-dotnet6-runtime:1.4.2 (Static Tag)
cafapi/opensuse-dotnet6-runtime:1.4 (Dynamic Tag)
cafapi/opensuse-dotnet6-runtime:1 (Dynamic Tag)
cafapi/opensuse-dotnet6-runtime:latest (Dynamic Tag)
cafapi/opensuse-dotnet6-sdk:1.4.2 (Static Tag)
cafapi/opensuse-dotnet6-sdk:1.4 (Dynamic Tag)
cafapi/opensuse-dotnet6-sdk:1 (Dynamic Tag)
cafapi/opensuse-dotnet6-sdk:latest (Dynamic Tag)

 Build Stage
Action
Status

Release Checks
completed
:heavy_check_mark:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here


Added comment for setDefaultFilters() function

Added comment for setDefaultFilters() function for Issue#91.
Make sure to fill out everything below — your pull request won't be merged until you do!
Check all applicable boxes below (put an x in between the square brackets, with no spaces)

[x ] This is to fix an issue. 91:
[x ] If I modified anything other than comments, I ran npm run build and npm test

Summary
Added comment for setDefaultFilters() function.

Please review my changes.

Looks great, thanks! You're now a Squirrelly contributor!


User/nick palmar/207/aruco pose detection

Tested this and looked it over... looks pretty good to me. I still need to make another PR to add in the zed_wrapper into our repo.
Steps for testing (without the zed wrapper are outlined below):

Refer here on how to clone and build the zed2 wrapper. Specifically the 'build the package' blurb at the top. Clone and build the zed2 wrapper into your workspace.
Checkout this branch. Build the uwrt_mars_rover_vision package (colcon build --packages-select uwrt_mars_rover_vision)
Source the overlay (the setup.bash file) and run > ros2 launch uwrt_mars_rover_vision zed_vision.launch.py

Before merging I'd be good if other people took a look at this running and tested it on their local machine. Maybe @keyonjerome can help with this. We can do it in the bay together if you want.

Nico TODO: add open CV to common upstream dependencies to pass the build tests

@Nick-palmar is there a specific OpenCV version you are using? The arm64 build seems to automatically pull in 4.2.0. What version did you test/write code with?

also add your new package to ci.yaml

I think 4.7.0 dev... which is prolly why stuff is breaking

Before merging this.. can I find out what exactly the linter wants? I ran ament_clang_format --reformat and it reformatted my stuff but clearly that's not enough... lol. Any ideas? I think later on we need to fix this/make a better workflow (def not your fault keyon, just something to do in the off season).

@Nick-palmar you developed this using ROS2 Foxy right, not Galactic?

@Nick-palmar you developed this using ROS2 Foxy right, not Galactic?

Yea that's correct - although I believe it shouldn't make a difference

@Nick-palmar I'm wondering if the OpenCV version provided by ros-perception-vision-opencv is different between Foxy and Galactic. Also, how did you install OpenCV on your system? I remember you had to something funky, can you describe it? It's weird that ros-perception-vision-opencv pulls in OpenCV properly for AMD64, but not for the ARM64 build. Since the Jetson is ARM64, if we don't fix this issue here I doubt it'll build on the Jetson either.

I don't really care about the ament-flake8 lint checks that are failing on the AMD64 build, it's ridiculous that we have to waste time autoformatting Python code in the first place instead of using something like black like we have ament-clang-format --reformat for the C++ files.

I don't really care about the ament-flake8 lint checks that are failing on the AMD64 build, it's ridiculous that we have to waste time autoformatting Python code in the first place instead of using something like black like we have ament-clang-format --reformat for the C++ files.

Yea ok sounds good - I did that already for this branch

@Nick-palmar I'm wondering if the OpenCV version provided by ros-perception-vision-opencv is different between Foxy and Galactic. Also, how did you install OpenCV on your system? I remember you had to something funky, can you describe it? It's weird that ros-perception-vision-opencv pulls in OpenCV properly for AMD64, but not for the ARM64 build. Since the Jetson is ARM64, if we don't fix this issue here I doubt it'll build on the Jetson either.

Well it was more my cuda version and nvidia driver version that I had to mess around with a bunch. I forget what exactly I did for opencv so maybe it wasn't too crazy. Any thoughts on what to do?


Update css/style.css

I think we don't need to activate the scroll-bar on mobile browserd

Thanks.

Change the numbering too. I forgot to change.

Ok, will catch in a later tidy up.


Fixed Exception Caused By Privacy Policy URL in Crash Reporter

PR Details

Clicking the Privacy Policy link in the Crash Reporter will generate an exception.
Description

The Process requires shell execute to be enabled, this was the default setting in .NET Framework but is no longer the case with .NET Core.
This PR can be tested by adding the following to Main() in Stride.GameStudio/Program.cs,
            try
            {
                throw new Exception("Test");
            }
            catch (Exception ex)
            {
                HandleException(ex, 0);
            }

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[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

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Unrelated but the Crash Reporter form still uses Xenko images, I wasn't able to find the correct .xaml file in the solution to fix it.

Thanks !


Support proto3-suite 0.5.0 and later.

Starting with proto3-suite 0.5.0, the initial character of
a service method names is no longer forced to uppercase.

@Friede80, @jcarr-awake ,
prefixedMethodName was added by https://github.com/awakesecurity/proto3-suite/pull/171 (first appearing in proto3-suite 0.5.0) and used for service method names only, with prefixedFieldName still used for other things.  Apparently the desire is to make it possible for two methods of the same service to differ only in the case of the first letter of their method names.
I ran into a compilation failure in an Awake application of this library before making this change, because the Haskell spelling of at least one service method was wrong.
Regarding other uses of prefixedFieldName in grpc-mqtt: thanks for spotting that problem with this PR; I'll push up a change.

c346d5762b1cf8a3463a012eb77fcd1c98289b6a replaces the other uses of prefixedFieldName and isolates the conditional code to a compatibility module.

@Friede80 , I think the test failures were a legitimate concern.  I see two solutions: use the old name creation function for the functions that grpc-mqtt adds that are not in the .proto file, or just capitalize their names in the grpc-mqtt source so that both old and new versions of proto3-suite will produce the same compound name.  I adopted the latter solution in ab569abb53db78f2a4c724bed6b29ba1eeacaef3 .


无法在Win10系统下安装

怎么在windows下安装呢？Win10 GPU
(delta-pip-py3.6) C:\WINDOWS\system32>pip install delta-nlp
Looking in indexes: https://mirrors.ustc.edu.cn/pypi/web/simple, https://pypi.tuna.tsinghua.edu.cn/simple
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='mirrors.ustc.edu.cn', port=443): Read timed out. (read timeout=15)",)': /pypi/web/simple/delta-nlp/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='mirrors.ustc.edu.cn', port=443): Read timed out. (read timeout=15)",)': /pypi/web/simple/delta-nlp/
ERROR: Could not find a version that satisfies the requirement delta-nlp (from versions: none)
ERROR: No matching distribution found for delta-nlp

抱歉，当前不支持在Windows系统下直接使用。


Add section to Test Analytics docs for permissions

This PR adds basic information about using Buildkite permissions to manage Test Analytics access.

@meiqimichelle I have a strong fear we are going to have a merge conflict of a lifetime soon because of https://github.com/buildkite/docs/pull/1486 :D

@karensawrey 😬😬😬😬😬 but also, happy to use this PR for review, and then copy-and-paste into a new PR based on your EPIC restructure. This should only be one page, or a bit if info to place into other pages.

and then copy-and-paste into a new PR based on your EPIC restructure
No need for you to do it @meiqimichelle as it's already pre-planned that once my changes from #1486 are merged in, I'm going to start a new one based on it & copy and paste https://github.com/buildkite/docs/pull/1478 into it. So I guess, I'll just also copy and paste stuff from here into that new PR, too. Plz ping me once you've getting a thumbs up from @plaindocs on this one. Thanks!

Just triple-checking -- I should NOT merge this one outright, because @karensawrey is going to transfer this info somewhere else (and then we'll close this PR)?

@meiqimichelle go ahead and merge it - I'll pull in your changes into my PR that @plaindocs is yet to review.


Following list can be included in the Open Source Events.

Curated List of Open Source Programs, Events, and Competitions:
-Alibaba Summer of Code
-Bountiful Open Source Summer- BOSS
-ACM MM Open Source Software Competition
-NJACK Winter of Code
-OpenCode IIITA
-MDG Winter of Code
-BOSS - Bountiful Open Source Summer by Coding Blocks
-Microsoft Open Source Challenge
Thanks.

Thank You @garimasingh128

Hi, @garimasingh128 I just add some events from your list, please have a look. Remaining items for next time. Thank You @garimasingh128 Feel free to share with others.
Sharing information is also a contribution in open-source😇

Thank You @garimasingh128, please have a look updated repo.


Where the code to transform the original nuscene lidar point clouds to unified normative coordinate?

Hi
The coordinate of original nuscene lidar point clouds is x pointing right, y pointing forward. However, I can't find the code to explicitly transform the nuscene lidar coordinate to the unified normative coordinate as the documentation states.
The getitem method of nuscene
https://github.com/open-mmlab/OpenPCDet/blob/dadda9ed5c0f190d06856c6ec15d552116203947/pcdet/datasets/nuscenes/nuscenes_dataset.py#L117-L151
The get_sweep method of nuscene
https://github.com/open-mmlab/OpenPCDet/blob/dadda9ed5c0f190d06856c6ec15d552116203947/pcdet/datasets/nuscenes/nuscenes_dataset.py#L76-L109

same question...

@ideasplus @lihao0374 Have you solved?


AttributeError: module 'attr.validators' has no attribute 'gt'

$ pip list | grep pg-activity
pg-activity            3.4.0

$ ~/.local/bin/pg_activity
Traceback (most recent call last):
  File "/home/pasha/.local/bin/pg_activity", line 5, in <module>
    from pgactivity.cli import main
  File "/home/pasha/.local/lib/python3.10/site-packages/pgactivity/cli.py", line 12, in <module>
    from . import __version__, data, types, ui
  File "/home/pasha/.local/lib/python3.10/site-packages/pgactivity/data.py", line 13, in <module>
    from .types import (
  File "/home/pasha/.local/lib/python3.10/site-packages/pgactivity/types.py", line 28, in <module>
    from .config import Configuration, Flag
  File "/home/pasha/.local/lib/python3.10/site-packages/pgactivity/config.py", line 162, in <module>
    class UISection:
  File "/home/pasha/.local/lib/python3.10/site-packages/pgactivity/config.py", line 165, in UISection
    default=None, validator=validators.optional(validators.gt(0))
AttributeError: module 'attr.validators' has no attribute 'gt'

Thank you for the report; this has just been fixed in version 3.4.1.


Error when parsing type declaration in 0.4.0

julia> ts = Lexer.TokenStream("""
       type Foo
           name::AbstractString
       end
       """)
JuliaParser.Lexer.TokenStream(IOBuffer(data=UInt8[...], readable=true, writable=false, seekable=true, append=false, size=38, maxsize=Inf, ptr=1, mark=-1),1,nothing,nothing,false,false,"")

julia> Lexer.next_token(ts)
:type

julia> Lexer.next_token(ts)
:Foo

julia> Lexer.next_token(ts)
'\n'

julia> Lexer.next_token(ts)
:name

julia> Lexer.next_token(ts)
ERROR: cannot resize array with shared data
 in push! at ./array.jl:433
 in read_operator at /Users/tim/.julia/v0.4/JuliaParser/src/lexer.jl:368
 in next_token at /Users/tim/.julia/v0.4/JuliaParser/src/lexer.jl:752
 in next_token at /Users/tim/.julia/v0.4/JuliaParser/src/lexer.jl:768

This may be fixed in the 'master' version. Try Pkg.checkout("JuliaParser).
If this works, and the 'master' version is tagged as a release in the future, you can Pkg.free("JuliaParser") again.

I cannot reproduce this, so I assume it's fixed.


Fix core QueryApi indexers affected by boilerplate code bug

Describe the bug
Block 107918982 contains a function call to social.near with an empty data element. The boilerplate social indexer code did not check for this case. Several of the core social indexers (notifications, components, probably others) do not check for this case.
Link to Indexer
https://near.org/dataplatform.near/widget/QueryApi.App?selectedIndexerPath=dataplatform.near/n0
107960267 | Error running IndexerFunction:Cannot convert undefined or null to object
Fix needed

Correct code
start backfill from affected block

Additional context
Corrected code
if (
              !functionCall ||
              !functionCall.args ||
              !functionCall.args.data ||
              !Object.keys(functionCall.args.data) ||
              !Object.keys(functionCall.args.data)[0]
            ) {
              console.log(
                "Set operation did not have arg data in expected format"
              );
              return;
            }
            const accountId = Object.keys(functionCall.args.data)[0];

Updated the code in n0, components, moderation indexers.
Moderation had a try/catch around that section so had continued. verification indexer works on a different contract.
social_feed had the check already but had failed for a different reason. The QueryApi runner was restarted and social_feed caught up.


Upgrade tested Python version to 3.6

Codecov Report

Merging #1886 into master will increase coverage by 5.57%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1886      +/-   ##
==========================================
+ Coverage   83.63%   89.20%   +5.57%
==========================================
  Files          40       40
  Lines        2872     2872
  Branches      138      138
==========================================
+ Hits         2402     2562     +160
+ Misses        465      307     -158
+ Partials        5        3       -2

Impacted Files
Coverage Δ

tests/test_dcos_e2e/backends/docker/test_docker.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...sts/test_dcos_e2e/backends/vagrant/test_vagrant.py
0.00% <0.00%> (-100.00%)
:arrow_down:

tests/test_dcos_e2e/backends/aws/test_aws.py
72.22% <0.00%> (-15.44%)
:arrow_down:

tests/test_dcos_e2e/test_legacy.py
90.51% <0.00%> (-9.49%)
:arrow_down:

src/dcos_e2e/backends/_docker/_containers.py
95.00% <0.00%> (-5.00%)
:arrow_down:

src/dcos_e2e/backends/_docker/__init__.py
97.88% <0.00%> (-2.12%)
:arrow_down:

tests/conftest.py
98.21% <0.00%> (-1.79%)
:arrow_down:

...est_dcos_e2e/backends/docker/test_distributions.py
90.41% <0.00%> (-1.37%)
:arrow_down:

src/dcos_e2e/backends/_aws/__init__.py
97.61% <0.00%> (+0.79%)
:arrow_up:

src/dcos_e2e/_subprocess_tools.py
100.00% <0.00%> (+6.77%)
:arrow_up:

... and 5 more

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 8d5dc80...1e85ed6. Read the comment docs.


fix chrome 72 compatibility by binding storage methods

This will fix the issue reported in RESTED client at https://github.com/RESTEDClient/RESTED/issues/154
The code is also less verbose since both the local and sync drivers are created via the same code path.

Thanks for the PR @csimi, and sorry for the ridiculous response time to this issue! I completely missed that you sent this PR in May, very sorry about that :bowing_man:
I'll test this PR and see if I can merge it later today when I release a new version.

Thanks a lot for the contribution. Much appreciated!

No problem.
Could you please also look into releasing a new RESTED version with the updated dependency?
Thank you.


Fix export command usage

It seems export command gives wrong help message for specifying output directory.
C:\Users\myd7349>vcpkg export edflib --directory D:\edflib
error: unexpected switch: --directory
vcpkg export <port names> [--nuget] [--directory=out_dir]
vcpkg export zlib zlib:x64-windows boost --nuget
Options:
    ...

vcpkg export <port names> [--nuget] [--output-dir=out_dir]"

vs
vcpkg export <port names> [--nuget] [--output-dir=<dir>]"

Which one do you prefer?
Should I update other l10n files in locales folder or just leave to bot?

C:\Users\myd7349>vcpkg export edflib --directory D:\edflib
error: unexpected switch: --directory
vcpkg export  [--nuget] [--directory=out_dir]

Does the = make a difference?

C:\Users\myd7349>vcpkg export edflib --directory D:\edflib
error: unexpected switch: --directory
vcpkg export  [--nuget] [--directory=out_dir]

Does the = make a difference?

Still the same error:
C:\Users\myd7349>vcpkg export edflib --directory=D:\abc --zip
error: unexpected option: --directory=D:\abc
vcpkg export <port names> [--nuget] [--directory=out_dir]
vcpkg export zlib zlib:x64-windows boost --nuget

--output-dir, however, works in both cases:
C:\Users\myd7349>vcpkg export edflib --output-dir D:\abc --zip
The following packages are already built and will be exported:
    edflib:x64-windows
  * vcpkg-cmake:x64-windows
  * vcpkg-cmake-config:x64-windows
Additional packages (*) need to be exported to complete this operation.
Exporting vcpkg-cmake:x64-windows...
Exporting vcpkg-cmake-config:x64-windows...
Exporting edflib:x64-windows...
Creating zip archive...
Zip archive exported at: D:\abc\vcpkg-export-20240706-195740.zip
To use exported libraries in CMake projects, add -DCMAKE_TOOLCHAIN_FILE=[...]/scripts/buildsystems/vcpkg.cmake to your CMake command line.

C:\Users\myd7349>vcpkg export edflib --output-dir=D:\abc --zip
The following packages are already built and will be exported:
    edflib:x64-windows
  * vcpkg-cmake:x64-windows
  * vcpkg-cmake-config:x64-windows
Additional packages (*) need to be exported to complete this operation.
Exporting vcpkg-cmake:x64-windows...
Exporting vcpkg-cmake-config:x64-windows...
Exporting edflib:x64-windows...
Creating zip archive...
Zip archive exported at: D:\abc\vcpkg-export-20240706-195751.zip
To use exported libraries in CMake projects, add -DCMAKE_TOOLCHAIN_FILE=[...]/scripts/buildsystems/vcpkg.cmake to your CMake command line.


Example seems wrong

input.Select(family=>family.parents[0])
        .Where(familyName == "Wakefield");

This doesn't seem right.  Perhaps the Where clause should be parent => parent.FamilyName == "Wakefield"

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

ID: 7af26f57-f473-916a-bd4d-0918ef9eefcd
Version Independent ID: b553182a-4d34-96d6-219e-1abbd031c642
Content: LINQ to SQL translation in Azure Cosmos DB
Content Source: articles/cosmos-db/sql-query-linq-to-sql.md
Service: cosmos-db
GitHub Login: @timsander1
Microsoft Alias: tisande

@joshlang Thank you for reporting this issue.
I see that there is an open pull request from the community to fix this issue.
The changes should be live in the next 24 hours

@joshlang Thanks for pointing out the issue, the PR reference above from @Potapy4 has the fix. It should be merged by EOD.
We will now close this issue of there aren't further questions.
#please-close


Incorrect File Name

Kindly rectify the type in the name of the office home run file. It doesn't match with the training command

Which part? the config file? or the run file?

This

Thank you for pointing out this!
I have corrected it.


Update to deis base v0.3.6

v0.3.6 removed v0.3.5's High vulnerability, leaving 14 medium vulnerabilities. Red to orange!

Thanks @jwhitlock!


Update partitions limitations

We have a limitation of 2048 characters on partition rule length. Updating the same in the documentation. More Details - https://sumologic.slack.com/archives/C0P4K20RL/p1695810197382599
Purpose of this pull request
This pull request (PR) ...
Issue number:

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@sukhhanda1, we can merge your doc update as soon as PR #3123 is done adding your name to our .clabot file.

@kimsauce, the clabot verification step didn't happen for this PR. I set this PR to auto-merge, and the PR went ahead and merged even though PR https://github.com/SumoLogic/sumologic-documentation/pull/3123 hadn't added the contributor to the clabot file yet.

@kimsauce, the clabot verification step didn't happen for this PR. I set this PR to auto-merge, and the PR went ahead and merged even though PR #3123 hadn't added the contributor to the clabot file yet.

thanks for the heads up - i'll look into it