text:
Inconsistencies between plugin docs and cookiecutter

📚 Documentation
There are inconsistencies between the "first plugin" docs (https://napari.org/plugins/stable/first_plugin.html) and what is generated by the cookiecutter-napari-plugin that might confuse people not familiar with the 101 ways (:grimacing:) to create a python package (for example if they create the plugin via cookiecutter and then refer to the docs if something doesn't work):

The docs (https://napari.org/plugins/stable/first_plugin.html#add-standard-python-package-metadata-files) say to put the source files directly in the base folder, while the cookiecutter creates a src subfolder. Because of that of course the setup.cfg file (https://napari.org/plugins/stable/first_plugin.html#setup-cfg) is not the same e.g. it lacks the package_dir option.
The docs say to create a pyproject.toml file (https://napari.org/plugins/stable/first_plugin.html#pyproject-toml) but the cookiecutter doesn't generate one.

I guess 1) should be changed in the docs and 2) in the cookiecutter but I don't if people (in particular @tlambert03) have strong opinions on that.

thanks @guiwitz, I opened a PR  to update the cookiecutter for pyproject.
as for the src setup, I think I'm going to leave that.  the stated point of "your first plugin" is a bare minimum plugin, and I don't want to get into the subtleties of the src layout in that document (side note, if you're curious yourself and haven't read this blog post, I recommend).  using src is essentially a "guard" against things working "on accident" because python adds the working directory to sys.path.  That's kind of an advanced topic, so I don't want to discuss it and adding src doesn't immediately look familiar or "bare minimal",  so it's a pickle.  We do mention that the cookiecutter adds a number of additional features, so it won't be the only difference they come across.  The point of the tutorial isn't necessarily to create a strict subset of the cookiecutter, but rather to introduce the bare minimum APIs for creating a plugin.


text:
ipdb 0.8.1 is not published yet

oldest version as of right now is 0.8 https://pypi.python.org/pypi/ipdb

Oops, thanks!

Fixed and released to PyPI. :sparkles:

Published now https://pypi.python.org/pypi/ipdb/0.8.1

Thanks, @gotcha. Since the requirement is specified as >= 0.8, there's nothing to change on debug side, I think.

source: gharchive/issue

authors: NorthIsUp gotcha narfdotpl

repo: narfdotpl/debug

license: unlicense

license_type: permissive

license_source: bigquery


text:
Bug of Crawler on Windows

See: https://github.com/narugo1992/gchar/actions/runs/4037555159/jobs/6940927399#step:14:85

Crawler is removed from main library, now it can be found in zoo module, and it will not be possible to run on Windows.
So this issue should be closed with won't fix.

license_source: github-api


text:
Unit test won't build with external time source configuration

Is your feature request related to a problem? Please describe.
Many failures in build with ENABLE_UNIT_TESTS=true and the following settings:
#define CFE_PLATFORM_TIME_CFG_SOURCE true
#define CFE_PLATFORM_TIME_CFG_SRC_TIME true
#define CFE_MISSION_TIME_CFG_FAKE_TONE false

This has already been noted in the general time unit testing issue #109 which includes many other unit test issues with changing time config.  Raising priority on this one with a unique issue since it's currently a stakeholder impact.
Describe the solution you'd like
Fix this configuration at minimum, which is often used when supplying cFS with time from an external source (or app).
Describe alternatives you've considered
Time services does need a general refactor as noted in #302, many issues w/ the unit tests as noted in #109.
Really would benefit from converting the configuration files to cmake as described in #2089.
Additional context
#2072 fixed the build issue, but unit test fails to build.
Requester Info
Jacob Hageman - NASA/GSFC per stakeholder request

Ping @jonathan-brandenburg-metecs for awareness.

repo: nasa/cFE


text:
Fix #2076, Improve ES unit test coverage

Describe the contribution

Fix #2076

Testing performed
Build/run unit tests and confirmed coverage
Expected behavior changes
Improves coverage
System(s) tested on

Hardware: i5/wsl
OS: Ubuntu 18.04
Versions: Bundle main + this commit

Additional context
Also tightened up the coverage enforcement
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB:2022-04-13 APPROVED

source: gharchive/pull-request

authors: astrogeco skliper


text:
Integration Candidate: Fast Track

Describe the contribution
cfe and osal
Testing performed
Steps taken to test the contribution:

Build steps '...'
Execution steps '...'

Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.

API Change: xxx (if applicable)
Behavior Change: xxx (if applicable)
Or no impact to behavior

System(s) tested on

Hardware: [e.g. PC, SP0, MCP750]
OS: [e.g. Ubuntu 18.04, RTEMS 4.11, VxWorks 6.9]
Versions: [e.g. cFE 6.6, OSAL 4.2, PSP 1.3 for mcp750, any related apps or tools]

Additional context
Add any other context about the contribution here.
Code contibutions
The cFS repository is provided to bundle the cFS Framework.  It is utilized for bundling submodules, continuous integration testing, and version management and does not contain any software.  Code contributions should be directed to the appropriate submodule.
Contributor Info - All information REQUIRED for consideration of pull request
Full name and company/organization/center of all contributors ("Personal" if individual work)

Note CLA's apply to software contributions.

@jphickey see Travis unit test failures
 45 - bin-sem-flush-test (Child aborted)

	 46 - bin-sem-test (Child aborted)

	 47 - bin-sem-timeout-test (Child aborted)

	 48 - count-sem-test (Child aborted)

	 49 - file-api-test (Child aborted)

	 50 - mutex-test (Child aborted)

	 51 - osal-core-test (Child aborted)

	 52 - queue-timeout-test (Child aborted)

	 53 - sem-speed-test (Child aborted)

	 54 - symbol-api-test (Child aborted)

	 55 - timer-test (Child aborted)

	 56 - osal_core_UT (Failed)

	 57 - osal_loader_UT (Child aborted)

	 58 - osal_filesys_UT (Child aborted)

	 59 - osal_file_UT (Failed)

	 60 - osal_network_UT (Child aborted)

	 61 - osal_timer_UT (Child aborted)

The issue is that it still wasn't picking up the PERMISSIVE mode setting.  Two minor fixups solve it:

had to propagate the native_osconfig.cmake from my local work area to cfe/cmake/sample_defs directory so this build will also pick it up.  Patched by nasa/cfe@4fba145.
OSAL also wasn't picking up the file because include() needed a foreach loop (a silent failure, it only read the first entry, ignoring the second, which is the one that had PERMISSIVE...).  Patched by nasa/osal@20f8b18

The issue is that it still wasn't picking up the PERMISSIVE mode setting. Two minor fixups solve it:
* had to propagate the `native_osconfig.cmake` from my local work area to `cfe/cmake/sample_defs` directory so this build will also pick it up.  Patched by [nasa/cFE@4fba145](https://github.com/nasa/cFE/commit/4fba145).

* OSAL also wasn't picking up the file because `include()` needed a foreach loop (a silent failure, it only read the first entry, ignoring the second, which is the one that had PERMISSIVE...).  Patched by [nasa/osal@20f8b18](https://github.com/nasa/osal/commit/20f8b18)

Can you add those to the respective IC branches?

Could we call it osconfig-doxygen.h as a slightly more specific name?

Could we call it osconfig-doxygen.h as a slightly more specific name?

Or could the osconfig.h.in itself be passed in?  I don't think it has to be a .h file.

Or could the osconfig.h.in itself be passed in? I don't think it has to be a .h file.

Tried this and it doesn't work ... doxygen appears to just ignore it.
I chose osconfig-example.h as it this is what it is (an example without real values) for documentation purposes.  This only exists in the build dir, not in source tree obviously, so this name is never used except it will appear in the generated docs when you click on the links to stuff in this file.
Is this the only thing holding this up at this point?  I have several other branches that need to be rebased after this goes to "master", so I'd like to move past this.
I recommend we just move forward with the way it is but if you don't like the name I chose, please just tell me specifically what name you will like, and I will patch it again.

Or could the osconfig.h.in itself be passed in? I don't think it has to be a .h file.

Tried this and it doesn't work ... doxygen appears to just ignore it.

It's possible (FILE_PATTERN, EXTENSION_MAPPING), but by the time I got it working it felt more complex than your example implementation.  Lets just go with this.

authors: astrogeco jphickey skliper

repo: nasa/cFS


text:
Remove chunk_size and output_size

Get these parameters from the network structure instead of duplicating.

Now I also replaced block_size_mb and tile_ratio with the more intuitive tile_size. Additionally, for FCNs (networks where the input dimensions are None) the imagery dataset operates directly on blocks and skips chunking. @furlong-cmu @ScottMcMichael could one of you check this over and make sure it looks good before I merge?

Confirmed working by Scott.

repo: nasa/delta


text:
Most recent models are not always deployed

Context: The 3 most recent models are chosen for deployment using this line: https://github.com/nasaharvest/openmapflow/blob/e1b3bb96da4933e5ff033c1ed0039d9c243ed6c4/openmapflow/config.py#L84
Issue: The above line uses the file age to sort, however, the file age depends on the latest dvc pull rather than the actual model file age. Therefore the most recent models are not always deployed.
Potential solution: Find another indicator to sort by for deployment.

It may also be nice to be able to control how many models are deployed

authors: gabrieltseng ivanzvonkov

repo: nasaharvest/openmapflow


text:
get status of operation

How do I monitor the status of a long running operation such as pinning folder meta data?

Pinning is not usually a long-running operation, as pinning is only a setting for a path that lets the system know that it should not evict items within that path from the cache. Pinning does not cause items that are not in the cache to be retrieved from the cloud. Bring into cache or autocache are two options that do that.
If you want to monitor if the system has processed a request to pin the path, use the message id from the pinning request and query the Get Message endpoint to see the status. A "pending" message is still being processed, while a "synced" message has completed processing.

Thankyou for your comment, I wanted to restate I was not making reference to pining file data but rather pinning folder meta-data for an entire volume and hence my question of how to monitor metadata pining progress.  Do you have a quick sample code snippet for the montiroing of pinning procegress?

We don't provide an API mechanism to track how long it takes either form of pinning (data or metadata) requests to take. From the API's perspective, requests are waiting to be picked up (pending) or have started processing (synced). My recommendation is to open a Support case for more insight.

authors: cdillahunty-nasuni maccardo

repo: nasuni-labs/nasuni-api-utilities

license: MIT


text:
Rotation based on day

Hello,
Would you be interessed by adding the possibility to rotate log file based on day please ?
If I do not any mistake, rotation is only activated by the size.
The idea would be to also activate it by day : rotate everyday for example.
Thanks a lot.

Hello,
Little up :)
Regards.

Sorry for not getting back to you sooner.  I had originally thought about doing time-based rotations, but it honestly isn't that useful. What if you get 10 gigs of logs in one day and your disk is only 8 gigs?  The point of rotating is to prevent you from running out of disk space.  Any rotation strategy that fails that test is not one I would want to implement.

Well, you're right, but I really think that it is useful for investigations/forensic/SIEM. By the way, file size rotation would always be applied on top.
If day rotation based is chosen and the file is exeeding the maximum size, the file could be nammed with the day and incremented (18-02-2016_......1, 18-02-2016......_2, etc..)

The other problem with rotating every day is that then the amount of space your backups will take up is non-deterministic.  You can have a max number of backups of 5, and a max size of 100MB... and your total size might be anywhere from 0 (if you had 5 days of rotated logs with no logging) or 500MB.
Rotating per day really just does not fit well with a sized-based model.  Note that if you want to implement it yourself on top of lumberjack, there is the Rotate() method that will cause an immediate rotation... it's easy enough to write a little goroutine to rotate once per day:
log := lumberjack.Logger{ /* some config */ }
go func() {
    for {
        <-time.After(time.Hour*24)
        log.Rotate()
    }
}()

partially agree with natefinch

a project timewriter impl daily rotate:

Hello here
This issue seems block caddyserver/caddy#1096.
I just escalate it as a GDPR compliance trouble and no more just as a nice to have feature.
Even outside compliance, I think this behavior should be added on this lib, given it's a decent/expectable one in all cases, as the number of related issues show, and it's at the hand of sysadmin to prefer a size or a date constraint.
Yes, such feature no more ensure log space size but it's not an issue at all since ages on many other log systems.

The other problem with rotating every day is that then the amount of space your backups will take up is non-deterministic. You can have a max number of backups of 5, and a max size of 100MB... and your total size might be anywhere from 0 (if you had 5 days of rotated logs with no logging) or 500MB.

I respectfully disagree that this problem should be considered a showstopper: If size differences become an issue in production, I feel that resorting to size-based rotation is just 'papering over' the underlying problem. Or to put it more diplomatically: It is a very one-sided tradeoff because it ignores other considerations.

The ability to preserve logs for a certain amount of time. With pure size-based rotation, it is impossible to preserve at least X days of logs but no more than Y days.
Date-based log files have helped me in the past to concentrate my focus on the relevant files with minimal tooling. In contrast, with size-based logs, I first need to check which files contain the time period I am interested in. Of course, these days most people probably use more sophisticated system-level log aggregation tools, but I like the simplicity of grep and other common Unix tools as a fallback.

That being said I completely respect your decision - thank you spending so much time in writing library in the first place.

authors: FelixSchwarz aeris fallais jinleileiking longbozhan natefinch

repo: natefinch/lumberjack

license: mit


text:
Solves issue #170: HTTP Header parsing is inconsistent

This push request solves issue #170 by moving the code from Response::_parseCode to Response\Headers::fromString.

How should I handle the lower case problem?

Hi there.
How should I handle the lower case problem?

I removed the lower case code and reverted the test

I just fixed all the issues. Headers remain as entered.

Is there any intereset oin this pull request by upstream?

Absolutely.

repo: nategood/httpful


text:
Documentation for Enabling, Disabling, Toggling Plugin

I'm sure many people would find it useful if you added documentation for the fairly important commands:
:IndentGuidesToggle
:IndentGuidesEnable
:IndentGuidesDisable

It's always nice to be able to read the documentation (readme, wiki) than have to go digging through the code!

Agreed, thanks for the PR :)

repo: nathanaelkane/vim-indent-guides


text:
Enriched status

Needs some minor formatting and layout tweaks, but adds time since enrichment to the detail edit page (six months ago/never etc). Mouse over it for an exact timestamp.

This was a proof of concept, we've got a better approach coming now.

repo: nationalarchives/ds-caselaw-editor-ui


text:
add support for ukait tribunal alias

Changes in this PR:
Add support for the ukait alias for the Upper Tribunal (Asylum & Immigration Chamber), also known as ut/aic
Trello card / Rollbar error (etc)
https://trello.com/c/Cj856ck9/1373-🏔backlog-support-ukait-urls

 🏔BACKLOG: support .../ukait/... URLs

repo: nationalarchives/ds-caselaw-public-ui


text:
Set specific version numbers for all dependencies

This makes the builds more consistent. It may also help Dependabot to upgrade depedencies when we add it.

@MancunianSam Would you mind taking a look at this PR?

repo: nationalarchives/tdr-antivirus


text:
Not working after dependency update.

It seems not working after https://github.com/nativescript-community/gesturehandler latest commit.

@ondrejlohnisky what do you mean by not working? can you share an error log?

False alarm, I don't know what was wrong... after I was working on something else it magically started working correctly.
Anyway, thx for fast reaction.
closed

False alarm, I don't know what was wrong... after I was working on something else it magically started working correctly.
Anyway, thx for fast reaction.
closed

authors: farfromrefug ondrejlohnisky

repo: nativescript-community/ui-drawer


text:
[UserPage] Make UserPage theme agnostic

Your idea:
As Homebrewery introduces more themes than just straight 5E PHB, having other parts of the website - like the UserPage - use the 5E PHB style becomes inappropriate. I suggest - once Themes are live - we alter the UserPage style to a theme-agnostic style, possibly mimicking the new UI Page style.
Please confirm:

[X] I have searched the Issues tracker for any duplicate requests and found none.

Are you thinking of pushing it down to Blank or a distinct new theme?

authors: G-Ambatte dbolack-ab

repo: naturalcrit/homebrewery


text:
🛑 Basic is down

In 71fc1dc, Basic (https://www.gemeinsam-ist-es-klimaschutz.de) was down:

HTTP code: 500
Response time: 1455 ms

Resolved: Basic is back up in 0cdbd62.

repo: natureOffice-GmbH/upptime


text:
Field ValidationErrors provide confusing and inconsistent error data structure

Environment

Nautobot version (Docker tag too if applicable): 1.5.18
Python version: 3.9
Database platform, version:
Middleware(s):

Steps to Reproduce

Create a custom field on platform and set it as required
Use the API to create a platform, but do not send a value for the custom field

Expected Behavior
The response should follow a standard structure for indicating errors that is strait-forward to understand and easy for API clients to parse, in all cases

Observed Behavior
You get this payload with a 400 response:
{
  "__all__": [
    "Invalid value for custom field 'test': Required field cannot be empty."
  ]
}

This is an example of an unbounded, non-field error, which is the case for custom fields, but is true of any non-field error. The confusing part here, is that if I don't have any experience with Django, I have no idea what __all__ means, and there is nothing in the structure of the response that actually indicates I am getting a list of errors. Worse, because of the way we handle validation, sometimes that __all__ key is presented in the UI, notably related to filtersets/filterforms.
Now, consider this 400 error response for bounded field errors:
{
  "name": [
    "platform with this name already exists."
  ],
  "slug": [
    "platform with this slug already exists."
  ]
}

This is obviously better, but still no indication to a client that these are contextual errors.
I would like to see us use a standard here that is more explicit and clear to solve both cases.

So you're thinking:
{
  "test": ["This is a required field and cannot be empty. No value provided."]
}

and
{
  "name": ["Platform with the name 'Example' already exists."]
}

authors: bryanculver lampwins

repo: nautobot/nautobot


text:
Power-port template with type dc-terminal  not accepted with API/Ansible

Environment

Nautobot version (Docker tag too if applicable): 1.5.20
Python version: 3.9.16
Database platform, version: PostgreSQL : 14
Middleware(s):

Steps to Reproduce

Add power-port template with type: dc-terminal, tried API and Ansible

Expected Behavior

Adding the power-port to the device template
With value of dc-terminal as also displayed in GUI

Observed Behavior
Error:
failed: [localhost] (item={'name': 'PS2', 'type': 'dc-terminal'}) => {"ansible_loop_var": "item", "changed": false, "item": {"name": "PS2", "type": "dc-terminal"}, "msg": "value of type must be one of: iec-60320-c6, iec-60320-c8, iec-60320-c14, iec-60320-c16, iec-60320-c20, iec-60309-p-n-e-4h, iec-60309-p-n-e-6h, iec-60309-p-n-e-9h, iec-60309-2p-e-4h, iec-60309-2p-e-6h, iec-60309-2p-e-9h, iec-60309-3p-e-4h, iec-60309-3p-e-6h, iec-60309-3p-e-9h, iec-60309-3p-n-e-4h, iec-60309-3p-n-e-6h, iec-60309-3p-n-e-9h, nema-5-15p, nema-5-20p, nema-5-30p, nema-5-50p, nema-6-15p, nema-6-20p, nema-6-30p, nema-6-50p, nema-l5-15p, nema-l5-20p, nema-l5-30p, nema-l5-50p, nema-l6-20p, nema-l6-30p, nema-l6-50p, nema-l14-20p, nema-l14-30p, nema-l21-20p, nema-l21-30p, cs6361c, cs6365c, cs8165c, cs8265c, cs8365c, cs8465c, ita-e, ita-f, ita-ef, ita-g, ita-h, ita-i, ita-j, ita-k, ita-l, ita-m, ita-n, ita-o, got: dc-terminal"}
...ignoring

When inspecting the form via GUI i see the value dc-terminal
When query a device with this power-template attached, I see DC_TERMINAL  as port type.

I see the values in the REST API Swagger schema:

This appears to be a bug in nautobot-ansible, as that module has a hard-coded list of valid values (https://github.com/nautobot/nautobot-ansible/blob/v4.5.0/plugins/modules/power_port.py) that appears not to have been updated to account for the added types from #3413. Similar gaps are likely present in the Ansible module for the other device components (console-port, power-outlet, etc.).
To be honest I'm not sure why the Ansible module should be in the business of enforcing valid choices for this and similar API endpoints; my vote would personally be to remove that logic from the module altogether rather than attempting to keep the list up-to-date with core.

authors: bsmeding glennmatthews


text:
API permits destination in one-to-many relationship to have multiple sources when multiple relationships are creating using a single extras.relationship_associations API call

Environment

Nautobot version (Docker tag too if applicable): 1.6.21
Python version: 3.11
Database platform, version:
Middleware(s): REST API (confirmed with and without using pynautobot, FWIW)

Steps to Reproduce

Create two (or more, one supposes) devices
Create a one-to-many relationship  (in my case, I mapped dcim.device to ipam.prefix)
Make an API call to extras.relationship_associations which takes a list of association definition dicts; for instance:

[
    {
        'source_id': DEVICE_UUID_1,
        'source_type': 'dcim.device',
        'destination_id': PREFIX_UUID_1,
        'destination_type': 'ipam.prefix',
        'relationship': {'name': RELATIONSHIP_NAME}
    },
    {
        'source_id': DEVICE_UUID_2,
        'source_type': 'dcim.device'
        'destination_id': PREFIX_UUID_1
        'destination_type': 'ipam.prefix',
        'relationship': {'name': RELATIONSHIP_NAME}
    }
]

Expected Behavior
Fail with HTTP 400 (or similar) with an error similar to:
Unable to create more than one Device to P2P Prefix association to 10.0.0.0/24 (destination)

Observed Behavior
Server returns an HTTP 201 and both associations are created which, in addition to being wrong, is not displayed well in the UI (not surprising, really). Each device shows 1 prefix in their records, whilst the prefix only shows one of the two devices in its record.

Let's try running validated_save after the create in the bulk operation.

I think the root issue here is that ValidatedModelSerializer.validate() runs for all new record datas before any of the new records are save()d, so it doesn't currently detect collisions between the new records.
Also relevant: https://github.com/encode/django-rest-framework/issues/6395

authors: glennmatthews lampwins nrnvgh


text:
🛑 BarefootEdu is down

In 8339a73, BarefootEdu (https://barefootedu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BarefootEdu is back up in b1a6447 after 6 minutes.

repo: navadhiti/upptime


text:
🛑 BarefootEdu is down

In 48ef9f6, BarefootEdu (https://barefootedu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BarefootEdu is back up in 44eb653 after 8 minutes.


text:
🛑 BarefootEdu is down

In 65d234e, BarefootEdu (https://barefootedu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BarefootEdu is back up in 6eea7d1 after 6 minutes.


text:
🛑 BarefootEdu is down

In 58e743b, BarefootEdu (https://barefootedu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BarefootEdu is back up in fcca1af after 1 hour, 2 minutes.


text:
🛑 BarefootEdu is down

In 4989c91, BarefootEdu (https://barefootedu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BarefootEdu is back up in 9993e7f after 48 minutes.


text:
🛑 Harmony Bot Website is down

In 8bd446f, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 474417c.


text:
🛑 Harmony Bot Website is down

In 7002341, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in ed9a2d9.


text:
🛑 Harmony Bot Website is down

In 895de8c, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in cc52ad2.


text:
🛑 Harmony Bot Website is down

In 36be72c, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 2814baa.


text:
🛑 Harmony Bot Website is down

In 0aa8b73, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in ef84011.


text:
🛑 Harmony Bot Website is down

In acc735f, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 6d163e6.


text:
🛑 Harmony Backup Bot is down

In c8bcc32, Harmony Backup Bot ($HARMONY_BACKUP) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Backup Bot is back up in 51ff90d.


text:
🛑 Harmony Bot Website is down

In 3cc4a33, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in a1e784e.


text:
🛑 Harmony Bot Website is down

In 8462e63, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in b08c57b.


text:
🛑 Harmony Bot Website is down

In 46db2d8, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 047c4b9.


text:
🛑 Harmony Bot Website is down

In 98c4620, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in bd9590b.


text:
🛑 Harmony Bot Website is down

In 0f2b630, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in da43fca.


text:
🛑 Harmony Bot Website is down

In 6143c16, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 9e02761.


text:
🛑 Harmony Bot Website is down

In 4727b7f, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 48e79c8.


text:
컴파일 실패 이슈.

develop 브랜치 기준으로 build 수행하면 아래 오류가 발생합니다.
[WARN] /home/jhpark/work/arcus-java-client/src/test/manual/net/spy/memcached/LoggerSetter.java:9: Class LoggerSetter should be declared as final. [FinalClass]
Audit done.
[WARNING] src/test/manual/net/spy/memcached/LoggerSetter.java:[9] (design) FinalClass: Class LoggerSetter should be declared as final.

에러 로그 재현을 위해 어떤 명령어를 통해 컴파일을 수행했는지, 그리고 설치된 JDK 버전을 알려주시면 좋겠습니다.

아래와 같이 수행하였고,
[jhpark@jam2in-t002 arcus-java-client]$ mvn clean install -DskipTests=true

java version은 아래와 같습니다.
[jhpark@jam2in-t002 ~]$ java -version
openjdk version "1.8.0_352"
OpenJDK Runtime Environment (build 1.8.0_352-b08)
OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode)

https://github.com/naver/arcus-java-client/pull/566
위 PR로 이슈 해결되어 close 합니다.

repo: naver/arcus-java-client


text:
OSX 10.11.5 maven compile error

OSX 10.11.5 maven compile error
run mvn install -Dmaven.test.skip=true and it throw exception
Environment

Pinpoint version: 1.6.0
OSX 10.11.5
JAVA HOME:

export JAVA_6_HOME='/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home'
export JAVA_7_HOME='/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home'
export JAVA_8_HOME='/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home'

I download jdk6 from https://support.apple.com/kb/DL1572?locale=en_US&viewlocale=en_US
and jdk7、jdk8 from oracle.com
Additional Info
maven outprint:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] pinpoint
[INFO] pinpoint-thrift
[INFO] pinpoint-commons
[INFO] pinpoint-commons-hbase
[INFO] pinpoint-commons-server
[INFO] pinpoint-bootstrap-core
[INFO] pinpoint-bootstrap
[INFO] pinpoint-rpc
[INFO] pinpoint-google-guava
[INFO] pinpoint-profiler
[INFO] pinpoint-profiler-optional-parent
[INFO] pinpoint-profiler-optional-jdk6
[INFO] pinpoint-profiler-optional-jdk7
[INFO] pinpoint-profiler-optional
[INFO] pinpoint-httpclient3-plugin
[INFO] pinpoint-httpclient4-plugin
[INFO] pinpoint-ning-asynchttpclient-plugin
[INFO] pinpoint-gson-plugin
[INFO] pinpoint-cubrid-jdbc-driver-plugin
[INFO] pinpoint-mysql-jdbc-driver-plugin
[INFO] pinpoint-mariadb-jdbc-driver-plugin
[INFO] pinpoint-postgresql-jdbc-driver-plugin
[INFO] pinpoint-jtds-plugin
[INFO] pinpoint-oracle-jdbc-driver-plugin
[INFO] pinpoint-commons-dbcp-plugin
[INFO] pinpoint-test
[INFO] pinpoint-cassandra-driver-plugin
[INFO] pinpoint-jdk-http-plugin
[INFO] pinpoint-redis-plugin
[INFO] pinpoint-tomcat-plugin
[INFO] pinpoint-json-lib-plugin
[INFO] pinpoint-jackson-plugin
[INFO] pinpoint-thrift-plugin
[INFO] pinpoint-user-plugin
[INFO] pinpoint-arcus-plugin
[INFO] pinpoint-google-httpclient-plugin
[INFO] pinpoint-jetty-plugin
[INFO] pinpoint-spring-plugin
[INFO] pinpoint-spring-boot-plugin
[INFO] pinpoint-ibatis-plugin
[INFO] pinpoint-mybatis-plugin
[INFO] pinpoint-okhttp-plugin
[INFO] pinpoint-log4j-plugin
[INFO] pinpoint-logback-plugin
[INFO] pinpoint-dubbo-plugin
[INFO] pinpoint-activemq-client-plugin
[INFO] pinpoint-cxf-plugin
[INFO] pinpoint-hystrix-plugin
[INFO] pinpoint-jboss-plugin
[INFO] pinpoint-plugins
[INFO] pinpoint-bootstrap-core-optional
[INFO] pinpoint-tools
[INFO] pinpoint-agent-distribution
[INFO] pinpoint-collector
[INFO] pinpoint-profiler-optional-jdk8
[INFO] pinpoint-web
[INFO] pinpoint-hbase-distribution
[INFO] pinpoint-thirdparty
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building pinpoint 1.6.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-pinpoint-build-requirements) @ pinpoint ---
[INFO]
[INFO] --- animal-sniffer-maven-plugin:1.15:check (ensure-java-1.6-class-library) @ pinpoint ---
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] pinpoint ........................................... FAILURE [  0.576 s]
[INFO] pinpoint-thrift .................................... SKIPPED
[INFO] pinpoint-commons ................................... SKIPPED
[INFO] pinpoint-commons-hbase ............................. SKIPPED
[INFO] pinpoint-commons-server ............................ SKIPPED
[INFO] pinpoint-bootstrap-core ............................ SKIPPED
[INFO] pinpoint-bootstrap ................................. SKIPPED
[INFO] pinpoint-rpc ....................................... SKIPPED
[INFO] pinpoint-google-guava .............................. SKIPPED
[INFO] pinpoint-profiler .................................. SKIPPED
[INFO] pinpoint-profiler-optional-parent .................. SKIPPED
[INFO] pinpoint-profiler-optional-jdk6 .................... SKIPPED
[INFO] pinpoint-profiler-optional-jdk7 .................... SKIPPED
[INFO] pinpoint-profiler-optional ......................... SKIPPED
[INFO] pinpoint-httpclient3-plugin ........................ SKIPPED
[INFO] pinpoint-httpclient4-plugin ........................ SKIPPED
[INFO] pinpoint-ning-asynchttpclient-plugin ............... SKIPPED
[INFO] pinpoint-gson-plugin ............................... SKIPPED
[INFO] pinpoint-cubrid-jdbc-driver-plugin ................. SKIPPED
[INFO] pinpoint-mysql-jdbc-driver-plugin .................. SKIPPED
[INFO] pinpoint-mariadb-jdbc-driver-plugin ................ SKIPPED
[INFO] pinpoint-postgresql-jdbc-driver-plugin ............. SKIPPED
[INFO] pinpoint-jtds-plugin ............................... SKIPPED
[INFO] pinpoint-oracle-jdbc-driver-plugin ................. SKIPPED
[INFO] pinpoint-commons-dbcp-plugin ....................... SKIPPED
[INFO] pinpoint-test ...................................... SKIPPED
[INFO] pinpoint-cassandra-driver-plugin ................... SKIPPED
[INFO] pinpoint-jdk-http-plugin ........................... SKIPPED
[INFO] pinpoint-redis-plugin .............................. SKIPPED
[INFO] pinpoint-tomcat-plugin ............................. SKIPPED
[INFO] pinpoint-json-lib-plugin ........................... SKIPPED
[INFO] pinpoint-jackson-plugin ............................ SKIPPED
[INFO] pinpoint-thrift-plugin ............................. SKIPPED
[INFO] pinpoint-user-plugin ............................... SKIPPED
[INFO] pinpoint-arcus-plugin .............................. SKIPPED
[INFO] pinpoint-google-httpclient-plugin .................. SKIPPED
[INFO] pinpoint-jetty-plugin .............................. SKIPPED
[INFO] pinpoint-spring-plugin ............................. SKIPPED
[INFO] pinpoint-spring-boot-plugin ........................ SKIPPED
[INFO] pinpoint-ibatis-plugin ............................. SKIPPED
[INFO] pinpoint-mybatis-plugin ............................ SKIPPED
[INFO] pinpoint-okhttp-plugin ............................. SKIPPED
[INFO] pinpoint-log4j-plugin .............................. SKIPPED
[INFO] pinpoint-logback-plugin ............................ SKIPPED
[INFO] pinpoint-dubbo-plugin .............................. SKIPPED
[INFO] pinpoint-activemq-client-plugin .................... SKIPPED
[INFO] pinpoint-cxf-plugin ................................ SKIPPED
[INFO] pinpoint-hystrix-plugin ............................ SKIPPED
[INFO] pinpoint-jboss-plugin .............................. SKIPPED
[INFO] pinpoint-plugins ................................... SKIPPED
[INFO] pinpoint-bootstrap-core-optional ................... SKIPPED
[INFO] pinpoint-tools ..................................... SKIPPED
[INFO] pinpoint-agent-distribution ........................ SKIPPED
[INFO] pinpoint-collector ................................. SKIPPED
[INFO] pinpoint-profiler-optional-jdk8 .................... SKIPPED
[INFO] pinpoint-web ....................................... SKIPPED
[INFO] pinpoint-hbase-distribution ........................ SKIPPED
[INFO] pinpoint-thirdparty ................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.046 s
[INFO] Finished at: 2017-03-24T12:44:17+08:00
[INFO] Final Memory: 26M/309M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.15:check (ensure-java-1.6-class-library) on project pinpoint: Execution ensure-java-1.6-class-library of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.15:check failed: A required class was missing while executing org.codehaus.mojo:animal-sniffer-maven-plugin:1.15:check: org/codehaus/plexus/util/StringUtils
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.codehaus.mojo:animal-sniffer-maven-plugin:1.15
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/Users/airclear/.m2/repository/org/codehaus/mojo/animal-sniffer-maven-plugin/1.15/animal-sniffer-maven-plugin-1.15.jar
[ERROR] urls[1] = file:/Users/airclear/.m2/repository/org/codehaus/mojo/animal-sniffer/1.15/animal-sniffer-1.15.jar
[ERROR] urls[2] = file:/Users/airclear/.m2/repository/org/ow2/asm/asm-all/5.0.3/asm-all-5.0.3.jar
[ERROR] urls[3] = file:/Users/airclear/.m2/repository/org/codehaus/mojo/java-boot-classpath-detector/1.15/java-boot-classpath-detector-1.15.jar
[ERROR] urls[4] = file:/Users/airclear/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar
[ERROR] urls[5] = file:/Users/airclear/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar
[ERROR] urls[6] = file:/Users/airclear/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.2.1/maven-reporting-api-2.2.1.jar
[ERROR] urls[7] = file:/Users/airclear/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.1/doxia-sink-api-1.1.jar
[ERROR] urls[8] = file:/Users/airclear/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.1/doxia-logging-api-1.1.jar
[ERROR] urls[9] = file:/Users/airclear/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
[ERROR] urls[10] = file:/Users/airclear/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar
[ERROR] urls[11] = file:/Users/airclear/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[12] = file:/Users/airclear/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[13] = file:/Users/airclear/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[14] = file:/Users/airclear/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar
[ERROR] urls[15] = file:/Users/airclear/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/1.4/maven-common-artifact-filters-1.4.jar
[ERROR] urls[16] = file:/Users/airclear/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------: org.codehaus.plexus.util.StringUtils
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException

Hi @airclear
Could you check if org.codehaus.plexus.util.StringUtils.class is in /Users/airclear/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar? Might be that the plexus-utils-1.5.6.jar used by the maven plugin is corrupted.
If the StringUtils class isn't in there, try deleting /Users/airclear/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar and rebuilding. Maven should automatically download it again and continue with the build.

tks! @Xylus
I remove the jar and then download from http://mvnrepository.com/
then run mvn , it just successed
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:05 min
[INFO] Finished at: 2017-03-24T14:49:57+08:00
[INFO] Final Memory: 200M/1515M
[INFO] ------------------------------------------------------------------------

authors: Xylus airclear

repo: naver/pinpoint


text:
"NAV-internal" lenke

Det er flere lenker, f.eks. de til Slack-kanaler, som bare er tilgjengelig for folk som jobber i NAV.  Det hadde vært fint om vi kunne velge å markere disse på samme måte som vi gjør lenker som åpner i en ny fane.  Trenger noen design-øyne, hvis ikke vi bare skal ha det skrevet i paranteser etter lenketittelen.

Design øyne her: Jeg lurer litt på om det hadde vært bedre om man hadde en form for "kort", eller bare lenker, som bare ble vist for innloggede brukere når det kommer. Aksel er vel ment til å være offentlig tilgjengelig, så jeg tenker det kanskje er litt uheldig at de ser irrelevant informasjon uansett? Hva tenker du?

Hmm.  Det er kanskje heller bedre å skrive det helt ut som dette (NAV intern) i de svært få stedene vi ville brukt det?  Fordi det er jo svært sjeldent.  Eller bare være helt konkret i selve lenketeksten, som dette: klarspråk på NAVs intranett.

authors: olejorgenbakken sarahbrodwall

repo: navikt/aksel-website


text:
Deploy av 1.1_2022.03.14.154611-c00f854

c00f85461a607e6a11879fdf7058466aac48377d

/promote dev-fss

repo: navikt/fp-frontend


text:
🛑 IMF is down

In 0f18371, IMF (http://dataservices.imf.org/REST/SDMX_XML.svc/Dataflow) was down:

HTTP code: 0
Response time: 0 ms

Resolved: IMF is back up in a4ae702.

repo: nbbrd/sdmx-upptime


text:
🛑 ESTAT is down

In 1b42d72, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in d407b9b.


text:
🛑 NBB is down

In a5e1d60, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 509 ms

Resolved: NBB is back up in f143fb3 after 702 days, 15 hours, 9 minutes.


text:
🛑 ESTAT is down

In 28a1aca, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 8d44d62 after 705 days, 6 hours, 38 minutes.


text:
🛑 ISTAT is down

In be621e2, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 04e4f06 after 17 minutes.


text:
🛑 IMF is down

In d51bf5e, IMF (http://dataservices.imf.org/REST/SDMX_XML.svc/Dataflow) was down:

HTTP code: 0
Response time: 0 ms

Resolved: IMF is back up in 21f6919 after 7 minutes.


text:
🛑 ISTAT is down

In fe7cc43, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 44f6063 after 11 minutes.


text:
🛑 ESTAT is down

In 11db79f, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 15f2a80 after 6 minutes.


text:
🛑 ECB is down

In 0fec566, ECB (https://data-api.ecb.europa.eu/service/dataflow/all/all/latest) was down:

HTTP code: 404
Response time: 568 ms

Resolved: ECB is back up in 6909272 after 47 minutes.


text:
🛑 NBB is down

In 39b8e31, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 542 ms

Resolved: NBB is back up in 740b3c3 after 13 minutes.


text:
🛑 UNICEF is down

In 24aced3, UNICEF (https://sdmx.data.unicef.org/ws/public/sdmxapi/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UNICEF is back up in b8f4ca6 after 6 minutes.


text:
🛑 ESTAT is down

In b3048ea, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 9bfa2ce after 51 minutes.


text:
🛑 ISTAT is down

In da8afd6, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in b112554 after 11 minutes.


text:
🛑 ISTAT is down

In 152b569, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 3e2b5b3 after 4 minutes.


text:
🛑 ESTAT is down

In 9e4b713, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 6291cef after 6 minutes.


text:
🛑 ISTAT is down

In 560c85a, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 5c20374 after 6 minutes.


text:
🛑 ISTAT is down

In 859f308, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 274695c after 8 minutes.


text:
🛑 INSEE is down

In 501a39c, INSEE (https://bdm.insee.fr/series/sdmx/dataflow/all/all/latest/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: INSEE is back up in a9b0623.


text:
🛑 ISTAT is down

In ca66ece, ISTAT (https://esploradati.istat.it/SDMXWS/rest/dataflow/all/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ISTAT is back up in 31dcd2d.


text:
🛑 NBB is down

In e0645b7, NBB (https://stat.nbb.be/restsdmx/sdmx.ashx/GetDataStructure/ALL) was down:

HTTP code: 429
Response time: 838 ms

Resolved: NBB is back up in 11a407f.


text:
🛑 ESTAT is down

In 941eccf, ESTAT (https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/all/latest) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ESTAT is back up in 17d5ad6.


text:
Setup

I added the list of possible carriers
ALLOWED_CARRIERS = ["globe", "smart", "sun", "dito", "tm", "tnt" "cherry", "gomo"]
also added the two endpoints we need for further dev
/api/getCarrierPrefixes
/api/getCarrierFromPrefix

lgtm

authors: just-jacob reddiedev

repo: nbt-ph/anongsimto-backend


text:
Adding Exception dates to node CRON

Is there any standard way to add exception to the cron dates? For example I don't want to run the cron job on national holidays. I think there should be some standard way to handle such exception dates array.

That isn't the way that cron itself works. This is intended to be a minimal project. A scheduler would be a better place to handle this kind of feature imo.

license: ISC


text:
Exception if python binary != python2.7 on nodes

I'm using a modified AMI Amazon Linux AMI release 2015.09, which seems to default to python 2.6 when firing python. On cluster launch I get:
[52.37.134.99] Configuring ephemeral storage...
At least one node raised an error: Traceback (most recent call last):
  File "/tmp/setup-ephemeral-storage.py", line 158, in <module>
    non_root_block_devices = get_non_root_block_devices()
  File "/tmp/setup-ephemeral-storage.py", line 53, in get_non_root_block_devices
    block_devices_raw = subprocess.check_output([
AttributeError: 'module' object has no attribute 'check_output'

This is from using python 2.6:
root@ip-172-31-30-154 tmp]$ python26 --version
Python 2.6.9
root@ip-172-31-30-154 tmp]$ python26 setup-ephemeral-storage.py
Traceback (most recent call last):
  File "setup-ephemeral-storage.py", line 158, in <module>
    non_root_block_devices = get_non_root_block_devices()
  File "setup-ephemeral-storage.py", line 53, in get_non_root_block_devices
    block_devices_raw = subprocess.check_output([
AttributeError: 'module' object has no attribute 'check_output'

Python 2.7 is in the path but it isn't called
root@ip-172-31-30-154 tmp]$ python27 --version
Python 2.7.10
root@ip-172-31-30-154 tmp]$ python27 /tmp/setup-ephemeral-storage.py
{"ephemeral": ["/media/ephemeral0", "/media/ephemeral1"], "root": "/media/root"}

Python 3.5 also fails for me:
root@ip-172-31-30-154 tmp]$ python3.5 setup-ephemeral-storage.py
Traceback (most recent call last):
  File "setup-ephemeral-storage.py", line 171, in <module>
    format_devices(ephemeral_devices)
  File "setup-ephemeral-storage.py", line 102, in format_devices
    "Format process returned non-zero exit code: {c}".format(c=return_code))
Exception: Format process returned non-zero exit code: 1

Based on https://github.com/nchammas/flintrock/blob/master/flintrock/core.py#L481 and these exceptions, it seems like python from the PATH must be only 2.7 in order for for setup-ephemeral-storage.py to work.

Thanks for the report @ereed-tesla.
I did assume that setup-ephemeral-storage.py would run under Python 2.7, though I didn't call that out explicitly enough.
The problem with Python 2.6 is that it does not have subprocess.check_output(). That was added only in Python 2.7.

I'm using a modified AMI Amazon Linux AMI release 2015.09

I normally test Flintrock against vanilla Amazon Linux, where the default Python for ec2-user is 2.7.
Did you explicitly change the default Python when you created your custom AMI?

Required mitigation:

Provide a clean error message from setup-ephemeral-storage.py about supported Python versions.

Extra credit:

Make setup-ephemeral-storage.py compatible with Python 2.7+ and 3.4+. We should probably do this anyway for forward-looking Linux distributions like Fedora, where Python 3.4+ is the default and Python 2 isn't even installed.

What I'd really like to avoid:

Making changes for the sake of Python 2.6. RHEL be damned!

Ahaa I didn't see that comment. The base AMI is the present from around spark_ec2.py ~v1.4 (maybe earlier) -- Anaconda is installed so the default is python --version -> Python 3.5.1 :: Anaconda 2.4.1 (64-bit)
However, a .bashrc/.profile is not fired in the cluster launch script so the default becomes the AMI default of 2.6:
$ ssh root@XYZ python --version
Python 2.6.9

Ah, the spark-ec2 AMIs.
They are packed with lots of goodies, but they have not been updated in 2 years, lack a slew of security updates (no biggie for short-lived clusters, perhaps), and have many other rough edges like depending on you logging in as root.
My strong recommendation is to use something else. Is there something in particular about the spark-ec2 AMIs that you are looking for?

I agree. The main reason I'm testing using a variant of the spark-ec2 AMI is because it has all the dependencies/packages for my workflow setup (unrelated to spark), and since it works, I of course hasn't changed it. Thanks for the advice -- closing this issue.

No worries.
You may be able to recreate what you need with Flintrock pretty easily using vanilla Amazon Linux and a combination of Flintrock's copy-file (e.g. to upload a script) and run-command commands to setup stuff you need on the cluster.
I'll keep this issue open to address the error message and Python 3 compatibility that should be added, per my earlier comment.

authors: ereed-tesla nchammas

repo: nchammas/flintrock


text:
Simplenote integration?

This is a feature request.
Would be great to have Simplenote (simperium API 2) integration.  These are basically text files, and rclone would be a terrific "backup" mechanism.  Not sure how well it would work for writing to the Simplenote service, but reading from it would be very easy, I would think.

The API looks quite capable.  I don't see any documentation on what an object is though - can it store arbitrary data?

Simperium can store arbitrary data, yes.
However, Simplenote (the first app that used Simperium) has a note repository that uses a standard JSON format that looks like:
{
tags, ["tag1, "tag2"],
deleted: false,
shareURL: "",
publishURL: "",
content: "some big long string with line feeds\n in it",
systemTags: [],
modificationDate: 1490233933
}
The "content" property has the actual text content in it.  The note also has a hash "key" for accessing it.  That is what most programs use for the "filename".  (However, for backup/syncing purposes, we could potentially just dump the whole json blob into a file instead of just the content property.)
There is also a separate "tags" repository, so not sure how (or if) dealing with that is important.  Each entry in the tags repo is just a single word string.  The key is the same string, instead of a hash.

Requested 4 years ago by a now deleted account.
No comments, no +1's

authors: dogear42 ivandeex ncw

repo: ncw/rclone


text:
Failed to create file system

What is the problem you are having with rclone?
There is no problem with version 1.40. There is an error when upgrading to 1.45.
After upgrading to version 1.45, I added the yandex network disk and then the following problem
2018/11/28 12:29:13 Failed to create file system for "onedrive:": unable to get drive_id and drive_type - if you are upgrading from older versions of rclone, please run `rclone config` and re-configure this backend

What is your rclone version (output from rclone version)
 rclone -V
rclone v1.45
- os/arch: linux/amd64
- go version: go1.11.2

Which OS you are using and how many bits (eg Windows 7, 64 bit)
Linux 64bit
Which cloud storage system are you using? (eg Google Drive)
onedrive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone -Luv --log-file=/home/xuan/logs/rclone_sync_Documents_to_onedrive.log --delete-excluded --exclude vnote_notebooks/** --exclude /security/topspeedsnail/** --exclude /security/learn-hacking/** --exclude Xblog/lufficc/** --exclude MyLife/_book/** sync /home/xuan/Documents/ onedrive:openSUSE-doc

rclone lsd onedrive:

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
rclone -vv lsd onedrive:
2018/11/28 12:36:58 DEBUG : rclone: Version "v1.45" starting with parameters ["rclone-1.45" "-vv" "lsd" "onedrive:"]
2018/11/28 12:36:58 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2018/11/28 12:36:58 Failed to create file system for "onedrive:": unable to get drive_id and drive_type - if you are upgrading from older versions of rclone, please run `rclone config` and re-configure this backend

The error message state :  if you are upgrading from older versions of rclone, please run rclone config and re-configure this backend, did you try that ?

@Aquarian-Age You don't need to re-configure all drives; just the OneDrive ones. This is because rclone has migrated to the new API for OneDrive - we had to do this because the old API is being phased out.

@Cnly OK Thank you very much

@Cnly
Use auto config?

Say Y if not sure
Say N if you are working on a remote or headless machine
y) Yes
n) No
y/n> y
If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth
Log in and authorize rclone for access
Waiting for code...
Got code
Choose a number from below, or type in an existing value
1 / OneDrive Personal or Business
\ "onedrive"
2 / Root Sharepoint site
\ "sharepoint"
3 / Type in driveID
\ "driveid"
4 / Type in SiteID
\ "siteid"
5 / Search a Sharepoint site
\ "search"
Your choice> ???

Every one has tried it, it’s not right.

authors: 131 Aquarian-Age Cnly


text:
onedrive: Removed upload cutoff and always do session uploads

Fixes the double versions on OneDrive except when copying files but still does it on copy

That is great thanks :-)
I'll merge that now and we can see how it does in the integration tests tonight!

The integration tests look a bit poorly :-(
On a normal consumer onedrive account I get this
$ echo "hello" | rclone rcat onedrive:test/hello.txt
2018/03/16 09:18:32 ERROR : hello.txt: Failed to copy: invalidRequest: API not found
2018/03/16 09:18:32 Failed to rcat: invalidRequest: API not found

Or with more info.
Note that the CreatedDateTime looks a bit whacky...
$ echo "hello" | rclone -vv --dump-bodies rcat onedrive:test/hello.txt
[snip]
2018/03/16 09:19:03 DEBUG : One drive root 'test': File to upload is small (6 bytes), uploading instead of streaming
2018/03/16 09:19:03 DEBUG : hello.txt: Starting multipart upload
2018/03/16 09:19:03 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018/03/16 09:19:03 DEBUG : HTTP REQUEST (req 0xc4205ae100)
2018/03/16 09:19:03 DEBUG : POST /v1.0/drive/root:/test/hello.txt:/createUploadSession HTTP/1.1
Host: api.onedrive.com
User-Agent: rclone/v1.39-DEV
Content-Length: 116
Authorization: XXXX
Content-Type: application/json
Accept-Encoding: gzip

{"item":{"fileSystemInfo":{"createdDateTime":"0001-01-01T00:00:00Z","lastModifiedDateTime":"2018-03-16T09:19:03Z"}}}
2018/03/16 09:19:03 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018/03/16 09:19:03 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2018/03/16 09:19:03 DEBUG : HTTP RESPONSE (req 0xc4205ae100)
2018/03/16 09:19:03 DEBUG : HTTP/1.1 400 Bad Request
Content-Type: application/json
Date: Fri, 16 Mar 2018 09:19:03 GMT
P3p: CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Asmversion: UNKNOWN; 19.97.227.2007
X-Msedge-Ref: Ref A: 2DD7821FD9A54F308A9AE40E07E55B46 Ref B: AM3EDGE0109 Ref C: 2018-03-16T09:19:03Z
X-Msnserver: DM5SCH103160408
X-Qosstats: {"ApiId":0,"ResultType":2,"SourcePropertyId":0,"TargetPropertyId":42}
X-Throwsite: 0274.43d9

{"error":{"code":"invalidRequest","message":"API not found"}}
2018/03/16 09:19:03 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2018/03/16 09:19:03 ERROR : hello.txt: Failed to copy: invalidRequest: API not found
2018/03/16 09:19:03 Failed to rcat: invalidRequest: API not found

Can you fix this?  Or I can revert it to give you more time to fix.

authors: ncw olihey


text:
Comments in args file

Please note that I am not too familiar with cmdargs but am a user of hledger, which uses cmdargs for parsing arguments stored in text files.
As specified in an issue there, I find that it would be very convenient to have comments in the argument files.
In case the functionality of reading the argument files is indeed part of cmdargs, would you consider ignoring lines that start with ";" (or other delimiters), for example, and leave them as comments.
This might be really useful for cases when there are multiple or confusing arguments, or just temporarily removing some of them.
Thanks!

Seems a reasonable thing to do - only question is what should the comment syntax be? Can you find any other similar args files that use comments? I'd prefer to copy rather than do something different.

Hi! Thanks a lot for the feedback. I'm coming from the viewpoint of parsing the arguments for ledger-style argument files, also used in hledger.
Ledger supports the following characters for comments: https://www.ledger-cli.org/3.0/doc/ledger3.html#Commenting-on-your-Journal
Naturally, I would not expect cmdargs to follow ledger's specs but some of those are common comment chars, like # and ;. Perhaps others, too, but I'm mostly using these two. That might be a good start?

Count me interested too. The recent https://www.stevegattuso.me/tech-stack/finances-budgeting.html#args has some nice examples of args files commented with #, but I'm not sure this actually works - it doesn't for me.
The only docs I have found for the argument file format are at https://stackoverflow.com/questions/53995002/where-does-shell-argument-files-or-files-originate-from .

The recent https://www.stevegattuso.me/tech-stack/finances-budgeting.html#args has some nice examples of args files commented with #, but I'm not sure this actually works - it doesn't for me.

Presumably this was just an annotated example and the # comments aren't actually part of the files

authors: MisterY alensiljak bsima ndmitchell simonmichael

repo: ndmitchell/cmdargs


text:
Cannot expand #if directive: MIN_VERSION_Cabal(a,b,c) is not a defined macro

Not quite how/when this started happening or if it might be due to newer haskell-src-exts perhaps, but anyway with recent hlint and haskell-src-exts I started seeing eg:
[cabal-rpm/src:master]$ hlint .
hlint: Cannot expand #if directive in file ./Commands/Spec.hs  at line 326 col 1:
    MIN_VERSION_Cabal(a,b,c) is not a defined macro

This doesn't happen with slightly older hlint/haskell-src-exts, eg with the hlint-1.8.50 in Fedora 20.

Guess this hasn't been fixed? Still struggling with this issue now.

I've pinged @malcolmwallace by email, let's see what he says (I entirely forgot to talk to him when he got back).

@malcolmwallace, concretely, running cpphs v1.19.3 over:
#if defined(MIN_VERSION_Cabal) && MIN_VERSION_Cabal(1,20,0)
#endif

Produces the error:
cpphs: Cannot expand #if directive in file Sample.hs  at line 1 col 1:
    MIN_VERSION_Cabal(a,b,c) is not a defined macro

Is that a bug? Or does the CPP spec say that is how it should be?
However, I always do a dummy define of the CPP macros with a sensible default. e.g. in Shake I have https://github.com/ndmitchell/shake/blob/master/src/Development/Shake/FileInfo.hs#L136:
#ifndef MIN_VERSION_unix
#define MIN_VERSION_unix(a,b,c) 0
#endif

And at https://github.com/ndmitchell/shake/blob/master/src/Development/Shake/FilePath.hs#L3 I have:
#ifndef MIN_VERSION_filepath
#if __GLASGOW_HASKELL__ >= 709
#define MIN_VERSION_filepath(a,b,c) 1
#else
#define MIN_VERSION_filepath(a,b,c) 0
#endif
#endif

Both these are designed to work in ghci, but have a happy side effect of working in HLint as well.

Since HLint 1.8.60 there is the --cpp-file file flag, point that at the generated Cabal macros file and it will be included and do the right thing.

I can confirm this behaviour. I have no problems using the --cpp-file option.
$ cpphs --version
cpphs 1.19.3

$ hlint --version
HLint v1.9.29, (C) Neil Mitchell 2006-2016

I have a file where I've said
#if defined(MIN_VERSION_base) && MIN_VERSION_base(4, 7, 0)
_iType :: FiniteBits b => a -> b -> DbType
...
#endif

and I get
% hlint --cpp-file=dist/build/autogen/cabal_macros.h  lib/Types.hs
hlint: macro MIN_VERSION_base expected 3 arguments, but was given 0

This is with
% hlint --version
HLint v1.9.28, (C) Neil Mitchell 2006-2016
% cpphs --version
cpphs 1.19.3

I don't have time to update to the latest hlint just now, as I have to go see Deadpool.

I don't  use defined(MIN_VERSION_base).

Is it possible for hlint to determine/find cabal_macros.h automatically?

@juhp - that seems sensible and simple, yes, I'll definitely do that - very good idea.

that seems sensible and simple

I'm not sure if it is simple. Keep in mind that Cabal sandboxes don't use the default directory dist/build for creating the cabal_macros.h file. In addition, the default directory can be changed using  the --builddir option of cabal-install.

From the CHANGELOG of cpphs, the issue related to #if defined(FOO) && FOO(a,b) was fixed in cpphs 1.20.

FYI, the bug tracker for cpphs is here.

Yes, cpphs-1.20.1 has the bugfixes for most of the issues mentioned in this thread.  Please try it out.

I can confirm that upgrading did seem to fix the issues for me:

old

% hlint --version
HLint v1.9.28, (C) Neil Mitchell 2006-2016
% cpphs --version
cpphs 1.19.3
% hlint tools/ObsCat.hs
hlint: Cannot expand #if directive in file tools/ObsCat.hs  at line 71 col
1:
    MIN_VERSION_time(a,b,c) is not a defined macro

new

% hlint --version
HLint v1.9.31, (C) Neil Mitchell 2006-2016
% cpphs --version
cpphs 1.20.1
% hlint tools/ObsCat.hs
tools/ObsCat.hs:244:3: Suggestion: Redundant bracket
Found:
... and a few more

The new version also worked on a file that was afflicted with the complaint
about containing lines like
#if defined(MIN_VERSION_base) && MIN_VERSION_base(4, 7, 0)

So thanks to everyone for this.
On Fri, Mar 4, 2016 at 11:18 AM Malcolm Wallace notifications@github.com
wrote:

Yes, cpphs-1.20.1 has the bugfixes for most of the issues mentioned in
this thread. Please try it out.
—
Reply to this email directly or view it on GitHub
https://github.com/ndmitchell/hlint/issues/53#issuecomment-192340886.

I now require cpphs-1.20.1, which hopefully fixes these issues, and also added a test specifically for this common case to hlint.

Thank you!  hlint-1.9.32 is working well for me so far.

authors: DougBurke Kasceh asr juhp malcolmwallace ndmitchell

repo: ndmitchell/hlint


text:
Rule Request: UnnecessaryShellCommand

As an engineer, I want to be warned early when my application code is trying to shell out for things that libraries already provide, such as:

curl/wget (Can probably use a URL request)
sed/awk/gawk/nawk (Can just use a regular expression)
jq (Can use a JSON marshaller)

This rule would encourage more performant applications, remove dependencies on unnecessary software components, reduce attack surfaces, and increase cross-platform support, by avoiding relying on platform-specific shell command syntax.
Example triggers:

Supplying a process object with a launch path ending with curl, wget, sed, awk, jq, jq.exe, etc.

Example non-triggers:

Supplying a process object with an argument of curl, wget, sed, awk, jq, jq.exe, etc. While there are plenty of cases where these would constitute unnecessary shell commands, such as /usr/bin/env curl... or exec wget..., the false positives for such commands are unfortunately more numerous than the true positives.

This rule should contain a limited number of common shell commands, such as those listed above. We can add more over time. Configuration for this rule should be able to customize which of these command patterns is relevant to the user's application needs.
As a security concern, this rule can reasonably become a default rule, as shelling out introduces additional security risks, including shell injections, compared to sticking to pure library code.
I would be happy to see this rule be included in HLint's available suite of checks, and if we find we're happy to apply it in a lot of places, then we can always turn it on by default later.

HLint can warn you, but it can't fix the code, which makes it less attractive.

Heh, this is an interesting problem in that case. Let's say hypothetically we add a bit of code to generate the equivalent pure Haskell (Shpider?) code to a simple shell + curl call. What about all the crazy flags that curl supports? What about wget and its flags? What about HTTPie? What about new flags that these applications add over time? What about external Perl, Ruby, Python, Lua, Tcl, sh calls?
I agree, it is impractical to automatically generate replacement code for arbitrary shell calls. So unfortunately, this rule would not be able to intelligently update the Haskell user's code on their behalf.
What do you think about treating this rule as more of a plain warning? We could recommend some pure Haskell libraries for some known shell calls, and leave it ultimately up to the programmer to decide how to react.
I think this rule is sensitive enough that it should probably be disabled by default, more opt-in than anything else.

I'm not averse to being disabled by default, but I don't think it should be the default out the box behaviour.

authors: mcandre ndmitchell


text:
Error during docker build

Describe the bug
After following the steps to build docker I have an error during this one =>https://docs.briefkastenhq.com/docs/self-hosting.html#docker
#0 19.43 > Build failed because of webpack errors
#0 19.46  ELIFECYCLE  Command failed with exit code 1.
------
failed to solve: executor failed running [/bin/sh -c pnpm build]: exit code: 1

There is an error in step 7=>
user@PC:~/docker/briefkasten$ docker-compose up -d
[+] Building 52.8s (14/21)
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 2.46kB                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 132B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:16-bullseye-slim                                                                                52.7s
 => [release  1/11] FROM docker.io/library/node:16-bullseye-slim@sha256:4fc367c89d498b455c6497cdd6211cc6a180bede77d8df80dea9acbcd5ffa19c                                                              3.5s
 => => resolve docker.io/library/node:16-bullseye-slim@sha256:4fc367c89d498b455c6497cdd6211cc6a180bede77d8df80dea9acbcd5ffa19c                                                                        0.0s
 => => sha256:154e3758048b273104a377666acd12ac09b66f2a05e695b323bc777cc4540822 4.19kB / 4.19kB                                                                                0.3s
 => => sha256:572071b42bdbd96b880d1f02aca7405829d929d1d956fd2d72aef4aa6bed22c4 35.35MB / 35.35MB                                                                                0.9s
 => => sha256:4fc367c89d498b455c6497cdd6211cc6a180bede77d8df80dea9acbcd5ffa19c 1.21kB / 1.21kB                                                                                0.0s
 => => sha256:7ce58a18c049245f918c4ce6a5129c89b5d9180a2bc24a8eb257d20968736a15 1.37kB / 1.37kB                                                                                0.0s
 => => sha256:08972e06c099ec776a8635d4ac29639b27ab676c9b2ecd490c4a269d46c3b721 7.03kB / 7.03kB                                                                                0.0s
 => => sha256:bd159e379b3b1bc0134341e4ffdeab5f966ec422ae04818bb69ecef08a823b05 31.42MB / 31.42MB                                                                                0.7s
 => => sha256:25e0c562fc17eafb2090a743dd5c12781f66ea1765c42eb2945888c8a1027170 2.77MB / 2.77MB                                                                                0.8s
 => => extracting sha256:bd159e379b3b1bc0134341e4ffdeab5f966ec422ae04818bb69ecef08a823b05                                                                                0.9s
 => => sha256:7c556d030bf688ba532e1546ea3acf5f835626d2bc3c67b3da0cdd6b49fa9e8b 450B / 450B                                                                                0.8s
 => => extracting sha256:154e3758048b273104a377666acd12ac09b66f2a05e695b323bc777cc4540822                                                                                0.0s
 => => extracting sha256:572071b42bdbd96b880d1f02aca7405829d929d1d956fd2d72aef4aa6bed22c4                                                                                1.2s
 => => extracting sha256:25e0c562fc17eafb2090a743dd5c12781f66ea1765c42eb2945888c8a1027170                                                                                0.1s
 => => extracting sha256:7c556d030bf688ba532e1546ea3acf5f835626d2bc3c67b3da0cdd6b49fa9e8b                                                                                0.0s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 9.27MB                                                                                0.1s
 => [release  2/11] WORKDIR /app                                                                                0.2s
 => [release  3/11] RUN npm install -g pnpm;   pnpm --version;   pnpm setup;   mkdir -p /usr/local/share/pnpm &&  export PNPM_HOME="/usr/local/share/pnpm" &&  export PATH="$PNPM_HOME:/usr/local/sb  1.8s
 => [release  4/11] RUN addgroup --system --gid 1001 nodejs                                                                                0.6s
 => [dependencies 4/5] COPY package.json pnpm-lock.yaml prisma ./                                                                                0.1s
 => [dependencies 5/5] RUN pnpm install --frozen-lockfile                                                                                13.9s
 => [release  5/11] RUN adduser --system --uid 1001 nextjs                                                                                0.5s
 => [build 4/7] COPY --from=dependencies /app/node_modules ./node_modules                                                                                2.4s
 => [build 5/7] COPY . .                                                                                0.1s
 => [build 6/7] RUN pnpm dlx prisma generate                                                                                7.1s
 => ERROR [build 7/7] RUN pnpm build                                                                                19.5s
------
 > [build 7/7] RUN pnpm build:
#0 0.778
#0 0.778 > briefkasten@0.9.0 build /app
#0 0.778 > next build
#0 0.778
#0 1.119 warn  - You have enabled experimental features (legacyBrowsers, browsersListForSwc) in next.config.mjs.
#0 1.120 warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
#0 1.120
#0 1.141 Attention: Next.js now collects completely anonymous telemetry regarding usage.
#0 1.141 This information is used to shape Next.js' roadmap and prioritize features.
#0 1.141 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
#0 1.141 https://nextjs.org/telemetry
#0 1.141
#0 1.245 info  - Linting and checking validity of types...
#0 4.793
#0 4.793 ./src/pages/index.jsx
#0 4.793 123:6  Warning: React Hook useEffect has a missing dependency: 'nextauth.user'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
#0 4.793
#0 4.793 info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
#0 4.795 info  - Creating an optimized production build...
#0 19.43 Failed to compile.
#0 19.43
#0 19.43 Sentry CLI Plugin: Command failed: /app/node_modules/.pnpm/@sentry+cli@1.74.5/node_modules/@sentry/cli/sentry-cli releases new ydC5d0zxMx3SlD5XQJeMM
#0 19.43 error: API request failed
#0 19.43   caused by: [60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: unable to get local issuer certificate)
#0 19.43
#0 19.43 Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
#0 19.43 Please attach the full debug log to all bug reports.
#0 19.43
#0 19.43 Sentry CLI Plugin: Command failed: /app/node_modules/.pnpm/@sentry+cli@1.74.5/node_modules/@sentry/cli/sentry-cli releases new ydC5d0zxMx3SlD5XQJeMM
#0 19.43 error: API request failed
#0 19.43   caused by: [60] SSL peer certificate or SSH remote key was not OK (SSL certificate problem: unable to get local issuer certificate)
#0 19.43
#0 19.43 Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
#0 19.43 Please attach the full debug log to all bug reports.
#0 19.43
#0 19.43
#0 19.43 > Build failed because of webpack errors
#0 19.46  ELIFECYCLE  Command failed with exit code 1.
------
failed to solve: executor failed running [/bin/sh -c pnpm build]: exit code: 1

Is it planned to have a docker image on a public registry (ex: docker.hub) ?
Thank you for your work
Reproduction
docker-compose up -d
System Info
System

Used Package Manager
n/a
Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Same issue on Rocky 9, Docker Compose version v2.10.2,  Docker 20.10.18.

Same issue, Debian 11, Docker 20.10.18, Compose 2.10.2,

Duplicate of #20.
Fixed in latest commit on main

authors: Bloopps ayaseenx ndom91 verchalent


text:
Ability to collect feedback from users

Users of the NDS Labs Workbench services should be able to send feedback about the system. We could follow the model of Cyverse/DE and provide a short questionnaire or simply provide a text box for free text.

https://opensource.ncsa.illinois.edu/jira/browse/NDS-183

Resolved by #118

repo: nds-org/ndslabs


text:
Advanced Validity Encoding

Closes #63
WIP

[ ] Python bindings
[ ] Docs.

repo: ndsev/mapget


text:
0067 beacon update listeners in beacon manager

Closes #67

Codecov Report

Merging #69 into dev will not change coverage.
The diff coverage is 0%.

@@            Coverage Diff            @@
##                dev      #69   +/-   ##
=========================================
  Coverage     35.12%   35.12%
  Complexity      194      194
=========================================
  Files            40       40
  Lines          1247     1247
  Branches        118      118
=========================================
  Hits            438      438
  Misses          763      763
  Partials         46       46

Impacted Files
Coverage Δ
Complexity Δ

...bleindoorpositioning/ble/beacon/BeaconManager.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

authors: codecov-io marvinmirtschin

repo: neXenio/BLE-Indoor-Positioning


text:
Upload Sentry Sourcemap

This PR contains following changes:

Upload DNS for fast-auth-signer-testnet (fast-auth-signer testnet)
Upload souremaps for testnet and mainnet if SENTRY_AUTH_TOKEN is available during the build

Background:
We have too many errors that hard to track where the error occurred from precisely. (Because we wrap around try, catch and put too many async within it) Aim of this PR is to upload source map during the build and upload to sentry so that it will reveal trans-piled code and reveal exactly where the error occurred.
Currently I have setup SENTRY_AUTH_TOKEN on mainnet environment
#171

My apologies, This PR is still WIP. Created this PR to do further testing. Will update status once it is finally ready

So I manage to get the source code revealing on sentry. Basically the reason why it wasn't showing was because I was trying to invoke this in localhost environment, but sentry server can't access to localhost on my machine.
I believe this is kind of ready, but at the same time, I haven't really had chance to test against github workflow side, so may need to pay attention after merge.
So at this point, I believe this PR is ready

repo: near/fast-auth-signer


text:
Support ES6 Module Imports [NAJ-181, NAJ-52]

Motivation
To support ES6 Module Imports
Description
This PR introduces a new bundler called tsup that is recommended by turborepo
It will produce index.js (CJS), index.mjs (ESM) and index.d.ts (Type) under /dist folder as result of build.
For due diligence, I have contacted small experiment by forking the NAJ into a seperate repo that has already merged this commit, and published to a independent npm package and tried few examples to see if everything work as normal.
So far everything worked as normal.
Closes #798
Checklist

[x] Read the contributing guidelines
[x] Commit messages follow the conventional commits spec
[ ] Performed a self-review of the PR
[ ] Added automated tests
[x] Manually tested the change

Hey everyone, I'm currently conducting a clean-up on the issues of NAJ. From my perspective, this PR seems no longer relevant. Please let me know if that's not the case - I'll create an issue to track the progress; otherwise, I'll proceed to close the PR in 5 days.

Hey everyone, I'm currently conducting a clean-up on the PRs of NAJ. From my perspective, this PR seems no longer relevant. Please let me know if that's not the case - I'll create an issue to track the progress; otherwise, I'll proceed to close the PR in 5 days.

This PR is dead but I imagine the #798 issue is still relevant despite having been closed by automated tooling.

@andy-haynes Sure, we will check #798 out.

authors: andy-haynes hcho112 vikinatora

repo: near/near-api-js


text:
serve docs via GitHub Pages

work in progress

@chadoh what is context for this?

Sorry for the premature review-request, @vgrichina! I marked this as draft only after my initial PR creation, which means you got a request for review too soon.
I've update the commit message & PR description with a full explanation of what this is and why we want it. Let me know if you have any concerns with this approach or suggestions for improvement!

@chadoh looks like links in sidebar are broken, e.g.:
https://near.github.io/near-api-js/modules/_key_stores_in_memory_key_store_.html
Looks like generally none of the links are functional (tested in Safari)

@vgrichina looks like this was because GitHub Pages assumes you're deploying a Jekyll site unless you tell it otherwise, and Jekyll sites ignore any route that starts with an underscore. I've updated the workflow action here to tell GitHub that it's not Jekyll (see the touch docs/.nojekyll part of the script), and I've manually deployed a version with this file. The link you posted now works.
Great catch! I must have only checked the generated documentation locally 🤦🏻♂

authors: chadoh vgrichina


text:
Server error: Timeout (When transaction successful)

When running commands in near shell you will receive a timeout error even though the transaction was successful.
Scheduling a call: blazenetio.stake({"amount": "30000000000000000000000000"})
Error: TypedError: [-32000] Server error: Timeout
at JsonRpcProvider.sendJsonRpc (/usr/local/lib/node_modules/near-shell/node_modules/near-api-js/lib/providers/json-rpc-provider.js:129:27)
Scheduling a call: blazenetio.stake({"amount": "30000000000000000000000000"})
Error: GuestPanic [Error]: Smart contract panicked: panicked at 'Not enough unstaked balance to stake', src/lib.rs:279:9
View call: blazenetio.get_account_unstaked_balance({"account_id": "blaze2.betanet"})
'0'
View call: blazenetio.get_account_staked_balance({"account_id": "blaze2.betanet"})
'40000000000000000000000000'

Not able to duplicate this issue on my end, is the problem consistent for you...
set NODE_ENV=betanet&&node --inspect-brk=9267 bin\near call blazenetio stake "{"amount":"1000000000000000000000000"}" --accountId tester400.betanet
Debugger listening on ws://127.0.0.1:9267/73b8e1ef-0ba2-4f3b-b527-4a090d76d226
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Using options: {
accountId: 'tester400.betanet',
networkId: 'betanet',
nodeUrl: 'https://rpc.betanet.near.org',
contractName: 'blazenetio',
walletUrl: 'https://wallet.betanet.near.org',
helperUrl: 'https://helper.betanet.near.org',
useLedgerKey: "44'/397'/0'/0'/1'",
gas: '100000000000000',
amount: '0',
methodName: 'stake',
args: '{"amount":"1000000000000000000000000"}',
initialBalance: null
}
Scheduling a call: blazenetio.stake({"amount":"1000000000000000000000000"})
[blazenetio]: @tester400.betanet staking 999999999999999999999999. Received 999999998999238686151034 new staking shares. Total 1000000000000000000000001 unstaked balance and 999999998999238686151034 staking shares
[blazenetio]: Contract total staked balance is 101000000109036815839400000. Total number of shares 101000000007959923031534608

@june07 I believe this happens when the network is stalling or not enough nodes are online. I have not seen it since @bowenwang1996 did the last hard-fork.

Duplicate of https://github.com/near/near-api-js/issues/127

repo: near/near-shell


text:
Update default wallet list criteria

Thanks for taking the time to submit a pull request!
If you haven't already, be sure to take a look at the CONTRIBUTING documentation to get up to speed with the practices in this repository.
When you're ready, switch to the "Preview" tab to select an applicable template:

General template (most common)
Wallet integration template

@janewang, thank you for submitting this PR.
I will align this update with dev branch soon.

Updated, thanks for the review @kujtimprenkuSQA

authors: janewang kujtimprenkuSQA

repo: near/wallet-selector


text:
Bug: Quotes in a command mean the command is executed then said

For example, the command whisper Adam this is a thing "with" quotes will whisper that to adam, but then also say it. Plus, the command "hello" should just do You say "hello" but it does "You say "hello""`

Thanks for catching this bug, which has officially been squashed. Let me know if you discover any other issues, though!


text:
[DOC] - environment-dev.yaml does not exist

Preliminary Checks

[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions

Summary
The virtual environment section within the code contribution guidelines
speaks of an environment-dev.yaml, but this file does not exist.
In addition, step 2. says to use the file mentioned above, but then the command displayed does not work if we had this file in the first place. My guess is that we had this file at some point, but forget to update the text here, but have updated the code.
Steps to Resolve this Issue
One of

create / reinstate environment-dev.yaml and fix the code in step 2.
fix the text in the whole section to not mention environment-dev.yaml

Partially resolved by #305, but we missed the text. I'll open another PR.

authors: pavithraes pmeier

repo: nebari-dev/nebari-docs


text:
[BUG] - AWS Deployment tests getting skipped because of conditional variable

Describe the bug
Since a couple weeks ago, our AWS Deployment tests are getting skipped. See:

https://github.com/nebari-dev/nebari/actions/runs/10240771812
https://github.com/nebari-dev/nebari/actions/runs/10344230388
https://github.com/nebari-dev/nebari/actions/runs/10371249794
https://github.com/nebari-dev/nebari/actions/runs/10372048378

The issue seems to be with the way we're checking for credentials in order to decide whether we skip the job or not. I believe this behavior was introduced in https://github.com/nebari-dev/nebari/pull/2569
Expected behavior
The AWS Deployment tests should not be skipped.
OS and architecture in which you are running Nebari
Not relevant
How to Reproduce the problem?
Run the AWS Deployment workflow manually.
Command output
No response
Versions and dependencies used.
No response
Compute environment
None
Integrations
No response
Anything else?
No response

This PR will replace the env variable with an action variable set at the repo level.
https://github.com/nebari-dev/nebari/pull/2632
To allow for the tests, the following action variables need to be set:
NO_PROVIDER_CREDENTIALS_AWS: 0
NO_PROVIDER_CREDENTIALS_AZURE: 0
NO_PROVIDER_CREDENTIALS_GCP: 0
NO_PROVIDER_CREDENTIALS_DO: 0

Thanks @BrianCashProf! In the near-term future, we'll refactor the cloud provider integration tests so they don't run on a schedule basis but rather after every PR has been merged or before cutting a release. Hopefully this will make it easier for forks to work with that.

I'm closing this issue as https://github.com/nebari-dev/nebari/pull/2632 was merged. Thanks @BrianCashProf !

authors: BrianCashProf marcelovilla

repo: nebari-dev/nebari


text:
FuzzyVersionResolver: clearly defining and improving syntax

Currently, FuzzyVersionResolver seems to support * wildcards in selectors. While this makes sense, the mechanism for doing so uses a regex conversion, which fails to quote the rest of the string. As such, com.mycompany.extensions would match com-mycompany-extensions since the rest of the string is interpreted as (modified) regex.
As a secondary concern, currently nested dependency overrides are not supported (e.g. I cannot specify com.mycompany.group:myapp-* as one version, but set com.mycompany.group:myapp-utils-* to some other version, e.g. due to independent versioning. Currently, if multiple glob-style overrides apply to one version, the glob used seems to be undefined (e.g. HashMap order).
Combining these concerns, I'd propose canonicalizing syntax some more, with the following rules:

The only control characters are : and *; the former is the group-module separator, and the latter is a wildcard character matcher. All other characters will be matched literally.
Exact module match is tested first. After that, glob matchers are tested in order of decreasing specificity (where specificity = number of non-wildcard characters).

Mostly, I'd like to enable the workflow of "obvious nested wildcard overrides", i.e.
com.mycompany.group:myapp-* = 1.0.1
com.mycompany.group:myapp-utils-* = 2.2.1

with the regex-escaping issue as incidental cleanup.

I'd be interested in using this behavior -- do the maintainers of this project feel it's in-scope for the plugin?

@DanielThomas @rspieldenner Can this be safely closed now that the PR is merged?


text:
BUG: Unable to load attribute of precompiled dll

When I import the hybrid-packages package, one assembly, which references pre-compiled dlls, seems to suddenly cannot find the dlls and is unloaded by unity.
Steps to reproduce

Create a new project in Unity 2021.3
Download this zip file and extract the content somewhere on your disk (it is a very small package)
In your Unity project, add the unzipped package via "+" -> "Add package from disk...".
Select a game object and realize that several fields are drawn yellow in the inspector now (this is what the test-package does - by using 0harmony.dll)
Import hybrid-packages via "+" -> "Add package from git URL..." and enter https://github.com/needle-tools/upm-in-unitypackage.git
Close Unity
Open the project again

Result
There are two error messages in the console:
Unable to load attribute info on class .ColorizeInspectorFields. Are you missing a reference?

Unloading broken assembly Library/ScriptAssemblies/Test.Editor.dll, this assembly can cause crashes in the runtime

When you click on the ColorizeInspectorFields file in the project window, another error is spammed to the console:
MissingMethodException: Method not found: void HarmonyLib.HarmonyPatch..ctor(string,string,HarmonyLib.MethodType)
System.MonoCustomAttrs.IsDefined (System.Reflection.ICustomAttributeProvider obj, System.Type attributeType, System.Boolean inherit) (at <487e528c992b4333913a4cf415048a57>:0)
System.RuntimeType.IsDefined (System.Type attributeType, System.Boolean inherit) (at <487e528c992b4333913a4cf415048a57>:0)
System.Attribute.IsDefined (System.Reflection.MemberInfo element, System.Type attributeType, System.Boolean inherit) (at <487e528c992b4333913a4cf415048a57>:0)
System.Attribute.IsDefined (System.Reflection.MemberInfo element, System.Type attributeType) (at <487e528c992b4333913a4cf415048a57>:0)
UnityEditor.EditorGUIUtility.GetIconPathFromAttribute (System.Type type) (at <41e5d835fcc44171a345bfc23f1271b9>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

Note that nothing will be tinted in yellow in the inspector.
Expected Result
hybrid packages should not mess with assembly references. Everything should work the same way as it does without hybrid-packages.
Notes
I only tried the "Add package from git URL" as described in step 5 yet. I did not try Unity's Asset Store Tool. I also only tried Unity 2021.3 yet.
When you remove the hybrid-packages package again and force a recompile (maybe step 6 & 7 can also be replaces with a simple recompile), everything works again.
If you have an idea what could cause this or know a workaround, please let me know.

I just looked into your source code and realized that you use Harmony as well.
This might be the problem, as unity might not want to load two dlls with the same namespaces inside?
So, maybe I have to make my own harmony-dll with different namespaces 🤔

I think I fixed it:

I made the "Hybrid Packages" mutable by copying it to the project's Packages folder
I changed the harmony reference in the asmdef file of the "Hybrid Packages" to the dll I am using in my package
I deleted the harmony dll of the "Hybrid Packages"

Seems like all is working now.

repo: needle-tools/hybrid-packages


text:
Want to be a collaborator

I've made some contributions to this repo and would love to have collaborator permissions on the repo to merge PRs and review others' PRs. @neetcode-gh would like to draw your attention to this matter.

Thanks for your contributions! Just invited you as collaborator

authors: neetcode-gh tahsintunan

repo: neetcode-gh/leetcode


text:
0.1.4

This pull request contains features/fixes for the following issues:

Issue 62
Issue 63
Issue 64

Codecov Report

Merging #68 into master will decrease coverage by 1.22%.
The diff coverage is 57.89%.

@@            Coverage Diff            @@
##           master     #68      +/-   ##
=========================================
- Coverage   83.72%   82.5%   -1.23%
=========================================
  Files           5       5
  Lines         424     440      +16
=========================================
+ Hits          355     363       +8
- Misses         69      77       +8

Impacted Files
Coverage Δ

pyscc/controller.py
86.17% <100%> (ø)
:arrow_up:

pyscc/element.py
80.41% <50%> (-1.81%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: codecov-io neetjn

repo: neetjn/py-component-controller


text:
Error code 0x0003 at src\HID.cpp(282) `anonymous-namespace'::HidModelInfo: The system cannot find the path specified.

Bug description
Cannot open device list in the configuration UI, crashes with "Something unforeseen..."
When running --dev-all with CLI client, showing error:
Error code 0x0003 at src\HID.cpp(282) `anonymous-namespace'::HidModelInfo: The system cannot find the path specified.

Steps to reproduce
Not sure the exact cause of this as it works on my other computer.

Does it also happen with this build?
Cheers

OMG It worked!! I have been messing around trying to figure out what's wrong for an hour. What's the magic 😂

Thanks for confirming, I need to craft a new public release ant it will be fixed for all 👍

Fixed here btw.

Published, can you please test and confirm this works: https://github.com/nefarius/HidHide/releases/download/v1.5.224.0/HidHide_1.5.224_x64.exe

Published, can you please test and confirm this works: https://github.com/nefarius/HidHide/releases/download/v1.5.224.0/HidHide_1.5.224_x64.exe

The released version does not seem to work. One thing worth noting is that the client says it's v1.5.212.0 in the title bar even though the installer says it's 1.5.224.

Gotcha, I'll look into it, thanks.

@v3i1y this should do the trick http://sharex.nefarius.at/u/HidHide_1.5.230_x64.exe

@Jaybooon feel free to test it as well.

@v3i1y how's it going, mate?

Sorry, haven’t had a chance to try it yet will take a look tonight.
On Thu, May 16, 2024 at 09:03 Benjamin Höglinger-Stelzer <
@.***> wrote:

@v3i1y https://github.com/v3i1y how's it going, mate?
—
Reply to this email directly, view it on GitHub
https://github.com/nefarius/HidHide/issues/151#issuecomment-2115635306,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2QWH7AE5UTUU4NBD6GXWDZCTKGNAVCNFSM6AAAAABHSBXQCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVGYZTKMZQGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I consider this fixed, closing.

repo: nefarius/HidHide