text:
[BUG] The corresponding address of https can be accessed, but the corresponding certificate of hertzbeat monitoring prompts UN_CONNECTABLE

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
ssl_cert monitoring availability alert, code is UN_CONNECTABLE

Expected Behavior
不告警
Steps To Reproduce
No response
Environment
HertzBeat version(s): 1.3.1

Debug logs
No response
Anything else?

I have solved the problem ，my DNS server is ERROR

repo: dromara/hertzbeat


text:
Enhance shenyu-plugin-dubbo module unit test

Task
Task List:

[ ]  Enhance shenyu-plugin-alibaba-dubbo module unit test，make its coverage rate is more than 80%
[ ] Enhance shenyu-plugin-apache-dubbo module unit test，make its coverage rate is more than 80%
[ ] Enhance shenyu-plugin-dubbo-common module unit test，make its coverage rate is more than 80%

Please read the Contribution Guideline before submitting the PR

I want shenyu-plugin-dubbo-common task

Please assign shenyu-plugin-apache-dubbo to me.

Please assign shenyu-plugin-alibaba-dubbo  task to me.

source: gharchive/issue

authors: ttttangzhen wyc192273 yiwenlong

repo: dromara/shenyu

license_type: permissive

license_source: github-api


text:
Port the auto tag feature from docker plugin

Support the feature in the "Autotag" section of docker plugin.
The logic is forked from https://github.com/drone-plugins/drone-docker code base with necessary modification. I've tested it e2e for DockerHub on my Drone server via this plugin image https://hub.docker.com/repository/docker/15cm/drone-kaniko, for both tag pushes and commit pushes.
With this change the .drone.yml in this repo should work as intended.
Other changes:

Rename the existing "auto tag" flags/code to "expand tag" for a less misleading naming.
ATTENTION: make a breaking change to set default value of "--tags" to empty.
Rationale is to expect most users to use the auto tagging feature. When power users want to specify tags, they should always explicitly set tags instead of being surprised by the default "latest" tag.

We cannot make any breaking changes until and unless they are security vulnerabilities. Auto tag was already supported in this plugin. Can you update what functionality was earlier missing for auto-tags?

The existing auto tag feature behaves differently from the auto tag feature of the drone docker plugin. Comparison:

The current auto tag requires users to specify the tag in the CLI argument. It expands the tag into several tags following semantic versioning.
The new auto tag in this PR automatically detect the tag without a user provided tag. Then expand it following semantic versioning.

The reason I make breaking change on the AUTO_TAG flag instead of creating a new flag is that, the current auto tag is not "auto". I have to specify the tag, which means an update of .drome.yml per tag push. Moreover, as a user who comes from the drone docker plugin (I believe I'm not the only one) that supports the auto tag feature that behaves the same as this PR, I was surprised by the behavior of the current auto tag feature and struggled to see if it could auto detect the tag of git commits.
In summary, I think the current auto tag feature:

diverges from the drone docker plugin which will surprise many users.
doesn't suit the AUTO_TAG name well given that we have a way to auto detect the tag from git commit (what I do in this PR).

Thanks a lot @15cm for your contribution.

Thanks for taking care of this PR @shubham149. Sorry a link in the README added by this PR is malformatted. I created another PR as a minor fix https://github.com/drone/drone-kaniko/pull/38.

source: gharchive/pull-request

repo: drone/drone-kaniko


text:
trusted builds from private repo or non pull requests can run under privileged mode

fixes issue #849 in 0.3.0.
Notice that this introduces a break change where privileged mode is determined by both privileged mode in repo setting and privileged in .drone.yml.

@shawnzhu thanks for putting some time into this. I think we can find a way to meet your needs, however, I do have some security concerns. The below change means that any public repository using privileged mode would be open to a malicious pull request. I'm not sure we want to expose existing Drone projects to a new attack vector when they may be relying on the existing behavior.
-Privileged: (b.Privileged && len(b.Repo.PR) == 0)
+Privileged: (b.Privileged && script.DockerPrivileged(b.Build.Docker)),

I therefore suggest the following change:
-Privileged: (b.Privileged && len(b.Repo.PR) == 0)
+Privileged: (b.Privileged && (len(b.Repo.PR) == 0 || b.Repo.Private)),

The above change enables privileged mode for pull requests if the repository is private. I think we can safely assume that team members with access to private projects can be trusted (otherwise they wouldn't have access). This also continues to prevents an attacker from issuing a malicious pull request to an open source repository. Hopefully this change would still meet your needs ...
Lastly, I'd prefer not to introduce breaking changes in 0.3 yaml. The tty change that we merged did not impact existing projects. Moving privileged to the yaml impacts every project using privileged mode. I'd prefer to push breaking changes to the next release unless absolutely necessary.
Please let me know your thoughts. I am very appreciate you rolled up your sleeves and dug into the code :)

What about privileged mode for pull requests if the author is a well known user for drone? :)

authors: bradrydzewski shawnzhu tboerger

repo: drone/drone


text:
fly_mission and fly_qgc_mission examples freezes on mission accepted

The future does not appear to be returning with mission uploaded.
hamish@hamish-ThinkPad-T470:~/github/dronecore/2test/DroneCore/example/fly_mission/build$ ./fly_mission udp://:14540
Waiting to discover system...
[04:48:15|Info ] New device on: 127.0.0.1:14557 (udp_connection.cpp:208)
[04:48:15|Debug] New: System ID: 1 Comp ID: 1 (dronecore_impl.cpp:286)
[04:48:15|Debug] Component Autopilot added. (mavlink_system.cpp:330)
[04:48:15|Debug] Found 1 component(s). (mavlink_system.cpp:462)
[04:48:15|Debug] Discovered 4294967298 (mavlink_system.cpp:464)
Discovered system with UUID: 4294967298
Waiting for system to be ready
[04:48:15|Debug] We got an ack: 520 (mavlink_commands.cpp:140)
[04:48:16|Debug] We got an ack: 511 (mavlink_commands.cpp:140)
System ready
Creating and uploading mission
Uploading mission...
[04:48:16|Debug] Send mission item 0 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 1 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 2 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 3 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 4 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 5 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 6 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 7 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 8 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 9 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 10 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 11 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 12 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 13 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 14 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 15 (mission_impl.cpp:904)
[04:48:16|Debug] Send mission item 16 (mission_impl.cpp:904)
[04:48:17|Debug] Send mission item 17 (mission_impl.cpp:904)
[04:48:17|Debug] Send mission item 18 (mission_impl.cpp:904)
[04:48:17|Debug] Send mission item 19 (mission_impl.cpp:904)
[04:48:17|Debug] Send mission item 20 (mission_impl.cpp:904)
[04:48:17|Debug] Send mission item 21 (mission_impl.cpp:904)
[04:48:17|Debug] Send mission item 22 (mission_impl.cpp:904)
[04:48:17|Info ] Mission accepted (mission_impl.cpp:162)

At this point waits forever. I am getting messages "manual control lost" that I can't seem to get rid of, but I don't think that is the cause.

@hamishwillee is this the latest latest? I just tested this yesterday and it worked multiple times.

Yes, it was the latest latest, against the latest latest PX4 firmware. The other examples worked fine.

Oh, that's the example and not the integration test. Sorry, I'll test that one then next.

I'm running into another problem:
Waiting for system to be ready
System ready
Creating and uploading mission
Uploading mission...
[11:03:21|Warn ] Mission handling timed out while uploading mission. (mission_impl.cpp:1058)

Maybe something with the mission handling changed (broke?) in the firmware.

Nevermind, the integration test works, so this is something about the example.

So, the example works just fine on my Fedora Linux but stalls on macOS.
@hamishwillee when I ask latest latest, I mean: have you made sure that you have built and installed the latest?

Ok, after debugging this for several hours, I found that I had leftover library files in /usr/local/lib/.
Once I cleaned it up, did make clean, it all worked fine.
sudo rm -rf "/usr/local/lib/libdrone*"
make clean
make default
sudo make default install
(cd example/fly_mission && rm -rf build && mkdir build && (cd build && cmake .. && make && ./fly_mission udp://))

latest latest, I mean: have you made sure that you have built and installed the latest?

I would have said yes, but when I tried this again with a clean build, it is indeed working. I didn't have to delete "/usr/local/lib/libdrone*".
I almost wish it hadn't worked so I would feel like I hadn't wasted your time. Sorry!

No worries, thanks @hamishwillee!

authors: hamishwillee julianoes

repo: dronecore/DroneCore

license_source: bigquery


text:
Streaming from dronekit python

Hi all,
I am facing an issue while streaming data from pixhawk using dronekit. I am using PX4 firmware. (I have also tried streaming using ardupilot). I am simultaneously accessing the vehicle through QGroundControl and Dronekit-python using the output udp ports specified in mavproxy. Then I try to stream the GPS_RAW_INT data.
Using the Mavlink Inspector widget in QGroundControl, I can see that the values in the GLOBAL_POSITION_INT, GPS_RAW_INT and other mavlink messages changing values in time. However, when I try to stream the same values using dronekit-python, it streams the values same as the mavlink inspector for a few seconds and then becomes constant(flat plot). I am accessing the values by simply calling the methods available for the vehicle object, for example, 'vehicle.location.global_relative_frame.lat'.
Does anyone have any idea why this could possibly happen?
Thanks in advance.
Regards,

The discussion in issue #812 may be of interest.

authors: GitRevisionGandalf pietrodn

repo: dronekit/dronekit-python


text:
[do not merge, 6.4.x] Reproducer for JBPM-5330 and JBPM-5331

To simulate the issue run integration tests with this command: mvn clean install -Peap64x -Deap64x.download.url="insert EAP URL" -Dkie.server.version=6.5.0-SNAPSHOT
Cannot be run on WildFly due to changes in ee7 war to support WildFly10

jenkins retest this

I believe this can be closed based on the backward compatibility discussion we had, correct?

Closing as we should not need it anymore. Please reopen in case I missed something.

authors: mswiderski psiroky sutaakar

repo: droolsjbpm/droolsjbpm-integration


text:
Redundant condition

there are redundant ternary operators in NearbySelectionConfig

I'm not an OptaPlanner developer so will wait for Geoffrey de Smet.. but the data-type is an Integer and there's no check for it being null prior to the lines you're changing so why is the null check a redundant term?

https://github.com/snurkabill/optaplanner/blob/redundancy2/optaplanner-core/src/main/java/org/optaplanner/core/config/heuristic/selector/common/nearby/NearbySelectionConfig.java#L197
on this line, we determine if linear distribution is enabled. and then we have condition:
} else if (linearDistributionEnabled) {
int sizeMaximum = linearDistributionSizeMaximum == null ? Integer.MAX_VALUE : linearDistributionSizeMaximum;
where "linearDistributionSizeMaximum == null" is redundant, because the information is already stored in linearDistributionEnabled boolean value.

Agreed. Good found (there might be more valid ones in findbugs or IntelliJ inspection, keep any you think are valid coming).
But I need to add support for nearbySelectionType (which I will do now on master so we're not stuck in a limbo state), which will make that null check required. Once that's pushed, I 'll reference that commit here and I 'll close this PR without merging.

Fixed alternatively, by adding NearbySelectionDistributionType:
https://github.com/droolsjbpm/optaplanner/commit/cb288f817f048f90ad8037f3d93503873605c758

authors: ge0ffrey manstis snurkabill

repo: droolsjbpm/optaplanner


text:
Generated C++ and ObjC interface with --ident-cpp-type formatting set to non-default fails to compile

An easy way to reproduce is to take the token.djinni from the test-suite:
token = interface +c +j +o {
whoami() : string;
}
Then modify test-suite/run_djinni.sh to have pass "--ident-cpp-type foo_bar". You will notice that the proxy class in the DBToken+Private.mm generated will be of ObjProxy type, but the toCpp/fromCpp functions will try to get it from the DbxObjcWrapperCache as a "objc_proxy".
My knowledge of scala is limited but it seems in ObjcppGenerator.scala, that it always generates the proxy class name as ObjcProxy, but when it generates the code the DbxObjcWrapperCache lookup, it uses objcppMarshal.helperClass("objc_proxy") which returns objc_proxy incorrectly.
Should that just be ObjcProxy instead of objc_proxy, since it's already being generated as ObjcProxy elsewhere?

Note changing the objcppMarshal.helperClass("objc_proxy") calls to objcppMarshal.helperClass("ObjcProxy") does fix the problem for me...

The name of that proxy should not depend on identifier styles because it's only ever seen by auto-generated code. So the proper approach is to hardcode ObjcProxy.

authors: jrogers mknejp

repo: dropbox/djinni


text:
When testing JSON serialization, whitespace is not ignored

In the Testing Docs, there is a note: The comparison is done via a normalized JSON string representation, so whitespace doesn’t affect the results.
However, when testing serialization, I get a Comparison Failure: org.junit.ComparisonFailure:  ... 	at com.example.core.user.SubscriberTest.serializesToJSON(SubscriberTest.java:64)
Test Code
@Test
public void serializesToJSON() throws Exception {

    assertThat(MAPPER.writeValueAsString(user))
            .isEqualTo(fixture("fixtures/Subscriber.json"));
}

Subscriber.json
{
  "email": "test@example.com",
  "password": "1234567890",
  "displayName": "Test User",
  "role": "SUBSCRIBER",
  "added": 1400429532000000,
  "modified": 1400429532000000,
  "id": 1,
  "emailConfirmed": true,
  "active": true
}

Differences
I used IDEA to check the differences
Whitespaced not ignored
When I set IDEA to not ignore whitespace, it shows that there is a difference:

Whitespace ignored
When I set IDEA to ignore all whitespace, it shows that there is no difference:

You shouldn't be comparing the strings, you should be comparing the object representations. See the code in the example:
http://www.dropwizard.io/manual/testing.html#testing-serialization

authors: MarkyC carlo-rtr

repo: dropwizard/dropwizard


text:
Consider using bonjour to advertise sites hosted by ddev

What happened (or feature request):
This would sidestep the hosts file editing, and also not require fiddling with DNS setups on users' machines. Avahi/Zeroconf/Bonjour would allow us to advertise the presence of sites hosted by ddev and allow users to connect to them with "sitename.local"
We did something similar for Aegir a while back: https://github.com/GetValkyrie/provision_avahi (publish.py is the file to look at there).
What you expected to happen:
How to reproduce this:
Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.
Anything else do we need to know:
Related source links or issues:
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

@cweagans supported on Windows and Linux as well?

I believe so. I know for sure it works on Linux. Can't say for sure on Windows

Cool. Ultimately, we want to make sure we're supporting all 3 OSes equally and we don't want to necessarily maintain separate, OS-specific solutions for a given feature unless the gains outweigh the additional costs. This is certainly a problem that we've been wanting to address for a long time, notably to reduce a potential security risk. Therefore, I anticipate that we'll be evaluating our options sooner than later and I'll add this to the mix. Thanks!

ngrok has been suggested many times for this sort of functionality as well - https://ngrok.com/

IMO this is too much of a Mac-specific approach; to date we're trying to avoid any OS-specific approaches, so closing this for now.

authors: beeradb cweagans rfay rickmanelius

repo: drud/ddev


text:
Add docker-php-ext-* helper tools for odd php extensions, fixes #2987 [skip ci][ci skip]

The Problem/Issue/Bug:
#2987 proposes adding docker-php-ext-* scripts to the web container to make it easy to add non-mainstream build-from-source php extensions.
How this PR Solves The Problem:
Adds the scripts... but there's more to be done to make them work. And I imagine they're not useful without build-essential, which I probably wouldn't add because of size.
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

I ran into some trouble with this because there are obviously missing steps before you can use these tools. Anyway, this build has the scripts in it.
You can try it out with docker run -it --rm drud/ddev-webserver:20210625_docker-php-ext bash and do whatever you'd like to do. Help me understand what's missing. Show me a set of steps that will successfully use this for the currently-configured PHP version.
Thanks for your help @StudioMaX

That would be great.
As far as I understand, now the scripts are just downloaded from the original repository at build-time. In my opinion, it would be more correct to make copies of these scripts in your repository with the same names, adapt them, and when we run each script, add some pre-initialization script to download the PHP sources with the required version (depending on the DDEV config), and install all the necessary dependencies.
Unfortunately I am not familiar with the internals of DDEV build scripts, but as I understood most of the steps can be taken from the original Dockerfile.

And I imagine they're not useful without build-essential, which I probably wouldn't add because of size.

Can it just be installed the first time when someone execute docker-php-ext-* scripts?

You don't need to know anything at all about ddev and its build scripts. As I said above, you just need to run docker run -it --rm drud/ddev-webserver:20210625_docker-php-ext bash and figure out how to use the scripts. If you figure that out, I'll add the necessary prereqs to the Dockerfile. But I think it will be way too heavyweight :(

Sure, I tried using your test image by running docker run -it --rm drud/ddev-webserver:20210625_docker-php-ext bash and ran into the same error as yours.
# docker-php-ext-install iconv
tar (child): /usr/src/php.tar.xz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

First, I downloaded archive with sources itself by manually executing the same commands from the original dockerfile:
https://github.com/docker-library/php/blob/541ab0e70f98cc3efce08ead9548285c984d6d33/7.4/buster/fpm/Dockerfile#L66-L98
After that, a new error occurred:
# docker-php-source extract
tar (child): xz: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

I realized that by default tar does not support unpacking xz archives at all, so I installed the xz-utils package (it was also mentioned in the original Dockerfile). After that, the archive was successfully unpacked using the sudo docker-php-source extract command. Then it became difficult to understand, since the scripts just don't find the dependencies they need. For example,
# docker-php-ext-configure gd
/usr/local/bin/docker-php-ext-configure: 68: /usr/local/bin/docker-php-ext-configure: phpize: not found
root@7b548e4b48c4:/usr/src# phpize
bash: phpize: command not found

phpize was not found, since in the original Docker PHP images PHP is built from source, but in our case it is just installed from the official repositories without dev-packages.
Therefore, I assumed that we would need some additional script (if we won't require all this stuff with the standard DDEV-PHP Docker images) that, depending on the DDEV config, will install the required php-dev package (for example php7.4-dev which contains phpize and header files) and all needed dependencies (xz-utils, etc).
If you're wondering how these scripts work together in a final Dockerfile, here's an example (Some dev packages of the libraries are unnecessary as this is only part of the Dockerfile):
RUN apt-get update && apt-get install -y \

        libfreetype6-dev \
        libjpeg62-turbo-dev \
        libmcrypt-dev \
        libpng-dev \
        zlib1g-dev \
        libbz2-dev \
        libxslt-dev \
        libicu-dev \
        libcurl3-dev \
        libc-client-dev \
        libkrb5-dev \
        libedit-dev \
        libxslt1-dev \
        libreadline6-dev \
        libtidy-dev \
        libxml++2.6-dev \
        g++ \
        unixodbc-dev \
        libxml2-dev \
        libaio-dev \
        freetds-dev \
        libssl-dev \
        openssl \
        curl \
        bzip2 \
        libfontconfig1 \
        libfontconfig1-dev \
        libzip-dev \
    && docker-php-ext-install -j$(nproc) iconv \
    && docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ \
    && docker-php-ext-install -j$(nproc) gd \
    && pecl install redis-3.1.1 \
    && pecl install xdebug-2.7.2 \
    && docker-php-ext-enable redis xdebug \
    && docker-php-ext-configure imap --with-imap --with-imap-ssl --with-kerberos \
    && docker-php-ext-install bcmath bz2 curl dom fileinfo gettext imap intl json \
        mbstring mysqli pcntl pdo pdo_mysql phar posix readline session \
        shmop simplexml soap sockets tidy tokenizer xml zip \
    && pecl install apcu \
    && pecl install apcu_bc-1.0.4 \
    && docker-php-ext-enable apcu --ini-name 10-docker-php-ext-apcu.ini \
    && docker-php-ext-enable apc --ini-name 20-docker-php-ext-apc.ini

It actually sounds like the original approaches as suggested in https://github.com/drud/ddev/issues/2987#issuecomment-831855689 are more appropriate, true?

This will be a great project for ddev-contrib, but it's not appropriate for the huge image size increase that would result from adding it. I didn't realize how much beyond the scripts was required.

authors: StudioMaX rfay


text:
Overlord Exception While Announcing Segments

Hi,
We are facing an exception in overlord in a production environment while announcing the Historical Segment.
It looks to me some sort of multi-threading issue (if thats possible ) as the segment is already present in the MetaData and still the "segmentExists"  method (IndexerSQLMetadataStorageCoordinator.java+581) is returning "FALSE" on some of the times .
We are using druid-0.9.1 in our production.
Following is the Logs :
2017-08-08 06:15:02.534+0000 INFO  io.druid.metadata.IndexerSQLMetadataStorageCoordinator Found [prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] in DB, not updating DB
2017-08-08 06:15:01.692+0000 ERROR io.druid.metadata.IndexerSQLMetadataStorageCoordinator Exception inserting segment[prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] into DB
org.skife.jdbi.v2.exceptions.UnableToExecuteStatementException: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "druid_segments_pkey"
...
Detail: Key (id)=(prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5) already exists.
Show all 89 lines
2017-08-08 06:15:01.690+0000 INFO [qtp1997290658-83] io.druid.metadata.IndexerSQLMetadataStorageCoordinator Published segment [prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] to DB
In above logs it is clear the the segment [prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] has already been inserted in the postgres (metadata) but still overlord throws an exception. Also the very first line (after around 1 minute difference), "segmentExists"  would have returned true.
Note the time between last two logger lines , hardly in milliseconds.  Is it possible that two thread would have come at this method (announceHistoricalSegment) and executed segmentExists without knowing about each other (Race Condition)
More Details : https://groups.google.com/forum/#!topic/druid-user/8hFWfsD6THk

@praveshg, do you know if this is still an issue in the latest version?

Hi, I'm experiencing the same issue except that I use mysql.
Race conditions seems as reasonable explanation due to random nature of the error occurrence.
In my case, this started happening after I increased task.replicants in tranquility from 1 to 2.
Now we have two worker tasks for each hour.
Druid version: druid-0.9.1.1
Anyone else experiencing this or have a solution?

authors: david-benes gianm praveshg

repo: druid-io/druid


text:
Restorable indexing tasks

Some changes that make it possible to restart tasks on the same hardware.
This is done by killing and respawning the jvms rather than reconnecting to existing
jvms, for a couple reasons. One is that it lets you restore tasks after server reboots
too, and another is that it lets you upgrade all the software on a box at once by just
restarting everything.
The main changes are,

Add "canRestore" and "stopGracefully" methods to Tasks that say if a task can
stop gracefully, and actually do a graceful stop. RealtimeIndexTask is the only
one that currently implements this.

Add "stop" method to TaskRunners that attempts to do an orderly shutdown.
ThreadPoolTaskRunner- call stopGracefully on restorable tasks, wait for exit
ForkingTaskRunner- close output stream to restorable tasks, wait for exit
RemoteTaskRunner- do nothing special, we actually don't want to shutdown

Add "restore" method to TaskRunners that attempts to bootstrap tasks from last run.
Only ForkingTaskRunner does anything here. It maintains a "restore.json" file with
a list of restorable tasks.

Have the CliPeon's ExecutorLifecycle lock the task base directory to prevent a restored
task and a zombie old task from stomping on each other.

jdk8 DruidCoordinatorTest.testCoordinatorRun:349 expected:<1> but was:<0>

After these changes, what is the behaviour of task logs ?
Do they get uploaded to s3 on each restart with diff file name or the new logs will override prev logs ?
or they get appended to the same file and finally when the task completes/fails they are uploaded to S3 ?

@nishantmonu51 they get uploaded to S3 on each restart, with new uploads overriding previous uploads. The FTR opens the log in "append" mode so each upload will contain logs from all previous runs of the same task.

@nishantmonu51 I do think that in the future we should make the uploading happen in chunks rather than all at once- but this would be a different PR

@himanshug @nishantmonu51 @drcrallen pushed a new commit, the main change is in firehose-closing behavior. also looking at adding some tests.

hmm, I think there's a further problem. If you don't close the kafka firehose, and no new data is forthcoming, I believe it will block forever on hasMore. I don't think there's anything we can do about that right now, but that points to potentially wanting to have a timeout on hasMore or a poll-style Firehose interface.

What that means is that if you do try to stopGracefully a realtime task reading from a dry kafka firehose, it will likely time out and be killed after the gracefulShutdownTimeout (default 5 minutes)

@himanshug @nishantmonu51 @drcrallen @guobingkun pushed updates for outstanding comments + also some unit tests for restoring realtime tasks

Overall :+1: for me once is considered.

Overall :+1: for me once https://github.com/druid-io/druid/pull/1881#discussion_r44506222 is considered.

@drcrallen @himanshug updated the branch with changes from code review

we've been using this internally for awhile, seems to work

:+1: with the changes too

would be great to add some integration tests for this feature.

authors: fjy gianm himanshug nishantmonu51 xvrl


text:
trying to fix transient errors in testRealtimeIndexTask() by increasing

... overall timeout and unlimited wait for segment publish
see example failure in https://travis-ci.org/druid-io/druid/jobs/98035374

:+1:


text:
[Fix] Remove data type and InputRowParser type bindings

see issue #190
Some warnings of type erasure are mentioned by compiler, seems ok. Tested with local kafka+tranquility+druid, any suggestion to write a reasonable test ?

@du00cs this test is failing in Travis: "Druid standalone - From config file - ByteBuffer type (CSV with ParseExceptions) *** FAILED ***". Does it work for you?

I will try to fix it soon.

@gianm  I checked again and both jdk7 and jdk8 pass the test. Something wrong with the CI?

@du00cs hmm, maybe, let me try running it again.

Looks like that was just the CI being flaky, the tests pass now. thx @du00cs

👍

repo: druid-io/tranquility


text:
Improved storybook integration.

Is your feature request related to a problem? Please describe.
As a project maintainer I want the Storybook integration to be readily accessible in the demo so I can demonstrate the integration,
Describe the solution you'd like

[x] Add static storybook build to demo.

Describe alternatives you've considered
N/A
Additional context
Would be great to have a link to the Storybook on the Druxt demo site, in a "About Druxt" section.

https://storybook.demo.druxtjs.org

license: MIT


text:
Provide explicit initialize arguments if super method doesn’t take any

This returns better feedback (an ArgumentError exception) if the user provides an unknown argument.
Resolves #16

Alright, this is looking good to go. I'll merge this into master now.
Now that this injection.rb has become so long, I think the next step will be to refactor each strategy (args, hash, kwargs) out into their own classes, then have a "strategies" container to hold them all (like how I handle dry-transaction's step adapters). I'll try get this done in the next few days and then we should be in a much nicer spot for a release.


text:
Bug: Reader::CommonLisp doesn't work as documented

Describe the bug
The README claims that Reader::CommonLisp treats special atoms specially:
SXP::Reader::CommonLisp.read %q((or t nil))          #=> [:or, true, nil]

However, in practice, Reader::CommonLisp doesn't map Lisp t and nil to Ruby true and false; it just treats them like any other atoms and converts them to Ruby symbols:
irb(main):008:0> SXP::VERSION.to_s
=> "1.2.2"
irb(main):009:0> SXP::Reader::CommonLisp.read %q((or t nil)) # the same example from the README
=> [:or, :t, :nil]
irb(main):010:0> RUBY_VERSION
=> "2.7.1"

I think this is a bug. Either the documentation or the gem should be updated.

@marnen, see if PR #22 solves the issue. It adds case-insensitive atoms 't' and 'nil'. I didn't see any other such tokens defined in CommonLisp beyond those defined in the Basic reader.

Thanks, I’ll look. I think it’s probably more sensible to have Lisp nil map to Ruby nil than to false…

Thanks, I’ll look. I think it’s probably more sensible to have Lisp nil map to Ruby nil than to false…

The are both Falsey, so that would be fine.

My thoughts exactly. The falsiness of Ruby nil means that the Common Lisp ambiguity between nil and false is OK, if not great.

Thank you for fixing this! For future reference, though, this was probably a breaking change, so I'm not sure it should have been a patch release (although it was a bugfix).
BTW, I appreciate this gem so much. I'm using this on a project that I'm translating from Lisp to Ruby, so it's coming in handy for constructing Lisp expressions and parsing Lisp output in my RSpec tests.

authors: gkellogg marnen

license: unlicense


text:
Adding box-shadow property, removing '$0' and adding max-(width/height)

Adding a box-shadow property as I keep having to Google the parameter order, bonus that this also addresses one of the three support issues https://github.com/dsandstrom/atom-css-snippets/issues/18
Default parameter outputs put a Material Design-style card shadow emphasising the container "floating".
Also outputs a comment at the end of the line with the parameters for reference.

Also addressed:
https://github.com/dsandstrom/atom-css-snippets/issues/17
by removing the trailing '$0' at the end of snippets; tested on latest Atom with no issues

Aaand just addressed https://github.com/dsandstrom/atom-css-snippets/issues/19 by adding max-width and max-height!

Awesome work.  I added some inline comments.

Have committed some adjustments based on your feedback!

Thanks @neromaki

authors: dsandstrom neromaki

repo: dsandstrom/atom-css-snippets

license: mit


text:
onClick event in actions don't seem to work

onClick event is not working? ISSUE: #9

this might be related to this: #164
a lot of the events dont appear to be firing like they should anymore.

authors: subratawebops tmburnell


text:
parallel performance with OpenMP

Describe the bug
Parallel performance with OpenMP is severely degraded wrt serial.
To Reproduce
Steps to reproduce the behavior:
I run the same test case (cavity-amr) in serial and parallel.
I configured with
-DUSE_ACC=OFF
-DUSE_OMP=ON

I tested the parallel performance with several applications and poses to try to understand why the parallel runs are much much slower, but to no avail.
Do you have any idea why this happens?
Should I try to activate USE_ACC in the configuration?
Expected behavior
At least similar performance, if not an improvement in computational time.
Screenshots
$> time ./test.sh -n 1 -c examples/cavity-amr/cavity > cavity-amr-serial.log

real    0m1.364s
user    0m5.955s
sys     0m0.170s
$> time ./test.sh -n 2 -c examples/cavity-amr/cavity > cavity-amr-omp.log

real    44m6.228s
user    515m37.217s
sys     0m21.519s

Desktop (please complete the following information):

OS: OpenSUSE
Version: Leap 15.5

Additional context
None

Hi @capitalaslash
I think there are several factors at play here

You don't need to compile with -DUSE_OMP=ON to test MPI parallelization so you can use the default build
The cavity example does not have enough number of cells to show speedup either for the MPI or OpenMP implementation, but it shouldn't take 44 min.

Note that when you use the MPI+OpenMP combo by turning on -DUSE_OMP=ON, the number of threads specified is per MPI rank. So make sure you set OMP_NUM_THREADS to a specific value first. I think if that is not set it may try to assign all available threads to each MPI rank thus severely degrading performance. MPI is recommended for most applications since it is faster than OpenMP implementation (as is the case in other CFD codes as well), but it may help to reduce MPI communication overhead and improve scalability when very large number of MPI ranks are used which is not the case for most people.
What I suggest is to first test the MPI implementation using the default build steps outlined
    mkdir build && cd build
    cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=.. ..
    make && make install

You can then test by setting different values to the -n option of the test.sh script. Don't have to worry about setting OMP_NUM_THREADS. You should get reasonable times in all cases, but I am certain the MPI runs will be slower for this simple test case that does not have enough number of grid points to show scalability.
Then, to test the OpenMP vs MPI implementation, make another build
    mkdir build-omp && cd build-omp
    cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=.. -DUSE_OMP=ON ..
    make && make install

When running the OpenMP build make sure to set -n 1 since that specifies the number of MPI ranks. Then before calling the script make sure to set export OMP_NUM_THREADS=1 or 2 or .... The OpenMP implementation will certainly be slower than the MPI implementation but it has its value in MPI+OpenMP mode with very large number of MPI ranks.

Here are some test runs to test the scalability of the MPI version first, the first build.
Let us use the cavity test case (not the amr one for this one). Modify examples/cavity/cavity file to increase the number of grid cells from 20x20 to 100x100 as follows
-8{0 1 2 3 4 5 6 7} linear 3{20 20 1}
+8{0 1 2 3 4 5 6 7} linear 3{100 100 1}

Run single MPI rank run
$ ./test.sh -n 1 -c examples/cavity/cavity
...
9018 [0] Time 5.000000
9025 [0] SYMM-FULL-SSOR-PCG :Iterations 1 Initial Residual 1.47888e-11 Final Residual 1.14971e-11
9027 [0] SYMM-FULL-SSOR-PCG :Iterations 1 Initial Residual 1.44703e-11 Final Residual 1.12991e-11
9073 [0] Exiting application run with 1 processes

Takes about 9073 milliseconds
Run 2-mpi ranks
$ ./test.sh -n 2 -c examples/cavity/cavity
....
4623 [0] Time 5.000000
4626 [0] SYMM-FULL-SSOR-PCG :Iterations 1 Initial Residual 3.55206e-11 Final Residual 3.16645e-11
4628 [0] SYMM-FULL-SSOR-PCG :Iterations 1 Initial Residual 3.38580e-11 Final Residual 3.00837e-11
4672 [0] Exiting application run with 2 processes

Takes about 4672 milliseconds for a speedup of  1.94x out of 2 which is good.

Lets do the same with the OpenMP implementation. Make sure to build-omp build
cd build-omp && make install

Then we set number of threads to 2
export OMP_NUM_THREADS=2

We can now run the test case with 1 mpi rank
$ ./test.sh -n 1 -c examples/cavity/cavity
....
6686 [0] Time 5.000000
6691 [0] SYMM-FULL-SSOR-PCG :Iterations 1 Initial Residual 1.47888e-11 Final Residual 1.14971e-11
6693 [0] SYMM-FULL-SSOR-PCG :Iterations 1 Initial Residual 1.44703e-11 Final Residual 1.12991e-11
6739 [0] Exiting application run with 1 processes

It took about 6739 milliseconds. It is slower than the MPI implementation but still faster than the serial implementation with a speedup of 1.34x times.
I hope this helps. Please let me know if you encounter additional issues.
Daniel

@capitalaslash I have now added basically what I described above in the README file so that others will not be confused by it. Thank you!

Ok, so I was already running with OpenMP on all my cores and oversubscribing with MPI led to the degraded performance.
Thank you for updating the description, it is now much clearer in my opinion.
This issue can be closed.

authors: capitalaslash danielabdi-noaa

repo: dshawul/NebulaSEM


text:
Excellent work

Thank you very much. Your project works great. Good job!

Thanks!

authors: DamienCassou dsifford

repo: dsifford/yarn-completion


text:
[moved] Table.drop sounds like it will mutate and has an out-of-date docstring

Prof. DeNero:

When I see drop, I think it's going to change the table like del.

Looks like pandas calls it drop too, so let's leave it. I fixed the docstring.

authors: alvinwan papajohn

repo: dsten/datascience


text:
CSS for docs not working; suspect DNS issue

http://data8.org/datascience/
Shows that the CSS isn't loading. I suspect this is because dsten.github.io is getting automatically redirected to data8.org but the asset files aren't being redirected properly. @papajohn any thoughts?

How did you publish? I would suggest just checking the whole docs directory
into https://github.com/dsten/dsten.github.io unless that poses a problem.
All the files should be served then.
On Tue, Sep 8, 2015 at 11:13 PM, Sam Lau notifications@github.com wrote:

http://data8.org/datascience/
Shows that the CSS isn't loading. I suspect this is because
dsten.github.io is getting automatically redirected to data8.org but the
asset files aren't being redirected properly. @papajohn
https://github.com/papajohn any thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/59.

Oh gotcha. I pushed to the gh-pages branch on the datascience library
itself. Will toss the docs directory into the dsten repo instead.
On Tue, Sep 8, 2015 at 11:45 PM John DeNero notifications@github.com
wrote:

How did you publish? I would suggest just checking the whole docs directory
into https://github.com/dsten/dsten.github.io unless that poses a problem.
All the files should be served then.
On Tue, Sep 8, 2015 at 11:13 PM, Sam Lau notifications@github.com wrote:

http://data8.org/datascience/
Shows that the CSS isn't loading. I suspect this is because
dsten.github.io is getting automatically redirected to data8.org but the
asset files aren't being redirected properly. @papajohn
https://github.com/papajohn any thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/59.

—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/59#issuecomment-138805795.

Issue still persists on the dsten.github.io repo. Closing the issue on this repo and will investigate.


text:
fix latex equations

something happened.
now the spaces and special characters have to be encoded.

![alt tag](http://latex.codecogs.com/svg.latex?g(\mathbb{E}[y|X]) = \beta_0 + f_1(X_1) + f_2(X_2) + \dots + f_p(X_p))

repo: dswah/pyGAM


text:
max_speed && speed problem

fit file:
2019-2-13-10-36-52-12791.fit.zip
fitparse version 1.0.1
max_speed : 14.201
fitparse version 1.1.0
max_speed: 14201
and speed encounter the same problem.

As I dive into detail, I found that bug is caused by generate_profile.py script, in line 468, which wipe out scale, offset and units.
But I think that only in situation of components scale is None or b'' or is not digit(

), we can wipe out scale, offset and units. so, wipe code should be
.  If you agree with me, I'd make a PR.

Hi, we've been happy users of this library for a while. We recently encountered an issue that is resolved by this work around which is available in 1.1. However, the bug described in this issue is preventing us from moving to 1.1. Any idea when this change will make it to a release that we can install with pip?
Thanks a lot for all the work on this library.

@cberthiaume You can create a new issue to detail your problem.

I'm confused, the issue in this issue is my problem. I see it's been merged. I'd just like to know when it will be released.

@cberthiaume, you're able to install it from pip immediately. Just use the latest SHA, see this post on Stack Overflow.

Excellent, thanks @dtcooper!

authors: beyoung cberthiaume dtcooper

repo: dtcooper/python-fitparse


text:
Mobile device issue update with certificate used to reach SSC Assistant (and mobile icon)

Currently using ICM certificate on Dev Subscription.
This issue should be resolved once the Assistant is moved to 163ENT (because it will use the F5 SSC firewall and manage certificates)
prerequisite
-163ENT Subscription
-Move Assistant to 163ENT

I have a solution after discussing with a coworker. I will try to use a service like let's encrypt and move away from ICM, this will remove this problem entirely.

repo: dto-btn/ssc-assistant


text:
Rigorous Exam Development Process

SHRM has a rigorous exam development process that ensures the integrity and credibility of the certification exams.
This includes a strict firewall between exam development and study material development to prevent any conflicts of interest or compromise of exam security.

The Society for Human Resource Management (SHRM) has a rigorous exam development process in place that is designed to ensure the integrity and credibility of the certification exams. The process involves several steps, including the following:

Job Analysis: SHRM conducts a comprehensive job analysis to identify the knowledge and skills that are essential for success in the HR field. This information is used to create a detailed exam outline that serves as the blueprint for the exam.
Item Writing: SHRM works with a team of subject matter experts to develop exam questions, or items, that are aligned with the exam outline. These items are designed to test a candidate's knowledge and skills across a range of HR topics.
Item Review: Before the items are finalized, they undergo a rigorous review process to ensure that they are clear, accurate, and free from bias. This review involves multiple rounds of feedback from subject matter experts, psychometricians, and other stakeholders.
Exam Form Construction: Once the items are finalized, they are used to create multiple exam forms, each of which consists of a unique set of items. This helps to ensure that the exams are fair and reliable, as candidates are not all taking the same exam.
Exam Security: SHRM takes exam security very seriously and has several measures in place to prevent cheating and protect the integrity of the exams. This includes a strict firewall between exam development and study material development, as well as other security measures such as proctoring, ID verification, and electronic monitoring.
Continuous Improvement: SHRM is committed to continuously improving its certification exams, and regularly conducts research to evaluate and refine the exams. This includes analyzing exam results, gathering feedback from stakeholders, and making adjustments to the exam outline and item pool as needed.

Overall, SHRM's exam development process is designed to ensure that its certification exams are fair, valid, and reliable measures of a candidate's knowledge and skills in the HR field. By following a rigorous process and maintaining a strong focus on exam security and continuous improvement, SHRM is able to maintain the credibility and value of its certifications over time.

repo: duafatimaa/timmsi


text:
Add Skip's POB Module to Duality

👋 Greetings from Skip!
This PR adds the POB Module into Duality.

Thanks Skip!

authors: keefertaylor teddyknox

repo: duality-labs/duality


text:
Compatible with external UVC USB camera ?

Hello!
Thank you for this project.
Would this approach be compatible with an external usb camera (UVC compatible webcam)?

I think it's compatible with an external camera, however, you probably need to handle the facing yourself, currently only CameraCharacteristics.LENS_FACING_BACK and CameraCharacteristics.LENS_FACING_FRONT are handled.
https://github.com/duanhong169/Camera/blob/d9fd8b4db468fb830d72e9852de629923cb0301a/camera/src/main/java/top/defaults/camera/Camera2Photographer.java#L48-L51


text:
Issue found on page 'INSERT Statement'

Please describe the issue on the page and include the "Page URL" link shown below.
Page URL: https://duckdb.org/docs/sql/statements/insert.html
Under Defining a Conflict Target it says
INSERT INTO tbl VALUES (1, 40, 700) ON CONFLICT (i) DO UPDATE SET k = 2 * EXCLUDED.;

Note the missing column at the end. Is this correct?

Yes, indeed column k should be there. Thanks for reporting this! A fix is on its way.

Excellent, thank you!

authors: michael-simons szarnyasg

repo: duckdb/duckdb-web


text:
Backup service

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3952   👈

This stack of pull requests is managed by Graphite.

repo: duckduckgo/Android


text:
Rename report flow param from prompt to reload-three-times-within-20-seconds

Task/Issue URL: https://app.asana.com/0/0/1208889990660025/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5339  👈 (View in Graphite)
develop

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


text:
Permission dialog

This is not so much an issue but more of a question for my own uwp development, so please close it if you want to.
How does the app know not to show the file permission dialog once the user already gave permission?

I can't allow this conversation to continue on the issues page, but since you've made some great contributions, I'll tell you.
In Files' case, you have to use a try/catch block to handle the AccessDeniedException (I think...) that gets thrown if permission is not available for the approperiate methods to run. In other words try to run code, and when the exception is caught, display a ContentDIalog.

Ok, thank you so much!


text:
Publishing records in search results refreshes the page

Publishing records in search results refreshes the page.  We want the user to remain in the search results when publishing items.

publish process is still reloading search results page.

repo: dulibrarytech/digitaldu-backend


text:
Tei pub fixes

this reinstates a working tei-publisher app with proper paths.
close #116
It does not address #67

note to self: add tests before merging

repo: duncdrum/generator-exist


text:
大佬帮忙看一下这是什么原因

填下代码里的配置，或者你可以用hamibot

填写下代码里的配置，或者你可以使用hamibot

我里面配置了好了百度api


text:
Added support for excluded routes

Here I am trying to add exclusions to secure routes list. It's useful when you have situation when one  or couple routes from secured routes list needs to work without csrf protection.
Changes:

New config option - exclude
New array of excluded routes in AngularCsrfValidationListener
Single behat test

@dunglas If I clean this up will it be still ok to merge?

Yes!

See PR #56

Closing as it was resolved in #56

authors: dunglas fatganz leevigraham

repo: dunglas/DunglasAngularCsrfBundle


text:
OpenTelemetry

caso possível falar da opentelemetry
https://opentelemetry.io/docs/instrumentation/python/

Up

Up

https://github.com/dunossauro/live-de-python/issues/359

Fechando issue: https://www.youtube.com/playlist?list=PLOQgLBuj2-3IL2SzHv1CHaBBHJEvHZE0m

authors: LorhanSohaky andreemidio dunossauro faustocaldeira

repo: dunossauro/live-de-python


text:
More closely following the AWS SDK environmental variables

I noticed that collect failed in an environment where e.g. aws sts get-caller-identity worked. There are two factors:

collect looks for AWS_REGION but the value typically used is AWS_DEFAULT_REGION (see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html): https://github.com/duo-labs/cloudmapper/blob/ceebed149f9d86f8c9db17f3633fe6da0bf43436/commands/collect.py#L211

collect does not check the AWS_PROFILE environmental variable so anyone using a non-default profile will have failures unless they specify --profile as well.

Ah, looks like I need to swap that AWS_REGION check for AWS_DEFAULT_REGION. Thank you.
As for AWS_PROFILE.  I try to just let botocore do what it is normally does.  If botocore is not checking that variable, then that seems outside the scope of this project.

Oh, interesting — awscli must have a special case for that since boto3 definitely requires you to do something like this:
session = boto3.Session(profile_name=os.environ.get('AWS_PROFILE'))
session.client('sts').get_caller_identity()

The AWS_PROFILE bit turned out to be an artifact of a stale .env file – AWS CLI & other tools were not loading that but pipenv was.

repo: duo-labs/cloudmapper


text:
🛑 Mention Robot is down

In 4f4bc6a, Mention Robot (https://backend.isbotdown.com/bots/mentionrobot) was down:

HTTP code: 200
Response time: 138 ms

Resolved: Mention Robot is back up in 2111c80.

repo: durof/status


text:
🛑 Mention Test Bot is down

In 1227897, Mention Test Bot (https://backend.isbotdown.com/bots/mentiontestbot) was down:

HTTP code: 200
Response time: 85 ms

Resolved: Mention Test Bot is back up in e7200a7 after 1 hour, 14 minutes.


text:
🛑 Mention Bot is down

In 4cecf06, Mention Bot (https://backend.isbotdown.com/bots/mentionbot) was down:

HTTP code: 200
Response time: 155 ms

Resolved: Mention Bot is back up in 64a7513 after 1 hour, 45 minutes.


text:
AgentMessage Component

Agent message component fully driven by the state coming from the Conversation component
It is composed of an Action component and a message component that should be aligned with the userMessage component
Some discussion to be done about the positioning of the picture since we might not always have messages and won't always have actions.
The Action component interface must be entirely generic (no retrieval word in the AgentMessage component).
Another task covers creating a RetrievalActionComponent which will be our first type of action component

depends on #1343

Leaving this opened as I am testing it right now.

authors: lasryaric spolu

repo: dust-tt/dust


text:
connectors cli: allow number in arguments

Description
If the workspace Id of a user has no letter connectors client yells at us. I tried tweaking the command line format with no success. Adding number as an accepted type solves the issue. We do turn wId intro a string in connectors client code
Risk
N/A
Deploy Plan

deploy connectors

PMRR

Actually builds fail due to a type error not caught here. Reverting for now

I think I see a fix. Taking (if ok with you).

authors: philipperolet spolu


text:
Problem whem sudo pip install -r python/requirements.txt

when i try to run
sudo pip install -r python/requirements.txt
it returns a error

Installing collected packages: leveldb, networkx, nose, python-dateutil, pandas, python-gflags, pyyaml
Running setup.py install for leveldb ... error
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-60J8XB/leveldb/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-kl7Lrj-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_ext
building 'leveldb' extension
creating build
creating build/temp.linux-aarch64-2.7
creating build/temp.linux-aarch64-2.7/snappy
creating build/temp.linux-aarch64-2.7/leveldb
creating build/temp.linux-aarch64-2.7/leveldb/db
creating build/temp.linux-aarch64-2.7/leveldb/table
creating build/temp.linux-aarch64-2.7/leveldb/util
creating build/temp.linux-aarch64-2.7/leveldb/port
aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c ./snappy/snappy.cc -o build/temp.linux-aarch64-2.7/./snappy/snappy.o -I./leveldb/include -I./leveldb -I./snappy -I. -fno-builtin-memcmp -O2 -fPIC -DNDEBUG -DSNAPPY -pthread -Wall -DOS_LINUX -DLEVELDB_PLATFORM_POSIX
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
./snappy/snappy.cc: In member function ‘bool snappy::SnappyIOVecWriter::Append(const char*, size_t)’:
./snappy/snappy.cc:1013:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (curr_iov_index_ + 1 >= output_iov_count_) {
^
./snappy/snappy.cc: In member function ‘bool snappy::SnappyIOVecWriter::AppendFromSelf(size_t, size_t)’:
./snappy/snappy.cc:1095:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (curr_iov_index_ + 1 >= output_iov_count_) {
^
aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c ./snappy/snappy-stubs-internal.cc -o build/temp.linux-aarch64-2.7/./snappy/snappy-stubs-internal.o -I./leveldb/include -I./leveldb -I./snappy -I. -fno-builtin-memcmp -O2 -fPIC -DNDEBUG -DSNAPPY -pthread -Wall -DOS_LINUX -DLEVELDB_PLATFORM_POSIX
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c ./snappy/snappy-sinksource.cc -o build/temp.linux-aarch64-2.7/./snappy/snappy-sinksource.o -I./leveldb/include -I./leveldb -I./snappy -I. -fno-builtin-memcmp -O2 -fPIC -DNDEBUG -DSNAPPY -pthread -Wall -DOS_LINUX -DLEVELDB_PLATFORM_POSIX
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c ./snappy/snappy-c.cc -o build/temp.linux-aarch64-2.7/./snappy/snappy-c.o -I./leveldb/include -I./leveldb -I./snappy -I. -fno-builtin-memcmp -O2 -fPIC -DNDEBUG -DSNAPPY -pthread -Wall -DOS_LINUX -DLEVELDB_PLATFORM_POSIX
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c leveldb/db/builder.cc -o build/temp.linux-aarch64-2.7/leveldb/db/builder.o -I./leveldb/include -I./leveldb -I./snappy -I. -fno-builtin-memcmp -O2 -fPIC -DNDEBUG -DSNAPPY -pthread -Wall -DOS_LINUX -DLEVELDB_PLATFORM_POSIX
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from ./leveldb/port/port_posix.h:50:0,
from ./leveldb/port/port.h:14,
from ./leveldb/db/filename.h:14,
from leveldb/db/builder.cc:7:
./leveldb/port/atomic_pointer.h:212:2: error: #error Please implement AtomicPointer for this platform.
#error Please implement AtomicPointer for this platform.
^
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-60J8XB/leveldb/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-kl7Lrj-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-60J8XB/leveldb/
ubuntu@tegra-ubuntu:~/caffe$

some one can help me ??

you don't have levelDB
you can try compiling manually and copying libraries
https://github.com/google/leveldb

repo: dusty-nv/jetson-inference


text:
能否把redux的store单独出来

现在是在app.start()里初始化store
在使用react-hot-loader@^3.0.0 时 ,无法做到重新render保留store

用 babel-plugin-dva-hmr 做 HMR。

@sorrycc 我试了下examples里的project  使用HMR是会整体页面刷新?

用 dva-cli 创建一个项目试试，改 components, router.js, routes 会 HMR，models 和 services 的 HMR暂未支持。

试了一下, 新创建的项目是可以HMR
但是index.js里默认代码是
// 3. Model
// app.model(require('./models/example'));

如果去掉该行注释则修改会整页刷新

index.js 也是没法做 HMR 的。

不是,我改动的是routes/IndexPage.js

如果store 能提供一个get/set接口 应该就能使用了...

重装 dva-cli 创建试试，我测试过已经没有问题了。
相关 Release：

https://github.com/dvajs/dva-cli/releases/tag/0.5.0
https://github.com/dvajs/babel-plugin-dva-hmr/releases/tag/0.2.0

authors: skyblue sorrycc

repo: dvajs/dva


text:
How can we organize columns?

How can we define the order of the columns we wish to display?

The built in way right now is by ordering the columns in the query in the order you want the table to be rendered, because it just iterates over each result.
There are some other methods available to customize tables (but ordering is not currently one of them):
query.render_table(self) do |t|
  # Column headings by default are the column name passed through I18n, but can be overridden:

  # ... with a block...
  t.override_heading do |heading|
    # ...
  end

  # ... or one at a time...
  t.override_heading :col, "My Column"

  # Records where a cell is 0 or nil can have the value overridden to something else:
  t.display_zero_as "N/A"
  t.display_nil_as "NULL"

  # You can specify how to format numbers:
  t.number_format "%0.1f"

  # You can also specify formatting on a per-column basis:
  t.format(:col) do |value|
    "#{(value / 50) * 100}%"
  end
end

authors: cimtico dvandersluis

repo: dvandersluis/compendium


text:
Presentation - Vertical Slides

Idea: Ability to use Vertical Slides in the Presentation Extension.
Use Case: In some case, bullets make sense to show. At other times, bullets are topics to explore in the presentation. For example, I have a long list of examples to explore in a presentation. In Roam, I've nested all my examples under an "Examples" bullet point. Rather than shoving 20 bullets into a slide, I'd like to use the Vertical Slide feature of reveal to do individual vertical slides for each nested bullet point.
I think it makes sense for this to be a configuration option in the slides command.
Example: Logseq implemented this really well. Go to any page and click the play button.

I'd like to attach a $20 bounty to this.

Adding comment from #595 to tackle here:
When expanding a bullet, often part of the content is not visible. Reveal.js has vertical navigation but it works for defined slides. In the case of Roam Presentation, it needs to work more like page down/up.

Moved to #745


text:
verifier: generate function is missing

i want to verifiy the received table via the onboard verification function:
flatcc_verify_field()
I generated the flatbuffer for C language.
The problem is that the prototype of the verify function is available in header flatcc_verifier.h but there is no function body.
Is the function body generation implemented for C?

I'm not sure I quite follow. As an example consider the following generated verifier:
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/reflection/reflection_verifier.h
Ignore reflection it is just some schema reflection.fbs that is already generated and checked in.
The verifier only verifies tables and structs. These are the only things that can be at the root of buffer. But the table verifiers are also not called directly under normal operation. Instead you call the _as_root version. This function is a thin helper to do additional work of reading and verifying the buffer header first. For example:
reflection_Schema_verify_as_root
A table verifier verifies fields, but there is no no generated field verifier. There is only one library function flatcc_verify_field that is called with different parameters. This function is not something you should call directly unless you really know what you are doing. It is defined in
https://github.com/dvidelabs/flatcc/blob/master/src/runtime/verifier.c
and its prototype is found in
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/flatcc_verifier.h

Maybe your problem is just that you need to link with the src/runtime/verifier.c code?

okey i copied the verifier.c into my project and now the code compiles.
i get allways the return code 2 of the function shema_verify_as_root(buffer, buffer_size)
my buffer is 100k big but the table i load is allways smaller so i give the verifier_as_root a pointer to the beginning of the buffer and the size of the loaded table.

Code 2 is probably identifier_mismatch - you can see be calling flatcc_verify_error_string(code)
This is a common problem, especially if your buffer is created elsewhere. Not all tools support identifiers. If you do not are about the identifier being correct you can specify a null identifier to the verifier:
mytable_verify_as_root_with_identifier(buf, size, 0).
If this works you may have to use similar with_identifier calls to read the buffer.

I added a section to the README:
https://github.com/dvidelabs/flatcc#trouble-shooting

Thanks for the hint.
with the verifier "mytable_verify_as_root_with_identifier(buf, size, 0)" it works and i found failures in the table.
Thanks for help.

authors: DanielHartung mikkelfj

repo: dvidelabs/flatcc


text:
--load_8bit is out of memory

My GPU has 24G VRAM， however when I used the --load_8bit, it says CUDA out of memory.

More details is here:
I launch chat.py by this way: CUDA_VISIBLE_DEVICES=0 python chat.py --version=mylocalpath --vision_tower=mylocalpath --precision=fp16 --load_in_8bit --image_size=256.
However, this is the out of memory messages given by pycharm:

Another try:
CUDA_VISIBLE_DEVICES=0 python chat.py --version=mylocalpath --vision_tower=mylocalpath --precision=bf16 --load_in_4bit --image_size=256.

Acutually, this is not a big problem when you use a GPU with 32 VRAM.

repo: dvlab-research/LISA


text:
How to train LongLoRA  step-by-step ?

Hi,
LongLoRA is a efficient framework to tackle LLM long-text problem.
I have some question about LongLoRA train pipeline after I readed paper and debug code.
As following steps are my understanding of LongLoRA，whether or not my understanding is correct.
Step1: we should interpolate positional encoding to adapt long-context
Step2: we replace original multi-heads-attention by Shift-Short-attention
Step3: take step2 model do unsupervised learning and training all parameters, like second-pretrain stage
Step4: take Step3 model use LongLoRA fintune(with S^2 Attention) train embedding / norm-layer / W_QKVO

Hi,
You could skip the continued retraining stage (step 3) and directly fine-tune base models with supervised fine-tuning.

repo: dvlab-research/LongLoRA


text:
add state management separate from frontend db

@nikonikoniko As briefly discussed we should have some state management for handling state that cannot or should not be dealt with in the frontend db (eg state of the app before initialization of db). I would suggest we go for https://github.com/pmndrs/zustand

I like how that library looks.
Considerations for non-db state:

What in particular will it store?

the config object
... any more?

Persistence

can this state easily be saved and loaded from local storage?
to a file?

my worry with zustand is that the 'actions' also live in the state object, and js functions can't be cleanly serialized.

I like how that library looks, and I think you're right about the need.
Considerations for non-db state:
1. What in particular will it store?

   * the config object?
   * ... any more?

2. Persistence

   * can this state easily be saved and loaded from local storage?
   * to a file?

my worry with zustand is that the 'actions' also live in the state object, and js functions can't be cleanly serialized, nor do we want it in this case, mixing app logic in with data.
we could use something like this and then on persisting the state do something like save(without(functions, state))

Actually, you can save the state to localStorage and also load the initial state from there: https://github.com/pmndrs/zustand/issues/195

Here is a library that is similar, but separates the actions from the state - also for consideration.

Think there is a link missing in your post?

added, sorry.  The link is: https://github.com/derrickbeining/react-atom

2. Persistence

   * can this state easily be saved and loaded from local storage?
   * to a file?

my worry with zustand is that the 'actions' also live in the state object, and js functions can't be cleanly serialized, nor do we want it in this case, mixing app logic in with data.
we could use something like this and then on persisting the state do something like save(without(functions, state))

Actually, you can save the state to localStorage and also load the initial state from there: pmndrs/zustand#195

Aha, so in this case, your store would always save the data in it's own key, and the actions separately?
so instead of
{
  fishes: {}
  birds: {}
  addFish: () => {}
  addBird: () => {}
}

You would have something like
{
  data: {
    fishes: {}
    birds: {}
  }
  addFish: () => {}
  addBird: () => {}
}

?
This could work for me but I wonder if there is any efficiency lost in nesting the data like that.  That might be worth asking.

I think the state managed through Zustand would be kind of limited: configuration and app state mostly. So, I guess we wouldn't run into performance issues on that end (if there were any with nested data).

Very good point.

authors: nikonikoniko tlmn


text:
[ansible] add 2.6 to CI and docs

Looks like no other effort is required

Something about temp file handling has broken from 2.5->2.6. Needs more work

repo: dw/mitogen


text:
Update context manager to return a NamedTuple

Updates the context manager so that it returns a NamedTuple instead of a regular tuple. This allows for easy access to the registers without having to always unpack the tuple on context enter.
with circuit.context as reg:
    X(reg.q[0])
    RX(0.5, reg.q[1])

works as well as
with circuit.context as (q, c):
    X(q[0])
    RX(0.5, q[1])

Codecov Report

Merging #13 (d902d14) into master (6566ce2) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   89.84%   89.89%   +0.05%
==========================================
  Files          15       15
  Lines        1142     1148       +6
  Branches      179      179
==========================================
+ Hits         1026     1032       +6
  Misses        116      116

Impacted Files
Coverage Δ

dwave/gate/circuit.py
100.00% <100.00%> (ø)

dwave/gate/registers/registers.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter thisac

repo: dwavesystems/dwave-gate


text:
Exception when using Rails 5.0.0

Logstash logger and rails versions:
    lograge (0.4.1)
    logstash-event (1.2.02)
    logstash-logger (0.15.1)
    rails (5.0.0)

Initialization of logstash logger (in config/application.rb):
  config.lograge.enabled = true
  config.lograge.formatter = Lograge::Formatters::Logstash.new
  config.logstash.uri = "file:///var/applications/test-app/log/logstash.log"

Fails with following exception:
2016-07-22 08:26:25 +0000: Rack app error: #<NoMethodError: super: no superclass method `silence' for #<Logger:0x00000003fc5d98>>
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/activesupport-5.0.0/lib/active_support/logger.rb:63:in `block (3 levels) in broadcast'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/activesupport-5.0.0/lib/active_support/logger_silence.rb:20:in `silence'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/activesupport-5.0.0/lib/active_support/logger.rb:61:in `block (2 levels) in broadcast'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/sprockets-rails-3.1.1/lib/sprockets/rails/quiet_assets.rb:11:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/actionpack-5.0.0/lib/action_dispatch/middleware/request_id.rb:24:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/rack-2.0.1/lib/rack/method_override.rb:22:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/rack-2.0.1/lib/rack/runtime.rb:22:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/activesupport-5.0.0/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/actionpack-5.0.0/lib/action_dispatch/middleware/executor.rb:12:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/actionpack-5.0.0/lib/action_dispatch/middleware/static.rb:136:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/rack-2.0.1/lib/rack/sendfile.rb:111:in `call'
/home/vagrant/.rvm/gems/ruby-2.3.0@global/gems/railties-5.0.0/lib/rails/engine.rb:522:in `call'

The exactly same setup works fine when using Rails 4.2.6. Any ideas on why might this happen?

Happening to me as well +1

Oh yeah. +1 Would be nice to find a solution for this

I agree this needs to be fixed. For now you can try working around the issue by adding config.assets.quiet = false to config/environments/development.rb.

After some research, it turns out that ActiveSupport's current logger silencing implementation won't work in custom Logger classes because of https://github.com/rails/rails/issues/24263.
I don't think it's a good idea to monkey patch LogStashLogger to work around an issue present in some versions of Rails and not others, especially since these seem to be internal implementation details that are bound to change further.
Nor do I want to re-implement the log silencing interface. (Unless this is a feature people want from LogStashLogger independently of making it work with Rails.)
The best solution might be to simply document the issue and workaround in the readme until the issue is fixed upstream in Rails.

I want LogStashLogger to work out-of-the-box with Rails. So I decided the best thing to do is vendor in a log silencing implementation that will remain stable instead of relying on internal ActiveSupport classes, similar to what was done for tagged logging.

The fix for this has been released in 0.17.0. No extra configuration is necessary. Logger silencing should "just work".

authors: altmer dwbutler joermungandr mduqueoviedo

repo: dwbutler/logstash-logger


text:
Select component label and arrow colors are not as per standard style guidlines

As per Select Style guildline the default label and underline color is #000000
Please check below states of this field

If you see the normal and select with focus state above it is clealy visible that only difference is in underline color which is not pitch black in normal state. The down arrow and label both remains #000000
Another state is select clicked where If you see the first options is not highlighted. It will only hightlight if user hover it.
Now compare above cases with current select implementation(https://developer.dxc.com/tools/angular/2/#/components/select) where label and arrow color is not black #000000 in normal state and first selection is auto highlighted in select clicked state without hover it.

Please correct if there are any other  Style guildlines
Regarding token visibility of label and underline, I have created issue in halstack-style-guide
@Lisa159 @mawelCaballero

Thanks @SavvySparrow for reporting the issue the fix has been merged.
It is already available so please check if everything is correct.

authors: Jialecl SavvySparrow

repo: dxc-technology/halstack-angular


text:
Fix help message text

Fixes Which Distro\'s ascii art to print in output when running --help. (Notice the backslash-quote.)
Caused by a rogue backslash in the heredoc.
Aside: I don't think Github's syntax highlighting is doing a good job here.

Thanks :+1:

repo: dylanaraps/neofetch


text:
--explain

everytime i run for example : shell-genie ask "list file" --explain
i get Error: Error in response.
any idea why ?

Hard to know if you don't provide more details. It's working for me:

It does happen with certain prompts. For example:
~> shell-genie ask "reinstall a package through pacman"
Error: Error in response.

shell-genie ask "reinstall a package through pacman"
Error: Error in response.

weirdly though this worked:
"reinstall a package"
Command: sudo pacman -S <package_name> --overwrite <file_to_overwrite>

authors: Kiraaliraa dylanjcastillo olofnuggts

repo: dylanjcastillo/shell-genie


text:
[Snyk] Security upgrade @backstage/cli from 0.0.0-use.local to 0.27.1

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

plugins/bazaar/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
  141

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)

repo: dylansnyk/backstage


text:
Implement Data Sources for Country Codes and Region Codes

As mentioned in #601 the basis for accepted Region Codes and Country Codes when creating / updating a Synthetic Location have recently changed.
Initially they could get deducted using the ISO 3166-2 standard and from FIPS 10-4 codes.
The new behavior defines the REST endpoints GET regions of the country and GET all countries for accepted region and country codes.
In order to have these valid codes available conveniently within Terraform Data Sources (e.g. dynatrace_geo_region and dynatrace_geo_country) will be helpful.

The next release will include three new data sources dynatrace_geo_countries, dynatrace_geo_regions, and dynatrace_geo_cities which will address this enhancement.


text:
Create sample dataset that has common feature types

DoubleType (FloatType)
IntegerType
BoolType
StringType

eventually there should be only 2 types Categorical and Numerical
https://stats.idre.ucla.edu/other/mult-pkg/whatstat/what-is-the-difference-between-categorical-ordinal-and-numerical-variables/

cd ammonite && make data will produce parquet directory.
make will bring up the ammonite shell,
interp.load.module(pwd/'libs/"sparkSession.sc")
val df = spark.read.parquet("parquet/")
df.schema

schema looks like
res2: StructType = List(
  StructField("Region", StringType, true, {}),
  StructField("ClassGrade", IntegerType, true, {}),
  StructField("Gender", StringType, true, {}),
  StructField("Handed", StringType, true, {}),
  StructField("Height_cm", DoubleType, true, {}),
  StructField("Languages_spoken", IntegerType, true, {}),
  StructField("Birth_month", StringType, true, {}),
  StructField("Favorite_Season", StringType, true, {}),
  StructField("Allergies", BooleanType, true, {}),
  StructField("Vegetarian", BooleanType, true, {}),
  StructField("Favorite_Music", StringType, true, {}),
  StructField("Superpower", StringType, true, {})
)

repo: dyno/facets-overview-spark


text:
data with unknown attr: xx Packet(80, 04,05......

Hello. When I connect the Armband by PyoConnect I get this error on the console and nothing changes.  I use 1.5.1970.2 firmware version and updated raspbian OS. Do you have any idea about this error?

@mehmetserdarcelik It seems that someone has been pushing a lot of updates until 3 years ago on this repo https://github.com/qtux/myo-raw so that one might work.
I'm also looking into seeing what can be done now with this Myo or if I should just trash it.

Hey @exadeci
I've made an updated version of this library which supports both Windows and Linux, I've added multithreaded support and a bunch of other stuff, including support for all three EMG modes the Myo supports.
I've also used this driver to play Breakout and predict my hand movements in SteamVR.

authors: PerlinWarp exadeci mehmetserdarcelik

repo: dzhu/myo-raw


text:
createLeft function is broken

Thanks for your work.
Latest commit, built with stack-local ghc-8:
*Data.Sext.TH Data.Sext Data.Sext.Class Data.Sext.TH> Data.Sext.createRight ' ' "string" :: Sext 10 String
"    string"
*Data.Sext.TH Data.Sext Data.Sext.Class Data.Sext.TH> Data.Sext.createRight ' ' "string" :: Sext 1 String
"g"

createRight is okay, but createLeft gives me:
*Data.Sext.TH Data.Sext Data.Sext.Class Data.Sext.TH> Data.Sext.createLeft ' ' "string" :: Sext 1 String
"string"
*Data.Sext.TH Data.Sext Data.Sext.Class Data.Sext.TH> Data.Sext.createLeft ' ' "string" :: Sext 100 String
"string"
*Data.Sext.TH Data.Sext Data.Sext.Class Data.Sext.TH>

It seems that the last call to C.take (C.length s) in the implementation is incorrect, since it just returns an origin string.
The correct implementation needs to use C.take t to be valid.

Hello, thank you for reporting the bug - this is really embarassing. Should be fixed in sext-0.1.3.

Don't worry! The issue was found when I played with liquidhaskell and your package for an university paper, so I am glad to help here.
I hope it is okay to mention your library in my course paper.
The issue is resolved, hence closed.

Of course. Best of luck.

authors: Altai-man dzhus

repo: dzhus/sext


text:
Allow extraHeaders for fetchNavigation

In a new version the navigationService can be secured with a token authentication. In order to access it from the fsxa-api "fetchNavigation()" function, it should be possible to pass additional headers, e.g.
async fetchNavigation(
    initialPath: string | null,
    defaultLocale: string,
   extraHeaders?: Record<string, string[]>
  ): Promise<NavigationData | null> {

alternatively, the complete oauth2 flow could be supported by the fsxa-api

We merged your PR so that you can pass additional headers to the navigation-service. We will close this issue for now, since we do not plan on supporting specific auth-flows in the nearer future.

authors: KoljaTM tgolbs

repo: e-Spirit/fsxa-api


text:
Tng 978

Fixed a bug where a empty query results into an error.
Also adjusted tests in this context

Good job, nice work.

authors: dbarczewski rrieger-espirit


text:
Debug and Stabilize Logging and Loki

Updates to increase default resource allocations for loki and logging agents, increase buffer and batch for logging. Should review before implementing in general prod, tested in smaller but high traffic prod environments

Important parts merged to dev

authors: Just-en-Time jakubno


text:
The correct character width for titles, subtitles and footnotes is now hard to determine due to the fixed width/aspect ratio of graphical outputs

The fixed aspect ratio of plots, combined with the fixed height/width of outputs produced by save_e61() means that when a long footnote is included in a graph, the plot area shrinks, making the default title/subtitle/footnote character-based widths too large.
This is a trade-off between maintaining the figure's dimensions, the plot's dimensions, and the positioning of the text elements around the plot, because it is likely impossible to have all three. Are we happy with the current trade-off where the user is more likely to have to make use of the manual character width adjustments?

@elyse-22 Bugging you with this since you wanted to aspect ratio fix.


text:
[Bug]: CI Icon 클릭 시 Github Actions로 이동되지 않고 있습니다.

연락처 Contact
chris5207@naver.com
오류 내용 Error Description
README 의 빌드 확인 CI Icon 클릭 시 Actions로 이동이 되지 않고 있습니다.

클릭 시 빌드 확인된 Github Actions 페이지로 이동이 되어야 할 것 같습니다.
오류 재현 방법 How to reproduce the error

Node.js CI Icon 클릭
단순 icon 파일 경로로 이동 됨

환경정보 Environmental Information

OS정보 Operating System:
표준프레임워크 버전 eGovFrame Version:
JDK(JRE) 정보:
WAS 정보:
DB 정보:
기타 환경 정보 Other environmental information:

어느 브라우저를 사용했나요? Which browser did you use?
Chrome
에러 로그 Error Logs
No response

Spring Security 깃허브 사이트 참고하면 좋을 것 같습니다.
https://github.com/spring-projects/spring-security
https://github.com/spring-projects/spring-security/actions?query=workflow%3ACI

[2023 전자정부 표준프레임워크 컨트리뷰션 참가 기념품 발송안내]
안녕하세요
전자정부 표준프레임워크 센터입니다.
'23년 4월 10일부터 8월 31일까지 약 4개월간, 전자정부 서비스 개발 표준 기반인 "전자정부 표준프레임워크" 개선에 민간 SW개발자의 아이디어와 의견을 반영하기 위해 "2023 전자정부 표준프레임워크 컨트리뷰션"을 실시 하였습니다.
표준프레임워크 깃허브(github.com/egovframework)에 보내주신 귀하의 의견에 감사드리며, 전자정부 표준프레임워크 운영·개선 과정에서 유용하게 활용토록 하겠습니다.
본 설문에 응답 주시면 표준프레임워크에서 마련한 소정의 기념품을 발송 드릴 예정이오니, 문항에 빠짐없이 응답 해 주시기 바랍니다.
아래의 URL을 통하여 설문지로 이동, 항목에 응답 부탁드립니다.
https://forms.gle/g5cKfG5rnNrqvqjaA
앞으로도 전자정부 표준프레임워크에 지속적인 관심 부탁드립니다.
※ 센터에서 준비한 감사장과 표준프레임워크 오픈커뮤니티에서 소정의 기념품을 택배 배송 해 드립니다.
※ 컨트리뷰션 종료 후, 시상 관련하여 연락 갈 예정이오니, 꼭 통화 가능한 본인번호를 기재해 주시기 바랍니다.
※ 귀하께서 답변해 주시는 내용은 컨트리뷰션 참가 확인 및 기념품 발송 목적으로만 활용되며, 개인정보는 기념품 발송 후 즉시 영구 삭제처리 됩니다.
감사합니다.

표준프레임워크 발전을 위해 소중한 의견 감사합니다.


text:
npm 怎么打deb的包

在linux下执行npm run dist:linux,会报如下错误
SyntaxError: Unexpected token function
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 _readConfigFile (/home/liuwx/temp/electron-wechat/node_modules/electron-builder/out/cli/cli.js:77:16)
at Object.args [as handler] (/home/liuwx/temp/electron-wechat/node_modules/electron-builder/src/cli/cli.ts:43:3)
at Object.runCommand (/home/liuwx/temp/electron-wechat/node_modules/yargs/lib/command.js:235:44)
at Object.parseArgs [as _parseArgs] (/home/liuwx/temp/electron-wechat/node_modules/yargs/yargs.js:1042:24)
at Object.get [as argv] (/home/liuwx/temp/electron-wechat/node_modules/yargs/yargs.js:957:21)
at Object. (/home/liuwx/temp/electron-wechat/node_modules/electron-builder/src/cli/cli.ts:25:28)
at Module._compile (module.js:570:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! electron-wechat@0.1.1 dist:linux: electron-builder --linux AppImage
npm ERR! Exit status 1
看了package.json, 里面的dist:linux 只会打  AppImage的包 ,想知道你是怎么打deb的包的?后续只需要更新代码自己在本地打包就可以使用最新版本了, 不需要每次都下载 release包(下载速度有点慢)

花了点时间研究了下 npm 打包,已经自行解决了.

解决方案
把 electron-builder --linux AppImage 改称 electron-builder --linux deb 就可以了
我的开发环境是arch，花时间BUILD DEB包，就没加进去。release的时候会有deb

authors: eNkru lexusking

repo: eNkru/electron-wechat


text:
Gradle installation note <2.0.x> [9882]

Signed-off-by: Ignacio Montesino ignaciomontesino@eprosima.com

Build status:

This PR requieres rebasing

Build status:

Build status:

authors: EduPonz imontesino richiware

repo: eProsima/Fast-RTPS-docs


text:
Maintenance/support php 81

Dropped support for laravel 6 and 7 : #34493
Tested support for php 8.1 : #34480
This branch was also built on feature/improve-test-coverage. So checkout the PR for this other branch before this one

Comme dans db-upgrade, il semble y avoir eu une erreur dans l'étape set-up php. J'ai simplement "re-run all jobs" et tous les check passent.

repo: eXolnet/laravel-translation-editor


text:
ValueError raised on just sequencer selected

Selecting just a sequencer ID and plotting raises a ValueError, might be escaping form validation

actually same is happening on selecting any of the subset selections :sadpanda:

I tried again and can't now....

I'm also unable to reproduce this. Closing this issue.

repo: eastgenomics/trendyQC


text:
Sync with Google Drive

Since every Android user normally also has a Google Drive account, (auto)syncing to Google Drive would be an additional measure to keep your texts safely backuped.

The feature is under development.

Nice to hear. Do you have an ETA?

May be early of July.

WriterSync (https://play.google.com/store/apps/details?id=co.easy4u.writer.sync) has been released. You can use it to sync files in WriterPlus app.


text:
Slurm's srun command passes hyperparameters as command line args instead of config files

I'm trying to run some decoding trials using slurm. I have a slurm config file that looks like this:
#!/bin/bash
#SBATCH --job-name=decoder_grid_search    # Job name
#SBATCH --mail-type=END,FAIL          # Mail events (NONE, BEGIN, END, FAIL, ALL)
#SBATCH --mail-user=yoniifriedman@gmail.com   # Where to send mail
#SBATCH --time=00:05:00               # Time limit hrs:min:sec
#SBATCH --account=zi
#SBATCH --nodes 1
#SBATCH -c 1

The job fails, with this message:

Here's the srun command where the arguments are coming from:

Should the srun command contain the typical config command line arguments instead of the hyperparameters themselves?
The __get_run_command function for context:
def __get_run_command(self, trial, slurm_cmd_script_path, timestamp, exp_i, on_gpu):
        trial_args = self._SlurmCluster__get_hopt_params(trial)
        trial_args = '{} --{} {} --{} {}'.format(trial_args,
                                                 HyperOptArgumentParser.SLURM_CMD_PATH,
                                                 slurm_cmd_script_path,
                                                 HyperOptArgumentParser.SLURM_EXP_CMD,
                                                 exp_i)

        cmd = 'srun {} {} {}'.format(self.python_cmd, self.script_name, trial_args)
        return cmd

@ebatty any input on this? I haven't used behavenet with slurm before

authors: themattinthehatt yifr

repo: ebatty/behavenet


text:
GSE148963_ProximalEpididymisCFTR

Dataset/group this task is for:
GSE148963_ProximalEpididymisCFTR
https://docs.google.com/spreadsheets/d/1c3lLM22-C4hOFvuLslJIhoZMH7zzaWp7/edit#gid=541177963
https://staging.contribute.data.humancellatlas.org/submissions/detail?id=6023d561f29f510eee5602dc
Wrangler responsible for this dataset/lab:
Primary: Ami
Secondary: Ray
Acceptance criteria for the task:

[x]  fill metadata
[x]  add ontologies
[x]  validate with graph validator
[x]  validate in ingest staging
[x]  secondary review
[x]  upload to ingest prod.
[x]  upload raw data to ingest prod.

Secondary review

Project - Contributors

Please, add ORCID identifiers for authors:

Shih-Hsing,,Leir	0000-0001-9524-3379
Shiyi,,Yin	0000-0003-4366-2189
Jenny,L,Kerschner	0000-0002-1980-2543
Ann,,Harris	0000-0002-6541-2546

Donor organism

the ontology fields are not filled in for testicular cancer (MONDO:0005447):

donor_organism.diseases.text    donor_organism.diseases.ontology    donor_organism.diseases.ontology_label
testicular cancer
testicular cancer
testicular cancer

Collection protocol:

need to add ontology terms

Specimen from organism:

need to add ontology terms

Dissociation protocol:

need to add ontology terms

Enrichment protocol:

need to add ontology terms

Cell suspension:

need to add ontology terms

Library preparation protocol:

need to add ontology terms

Sequence file

need to add ontology terms

graph validator

Two of the ingest graph validator tests have failed on GSE148963.xlsx,

Failed test [experimental_design_donthave_cycles.adoc]
I think this is caused by the re-use of the experiment accessions (SRX) as identifiers for

library prep/sequencing process IDs process.process_core.process_id and
input cell suspension IDs cell_suspension.biomaterial_core.biomaterial_id.

If I change the input cell suspension IDs
from     to
SRX8143297 -->  GSM4486714
SRX8143298 -->  GSM4486715
SRX8143299 -->  GSM4486716

, then that version of the spreadsheet passes validation and there are no cycles in the experimental design graph.

Failed test [file_donthave_outward_links.adoc] : this is a known false error.

Thanks @rays22 I have uploaded it to ingest. I can't transfer the fastq files yet as there is a problem with EC2.

Downloading data to an hca-util upload area.

There are some data protection concerns with this dataset.

2 main issues need to be solved:

The submission still has a exported state
There is data under 842605c7-375a-47c5-9e2c-a71c2c00fcad folder in the staging area; we may need to delete it

@ami-day @yusra-haider can you work together and confirm what needs to be done to get this sorted. I think getting this done before the next Operations meeting would be fantastic

I spoke to @yusra-haider , she is going to look into updating it so it can be exported tomorrow.

okay so I can see the project in the terra staging area and that it has been exported.
I'm not sure if there's anything else that needs to be looked into? @ami-day
Is there a way we can ask the folks at broad to take on this dataset? @aaclan-ebi
cc: @lauraclarke

@yusra-haider do we have a way to confirm the export is correct?
@ami-day Do you need to complete all the steps in the Export SOP for this?

okay so this project was exported on March 19, 2021, and the earliest exporter logs I can see via kubernetes is beginning of April. There should be a way to check earlier logs and verify this export, @aaclan-ebi could you please guide me on this, if possible?
other than that I can see the expected number of data files is in the terra staging area
@lauraclarke

What is needed for this dataset? I read @ESapenaVentura  2 issues but I'm still uncertain what needs to be done.

The submission still has a exported state
Why is this an issue?

There is data under 842605c7-375a-47c5-9e2c-a71c2c00fcad folder in the staging area; we may need to delete it
Do we want to delete the submission?

@rays22 also said this dataset has data protection concerns.
Do we want to make sure everything's exported correctly OR do we want to delete everything?
Many Thanks
Alegria

nvm, sorry i was confused, looks like Laura's confirming if dataset was exported correctly.

If the submission is exported, it should be good enough to say everything's exported correctly. (Unless there was an update and the submission was reexported. There is a current issue on that. ebi-ait/dcp-ingest-central#220 )
@yusra-haider we could just check the count of metadata & data files in terra and compare it with the count of metadata/data in Ingest. It's tricky to get the exporter logs after it was redeployed. It might have been deleted already since this was from last 19th March (checking from the submission last updateDate , https://api.ingest.archive.data.humancellatlas.org/submissionEnvelopes/605209fe91708e06ec075d55)

This dataset wasn't updated, it was just on hold during the last release as after I hit the export button, the authors got back saying there were uncertain about potential data privacy issues. This has been resolved now and we can export this month (but won't need to since it is already exported! i just need to follow the last steps in the export SOP to make sure it gets handed over to pipelines).

Submitted import form as part of export SOP.

Converting to scea format with id: E-HCAD-38

This has now been approved by Silvie.

authors: ESapenaVentura aaclan-ebi ami-day lauraclarke rays22 yusra-haider

repo: ebi-ait/hca-ebi-wrangler-central


text:
CHEBI:58650, error in current structure

Hi,
There is an error in the structure of CHEBI:58650, N(4)-{N-acetyl-beta-D-glucosaminyl-(1->2)-alpha-D-mannosyl-(1->3)-[N-acetyl-beta-D-glucosaminyl-(1->2)-alpha-D-mannosyl-(1->6)]-beta-D-mannosyl-(1->4)-N-acetyl-beta-D-glucosaminyl-(1->4)-[alpha-L-fucosyl-(1->6)]-N-acetyl-beta-D-glucosaminyl}-L-asparagine zwitterion.
The alpha-L-fucosyl group is actually beta in the current structure. A corrected structure mol file is attached.
CHEBI_58650.txt
Cheers,
Kristian

I close the ticket because it was an error. There is no mistake in the structure

repo: ebi-chebi/ChEBI


text:
merging ncep_data

merge ncep_data
make Boolean variables binary
make planting_density variable numeric (previously string)

@sidewallme can you please send another pull request? This one has conflicts.

authors: dlebauer sidewallme

license: NCSA


text:
Newer versions of perl have trouble with require 'eds-methods.pl' with strict on

The result is that eds-methods.pl won't load, as . isn't in @inc.

to replicate, you'll probably need Debian 9

Hi Liz,
We found this as well on a Debian 9 machine and running Koha 18.11.x branch. We have found adding ./ to the start of the filename in the require line in  eds-detail.pl, eds-ac.pl, eds-cite.pl, eds-raw.pl, eds-search.pl, pfi-search.pl fixes this issue so I have submitted a pull request with these fixes in it:
https://github.com/ebsco/edsapi-koha-plugin/pull/67
We also found that the line: $self->go_home(); which was removed in the Koha EDS master branch is required otherwise a 500 error is shown upon saving the Koha EDS configuration page.
Now with this aforementioned fix after saving the config form you are redirected back to the Tools > Tool plugins page in the Koha intranet.
Cheers,
Alex

#68 should close this issue

This looks to be resolved with the 19.05 release to master, but please feel free to reopen if you install the new release and still see this issue.

authors: Alex-Buckley cambw mmabrahamson wizzyrea

repo: ebsco/edsapi-koha-plugin