Attempting to load pdfjs library fails with syntax error

I would like to use the pdf.js library from Python. This is how I tried to load it with JSPyBridge:
>>> import javascript
>>> pdfjsLib = javascript.require("pdfjs-dist")

It fails with the following error:
Error in exception handler
[Errno 2] No such file or directory: 'internal/modules/cjs/loader.js'
** JavaScript Stacktrace **
/home/mara/node_modules/pdfjs-dist/build/pdf.js:2440
    return this._jsActionsPromise ||= this._transport.getPageJSActions(this._pageIndex);
                                  ^^^

SyntaxError: Unexpected token '||='
    at wrapSafe (internal/modules/cjs/loader.js:1001:16)
    at Module._compile (internal/modules/cjs/loader.js:1049:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async Object.$require [as require] (/home/mara/.local/lib/python3.8/site-packages/javascript/js/deps.js:128:15)
    at async Bridge.call (/home/mara/.local/lib/python3.8/site-packages/javascript/js/bridge.js:136:17)
** Python Stacktrace **
  File "<stdin>", line 1, in <module>

  File "/home/mara/.local/lib/python3.8/site-packages/javascript/__init__.py", line 37, in require
    return config.global_jsi.require(name, version, calling_dir, timeout=900)

  File "/home/mara/.local/lib/python3.8/site-packages/javascript/proxy.py", line 213, in __call__
    else self._exe.callProp(

  File "/home/mara/.local/lib/python3.8/site-packages/javascript/proxy.py", line 153, in callProp
    resp = self.pcall(ffid, "call", method, args, timeout=timeout, forceRefs=forceRefs)

  File "/home/mara/.local/lib/python3.8/site-packages/javascript/proxy.py", line 141, in pcall
    raise JavaScriptError(attr, res["error"])

That error is "your node version is below 16"
On Sat, Feb 12, 2022, 18:25 mara004 @.***> wrote:

I would like to use the pdf.js https://github.com/mozilla/pdf.js from
Python. This is how I tried to load it using JSPyBridge:

import javascript>>> pdfjsLib = javascript.require("pdfjs-dist")

It fails with the following error:
Error in exception handler
[Errno 2] No such file or directory: 'internal/modules/cjs/loader.js'
** JavaScript Stacktrace **
/home/mara/node_modules/pdfjs-dist/build/pdf.js:2440
return this._jsActionsPromise ||= this._transport.getPageJSActions(this._pageIndex);
^^^
SyntaxError: Unexpected token '||='
at wrapSafe (internal/modules/cjs/loader.js:1001:16)
at Module._compile (internal/modules/cjs/loader.js:1049:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at ModuleWrap. (internal/modules/esm/translators.js:199:29)
at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
at async Loader.import (internal/modules/esm/loader.js:178:24)
at async Object.$require [as require] (/home/mara/.local/lib/python3.8/site-packages/javascript/js/deps.js:128:15)
at async Bridge.call (/home/mara/.local/lib/python3.8/site-packages/javascript/js/bridge.js:136:17)
** Python Stacktrace **
File "", line 1, in
File "/home/mara/.local/lib/python3.8/site-packages/javascript/init.py", line 37, in require
return config.global_jsi.require(name, version, calling_dir, timeout=900)
File "/home/mara/.local/lib/python3.8/site-packages/javascript/proxy.py", line 213, in call
else self._exe.callProp(
File "/home/mara/.local/lib/python3.8/site-packages/javascript/proxy.py", line 153, in callProp
resp = self.pcall(ffid, "call", method, args, timeout=timeout, forceRefs=forceRefs)
File "/home/mara/.local/lib/python3.8/site-packages/javascript/proxy.py", line 141, in pcall
raise JavaScriptError(attr, res["error"])
—
Reply to this email directly, view it on GitHub
https://github.com/extremeheat/JSPyBridge/issues/47, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437XUWVXISW5I47YTBPDU22JWVANCNFSM5OHGAC2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Try doing what the error says and use the legacy build, or Google the error. it doesn't look like it has anything to do with the bridge

This thread looks related. I'll try the legacy build...

Yes, the legacy build helped. I am now able to invoke pdfjs using
>>> pdfjsLib = javascript.require("/home/mara/Downloads/builds/pdf.js/build/generic-legacy/build/pdf.js")
>>> loadingTask = pdfjsLib.getDocument("/home/mara/Downloads/Anderes/pdfs/test.pdf")

However, I'm wondering what is meant by browser/environment in the exception. What would I need to update in order to use the "normal" (non-legacy) build?

I guess you'd need to use a browser
On Sat, Feb 12, 2022, 20:04 mara004 @.***> wrote:

Closed #47 https://github.com/extremeheat/JSPyBridge/issues/47.
—
Reply to this email directly, view it on GitHub
https://github.com/extremeheat/JSPyBridge/issues/47#event-6057893382,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437TX2Y3VEKUUIQW7XFTU22VKZANCNFSM5OHGAC2A
.
You are receiving this because you commented.Message ID:
@.***>

FWIW, this works now with the regular (non-legacy) build, outside of a browser. I'm on a newer OS and nodejs version these days. Perhaps my nodejs was just still too old?

@mara004 seems that Node added ReadableStream quite recently, https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream


Improve ScreenshotBaseTest

WHAT
Improve ScreenshotBaseTest to allow it to set the parameters in a more convenient way, without requiring to call and import screenshotTestRuleParams. For example:
class MyTest : ScreenshotBaseTest({
    screenTimeText = {}
    enableA11y = true
}) {

WHY
Feedback on usage https://github.com/google/horologist/pull/1312#discussion_r1205741849
HOW
Suggestion of implementation with type safe builders.

We should probably also pick up the record default value from a system property so we can run tests in a record mode, and not edit the files.


filewatcher: Change to pull+push mode

Currently filewatcher only work on push mode, by using fsnotify to
monitor the parent directory. This might break when the whole parent
directory is remounted. Add pull mode, that checks the file mtime when
Get is called, and force reload the file if the mtime is after the last
parsed mtime.

so we can pump the mtime from limitopen.Open, but that requires some breaking changes (also limitopen is under internal so breaking changes should be OK?). I feel that it's probably not worth all the trouble as the consequences are very minor, but if people feel strongly I can do that.


Ctags doesn't work in Vim

Windows Version: 10.0.18362.900
Steps to reproduce

Install WSL2
Install ctags and vim
Tag a source directory with ctags -R .
Open vim and try to jump to function definitions with Ctrl+]
Vim reports no tags stack was found

Expected behavior'
Vim should jump to the function definition

Cannot repro here.


feat: Add gitlab group visibility to group entity via annotation

Hey, I just made a Pull Request!
This PR adds an annotation to groups ingested by gitlab org provider and annotates them with their visibility level:
fixes #22887
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Not stale :-)

Anyone that's consuming the GitLabGroup type that's exported is now going to have to provide visibility in that now, which would be a breaking change. Not sure what the impact of that is though, maybe it's fine to just accept that this is a breaking change,  otherwise @tudi2d is correct, that we should make this optional instead, even though the producer of this would always make sure its set.

I changed the visibility to optional - you are right, it is totally fine to make it optional and set it all the time


Accordion Section does not render across the screen

Issue Details
Type of Issue  (check one with "X")
[X] Bug Report => Please search GitHub for a similar issue or PR before submitting
[ ] Feature Request => Please ensure feature is not already in progress
[ ] Support Request => Please do not submit support requests here, instead see: https://discourse.oss.antheminc.com/

Current Behavior
Currently when the content in the Accordion Label is not enough to cover the entire width of the screen, the Accordion section does not render across the screen.
Expected Behavior
The Accordion section must render across the available UI real estate
How to Reproduce the Issue
Steps to Reproduce
Code Snippet

Environment Details

Nimbus Version:
1.3.2.M2

Browser:
Google Chrome

nm-accordion {flex-basis:100%;}
Please override the css by pasting the above in the app_styles.css


Why ...error: NaN...?

Inputs are not normalized.  Take the highest value for each of the input names, and divide each by the highest number.
Why this needs to be done either automatically or manually: Imagine whispering a beautiful novel to someone right in their ear, then yell at the top of your voice randomly and see how much they get out of it.  Or imagine yelling across a casum to someone that you need help, and then whispering why and what you need, and see how much the person understands.
Digital neural networks operate on the same principles as real ones.  Ensuring values are of the same magnitude prevent headaches.


feat(20454): Implement basic config based event filtering

https://kontur.fibery.io/Tasks/Task/FE-Implement-basic-config-based-event-filtering-20454

Summary by CodeRabbit

New Features

Added a message for no matching disasters in search results.
Introduced new sorting and filtering functionalities for event lists.
Enhanced event categorization with new event types and sorting configurations.
Implemented Multi-Criteria Decision Analysis (MCDA) for event sorting.

Bug Fixes

Improved error handling for sorting and filtering operations.

Documentation

Updated documentation to include new sorting capabilities and configuration options.

Chores

Removed obsolete constants related to event list controls.

@coderabbitai pause

Filtering by filterByMinStartedAt is already fixed, needs a review/approve


How to pre populate/'ui:placeholder' an input of format 'date-time'?

I have a form which requires an input of format 'date-time'. I would like to be able to pre populate it with the current date (whatever today is). I have tried simply passing the current date as a string to the uiSchema as such:
const schema = {
  title: 'Title',
  type: 'object',
  required: ['myDateField'],
  properties: {
    myDateField: {
      type: 'string',
      title: 'Date',
      format: 'date-time'
    }
  }
};

const uiSchema = {
  myDateField: {
    'ui:placeholder': (new Date()).toString() // Does not work
  }
};

I have searched both in the documentation, current and old issues and can't find an answer to that. I was wondering if anyone could give me hand with this.

Either set formData with the current date or dynamically define it as a default value for that field in the schema.

Closing, feel free to reopen if this didn't fix your issue.

Thank you so much, I ended up setting the formData.


Fixes

Added submit whenToValidate option
Add state when validating form fields
Added blob form field type
Fix null value checks validations
Add field name name to form isInvalid

How Has This Been Tested?
Unit and functional tests
Types of changes

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

Checklist:

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

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is 100%.

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


Analytics as classes

Implement analytics as classes:

should be able to get e,b,h,j from any analytic
each one will need to have docs and error checking so it is clear what you can use for input (ie. if the solution is confined to a given plane)
This will allow us to wrap them up later as problems

This issue was moved to simpeg/simpeg#145


Include lib can't be found that is present

There seems to be an issues with the compilation order in release-structured projects. This is an example how the problem presents itself:
https://github.com/ypaq/merp_test
There are two OTP applications in apps, merp_test and nerp_test. merp_test_app.erl includes a header file from nerp_test using -include_lib. rebar3 fails to compile the project due to missing header.
$ rebar3 compile
===> Verifying dependencies...
===> Compiling merp_test
===> Bad use of -include_lib("nerp_test/include/nerp_test.hrl"). First path component should be the name of an application. You probably meant -include("nerp_test/include/nerp_test.hrl").
===> Could not find header for -include_lib("nerp_test/include/nerp_test.hrl").
===> Compiling /Users/tilman/dev/erlang/merp_test/_build/default/lib/merp_test/src/merp_test_app.erl failed:
/Users/tilman/dev/erlang/merp_test/_build/default/lib/merp_test/src/merp_test_app.erl:10: can't find include lib "nerp_test/include/nerp_test.hrl"

The file nerp_test/include/nerp_test.hrl is present in the project: https://github.com/ypaq/merp_test/blob/master/apps/nerp_test/include/nerp_test.hrl

I'm hoping that this will fix it: Add nerp_test to the applications list in merp_test. My guess is that it since it isn't depending on it rebar3 won't compile and load into the path nerp_test before compiling merp_test.

Doesn't fix it, sorry.

Ok, I'll clone it and try some things in a bit.

Thanks!

Yup, looks like compile order isn't right for project apps.

Should be fixed.

Awesome, works! Thank you! :+1:


Multiple ResultsPanel improvements

Summary:

Fixed shortcuts

The active panel gets the input shortcuts.
Contextual shortcuts (Ctrl+C and Delete) are only executed when the active panel has focus.

Fixes squiggles

Squiggles appear when panel is on focus; disappear when lost focus.
The main UI always shows squiggles.

Active panel management

The panel that got the focus most recently is the active panel, regardless of whether it currently has focus or not.

Issues:

[x] Focus management with floating panels is really buggy. It sometimes fires Enter event, but most of the time it doesn't.

Todo:

[x] Save layout data.
[x] Allow multiple windows for Find All References.

Should there be a setting for whether to allow multiple windows for Find All References?
Wouldn't be much of a hassle to add.

From my side I don't think I would ever switch back to the old behavior... I guess for some people it may be faster to just have one results panel, but then it's most times a PITA to work like that... you lose your results on so many unwanted occasions...

Why show squiggles only on active panel?

Not exactly the old behaviour. See how 'Find All References' creates a new panel each time. For example, in VS, the same panel for 'Find All References' is used unless you lock the panel; then multiple panels are created for each use.
Advantages of using that feature: it wouldn't be only 'Find All Reference', which is hardcoded to have multiple panels, to be able to have multiple panels for each use. Other panels will also be able to have multiple panels (which panels will have the option to let users allow multiple windows, will however be hardcoded, since you wouldn't want multiple linting results panels).
If we set the default of these panels to allow multiple panels, there aren't any disadvantages of adding this.

Those squiggles are more like highlights, and before I used to allow all highlights to be visible, and while testing, I figured that it looks confusing and not very useful.
The default panel, which shows the errors and warnings, will always have them visible.

OK, sorry, I understood your message as a setting for the old behavior. In that case I think it may be useful.
I would prefer to have all squiggles visible at any time. I know it may be confusing to see squiggles and not know where the problem comes from, but IMHO that's better than having some issue and not knowing you have it because you didn't activate the corresponding panel.
I guess we should display issues when hovering some squiggle, but that's another subject.

Merging to let progress  go on, but left some comments.


Network card retrieval

Maybe added in a next update:
NetworkCard MAC retrieval
Get-CimInstance Win32_NetworkAdapterConfiguration | Select-Object MACAddress

Done


had to click multiable times to get mutation data correctly

I am trying to run mutation but for the first or second time result.data returns null as well as the context and the exception
but when I run the mutation again it returns data correctly
here is my VIEW code :
Scaffold(
      appBar: AppBar(
        title: Text('LoginView'),
        centerTitle: true,
      ),
      body: Center(
        child: Mutation(
            options: MutationOptions(
                document: gql(Queries.LOGIN),
                fetchPolicy: FetchPolicy.networkOnly),
            builder: (runMutation, QueryResult? result) {
              return Column(
                children: [
                  TextFormField(
                    controller: controller.username,
                  ),
                  TextFormField(
                    controller: controller.password,
                  ),
                  TextButton(
                      onPressed: () async {
                        try {
                          runMutation(
                            {
                              "email": controller.username.text,
                              "password": controller.password.text,
                            },
                          );

                          print(result!.data);
                          token = result.data!["userLogin"]["token"];
                          print(token);
                          Get.toNamed(Routes.PROFILE, preventDuplicates: true);
                        } catch (e) {
                          print(e);
                        }
                      },
                      child: Text("GET TOKEN"))
                ],
              );
            }),
      ),
    );

and this is my query :
static final CREATE_PROPERTY = r"""mutation add_property($by: Int!, $name: String!,
   $purpose: String!, $propType: String!, $payMethod: String!, $available: Boolean!,
    $price: Float!, $area: Float!, $bedroom: Float!, $bathrooms: Float!, $image: Image) {
  createProperty(data: {createdBy: $by, propertyName: $name, purpose: $purpose,
   propType: $propType, payMethod: $payMethod, available: $available, price: $price,
   area: $area, bedrooms: $bedroom, bathrooms: $bathrooms, verified: false,
   features: {elevator: false, attachment_building: false, servantRoom: false,
    has_furniture: false, carParking: false, carEntrance: false, hall: false,
     garden: false, kitchen: false},
    image: $image}) {
    id
    verified
    area
    available
    bathrooms
    bedrooms
    propertyName
    price
    createdBy {
      id
      name
      phone
      roles
    }
    propType
    payMethod
    image
  }
}
""";

pubspec.yaml

dependencies:
  flutter:
    sdk: flutter
  cupertino_icons: ^1.0.2
  dio: ^4.0.0
  flutter_easyloading: ^3.0.0
  get: 4.3.0
  graphql_flutter: ^5.0.0
  http: ^0.13.3
  infinite_scroll_pagination: ^3.1.0
  multi_image_picker2: ^5.0.2
  path: ^1.8.0
  responsive_framework: ^0.1.4

dev_dependencies:
  flutter_test:
    sdk: flutter
  lints: 1.0.1

If you prepare reproducible demo you will have more chances that some will try to help you

@vasilich6107 thanks because you remind me to update this
wrong scenario : 👎🏻
I was trying to get and use mutation data from onPressed  after runMutation
correct scenario : 👍🏻
get mutation and use it from either onFinshed:  or update :  ( Use it from mutation options)
better scenatio : 💯
split your view from your business logic and get data from your logic using var result = client.query () or var result = client.mutate()  and then use the data from result (will be better if you parsed that data)  in your view .
(Setup your client first and you may need to use get_it or getx to use it as service)


[Fix  #4333] Implement asynchronous search reindex functionality using celery

The management command reindex_elasticsearch has been rewritten from scratch using celery tasks.
The idea is taken from @robhudson blog post and heavily inspired from the code of mozilla/zamboni.
Need to overwrite some method of django-elasticsearch-dsl in order to support zero downtime rebuild (https://github.com/sabricot/django-elasticsearch-dsl/issues/75). I am hoping to send a PR to upstream.
This fixes  #4333
@ericholscher @rtfd/core r?

I have tested with about 10K files in single celery host with 4 workers. The indexing got finished within 20 seconds.

Another thought -- should this be implemented as a contribution to DED with a Celery backend, instead of our own custom logic? It sounds like we might be able to do it fix Celery with a setting: https://github.com/sabricot/django-elasticsearch-dsl#elasticsearch_dsl_signal_processor

Another thought -- should this be implemented as a contribution to DED with a Celery backend, instead of our own custom logic? It sounds like we might be able to do it fix Celery with a setting:
https://github.com/sabricot/django-elasticsearch-dsl#elasticsearch_dsl_signal_processor

Sure, I will surely port it to DED, but I wonder if we can use the signal processor as that is called while saving/updating the objects.

We could also perhaps add a celery flag to the existing indexer command? So that we don't have to maintain our own set of code around indexing.

Thats really true. But it needs some time to get it reviewed and merged into master. I will open a PR there soon, but to get our deployment soon, we can keep it here untill then.

Thats really true. But it needs some time to get it reviewed and merged into master. I will open a PR there soon, but to get our deployment soon, we can keep it here untill then.

We can always deploy a forked version while we wait for it to get accepted. It's true though we don't want to be waiting for review & merge from them, but perhaps it will be quick.

I'm a little concerned about the complexity of this approach. Is there a reason we're using chunks here when we already have a domain object to chunk on which is the Version? This feels like extra work to do and code to maintain, when we already have an existing way to think about this problem.

This is a general purpose management command for indexing all type of documents like Project/HTMLFile, not only the HTMLFile. So I had only one way to make a chunk depending on number.

This approach also doesn't use the same code path for indexing as our application code, so now we have two different ways of indexing files, which doesn't seem great.

Yeah, thats true. This management command actually reindex all the documents. On the otherside, DED catch the signal when a new file is created and index it into Elasticsearch.

It really feels like all we need is:

- A management commands that iterates over versions, and sends them to be indexed
- A celery task that takes a version and indexes all the files in that version, which is called both in production as well as in reindexing.

As mentioned above, the management command is general purpose. So something specially for HTMLFile would be extra implementation that maybe not available when we port it to DED

Yeah, thats true. This management command actually reindex all the documents. On the otherside, DED catch the signal when a new file is created and index it into Elasticsearch.

Right, but that doesn’t scale properly right now. It currently sends an http request per file saved during project build. We need to batch it, which could use similar logic to this.

Right, but that doesn’t scale properly right now. It currently sends an http request per file saved during project build. We need to batch it, which could use similar logic to this.

I understand. but how do we get the files in batch? Do there any signal that is sent in batch?

We should just update the code to keep track of the files that are changed, as it works now.

Do we need this to be another Celery task? It's already running inside of Celery, so I'm not sure we need to delay it here. It could lead to weird race conditions if it got queued up for a long time.

Good catch @ericholscher. I will fix it in synchronous task. Thanks

@ericholscher I have fixed the issues as you mentioned and fixed the tests. Also added a comment in https://github.com/rtfd/readthedocs.org/issues/4264#issuecomment-406404957 for testing it in backlog. r?

@ericholscher Fixed the timestamp issue. r?

This looks good. 👍


Tecs fix pitch integ

This should fix #2893.

@boosfelm @tumbili please review / test.

@dagar This might be relevant for you.

from a first glance looks reasonable to me, we will test asap.
@mswingtra this is not yet in master, can you make sure we test it when we go flying next time? Thanks

This could be another instance (pre-fix):
http://logs.uaventure.com/view/CRzMpDoUvSshcFPY8wNXUA

@sjwilks @AndreasAntener Could you maybe cross-test this on a Wing-Wing on your next test flight session?

@AndreasAntener did we not already test this? Or are we just not seeing it now that we start with a runway takeoff?

No we didn't test this yet. We don't see the effect of it because during runway takeoff TECS is already running, and at the time when it actually switches to TECS for pitch (after takeoff), the integrator has normalized itself. But the spike is there in the beginning. Let's just take that in for the next test.

Rebased on master

I'll give this a go later.

Rebased on master, applied.

Just to clarify: I've flown master with and without this. I wanted to reproduce it first with plain master but the issue did not occur (in 3 flights, also not with our runway takeoff/land branch), so I can only say that this didn't have an adverse effect.

We tested the patch and it does not happen anymore. Thanks @LorenzMeier


Suggestion: generate favicons from src folder

Basically, integrate https://github.com/jantimon/favicons-webpack-plugin
My understanding is that generally, moving things out of the public/ folder is a good thing. This seems like a sensible thing to install by default so that I don't have to eject when I want to change my favicon (which usually happens pretty immediately after creating the project

Happy to submit a PR, if desired.

Static assets should be in /public

Yes, you don't need to eject to change your favicon.
I don't think we'll go forward with this because we're breaking understood normal behavior.
Let me know if I misunderstood.


docs(installation): fix typo and edit text

Coverage remained the same at 97.524% when pulling 1396cdf39d9510f1cefa6dfe500b0b8d61e6e50a on oboukli:edit-installation-doc into 4465a9f980213ca0a6149427c0f5569f4adeaafa on ReactiveX:master.


LightGraphs dependency warning

I’m using GeometricFlux and building my graphs using SimpleWeightedGraph. However, it seems to get some of the functions I need I also have to import LightGraphs itself (for example, the add_edge! function). Then, when I import GeometricFlux I get this warning:
┌ Warning: Package GeometricFlux does not have LightGraphs in its dependencies:
│ - If you have GeometricFlux checked out for development and have
│   added LightGraphs as a dependency but haven't updated your primary
│   environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with GeometricFlux
└ Loading LightGraphs into GeometricFlux from project dependency, future warnings for GeometricFlux are suppressed.

I brought this up on the #graphs channel in the Slack and Dhairya suggested I report it here.

Thank s for trying this package!
I will deal with it ASAP. Wait for new bug fix.

The warning is just fine. It doesn't affect the use of LightGraphs and GeometricFlux anyway.
I will keep this open until the warning is solved.

Solved.


Request: Ability to copy files directly to an attached drive via web interface

Info

Which version of Pi are you using: RP 4B
Which github revision of software: 22.8.1 [b5ddb88]
Which board version: 2.3
Which computer is the RaSCSI connected to: Quadra 950

Describe the issue
Unless I'm missing something blatantly obvious, it'd be amazing if there was a way to download files (or drag to from a local machine) an area on the web config page and have those files copied directly onto one of the attached drives mounted on the RASCSI device, much like when copying files for use with AppleShare, but much easier to access when you're using a setup that doesn't allow for AppleTalk to work.

Hi @durosity !
Thank you for the suggestion. This would be a rather difficult undertaking (at least for me). The MacOS doesn't expect the SCSI drive to be changing underneath it. You'd end up with corrupted drive images if you just added files to the drive while its mounted by MacOS (or any other operating system).
The host controller interface that Gimons developed for the X68000 did something similar to what you're wanting to do , but it required a special host (Sharp X68k) driver in order to make it work.
We want to update RaSCSI to work with the BlueSCSI transfer tool (https://github.com/erichelgeson/BlueSCSI-Toolbox#bluescsi-transfer-utility), which would also allow you to transfer files to/from the Raspberry Pi to your Mac. However, that functionality isn't pulled into RaSCSI yet.
Right now, the easiest way to achieve what you're looking to do is to create a Netatalk share on your Raspberry Pi and share it with your Macintosh over Ethernet (potentially using the DaynaPort SCSI Ethernet adapter functionality)

@durosity You also have the "Download to ISO" functionality in the Web UI. If you have an "empty" CD-ROM drive attached you can get the iso image immediately inserted and mounted by Mac OS.
Beyond that, as akuker say directly writing to a hard drive image that is in use might lead to data corruption so it is not an advisable solution. I will close this ticket as WONTFIX.


pods not starting - pending status

Hi, I have coreos cluster on digitalocean, I installed kubernetes according to your example at:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
One master and two minions.
Then I followed guesbook example:
https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/guestbook
However, pods are not starting they are always in Pending status:
core@kubernetes-master ~/kubernetes_git $ kubectl get events
NAME                                   KIND                STATUS              REASON              MESSAGE
c1f73e81-90ce-11e4-9101-040136d07101   Pod                 Pending             scheduled           Successfully assigned c1f73e81-90ce-11e4-9101-040136d07101 to <IP_ADDRESS>
c1fb61e3-90ce-11e4-9101-040136d07101   Pod                 Pending             scheduled           Successfully assigned c1fb61e3-90ce-11e4-9101-040136d07101 to <IP_ADDRESS>

core@kubernetes-master ~/kubernetes_git $ kubectl get mi
NAME                LABELS
<IP_ADDRESS>       <none>
<IP_ADDRESS>       <none>

core@kubernetes-master ~/kubernetes_git $ kubectl describe pod c1f73e81-90ce-11e4-9101-040136d07101
Name:                           c1f73e81-90ce-11e4-9101-040136d07101
Image(s):                       brendanburns/redis-slave
Host:                           <IP_ADDRESS>/
Labels:                         name=redisslave,uses=redis-master
Status:                         Pending
Replication Controllers:        redisSlaveController (2/2 replicas created)
Events:
From            SubobjectPath   Status  Reason          Message
scheduler                       Pending scheduled       Successfully assigned c1f73e81-90ce-11e4-9101-040136d07101 to <IP_ADDRESS>

I did basic troubleshooting described in: https://github.com/GoogleCloudPlatform/kubernetes/wiki/Debugging-FAQ
core@kubernetes-minion-1 ~ $ ps aux|grep proxy
root       705  0.0  2.1<PHONE_NUMBER>4 ?        Ssl  Dec27   4:00 /opt/bin/kube-proxy --etcd_servers=http://<IP_ADDRESS>:4001 --logtostderr=true
core     20747  0.0  0.1   4384   724 pts/0    S+   09:40   0:00 grep --colour=auto proxy
core@kubernetes-minion-1 ~ $ ps aux|grep kubelet
root       722  0.0  2.1<PHONE_NUMBER>2 ?        Ssl  Dec27   0:41 /opt/bin/kubelet --address=<IP_ADDRESS> --port=10250 --hostname_override=<IP_ADDRESS> --etcd_servers=http://<IP_ADDRESS>:4001 --logtostderr=true
core     20755  0.0  0.1   4384   820 pts/0    S+   09:40   0:00 grep --colour=auto kubelet
core@kubernetes-minion-1 ~ $ ps aux|grep docker
root       641  0.0  2.9<PHONE_NUMBER>2 ?        Ssl  Dec27   0:16 /usr/bin/docker -d --bip=<IP_ADDRESS>/24 --mtu=1450 -s=btrfs -H fd://
core     20775  0.0  0.1   4384   812 pts/0    S+   09:40   0:00 grep --colour=auto docker

I am willing to provide extra info if required.

Your kubelet thinks it is called "<IP_ADDRESS>" but your pod was assigned to "<IP_ADDRESS>". I'm not sure how digital ocean works, but if I had to guess I would guess that this is a case of using the wrong network interface somewhere.
So the next step is probably to figure out why kubernetes master didn't use <IP_ADDRESS> as the name for the node.

If I recall DO uses two net interfaces for public and private IP, in that
order.  Maybe we grabbed eth0 and we need eth1?
On Jan 2, 2015 10:27 AM, "Daniel Smith"<EMAIL_ADDRESS>wrote:

Your kubelet thinks it is called "<IP_ADDRESS>" but your pod was
assigned to "<IP_ADDRESS>". I'm not sure how digital ocean works, but if I
had to guess I would guess that this is a case of using the wrong network
interface somewhere.
So the next step is probably to figure out why kubernetes master didn't
use <IP_ADDRESS> as the name for the node.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/3185#issuecomment-68549065
.

Yes that is interesting observation, minions are listed with public ip, but when I initialized kubernetes, I used private ip of main server.
But there should be some kind of error for this somewhere if something is not connectable?
Ports on the main server as as follows:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601:36ff:fed0:7101  prefixlen 64  scopeid 0x20<link>
        ether 04:01:36:d0:71:01  txqueuelen 1000  (Ethernet)
        RX packets 1337473  bytes 894253322 (852.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1888190  bytes 176462231 (168.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601:36ff:fed0:7102  prefixlen 64  scopeid 0x20<link>
        ether 04:01:36:d0:71:02  txqueuelen 1000  (Ethernet)
        RX packets 8904322  bytes<PHONE_NUMBER> (963.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8874479  bytes<PHONE_NUMBER> (1.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::5cd2:5ff:fe4b:2750  prefixlen 64  scopeid 0x20<link>
        ether 5e:d2:05:4b:27:50  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 8395 overruns 0  carrier 0  collisions 0

minion-1:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601:36ff:fed0:9c01  prefixlen 64  scopeid 0x20<link>
        ether 04:01:36:d0:9c:01  txqueuelen 1000  (Ethernet)
        RX packets 1020530  bytes 239009204 (227.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 712361  bytes 91083822 (86.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601:36ff:fed0:9c02  prefixlen 64  scopeid 0x20<link>
        ether 04:01:36:d0:9c:02  txqueuelen 1000  (Ethernet)
        RX packets 4498047  bytes 812621386 (774.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4505024  bytes 514687649 (490.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::c442:7fff:feab:c820  prefixlen 64  scopeid 0x20<link>
        ether c6:42:7f:ab:c8:20  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 8393 overruns 0  carrier 0  collisions 0

minion 2:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601:36ff:fed0:9f01  prefixlen 64  scopeid 0x20<link>
        ether 04:01:36:d0:9f:01  txqueuelen 1000  (Ethernet)
        RX packets 1013594  bytes 238333400 (227.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 707651  bytes 82885225 (79.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::601:36ff:fed0:9f02  prefixlen 64  scopeid 0x20<link>
        ether 04:01:36:d0:9f:02  txqueuelen 1000  (Ethernet)
        RX packets 4393653  bytes 762215692 (726.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4405048  bytes 495863109 (472.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::9ce4:8eff:fecb:52e1  prefixlen 64  scopeid 0x20<link>
        ether 9e:e4:8e:cb:52:e1  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 8395 overruns 0  carrier 0  collisions 0

[root@monion1 ~]# /usr/bin/kubectl log webserver-controller-182tv -s <IP_ADDRESS>:8080
Pod "webserver-controller-182tv" does not exist
[root@monion1 ~]# /usr/bin/kubectl get pods -s <IP_ADDRESS>:8080
POD                          IP                  CONTAINER(S)        IMAGE(S)            HOST                LABELS                                          STATUS
db-controller-zwk1b                              db                  dbforweb            <IP_ADDRESS>/     name=db,selectorname=db                         Pending
webserver-controller-182tv                       apache-frontend     webwithdb           <IP_ADDRESS>/     name=webserver,selectorname=webserver,uses=db   Pending
[root@monion1 ~]# /usr/bin/kubectl log webserver-controller-182tv -s <IP_ADDRESS>:8080
Pod "webserver-controller-182tv" does not exist
[root@monion1 ~]# /usr/bin/kubectl describe pod webserver-controller-182tv -s <IP_ADDRESS>:8080
Name:                           webserver-controller-182tv
Image(s):                       webwithdb
Host:                           <IP_ADDRESS>/
Labels:                         name=webserver,selectorname=webserver,uses=db
Status:                         Pending
Replication Controllers:        webserver-controller (1/1 replicas created)
Events:
FirstSeen                       LastSeen                        Count   From            SubobjectPath   Reason          Message
Thu, 05 Mar 2015 15:33:23 +0800 Thu, 05 Mar 2015 15:33:23 +0800 1       {scheduler }                    scheduled       Successfully assigned webserver-controller-182tv to <IP_ADDRESS>

minons config >> /etc/kubernetes/kubelet

[root@monion1 ~]# vi /etc/kubernetes/kubelet

###
# kubernetes kubelet (minion) config

# The address for the info server to serve on (set to <IP_ADDRESS> or "" for all interfaces)
KUBELET_ADDRESS="--address=<IP_ADDRESS>"

# The port for the info server to serve on
KUBELET_PORT="--port=10250"

# You may leave this blank to use the actual hostname
KUBELET_HOSTNAME="--hostname_override=minion1"

# Add your own!
KUBELET_ARGS=""

We’re going through old support issues and asking everyone to direct your questions to stackoverflow.
We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.
We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on github is making it difficult for us to use issues to identify real bugs.
The Kubernetes team scans stackoverflow on a regular basis, and will try to ensure your questions don't go unanswered.


Declare lsu_error_pkt_dc4 before using it

lsu_error_pkt_dc4 is referenced before declaration. This seems to be acceptable for some EDA tools, but not for all of them.
Ref: https://github.com/SymbiFlow/sv-tests/issues/1348

CC @MikePopoloski


how to used nccl.reduce_sum

is there some example to use nccl.reduce_sum , as the doc say:
// Note: This op has no kernel implementation, but is replaced by
// _NcclReduceSend and _NcclReduceRecv during graph optimization stage.

so  how the nccl.reduce_sum works?

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 44 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


new getPiece function

Fixes the error at line 998 "getPieceId(object)" where an integer is sent to getPieceId.
Fixes the specific error described by https://steamcommunity.com/workshop/filedetails/discussion/2157495951/2993165479023391663/

Do you have steps to recreate the linked error?  Any way to validate this fix?

I didn't come up with a way to reproduce it 100%.
Tracing the code from line 1203 in the *.ttslua
"local targetPiece = getPiece(targetId)"
you can see how getPiece can't handle an id it has never seen before appropriately since it's a number.

I'm not following the basis of this change.  getPiece(object) is already designed to accept numbers.  That's the foundation of the neighbors/candidateMatches in onPieceDropped.


Allow custom ognl for XMLLanguageDriver

There is a default XMLLanguageDriver for xml, and actually it's ognl.
However, it's impossible to custom, as following method is hard coded:

OgnlCache.getValue
new ExpressionEvaluator()

In our cases, we'd like to solve problem like this:

analysis the dynamic sql in mybatis' xml
check unsafe $ usage

In this pull request, we allow custom OgnlCache.getValue and new ExpressionEvaluator(), so we can:

check $
custom test (like if / when)
custom foreach

In our cases, we use strategy like this (may change):

parse the condition try to make it true

use constant value in condition, dynamic adjust parameter value, try make first condition always true

always return one item for sql
Then we can get the sql, and analysis.

I do not fully understand your explanation, but the change is way too intrusive.
You might want to check out the discussion on #2453 .


ROX-27203: Ensure collector/scanner images exist during updates

Description
Ensure that GHA and Konflux built images are present when attempting to update the SCANNER_VERSION, COLLECTOR_VERSION files.
Had to bump COLLECTOR_VERSION to a successful Konflux build.
User-facing documentation

[x] CHANGELOG  update is not needed
[x] documentation PR  is not needed

Testing and quality

~[ ] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag~
[ ] CI results are inspected

Automated testing

~[ ] added unit tests~
~[ ] added e2e tests~
~[ ] added regression tests~
~[ ] added compatibility tests~
~[ ] modified existing tests~

How I validated my change

check-collector-images-exist
check-scanner-images-exist

checks on the build pipeline.

/retest


Delete obsolete alarms on AWS Cloudwatch

Alarms for
dev-group-registry-diskspace
and
hcommons-prod-group-registry
were deleted.


User Account Creation

Use Case Description: As a user, I can create an account on the system.

Should we have this? Probably


Add bypass url argument (uses NEUTRONCLIENT_BYPASS_URL environment va…

When dealing with multiple neutron server instances, this variable allows us to specify the neutron API to interact with (just like what bypass_url variable do in Nova).

Thank you for contributing to openstack/python-neutronclient!
openstack/python-neutronclient uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Monitor thread errors out with IndexError

I am trying to test out a few different software and it seems that for some of them the monitor thread errors out during intel RAPL calls. I have tested this on two different CPUs (1) Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz and 2) Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz.
experiment_impact_tracker.compute_tracker.ImpactTracker - ERROR - Encountered exception within power monitor thread!
ERROR:Encountered exception within power monitor thread!
experiment_impact_tracker.compute_tracker.ImpactTracker - ERROR -   File "../../experiment-impact-tracker/experiment_impact_tracker/compute_tracker.py", line 161, in launch_power_monitor
    _sample_and_log_power(log_dir, initial_info, logger=logger)
  File "../../experiment-impact-tracker/experiment_impact_tracker/compute_tracker.py", line 112, in _sample_and_log_power
    log_dir=log_dir,
  File "../../experiment-impact-tracker/experiment_impact_tracker/cpu/intel.py", line 88, in get_intel_power
    return get_rapl_power(pid_list, logger, **kwargs)
  File "../../experiment-impact-tracker/experiment_impact_tracker/cpu/intel.py", line 435, in get_rapl_power
    st2, st22, system_wide_pt2, pt2 = infos2[i]

ERROR:  File "../../experiment-impact-tracker/experiment_impact_tracker/compute_tracker.py", line 161, in launch_power_monitor
    _sample_and_log_power(log_dir, initial_info, logger=logger)
  File "../../experiment-impact-tracker/experiment_impact_tracker/compute_tracker.py", line 112, in _sample_and_log_power
    log_dir=log_dir,
  File "../../experiment-impact-tracker/experiment_impact_tracker/cpu/intel.py", line 88, in get_intel_power
    return get_rapl_power(pid_list, logger, **kwargs)
  File "../../experiment-impact-tracker/experiment_impact_tracker/cpu/intel.py", line 435, in get_rapl_power
    st2, st22, system_wide_pt2, pt2 = infos2[i]

Process Process-1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib/python3.6/multiprocessing/process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "../../experiment-impact-tracker/experiment_impact_tracker/utils.py", line 68, in process_func
    raise e
  File "../../experiment-impact-tracker/experiment_impact_tracker/utils.py", line 62, in process_func
    ret = func(q, *args, **kwargs)
  File "../../experiment-impact-tracker/experiment_impact_tracker/compute_tracker.py", line 161, in launch_power_monitor
    _sample_and_log_power(log_dir, initial_info, logger=logger)
  File "../../experiment-impact-tracker/experiment_impact_tracker/compute_tracker.py", line 112, in _sample_and_log_power
    log_dir=log_dir,
  File "../../experiment-impact-tracker/experiment_impact_tracker/cpu/intel.py", line 88, in get_intel_power
    return get_rapl_power(pid_list, logger, **kwargs)
  File "../../experiment-impact-tracker/experiment_impact_tracker/cpu/intel.py", line 435, in get_rapl_power
    st2, st22, system_wide_pt2, pt2 = infos2[i]
IndexError: list index out of range

Any suggestions? Thanks!

Apologies for the bug and thanks for fixing it. We've merged your fix in, but please re-open if it's still an issue.


Is this project available in any Public Repositories?

I'd like to add this project via Maven or SBT.  Is it available anywhere publicly?  I don't see it on Maven Central.

+1

I am working on publishing the artifacts to Maven Central. Will update this PR  again when the artifacts are uploaded

+1 Looking forward to start using it in my projects.

From now on, all spark-solr releases will be available on maven central.
The latest release 1.1.2 is on central (https://github.com/LucidWorks/spark-solr/releases/tag/1.1.2).

:+1:


⚠ Bofrost.be has degraded performance

In f4e85f9, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1093 ms

Resolved: Bofrost.be performance has improved in 9e2dc3a.


Node.Replace_with automatically encodes everything

For example,
I'm replacing following block

...

using Node.Replace_with which results in

inside HTMLParser.html. It's kinda critical because I'm using selectolax only for replacing html block and it's actually messes with the selectolax's ability to find specified block if another change to it is requried later

The current version of replace_with is limited to plain-text only. That's why your tags are encoded.
See #25 for progress on this issue.

The current version of replace_with is limited to plain-text only. That's why your tags are encoded.
See #25 for progress on this issue.

I see. Is there any way to circumvent it for now? Or everything will break if encoding is removed?

I see. Is there any way to circumvent it for now? Or everything will break if encoding is removed?

What do you mean by removing encoding? I don't think it's possible to circumvent it somehow, the Modest engine serializes all the tree when you change something. And it knows which nodes are plain-text.
If you want a quick fix, you can compile #25 and use node_replace_with.

I see. Is there any way to circumvent it for now? Or everything will break if encoding is removed?

What do you mean by removing encoding? I don't think it's possible to circumvent it somehow, the Modest engine serializes all the tree when you change something. And it knows which nodes are plain-text.
If you want a quick fix, you can compile #25 (python setup.py install) and use node_replace_with.

I'll try that, thanks

Resolved via #25


Dumps created by Procdump -r are not supported

Procdump -r creates a dump file without suspending the target process. Even for a very simple application, opening such a dump file with WinDbg + SOS works fine but fails with CLRMD. For example, ClrThread.StackTrace returns an empty collection of frames (whereas SOS produces a non-empty managed call stack).

We've moved CLR MD into its own GitHub repository. If this issue still applies, please file it there.
Sorry for the inconvenience but we never intended for this repo to contain the component itself.


build: Always check tgetent return code

Hey folks,
I finally found the root cause of the problem I experienced and reported in issue #1601 thanks to the extra information I got from #1634. I explicitly set the terminal library by passing --with-tlib=ncurses. Due to the logic in the configure script this caused the check to determine whether the tgetent returns zero or non-zero when given a non-existent terminal. The check is only run when $olibs != $LIBS which is not met when --with-tlib is passed, because in that case $LIBS is intentionally set to $olibs in oder to meet the $olibs = $LIBS condition of the subsequent check for the function tgetent. Therefore TGETENT_ZERO_ERR won't be defined even if the specified terminal library returns zero.
My best judgement is that the check should be run no matter if the terminal library was explicitly given or automatically selected. The proposed patched removes the condition around the check, so that it's always run

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1664      +/-   ##
==========================================
+ Coverage   74.87%    74.9%   +0.02%
==========================================
  Files          76       76
  Lines      124888   124888
==========================================
+ Hits        93516    93543      +27
+ Misses      31372    31345      -27

Impacted Files
Coverage Δ

src/undo.c
81.69% <0%> (-0.07%)
:arrow_down:

src/gui.c
45.56% <0%> (ø)
:arrow_up:

src/evalfunc.c
80.95% <0%> (+0.02%)
:arrow_up:

src/gui_gtk_x11.c
47.44% <0%> (+0.05%)
:arrow_up:

src/window.c
81.25% <0%> (+0.13%)
:arrow_up:

src/channel.c
83.92% <0%> (+0.13%)
:arrow_up:

src/os_unix.c
58.78% <0%> (+0.48%)
:arrow_up:

src/version.c
80.3% <0%> (+1.01%)
:arrow_up:

src/if_xcmdsrv.c
84.62% <0%> (+1.29%)
:arrow_up:

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 b7637c4...62df145. Read the comment docs.


px4io: on config error ask IO to reboot to bootloader

this allows us to update fw when core config settings have changed,
such as the actuators/servos change that happened recently

Thanks, applied!


is running rspec specs possible when using heroku-docker solution?

After using heroku-docker and the heroku/ruby Docker image (modified to use Heroku's ruby 2.0.0 buildpack) I was able to get an existing Rails 3.2 app running under Docker with relative ease, despite being a total Docker newbie, with the exception that nothing I tried so far allows me to prepare a Postgres test database, so I'm unable to run specs.
If there IS a way to run test specs I'd like to help document it.
docker-compose run web rake db:reset

works great, loads seed data, and the web app runs fine.
However, anything that tries to create or load or use the test database returns the error PG::ConnectionBad: FATAL:  role "root" does not exist for example the commands:
docker-compose run web rake db:test:prepare
docker-compose run web rake spec

If however I run the shell first via docker-compose run shell then bundle exec rake db:migrate runs fine but bundle exec rake db:test:prepare I get a different error than above when running the command on the web container using with docker-compose:
PG::ConnectionBad: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

(Incidentally the exact same error occurs when you run bundle exec rake db:test:prepare in the shell for the sample ruby-getting-started app used in the heroku blog article to explains heroku-docker.)
My database.yml is:
default: &default
  adapter: postgresql
  encoding: unicode
  pool: 5

development:
  <<: *default
  database: docker_mondo_dev

test:
  <<: *default
  database: docker_mondo_test

Did I miss a step in setup? Or is 'test' environment (like on Heroku itself) disabled?

I was able to get the test environment (mostly) working via a modified database.yml (added   username: postgres and host: herokuPostgresql) and by performing all test actions within the shell instead of as part of a docker-compose run web xxxxx command.
What does not work, oddly enough, is within Rspec 2 the fixture statement lilerally does nothing... so any spec relying upon a fixture statement will fail. Works perfectly in naative Mac OS X and under vagrant, but not under docker.

Thanks for following up. We're experimenting with this als. I'm going to add @hone to see if he has ideas for how to do this better.
Michael

The sole issue I still see is that the fixtures method is completely ignored when running under the heroku-docker setup... the quick acid test is to specify a nonsense filename and see if it throws an error.
It does not matter if fixtures is invoked directly in a spec via fixtures :something or in spec_helper.rb via config.global_fixtures [:something, :something else] ... either way, it works under native Mac OS X and Vagrant, but is completely ignored under Docker. (By ignored I means if you specify a nonsense filename, no error shows up, so it's not even trying).
Fixtures work under minitest / rails 4.2.3, based running rake test on the ruby getting started example documented
Fixtures also work if I add Rspec and a quick test spec to the Rails 4.2.3 ruby getting started example (with either the default ruby 2.2, or the same starting image with Ruby 2.0.0. that I created for my app, whcih is the heroku/ruby but modified to use your 2.0.0 buildpack)
But based on what I see in my app, there is clearly something broken under docker vs vagrant... same code, different results... if anyone has a clue where to look to see why the fixtures command would be ignored (when everything else seems to work fine) please LMK.

FWIW I've narrowed it down to the fixtures bug to being specific to Rails 3.?? / Rspec / Docker.
I created a virgin Rails 3.2.21 app, ruby 2.0.0, with rspec-rails 2.14 and also with rspec-rails 3.3.3 ... added a Widget model and a fixture ... the fixtures command is completely ignored under Docker as described above.
Then I migrated that app to Rails 4.2.4... the fixtures command works correctly under Docker (thorws an error is you give it an invalid filename, loads the model if you specify a valid yml file).
On one hand that;s pretty good news that it's reproducible for a virgin Rails 3.2.21 app but works for Rails 4.2.4.
On the other hand, I would expect it is nonetheless troubling that Docker breaks any code on the Heroku stack that runs fine on Vagrant and native Mac OS X.
My Docker image uses the heroku/ruby image, with the Dockerfile modified ONLY to use ruby 2.0.0..
My Vagrant image is based on lazygray/heroku-cedar-14... so similar if not identical underlying Ubuntu version


Plugin not working on 1.20.1

Using 1.20.1, Skript 2.6.4, latest skript-packet

Am I doing something wrong? I can't find anywhere to get support.

Did you have any console error ?
What is your ProtocolLib version ?

Did you have any console error ? What is your ProtocolLib version ?

Turns out those events I was using were just out of date syntax or something. When I finally got the right event going, it crashed my server, so I gave up using this plugin.


xarray.DataArray.to_netcdf - file not found but file in directory

When using xarray.to_netcdf I get for some xarray.DataArrays the following error:
OSError: [Errno -101] NetCDF: HDF error:
or
RuntimeError: NetCDF: file not found
MCVE Code Sample

# Your code here
import xarray as xr
from datetime import datetime

# datetime object containing current date and time
now = datetime.now()
# dd/mm/YY H:M:S
date = now.strftime("%Y%m%d")
time = now.strftime('%H')
print("date and time =", date, time)

ini_time = '06'

#  Open the netCDF file containing the input data.
fnx = xr.open_dataset('https://thredds.met.no/thredds/dodsC/mepslatest/meps_det_2_5km_%sT%sZ.ncml' %(date, ini_time),
                      #decode_times  = True, use_cftime = True
                     )

# write to file 'meps_out.nc'
fnx.forecast_reference_time.to_netcdf(path = 'meps_out.nc', mode = 'w', format = 'NETCDF4')
fnx.p0.to_netcdf(path = 'meps_out.nc', mode = 'a', format = 'NETCDF4')
fnx.ap.to_netcdf(path = 'meps_out.nc', mode = 'a', format = 'NETCDF4')
fnx.b.to_netcdf(path = 'meps_out.nc', mode = 'a', format = 'NETCDF4')
fnx.projection_lambert.to_netcdf(path = 'meps_out.nc', mode = 'a', format = 'NETCDF4')
# variables with dimension: (time: 48, height0: 1, y: 1069, x: 949)
fnx.ozone_profile_c.isel(time = slice(0,48)).to_netcdf(path = 'meps_out.nc', mode = 'a', format = 'NETCDF4')
# variables with dimension: (time: 48, hybrid: 65, y: 1069, x: 949)
# here is where the error occurs
fnx.specific_humidity_ml.isel(time = slice(0,48)).to_netcdf(path = 'meps_out.nc', mode = 'a', format='NETCDF4')

Expected Output
How to get all xarray.DataArrays to a netcdf file.
Problem Description

Save all variables from an OPeNDAP thredds file with shorter time (0-48h, instead of 0-67h). Once I want to save a DataArray with a hybrid coordinate (dim = 65) I get the error:
RuntimeError: NetCDF: file not found
even though I already appending to the file.
DaraArrays are appended to the file if they don't have the hybrid coordinate.
 Your upstream data is broken for the variable specific_humidity_ml.
When you invoke to_netcdf(), the remote resources actually holding the variable(s) are requested for the first time, and the server is responding 404.
Just load the variable into memory:
>>> fnx.specific_humidity_ml.compute()
RuntimeError: NetCDF: file not found

Please reopen if you have reason to believe the issue is in the xarray pydap driver and not in the source data.
P.S. all your lines invoking to_netcdf could be replaced with a single command:
fnx[
    [
        "forecast_reference_time",
        "p0",
        "ap",
        "b",
        "projection_lambert",
        "ozone_profile_c",
        "specific_humidity_ml",
    ]
].isel(time = slice(0,48)).to_netcdf('meps_out.nc', 'w', format = 'NETCDF4')


add info about your activity

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don't have working experience tell about your pet-projects or student projects. Don't be shy :)

done


Release 2017-10-26

Coverage decreased (-0.8%) to 85.238% when pulling 43ecda45f9e22b45f042f4e6625804ac82045933 on develop into 0a74747565a2dff289543728df3f9c44c3e0454d on master.

Coverage decreased (-0.8%) to 85.238% when pulling 43ecda45f9e22b45f042f4e6625804ac82045933 on develop into 0a74747565a2dff289543728df3f9c44c3e0454d on master.

Coverage decreased (-0.8%) to 85.238% when pulling 43ecda45f9e22b45f042f4e6625804ac82045933 on develop into 0a74747565a2dff289543728df3f9c44c3e0454d on master.


Show unicode user names in viewer

Unicode characters currently show as ?.
a potential partial fix is to set the console to utf8 and maybe it is also due to a incompatible font.

PR #177 has partially resolved the issue. More characters are now shown in the console but not all are shown correct:

https://twitter.com/snowded

ᗪᗩᐯᕮ SᑎOᗯᗪᕮᑎ

I've tried the available fonts Consoles, Lucida Console and Courier New. These fonts do not show this name correctly in the console.

https://twitter.com/debasishg : Debasish (দেবাশিস্) Ghosh


Example Issue

This issue will serve as an example issue for the demonstration.
Issues are suggested improvements, tasks or questions related to the repository. Issues can be created by anyone (for public repositories), and are moderated by repository collaborators. Each issue contains its own discussion thread. You can also categorize an issue with labels and assign it to someone.
From the GitHub Guides Mastering Issues, a typical issue looks like:

A title and description describe what the issue is all about.
Color-coded labels help you categorize and filter your issues (just like labels in email).
 This is useful for associating issues with specific features or project phases (e.g. Weekly Sprint 9/5-9/16 or Shipping 1.0).
One assignee is responsible for working on the issue at any given time.
Comments allow anyone with access to the repository to provide feedback.

Issues can include checklists:

[x] Fix bug
[x] Add feature
[ ] Write documentation

When reporting bugs or errors for software projects, it is often helpful to include a helpful snippet of code:
print("Hello world!")
Hello world!

You can also assign your issues to Projects and visualise them on your project kanban board.

I am now working on this issue in Pull Request #36 🎉


Map pins are only displayed on the first run of the conversation

After going through the conversation once and mapping events subsequent requests for events do not display pins.

Fixed in PR #35


Cant run the software

When following the README instructions I get :
build_signature_one_phase.go:4:5: "./ppt_filter" is relative, but relative import paths are not supported in module mode
I tried to change it in the source to absolute path, but I then get:
build_signature_one_phase.go:4:5: "/home/AR1/Documents/reviews/23PhaBox/MetaBIDx-master/src/build_index/ppt_filter" is not a package path; see 'go help packages'
Any clue?

Hi,
Thanks for contacting us. Are you running the software on MacOS? Currently we only support running on Linux. Sorry for missing that information in the instruction, I'll update the README for clarification.
In order to avoid similar issue, we released Linux executables for build_index and query which can be downloaded and run directly.


Feat/add music year

Description Automate adding of a music year to each PR
Music year: 1975
To test: the above string will contain a music year rather than a placeholder string.

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


Write Implementation section of DG

Explain in the Implementation section of the DG how the following is implemented:

Handling of compulsory vs optional Person attributes
CommandParser structure

Moving on from this cos honestly too lazy to do it and I gotta do other mods. Thanks


[Mod Support Request] MOD NAME HERE

Link to the mod page
https://modrinth.com/resourcepack/no-break-particles/version/1.19.4a
Description
When using the texture pack my shulker boxes are invisible
What Minecraft Version would you like to see supported?
1.19

Hello thanks for making this issue!
When I use 1.19.2a from Modrinth, and I place down Shulker Boxes, they are all visible.
Could you test if this is still the case if you're only using my pack (also make sure its above the rest of the packs. And if it is, give me some steps to replicate the issue.
For Reference!


InfluxDB inserts data very slowly.

In InfluxDB version 1.8, I am inserting two types of data: one is detailed data, and the other is aggregated data computed from the detailed data. The aggregated data includes new fields such as count, sum, avg, max, and min, all of which are of type float. When using the same code, inserting detailed data is very fast, achieving approximately 200k/s. However, when inserting aggregated data, I frequently encounter statusCode=504 errors, and the insertion speed struggles to reach even 1k/s. I would like to know where I can log the write operations or how I should debug this issue.

There are two things you should look at: what error message is returned with the 504 errors, if any, and the server logs for more details on the write failures.  Turning your [log level](Structured logging) up to debug will provide more information.

There are two things you should look at: what error message is returned with the 504 errors, if any, and the server logs for more details on the write failures. Turning your [log level](Structured logging) up to debug will provide more information.

I am currently using Spark's Kafka backpressure mechanism, which has effectively alleviated the issue. However, I still haven't identified the root cause of the problem. I am attempting to investigate further by leveraging HTTP-related log configurations in InfluxDB. Thank you for your response. If I manage to identify the root cause later, I will share it. Thank you once again!

There are two things you should look at: what error message is returned with the 504 errors, if any, and the server logs for more details on the write failures. Turning your [log level](Structured logging) up to debug will provide more information.

I now know what the root cause is. When I use Spark to consume multiple Kafka topics, Spark treats the data from multiple topics as the same type of data for processing. However, each of my topics corresponds to a different database in InfluxDB. As a result, I was frequently creating batchPoint objects for insert operations. After identifying this issue, I modified my approach to consume the Spark topics sequentially. Following this change, my program started working perfectly


Table 26 (comparing results with last year's base model) not working

Yesterday it would just show an error but the .tex would still build. Now it's breaking as it won't put the 2023 and 2022 years on the first line. In console when just running the function, it says:
New names:
• `Base model` -> `Base model...2`
• `Base model` -> `Base model...3`
New names:
• `Base model...2` -> `Base model...3`
• `Base model...3` -> `Base model...4`
\begin{table}[H]
\centering
\caption{Select parameters, derived quantities, and reference point posterior median estimates for the (2023) base model compared to the previous assessment's (2022) base model.}
\label{tab:main-parameter-estimates}
\begingroup\fontsize{10}{11}\selectfont
\begin{tabular}{lcc}
  \hline
 & \mlc{Base\\model} & \mlc{Base\\model} \\
  \hline
 &  &  \\

The bullet point errors are strange, and you can see the third line from the bottom doesn't have the years, when they got inserted last year.
Chris - I put in last_yr_base_model_name in fa05a5b2, as it had disappeared from last year it seems. Later tables also breaking at the \mlc stage, but they were just letting me skip over them yesterday.  :puzzled.

Actually I think know what it is....

Above commit wasn't meant to close this (I thought I worded the message so it wouldn't automatically close). Builds for now.

Just missing the years being automatically included in the column headers.

Turns out that switching the bold headings on does break the table (I switched them back off in 3e1bf400). Not quite sure why, but not too important right now.

Also, the Dirichlet-multinomial parameters are missing from the first column (the 2023 model), to do with the names changing.

Above comment also relevant to the final three main tables (Tables 33-35).

I also think (if we have time) that adding the 2020 recruitment (millions) after the 2016 row in the sensitivity tables will be useful.

I think I got most of this working.  However, the DM parameters still don't show up for 2022 base model in the parameter estimate comparison table.  It looks like it was called the same thing last year.  Leaving this open for now.

All are correct, last year ones match with the table from last year, I added the fix to make DM params appear for both years.
I noticed that the 2023 relative biomass row is in the wrong subheading as it was added this year, I think it should be in derived quantities:

Agree it should be moved if possible. We're missing the '2023' in the first column heading, but it's kind of implied in the caption so probably fine.

The above screenshot correctly has two dashes in the 2022 base model column, but the latest version has some numbers (which is incorrect - they were correctly dashes in the submitted version):

This fix also correctly put dashes in Table 36 for the retrospective calcs - nice.


Valid highlights don't account for ng-touched

Short description of the problem:
Inputs in an edit form shouldn't show any highlights, whether valid or invalid, until touched by the user. Currently, the valid highlight shows regardless, while the invalid highlight waits for ng-touched to be applied.
You don't notice this until pre-populating inputs with valid data from a server, or what have you. Perhaps I'm mistaken and this is the expected "native" behavior, but opening a form and seeing a bunch of green everywhere seems odd.
PR upcoming.
What behavior are you expecting?
I expect inputs to wait to be touched for valid values as they do for invalid values.
Steps to reproduce:

Use FormBuilder or ngModel to give an input a valid value before a user uses a form.
Notice green/valid highlights before touching input.

Which Ionic Version? 2.x
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.3.1
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic CLI Version: 2.1.1
Ionic App Lib Version: 2.1.1
ios-deploy version: 1.9.0
ios-sim version: 5.0.8
OS: Mac OS X Sierra
Node Version: v6.6.0
Xcode version: Xcode 8.0 Build version 8A218a

I think this needs to be more customizable in general. We assume the user only wants the invalid to show when touched, but sometimes they may want it to show on submit. I was thinking we could add some variables that control when to add the valid/invalid highlights based on the ng-* classes. Thoughts?

When submitting a form, you can always markAsTouched() the controls that need to show as invalid, the idea being that submitting is equivalent to touching the whole form.
You could go overboard with all the variations of valid, touched, & dirty. This fix at least brings valid & invalid highlights inline so they act the same way.


georgeda: Implement the header

@aefox or @lau32 please review:)

there's some repetitiveness in the smaller components, but not a big thing, could be cleaned up easily. nice job! 👍 but I'm closing this as we'll be approaching the next workshop differently


CQ-4301935 Add tests for PortalLister

@review @rismehta @sakshi-arora1

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

Merging this and raising PR in main repo to check with code-cov


Benchmarking

I just added a benchmark script at https://github.com/JuliaIO/PNG.jl/blob/master/benchmarking/benchmark.jl
Looks like QuartzImageIO >> PNG > ImageMagick overall, but PNG is fastest to load
All of this is before @drvi's https://github.com/ianshmean/ImageIO.jl/pull/3 which looks like it will improve things 👍🏻
Small image
[ Info: Testing with rand(RGB{N0f8}, 244, 244) image -----------------------------

[ Info: Testing FileIO with ImageMagick (dedicated environment, new instance)
Time to first save (including save): 2.336 seconds
Save @btime:  27.209 ms (3562 allocations: 710.64 KiB)
Load @btime:  5.420 ms (3722 allocations: 717.97 KiB)

[ Info: Testing FileIO with QuartzImageIO (dedicated environment, new instance)
Time to first save (including save): 2.445 seconds
Save @btime:  8.773 ms (1837 allocations: 794.13 KiB)
Load @btime:  3.477 ms (2062 allocations: 574.75 KiB)

[ Info: Testing FileIO with PNG (dedicated environment, new instance)
Time to first save (including save): 1.776 seconds
Save @btime:  20.581 ms (279 allocations: 370.69 KiB)
Load @btime:  2.569 ms (184 allocations: 183.33 KiB)

Large image
[ Info: Testing with rand(RGB{N0f8}, 20000, 4000) image -----------------------------

[ Info: Testing FileIO with ImageMagick (dedicated environment, new instance)
Time to first save (including save): 32.806 seconds
Save @btime:  30.127 s (3562 allocations: 686.83 MiB)
Load @btime:  4.962 s (3729 allocations: 686.84 MiB)

[ Info: Testing FileIO with QuartzImageIO (dedicated environment, new instance)
Time to first save (including save): 14.143 seconds
Save @btime:  11.721 s (1837 allocations: 915.62 MiB)
Load @btime:  3.934 s (2064 allocations: 610.46 MiB)

[ Info: Testing FileIO with PNG (dedicated environment, new instance)
Time to first save (including save): 30.107 seconds
Save @btime:  28.491 s (20035 allocations: 460.82 MiB)
Load @btime:  4.107 s (186 allocations: 228.89 MiB)

As expected, we now win with #2 merged
[ Info: Testing with rand(RGB{N0f8}, 244, 244) image -----------------------------
[ Info: Testing FileIO with ImageMagick (dedicated environment, new instance)
Time to first save (including save): 2.303 seconds
Save @btime:  27.416 ms (3562 allocations: 710.64 KiB)
Load @btime:  5.335 ms (3722 allocations: 717.97 KiB)

[ Info: Testing FileIO with QuartzImageIO (dedicated environment, new instance)
Time to first save (including save): 2.37 seconds
Save @btime:  8.847 ms (1837 allocations: 794.13 KiB)
Load @btime:  3.456 ms (2062 allocations: 574.75 KiB)

[ Info: Testing FileIO with PNGFiles (dedicated environment, new instance)
Time to first save (including save): 2.05 seconds
Save @btime:  4.608 ms (46 allocations: 178.64 KiB)
Load @btime:  3.145 ms (182 allocations: 359.59 KiB)

[ Info: Testing with rand(RGB{N0f8}, 20000, 4000) image -----------------------------
[ Info: Testing FileIO with ImageMagick (dedicated environment, new instance)
Time to first save (including save): 33.791 seconds
Save @btime:  29.370 s (3562 allocations: 686.83 MiB)
Load @btime:  5.350 s (3729 allocations: 686.84 MiB)

[ Info: Testing FileIO with QuartzImageIO (dedicated environment, new instance)
Time to first save (including save): 15.481 seconds
Save @btime:  13.516 s (1837 allocations: 915.62 MiB)
Load @btime:  4.120 s (2064 allocations: 610.46 MiB)

[ Info: Testing FileIO with PNGFiles (dedicated environment, new instance)
Time to first save (including save): 9.059 seconds
Save @btime:  6.418 s (49 allocations: 229.04 MiB)
Load @btime:  4.638 s (185 allocations: 457.92 MiB)

Wondering if ImageMagick and PNGFiles numbers are improving after Zlib_jll got -O3 flag in https://github.com/JuliaPackaging/Yggdrasil/pull/1051.


Unable to connect with POSTGRES_USER even though entrypoint script shown as run

I am running the postgres:11-alpine image through kubernetes run from minikube. I am unable to connect to postgres using my POSTGRES_USER value.
Below are my mainfests

deployment manifest

apiVersion: apps/v1
kind: Deployment
metadata:
  name: db-deployment
  labels:
    tier: backend
    app: db
spec:
  replicas: 1
  selector:
    matchLabels:
      tier: backend
      app: db
  template:
    metadata:
      labels:
        tier: backend
        app: db
    spec:
      containers:
        - name: db
          image: postgres:11-alpine
          ports:
            - containerPort: 5432
          volumeMounts:
            - name: data
              mountPath: /var/lib/postgresql/data/pgdata
          env:
            - name: PGDATA
              value: /var/lib/postgresql/data/pgdata
            - name: POSTGRES_USER
              valueFrom:
                secretKeyRef:
                  name: world-of-chatting-secrets
                  key: POSTGRES_USER
            - name: POSTGRES_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: world-of-chatting-secrets
                  key: POSTGRES_PASSWORD
      volumes:
        - name: data
          persistentVolumeClaim:
            claimName: postgresql-pv-claim

persistenvolueclaim manifest

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: postgresql-pv-claim
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi

description of persistent volume (dynamically provisioned by minikube)

Name:            pvc-d47d87a5-e169-4c3c-a563-8967ad75759c
Labels:          <none>
Annotations:     hostPathProvisionerIdentity: 6ae86055-fb12-11e9-934c-080027483f85
                 pv.kubernetes.io/provisioned-by: k8s.io/minikube-hostpath
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    standard
Status:          Bound
Claim:           default/postgresql-pv-claim
Reclaim Policy:  Delete
Access Modes:    RWO
VolumeMode:      Filesystem
Capacity:        2Gi
Node Affinity:   <none>
Message:
Source:
    Type:          HostPath (bare host directory volume)
    Path:          /tmp/hostpath-provisioner/pvc-d47d87a5-e169-4c3c-a563-8967ad75759c
    HostPathType:
Events:            <none>

When I look at the logs for the pod, it seems to indicate the entrypoint script was run and user created
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... UTC
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
sh: locale: not found
2019-10-31 03:39:15.086 UTC [26] WARNING:  no usable system locales were found
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start

waiting for server to start....2019-10-31 03:39:16.501 UTC [30] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-10-31 03:39:16.519 UTC [31] LOG:  database system was shut down at 2019-10-31 03:39:16 UTC
2019-10-31 03:39:16.522 UTC [30] LOG:  database system is ready to accept connections
 done
server started
CREATE DATABASE

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

2019-10-31 03:39:16.917 UTC [30] LOG:  received fast shutdown request
waiting for server to shut down....2019-10-31 03:39:16.919 UTC [30] LOG:  aborting any active transactions
2019-10-31 03:39:16.920 UTC [30] LOG:  background worker "logical replication launcher" (PID 37) exited with exit code 1
2019-10-31 03:39:16.965 UTC [32] LOG:  shutting down
2019-10-31 03:39:16.977 UTC [30] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2019-10-31 03:39:17.033 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2019-10-31 03:39:17.033 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2019-10-31 03:39:17.037 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-10-31 03:39:17.058 UTC [41] LOG:  database system was shut down at 2019-10-31 03:39:16 UTC
2019-10-31 03:39:17.062 UTC [1] LOG:  database system is ready to accept connections

However, when I ssh into the pod and run "psql -U [$POSTGRES_USER value]," it fails so I am confused by what I am seeing in the logging. I have deleted the container, the postgres image, the persistent volume, and redeploying the pod but still unable to connect.

Is your volume empty when you mount it, does your container show the proper environment variables?

@wglambert

I printed out the container environment variables and yep it is showing the correct values
I'm still getting down my understanding of volumes so hopefully I answer this correctly. When you ask about the volume being empty, you are referring to the persistent volume right? And more specifically you are referring to this part right?

Source:
    Type:          HostPath (bare host directory volume)
    Path:          /tmp/hostpath-provisioner/pvc-d47d87a5-e169-4c3c-a563-8967ad75759c
    HostPathType:

That path,  /tmp/hostpath-provisioner/pvc-d47d87a5-e169-4c3c-a563-8967ad75759c (which is created by minikube), is empty. Since it is empty, I should be clear right? Wouldn't the entrypoint script not run if it wasn't empty?

Yeah it looks like it should have ran fine
server started
CREATE DATABASE

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

https://github.com/docker-library/postgres/blob/a8613f4cda3e932245f09c4d0f6733462b14b582/docker-entrypoint.sh#L136-L141
If you log in as root can you get a list of users, perhaps the user is created but the password has an odd formatting that you're unable to enter it in a valid way
I think Postgres' list users is \du

@wglambert i can't even log in as root, or even with username = postgres (maybe that's what you meant). Definitely at quite a loss here.

@wglambert seems like it is actually an issue with the deployment yaml. When I put a value for POSTGRES_USER directly in the yaml, i.e.
            - name: POSTGRES_USER
              value: ***

it works. It just doesn't work when I use a secret. Very strange. Will have to investigate

@wglambert sorry to keep spamming you but figured it out. The following was my issue

That's super annoying. Thanks for validating I was on the right track. Closing this now


handling of already escaped í (as in García) seems broken

There seems to be a problem with biber when it encounters an already escaped unicode compound char like in Garc{\'{\i}}a in the .bib file. This seems to generate a compound Garcı´a in the .bbl file, leading to an error like Package inputenc Error: Unicode char ́ (U+301) [\end]. If i instead use backend=bibtex (which i'd rather not), it works as expected...
biber version: 2.2, on a current mactex
Below is a minimal test-case:
Bibliography.lib:
@inproceedings{Mendes2011DBpediaSpotlight,
address = {Graz, Austria},
author = {Mendes, Pablo N. and Jakob, Max and Garc{\'{\i}}a-Silva, Andr{\'{e}}s and Bizer, Christian},
booktitle = {Proc. of the I-SEMANTICS},
isbn = {9781450306218},
keywords = {dbpedia,linked data,named entity,text annotation},
publisher = {ACM},
title = {{DBpedia Spotlight: Shedding Light on the Web of Documents}},
year = {2011}
}

foo.tex:
\documentclass{article}
\usepackage[utf8]{inputenc}
\PassOptionsToPackage{%
    backend=biber,%
    % backend=bibtex8,bibencoding=utf8,%
    maxbibnames=5, % default: 3
    }{biblatex}
    \usepackage{biblatex}
\addbibresource{Bibliography.bib}
\begin{document}
\cite{Mendes2011DBpediaSpotlight}
\printbibliography
\end{document}

Removing the \usepackage[utf8]{inputenc} makes the problem disappear. Alternatively switching to backend=bibtex,bibencoding=ascii or backend=bibtex8 as in the comment above also seems to work for this case, but i couldn't get it running with my full library.
Replacing all occurrences of {\'{\i}} with {\'{i}} in the .bib file it seems to work with biber. Sadly my library.bib is auto-generated by Mendeley so this doesn't seem like a viable option either :(
Any idea how this could be fixed?

This is a common issue with utf8 and pdflatex. Usually you should use the biber option --output-safechars with utf8 and pdflatex since inputenc doesn't support a full set of unicode encoded chars. It's best to ask this on tex.stackexchange.com as you will get immediate help there.

On TeX.SX there is Input encoding error after upgrading from Biber 1.9 to Biber 2.1. There is also https://github.com/plk/biber/issues/65

uhm, i'm just running this with latexmk --pdf foo.tex... maybe if this "breaks by default", it's a bad default?

Joseph Wright describes the issue on stack exchange How to put an acute on an i using Biber: issues with "'{\i}".  Can we reopen this to fix the conversion to an appropriate single codepoint í so that people don't keep running into this issue and wasting hours trying to find the non-obvious and non-default fix of adding --output-safechars?
Perhaps at a minimum, the documentation could include an appropriate hint in the Unicode section, which currently offers only the following which, to my eyes, does not provide any useful information about these types of issues:

Biber uses NFD UTF-8 internally. All data is converted to NFD UTF-8 when read. If UTF-8 output is requested (to .bbl for example), the UTF-8 will always be NFC.

See also the following small collection of related issues on Stack Exchange (there are many more):

How to put an acute on an i using Biber: issues with "'{\i}"
Unicode -(U+301) error in biblatex, but not in main text: {'{\i}}
Input encoding error after upgrading from Biber 1.9 to Biber 2.1
https://sourceforge.net/p/bibdesk/bugs/1523/: BibDesk causes problems by doing the right thing and converting í to {\'\i} so that it also works with BibTeX.

Alright, I've given in and make this a special case in the 2.19 development version on SF. The "combining diacritic" output is perfectly valid UTF-8 both NFD and NFC but it should now be a single grapheme on output as it's seemingly a common issue.


Document federation use cases and examples

I was looking for some guidance around federation best practices, but couldn't find some immediately. It'd be great to add a section for that.
In our concrete case, we want to scrape some metrics from almost all our prometheus servers, so we list them all right now. The critical servers use a HA setup where we run two identical servers scraping the same targets. Our current federation config management configures them so that a service address is used, randomly pointing to one or the other node of a HA pair. This doesn't feel right to me.
@brian-brazil You mentioned some best practices here. Would it be better to always scrape all servers? What labeleling has emerged as best practice for this scenario?

Which makes me think we might want to have access to all the SD mechanisms in federation, too. After all, if Prometheus monitors services managed by some kind of orchestration system, the odds are that the Prometheus servers are managed by the same system, and thus other Prometheus servers are discoverable via the same SD mechanism as targets.

@beorn7 That's currently the case, no? Since federation targets are just normal targets with some extra settings.

Yes, obviously. Pardon my stupidity.
So I guess the best way to federate from HA pairs is to scrape each of them but then also add labels so that they don't feed into the same series (because of honor_labels).
What do you (all) think?

external_labels covers that use case already, you should probably only scrape one of them though.

But how do you scrape the one that is up? Or in other words: I Want to scrape the same server of a pair normally, but if that one goes down, I want to fall back to the other...

Global prometheus servers are inherently unreliable due to going over the WAN.
Attempting to work with two HA prometheus servers each with their own view of the world (which is only in theory identical) is going to involve substantial amounts of work for the user to try and eliminate all the potential weirdness. Better to keep it simple and accept a bit of availability loss for the brief time one a prometheus is down. The other prometheus in the pair will still be firing alerts, which is what is really important.

Unless you have alerts for the global level...
Scraping both with some extra label seems to me the sanest thing.

Alerts at a global level need to allow for additional races, so tend to have high thresholds to allow for this. As long as you get the server back up relatively quickly it'll likely be fine.

Scraping both with some extra label seems to me the sanest thing.

That's what external_labels is for.

So if you have global alerts, you needed to wake somebody up if the "wrong" server in a HA pair goes down. If you have many of those pairs, those incidents will happen relatively frequently. So I'd say that's a bad strategy for your alerting setup. It arguably defeats the purpose of an HA setup.
So I'd go for recommending federating from both servers with an extra label in the docs.

So I'd say that's a bad strategy for your alerting setup. It arguably defeats the purpose of an HA setup.

The purpose of a HA setup is that both send alerts if one fail, which it provides.
The purpose of a HA setup is not to provide a unified uninterrupted view of the services being monitored. This is fundamentally not possible.

So if you have global alerts, you needed to wake somebody up if the "wrong" server in a HA pair goes down.

Global alerts are fundamentally unreliable. If it's that important an alert, it probably shouldn't be global.

Symptom-based monitoring requires global alerts under circumstances. Let's say I want to get alerted if my global capacity reserve doesn't fulfill the "n+1" criterion anymore. In that case, I want to get woken up. I don't want to get woken up because somewhere in the world, one of my two local Prometheus servers is down.

Thanks, this looks like a lot of great material for a "best practices" section already. Right now, the federation servers I set up only scrape aggregation results which don't have instance labels, so I get the differentiation for free as new instance labels get attached.
It might be the responsibility of sd to deliver one healthy, ideally stable target.

It might be the responsibility of sd to deliver one healthy, ideally stable target.

That's not the role of SD, we want all targets so you can monitor them when they're not fully healthy.

What about a relabeling function that somehow allows to "pick one" (by a
specified label combination), and does so consistently between scrapes? like
- action: keep_one
  source_label: __address__

(slightly beyond the scope of documenting what is possible though)

I don't think that belongs in SD, and that it would be greatly abused leading to both user problems and additional support load. Even for this use we'd have problems along those lines.

http://www.robustperception.io/monitoring-without-consensus/ has some general background here, particularly the Perfection section.

I was surprised that a timeseries federated from two replicated prometheus servers failed to merge into a single timeseries at the global level, and I found this thread which suggests that they shouldn't be allowed to merge. Why exactly is that a bad idea?
I understand that a point cannot be added to a timeseries if there's already a value with a newer timestamp, and that it would be very common for such out-of-order ingestions to be rejected. But for HA purposes, what's wrong with that? If I'm merging dc:requests:rate5m from two dc-level monitors with similar configurations, I'm happy to get stream 1, stream 2, or a merge of both streams; so long as the result has consistent labels. From the comments above, it appears that there is a firm design decision not to allow this. Why not?
Let's suppose that I'm resigned to having distinct timeseries for the HA pair. I could apply external labels such as ha=left, ha=right, but that presents obvious practical problems when querying for them. One way out is to introduce a new aggregation level below dc:, called dcha:. Each dc-level prometheus could calculate its dcha: variables and export them with ha external labels. Each global-level prometheus would combine them into a single dc: variable without the ha label. Apart from being ugly, this presents another problem: how do you express a query for most_recent(dcha:requests:rate5m) without (ha)? I could use avg(...) without (ha), but that's extra nasty.
Also, how do I get rid of the instance labels that federation attaches to all variables? They don't belong there, and relabel_config doesn't want to remove them.
I'm trying to find a mechanism which will allow a single prometheus server to be taken out of service temporarily without needing a manual reconfiguration of the global prometheus. Is this a thing that federation permits?

Why exactly is that a bad idea?

You're presuming that the two Prometheus servers are seeing identical data and making identical calculations from that data.

Each global-level prometheus would combine them into a single dc: variable without the ha label.

This is the general approach to take if you want to do that, and the same used for any clustering-like system where not all targets necessarily agree on what the state of the world is (which is to say all clustering-like systems).

From the comments above, it appears that there is a firm design decision not to allow this. Why not?

It's impossible for us to do this correctly. We take the approach of presenting the data as it is, and leaving it to the user to make whichever tradeoffs they want if they want to do a merge.

Also, how do I get rid of the instance labels that federation attaches to all variables?

honor_labels: true

I'm trying to find a mechanism which will allow a single prometheus server to be taken out of service temporarily without needing a manual reconfiguration of the global prometheus. Is this a thing that federation permits?

Not per-se. You should try to ensure you gracefully handle any one Prometheus being down.

https://prometheus.io/docs/operating/federation/ seems to cover this already.


build_library: set correct SELinux contexts in final images

build_packages: use setfiles to label the system
setfiles can be used to directly set the SELinux labels on a root filesystem based on the values in file_contexts.

$ tar --selinux --xattrs -xf $(readlink -f docker\:20.10.torcx.tgz)
$ find -context "*unlabeled*"
$

Closed in favor of #666 (imp)

Can you rather rebase? My PR only did the labeling for /etc which was what I needed to prevent overlay upcopies but most of your PR is still relevant, to fix any /usr labels and also produce correct torcx labels.