text:
Null Pointer Exception from convertStringToStruct()

System information:

Operating system (distribution) and version: Ubuntu 18.04.3 LTS
DBeaver version: 6.3.3.2
Additional extensions: None

Connection specification:

Database name and version: PostgreSQL 11.6
Driver name: PostgreSQL JDBC Driver
Do you use tunnels or proxies (SSH, SOCKS, etc)?  No

Describe the problem you're observing:
DBeaver becomes unstable (throws null pointer exceptions and sometimes crashes) when viewing table data if (it seems) a type is in a different schema than the table.
Steps to reproduce, if exist:
CREATE SCHEMA schema_a;

CREATE TYPE schema_a.bookmark AS (
  target_url varchar,
  link_text varchar
);

CREATE SCHEMA schema_b;

CREATE TABLE schema_b.orgs (
  id uuid NOT NULL,
  bookmarks schema_a.bookmark[]
);

INSERT INTO schema_b.orgs (id,bookmarks) VALUES
('06374133-44d8-11ea-969d-9cb6d09a79f1', ARRAY[('https://google.com/', 'Some words')]::schema_a.bookmark[]),
('06374172-44d8-11ea-969d-9cb6d09a79f1', ARRAY[('https://github.com/', 'Words')]::schema_a.bookmark[]);

Then looking at the data in the schema_a.orgs table:

One weird thing, if the Some words text in the first row is inserted as just a single word, it seems to work OK?
Also seems to work if the type is in the same schema as the table.
And also seems fine if the data is returned via a SELECT.

Include any warning/errors/backtraces from the logs
java.lang.NullPointerException
	at org.jkiss.dbeaver.ext.postgresql.model.data.PostgreStructValueHandler.convertStringToStruct(PostgreStructValueHandler.java:111)
	at org.jkiss.dbeaver.ext.postgresql.model.data.PostgreStructValueHandler.getValueFromObject(PostgreStructValueHandler.java:95)
	at org.jkiss.dbeaver.ext.postgresql.PostgreUtils.convertStringToSimpleValue(PostgreUtils.java:513)
	at org.jkiss.dbeaver.ext.postgresql.PostgreUtils.convertStringToValue(PostgreUtils.java:502)
	at org.jkiss.dbeaver.ext.postgresql.model.data.PostgreArrayValueHandler.convertStringToCollection(PostgreArrayValueHandler.java:98)
	at org.jkiss.dbeaver.ext.postgresql.model.data.PostgreArrayValueHandler.getValueFromObject(PostgreArrayValueHandler.java:74)
	at org.jkiss.dbeaver.ext.postgresql.model.data.PostgreArrayValueHandler.getValueFromObject(PostgreArrayValueHandler.java:1)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetUtils.bindAttributes(ResultSetUtils.java:189)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetDataReceiver.fetchEnd(ResultSetDataReceiver.java:163)
	at org.jkiss.dbeaver.model.impl.jdbc.struct.JDBCTable.readData(JDBCTable.java:213)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:110)
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:159)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:108)
	at org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$17.run(ResultSetViewer.java:3454)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:103)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

It is a bug in array parser.
PG driver returns arrays in string form. There were two issues which lead to this bug:

JDBC driver doesn't provide correct type info (Types.OBJECT instread of Types.ARRAY)
DBeaver parsed arrays of struct types incorrectly.

Fixed

verified

authors: serge-rider timneedham uslss


text:
dbeaver/pro#3301 Fix PostgreSQL role editor

Save "Valid Until" date option
Add date picker for easier selection

Please provide a screenshot or a short video showing the new editor

related issue, existing before https://github.com/dbeaver/dbeaver/issues/36185
verified

source: gharchive/pull-request

authors: ShadelessFox ivgag uslss

repo: dbeaver/dbeaver

license_type: permissive

license_source: github-api


text:
How to pass trade mark sign?

Hello,
I am trying to pass ™ to the .xml file but it doesn't seem to work, is there another char that I can reference to replace ™?
thank you

Have you tried using ™ instead of ™?

I just tried it, DNI says invalid character...
e.g. Microsoft™
exeparameters="&quotMicrosoft™ Office"

Maybe DNI is complaining about &quot which should actually be ".

This should be reproducible in a test, @makotia if you write one I could help fix it.

source: gharchive/issue

authors: dblock icnocop makotia

repo: dblock/dotnetinstaller

license: mit

license_source: bigquery


text:
Unable to Load Images to train model on Custom Datasets

Hello, I have just stuck with Image Instance Segmentation for a while. I am trying to train the Yolact model for my custom data. Here is some brief information about what I have done so far

I have annotated the image using labelme annotation tool
I have converted annotation file for each (train & validation data) using labelme2coco -> train.json & test.json
I made changes in the cofig.py file as needed and expected by yolact
As I was following this repository I encountered an error Argument 'bb' has incorrect type to which I have solved with the approach stated in this closed issue

After completing the above task I am stuck here with below-stated issue.
`Scaling parameters by 0.12 to account for a batch size of 1.
Per-GPU batch size is less than the recommended limit for batch norm. Disabling batch norm.
loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
/usr/local/lib/python3.6/dist-packages/torch/jit/_recursive.py:165: UserWarning: 'lat_layers' was found in ScriptModule constants,  but it is a non-constant submodule. Consider removing it.
" but it is a non-constant {}. Consider removing it.".format(name, hint))
/usr/local/lib/python3.6/dist-packages/torch/jit/_recursive.py:165: UserWarning: 'pred_layers' was found in ScriptModule constants,  but it is a non-constant submodule. Consider removing it.
" but it is a non-constant {}. Consider removing it.".format(name, hint))
/usr/local/lib/python3.6/dist-packages/torch/jit/_recursive.py:165: UserWarning: 'downsample_layers' was found in ScriptModule constants,  but it is a non-constant submodule. Consider removing it.
" but it is a non-constant {}. Consider removing it.".format(name, hint))
Initializing weights...
Begin training!
Traceback (most recent call last):
File "train.py", line 504, in
train()
File "train.py", line 270, in train
for datum in data_loader:
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/dataloader.py", line 363, in next
data = self._next_data()
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/dataloader.py", line 989, in _next_data
return self._process_data(data)
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/dataloader.py", line 1014, in _process_data
data.reraise()
File "/usr/local/lib/python3.6/dist-packages/torch/_utils.py", line 395, in reraise
raise self.exc_type(msg)
AssertionError: Caught AssertionError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/_utils/worker.py", line 185, in _worker_loop
data = fetcher.fetch(index)
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/usr/local/lib/python3.6/dist-packages/torch/utils/data/_utils/fetch.py", line 44, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/content/yolact/data/coco.py", line 94, in getitem
im, gt, masks, h, w, num_crowds = self.pull_item(index)
File "/content/yolact/data/coco.py", line 141, in pull_item
assert osp.exists(path), 'Image path does not exist: {}'.format(path)
AssertionError: Image path does not exist: data/YolaDataset/train/6.JPG`
NOTE:I have moved my test & train data to yolact/data/YolactDataset ( also CWD is /yolact/ )
Here is the Log file
Yolact Leather Defect Config.log
Here is the content of config.py
yolact_leather_defect_dataset = Config({
    'name': 'Yolact Leather Defect',

    # Training images and annotations
    'train_images': './data/YolaDataset/train/',
    'train_info':   './data/train.json',

    # Validation images and annotations.
    'valid_images': './data/YolaDataset/test/',
    'valid_info':   './data/test.json',

    # Whether or not to load GT. If this is False, eval.py quantitative evaluation won't work.
    'has_gt': True,

    # A list of names for each of you classes.
    'class_names': ("FC", "LF", "OC", "PM"),

    # COCO class ids aren't sequential, so this is a bandage fix. If your ids aren't sequential,
    # provide a map from category_id -> index in class_names + 1 (the +1 is there because it's 1-indexed).
    # If not specified, this just assumes category ids start at 1 and increase sequentially.
    'label_map': {
        1:1, 2:2, 3:3, 4:4,
    }
})

yolact_leather_defect_config = coco_base_config.copy({
    'name': 'Yolact Leather Defect Config',

    # Dataset stuff
    'dataset': yolact_leather_defect_dataset,
    'num_classes': len(yolact_leather_defect_dataset.class_names) + 1,

    # Image Size
    'max_size': 550,

    # Training params
    'lr_steps': (280000, 600000, 700000, 750000),
    'max_iter': 800000,

    # Backbone Settings
    'backbone': resnet101_backbone.copy({
        'selected_layers': list(range(1, 4)),
        'use_pixel_scales': True,
        'preapply_sqrt': False,
        'use_square_anchors': True, # This is for backward compatability with a bug

        'pred_aspect_ratios': [ [[1, 1/2, 2]] ]*5,
        'pred_scales': [[24], [48], [96], [192], [384]],
    }),

    # FPN Settings
    'fpn': fpn_base.copy({
        'use_conv_downsample': True,
        'num_downsample': 2,
    }),

    # Mask Settings
    'mask_type': mask_type.lincomb,
    'mask_alpha': 6.125,
    'mask_proto_src': 0,
    'mask_proto_net': [(256, 3, {'padding': 1})] * 3 + [(None, -2, {}), (256, 3, {'padding': 1})] + [(32, 1, {})],
    'mask_proto_normalize_emulate_roi_pooling': True,

    # Other stuff
    'share_prediction_module': True,
    'extra_head_net': [(256, 3, {'padding': 1})],

    'positive_iou_threshold': 0.5,
    'negative_iou_threshold': 0.4,

    'crowd_iou_threshold': 0.7,

    'use_semantic_segmentation_loss': True,
})

I have tried to resolve the issue to the best can help myself. Any help would be appreciated.
Thank You!

I have miss-spelled the YolactDataset to YolaDataset in the configuration file.

I also have this problem with you, my reason is that there is a problem with the path of the picture, you are checking it well

authors: kevalrajpalknight xqh-code

repo: dbolya/yolact

license: MIT


text:
Low mAP .95 in validation

Hi,
I am training YOLACT with 179 training images and 30 validation images. I have good results in mAP from 0.5 to 0.8, but in 0.95 it is reduced. Does it need to change some parameters?

At the end, what was the source of this issue?


text:
Grammar

"Check the model has a tests" is maybe tech jargon I don't understand but it sounds like this guy:

Codecov Report
Patch and project coverage have no change.

Comparison is base (c57c8dd) 98.45% compared to head (ddf6c4d) 98.45%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #150   +/-   ##
=======================================
  Coverage   98.45%   98.45%
=======================================
  Files          47       47
  Lines        2330     2330
  Branches      309      309
=======================================
  Hits         2294     2294
  Misses         21       21
  Partials       15       15

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: carlthome codecov-commenter

repo: dbt-checkpoint/dbt-checkpoint


text:
[CT-254] dbt-core - Snapshot - macro dbt_macro__create_schema takes not more than 1 argument(s)

https://github.com/dbt-labs/dbt-core/blob/3ad61d5d810aab8bf7bf7bc38f62d02348839c80/core/dbt/include/global_project/macros/materializations/snapshots/snapshot.sql#L9-L11
Hi I've raise this same issue in dbt-sqlserver, but the issue might actually lie here after further investigation. I'm running into the issue, "macro 'dbt_macro__create_schema' takes not more than 1 argument(s)", when attempting to do a simple snapshot. When I delete lines 9-11 in the above all goes well.
Please see additional details on dbt-sqlserver issue at https://github.com/dbt-msft/dbt-sqlserver/issues/208

@rlshuhart Thanks for opening, you're totally right! We need to make that create_schema call take a single Relation argument, rather than database + schema. This was a breaking change a long time ago... all the way back in v0.17 (https://github.com/dbt-labs/dbt-core/pull/2411).
It's worth checking to see if we actually need this create_schema call at all. I have a sneaking suspicion that the snapshot may already be properly accounted for by this logic:
https://github.com/dbt-labs/dbt-core/blob/5e0a7659174a9277e2013390f8615acc97464d40/core/dbt/task/run.py#L437-L439

I've concluded these lines are totally unneeded. After a bit of digging through the git blame, I see that the origin of the create_schema in the snapshot (then archive) materialization was in: https://github.com/dbt-labs/dbt-core/pull/625
At the time, Drew noted that:

There might be a smarter way to do this -- we could set the node schema to the value of target_schema, then this will happen automatically through the node_runner before_run flow.

This is in fact what we do:
https://github.com/dbt-labs/dbt-core/blob/204d53516a08a619ebea69b68aa8138dd1814f54/core/dbt/parser/snapshots.py#L38-L40
And have been doing since https://github.com/dbt-labs/dbt-core/pull/1478 (here specifically). This is picked up accordingly by the before_run method in the snapshot task (inherited from the method in the run task shown above).
Worth noting that this piece still isn't perfect, if you're defining target_schema in a .yml file instead of snapshots/*.sql: https://github.com/dbt-labs/dbt-core/issues/4000

repo: dbt-labs/dbt-core


text:
[CT-3527] [implementation] extend access and groups to exposures & source

Housekeeping

[X] I am a maintainer of dbt-core

Short description
From the discussion here...
We should extend group configurations to all resource types. The current outstanding ones are sources and exposures:

exposures should be able to reference models within the same group
sources should be able to be private to a given group

We should also enable sources to configure access to private or protected (default). We should not allow folks to set access to public for sources.
Acceptance criteria

[ ] you can set group config for an exposure
[ ] you can set group config for a source
[ ] you can set access to private or protected (default) for a source
[ ] you can not set access for an exposure (they are inherently public)

As described here, referencing a resource outside of its supported access should raise an error (but otherwise should not).
Impact to Other Teams
none
Will backports be required?
none
Context
Notes from technical refinement:

would allow folks to set this for the source, and also for a specific table within a source
it's a config (enabled is the only one right now https://docs.getdbt.com/reference/source-configs), may be more complicated

Estimated based on there's a PR from Dave and some work needed to get that in

authors: ChenyuLInx graciegoheen


text:
[SEMANTIC-68] [Feature] Option to turn off 0 values from datespine

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Sometimes the datespining logic is relevant and helpful - it ensures that the BI tool has a consistent representation of the metric across the dimensions and ensures that the graphs returned don't look like scratches.
That being said, there are cases when the cardinality of a dimension and the data being logically time-grouped can result in the vast majority of rows returned being 0.
We should offer a config option that allows users to override this base behavior.
Describe alternatives you've considered
Not pursuing this issue.
Who will this benefit?
Anyone who is running into this problem.
Are you interested in contributing this feature?
Yes
Anything else?
No response

This will be part of #204 and won't be a config option - it will be the default behavior! Closing out this issue.


text:
Editorial fixes

What are you changing in this pull request and why?
Editorial fixes to a beta page
Checklist

[ ] Review the Content style guide so my content adheres to these guidelines.
[ ] For docs versioning, review how to version a whole page and version a block of content.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):

[ ] Add/remove page in website/sidebars.js
[ ] Provide a unique filename for new pages
[ ] Add an entry for deleted pages in website/vercel.json
[ ] Run link testing locally with npm run build to update the links that point to deleted pages

Merging changes to beta docs


text:
localhost connecting error

SQLSTATE[HY000] [1045] Access denied for user 'database username'@'localhost' (using password: YES)
how to fix this error

change the database credentials to match your own. In includes/config.php

repo: dcblogdev/loginregister


text:
"Bring your own shape" geometry

I have a set of data that I'm plotting on top of a map of the united states. I'm generating compose canvases for all the individual counties and it works very well, but I've been thinking about how to integrate this into Gadfly. What I came up with is basically a geometry that lets you specify your own Compose shape to be drawn (think of it like Geom.rectbin, but instead of rectangles you specify your own function to draw a compose object). With that something like this would be possible:
plot(data, shape="FIPS", shapefunc=draw_county, color="population", Geom.whatever)

which would draw a population heatmap. In this particular example draw_county(FIPS) would return a compose canvas for the county with the given FIPS code. Of course the interface can be debated about, but that's the basic idea. The geometry would possibly need to take some arguments such as the UnitBox for the shapes, but that's a detail.

There's now a Geom.polygon to draw polygons from coordinates, and Guide.annotation which can draw them directly with compose, so I'm calling this one done.

authors: Keno dcjones


text:
Theming defaults for AppChrome

Currently, in the UI we are using ThemeProvider in 2 locations to override variables for the AppChrome sidebar and header. We can remove these if we create updates to the AppChrome to match these values. This could even help to remove the @emotion/react  depedency altogether, as it's only used for ThemeProvider.
The previous defaults here seemed to match the old DC/OS theming with the dark header and sidebar. This is a good opportunity to align with the current design of our product using ui-kit.
We are able to change the fallback design token for bgAppHeader as it is only used by AppChrome and we would be overriding this value anyway in the UI. There was some auto-formatting on this fallbacks.json file also.
I've refactored the stories to better match the changes, with some extra cleanup.
All components have been refactored to move away from React.FC and the children props are explicitly set. It was not necessary for AppChrome to be a class component so that was converted to a memoized FC.
Added a TODO and I will revisit the two values that are set to hex codes that we do not have in our Design System. I have brought this up with product design and we will address this in the design token audit with our transition to Figma.
Overall, these changes should help us to tidy up some outdated and unnecessary code in the UI. I believe these changes will help with issues seen through setting up npm link too.

Testing
Startup Storybook and view the AppChrome stories.

Trade-offs

Dependencies

Screenshots

Checklist for PR creator

[ ] If any new components were added, there are exported from packages/index.ts
[ ] If this PR is associated with a JIRA, it is mentioned in commit message footer ("Closes …")
[ ] If this PR contains breaking changes, is stated in commit message body ("BREAKING CHANGE: …")
[x] Info for applicable sections above is provided

FYI this is probably a feature: and is a BREAKING CHANGE

repo: dcos-labs/ui-kit


text:
[System Tests] Automatically starting npm testing on dev.sh

This PR updates the dev.sh configuration script in order to automatically start a testing version of webpack and automatically configure proxy.dev to use the CLUSTER_URL  specified.
Effectively, using the ./system-tests/driver-config/dev.sh driver configuration script you can serve the current branch's version without the need of building a dist first.
For example, you should now use the following to run the tests:

docker run -it --rm --ipc=host \
  -v `pwd`:/dcos-ui \
  -e CLUSTER_URL=$OPEN_CLUSTER_URL \
  mesosphere/dcos-ui dcos-system-test-driver \
  ./system-tests/driver-config/dev.sh

L👀ks good!

authors: orlandohohmeier wavesoft

repo: dcos/dcos-ui


text:
DCOS-43373: Mark and translate jobs plugin constants

Testing
There should be no visual differences or markup changes after this PR is merged.
Dependencies
Once the dust settles we need to run npm run lingui-extract-with-plugins and commit the message catalog.
Notes
I was able to remove some unused job methods that depended on some unused job status constants

Unused code seems to be ok to remove

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

authors: brandonc mesosphere-ci nLight


text:
chore(deps): update dependency stylelint to v13.6.1

This PR contains the following updates:

Package
Type
Update
Change

stylelint (source)
devDependencies
patch
13.6.0 -> 13.6.1

Release Notes

stylelint/stylelint
v13.6.1
Compare Source

Fixed: max-empty-lines TypeError from inline comment with autofix and sugarss syntax (#4821).
Fixed: property-no-unknown false positives for namespaced variables (#4803).
Fixed: selector-type-no-unknown false positives for idents within ::part pseudo-elements (#4828).

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

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

v5.1.3
GitHub release

Your semantic-release bot :package::rocket:

authors: mesosphere-ci mesosphere-renovate


text:
Set DNS server only on dcos-net interface

Until now we were setting the dcos-net DNS server on all interfaces.
We should leave the host interface with its former DNS address.
Signed-off-by: Alin Gabriel Serdean aserdean@ovn.org
CC: @ionutbalutoiu

Please do not merge until a smoke CI run.

repo: dcos/dcos-windows


text:
exhibitor: Add back  to journald log messages

High Level Description
Adds back [myid:{}] to journald messages output which was removed in one of the previous patches. This is a backport of patch that is going to the master.
Related Issues

DCOS-15317 ZooKeeper log: ensure that myid is in the log

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

Could you review please @jgehrcke @vespian @gpaul

@mesosphere-mergebot label Ready For Review

Let's wait for Miguel to have a look.

authors: jgehrcke mhrabovcin

repo: dcos/dcos


text:
[master] Bump Mesos to nightly master da8cac1

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/22471b83a418e614b19a7ae50b73ee028dc7c363...da8cac1691cdb04c179e021980fbfd7773347095

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

Closing in lieu of #3104


text:
Added libseccomp package for dynamic linking with Mesos due to license.

DO NOT MERGE

Closed in lieu of https://github.com/dcos/dcos/pull/5460


text:
Mobile: search bar becomes microscopic

Would be nice for the narrow mobile view to put the search for below the nav bar.

In an effort to conserve the precious vertical screen real estate on mobile I did a little re-org of the top and footer nav links in #125  to make more space for search.

Closing because PR was merged.

authors: chappjc gozart1 raedah

repo: dcrdata/dcrdata

license: isc


text:
🛑 Danbs is down

In 3d6c59b, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3609 ms

Resolved: Danbs is back up in 5ad601d after 327 days, 15 hours, 33 minutes.

repo: ddanbs/upptime


text:
🛑 Danbs is down

In c1b851a, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 2411 ms

Resolved: Danbs is back up in fa0a295 after 14 minutes.


text:
🛑 Danbs is down

In 71a11de, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 266 ms

Resolved: Danbs is back up in 9f01e2b after 19 minutes.


text:
🛑 Danbs is down

In 2f32970, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 146 ms

Resolved: Danbs is back up in 39d3646.


text:
🛑 Danbs is down

In cc28204, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 160 ms

Resolved: Danbs is back up in 76e9c24.


text:
🛑 Danbs is down

In 635c8e0, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 919 ms

Resolved: Danbs is back up in bbfb8cd.


text:
Add menu item

Add menu item connected to backend
TODO: we need a getUser function that gets the current logged in user. This will help us get the user type (needed on many pages) and the chef (final thing needed when adding a menu item)

see no errors when I run it, in my opinion its good to merge so imma merge it 🦅

authors: Abdul-Andha BaljinderHothi


text:
Import frameworks from plist.

By applying this PR, Tuna get import framework list from the plist file stored ~/Library/Preferences/net.dealforest.Tuna.import.plist. If the plist file is not exists, the file will create.
When you want to customize import framework list, you can open ~/Library/Preferences/net.dealforest.Tuna.import.plist using Xcode and edit it.
After editing, new import framework list will be applied by restarting Xcode.

Temporarily close.
If it becomes necessary to the code, and use to cherry-pick.

authors: EZ-NET dealforest

repo: dealforest/Tuna


text:
Workflow seems to crash when typing in multi-item delimiter

I type in "fake Name ", and things look good. As soon as I type the DELIMITER character, the search resets back to "fake ".
If I instead type "fake Name  5", and then left arrow twice and add the DELIMITER, it works.

Yeah. It's meant to do that. You're not supposed to enter the delimiter (which is why it's a character not on your keyboard) by hand but to hit TAB on one of the data types. That will complete the name and add the delimiter and a trailing space for you. (If you hit ENTER it will copy 1 fake dataset to your clipboard, CMD+ENTER will also paste the fake data into the active app).
If you delete the trailing space (i.e. the delimiter is the last thing in the query), the workflow treats that as a "go back" instruction and will take you back to the list of all datatypes.

repo: deanishe/alfred-fakeum


text:
Image Download Error Cant download Images

Image is not downloading when using markdownloader

May I suggest that image links be included in the Markdown document:
![Image Text](URL of image)

authors: johnblommers skillhacker-code

repo: deathau/markdownload


text:
DBZ-2915  Use Testcontainers to setup Pulsar

Use  mvn clean install -pl debezium-server-pulsar -am -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn to run.
On commenting out withCopyFileToContainer property and running the existing changes produces:
Exception in thread "pool-4-thread-1" io.debezium.DebeziumException: org.apache.pulsar.client.api.PulsarClientException: java.util.concurrent.ExecutionException: org.apache.pulsar.client.api.PulsarClientException: java.util.concurrent.CompletionException: org.apache.pulsar.shade.io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:6650
        at io.debezium.server.pulsar.PulsarChangeConsumer.createProducer(PulsarChangeConsumer.java:110)
        at io.debezium.server.pulsar.PulsarChangeConsumer.lambda$handleBatch$1(PulsarChangeConsumer.java:121)
        at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1133)
        at io.debezium.server.pulsar.PulsarChangeConsumer.handleBatch(PulsarChangeConsumer.java:121)
        at io.debezium.embedded.ConvertingEngineBuilder.lambda$notifying$2(ConvertingEngineBuilder.java:82)
        at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:812)
        at io.debezium.embedded.ConvertingEngineBuilder$2.run(ConvertingEngineBuilder.java:171)
        at io.debezium.server.DebeziumServer.lambda$start$1(DebeziumServer.java:142)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)

There are config files under debezium-server-pulsar/docker/conf/ which have been used in the docker maven plugin as here. Upon looking into GenericContainer methods to do volume mapping using withClasspathResourceMapping (for eg here) in our case produced:
Caused by: java.lang.IllegalArgumentException: Resource with path /docker/conf/ could not be found on any of these classloaders: [jdk.internal.loader.ClassLoaders$AppClassLoader@5bc2b487, QuarkusClassLoader:Quarkus Base Runtime ClassLoader]

So certainly unsure of which method to use to map the config files and establish/start the container successfully.
cc: @gunnarmorling

@ani-sha, with those resources being under docker/conf, they were not part of the test classpath and thus not visible to the classloader of the test. I pushed a commit for moving them under test/resources to fix that. With that change and some corresponding adjustment, the test passes for me locally.

@ani-sha, with those resources being under docker/conf, they were not part of the test classpath and thus not visible to the classloader of the test. I pushed a commit for moving them under test/resources to fix that. With that change and some corresponding adjustment, the test passes for me locally.

Thanks @gunnarmorling, works for me as well. Marking the PR ready for review.

Thanks @gunnarmorling, works for me as well. Marking the PR ready for review.

https://issues.redhat.com/browse/DBZ-2915

https://issues.redhat.com/browse/DBZ-2915

Applied; thx!

Applied; thx!

authors: ani-sha gunnarmorling

repo: debezium/debezium


text:
DBZ-3169 Adds doc for debezium UI

Adding doc for the Debezium UI.

@rk3rn3r What's the current status of this PR? Can it be merged?

LGTM. One last question would be: Do we need to wrap this somehow that it only goes to the upstream docs and not yet to downstream? I think @roldanbob once said when a doc is not listed it will not be included.

LGTM. One last question would be: Do we need to wrap this somehow that it only goes to the upstream docs and not yet to downstream? I think @roldanbob once said when a doc is not listed it will not be included in downstream docs?

@rk3rn3r When I update docs for a downstream release, I fetch content only from the upstream branch that is aligned with that release, for example, for Q1, it was the 1.4 branch. So as long as the UI doc is backported to a release branch, I don't think that there's any concern about the content being inadvertently included downstream.

@rk3rn3r @mdrillin @indraraj So where exactly does this stand now?  This is tagged for 1.6, so should this be merged before next week's release or is this on hold until 1.7?

This should wait for 1.7. By then, we should be clear on where we stand
with the UI, we can update Mark's blog post, etc.

@mdrillin, @indraraj, @uidoyen, @rk3rn3r, is any update needed here still? Like new screenshots or similar?

I think similar to https://github.com/debezium/debezium.github.io/pull/644 we should describe application.properties and related environment variables better. Especially the ui.base.uri property / UI_BASE_URI env var.
@mdrillin could you maybe add that?

@mdrillin, @indraraj, @uidoyen, @rk3rn3r, is any update needed here still? Like new screenshots or similar?

For the screenshots, there is a slight change with the KAFKA_CONNECT_URI dropdown placement. And also I was thinking if we should also add a screenshot of the final "Review" step. @mdrillin
FYI I have made some recent modifications to show the hidden password and download the final config json.

And applied. Thanks, @mdrillin!

I think similar to debezium/debezium.github.io#644 we should describe application.properties and related environment variables better. Especially the ui.base.uri property / UI_BASE_URI env var. @mdrillin could you maybe add that?

I searched through Debezium's issue list and communication emails, as well as debezium-ui's online information, but I couldn't find the configuration address of the parameter ui.base.uri. I tried to set it in ui/packages/services/src/config/config. service.ts;
backend/src/main/resources/application.properties;
deployment/dbzui-config.sh;
ui/config/config.js;
Updating or adding configuration cannot modify the uri address of debezium-ui, which causes this service to only open port 8080 for this machine and cannot be accessed from the outside. In addition to using port forwarding to solve this problem, Do you have any other good suggestions, thank you!

@taoyuanai  Please have a look at https://github.com/debezium/debezium-ui/pull/398. The config options was required by the UI frontend to get the UI backend domain name and base path. The UI frontend got updated to use the path from the initial call. Thus, the config options was not required anymore and was removed with the forementioned PR.
Correct @indraraj ? Maybe you have the UI task / PR at hand where you changed that behavior?

yes I guess it was removed after this https://github.com/debezium/debezium-ui/pull/376

Maybe you have the UI task / PR at hand where you changed that behavior?

sure, lets discuss this

authors: Naros gunnarmorling indraraj jpechane mdrillin rk3rn3r roldanbob taoyuanai


text:
public some function

Sometimes we need to repeatedly squeezing a sponge, like newhope/poly.rs.
:D

I agree with making absorb/pad/squeeze pub, but imo finalize should remain unchanged. For convenience you can also add keccakf method to Keccak impl
impl Keccak {
/*
some code
*/

  #[inline]
  pub fn keccakf(&mut self) {
    keccakf(&mut self.a);
  }

/*
some code
*/
}

Thank you! I will release new version in few minutes! :)

Thank you! :D

1.1.0 released

authors: debris quininer

repo: debris/tiny-keccak


text:
Add catalog-info.yaml config file

This pull request adds a Backstage entity metadata file
to this repository so that the component can
be added to the software catalog.
After this pull request is merged, the component will become available.
For more information, read an overview of the Backstage software catalog.
View the import job in your app here.

Closing PR upon request for bulk import deletion. This request was created from Janus IDP Plugins.


text:
Added a litreview for some random guy

I think his name is Beru

:bear: :bear:

authors: Berulacks decause

repo: decause/bizlegfoss


text:
Cleaning up a request-response cycle regardless of errors

Consider this scenario where we are getting a Db instance to be shared throughout a request-response cycle:
// Preparation route for
ALL("/.*", (request, response, chain) -> {
    response.bind("db", getDb());
});

POST("/{id}", (request, response, chain) -> {
    Db db = (Db) response.getLocals().get("db");
    // this throws an runtime exception somewhere deep inside
    db.insert(something);
});

// Cleanup route
ALL("/.*", (request, response, chain) -> {
    Db db = (Db) response.getLocals().remove("db");
    db.release();
});

If an exception is thrown in POST then the cleanup route is never executed and we are now leaking Db connections.  Instead of trapping Db exceptions in every handler, it would be nice to be able to specify cleanup routes/routines that are guaranteed to execute at the end of the Request-Response cycle despite exceptions within the chain.  These mechanisms should be fail-safe themselves and should not have a chain parameter.
void cleanup(Request request, Response response);

The RouteHandlerChain or PippoFilter should execute these cleanup routines within independent try {} catch {} blocks.
for (CleanupHandler handler : cleanupHandlers) {
    try {
        handler.cleanup(request, response);
    } catch (Exception e) {
        log.error("Whoops", e);
    }
}

Perhaps these could be registered as:
// Cleanup route
CLEANUP("/.*", (request, response) -> {
    Db db = (Db) response.getLocals().remove("db");
    db.release();
});

Personal, I found two options:

use a RouteHandler (filter - no commit) and a custom ErrorHandler

setErrorHandler(new DefaultErrorHandler() {

    @Override
    public void handle(Exception exception, Request request, Response response) {
        >> here close database connection
        super(exception, request, response);
    }

}

>> here add routes

// Cleanup route
ALL("/.*", (request, response, chain) -> {
    Db db = (Db) response.getLocals().remove("db");
    db.release();
});

add a marker Finally for RouteHandler (Finally annotation or FinallyRouteHandler that extends RouteHandler) and in PippoFilter when we catch an exception in a RouteHandler then iterates through the chain, find FinallyRouteHandler and call them.

By the way. I think that it's better to change this code from PippoFilter
} catch (Exception e) {
    log.error(e.getMessage(), e);
    if (!response.isCommitted()) {
        errorHandler.handle(e, request, response);
    } else {
        log.debug("The response has already been committed. Cannot use the exception handler.");
    }
}

with a simple
} catch (Exception e) {
    log.error(e.getMessage(), e);
    errorHandler.handle(e, request, response);
}

and move the if/else block in (Default)ErrorHandler. In this mode we are more flexible.
What you think?

The first suggestion is how it could be done right now without API changes.  I don't care for this approach as I don't find it to be terribly elegant.
The second approach is more to my liking.  Annotations are nice.  That would work with a controller-based design but it would not work with Lambdas.  Hard classes are nice.  Would work with Lambdas but not controllers.  Do we need both?
As for the error handler change, sure as long as DefaultErrorHandler performs that check.

Hi guys, I don't know if a CLEANUP or FINALLY annotation is very clear for a new user it exists and it needs to use that. I remember @gitblit mentioning something that stuck: "the rule of least astonishment" and I guess it also applies to the custom number of things a new user needs to learn to use a new framework. I think we need to consider how often we expect the users to use this cleanup pattern before doing some custom things. I'm thinking you are referring to something alike "OpenSessionInView" or a MDC value kept in ThreadLocal.
Maybe something like a request listener(onbegin and onfinish) could be considered to support this?

A listener design would be another option.  I could go either way for my needs.
There are two nice things about the RouteHandler approach:

we are not adding a new mechanism with registration/removal methods
the appropriate cleanup/finally handler would be matched with uriPattern by the Router.

A listener mechanism would either need to also match by uriPattern or would be a global mechanism for all requests.  Having a global onFinished request listener could have other creative uses.
Like I said, either would solve the scenario I've outlined.  One is more targeted than the other.
I guess the real question should be: is cleanup/finally a filter or is it a listener?

It's important for adoption to have a steep learning curve. For this reason I wish to not introduce new concepts if not necessarily need.

I guess the real question should be: is cleanup/finally a filter or is it a listener?

I prefer a filter.
I propose an idea introduced by James (gitblit) in https://github.com/decebals/pippo/issues/66.
The idea consists in:

returns a Route in Application.ALL (in don't know if it's ok to make this modification for other methods - GET for example)
add a cleanup/finally method to Route

ALL("/.*", (request, response, chain) -> {
    >> here close database connection
}).cleanupOrFinally();

Make sense?

Yup.  That'll work when coupled with appropriate logic in PippoFilter.

Very nice. Maybe rephrase the method name as to suggest more of a flag setting, not an actual action.
I guess passing a lambda instead to cleanup( ()-> { .. }) is not a better option.

@balamaci I think that can be an idea (a finally block for a concrete route) but the implementation requires java 8 and for now I say to stay with java 7 for a while.
I created a new branch  finally to create a RFC for this feature.
I added new routes in BasicApplication to make some tests:
// throw a programatically exception
GET("/exception", new RouteHandler() {

    @Override
    public void handle(Request request, Response response, RouteHandlerChain chain) {
        throw new RuntimeException("My programatically error");
    }

});

// use a finally filter (invoked even when exceptions were raised in previous routes)
// test with route "/" and "/exception"
ALL("/.*", new RouteHandler() {

    @Override
    public void handle(Request request, Response response, RouteHandlerChain chain) {
        System.out.println(">>> Cleanup here");
    }

}).runAsFinally();

In the internet browser I made a request to http://localhost:8338/exception and I noticed that the cleanup filter is executed (for the moment I implemented nothing in PippoFilter related to runAsFinally flag).
I will inform you about evolution of this branch.

In the internet browser I made a request to http://localhost:8338/exception and I noticed that the cleanup filter is executed (for the moment I implemented nothing in PippoFilter related to runAsFinally flag).

After some tests I can infirm this affirmation.
I made some tests and I found some issues in actual pippo-core:

if I call "/not-found" from browser then "cleanup" filter is called because the URI pattern is ALL("/.*") (here I expect route not found)
I see a request "/favicon.ico" in pippo from browser (I resolved with 5c1c43d7318ff8f92c9848831de0868f39125d2f) that activate the "cleanup" filter and I don't want this behavior

Questions:

how we can solve first issue described above ("/not-found")?
do I want to call the "cleanup" filter if chain.next() was not called in previous route?
is it possible to write (and how) some unit tests for this feature (because I think that)?

In PippoFilter after the ignore paths check we should...
response.status(0);

Then after the check for !response.isCommitted() we should...
if (response.getStatus() == 0) {
    response.notFound();
    log.info("Handlers in chain did not set a status code for {} '{}'",
requestMethod, requestUri);
}

I implemented that last night but didn't propose it yet.  Works nicely.
Because of filters, we have to default to an uninitialized status code.  A
handler somewhere in the chain must set a status code, otherwise it's a 404.
-J
On Fri, Jan 30, 2015 at 11:36 AM, Decebal Suiu notifications@github.com
wrote:

In the internet browser I made a request to
http://localhost:8338/exception and I noticed that the cleanup filter is
executed (for the moment I implemented nothing in PippoFilter related to
runAsFinally flag).
After some tests I can infirm this affirmation.
I made some tests and I found some issues in actual pippo-core:

if I call "/not-found" from browser then "cleanup" filter is called
because the URI pattern is ALL("/.*") (here I expect route not found)
I see a request "/favicon.ico" in pippo from browser (I resolved
with 5c1c43d
https://github.com/decebals/pippo/commit/5c1c43d7318ff8f92c9848831de0868f39125d2f)
that activate the "cleanup" filter and I don't want this behavior

Questions:

how we can solve first issue described above ("/not-found")?
do I want to call the "cleanup" filter if chain.next() was not
called in previous route?
is it possible to write (and how) some unit tests for this feature
(because I think that)?

—
Reply to this email directly or view it on GitHub
https://github.com/decebals/pippo/issues/81#issuecomment-72229209.

I pushed a change to your finally branch to handle the /not-found scenario.  We couldn't use 0 on Jetty, so I used Integer.MAX_VALUE instead.  Some handler in the chain must set a status code, otherwise we trigger a 404.

I was not able to repeat your runAsFinally() observation - i.e. I disagree that that cleanup occurred after an exception was thrown.  Perhaps you were testing with the /not-found path which should have been a 404 but was not and also did not throw an exception.
I completed your implementation of runAsFinally() by integrating it into the  into the RouteHandlerChain and ensuring it's called from the finally block of PippoFilter.  It is now working as envisioned.
Side note, I find the IntelliJ Grep Console plugin to be very helpful in visually filtering out signal from noise.  It automatically colors debug, info, warn, etc differently.

I was not able to repeat your runAsFinally() observation - i.e. I disagree that that cleanup occurred after an exception was thrown. Perhaps you were testing with the /not-found path which should have been a 404 but was not and also did not throw an exception.

It was my mistake.
I like IntelliJ Grep Console plugin.
Can we find a better name for runAsFinally or it's ok? Now in RouteHandlerChain we have cleanup and maybe it's good to use the same term to mark a cleanup route.

I like both finally and cleanup.  Unfortunately "finally", by itself, is a
reserved keyword.  I'm happy with whichever you prefer.

Just an observation. Now I see that I can call chain.cleanup() (accidentally or not) in a route handler. Is it ok?

Resolved by #84.

authors: balamaci decebals gitblit

repo: decebals/pippo


text:
Caching Cleanup + Timer clearing update

Description
This took me longer than I expected. The original goal of this PR was to clean up some of the redundancy in the master copy lookup and caching. While doing this I uncovered a loading issue. I'll go through a code review and talk about the specific changes as I only have an assumption on why my changes caused this issue to pop up.
Issue Arises
So after create useMasterCopy and updating all the places that use the same pattern. I started noticing that the original decrease was erased and requests increased. After several console logs through out the loading places that were loading either out of sequence or now causing re-renders that were not being revealed before as the previous RPC request held these things up.
The Fix

useUpdateTimer in useProposals
When loading a Azorius DAO (pre-fix) it would for a moment load as a Multisig DAO, which caused me to notice that the setMethodInterval was firing in the background. This was also happening after switching from viewing one to another via links (Hierarchy Page and parent-safe link).

useGovernanceContract logic cleanup
This seemed in the end to be causing extra re-renders. I cleaned up the logic a bit and seems to be working now as expected.

Notes
Every once in a while, if clicking between DAOs very quickly I would run into the ErrorBoundaryScreen and would need to reload but was pressing around really quickly.
Issue
Testing
To test that everything is working as expected. I'd would main checking this PR by loading different DAO in different ways.

via Search
via Hierarchy Page
via Reload

Then just do a few reloads on the deeper pages to make sure state is still loading correctly.
Screenshots (if applicable)

My testing:

Attempting to load Azorius DAO

No wallet connected

[x] via Search
[x] via Reload
[ ] via Hierarchy Page

Frame wallet connected via Browser Wallet

[x] via Search
[x] via Reload
[ ] via Hierarchy Page

Safe connected via WalletConnect

[x] via Search
[x] via Reload
[ ] via Hierarchy Page

Attempting to load Multisig DAO

No wallet connected

[x] via Search
[x] via Reload
[ ] via Hierarchy Page

Frame wallet connected via Browser Wallet

[x] via Search
[x] via Reload
[ ] via Hierarchy Page

Safe connected via WalletConnect

[x] via Search
[x] via Reload
[ ] via Hierarchy Page

@Da-Colon @tomstuart123 do you have any sepolia daos offhand that have some hierarchy set up that I can use for testing?

@adamgall looks like we are good to go for another round of testing. Sorry for this misfire. The 'reload' screen issue that pops up every once in a while seems to be a problem with some state somewhere in VoteContext. Gonna see if I can locate it.
This same component seems to show up alot with the 429 errors too so gonna take a closer look.

authors: Da-Colon adamgall

repo: decent-dao/fractal-interface


text:
Stop fetching VP score when the user creates a Like/Favorite

Replacement Candidates:

background job that loads VP on batch (order by update)

@2fd is this still needed?

@pentreathm yes

repo: decentraland/places


text:
Add VerifierAlgorithm for ES256

This is the answer to:
https://github.com/decentralized-identity/did-jwt/pull/248#pullrequestreview-1095293061
Update VerifierAlgorithm.ts for ES256.
Update VerifierAlgorithm.test.ts for ES256.
I had to re-declare some variables locally for ES256. Is it appropriate to move some globally declared variables for ES256K and ed25519 or just leave them?

I should note that I am making progress with JWT.ts and JWT.test.ts. This may be relevant to the VerifierAlgorithm.ts. Maybe we should wait for that?

I had to re-declare some variables locally for ES256. Is it appropriate to move some globally declared variables for ES256K and ed25519 or just leave them?

Don't concern yourself too much with refactoring. While that is very important, I'd like to separate any refactoring changes from feature implementations.
If you do want to contribute refactoring PRs, please separate code-refactoring-PRs from test-refactoring-PRs to ease the review.
Thank you for coming back with small PRs, it makes this process so much easier!

authors: bshambaugh mirceanis

repo: decentralized-identity/did-jwt


text:
Define use of initial state / align with sidetree.

Formerly: https://github.com/openssi/peer-did-method-spec/issues/129
We need a paragraph on how initial-state works, and how to pass the first delta.

@peacekeeper ping.

When this ticket is complete, we will have addressed the concern that @TelegramSam raised in https://github.com/openssi/peer-did-method-spec/issues/96.


text:
Autofill of session code via hash doesn't work

Seems like the onload EventListener added if a session code is detected via URL hash does not trigger. Some other way to call the connect() function in the client with a delay is necessary.

"load" events are NOT fired on body elements.

authors: monofon salbeira

repo: decker-edu/quizzer


text:
Ability to set the EXIF/GPS metadata dates from the File Properties "Date Modified" within existing Edit Date/Time utility

Is your feature request related to a problem? Please describe.
Editing tags and performing other modifications with images that lack Date/Time metadata within their EXIF data (such as those downloaded from social networking sites) causes the File Modified date to be set to the current time, shooting it up to the top of the chronological gallery.
From the way the Android media access works, this behaviour is expected, but not ideal, as people may expect their media to still be on the correct place in the chronological gallery even after they've modified and edited it.
Describe the solution you'd like
Adding functionality to the existing "Edit Date and Time" utility to get the Last Modified Date from the file properties and embedding it into the file's EXIF and GPS metadata would be heavily appreciated.
It might also be done automatically when the tags and other metadata are edited for media that does not contain EXIF/GPS date, to prevent the user from being surprised with the loss of date information.
Describe alternatives you've considered
I do believe other applications, namely Google Photos, allows modification of media descriptions and metadata without affecting the date. However, I've chosen Aves due to its unparalleled ability to view and modify metadata without propieratary services or file formats - and it's been great at that.
Additional context
I do believe similar functionality was implemented in #111 , but that only gets the Date from the filename, not the Last Modified date from file properties.

I remember in #111 rejecting the idea of automatically editing the date when moving/renaming files, but automatically editing the date when editing metadata (tag, orientation, non-exif metadata removal) sounds fair.
Regarding the "Edit Date and Time" utility, I also wanted to allow copying from one field to another, so I'll do this work together with what you suggest.
Google Photos, as far as I know, doesn't actually modify the files when you edit descriptions or locations. Editing these metadata is only available when your files are backed up, as the metadata is stored by Google. People who wish to retrieve that metadata need to export their photos with Google Takeout, and the metadata is in separate JSON files.

repo: deckerst/aves


text:
Support installation of specific version is not supported

At the moment, it is only possible to install the latest version of the package.

We should support installation of specific versions by adding version to PackageQuery's value.

Now queries are supported: @deep-foundation/pow@0.0.9, @deep-foundation/pow and so on.

repo: deep-foundation/npm-packager

license: Unlicense


text:
Startup script

Hi.
Have anyone made a startup script for rtsptoweb and want to share it
I'l need a script so rtsptoweb start  when server starts.
Tanks
Ivan

docker-compose isn't enough for you? Thats what makes it start for me on boot

Have never used docker-compose :-)   But tanks for the answer

I am using Linux Services for start the rtsptoweb when the server starts. This is my services configure
[Unit]
Description=RTSP to Web Service
After=network.target

[Service]
WorkingDirectory=/home/pi/RTSPtoWeb
ExecStart=go run RTSPtoWeb.go apiHTTPRouter.go hlsFragment.go storageClient.go storageStreamHLS.go apiHTTPChannel.go  apiHTTPSaveMP4.go  hlsMuxer.go     storageConfig.go         storageStruct.go apiHTTPHLS.go      apiHTTPServer.go   hlsSegment.go   storageServer.go         streamCore.go apiHTTPHLSLL.go    apiHTTPStream.go   loggingLog.go   storageStream.go         streamRemoteAuthorization.go apiHTTPMSE.go      apiHTTPWebRTC.go   serverRTSP.go   storageStreamChannel.go  supportFunc.go
Environment="GO111MODULE=on"
User=pi
Group=pi

[Install]
WantedBy=multi-user.target

Hi. Tanks for this 🥇

repo: deepch/RTSPtoWeb


text:
[Controller/Mysql] modify mysql issu

This PR is for:

I think this is a hotfix and the 6.40.0 should be trashed, and new tag is needed.
I'm suggesting this because it's hard for user to rollback those database change and issued tag should be avoid. Plus tagging won't take a lot of time & efforts.

6.40.0 is still listed in release page, which is claiming that 6.40.0 is a version officially supported. @Ericsssss @xiaochaoren1

authors: Ericsssss jiekun

repo: deepflowio/deepflow


text:
[Lgbm] support multi type prediction

Description
This PR is primarily aimed at implementing data inference functionality using the LightGBM model, supporting various types of inference including Raw Score, Leaf Index, and Feature Contribution. The inference task is accomplished through JNI calls to the LightGBM C API, and the results are returned in the form of a ByteBuffer for further processing.

Backward Incompatible Changes: There are no backward incompatible changes in this update. It mainly introduces new functionalities without altering the behavior of existing features. Therefore, existing code and functionalities should not be affected by this change.
Interesting Edge Cases to Note:

When the prediction type is Leaf Index, although the LightGBM C API returns the results as floating-point numbers (double), these values are actually integer indices. Therefore, when processing these values, it might be necessary to convert them into integer types.

Codecov Report
Attention: Patch coverage is 68.51852% with 17 lines in your changes missing coverage. Please review.

Project coverage is 72.41%. Comparing base (bd7f4ca) to head (03e9809).
Report is 3 commits behind head on master.

Files
Patch %
Lines

...src/main/java/ai/djl/ml/lightgbm/jni/JniUtils.java
48.00%
12 Missing and 1 partial :warning:

...bm/src/main/java/ai/djl/ml/lightgbm/LgbmModel.java
71.42%
0 Missing and 2 partials :warning:

.../main/java/ai/djl/ml/lightgbm/LgbmSymbolBlock.java
90.90%
1 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #3237      +/-   ##
============================================
+ Coverage     64.26%   72.41%   +8.15%
- Complexity     6455     7317     +862
============================================
  Files           676      676
  Lines         32443    32486      +43
  Branches       3417     3425       +8
============================================
+ Hits          20849    23525    +2676
+ Misses        10016     7346    -2670
- Partials       1578     1615      +37

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

repo: deepjavalibrary/djl


text:
Transformations for 3d images

Hello 2 questions

as the transformations are implemented in pure Jax they are differentiable in most cases - am I right? (more precisely I am considering putting the probability of applying transform as learnable parameter)
is it possible to use transformations in 3D images (Magnetic resonance imagiing)?

Hello @jakubMitura14 !

That will be transformation dependent, I know some are differentiable but I would not be able to answer about all of them as a whole. If you have questions about specific ones, we can take a look at those.
What you can do is vmap the transformations you want to do over the slice (slice as in MRI slice) axis. That way you can apply the same transformation to the whole 3D image. However that will still apply 2D transformations. There might be some of the transformations that are 3D friendly but from what I recall most actually expect the third dimension to be channel and treat it as such.

Thank You ! I am mainly thinking about the differentiability of brightness, gamma, rotate and elastic deformation

Hey @jakubMitura14, they are all differentiable indeed. If you hit any issues with your setup/experiment, please do let us know so we can look into it (or you can have a look and send a PR if you want to!) 😄


text:
Bug: reconnection problems on mobile

This is a long-shot, we don't know where this error lives; nginx, cloudflare or deepstream but we experience that it started to show up after upgrading to deepstream 2.x.
So after waking up our mobile app after a period of sleep longer than heartbeat interval it will try to reestablish the websocket connection. Often it doesn't take any time at all and all is fine but sometimes, pretty often it takes up to 30 seconds before it succeeds. This happens on both Android and iOS (both relying on deepstream-client-js) So we don't think it is frontend related. The error we see looks like this:
{
"timestamp": 1501003753273,
"error": "heartbeat not received in the last 20000 milliseconds",
"event": "connectionError",
"topic": "C"
},
{
"timestamp": 1501003754312,
"error": ""{"isTrusted":true}",
"event": "connectionError",
"topic": "C"
},
{
"timestamp": 1501003755345,
"error": "{"isTrusted":true}",
"event": "connectionError",
"topic": "C"
},
{
"timestamp": 1501003755834,
"error": "{"isTrusted":true}",
"event": "connectionError",
"topic": "C"
},
...... goes on until it succeeds and then a lot of these:
{
"timestamp": 1501003801150,
"error": "emailAccount/xxxxx",
"event": "MULTIPLE_SUBSCRIPTIONS",
"topic": "R"
},
{
"timestamp": 1501003801164,
"error": "emailAccount/xxxxx",
"event": "MULTIPLE_SUBSCRIPTIONS",
"topic": "R"
},
{
"timestamp": 1501003801188,
"error": "role/xxxx",
"event": "MULTIPLE_SUBSCRIPTIONS",
"topic": "R"
},
... etc
Its always when reconnecting, never on a fresh start.
I have experimented with reconnection intervals, heartbeat intervals and all that but found nothing. Also one user has reported this on his desktop client bu we have never been able to replicate that.
I have also tried with different networks, wifi, really slow mobile data etc but it doesn't seem to make any difference either
clientOptions: {
maxReconnectAttempts: Infinity,
reconnectIntervalIncrement: 1500,
rpcAckTimeout: 20000,
rpcResponseTimeout: 20000,
subscriptionTimeout: 20000,
recordReadAckTimeout: 20000,
recordReadTimeout: 20000,
recordDeleteTimeout: 20000,
heartbeatInterval: 10000,
maxReconnectInterval: 5000
}
Anyone else experience symptoms like these?

hey! Sorry for the delay. We have just upgraded uws to the latest version and have the suspicion it will be fix this issue. There should be an RC release out tomorrow which you can try out.

So after waking up our mobile app after a period of sleep longer than heartbeat interval it will try to reestablish the websocket connection. Often it doesn't take any time at all and all is fine but sometimes, pretty often it takes up to 30 seconds before it succeeds.

Is there a possibility you need the same hook we have in java, where you can inform the client to go into network_disconnected mode and then reconnected again when resumed?

Hi,
Thank you for your answer, I planned to wait for your uws upgrade before posting this but it took a while. I will try with the new version and report back.
Maybe we need some custom tear-down logic but it worked perfect before so something changed, possibly uws.

No worries, apologies for the time it took to get that update out. Required a bit of C++ build stuff which is always fun.

Closing due to inactivity

authors: daviderenger yasserf


text:
Feature/distributed state registry

The distributed state registry on its own. I think this might be useful for a couple of cases, e.g. keeping remote server urls for failover, keeping track of listeners etc.
There is a todo left which regards cluster-presence. In order to make sure that all nodes within a cluster are still present, we might want to implement a global registry, rather than many local ones. Let's talk about this on Monday.

Coverage decreased (-0.4%) to 96.132% when pulling 5335f8e78bb51d4419726ec8d424fa4fc3de5cbe on feature/distributed-state-registry into b026f5454834ec627cecd9740484f4e260f45cb1 on master.

Just a question. Wouldn't it be better to have a state registry connector instead and use existing services, e.g. etcd, zookeeper or consul?

We feel that it's important for deepstream going forward to be a truly distributed system without master/slave relationships or a centralized state registry (if we needed that, we could have just written to the cache)

@WolframHempel: All of the tree software I listed are distributed key-value stores... I'm not saying it's a bad idea do have it native in ds. Just wondering if the option has been considered.
Implementing a consensus algorithm is no small task...

Coverage decreased (-0.4%) to 96.132% when pulling 42f92dfc467628444c1da67fe115701d33abf7d8 on feature/distributed-state-registry into b026f5454834ec627cecd9740484f4e260f45cb1 on master.

@ronag there was a discussion about whether we can leverage other technologies ability for that. Problem is however that we have a flexible set of plugins and we don't want to suddenly tie ourselves down.
We are also working on a lightweight peer2peer messaging layer incase a distributed message system is considered overkill, which wouldn't work without native implementation. Hope that clears it up!

authors: WolframHempel coveralls ronag yasserf


text:
feature:Inferring UI from a chatGPT prompt

I realize our goal for trying to stay true to good-old Hypercard, but a UI by inference would be a cutting-edge approach for Wyldcard to build user interfaces that leverages natural language processing and machine learning techniques to generate UI elements on the fly based on text input. With UI by inference, developers can create highly flexible and customizable conversational interfaces that can adapt to a wide range of use cases, without the need for manual UI design or coding. By empowering users to interact with technology using natural language, UI by inference represents the next frontier in user interface design.
I realize there are challenges, like layout templating and the like, but here is one way we can do it:
Provided we have integrated ChatGPT, take a prompt as input, parse it into object(s), nouns, adjectives and propositions using the Stanford NLP library, and then building a script that creates a memory-resident card (or a persistent one, depending on use case) for that object, then show it to the user for input, and finally build and pass the response back out to ChatGPT for further processing. Here is sample code, followed by a a few prompts. None of it has been tested.
import io.github.bensku.spacelang.SpaCyLang;
import io.github.bensku.spacelang.api.Model;
import io.github.bensku.spacelang.api.ModelPackage;
import io.github.bensku.spacelang.api.Token;
import io.github.bensku.spacelang.api.Tokenizer;
import io.github.bensku.spacelang.impl.SpaCy;
import io.github.bensku.spacelang.impl.model.BaseModelPackage;
import com.defano.wyldcard.runtime.ExecutionContext;
import com.defano.hypertalk.exception.HtException;
import com.defano.hypertalk.exception.HtSemanticException;
import java.util.ArrayList;
import java.util.List;
public class InferredPromptCard {
private String prompt;
private List fieldNames;
private ExecutionContext context;
public InferredPromptCard(ExecutionContext context, String prompt, List<String> fieldNames) {
    this.context = context;
    this.prompt = prompt;
    this.fieldNames = fieldNames;
}

public void createCard() throws HtException {
    // Load the Spacy model
    ModelPackage spacyModel = new BaseModelPackage();
    Model model = spacyModel.load("en_core_web_sm");

    // Parse the prompt using the Spacy model
    List<Token> tokens = new ArrayList<>();
    Tokenizer tokenizer = new SpaCy().tokenizer(model);
    tokenizer.tokenize(prompt).forEachRemaining(tokens::add);

    // Extract the field values from the parsed prompt
    List<String> fieldValues = new ArrayList<>();
    for (String fieldName : fieldNames) {
        String fieldValue = "";
        for (Token token : tokens) {
            if (token.getPos().equals("NOUN") && token.getDep().equals("dobj") && token.getText().toLowerCase().contains(fieldName.toLowerCase())) {
                fieldValue = token.getText();
            }
        }
        fieldValues.add(fieldValue);
    }

    // Generate a HyperTalk script to create a new card with input fields for each field name
    String script = "domenu \"new card\"\n";
    script += "set the name of card to \"Inferred Prompt Card\"\n";

    for (int i = 0; i < fieldNames.size(); i++) {
        String fieldName = fieldNames.get(i);
        String fieldValue = fieldValues.get(i);

        script += "domenu \"new field\"\n";
        script += "set the name of last field to \"" + fieldName + "\"\n";
        script += "set the width of last field to 150\n";
        script += "set the height of last field to 20\n";
        if (i > 0) {
            script += "set the top of last field to the bottom of last card's field \"" + fieldNames.get(i - 1) + "\" + 10\n";
        }

        if (!fieldValue.isEmpty()) {
            script += "set the text of field \"" + fieldName + "\" to \"" + fieldValue + "\"\n";
        }
    }

    // Execute the HyperTalk script in the WyldCard context
    try {
        context.evaluate(script);
    } catch (HtSemanticException e) {
        throw new HtException("Error creating inferred prompt card: " + e.getMessage());
    }
}

}
-------‐--------  unit test -------------
import com.defano.hypertalk.exception.HtException;
import com.defano.wyldcard.runtime.ExecutionContext;
import org.junit.jupiter.api.Test;
import java.util.Arrays;
import java.util.List;
import static org.mockito.Mockito.*;
public class InferredPromptCardTest {
@Test
public void testCreateCard() throws HtException {
    // Create a mocked WyldCard execution context
    ExecutionContext context = mock(ExecutionContext.class);

    // Define the prompts and corresponding field names
    String pizzaPrompt = "I would like a pepperoni pizza with mushrooms, delivered to 123 Main St.";
    List<String> pizzaFields = Arrays.asList("size", "toppings", "address");

    String drinkPrompt = "I want a large iced coffee with cream and sugar.";
    List<String> drinkFields = Arrays.asList("size", "drink", "cream", "sugar");

    String emailPrompt = "Please send an email to John Doe at john.doe@example.com with the subject \"Important meeting\".";
    List<String> emailFields = Arrays.asList("recipient", "recipient email", "subject");

    String flightPrompt = "I need to book a flight from Los Angeles to New York City for two people departing on June 15th and returning on June 20th.";
    List<String> flightFields = Arrays.asList("origin", "destination", "passengers", "departure date", "return date");

    // Create the inferred prompt cards and execute the unit tests
    InferredPromptCard pizzaCard = new InferredPromptCard(context, pizzaPrompt, pizzaFields);
    pizzaCard.createCard();
    verify(context, times(1)).evaluate(anyString()); // Verify that the card creation script was executed once

    InferredPromptCard drinkCard = new InferredPromptCard(context, drinkPrompt, drinkFields);
    drinkCard.createCard();
    verify(context, times(2)).evaluate(anyString()); // Verify that the card creation script was executed twice

    InferredPromptCard emailCard = new InferredPromptCard(context, emailPrompt, emailFields);
    emailCard.createCard();
    verify(context, times(3)).evaluate(anyString()); // Verify that the card creation script was executed thrice

    InferredPromptCard flightCard = new InferredPromptCard(context, flightPrompt, flightFields);
    flightCard.createCard();
    verify(context, times(4)).evaluate(anyString()); // Verify that the card creation script was executed four times
}

}

The project will not catch on beyond people who used the original HyperCard and those who want to research the original, for a variety of reasons. If you want the project to appeal to the modern consumer, there are a multitude of changes you need to make, to the point where you may as well just make a new project (and at that point, you have the freedom to not have to bother with a new programming langauge. Just save tokens by asking ChatGPT to create a json file).

authors: IoIxD ooper-zz

repo: defano/wyldcard


text:
HONOLULU, HAWAII

Hi @kayceebeardeaux ,
To add your city, please provide email addressed and an email that we can add. Check out the guidelines here and submit an new request: email guidelines
Thanks!

authors: kayceebeardeaux swallan


text:
Can't create a repo in an organization

I'm trying to create a repo in my org's space but I'm getting an error:

git create orgname/reponame
unexpected argument: sfu/ca_sfu_icat_calscheduler
usage: …

This was added in fc0e05c437ad9d0cd2b8ec23d16004c3d2efe45e but is yet unreleased. You can install hub from master with OS X Homebrew: brew upgrade hub --HEAD
Or you can get the source and rake install

authors: grahamb mislav

repo: defunkt/hub


text:
Changing delimiters should only affect the upcoming text.

I am not sure if/how this issue relates to issue #84
using the dataset {"a":"a", "b":"b", "c":"c", "d":"d", "e":"e", "f":"f"}
The following:
<%a%>
{{b}}
{{=<% %>=}}
<%c%>
{{d}}
<%={{ }}=%>
{{e}}
<%f%>

Should result in:
<%a%>
b
c
{{d}}
e
<%f%>

But it actually results in:
a
b
c
d
e
<%f%>

This is very bad if you want to use both server-side and clien-side templates within one file. I checked the code and couldn't think of a quick-fix because this bug is inherent in the way the parser works: just search the whole template for the first match to a regex, replace this match then restart, from the beginning. It would rather need to restart from the previous match position.

This is possibly a duplicate of issue #35, which has been fixed in the development branch.  See this test case, for example.  Just to be sure, I'll try to confirm that the example in the original comment above works in the development branch.

Yes, the test case presented in the original comment above works as expected in the development branch:
>>> import pystache
>>> context = {"a":"a", "b":"b", "c":"c", "d":"d", "e":"e", "f":"f"}
>>> template = """<%a%>
... {{b}}
... {{=<% %>=}}
... <%c%>
... {{d}}
... <%={{ }}=%>
... {{e}}
... <%f%>"""
>>> print pystache.render(template, context)
<%a%>
b
c
{{d}}
e
<%f%>
>>>

authors: cjerdonek lucasb-eyer

repo: defunkt/pystache


text:
Import not working for Little Trouble in Big Absalom

It gets stuck at Madame Trunchsnuffle during import process.
PF2e: v6.5.0
FVTT: v12.331
Importer: v4.61

Same issue here, tested on an empty world, getting this error:
simeek.actor.webp saved to helyx/little-trouble-in-big-absalom/actors [foundry.js:70651:22](https://foundry.dawid-izydor.pl/scripts/foundry.js) simeek.token.webp saved to helyx/little-trouble-in-big-absalom/actors [foundry.js:70651:22](https://foundry.dawid-izydor.pl/scripts/foundry.js) Uncaught (in promise) TypeError: d is null     #preCreateDocumentArray https://foundry.dawid-izydor.pl/scripts/foundry-esm.js:56315     _createDocuments https://foundry.dawid-izydor.pl/scripts/foundry-esm.js:56275     create https://foundry.dawid-izydor.pl/scripts/foundry-esm.js:12264     createDocuments https://foundry.dawid-izydor.pl/scripts/foundry-esm.js:11407     create https://foundry.dawid-izydor.pl/scripts/foundry-esm.js:11550     #import_actor https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     #import_entry_step3 https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     #import_entry https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     #import_entries https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     async* https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     do_start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0xe0b752 https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0x21d80b https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     promise callback*state https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     proceed https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     #run https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     do_start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0xe0b752 https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0x21d80b https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     promise callback*state https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     proceed https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     import_folders https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     promise callback*#import_folders https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     do_start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0xe0b752 https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0x21d80b https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     promise callback*state https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     proceed https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     #prepare https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     <anonymous> https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     do_start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0xe0b752 https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0x21d80b https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     promise callback*state https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     proceed https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     load_items https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     #load_items https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     <anonymous> https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     do_start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0xe0b752 https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     start https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     _0x21d80b https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1     promise callback*state https://foundry.dawid-izydor.pl/modules/pf2-pdf-en-import/src/helyx.bundle.js:1

confirmed. Dragon Faery renamed Fey Dragonet in remaster.

Fixed for next release

Fixed and released

authors: DawidIzydor deidril nickkeane


text:
Failed health checks still deploy

From @sstarcher on May 3, 2016 17:19
I created an app that without proper configuration would fail health checks.  The following steps were followed.

Deis create app
git push deis
First version of app is deployed and in a crashback loop as expected
deis config:set HEALTHCHECK_URL=/
Second app version deployed and in a crashback loop as expected.  At this point kubectl get rcs --namespace=app shows 2 app versions are in a crashback loop
deis config:set rest of data to make app function
Third app version claims it has passed the health check, but the app takes several minutes to start up.  At this point the deis router routes to the app and gives a 503 even though the deis command line shows the app is good.  deis info shows version 3 of the app is up
Third version of the app finally comes up after several minutes and the router routes correctly to the app.
deis config:set is used to break the application configuration.
Fourth version of the app comes up and deis believes it has passed the health check.  Deis removes the third version of the app and now the router is back to a 503.

End result is
NAME                 READY     STATUS             RESTARTS   AGE
hound-v1-cmd-2fe47   0/1       CrashLoopBackOff   20         1h
hound-v2-cmd-qggwg   0/1       Error              5          33m
hound-v4-cmd-dw6u6   0/1       CrashLoopBackOff   6          9m

Old RCs are still hanging around and the app is down due to the third version being deleted prior to the 4th version passing health checks.
deis config:list
HEALTHCHECK_FAILURE_THRESHOLD      3
HEALTHCHECK_INITIAL_DELAY          1080
HEALTHCHECK_PERIOD_SECONDS         10
HEALTHCHECK_PORT                   5000
HEALTHCHECK_SUCCESS_THRESHOLD      1
HEALTHCHECK_TIMEOUT                400
HEALTHCHECK_URL                    /

Copied from original issue: deis/workflow#214

As it stand right now Deis has various timeouts when it is checking the kubernetes API and seeing if the pods are up and running. This is roughly ~2 mins timeout or so...
However Deis is not stopping the deploy if you see a situation like you are describing, it could end in a scenario where you have your old RC deleted. There is a failsafe switch that is supposed to rather bring up the old RC (up to previous scale) and kill off the new RC; seems like that is not kicking in for you.
One thing to take note of is the high initial delay and high timeout - We account for neither right now in our timeout handling for deploy / scale operations

@helgi thank you for the additional info.  I have now seen in several different occasions a healthy running app being updated with an app that never passes the health check and the old healthy RC is deleted which takes down the app.

Is it intended going forward that git push deis can succeed, but the application is never put live?  I don't believe that was the case in Deis v1.
Going forward will users need to query Deis to verify the new release succeeded?

@sstarcher I believe there may be a bug in the builder that is showing you success when it should be a failure.
The intent is not to have people verify these by hand, my point in the previous comment was more to list out what we may not be accounting for yet and could be making Deis return earlier, and do additional actions. Such as our cleanup procedure might be kicking in and killing v3 for you.
The way deploy works is that we bring in 1 pod of the new app, and remove 1 pod of the old (which we also did in v1; v2 does try to do more than 1 in/out if it has capacity if you are using current master and you can set DEIS_DEPLOY_BATCHES to 4 if you want 4 in/out kind of deployment) - With that model we will bring in the pod and query k8s on various status checks (including the health check), however we generally only have a 2 minute timeout on that operation.
Now if you consider the 2 minute timeout and then start looking at the fact you have a 1080 second INITIAL_DELAY (18 minute delay) then kubernetes won't even start consider to check the health of the app (readiness nor liveness) until after 18 minutes. During that time the pod should not be attached to the Service (in kubernetes) and thus not routable
If you have more than 1 pod then this will compound and deploy of the pods will take quite a wile, at least for kubernetes to funnel it into active usage
http://kubernetes.io/docs/user-guide/pod-states/ may help understand things beyond my ramblings :)
This is the key thing:

The default state of Readiness before the initial delay is Failure

Right now Deis combines your healthcheck into a readiness and a liveness check
It would help if you could put the controller log into a gist and link here for one of your deploys so I can see what's happening so we can come up with a plan of action.
Hope this sheds a bit of light, let me know if you need more info on a particular piece

I removed the 10.245.188.1 "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http" from the other applications.  v10 was the functional application that got scaled out of existence.  v11 had it's config changed to ensure it would fail the health check.
INFO app-latest: config app-latest-739613e updated
INFO app-latest: release app-latest-v11 created
INFO [app-latest]: jenkins changed HEALTHCHECK_URL
DEBUG create app-latest
DEBUG deploy app-latest-v11-cmd, img app-latest:git-7940f64b, params {'envs': {'HEALTHCHECK_PERIOD_SECONDS': 10, 'HEALTHCHECK_TIMEOUT': 120, 'HEALTHCHECK_FAILURE_THRESHOLD': 10, 'HEALTHCHECK_PORT': 8080, 'deis_whitelist': '10.0.0.0/16', 'HEALTHCHECK_URL': '/servlet/noooo', 'HEALTHCHECK_SUCCESS_THRESHOLD': 1, 'HEALTHCHECK_INITIAL_DELAY': 60, 'profile': 'aws-us-east-1-production-web'}, 'version': 'v11', 'healthcheck': {'timeout': 120, 'path': '/servlet/noooo', 'success_threshold': 1, 'period_seconds': 10, 'failure_threshold': 10, 'delay': 60, 'port': 8080}, 'batches': None, 'app_type': 'cmd', 'build_type': 'dockerfile', 'cpu': {}, 'replicas': 1, 'tags': {}, 'memory': {}, 'routable': True}, cmd ""
DEBUG scaling release app-latest-v11-cmd to 1 out of final 1
DEBUG waiting for 1 pods in app-latest namespace to be in services (120s timeout)
DEBUG waited 10s and 0 pods are in service
DEBUG waited 20s and 0 pods are in service
DEBUG waited 30s and 0 pods are in service
DEBUG waited 40s and 0 pods are in service
DEBUG waited 50s and 0 pods are in service
DEBUG waited 60s and 0 pods are in service
DEBUG waited 70s and 0 pods are in service
DEBUG waited 80s and 0 pods are in service
DEBUG waited 90s and 0 pods are in service
DEBUG waited 100s and 0 pods are in service
DEBUG waited 110s and 0 pods are in service
DEBUG 0 out of 1 pods in namespace app-latest are in service
DEBUG scaling old release app-latest-v10-cmd from original 1 to 0
DEBUG scaling RC app-latest-v10-cmd in Namespace app-latest from 1 to 0 replicas
DEBUG waiting for RC app-latest-v10-cmd to get a newer resource version than 94307274 (30s timeout)
DEBUG RC app-latest-v10-cmd has a new resource version 95173194
DEBUG waiting for 1 pods in app-latest namespace to be terminated (30s timeout)
DEBUG waited 10s and 0 pods out of 1 are fully terminated
DEBUG waited 20s and 0 pods out of 1 are fully terminated
DEBUG 1 pods in namespace app-latest are terminated
DEBUG Not scaling RC app-latest-v10-cmd in Namespace app-latest to 0 replicas. Already at desired replicas

Thanks - You are being bitten by the (somewhat arbitrary) 120 second timeout which never passes but we then happily go ahead start scaling down old release.
This one is a bit of a tough cookie... On one hand we should bail out if pods are not coming up within X period but on the other hand it is often k8s taking extra long and the deploy will eventually finish. If we bailed out then you'd never be able to finish (as things stand).
I'm going to think about this for a bit and see if I can come up with a solution that accounts for all these variances - Be warned tho, your deploy can take considerably longer if I start adding in more checks and balances (but you could cheat that by being generous with DEIS_DEPLOY_BATCHES or have many nodes)
If you are willing to fork the controller for now and bump up the timeouts then you can modify this line https://github.com/deis/controller/blob/master/rootfs/scheduler/init.py#L858 to be a much higher value, to fit your needs - You may run into this: https://github.com/deis/controller/issues/652 if you do a very high value but that's only a maybe.

@helgi I'm in no hurry as I won't be using this in production until after Deis v2 is stable.  Let me know if you need me to test anything out.  We do have 2 separate apps that take a while to load.  One takes 60-90s and the other one can take upward of 5mins as it has to warm a very large cache before being healthy.

Is that large cache warmed up on every deploy (as in local to every pod) or just the first time you put it on deis?
How acceptable to you is a very slow deploy, given the warmup period of your applications? Only so fast we can go, the main downside we have is the lack of feedback from the API back into the CLI, or just lack of feedback in generally from the API.

@helgi the things that takes a very long time would be on every deploy, but it's perfectly fine for it to also take a very long time to update.  It's an internal tool and very rarely has any changes applied to it.  If we had two instance of it and it takes them 5 mins to become healthy it would be no problem for it to take 10-20mins for all the applications to roll.

@sstarcher #709 partially addresses this - It basically takes your initial delay and combines it with the normal timeout (120s)
That way each pod gets a longer "wait" time while k8s and the health checkers are doing their thing.
See if you can give it a spin and if it addresses some of your issues

I likely won't get a chance to test it out until next week.

I once again reproduce this problem running rc1.  The deis controller took my app out of service when the new app was never healthy.

Previous apps were deployed via git push deis and the health check port has always been correct at port 80 as defined in the Dockerfile.  A new app was pushed using deis pull which proceeded to take the app out of service and cause an outage.
INFO [APP]: quay.io/IMAGE exists in the target registry. Using image for release 26 of app APP
WARNING [APP]: Private registry detected but no $PORT defined. Defaulting to $PORT 5000
INFO deploy APP-v26-cmd, img quay.io/IMAGE, cmd ""
INFO scaling release APP-v26-cmd to 4 out of final 4
INFO adding 50s on to the original 120s timeout to account for the initial delay specified in the readiness probe
INFO waiting for 4 pods in APP namespace to be in services (170 timeout)
INFO waited 10s and 0 pods are in service
INFO waited 20s and 0 pods are in service
INFO waited 30s and 0 pods are in service
INFO waited 40s and 0 pods are in service
INFO waited 50s and 0 pods are in service
INFO waited 60s and 3 pods are in service
INFO 4 out of 4 pods in namespace APP are in service
INFO scaling old release APP-v19-cmd from original 4 to 0
INFO scaling RC APP-v19-cmd in Namespace APP from 4 to 0 replicas
INFO waiting for RC APP-v19-cmd to get a newer resource version than 332481283 (30s timeout)
INFO RC APP-v19-cmd has a new resource version 332621049
INFO waiting for 4 pods in APP namespace to be terminated (30s timeout)
INFO 4 pods in namespace APP are terminated
INFO Not scaling RC APP-v19-cmd in Namespace APP to 0 replicas. Already at desired replicas

Another example of failed health checks, but the git push claims success.
NAME                  READY     STATUS             RESTARTS   AGE
public-v5-cmd-x3c93   0/1       CrashLoopBackOff   4          2m

=== public Config
HEALTHCHECK_FAILURE_THRESHOLD      3
HEALTHCHECK_INITIAL_DELAY          10
HEALTHCHECK_PERIOD_SECONDS         10
HEALTHCHECK_SUCCESS_THRESHOLD      1
HEALTHCHECK_TIMEOUT                50
HEALTHCHECK_URL                    /
PORT                               80

Build complete.
Launching App...
...
...
...
...
...
...
...
...
...
...
...
...
...
Done, public:v5 deployed to Deis

Use 'deis open' to view this application in your browser

To learn more, use 'deis help' or visit http://deis.io

To ssh://git@deis.cluster.private:2222/public.git
 * [new branch]      master -> master

INFO [public]: build public-be7638f created
INFO [public]: sstarcher deployed 66d4ade
INFO deploy public-v5-cmd, img 192.168.3.84:80/public:git-66d4adee, cmd ""
INFO No prior RC could be found for public-cmd
INFO scaling release public-v5-cmd to 1 out of final 1
INFO adding 10s on to the original 120s timeout to account for the initial delay specified in the readiness probe
INFO waiting for 1 pods in public namespace to be in services (130 timeout)
INFO waited 10s and 0 pods are in service
INFO waited 20s and 0 pods are in service
INFO waited 30s and 0 pods are in service
INFO waited 40s and 0 pods are in service
INFO waited 50s and 0 pods are in service
INFO waited 60s and 0 pods are in service
INFO waited 70s and 0 pods are in service
INFO waited 80s and 0 pods are in service
INFO waited 90s and 0 pods are in service
INFO waited 100s and 0 pods are in service
INFO waited 110s and 0 pods are in service
INFO 1 out of 1 pods in namespace public are in service
WARNING [public]: Router was not ready to serve traffic to process type cmd in time, waited 10.052513599395752 seconds
10.245.18.132 "POST /v2/hooks/build HTTP/1.1" 200 25 "deis-builder"

authors: helgi sstarcher

repo: deis/controller


text:
fix(controller): Persist ssl.enforce header on service creation

This is a fix for #1304

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

Jenkins, add to whitelist.

Thanks @mattk42! This needs a rebase and seems to have failed a unit test:
12:42:45 ======================================================================
12:42:45 FAIL: test_config_set_unicode (api.tests.test_config.ConfigTest)
12:42:45 ----------------------------------------------------------------------
12:42:45 Traceback (most recent call last):
12:42:45   File "/usr/local/lib/python3.5/dist-packages/requests_mock/mocker.py", line 222, in inner
12:42:45     return func(*args, **kwargs)
12:42:45   File "/usr/lib/python3.5/unittest/mock.py", line 1157, in patched
12:42:45     return func(*args, **keywargs)
12:42:45   File "/test/rootfs/api/tests/test_config.py", line 252, in test_config_set_unicode
12:42:45     self.assertEqual(response.status_code, 201, response.data)
12:42:45 AssertionError: 400 != 201 : {'detail': 'duplicate key value violates unique constraint "api_release_app_id_version_e492eaee_uniq"\nDETAIL:  Key (app_id, version)=(17a9703c-d248-4337-9fad-4d39ee1e5f1c, 3) already exists.\n'}

ping @mattk42 -- any chance to rebase and potentially fix up test(s)?

Sorry, lost track of this. Will take a look tonight.
On Jul 3, 2017 3:07 PM, "Vaughn Dice" notifications@github.com wrote:
ping @mattk42 https://github.com/mattk42 -- any chance to rebase and
potentially fix up test(s)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/deis/controller/pull/1305#issuecomment-312733842, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAe01luXKL2dG5tTGF7v1h-YyvKkyzzrks5sKVgCgaJpZM4NxrZN
.

Thanks @mattk42 !
fyi: e2e actually passed (ran right up to the 30 min timeout, but all specs passed): https://ci.deis.io/job/workflow-chart-e2e/391/console

Codecov Report

Merging #1305 into master will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1305      +/-   ##
==========================================
- Coverage   86.99%   86.88%   -0.12%
==========================================
  Files          45       45
  Lines        3929     3941      +12
  Branches      681      682       +1
==========================================
+ Hits         3418     3424       +6
- Misses        339      346       +7
+ Partials      172      171       -1

authors: codecov-io deis-admin mattk42 mboersma vdice


text:
fix(user-data): update fleetd 0.92 to /opt so it survives reboots

This workaround should be removed when a newer CoreOS makes it into the stable channel, but for now putting the fleetd-0.9.2 binary and conf file under /opt ensures they will survive a reboot.
Tested with make discovery-url && vagrant up, then vagrant reload deis-01 && vagrant ssh deis-01 -c 'ps faux | grep fleetd', which fails on Deis master but succeeds when provisioned from this PR. Also checked by hand that the fleetd binary disappeared before, but remains now after reboot.
Closes #3547.

nicely done. Code LGTM

Code LGTM.

authors: bacongobbler carmstrong mboersma

repo: deis/deis


text:
feat(nsq): Provide a simple queue for deis infrastructure

The nsq instance is run as a replication controller.
It contains no logic for discovering other nsq instances or an nsqlookupd instance.
There is also no data persistence.

Apart from some feedback on the Dockerfile, this looks great.

@krancour updated

authors: jchauncey krancour

repo: deis/nsq


text:
chore(requirements): update DRF to 3.3.3

See http://www.django-rest-framework.org/topics/release-notes/#333

Current coverage is 83.01%

Merging #502 into master will not affect coverage as of 224e19e

@@            master    #502   diff @@
======================================
  Files           32      32
  Stmts         1914    1914
  Branches       270     270
  Methods          0       0
======================================
  Hit           1589    1589
  Partial         61      61
  Missed         264     264

Review entire Coverage Diff as of 224e19e

Powered by Codecov. Updated on successful CI builds.

authors: codecov-io mboersma

repo: deis/workflow


text:
i cant use it pls help me

i cant use it pls help me

Please post your error screen or problem you got. Which step that it happen, so I can be able to help you out.
First redo the steps in the Readme accurately.

authors: dekkeng kadirbaycan

repo: dekkeng/runiverse-auto