Inconsistent behavior of setting min-date

We can not select the day 2016-09-20

But we can select the day 2015-09-02 if we set min-date in different format

Is it a expected result?

I wouldn't say that is expected behavior

Hello,
and thanks for reporting the issue!
That is certainly not expected behavior.
As far as date handling goes, see below:

All that aside, I could not reproduce the issue.
If you could provide a codepen/jsfiddle/etc, I'd have a solution rather sooner than later.

It's fairly trivial to reproduce: https://jsfiddle.net/daneren2005/td42hff6/.  Came here to comment on this same issue.

Moment.js is the only pre made fix I know of currently. I went down a different route, so you can close this if you want or keep it open for other folks.
Dang JavaScript.
Robert Pearce
robertwpearce.com
linkedin.com/in/robertwpearce
m-US: 1.843.568.9080
m-UK: +44 7477 424374

On May 24, 2016, at 7:52 PM, Scott Jackson<EMAIL_ADDRESS>wrote:
It's fairly trivial to reproduce: https://jsfiddle.net/daneren2005/td42hff6/. Came here to comment on this same issue. It appears to only happen when you have a time on the Date.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

How did you fix it with moment.js?  I would prefer the root issue was fixed rather then everyone just using a bandaid over it.

Sorry I mean moment.js provides an alternative to the JavaScript Date object with timezones -- not a fix with the library's timezone issue.
To fix the problem with the library is not a big deal so long as there is an ability to pass a timezone to it that then affects the usage. If you like I can think on it and get back tomorrow if it's a big deal for others.
Robert Pearce
robertwpearce.com
linkedin.com/in/robertwpearce
m-US: 1.843.568.9080
m-UK: +44 7477 424374

On May 24, 2016, at 9:56 PM, Scott Jackson<EMAIL_ADDRESS>wrote:
How did you fix it with moment.js? I would prefer the root issue was fixed rather then everyone just using a bandaid over it.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

See https://jsfiddle.net/chmln/hoxkwc3y/

For now, due to arbitrary implementations of Date parsers across different browsers, it is necessary that minDate/maxDate are supplied without timezone/time data. Local and UTC date comparisons are pretty much guaranteed to be unreliable.
Obviously, flatpickr could rely on libraries like moment.js etc, but I'd rather not until I figure alternative solutions are non-existent. The aim of this project is to be standalone, lightweight, usable with rich enough functionality for the majority of use cases.
I will explore solutions, and keep this issue open and updated.

@chmln
Really thanks for your response.
To solve this issue temporary, I use .fp_incr(0) to remove time data before set minDate
It would be great that this issue can be fixed

I agree on it having no dependencies. Rock on, and a solution will present itself in time.
Robert Pearce
robertwpearce.com
linkedin.com/in/robertwpearce
m-US: 1.843.568.9080
m-UK: +44 7477 424374

On May 24, 2016, at 11:38 PM, Gregory<EMAIL_ADDRESS>wrote:
For now, due to arbitrary implementations of Date parsers across different browsers, it is necessary that minDate/maxDate are supplied without timezone/time data. Local and UTC date comparisons are pretty much guaranteed to be unreliable.
Obviously, flatpickr could rely on libraries like moment.js etc, but I'd rather not until I figure alternative solutions are non-existent. The aim of this project is to be standalone, lightweight, usable with rich enough functionality for the majority of use cases.
I will explore solutions, and keep this issue open and updated.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

https://github.com/chmln/flatpickr/commit/9bae58137402c7ff87bb301cd1342457f8437bbc fixed numerous issues.
Please check whether the initial problem is still relevant.
Thanks!

minDate tested working properly both in UTC (https://github.com/chmln/flatpickr/commit/eab4374f59e0122bad7936e566b0e2de9c7065b1#diff-51ad6ed16e74144ae6e17bbd53d35a5bR769) and non-UTC modes :tada:
Shall any problems arise in the future, feel free to comment and I'll reopen the issue.
Thanks again for the report!


Docs: Convert comp guide to one-way bindings, update iscp error

LGTM as long as you are sure that the cases where you have changed it to < are definitely valid.

@petebacondarwin What do you mean by valid? < can be used for everything, imo. I've only used @ because it doesn't two-way bind. But with < we don't have to interpolate.

I mean that does the change actually improve the use case? Does it take into account that although the binding is now one-way, we can still change properties of objects, etc, etc.

Hmm ..yeah, I don't mention that you can still update the parent expression if you are not careful. Maybe I should. One thing that's now easier is that we don't use @ for strings anymore (which I used previously because they don't bind to the parent scope)

I re-added @ and added some hopefully clarifying info about one-way binding.

LGTM


New configuration value to disable resolving references

Fixes #31 . Default value is set to preserve backwards compatibility.

Just starting to use Serverless today, but am frustrated that the get-started guide does not work.
I put "resolveReferences: true" into my serverless.yml, and now it starts working again. Thanks for the fix.


License

Can we get a liberal open source license on this thing?

Yes, what is license on this.. Cannot use it without a license. Thanks.

Is there a license for this?

There is now a license: https://github.com/Toniq-Labs/extendable-token/blob/main/LICENSE.md


[DNM] Support box-drawing-based blocks

There’s a social media post circulating where #define is used to write blocks using box-drawing characters in C code. Swift macros aren’t suitable for that kind of thing, but I wanted to see how difficult it would be to implement, just for funsies.
This is—and I cannot believe I am about to write this sentence—perhaps not the way we would actually want to implement box-drawing-based blocks, as it works by treating most of the characters as trivia and only assigning a semantic meaning to a few corner characters that happen to fall into the same positions as braces. That means it doesn’t actually enforce the validity of the box shapes.
Nor is this—and I cannot believe I am about to write this sentence, either—a production-quality implementation of box-drawing-based blocks. There’s a lot I haven’t tested, the diagnostics are probably a mess, there’s no formatter support (which would actually be a super cool addition), and there are a number of places where I suspect I made changes that would cost us some speed.
However, it’s certainly a fun little hack:
    assertParse(
      #"""
      ╔═════════════ func fizzBuzz() ═════════════╗
      ║ ╔═══════════ for i in 0..<100 ══════════╗ ║
      ║ ║ ╔═════ if i.isMultiple(of: 15) ═════╗ ║ ║
      ║ ║ ║        print("fizzbuzz ")         ║ ║ ║
      ║ ║ ╠═══ else if i.isMultiple(of: 3) ═══╣ ║ ║
      ║ ║ ║          print("fizz ")           ║ ║ ║
      ║ ║ ╠═══ else if i.isMultiple(of: 5) ═══╣ ║ ║
      ║ ║ ║          print("buzz ")           ║ ║ ║
      ║ ║ ╠══════════════ else ═══════════════╣ ║ ║
      ║ ║ ║          print("\(i) ")           ║ ║ ║
      ║ ║ ╚═══════════════════════════════════╝ ║ ║
      ║ ╚═══════════════════════════════════════╝ ║
      ╚═══════════════════════════════════════════╝
      """#
    )

SE-NNNN: Allow control flow using arrows 😄


RRateLimiter doesn't work

Hi,
I have created RRateLimiter instance.  If I call acquire (), it doesn't work.
RRateLimiter limiter = redisson.getRateLimiter("test.rate.limit.do");
// Initialization required only once.
// 5 permits per 50 seconds
limiter.tryAcquire(RateType.OVERALL, 5, 50, RateIntervalUnit.SECONDS);
limiter.acquire();

You need to call trySetRate method before and not tryAcquire


win screen

Pulling into dev to bring into my branch for vacuum testing

merging into dev to pull into my branch for vacuum testing with player controller


a problem in Compare validator

hi
a problem  in  Compare validator.
['password_repeat', 'compare', 'compareAttribute' => 'password_hash'],
when password_hash is not empty and password_repeat is empty.
validate is true.

Why are you comparing hash with password?

Is field of null == field of string ?

What do you mean? null == ''? Yes.

when i  filled password_hash text box and password_repeat was null .
form vlaidate returened true.

Is it user model or some other model? If it's user model then hash should not be obtained from the form at all.


v1.2.1 runs fine, but v1.2.2 throws error

This PR (https://github.com/postcss/postcss-loader/pull/161) assumes that a postcss.config.js will always be present. But isn't this file optional? In my project, I was configuring postcss using Webpack 1.0 syntax as mentioned in the Readme.
module.exports = {
  module: {
    loaders: [
      {
        test: /\.css$/,
        loaders: [
          …
          'postcss-loader'
        ]
      }
    ]
  },
  postcss: () => {
    return [
      require('precss'),
      require('autoprefixer')
    ];
  }
}

This works fine in v1.2.1, but breaks in v1.2.2 with the following error
No PostCSS Config found in /path/to/dir

This seems to be a breaking change and not support the Webpack 1.0 configuration model.

Nope, in that PR config could be generated from loader options. Check then above.
Tests are passed too.

@detj What is the current version of webpack you use?

@ai okay, yes you are right.
@michael-ciniawsky Yeah, I'm using<EMAIL_ADDRESS>Sorry, I should have explained my problem in detail.
So, my project is based on React Redux Starter Kit. It uses<EMAIL_ADDRESS>and has the following postcss config in its webpack config.
webpackConfig.postcss = [
  cssnano({
    autoprefixer : {
      add      : true,
      remove   : true,
      browsers : ['last 2 versions']
    },
    discardComments : {
      removeAll : true
    },
    discardUnused : false,
    mergeIdents   : false,
    reduceIdents  : false,
    safe          : true,
    sourcemap     : true
  })
]

I recently moved my project to a new machine and ran npm install (yeah, I should have used yarn, I know, but otherwise I couldn't have discovered issues like these :)). After installing fresh node_modules, npm run test started failing with the following error.
No PostCSS Config found in: /path/to/dir/where/style/resides

I read in the README of postcss-loader and postcss-load-config that the recommended way to now write postcss config is to create a postcss.config.js file in the root directory or any subdirectory as required.
Creating postcss.config.js and moving the configuration solves my problem, but what I want to understand is why the configuration from webpack not being read?
Also, there now seems to be multiple ways of loading postcss config including adding it in package.json or creating .postcssrc file. Is there any difference among them?
I'm sure I'm missing something, just don't know what exactly :)
Thanks

Creating postcss.config.js and moving the configuration solves my problem, but what I want to understand is why the configuration from webpack not being read?

Yep thats what I'm also interest in, bc normally options in webpack.config.js supersede postcss.config.js
Could you please do the following to help debugging
cd node_modules/postcss-loader
editor index.js

postcss-lodader/index.js
[L47] console.log(params)
[L51] console.log(options)

and run taht with options in webpack.config.js + afterwards post the result here please? :)

Also, there now seems to be multiple ways of loading postcss config including adding it in package.json or creating .postcssrc file. Is there any difference among them?

package.json|.postcssrc (JSON) [static] <=> postcss.config.js(JS) [dynamic] :)
package.json
{
   "devDependencies": {
     "cssnano": "^3.10.0",
     "postcss-nested": "^1.0.0"

  },
  "postcss": {
    "parser": "sugarss",
    "plugins": {
      "postcss-nested": {},
      "cssnano": { "autoprefixer": false }
    }
  }
}

postcss.config.js (recommended)
module.exports = (ctx) => ({
   // works for both (file.sss, file.css) automatically
   parser: ctx.webpack.resourcePath.endsWith('.sss') : 'sugarss' : false,
   plugins: {
     'postcss-nested': {}
     'cssnano': ctx.env === 'production' ? {} : false // Will only load in production mode
  }
})

@michael-ciniawsky That makes so much sense! Thank you for the detailed answer :)
Okay, so I added a few console.logs and here's what I discovered.
console.log(params)
{}

console.log(options)
undefined

I also added more logs to debug further
var loader = this;
console.log('loader', loader);
console.log('loader.options', loader.options);
console.log('loader.options.postcss', loader.options.postcss);

// output

loader { data: undefined,
  inputValue: null,
  query: '',
  async: [Function: async],
  callback: [Function] }
loader.options { output:
   { filename: 'extract-text-webpack-plugin-output-filename',
     publicPath: '/_karma_webpack_//' } }
loader.options.postcss undefined

Is this helpful? Let me know if I should do more debugging.

extract-text-webpack-plugin-output-filename
@detj  Yep, thx I think we found the bug 😛 , you use  extract-text-wbepack-plugin as it seems, which version and could you try if it works without extract-text-webpack-plugin + post your whole webpack.config.js please and say it directly extract-text-webpack-plugin + postcss in it's current state is a troublemaker and straight out mess, we recieve tickets for it nearly every day atm, I already stressed out to fix it in the webpack slack and work on fixing it myself, but the code is very complicated and verbose.

@detj In that starter project, I noticed for npm run test it uses the karma.config to build and not the webpack.config. The karma config actually doesn't include any postcss options in it. I think if you add postcss: webpackConfig.postcss right below sassLoader : webpackConfig.sassLoader then the postcss config will be passed into your test bundle and should clear your error.

@caseyduquettesc you're right. I did as you said and the tests are passing. But the thing is, tests were passing before and because of some change in this package (my guess), this error started showing up. Anyways, I'll update the react-redux-starter-kit about this development nonetheless. Appreciate it! Thanks.
@michael-ciniawsky okay, will take a look when I have some time. thanks. 👍


Revisit API definition

Evaluate the current message routing API. The API should be as clear and simple to make the reuse of the code as painless as possible. Should we position the message routing closer to middleware model?

This is not far from done (in development branch currently), but I'll let this issue wait for review before closing.


Auth issue causes endless notifications

There is some kind of authentication issue this morning. All extensions using GH have issues but GHPR is very aggressively retrying causing endless notifications spam.
https://github.com/user-attachments/assets/c7c305c0-ce92-44ca-bda3-337b8aa90df6
@TylerLeonhardt The renderer/api-impl should prevent this from happening

This is not something that that auth stack can help with because it is not in control of requests, only minting auth tokens. This needs to be handled in the extension.

@jrieken if you see this again please share GitHub Pull Request logs.


KAFKA-5142: Add Connect support for message headers (KIP-145)

KIP-145 has been accepted, and this PR implements KIP-145 except without the SMTs.
Changed the Connect API and runtime to support message headers as described in KIP-145.
The new Header interface defines an immutable representation of a Kafka header (key-value pair) with support for the Connect value types and schemas. This interface provides methods for easily converting between many of the built-in primitive, structured, and logical data types.
The new Headers interface defines an ordered collection of headers and is used to track all headers associated with a ConnectRecord (and thus SourceRecord and SinkRecord). This does allow multiple headers with the same key. The Headers contains methods for adding, removing, finding, and modifying headers. Convenience methods allow connectors and transforms to easily use and modify the headers for a record.
A new HeaderConverter interface is also defined to enable the Connect runtime framework to be able to serialize and deserialize headers between the in-memory representation and Kafka’s byte[] representation. A new SimpleHeaderConverter implementation has been added, and this serializes to strings and deserializes by inferring the schemas (Struct header values are serialized without the schemas, so they can only be deserialized as Map instances without a schema.) The StringConverter, JsonConverter, and ByteArrayConverter have all been extended to also be HeaderConverter implementations. Each connector can be configured with a different header converter, although by default the SimpleHeaderConverter is used to serialize header values as strings without schemas.
Unit and integration tests are added for ConnectHeader and ConnectHeaders, the two implementation classes for headers. Additional test methods are added for the methods added to the Converter implementations. Finally, the ConnectRecord object is already used heavily, so only limited tests need to be added while quite a few of the existing tests already cover the changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation matches KIP-145
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Is there any plan to implement the SMT’s (as specified by KIP-145) as well ?


fix jsonl line parsing

Fix error when parsing jsonl documents from s3 extractor.
iterator of StringIO type returns type bytes, using iterator of StringIO.readlines() returns type str

I think maybe also add a test for jsonl file types in the S3 Extractor test files:
tests/unit/pipeline/extractors/stores/aws/test_s3_extractor.py
That replicates the JSON decode error when these changes are undone.


Limit setting

See #37, we add code that is used to set limits in the case of no background

Coverage increased (+0.9%) to 95.116% when pulling<PHONE_NUMBER>9f5071ea3fbd79ba269d3ff27a5d38 on LZ_limits into fe3acc2e41750db7b786e6386d67203fb11e73ed on master.


Add gdpr

@mhadam:

changed it to use variables local to tracker
Added a unit test to check gdpr context is added to all events

PR should be rebased to conform to our naming conventions/standards before merging I think - would be good to catch up & make sure I do that right once code is reviewed. :)

Forgot to push the cleanup etc. but is now ready for review. :)

Rebased.


one version...

I create one new command in package.json, to install all dependences(comand: npm run install), I'm beginer in javascript and this, plus... one small contribuition is better than nothing
by artur, in brazil

??? what is the point of this, npm i will just install all the modules automatically

ow, sorry. but is a good idea?

try the my other games (:

I created the title like this because I don't know English very well, I'm from Brazil

one new meme for you:


Port Lists module to Java

https://github.com/CategoricalData/hydra/blob/main/hydra-haskell/src/main/haskell/Hydra/Dsl/Lib/Lists.hs

Done and tested using the common test suite.


block comment don't give rise to foldable blocks

#[
should show a foldable icon so this comment is foldable
]#

# note the foldable icon (triangle) here
proc fun()=
  proc fun2()=
    discard
  discard

fun()

Do you know of a way to enable this? Even the Python syntax doesn't allow folding triple-quoted strings.

https://www.sublimetext.com/docs/3/api_reference.html
fold([regions]) | bool | Folds the given regions, returning False if they were already folded
-- | -- | --
fold(region) | bool | Folds the given region, returning False if it was already folded
unfold(region) | [Region] | Unfolds all text in the region, returning the unfolded regions
unfold([regions]) | [Region] | Unfolds all text in the regions, returning the unfolded regions

example: syntax based folding:
https://github.com/jamalsenouci/sublimetext-syntaxfold/blob/master/SyntaxFold.py

See this:
Note: This plugin does not create folding markers (the functionality for creating these markers is not exposed within the Sublime Text API). The folding functionality provided by this plugin relies on using keyboard shortcuts assigned by the User or by invoking fold commands through the command panel.

@timotheecour ^
The above quote means that even if this functionality was implemented, it would only be accessible via hotkeys. To me, this significantly reduces the usefulness. Furthermore, there already appears to be a plugin which implements a generic approach to this problem.


TUT 3 - HPL Compile with IntelOpenAPI

I have attached a screenshot of the instructions, and the files that are in the setup

Fixed, Make.Linux_Intel64


Closing Preview toolbar does not close it

I have @nuxtjs/prismic setup up and working as expected.  However, when I preview a document in my application, and then I try to "turn off" preview mode by clicking the X on the purple preview toolbar, preview mode never goes away.  The only way for me to get out of preview mode is to go into my cookies and delete the prismic preview cookies.
I would expect the preview mode to be removed by closing the X button, however this never happens.

+1

Hey, I'm really sorry for the lack of support back then! The toolbar has since gone through a lot of fixes related to that kind of issue (due to privacy policy updates and cookies messing), feel free to open another issue if you're still experiencing it!


Adding Second Device Causes Plugin / Homebridge to Crash

I just added a second device to my EcoFlow plugin config. The original device (Delta 2 Max) was working fine, but when I added the Delta 2, it went into a crash loop. The plugin crashed and took Homebridge down with it, similar to the issue I had when the api-e was failing, even though I had it setup the same way. I tried updating the plugin to the latest version, but that failed as well, even after setting the server to the US one. From review of the logs, the plugin connects and pulls data for both devices, but eventually gets this error:
[8/11/2024, 2:42:24 PM] [Homebridge EcoFlow] [Delta 2 Max] Acquire certificate for MQTT connection
[8/11/2024, 2:42:25 PM] ErrorWithReasonCode: Connection refused: Client Identifier not valid
at handleConnack (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/handlers/connack.ts:47:15)
at handle (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/handlers/index.ts:49:17)
at work (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/client.ts:765:17)
at Writable.writable._write (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/client.ts:789:4)
at writeOrBuffer (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/readable-stream/lib/internal/streams/writable.js:334:12)
at _write (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)
at Writable.write (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/readable-stream/lib/internal/streams/writable.js:286:10)
at TLSSocket.ondata (node:internal/streams/readable:1007:22)
at TLSSocket.emit (node:events:519:28)
at TLSSocket.emit (node:domain:488:12)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at TLSSocket.Readable.push (node:internal/streams/readable:390:5)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:191:23)
[8/11/2024, 2:42:25 PM] [Homebridge EcoFlow] [Delta 2] Connected to EcoFlow MQTT Service
[8/11/2024, 2:42:25 PM] Got SIGTERM, shutting down Homebridge...
I wasn't sure if there was a limit to one device per API key, but when I tried creating a second one, to see if that would fix it, EcoFlow said I could only have 1 per account.
Just to make sure it wasn't the new device itself, I removed the old Delta 2 Max config and just left the Delta 2, restarted, and that one is working fine by itself. So it seems like either device individually works, but adding both will cause the plugin (and Homebridge) to crash. I'm not sure why it says "Connection refused" in the log above, because right before then I can see it pulling all of the data for both devices, but maybe there is some limitation on connections, etc.
Also, on a separate note, prior to updating to the latest version, the logs were pretty quiet. But now I am seeing a constant flood of log entries on the status screen for the plugin every couple of seconds, even with the device in standby mode:
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] BatteryLevel -> 100
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:33 PM] [Homebridge EcoFlow] [Delta 2] INV: { invOutVol: 120334, acInVol: 120987 }
[8/11/2024, 3:09:34 PM] [Homebridge EcoFlow] [Delta 2] BMS: {
amp: 0,
soc: 100,
minCellVol: 3355,
outputWatts: 0,
maxCellVol: 3369,
inputWatts: 0,
f32ShowSoc: 100,
cellVol: [ 3358, 3355, 3358 ],
mosState: 2,
cellTemp: [],
actSoc: 100,
sysState: 2,
allErrCode: 8388672
}
[8/11/2024, 3:09:34 PM] [Homebridge EcoFlow] [Delta 2] Status Low Battery -> false
[8/11/2024, 3:09:34 PM] [Homebridge EcoFlow] [Delta 2] BatteryLevel -> 100
[8/11/2024, 3:09:34 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:34 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:34 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:36 PM] [Homebridge EcoFlow] [Delta 2] INV: { acInVol: 121358 }
[8/11/2024, 3:09:36 PM] [Homebridge EcoFlow] [Delta 2] BMS: {
.....
I'm concerned this could fill up the log files very quickly.
Please let me know if you need anything else in order to troubleshoot. Thanks!

The plugin crashed and took Homebridge down with it
It will be hard to reproduce your steps because I have only one device, but i will try to look on the issue.

Also, on a separate note, prior to updating to the latest version, the logs were pretty quiet. But now I am seeing a constant flood of log entries on the status screen for the plugin every couple of seconds, even with the device in standby mode
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] BatteryLevel -> 100
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:32 PM] [Homebridge EcoFlow] [Delta 2] Battery Level, % -> 100
[8/11/2024, 3:09:33 PM] [Homebridge EcoFlow] [Delta 2] INV: { invOutVol: 120334, acInVol: 120987 }_
It is a debug information about received MQTT messages and set characteristics based on information in them. Adding of those log records were added in version 1.0.0 of the plugin. Maybe you turned on "Homebridge Debug Mode -D" and start seeing all Debug information.

even with the device in standby mode
The plugin subscribes on MQTT topic and is notified when MQTT server publishes messages. So despite on device is in standby mode, MQTT server decides that something was changed and subscribers should be notified.

I wasn't sure if there was a limit to one device per API key, but when I tried creating a second one, to see if that would fix it, EcoFlow said I could only have 1 per account.
Yes, it is possible to have one Access Key active per account.

[8/11/2024, 2:42:24 PM] [Homebridge EcoFlow] [Delta 2 Max] Acquire certificate for MQTT connection
[8/11/2024, 2:42:25 PM] ErrorWithReasonCode: Connection refused: Client Identifier not valid
If you have 2 devices for the same account (accessKey and secretKey are the same), plugin will try to create two connection to MQTT Server with the same parameters (username, password, clientId). I assume this is reason of the failure. I will extend plugin by sharing mqtt connection for devices with the same accessKey and secretKey

I've published version 1.3.0-beta where added support for multiple devices:

Devices for the same EcoFlow account share a mqtt connection
Devices for different EcoFlow accounts use a mqtt connection that is established for each EcoFlow account

@jamesbabiak. can you try it? And let me know whether your issue was fixed and both devices for the same account are added successfully?

I just upgraded and tested it out. Some bad news, good news, then more bad news.
I added my Delta 2 Max back into the plugin settings, as I only had the Delta 2 left from before. Restarted Homebridge and noticed it immediately started failing again, which once again caused Homebridge to shutdown and restart as well.
Here are the relevant error logs from the crash loop:
[8/17/2024, 8:25:40 AM] TypeError: Cannot read properties of null (reading 'bms_bmsStatus')
at Delta2Accessory.processQuotaMessage (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/accessories/batteries/batteryAccessory.ts:46:32)
at Object.next (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/containers/mqttDevice.ts:41:49)
at ConsumerObserver.next (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/rxjs/src/internal/Subscriber.ts:161:25)
at SafeSubscriber.Subscriber._next (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/rxjs/src/internal/Subscriber.ts:119:22)
at SafeSubscriber.Subscriber.next (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/rxjs/src/internal/Subscriber.ts:75:12)
at /usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/rxjs/src/internal/Subject.ts:68:20
at Object.errorContext (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/rxjs/src/internal/util/errorContext.ts:29:5)
at Subject.next (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/rxjs/src/internal/Subject.ts:61:5)
at MqttDevice.processReceivedMessage (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/containers/mqttDevice.ts:25:27)
at /usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowMqttApiManager.ts:123:38
at Array.forEach ()
at EcoFlowMqttApiManager.processReceivedMessage (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowMqttApiManager.ts:123:13)
at MqttClient. (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowMqttApiManager.ts:84:16)
at MqttClient.emit (node:events:519:28)
at MqttClient.emit (node:domain:488:12)
at handlePublish (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
at handle (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
at work (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/client.ts:773:17)
at Writable.writable._write (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/mqtt/src/lib/client.ts:797:4)
at writeOrBuffer (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/readable-stream/lib/internal/streams/writable.js:334:12)
at _write (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)
at Writable.write (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/node_modules/readable-stream/lib/internal/streams/writable.js:286:10)
at TLSSocket.ondata (node:internal/streams/readable:1007:22)
at TLSSocket.emit (node:events:519:28)
at TLSSocket.emit (node:domain:488:12)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at TLSSocket.Readable.push (node:internal/streams/readable:390:5)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:191:23)
Then, just as I was about to remove the second device again, I noticed things seemed to stabilize. No more errors or restarts. I checked the accessories and was able to confirm that both devices were showing up.
Unfortunately, just as I was about to let you know that, after a few hiccups, it seemed to be working, I saw it start to crash again, albeit a little differently this time.
Relevant logs:
[8/17/2024, 8:29:17 AM] [Homebridge EcoFlow] [Delta 2] Request is failed: TypeError: fetch failed
at node:internal/deps/undici/undici:13178:13
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at EcoFlowHttpApiManager.execute (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowHttpApiManager.ts:98:24)
at EcoFlowHttpApiManager.acquireCertificate (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowHttpApiManager.ts:61:22)
at EcoFlowMqttApiManager.acquireCertificate (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowMqttApiManager.ts:131:29)
at EcoFlowMqttApiManager.connect (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowMqttApiManager.ts:66:23)
at EcoFlowMqttApiManager.subscribeOnTopic (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowMqttApiManager.ts:95:20)
at Delta2Accessory.initMqtt (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/accessories/ecoFlowAccessory.ts:139:8)
at Delta2Accessory.connectMqtt (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/accessories/ecoFlowAccessory.ts:128:5)
at Delta2Accessory.initialize (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/accessories/ecoFlowAccessory.ts:45:5)
at EcoFlowHomebridgePlatform.initialize (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/platform.ts:176:7) {
[cause]: ConnectTimeoutError: Connect Timeout Error
at onConnectTimeout (node:internal/deps/undici/undici:2331:28)
at node:internal/deps/undici/undici:2283:50
at Immediate._onImmediate (node:internal/deps/undici/undici:2315:13)
at processImmediate (node:internal/timers:483:21) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
}
[8/17/2024, 8:29:27 AM] [Homebridge EcoFlow] [Delta 2] Request is failed: TypeError: fetch failed
at node:internal/deps/undici/undici:13178:13
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at EcoFlowHttpApiManager.execute (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowHttpApiManager.ts:98:24)
at EcoFlowHttpApiManager.getAllQuotas (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/apis/ecoFlowHttpApiManager.ts:46:22)
at Delta2Accessory.initializeDefaultValues (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/accessories/ecoFlowAccessory.ts:164:21)
at EcoFlowHomebridgePlatform.initialize (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/platform.ts:177:7) {
[cause]: ConnectTimeoutError: Connect Timeout Error
at onConnectTimeout (node:internal/deps/undici/undici:2331:28)
at node:internal/deps/undici/undici:2283:50
at Immediate._onImmediate (node:internal/deps/undici/undici:2315:13)
at processImmediate (node:internal/timers:483:21) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
}
After removing the second device again, it stopped crashing and seems to be OK.
So unfortunately, while it did seem, at least temporarily, to successfully connect and work with 2 different devices, that was only for a minute or so before it crashed again.
One other weird issue I found was that, after removing the 2nd device, it was still showing up in my HomeBridge accessories. I reviewed the logs and it didn't mention the other one, but it was still listed. I checked the config file and confirmed only the single Delta2 was listed. I tried restarting HomeBridge a couple times, but the second orphaned device remained. I downgraded to the previous 1.2.1 version, restarted, and that seemed to purge the old record. Not sure if that was just a bug in the new version or some weird one-off situation, but I figured I would mention it.
Let me know if you need anything else. Thanks!

Thanks for testing. I have several comments:

I added my Delta 2 Max back into the plugin settings, as I only had the Delta 2 left from before. Restarted Homebridge and noticed it immediately started failing again, which once again caused Homebridge to shutdown and restart as well.
Here are the relevant error logs from the crash loop:
[8/17/2024, 8:25:40 AM] TypeError: Cannot read properties of null (reading 'bms_bmsStatus')
at Delta2Accessory.processQuotaMessage (/usr/lib/node_modules/@pietrolubini/homebridge-ecoflow/src/accessories/batteries/batteryAccessory.ts:46:32)

Can you turn on Debug mode in homebridge for debug messages be shown as well?

Unfortunately, just as I was about to let you know that, after a few hiccups, it seemed to be working, I saw it start to crash again, albeit a little differently this time.
Relevant logs:
[8/17/2024, 8:29:17 AM] [Homebridge EcoFlow] [Delta 2] Request is failed: TypeError: fetch failed

This error should not force homebridge to restart. Nevertheless, can you post your config by anonymizing your secrets? Something like this
"devices": [
{
    "name": "Name1",
    "model": "Delta 2",
    "serialNumber": "sn1",
    "location": "US",
    "accessKey": "accessKey1",
    "secretKey": "secretKey1",
},
{
    "name": "Name2",
    "model": "Delta 2 Max",
    "serialNumber": "sn2",
    "location": "US",
    "accessKey": "accessKey1",
    "secretKey": "secretKey1"
}
],

I am particularly interested in whether you have the same accessKey and secretKey for both devices.

So unfortunately, while it did seem, at least temporarily, to successfully connect and work with 2 different devices, that was only for a minute or so before it crashed again.

Can you turn on Debug mode and post the whole log for Ecoflow plugin particularly?

I tried restarting HomeBridge a couple times, but the second orphaned device remained.

This feature is by design. Despite on fact that your removed device from configuration, the accessory is still in homebridge's cache. This is useful when you have some automations for that device in HomeKit and your want to disable it for a while and later return back. In this case you don't need to update those automations, but if a device is removed from homebridge, next time it is created, you will have to update all conditions where it is stated.
If you really want to remove device, you can do it in homebridge -> Settings -> Manage Cached Accessories -> Remove Single Cached Accessory


Landing Page Links to Notes Page

Landing Page Links to Notes Page
User Story
AS A small business owner
I WANT to be able to write and save notes
SO THAT I can organize my thoughts and keep track of tasks I need to complete
Acceptance Criteria
GIVEN a note-taking application
WHEN I open the Note Taker
THEN I am presented with a landing page with a link to a notes page

The landing page links to the notes page.  When the "Get Started" button is clicked, the user is taken to the notes page.  Users are also able to navigate back to the home page from Notes.


Application of patch 10-realsense-camera-formats-4.4.patch failed.

Required Info

Camera Model
R200

Firmware Version

Operating System & Version
Ubuntu 16.04.03 LTS

Kernel Version (Linux Only)
4.4.0-109-generic

SDK Version

Hi I am following the installation instruction as given here. When I do
sudo apt-get install realsense-uvcvideo
I am thrown with the following failed message:
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/realsense-uvcvideo.0.crash'
Error! Application of patch 10-realsense-camera-formats-4.4.patch failed.
Check /var/lib/dkms/realsense-uvcvideo/4.10.0/build/ for more information.
Processing triggers for shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) .

Additionally cannot find R200 in realsense-viewer.
I tried building from source. And when I did sudo dmesg | tail -n 50 I received:
[ 6849.594419] Linux video capture interface: v2.00
[ 6849.604867] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0c45:6713)
[ 6849.851869] input: Integrated_Webcam_HD as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input35
[ 6849.852108] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 6849.854560] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 6849.857146] uvcvideo: Unable to create debugfs 2-6 directory.
[ 6849.857405] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 6849.859363] uvcvideo: Unable to create debugfs 2-6 directory.
[ 6849.859515] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.4/input/input36
[ 6849.859597] usbcore: registered new interface driver uvcvideo
[ 6849.859598] USB Video Class driver (1.1.1-3-realsense)

Hi @arunavanag591 , I'm closing the ticket now.
Feel free to reopen in case you need more assistance.

Thanks @ev-mp , I think its resolved for now.


Update products.md

Added info on Advanced Settlement Options & made some minor grammatical improvements.

Some good additions here. @TomintheToon see comments

Some good additions here. @TomintheToon see comments

Thanks + for your helpful comments. Committed changes as suggested.

@DonDuala Committed changes as suggested.

You may have to create another PR that attempts to merge these changes to the main dual finance repo


Use Swift Package Manager

Xcode projects are hard to maintain
Much easier to deal with updates to Package.swift instead of an Xcode project

I don't disagree with you, but the main purpose of this repo is to serve as an example of how to build a native app using the most frequent tools developers would use themselves. There is also a simple command-line tool in swift-transformers that can be maintained as part of that package: https://github.com/huggingface/swift-transformers/blob/9e01d03f729b7ca404caf6b442ef491687ba457b/Package.swift#L22. I thought an UI would require more dependencies and contribute to bloating the package. Hence, this repo.
I've also found the use of xcconfig files as a good compromise. It allows easy diffs of configuration changes and is fully compatible with all Xcode workflows. Maybe we could explore that avenue instead?


implement the recommendations of the security review report (2)

Implement the 2 recommendations from the security report:
Stop using github.com/form3tech-oss/jwt-go. The report recommends using github.com/golang-jwt/jwt instead. But since this library is not really used, we suggest to remove it for now.
Update RBAC configuration, restricting access to resources such as secrets, serviceaccounts to the operator and operand namespaces only
    Namespace permissions remain on the clusterRole
    Permissions for secrets creation/update in the operator namespace are given through a new role (generated by kubebuilder annotations)
    Permissions for secrets & serviceaccounts creation/update in the operand namespace are given through a role and rolebinding under the configure/operand_rbac folder. Makefile's targets deploy, undeploy and olm-manifest are updated to this effect

/retest


Update to .NET Core 2.1.5 with SDK 2.1.403

PR Summary
Update to .NET Core 2.1.5 with SDK 2.1.403
https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.5/2.1.5.md
https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.5/2.1.5-commits.md
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@TravisEz13 thank you, your script saves a lot of time!

Ported to 6.1.1 servicing branch


Issue 3430, tests for the Wikidata extension

First PR of a serie, in order to cover the wikidata extension with Cypress tests
issue #3430

It looks like the tests do not pass yet, so I am marking the PR as draft.

Superseded by #5273.


Update cautions.md

What type of PR is this?
wrongly written character

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add bower support.

I'd love to be able to pull vanilla lodash from bower_components in a work project and replace with lodash-fp.

Yep there are plans for that.

Great! Thanks a lot.

I haven't decided if I want to have a dist/ folder or a branch for it.
The plan is to have it browserified/minified. Though I could see the benefit of just using the convert.js to convert an existing lodash instance into -fp.

Have you considered having a dist/ folder with both a bundled standalone build and one that takes lodash as a parameter? In my project, we are already using lodash and would love to start using this, but can't switch over all at once. Loading lodash twice would be unfortunate.

Hi, we are planning of using lodash-fp in a full mean stack project. Since there is no bower support is there any possible way to use the -fp version in the browser.

+1 I use lodash-fp in my node.js scripts and I'd like to include it in my client-side code, too.

Ok we solved it using browserify which can be later combined with gulp to ensure that u always have consitency between versions.
http://browserify.org/#install
This is hopefully temporary solution till there is bower support.

Browserify doesn't fully solve the use case of using this on the client - if you're already using requirejs (like we are), it won't work.

You should be able to browserify in a way that won't affect amd loaders.

@jdalton while we may be able to make it available as a global that gets loaded before requirejs does, I'm not aware of any way to load a browserified module through requirejs in the same way we're currently loading lodash. If you know of something, I'd greatly appreciate being pointed in the right direction.

@daedalus28 I can't repro. Try:
browserify . -s _ -o bundle.js

Closing by way of https://github.com/lodash/lodash-fp/commit/706d333feb8a01d8d6dec4d8289838fdcf40f231. I'll move the tag up to catch it.

Can't install lodash-fp...
bower install lodash
bower not-cached    git://github.com/lodash/lodash.git#*
bower resolve       git://github.com/lodash/lodash.git#*
bower download      https://github.com/lodash/lodash/archive/3.10.1.tar.gz

bower install lodash-fp
bower ENOTFOUND     Package lodash-fp not found

Yah, I still need to publish it.

Please update npm package and readme.
Thanks!

Updated, registered, and tagged.

npm package v 0.10.2 still doesn't have dist folder :(

Works for me.

The npm package wouldn't have the dist. If you want client side use bower. If you want npm to client side then use the same setup I'm doing to webpack bundle it.


Date and day is off instead of the 17 on Wednesday it show the 17 on Tuesday and so on and on. How can I fix this? thank you

Are you using the current version of the script and what settings have you changed? There was a similar issue back in November, but the current script should show it correctly when the week is set to start on a Monday as well as on a Sunday.

Thank you for the quick response I haven't changed anything I think is perfect but I'm not sure which version I'm running really?

If you copied the contents of the calendar.js file then it's up to date and I'm at a loss what could cause this, because I'd expect that they then wouldn't line up for me either.

I’m having this issue as well! I just copied the code and ran it without changing anything and this is happening. I’ve tried on two different phones as well and it’s still happening


Value updates not rendering

I've noticed a few issues since the last update where values and/or updates to them aren't rendered. I've managed to create a cut-down example to demonstrate the issue:
This is using v0.10.0
http://jsbin.com/fadogipafi/1/edit?html,output
Click the add button a few times and you should see the items all with the same values repeated in the row as I expect it to work:

Now try the same thing with v0.10.2
http://jsbin.com/moboqobiba/edit?html,output
This time some of the values stop rendering and are inconsistent, even though they should all be referencing the same value:

In a more complex app I'm seeing this manifest itself in strange random ways such as some cart-items or the cart total not updating and every time I've confirmed that the values are correct and if I output them in the template instead of passing them into a child element they show up correctly. In some cases, a repeat directive list will render correctly but the same items output with a map won't. When it happens, it's like the property setter is never being called at all.

This is caused by #241:

The template is stamped, but the cloned content is not yet adopted by the document (so custom elements are not upgraded yet, which is what #241 was all about)
The initial values are set
The clone is inserted into the document, it gets adopted which leads to the custom elements getting upgraded.

This means that in the constructor of the MyItem in the example, this.item can already be assigned to a value. This is similar to what went wrong in https://github.com/Polymer/lit-html/issues/237#issuecomment-355672630.
Fixing this should be as easy as moving line 182 to the bottom of the render function (working jsbin with the patch)
https://github.com/Polymer/lit-html/blob/0cde2220c1beb43ce4adcf5c21d01a6ab1507e92/src/lit-html.ts#L181-L185

I can confirm that also appears to fix it in the app as well - thanks for the detailed explanation 👍


use fmt library for C++ logging (IDFGH-8779)

Is your feature request related to a problem?
More powerful formatting for log messages
Describe the solution you'd like.
If using C++11/14/17: https://github.com/fmtlib/fmt
For C++20 it is part of the standard https://en.cppreference.com/w/cpp/utility/format
Describe alternatives you've considered.
No response
Additional context.
This would only work for C++

This might be something we could support in https://github.com/espressif/esp-idf-cxx repository, which contains C++-specific libraries for ESP-IDF. I would suggest moving this issue there.


serial server notes (from ITP workshop)

We had a workshop today with heavy use of the p5.js editor and the new serial server.  I'm making some notes here as I recall.  Some of these issues may be for the serialport repo.

Should editor include p5.serialport.js?  Probably not for every project.  Probably as some sort of "add library" option.
Does the editor restart the server on each run?  I was having issues with zombie console logging when sketches are closed.
There should probably be an "enable serial" editor option? No reason to run the serial server when not used.  Warn the user if they are including p5.serialport but not running the server?
Should there be a tool, like in arduino, to see the available ports and/or do some sort of serial monitoring (separate from println() in your code)?

We should meet and then we can break these out into separate issues depending on what we decide.
cc @lmccart @vanevery

Re:  "Does the editor restart the server on each run? I was having issues with zombie console logging when sketches are closed."  This may be an issue with the p5.serialserver itself, particularly the "stop" method so I'll open an issue over there just in case.
https://github.com/vanevery/p5.serialport/issues/11


Add opt-in Neuvector Security-as-Code Templates

Changes

Add chart containing Neuvector policies generated from a Gen3 platform in-use

Add values configurations to modify per your environment needs
Omitted Krum specifics
Added ability to upgrade policy enforcement modes

Test manually.

By default, this will not interfere with your platform functionality since we will start in Discover or Monitor mode rather than Protect

New Features
Default Security-as-Code templates that users may opt-in to install
Dependency updates
Neuvector and Neuvector CRDs (if the subchart is enabled)

Thank you so much for this code.
https://github.com/uc-cdis/gen3-helm/pull/181
Merging in another PR, to resolve some merge conflicts.


Malformed input can cause excessive memory allocation

Hi there,
I ran a fuzzer on this crate and it managed to uncover an out-of-memory crash.
From a very quick look at the code, it seems that read_byte_vec pre-allocates a vector with a size that is extracted verbatim from the input file (at least here and here - these are in the function that the fuzzer tripped on) allowing an attacker to craft an opus file that will exhaust the machine's memory, or otherwise cause excessive allocation.
I've attached the minimal test case (zipped because GitHub doesn't allow opus attachments to issues) produced by rust-fuzz, hope that helps.
Cheers
minimized-from-7bdc9f5196cea729c07f16f484685efc51ae4034.zip

Thank you very much for taking the time to find and report this.
May I ask how you did the actual fuzzing? I found cargo fuzz and just ran it with cargo fuzz run name_of_target. As far as I can tell, it "just" throws a lot of random bytes at the library it is testing.
It should be fixed it now. I now keep track of the length of the comment header and reject it, if it exceeds 120MB. This is mentioned in the specification as a countermeasure against such attacks.
While parsing the strings, I now check whether the strings length exceeds the remaining header and, if it does, abort parsing. This way the maximum memory allocation consists of a little more than 120MB for the Ogg pages and another 120MB for the parsed header, totaling 240MB.

May I ask how you did the actual fuzzing? I found cargo fuzz and just ran it with cargo fuzz run name_of_target. As far as I can tell, it "just" throws a lot of random bytes at the library it is testing.

libFuzzer - the underlying library used by cargo-fuzz - allows one to seed the fuzzer with examples, it'll then make randomised changes to the input.
I added the silence_standard.opus file provided in your test directory in the repo to the corpus/fuzz_target_1 directory in the fuzz harness and the fuzzer used that as a starting point.

Thanks for the explanation :)
(and sorry for the late reply)
I also just noticed that I totally forgot about pushing my fix to github... anyway, since I can run the tests with the file you provided without running out of memory (and it returns the expected error) I would assume this to be fixed.
Thanks for your help.


Not able to add an address with label to new organization

When I want to create a new organization with the Sdk4me.GraphQL version 1.4.3, I got next error:

Label is invalid

Below my code:
using Sdk4me.GraphQL;

Sdk4meClient client = new(
    new AuthenticationToken(
        "<enter id here>",
        "<enter key here>"
    ),
    "<enter account here>",
    EnvironmentType.Quality,
    EnvironmentRegion.EU
);

OrganizationCreatePayload payload = await client.Mutation(
    new OrganizationCreateInput()
    {
        Name = "Test Organization",
        NewAddresses = [
            new AddressInput() {
                Street = "Random address 1997",
                City = "Town",
                Zip = "80000",
                Label = AddressLabel.Home,
                Integration = true,
            }
        ]
    },
    new OrganizationQuery().Select(OrganizationField.ID),
    throwOnError: false);

if (payload.Organization is not null)
{
    Console.ForegroundColor = ConsoleColor.Green;
    Console.WriteLine(payload.Organization.ID);
}
else
{
    Console.ForegroundColor = ConsoleColor.Red;
    Console.WriteLine(payload.Errors[0].Message);
}

Console.ReadLine();

Could this bug be fixed?

@HeinPauwelyn,
While all addresses labels are defined in a single enum only street, mailing and billing can be used for organizations. They are listed on Organizations - Addresses API.

Oh now I see, the enum is reused for persons too. Thanks for the replay.


Fix for RHUI certificate issue in some RHEL based images

RHEL images on azure have certificate issues that can be resolved according to the following docs article:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/redhat/redhat-rhui#update-expired-rhui-client-certificate-on-a-vm
This issue is causing a bunch of failures on dpdk tests currently, so this commit adds the certificate fix to the tests.

Why produce a new PR?


Propogate error when rls is not found

Propogate error when rls is not found
Don't check toolchain/rls when rlsCommandOverride is present.

Currently server startup can return a non failing promise when Rls is missing, despite showing the correct error notification. This can cause atom-languageclient to show busy-signal 'initializing' without end, which is how I noticed it.
I also removed the toolchain/rls check when using rlsCommandOverride and simplified this branch of the code.

@mehcode I'll just merge smaller stuff like this in myself, and wait for review for bigger items if that's cool?


[WIP] Sidecars documentation

This is a placeholder PR for the docs for the Sidecars KEP
https://github.com/kubernetes/enhancements/issues/753

/milestone 1.16

@Joseph-Irving can you close this ticket since  this is now targeted for 1.17?


Cloud agent leads to infinite growth of IP rules

Describe the bug
The IP rules of cloud agent nodes have increased by approximately 400 records in 14 hours. I don't know if this will have an impact on the operating system

fabedge version: v0.8.0
os version: ubuntu 16.04

Found this issue with ubuntu, but there is no issue with Centos

Thanks for your reporting, I'll try reproducing it on ubuntu.


Bulk Data Transfer broken on ES 2.1.1?

I'm using the --bulk option, but it doesn't seem to work. When I don't use the bulk option, data transfers (but very slowly). With --bulk, I can see no documents get transferred (via Kibana), even though the elasticsearch-dump says it wrote them all. In my ES log I see:
ElasticsearchParseException[failed to parse source for create index]; nested: JsonParseException[Unexpected character ('"' (code 34)): was expecting comma to separate OBJECT entries
 at [Source: [B@252a9595; line: 9, column: 18]];

Here is my ES version:
{
  "name" : "trakit-staging01",
  "cluster_name" : "trakit-staging",
  "version" : {
    "number" : "2.1.1",
    "build_hash" : "40e2c53a6b6c2972b3d13846e450e66f4375bd71",
    "build_timestamp" : "2015-12-15T13:05:55Z",
    "build_snapshot" : false,
    "lucene_version" : "5.3.1"
  },
  "tagline" : "You Know, for Search"
}

Thoughts?

Can you please provide some sample documents and index to recreate this?

I have same problem.
elasticdump --bulk=true --input=./data/production_searchproduct_data.json --output=http://{ip_address}:9200/searchproduct/ --type=data
--I have this message
Wed, 13 Apr 2016 07:24:47 GMT | starting dump
Wed, 13 Apr 2016 07:24:47 GMT | got 100 objects from source file (offset: 0)
Wed, 13 Apr 2016 07:24:49 GMT | sent 100 objects to destination elasticsearch, wrote 100
Wed, 13 Apr 2016 07:24:49 GMT | got 117 objects from source file (offset: 100)
Wed, 13 Apr 2016 07:24:53 GMT | sent 117 objects to destination elasticsearch, wrote 117
but the new index is empty
while with elasticdump --input=./data/production_searchproduct_data.json --output=http://{ip_address}/searchproduct/ --type=data
it works correctly

Ok, I'm going to remove bulk mode entirely.  It's been buggy for a long time, and no one seems to have the time to fix it.
Closed by https://github.com/taskrabbit/elasticsearch-dump/pull/191


fix: add retries to notification config tests

Fixes #7859
The issue seems to be one-off. Couldn't reproduce it.
Closing it by adding retries. Kindly reopen if flaky in the future.

@Shabirmean  The other one fixes Batch test. This is for SCC.


[Script API] EntityHitEvent doesn't get triggered by entity hits into the air.

Describe the bug
When an entity(in this case a player) hits into the air without hitting an entity or a block, the EntityHitEvent doesn't get triggered. The documentation suggests that such case should still trigger the event with both hitEntity and hitBlock being undefined, which would be handy thing to have.
To Reproduce
Steps to reproduce the behavior:

Subscribe to the entity hit event in a script. Set it to print out values of hitEntity and hitBlock properties.
Left click with the mouse button while facing no entity nor block.
See no output by the event listener.

Expected behavior
Swiping into the air should trigger the event and print out the values of hitEntity and hitBlock both as undefined.
Desktop (please complete the following information):

OS: Windows 11
Minecraft Version: Preview <IP_ADDRESS>+

Hi, this is no longer related to current design, in latest Preview <IP_ADDRESS> was event split into two separated events, blockHit and entityHit, Thank you for your report.


[Hold][ENG-4265] Collection moderation submission sorting

Ticket: ENG-4265
Feature flag: n/a

Purpose

Allow moderators to sort collection submissions in moderation view

Summary of Changes

add dropdown to collection moderation app's submission view

Screenshot(s)

Side Effects

QA Notes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 71.881%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/collections/addon/provider/moderation/all/controller.ts
2
3
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
5575

Relevant Lines:
7539

💛  - Coveralls


Fix issues related to task/taskboard API

Issues fixed in this PR

[x] #170
[x] #171
[x] #176

What has been changed?

Removed unnecessary getting query set in TaskViewSet:list
TaskViewSet:list now only returns tasks that belong to the current user
TaskboardViewSet:create always binds the current user to the Taskboard object created

oops I forgot I worked on this branch. @ErikLupical, and @Jangsoodlor should review this then.


Seclist refusing to clone into my kali

Good day Daniel
Each time I try to git clone the seclist repo, it is extremely slow and then times out, leaving this error message as a result;
┌──(kali㉿kali)-[~/Documents/CTF]
└─$ git clone https://github.com/danielmiessler/SecLists.git
Cloning into 'SecLists'...
remote: Enumerating objects: 11021, done.
error: 1276 bytes of body are still expectedMiB | 181.00 KiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
Please is there a solution to this?

Can you clone other repositories?

Yes, I can clone other repositories
I just cloned sublist3r this morning
Thanks for your prompt response
On Sat, Jun 4, 2022, 2:55 AM Ignacio J. Perez Portal <
@.***> wrote:

Can you clone other repositories?
—
Reply to this email directly, view it on GitHub
https://github.com/danielmiessler/SecLists/issues/761#issuecomment-1146494511,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANEPSLSFVJEIYK2ZYTMLTF3VNKZR7ANCNFSM5XZUTLBA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Try cloning this repository again. If that fails, try updating git: sudo git update

Hi,
The problem is not present on a Ubuntu:

No problem on a Kali 2022.2 too:

I have the same version of git and the latest Kali version as well, what
else could be the problem?
On Sun, Jun 5, 2022, 3:37 PM Dominique RIGHETTO @.***>
wrote:

No problem on a Kali 2022.2 too:
[image: image]
https://user-images.githubusercontent.com/1573775/172055865-fdf254d5-e153-43c5-82ac-1ea725be29a9.png
—
Reply to this email directly, view it on GitHub
https://github.com/danielmiessler/SecLists/issues/761#issuecomment-1146816339,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANEPSLQA3ZOJ7QD3BGQ5XHLVNS3UNANCNFSM5XZUTLBA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I really do not know.
I retried after fully updading the Kali and I still not have error cloning the repository...

I had no problems here. You can try other methods of installing the repository besides git. Examples: https://kalilinuxtutorials.com/seclists-security-testers/

Thank you so much, I was able to download the zip file directly through the
link you provided.
Have a lovely day
On Sun, Jun 5, 2022, 4:20 PM Corvo @.***> wrote:

I had no problems here. You can try other methods of installing the
repository besides git. Examples:
https://kalilinuxtutorials.com/seclists-security-testers/
—
Reply to this email directly, view it on GitHub
https://github.com/danielmiessler/SecLists/issues/761#issuecomment-1146832939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANEPSLR7GTZNOBBZKLFQRL3VNTASJANCNFSM5XZUTLBA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You should be able to apt install seclists on Kali.
I'm guessing whatever partition you are trying todo it on, in in a format (e.g. fat32, NTFS, EXT4) which doesn't like "something".

First, turn off compression:
git config --global core.compression 0
Then do a partial clone to truncate the amount of info coming down:
git clone --depth 1 https://github.com/danielmiessler/SecLists
The change into the directory and get the rest
cd Seclists && git fetch --unshallow


Bolus cleanup

WIP: Don't merge
To fix:

discard differences in programmed vs. actual delivery below a certain threshold
verify or fix expectedDuration on extended or dual boluses that were cancelled after some insulin delivered

 <1> [tandem] boluses clean-up

 <1> [tandem] wizards clean-up


Tx pool check API

I can't get tx pool information from json_rpc. We can add it to json_rpc/index.js with getPoolSize and getPerAccountPoolSize.

Feature is added to develop branch!


ADD: Swap view only displays tokens with balance

At the moment the swap view is generic to all chains, leading to that when sending on a chain like ETH, all the tokens get displayed in a non interesting order.
Please implement that only tokens with balance are displayed and able to send. This can be done after #486 is implemented.

This is not correct , for example , I don't have any USDT , but I would like to swap some RUNE to USDT, if we only display tokens with balance , then USDT won't show up on the list , I won't be able to swap it.
I still rather user add the token first , and then swap from/to it

@yvebe did we also apply #329 to swap view? If so we can close.


fix: Key missing error in Boxed component

Description
Add Key to Boxed Component
Fixes # (issue)
Type of change
Chore
How Has This Been Tested?
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=5bbfd4d


JBoss EAP Standalone Remote Debugging

Hi everyone,
I'm trying to debug some custom application deployed in JBoss EAP.
My setup for it is like so:

standalone.conf enabled the following property:
JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
started jboss standalone on Terminal:
./standalone.sh --debug
Visual Studio Code's task.json has nothing special and works fine:
{   "version": "0.1.0",   "command": "mvn",   "isShellCommand": true,   "showOutput": "always",   "suppressTaskName": true,   "tasks": [       {           "taskName": "clean package",           "args": [               "-Plocal-deploy",               "clean",               "package",               "wildfly:deploy"           ],           "isBuildCommand": true       }   ] }
Visual Studio Code's launch.json I've tried this:
{           "name": "Debug JBoss",           "type": "java",           "request": "launch",           "stopOnEntry": true,           "cwd": "${fileDirname}",           "startupClass": "${fileBasename}",           //"jdkPath": "${env:JAVA_HOME}/bin",           "jdkPath": "/usr/local/java/jdk1.8.0_102/bin",           "options": [               "-classpath",               "\"${fileDirname};.\""           ],           "externalConsole": true,           "debugServer": 8787       }

With remote server started in debug mode, the console shows this when I try to connect to it:
Debugger failed to attach: handshake failed - received >Content-Length< - expected >JDWP-Handshake<
Does anyone has the same problem?
Thank you for the help by the way.

There might be a mistake with "debugServer": 8787, I think it should be "remotePort": 5005 instead.


GUI does not use translated files

I know the market rule is translated here:
https://github.com/BitShares/web_wallet/blob/b836a2aecde807eac58f45f3e823ce695e0d09e6/app/templates/context_help/zh-CN/market.html
but when I set my UI to zh-CN, the help file still show the EN file:
http://i.imgur.com/slqeTks.png

@svk31 oh great - I think you now can commit directly to the web_wallet repo

yep BM added me the other day :)


[WIP][Feature] Enable Swagger with API Versioning

Purpose
API Versioning (#6329) went out recently, and broke Swagger. This fixes Swagger.
Changes

Update DR(F|S) to versions allow Swagger to support Versioning
Update templates based on the DRS version bump 0.3 to 2.0
Copy/Modify helper function in rest_framework_swagger/views.py to allow kwargs through
Add default value for kwargs[user_lookup_url_kwarg] so that Swagger doesn't through a KeyError when building views.

Side effects
WIP: Bug noticed (possibly in DRS) with how API version is specified. The regex in urls.py is '^(?P<version>(v2))/, but this appears mishandled on the frontend, causing any input make a request to <base>/<input>)/, e.g. http://api.osf.io/v2)/. Fixing this may require a slight modification to our versioning system or a monkey patch.
Ticket
None known

Also, alternate implementation: The only thing I really like about DRS is the generation of the json file. Having it handle the creation and serving of the swagger-ui is inefficient and inconvenient. Better would be to have it create a static file either as an invoke task or on startup, then serving that information separately, so that we can upgrade or modify the swagger-ui independently of DRS.

And I talked with Chrïs. Having had to go through the last Django/DRF pain, he did not upgrade those for DjangOSF, so this can't happen until DjangOSF is out on production and we have a spare cycle for QA to test.

Improvements in API documentation obviate this (h/t @caseyrollins ), though we should still update Django/DRF in the near future. Closing this.


Pick up the latest updates to go-restful.

includes https://github.com/emicklei/go-restful/pull/199 and https://github.com/emicklei/go-restful/pull/200
Part of the fix for https://github.com/GoogleCloudPlatform/kubernetes/issues/4083 along with #6117

LGTM


Dio error after introducing null data object in 5.0.0+1

With version '5.0.0+1', there is a change where data objects are set to null when they are empty. This is breaking my code due to causing an error on Dio side with the following error:
DioError [DioErrorType.other]: type 'Null' is not a subtype of type 'Object'

@behnamsattar This PR is fixing it in the generator. CC @trevorwang


exclude ios vc by default

Currently, the BrowserViewController is excluded in the package only when the target is macOS. the BrowserViewController should be excluded for all targets except iOS.

Hi, thank you for your PR. I'm agree with your propose to exclude BrowserVC from all platforms except iOS. But we actually just drop it totally from within codebase in last patch. So there's nothing to exclude now actually.
But also I've mentioned that you've adding some Linux related thing within the code. Could you elaborate about its purposes?

@yaroslavyaroslav Cool. If BrowerVC is already dropped or will be dropped, then you can ignore this PR.
Sorry about the Linux commits, those weren't supposed to be part of the PR. I'm experimenting with Vapor and want to see what it would take to use Web3swift on the server. I can take that discussion to Discord

We've plans for porting ourselves to Linux platform as well, well, not so much porting as much as just drop all Apple locked dependencies, but there's actually none in currently contributors are, you know, drives it further.
So if you've keen on it -- you're more than welcome to push this side of this lib.

Cool. Yes, definitely interested. Let me first see if I can get it to run it quick and dirty. It might be less work that you'd think


support for promise-based block?

I'm thinking about customizing block operations on a per-individual basis.
For example, one part of code requires Auth API promise, another would require Item API promise.
What do you think about supporting individual-level customizable block API?
Example code:
history.block(async (location, action) => {
     ...
     try {
         const loggedIn = await getLogin( ... );
         return true;
     } catch { return false; }
})

Moreover, it might be better to have a generalized 'customized-catch-and-redirect':
history.beforeChange(async (location, action, callback) => {

    const userLevel = await getUserLevel( ...);
    if (userLevel == "admin") {
         return location
    }
    else if (userLevel == "user") {
         return modifiedLocationForNotAdmins;
     }
     else {
          return false; //block.
     }
});

Sure, I'd be open to including support for promises in the blocking API. Just needs a PR.


Benchmark scripts for republishing

Adds profiled benchmark scripts for the PublicationPresenter and also the PublishingApiWorker.
Uses StackProf to sample where the interpreter spends its time. It produces output like this:
$ bundle exec stackprof tmp/publishing_api_worker.dump --method PublishingApiWorker#call
PublishingApiWorker#call (/var/govuk/whitehall/app/workers/publishing_api_worker.rb:4)
  samples:     0 self (0.0%)  /   7099 total (97.7%)
  callers:
    7099  (  100.0%)  WorkerBase#perform
  callees (7099 total):
    7005  (   98.7%)  #<Module:0x007f3bb138d850>#with_locale
      80  (    1.1%)  #<Module:0x007f3bb8940250>.presenter_for
      13  (    0.2%)  ActiveRecord::FinderMethods#find_by
       1  (    0.0%)  ActiveSupport::Dependencies::ModuleConstMissing#const_missing
  code:
                                  |     4  |   def call(model_name, id, update_type = nil, locale = I18n.default_locale.to_s)
   13    (0.2%)                   |     5  |     model = class_for(model_name).unscoped.find_by(id: id)
                                  |     6  |     return if model.nil?
                                  |     7  |
   81    (1.1%)                   |     8  |     presenter = PublishingApiPresenters.presenter_for(model, update_type: update_type)
                                  |     9  |
 7005   (96.4%)                   |    10  |     I18n.with_locale(locale) do
                                  |    11  |       begin
block in PublishingApiWorker#call (/var/govuk/whitehall/app/workers/publishing_api_worker.rb:10)
  samples:     0 self (0.0%)  /   7005 total (96.4%)
  callers:
    7005  (  100.0%)  #<Module:0x007f3bb138d850>#with_locale
  callees (7005 total):
    6996  (   99.9%)  PublishingApiWorker#send_item
       9  (    0.1%)  ActiveSupport::Dependencies::ModuleConstMissing#const_missing
  code:
                                  |    10  |     I18n.with_locale(locale) do
                                  |    11  |       begin
 6996   (96.3%)                   |    12  |         send_item(presenter, locale)
                                  |    13  |       rescue GdsApi::HTTPClientError => e
                                  |    14  |         handle_client_error(e)
                                  |    15  |       end
                                  |    16  |
    9    (0.1%)                   |    17  |       if model.is_a?(::Unpublishing)
                                  |    18  |         # Unpublishings will be mirrored to the draft content-store, but we want

/cc @gpeng @mgrassotti

:+1:


Rename hw info class type to plugin name

This fixes API break from
https://github.com/ros-controls/ros2_control/pull/780

This now breaks with the setup:
ros2_control on humble and gazebo_ros2_control on master. @ahcorde can we have a humble branch?

Sorry @tonynajjar, I created the branch https://github.com/ros-controls/gazebo_ros2_control/tree/humble

Thank you @ahcorde!


无法进入容器执行 copydb 命令

Describe the bug
设置好 mysql 连接并成功创建新的数据库，希望将 sqlite 数据迁移至数据库。用 docker exec 命令进入容器执行 copydb 命令失败。
返回错误
“/bin/sh: can't open 'mysql': No such file or directory”
Steps to reproduce

Start memos container
run "docker exec -it CONTAINERID /bin/sh"
run "/usr/local/bin/memos --driver mysql --dsn 'dbuser:dbpass@tcp(dbhost)/dbname' copydb --from sqlite://path_to_your_memos_prod.db"
get error message “/bin/sh: can't open 'mysql': No such file or directory”

Screenshots or additional context
No response

0.17.1 会报错Error: unknown flag: --driver
0.17.0 可以使用/usr/local/memos/memos --driver mysql --dsn 'dbuser:dbpass@tcp(dbhost)/dbname' copydb --from sqlite://path_to_your_memos_prod.db

@leoshcn
The memos binary is located in /usr/local/memos/memos, NOT /usr/local/bin/memos, you should modify your command.
@jkjoy
I've tried the command provided by you, and there isn't any errors like unknown flag: --driver, could you provide more information about this?

@athurg  It works. But maybe the documentation should be updated
https://www.usememos.com/docs/advanced-settings/mysql

@athurg It works. But maybe the documentation should be updated
https://www.usememos.com/docs/advanced-settings/mysql

You're right, I have updated the document. Thank's for your suggestion.

0.17.1 使用docker run 会报错Error: unknown flag: --driver


Add [Constructor]Parameters types to lib.d.ts

Based on #26042 and discussion from the most recent design meeting. Thanks @anurbol for creating the initial PR.
It turns out that our tests have a couple of examples of looser definitions of Parameters. The differences are instructive:
type Parameters<T extends Function> = ((...args: infer U) => any) | (new (...args: infer U) => any) ? U : any[];

This looser definition allows:

Function to create an array of parameters any[].
Either constructors or functions to be passed in.
Tuple-constrained type parameters, for example T extends any[] to be used as the type of rest parameters.

(1) is pretty questionable and is fine to disallow, I think. (2) is now handled by Parameters vs ConstructorParameters. (3) is unsound, as pointed out in #26013, since it is equivalent to allowing the assignability of T extends any[] to any[]. So I think all 3 differences are improvements. I preserved them in the test baselines.
Fixes #26019

There were three questions involving Parameters on Stack Overflow just today: 1, 2, 3.  It would be great if Parameters got into the standard library before more people have to copy it into their own projects.


Serialization produces a null field, only when running on TestNG

TestNG Version
6.11
Expected behavior
A static method that throws no exceptions when wrapped as its class's main() method also throws no exceptions when wrapped as a test. Serialization behaves normally (i.e. non-transient fields that were non-null in the original object are also non-null in a copy made by serializing and deserializing).
Actual behavior
java.lang.AssertionError: @AssumeAssertion(nullness)
at betterrandom.prng.BaseRandom$BaseEntropyCountingRandom.checkedReadObject(BaseRandom.java:110)
at betterrandom.prng.BaseRandom.readObject(BaseRandom.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2136)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2027)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422)
at betterrandom.prng.BaseRandom$CellularAutomatonRandom.test(BaseRandom.java:299)
at betterrandom.prng.CellularAutomatonRandomTest.testSerializable(CellularAutomatonRandomTest.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:108)
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:54)
at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Is the issue reproductible on runner?

[ ] Shell
[X] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[X] IntelliJ
[ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue
BaseRandom.zip
See https://github.com/Pr0methean/betterrandom/tree/serialmcve for full context. The failure to replicate this when main() is the entry point is how I know this is a TestNG bug, and not a Java serialization bug or a bug in my own code.

FYI: This is the first case I've seen of a "reverse Heisenbug" -- one that occurs when it's being tested for in a formal testing framework, but can't be reproduced in production.

@Pr0methean - I was able to reproduce this exception even when running from within a main() method. So not sure how TestNG is involved here.
In order to simulate the problem, you would need to pass -ea to the JVM so as to enable assertions.
Here's the altered java class with the main() method.
public class CellularAutomatonRandomTest {
    public static void main(String[] args) throws IOException, ClassNotFoundException {
        new CellularAutomatonRandomTest().testSerializable();
    }

    @Test(timeOut = 15000)
    public void testSerializable() throws IOException, ClassNotFoundException {
        // Serialise an RNG.
        CellularAutomatonRandom rng = new CellularAutomatonRandom();
        CellularAutomatonRandom result;
        try (
                ByteArrayOutputStream byteOutStream = new ByteArrayOutputStream();
                ObjectOutputStream objectOutStream = new ObjectOutputStream(byteOutStream)) {
            objectOutStream.writeObject(rng);
            byte[] serialCopy = byteOutStream.toByteArray();
            // Read the object back in.
            try (ObjectInputStream objectInStream = new ObjectInputStream(
                    new ByteArrayInputStream(serialCopy))) {
                result = (CellularAutomatonRandom) (objectInStream.readObject());
            }
        } catch (IOException | ClassNotFoundException e) {
            throw new RuntimeException(e);
        }
        result.nextLong();
    }
}

Here's my run configuration

Here's the main() method output
Exception in thread "main" java.lang.AssertionError: @AssumeAssertion(nullness)
	at betterrandom.prng.BaseEntropyCountingRandom.checkedReadObject(BaseEntropyCountingRandom.java:25)
	at betterrandom.prng.BaseRandom.readObject(BaseRandom.java:98)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058)
	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2136)
	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2027)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422)
	at betterrandom.prng.CellularAutomatonRandomTest.testSerializable(CellularAutomatonRandomTest.java:49)
	at betterrandom.prng.CellularAutomatonRandomTest.main(CellularAutomatonRandomTest.java:33)

Hmm, I would've assumed IntelliJ would default to running in a "debug mode" that would include enabling assertions (especially since in one of my runs via main(), I had a breakpoint set). So can anyone possibly advise on how a non-transient field of Serializable (in this case AtomicLong) type that wasn't null when written can possibly become null when read back in?

BTW, I've only actually tested with a main() method in this simplified case; in the far-more-complex library where I encountered the issue, disabling assertions would only have turned their failures into harder-to-trace NPEs.

So can anyone possibly advise on how a non-transient field of Serializable (in this case AtomicLong) type that wasn't null when written can possibly become null when read back in?

Please check if this link helps answer your question : http://blog.clempinch.com/transient-and-final-instance-variables-in-java/

It doesn't, since the field I'm having issues with is not transient. However, it is final (I'm counting on defaultReadObject() to initialize it when no constructor gets a chance to do so, with only the usual fine print involving reflection and Objenesis backdoors); any resources you can recommend for other related serialization technicalities?

@Pr0methean - I found this article to be a bit interesting http://www.oracle.com/technetwork/articles/java/javaserial-1536170.html
We know

transient fields are ignored from serialization
for final data members, their default value (null for objects and for primitives their default values) is what gets assigned.

So if you would like your final data members to be initialised when the deserialisation happens then you might want to provide your own readObject() and writeObject() implementations in your class.

Closing off this issue, since its not a TestNG anymore, but more of a serialization/de-serialization related query.


Lockstep video record results in deadlock

Environment

OS Version: Ubuntu
Source or binary build? Source

Description

Expected behavior: Recording a video using the GUI and <lockstep>true</lockstep> should work.
Actual behavior: When <lockstep> is true then the GUI deadlocks.

Steps to reproduce

Modify the video_record_dbl_pendulum.sdf example world to set <lockstep>true</lockstep>
Run the world.
Select the video record button.

Instead of clicking on the button on the top left, if you load the Video Recording plugin from the plugin menu and start recording, the deadlock doesn't happen.
https://user-images.githubusercontent.com/206116/190283649-42744b94-8cb8-49c7-889e-0ec50d465c46.mp4

Hey, is the issue been resolved?

Hello, has the problem concerning the top-left button causing a deadlock been resolved?

As far as I know, it hasn't been addressed.


publish bug: pass claim_id for edits

If we're editing, pass the claim_id. This tells the backend to do a stream update instead. Helps if you have duplicate file names.
This is where it was added: https://github.com/OdyseeTeam/odysee-frontend/pull/1465

Patched, but since I can't see what's happening on the backend I'm kinda fixing this blind based on the linked PR. I'm not 100% sure if I'm supposed to pass claim_id or claimId. Please let me know if this works. Re-open if it doesn't.

Miko tested and it's not passing it still. Claim_id is correct. To confirm it's working, check the payload in network tab. Pretty sure this also has to be done on the publish preview call too.


cmd: sqlc init doesn't create an empty sqlc.yaml settings file

After installing sqlc using :
go get github.com/kyleconroy/sqlc/cmd/sqlc
I tried running the following command :
$sqlc init
Expected Output : sqlc.yaml file should have been generated by default as description suggests (Create an empty sqlc.yaml settings file)
Actual Output : Error: open : no such file or directory
sqlc version : v1.7.0

This has been fixed in v1.8.0


Add to cart: loading wheel always active

After completing the entire site and everything worked out wonderfully, that's where I click on add to the cart and the wheel turns but nothing happens.
I tried to figure out what had happened but it seemed all right.
Okay, I did everything from the beginning and it all works but here is the same thing now, the wheel is just turning.
What should I do? Rebuild everything from the beginning?
Environment Information
concrete5 Version
Core Version - 8.1.0
Version Installed - 8.1.0
Database Version -<PHONE_NUMBER>0000
concrete5 Packages
Breadcrumb Trail Page Links (1.1), Community Store (1.1.5), Community Store Toolbar Buttons (1.0), Login/Logout Link (1.0), Manual Nav (2.1.1), Neat (0.9.2), Paypal Payment Method (1.0), Styled Maps (1.2.3), Vimeo Video (1.0.2)
concrete5 Overrides
languages/cs_CZ/LC_MESSAGES/messages.mo, languages/cs_CZ/LC_MESSAGES, languages/cs_CZ, languages/da_DK/LC_MESSAGES/messages.mo, languages/da_DK/LC_MESSAGES, languages/da_DK, languages/de_DE/LC_MESSAGES/messages.mo, languages/de_DE/LC_MESSAGES, languages/de_DE, languages/el_GR/LC_MESSAGES/messages.mo, languages/el_GR/LC_MESSAGES, languages/el_GR, languages/en_GB/LC_MESSAGES/messages.mo, languages/en_GB/LC_MESSAGES, languages/en_GB, languages/es_PE/LC_MESSAGES/messages.mo, languages/es_PE/LC_MESSAGES, languages/es_PE, languages/es_PY/LC_MESSAGES/messages.mo, languages/es_PY/LC_MESSAGES, languages/es_PY, languages/fi_FI/LC_MESSAGES/messages.mo, languages/fi_FI/LC_MESSAGES, languages/fi_FI, languages/it_IT/LC_MESSAGES/messages.mo, languages/it_IT/LC_MESSAGES, languages/it_IT, languages/ja_JP/LC_MESSAGES/messages.mo, languages/ja_JP/LC_MESSAGES, languages/ja_JP, languages/nb_NO/LC_MESSAGES/messages.mo, languages/nb_NO/LC_MESSAGES, languages/nb_NO, languages/nl_NL/LC_MESSAGES/messages.mo, languages/nl_NL/LC_MESSAGES, languages/nl_NL, languages/pt_BR/LC_MESSAGES/messages.mo, languages/pt_BR/LC_MESSAGES, languages/pt_BR, languages/ru_RU/LC_MESSAGES/messages.mo, languages/ru_RU/LC_MESSAGES, languages/ru_RU, languages/sv_SE/LC_MESSAGES/messages.mo, languages/sv_SE/LC_MESSAGES, languages/sv_SE, languages/cs_CZ/LC_MESSAGES/messages.mo, languages/cs_CZ/LC_MESSAGES, languages/cs_CZ, languages/da_DK/LC_MESSAGES/messages.mo, languages/da_DK/LC_MESSAGES, languages/da_DK, languages/de_DE/LC_MESSAGES/messages.mo, languages/de_DE/LC_MESSAGES, languages/de_DE, languages/el_GR/LC_MESSAGES/messages.mo, languages/el_GR/LC_MESSAGES, languages/el_GR, languages/en_GB/LC_MESSAGES/messages.mo, languages/en_GB/LC_MESSAGES, languages/en_GB, languages/es_PE/LC_MESSAGES/messages.mo, languages/es_PE/LC_MESSAGES, languages/es_PE, languages/es_PY/LC_MESSAGES/messages.mo, languages/es_PY/LC_MESSAGES, languages/es_PY, languages/fi_FI/LC_MESSAGES/messages.mo, languages/fi_FI/LC_MESSAGES, languages/fi_FI, languages/it_IT/LC_MESSAGES/messages.mo, languages/it_IT/LC_MESSAGES, languages/it_IT, languages/ja_JP/LC_MESSAGES/messages.mo, languages/ja_JP/LC_MESSAGES, languages/ja_JP, languages/nb_NO/LC_MESSAGES/messages.mo, languages/nb_NO/LC_MESSAGES, languages/nb_NO, languages/nl_NL/LC_MESSAGES/messages.mo, languages/nl_NL/LC_MESSAGES, languages/nl_NL, languages/pt_BR/LC_MESSAGES/messages.mo, languages/pt_BR/LC_MESSAGES, languages/pt_BR, languages/ru_RU/LC_MESSAGES/messages.mo, languages/ru_RU/LC_MESSAGES, languages/ru_RU, languages/sv_SE/LC_MESSAGES/messages.mo, languages/sv_SE/LC_MESSAGES, languages/sv_SE
concrete5 Cache Settings
Block Cache - On
Overrides Cache - On
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).
Server Software
Apache
Server API
cgi-fcgi
PHP Version
5.6.28
PHP Extensions
bcmath, bz2, calendar, cgi-fcgi, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imagick, imap, ionCube Loader, json, libxml, mbstring, mcrypt, mhash, mysql, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, pdo_sqlite, Phar, posix, Reflection, session, SimpleXML, soap, SourceGuardian, SPL, sqlite3, standard, tidy, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, zip, zlib
PHP Settings
max_execution_time - 300
log_errors_max_len - 1024
max_file_uploads - 40
max_input_nesting_level - 64
max_input_time - 60
max_input_vars - 3000
memory_limit - 256M
post_max_size - 55M
sql.safe_mode - Off
upload_max_filesize - 50M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - no value
session.gc_maxlifetime - 7200
soap.wsdl_cache_limit - 5

This sounds like you have a javascript error on the checkbox page or similar.
What you need to do here is open up Chrome's Developer tools and have a look at what is happening when you try adding to the cart. Under the Console tab you may see a javascript error, or if that's not the case you should look at the Network tab and observe the requests. You should see something like the attached in a normal case, but if something is going wrong you should be able to see this via the response - they'll be the HTML of an error page instead of a smaller JSON response.
You should never have to rebuild anything from scratch in situations like this, it's always less work to debug and work out what is causing an issue like this. A rebuild is likely to end up with the exact same error if there's some sort of scripting conflict.
It would help if you you can push this development site up to an accessible URL.

what is happening when you try adding to the cart when open up Chrome's Developer tools:

I think this might be because you've moved the /cart page at some point
The /cart page needs to stay at the top level in the sitemap, otherwise you'll need to adjust the CARTURL at the bottom of community_store/controller.php to a new path.

This is my "Site Map":

So what happens when you visit /index.php/cart ?
I'd expect to see the actual cart page here
Or if you visit /index.php/cart/add ?
I'd expect to see an error message or a blank page

Perfect.
if you visit /index.php/cart see the actual cart page
but you click "add to cart" so you visit /index.php/cart/add see a blank page

Ok, in this case my suggestion would be that 'Mod Security' is blocking the post requests to /index.php/cart for some reason.
You could contact the host and ask them to check their mod security logs for this site, to see if they can see any rules being triggered for this url. If they are, you will need to ask them to 'whitelist' them
Otherwise feel free to send through a live URL to<EMAIL_ADDRESS>and I'll see if I can spot anything

The first time I installed "CommunityStore" on this specific site, it worked perfectly. Only after almost completing the entire site I noticed that it did not work anymore. As already mentioned just clicked on add to the cart, left the wheel and did not see the cart.
Now I'm trying to redesign the site to the local server, for now everything works fine, just complete I'll put the files and the database on the host server.
We will see what happens.

Make you sure understand my point about Mod Security - that's going to be down to the server detecting particular words or type of request, something you won't see on your local server.

ok. thank you.

Can I contact you privately in the email you provided to me?

Sure. I'm probably going to say the same thing though - you shouldn't ever have to rebuild a site to fix an issue like this

Just closing this as I think if it it's an issue it would need to be reopened with more detail

A simple note to this. If someone is googling:
We had a similiur issue where the sopping cart wasn't loaded. In our case the currency settings where the issue:
The sign for dividing the numbers for thousand in our case was: ' for 10**'**000
So that sign is causing an error in javascript. We used a blank instead an it worked.

@typoman76 that's interesting. The currency formatting was reworked not that long ago, it now should be more automatic. Do you know what version of Community Store you were using when this bug happened?


move officer's list to table

Convert officer list into markdown table

this is no longer an issue, or better yet worth addressing