Liftmaster URI error

I have the wink platform working with several lights so i can say "Hey Siri, turn off front door light" and it works - which is amazing! I added a garage door opener this weekend and i am able to get the wink app to open/close the garage door when i press the button. However, when i say "Hey Sire, open the garage door" i get the following error:
Error 'null' logging in: {"Message":"No HTTP resource was found that matches the request URI 'http://myqexternal.myqdevice.com/api/user/validatewithculture?appId=JVM%2FG9Nwih5BwKgNCjLxiFUQxQijAebyyg8QUHr7JOrP%2BtuPb8iHfRHKwTmDzHOu&culture=en'."}
Also, I only have one garage door.
Config.json
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [
{
"platform": "Wink",
"name": "Wink",
"client_id": "i deleted this for the post",
"client_secret": "i deleted this for the post",
"username": "i deleted this for the post",
"password": "i deleted this for the post"
}
],
"accessories": [
{
"accessory": "LiftMaster",
"name": "Garage Door",
"description": "MyQ service.",
"username": "I deleted this for the post",
"password" : "I deleted this for the post"
}
]
}
Liftmaster.js
var types = require("HAP-NodeJS/accessories/types.js");
var request = require("request");
// This seems to be the "id" of the official LiftMaster iOS app
var APP_ID = "JVM/G9Nwih5BwKgNCjLxiFUQxQijAebyyg8QUHr7JOrP+tuPb8iHfRHKwTmDzHOu"
//var APP_ID = "Vj8pQggXLhLy0WHahglCD4N1nAkkXQtGYpq2HrHD7H1nvmbT55KqtN6RSF4ILB"
function LiftMasterAccessory(log, config) {
this.log = log;
this.name = config["Garage Door"];
this.username = config["i deleted this for the post"];
this.password = config["i deleted this for the post"];
this.requiredDeviceId = config["i deleted this for the post"];
}
LiftMasterAccessory.prototype = {
setState: function(state) {
this.targetState = state;
this.login();
},
login: function() {
var that = this;
// reset our logged-in state hint until we're logged in
this.deviceId = null;
// querystring params
var query = {
appId: APP_ID,
username: this.username,
password: this.password,
culture: "en"
};
// login to liftmaster
request.get({
url: "https://myqexternal.myqdevice.com/api/user/validatewithculture",
qs: query
}, function(err, response, body) {
if (!err && response.statusCode == 200) {
// parse and interpret the response
var json = JSON.parse(body);
that.userId = json["UserId"];
that.securityToken = json["SecurityToken"];
that.log("Logged in with user ID " + that.userId);
that.getDevice();

}
else {
that.log("Error '"+err+"' logging in: " + body);
}
});
},
// find your garage door ID
getDevice: function() {
var that = this;
// querystring params
var query = {
appId: APP_ID,
SecurityToken: this.securityToken,
filterOn: "true"
};
// some necessary duplicated info in the headers
var headers = {
MyQApplicationId: APP_ID,
SecurityToken: this.securityToken
};
// request details of all your devices
request.get({
url: "https://myqexternal.myqdevice.com/api/v4/userdevicedetails/get",
qs: query,
headers: headers
}, function(err, response, body) {
if (!err && response.statusCode == 200) {
// parse and interpret the response
var json = JSON.parse(body);
var devices = json["Devices"];
var foundDoors = [];

// look through the array of devices for an opener
for (var i=0; i<devices.length; i++) {
  var device = devices[i];

  if (device["MyQDeviceTypeName"] == "GarageDoorOpener") {

    // If we haven't explicity specified a door ID, we'll loop to make sure we don't have multiple openers, which is confusing
    if (!that.requiredDeviceId) {
      var thisDeviceId = device.MyQDeviceId;
      var thisDoorName = "Unknown";
      for (var j = 0; j < device.Attributes.length; j ++) {
        var thisAttributeSet = device.Attributes[j];
        if (thisAttributeSet.AttributeDisplayName == "desc") {
          thisDoorName = thisAttributeSet.Value;
          break;
        }
      }
      foundDoors.push(thisDeviceId + " - " + thisDoorName);
      that.deviceId = thisDeviceId;
    }

    // We specified a door ID, sanity check to make sure it's the one we expected
    else if (that.requiredDeviceId == device.MyQDeviceId) {
      that.deviceId = device.MyQDeviceId;
      break;
    }

  }

}

// If we have multiple found doors, refuse to proceed
if (foundDoors.length > 1) {
  that.log("WARNING: You have multiple doors on your MyQ account.");
  that.log("WARNING: Specify the ID of the door you want to control using the 'requiredDeviceId' property in your config.json file.");
  that.log("WARNING: You can have multiple liftmaster accessories to cover your multiple doors");

  for (var j = 0; j < foundDoors.length; j++) {
    that.log("Found Door: " + foundDoors[j]);
  }

  throw "FATAL: Please specify which specific door this Liftmaster accessory should control - you have multiples on your account";

}

// Did we get a device ID?
if (that.deviceId) {
  that.log("Found an opener with ID " + that.deviceId +". Ready to send command...");
  that.setTargetState();
}
else
{
  that.log("Error: Couldn't find a door device, or the ID you specified isn't associated with your account");
}

}
else {
that.log("Error '"+err+"' getting devices: " + body);
}
});
},
setTargetState: function() {
var that = this;
var liftmasterState = (this.targetState + "") == "1" ? "0" : "1";
// querystring params
var query = {
appId: APP_ID,
SecurityToken: this.securityToken,
filterOn: "true"
};
// some necessary duplicated info in the headers
var headers = {
MyQApplicationId: APP_ID,
SecurityToken: this.securityToken
};
// PUT request body
var body = {
AttributeName: "desireddoorstate",
AttributeValue: liftmasterState,
ApplicationId: APP_ID,
SecurityToken: this.securityToken,
MyQDeviceId: this.deviceId
};
// send the state request to liftmaster
request.put({
url: "https://myqexternal.myqdevice.com/api/v4/DeviceAttribute/PutDeviceAttribute",
qs: query,
headers: headers,
body: body,
json: true
}, function(err, response, json) {
if (!err && response.statusCode == 200) {
if (json["ReturnCode"] == "0")
  that.log("State was successfully set.");
else
  that.log("Bad return code: " + json["ReturnCode"]);
  that.log("Raw response " + JSON.stringify(json));

}
else {
that.log("Error '"+err+"' setting door state: " + JSON.stringify(json));
}
});
},
getServices: function() {
var that = this;
return [{
sType: types.ACCESSORY_INFORMATION_STYPE,
characteristics: [{
cType: types.NAME_CTYPE,
onUpdate: null,
perms: ["pr"],
format: "string",
initialValue: this.name,
supportEvents: false,
supportBonjour: false,
manfDescription: "Name of the accessory",
designedMaxLength: 255
},{
cType: types.MANUFACTURER_CTYPE,
onUpdate: null,
perms: ["pr"],
format: "string",
initialValue: "LiftMaster",
supportEvents: false,
supportBonjour: false,
manfDescription: "Manufacturer",
designedMaxLength: 255
},{
cType: types.MODEL_CTYPE,
onUpdate: null,
perms: ["pr"],
format: "string",
initialValue: "Rev-1",
supportEvents: false,
supportBonjour: false,
manfDescription: "Model",
designedMaxLength: 255
},{
cType: types.SERIAL_NUMBER_CTYPE,
onUpdate: null,
perms: ["pr"],
format: "string",
initialValue: "A1S2NASF88EW",
supportEvents: false,
supportBonjour: false,
manfDescription: "SN",
designedMaxLength: 255
},{
cType: types.IDENTIFY_CTYPE,
onUpdate: null,
perms: ["pw"],
format: "bool",
initialValue: false,
supportEvents: false,
supportBonjour: false,
manfDescription: "Identify Accessory",
designedMaxLength: 1
}]
},{
sType: types.GARAGE_DOOR_OPENER_STYPE,
characteristics: [{
cType: types.NAME_CTYPE,
onUpdate: null,
perms: ["pr"],
format: "string",
initialValue: "Garage Door Opener Control",
supportEvents: false,
supportBonjour: false,
manfDescription: "Name of service",
designedMaxLength: 255
},{
cType: types.CURRENT_DOOR_STATE_CTYPE,
onUpdate: function(value) { that.log("Update current state to " + value); },
perms: ["pr","ev"],
format: "int",
initialValue: 0,
supportEvents: false,
supportBonjour: false,
manfDescription: "BlaBla",
designedMinValue: 0,
designedMaxValue: 4,
designedMinStep: 1,
designedMaxLength: 1
},{
cType: types.TARGET_DOORSTATE_CTYPE,
onUpdate: function(value) { that.setState(value); },
perms: ["pr","pw","ev"],
format: "int",
initialValue: 0,
supportEvents: false,
supportBonjour: false,
manfDescription: "BlaBla",
designedMinValue: 0,
designedMaxValue: 1,
designedMinStep: 1,
designedMaxLength: 1
},{
cType: types.OBSTRUCTION_DETECTED_CTYPE,
onUpdate: function(value) { that.log("Obstruction detected: " + value); },
perms: ["pr","ev"],
format: "bool",
initialValue: false,
supportEvents: false,
supportBonjour: false,
manfDescription: "BlaBla"
}]
}];
}
};
module.exports.accessory = LiftMasterAccessory;

That is strange ... the version in master works fine for me? Have you made any modifications to this file? I notice the extra APP_ID parameter in your pasted source. Also the error complains about a URI that begins with http:// instead of the correct https://.

Thanks for the response. I checked the liftmaster.js file and all 3 URI references have https:// prefix. I thought that the appID was bad so I tried replacing that variable with another string that I was manually able to create and get an XML response that provided me with my garage door device ID.
Can you include your liftmaster.js file without your username, password and other specifics? I will replace what I have and see if that works.
Sent from my iPhone
On Sep 6, 2015, at 6:38 PM, Nick Farina <notifications<EMAIL_ADDRESS>wrote:
That is strange ... the version in master works fine for me? Have you made any modifications to this file? I notice the extra APP_ID parameter in your pasted source. Also the error complains about a URI that begins with http:// instead of the correct https://.

Reply to this email directly or view it on GitHubhttps://github.com/nfarina/homebridge/issues/136#issuecomment-138137131.
Confidentiality Notice: This e-mail communication and any
attachments may contain confidential and privileged information for
the use of the designated recipients named above. If you are not
the intended recipient, you are hereby notified that you have
received this communication in error and that any review,
disclosure, dissemination, distribution or copying of it or its
contents is prohibited. If you have received this communication in
error, please notify me immediately by replying to this message and
deleting it from your computer. Thank you.

A thought, do you have a garage door opener with wifi built in, or their ~2014 bridge device? I have the bridge device, and I found that I still needed to find and specify my garage door ID (I only have one opener also) because it counts the bridge as a device...so I had two device IDs. I don't recall getting the error you have, but it might have been.

I just got it to work... I don't think you need to modify the accessories/LiftMaster.js file, just add the blocks under accessories to the config.json file. I could not figure out my requiredDevice ID, so I used an empty value for the requiredDeviceID. The log of npm gave me these along with the descriptions. I plugged them in config.son file under two separate blocks. Siri is able to open and close them now.
However, the status in Insteon+(I am using this as the HomeKit DB) is incorrectly showing as open always. MyQ shows correctly and I have cameras in my garage to confirm the state of the garage doors!
Hope this helps (and someone can help me with the incorrect state of these doors in Insteon+)

Yeah--currently it only reports status right (at best) if you only open and close it via Homebridge...kindof annoying. It's on the list of things I want to write a pull request for. To do anything different it'll have to poll MyQ's services every few seconds...which hopefully won't annoy the MyQ servers... :-\

I cannot do anything via the Insteon+ app (neither open nor close my two garage doors). Siri works, and that is huge for me. Thanks to the developers for making this possible :-)

Man I'm glad I found this thread. I have been going nuts trying to get it to report the right open/closed status. I guess that just doesn't work right now. Pretty cool anyway, but the status would really make it sweet. So Liftmaster have said they are not going to make the "bridged" MyQ devices Homekit compatible, but it seems like this proves it is totally doable! Annoying.

It shouldn't be too hard to support "reading" status on demand similar to the Lockitron accessory - this way when you ask Siri or visit it in the app, the correct open/close state will be queried "on demand". Also it would be nice to upgrade this accessory to the "new API". I would welcome a PR if anyone wants to tackle it :)

It's on my list...other ideas for ZWayServer or YamahaAVR keep coming up :smile:

I'd certainly appreciate the on demand status working. Another question. Does the "obstruction detected" work? Not sure how I even expect that to behave.

I don't think it currently works. It should work with the IR safety sensors you can buy and attach to your opener near the bottom of the door track, to disable the door closing if someone or something is standing in the way. I have the sensors but I don't have them hooked up yet...another thing on my to-do list.

Not sure where to put this, but I copied the LiftMaster.js and altered it for Craftsman Assurelink, updating the URLS and the APP_ID variables to work.  Get the same issues with Insteon+ App not not reporting the correct garage door state, but Siri works :)

Hey that's cool! Could you post the values you changed to make it work? Perhaps we could enhance the shim to support both.

Sure thing... the value for the Craftsman Assurelink (basically the same as the MyQ Liftmaster, but different APP_ID and URL)...
APP_ID = "eU97d99kMG4t3STJZO/Mu2wt69yTQwM0WXZA5oZ74/ascQ2xQrLD/yjeVhEQccBZ"
... for the URLs, they need to start with "https://craftexternal.myqdevice.com/"..
That URL is hard-coded in 3 function calls in the existing Liftmaster.js accessory shim.
It'd be nice if we can get it working with Insteon+ :)  As others say in the thread, my door seems always open in the app and the buttons don't work.  Siri does tho, which is what I wanted it for.

In case anyone is interested I use an app called iDevices. It does not accurately reflect the door status, but it can open and close the door. It also works out of your home network which I've found other apps struggle with.


fix(assert): Allow access to Redactions

This can be used for very custom hacks

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/snapbox/src/assert/mod.rs
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.02%

Covered Lines:
1404

Relevant Lines:
2725

💛  - Coveralls


Arangodb Failover mode is not working as expected

Hi Team,
I'm using arangodb version as mentioned below
ArangoDB 3.3.12 [linux] 64bit, using jemalloc, build tags/v3.3.12-0-g225095d, VPack 0.1.30, RocksDB 5.6.0, ICU 58.1, V8 5.7.492.77, OpenSSL 1.0.2g  1 Mar 2016
And running arangodb starter.mode=failover with 3 nodes instances.
But when i starting arangodb  with this mode , it keeps on accumulating WAL logs on Leader node in path journals/archive folder which is almost 10X times the actual data size.
Also when the leader stopped and follower which becomes leader doesnt contains any data :(
Could you please provide the fix for this?
Thanks,
Rohan

What storage engine do you have in use?

What storage engine do you have in use?

Its rocksdb

Hi Team,
Is there any update on this?
Could you please respond on this?
Thanks,
ROhan

Hi @RohanKumbhar1,
first of all sorry for the late reply. How are things going, does the problem still persist? Is it reproducible in your environment?
If that is the case, could you please share the following information so that we can investigate this issue?

missing information from the info table, e.g. OS, Used Package etc.
the exact starter (arangodb) commands on each node to start the Active Failover instance
log files of dbserver + agent + coordinator from each node (located in the starter directory specified with --starter.data-dir)

@RohanKumbhar1
I am closing this issue since we have not heard back from you in a while.
In case you are still facing this problem, please share the requested information and we would be glad to look into it.
Please note that with 3.3.12 you are using a quite old version. The latest version available of the 3.3.x series is 3.3.23 and includes many improvements + fixes.


[FLINK-19420][docs-zh] Translate "Program Packaging" page into Chinese

What is the purpose of the change
Translate "Program Packaging" page into Chinese.
The page url is https://ci.apache.org/projects/flink/flink-docs-master/zh/dev/packaging.html
The markdown file is located in flink/docs/dev/packaging.zh.md
Brief change log
Translate "Program Packaging" page into Chinese.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi, @klion26
This PR is ready to be reviewed. Could you help to review it at your convenience?
Thanks.

Thanks for your kind reminder.
I have made the changes. PTAL.


Why does typescript-operations generate every filed as mandatory with ?

I have a type "personAlias", and query for it
personAlias {
        firstName
        lastName
        gender {
          code
          description
        }
      }

Type that gets generated for it looks like
export type PersonAliasType = {
   __typename?: 'PersonAliasType',
  firstName?: Maybe<Scalars['String']>,
  gender?: Maybe<RefDataType>,
  lastName?: Maybe<Scalars['String']>,
};

Notice that  gender is optional.
But in the end query it looks like
personAlias: (
        { __typename?: 'PersonAliasType' }
        & Pick<Types.PersonAliasType, 'firstName' | 'lastName'>
        & { gender: Types.Maybe<(
          { __typename?: 'RefDataType' }
          & Pick<Types.RefDataType, 'code' | 'description'>
        )> }
      )

Which makes it mandatory, which causes conflicts. Why? I have set as avoidOptionals: false

Can you share your schema please?

@n1ru4l
type PersonAliasType {
  dateOfBirth: DateTime
  firstName: String
  gender: RefDataType
  id: String!
  lastName: String
}

The types are Maybe types cause they could be null according to your schema

But null doesn't mean that they they are optional, it just means that they can exist with value of null. You can't have no key at all

Could you please provide a minimal reproduction using the code sandbox template (https://codesandbox.io/s/github/dotansimha/graphql-code-generator-issue-sandbox-template)?

@TheWWWorm In GraphQL, there are nullables and nonnullables. If you return undefined or null, it is considered as null. AFAIK, GraphQL Client returns null for undefined fields. But it would be great if you show your problem using the sandbox template as @n1ru4l asked.

Also, note that you can try to add avoidOptionals: true and it will avoid using ? while generating.

Closing. @TheWWWorm feel free to re-open/comment if this is still relevant.


homonym descriminator

homonyms in the names index can be resolved via authorship or in lost cases also the classification. this is needed for data missing authorship, especially lacking for monomials/higjer taxa which show most homonyms.
Instrad of using/comparing the entire classification store the highest rank that uniquely descriminates the homonyms. maybe as hstore inntje names index table?

we dont see the names index as a registry of names anymore


Update dependencies for jupyterlab_3 branch

I needed to bump the webpack dependencies to be able to install via pip for JupyterLab 3.
I'm not an expert in the JS ecosystem, so let me know if anything here is superfluous / the updates are too aggressive.

I think this can be closed now that https://github.com/maartenbreddels/ipyvolume/pull/355 is released.

Thanks for the work!

Excellent news, thank you for fixing!


Partition Support

Partitions are not supported, so Athena will not parallelize the query using partitions.

The main reason we wanted to use this SDK was to create Athena tables build from multiple individual file partitions, as in:
https://github.com/quiltdata/quilt-package-metadata-athena/blob/main/04_create_datalake_and_athena_tables.ipynb
In particular, we wanted to use Athena Federation directly rather than having to hack it with symlinks.
This appears possible with Java, though I'm not entirely sure how.
Would you expect that to work? If not, how hard do you think it might be to add full Partition support?

It shouldn't be too hard to add partition support - I thought I had a branch for this, but I can't find it now. In the Java example, we can see that the partitions are fetched as part of the doGetSplits function. So in theory it would be possible to do the same here.
The partitions need to be added to the schema as part of the table schemas and also added as metadata.


bug

tail -f /usr/local/nginx/logs/access.log  | goaccess --log-format=COMBINED -q -a -o /data/visit/status.html --real-time-html
Output all the time  like "Parsing... [520,438] [1,112/s]"，but no result。

Can you please try adding the extra dash in there,
tail -f access.log | goaccess - --log-format=COMBINED

tanks,but not helpful

Are you in v1.3?

thanks , I use 1.1.1，its work in 1.3


UMD and npm

Would you accept a pull request that adds a UMD shim, so mousetrap can work in AMD and commonjs environments (and of course also as a browser global)?
Also it could you publish mousetrap to npm, so that we can deprecate this shim?
Would make me as a browserify user very happy.
(as per https://github.com/component/mousetrap/pull/1)
Thanks

I came here because of the same problem. Mousetrap is on npm and it points to this repository. Sadly, it's not CommonJS compatible. I see pull request #145 adds an additional check for module.exports but wouldn't it be better to write the module in CommonJS and then make it AMD and global compatible with Browserify's --standalone option?
Like this:
browserify mousetrap.js --standalone Mousetrap

In VictorJS I make a build like this:
(echo '/*!' ; cat ./LICENSE ; echo '*/' ; browserify index.js --standalone Victor) > build/victor.js \
&& cat build/victor.js | uglifyjs -mc --comments '/^!/' > build/victor.min.js

It creates an UMD version - both minified and unminified -  for Bower and others, and adds the license at the top. And keeps the CommonJS version for Node and Browserify.

@maxkueng this project seems inactive.
I recommend my spork, which has already seen some community participation and has more than 400 stars.

@mightyiam yeah I noticed. I'm using your fork right now (thanks, btw!). But this project is still being used my a lot of people according to its download stats on npm. Would be nice it if could be somehow revived.


E-he*tai extension suddenly missing in just TachiyomiSY

Steps to reproduce
Opened the app yesterday, and the extension was still there. Upon opening it today, it has disappeared, and does not appear in the extensions list at all. Downloaded TachiJ2K and the extension was available to download in that.
Expected behavior
The extension should show up.
Actual behavior
The extension is missing. Also, any saved posts from the extension can still be opened in the library but the extension itself is missing.
Crash logs
No response
Tachiyomi version
1.9.0
Android version
Android 11
Device
Samsung Galaxy S20 FE
Other details
No response
Acknowledgements

[X] This is a TachiyomiSY specific issue that does not happen in Tachiyomi Preview.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 1.9.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Ehentwi is preinstalled so the extension doesn't show up. Enable it from filters in browse

Try force closing SY and re-opening


Requesting to add spocc download script

spocc_download.R contains code for download and visualizing species occurrence data from both the nic dataset and citizen science pulled from various databases (i.e., iNaturalist, GBIF). Download data will be added on the OneDrive.

Adding one more comment I forgot about, in reference to converting the workflow to a .Rmd you can actually just build off of the 01_process_occurrences.Rmd I already have in the root directory under the header at the bottom "Read and Process Additional Occurrence Data". So basically copy over the code in this R script and add the suggested edits in there.


kafka: split protocol generation into .h and .cc files

Commit Message: kafka: split protocol generation into .h and .cc files
Additional Description: instead of having enormous generated requests.h and responses.h, split them into header and implementation files - this will allow me to add proper static functions in the future (such as the one converting string request_name -> int16_t api_key for better configs)
Risk Level: low
Testing: unit and integration tests
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/retest

Good for review!
/assign @mattklein123

Good for review 2 (minor doc fix)


Do not crash if not in repo or ci

Fixes https://github.com/jumaffre/cimetrics/issues/61

no_crash_tarball@458 aka 20200225.14 vs master ewma over 4 builds from 445 to 453

This looks good but I wonder if:

Some of the error messages could be a little more explicit.
We could have less error handling/logging. Perhaps a single exception, with a single log message?

I have no functional objections however, I think this works.

I've made the error messages more explicit and removed some of the logging. We could make this an exception rather than returning None but we would still have to catch that exception every time we call get_env(), as the app using cimetrics should not crash if the environment is not valid. My preference is to leave it as it is for now.


Updating onnx.md and krnl.md

Right now, our doc dir has possibly outdated onnx.md and krnl.md files, which can be auto-generated from their respective Dialect/ONNX/ONNXOps.td and Dialect/Krnl/KrnlOps.td using the make onnx-mlir-docs command.
That make script generates the up to date files under the build directory. Kevin's suggestion is that we automatically move them under Docs/Dialect subdirectories, when we rebuild the *.td files
Would someone object? And someone knows how to do this in the cmake env?

Have you looked at make OMONNXOpsIncTranslation? It automatically generates .inc files and move them to appropriate places. I hope we can do the same for make onnx-mlir-docs

@tungld found a way, linked a PR that implements this change.

implemented in #972


Edit: ITV Patagonia

Channel ID (required)
ITVPatagonia.cl
Channel Name
No response
Alternative Names
No response
Network
No response
Owners
No response
Country
No response
Subdivision
No response
City
No response
Broadcast Area
No response
Languages
No response
Categories
No response
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
No response
Logo
https://www.itvpatagonia.com/wp-content/uploads/2022/06/logo-1000x1000-1.png
Notes
No response

Max allowed size of the logo  is 512x512 pixels. The link should not be geo-blocked


fix(@angular/cli): ng generate is not respecting --dry-run flag

This fixes #6810
#goodnessSquad

Actually I'm going to hold this. Schematics fixes the --dry-run flag the proper way, and we're almost ready to remove all our blueprints.

Schematics has been merged and released. This is fixed in the devkit repo. Closing this. Thanks!


Word status tracking parent status

Shouldn't the status of the word and its parent change at the same time?
It seemed to me that the whole point of this functionality was to be able to link different conjugations to a common parent and change statuses/translations in one place.

The initial point of the parents was to allow for entering the translation/meaning only once, and have that value be inherited and shown in the term hover.  For me that was always the huge pain point.
I didn’t think that status linking was as important, but others requested it, so it’s spec’d out in https://github.com/jzohrab/lute-v3/issues/66 and I’m working on it now.
I think this issue is a duplicate, please close it if so. Thanks!

Oh, sorry, I hadn't noticed. Thanks for letting me know.


app.setLoginItemSettings works incorrectly while packaged with the environment variable --win32metadata.requested-execution-level=requireAdministrator

Preflight Checklist

[x] I have read the [contribution documentation](https://github.com/electron/electron-packager/blob/main/CONTRIBUTING.md) for this project.
[x] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Packager Version:

15.5.1

Electron Version:

17.1.0

Operating System:

Windows 10 (21H2)

Behavior

I'm trying to add a feature to my Electron application to make it automatically run after my computer starting up. And this is my source code:
		ipcMain.on('EXCHANGE_OPEN_AT_LOGIN', (evt, openAtLogin) => {
			if (app.isPackaged) {
				app.setLoginItemSettings({
					openAtLogin,
				});
			}
		});

If I packaged my application with command like this , my application can be successfully self-booted.
electron-packager ./build SduMeeting --platform=win32 --arch=x64 --out ./dist --asar --overwrite

However, to implement certain features, I have to package it with command like this to get administrator privileges.
electron-packager ./build SduMeeting --platform=win32 --arch=x64 --out ./dist --asar --overwrite --win32metadata.requested-execution-level=requireAdministrator

The application packaged in this way cannot be opened automatically.
Additional Information

Excuse me, I'm a college student from a university in China with poor English. I wish my poor presentation wouldn't cause troubles for you.

Hey man, have you fixed this error yet?

Hey man, have you fixed this error yet?

Yes, I have solved this problem by modifying the Windows registry, but I am not sure that my method is appropriate.
You can see my code from the link below:
https://github.com/ch1ny/SduMeeting/blob/7ed5a51e2eac5716f16f30639455aa3d762b1260/main.js#L363
There may be other, better ways to work it out.

up


Update tf_records_generation.py

instead of by split building features, split training and test by tiles.

@Geoyi this is the code from #67, maybe you could give a check

@Geoyi , happy to know about my code could help with further users of lable-maker.


Fix service script for ubuntu

see comments in the changes

Thank you Fatih,
I will check it on weekend. Sorry for delay, too much work.
Thank you.

Sorry I was installed restyaboard in daemon's directory. So I have commited some files unnecessary(installation bash script and log file). I have deleted them at last commit. If you want, delete this pr and copy files from my repo by hand.
I have fixed service installation for ubuntu and windows(I have tried install and remove, they are working.).

Thank you Fatih,
Right now we have two different solutions under one pull request. Could you please split the pull request by on two different pull requests?

@takama I should close this pr and make two different prs, right? If yes, I will do in my next freetime(probably in today or tomorrow).

Yes, I will be very grateful to you for it.


update Flux.jl for GLPK v0.14.2

I updated Flux.jl to get it run with GLPK v0.14.2.
# ----------------------------------------------------------------------------------- #
# Copyright (c) 2020 Varnerlab
# Robert Frederick School of Chemical and Biomolecular Engineering
# Cornell University, Ithaca NY 14850

# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
# THE SOFTWARE.
# ----------------------------------------------------------------------------------- #

"""
    calculate_optimal_flux_distribution(S,[Lv,Uv],[Lx,Ux],c; min_flag=true)

    Computes the optimal metabolic flux distribution given the constraints.

    Inputs:
    `S` - stoichiometric_matrix (M x R)
    `[Lv,Uv]` - (R x 2) array of the flux lower (L) and upper (U) bounds
    `[Lx,Ux]` - (M x 2) array of species lower (L) and upper (U) bounds (if at steady-state, L = U = 0)
    `c` - R x 1 vector holding indexes for objective vector

    Outputs:
    `objective_value` - value of the objective function at the optimum
    `calculated_flux_array` - R x 1 flux array at the optimum
    `dual_value_array` - R x 1 dual values
    `uptake_array` - M x 1 array of S*v
    `exit_flag` = 0 if optimal
    `status_flag` = 5 if optimal
"""
function calculate_optimal_flux_distribution(stoichiometric_matrix::Array{Float64,2}, default_bounds_array::Array{Float64,2}, species_bounds_array::Array{Float64,2}, objective_coefficient_array::Array{Float64,1}; min_flag::Bool = true)

    # set some constants -
    TIME_RESTART_LIM = 60

    # Get the stoichiometric_matrix from data_dictionary -
    (number_of_species,number_of_fluxes) = size(stoichiometric_matrix);

    # # Setup the GLPK problem -
    lp_problem = GLPK.glp_create_prob();
    GLPK.glp_set_prob_name(lp_problem, "sample");
    GLPK.glp_set_obj_name(lp_problem, "objective")

    # Set solver parameters
    solver_parameters = GLPK.glp_smcp();
    GLPK.glp_init_smcp(solver_parameters);
    solver_parameters.msg_lev = GLPK.GLP_MSG_OFF;

    # Are we doing min -or- max?
    if min_flag == true
    	GLPK.glp_set_obj_dir(lp_problem, GLPK.GLP_MIN);
    else
    	GLPK.glp_set_obj_dir(lp_problem, GLPK.GLP_MAX);
    end

    # Set the number of constraints and fluxes -
    GLPK.glp_add_rows(lp_problem, number_of_species);
    GLPK.glp_add_cols(lp_problem, number_of_fluxes);

    # Setup flux bounds, and objective function -
    (number_of_fluxes,number_of_bounds) = size(default_bounds_array)
    for flux_index = 1:number_of_fluxes

    	flux_lower_bound = default_bounds_array[flux_index,1]
    	flux_upper_bound = default_bounds_array[flux_index,2]

    	# Check bounds type ... default is DB -
    	if (flux_upper_bound == flux_lower_bound)
    		flux_constraint_type = GLPK.GLP_FX
    	else
    		flux_constraint_type = GLPK.GLP_DB
    	end

    	# flux symbol? (later use name - for now, fake it)
    	flux_symbol = "R_"*string(flux_index)

    	# Set the bounds in GLPK -
    	GLPK.glp_set_col_name(lp_problem, flux_index, flux_symbol);
    	GLPK.glp_set_col_bnds(lp_problem, flux_index, flux_constraint_type, flux_lower_bound, flux_upper_bound);
    end

    # Setup objective function -
    for (flux_index,obj_coeff) in enumerate(objective_coefficient_array)

    	# Set the objective function value in GLPK -
    	GLPK.glp_set_obj_coef(lp_problem, flux_index, obj_coeff);
    end

    # Setup problem constraints for the metabolites -
    for species_index = 1:number_of_species

    	species_lower_bound = species_bounds_array[species_index,1]
    	species_upper_bound = species_bounds_array[species_index,2]

    	# defualt
    	species_constraint_type = GLPK.GLP_FX
    	if (species_lower_bound != species_upper_bound)
    		species_constraint_type = GLPK.GLP_DB
    	end

    	# set the symbol -
    	species_symbol = "x_"*string(species_index)

    	# Set the species bounds in GLPK -
    	GLPK.glp_set_row_name(lp_problem, species_index, species_symbol);
    	GLPK.glp_set_row_bnds(lp_problem, species_index, species_constraint_type, species_lower_bound, species_upper_bound);

    end

    # Setup the stoichiometric array -
    counter = 1;
    row_index_array = zeros(Cint,number_of_species*number_of_fluxes);
    col_index_array = zeros(Cint,number_of_species*number_of_fluxes);
    species_index_vector = collect(1:number_of_species);
    flux_index_vector = collect(1:number_of_fluxes);
    flat_stoichiometric_array = zeros(Float64,number_of_species*number_of_fluxes);
    for species_index in species_index_vector
    	for flux_index in flux_index_vector
    		row_index_array[counter] = species_index;
    		col_index_array[counter] = flux_index;
    		flat_stoichiometric_array[counter] = stoichiometric_matrix[species_index,flux_index];
    		counter+=1;
    	end
    end
    GLPK.glp_load_matrix(lp_problem, number_of_species*number_of_fluxes, GLPK.offset(row_index_array), GLPK.offset(col_index_array), GLPK.offset(flat_stoichiometric_array));

    # Call the solver -
    exit_flag = GLPK.glp_simplex(lp_problem, solver_parameters);

    # Get the objective function value -
    objective_value = GLPK.glp_get_obj_val(lp_problem);

    # Get the calculated flux values from GLPK -
    calculated_flux_array = zeros(Float64,number_of_fluxes);
    for flux_index in flux_index_vector
    	calculated_flux_array[flux_index] = GLPK.glp_get_col_prim(lp_problem, flux_index);
    end

    # Get the dual values -
    dual_value_array = zeros(Float64,number_of_fluxes);
    for flux_index in flux_index_vector
    	dual_value_array[flux_index] = GLPK.glp_get_col_dual(lp_problem, flux_index);
    end

    # is this solution optimal?
    status_flag = GLPK.glp_get_status(lp_problem)

    # Calculate the uptake array -
    uptake_array = stoichiometric_matrix*calculated_flux_array;

    # Formulate the return tuple -
    return (objective_value, calculated_flux_array, dual_value_array, uptake_array, exit_flag, status_flag);
end

Peter updated Flux.jl in  repo - AA tried new version. g2g


BACKLOG-2583 -- Upgrade to MongoDB Driver 2.13 for the MongoDB plugin -

PDI.
What was done:

changed driver version in property files

here is the link to corresponding component process case http://jira.pentaho.com/browse/COMP-1362
@m-a-hall could you please review?


[Feature] Add a client(SDK) manager

SDK manager holds a map of SDK clients, when used, you can get a client, just provide the server address, if the client not exist, the manager will create one and store it in the map.

@Pil0tXia the name SDKManager okay?

good idea

feature merged


docs: s/loadUrl/loadURL/g in docs-translations/

Run npm start, and show warnings in my console:
(electron) loadUrl is deprecated. Use loadURL instead.

#3424 updates, fix it.

:+1:


Nudge Suite missing in latest version

Is it correct that the Nudge Suite is missing from the latest release (<IP_ADDRESS>719), from the change logs I can not see any changes about this.
Could you please add the Nudge Suite version again?

It looks like the notary service was down right as the suite was being signed. Strange.

Fixed


ES6 issue with aliasify?

(I'm not sure if this is an issue with watchify or aliasify, so feel free to close the issue if needed.)
I have two simple npm scripts at the moment that are identical except for browserify vs. watchify:
"build": "browserify --extension '.jsx' -t 6to5ify -t aliasify app/index.js -o bundle.js -v -d"`
"watch": "watchify --extension '.jsx' -t 6to5ify -t aliasify app/index.js -o bundle.js -v -d"

My app/index.js file is in ES6 format. When I run npm run build, the file compiles successfully. npm run watch fails with the following error:
Error: Line 1: Unexpected reserved word (while aliasify was processing /Users/kshipley/Programming/rms/web-app/js/app/index.js) while parsing file: /Users/kshipley/Programming/rms/web-app/js/app/index.js

This repo is an extremely simple reproduction.
I'm working in a Flux-like architecture, so my overall goal is just to be able to require app/stores/foo.js from app/components/x/y/z/bar.js without having to back out of arbitrarily deep directory structures (e.g. import FooStore from ../../../../stores/foo). If there's a simpler way to do that than aliasify, I'm open to that as a workaround.

After updating the dependencies to:
  "devDependencies": {
    "6to5ify": "^4.1.1",
    "aliasify": "^1.7.2",
    "browserify": "^9.0.3",
    "watchify": "^2.6.0"
  },

it worked.


C# cleaner signal emission (v2)

Provides a type safe way to emit signals in c#.
Previous:
EmitSignal(SignalName.SomethingHappened, arg1, arg2, arg3);
// This does not have syntax highlighting and compile error when signature is not met.

Now:
GetEmitter<SignalEmitter.SomethingHappened>().Emit(arg1, arg2, arg3);

I also implemented that enums can be used.

Previous PR: C#: Cleaner signal emission
Can't be archieved seamlessly (allocations or pullotion)

Alternative: C#: Generate strongly-typed method to raise signal events and fix event accessibility

Pollutes classes
Shorter code
Guidelines

I'm a huge fan of this. I like how the type is leveraged for better compile-time checking and I especially need the enums as args. Since this is going to break the signal emission API, I say the sooner we merge the better 👍

cc @raulsntos @neikeq

This PR does not break compatibility so there's no rush to merge it.
I'd love to have a way to emit signals using a typed method but it's not clear which is the best approach. I personally favor my own implementation (#68233) over this PR.
My opinion on this PR:

I don't like how much more verbose this is compared to my version.
I prefer to follow the .NET event conventions more closely.
Accessing the Bounds property uses a callvirt, not sure how much of an impact this has on performance.
The new() constraint uses Activator.CreateInstance() which uses reflection, we may be able to avoid this in .NET 7 with static abstract members.

I kinda agree to the verbosity of this.
Would it be better to use default instead of new?

Would it be better to use default instead of new?

I think so, I'd also recommend using the struct constraint since we know all the TSignalEmitter types will always be structs and that will avoid the nullability warning.


Add toolfile and triplet to build with system provided clang and libc++

Add toolfile and triplet to build with system provided clang and libc++
Related: https://github.com/microsoft/vcpkg/issues/24086

I think there was currently a policy to not accept new community triplets. But people can correct me if I am wrong about that.

additional note, not sure there should be any changes to azure ci, maybe additional run for x64-linux-clang? your opinion is important

additional note, not sure there should be any changes to azure ci, maybe additional run for x64-linux-clang?

No.

I think this is ... dubious given that the resulting software isn't going to work in the vast vast majority of cases given that libc++ isn't link compatible with any system libs. Morever, it's not clear that someone asking for "clang" is going to also be expecting "libc++".


License of this project

Hey, I am working on a project that aims to be compatible to this plugin, however you haven't specified under which license your project/code falls and under what conditions one can adapt or work with your code.

Done!


feat(v2): display footer in docs page for consistency

Motivation
Previously, the sticky stuff on the docs page might not play well with a Footer underneath so we chose to leave it out. But since #1855, it is now possible to have consistent look like v1.
See https://github.com/facebook/docusaurus/issues/1598
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
Imgur
Imgur

Cool, thank you for this! :tada:


Create rules for bean property determination

According to the migration guide:

The core container performs basic bean property determination without java.beans.Introspector by default. For full backwards compatibility with 5.3.x in case of sophisticated JavaBeans usage, specify the following content in a META-INF/spring.factories file which enables 5.3-style full java.beans.Introspector usage: org.springframework.beans.BeanInfoFactory=org.springframework.beans.ExtendedBeanInfoFactory

Investigate and create rules if necessary.
In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.

This rule could look for java.beans.Introspector usage or BeanInfo implementations. Further investigation is needed.


Dragging in blocks result in a smaller editing pane

When one drags in a block from the palette into the bottom of the editing pane in blocks mode, the editing pane contracts vertically and one is no longer able to view the top lines of the program.

Additionally, when dragging a block into a socket, the socket does not highlight itself.


CI: bump versions to latest GEOS-3.9.1

GEOS 3.9.1 was recently announced. Bump the following GEOS versions:

Github Actions: 3.9.0 -> 3.9.1
AppVeyor: 3.8.1 -> 3.9.1

Thanks!


move-upload-csv-to-frontend

move the logic for Upload CSV from the frontend to the backend
closes #172

Hi Megha, this error should actually be fixed by this PR because clicking Add to Map will now open the first row on Mobile that has an error, so the tooltip should show up in the right place.

Hi Megha, this error should actually be fixed by this PR because clicking Add to Map will now open the first row on Mobile that has an error, so the tooltip should show up in the right place.

Gotcha!


Use settings.type for name conversion

fix #31 quickly and dirty-ly

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

great i need this too , is this all ready patch and update on npm package  ?

@endjay I don't know but I'm using my github fork, specified in package.json

@lukewendling and @endjay - thanks for the wake up call, I published version 1.0.3 with these changes to NPM now

@lukewendling - I don't think I heard back from you about my feedback i nthe gitter chat room back when:

Nov 18 14:20
@lukewendling - not sure the fix you made thus far is the right one ... did it actually work for you? the way you have it, i think you'll end up with one custom type for all models instead of one custom type per model

@pulkitsinghal this was definitely a quick fix. it allows to create an ES connector for each specified type. thus one config section in datasources.json for each type. not ideal. a better solution perhaps is a mapping from model name to ES type, perhaps in datasources.json.


🐛 No validation on metadata URL length for votes

Area
Voting Pillar
Domain
gov.tools
Which wallet were you using?
No response
Context

when entering any URI for offchain metadata, GovTool must check that the URL is  128 chars or under as this is the max length enforced by the ledger

Steps to reproduce

try to vote
attach metadata URI which is longer than 128

Actual behavior

Crazy confusing error message

Expected behavior

nice validation, maybe no pop up error message

@bosko-m , this issue is still occurring.
Validation is missing for anchor URLs exceeding 128 bytes.
Report
4O. Should reject invalid metadata anchor in vote context

Sentry Issue
https://intersect.sentry.io/issues/5795109910/?environment=prod&environment=production&project=4507101527277568&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=14d&stream_index=14


feat: using pyproject.toml instead of setup.py

Should the tests pass? Looks like you are missing a dependency

Should the tests pass? Looks like you are missing a dependency

The tests are fine as not passing and the missing package(exchangelib) is fine as is. I asked Elizabeth and she confirmed everything is as it should be
No, it's fine that they don't work. exchangelib is imported by BEAM's requirements file, so that's why it still works fine when the package isn't mentioned in django-post_office.

Why not just add it as a dependency here?


tests(Session): Add failure tests to terminal connections

[x] This contribution adheres to CONTRIBUTING.md.
[x] New tests have been created for any new features or regression tests for bugfixes.
[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Coverage remained the same at 64.23% when pulling d461263637b9c8e241e57c308d451a6fb079a188 on epage:term into 1f14f8be851a764606228c0ff5f68291a9f8118d on ni:master.

Coverage remained the same at 64.23% when pulling 0818760e6a43c9e12d2eda19dffeed40157fe51a on epage:term into 1f14f8be851a764606228c0ff5f68291a9f8118d on ni:master.

Coverage remained the same at 64.23% when pulling deac6caa006e65f2a8fff29358a2d581d7c3f3e0 on epage:term into 1f14f8be851a764606228c0ff5f68291a9f8118d on ni:master.


Package gendc_separator for installation with pip

https://packaging.python.org/en/latest/tutorials/packaging-projects/
TODO:

Allow users to install the module as pip install

Note:

Get rid of gendc_separator from SDK installer after this task
Add the pip install instruction on doc

[ ] LICENSE
[ ] pyproject.toml
[ ] README
[ ] src
[ ] tests

First package for test: https://test.pypi.org/project/gendc-separator/0.0.1/

Rearrange files as per https://packaging.python.org/en/latest/tutorials/packaging-projects/
C:.
│   LICENSE
│   pyproject.toml
│   README.md
│
│
├───src
│   └───gendc_separator
│           descriptor.py
│           __init__.py

see commit https://github.com/Sensing-Dev/GenDC/pull/4/commits/2c586d82f11986819cdeffc6c64bf1299b2b32b7

Use hatchling build system to create pip,
Create pyproject.toml

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

Python version: 3.11
Update the project details in  pyproject.toml
[project]
name = "gendc_separator"
version = "0.0.1"
authors = [
  { name="Example Author"<EMAIL_ADDRESS>},
]
description = "GenDC Seprator package"
readme = "README.md"
requires-python = ">=3.11"
classifiers = [
    "Programming Language :: Python :: 3",
    "License :: OSI Approved :: MIT License",
    "Operating System :: OS Independent",
]

[project.urls]
Homepage = "https://github.com/Sensing-Dev/GenDC"
Issues = "https://github.com/Sensing-Dev/GenDCt/issues"

#TODO: We still need to decide on the content of LICENSE and README.

Make sure you have the latest version of PyPA’s build installed:
python -m pip install --upgrade build

Generating distribution archives
python -m build

Result:
(base) PS C:\WorkSpace\Sensing-Dev\GenDC> python -m build
* Creating venv isolated environment...
* Installing packages in isolated environment... (hatchling)
* Getting build dependencies for sdist...
* Building sdist...
* Building wheel from sdist
* Creating venv isolated environment...
* Installing packages in isolated environment... (hatchling)
* Getting build dependencies for wheel...
* Building wheel...
Successfully built gendc_separator-0.0.1.tar.gz and gendc_separator-0.0.1-py3-none-any.whl

Test uploading created distribution:

Create account at https://test.pypi.org/account/register/
Create API token https://test.pypi.org/help/#apitoken
Use twine to upload the distribution packages.

python -m pip install --upgrade twine

Once installed, run Twine to upload all of the archives under dist:

(base) PS C:\WorkSpace\Sensing-Dev\GenDC> python -m twine upload --repository testpypi dist/*
Uploading distributions to https://test.pypi.org/legacy/
Enter your username: __token__
Enter your password:
Uploading gendc_separator-0.0.1-py3-none-any.whl
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.9/6.9 kB • 00:00 • ?
Uploading gendc_separator-0.0.1.tar.gz
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.9/5.9 kB • 00:00 • ?

View at:
https://test.pypi.org/project/gendc-separator/0.0.1/

sonali has already upload on test.pypi, before I upload to the real pypi, just have something to confirm:

name "gendc_separator" or "gendc-separator" on test pypi it is "gendc_separator"
version 0.0.1 or 0.1.0?
LICENSE?

detailed config is as follows:
[project]
name = 'gendc-separator'
dynamic = ["version"]
authors = [
  { name="Takuro Iizuka"<EMAIL_ADDRESS>}
]
description = "GenDC Seprator package"
readme = "README.md"
requires-python = ">=3.8"
classifiers=[
    "Development Status :: 3 - Alpha",
    "Programming Language :: Python"
]

[project.urls]
Documentation = "https://sensing-dev.github.io/doc/"
Repository = "https://github.com/Sensing-Dev/GenDC"
Changelog = "https://sensing-dev.github.io/doc/blog/index.html"

[build-system]
requires = ["setuptools>=61.0", "setuptools_scm[toml]>=6.2"]
build-backend = "setuptools.build_meta"

[tool.setuptools]
packages = ["gendc_separator"]

[tool.setuptools.dynamic]
version = {attr = "gendc_separator.__version__"}

gendc-python
-- gendc-separator
version 0.1.0
MIT

Upload on testPYPI first https://test.pypi.org/project/gendc-python/0.1.0/


Override client service saving actions to use password encoder to save client secret

The following pull request resolves the issue Password encoder doesn't work from Web Interface
The solution is to overwrite the client service of the project mitreid-connect / OpenID-Connect-Java-Spring-Server so that when saving a new client or when updating an existing client, the client secret is stored encoded using the configured encoder for clients.
In the case of having no password encoder configured, the NoOpPasswordEncoder is used, which stores the password as plain text.
This solution is merely temporary since the objective is to modify the mitreid-connect / OpenID-Connect-Java-Spring-Server project so that an instance of a PasswordEncoder can be injected.

Hello, have you been able to review the proposed solution?
Thank you


mpl2: draw shapes based on the simulated annealing outline

Trying to make it easier to understand what is going on during both Cluster and Macro placement in the Hierarchical Macro Placement stage of HierRTLMP flow.
I also added a method to clear the drawning made by Graphics so we can see the result after running mpl2 flow while OR is still running.

Please resolve the conflict with your previous PR

Done


fix: append cmf.core.app to HTML packages, isn't used in ISO but is needed in bundles for containers

can we have a test for this?

yep, just wanted someone to validate the check, tests pushed


Image in Program Card

Is your feature request related to a problem? Please describe.
Residents, CBOs, and City Staff have all mentioned that having images in the program card would help to know who the program serves. It's quicker to digest images than text. Would it be possible to add an image to the program card?
Describe the solution you'd like
As the CiviForm Admin, I would like to be able to upload an image that displays on the program card.
Additional context
Screenshots below and attached:

Done when
There is an upload box on the main program edit page. Uploaded photo shows on the program card. Supports JPEG, PNG, GIF images at a minimum.
Image in Program Card.pdf

I thought there may be a way to do this using existing functionality, but I'm afraid not.
This will likely require creating a way for admins to upload images to the file storage backend (S3) and then reference those images somehow in the question definition. Recommend collaborating with @mferhut on what admin and applicant UI for this could look like.

@cassandralfernandes Let me know the priority on this on when to pick this up.

See #979 (closed as duplicate) for more discussion.

Behavioral economics research: https://docs.google.com/presentation/d/1q7atQDjFbaBeP2QbHt32PyijOtFVV_KCvoR7xBPfFd0/edit#slide=id.g24d728ee21f_0_0

This is being worked under https://github.com/civiform/civiform/issues/5676. Closing this item


System Test: optionally, don't fail on additional records.

topic expectations should be able to define if they are an exact list of records to expect, or a subset of records that must be produced, i.e. should a test fail on additional records?
This is probably best captured at the TopicExpectation level.

Should the expectation ordering, currently define in the KafkaOptions class, also be defined at the TopicExpectation level instead?

The ks-connected-services-demo would benefit from updating to use this new option once its ready.


Unexpected token ...

I would like to contribute to this project but when using npm run dev I am thrown an error.
league-for-good\server\api\registration.js:25         const player = ({...req.body, ...{ leagueId }});
From what I understand ... is ES7 and/or experimental and Babel may not catching it. How should I proceed?

That's a syntax error, I will update the master branch later today. In the
meantime, if you want to work on a different branch, just change that line
to :
const player = Object.assign({}, req.body, { leagueId });
On Wed, Aug 9, 2017 at 4:38 PM, Andrew Gingrich<EMAIL_ADDRESS>wrote:

I would like to contribute to this project but when using npm run dev I
am thrown an error.
league-for-good\server\api\registration.js:25 const player =
({...req.body, ...{ leagueId }});
From what I understand ... is ES7 and/or experimental and Babel may not
catching it. How should I proceed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/league-for-good/issues/51, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AO6vXTTnzjNtabsVGbTLY8EzAjWhGRPKks5sWhiogaJpZM4Oym9R
.

ok thanks!


Printing looks different after cleanup

can be at least reproduced with several PDFs on FF 32a on my Mac .
Load the PDF, print (to pdf) - the PDF will look good quite identical.
Reload
Load the same PDF, wait 45 seconds, print (to pdf) - the PDF will look different. In most cases fonts which were bold are no longer bold.
one example: http://www.postgis.us/downloads/postgis21_cheatsheet.pdf

Evidence: built-in Firefox viewer (looks like modified) has no this problem.
Tested on Firefox 46.0.1 (with built-in viewer 1.3.231)

Closing as (most likely) fixed by #7694.


Add OSX support

This PR is a tentative for adding OSX support.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@traversaro the PR is ready for review, thanks! Correct me if I'm wrong, but I don't think we should bump the build number in this case.

Correct me if I'm wrong, but I don't think we should bump the build number in this case.

Yes, if indeed after the rerender the files in https://github.com/conda-forge/warp-lang-feedstock/tree/main/.ci_support are not modified, it is ok not to bump the build number.


The current source prefix mapping sets the root of all directories which contains vendored sources, but apparently that isn't enough to make the remapping work, so we'll need to remap things multiple times

Ah I finally found the issue after banging my head for a few hours as to why I couldn't reproduce it as a test case within this repo:
The flake in question has a .cargo/config.toml setting for rustflags. It appears that cargo will give precedence to these flags instead of the CARGO_BUILD_RUSTFLAGS environment variable we set
[target.x86_64-unknown-linux-gnu]
linker = "clang"
rustflags = ["-Clink-arg=-fuse-ld=lld"]
# nightly
# rustflags = ["-Clink-arg=-fuse-ld=lld", "-Zshare-generics=y"]

If we instead set RUSTFLAGS it "fixes" the dependency issue, but has the effect of ignoring whatever flags the project may have configured in .cargo/config.toml
Perhaps we need to have another mechanism to do the source prefix remapping besides setting the rustc flag (maybe patching the binaries after the fact?)

Do you have any link at hand where I could read about what is actually going on here? It seems like Nix does some scanning of binaries to find dependencies of each binary?

Do you have any link at hand where I could read about what is actually going on here?

Did a quick search but I couldn't find a well documented place which explains this :(

It seems like Nix does some scanning of binaries to find dependencies of each binary?

Yep, this is exactly what Nix does in practice. If it finds any reference to /nix/store/<hash>-<package>/... then it infers that the final binary depends on that store path. For interpreted languages this could be references to other code, or it could be shared libraries and so on


Fix back button in Sandcastle.

We store information in history state objects about the loaded demo.
Navigating to new demos calls pushState, and a fresh load
stores the demo specified via URL using replaceState.
Fixes #6509

@shunter, thanks for the pull request! Maintainers, we have a signed CLA from @shunter, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks @shunter!


Add more explanation for nsenter

Now the README in nsenter is a little confused and hard for new commings to understand.
Signed-off-by: Sun Jianbo<EMAIL_ADDRESS>

LGTM, thanks

LGTM


[torchlib] Remove adaptive_avg_pool implementation

Remove adaptive_avg_pool implementation because our implementation using GlobalAveragePool is incorrect. We can rely on torch decomp instead.

What ops do we get after decomposition? I recall 1D is correct, but 2d and 2d is not passing test_fx_op_consistency.py

Good point. I can test that. In any case globalavgpool is incorrect so we need to either improve the implementation or fix decomp


kill -HUP behaviour

Sorry for long time not checking in, jump to v2 is very good.
Now I use 2.0.6 linux x64 binary from release, run manually.
This is Enhancement request :)
In linux usually kill -HUP command put the program to reload the config then restart/resume the operation with the same pid.
I did that and dnscrypt-proxy just quit and no log write that it did quit.
Would be nice to have this feature. Thanks.

If something has changed in the configuration file, we will need to parse everything again, refetch certificates, and essentially do the same thing as stop/start. Even the cache needs to be flushed in cache cloaking rules are changed.
So, handling SIGHUP to reload the configuration wouldn't be very different than stop/start.
It could reload the modules, though. So that blacklists could be reloaded that way.
Except that... SIGHUP (and generally, Unix signals) has no equivalent on Windows.
So, this has to be done differently. Maybe by watching blacklist/cloaking/forwarding files for time changes.
Do you think this is something you can implement?

Haha I'm not a coder in terms of Go. Sorry.
No pressure though. Could use some list to do for this feature, if all above behaviors will be included. Put long milestone to this if that needed.
What bother me first are, nothing in log and very quick on quitting [kill will do that of  course :) ].


Problem with saving settings

In the latest version of the interface there is a problem with savings settings in the Alarm tab and OSD tab of Majestic. After reboot it checks checkboxes back. Version is master+57f945c, 2023-07-06, firmware is <IP_ADDRESS>. It appears on different browsers and PCs.

There is a connection between .motionDetect.visualize and .osd.enabled: majestic-settings.cgi
One cannot work without the other.


Oak-9126: TestFramework: create tests for both lucene and elastic

I left some comments/questions.
Overall, I think it's a good job. Only one question: I am able to execute the tests that extend from oak-search from IntelliJ without any problem. But if I run mvn clean install they are not executed. Any idea?

Didn't saw this. Will have a look at why tests are not running with mvn clean install

I left some comments/questions.
Overall, I think it's a good job. Only one question: I am able to execute the tests that extend from oak-search from IntelliJ without any problem. But if I run mvn clean install they are not executed. Any idea?

Found the issue, surefire have a regex with "*Test" which led to no picking Test1 for execution when we do mvn clean install --> changed name to CommonTest instead of Test1

Added a couple of comments, plus one general question/ point to discuss,
In the elastic test, could we have another layer of abstraction where we can define stuff as the class rule and assert eventually (because these would be exactly same for all the test classes and currently we are writing them in all of them).
We can have a structure something like -
AbstractBaseTest -> in oak-search (with util/helper stuff common to both elastic and lucene)
AbstractElasticBase - > in oak-search-elastic (with the elastic rule, overriding assertEventually from the above class, stuff like that) that extends the AbstractBaseTest class
We can make the abstract classes like SpellcheckTest1 as interfaces with default methods (I am not sure if that would work with @test methods, but we can give it a try) and then the
final test class in Elastic module would be something like
ElasticTest extends AbstractElasticBase implements FeatureTest

Adding test as default methods in interface doesn't feel right to me. But lets discuss this.


fix cluster perm classification for msearch template

Description
Changes classification of 'indices:data/read/msearch/template' to be a cluster permission instead of an index permission. It seems that this should have the same classification as  'indices:data/read/msearch', since it is a msearch but just with a template.
https://github.com/opensearch-project/OpenSearch/blob/63dc6aa795f8ec78597c7f93e732b979b6963d8f/modules/lang-mustache/src/main/java/org/opensearch/script/mustache/MultiSearchTemplateAction.java#L40
Issues Resolved
[List any issues this PR will resolve]
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

For additional context, there already is an existing bug in how SearchTemplateRequests are authorized: https://github.com/opensearch-project/security/issues/1678
A SearchTemplateRequest is a SearchRequest with a template, but the security plugin is not extracting the indices from the request correctly when going to evaluate the request. For a MultiSearchTemplateRequest, the user should be able to perform the multi search template and each individual SearchTemplateRequest that composes the multi request will be authorized individually. After the linked bug is resolved it should be working properly.


drone agent on ECS

hi, it looks like you're trying to set up the server on ECS but I can't see anything about the agents. Do you have any advice for running a single drone agent in ECS? I plan on creating a daemon that automatically starts/stops instances (containing tasks that contain drone-agent containers) based on the drone server's work queue.

Afraid not. This was just a very basic example and I no longer have access to AWS to test it myself.


Power up and power down buttons

@bonustrack Nope as I asked you before we never discussed nor we had any brief..
For example if you remeber our conversation I asked you do we reduce the earning of a user if someone vote down? or just the numbers?

@bonustrack Expected behaviour
User A upvoted the post and gave 0.20$ reward and then User B downvoted.. Now here we will reduce the rewards (like he got 0.20$ from user A and then B down voted for 0.10$ so we will remove the 0.10$ reward from his rewards right?)

@pareshUD

Hey @Sekhmet yes I am looking at it already. I will update something today.
Thanks
Paresh


orocos-kdl: 1.5.0 -> 1.5.1

Motivation for this change
Update orocos-kdl to the latest version.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 138181 at 0a976c01 run on x86_64-linux 1

3 packages built successfully:

orocos-kdl
python38Packages.pykdl
python39Packages.pykdl


Default Release Upload URL Fails

When #4 was merged, we started having the following failure with our release asset uploads:
> Run csexton/release-asset-action@master
Uploading file: bundles/adafruit-circuitpython-bundle-4.x-mpy-20200207.zip
Uploading file: bundles/adafruit-circuitpython-bundle-5.x-mpy-20200207.zip
Uploading file: bundles/adafruit-circuitpython-bundle-examples-20200207.zip
Uploading file: bundles/adafruit-circuitpython-bundle-py-20200207.zip
Uploading file: bundles/z-build_tools_version-1.4.1.ignore
##[error]Upload failed: Cookies must be enabled to use GitHub. undefined
Uploaded z-build_tools_version-1.4.1.ignore
##[error]Upload failed:  undefined
Uploaded adafruit-circuitpython-bundle-examples-20200207.zip
##[error]Upload failed:  undefined
Uploaded adafruit-circuitpython-bundle-4.x-mpy-20200207.zip
##[error]Upload failed:  undefined
Uploaded adafruit-circuitpython-bundle-py-20200207.zip
##[error]Upload failed:  undefined
Uploaded adafruit-circuitpython-bundle-5.x-mpy-20200207.zip
##[error]Node run failed with exit code 1

It took us a little while to figure out what would cause this, since the error messages didn't really point to the root cause. I finally settled on researching Cookies must be enabled to use GitHub and came across an old octokit/rest.js issue that pointed out the need to send requests to https://api.github.com vs https://github.com.
After debugging on a fork, I realized that this line was resulting in the default of a non-api URL:
url= core.getInput('release-url', {required: false}) || context.payload.release.html_url;
By changing || context.payload.release.html_url --> || context.payload.release.upload_url, I had successful uploads.
I know you can now pass in the release-url variable, and I've worked that out using the available context expression in the workflow. However, we'd have over 200 repositories to update with that approach.
I'm just wanting to gauge interest, or reasoning, for having the default release upload URL be one that will fail.
I would happily submit a PR if a change is desired.
Also, thanks @csexton for this Action. Having glob pattern uploads is a life saver!

I wonder how it worked before, because am sure it did. Are you using the v2 tag?
A PR would be quite welcome. I’ll be on the lookout.

I wonder how it worked before, because am sure it did.

Best I can tell, is that before it was hardcoded to use the upload_url when calling the upload function:
https://github.com/csexton/release-asset-action/blob/6a964e8a644f28832c3f9a46abc69dda52fc6d17/main.js#L31
I'll have a PR in shortly. I just wanted to make sure there wasn't some reason html_url was being used.

Well #4 did not chnaging anything concerning this is was html_url before #4 and also afterwards

Prior to #4, the URL was hardcoded to use upload_url:
async function upload(filePath, context, octokit) {
  ....
  try {
    let response  = await octokit.repos.uploadReleaseAsset({
      name: fileName,
      file: file,
-->   url: context.payload.release.upload_url,
      headers: {
        "content-length": file.length,
        "content-type": mimeType
      }
    });

4 changed it to use the passed in variable url, which was being set as html_url if no release-url was provided:
async function upload(filePath, context, octokit, url) {
  ....
  try {
    let response  = await octokit.repos.uploadReleaseAsset({
      name: fileName,
      file: file,
-->   url: url,
      headers: {
        "content-length": file.length,
        "content-type": mimeType
      }
    });

As I mentioned in my PR, I'm not entirely sure what core.setOutput('url', ...) is doing in run(). It is a confusing step for me in either version, as it doesn't seem to be actually used anywhere.
I also mentioned my lack of experience in JS, so if I'm completely misunderstanding how this codebase is working let me know.

oh ok


Add Python3 Support

Changes

Add Python 3.5+ support
Update Python dependencies
Rebuild gRPC

@dcramer
Hello,
If you have time, could you please review this change for me?
Thanks very much!

Seems straight forward - what was the approach to build the bindings so that they supported both?

Hello,
First of all, thanks for the quick response! Actually, I did nothing. Seems like the gRPC was built to support both versions. I already tested in Python 2.7.18 and 3.9.1. It looks fine so far.
Here's the screenshot for both versions:

BTW, your work on Sentry is terrific! It helps me a lot! And I'm very glad to have a conversation with you.
Have a nice day!

@earthpyy thanks! Glad you vetted it as I was debating how I was going to do the same without spending a lot of time :)

Published 0.2.0 - pretty sure its correct for both py2/py3, tho i was disappointed in myself that I didn't setup a build script (or GitHub Action!) to auto publish previously!

Everything is fine. Very thanks to you amd have a nice day!


pythonPackages.boa-api: init at 0.1.14

Description of changes

The boa-api package allows interfacing with the Boa infrastructure for MSR research
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build python310Packages.boa-api

fails to build:
util (unittest.loader._FailedTest) ... ERROR
======================================================================
ERROR: util (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: util
Traceback (most recent call last):
  File "/nix/store/ar76b3831ydkmfhf0r9v3wbma5i61iz2-python3-3.10.9/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName
    module = __import__(module_name)
  File "/build/source/boaapi/util.py", line 26, in <module>
    import boaapi.boa_client
  File "/build/source/boaapi/boa_client.py", line 20, in <module>
    from boaapi.util import CookiesTransport, parse_job, fetch_url
ImportError: cannot import name 'CookiesTransport' from partially initialized module 'boaapi.util' (most likely due to a circular import) (/build/source/boaapi/util.py)
----------------------------------------------------------------------
Ran 1 test in 0.000s
FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>

Talked to upstream.  They cut a new release with a fix.

@ofborg build python310Packages.boa-api


Proper License information (and errata?)

I've adjusted and included the correct license excerpts.
Readme reflecting this.
May want to revert website. (sorry)
Updates #39.
Since ffmpeg docs are in markdown it's best for them to be in the repository.

hey!
thanks for the changes, but...
the license file should be the license for this project (MIT), all the other stuff should be in a file called COPYING or the readme (that's where i'm putting it). for ffmpeg i don't want the license in this repo because it's already in a source dependency:
https://github.com/kritzikratzi/ofxAvCodec/tree/master/ffmpeg_src and here
https://github.com/kritzikratzi/ofxAvCodec/blob/master/data/license-libavcodec.md

Oh, thanks for clarifying.
I'll adjust or nevermind then


GraphQLDocumentError: Unknown type "FRAGMENT_TYPE_NAME"

Hi Corey,
Hope you're doing great. First of all, thank you for this amazing plugin! I've been looking for something like this for a while now :) Now, I keep getting an error that looks like this:
GraphQLDocumentError: Unknown type "__FRAGMENT_TYPE_NAME__"
My config looks like this:
{
    resolve: 'gatsby-plugin-sanity-image',
    options: {
      projectId: SANITY_PROJECT_ID,
      dataset: GATSBY_SANITY_DATASET,
      includeFragments: false
    }
}

Let's me run my dev environment with no issues but it does kill the build when I try to serve it. Not entirely sure why this is happening since I disabled the fragments, am I missing something? We are using typescript as well.

Do you have a file at .cache/fragments/gatsby-plugin-sanity-image.js? If so, it's likely that you ran your dev server before setting includeFragments to false, which would have created that cached fragments file. Deleting it and restarting should fix the problem (or you can run gatsby clean from your project root if preferred).
If you don't have that file, or if removing it and restarting recreates it, or if doing so doesn't fix the problem, please provide details about the Gatsby version you're using and any other configuration info that might be related.

Hi @coreyward , thanks for the quick reply. So I just tested on a branch we have with Gatsby v3 and that seems to have solved the issue. Thank you! I'm closing the issue.

having the above issue on gatsby ^2.10.4. Is this plugin supposed to work with v2? because im also not seeing issues on a clean install with v3.

@timbakkum Yep, it was developed against 2.x and is in active use with 2.x. Does running gatsby clean and restarting fix your issue?


Use stdout.isatty to finalize color

Currently checks stdin
Fixes #266

Thank you! This looks reasonable, but you probably need to update the associated test. Let me know if you need any help with that.

Fixed the test, had some trouble running the full unit test suite locally because of an issue with venv.

Thank you!


[TEST] Fix flaky ha_salvage_test

What's the test to develop? Please describe
Function ha_salvage_test in test_ha.py is flaky.
Because it will try get specific volume state 'faulted' but in recent build, LH volume recover from faulted to detached state almost immediate,  ha_salvage_test hard to correct capture expected volume state
Describe the items of the test development (DoD, definition of done) you'd like

[ ] Submit fix PR
[ ] Verify on pipeline

Additional context
Related test case

test_backing_image.test_ha_salvage_with_backing_image
test_ha.test_ha_salvage

https://github.com/longhorn/longhorn-tests/pull/977
https://github.com/longhorn/longhorn/issues/4045
cc @cchien816

Close this issue since we already have issue for this issue

caused  a side effect: https://github.com/longhorn/longhorn-tests/pull/982#discussion_r887620154


Improve error message for parse errors in storage-schemas

fixes #773

Codecov Report

Merging #780 into master will decrease coverage by 0.03%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master     #780      +/-   ##
==========================================
- Coverage   50.27%   50.24%   -0.04%
==========================================
  Files          36       36
  Lines        3306     3310       +4
  Branches      471      471
==========================================
+ Hits         1662     1663       +1
- Misses       1540     1543       +3
  Partials      104      104

Impacted Files
Coverage Δ

lib/carbon/storage.py
72.54% <40%> (-1.95%)
:arrow_down:

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 16767fe...67c641a. Read the comment docs.


feat(ion-fab-button) customize close button

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (npm run build) was run locally and any changes were pushed
[x] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
Activated ion-fab-button is hardcoded to use the close ionicon
Issue Number: #18442
What is the new behavior?
ion-fab-button has a slot=close which can be used to customize how the close button will look
Does this introduce a breaking change?

[ ] Yes
[x] No

Other information
The tests I added might have to be modified because I have added 2 new FAB buttons in the standalon test and the initial screenshot won't match.
I wasn't sure if I have to update the old screenshots or it would be better to separate the test.

Closed in favor of #18827

Closing in favor of #18827


Disable Travis git clone depth to avoid version tags missing up to depth setting and reverting to 1.0.0-SNAPSHOT

Coverage decreased (-0.02%) to 90.586% when pulling 6f0d68074ca2268532176ccc86251c919af410a2 on tgianos:disableTravisGitDepth into e9319732d4a2c03131de895b774b8b842847fad4 on Netflix:master.


[IMPROVEMENT][UI] Recurring jobs create new snapshots while being not able to clean up old one

Is your improvement request related to a feature? Please describe (👍 if you like this request)
Need to support UI for two new recurring jobs. https://github.com/longhorn/longhorn/issues/4898
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@mantissahz Please provide the test steps.

Just a suggestion instead of  Backup Force Create and Snapshot Force Create in the task, can we have a check box for Force create when user selects Backup or Snapshot?
cc: @innobead

Just a suggestion instead of  Backup Force Create and Snapshot Force Create in the task, can we have a check box for Force create when user selects Backup or Snapshot?
cc: @innobead

@smallteeths Can we help with this? Probably need a tip for the checkbox. @mantissahz Could you help follow up with @smallteeths ? Thanks.

Just a suggestion instead of  Backup Force Create and Snapshot Force Create in the task, can we have a check box for Force create when user selects Backup or Snapshot?
cc: @innobead

@smallteeths Can we help with this? Probably need a tip for the checkbox. @mantissahz Could you help follow up with @smallteeths ? Thanks.

Sure, I'll make the modification. When the user selects "backup" and checks the "Force create" option, the type of recurring job will be "Force create backup". The same logic applies to snapshots as well.

Verified on master-head 20230414

longhorn master-head (ccf9f3a)
longhorn-manager master-head (092eca2)
longhorn-ui master-head (3ddbe5d)

The test steps

In the Longhorn UI, go to the Recurring Job page.
Click on the Create Recurring Job button.
From the Task dropdown menu, select either Backup or Snapshot.
Check the Force create option.
Verify that the recurring job task has been updated to Force create backup or Force create snapshot accordingly.
Click OK to create the recurring job.
Repeat steps 1-6 on the Volume Details page in the Longhorn UI.

Result Passed

@roger-ryao Could you please attach a screenshot here. Thanks


Install patched LLDB on vscode extension activation

Summary
Download and install the WAMR patched LLDB binary on vscode extension activation
This allows the user to download the packaged .vsix file, where the activation script should handle determining what LLDB binary they should use, and install it in the correct location.

I wonder if we actually need the non-bundled version at all? Are there any benefits of having that?
@wenyongh @lum1n0us

@loganek @cimacmillan   Hey guys, followings are current status and some enhancement need to be developed for wamr-ide with the release.
Necessary Resource

Docker images: wasm-toolchain:release-version & wasm-debug-server:release-version
LLDB under VSCode-Extension/resource/debug (for source debugging)

Current Status:

docker images are built with release-version-number tag, can be directly pulled with docker command.
The extension version of wamr-ide has set as the release-version-number(stored in package.json config file)

Enhancement to be developed:

wamr-ide will auto check and pull the docker images if the images are not ready in activation stage.

wamr-ide reads the release-version-number firstly,
execute the docker pull command with the release-version-number tag

wamr-ide will auto install the lldb and construct the resource\debug folder
The docker-image:tag of commands to create docker containers is hard code right now, please check here , it should be changed with the release-version-number

read release-version-number firstly
invoke the script with the release-version-number argument.

so back to this PR, LLDB will be auto installed in vscode-extension activation stage according to the above.

wamr-ide will auto install the lldb and construct the resource\debug folder

@NingW101 This approach makes sense, and is a bit more flexible. In the linux case, it would allow the user to specify which of the ubuntu LLDB builds (or determine via the OS currently running).
Is it something that's already being worked on? If not, I can revise this PR.

Is it something that's already being worked on?

The modifications are mainly in vscode-extension part, and the development has not started yet.

If not, I can revise this PR.

That would be nice, thank you very much! I can help to file an issue and draft the basic logic so that we can have more discussion there

wamr-ide will auto install the lldb and construct the resource\debug folder

@NingW101 Sorry for the delay, I've revised the PR to address this aspect.

@NingW101 This is a good suggestion, thanks. I'll revise the PR.

One more thing after my debugging for this patch, I think maybe we should add enhancement for starting debugging process. Currently we only check the lldb resource and give prompt during the activation stage, but what if the lldb is not downloaded or installed normally or users just skip it? We should check lldb and prompt it again if necessary after users clicking Debug button, otherwise, debugging process wont work well. How do you think?

@cimacmillan I changed the destination branch to main since the changes of dev/binary_release has been merged into main and dev/binary_release is to be removed. And since this PR supposes that lldb binary has been compiled and released, and gets lldb binary from the released link, so my understanding is that it doesn't work currently, and we should not merge this PR until we are to release a new version with lldb binary released, right?
And there are several conflicts after changing the destination branch, could you help resolve them? Thanks.

@cimacmillan I changed the destination branch to main since the changes of dev/binary_release has been merged into main and dev/binary_release is to be removed. And since this PR supposes that lldb binary has been compiled and released, and gets lldb binary from the released link, so my understanding is that it doesn't work currently, and we should not merge this PR until we are to release a new version with lldb binary released, right?
And there are several conflicts after changing the destination branch, could you help resolve them? Thanks.

@wenyongh Thanks, I've rebased my changes on top of main. The binary release job will build patched LLDB versions and this vscode extension in parallel. If a user installs the extension from the wamr-ide artefact in the release, there will be compiled LLDB available and it should setup correctly. I think we should merge this before the next release so that latest wamr-ide artefact includes these changes.
There isn't an official WAMR release which contains patched LLDB yet, so it's only a consideration for internal testing. Personally, I have been running the binary release job from a personal fork, which has been a good method.

@cimacmillan I changed the destination branch to main since the changes of dev/binary_release has been merged into main and dev/binary_release is to be removed. And since this PR supposes that lldb binary has been compiled and released, and gets lldb binary from the released link, so my understanding is that it doesn't work currently, and we should not merge this PR until we are to release a new version with lldb binary released, right?
And there are several conflicts after changing the destination branch, could you help resolve them? Thanks.

@wenyongh Thanks, I've rebased my changes on top of main. The binary release job will build patched LLDB versions and this vscode extension in parallel. If a user installs the extension from the wamr-ide artefact in the release, there will be compiled LLDB available and it should setup correctly. I think we should merge this before the next release so that latest wamr-ide artefact includes these changes.
There isn't an official WAMR release which contains patched LLDB yet, so it's only a consideration for internal testing. Personally, I have been running the binary release job from a personal fork, which has been a good method.

@cimacmillan OK, let's merge the PR before we release a new version.

@wenyongh @cimacmillan are there any further changes required before we merge that? Looks like all the comments have been resolved and there are no conflicts with the main branch.

sounds good, thanks

@wenyongh When is the next release planned?
I think it would be safe to merge this. The missing wamr lldb binary release is only a consideration for internal testing. To avoid an error around the missing LLDB binary, you can include a pre-built LLDB in the debug folder of the VS code extension for testing. If LLDB is present in this folder, then it won't attempt to download anything.

OK, let's merge it first. BTW, we may upload another PR to include the pre-built LLDB in the debug folder of the VS code extension, and do not merge it now. If developer encounters issue, we can let him refer to the PR.
And yes, we are planning to release the next version, is there any PR from you to merge recently?


one group bind many topics problem

Describe the bug
I have two programs using the same group id.
Two programs subscribe to different topics, such as topicA and topicB.
I found that only one of the programs can consume the topics.
When I use two different group id, the program works normally
What kind of question is this, and I hope to answer!!!
To Reproduce
ProgramA-Code
import { Kafka, Producer, ConsumerGroup, Consumer } from 'kafkajs'
const topic = "topicA"
function async start(){
  const client = new Kafka({
          clientId: `delay-api-${process.pid}-${Math.floor(Math.random() * 10000000)}`,
          brokers: _.split(host, ','),
          connectionTimeout: 10000,
          requestTimeout: 5000
        })
  const consumer = this.client.consumer({ groupId: "group-id" })
  consumer.on('consumer.connect', () => logger.info(`${topic} Consumer Is Connect`))
  consumer.on('consumer.disconnect', err => logger.info(`${topic} Consumer Is Disconnect`, err))
  consumer.on('consumer.crash', err => logger.info(`${topic} Consumer Is Crash`, err))
  consumer.on('consumer.stop', err => logger.info(`${topic} Consumer Is Stop`, err))
  await consumer.connect()
  await consumer.subscribe({ topic:topic, fromBeginning: false })
  consumer.run({
    eachMessage:({message})=>{
       console.log(message)
    }
  })
}

ProgramB-Code
import { Kafka, Producer, ConsumerGroup, Consumer } from 'kafkajs'
const topic = "topicB"
function async start(){
  const client = new Kafka({
          clientId: `delay-api-${process.pid}-${Math.floor(Math.random() * 10000000)}`,
          brokers: _.split(host, ','),
          connectionTimeout: 10000,
          requestTimeout: 5000
        })
  const consumer = this.client.consumer({ groupId: "group-id" })
  consumer.on('consumer.connect', () => logger.info(`${topic} Consumer Is Connect`))
  consumer.on('consumer.disconnect', err => logger.info(`${topic} Consumer Is Disconnect`, err))
  consumer.on('consumer.crash', err => logger.info(`${topic} Consumer Is Crash`, err))
  consumer.on('consumer.stop', err => logger.info(`${topic} Consumer Is Stop`, err))
  await consumer.connect()
  await consumer.subscribe({ topic:topic, fromBeginning: false })
  consumer.run({
    eachMessage:({message})=>{
       console.log(message)
    }
  })
}

** Logger:**
ProgramA
{"level":"WARN","timestamp":"2021-10-19T06:52:13.524Z","logger":"kafkajs","message":"[ConsumerGroup] Consumer group received unsubscribed topics","groupId":"delaygroup_dev","generationId":83,"memberId":"delay-api-52386-5344417-2d9403ff-5b58-41ce-9ecd-d595407aff31","assignedTopics":["SQLRunningDev"],"topicsSubscribed":["TaskRunningDev"],"topicsNotSubscribed":["SQLRunningDev"],"helpUrl":"https://kafka.js.org/docs/faq#why-am-i-receiving-messages-for-topics-i-m-not-subscribed-to"}
{"level":"INFO","timestamp":"2021-10-19T06:52:13.524Z","logger":"kafkajs","message":"[ConsumerGroup] Consumer has joined the group","groupId":"delaygroup_dev","memberId":"delay-api-52386-5344417-2d9403ff-5b58-41ce-9ecd-d595407aff31","leaderId":"delay-api-52387-8377299-2ec6bfc6-9c17-47b0-93ad-e7af4a146760","isLeader":false,"memberAssignment":{},"groupProtocol":"RoundRobinAssigner","duration":9237}

ProgramB
{"level":"INFO","timestamp":"2021-10-19T06:52:13.504Z","logger":"kafkajs","message":"[ConsumerGroup] Consumer has joined the group","groupId":"delaygroup_dev","memberId":"delay-api-52387-8377299-2ec6bfc6-9c17-47b0-93ad-e7af4a146760","leaderId":"delay-api-52387-8377299-2ec6bfc6-9c17-47b0-93ad-e7af4a146760","isLeader":true,"memberAssignment":{"SQLRunningDev":[12,15,2,3,4,5,6,9]},"groupProtocol":"RoundRobinAssigner","duration":9236}

Environment:

OS: Mac OS 11.2.3
KafkaJS version 1.15.0
Kafka version 0.10.2
NodeJS version 14.x

Additional context
Add any other context about the problem here.

You cannot have the same groupId subscribing to different topics. The whole point of the group id is to identify consumers as being part of the same consumer group.

A consumer group is a set of consumers which cooperate to consume data from some topics. The partitions of all the topics are divided among the consumers in the group.

https://docs.confluent.io/platform/current/clients/consumer.html#consumer-groups

@Nevon would you, please, clarify, what is wrong with stackoverflow question and answer.

"radai" already explained it in the comments:

i dont think anyone claimed they would see records from topics they dont own. to complete your experiment, try and force a rebalance by adding partitions to one of the topics and you will see ALL consumers (even those that dont care about that topic) stop to rebalance.

Partitions will still be assigned to all members of the consumer group. It's just that if a consumer isn't subscribed to a topic that it receives assignments for, it'll ignore them. This is client-side behavior, not server side behavior.
When I say "You cannot have the same groupid subscribing to different topics" I don't mean it's literally impossible to do. There's just absolutely no benefit to doing it, and is a misunderstanding of what the purpose of a consumer group is.