Provide posiblity to define if sourcecode.zip and/or binaries.tar shall be fetched from storage

Situation
This is a kind of sub issue of #729,  #1098 but mainly of #1166
At the moment, every code scan will insist on fetching SOURCE.zip from s3.
Because we introduce BINARY.tar for binary uploads, we must have a possibility to define which one shall be handled
Wanted
We introduce new configuration entries
Solution

Introduce new enum StorageType with SOURCE and BINARY inside
Introduce StorageSupport class which will provide logic to fetch streams automatically and also to
handle missing mandatory storages (depending on type)
PDS shall use the the runtime product executor configuration to determine the supported data storage types

we introduce: pds.storage.datatypes.accepted=$content. Content can be a combination of SOURCE,BINARY
we introduce: pds.storage.datatypes.mandatory=$content. Content can be a combination of SOURCE,BINARY
when no data type is defined the default will be defined by the dedicated PDS product executor classes (e.g. a PDSCodeScanProductExecutor will per default insist on SOURCE`

CheckmarxProductExeuctor will always insist on SOURCE` and is not configurable at runtime

Some of the parts are already done - but the configuration if a PDS does need sourcecode and/or binaries is still missing.
This is import for #1744


fix: replace removing the addTrailingSlash with removeTrailingSlash and deleted installOptions.alias options

Changes
Deleted intsallOptions.alias options and Replace removing the addTrailingSlash with  removeTrailingSlash, some discussion related to https://github.com/snowpackjs/snowpack/pull/1006

Testing
All tests have been passed.

Docs
The docs have been updated.

LGTM, the less tricky we can make these inputs and the more we can clean them for the user, the better


Alexa can get events from the previous day

Sometimes Alexa will get events from the a day prior to the given date(s) that the user wants to hear about. In the past we have had similar issues, and the solution was to add ::timestamp at time zone 'America/Los_Angeles' to the end of the dates that we were using in our queries. Below is an example of an interaction that causes Alexa to get events from the wrong day.

User: What is happening on November fourteenth
(Note, the fourteenth is a Monday)

Alexa: I was able to find 15 different events on Monday, <say-as interpret-as="date">????1114. What kind of events would you like to hear about?

User: All of them

Alexa: Cool. Here are the  events that I was able to find. On Sunday, <say-as interpret-as="date">????1113 there is , Sonoma Film Institute at <say-as interpret-as="time">4:00 PM, Alpha Xi Delta Chapter Meeting Fall 2016 at <say-as interpret-as="time">5:00 PM, Fall 2016 Gamma Phi Beta Chapter Meeting at <say-as interpret-as="time">6:00 PM, Phi Delta Theta Weekly Chapter Meeting at <say-as interpret-as="time">6:00 PM, Alpha Psi Chapter Meeting Fall 2016 at <say-as interpret-as="time">6:00 PM, Alpha Gamma Delta Fall 2016 Chapter Meetings at <say-as interpret-as="time">7:00 PM, Intermural Basketball at <say-as interpret-as="time">7:00 PM, Phi Sigma Sigma Chapter Meeting at <say-as interpret-as="time">7:00 PM, Pi Kappa Phi Chapter Meeting Fall 2016 at <say-as interpret-as="time">7:04 PM, Intermural Indoor Soccer at <say-as interpret-as="time">8:00 PM, Alpha Psi New Member Meeting Fall 2016 at <say-as interpret-as="time">8:00 PM, and Kappa Delta Zeta New Member Meeting at <say-as interpret-as="time">8:30 PM. On Monday, <say-as interpret-as="date">????1114 there is Fall 2016 Monthly Nursing Club Meeting at <say-as interpret-as="time">10:00 AM, Bible Club at SSU Bible Study at <say-as interpret-as="time">11:00 AM, and Women's Ultimate Frisbee Club Meetings at <say-as interpret-as="time">12:00 PM.

Lambda Request JSON after the user says "All of them":
{
  "session": {
    "sessionId": "SessionId.af1437ba-f1be-42c6-acde-b9984d7c4171",
    "application": {
      "applicationId": "amzn1.ask.skill.68a28ff8-30a5-493e-8e11-fca2cb138d6c"
    },
    "attributes": {
      "recentlySaidEvents": {
        "Fall 2016 Monthly Nursing Club Meeting": 209,
        "Alpha Xi Delta Chapter Meeting Fall 2016": 199,
        "Alpha Psi Chapter Meeting Fall 2016": 200,
        "Phi Delta Theta Weekly Chapter Meeting": 202,
        "IMS Basketball": 99,
        "Phi Sigma Sigma Chapter Meeting": 205,
        "Sonoma Film Institute": 26,
        "Alpha Psi New Member Meeting Fall 2016": 207,
        "Pi Kappa Phi Chapter Meeting Fall 2016": 206,
        "Women's Ultimate Frisbee Club Meetings": 211,
        "AGD Fall 2016 Chapter Meetings": 203,
        "Bible Club at SSU Bible Study": 210,
        "KDZ New Member Meeting": 208,
        "IMS Indoor Soccer": 100,
        "Fall 2016 Gamma Phi Beta Chapter Meeting": 201
      },
      "stateId": "LIST_TOO_LONG",
      "savedDate": {
        "relativeDate": "Monday, <say-as interpret-as=\"date\">????1114</say-as>",
        "relativeDateWithPreposition": "on Monday, <say-as interpret-as=\"date\">????1114</say-as>",
        "begin": "2016-11-14",
        "end": "2016-11-15"
      }
    },
    "user": {
      "userId": "amzn1.ask.account.AGUBCBZQXDWUBLXZHDQPT2U77RUUKFW7JWE5TRFZ6UH62H47ZP43CRKNOLYE27GK6BF2FUOJF3UTBBMI4ET4WEIWVPMPH72MGCLKVBORDBGU6O6PFXCD33S2R6GKKXI426Y4XI4RGJ4ULN3J2I3EVHNPJK2ELLUTGLLUFY26C3U6FDUKLID5ZP7EX4TS6JTKKWQKJUDBSI4DRAQ"
    },
    "new": false
  },
  "request": {
    "type": "IntentRequest",
    "requestId": "EdwRequestId.6cfa0d7f-3bfe-4120-b10f-dce5cec3c107",
    "locale": "en-US",
    "timestamp": "2016-11-11T03:08:31Z",
    "intent": {
      "name": "AllCategoryIntent",
      "slots": {}
    }
  },
  "version": "1.0"
}

Lambda Response
{
  "version": "1.0",
  "response": {
    "outputSpeech": {
      "type": "SSML",
      "ssml": "<speak>Cool. Here are the  events that I was able to find. On Sunday, <say-as interpret-as=\"date\">????1113</say-as> there is , Sonoma Film Institute at <say-as interpret-as=\"time\">4:00 PM</say-as>, Alpha Xi Delta Chapter Meeting Fall 2016 at <say-as interpret-as=\"time\">5:00 PM</say-as>, Fall 2016 Gamma Phi Beta Chapter Meeting at <say-as interpret-as=\"time\">6:00 PM</say-as>, Phi Delta Theta Weekly Chapter Meeting at <say-as interpret-as=\"time\">6:00 PM</say-as>, Alpha Psi Chapter Meeting Fall 2016 at <say-as interpret-as=\"time\">6:00 PM</say-as>, Alpha Gamma Delta Fall 2016 Chapter Meetings at <say-as interpret-as=\"time\">7:00 PM</say-as>, Intermural Basketball at <say-as interpret-as=\"time\">7:00 PM</say-as>, Phi Sigma Sigma Chapter Meeting at <say-as interpret-as=\"time\">7:00 PM</say-as>, Pi Kappa Phi Chapter Meeting Fall 2016 at <say-as interpret-as=\"time\">7:04 PM</say-as>, Intermural Indoor Soccer at <say-as interpret-as=\"time\">8:00 PM</say-as>, Alpha Psi New Member Meeting Fall 2016 at <say-as interpret-as=\"time\">8:00 PM</say-as>, and Kappa Delta Zeta New Member Meeting at <say-as interpret-as=\"time\">8:30 PM</say-as>. On Monday, <say-as interpret-as=\"date\">????1114</say-as> there is Fall 2016 Monthly Nursing Club Meeting at <say-as interpret-as=\"time\">10:00 AM</say-as>, Bible Club at SSU Bible Study at <say-as interpret-as=\"time\">11:00 AM</say-as>, and Women's Ultimate Frisbee Club Meetings at <say-as interpret-as=\"time\">12:00 PM</say-as>.</speak>"
    },
    "reprompt": {
      "outputSpeech": {
        "type": "SSML",
        "ssml": "<speak>Is there anything you would like to know about those events?</speak>"
      }
    },
    "shouldEndSession": false
  },
  "sessionAttributes": {
    "recentlySaidEvents": {
      "Fall 2016 Monthly Nursing Club Meeting": 209,
      "Alpha Xi Delta Chapter Meeting Fall 2016": 199,
      "Alpha Psi Chapter Meeting Fall 2016": 200,
      "Phi Delta Theta Weekly Chapter Meeting": 202,
      "IMS Basketball": 99,
      "Phi Sigma Sigma Chapter Meeting": 205,
      "Sonoma Film Institute": 26,
      "Alpha Psi New Member Meeting Fall 2016": 207,
      "Pi Kappa Phi Chapter Meeting Fall 2016": 206,
      "Women's Ultimate Frisbee Club Meetings": 211,
      "AGD Fall 2016 Chapter Meetings": 203,
      "Bible Club at SSU Bible Study": 210,
      "KDZ New Member Meeting": 208,
      "IMS Indoor Soccer": 100,
      "Fall 2016 Gamma Phi Beta Chapter Meeting": 201
    },
    "stateId": "USER_HEARD_EVENTS",
    "savedDate": {
      "relativeDate": "Monday, <say-as interpret-as=\"date\">????1114</say-as>",
      "relativeDateWithPreposition": "on Monday, <say-as interpret-as=\"date\">????1114</say-as>",
      "begin": "2016-11-14",
      "end": "2016-11-15"
    }
  }
}

This should be fixed by 1cdcf8112c96342c7d00a489ecf289099efeb88f


Incorrect render for repeated pointerover/pointerout

Description
I've create a very simple application with a custom component that changes colour when you hover over it. If you hover over then off the component everything is fine for the first 12 times but on the 13th the colour states are reversed. It's very strange... not sure if I'm doing something wrong but it's probably the simplest component I could make!
Here's a Codepen demonstrating the issue: https://codepen.io/lewispeel/pen/RwWpbEG
Steps to reproduce

Create a new react app using yarn create react-app test
Install Pixi.js and ReactPixi
Create a simple button component that is red for pointerout and green for pointerover (see below)
Keep hovering over and off the button until the colours are broken (green for pointerout and red for pointerover)
Keep hovering and eventually it'll change back.

// app.js

import React from 'react';
import { Stage } from '@inlet/react-pixi';
import Button from './Button';

function App() {
  return (
    <Stage>
      <Button x={100} y={100} width={100} height={100} />
    </Stage>
  );
}

export default App;

// Button.js

import React, { useReducer } from 'react';
import { Container, Graphics } from '@inlet/react-pixi';

const BG_UP = 0xCC0000; // red
const BG_OVER = 0x00CC00; // green

const initialState = { bgColor: BG_UP };

function reducer(state, action) {
  switch (action.type) {
    case 'over':
      return { ...state, bgColor: BG_OVER };
    case 'out':
      return { ...state, bgColor: BG_UP };
    default:
      throw new Error();
  }
}

export default props => {
  const [state, dispatch] = useReducer(reducer, initialState);

  return (
    <Container
      x={props.x}
      y={props.y}
      buttonMode={true}
      interactive={true}
      pointerover={e => dispatch({ type: 'over' })}
      pointerout={e => dispatch({ type: 'out' })}
    >
      <Graphics
        draw={g => {
          g.beginFill(state.bgColor);
          g.drawRect(0, 0, props.width, props.height);
          g.endFill();
        }}
      />
    </Container>
  )

};

I've tried writing the button component with useReducer and useState but both result in the same error.
Additional info

@inlet/react-pixi version: 1.2.18
React version: 16.13.1
ReactDOM version: 16.13.1
PIXI version: 5.2.2

This is the expected behavior.
The draw call gets executed every frame, make sure to clear it first before redrawing.

Keep in mind that this might be an expensive operation as it gets drawn every frame. There's a PR with a fix to render it based on the React cycle here: #187

Ah ok, thanks for the explanation!


Process crash with "Callback was already called."

Hi there,
I am getting this error.
if (fn === null) throw new Error("Callback was already called.");
                         ^
Error: Callback was already called.
    at /path/to/project/node_modules/async/dist/async.js:903:32
    at /path/to/project/node_modules/async/dist/async.js:2490:13
    at /path/to/project/node_modules/async/dist/async.js:2551:17
    at /path/to/project/node_modules/rascal/lib/amqp/tasks/createConnection.js:24:9
    at /path/to/project/node_modules/async/dist/async.js:4566:26
    at /path/to/project/node_modules/rascal/lib/amqp/tasks/createConnection.js:18:29
    at /path/to/project/node_modules/rascal/lib/amqp/tasks/createConnection.js:32:29
    at /path/to/project/node_modules/amqplib/callback_api.js:16:10
    at /path/to/project/node_modules/amqplib/lib/connect.js:147:12
    at bail (/path/to/project/node_modules/amqplib/lib/connection.js:175:5)

Not sure, how this error is created. No other logs. I am not even sure that this is caused from application code or connection related issue triggered in library code.
Thank you!

Sorry you're having problems. Can you answer the following questions please...

Is this happening when the application is starting or after it's been running for some time?
How often does it happen
Has rascal been working reliably in your application before now?

Thanks

I think it's likely to be this issue with amqplib. I can wrap the callback using lodash.once which will stop async hiding the original connection error.

@cressie176, only today I saw this on one of our staging servers. In production, we did not had any issues like this & also no issues with rascal either. My guess is that the problem is because of the connection to rabbitmq got disconnected & reconnected. Due to this error, the process exited. Our process management tool restarted the process & the error kept occurring till the connection is established. Sorry that I couldn't debug further at the moment.

I've wrapped the callback using lodash.once. Published to npm as<EMAIL_ADDRESS>

Cool. Thank you for providing a solution this quickly.

ok to close?

Sorry. Done!


[Blog Comments] Thesaurus Funnies - 2/14/2016

https://tadukooverse.github.io/blog/2016/02/14/thesaurus-funnies.html

page removed


live audio can not continues

My audio live stream stop in this version (revision: 02e4c5e) . but last version is work fine
seems Manifest doesn't refresh , only once
Manifest has been refreshed at Tue Nov 10 2015 18:22:42 GMT+0800 (台北標準時間)[1447150962581]
flowplayer.mpegdash.min.js:30 SegmentTimeline detected using calculated Live Edge Time
flowplayer.mpegdash.min.js:30 MediaSource is open!
flowplayer.mpegdash.min.js:30 [object Event]
flowplayer.mpegdash.min.js:30 Duration successfully set to: 1.7976931348623157e+308
flowplayer.mpegdash.min.js:30 Added 0 inline events
flowplayer.mpegdash.min.js:30 No video data.
flowplayer.mpegdash.min.js:30 audio codec: audio/mp4;codecs="mp4a.40.5"
flowplayer.mpegdash.min.js:30 [audio] stop
flowplayer.mpegdash.min.js:30 No text data.
flowplayer.mpegdash.min.js:30 No fragmentedText data.
flowplayer.mpegdash.min.js:30 No muxed data.
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 [audio] start
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 0
flowplayer.mpegdash.min.js:30 [audio] Index for time 0 is -1
flowplayer.mpegdash.min.js:30 loaded audio:Initialization Segment:NaN (200, 0ms, 55ms)
flowplayer.mpegdash.min.js:30 [audio] Initialization finished loading
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 0
flowplayer.mpegdash.min.js:30 [audio] Index for time 0 is -1
flowplayer.mpegdash.min.js:30 [audio] Stalling Buffer
flowplayer.mpegdash.min.js:30 [audio] Waiting for more buffer before starting playback.
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30  loadedmetadata
flowplayer.mpegdash.min.js:30 Starting playback at offset: 2304
flowplayer.mpegdash.min.js:30 [audio] seek: 2304
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2304 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 loaded audio:Media Segment:2304 (200, 172ms, 4ms)
flowplayer.mpegdash.min.js:30 [audio] Buffered Range: 2304 - 2314.24
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 Do seek: 2304
flowplayer.mpegdash.min.js:30  seek
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2314.24
flowplayer.mpegdash.min.js:30 [audio] Index for time 2314.24 is 0
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2304 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2314.24 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2324.4799999999996
flowplayer.mpegdash.min.js:30 [audio] Index for time 2324.4799999999996 is 1
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2314.24 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2324.48 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Got enough buffer to start.
flowplayer.mpegdash.min.js:30 [audio] seek: 2304
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2314.24
flowplayer.mpegdash.min.js:30 [audio] Index for time 2314.24 is 0
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2304 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2314.24 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2324.48 / 2364.3590000000004
flowplayer.mpegdash.min.js:30  seeked
flowplayer.mpegdash.min.js:30 Start Event Controller
flowplayer.mpegdash.min.js:30  playing
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2334.72
flowplayer.mpegdash.min.js:30 [audio] Index for time 2334.72 is 2
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2324.48 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2334.72 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 loaded audio:Media Segment:2314.24 (200, 1289ms, 65ms)
flowplayer.mpegdash.min.js:30 [audio] Buffered Range: 2304 - 2324.48
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 loaded audio:Media Segment:2324.48 (200, 971ms, 48ms)
flowplayer.mpegdash.min.js:30 [audio] Buffered Range: 2304 - 2334.72
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 loaded audio:Media Segment:2334.72 (200, 1286ms, 35ms)
flowplayer.mpegdash.min.js:30 [audio] Buffered Range: 2304 - 2344.96
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2344.96
flowplayer.mpegdash.min.js:30 [audio] Index for time 2344.96 is 3
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2334.72 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 loaded audio:Media Segment:2344.96 (200, 1346ms, 70ms)
flowplayer.mpegdash.min.js:30 [audio] Buffered Range: 2304 - 2355.2
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2304
flowplayer.mpegdash.min.js:30 [audio] Index for time 2304 is 0
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] start
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] start
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Stalling Buffer
flowplayer.mpegdash.min.js:30 [audio] Waiting for more buffer before starting playback.
flowplayer.mpegdash.min.js:30  ratechange:  0
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2
flowplayer.mpegdash.min.js:30 [audio] Index for time 2355.2 is 4
flowplayer.mpegdash.min.js:30 [audio] SegmentTimeline: 2344.96 / 2364.3590000000004
flowplayer.mpegdash.min.js:30 [audio] Getting the request for time: 2355.2

https://github.com/flowplayer/flowplayer-mpegdash/commit/02e4c5e52cef3a52934466c9c48578184a5367f3 did not introduce functional changes
http://demos.flowplayer.org/api/dash.html#live still works
does your stream work in the dash.js demo player - http://dashif.org/reference/players/javascript/v1.5.1/samples/dash-if-reference-player/ ? - see also https://github.com/flowplayer/flowplayer-mpegdash#debugging
link to a minimal sample page please, live stream should be on

Our live stream is audio . I try your video live stream is ok  (http://vm2.dashif.org/livesim/testpic_6s/Manifest.mpd)
but audio live stream stop in revision: 02e4c5e
the follow is our manifest.mpd  . I think the different is "SegmentTimeline" as video live
could someone help ?

ch01-test

Apart from the fact that Flowplayer support audio officially, may I ask you again to come back to the last 2 point in https://github.com/flowplayer/flowplayer-mpegdash/issues/7#issuecomment-155387650

how does it behave in the dash.js player 1.5.1 http://dashif.org/reference/players/javascript/v1.5.1/samples/dash-if-reference-player/ ? and, for comparsion in the 1.5.0 player http://dashif.org/reference/players/javascript/v1.5.0/samples/dash-if-reference-player/
sample page or at least working mpd, so we can bisect exactly which revision broke it

Q: how does it behave in the dash.js player 1.5.1
http://dashif.org/reference/players/javascript/v1.5.1/samples/dash-if-reference-player/ ? and, for comparsion in the 1.5.0 player http://dashif.org/reference/players/javascript/v1.5.0/samples/dash-if-reference-player/
A : I try both , they are work
Q:sample page or at least working mpd, so we can bisect exactly which revision broke it
A: OK. i will try to make one
And i try to make a video live stream . the revision: 02e4c5e also stop.
I compare manifest.mpd . I think our manifest.mpd always have "SegmentTimeline" like this.
            <SegmentTimeline>
                <S t="537292" d="197744"/>
                <S d="341180"/>
                <S d="147162"/>
                <S d="229915"/>
                <S d="229915"/>
            </SegmentTimeline>

I think it alwasy generated by WOWZA server (version 4.2.0 build15089) .
But I try some other player like bitdash also works good. any idea or suggestions ?
Thanks a lot.
The follow is full manifest.mpd sample
<?xml version="1.0" encoding="UTF-8"?>
<MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns="urn:mpeg:dash:schema:mpd:2011"
     xmlns:xlink="http://www.w3.org/1999/xlink"
     xsi:schemaLocation="urn:mpeg:DASH:schema:MPD:2011 http://standards.iso.org/ittf/PubliclyAvailableStandards/                              MPEG-DASH_schema_files/DASH-MPD.xsd"
     profiles="urn:mpeg:dash:profile:isoff-live:2011"
     type="dynamic"
     minimumUpdatePeriod="PT1.207S"
     availabilityStartTime="2015-11-11T01:36:55Z"
     timeShiftBufferDepth="PT51.969S"
     suggestedPresentationDelay="PT15.0S"
     minBufferTime="PT6.0S">
<ProgramInformation>
    <Title>ch01-test</Title>
</ProgramInformation>
<Period id="0" start="PT0.0S">
    <AdaptationSet id="0"  mimeType="video/mp4" width="1280" height="720" par="16:9" frameRate="24000/1001" segm                              entAlignment="true" startWithSAP="1" subsegmentAlignment="true" subsegmentStartsWithSAP="1">
        <SegmentTemplate timescale="90000" media="chunk_u0pctug93_ctvideo_cfm4s_rid$RepresentationID$_cs$Time$_m                              pd.m4s" initialization="chunk_u0pctug93_ctvideo_cfm4s_rid$RepresentationID$_cinit_mpd.m4s">
            <SegmentTimeline>
                <S t="2193030" d="807120"/>
                <S d="1392570"/>
                <S d="600660"/>
                <S d="938430"/>
                <S d="938430"/>
            </SegmentTimeline>
        </SegmentTemplate>
        <Representation id="p0a0r0" codecs="avc1.64001f" sar="1:1" bandwidth="627000" />
    </AdaptationSet>
    <AdaptationSet id="1" mimeType="audio/mp4" lang="eng" segmentAlignment="true" startWithSAP="1" subsegmentAli                              gnment="true" subsegmentStartsWithSAP="1">
        <Role schemeIdUri="urn:mpeg:dash:role:2011" value="main"/>
        <SegmentTemplate timescale="22050" media="chunk_uabi90g6w_ctaudio_cfm4s_rid$RepresentationID$_cs$Time$_m                              pd.m4s" initialization="chunk_uabi90g6w_ctaudio_cfm4s_rid$RepresentationID$_cinit_mpd.m4s">
            <SegmentTimeline>
                <S t="537292" d="197744"/>
                <S d="341180"/>
                <S d="147162"/>
                <S d="229915"/>
                <S d="229915"/>
            </SegmentTimeline>
        </SegmentTemplate>
        <Representation id="p0a1r0" codecs="mp4a.40.2" audioSamplingRate="22050" bandwidth="97000">
        <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2                              "/>
        </Representation>
    </AdaptationSet>
</Period>
</MPD>

I found something , if i use the the html5 tag to load .mpd ,  it's work
<video class="dashjs-player" controls>
  <source type="application/dash+xml" src="//example.com/testvideo.mpd">
</video>
</video>

but if i use like this , it will stop after 20 sec
 <div id="mpd-container" class="player"></div>
<script>
                    flowplayer('#mpd-container', {
                      ...
                        clip: {
			   live: true,
                            sources: [
                                { type: type,
                                  src: src
                                }
                            ]
                        }
                    }).on('error', function() {
                        ...
                    });
</script>

api callback error ?

segment-timeline per se is certainly not causing it, we're using that in all our VOD examples.
What is the error?
For further diagnosis and bisecting I need the address of a working stream. Even if we find the exact revision where the plugin broke, I cannot second guess the actual problem without testing it on an actual stream.

Please see the follow link
http://yancey918.github.io/flowplayer/flowplayer_dash.html
and the live stream url is  http://<IP_ADDRESS>:1935/live/livestream/manifest.mpd
there was no error , but the manifest never refresh . please help.

Here's what I get with your stream in the DashIF sample player - apart from no time information:

Not the multiple audio stop which should not happen imho, looks like the stream has some serious hiccups.

Sorry Sir. why I didn't see any error message ?  anything I didn't open ?
note) the test stream location is in Singapore.

I saw what you say  'audio stop' , I will checkout what happen of the stream first .  thanks

I did not see the errors all the time, but sometimes I saw them - as my screenshot proves.
What's always there is the stop/start.

I am not sure now, before I thought it's just normal information.
Thanks for your reminder. I will try to resolve it first .
But do you know what usually event touch the 'audio stop' ?
And the flowplayer auto stop because this event ? thanks

It may be a good idea to take this to the dash.js bug tracker: https://github.com/Dash-Industry-Forum/dash.js/issues - they have more experience with live streams, and certainly more with audio streams - we don't, as I said, Flowplayer HTML5 so far is a video player.

Dear sir ,
the dash.js bug tracker say the 'audio stop' just normal information.
ref. https://github.com/Dash-Industry-Forum/dash.js/issues/885
I am still find out why the stream stop of flowplayer . please help . thanks
http://yancey918.github.io/flowplayer/flowplayer_dash.html

Currently your stream times out again, I had it working for a while (I think), but it's hard to be sure, because even when it's on sometimes the refreshed manifests don't load, at least from where I am.

@yancey918 - please check https://github.com/Dash-Industry-Forum/dash.js/issues/885#issuecomment-156538759 and submit a bug there. Thank you.
Closing, at least for now.

@blacktrash   thanks a lot . I submit a bug tracker here.  thanks
https://github.com/Dash-Industry-Forum/dash.js/issues/887


Generalize scrolling from an integer to a Vector2

Refactored int Wheel; to Vector2 Scroll;. This lays the groundwork for eventually having smooth scrolling when devices support it (e.g. some trackpads, such as on MacBooks).

I've had a quick look into detecting mouse capabilities with OpenTK:

Nothing related to high-precision scroll input. My approach to implementing this would be to automatically set devices to "high precision" whenever a non-1 scroll input was registered at least once at framework-side
OpenTK seems to know (in MouseDevice) the number of scroll wheels (which are required to toggle between the X-wheel and the Y-wheel for scrolling in horizontal ScrollContainers); however I don't see any immediate way to obtain the current MouseDevice from OpenTK. This requires a small change on OpenTK's side


[3.1] Fix cross-file diagnostics for protocol conformance failures

The protocol conformance checker tries to delay the emission of
diagnostics related to the failure of a type to conform to a protocol
until the source file that contains the conformance is encountered, to
provide redundant diagnostics. However, if a file produced only such
delayed diagnostics, such that all diagnostics were suppressed,
invalid ASTs could slip through to later stages in the pipeline where
they would cause verification errors and crashes. This happens
generally with whole-module-optimization builds, where we are re-using
an ASTContext when typing multiple source files.
This is a narrow-ish fix to stop dropping diagnostics from one source
file to the next in whole-module-optimization builds, along with another fix to detect cases where we're suppressing an error due to a conformance-related diagnostic that will be emitted in another file and emit something.

Resolves rdar://problem/29689007.

Whoops, wrong branch.


failed to deploy deployments: error waiting deployment: workload "T" state within deployment N is paused

I get the following error, if I want to apply something to the grid via terraform. I get this since around 3 days. The deployment 15145 and 15146 is up and running and i can ping them...
Provider version 1.6.2
Errormessage:
╷
│ Error: failed to deploy deployments: error waiting deployment: workload SlaveOfDoom01 state within deployment 15145 is paused: paused; failed to revert deployments: error waiting deployment: workload SlaveOfDoom03 state within deployment 15146 is paused: paused; try again
│
│   with module.kubernetes.grid_kubernetes.k8s1,
│   on ../../modules/threefold/main.tf line 50, in resource "grid_kubernetes" "k8s1":
│   50: resource "grid_kubernetes" "k8s1" {
│
╵
Playground:

ID
Type
Node ID
State
Billing Rate
Solution type
Solution name
Created at
Expiration
Actions

15145
node
31
Created
5.0758749 TFT/hour
kubernetes

3.12.2022, 14:20:54
-
Show Details

15146
node
34
Created
5.0712312 TFT/hour
kubernetes

3.12.2022, 14:21:12
-

the error indicates that the slaveOfDoom3 workload is in paused state, which means that this account has no enough tokens to keep billing for this workload, and the wallet needs to be funded. After the wallet is refunded, the paused workload should return to a stateOK within an hour.
If this is not the case, please report it.

thanks for your informations, i have to say in this time i had enought tokens a few days and the error didnt get away. maybe there is a time/performance issue. i can test it again if you want.

set up the deployments
let run out the tokens
wait for the error
fill up tokens
wait
try to change deployments.


not able to set DEBUG_TOOLBAR_CONFIG

Maybe I'm missing something simple, but I can't seem to figure this out...  My toolbar is working fine, but I'd like to change it so the jquery that's loaded is a local copy for when I'm working offline.  However, whenever I try to set anything in DEBUG_TOOLBAR_CONFIG the toolbar seems to fail to load but I get no errors.
The following fails to load the toolbar:  (which is the default setting)
DEBUG_TOOLBAR_CONFIG = {
    'JQUERY_URL': '//ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.min.js',
}

I also tried the following which also fails:
DEBUG_TOOLBAR_CONFIG = {}

I'm using 1.3.2 in Django 1.4.22 .  The toolbar works fine if I simply remove the DEBUG_TOOLBAR_CONFIG setting.
Incidentally, the docs at http://django-debug-toolbar.readthedocs.org/en/1.3.2/configuration.html show an example at the very bottom that shows using CONFIG_DEFAULTS instead of DEBUG_TOOLBAR_CONFIG .

Ack!  Okay, I was setting the config setting twice and was overwriting where I was setting SHOW_TOOLBAR_CALLBACK.  Sorry for the noise!


FastCorrect1: how to calculate the 'P', 'R'?

Sorry to bother, and thanks for this awsome paper && code.
I've done all the steps of FastCorrect1, but found no code for P_{edit}, R_{edit}, P_{right} which mentioned in the paper. I am really not sure how to calcaulate them.
Again, thanks so much for ur time and all the wonderful work!

Oh, I see.
Thanks so much for ur help!


Add istanbul badges readme

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆
github: https://github.com/olavoparno/istanbul-badges-readme

Thanks for the suggestion, but I think this is too Istanbul specific. This list is more about general tools than plugins/packages for specific projects. I would rather try to get it listed in the Istanbul readme.


Firestore API

Usage:
Firestore fs = FirestoreClient.getFirestore();

@mikelehen Code is pretty much the same as it was when you reviewed a while ago. It has just been updated/merged with the other changes that has been done recently in the master branch.

Made the suggested changes.


Mazumder - Begin V1.0 Close Out Documentation for FDA

Create Close out documentation google Doc drafts in this folder.
Create 2 volumes: Volume 1 = Technical Volume; Volume 2 = Usage Guide
Use 0.7 margins, Arial size 11 font (standard for the Lab)
If you wish to include color or design, please make sure things are clean. Approved project colors are: light cornflower blue 1, dark grey 4, white, or black

Please begin with the skeleton of each and reassign me this ticket to review before moving on.
Please include the following:
Applicable for both volumes. Some info make be duplicated such as some of the content on page 3/4:

[ ] Cover page including a Title of Project (FDA-ARGOS Project), Sub title (volume type and #), document version (V1.0 for both right now), Contract # (on SOW or Tech reports), and Project Period. Make sure to select appropriate headings for the entire document and be consistent.
[ ] 2nd page: table of contents only
[ ] 3rd/4th page:  (headers and their content) Project Description & Project Aims (Can be taken from the FDABAA/SOW OR Tech reports (use the most recent)), Document Description (volume specific)

Technical Volume 1: input the following headers/sections. Adjust the phrasing/wording to make it clear and concise (as needed). If you have any suggestions please include them in your draft:

[ ] BETSY Deployment package
[ ] Technical instructions for instantiation of an instance inside FDA
[ ] Maintenance manuals
[ ] BioProject submission information
[ ] GitHub manifest and access
[ ] API documentation
[ ] Roles outlining responsibilities
[ ] Chain of command for data product issues
[ ] Appendix

User Guide volume 2:

[ ] Data Model
[ ] Categorization and manifest of all data products
[ ] Written QC usage protocols
[ ] Biocompute Objects Manifest
[ ] Data.argosdb usage guide
[ ] Troubleshooting guide
[ ] Help Contact
[ ] Appendix

Created a rough skeleton for both volumes. Sent via Slack to Stephanie fo review

https://docs.google.com/document/d/1QsEYV1LzAT5mZvqc9mGIqRcfVGCL21VK-5LlmXWYJ94/edit?usp=sharing

https://docs.google.com/document/d/1CT4SG0JzN0d7-AGGS9mj9jXnh-fgLidjDgMFSLnhUg0/edit?usp=sharing

Added some more updates to volume 2 and some formatting

In review

It has begun, but with the possibility of an extension, we may not need to do this quite yet.

We do not need to do this, because Embleema will be in charge. Also it is extended


How do you access conversation data from a controller now the state API has been made obsolete?

Using the latest version of BotBuilder, is there a way to access/update UserData from a controller now the State API has been made obsolete?
I used to do something like this:
https://stackoverflow.com/questions/40328134/accessing-conversation-data-from-message-controller-c-sharp

This answer by @JasonSowers provides a solution for accessing the bot state without a context object:
https://stackoverflow.com/questions/46085614/how-can-i-access-bot-framework-conversationdata-outside-of-a-dialog/46085785#46085785

Brilliant thank you! Exactly what I was looking for.


Are there plans to support merge on read mode

As we know, Delta Lake is currently a copy on write mode, this mode is useful for write less and  read more scenarios, But it is not very friendly to write more and read less scenarios, So I want to know if there is such a plan to support read on merge mode.

Hello @397090770
Today delta can solve merge on read use cases.  In order to accomplish this, we create two tables and one view.
We have a changes table, which is constantly streamed into in append mode.
We have an "optimized" table which periodically takes the changes from the change table and merges them into the "optimized" table.  You can use a streaming job with trigger.once to accomplish this trivially.
We then create a view that joins the optimized table with the changes table to get the latest record for each key.

@joewiden - are you proposing a solution - by layering on top of Delta lake? or are these Delta lake constructs?
It lookslike - these are your constructs.
I think, the solution you proposed CANNOT solve MERGE ON READ due to the below reasons:

If the multiple changes are streamed to the same row in the Changes Table and each of the changes are modifying different set of columns in a given row - what will be the View query - which will you get the merged record?
deltalake doesn't support multi-table transactions. How will you remove the records from Change table and Add the new Rows to Optimized table in a single transaction?

I think your solution - caters to a very specific scenario - that you wanted to solve. Pls let me know if that is not the case.
It would be really great to understand - if DeltaLake is invested in evolving the deltaLake into supporting Merge On Read semantics.

Any difference in Delta Lake 2.x ?

Hi @dohongdayi - no, Delta 2.1 does not yet natively support MOR. The good news is that one of MOR's dependencies, deletion vectors, is on the H2 roadmap here: https://github.com/delta-io/delta/issues/1307 if you'd like to push for this feature please add a comment and upvote it :)

四年了 还不支持？

For information, Deletion Vectors are supported since Delta Lake 2.3.0 (released April 2023).


Not working when using Safari

When I test my angular app in Safari the cookies are not being saved.
version: 2.2.0

@Aristotelis1 which version of safari are you using?

Angular: 17+
Safari: 17.5

@Aristotelis1
after looking in to the code i know basically where the problem persist - could you please try to avoid localhost in safari on a mac.

closed due inactivity


List all potential test benchmarks

List all most used datasets in RAG researches, and we will add them to the benchmarks.

[ ] THUDM/webglm-qa from huggingface: https://huggingface.co/datasets/THUDM/webglm-qa
[ ] NaturalQuestions from huggingface: https://huggingface.co/datasets/natural_questions
[ ] #64
[ ] Trivia QA from huggingface: https://huggingface.co/datasets/trivia_qa
[ ] Hotpot QA from huggingface: https://huggingface.co/datasets/hotpot_qa
[ ] WikiEval from huggingface: https://huggingface.co/datasets/explodinggradients/WikiEval

[ ] MedMCQA  from hugginggace: https://huggingface.co/datasets/medmcqa
[ ] GSM8K from hugginggace: https://huggingface.co/datasets/gsm8k
[ ] BBH from github: https://github.com/suzgunmirac/BIG-Bench-Hard
[ ] SQuAD from hugginggace: https://huggingface.co/datasets/squad
[ ] SQuAD_v2 from hugginggace: https://huggingface.co/datasets/squad_v2
[ ] Wizard-of-Wikipedia(WoW) from hugginggace: https://huggingface.co/datasets/chujiezheng/wizard_of_wikipedia

Select and implement typical benchmarks, collect RAG papers that utilized these benchmarks, and try to reproduce evaluation result in the paper.

List benchmark and related papers & metrics.
Produce testset using baseline RAG in the paper. Pack testset as dataset format and upload to HuggingFace.
Reproduce evaluation result in RAGEval.

Eli5 @QianHaosheng , ASQA @bugtig6351 , Fever @henan991201


[Flagd] offline mode for in-process provider

Flagd has in-process evaluation capability introduced through PR https://github.com/open-feature/go-sdk-contrib/pull/327
Similar to the offline in-process mode in Java provider [^1], we should introduce an offline in-process mode for Go provider.
This needs to be followed up after completing the #393
[^1]: - https://github.com/open-feature/java-sdk-contrib/pull/473

We should also include the improvement done in https://github.com/open-feature/java-sdk-contrib/pull/614
This would enable mounting a ConfigMap directly on a Pod that contains the FF definition.

We should also include the improvement done in open-feature/java-sdk-contrib#614 This would enable mounting a ConfigMap directly on a Pod that contains the FF definition.

Opened PR #421 and in that I use flagd's implemenation of the file sync. This has proven to work fine (compared to what I found on Java libraries and watchers). I think reusing this reduce complexity and avoid code duplication :)


Simplify the Finder tool

Suggested new feature or improvement
The button for the Finder tool right now does 2 things:

Finder tool, to target an app.
Go to expanded mode and go to the Process list page.

The “finder” aspect is a well-known pattern used in other apps such as ProcExp, ProcMon, WinSpy. Having it also go to expanded mode and navigate to the process list page is confusing. It’s also redundant, because if the user is not already targeting an app, then they can use the Expand custom chrome button to go to expanded mode, and this will by default open the process list page.
Remove the “expand the ProcessList” feature from the Finder tool. Instead, leave it to the user to use the Expand custom chrome item to expand the window. If there is no target app, the default page will be the ProcessList anyway.
See related issues
#3066
#3431
#3060

Dupe of #3431


Understanding .gitignore

@thuhoainguyen  The full dataset is about 52GB, which is huge. By using .gitignore we can ignore the image data (large file) and avoid pushing it to github. That's why in the .gitignore there's a line:
dataset/*/*imaging.nii.gz

So not all the files with extension nii.gz are ignored, but only the files with the suffix imaging.nii.gz are ignored.

I see, the file imaging.nii.gz is 4.5 times larger than all the other files (227MB to 50MB) in each case folder.

That file is the image data, and the rest are annotations.

ok ! got it


AttributeError: 'AdeptConnection' object has no attribute 'send_clock_jump'

I periodically see an exception on my Piaware 8.2 instance. Looks like a module version mismatch? Here are my logs:
[piaware] 2023/10/21 19:06:07 mlat-client(174): outlier detected with ts: 6269.091, last_ts: 6269.063, ts_elapsed: 0.027, sys_elapsed: 1.503 (values in seconds)
[piaware] 2023/10/21 19:06:07 mlat-client(174): Unexpected exception on connection to localhost:30005
[piaware] 2023/10/21 19:06:07 mlat-client(174): Traceback (most recent call last):
[piaware] 2023/10/21 19:06:07 mlat-client(174):   File "/usr/lib/python3.11/asyncore.py", line 88, in read
[piaware] 2023/10/21 19:06:07 mlat-client(174):     obj.handle_read_event()
[piaware] 2023/10/21 19:06:07 mlat-client(174):   File "/usr/lib/python3.11/asyncore.py", line 425, in handle_read_event
[piaware] 2023/10/21 19:06:07 mlat-client(174):     self.handle_read()
[piaware] 2023/10/21 19:06:07 mlat-client(174):   File "/usr/local/lib/python3.11/dist-packages/MlatClient-0.4.2-py3.11-linux-x86_64.egg/mlat/client/receiver.py", line 214, in handle_read
[piaware] 2023/10/21 19:06:07 mlat-client(174):     self.coordinator.input_received_messages(messages)
[piaware] 2023/10/21 19:06:07 mlat-client(174):   File "/usr/local/lib/python3.11/dist-packages/MlatClient-0.4.2-py3.11-linux-x86_64.egg/mlat/client/coordinator.py", line 328, in input_received_messages
[piaware] 2023/10/21 19:06:07 mlat-client(174):     handler(message, now)
[piaware] 2023/10/21 19:06:07 mlat-client(174):   File "/usr/local/lib/python3.11/dist-packages/MlatClient-0.4.2-py3.11-linux-x86_64.egg/mlat/client/coordinator.py", line 350, in received_timestamp_jump_event
[piaware] 2023/10/21 19:06:07 mlat-client(174):     self.server.send_clock_jump()
[piaware] 2023/10/21 19:06:07 mlat-client(174):     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[piaware] 2023/10/21 19:06:07 mlat-client(174): AttributeError: 'AdeptConnection' object has no attribute 'send_clock_jump'
[piaware] 2023/10/21 19:06:07 mlat-client(174): Lost connection to localhost:30005

You seem to be running a 3rd party fork of mlat-client with piaware.
Usually piaware will include its own separate copy of mlat-client to avoid
this sort of breakage. How did you build/install your piaware?

I'm running a container of image from sdr-enthusiasts/docker-piaware repo. I figured that might be the case regarding breakage, thanks.
I'll open an issue with sdr-enthusiasts/docker-piaware.

Yeah, this is because that docker container is using the wrong mlat-client.
I'll comment over there.


Bicep VS Code extension should show/remove properties with default values

Is your feature request related to a problem? Please describe.
I'm desperately trying to migrate away from a set of poorly-understood ARM templates.  It's great that there are a bunch of example BICEP projects in the repo but the vast majority appear to be uncommented and suffer from the same issue as ARM templates - i.e every possible parameter has been filled out with no indication of which are defaults and which are "important".
In contrast, when I create a resource in the Azure Portal, it's (generally) quite simple to leave everything at default settings and have the UI guide you through the few mandatory changes.
Describe the solution you'd like
This is just a suggestion and perhaps there are better ways to do this but:

The VS Code extension could provide different styling for parameters which have a required non-default value (e.g. names) or a strongly encouraged non-default value (e.g. locations).
The VS Code extension could provide different styling for parameter values which are at their default (factory) setting
The VS Code extension could provide tooltip descriptions for parameter names and values.

For example when I look at https://github.com/Azure/bicep/blob/main/docs/examples/101/vm-simple-windows/main.bicep (which seems fairly representative) it's entirely unclear whether
var addressPrefix = '<IP_ADDRESS>/16'

is being set for some specific reason or if it's just the standard default.  And if it's the default, why can't I just write
resource nInter 'Microsoft.Network/networkInterfaces@2020-06-01' = {
  name: nicName
  location: location
}

and have the properties block defaulted?

I'm pretty certain I have never had to explicitly set this value when creating a VM in the portal.

Nailed it. The portal client is abstracting these details away from you. I suspect this will be solved with the #2128 in which Microsoft (and others) can publish a canonical interface (via a module) for a particular resource or set of resources to abstract  this away.  In a sense, the portal UX (and a PS or CLI client) is analogous to a built-in module in the registry. They are both hand-authored and designed to make consumption of that resource(s) as easy as possible.
WRT the VS code ux for properties, that mockup helped clarify. I guess what I'm stuck on is that all the properties with default values shouldn't even be there - they are just noise.  IOW, why not remove all the properties with gray values? There's probably something that could be added to the linter (#2341) to catch "properties with values set to the default value" and provide a quick fix to remove it.  (FYI @marcusfelling @jfleisher).

guess what I'm stuck on is that all the properties with default values shouldn't even be there - they are just noise. IOW, why not remove all the properties with gray values?

No argument there, you're actually going further than hoped for :-)   Tbf, it is sometimes useful to see what could be changed and you still need a styling policy for values which are present but changed back to their default value.   Another possibility would be to use folding  to hide blocks of default values.

Related to #5316

@NeilMacMullen I'm changing the title of this bug to reference just the default properties issue.  Above, though, you also say:

The VS Code extension could provide tooltip descriptions for parameter names and values.
I think this functionality already exists, e.g.:

Or is it something else you meant?  (If so, I'd prefer a separate issue to be entered and referenced here).  Thanks!

The confusing part here is that this particular resource type does not do a great job defining required properties in their REST API spec (which is what powers the bicep types), so bicep will tell you it's not required even though it is.

Are resource types responsible for defining the properties property as required? Or is this something that bicep should assume?
For example, https://learn.microsoft.com/en-us/azure/templates/microsoft.insights/actiongroups?pivots=deployment-language-bicep mentiones that some ActionGroup properties are required (enabled and groupShortName) but it does not mention that the root properties itself is required. So you could assume that some default values will be applied, but trying to deploy will return an error "The ActionGroup request is null or empty".

I don't believe Bicep makes any assumptions about this and we rely on the swagger to capture this, but @anthony-c-martin / @jeskew would know for sure.

Bicep does rely on resource provider service models to determine what properties are required. properties is not marked as optional in the ActionGroups body definition, and Bicep is just reflecting what's in the model.
There are resource types that don't require the properties property (Micrsoft.Storage/storageAccounts and Microsoft.ManagedIdentity/userAssignedIdentities come to mind), so I wouldn't want Bicep to just assume that not marking properties as required is a mistake.


NO-TICKET: {generate-chainspec,run-dev-tmux}.sh: add delay parameter

This PR adds a positional delay parameter to generate-chainspec.sh and run-dev-tmux.sh.  Went with the simple approach here rather than using getopt or a bespoke parser.
Examples:
./generate-chainspec.sh
# runs with default delay of 40

./generate-chainspec.sh 50
# runs with delay of 50

./run-dev-tmux.sh
# runs with default delay of 40

./run-dev-tmux.sh 50
# runs with delay of 50

bors r+


RFC: Implement base numeric types and bool as a library

 Issue by bjz
Tuesday Jan 14, 2014 at 01:57 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/11526
This issue was labelled with: A-libs, B-RFC in the Rust repository

Here is a (possibly crazy) proposal to remove some magic from the compiler:
#[repr=1 ] pub enum bool { true, false }

#[repr=8 ] pub struct u8;
#[repr=16] pub struct u16;
#[repr=32] pub struct u32;
#[repr=64] pub struct u64;

#[cfg(target_pointer_size = "32")] #[repr=32] pub struct uintptr;
#[cfg(target_pointer_size = "64")] #[repr=64] pub struct uintptr;

#[repr=8 ] pub struct i8;
#[repr=16] pub struct i16;
#[repr=32] pub struct i32;
#[repr=64] pub struct i64;

#[cfg(target_pointer_size = "32")] #[repr=32] pub struct intptr;
#[cfg(target_pointer_size = "64")] #[repr=64] pub struct intptr;

#[repr=32] pub struct f32;
#[repr=64] pub struct f64;

macro_rules! impl_llvm_op(
    ($Binop:ident, $binop:ident, $Self:ident, $init:expr, $llvm_op:ident, $llvm_ty:ident) => (
        impl $Binop<$Self, $Self> For $Self {
            fn $binop(a: &$Self, b: &$Self) -> $Self {
                let (a, b) = (*a, *b);
                unsafe {
                    let ret = &mut $init;
                    llvm!(concat!("%ret = ", stringify!($llvm_op), " ",
                                  stringify!($llvm_ty), " %a, %b")
                        :"a" = a
                        :"b" = b
                        :"ret" = ret
                    )
                    *ret
                }
            }
        }
    )
)

impl_llvm_op!(Add, add, u8, 0, add, i8)
impl_llvm_op!(Add, add, u16, 0, add, i16)
impl_llvm_op!(Add, add, u32, 0, add, i32)
impl_llvm_op!(Add, add, u64, 0, add, i64)

#[cfg(target_pointer_size = "32")] impl_llvm_op!(Add, add, uintptr, 0, add, i32)
#[cfg(target_pointer_size = "64")] impl_llvm_op!(Add, add, uintptr, 0, add, i64)

impl_llvm_op!(Add, add, i8, 0, add, i8)
impl_llvm_op!(Add, add, i16, 0, add, i16)
impl_llvm_op!(Add, add, i32, 0, add, i32)
impl_llvm_op!(Add, add, i64, 0, add, i64)

#[cfg(target_pointer_size = "32")] impl_llvm_op!(Add, add, intptr, 0, add, i32)
#[cfg(target_pointer_size = "64")] impl_llvm_op!(Add, add, intptr, 0, add, i64)

impl_llvm_op!(Add, add, f32, 0.0, fadd, f32)
impl_llvm_op!(Add, add, f64, 0.0, fadd, f64)

This relies on many hypothetical language features including the llvm! macro, CTFE and possibly some way of implementing adding literal assignments, and so might be too ambitious for 1.0. But in the end it could make our language far more extensible and powerful. It might also help simplify our documentation issues with builtin types #10114 #11409

Just stumbled upon this reading through these RFCs, has there been any movement on the llvm! macro, I can imagine a lot of really interesting uses for this, especially as LLVM continues to grow.

I think we've basically tied our hands at this point with a stable language, and the inherent impl problem has since been solved, so closing.


ValueError: too many values to unpack

Check if the csv file has more than two columns

Yes i changed


Updated the temperature_scale_converter.py

Added the SI unit of Temperature- The Kelvin Scale
Earlier temperature value in decimal was converted to an integer. So, converted the data type to float, so that temperature in
decimals can be considered
Added comments to make it user-friendly

@ssm0801 pls verify my code. I have more features for the temperature converter.

@herkura @niyoj


Add InstallPlan variable to SubmarinerConfig

In order to pin Submariner operator version installed, to prevent auto update with its default Subscription:
https://github.com/stolostron/submariner-addon/blob/e9fb85939918d4b1e52d007e192827a05c061c87/pkg/hub/submarineragent/manifests/operator/submariner-operator-subscription.yaml#L10
Please add installPlanApproval variable to SubmarinerConfig, so it can be set to "Manual".

According to the submarinerconfig object, installPlan parameter is not supported within the SubmarinerConfig.

I think that’s the point of this feature request — to add some way of configuring installPlanApproval in SubmarinerConfig.

@skitt IIUC, this would also need to be backported to release-2.4 once merged?
@sridhargaddam @tpantelis can you review please? This is currently blocking QE downstream.

/cherrypick release-2.4

@skitt IIUC, this would also need to be backported to release-2.4 once merged?

Yes, I’ve queued a cherry-pick.


ProtocolLib unable to send packet: nmsPlayer cannot be null!

What version of ViaVersion are you using? Type /ver viaversion
0.6.3
What version of Spigot are you using? Type /ver
paperspigot and spigot 1.8.8
What plugins are you using? Type /plugins
Plugins (48): PlugMan, EnchantmentAPI, DeathDropsAPI, ItemCasesFix, ViaVersion, ChestShopCreate, AsyncWorldEditInjector, EnchantManager, WorldEdit, EmptyWorldGenerator, SkinsModule, DefaultSkinsBungeeCordSub, NBTEditor, ClearLag, TimedItems, EnchantPotionPack, ProtocolLib, NoCheatPlus, AsyncWorldEdit, PermissionsEx, EnchantActivePack, EffectLib, Vault, EnchantPassivePack, ItemHolo, PlayerPoints, WorldGuard, BungeePortals, ASkyBlock, ChestCommands, LockedItems, CheckMyInventory, EnchantIntensePack, Essentials, MCTopup, Multiverse-Core, Citizens, Shopkeepers, EssentialsChat, Multiverse-Portals, HolographicDisplays, EssentialsSpawn, MyPet, ItemCases, PlaceholderAPI, BetterShops, BungeeTabListPlus, TitleManager
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
Lasted build, plugins: JustOneMore, BungeeTabListPlus, ServerListPlus, SkinsRestorer.
Players can connect to lobby but can't connect to SkyBlock server
How does this error happen? login? Using an item?
login
Is there an error in the console? Use pastebin.com. Is there a kick message?
http://pastebin.com/tchJSTSW

So does the same error occur on paperspigot and spigot?
Also it's really strange because these two lines are contradictory:
[06:26:16] [Server thread/WARN]: [ProtocolLib] Error filtering reports: java.lang.IllegalArgumentException: Cannot find report name for Unable to send packet %s to %s [06:26:16] [Server thread/WARN]: [ProtocolLib] [ProtocolLibrary] Unable to send packet net.minecraft.server.v1_8_R3.PacketPlayOutMapChunk@b9ee16e to EarthBound_Ness
Somehow the nms player got invalidated, are you sure you are using ProtocolLib for 1.8?
I assume this error doesn't happen without ViaVersion?
Does this happen for just 1.9 players? And does it happen from server startup, or is it sometimes randomly that this happens?

I'm using recomended ProtocolLib build for spigot 1.8, happen for just 1.9 players when they join.
Also tried paperspigot.
It works fine on Lobby, but when a player tries to connect to skyblock, bungeecord sends player back to lobby.

I will remove one by one plugin to see what plugin causes the issue when I have time.

Does this error only apply to the MapChunkBulk packet or does it also list other packets in the error?

The problem was CheckMyInventory, reported to the developer.
https://www.spigotmc.org/threads/check-my-inventory-offline-player-support-paid.48111/

Closed, CheckMyInventory has fixed their code.

What caused the issue? I'm having the same issue right now with my own plugin


Update plugin.yml and linter

We've made some changes to plugin.yml which means we're recommending plain English plugin names (for a future plugin directory), and I've renamed the --name param of the linter to --id to avoid confusion (buildkite-plugins/buildkite-plugin-linter#15).
This updates the sauce connect plugin with the new conventions.

ah, how did I miss this? Ta!

😆 No worries!


coding: add man-running icon to the status of coding topic

Add 🏃icon next to (in-progress) of coding column:

https://github.com/tungbq/devops-basic/blob/main/README.md

Fixed this and sent a PR.


MatSort.active returns 'created' when pristine

Bug, feature request, or proposal:
bug
What is the expected behavior?
MatSort.active should return undefined if no sortables is selected.
What is the current behavior?
when the table is first initialised, clicking next on the paginator also triggers matSort.active with the value 'created'.
this happens using the angular material example code of table with pagination.
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
i am now adding a statement to check if matSort is initialised and replacing the value of MatSort.active to undefined manually
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular "6.0.5", material "6.2.1", windows 10, "typescript": "2.6.2", chrome
Is there anything else we should know?

I was not able to reproduce the issue that you described.  As you can see in this stackblitz, it looks to be that no value is give to MatSort's active property until a sorting column is selected.
If you can provide a stackblitz reproduction, that will allow us to troubleshoot the issue you are seeing.

Closing as we still have not be able to reproduce this issue.


Forward --update flag in ./ci/spectest-zkasm.sh

Currently updating of state.csv is a bit inconvenient, and forces you to manually run commands from script with --update flag. Forwarding of this flag will make our life a bit better (=

In general, I think we want some script, which will provide interface to easy compile and run wasm locally, with commands like:

compile_all
run_one (and print verbose error)
run_all (and print list of changed statuses)
update_csv (run all and update all csv's)

@MCJOHN974 , we already forward the "--update" flag - do you this it is still worth doing https://github.com/near/wasmtime/issues/116#issuecomment-1831595188? If so, please update the title of the issue.


plugins/gitblame: switch to mkNeovimPlugin

I had to re-create a PR because I had originally used a branch on the main repo (by mistake) and thus couldn't force-push on it...
helpers -> lib.nixvim seems to work great !

Could we try removing the with lib; too?

Could we try removing the with lib; too?

I agree this may be nice going forward.
Although, in practice with lib is unlikely to cause us major issues?
If we only need a handful of things from lib, maybe do inherit (lib) x y z?

I made an attempt, please, let me hear your feedback.

Should we merge this then ?

Should we merge this then ?

👍 from me

@mergifyio queue


HDF5: attributes are not supported

I just found out that attributes of a dataset are not copied by odo. Looking at the dataset with Data I noticed attributes don't show up either.
As described in the link, attributes are pretty important for users of HDF5.

Agreed, can't use hdf5 file format idiomatically without attributes. Need to create annoying meta groups which obfuscates the structure.

How would you want the attributes represented? Right now blaze and odo unify different backends through the abstraction of a table, so we don't preserve metadata across queries or conversions. How would you want to query the attributes?
One option would be to use odo.resource to get the hdf object and then read the attributes from that. You could create the bz.data wrapper around this object directly so that you have access to both the attrs and the expressions.

How would you want the attributes represented? Right now blaze and odo unify different backends through the abstraction of a table, so we don't preserve metadata across queries or conversions. How would you want to query the attributes?

I think there should be a reserved attribute that can hold a dictionary with metadata. I don't know whether that's doable with blaze though since it deals with tables.
Relevant links:

pandas: https://github.com/pandas-dev/pandas/issues/2485
xarray: http://xarray.pydata.org/en/stable/faq.html#approach-to-metadata


Object nextCommunication has "Invalid date" after updating javascript or admin adapter

Describe the bug
The Object "nextCommunication" has "Invalid date" after updating javascript or admin
To Reproduce
Steps to reproduce the behavior:

Open object "melcloud.0.devices.X.info.nextCommunication"
Check state

Expected behavior
date should be displayed correct like object "melcloud.0.devices.X.info.lastCommunication"
Screenshots & Logfiles

Versions:

Adapter version: 1.1.4
JS-Controller version: 3.3.12
Node version: v12.19.0
Operating system: raspbian

Additional context
Add any other context about the problem here.

That's intended behavior.
The state "nextCommunication" only has a valid value/date when a pending command is outstanding, e.g. some device setting was changed. After the change was received by MELCloud, the state is filled with "null" again and "lastCommunication" is filled accordingly. Objects with type "date" und value "null" are interpreted as "Invalid Date" in the object tree.

ok, thanks. So this issue can be closed.