Warn if JSON schema file is valid, but an "empty schema"

A JSON schema file that contains just {} is a vaild JSON schema as by draft-03, draft-04, draft-06 and draft-07. Same is true for a JSON schema file that contains at "root level" no typical JSON schema elements, but custom element names only.
(see: https://tools.ietf.org/html/draft-zyp-json-schema-03#section-5 for details)
These JSON schema files can be called "emtpy schema", as they are valid schema files but without any validation rule.
In fact, if an empty schema file is used to validate a JSON instance, then this instance is always valid (as it has no chance to fail; as there is no validation rule defined in that schema). A good validator should not error on "empty schema" files by default, but it should print a warning/info that this schema file is an "empty schema". An empty schema is not helpful, as it generates no business value and may lead into a false feeling of having all JSON instances successful validated.
To not introduce a backward compatibility break i recommend to implement a --strict flag.
When --strictis set, then the validator should fail + exit (with exit code != 0) when an "empty schema" is detected.
This is would be helpful for draft-03, draft-04, draft-06 and draft-07. At least on draft-07 there is  a small hint in the official JSON Schema documentation, but on all other drafts that is missing, which makes it hard for "first time users" (of JSON schema an validators) to spot that "empty schema" problem.

I'm not sure I follow/agree with your assertions.
An empty schema is useful in many of the same ways that say, the identity function is.

JSON schema + JSON instances are agnostic to programming languages. I think you could use a JSON instance directly without an "empty schema" the same way as you can use it as with an "empty schema".
JSON data producers can be implemented in programming language A, validator in B and consumer in C. If someone wants to use an identity function in the prefered programming language then he should be able to to that style/flavor independent from the fact that there is a schema, no schema or an empty schema.
If your code do not make assumption on the data structure of the JSON data, then you don't need a schema to validate it (but you may still want to validate it to ensure structure is consistent between datasets). If there is no need to validate the data structure, then i do not see a point in having an "empty schema" instead of no schema at all.
If i do not get your point: please explain your argument more in detail.

You're assuming one single scenario where the one schema someone is using
is the empty schema.
There are many others. Consider for example where an instance is fixed, and
someone is providing which schema to validate it with.
It's just not an error or warning condition -- same as if you wouldn't warn
if you were writing add(x, y) and someone passed y=0.
Sometimes the null thing is what sometime needs for some broader situation,
and warnings are just noise for them.
On Thu, Dec 5, 2019, 16:52 christian-weiss<EMAIL_ADDRESS>wrote:

JSON schema + JSON instances are agnostic to programming languages. I
think you could use a JSON instance directly without an "empty schema" the
same way as you can use it as with an "empty schema".
JSON data producers can be implemented in programming language A,
validator in B and consumer in C. If someone wants to use an identity
function in the prefered programming language then he should be able to to
that style/flavor independent from the fact that there is a schema, no
schema or an empty schema.
If your code do not make assumption on the data structure of the JSON
data, then you don't need a schema to validate it (but you may still want
to validate it to ensure structure is consistent between datasets). If
there is no need to validate the data structure, then i do not see a point
in having an "empty schema" instead of no schema at all.
If i do not get your point: please explain your argument more in detail.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Julian/jsonschema/issues/636?email_source=notifications&email_token=AACQQXQA7BKIEB7TNNREYMTQXFZ2BA5CNFSM4JV5ERN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGCI3XA#issuecomment-562335196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACQQXWVMDR6C5Q6B7HOMPTQXFZ2BANCNFSM4JV5ERNQ
.

I am trying hard, but i do not get your point.
Could you give a a concrete example of when a "empty schema" adds a benefit compared to NO SCHEMA? A sample JSON instance data + minimalistic implementation that uses an "empty schema" on that instance/data, that demonstrates why having an "empty schema" is better then NO SCHEMA. If you want to use an "empty schema" that is not equal to "{}" please also provide that schema.

I apologize for not really having a ton of time to write this out.
But I'd again basically encourage you to think about your last comment in the context of simple addition, in which what you're saying is "why bother having 0, if you don't have any number of things just don't write anything down at all".
It just turns out sometimes you still do want to write something down.
It's not for this library to decide when or why that may be, the user should decide, in the same spirit as "we are all consenting adults".
There just isn't any upside to such a warning.
Hopefully some of the above now starts to make sense, I'm going to close this since it's just not going to happen, but if it still doesn't feel free to respond and I'll make some effort when I have more spare cycles to have the dialog.

I kindly ask to implement a --strict option and only warn on "empty schema" when --strict flag is set.

With apologies, not going to happen -- I'm especially not in favor of arbitrary "strict" modes with no standard definition and no good way to have backwards compatibility.
If you want such a thing, you're free to create an alias or function that'd be fairly simple:
function jsonschema() {
    command jsonschema -i "${(P)#}" =(echo '{"not": {"enum": [{}]}}') && command jsonschema $@
}```

(not tested, but I'm sure you can see what's there).


fix: bump dependencies.

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.948%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
90

Relevant Lines:
117

💛  - Coveralls


Consider switching to react-jsonschema-form from vazco / uniforms

Is your feature request related to a problem? Please describe.
Each of the cellPlugins need various fields to be entered by the user, ie forms which are the bedrock of user input. This is currently realized with Uniforms. I would like to be able to show headings / help text / error messages etc for the form inputs on the cellPlugin control panel and this cannot be realized by Uniforms.
Describe the solution you'd like
Vazco / uniforms has a lot of limitations - it is not fully controllable from the schema and instead needs code (component) changes even to realize simple things like headings, help text for fields, error messages. See https://github.com/vazco/uniforms/discussions/912. The complicated solution from uniforms is this: https://uniforms.tools/docs/tutorials-customizing-your-form-layout.
Also the playground and docs of Uniforms is very limiting, without any details about the schema - https://github.com/vazco/uniforms/discussions/916
I'm proposing that we use react-jsonschema-form instead. Of course this might be a huge impact on the code, not to mention backward compatibility aspects.
Nevertheless, perhaps its worth discussing.

As a practical example, here's a Blurb plugin:

Now I want to be able to have a helptext for the "outside margin" field that says something as follows: No value uses default outside margin.
I dont see a way to do that using Uniform's schema.

you can show a helpertext simply with:
schema: {
  type: "object",
  properties: {
    outsideMargin: {
      type: "number",
      uniforms: {
        helperText: "No value uses default outside margin",
      },
    },
  },
};

Oh nice. Is there something for headings and error messages as well?


How to process 10ms audio frame

Hi, i found there is only support 8ms audio frame in this project, is it support 10ms frame?
Good luck.

Not yet.
But you can use a queue-buffer, which take 10ms-per-frame as input, and output 8ms-per-frame to the athena-signal project.

Thanks


Deployment check patch4

This change addresses various things:

Respect race conditions when checker pod starts up by utilizing KH_CHECK_RUN_DEADLINE -- described in #380 and #386
Add a function to pull KH_CHECK_RUN_DEADLINE from the environment variables
Report back to Kuberhealthy on the current state of the check when given interrupt / kill signal
Respect custom resource requests and limits on the deployment pods that are brought up during the deployment check described in #395 (adds CHECK_POD_CPU_REQUEST, CHECK_POD_CPU_LIMIT, CHECK_POD_MEM_REQUEST, CHECK_POD_MEM_LIMIT)

https://hub.docker.com/layers/kuberhealthy/deployment-check/v1.4.0/images/sha256-791a3de6c57dea569646d1d3b3e195d6f98a879cb98151db9983a2a8d5058081?context=repo


PFFile fails to save from iOS SDK 1.12.0 on parse-server 2.1.3

Just got this error message from iOS SDK
[Error]: Could not store file. (Code: 130, Version: 1.12.0)
The feature was working but stopped since I updated to the latest version. Unfortunately I don't have more information about the error yet cause parse-server isn't logging anything unusual. Below are dependencies I'm using:

I am also using the S3 adapter to upload files. In my main app.js file I have
var S3Adapter = require('parse-server').S3Adapter;
var s3Adapter = new S3Adapter('XXXXX', 'XXXXXX', {
  bucket: "img-images",
  region: "xxxxxx"
});

var api = new ParseServer({
  databaseURI: 'mongodb://xxx:xxxx@localhost:27017/xxx',
  cloud: appRoot + '/parse_cloud/main.js', // Provide an absolute path
  appId: 'xxx',
  masterKey: 'xxxxxx',
  filesAdapter: s3Adapter,
  serverURL: 'http://localhost:1337/parse',
  push: {
    ios: [
      {
        pfx: appRoot + '/apns_cert/apns-dev-key.p12', // Dev PFX or P12
        bundleId: 'com.xxx.xxxxx',
        production: false // Dev
      },
      {
        pfx: appRoot + '/apns_cert/apns-pro-key.p12', // Prod PFX or P12
        bundleId: 'com.xxx.xxxxxxx',
        production: true // Prod
      }
    ]
  }
});

Any ideas what could be wrong? Don't know if it could be related to issue #136. Thanks

Hey @vioside, looks like we don't fully expose the error on saving Files when using any provider - referenced in #661. I would recommend double checking your setup, but this said, I think if we do expose them - it would help you debug the issue.
Also would be a great help in debugging - simply logging the error in place which #661 highlights and putting it here.

Ok so I exposed the error as highlighted in #661 and I got more information. The error was Could not store file: InvalidParameterType: Expected params.Bucket to be a string (Code: 130, Version: 1.12.0)
Maybe the way we configure S3 has changed somewhere and now, instead of passing an object with bucket and region in the parameters, we just need to pass the bucket name like so:
var s3Adapter = new S3Adapter('XXXXX', 'XXXXXX', bucket: "[bucket name]");
Now the upload is working again! Thanks again for the pointers I'm saved :)


APEXMALHAR-1998 Set test log level to INFO.

@davidyan74 please merge, this reduces the logs generated by the build.
@vrozov We see all builds getting killed in the Kafka module. Could this be related to https://issues.apache.org/jira/browse/APEXCORE-335 ?

Yes, it may be related. Travis limits VM size, and https://issues.apache.org/jira/browse/APEXCORE-335 fixes resource leak. There may be other reasons why builds are killed.

Since this change is mainly for Travis and developers generally want the logging level to be DEBUG, can we set the logging level just for Travis to be INFO and leave the default logging level to be DEBUG?

Need to double check whether the Kafka test fails because of log overflow or due to memory limit in Travis environment.

Confirmed that build fails in kafka module without excessive logging also.

@tweise  this branch has conflicts. Can you please rebase?

@chandnisingh rebased and also changed to set INFO threshold in Travis only.


Rename project from Project Manger

Result:

I think you should remove the target name (Haxe) when edit begins.

Or what about using the rename dialog avoiding all issues?

Good point - it's fancier to rename in the tree but it would be fair to prompt for a new name.

After last commit:

@elsassph: Should we merge this as such and not with a dialog? Ok for me.


Add Space mapping

What
Add Space to Room mapping
Why
blocker for Sanofi prod
Tested
Valid DTMI format

Hmm, not sure how dtmi:org:w3id:rec:Company;1 was able to merge to main to begin with. I'll remove it for now


Split out ecolor crate

Makes color its own crate and splits it in turn into lot of smaller modules.
Due to the generous imports of color structs this should not be a (hugely) breaking change!

Thanks! Please silence clippy with #![allow(clippy::manual_range_contains)]. I'm not a big fan of that warning. Perhaps we can add it to allow-section in Cranky.toml?


rss.js page error for the author, date and description

Summary
When I start the react.dev in my local system that time I get this error.
This error comes because of some of the react.dev markdown file doesn't have an author, date, or description. It can be solve using proper error handling.
Page
https://react.dev/
Details
When I comment that unhandled area of the code then it run properly.

Related to #7085.

I fix that issue in #7159, but this is not merged at that time so the issue is continued in others.

Fixed by https://github.com/reactjs/react.dev/pull/7159


Support paths that contain directories with spaces in their names.

Currently paths that contain directories with spaces in their names cause the command to fail.
For example, if the directory of the lumen project is:
"/Users/MyUser/Code Repositories/MyLumenProject"
The serve command will fail with the following message:
"Directory /Users/MyUser/Code does not exist."
This is due to the string before and after the space being considered separate parameters.
The fix is to surround the path in quotation marks to ensure that the path is read in full.

Thanks!


Feature/check for equal engines

This will not work at all.

The feature has "Logger" as its only dependency. So it may start directly after the Logger, when ClusterComm and all this is completely dysfunctional. It must start after the coordinator is up and running and communication to other cluster nodes has been established.

This is WIP it was not ready for review. According to (the github workflow document) I am not allowed to set labels form group 9.

Ok. Just let us know when this PR is ready.

Is there a Jenkins run for this PR? If not, please start one.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr-linux/171/


WIDevine Installation Fails in 0.13.6

I'm submitting a ...

[ ] bug report
[ ] feature request
[X] support request

Description
I can install and run the newest version, even login to netflix. When I select an episode to play it goes thru the process of downloading large file and then prompts me that it may take 10 minutes to extract and I say ok. It thinks for a few minutes and then fails. "One of more items failed to play. Check the log for more information about this message."
Prerequisites

[X] Are you running the latest version? YES

Installation

[X] I installed the plugin via zip from the Releases page
[ ] I´m using the Netflix Repo (THE REPO IS CURRENTLY DOWN)
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[X] Linux (ARM)
[ ] Android

Additional informatin on the environment
See debug log for kodi version.
Debug log
https://pastebin.com/AZXCAmVR
It looks like the downloaded file fails a CRC32 check?

same problem here , I cannot play an episode I get the two messages shown below. And I dont know what to do. I chose No

hodor - you will have to say yes to that message. The issue I am experiencing is that even when I say yes, the process completes and then fails to play. Trying to play after that just prompts to do the update again.
This seems to be a glitch in inputstreamhelper. Either with the downloaded file CRC check, or with correctly identifying a related path. I have seen both errors in the log in my many attempts.

I pressed yes - but it doesnt solve the problem. No playback possible

The place to find help regarding Widevine installation issues is the repo of script.module.inputstreamhelper which provides the functionality for the plugin.
The video plugin itself just calls that one & itself has nothing to do with the Widevine installation itself.

problem solved after I updated to a new kodi alphabuild!

hodor - wondering what commit you used?

milhouse alpha from 28.5 arm-9.0-Milhouse-20180523224632

Just to update - tested that kodi commit and sadly it did not resolve for me. Something else going on in my case.


[RESOLVED] High ICMP ping response time

Problem started at 14:10:16 on 2023.06.28
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Operational data: Value: 929ms
Original problem ID: 31948
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23135&eventid=31948

Problem has been resolved in 6m 0s at 14:16:16 on 2023.06.28
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Original problem ID: 31948


Add external credit support

Implement external credit support in a separate tab in the main view
Use styled components instead of a css file to style the schedule + semesters
Refactor the schedule by using css grid instead of tables, which allows for more flexibility
Update color for courses that can fit in both semesters to a gradient
Fix bug where the delete course button was overflowing to the next line in small widths
Update tutorial colors

Resolves https://github.com/TigerPathApp/tigerpath/issues/101
Resolves https://github.com/TigerPathApp/tigerpath/issues/179
Schedule view:

External Credits view:

This looks really good!
The only issue I can see is that when you click on an external credit in the req tree, it disappears from the req tree and there's no way to bring it back other than to delete the class and readd it.
Also, we've discussed this, and maybe it doesn't have to be part of the MVP, but should be added at some point: there should be a way to pin additional requirements on external courses that have already been added. This is both for external credits that satisfy multiple requirements, and so that the user doesn't have to delete and readd them when they switch majors.

I agree with Barak that clicking on a req on the tree from external credit and making it go away doesn't really make sense (unless that's a bug) since the course is still on the schedule. Other than that, everything looks really good!

Clicking on the external credit in the requirements pane and having it go away is definitely a bug. Good catch, guys! I've fixed it and also addressed Barak's comments.


Amplify pod does not support new CLI release with customType and EnumPersistable

Describe the bug
I have updated my Amplify CLI after the new release to solve previous issues with [String] and enum types. But now when I run the codegen, xcode complains about undeclared type EnumPersistable as well as ModelFieldType has no member customType. It seems like the Encodable, Decodable issue is also not fixed yet.
Environment:

Amplify Framework Version: [e.g. 0.10.0]
Dependency Manager: [Cocoapods]
Swift Version : [5.0]

Hi @AnruStander, we're working towards a new release of Amplify, in the meantime, could you try pointing your pods to the master branch of this repo and give it a try?
  pod 'Amplify', :git => 'https://github.com/aws-amplify/amplify-ios.git', :branch => 'master'
  pod 'AWSPluginsCore', :git => 'https://github.com/aws-amplify/amplify-ios.git', :branch => 'master'
  pod 'AmplifyPlugins/AWSAPIPlugin', :git => 'https://github.com/aws-amplify/amplify-ios.git', :branch => 'master'
  pod 'AmplifyPlugins/AWSDataStorePlugin', :git => 'https://github.com/aws-amplify/amplify-ios.git', :branch => 'master'

Thanks, it was quite urgent at the time, so we had to use something else. But will try it again soon. Thank you.

@AnruStander since version 1.0.0 with enum support has been out for a few weeks I'll close this one. Let me know if you still have issues with enums.


Fix the bug that causes the unit summaries not to show up in the /listings view

Issue
Addresses #183

[X] This change addresses the issue in full
[ ] This change addresses only certain aspects of the issue
[ ] This change is a dependency for another issue
[ ] This change has a dependency from another issue

Description
I can't fully explain what this change is doing or why it works. How I arrived at this change: by observing that the unitsSummarized field in ListingDto was the only field that appeared to be defined by a get method; all other derived fields were decorated with the @Transform decorator (which the NestJS documentation is unfortunately quite light on.)
I dug into code that's involved in the serialization and recorded thoughts in https://github.com/CityOfDetroit/bloom/issues/183#issuecomment-885894007. That led to an observation of something being different between our code and Exygy's, but that difference didn't point towards an obvious solution. At that point, I stopped trying to understand the problem and switched to just trying reasonable things to fix the problem. And that's how I arrived at using the @Transform decorator to derive the unitsSummarized field.
The result: we got our unit summary table in the listing view back.

Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Prototype/POC (not to merge)
[ ] This change is a refactor/address technical debt
[ ] This change requires a documentation update
[ ] This change requires a SQL Script

How Can This Be Tested/Reviewed?
Viewed the fix in

[X] Desktop View
[X] Mobile View

Also confirmed that there were no new failing tests in backend/core.
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have reviewed the changes in a desktop view
[X] I have reviewed the changes in a mobile view
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] 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
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have assigned reviewers
[ ] I have updated the changelog to include a description of my changes

Please also contribute this upstream! (Maybe that will help us all understand why this works when the other way doesn't for us).

Thanks and sounds good - I'll send a PR to them!


Why should we make a "viewRay z division" to viewRayOS?

Good guy, I have some doubts when studying the code, why do we need to do perspective division on the ray from the model space camera to the vertex? In my cognition, perspective division is only to get the NDC coordinates, and there are some unclear meanings here.
大佬好，在研究代码的时候有一些疑惑，为什么要对模型空间相机到顶点的射线做透视除法，在我的认知里透视除法只是为了得到NDC坐标，而这里让我有些摸不到头脑
i.viewRayOS.xyz = i.viewRayOS.xyz / i.viewRayOS.w;

after i.viewRayOS.xyz /= i.viewRayOS.w;
i.viewRayOS is now an object space view direction with view space depth = 1 (not a unit vector).
cameraPosOS + i.viewRayOS * linearEyeDepth = reconstruct scene position in object space from depth texture

Okay, thank you for your reply, I think I already understand why, as shown below

In addition, I wrote a technical blog to analyze this project, hoping to help those who want to understand the principles of the project，https://www.lfzxb.top/screen-space-decal-in-urp-study/


Auto class loader, similar to php. for lazy instantiation of objects

In My Application I just want to register classes and instantiate them only when needed. it will improve performance of app.
Please implement this if it is possible.
https://www.php.net/manual/en/language.oop5.autoload.php
Thank you

Take a look at the section 'Lazily loading a library' in the language tour.


Node system requirements

Hello. What are the system requirements for installing this node? In the documentation https://docs.seinetwork.io/nodes-and-validators/joining-testnets this column is empty.

Thanks for the heads up. Info is there now


"Relative" Asset Paths

Some assets (like shaders) refer to other assets by path. Currently, they must write out the full path which is inconvenient when moving assets around.
A function "PathRelativeTo" which takes two paths should be added to the AssetLoader, and then used in Asset.Load where appropriate.
Shaders/Default.xml -> PathRelativeTo("Shaders/Default.xml", "Default.frag") -> Shaders/Default.frag

The tilemap already does this by loading tilesets relative to the map file/tileset folder, using GetNonRelativePath(folder, filePath)
ShaderAsset can pass in its directory in this way as well.
The only case I haven't thought out is when a path isn't relative. Since engine paths omit the "./" used to denote the current folder, maybe an existence check for the specified path should be done first, before relative is assumed.


Raspberry Pi GPIO control in electron App

I have created a simple app that can control the GPIO pins on the Raspberry Pi with a simple button press. However, when I press the button, there is no response from the GPIO pins (here connected to GPIO 24). Also, I have already installed the onoff module from npm install onoff. When I create a simple javascript file with only GPIO control and run node <file_name>.js, it runs successfully. But when I try to integrate into electron, it stops working. Please check the following code. Help would be appreciated.
index.html
<!DOCTYPE html>

GPIO Control

        <button id="Btn" class="button is-primary">LED ON</button>

main.js
const { app, BrowserWindow } = require('electron')
const path = require('path')

function createWindow () {
  const mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
        nodeIntegration: true
      }
  })

  mainWindow.loadFile('index.html')
}

app.whenReady().then(() => {
  createWindow()

  app.on('activate', function () {
    if (BrowserWindow.getAllWindows().length === 0) createWindow()
  })
})

app.on('window-all-closed', function () {
  if (process.platform !== 'darwin') app.quit()
})

render.js
var Gpio = require('onoff').Gpio;
var LED = new Gpio(24, 'out');

const Btn = document.getElementById("Btn");
Btn.onclick = function() {
  myFunction()
};

function myFunction() {
  LED.writeSync(1);
}

I'm afraid I'm not familiar with Electron and can't provide much help. Are error messages displayed when the application is run?

Duplicate of https://github.com/atom/atom/discussions/22638
onoff depends on a native Node module called epoll. Special steps need to be taken when installing native Node modules like epoll with Electron. For additional information see here.
If these special steps are not taken into account, errors complaining about incorrect NODE_MODULE_VERSION numbers like the errors shown here can occur.
@lakshanthad Is your application showing NODE_MODULE_VERSION errors or other errors?

might be the missing semi colon on myFunction call
Btn.onclick = function() {
myFunction()
};
also do not see in this code where you are loading the gpio library
On Wed, Jun 23, 2021 at 12:39 AM Lakshantha Dissanayake <
@.***> wrote:

I have created a simple app that can control the GPIO pins on the
Raspberry Pi with a simple button press. However, when I press the button,
there is no response from the GPIO pins (here connected to GPIO 24). Also,
I have already installed the onoff module from npm install onoff. When I
create a simple javascript file with only GPIO control and run node
<file_name>.js, it runs successfully. But when I try to integrate into
electron, it stops working. Please check the following code. Help would be
appreciated.
index.html

GPIO Control

    <button id="Btn" class="button is-primary">LED ON</button>

main.js
const { app, BrowserWindow } = require('electron')const path = require('path')
function createWindow () {
const mainWindow = new BrowserWindow({
width: 800,
height: 600,
webPreferences: {
nodeIntegration: true
}
})
mainWindow.loadFile('index.html')}
app.whenReady().then(() => {
createWindow()
app.on('activate', function () {
if (BrowserWindow.getAllWindows().length === 0) createWindow()
})})
app.on('window-all-closed', function () {
if (process.platform !== 'darwin') app.quit()})
render.js
var Gpio = require('onoff').Gpio; var LED = new Gpio(24, 'out');
const Btn = document.getElementById("Btn");Btn.onclick = function() {
myFunction()};
function myFunction() {
LED.writeSync(1);}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fivdi/onoff/issues/189, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMULCYHNN4TYAHU6OFRI3TTUFXQRANCNFSM47FBS4DQ
.

Hello. Thank you all for the replies. I have now made it work using ipcMain and ipcRenderer modules. Not sure whether there is an easy way to do this

Thank you for the feedback. I guess if it's working now the issue can be closed.

the ipcMain and ipcRenderer are the only ways to communicate between electron and an external Node instance. This functionality is to help maintain security on the host device when creating a shipped application.

I am trying to do the same. @lakshanthad  Can you share please show/share what you did to get it workin?

@TheGrateMartian
Here is a sample using ipc.
https://github.com/boraciner/electron-gpio


Autoclass is changing all the file modified dates

Current Report Index page generation is utilising the Last Modified date on GCP files to find which files to present as 'latest'. The AutoClass migration seems to be ruining this concept... This Issue lines out a working hypothesis...
Every time an old file is downgraded to a different storage tier it is copied to a new location (??)
This creates a new edit date (??)
This results in older files being flagged as latest on the report
Still need to nail down the cause here.
Might transition to using the dates in file paths instead of using created/modified dates.

Ugg what a pain, and what bad semantics from gcp.

The original migration incurred a change of the "modified time", as we had to made a full copy of all bucket contents to change the bucket's class to Autoclass. However, as far as I understand this should have been a one-time thing -- i.e. that should not happen for class migrations now that Autoclass is active...

Dropping in an example here - I've tried to tiptoe around this as I believe loading the HTML page may re-locate the file into standard storage and reset all the dates...
https://console.cloud.google.com/storage/browser/cpg-ravenscroft-arch-main-web/reanalysis/2023-02-20/summary_output.html
This file has a created date of 17 Feb 2023, 10:04 matching the time of the AutoClass migration, and was since superseded by a new run on March 13th, which was picked up in the report index at the time. The Modified date of the file is 19 Mar 2023, 10:54, and the storage class is Nearline so it has not been accessed in that time. That change came ~30 days after the migration took place, and the modified time was around Saturday at midnight, so must have been an automated change.
If this is right and the modified date is being tweaked by AutoClass that's a bit irritating, but a clean solution is for AIP to be logging analysis outputs into metamist, and reading the latest reports the same way - I probably should have been doing that from the start so it's not a huge problem.

I'm closing this as mitigated by the move to Metamist result logging

I'll ask Google tech support about this anyway.


getting server error 500 out of nowhere

Been working fine then all of a sudden I'm getting error 500. The devices that has been add still works but when I click on vera devices it's empty but the already configure devices populate when I click on it. please help troubleshoot this.

Will need to see the output file from the program that will have an exception in it.

What version of the ha-bridge are you using?

I did get the error as well.  I added my user and password and the error went away.  Worth a try

Michael... what username/pw are you referring to?
I'm using the latest version 4.5.6 I tried to run 4.5.0 yesterday by modifying my startup script with same result. :(

btw: Here's the log, not showing any errors unless there's another log?
`

11-14-2017 19:55:38.530
INFO
HA Bridge (v4.5.6) starting....
com.bwssystems.HABridge.HABridge

11-14-2017 19:55:38.654
INFO
reading from config file: data/habridge.config
com.bwssystems.HABridge.BridgeSettings

11-14-2017 19:55:40.210
INFO
HA Bridge initializing....
com.bwssystems.HABridge.HABridge

11-14-2017 19:55:40.222
INFO
System control service started....
com.bwssystems.HABridge.SystemControl

11-14-2017 19:55:40.236
INFO
Initializing UDP response Socket...
com.bwssystems.HABridge.util.UDPDatagramSender

11-14-2017 19:55:40.252
INFO
UDP response Seocket initialized to: 50000
com.bwssystems.HABridge.util.UDPDatagramSender

11-14-2017 19:55:40.254
INFO
Harmony Home created.
com.bwssystems.HABridge.plugins.harmony.HarmonyHome

11-14-2017 19:55:40.322
INFO
== Spark has ignited ...
spark.webserver.JettySparkServer

11-14-2017 19:55:40.324
INFO
>> Listening on <IP_ADDRESS>:80
spark.webserver.JettySparkServer

11-14-2017 19:55:40.608
INFO
setup initiated ....
com.bwssystems.HABridge.plugins.harmony.HarmonyServer

11-14-2017 19:55:42.934
INFO
activity changed: [29386065] Watch Fire TV
com.bwssystems.HABridge.plugins.harmony.HarmonyServer

11-14-2017 19:55:42.936
INFO
Nest Home created. No Nest configured.
com.bwssystems.HABridge.plugins.NestBridge.NestHome

11-14-2017 19:55:42.936
INFO
Hue passthru Home created. No Hue passtrhu systems configured.
com.bwssystems.HABridge.plugins.hue.HueHome

11-14-2017 19:55:42.938
INFO
HAL Home created. No HAL devices configured.
com.bwssystems.HABridge.plugins.hal.HalHome

11-14-2017 19:55:42.938
INFO
MQTT Home created. No MQTT Clients configured.
com.bwssystems.HABridge.plugins.mqtt.MQTTHome

11-14-2017 19:55:42.940
INFO
HomeAssistant Home created.  No Domoticz devices configured.
com.bwssystems.HABridge.plugins.domoticz.DomoticzHome

11-14-2017 19:55:42.970
INFO
Somfy Home created. No Somfys configured.
com.bwssystems.HABridge.plugins.somfy.SomfyHome

11-14-2017 19:55:42.972
INFO
LifxDevice Home created. No LifxDevices configured.
com.bwssystems.HABridge.plugins.lifx.LifxHome

11-14-2017 19:55:42.992
INFO
HABridge device management service started....
com.bwssystems.HABridge.devicemanagmeent.DeviceResource

11-14-2017 19:55:43.000
INFO
Hue description service started....
com.bwssystems.HABridge.upnp.UpnpSettingsResource

11-14-2017 19:55:43.006
INFO
Hue emulator service started....
com.bwssystems.HABridge.hue.HueMulator

11-14-2017 19:55:43.072
INFO
UPNP Discovery Listener starting....
com.bwssystems.HABridge.upnp.UpnpListener

11-14-2017 19:55:43.124
INFO
UPNP Discovery Listener running and ready....
com.bwssystems.HABridge.upnp.UpnpListener

11-14-2017 20:00:21.122
INFO
Link button pressed....
com.bwssystems.HABridge.SystemControl

11-14-2017 20:00:51.124
INFO
Link button time ended....
com.bwssystems.HABridge.LinkButtonPressed

11-14-2017 21:13:18.072
INFO
activity changed: [-1] PowerOff
com.bwssystems.HABridge.plugins.harmony.HarmonyServer

11-14-2017 22:31:42.814
INFO
Link button pressed....
com.bwssystems.HABridge.SystemControl

11-14-2017 22:32:00.110
WARN
Error calling out to HA gateway: IOException in log
com.bwssystems.HABridge.plugins.http.HTTPHandler

11-14-2017 22:32:00.110
WARN
Error calling out to HA gateway: IOException in log
com.bwssystems.HABridge.plugins.http.HTTPHandler

11-14-2017 22:32:01.233
ERROR

spark.webserver.MatcherFilter

11-14-2017 22:32:01.233
ERROR

spark.webserver.MatcherFilter

`

I believe there are some issues in the http handler. These will be corrected in 5.0.0

thanks, when can we expect to see v5 release? If u need a beta tester, I'll volunteer. It's already broken, it's not like it can be any worse. LOL

Little update:
Installed HA Bridge on another computer, copied the devices file over and reinitialize and it seems to be working fine over there. After I added the Vera device IP back in I can control it right out of the box. But I think my GH needs to be reconfigure to see the new Hue Device. At least this will get me going for now.

Great!


Checkpoints for 8-step models

Thank you for your excellent work! I was wondering if you have any plans to release the checkpoints for the 8-step models. Thanks a lot in advance.

So the "8 steps" in Figure 8 mean 4 forwards and 4 reverses? That make sense, thanks for your response!


LS fails to provide suggestions when cursor is at topline of an if statement

Please refer to below screen recording.

This has been fixed in the latest master. Hence closing the issue


Feature/updated plotting

Update the plotting to reflect the changes that were made for the 12/12/2023 TAG update meeting. Allows more flexibility by adding plotting parameters to the yaml file and cleans up the formatting.
Also included some bug fixes related to output generation in the CLI. Specifically to properly read in the wfe, wfsc, and sensitivity files, and to properly format and handle the input JSON file

I pushed a minor change to the input-path specification in <parameters.yml>.
When I execute the command <run_ebs scienceINstruments -sub QE -c inputs/parameters.yml>, I get the following error.  Could you look into this?
Traceback (most recent call last):
File "/home/pinchen/anaconda3/envs/exosims/bin/run_ebs", line 33, in
sys.exit(load_entry_point('ebs==0.5', 'console_scripts', 'run_ebs')())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/pinchen/anaconda3/envs/exosims/lib/python3.11/site-packages/ebs-0.5-py3.11.egg/ebs/cli_interface.py", line 63, in main
File "/home/pinchen/anaconda3/envs/exosims/lib/python3.11/site-packages/ebs-0.5-py3.11.egg/ebs/error_budget.py", line 969, in run_sweep
File "/home/pinchen/anaconda3/envs/exosims/lib/python3.11/site-packages/ebs-0.5-py3.11.egg/ebs/error_budget.py", line 380, in run_etc
File "/home/pinchen/anaconda3/envs/exosims/lib/python3.11/site-packages/ebs-0.5-py3.11.egg/ebs/error_budget.py", line 203, in compute_ppFact
ValueError: operands could not be broadcast together with shapes (4,) (5,)

run_ebs scienceINstruments -sub QE -c inputs/parameters.yml

Just pushed a commit that should fix this. The code is now expecting the input csv files to all have headers but I did not update the examples to include those headers.


Referencing a previous window function column produces nested window functions which are not allowed

What happened?
Using either sort b or sort c in the window function for d produces nested window functions which is not valid SQL (at least not in DuckDB).
PRQL input
from_text format:csv "i,a\n1,3\n2,1\n3,2\n4,3\n5,1"
select [i, a, b=lag 1 a]
window (
  sort a
  derive [c = lag 1 a]
  )
window (
  sort b
  #sort c
  derive [d = lag 1 a]
  )
sort i

SQL output
WITH table_0 AS (
  SELECT
    '1' AS i,
    '3' AS a
  UNION
  ALL
  SELECT
    '2' AS i,
    '1' AS a
  UNION
  ALL
  SELECT
    '3' AS i,
    '2' AS a
  UNION
  ALL
  SELECT
    '4' AS i,
    '3' AS a
  UNION
  ALL
  SELECT
    '5' AS i,
    '1' AS a
)
SELECT
  i,
  a,
  LAG(a, 1) OVER () AS b,
  LAG(a, 1) OVER (
    ORDER BY
      a ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
  ) AS c,
  LAG(a, 1) OVER (
    ORDER BY
      LAG(a, 1) OVER () ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
  ) AS d
FROM
  table_0 AS table_1
ORDER BY
  i

-- Generated by PRQL compiler version:0.8.1 (https://prql-lang.org)

Expected SQL output
I'm not sure but I suspect the expressions for `b` and `c` need to be wrapped in CTEs to make them referenceable in `d`.

MVCE confirmation

[X] Minimal example
[X] New issue

Anything else?
No response

Great bug report. Minimal amount of words to precisely explain the bug.


Update Go to 1.9.4

This is a security fix release of Go, see https://go-review.googlesource.com/c/go/+/73392
Some of the fixes may be relevant for Notary.
Signed-off-by: Justin Cormack<EMAIL_ADDRESS>

Rebuilding CircleCI now. LGTM pending tests.

Do we want to merge this or bump up to go 1.9.3?

When i opened this i thought the next release was about to happen so latest
1.8 made sense, but now as 1.10 is almost out so 1.8 will go.out of
support, moving to 1.9 makes sense, will update.
On 6 Feb 2018 20:06, "Ying Li"<EMAIL_ADDRESS>wrote:

Do we want to merge this or bump up to go 1.9.3?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/theupdateframework/notary/pull/1284#issuecomment-363530319,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdcPOY-3Yl-F0O386-Pc9nBcitUvMiMks5tSKKrgaJpZM4RR1mH
.

Ok, updated to 1.9.3

Hmm, failing on osx cross build issues that I can't replicate locally...

Of course 1.9.4 is out now, but the Docker images are not yet.

Thanks for updating this @justincormack!  Although this is kinda strange - I seem to be getting a bunch of windows related errors when running make cross locally:
# github.com/theupdateframework/notary/vendor/golang.org/x/crypto/ssh/terminal
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:42:16: undefined: windows.ENABLE_ECHO_INPUT
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:42:44: undefined: windows.ENABLE_PROCESSED_INPUT
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:42:77: undefined: windows.ENABLE_LINE_INPUT
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:42:105: undefined: windows.ENABLE_PROCESSED_OUTPUT
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:43:12: undefined: windows.SetConsoleMode
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:62:9: undefined: windows.SetConsoleMode
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:67:11: undefined: windows.ConsoleScreenBufferInfo
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:68:12: undefined: windows.GetConsoleScreenBufferInfo
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:91:10: undefined: windows.ENABLE_ECHO_INPUT
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:92:9: undefined: windows.ENABLE_PROCESSED_INPUT
vendor/golang.org/x/crypto/ssh/terminal/util_windows.go:92:9: too many errors

I resolved this by re-vendoring a more recent version of golang.org/x/sys.
The errors do seem to be happening in CI too, but it's not failing the build for some reason.

Ok, updated to 1.9.4 and updated the x/sys vendoring, builds fine locally.

Ok, I can see why the test passed, but fixing it shows some other issues...

Ok, fixed the cross build script to error out correctly, and also fixed the pkcs11 issues that showed up from that in addition to the Windows issues by updating that package.

@thaJeztah had a PR I've merged to just bump golang.org/x/sys. Can we reset that vendored package against master to remove the conflicts.

Ok removed and rebased.

LGTM


Advent

day1

day1

Cooking should not have been included. Also please give a better description. You could literally paste the task description and that would already be way better


Add/change highlight groups

What's the best way to add more groups (and maybe slightly override existing ones, for Telescope in my case) having access to colours defined in the scheme?
I was thinking, maybe some interface (from setup()) where one could have some callbacks receiving same arguments as functions in lua/nordic/colors/?

If you only need the palette, then you can just do this:
local palette = require('nordic.palette')
vim.highlight.create('TelescopeSomething', { guifg = palette.red })

If you need the other stuff, then this could be exposed in the configuration options as a callback I suppose :thinking:

Ah yeah, being able to use cs.bg('telescope') would be what I need for that very case.

Try https://github.com/andersevenrud/nordic.nvim/pull/49 . It gives you the option to define colors just like in this codebase via the discussed callback.

Works very nice and is exactly what I had in mind. So quick, thank you!

Great! Then I'll merge it :smile:


[Run] Unable to find windows terminal

Comments by @latipun7 copied from #3223
actually I didn't find Windows Terminal too.

I update terminal from windows store 1st then install PT msi. Otherwise I already restart my windows too, and it still can't find terminal (and ofc windows explorer too).
It only find already running instances.

@latipun7, can you pls confirm if you are able to search for other packaged applications like calculator etc?
Can you please try to exit powertoys, delete the following folder and try to search again. Let us know if the issue still persists.
C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run.

@alekhyareddy28

I've installed PT v0.18.2 on fresh windows machine.

@latipun7, Can you pls navigate to this location C:\Users\USERNAME\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs\X.X.X (Please replace USERNAME with your username and X.X.X could be any of the subfolders eg:1.0.0). There would be txt files under the Logs\X.X.X folder. Can you please check for the string 'UWP' in those log files ? If there is an error in retrieving information about any UWP application it would be logged there. Thank you.

@alekhyareddy28 This windows system is new, just install clean windows the other days and install power toys.
Even though I can see windows terminal and other packaged applications now, I didn't notice there's an error.
There's logs of errors everyday. I dump it everything here

Thank you for clarifying that you can find the packaged applications now.

Reopening it to see why this is happening to the UWP cache.

Based on the logs that @latipun7 shared, the issue was because AppXManifest.xaml was not accessible as another stream was using it. Here is quick overview of what happened :

"AppxManifest.xml" is opened as a stream with  Stgm.Read | Stgm.ShareExclusive Mode. Note:  In this mode, no other object can read/write to this file.
We use stream to get some information from AppxManifest.xaml.
We again try to read "AppxManifest.xml" to fetch some other metadata but since the stream in step 1 hasn't been disposed it leads to the following error:  " The process cannot access the file because it is being used by another process".

This should be fixed after #4217

Fixed in 0.19.0, please visit https://github.com/microsoft/PowerToys/releases/ for the latest release


DupElim implementation using only 128-bit hash codes

Based on discussion in https://github.com/uwescience/myria/pull/889.
Summary: instead of storing unique tuples for deduplication of input tuples, we store their 128-bit hash codes. For a sufficiently high-quality hash function (currently MurmurHash3, but we could switch to a fast cryptographic hash function like SipHash), this yields vanishingly small probability of collisions (e.g. 2^-49 for a trillion input tuples). This assumption that collisions are statistically impossible for a sufficiently large hash space (about N^3 for inputs of size N) is shared by many cryptographic systems as well as all content-addressable storage systems, such as git.
Since Java doesn't have a primitive type for 128-bit integers, we split the hash codes into two 64-bit integers and store them as the keys and values of a hash table. Until the number of input tuples approaches a billion or so, we don't expect collisions in the first 64-bit hash, so we separately handle collisions in an overflow table, with a special value in the main table to indicate collisions.
Note: it's currently unclear to me how to make this implementation fit into the StreamingState framework, like the current DupElim implementation. The hash codes don't seem to be a sensible output from the StreamingState.exportState() method, but I hope I'm misunderstanding something.
If possible, I'd like to benchmark this implementation against the current one for some very large datasets.

Coverage decreased (-0.1%) to 26.837% when pulling c0d773b71bd0fcf9282cf9b14ac60ba9a01ffb22 on dup_elim_hash into c21544a7697aabd8a9e7c980dab538e963757067 on master.

Coverage decreased (-0.1%) to 26.838% when pulling 6b876b80a905a467428627af801c45d028c8a700 on dup_elim_hash into c21544a7697aabd8a9e7c980dab538e963757067 on master.

FYI, there is a good discussion of hash collision probabilities (by an experienced crypto implementer) here: https://crypto.stackexchange.com/questions/39641/what-are-the-odds-of-collisions-for-a-hash-function-with-256-bit-output

How about using 64-bit hash code? My point is mostly for less memory consumption. It's 64 bits less per key comparing to 128-bit, and let's say the chance of a collision is 1/10. The cost of each collision is the size of the Java array that stores indices, let's say it takes 50 bytes. Then 64-bit still uses less memory than 128-bit.
You're right that StreamingState makes no sense for this DupElimHashOnly, maybe we can rename it to be StatelessDupElim or something like that.

I don't quite understand your comments. The point of this implementation is to avoid storing tuples at all, just hash codes. In order to do that, we have to avoid collisions entirely, since there is no way to resolve collisions without comparing against the actual tuple values. We don't store indices because there is no table of tuples to index into. The design of mapping 64-bit hash codes (first half of the hash value) to 64-bit hash codes (second half of the hash value), and also to an overflow table (second half of the hash value) for collisions in the first hash code, is just a workaround for the fact that Java has no 128-bit integer primitive type. Otherwise we would simply store a single set of 128-bit integers. I can explain the design further in the Myria meeting today if you want.

Oh I see I missed a point, the cost of a collision includes storing the tuples.

I was thinking about #889 when making the above comments so I'm copying them there.

Coverage decreased (-0.1%) to 26.84% when pulling 6ddec0409c459c79570ebd75edbdf55fe3f908a0 on dup_elim_hash into c21544a7697aabd8a9e7c980dab538e963757067 on master.

Coverage increased (+0.04%) to 26.999% when pulling 394e92fc99dde9a60cd71255c2d89d082a4116f7 on dup_elim_hash into c21544a7697aabd8a9e7c980dab538e963757067 on master.

Coverage increased (+0.02%) to 26.981% when pulling cb437a7f9d65393150b2902a287592e689f3ee0e on dup_elim_hash into c21544a7697aabd8a9e7c980dab538e963757067 on master.


Diagonal/Sparse Control Term

Hi,
I have to solve a bunch of fairly high dimensional SDE's, but I only have a diagonal diffusion matrix/control term.
As it turns out this is a fairly big bottleneck in my case, because I have already optimized the ode term.
Is there a way to use a sparse matrix to speed up the integration?
I tried to sparsify() diffeqsolve with the jax.sparse module, but I could not get it to work.
Passing just the diagonal as vector results in a the dot product being used for every dimension and one gets the same noise realization for each dimension.
Is there a way to cleverly pass only the diagonal array?
Thanks for the help!

I just found the example using a lineax linear operator in the docs.


refactor: use ngx-meta base URL and remove helper code

#477  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Independent schema is set for each consumer generated by topic

Motivation
Master Issue: #5454
When one Consumer subscribe multi topic, setSchemaInfoPorvider() will be covered by the consumer generated by the last topic.
Modification
clone schema for each consumer generated by topic.
Verifying this change
Add the schemaTest for it.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (yes)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@sijie PTAL

@congbobo184 Please look at sijie's comment.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

cherry-picked into branch-2.5


Automatically download optional simulators

A big advantage for me of Xcodes is when the betas are released I can set them downloading and then when I start work get straight to it.
Since Xcode 14 apple no longer include all the simulators with Xcode. I get why they do this, but it's still frustrating on first run, especially during beta season.
It would be amazing if I in Xcodes I could choose which extra sims I need (in my case, just watchOS) and then Xcodes could somehow always download them as part of their process.
Then as soon as Xcodes says it's done I'm ready to go :) I appreciate that this is a long shot, but I'm sure I'm not the only one frustrated by this.

FWIW, there seems to be a new simctl option for managing runtimes. simctl runtime lets you add / delete runtimes, but you need the disk image to be able to add a runtime. I don't see anything (at a quick glance) for getting a list of remote downloads available for runtimes and managing that.

In Xcode 15 you don't even get the iOS sims without downloading them after you open your project :|

Apple released separated runtime images. https://developer.apple.com/download/all/?q=runtime

Any plans for supporting this? the Xcodes CLI tool already supports downloading runtimes


Update README.md

Adding reference to report transparency

could you please review and merge this documentation update related to adding docu for reports transparency


Enable using V3 generator ourside of azure-sdk-for-net

Hi @pakrym ,
I see this has been closed; is there any indication when  autorest --csharp --v3 will use the V3 C# generator?
Waiting very patiently and excitedly for this. 😀
BR,
Mark

The autorest --csharp --v3 part is still being worked on. But there is a way to use V3 generator in your repo.
You can use the V3 generator outside of azure-sdk-for-net by referencing the
    <PackageReference Include="AutoRest.CSharp.V3" Version="1.0.0-alpha.20201013.3" />

from https://azuresdkartifacts.blob.core.windows.net/azure-sdk-tools/index.json feed.
Adding autorest.md file that poins to you swagger (remove space in between ```)
Run `dotnet build /t:GenerateCode` in src directory to re-generate.

`` ` yaml
input-file:
- https://github.com/Azure/azure-rest-api-specs/blob/615259b6d33d3029de2d6e403ffe0c12776da1d4/specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.1/storage.json
`` `

And running dotnet build /t:GenerateCode

Thanks for this, I will give it a go next week! Cheers!

Hi @pakrym , I did have a go with new C# generator (Version="1.0.0-alpha.20201021.2"). I tested with following autorest.md YAML:
input-file:
- https://github.com/OpenBankingUK/client-registration-api-specs/blob/e211e5eef8b9dfd907760b42723c31632a226e1d/dist/client-registration-openapi.yaml
output-folder: .
csharp:
  namespace: FinnovationLabs.OpenBanking.Library.Connector.ObModels.ClientRegistration.V3p2
  use-datetimeoffset: true

The generator has a problem with the csharp YAML options in autorest.md as shown above; they create this error:
EXEC : error : Cannot resolve pipeline stage 'openapi-document/identity'. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\AutoRest.CSharp.V3.targets(33,5): error MSB3073: The command "npx autorest@https://github.com/Azure/autorest/releases/download/autorest-3.0.6250/autorest-3.0.6250.tgz --skip-upgrade-check --version=3.0.6324 C:\Repos\Tmp\AutoRestTest\src/autorest.md  --use=C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\../tools/netcoreapp3.0/any/ --output-folder=C:\Repos\Tmp\AutoRestTest\src --namespace=AutoRestTest --shared-source-folders="C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\../content/Azure.Core.Shared/;C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\../content/Generator.Shared/"" exited with code 1. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]

But even removing these creates a failure with above document:
EXEC : warning (PreCheck/SchemaMissingType): The schema 'components┬╖1sjd0h8┬╖responses┬╖obclientregistration1┬╖content┬╖application-json┬╖schema' with an undefined type and 'allOf'/'anyOf'/'oneOf' is a bit ambigious. This has been auto-corrected to 'type:object' [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (PreCheck/EmptyParentSchemaWarning): Schema 'components┬╖1sjd0h8┬╖responses┬╖obclientregistration1┬╖content┬╖application-json┬╖schema' has an allOf list with an empty object schema as a parent, removing it. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (PreCheck/CheckDuplicateSchemas): Checking for duplicate schemas, this could take a (long) while.  Run with --verbose for more detail. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (Interpretations): Generating 'operationId' for 'post' operation on path '/register' [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (Interpretations): Generating 'operationId' for 'get' operation on path '/register/{ClientId}' [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (Interpretations): Generating 'operationId' for 'put' operation on path '/register/{ClientId}' [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (Interpretations): Generating 'operationId' for 'delete' operation on path '/register/{ClientId}' [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : warning (Modeler/MissingType): The schema 'components┬╖fj9vuw┬╖responses┬╖obclientregistration1┬╖content┬╖application-json┬╖schema┬╖allof┬╖1' has no type or format information whatsoever. Location: [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : error (): Duplicate Operation 'Optional' detected. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : error (): Duplicate object schemas with 'RegistrationError' name  detected. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
FATAL : error : 2 errors occured -- cannot continue. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
EXEC : error : Plugin checker reported failure. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\AutoRest.CSharp.V3.targets(33,5): error MSB3073: The command "npx autorest@https://github.com/Azure/autorest/releases/download/autorest-3.0.6250/autorest-3.0.6250.tgz --skip-upgrade-check --version=3.0.6324 C:\Repos\Tmp\AutoRestTest\src/autorest.md  --use=C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\../tools/netcoreapp3.0/any/ --output-folder=C:\Repos\Tmp\AutoRestTest\src --namespace=AutoRestTest --shared-source-folders="C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\../content/Azure.Core.Shared/;C:\Users\mark\.nuget\packages\autorest.csharp.v3\1.0.0-alpha.20201021.2\build\../content/Generator.Shared/"" exited with code 1. [C:\Repos\Tmp\AutoRestTest\src\AutoRestTest.csproj]
    8 Warning(s)
    5 Error(s)

Do you have any tips? 😀

You seem to have some duplicated schemas defined, are you sure every one of those are defined only once?

Thanks for quick response.
This is actually a file from a public standard (not my file) but seems to cause a problem because of multiple optional endpoints (three of them) and a claimed duplicate RegistrationError schema definition seems not to be correct (you can verify by quick text search here ).

Just to add, the Swagger 2.0 version of the same file works with the C# v2 generator so I think the file is okay. Also it previews fine in VS Code using the Swagger Viewer extension.
So maybe there are a few issues to be ironed out with the new generator unless I've made a mistake somewhere? Also can you make any comment about support for csharp options in autorest.md?

The V2 generator pipeline wasn't as strict as V3 and some swagger that worked before would contain errors. Feel free to file an issue in https://github.com/Azure/autorest/ repo that contains the duplicate checking logic.
I don't have an answer as to why having the csharp section makes generation fail.

Okay, thanks very much for your help, appreciated. I've raised this issue: https://github.com/Azure/autorest/issues/3621.


fix(plugin-react-refresh):  ensure decorators before export

fix #2776

Description

Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

which version contains this commit? please


mlflow autolog saves torchmetrics' differentiable as False

🐛 Bug
It's literally the same as the title. I'm using mlflow with pytorch lightning and torchmetrics. And, I found that mlflow's autolog method saved 'differentiable'. I assume this parameter came from torchmetrics.

To Reproduce
The example code is integrated with mlflow.(example code comes from official documents in torchmetrics)

Code sample
import os
import mlflow
from torch import optim, nn, utils, Tensor
from torchvision.datasets import MNIST
from torchvision.transforms import ToTensor
import pytorch_lightning as pl

from torchmetrics import MeanSquaredError

# define any number of nn.Modules (or use your current ones)
encoder = nn.Sequential(nn.Linear(28 * 28, 64), nn.ReLU(), nn.Linear(64, 3))
decoder = nn.Sequential(nn.Linear(3, 64), nn.ReLU(), nn.Linear(64, 28 * 28))

# define the LightningModule
class LitAutoEncoder(pl.LightningModule):
    def __init__(self, encoder, decoder):
        super().__init__()
        self.encoder = encoder
        self.decoder = decoder
        self.criterion = MeanSquaredError()

    def training_step(self, batch, batch_idx):
        # training_step defines the train loop.
        # it is independent of forward
        x, y = batch
        x = x.view(x.size(0), -1)
        z = self.encoder(x)
        x_hat = self.decoder(z)
        loss = self.criterion(x_hat, x)
        # Logging to TensorBoard (if installed) by default
        self.log("train_loss", loss)
        return loss

    def configure_optimizers(self):
        optimizer = optim.Adam(self.parameters(), lr=1e-3)
        return optimizer

# init the autoencoder
autoencoder = LitAutoEncoder(encoder, decoder)

# setup data
dataset = MNIST(os.getcwd(), download=True, transform=ToTensor())
train_loader = utils.data.DataLoader(dataset)

# train the model (hint: here are some helpful Trainer arguments for rapid idea iteration)
trainer = pl.Trainer(limit_train_batches=100,
                    max_epochs=1)

mlflow.set_tracking_uri('http://<IP_ADDRESS>:5000')  # set up connection
mlflow.set_experiment('TorchMetrics_dummy')          # set the experiment comes from args.Title
mlflow.pytorch.autolog(log_models=False)
with mlflow.start_run(run_name="test", nested=False) as run:
    trainer.fit(model=autoencoder, train_dataloaders=train_loader)

Expected behavior
I assume that mlflow should store differentiable parameter as True since default value of torchmetrics.MeanSquaredError is is_differentiable = True.
However, it saved as False.

Environment

torchmetrics==0.11.4
python==3.10.0
torch==2.0.0
pytorch-lightning==1.9.4
mlflow==2.3.1

Additional context

Hi @marquis08, thanks for raising this issue.
After running your provided example, I could reproduce the results. Looking at the source code of torch.optim.Adam we can see that all the logged parameters in mlflow are actually parameters of the optimizer. In particular, it has a parameter differentiable that is False by default:
https://github.com/pytorch/pytorch/blob/main/torch/optim/adam.py#L14-L27
The problem is therefore unrelated to torchmetrics, and in general it seems to work as intended.
Closing issue.


Update React Event Handler Docs To Be More Helpful

Hey! A small suggestion to your React Docs:
https://soapbox.github.io/linkifyjs/docs/linkify-react.html#events
let linkProps = {
  onClick: () => confirm('Are you sure you want to leave this page')
};

This is a great example of what most folks want-- a confirmation modal making sure that the user actually did want to leave the page. However, with this implementation, the 'Cancel' button triggers the default event anyway and will open the link.
let linkProps = {
  onClick: (event) => {
    if (!confirm('Are you sure you want to leave this page')) {
       event.preventDefault()
    }
  }
};

I'd love to change it so that your example covers the actual use case of canceling navigation when the "Cancel" button is pressed! I wasn't sure where I could suggest changes to your docs, so I'm posting it here. Let me know if this is something you'd like a PR (and where I can go to make those changes)-- I'd be happy to make one.

Hi @cranberryofdoom, great suggestion; pull requests are definitely welcome!
The docs for this repo are on the gh-pages branch. The React Events docs are at docs/linkify-react.md.


Fix master build message for Circle CI integration

Right now it is
Circle CI reports, another successful master build: https://circleci.com/gh/minishift/minishift/1566. Commit by Hardy Ferentschik: undefined

It should display the commit message

Merged via pull request #26


Try again later bug

Whenever I run the unfollow command, this bug shows up:

Facing the same issue.

now this is constantly happening, maybe an API change or rate limiting issue?


Add coverage to proxy for integration tests.

Fixes #1154

@rade @paulbellamy I think this is GTG

LGTM, with a squash


runtime: removing envoy.restart_features.remove_runtime_singleton

Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: inline

/retest

@zuercher ping?


Notice of Copyright/License Violation

This is an official notice of Copyright violation against the PIVX developers in which this project has been forked from. The MIT copyright license, and subsequent copyright headers in source files have been modified to explicitely exclude the PIVX developers.
You are hereby notified of an intention to pursue further action if this issue is not acknowledged and formally addressed with a resolution timeframe commitment wherein. Failure to acknowledge and correct the violation will result in a formal DMCA takedown notice filed with GitHub Proper after no less than five business days from the date of this notice.
Explicit acknowledgement and referencing progress to maintain compliance MUST be noted in this issue's comments or referred to in any subsequent pull requests to this repository.
Resubmitting this since the original repository was removed and recreated without addressing the issue at hand.

Addressed in Pull Req #4 - Issue closed and resolved.

you forgot the https://github.com/insta-cash/instacash/blob/master/COPYING file


[SPARK-13331] AES support for over-the-wire encryption

What changes were proposed in this pull request?
DIGEST-MD5 mechanism is used for SASL authentication and secure communication. DIGEST-MD5 mechanism supports 3DES, DES, and RC4 ciphers. However, 3DES, DES and RC4 are slow relatively.
AES provide better performance and security by design and is a replacement for 3DES according to NIST. Apache Common Crypto is a cryptographic library optimized with AES-NI, this patch employ Apache Common Crypto as enc/dec backend for SASL authentication and secure channel to improve spark RPC.
How was this patch tested?
Unit tests and Integration test.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can you change the title to say "AES support for over-the-wire encryption"?

ok to test

Test build #65779 has started for PR 15172 at commit da8aee6.

Test build #65779 has finished for PR 15172 at commit da8aee6.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65779/
Test FAILed.

That's a weird error... complaining about classes that really should exist. retest this please

Test build #65791 has started for PR 15172 at commit da8aee6.

Test build #65791 has finished for PR 15172 at commit da8aee6.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65791/
Test FAILed.

Replying to myself:
http://stackoverflow.com/questions/14935447/why-am-i-getting-package-javax-crypto-does-not-exist
Seems like we need a small tweak in the build code. I'll send a separate PR for that.

retest this please

Test build #65813 has started for PR 15172 at commit da8aee6.

Test build #65813 has finished for PR 15172 at commit da8aee6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65813/
Test PASSed.

Test build #65952 has started for PR 15172 at commit 06b0009.

Test build #65954 has started for PR 15172 at commit 9eb31e2.

Test build #65954 has finished for PR 15172 at commit 9eb31e2.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65954/
Test FAILed.

Merged build finished. Test FAILed.

Test build #65955 has started for PR 15172 at commit 535945c.

Test build #65952 has finished for PR 15172 at commit 06b0009.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65952/
Test FAILed.

Test build #65955 has finished for PR 15172 at commit 535945c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65955/
Test PASSed.

Merged build finished. Test PASSed.

Test build #66080 has started for PR 15172 at commit c1936eb.

Test build #66080 has finished for PR 15172 at commit c1936eb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66080/
Test PASSed.

To give you some pointers to what I think the AES path should look like:

decryption should work similarly to how CryptoInputStream works. It uses the Input interface which has a ReadableByteChannel implementation, but you don't really have a ReadableByteChannel here, just byte buffers. So you're gonna need some code to make those work together.

encryption: CryptoOutputStream has int write(ByteBuffer src) which should make it easy to implement the custom FileRegion used in Spark.

In both cases, there might be enhancements needed to the Commons Crypto library. That's something that we knew from the start. We should not provide a hacky implementation in Spark just because the features don't exist yet in Commons Crypto; this code has strict backwards compatibility requirements because it's used in the shuffle service, so we need a stable implementation from the start to avoid having to build version negotiation into the protocol.

Test build #66785 has started for PR 15172 at commit 0bf663f.

Test build #66786 has started for PR 15172 at commit 46b52e6.

Test build #66785 has finished for PR 15172 at commit 0bf663f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66785/
Test PASSed.

Merged build finished. Test PASSed.

Test build #66786 has finished for PR 15172 at commit 46b52e6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66786/
Test PASSed.

Test build #66812 has started for PR 15172 at commit deb63a7.

Test build #66818 has started for PR 15172 at commit 64b8f33.

Test build #66812 has finished for PR 15172 at commit deb63a7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66812/
Test PASSed.

Test build #66818 has finished for PR 15172 at commit 64b8f33.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #67245 has started for PR 15172 at commit 8d7532f.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67246/
Test FAILed.

Test build #67245 has finished for PR 15172 at commit 8d7532f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67245/
Test PASSed.

Test build #67248 has finished for PR 15172 at commit 3d463b3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67248/
Test PASSed.

Test build #67499 has started for PR 15172 at commit 76136c5.

Test build #67499 has finished for PR 15172 at commit 76136c5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67499/
Test PASSed.

Merged build finished. Test PASSed.

Test build #67545 has started for PR 15172 at commit f3e2518.

Test build #67545 has finished for PR 15172 at commit f3e2518.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67545/
Test PASSed.

Test build #67870 has started for PR 15172 at commit daed43c.

Test build #67870 has finished for PR 15172 at commit daed43c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67870/
Test PASSed.

Test build #67973 has started for PR 15172 at commit 7e1400d.

Test build #67975 has started for PR 15172 at commit f614691.

Test build #67976 has started for PR 15172 at commit 17427b4.

Test build #67976 has finished for PR 15172 at commit 17427b4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67976/
Test PASSed.

Test build #67973 has finished for PR 15172 at commit 7e1400d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67973/
Test PASSed.

Test build #67975 has finished for PR 15172 at commit f614691.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67975/
Test PASSed.

The configuration part is now ready.

Test build #68311 has started for PR 15172 at commit 7071ca6.

Test build #68313 has started for PR 15172 at commit 5ff19a5.

Test build #68313 has finished for PR 15172 at commit 5ff19a5.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68313/
Test FAILed.

Merged build finished. Test FAILed.

Test build #68311 has finished for PR 15172 at commit 7071ca6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68311/
Test PASSed.

Test build #68319 has finished for PR 15172 at commit c50e088.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68319/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68434 has started for PR 15172 at commit 573a8f3.

The encryption of config message was removed by mistake, very strange..  Add it back..

Test build #68434 has finished for PR 15172 at commit 573a8f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68434/
Test FAILed.

Test build #68438 has started for PR 15172 at commit cf7f62a.

Test build #68438 has finished for PR 15172 at commit cf7f62a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68438/
Test FAILed.

Test build #68444 has started for PR 15172 at commit 977bda7.

Test build #68444 has finished for PR 15172 at commit 977bda7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68444/
Test PASSed.

Test build #68467 has started for PR 15172 at commit cb93e18.

Test build #68467 has finished for PR 15172 at commit cb93e18.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68467/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68499 has started for PR 15172 at commit 6863efe.

LGTM, I'll leave it open a bit in case others want a second look.

Test build #68499 has finished for PR 15172 at commit 6863efe.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68499/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #68507 has started for PR 15172 at commit 6863efe.

Test build #68507 has finished for PR 15172 at commit 6863efe.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68507/
Test PASSed.

Merging to master.


Make InputHandling smarter; queue potentially multiple states per update frame.

@Tom94 this should fix the issue you were having, but I believe we can still go further in refactoring to decouple actual event firing from individual states. i don't think there are any adverse effects from firing events inside the foreach for now, but it doesn't feel as right as it should.


Question: Can the X1C3 be used without a battery?

Wondering if you are able to test if the X1C3 can be made to run directly off 5v with no power in. Want to use it in my car with no worry for charging it.

Sorry it took so long to get to that.
Yes, when the battery is completely disconnected, and power supplied to the USB, it powers on and otherwise works, which means you can keep it in your car forever with no issues.

Sorry it took so long to get to that.
Yes, when the battery is completely disconnected, and power supplied to the USB, it powers on and otherwise works, which means you can keep it in your car forever with no issues.

No apologies needed. Thank you so much for checking that!


[Tests] Improve model specs for Speaker

Should test associations, validations, and methods (see story or place specs for example of .import_csv method tests)

i'll take that issue :smile:

@GQuirino Thank you!

Merged in here! 83c5b51b34d1b07389b7c8afb08eb8810ac16653


Added support for annotating interface groups in KNE topology

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 54.101%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

topo/node/ixia/ixia.go
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

topo/node/ixia/ixia.go
1
8.92%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
1893

Relevant Lines:
3499

💛  - Coveralls


New list created with WiP limit not displayed as WiP list

Fixed hopefully. Added event handlers and refactored code to fix DOM for new list.


Update Image.js

small comment spelling correction. Also, I'm in love with your repo.

Thanks for the feedback :)


Additional settngs for db objects

postgresql allows to change some session settings for specific database objects (database, schemas, functions, roles etc). For example you can set character set for single function, or connection limit for role, or just custom config parameter for database.
Those
DBeaver doesn't show those settings. Would be nice to get them at least in DDL tab.
Example (from pgAdmin3)

thanks for suggestion


feat(app): Add file info page

overview
This PR closes #2129 by rendering FileInfoPage on successful protocol upload.

changelog

feat(app): Add file info page

review requests
TODO:

Refactor: move moduleInfo and pipetteInfo logic up to components/FileInfo
Point [calibrate labware] button route to first uncalibrated labware
Revisit after designs are finalized

Temporarily closing this PR to avoid clogging CI


A .gif should not be turned into thumbnail.

When you insert a .gif the editor gives it a width and height. Because of the width and height the thumbnails method in utils/html.py turns the .gif in a thumbnail. This makes the .gif freeze at the first frame instead of animating.
I found two workarounds for this problem.

If you upload a .gif for the first time and immediately place on you page it will not have a width and height in the HTML source. This way the thumbnails method doesn't turn in to a thumbnail. Unfortunately this only  works for a fresh upload.
Remove the width and height from the HTML source by hand.

A better solution would be to have the thumbnails method skip .gif images. I've tried the following code and it does the trick.
def thumbnails(html):
"""
Given a HTML string, converts paths in img tags to thumbnail
paths, using Mezzanine's ``thumbnail`` template tag. Used as
one of the default values in the ``RICHTEXT_FILTERS`` setting.
"""
from django.conf import settings
from bs4 import BeautifulSoup
from mezzanine.core.templatetags.mezzanine_tags import thumbnail

# If MEDIA_URL isn't in the HTML string, there aren't any
# images to replace, so bail early.
if settings.MEDIA_URL.lower() not in html.lower():
    return html

dom = BeautifulSoup(html, "html.parser")
for img in dom.findAll("img"):
    src = img.get("src", "")
    # check for gif
    if src[-3:] == 'gif':
        continue
    src_in_media = src.lower().startswith(settings.MEDIA_URL.lower())
    width = img.get("width")
    height = img.get("height")
    if src_in_media and width and height:
        img["src"] = settings.MEDIA_URL + thumbnail(src, width, height)
# BS adds closing br tags, which the browser interprets as br tags.
return str(dom).replace("</br>", "")

I think the best approach would be to skip animated gifs only. Regular
gifs are perfectly valid candidates for thumbnailing. I have no idea if
Pillow can tell those two apart, though.

I created a pull request to address this here:
https://github.com/stephenmcd/mezzanine/pull/1701


Minor fixes to links from closure updates

@samarsha - I fixed a few links from the closure updates you recently made. Not your fault - the doc conversion project is pretty basic and needs full URLs and the updated file names.

updated filenames in links from 'partialapplication.md' to 'closures.md'
updated relative links to full URLs
fixed Note formatting (from a previous edit pass)

Thanks!

Thanks! FYI - you can create any future docs PRs in the private repo, quantum-docs-private. It will flag someone on our team and run build checks to catch broken links, file discrepancies, etc.


reset threads in semidiscretize

I added the option to reset the threads from Polyester.jl in semidiscretize. However, I did not document it in the docstring since we have not documented that we use Polyester.jl threads in general - and the resetting is specific to Polyester.jl. I was not sure whether we still would like to keep the option to change the threading backend any time - although I do not see a good reason why we should do so.
Closes #1583

I was not sure whether we still would like to keep the option to change the threading backend any time - although I do not see a good reason why we should do so.

According to Chris Elrod, we are currently the only major user of some of the packages around Polyester.jl (and thus it is not clear how sustainable this will be in the long term). Thus for the future it might make sense to remain flexible here, but I'd be ok either way.

CI fails due to a problem with Makie.jl:
 Makie visualization tests for UnstructuredMesh2D: Error During Test at /home/runner/work/Trixi.jl/Trixi.jl/test/test_trixi.jl:187
  Got exception outside of a @test
  KeyError: key :colorscale not found

See https://github.com/trixi-framework/Trixi.jl/actions/runs/5641691392/job/15280161841?pr=1584#step:7:3754
This is not related to this PR, so we should be able to go ahead with it and debug the CI problem elsewhere


FID Curve

Great work! However, I use 4 x 3090 GPUs to train StyleSwin on the FFHQ-256 dataset, and evaluate FID on the same dataset. Then get the following FID curve from 0-500k after 4 days.

Is this normal? I might not see the probability of getting FID less than 10 after 1000k. Could you please show your FID curve in this dataset?

BTW, for each evaluation, the number of generated images is only 5000, because val_num_batches=1250 and val_batch_size=4.

We report FID between 50k generated images and 50k randomly selected images from FFHQ dataset, so maybe you should evaluate your training model again to see the fid score. The training fid curves could be found on link1 and link2.

Thank you! I got it.


:sparkles: Update go.mod

/test-integration

/test-integration

/approve
This goes back in the K8S version to be able to support the latest CAPI version that requires controller runtime 0.5.14 (instead of the 0.6.X we were using before). When we will take the v1a4 CAPI we will be able to properly uplift controller-runtime dependencies and match the kubernetes version.

/approve
This goes back in the K8S version to be able to support the latest CAPI version that requires controller runtime 0.5.14 (instead of the 0.6.X we were using before). When we will take the v1a4 CAPI we will be able to properly uplift controller-runtime dependencies and match the kubernetes version.

/lgtm

/lgtm


How to add blockchain level access control in this repository?

How to introduce blockchain level access control in the minimal contract present in this repository.
Our UI has been using this repository for quite some time now. Switching to composer will mena a lot of changes to the UI code.
Is there a way to introduce blockchain level access control, just the way done in another example of IBM blockchain "car lease demo"?
Appreciate an early response. Thanks.

Try to see if you can put in a field or header option stating who is accessing. This could be easily checked via a conditional statement to see who is accessing and accomplishing an assess control model

@risham33 I already planned to attempt something like this. But, for this I will need to make changes in the query methods inside of "iotcontractplatform". And once I do that I will start getting compile errors (during chaincode deploy). As per @kletkeman this is due to "not doing revendoring". I dont know how to revendor at this point in time. DO you have any clue?

@kletkeman Hi there!
Any clues how I can introduce chain code level security in this repository. Something that can be done quickly.
Thanks for all the information you have provided so far.

Hi all ... I have not formally verified the port of the IoTCP (contract platform) to fabric v1, and don't have an ETA for that.
What I would do (or preferably will do when there is time) would be to create a fairly simple mechanism with a known admin transaction that allows someone with an admin level account (which can be tested for by examining the ecert passed in and available at the getCreator stub API) and then set up roles with CRUD privileges. Each transaction would then read and check this RBAC table when executing, wince the user role is known from the ecert and the CRUD role is implicityly defined in the transaction code itself.
I hope that helps.

@kletkeman Hi there!
Appreciate the quick response from your side.
Is there a tutorial or link that one can follow in order to develop smart contracts for the hyperledger. I am looking for a comprehensive tutorial that talks about smart contract,  shim library, how a typical contract code is structured etc.
This will be a great help. Thanks!


Test CI with ephemeral cluster changes

Codecov Report

Merging #455 (bddbeb3) into main (eb53788) will increase coverage by 0.02%.
The diff coverage is 61.11%.

@@            Coverage Diff             @@
##             main     #455      +/-   ##
==========================================
+ Coverage   55.22%   55.25%   +0.02%
==========================================
  Files          48       48
  Lines        8751     8788      +37
==========================================
+ Hits         4833     4856      +23
- Misses       3175     3184       +9
- Partials      743      748       +5

Impacted Files
Coverage Δ

rpc/client/client.go
46.46% <0.00%> (ø)

state/executor.go
70.79% <30.76%> (-0.50%)
:arrow_down:

block/manager.go
62.46% <66.03%> (+0.08%)
:arrow_up:

store/store.go
66.23% <100.00%> (+0.44%)
:arrow_up:

Continue to review full report at Codecov.

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


Create a way to update mappings automatically

Will likely use a java version of https://gist.github.com/LambdAurora/b987fbb580827566ef1bf52bdde441de

My only worry with a Java version of this is stuff like the ASM lib, and stuff to parse tiny/Enigma mappings.
When I looked at those it looked way over-complicated, and possibly-breaking with time (looks at ASM lib being very strict on bytecode version).


Adds cursor design doc

Adds cursor design doc

I included those files by accident. Please ignore them for now.


Breaking TypeScript default export change undocumented

The 1.1.0 to 1.1.1 update was actually a breaking change for TypeScript users. (For JS consumers it could make sense for it to be a minor or patch.) The change to using default export typings is a welcome one but of course breaks existing import statements.
The usage for TypeScript for use with Webpack could be updated in README
import SpotifyWebApi from 'spotify-web-api-js';

let spotify = new SpotifyWebApi();

While this may be obvious to seasoned TS users working with default exports to not use {} or * as here is an explanation for others still learning. This works through the 1.1.1 to the current 1.2.0 releases.
This simplified import should resolve errors like TS2694 Namespace ... /spotify-web-api-js/src-typings/spotify-web-api has no exported member SpotifyWebApiJs, TS2305 Module ... /spotify-web-api-js/src/typings/spotify-web-api has no exported member SpotifyWebApi and error TS2351.

Fixed changing the README on https://github.com/JMPerez/spotify-web-api-js/commit/1487329717fc12665bd9b983b71040609bdb4069. Should have caught this one and ship a major update due to the breaking change.
The amendment in README will prevent other users from hitting this issue.