Connection leak

What kind an issue is this?

Bug report.

Issue description
I have a long running job on spark that makes quite a lot of reading requests to ES.
There is definitely a connection leak related to HTTP client, because
lsof -p %sparkExecutorPID% | grep TCP | grep 9200 | sort -t '>' -k2 | wc -l

shows over 1000 connections after 1 day of work. However there is only one esRDD is used at any moment of time.
Eventually this leads to too many open files error.
Log (for es-hadoop 6.2.1):
2018-10-29 03:28:13 INFO HttpMethodDirector: I/O exception (java.net.SocketException) caught when processing request: Too many open files
2018-10-29 03:28:13 INFO HttpMethodDirector: Retrying request

Version Info
OS:         :  Debian 8
JVM         :  java8 oracle
Spark:  2.3.1
ES-Hadoop   :  tried elasticsearch-spark-20 versions 5.6.10 and 6.2.1.
ES          :  5.6.10

This is a tricky one. Obviously we should be caching and reusing connections to ES as much as possible. We enable a connection pooling strategy on Spark Streaming jobs, but it uses entirely internal settings that are not documented for a reason: the way we do pooling is weird in that we are pooling entire rest clients instead of pooling connections - mostly because of how much state we have bound to a particular connection right now. I am working through some stuff to address this problem and more in other issues (#801 and #1184) but the progress is slow going.
As a super hacky workaround, you could try enabling the internal streaming job pooling for your batch rdd by setting es.internal.transport.pooling.key -> UUID.randomUUID().toString in your conf settings. It's important that every RDD you launch with that setting has a unique pooling key or else RDD's running in the same app instance might pollute each other's connection pools with clients that are misconfigured, so make sure that the value is not shared across RDD's.

Thank you for your response.
I've tried to add this setting in my MWE and connection count started to grow even faster. It eventually hit around ~3000 connections and the app is crashed with connection error.
Then I tried to make one fixed key for all rdds
   val uuid = UUID.randomUUID().toString
  ...
  "es.internal.transport.pooling.key" -> uuid

and that didn't help either :(

is there any progress on this issue?


Add same section for SP8

@joostverhoog I saw in the Jira issue that it needs to also be updated for SP8 so adding it here.


Specify Content-type for viewable Images?

Is it possible to specify the Content-type metadata for images? Currently, clicking the Object URL downloads the image instead of displaying it in the browser. By default, it seems to upload to the S3 bucket as a "binary/octet-stream" instead of "image/jpg".

@Serdnad @meghead I faced this same problem, so I created #13 to fix the issue.


Add fileName, latitude, longitude and timestamp response fields for iOS

This PR adds response fields for fileName, latitude, longitude and timestamp values on iOS. There are some caveats about when these fields are available in the response:

fileName is always available for picked media and is available for media captured with the camera when cameraRoll and waitUntilSaved are both true (i.e. it needs to be in the filesystem to have a file name).
latitude and longitude are available for picked media. Captured media doesn't get this metadata automatically, so some CoreLocation code can be added in the future to have this data for all cases.
timestamp is available for picked media and is available for media captured with the camera when cameraRoll and waitUntilSaved are both true. Some more logic can be added in the future to get this for all cases.

There is still room for improvement here but this is what I needed to change for our uses, and hopefully it can be merged in order for other people to take advantage of.

This PR has been squashed into one commit and rebased on master to resolve merge conflicts in the readme, it should be ready for review and merging now.


replace davclient.js with perry-mitchell/webdav-client

subtask of #705
the current davclient is not working on node, so we need to replace it with a client that works with node as well as browsers.
one possibility is https://github.com/perry-mitchell/webdav-client
It used not to support customer dav props see https://github.com/perry-mitchell/webdav-client/pull/165 (current status need to be researched and if needed an upstream PR need to be created)

Fixed by #735


Implement shallow clone?

If I want to implement a traverse-and-copy algorithm, but copying only some nodes selectively, my first idea would be to use a shallow clone and traverse the jsoup DOM.
Since the DOM is kinda immutable, how can I implement this? A shallow clone (eg: exposing doClone I guess) would be ideal, otherwise I would have to implement a shallow clone myself.

Thanks for the suggestion, makes sense.

Thanks; took a while but it's done :)

Great! Thanks 👍


Adding SAC example for pendulum env

Maybe, the binder service needs to be restarted. I cannot include the sac header.
Also, I think we can rename the q_learning folder to a more suitable name, maybe reinforcement_learning, as Soft-AC does not fall under the category of q_learning, I suppose.

Maybe, the binder service needs to be restarted. I cannot include the sac header.

I have to rebuild the mlpack package against the latest master branch, will do that today.

Also, I think we can rename the q_learning folder to a more suitable name, maybe reinforcement_learning, as Soft-AC does not fall under the category of q_learning, I suppose.

Yes, good idea, maybe we can also say reinforcement_learning_gym to make clear we apply RL to gym env's.

Currently rebuilding the package.

Okay, so due to some recent updates (https://github.com/mlpack/mlpack/pull/2543) regarding the go package, we have to disable the go mlpack package - https://github.com/zoq/examples/commit/08bf8169d950217192308f5910d0467d124729bd should do the trick.

Okay, so due to some recent updates (mlpack/mlpack#2543) regarding the go package, we have to disable the go mlpack package - zoq@08bf816 should do the trick.

The training process is super slow using this, for me. Is that the case for you as well? I'll update the notebook here, so please use that to test.

The training process is super slow using this, for me. Is that the case for you as well? I'll update the notebook here, so please use that to test.

Yes I can see the same result, I timed the train block using:
arma::wall_clock timer;
timer.tic();

train(5000);

double n = timer.toc();
std::cout << "number of seconds: " << n << std::endl;

number of seconds: 345.687

I also tested with adding:
omp_set_dynamic(0);
omp_set_num_threads(2);

after the using namespace section and got slightly better results: number of seconds: 292.053. I'm not sure the cling kernel can handle openmp instructions. We can try to reduce the network size to speed things up.

after the using namespace section and got slightly better results: number of seconds: 292.053. I'm not sure the cling kernel can handle openmp instructions. We can try to reduce the network size to speed things up.

I've reduced the network size and decreased the no. of updates in an interval. Though the agent is not able to perform as well as the "discretized" dqn, but still I think we can manage. Or, maybe train for longer and see the results?

I've reduced the network size and decreased the no. of updates in an interval. Though the agent is not able to perform as well as the "discretized" dqn, but still I think we can manage. Or, maybe train for longer and see the results?

Yeah, let's train with more iterations, I don't mind to wait a little but longer, if the result is more stable.

Here we go, thanks again.


Modify the README content and resolve the title display exception

Modify the README content and resolve the title display exception

thanks for contributing


Definitions cause infinite loop loading Swagger UI

Hi folks, great work. When I include a "definition" in my swagger spec, which otherwise works, I get this error:
<IP_ADDRESS> - - [20/Mar/2017 22:00:17] "GET /specs HTTP/1.1" 200 -
<IP_ADDRESS> - - [20/Mar/2017 22:00:17] "GET /v1/spec HTTP/1.1" 500 -
Traceback (most recent call last):
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1994, in __call__
    return self.wsgi_app(environ, start_response)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1985, in wsgi_app
    response = self.handle_exception(e)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1540, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
    raise value
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
    response = self.full_dispatch_request()
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
    raise value
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/views.py", line 84, in view
    return self.dispatch_request(*args, **kwargs)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flask/views.py", line 149, in dispatch_request
    return meth(*args, **kwargs)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flasgger/base.py", line 267, in get
    verb=verb)
  File "/Users/scox/dev/exposures/venv/lib/python3.6/site-packages/flasgger/base.py", line 123, in _extract_definitions
    schema = item.get("schema")
AttributeError: 'str' object has no attribute 'get'

I'm using an external yaml file for a single operation so I could see how a definition might not be in the correct context for that file. So I looked for an example using definitions in this repo but didn't see any. What am I doing wrong?

Can you share your YAML?
Looks like you defined something as string when should be a dict

@rochacbruno, the YAML is pasted below. It's also available in the Swagger editor like this if that's helpful:

See the smartAPI Registry
See Exposure API v0.0.1
Select Swagger Edtor

What I'd really like to do is use the spec as a whole like it is below, including for validation. Is that an option? i.e. instead of splitting it up into separate operations.
swagger: '2.0'
info:
  contact:
    responsibleDeveloper: Data Translator Green Team
    url: www.renci.org
    email<EMAIL_ADDRESS>    responsibleOrganization: Data Translator Green Team
  title: Exposure API
  description: API for environmental exposure models for NIH Data Translator program
  termsOfService: None Available
  version: 0.0.1
host: renci.org
basePath: /DataTranslatorExposures/api
schemes:
  - http
paths:
  '/exposureValue/{exposure}':
    get:
      description: >-
        Retrieve the computed exposure value for a given environmental exposure
        factor, time period, and set of locations
      operationId: getExposureValue
      responses:
        '200':
          description: successful operation
          schema:
            type: array
            items:
              $ref: '#/definitions/Exposures'
      parameters:
        - name: exposure
          in: path
          description: 'The name of the exposure factor (currently limited to pm25, ozone).'
          required: true
          type: string
        - name: stime
          in: query
          description: >-
            The starting date to obtain exposures for (example 1985-04-12 is
            April 12th 1985). Currently time of day is ignored.
          required: true
          type: string
        - name: etime
          in: query
          description: >-
            The ending date to obtain exposures for (example 1985-04-13 is April
            13th 1985). Currently time of day is ignored.
          required: true
          type: string
        - name: loc
          in: query
          description: >-
            A description of the location(s) to retrieve the exposure for.
            Locaton may be a single geocoordinate (example
            '35.720278,-79.176389') or a semicomma separated list of
            geocoord:dayhours giving the start and ending hours on specific days
            of the week at that location (example
            '35.720278,-79.176389,Sa0813;35.720278,-79.176389,other') indicates
            Saturdays from 8am to 1pm is at one location and all other times are
            at another location. Hours should be in 24 hours time using 2
            digits, days of the week should be the first two characters of the
            day.If the day of the week does not appear then the time periods
            apply to all days (example
            '35.720278,-79.176389,0614,35.731944,-78.852778,1424') gives two
            time periods for all days. If hours do not appear then the time
            period applies to all hours of the day (example
            '35.720278,-79.176389,Sa,35.731944,-78.852778,Su').
          required: true
          type: string
        - name: tres
          in: query
          description: >-
            The temporal resolution to use for results, should be one of 'hour'
            or 'day'. Default is 'day'
          required: false
          type: string
        - name: tstat
          in: query
          description: >-
            The statistic to use for results, should be one of 'max', 'mean', or
            'median'. Default is 'max'
          required: false
          type: string
      summary: Get exposure value for a given environmental factor
      produces:
        - application/json
  '/exposureScore/{exposure}':
    get:
      description: >-
        Retrieve the computed exposure score for a given environmental exposure
        factor, time period, and set of locations
      operationId: getExposureScore
      responses:
        '200':
          description: successful operation
          schema:
            type: array
            items:
              $ref: '#/definitions/Exposures'
      parameters:
        - name: exposure
          in: path
          description: 'The name of the exposure factor (currently limited to pm25, ozone).'
          required: true
          type: string
        - name: stime
          in: query
          description: >-
            The starting date to obtain exposures for (example 1985-04-12 is
            April 12th 1985). Currently time of day is ignored.
          required: true
          type: string
        - name: etime
          in: query
          description: >-
            The ending date to obtain exposures for (example 1985-04-13 is April
            13th 1985). Currently time of day is ignored.
          required: true
          type: string
        - name: loc
          in: query
          description: >-
            A description of the location(s) to retrieve the exposure for.
            Locaton may be a single geocoordinate (example
            '35.720278,-79.176389') or a semicomma separated list of
            geocoord:dayhours giving the start and ending hours on specific days
            of the week at that location (example
            '35.720278,-79.176389,Sa0813;35.720278,-79.176389,other') indicates
            Saturdays from 8am to 1pm is at one location and all other times are
            at another location. Hours should be in 24 hours time using 2
            digits, days of the week should be the first two characters of the
            day.If the day of the week does not appear then the time periods
            apply to all days (example
            '35.720278,-79.176389,0614,35.731944,-78.852778,1424') gives two
            time periods for all days. If hours do not appear then the time
            period applies to all hours of the day (example
            '35.720278,-79.176389,Sa,35.731944,-78.852778,Su').
          required: true
          type: string
        - name: tres
          in: query
          description: >-
            The temporal resolution to use for results, should be one of 'hour'
            or 'day'. Default is 'day'
          required: false
          type: string
        - name: tscore
          in: query
          description: >-
            The exposure score type to return. The accepted values vary by
            exposure factor. For pm25 values are '7dayrisk', '14dayrisk' (NOT
            COMPLETE)
          required: false
          type: string
      summary: Get exposure score for a given environmental factor
      produces:
        - application/json
definitions:
  Exposures:
    type: object
    properties:
      values:
        $ref: '#/definitions/Exposure'
  Exposure:
    type: object
    properties:
      stime:
        type: string
        format: dateTime
        example: starting time for the given measure
      value:
        type: string
        example: numerical or categorical depending upon type of value being requested
      etime:
        type: string
        format: dateTime
        example: ending time for the given measure

I've split that into this and changed the operation definition to include a schema to take advantage of flasgger as follows:
Get environmental exposure value operation
---
swagger: '2.0'
info:
  title: Exposure API
  description: API for environmental exposure models for NIH Data Translator program
  contact:
    responsibleOrganization: Data Translator Green Team
    responsibleDeveloper: Data Translator Green Team
    email<EMAIL_ADDRESS>    url: www.renci.org
  termsOfService: None Available
  version: 0.0.1
host: exposures.renci.org
basePath: /api
schemes:
  - [ "http", "https" ]
tags:
  - Exposure
operationId: getExposureScore
parameters:
  - name: body
    in: body
    required: true
    schema:
      id : exposureScoreRequestSchema
      required:
        - exposure
        - stime
        - etime
        - loc
      properties:
        exposure:
          description: 'The name of the exposure factor (currently limited to pm25, ozone).'
          required: [ "true" ]
          default: pm25
          type: string
        stime:
          description: >-
            The starting date to obtain exposures for (example 1985-04-12 is
            April 12th 1985). Currently time of day is ignored.
          required: [ "true" ]
          default: '1985-04-12'
          type: string
        etime:
          description: >-
            The ending date to obtain exposures for (example 1985-04-13 is April
            13th 1985). Currently time of day is ignored.
          default: '1985-04-12'
          required: [ "true" ]
          type: string
        loc:
          description: >-
            A description of the location(s) to retrieve the exposure for.
            Locaton may be a single geocoordinate (example
            '35.720278,-79.176389') or a semicomma separated list of
            geocoord:dayhours giving the start and ending hours on specific days
            of the week at that location (example
            '35.720278,-79.176389,Sa0813;35.720278,-79.176389,other') indicates
            Saturdays from 8am to 1pm is at one location and all other times are
            at another location. Hours should be in 24 hours time using 2
            digits, days of the week should be the first two characters of the
            day.If the day of the week does not appear then the time periods
            apply to all days (example
            '35.720278,-79.176389,0614,35.731944,-78.852778,1424') gives two
            time periods for all days. If hours do not appear then the time
            period applies to all hours of the day (example
            '35.720278,-79.176389,Sa,35.731944,-78.852778,Su').
          required: [ "true" ]
          default: '35.720278,-79.176389,Sa,35.731944,-78.852778,Su'
          type: string
        tres:
          description: >-
            The temporal resolution to use for results, should be one of 'hour'
            or 'day'. Default is 'day'
          required: [ "false" ]
          type: string
        tscore:
          description: >-
            The exposure score type to return. The accepted values vary by
            exposure factor. For pm25 values are '7dayrisk', '14dayrisk' (NOT
            COMPLETE)
          required: [ "false" ]
          type: string
produces:
  - application/json
summary: Get exposure score for a given environmental factor
description: >-
  Retrieve the computed exposure score for a given environmental exposure
  factor, time period, and set of locations
responses:
  '200':
    description: successful operation
    schema:
      items:
        $ref: '#/definitions/Exposures'
        type: array
definitions:
  Exposures:
    type: object
    properties:
      values:
        $ref: '#/definitions/Exposure'
  Exposure:
    type: object
    properties:
      stime:
        type: string
        format: dateTime
        example: starting time for the given measure
      value:
        type: string
        example: numerical or categorical depending upon type of value being requested
      etime:
        type: string
        format: dateTime
        example: ending time for the given measure

On the face of it, it doesn't seem like definitions really belong at the same level as an operation. It works great without that part. Anyway, any guidance is appreciated.

I will try to reproduce your problem.

@stevencox sent https://github.com/stevencox/exposures/pull/1


Pod not available on CocoaPods trunk

[!] CocoaPods could not find compatible versions for pod "UICircularProgressRing":
In Podfile:
UICircularProgressRing (~> 1.8.5)
None of your spec sources contain a spec satisfying the dependency: UICircularProgressRing (~> 1.8.5).
CocoaPods version: 1.5.0
Xcode Version: 9.3

Which Swift version are you using?

4.1

That’s odd. I see the release on github and the podspec is pointing to 1.8.5. I’ll take a look when I get a chance.

Oh never mind I totally forgot to push 1.8.5 to trunk, I’ll do that when I get home.

Thank you! You are awesome!


First pass on documentation verification

While unifying the class documentation in #368 I noticed (and fixed) a few broken or incorrect links, but for the most part I left everything else alone. I pretty much just copy/pasted the contents of the separate class files into a single file to consolidate the class reference documentation. So if there were any other errors already in the documentation, they're still there. In addition to that, there's a decent chance that I may have broken some links myself when I moved files around. For that reason I've decided to make a more thorough pass at all the documentation to make sure all the links are working and pointing to the correct location.
I've spent a few hours and made some improvements already, most noteworthy of all being that I resolved all the warnings/complaints that MKDocs would spit out when compiling the docs. I've also updated several outdated links such as the support email, links which were pointing to the example project branch in the main repo, and links which said the example project was for Godot 3.x only and not for Godot 4.x.
That said, I still have a long way to go before I have thoroughly checked every single page of documentation and all the links. So I figured that people accessing the documentation could benefit from the changes right away if they get merged in an iterative fashion. Here a little and there a little, until it's all been looked over and verified. (I think future PRs wouldn't be as large as this one, since I'd likely submit a few thoroughly checked files at a time now that I've "mass edited" the majority of files.)
The alternative is that the published documentation stays more or less how it is until I get the chance to verify absolutely everything else, which could take several days or possibly a few weeks.
So if me submitting PRs every couple of days is adding too much extra work and stress for you, or for whatever reason you just want to wait until I've had time to verify every page and submit one massive PR with all the changes, then you can consider this a draft PR. If that's the case just let me know and I'll continue making commits to it until this PR becomes the one massive PR with all the changes. 😉

Damn!  Another heroic effort, thank you so much!
Haha, alas, it has removed my beloved double-spacing after periods!  I know for some reason some standards have removed that as unnecessary but it is much better for quick text scanning; as long as it isn't removing the Oxford comma which is completely insane.
Eh, if PR's and code review are too much work or stress than I have been in the wrong business for many years.  Haha.  However many you need to make, friend!

alas, it has removed my beloved double-spacing after periods! I know for some reason some standards have removed that as unnecessary but it is much better for quick text scanning; as long as it isn't removing the Oxford comma which is completely insane.

HTML doesn't render the extra spacing, so it's largely redundant/obsolete now to have two spaces after a period. But I'm a fan of the Oxford comma so I'm more likely to add that in places where it's missing. 🤓

Ah yes.  Good point.  Thanks for nothing HTML.  And yes on the Oxford comma.  Without it the sentence structure changes a bit and it looks ridiculous.


Add ECS+Docker to Stelligent Demo Documentation.

This has been started and can be found here :
https://docs.google.com/document/d/1CZL7JAPft1guhCwrayBDA96GActd2QjWJ2pLpDcXCVw/edit


Add CI stage which deploys the documentation

[x] Only on master branch
[x] Upload via FTP using separate account, adapt existing deploy target
[x] Store credentials on CI server using lftp bookmark

Implemented via #57.


Markdown Parser Rework

[x] Working parsers
[ ] Implement presets

[x] Default (current Quartz defaults)
[ ] Obsidian

[ ] Include links defined in frontmatter.

[ ] CommonMark (possibly, might do in another PR)
[ ] Custom (basically custom.scss for parsers. We won't change the parser order to allow users to costumize.)

[ ] Fix current known transformer bugs
[ ] Testing
[ ] Update documentation

Open parser issues

[ ] https://github.com/jackyzha0/quartz/issues/1424
[ ] https://github.com/jackyzha0/quartz/issues/1535
[ ] https://github.com/jackyzha0/quartz/issues/1536
[ ] https://github.com/jackyzha0/quartz/issues/1537
[ ] https://github.com/jackyzha0/quartz/issues/1538
[ ] https://github.com/jackyzha0/quartz/issues/1541
[ ] https://github.com/jackyzha0/quartz/issues/1542
[ ] https://github.com/jackyzha0/quartz/issues/1547
[ ] https://github.com/jackyzha0/quartz/issues/1550
[ ] https://github.com/jackyzha0/quartz/issues/1559
[ ] https://github.com/jackyzha0/quartz/issues/1561
[ ] https://github.com/jackyzha0/quartz/issues/1628
[ ] https://github.com/jackyzha0/quartz/issues/1639

Fixed parser issues

closes https://github.com/jackyzha0/quartz/issues/1114

@aarnphm Just a quick check if this direction is okay before I continue implementing the fixes for the 10+ open issues related to transformer.

that is, a lot of change :)

probably cc @jackyzha0 once he has bandwidth
source of this change is from #1424

that is, a lot of change :)

Yeah, in its current form, it merely breaks up every text/markdown/html parsing step into a separate file, instead of grouping them.

probably cc @jackyzha0 once he has bandwidth
source of this change is from #1424

This can be resolved by adding a markdown parser for non-wikilinks. Users could choose to use the non-wikilink parser over the wikilink parser should they prefer that functionality.
It believe it also makes parser more extendable.
Having said that, I am aware this is a breaking change, but I am not entirely sure if it is possible to make it a non-breaking change. However, I think configuration could probably be done in a more sophisticated manner.

source of this change is from #1424

This can be resolved by adding a markdown parser for non-wikilinks. Users could choose to use the non-wikilink parser over the wikilink parser should they prefer that functionality.

We did mention some structural change that you have in this PR in that issues

Maybe #1647 would be a related bug to fix in this branch.
Thanks for working on Quartz, this rework is huge!

hmm, I look into remark and unist ecosystem a bit, fwiw we might want to write remark-obsidian and rehype-obsidian at this point

hmm, I look into remark and unist ecosystem a bit, fwiw I'm considering writing remark-obsidian and rehype-obsidian during the break :)

You know. That would actually be a way more robust solution.
Do you want me to look into that, or do you prefer to take care of implementing that?
I could work on proposing a plugin interface if you prefer to work on the parsers.

I think quartz is a lot more feature-full comparing to that, but I will def give them remarks


Use DataSource API for OAI harvest

This implements the DataSource API for an OAI harvest instead of the RDD API.
I tested this locally using the following params:
endpoint: http://oai.artstor.org/oaicatmuseum/OAIHandler
metadataPrefix: oai_dc
verb: ListRecords

It addresses ticket DT-1278.

Good suggestion @mdellabitta, thanks!  I changed the field name as you suggested rebased.


spidermonkey: update to 102 and fix build under macOS

Description of changes
This PR adds spidermonkey_102 which can be used on every unix which includes macOS. It also fix build of old version under macOS.
Thus, it suppress / consumes / closes #172376 and fixes #91415
And it adds tests for all packages :)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval

@SuperSandro2000 may I ask you to re-review this one also? Thanks!

It would be nice to split the changes into independent commits, for example:

spidermonkey_*: Factor out into a common expression
spidermonkey_*: Fix build under macOS
spidermonkey_102: init at 102.0

That will make it easier to review.

@jtojnar I've done it in different way:

added 102 with macOS support
added macOS support for 91 and 78;
refactored it.

Having (2) separate from the other changes is the most important. But having the unification first would be the best since it minimizes the number of files needed to compare.

@jtojnar ok, let me try do it. It shouldn't be something complicated.

@jtojnar here it is.

@jtojnar seems that I've addressed all your comments. Or at least I hope so.
To make review easy I haven't rebased anything, and keep all changes as two dedicated commits.

It seems to me like the removed adds-Wno-deprecated-declarations-icu.patch may have been a fix of system icu for 102esr on darwin?
If the patch did work my preference from a couchdb perspective is to use the system icu where possible since couchdb independently depends on the system icu, but that's not a very high priority.

@lostnet things a bit more complicated. It is failed since https://github.com/mozilla/gecko-dev/commit/9aa3587bbf0416dd2eb5b614f7b301c71c64286b
The patch wasn't needed at all, it was a wrong lead which I forgot to remove.
I may hack build system a bit more to allow using both system's icu and nspr, but it seems quite ugly.

Passing --with-system-icu and --with-system-nsprshould be possible. We do use that onbuildMozillaMach`, also for 91 and 102 ESR releases. But we also only build for the two Linux targets.

@mweinelt are you sure? I see that firefox 102 has badPlatforms = lib.platforms.darwin: https://github.com/NixOS/nixpkgs/blob/be948cdf737fec2f1d69ff721da2c0bd2232bb46/pkgs/applications/networking/browsers/firefox/packages.nix#L43

I'm not sure what about Darwin is broken. It hasn't been maintained for more than 3y, and even then it was on and off.
What error are you seeing with both enabled?

@mweinelt it simple fails on configure stage because icu / nsr can't be used from system if it bootstraped from scratch.

@mweinelt to summarize: --with-system-icu and --with-system-nspr aren't used only on macOS and only for 102+ version.

Its nice to preserve the commits for people doing code archaeology with git blame.

@jtojnar when let keep it on this way

I've:

revased to last master and consume fixup commits;
added a trivial patch to allow using system's icu and nspr on macOS.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/548

@lostnet any idea what should I do to have it merged?

Result of nixpkgs-review pr 179822 run on aarch64-darwin 1

1 package marked as broken and skipped:

spidermonkey

2 packages failed to build:

jsawk
spidermonkey_78

3 packages built:

couchdb3
spidermonkey_102
spidermonkey_91

@siraben did it builds before?

Rebased to the last master to fix conflict with https://github.com/NixOS/nixpkgs/pull/182849
@mweinelt maybe we should merge it?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/567

@SuperSandro2000 may I ask you to re-review this one?

@catap This comment has yet to be solved.

Just saw that GNOME 43 will depend on SpiderMonkey 102!

@wegank thanks for the ping. I'll take a look on this on couple of hours.

Since this is blocking #182618, I cleaned up it a bit, addressed the remaining review comments and reverted some pointless changes (e.g. exporting configureScript): https://github.com/NixOS/nixpkgs/pull/185928


Lack of Guidelines for Community Contributions

There's no content in the page: https://kamaji.clastix.io/contribute/
How can one contribute ?

@wrkode content is in the first section https://kamaji.clastix.io/contribute/guidelines/#general
We'll try to improve the navigation of the menu.


inconsistent result on volume

Hi,
I'm not sure which forum or mail list I should discuss this topic. But, I'm guessing everybody here is familiar with this.
When I fetch volume data continuously from endpoint https://api.robinhood.com/fundamentals , I found the volume decreases sometimes. It usually increases as time goes as expected. But, sometimes, decreasing happens - with 5% reproducibility.
For example,
MSFT : updateat 2019-03-27T13:30:01Z | volume:<PHONE_NUMBER>00
MSFT : updateat 2019-03-27T13:30:21Z | volume:<PHONE_NUMBER>00
MSFT : updateat 2019-03-27T13:30:41Z | volume: 1259314.000000
MSFT : updateat 2019-03-27T13:31:01Z | volume:<PHONE_NUMBER>00 // What???
MSFT : updateat 2019-03-27T13:31:21Z | volume: 1332935.000000
MSFT : updateat 2019-03-27T13:31:41Z | volume:<PHONE_NUMBER>00 // What???
I also posted this on below but couldn't get answer.
https://www.reddit.com/r/algotrading/comments/b6fmbi/weird_decreasing_volume_sequence_data_fetched/
My feeling is, looks there's multiple API server on RH and they aren't sync correctly, timely.
Does anybody have same issue with me?

Just a note, I use robinhood mobile app daily and I consistently observe
this issue in their app. I suggest you reach out to them directly or post
on robinhood reddit page.
On Thu, Mar 28, 2019 at 11:11 AM indigo62018<EMAIL_ADDRESS>wrote:

Hi,
I'm not sure which forum or mail list I should discuss this topic. But,
I'm guessing everybody here is familiar with this.
When I fetch volume data continuously from endpoint
https://api.robinhood.com/fundamentals , I found the volume decreases
sometimes. It usually increases as time goes as expected. But, sometimes,
decreasing happens - with 5% reproducibility.
For example,
MSFT : updateat 2019-03-27T13:30:01Z | volume:<PHONE_NUMBER>00
MSFT : updateat 2019-03-27T13:30:21Z | volume:<PHONE_NUMBER>00
MSFT : updateat 2019-03-27T13:30:41Z | volume: 1259314.000000
MSFT : updateat 2019-03-27T13:31:01Z | volume:<PHONE_NUMBER>00 // What???
MSFT : updateat 2019-03-27T13:31:21Z | volume: 1332935.000000
MSFT : updateat 2019-03-27T13:31:41Z | volume:<PHONE_NUMBER>00 // What???
I also posted this on below but couldn't get answer.
https://www.reddit.com/r/algotrading/comments/b6fmbi/weird_decreasing_volume_sequence_data_fetched/
My feeling is, looks there's multiple API server on RH and they aren't
sync correctly, timely.
Does anybody have same issue with me?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Jamonek/Robinhood/issues/171, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADtLsL2TJRlncFY6QGR7ZNwBSuMWCkwFks5vbQXcgaJpZM4cQzsg
.

Reaching out to Robinhood may result in your account being shutdown for using an unofficial API. I’d be careful
Best,
Jamone

On Mar 28, 2019, at 2:11 PM, indigo62018<EMAIL_ADDRESS>wrote:
Hi,
I'm not sure which forum or mail list I should discuss this topic. But, I'm guessing everybody here is familiar with this.
When I fetch volume data continuously from endpoint https://api.robinhood.com/fundamentals , I found the volume decreases sometimes. It usually increases as time goes as expected. But, sometimes, decreasing happens - with 5% reproducibility.
For example,
MSFT : updateat 2019-03-27T13:30:01Z | volume:<PHONE_NUMBER>00
MSFT : updateat 2019-03-27T13:30:21Z | volume:<PHONE_NUMBER>00
MSFT : updateat 2019-03-27T13:30:41Z | volume: 1259314.000000
MSFT : updateat 2019-03-27T13:31:01Z | volume:<PHONE_NUMBER>00 // What???
MSFT : updateat 2019-03-27T13:31:21Z | volume: 1332935.000000
MSFT : updateat 2019-03-27T13:31:41Z | volume:<PHONE_NUMBER>00 // What???
I also posted this on below but couldn't get answer.
https://www.reddit.com/r/algotrading/comments/b6fmbi/weird_decreasing_volume_sequence_data_fetched/
My feeling is, looks there's multiple API server on RH and they aren't sync correctly, timely.
Does anybody have same issue with me?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

thanks guys for your advice. :) let me close this


Liability Statement Missing in Translations from mdJSON

Distribution Liability (distliab) is not writing to CSDGM from mdJSON input: schema{ } > metadata{ } > resourceDistribution[ ] > distribution{ } > liabilityStatement. Data appears to be in mdJSON file.

I think the issue might be, related to this comment in the fgdc writer for distribution
# in FGDC each distribution can have only one distributor
# the passed in mdJson hDistribution may contain multiple distributors
# therefore, create a separate FGDC distribution record for each distributor
# and repeat the distribution information

so if they're no distributor, no distribution info gets printed out.  I added a check if there's no distributors, still print out the description and liabilityStatement

While that rule is true, it is not the use case here in which there is a single distribution.
Here is the mdJSON, followed by the translated CSDGM:
	"resourceDistribution": [{
		"distributor": [{
			"contact": {
				"role": "distributor",
				"party": [{
					"contactId": "1b759b80-bb2a-4b66-898d-56e4c9b4a341"
				}]
			},
			"orderProcess": [{
				"fees": "None",
				"orderingInstructions": "It is recommended that a geographic information system or other native GeoTIFF viewer be used to view the elevation raster."
			}],
			"transferOption": [{
				"onlineOption": [{
					"uri": "https://doi.org/10.5066/P9K7CFRI",
					"protocol": "HTTPS",
					"description": "Landing webpage for data download"
				}],
				"distributionFormat": [{
					"formatSpecification": {
						"title": "geoTIFF"
					},
					"compressionMethod": "LZW"
				}],
				"transferSize": 6000
			}]
		}],
		"description": "Authoritative source for the data.",
		"liablityStatement": "Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty."
	}],

<distinfo>
     <distrib>
        <cntinfo>
           <cntorgp>
              <cntorg>U.S. Geological Survey, Alaska Science Center</cntorg>
           </cntorgp>
           <cntaddr>
              <addrtype>physical</addrtype>
              <address>4210 University Drive</address>
              <city>Anchorage</city>
              <state>AK</state>
              <postal>99508</postal>
              <country>USA</country>
           </cntaddr>
           <cntvoice>907-786-7000</cntvoice>
           <cntfax>907-786-7020</cntfax>
<EMAIL_ADDRESS>        </cntinfo>
     </distrib>
     <resdesc>Authoritative source for the data.</resdesc>
     <stdorder>
        <digform>
           <digtinfo>
              <formname>geoTIFF</formname>
              <formspec>geoTIFF</formspec>
              <filedec>LZW</filedec>
              <transize>6000</transize>
           </digtinfo>
           <digtopt>
              <onlinopt>
                 <computer>
                    <networka>
                       <networkr>https://doi.org/10.5066/P9K7CFRI</networkr>
                    </networka>
                 </computer>
                 <accinstr>HTTPS</accinstr>
                 <oncomp>Landing webpage for data download</oncomp>
              </onlinopt>
           </digtopt>
        </digform>
        <fees>None</fees>
        <ordering>It is recommended that a geographic information system or other native GeoTIFF viewer be used to view the elevation raster.</ordering>
     </stdorder>
     <techpreq/>
  </distinfo>

The distliab tags should appear below the resdesc tags

@dwalt I see the issue, it looks like there a misspelling, liablityStatement vs liabilityStatement (missing i)
this is coming from mdEditor https://github.com/adiwg/mdEditor/blob/f94770686df07ef76aa111f8f9734b32bbad7f21/app/pods/components/object/md-distribution/template.hbs#L22
since this is in the Production version I'll do a little digging on how we can handle upgrading existing mdJson to the correct spelling transparently in the editor, and I suppose we should handle both spellings in the translator

Good eye! I would agree with supporting both spellings in the translator to avoid breaking older mdJSON files. I am surprised the schema validator did not catch the invalid tag.

@dwalt this and the other "CSDGM" issues are deployed here for testing:
https://dev-translator.mdeditor.org/demo
(and https://dev-editor.mdeditor.org/dashboard points to the above)

mdJSON-CSDGM translated successfully

@dwalt how do we want to handle instances where BOTH a liabilityStatement (imported from CSDGM) and a liablityStatement (missing i) are present? I came across an instance of this today. In theory, the statement entered via the editor (after CSDGM import) could supersede the initial statement. Do we want to append the two values into a single statement?

@hmaier-fws I would tend to think that what the user entered in mdEditor is the latest and greatest and should supersede what was imported. Often, the re-entered text is the same as what was imported, so if it is appended, it is definitely wrong.

This problem has been discovered in -2 output and HTML and is therefore universal. The fix should solve it for all writers, but should be verified.

PR created https://github.com/adiwg/mdEditor/pull/557

https://github.com/adiwg/mdEditor/issues/497 is related


misc(fraud): rework register func

Overview
Please provide an explanation of the PR, including the appropriate context,
background, goal, and rationale. If there is an issue with this information,
please provide a tl;dr and link the issue.
-->
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

N/A


Python2.7 custom reporting

@maboelnour @OAbubakr After getting python2.7 and dependencies to work, found that the explosion operators * and ** are unsupported. It is a lot of work to refactor this :(


Instana exporter documentation.

Addition of new Instana exporter documentation. These changes are related to the following PR that adds an OpenTelemetry exporter for Instana https://github.com/open-telemetry/opentelemetry-php/pull/1462

Hi @kothiga, could you sign the CLA please? Thanks!

Hey @kothiga,
vendor specific documentation does not belong into the OpenTelemetry documentation. Please add them to the instana documentation directly. You can then link to them via an entry in the registry. Either an existing one or a new one.
Thanks.


Metasys10.1 update

I am not sure if this should be a pull request into the 10.1 branch rather than master.


Fluent Parameters

As far as I have seen, there is currently no way of using the fluent variables in tlf files.
This PR makes it so that you can use that feature of fluent-rs.
The ui-example was extended to demonstrate how to use it.

@kgv  I do not know any Russian, so if you might help me with that, it would be appriciated

could be wrong, but this seems very similar to #32 from me.
I also assumed you couldn't use the parameters, but you actually could.
i'm not so up to date with this crate, but last time i used it in bevy 0.11.x i could just do
localization.content("id?attribute=value")

as seen here: https://docs.rs/fluent_content/0.0.5/fluent_content/struct.Request.html#examples


Ignore dynamic assemblies.

Cannot call ExportedTypes on a dynamic assembly so make sure these are filtered out first.

Thank you! nice catch!


[BUG] Unable to create detector

What is the bug?
It is not possible to create a detector in the UI. Is it possible to recreate all the necessary indexes/aliases for security analytics?
How can one reproduce the bug?
Steps to reproduce the behavior:

Go to 'Security Analytics page'
Click on 'Create detector'
Select windows log type
Click 'Create'
See error
See error log:

[2024-02-04T16:52:50,482][INFO ][o.o.a.t.TransportIndexMonitorAction] [msk-it-siem-03] Central Percolation index .opensearch-sap-windows-detectors-que
ries created
[2024-02-04T16:52:50,490][ERROR][o.o.a.u.DocLevelMonitorQueries] [msk-it-siem-03] Failed to get write index for queryIndex alias:.opensearch-sap-windo
ws-detectors-queries
[2024-02-04T16:52:50,491][ERROR][o.o.a.u.AlertingException] [msk-it-siem-03] Alerting error: OpenSearchStatusException[Failed to get write index for q
ueryIndex alias:.opensearch-sap-windows-detectors-queries]
[2024-02-04T16:52:50,492][ERROR][o.o.a.t.TransportIndexMonitorAction] [msk-it-siem-03] failed to index doc level queries monitor mTBkdI0BHZISNeu3qIjH.
 deleting monitor
org.opensearch.alerting.util.AlertingException: Failed to get write index for queryIndex alias:.opensearch-sap-windows-detectors-queries
        at org.opensearch.alerting.util.AlertingException$Companion.wrap(AlertingException.kt:70) ~[opensearch-alerting-<IP_ADDRESS>.jar:<IP_ADDRESS>]
        at org.opensearch.alerting.util.DocLevelMonitorQueries.updateQueryIndexMappings(DocLevelMonitorQueries.kt:407) ~[opensearch-alerting-<IP_ADDRESS>.
jar:<IP_ADDRESS>]
        at org.opensearch.alerting.util.DocLevelMonitorQueries.indexDocLevelQueries(DocLevelMonitorQueries.kt:284) ~[opensearch-alerting-<IP_ADDRESS>.jar:
<IP_ADDRESS>]
        at org.opensearch.alerting.util.DocLevelMonitorQueries$indexDocLevelQueries$1.invokeSuspend(DocLevelMonitorQueries.kt) ~[opensearch-alerting-2
.11.1.0.jar:<IP_ADDRESS>]
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) [kotlin-stdlib-1.8.21.jar:1.8.21-release-380(1.8.21)
]
        at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:233) [kotlinx-coroutines-core-1.1.1.jar:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594) [kotlinx-coroutines-core-1.1.1.jar:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60) [kotlinx-coroutines-core-1.1.1.jar:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:742) [kotlinx-coroutines-core-1.1.1.jar:?]
Caused by: java.lang.Exception: org.opensearch.OpenSearchStatusException: Failed to get write index for queryIndex alias:.opensearch-sap-windows-detec
tors-queries
        ... 9 more
[2024-02-04T16:52:50,540][ERROR][o.o.a.u.AlertingException] [msk-it-siem-03] Alerting error: AlertingException[Failed to get write index for queryInde
x alias:.opensearch-sap-windows-detectors-queries]; nested: Exception[org.opensearch.OpenSearchStatusException: Failed to get write index for queryInd
ex alias:.opensearch-sap-windows-detectors-queries];
[2024-02-04T16:52:50,541][ERROR][o.o.s.t.TransportIndexDetectorAction] [msk-it-siem-03] exception:
org.opensearch.alerting.util.AlertingException: Failed to get write index for queryIndex alias:.opensearch-sap-windows-detectors-queries
        at org.opensearch.alerting.util.AlertingException$Companion.wrap(AlertingException.kt:70) ~[?:?]
        at org.opensearch.alerting.transport.TransportIndexMonitorAction$IndexMonitorHandler.indexMonitor(TransportIndexMonitorAction.kt:552) ~[?:?]
        at org.opensearch.alerting.transport.TransportIndexMonitorAction$IndexMonitorHandler.access$indexMonitor(TransportIndexMonitorAction.kt:251) ~
[?:?]
        at org.opensearch.alerting.transport.TransportIndexMonitorAction$IndexMonitorHandler$indexMonitor$1.invokeSuspend(TransportIndexMonitorAction.
kt) ~[?:?]
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[?:?]
        at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:233) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:742) ~[?:?]
Caused by: java.lang.Exception: org.opensearch.alerting.util.AlertingException: Failed to get write index for queryIndex alias:.opensearch-sap-windows
-detectors-queries
        ... 9 more
[2024-02-04T16:52:50,543][ERROR][o.o.s.u.SecurityAnalyticsException] [msk-it-siem-03] Security Analytics error:
org.opensearch.alerting.util.AlertingException: Failed to get write index for queryIndex alias:.opensearch-sap-windows-detectors-queries
        at org.opensearch.alerting.util.AlertingException$Companion.wrap(AlertingException.kt:70) ~[?:?]
        at org.opensearch.alerting.transport.TransportIndexMonitorAction$IndexMonitorHandler.indexMonitor(TransportIndexMonitorAction.kt:552) ~[?:?]
        at org.opensearch.alerting.transport.TransportIndexMonitorAction$IndexMonitorHandler.access$indexMonitor(TransportIndexMonitorAction.kt:251) ~
[?:?]
        at org.opensearch.alerting.transport.TransportIndexMonitorAction$IndexMonitorHandler$indexMonitor$1.invokeSuspend(TransportIndexMonitorAction.
kt) ~[?:?]
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[?:?]
        at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:233) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:742) ~[?:?]
Caused by: java.lang.Exception: org.opensearch.alerting.util.AlertingException: Failed to get write index for queryIndex alias:.opensearch-sap-windows
-detectors-queries
        ... 9 more
[2024-02-04T16:52:50,544][WARN ][r.suppressed             ] [msk-it-siem-03] path: /_plugins/_security_analytics/detectors, params: {}
org.opensearch.securityanalytics.util.SecurityAnalyticsException: Failed to get write index for queryIndex alias:.opensearch-sap-windows-detectors-que
ries
        at org.opensearch.securityanalytics.util.SecurityAnalyticsException.wrap(SecurityAnalyticsException.java:68) ~[?:?]
        at org.opensearch.securityanalytics.util.SecurityAnalyticsException.wrap(SecurityAnalyticsException.java:43) ~[?:?]
        at org.opensearch.securityanalytics.transport.TransportIndexDetectorAction$AsyncIndexDetectorsAction.lambda$finishHim$0(TransportIndexDetector
Action.java:1474) ~[?:?]
        at org.opensearch.action.ActionRunnable.lambda$supply$0(ActionRunnable.java:74) [opensearch-2.11.1.jar:2.11.1]
        at org.opensearch.action.ActionRunnable$2.doRun(ActionRunnable.java:89) ~[opensearch-2.11.1.jar:2.11.1]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:908) [opensearch-2.11.1.jar:
2.11.1]
        at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.11.1.jar:2.11.1]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: java.lang.Exception: org.opensearch.alerting.util.AlertingException: Failed to get write index for queryIndex alias:.opensearch-sap-windows
-detectors-queries
        ... 10 more

What is the expected behavior?
Successful creation of the detector.
What is your host/environment?

OS: Ubuntu 22.04.2
OpenSearch: 2.11.1
Plugins: security-analytics 2.11.1

Do you have any screenshots?

@qw1mb0 , can you please share any additional information on the version of OpenSearch - i.e did you upgrade from OpenSearch 2.5 to 2.11/2.12 recently? We added the concept of using alias for the query index (rules are copied to a system index as queries) in 2.7.

This error seems to be related to the fact that there is no alias called .opensearch-sap-windows-detectors-queries associated with the concrete windows query index. There is supposed to be an alias associated with each query index and should have have one write index associated with that alias. Your alias may have not been created, was somehow deleted, or may not have an index set as the write index. Here are the steps to manually create/fix this.

Check see if the alias .opensearch-sap-windows-detectors-queries doesn't exist or if the alias doesn't have a designated write index: GET _cat/aliases
If this alias doesn't exist or doesn't have a write index, manually create it
First find the newest windows query index: `GET _cat/indices/.opensearch-sap-windows-detectors-queries-*'
Then create the alias on the newest windows query index:

POST _aliases
{
  "actions": [
    {
      "add": {
        "index": ".opensearch-sap-windows-detectors-queries-000001 (i.e. your newest created windows query index)",
        "alias": ".opensearch-sap-windows-detectors-queries",
        "is_write_index": true
      }
    }
  ]
}

I updated OpenSearch to version 2.12, but when I try to create a detector I get an error:
[security_analytics_exception] Failed to get write index for queryIndex alias:.opensearch-sap-windows-detectors-queries

Existed aliases in opensearch:
$ curl -k -XGET -u 'admin:password' 'https://<ip>:9200/_cat/aliases' -s
.opendistro-alerting-alert-history-write .opendistro-alerting-alert-history-2024.03.16-000011     - - - -
.opensearch-sap-windows-alerts-history   .opensearch-sap-windows-alerts-history-2024.03.06-000002 - - - -
.opensearch-sap-windows-findings         .opensearch-sap-windows-findings-2024.03.06-000002       - - - -

There are also no indices  in the cluster (.opensearch-sap-windows-detectors-queries-*) :
$ curl -k -XGET -u 'admin:password' 'https://<ip>:9200/_cat/indices' -s  | grep opensearch
green open .opensearch-notifications-config QDfok7N0SnmHHPXP4PEMlQ 1 2        0   0     624b     208b
green open .opensearch-observability        rBhEJuZxR3SPvspYqcQD6w 1 2        0   0     624b     208b

Manually created alias:
$ curl -H 'Content-Type: application/json' -k -XPOST -u 'admin:password' 'https://<ip>:9200/_aliases'  -d '{"actions":[{"add":{"index":".opensearch-sap-windows-detectors-queries-000001","alias":".opensearch-sap-windows-detectors-queries","is_write_index":true}}]}'
{"acknowledged":true}

$ curl -k -XGET -u 'admin:password' 'https://<ip>:9200/_cat/aliases' -s   | grep detector
.opensearch-sap-windows-detectors-queries .opensearch-sap-windows-detectors-queries-000001         - - - true

And try to create detector in OpenSearch Security Analytics and this detector create successfully.

Looks like the issue was resolved by manually creating the alias. Will close this issue. Please reopen if there is still a problem creating a detector


Feature: new mbtiles diff command

Implement mbtiles diff file_a.mbtiles file_b.mbtiles diff.mbtiles. This should behave exactly the same as mbtiles copy file_a.mbtiles --diff-with-file file_b.mbtiles diff.mbtiles.

[ ] Add mbtiles diff as a separate command
[ ] Update doc
[ ] Update changelog.md so we can make release easier maybe?

I just did a bit of refactoring to separate Clap args from the internals of the mbtiles copy options.  You could simply reuse that directly, without any changes to the diff. This way the new CLI command will be available right away, and then we can do more refactorings later.

@sharkAndshark i merged in the main branch, resolving a few conflicts. Let me know if you need any help with this

@nyurik Thx!! :D Traveling with family, will be back Monday

Looks much better, thx!  TODO: docs and tests


feat(v1 API): document v1 API examples

v1 API does not exist yet.
I want to make sure that all relevant use cases are sketched out before starting with the implementation.
Most notable changes that the new design will bring:

inspect options of any package via dream2nix man
override packages safely and conveniently using modules
no dependency on nix' flakes feature
better composition of outputs
vastly simplify  integration of existing lang2nix tools into dream2nix (see examples in docs)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/drv-parts-configure-packages-like-nixos-sytems/23629/18


io: documentation for Seeker is ambiguous

In https://groups.google.com/d/msg/golang-nuts/uInF2v-rfqY/VN0VVGfGHM0J, the author expresses confusion at the statement "Seeking to a negative offset is an error". This is reasonable, considering that the name of the first parameter is "offset", and providing a negative value for that argument is not necessarily an error.
Maybe it can be reworded to reduce the ambiguity.

/cc @robpike


Getting error while deploying

I followed the above instructions, i even have apple developer account approved. Phone is connected, iTunes is opened, but I am unable to deploy to iPhone. Using VS 2019 16.5. Cleaned the build and rebuild. I don't have Macbook.  Not sure what's causing the below error.
An error occurred while trying to deploy the app 'App2.iOS.app'.
Details: Error running winiosterminal: 'An error occurred while deploying the application 'App2.iOS.app' into 'test's iPhone'.
Details: An Afc error occurred. The error code was ObjectNotFound'. Command: 'deploy -u=00008020-001D4CCC2E50003A -i=com.companyname.App2 -n=App2.iOS.app'

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

ID: 5ccadd93-fcc8-6a15-9670-d5af7ee7f6f8
Version Independent ID: 188007d3-cf20-97ba-137f-64ff25a88e7c
Content: Automatic Provisioning for Xamarin.iOS - Xamarin
Content Source: docs/ios/get-started/installation/device-provisioning/automatic-provisioning.md
Product: xamarin
Technology: xamarin-ios
GitHub Login: @davidortinau
Microsoft Alias: daortin

Please post this via Send Feedback Report a problem Microsoft won't look at the issue from here as this is solely for documentation bugs.

Okay. I haven't searched in the VS feedback. I will raise a new issue, if i don't find anything.
Thank you!

Hey i have this issue, how did yo resolve it?
Regards, Gabriel!

There is an existing open ticket and looks like Microsoft is investigating the Visual studio issue.
https://developercommunity.visualstudio.com/content/problem/963269/hotrestart-unable-to-deploy-application.html?childToView=975818#comment-975818
Since it’s a VS issue and document I have closed the issue here. No known solutions till now.😞

Visual Studio Feedback System, 20200520:
A fix for this issue has been internally implemented and is being prepared for release. We'll update you once it becomes available for download.
Continue on https://developercommunity.visualstudio.com/comments/1041598/view.html


Rename relevant occurences of MeshBoundingBox to GetMeshBoundingBox

Changes
The MeshBoundingBox function does not exist, so I've renamed some of the occurences of the function to GetMeshBoundingBox.

@PtitLuca thank you very much for the update! Actually, there are several functions that have been renamed lately, I'll update some of those files for next release.


Download server issues with new MangaDex@Home

Describe the bug
Chapter in question, Series 18734 chapter 29 (185017).
With some chapters, if you attempt to get information from the mangadex api like so "https://mangadex.org/api/chapter/185017" you will get the general json information page with some server url like "s2.mangadex".
But if you do it without an user-agent, you receive another server url like this one "https://tje23x26yczcr.tceq6s3bnjcyj.mangadex.network:443/data/", which Mango fails to connect to.
I actually don't know if this is a Mangadex or Mango issue, since i cannot seem to get the image from that url either.
Firefox just says "The image 'X' cannot be displayed as it contains errors."

[WARNING] 2020/06/09 12:07:51 | Failed to download page https://mactzbskc0zxm.ztxvgq2d6yc0e.mangadex.network:5535/data/7251260e9126852d439081eb6f7bc035/x1.png. Retrying... Remaining retries: 3
[ERROR]   2020/06/09 12:07:58 | SSL_connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

To Reproduce

Download chapter 29 of series 18734

Expected behavior
I would expect it to successfully download
Environment (please complete the following information):

OS: Manjaro Linux 20.0.3
Browser: Firefox 77.0.1
Mango Version: 0.5.2

Yeah, I am starting to get the same error today. Mango does use a user-agent when communicating with the API (see here). In my experience this issue goes away after some time, and I am not sure what triggers it. I will investigate and see if there's anything we can do. I don't like making Mango look like a real browser by setting fake values in the user-agent, so that would be the last resort.

It looks like MangaDex only returns the real server URL when the user is logged in. Try accessing https://mangadex.org/api/chapter/185017 in a private window and you will get the wrong URL. Unfortunately, Mango does not support MangaDex login. I will have to implement this feature if the problem persists.

It seems this is their new MangaDex@Home initiative, and is a server sided issue.
But we should still refresh the chapter index as to get a new "server" if the current one is unresponsive.

Yeah, I noticed that too, but the solution sounds a bit hacky. I will focus on this and hopefully we can get the login functinality in the next version!

I dont think login in fixes this, as i tried getting "One Punch Man" chapter one while logged in, and it gave me a @Home address, but i did figure out how to login (with python not crystal though).
import requests

url = "https://mangadex.org/ajax/actions.ajax.php?function=login&nojs=1"
data = {
	"login_username": "USERNAME",
	"login_password": "PASSWORD",
	"two_factor": "",
	"remember_me": "1",
}

req = requests.post(url, data)
print(req.headers)
print(req.headers["Set-Cookie"])

Where the response header contains a Set-Cookie with a "mangadex_session=X;" line, which is the session id.
This might be useful for the on-by-default data compression, but not for fixing @Home.

I dont think login in fixes this, as i tried getting "One Punch Man" chapter one while logged in, and it gave me a @Home address

I just tested it and https://mangadex.org/api/chapter/67377 always returns the real server URL when logged in. Are you sure you are sending the correct session ID in the header when making the request?
Thanks for investigating the login API. I will work on this in the coming weekend.

I just logged into Mangadex, went to chapter 1 and copied the image source, and it originated from @Home. So im pretty sure its just a regional difference, and logging in does not ensure that its consistently from the original source.

@flying-sausages Thanks! Here's what they said

Long story short, this bug has been fixed, but that node owner hasn't updated his node
try another node

So it's a temporary issue on their side. Closing.


disable the iam-assuable-role and used resource to create it

@uchinda-sph pls update the role reference in the lambda.


Do not create issues for CI failures

Description
Let's skip issues creation for now. We collected list of improvements so we need to work on it and then enable this feature.

/retest

/retest

wtf OpenShift CI can't you give me an image or what?
/retest

/test images


[deemix] Add Deemix chart

Description of the change
Added new chart for Deemix, the barebone deezer downloader. Specifically for the deemix-docker container which provides deemix-gui over HTTP.

Benefits
Makes it easy to install Deemix on Kubernetes

Possible drawbacks
Not sure if renovate understands the weird appVersion / tag versioning format.

Checklist

[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Chart version bumped in Chart.yaml according to semver.
[x] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[x] Variables have been documented in the values.yaml file.

LGTM :) Thanks for submitting this PR!


Image padding

2 minor padding issues highlighted in yellow:

Also the checkbox in this page get's clipped oddly:

The refresh icon get's clipped on the left when refreshing
The confirmations success text needs some padding to stop clipping the right edge

Second screen is ok, because this is our "checked" icon ;) - https://github.com/ETCDEVTeam/emerald-svg-icons/blob/master/icons/check1.svg

resolved now.


Debug Console: ANSI color escapes garbled in console output

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.94.0
OS Version: Windows 11 23H2

This problem started after updating to newest version today.
Steps to Reproduce:

Create a launch configuration (mine is below, runs pnpm run dev launches Vite)
Run launch configuration
Look at Debug Console, output is garbles

    {
      "name": "Debug Vite/SvelteKit",
      "type": "node",
      "request": "launch",
      "cwd": "${workspaceRoot}",
      "env": {
        "NODE_OPTIONS": "--inspect --enable-source-maps"
      },
      "runtimeExecutable": "pnpm",
      "runtimeArgs": [
        "run",
        "dev"
      ]
    }

Cheers!

+1
Happening in c# as well.

I'm facing this issue too. I had to roll back to 1.93.1.

I thought it was my setting make it break. it because vscode version 1.94.0 ??

Yes confirmed its the update :-) You can either revert or wait for a hotfix.

waiting too

Same problem here.

The funny bit is the only application that I found to be affected by this is gh cli :) --- Where it does break the title of the pull requests when trying to create a new PR.

The weird characters in the title are caused by the latest version of vscode. Clear regression, older versions worked fine.

@ssbarnea your issue is unrelated, this bug only impacts certain output displayed in the Debug Console

Fixed in js-debug nightly https://github.com/microsoft/vscode-js-debug/?tab=readme-ov-file#nightly-extension which will be available in an hour or two. I'll also put this in as a candidate.

Same issue with NestJS (Node, TS) project: TypeORM query logging became messed up.
Please fix asap!

Same issue with GO.
This
package main

import "fmt"

const (
    Red    = "\033[31m"
    Green  = "\033[32m"
    Yellow = "\033[33m"
    Blue   = "\033[34m"
    Reset  = "\033[0m"
)

func main() {
    fmt.Println(Red, "This is red text", Reset)
    fmt.Println(Green, "This is green text", Reset)
    fmt.Println(Yellow, "This is yellow text", Reset)
    fmt.Println(Blue, "This is blue text", Reset)
}

prints this

Here is my build

This is fixed in VS Code Insiders, and users of the JS debugger who hit this can also use js-debug nightly. We will put out a stable release with this fix next week.


Genes are not used on plots

@phyllers Can you expand on how this might work better

This screenshot shows how one would select the variable they're interested in.

This screenshot shows how the variable they selected in the previous screenshot would appear in the plot settings. Where a new select box would appear with the genes that they have as their sources.

Accomplishing this would require a lot of extra work. Separating the selectable variables from the current feature definitions will be tricky.
Some data types do not use genes, like methylation. That uses probes which is something that we would not have a filter for outside of the variable selection.

Do you think some form of this could be ready by Monday? I'm trying to understand what's left to do before our release. Thanks!

Looks good. I added a small fix so that the colour_by select box is populated by the selected x and y axis, but also the common variables.


Add support for Near Field Communication (NFC)

With services like Apple pay and Google pay NFC is going mainstream as a way to make payments with mobile devices, it would offer a familiar UX to new lightning users if payments via NFC were supported in mobile lightning wallets.
I developed a PoC for this using a modified version of  zap-android and would like some feedback and (hopefully) help and support in bringing this into the project which I believe would give it a good USP.
Check out the  [Https://GitHub.com/runcrypto/static-discharge](project repo) and [Https://GitHub.com/runcrypto/zap-android](modified zap repo) to see what I've managed to do so far.

Hi Hawkmauk,
That is something I definetly want to have in Zap. I have no experience with NFC so far, but I will have a look at your implementation in the next days :)
Thank you very much!

There are a few details that still need to be worked on which is some of the additional help that would be needed .. ontop of this being my first foray into android development.

There isn't a formal spec for the message format that needs to be sent.  Ndef messages are sent over NFC with a URN header that specifies the service the message is intended for.  The URN would need to be agreed.
I believe from conversations over the last couple of days, that some other implementations already have NFC integration but using a LNURL encapsulated in a url Ndef message that might be worth considering.
How should the NFC functionality be included and what should the workflow be through the Zap app?

Sorry, I was very busy the last two weeks with my job, so I didn't find the time to explore this. But I should be able to do this till the end of the year.

Same here but hope to do some more over the next week when I have some time off

Hey,
I just had a short look at it and wanted to test it, but I do not know how to do so.
If I use a second phone, both have NFC activated, then just the android Beam stuff starts.
What do I need to test this?
Furthermore I saw in my NFC settings that there is a "Tap and Pay" section where one can set the default Payment provider. Maybe we somehow have to get on that List with Zap.

The setup I had was with a Raspberry Pi but two android phones would be simpler to setup... unfortunately I only have one NFC enabled android phone.
There is an app called NFC Tools that is useful and should be able to provide the functionality to test:

Navigate to the WRITE tab
Click on Add a record
Select Text
Paste in a lightning invoice to the textfireld and click OK
Click on the More options menu.
Select Emulate an NFC tag (beta)
Present 2nd Android phone to 1st phone to transfer invoice

Thanks for the info.
I tried, but the emulation doesn't seem to work. I am not able to read the emulated NFC Tag even if I try to read it using the NFC Tools app on the other phone. I also switched phones and emulate on the other and even with another NFC Tag emulation app. But no luck so far.

Hi,
I received my tags and with them it worked!
So I did some tests and further reading.
The intent in the manifest should not be of type text in my opinion. Instead it should be:

And I think we should support both, normal lightning and LNURL request via nfc.
But LNURL is completely independent from nfc. Nfc just transmits the data.
When LNURL support is added, it should make no difference if the data comes from scanning a QR-Code or from reading a nfc tag.
So all we need to do regarding nfc is read the data and then start the intent that handles transaction data.
In your current implementation the tag information gets "lost" if the app is either not open at all or on another activity than the home activity. In that case the app just opens / goes to the home screen and then the tag has to be scanned again.
This is of course not ideal and will have to be changed.
Furthermore, I think in the current state we do not need this permission:
android.permission.NFC_TRANSACTION_EVENT
in my tests it worked without it.

#163 got just merged. NFC Support will be in the next release.


lighthouse to support authenticated catalog api

Hey, I just made a Pull Request!
lighthouse to support authenticated catalog api
:heavy_check_mark: Checklist

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

fixes #17248


Black-body emission not working unless emission color is non-black in asStandardSurface

In the asStandardSurface material, if emission color is pure black (zero), then black-body emission is disabled. Any non-black emission color makes black-body radiation work correctly.

@dictoon I think this can be closed now 🙂

Indeed, thanks!


CASMINST-6815 add step to IUF preparation to save system status

Description
A step has been added to the IUF preparation stage to record system status before an upgrade/install is done. Things that are recorded are SAT status, SAT site information, HSN status, Ceph status, and SDU and RDA configurations. This information will be saved in '/etc/cray/upgrade/csm/system-status/'.
I have added a script called pre-upgrade-status.sh to gather all of this information and save it in a directory.

Checklist

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.5


Arrow function expressions followed by regular expressions are not parsed correctly

Example code:
var foo = () => { return bar }
/regex/.test('baz');

// Using acorn 4.0.3

require('acorn').parse("var foo = () => { return bar }\n/regex/.test('baz')");
// -> SyntaxError: Unexpected token (2:7)

It looks like the leading / in the regular expression is getting parsed as a division operator. However, I don't think this is correct -- Chrome and Firefox both parse this without any errors.

Interestingly,
var foo = function() { return bar }
/regex/.test('baz');

gives a syntax error on both Chrome and Firefox.

@not-an-aardvark I believe it is a correct behaviour. By spec there's no ASI here, therefore/ is treated as continuation of expression, so division operator.
To fix it simply add semicolon  after foo definition.

I don't think the behavior is correct; even without relying on ASI, you can't do division with an arrow function expression anyway:
var foo = () => { return bar } / 5; // SyntaxError on Chrome and Firefox

I'll try to find the relevant portions of the spec a bit later.

My analysis of the spec, as applied to this text:
() => {} / 5 // this is a parsing error in Chrome/Firefox, but not acorn.

A division expression is a type of MultiplicativeExpression (source).
The left side of a MultiplicativeExpression must be another MultiplicativeExpression (source). Therefore, if the text is a valid division expression, () => {} must be a MultiplicativeExpression.
A MultiplicativeExpression can either be an ExponentiationExpression or a production that contains a MultiplicativeOperator (*, /, %) (source). The arrow function () => {} does not contain any MultiplicativeOperators, so if the text is a valid division expression, () => {} must be an ExponentiationExpression.
An ExponentationExpression can either be a UnaryExpression or a production that uses the ** exponentiation operator (source). The arrow function () => { return bar } does not contain the ** exponentiation operator, so if the text is a valid division expression, () => {} must be a UnaryExpression.
A UnaryExpression is either an UpdateExpression or another UnaryExpression preceded by the operator delete, void, typeof, +, -, ~, or ! (source). () => {} is not preceded by any of those operators. Therefore, if the text is a valid division expression, () => {} must be an UpdateExpression.
An UpdateExpression is either a LeftHandSideExpression or something that uses the ++ or -- operators (source). () => {} does not use the ++ or -- operators, so if the text is a valid division expression, () => {} must be a LeftHandSideExpression.
A LeftHandSideExpression is either a NewExpression or a CallExpression (source).
NewExpression
1. A NewExpression is either a MemberExpression or a production that uses the new keyword (source). () => {} does not use the new keyword, so if () => {} is a NewExpression, it must also be a MemberExpression.
1. A MemberExpression is either a PrimaryExpression or a production that uses bracket-notation access, dot-notation access, tagged template syntax, the super keyword, the new.target metaproperty, or the new keyword (source). () => {} does not use any of the last 6 productions, so if () => {} is a MemberExpression, it must also be a PrimaryExpression.
1. A PrimaryExpression is either this, an identifier, a null/boolean/string/number literal, an array literal, an object literal, a FunctionExpression, a ClassExpression, a GeneratorExpression, a regex literal, a template literal, or a CoverParenthesizedExpressionAndArrowParameterList (source). () => {} is none of these. (A FunctionExpression in the spec only refers to functions with the function keyword (source), and a CoverParenthesizedExpressionAndArrowParameterList only refers to the parenthesized arguments of an arrow function, not an arrow function itself (source). Therefore, () => {} is not a PrimaryExpression, so it is not a MemberExpression, so it is not a NewExpression.
CallExpression
1. A CallExpression is either a MemberExpression followed by Arguments, a SuperCall, a CallExpression followed by Arguments, or a production involving dot-notation access, bracket-notation access, or a template literal. (source). Arguments always end with a ) character (source). () => {} does not end with a ) character, so it is not a MemberExpression followed by Arguments or a CallExpression followed by Arguments. () => {} does not have any of the characters ., [, or `, so it cannot contain any of the last three productions. It also can't be a SuperCall, since a SuperCall always contains the super keyword (source). Therefore, () => {} is not a CallExpression.
Since () => {} is not a valid NewExpression or CallExpression, it is not a valid LeftHandSideExpression. Therefore, () => {} / 5 is not a valid division expression, so the syntax is invalid.

So there are two bugs in acorn here:

This should be a SyntaxError, but acorn parses it without any errors.

() => {} / 5

This should parse successfully, but acorn fails to parse it. (Parsing the / as a division operator would not result in a valid grammar production, so a semicolon should be inserted.)

() => {}
/regex/.test('foo');

Interesting; so what the argument boils down to is that, unlike a FunctionExpression, an ArrowFunction is not a PrimaryExpression but an AssignmentExpression (cf. http://ecma-international.org/ecma-262/7.0/#prod-AssignmentExpression).

I agree -- thanks for the detailed reasoning. Attached patches should help.


Adding Mix Plugin README

This contributes to #7175

The completion list wasn't necessary but the rest is awesome. Thanks!


Allow ordering of statuses in the update status form on submissions

Now the statuses are sorted be the machine name (key) of the status, e.g "post_review_discussion". This looks very arbitrary to a human.
The overall goal is to have the first option be the most common one and the rest to be in some logical order.
Would it be possible to get the status in the same order they are set in "transitions" for each status? Then we could manually order them there to have them in the most social order, I think they already are in decent shape for that.
https://github.com/OpenTechFund/opentech.fund/blob/3d2e02a16e38894282ebf2f5f79eab405a61c784/opentech/apply/funds/workflow.py#L194-L200
The default now is almost never the right one now so if staff is a bit too quick the wrong status is often set.

@Parbhat @todd-dembrey Any good ideas on this?

@frjo Django fsm's method get_available_user_FIELD_transitions return transitions sorted by transition name. For custom order, we can sort it again here. It will need an order with value say 3 to each phase dictionary like:
    {
        'internal_review': {
            'transitions': {
                INITIAL_STATE: 'Screening (back)',
                'post_review_discussion': 'Close Review',
            },
            'display': 'Internal Review',
            'public': 'OTF Review',
            'stage': Request,
            'permissions': default_permissions,
            'order': 3,
        },
    },

Based on the value of the order for each phase we can update the status form choices list.

@saoun @fourthletter This is not something OTF has asked for but I believe it has been a problem non the less.
The issue is the order that the statuses are listed in the "Update status" form on submissions. The one OTF staff use every time a submission need to change state.
I believe there would be less mistakes if the first status is the most common one and the rest follow a logical order.
All the workflows with states and transitions are setup in the workflow.py file like this:
https://github.com/OpenTechFund/opentech.fund/blob/fe9bab2040478a1cca4d116082a6712b32ba0812/opentech/apply/funds/workflow.py#L191-L817
The PR I created sorts the status popup meny the same way the status is listed in "transistion" for each status.
I have ordered the transitions in a way that look good to me but please have a look and see what you think.
You test on the test site at https://test-apply.opentech.fund

I think this works on my end. Just tested. But since I'm not the most familiar with the flow of an application right now, better for @danblah or @fourthletter to check also


Firebase Performance Monitoring seems not to work

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
I integrated Firebase Performance Monitoring in my application;
https://firebase.google.com/docs/perf-mon/get-started-ios
What did you expect to happen?
I expected that all my network calls are monitored and logged in Firebase.
What happened instead?
All network calls where I use Alamofire for, aren't logged.
There are some known issues, it's in beta. But in the list of known issues I don't see something that could cause the problem for al 'Alamofire-calls'. Only the issue about NSUrlSession delegation is a possible cause. But I did a, quick, look in the Alamofire code, but I don't think this can be it.
I'm wondering is someone can explain what could be the problem.
Alamofire Environment
Alamofire version: 4.5.1
Xcode version: 9.1
Swift version: 3.2
Platform(s) running Alamofire: iOS
macOS version running Xcode: 10.13.1

I would suggest opening this issue with Firebase. I have no idea how that framework works, so I have no way of judging whether or not it should be working with Alamofire. I'd think yes, but perhaps there's some interaction with Swift the framework doesn't handle? I really don't know. They should be able to answer such questions.

I have exactly this same question. We recently started adding Firebase analytics to our app, but Alamofire calls are not being monitored, while other http(s) calls are.
Did anyone get around opening this issue with Firebase? Any reference or links we can monitor?

Yes, I got this response from Firebase Support:

Hi Martijn,
Thank you for reaching out.
Apologies, but Alamofire is not something we officially support and I'm not familiar enough with that library to help troubleshoot. Kindly note that we cannot guarantee that these third-party libraries will work properly with Firebase as they are not maintained by the Firebase Engineers.
One thing to check would be to remove Alamofire and try using NSURLSession API and see if the network requests are being logged.
I would recommend that you reach out to a developer community such as Stack Overflow where fellow developers can help you out.

After updating my pods this started to work. An extract from my podfile.lock:
  - Alamofire (4.6.0)
  - AlamofireObjectMapper (5.0.0)
  - Firebase/Core (4.7.0)
  - Firebase/Crash (4.7.0)
  - Firebase/Performance (4.7.0)
  - FirebaseAnalytics (4.0.5)
  - FirebaseCore (4.0.12)
  - FirebaseCrash (2.0.2)
  - FirebaseInstanceID (2.0.7)
  - FirebasePerformance (1.0.7)
  - FirebaseSwizzlingUtilities (1.0.0)


import for wine_pasta.owl seems to break XML parsing

This imports statement in foodon.owl seems to break XML parsing:
<owl:imports rdf:resource="http://purl.obolibrary.org/foodon/imports/wine_pasta.owl"/>

On June 1, it was changed to
 <owl:imports rdf:resource="&obo;foodon/imports/wine_pasta.owl"/>

but it was for some reason reverted on July 1. Is there any way it can be fixed?
I've tried parsing the foodon.owl (the master branch version) using robot and owltools, and both fail.

Thanks for bringing that to my attention.  I can see the import file was missing an /obo/ path in file which was manually adjusted but not in the instructions for redoing it which happened last month.  I've fixed that now, so let me know if you have issues parsing it again...

I presume this is resolved now?

Closing unless further comment.

Thanks, I will test it tonight in our workflow:
https://github.com/RTXteam/RTX/tree/master/code/kg2

Confirmed, it is working now.  Thank you.


Publication quality hulls

To facilitate sharing screenshots and using the ontology viewer for publications, better, sharper hulls and layout will help.
For example, via: https://www.sciencedirect.com/science/article/abs/pii/S0092867421005018

h/t Norbert Tavares

One of the challenges with hulls are orphan nodes — where do we 'send' nodes that are no longer linked. In a force layout, we can give them an xy destination, which would be interesting if we want to prevent orphan nodes from flying around and making the hull bigger than is desirable.


Request: Theme Shop

It would be cool if Gitea had a website or repo where people could download and contribute to themes for Gitea.

A theme is a zip package which contains the css/less files and some custom golang template files. Js files should not be allowed currently for security consideration.
There is an entry file which could be named main.yml which contains all the meta informations which the theme needed. Css/less/template files location have been references as a relative path on the main.yml.
All possible informations:

File version, currently always 1. Once we have another file format, we may use 2.
Name: the theme name.
Type: theme. We may have another type like plugin.
Version: the version of the zip package.
Required gitea version
Authors: name
Website link
Avatar: reversed word.
Screenshots: which maybe displayed on the market and the gitea instance if online mode enabled.
Css/Less files path
Template files path

Gitea could have a feature to install a theme by administrator on admin panel by upload a theme package file or install it from the URL online.
When installing a theme, the theme information should be stored in database table maybe named theme or plugin(A theme is also some kind of plugin).  All needed files should be copied to the location where the themes stored currently. And also gitea should reload all the themes.
A theme could be also uninstalled.

Still that would not solve the fundamental issue that if we introduce new colors in the base theme, it breaks all existing themes.
.some-selector {
  background: #fff;
}

Now all themes break with this unless they copy that selector and override the rule. I think for themes to be actually feasible, we need:

All colors to be defined in CSS variables
(Optionally) Let the theme have its own remap-css configuration options so they can benefit from auto-generated selectors. This probably means a theme needs to be either a JSON or JS file.

@silverwind  So we could have some gitea versions on the theme. If the theme isn't matched gitea's version it will be disabled automatically. Only remap-css will limit the ability a theme could do. I noticed some themes need customerized templates.
And we should also consider how a theme creator to develop a theme with a gitea binary instance easily.

Actually I don't think we even need to expose remap-css config. We can just have it generate the CSS variables out of the gitea theme, overriding the fomantic rules (which in itself is around 150kB of CSS) which then can be overridden again by the theme and that way, the theme could stay pure CSS.


[Feature Request] Color Picker

Is your feature request related to a problem? Please describe.
Hello everyone. I have been using this library for a long time. I love this. But i need color-picker at some project. I think the process of creating the ColorPicker component is conceivable.
Describe the solution you'd like
New Component
Describe alternatives you've considered
None
Screenshots or Videos
No response

Can your give some idea/reference/example what sort of color picker  you want @gokhangunduz

I think the best reference;
https://primereact.org/colorpicker/

Hi, any progress ? I'm looking forward to. Thanks @abhinandan-verma

@gokhangunduz  currently the team is busy with zigma,
And I need their acceptance for any new component, i will inform youe soon, once the team gives acceptance for the component:)


Write a Java program to convert string to snakecase

Description
Write a Java program to convert string to snakecase
Snakecase is a style of writing in which all letters are lowercase and spaces are replaced with underscores.
Input  : "hello world"
Output : "hello_world"

How to contribute

Save the solution in program/ConvertStringToSnakecase.java file
Add ConvertStringToSnakecase.java file in convert-string-to-snakecase folder

!assign

!assign


Fixing the mapping bug

This should fix the mappings bug.
Now the newly added function _construct_full_path(), checks if the input path is a full path and, if not, converts it to it.
The assumption is that the relative path takes as cwd the selected directory (i.e. self.directory).

i think this version explicitly asks for the presence of the mapping.csv file?

Not necessarily, I made it so that if the file mappings.csv exists (if clause in line 195) then uses that for mapping images and masks, otherwise (else clause in line 205) uses the original fetching logic, i.e. files need to be named correctly with the suffixes _img.nii and mask.nii.

restructured logic a bit in the new commit - with support of no masks, closing the PR https://github.com/zapaishchykova/SegmentationReview/commit/a22eb7b5d2c1b1d348520bd24eb875f1c7ac70db


Darn it, I broke CI due to multiple declarations

Signed-off-by: John Howard<EMAIL_ADDRESS>Darn, darn, darn. Yes, I broke it. Each of my previous PRs was good on its own, just not all together as each declared the same variable. Sorry! Please merge quickly.

LGTM if janky is happy

LGTM :smile:

Just realized the same ;-) I'm fixing this in a branch to refactors the usage of sleeping containers.
Of course LGTM.

#IAmStupid :sob: Yes, this fixes the multiple declarations and gets past the failure. I've taken all the WindowsTP4 CI nodes offline temporarily to avoid false failures until this is merged.  Sorry everyone. I'll sleep in the dog crate tonight, and they can have my bed. Think I deserve it!

@vdemeester As I'm sure you'll be up soon. This fixes CI on master. My bad :cry:

We don't expect any surprise with gccgo: merging.

Yes, back to green. Please, please, please merge.

@jhowardmsft no harm done, sh*t happens, thanks! Now, let that poor dog back in its crate :smile:

Seems to happen in "real" world, too - https://twitter.com/thepracticaldev/status/687672086152753152
:smile:


Provide c-icon to files with .C extension

Add ".C" extension to the list of C file extensions

I really wish Less would support case-insensitive attribute selectors. Seriously.


Is it possible to make the onHandle in hooks.server.js a async function?

For other modules I need to add await statements in the hooks.server.js. How do I make the onHandle function async?

Thanks, this is how it works. Another question, do you have any idea why on dev still errors go to sentry even though I set enableInDevMode: false in the serverInit of hooks.server.js?

I am aware of this phenomenon as a bug, but have not been able to resolve it.
For the sake of transparency, I would like to Open the following Issue and begin addressing it.
Issue #91


Yandex transport issue

Home Assistant release with the issue:
0.100.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Raspberry Pi 3
Hass.io Version | 192
System | HassOS 2.12
Integration:
https://www.home-assistant.io/integrations/yandex_transport
Description of problem:
Log Details (ERROR)
Sat Oct 26 2019 15:20:42 GMT+0300 (Moscow Standard Time)
Error while setting up platform yandex_transport
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/yandex_transport/sensor.py", line 44, in setup_platform
    data = YandexMapsRequester(user_agent=USER_AGENT)
  File "/usr/local/lib/python3.7/site-packages/ya_ma.py", line 55, in __init__
    self.set_new_session()
  File "/usr/local/lib/python3.7/site-packages/ya_ma.py", line 84, in set_new_session
    rf'"{CSRF_TOKEN_KEY}":"(\w+.\w+)"', reply
AttributeError: 'NoneType' object has no attribute 'group'

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
configuration.yaml
packages: !include_dir_named packages

packages/components/component_yandex.yaml
sensor:

  - platform: yandex_transport
    stop_id: XXXXXXX
    name: NameXXX
    routes:
      - XXXX

Traceback (if applicable):

Additional information:

Looks like a problem with service rate limiting https://github.com/rishatik92/ya_ma/issues/2

Sorry for duplicate


How to set the parameters target and name and use the pre-training parameters？

Thank you very much for your work, but I have two questions: First, there are target and name in the parameter. I see that the name is very complicated, and I would like to ask what rules are followed in the setting of it? Second, I saw in the previous reply that the training is divided into two stages, but when I loaded the pre-training parameters you shared, it was not successful.

Hi @shumile66 ,
Thanks for your interests!

Is it the name in optimizers_and_schedulers that your are confused? It is used to train GAN like models, where two (or more) different parts need to be trained in different iterations. Once the name is provided, the model will return the corresponding patameters acoording to the given name throhg the overwritten function parameters(self, recurse=True, name=None) (Please take image_synthesis/modeling/codecs/image_codec/patch_vqgan.py as an example). After getting the parameters need to be trained, Solver will create different optimizers for different part parameters.
https://github.com/liuqk3/PUT/blob/7de8ce0ada1e63e8c5300857a463d68380e142f0/image_synthesis/modeling/codecs/image_codec/patch_vqgan.py#L1137

Did you download the pretrained model from OneDrive or BaiDuYunPan? Due to some mysterious reasons, I failed to upload the models to BaiduYunPan. You can download them from OneDrive.

Thansk.