Problems with Homebridge's new "Bridged Mode"

I have a ISY994i that I am using as a controller for three LampLincs and about a dozen SwitchLincs. I am able to control each of the devices individually as well as in groups, using scenes, via the ISY’s built-in web-based (Java) interface. I also use Mobilinc HD on my iPad and iPhone to control the devices and scenes.
I’ve just installed the latest version of HomeBridge on a Raspberry Pi 2 B along with homebridge-isy-js. When I start the HomeBridge server, it initializes the ISY platform as well as the LampLincs exposed by the ISY (thanks to the new "Bridged Mode"). However, it does not seem to pick up on the SwitchLincs via Bridge Mode. Am I missing something?
Any advice/pointers would be greatly appreciated. Many thanks in advance!

Per DavidG's suggestion on the UDI forum I managed to solve this by by looking at the nodes on the ISY at http:///rest/nodes, then editing the isydevicetypes.json file located in /usr/local/lib/node_modules/homebridge-isy-js/node_modules/isy-js/isydevicetypes.json to include entries for the SwitchLinc versions that I have.

Sorry I missed this. Could you send along the change you made? I'll flow it back into the root project so this is supported for others.

No worries. I added the following line to /usr/local/lib/node_modules/homebridge-isy-js/node_modules/isy-js/isydevicetypes.json :
{ "type": "<IP_ADDRESS>", "address": "", "name": "(2477D) Dual Band SwitchLinc Dimmer v.45", "deviceType": "DimmableLight", "connectionType": "Insteon Wireless", "batteryOperated": false },

Following the same advice, I added a few more entries to the isydevicetypes.json file to enable support for three more Insteon devices:
{ "type": "<IP_ADDRESS>", "address": "", "name": "(2477S) Dual Band SwitchLinc On/Off Switch v.43", "deviceType": "Light", "connectionType": "Insteon Wireless", "batteryOperated": false },
{ "type": "<IP_ADDRESS>", "address": "", "name": "(2334-2) KeypadLinc Dimmer 5 Buttons v.43", "deviceType": "DimmableLight", "connectionType": "Insteon Wired", "batteryOperated": false },
{ "type": "<IP_ADDRESS>", "address": "", "name": "(2487S) Dual Band KeypadLinc Relay v.41", "deviceType": "Light", "connectionType": "Insteon Wireless", "batteryOperated": false },

Note that I added all 4 of these devices to the isy-js library. You should be able to do a sudo npm update and it should pull down the new version of these.

@rodtoll I have the following devices in my insteon environment which aren't part of isydevicetypes.json:
  { "type": "<IP_ADDRESS>", "address": "1", "name": "(2842-222) Insteon Motion Sensor v.24", "deviceType": "MotionSensor", "connectionType": "Insteon Wireless", "batteryOperated": true },
  { "type": "<IP_ADDRESS>", "address": "", "name": "(2635-222) Insteon On/Off Module", "deviceType": "Light", "connectionType": "Insteon Wireless", "batteryOperated": false },
  { "type": "<IP_ADDRESS>", "address": "", "name": "(2472dwh) Insteon OutletLinc Dimmer", "deviceType": "DimmableLight", "connectionType": "Insteon Wireless", "batteryOperated": false },
  { "type": "<IP_ADDRESS>", "address": "", "name": "(2334-222) KeypadLinc Dimmer 8 Buttons", "deviceType": "DimmableLight", "connectionType": "Insteon Wireless", "batteryOperated": false },
  { "type": "<IP_ADDRESS>", "address": "", "name": "(2466S) ToggleLinc", "deviceType": "Light", "connectionType": "Insteon Wired", "batteryOperated": false },

This next one is a dual On Off outlet, so there are two addressable relays in one device. I'm not sure if I understood the "address" parameter correctly, but here is my initial guess as to how it should be setup:
  { "type": "<IP_ADDRESS>", "address": "1", "name": "(2663-222) Insteon Dual On/Off Outlet Top", "deviceType": "Outlet", "connectionType": "Insteon Wireless", "batteryOperated": false },
  { "type": "<IP_ADDRESS>", "address": "2", "name": "(2663-222) Insteon Dual On/Off Outlet Bottom", "deviceType": "Outlet", "connectionType": "Insteon Wireless", "batteryOperated": false },

where do i get the type from?  I have a (2635-222) On/Off Module v.48 that isn't being recognized.

nevermind, reread the thread - it is at http:///rest/nodes

@eddiemoy718 is your On/Off module a different type then mine? According to what you posted they are the same model #. Just curious...

@fahrvergnuugen my type is different I ended up putting this in based on the http:////rest/nodes output
{ "type": "<IP_ADDRESS>", "address": "", "name": "(2635-222) On/Off Module v.48", "deviceType": "Light", "connectionType": "Insteon Wired", "batteryOperated": false },
Anyone know if there is a connection type for both?  I see "Insteon Wired" and "insteon Wireless", but most of my switches are dual band, meaning they use both the wire line and wireless communication.
It is working great now by the way...  I have all the devices registered now and can control it with Siri.  Really Cool!  Also ISY works a lot better than the Insteon Hub, but I still need the Hub for Amazon Echo Integration.

I added all the requested devices to the isy-js package. If you update to the latest version of isy-js it will pickup all your devices from above. (Homebridge-isy-js uses isy-js under the covers).
Regarding the connection type it's for informational reasons only so feel free to set it to something like Insteon Dual or something else. I may make this stricter in the future but for now it is freeform.
BTW, for future device adds there is a issue in the isy-js project for requesting them. You can see it here:
https://github.com/rodtoll/isy-js/issues/7

@rodtoll thanks!  So does isy-js pick up the devices based on the device type only?  I see that I have different device type even though the description is the same as some of the others here.

Yes. All fields are used but only the type, deviceType and address elements actually make a difference in the code. The other fields are just used for descriptive purposes. (Although I'd like to use them for more later).
Essentially the code enumerates all the devices from the ISY via the REST API and then looks at the type attribute to find a matching entry in isydevicetypes.json. If it's not in that list it's ignored. Hope this helps!

@fahrvergnuugen - The address field tells the ISY library to only match that entry if the last digit of the address matches the specified value. If the value is empty it matches regardless. This is used when you have composite devices with multiple components. For example FanLinc has a light and a fan level control and so two entries end up in the isydevicetypes.json -- one for the fan and one for the light. Both have the same type, they only differ in addresses.

@rodtoll ah, that is where i can get only the 1st button from a 5 button device.  so if i put in "1" in the address then it will only match the first instance of the 5 entries in the 5 button device.
thanks, this helps a lot!

@eddiemoy718 Correct! Glad to help.

Hi Rod,
I hope you’re well. I had to add the following line to the isydevicetypes.json file to get a recently purchased ToggleLinc to work. You might want to add it to the package in your next update:
{ "type": "<IP_ADDRESS>", "address": "", "name": "(2466S) ToggleLinc Relay v.41", "deviceType": "Light", "connectionType": "Insteon Wired", "batteryOperated": false },
Best regards,
Mark

On Dec 20, 2015, at 9:36 PM, rodtoll<EMAIL_ADDRESS>wrote:
I added all the requested devices to the isy-js package. If you update to the latest version of isy-js it will pickup all your devices from above. (Homebridge-isy-js uses isy-js under the covers).
Regarding the connection type it's for informational reasons only so feel free to set it to something like Insteon Dual or something else. I may make this stricter in the future but for now it is freeform.
BTW, for future device adds there is a issue in the isy-js project for requesting them. You can see it here:
rodtoll/isy-js#7 https://github.com/rodtoll/isy-js/issues/7
—
Reply to this email directly or view it on GitHub https://github.com/rodtoll/homebridge-isy-js/issues/1#issuecomment-166181711.

@markleepgh - Just FYI -- I missed your comment earlier so the device didn't get added to the device types. But I made sure it went in this morning's publish of v0.4.1. Thanks for sending it.

@rodtoll - Is there anyway with Homebridge-isy-js to change the device type as it is fed into Homekit? I have an Insteon switch that I am using to control a celling fan and one for bathroom fan. They are not "Lights" so I would like Homekit to think they are so when I "Turn Off The Lights" it does not cut off the fans. Didn't know if there was a way to do this like the rename statements or something.


publish new version

I want to try this with hapi 13 but it seems like the module has not been published in a while.
Is this for a reason and if so when can I expect a new release? I really want to try this.
Also what is the command to log debug info to console (like DEBUG=cloud-trace node server)?

You can get debug info by running GCLOUD_TRACE_LOGLEVEL=4 node server.js. We will be doing a release soon but you can try out hapi 13 functionality by installing from master: npm install GoogleCloudPlatform/cloud-trace-nodejs.

Cool thanks!

Ok did some testing on dev and looks nice!
Will enable on staging env for more testing.
Also Mysql did not seem to be logged due to no root. Logs:  Untraced mysql query: (I don't know what it means but just letting you know :P)
I am using https://www.npmjs.com/package/hapi-plugin-mysql for my sql connection, not sure if related.
Also I am using ioredis, is this package supported?

Thank you for the log information. #222 should get mysql reporting working with your plugin. We do not currently have plans to support ioredis but do have support for node redis.

Very cool! Also awesome that you used a module I wrote to test :O
Is there a reason you chose node_redis instead of ioredis? (they have plan to merge but no idea on the timeline on that)

We went with node_redis due to its popularity but we hope to increase the number of frameworks we can support over time.

Redis usage is not significant for atm so fine maybe I can do a shot at a PR after my vacation

Thanks for the help and the great work!

Thanks for trying it out. I'm glad the information is useful!


mruby: When RAKE is unavailable, skip building mruby

This change makes Ruby built in only when rake is available. If it's not available, it will skip embedding mruby, and issue a warning.
This will make it so that it will still build for platforms that don't have Rake available. Unfortunate side effect that Ruby won't be available, but it will keep backwards compatibility with older platforms.

@RobLoach Could you give an example of an actual platform that neither cannot be cross-compiled to, nor could it handle MRI?


Dc7

NOTE: In the integration test, the 1st test case doesn't have geoId/06085 (Santa Clara county) in the golden file, it's a bug in the cache data (not a bug in this PR), and it's already fixed in cl/409441009 - after next cache build, I'll update the golden file.  @pradh @shifucun

Submitting for now to allow for further development on top of this. Since the code is not used, so there is no risk. Will have Bo or Shanth to look after their vacation, and can make more changes then. Thanks.


[SPARK-8972][SQL]Incorrect result for rollup

We don't support the complex expression keys in the rollup/cube, and we even will not report it if we have the complex group by keys, that will cause very confusing/incorrect result.
e.g. SELECT key%100 FROM src GROUP BY key %100 with ROLLUP
This PR adds an additional project during the analyzing for the complex GROUP BY keys, and that projection will be the child of Expand, so to Expand, the GROUP BY KEY are always the simple key(attribute names).

Merged build triggered.

Merged build started.

Test build #37024 has started for   PR 7343 at commit c695760.

Test build #37024 has finished for   PR 7343 at commit c695760.

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

Merged build finished. Test PASSed.

cc @marmbrus @yhuai

Can you explain what is the problem in the JIRA?

Merged build triggered.

Merged build started.

Test build #37112 has started for   PR 7343 at commit 34def69.

Thanks you @yhuai , I've updated the description of the bug, and also add more unit tests for the fixing.

Test build #37112 has finished for   PR 7343 at commit 34def69.

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

Merged build finished. Test FAILed.

@chenghao-intel Thanks for the update. I find complex group by keys is a confusing term. If I understand correctly, we do not handle expressions other than AttributeReferences, right? Also, with your change, seems we will change the group by expressions (e.g. from key % 100 to key)? What will happen if an expression involves multiple columns (e.g. key1 + key2)?

That's correct, complex group by keys is the expression other than AttributeReferences.
I am not just simply change the group by keys, but with an alias. e.g.
SELECT key+key FROM src GROUP BY key+key WITH ROLLUP
==>
SELECT k FROM (SELECT key + key as k FROM src) t GROUP BY k WITH ROLLUP

oh, i see. Yeah, you are right.
Can we use another term for complex group by keys? It is confusing and something like key1 % 100 is not complex.

@yhuai thanks for the reviewing, any better idea for the term complex group by keys? Or should I just call it non-attribute expressions?

Test build #1050 has started for   PR 7343 at commit 34def69.

Test build #1050 has finished for   PR 7343 at commit 34def69.

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

Merged build triggered.

Merged build triggered.

Merged build started.

Test build #37300 has started for   PR 7343 at commit 827873f.

Test build #37300 has finished for   PR 7343 at commit 827873f.

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

Merged build finished. Test PASSed.

The fix looks good to me.

Merged build triggered.

Merged build started.

Test build #37313 has started for   PR 7343 at commit 1ebbb59.

Test build #37313 has finished for   PR 7343 at commit 1ebbb59.

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

Merged build finished. Test FAILed.

seems not related.
retest this please

retest this please

Merged build triggered.

Merged build started.

Test build #21 has started for   PR 7343 at commit 1ebbb59.

Merged build triggered.

Merged build started.

Test build #37340 has started for   PR 7343 at commit 1ebbb59.

Test build #21 has finished for   PR 7343 at commit 1ebbb59.

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

Merged build finished. Test PASSed.

Test build #37340 has finished for   PR 7343 at commit 1ebbb59.

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

Merged build finished. Test PASSed.

@yhuai any more comments?

LGTM. I am merging it to master.


Replace CAIP property names in the parser with generic names (assetId, chainId, etc)

Overview
We use CAIP vernacular in our parsing logic, including on transactions, transfers, fees etc.
Rename these to their more generic equivalents.
References and additional details
E.g. https://github.com/shapeshift/unchained/blob/650ce054bf30e923c858a01f2096d4322f8419f6/node/packages/client/src/types.ts#L7
This will be a multi-PR process:

unchained: Add additional types alongside existing types: (https://github.com/shapeshift/unchained/pull/404)
lib: Add additional types alongside existing types: https://github.com/shapeshift/lib/pull/587
web: Update logic to point to new property names
unchained: Remove deprecated properties

Acceptance Criteria
We no longer use CAIP vernacular in unchained parser.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

Issue now tracked in lib: https://github.com/shapeshift/lib/issues/618


Add hacker news loader

In builder_helpers add a method to load hacker news url from the builder.url file

In the Builder Helper, there is a load_web.py module commonly employed for retrieving content from the web. Langchain offers specialized loaders designed for specific websites, ensuring that the obtained results are cleaner and free of unnecessary HTML elements. You need to use Hacker new loader to get content from ycombinators website

oh got it now, cool.


Ports Learn page is missing info on possibility of static ports

See also: https://groups.google.com/d/topic/elm-discuss/mkOD1YaBtjM/discussion
The confusion of the poster of that thread points out a weakness in the documentation of Ports:
The page only gives example code of ports which are of type Signal x.
Only when you look carefully at the examples that are linked to on page, do you see that "static" (non-Signal typed) Ports are also possible. And that they can be used for program start-up configuration (static in-ports) and exporting of functionality (static out-ports, main use is functions I think?).
It would be nice to have that more prominently on the Learn page.

It looks like there's a section at the bottom that specifies what can be sent through a port, under "Customs and Border Protection":
http://elm-lang.org/guide/interop
Maybe it was added after this issue was posted?

Not relevant with 0.17


error[E0433]: failed to resolve: use of undeclared crate or module cstr   --> src/nethostexcel.rs:69:13

I got below error in my ubunutu box
error[E0433]: failed to resolve: use of undeclared crate or module cstr
--> src/nethostexcel.rs:69:13
|
69 |             pdcstr!("test"),
|             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared crate or module cstr
|
= note: this error originates in the macro pdcstr (in Nightly builds, run with -Z macro-backtrace for more info)

Which version are you using?

rustc 1.57.0-nightly (e30b68353 2021-09-05)
cargo 1.56.0-nightly (18751dd3f 2021-09-01)

And what version of netcorehost?

netcorehost = "^0.3.1"

netcorehost = "^0.3.1"
path-absolutize = "3.0.10"
wchar = "0.10.1"

The bug should be fixed since<PHONE_NUMBER>15c9bd541ed3d4313cc5b17957519a alongside #12. Try a version >= 0.5.0, 0.6.4 should be the best choice as its the newest.

tried 0.6.4
^^^^^^^^ expected enum c_void, found ()
|
49 |         hello(_pointer, 1)
|               ^^^^^^^^ expected enum c_void, found ()
|
= note: expected raw pointer *const c_void
found raw pointer *const ()

You probably only need to change some occurance of *const () to *const std::ffi::c_void. You can also take a look at the updates examples.

i wanted to pass data to DLL

sample code
let c_string = CString::new("pass string".to_string()).expect("CString::new failed");
let ptr = c_string.into_raw();
let _pointer = ptr as *const ();

let result = unsafe {
    hello(_pointer, 1)
};

worked after adding cstr = "0.2.8" to toml and keeping verison 0.3.0

You just need to replace the *const () to *const std::ffi::c_void on the third line.


[Xcode] Add Menu Bar Command

Description

Added Show Recent Projects in Menu Bar command with preferences allowing to specify the number of visible project and project types.
Added search bar accessory to Search Recent Projects command List allowing to filter the results based on the selected project type.

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

nice! I added two very small suggestions. You don't have to implement them, but I think they'd improve UX ever so slightly. Once you've looked over them and decided, we should be good to go. :shipit:

Hi @sxn,
Thanks for your feedback ✌
I have just added your recommendation to update the title based on the isLoading state as well as the availability of recent projects (https://github.com/raycast/extensions/pull/2598/commits/3f365532bea2268f8516837b250371ee61aaf4c6).
Additionally, I have added a MenuBarExtra.Separator if recent projects are available (https://github.com/raycast/extensions/pull/2598/commits/e189abe6711b23aa2fbd7d4389bf3560ef3601b0).


Using different animations with modal

Is there an easy way to pass in a modifier to change the animation to a growIn or something other than the awesome animation it currently uses?

Didn't realize all I had to do was jump in the CSS file and change my animation as needed.  Thanks so much!

@simsketch Did you have an example of the animation you swapped to? Looking to change out the animation as well, and just wondering how you went about it/what you changed it to? Cheers!


Duplicate mcllh_eff functions defined in stats.py

Commit 75b64d0278cf1ee892078c42c10a8643aa757d35 renamed thorsten_llh as mcllh_mean and renamed say_llh as mcllh_eff in map.py but renamed both thorsten_llh and say_llh to mcllh_eff in stats.py.
See diff here: https://github.com/IceCubeOpenSource/pisa/commit/75b64d0278cf1ee892078c42c10a8643aa757d35#diff-1334536ceecd695ac38b5eaa6d586df2
Blame appears to lie one @austinschneider and/or @philippeller so I'm assigning this to you two this issue to sort out.

Pull request #548 should fix this issue.


Question about ssh and starship promt

I have a question about ssh and starship.
So i have customized my zsh shell with starship on my wsl2 linux . Now whenever i ssh to a server everything changes. I just get username@hostname: Is this normal? Do i need to customize every server? Or should starship just adjust the promt with the user and hostname of the server?

Hi,
Yes, this is expected behavior. When you SSH to a remote server, your shell is running on the remote server, not on your local machine. Therefore, the configuration and prompt settings that you have set up on your local machine will not be applied to the remote shell session.
To use the same prompt settings on the remote server, you should install and configure Starship on every remote server as well.
if you have multiple remote servers you can automate the task using ansible and a dotfiles repo.
you can check  https://github.com/peupeuv/dotfiles


Only rasterize if the screen is not raster-backed

Description
Only rasterize plots if the screen is not itself a raster device, i.e., backed by a PNG or ARGB surface.
This speeds up recording significantly, since the colorbuffer is essentially a raster device.
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Compile Times benchmark
Note, that these numbers may fluctuate on the CI servers, so take them with a grain of salt.
using time
master:  9.08 < 9.16 > 9.33, 0.09+-
pr:      9.09 < 9.13 > 9.22, 0.04+-
speedup: 0.99 < 1.00 > 1.02, 0.01+-
median:  -0.37% => invariant

This PR does not change the using time.
ttfp time
master   25.12 < 25.47 > 26.38, 0.43+-
pr       25.13 < 25.29 > 25.61, 0.19+-
speedup: 1.00 < 1.00 > 1.03, 0.01+-
median:  -0.72% => invariant

This PR does not change the ttfp time.


How to use metacrate for output?

Hi! I am using pyro to discover FDs from customer.csv, and I want to output score and errors of FDs. But I don't know how to use metacrate.
How should I correct the command below?
java -cp metanome-cli-1.1.0.jar:pyro-distro-1.0-SNAPSHOT-distro.jar de.metanome.cli.App  --algorithm de.hpi.isg.pyro.algorithms.Pyro  --separator comma --file-key inputFile  --files customer.csv --output crate:
I would appreciate a lot if u can reply!

Hi, I haven't worked with Pyro and Metacrate in ages, so I can just give a couple vague hints, I'm afraid.
First of all, you don't have to use Metacrate with Pyro. You can also just write the results to files using --output file:<path>. See the createResultReceiver() method for options.
But if you do want to use Metacrate, you'll first have to (1) create a new Metacrate instance and (2) import the schema of the database or table that you'd like to analyze. The README in the stratosphere/metadata-ms respository explains how to do that from a Jupyter notebook. If you're not going to use a Jupyter notebook, there are also two main classes that you can run to do those two steps, namely CreateMetadataStoreApp and CreateSchemaForCsvFilesApp. See their inlined Parameters classes for relevant command line flags. --schema-name is an arbitrary identifier for a collection of tables.
Once you have created your Metacrate instance, you should be able to use it with Pyro/Metanome CLI via --output crate:<path to your Metacrate instance>:<schema name>.<table name>, I think. Does that help you?

Hi, I haven't worked with Pyro and Metacrate in ages, so I can just give a couple vague hints, I'm afraid.
First of all, you don't have to use Metacrate with Pyro. You can also just write the results to files using --output file:<path>. See the createResultReceiver() method for options.
But if you do want to use Metacrate, you'll first have to (1) create a new Metacrate instance and (2) import the schema of the database or table that you'd like to analyze. The README in the stratosphere/metadata-ms respository explains how to do that from a Jupyter notebook. If you're not going to use a Jupyter notebook, there are also two main classes that you can run to do those two steps, namely CreateMetadataStoreApp and CreateSchemaForCsvFilesApp. See their inlined Parameters classes for relevant command line flags. --schema-name is an arbitrary identifier for a collection of tables.
Once you have created your Metacrate instance, you should be able to use it with Pyro/Metanome CLI via --output crate:<path to your Metacrate instance>:<schema name>.<table name>, I think. Does that help you?

Hi, I haven't worked with Pyro and Metacrate in ages, so I can just give a couple vague hints, I'm afraid.
First of all, you don't have to use Metacrate with Pyro. You can also just write the results to files using --output file:<path>. See the createResultReceiver() method for options.
But if you do want to use Metacrate, you'll first have to (1) create a new Metacrate instance and (2) import the schema of the database or table that you'd like to analyze. The README in the stratosphere/metadata-ms respository explains how to do that from a Jupyter notebook. If you're not going to use a Jupyter notebook, there are also two main classes that you can run to do those two steps, namely CreateMetadataStoreApp and CreateSchemaForCsvFilesApp. See their inlined Parameters classes for relevant command line flags. --schema-name is an arbitrary identifier for a collection of tables.
Once you have created your Metacrate instance, you should be able to use it with Pyro/Metanome CLI via --output crate:<path to your Metacrate instance>:<schema name>.<table name>, I think. Does that help you?

Hi! Your hints is useful. But I still got some problems. I use the command below:
java de.hpi.isg.mdms.tools.apps.CreateMetadataStoreApp --metadata-store ./cus.db
java de.hpi.isg.mdms.tools.apps.CreateSchemaForCsvFilesApp customer.csv   --schema-name "cus-schema"  --metadata-store "cus.db" --field-separator comma --has-header true
java de.metanome.cli.App --algorithm de.hpi.isg.pyro.algorithms.Pyro --files customer.csv  --separator comma --file-key inputFile --output crate:cus.db:cus-schema.customer --algorithm-config tableIdentifier:cus-schema.customer
The first two commands work well, but the last one has error:

Do u have advice? Thanks a l ot

It works finally, thanks.

It works finally，thanks!

Glad to hear you could make it work!


tvOS support

Waiting on release with tvOS support before merging.

Added tvOS support by flagging out features that are not available for tvOS.
Fixed layout issues on tvOS and iPad

Here are screen shots of before

Here are screen shots of the fixes after

@ErikEverson Thanks!
I'm hoping to merge the SDK version bump as its own PR in https://github.com/getditto/DittoSwiftTools/pull/138 so it gets called out in the changelog and we make sure to bump the major version here

From our conversation, this should also fix https://github.com/getditto/DittoSwiftTools/issues/139


Execute “gn gen out/debug” command  failed when compiling owt sdk on Ubuntu 18.04 system

Hi，
Seems that "gclient sync" is done.
When execute “gn gen out/debug” command
It outputs as follow:
ERROR at //testing/test.gni:21:30: Undefined identifier
tests_have_location_tags = generate_location_tags
^---------------------
See //testing/libfuzzer/fuzzer_test.gni:9:1: whence it was imported.
import("//testing/test.gni")
^--------------------------
See //media/media_options.gni:11:1: whence it was imported.
import("//testing/libfuzzer/fuzzer_test.gni")
^-------------------------------------------
See //chromecast/chromecast.gni:8:1: whence it was imported.
import("//media/media_options.gni")
^---------------------------------
See //chrome/browser/buildflags.gni:8:1: whence it was imported.
import("//chromecast/chromecast.gni")
^-----------------------------------
See //BUILD.gn:19:1: whence it was imported.
import("//chrome/browser/buildflags.gni")
^---------------------------------------
Any advice about this error?

I disabled "tests_have_location_tags" option in test.gni,and "gn gen out/debug" worked.
I execute "ninja -C out/debug/ owt_web_transport"  to compile the owt sdk
But at last it gets errors as below,seems that something wrong with linking ?
ninja: Entering directory `out/debug/'
[0/1] Regenerating ninja files
[2068/2068] SOLINK ./libowt_web_transport.so
FAILED: libowt_web_transport.so libowt_web_transport.so.TOC
python3 "../../build/toolchain/gcc_solink_wrapper.py" --readelf="../../third_party/llvm-build/Release+Asserts/bin/llvm-readelf" --nm="../../third_party/llvm-build/Release+Asserts/bin/llvm-nm"  --sofile="./libowt_web_transport.so" --tocfile="./libowt_web_transport.so.TOC" --output="./libowt_web_transport.so" -- ../../third_party/llvm-build/Release+Asserts/bin/clang++ -shared -Wl,-soname="libowt_web_transport.so" -fuse-ld=lld -Wl,--fatal-warnings -Wl,--build-id -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,--color-diagnostics -Wl,--no-call-graph-profile-sort -m64 -no-canonical-prefixes -Werror -Wl,--gdb-index -rdynamic -nostdlib++ --sysroot=../../build/linux/debian_sid_amd64-sysroot -Wl,-z,defs -Wl,--as-needed -Wl,-rpath=$ORIGIN -o "./libowt_web_transport.so" @"./libowt_web_transport.so.rsp"
ld.lld: error: undefined symbol: net::InitializeQuicConfig(net::QuicParams const&)

referenced by web_transport_http3_client.cc:467 (../../owt/web_transport/sdk/impl/web_transport_http3_client.cc:467)
obj/owt/web_transport/owt_web_transport_impl/web_transport_http3_client.o:(owt::quic::WebTransportHttp3Client::CreateConnection())
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.

How to sovle this problem?

Where is function "net::InitializeQuicConfig"  definition?
I can't find it in owt sdk impl code.

I have the same problem. How can I solve it?


If a yara rule is in the directory, the unpacker will end with an error

If I run retdec-unpacker from the directory where the *.yar or *.yara files is located, the program will end with an error. Small example follows.
$ ls
36b28625c4b9ebcdffd56b1ddabd0ca8f8325db520990c3e5890dd562dd2d823

$ retdec-unpacker 36b28625c4b9ebcdffd56b1ddabd0ca8f8325db520990c3e5890dd562dd2d823
[UPX] Detected DIRECT JUMP scrambler unpacking stub based on signature & metadata.
[UPX] Started unpacking of file '36b28625c4b9ebcdffd56b1ddabd0ca8f8325db520990c3e5890dd562dd2d823'.
[UPX] Detected NRV2B unpacking stub based on metadata.
[UPX] Detected filter 0x26 with parameter 0x12 based on UPX metadata.
[UPX] Unpacked data based on UPX metadata.
[UPX] Original header found at address 0x44be50 in extra data.
[UPX] Import hints address 0x44a000 found in extra data.
[UPX] Relocations hints address 0x44a758 found in extra data.
[UPX] Original TLS directory found at RVA 0x5fab0 with size 0x18.
[UPX] Original entry point address set to 0x310d6.
[UPX] Original load configuration directory found at RVA 0x57f00 with size 0xa0.
[UPX] Original resources directory found at RVA 0x6b000 with size 0x3db2f8.
[UPX] Original certificates directory found at offset 0x255a00 with size 0x20f0.
[UPX] Packed file has overlay with size of 0x152b7 bytes. Copying into unpacked file.
[UPX] Successfully unpacked '36b28625c4b9ebcdffd56b1ddabd0ca8f8325db520990c3e5890dd562dd2d823'!

$ cp ../yara-rule.yar .
$ retdec-unpacker 36b28625c4b9ebcdffd56b1ddabd0ca8f8325db520990c3e5890dd562dd2d823
retdec-unpacker: compiler.c:701: yr_compiler_get_rules: Assertion `compiler->errors == 0' failed.
Aborted (core dumped)

This should be fixed since 4878585d1a51e7b4c28c8eae7ed7bb2cbc531f93, could you please check that you have this commit in your local build and try again?

I used an older version, in the new version it works without problems, thank you.


chore: updates CRS, more tests passing

Some CRS tests are now compatible with Coraza( see https://github.com/coreruleset/coreruleset/pull/3133 and https://github.com/coreruleset/coreruleset/pull/3134). This PR updates the CRS to the latest commit and reduces the failing tests

Awesome!
On Wed, 22 Feb 2023, 16:45 codecov[bot], @.***> wrote:

Codecov
https://codecov.io/gh/corazawaf/coraza/pull/674?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf
Report
Base: 80.31% // Head: 80.24% // Decreases project coverage by -0.07%
⚠
Coverage data is based on head (9be6486)
https://codecov.io/gh/corazawaf/coraza/pull/674?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf
compared to base (ad561b8)
https://codecov.io/gh/corazawaf/coraza/commit/ad561b8035f8e4598b7ce0f51331c9242af0de24?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf
.
Patch has no changes to coverable lines.
Additional details and impacted files
@@            Coverage Diff             @@
v3/dev     #674      +/-
==========================================

Coverage   80.31%   80.24%   -0.07%

==========================================
Files         145      145
Lines        7756     7756
==========================================

Hits         6229     6224       -5

Misses       1296     1301       +5
Partials      231      231

Flag Coverage Δ
default 76.20% <ø> (-0.04%) ⬇
examples 27.08% <ø> (ø)
ftw 51.47% <ø> (-0.07%) ⬇
ftw-multiphase 51.57% <ø> (-0.07%) ⬇
tinygo 75.20% <ø> (ø)
Flags with carried forward coverage won't be shown. Click here
https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf#carryforward-flags-in-the-pull-request-comment
to find out more.
Impacted Files
https://codecov.io/gh/corazawaf/coraza/pull/674?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf Coverage
Δ
actions/ctl.go
https://codecov.io/gh/corazawaf/coraza/pull/674?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf#diff-YWN0aW9ucy9jdGwuZ28= 68.94%
<0.00%> (-2.64%) ⬇
Help us with your feedback. Take ten seconds to tell us how you rate us
https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf.
Have a feature suggestion? Share it here.
https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf
☔ View full report at Codecov
https://codecov.io/gh/corazawaf/coraza/pull/674?src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf
.
📢 Do you have feedback about the report comment? Let us know in this
issue
https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=corazawaf
.
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/pull/674#issuecomment-1440283690,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAS2MPXDS2RK2UZYNT3WYYYA3ANCNFSM6AAAAAAVEPWUDY
.
You are receiving this because your review was requested.Message ID:
@.***>

Can we force merge this ?

I would go for it. Nothing has changed in terms of coverage.
On Wed, 22 Feb 2023, 17:45 Juan Pablo Tosso, @.***>
wrote:

Can we force merge this ?
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/pull/674#issuecomment-1440401865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATVEWYGVWJ2AM26YWTWYY7CZANCNFSM6AAAAAAVEPWUDY
.
You are receiving this because your review was requested.Message ID:
@.***>


Possible Sandstorm Deployment?

This is a suggestion for Nightcoders.
I know you said that you are thinking of potential commercialization. If that doesn't appeal to you down the line I think it would be a nice direction to package the setup as a Sandstorm application.
I've been running Sandstorm for about a year now and I believe in it's general messaging. Would love to help implement/test the app.
And as always thanks for all your work Zach.

Never heard of it, what exactly is a Sandstorm app? Are they web apps embedded into something else?

I don't want to butcher their terminology/description so here is a good page describing the app developer standpoint: https://sandstorm.io/developer
From a basic (poorly worded) perspective, Sandstorm runs on a server and apps run as instances within it thinking that they are running as they are normally designed. The main offering is that sandstorm can manage user account details, sessions and external security, so that the app can offload that to it.
For end users this means that they just need to run a single instance of Sandstorm, and have access to as many server+web based apps as they want. Here is a list of the current ones available: https://apps.sandstorm.io/
All data remains on the users server, which is mostly why I am using it.
For Nightcoders it would allow people to just install the whole stack on their server with one click, and share instances of it with others or just use it themselves from wherever. Sandstorm can have multiple users, and multiple instances of each app. That could be per-project or per-team. Its quite flexible!
Sorry for stream of consciousness dump. If you need more clarification I can attempt to provide it.

Also this is their 'quick packaging tutorial' if you want to see whats involved with a generic app: https://docs.sandstorm.io/en/latest/vagrant-spk/packaging-tutorial/


EmissionTracker failed on GCP Colab Enteprise

CodeCarbon version: 2.4.2
Python version: 3.10.12
Operating System: Ubuntu 22.04.3 LTS

Description
Tried to launch codecarbon EmissionTracker on GCP Colab Enterprise.
It works correctly on Colab Web with same codecarbon version 2.4.2.
It failed on different GCP region trials always with same error message below.
As you recently updated GCP location metatadata this might be related.
I appreciate your help.
What I Did
from codecarbon import EmissionsTracker
tracker = EmissionsTracker()

[/usr/local/lib/python3.10/dist-packages/codecarbon/emissions_tracker.py](https://localhost:8080/#) in __init__(self, project_name, measure_power_secs, api_call_interval, api_endpoint, api_key, output_dir, output_file, save_to_file, save_to_api, save_to_logger, logging_logger, save_to_prometheus, prometheus_url, gpu_ids, emissions_endpoint, experiment_id, experiment_name, co2_signal_api_token, tracking_mode, log_level, on_csv_write, logger_preamble, default_cpu_power, pue)
    379         self._data_source = DataSource()
    380
--> 381         cloud: CloudMetadata = self._get_cloud_metadata()
    382
    383         if cloud.is_on_private_infra:

[/usr/local/lib/python3.10/dist-packages/codecarbon/emissions_tracker.py](https://localhost:8080/#) in _get_cloud_metadata(self)
    881     def _get_cloud_metadata(self) -> CloudMetadata:
    882         if self._cloud is None:
--> 883             self._cloud = CloudMetadata.from_utils()
    884         return self._cloud
    885

[/usr/local/lib/python3.10/dist-packages/codecarbon/external/geography.py](https://localhost:8080/#) in from_utils(cls)
     44
     45         provider: str = cloud_metadata["provider"].lower()
---> 46         region: str = extract_region_for_provider.get(provider)(cloud_metadata)
     47         if provider in ["aws", "azure"]:
     48             logger.warning(

[/usr/local/lib/python3.10/dist-packages/codecarbon/external/geography.py](https://localhost:8080/#) in <lambda>(x)
     35             "aws": lambda x: x["metadata"]["region"],
     36             "azure": lambda x: x["metadata"]["compute"]["location"],
---> 37             "gcp": lambda x: extract_gcp_region(x["metadata"]["zone"]),
     38         }
     39

KeyError: 'zone'

@eherra

Thanks for reporting this. Can you run the command curl http://<IP_ADDRESS>/computeMetadata/v1/instance/?recursive=true&alt=json because I expect that there is a missing field "zone" in "metadata". It is not related to the update of GCP location data in CodeCarbon. GCP may have modify the output of their API we use to know if we are on GCP and where.

Hi Benoit,
thanks for your reply.
After I ran the command from GCP colab entreprise notebook I got the following:
Missing required header: Metadata-Flavor
I appreciate your feedback.

Sorry, from https://stackoverflow.com/questions/62026424/is-it-possible-to-obtain-instance-metadata-for-gcp-on-google-collaboratory it seems to be ```
curl -v -w "\n" -H "Metadata-Flavor: Google" http://<IP_ADDRESS>/computeMetadata/v1/instance/machine-type

Hi,
here is the output:

Trying <IP_ADDRESS>:80...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 80 (#0)

GET /computeMetadata/v1/instance/machine-type HTTP/1.1
Host: <IP_ADDRESS>
User-Agent: curl/7.81.0
Accept: /
Metadata-Flavor: Google

Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< Metadata-Flavor: Google
< X-Content-Type-Options: nosniff
< Date: Fri, 14 Jun 2024 11:31:14 GMT
< Content-Length: 10
<
Not Found
Connection #0 to host <IP_ADDRESS> left intact

Sorry, it's curl -v -w "\n" -H "Metadata-Flavor: Google" http://<IP_ADDRESS>/computeMetadata/v1/instance/?recursive=true&alt=json
I tested it and I get this from Cloud Shell (I delete un-relevant lines)
{
  "cpuPlatform": "Intel Broadwell",
  "machineType": "projects/8xxxxx2/machineTypes/e2-standard-4",
  "zone": "projects/8xxxx2/zones/europe-west1-b"
}

So it seems that on Colab Entreprise you get an answer from the GCP API but it's an empty JSON {}
We have to update our GCP detection to handle this case. Thanks for reporting the details.

Hello, I've opened a PR for that : https://github.com/mlco2/codecarbon/pull/580


Adds Serializer and virtual functions for new transform inits

Submission Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary
This adds a stan::io::serializer class that reads in objects and writes them to a linear array of data. This will be used in the new transform_inits() signature for the model class to serialize the unconstrained parameters.
The only function here is .write() which accepts any Stan type and writes that to the internal reference to a linear vector.
Eigen::MatrixXd xx = Eigen::MatrixXd::Random(10, 10)
Eigen::VectorXd my_vec(100);
stan::io::serializer serializer(my_vec);
serializer.write(xx); // Write xx to my_vec

The new transform inits signature is of the form
void transform_inits(Eigen::VectorXd& input_r,
                                Eigen::VectorXd& params_r,
                                std::ostream* msgs)

Where input_r is the input parameters values and  params_r is an input/output vector of the unconstrained parameters values
The new transform inits will use these classes by wrapping input_r into stan::io::deserializer and params_r into stan::io::serializer, where it can perform the unconstrain as
stan::io::deserializer deserializer(input_r);
stan::io::serializer serializer(params_r);
serializer.write(deserializer.read_free_lub<std::vector<Eigen::MatrixXd>>(lb, ub, J, N, M));

Where J is the size of the array and N, M are the dimensions of the matrix.
Intended Effect
Along with #3018 this will cleanup a lot of the code generated by the Stan compiler
How to Verify
Tests can be run with
./runTests.py ./src/test/unit/io/serializer_varmat_test.cpp ./runTests.py ./src/test/unit/io/serializer_test.cpp ./runTests.py ./src/test/unit/io/serializer_stdvector_test.cpp

These test all the basic types, arrays of those basic types, and var_value<> types with inner values of the basic types
Side Effects
None
Documentation
Documentation is written for the new class and for each method in the class.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Steve Bronder
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses: Ste

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

@bbbales2 I thought we could just add the new signature in this PR but I think the steps here are

Put in this PR and the deserializer PR
Ryan puts in his PR
We then add the new transform_init() signature since it exists in the model and use it in the code

Aight @bbbales2 I think this is good to go!

Are there examples of what the new stanc3 code should look like using this?
Just a note from another thread - we can't change the transform_init method without bumping the major version number of Stan, so I would propose we not plan on that right now.


small fixups re: browser & browser commands

When going through the Getting Started writeup, I had two random issues with plotting on my system (macOS & SBCL). With these changes, the plot example works correctly.

Thank you! Much appreciated. I don't have a MacOS system to test on, and I'm glad someone with interest does.
You should be prompted by the CLA assistant to do a 'click-sign' and then it will be merged automatically (I think, the classistant setup is new)
Thanks again.

Huh.  As it happens, magicl and brushing up on linear algebra is my Christmas time project this year. If I'm lucky, I might get to cl-quil too.
Small world.

Huh.  As it happens, magicl and brushing up on linear algebra is my Christmas time project this year. If I'm lucky, I might get to cl-quil too.
Small world.

That's great to hear!


add snapshot processors for class models

[BREAKING CHANGE] The model override fromSnapshot has been removed in favor of fromSnapshotProcessor / toSnapshotProcessor for Model / ExtendedModel. These allow you to set up pre/post snapshot processors for models.

Snapshot pre/post-processors: fromSnapshotProcessor / toSnapshotProcessor
fromSnapshotProcessor might be used to transform an input snapshot into the model expected input snapshot.
This is useful for example for versioning.
Note that the $modelType property will always be there and will remain unchanged no matter the transformation.
@model("name")
class Name extends fromSnapshotProcessor(
  Model({
    // in version 2 we split fullName into firstName and lastName
    _version: prop(2),
    firstName: prop<string>(),
    lastName: prop<string>(),
  },
  (
    sn: { _version: 2; firstName: string; lastName: string } | { _version: 1; fullName: string }
  ) => {
    if (sn._version === 2) {
      return sn
    }

    const [firstName, lastName] = sn.fullName.split(" ")

    return {
      _version: 2,
      firstName,
      lastName,
    }
  }
) {
  // ...
}

toSnapshotProcessor is the opposite and might be used to transform the model expected output snapshot into another kind of object snapshot.
Note that the $modelType property will always be there and will remain unchanged no matter the transformation.
@model("name")
class Name extends toSnapshotProcessor(
  Model({
    firstName: prop<string>(),
    lastName: prop<string>(),
  },
  (sn, modelInstance) => {
  // we want to also keep fullName for backwards compatibility
  return {
    ...sn,
    fullName: `${sn.firstName} ${sn.lastName}`,
  }
}) {
  // ...
}

Thanks for implementing this feature and also the version example, which I find very helpful!
A comment and a question:

I find calling fromSnapshotProcessor/toSnapshotProcessor a bit hard to read, especially with multiple calls. How about a builder pattern style API?class M extends Model(…)
  .fromSnapshotProcessor(…)
  .fromSnapshotProcessor(…) {
  // …
}

Just to be sure I understand the feature correctly: Both fromSnapshotProcessor and toSnapshotProcessor can be called on the same model, right? And multiple calls of the same processor behave like chaining the processors?

class M extends Model(…)
  .fromSnapshotProcessor(…)
  .fromSnapshotProcessor(…) {
  // …
}

That was my first attempt, but adding builders to model breaks "the new way to make generics" that you devised :(
In the end I think I'm gonna move those functions to the model options, which should be more readable
class M extends Model(..., {
  fromSnapshotProcessor(...) {},
  toSnapshotProcessor(...) {}
}) {}

The only downside is that it doesn't make them directly composable anymore (they are with the original version), but then again you can just call multiple functions inside the fromSnapshotProcessor if needed

Ah, I see. Yes, that would be more readable in my opinion. 🙂


LDM package error

Hello
When I use the inference code of (depth) I get this error
/models_depth/model.py", line 15, in
from ldm.util import instantiate_from_config
ModuleNotFoundError: No module named 'ldm.util'; 'ldm' is not a package
I have already installed ldm: pip install ldm
ldm                       0.1.3
but there is no util in it
ldm.txt

Hi, you should not install ldm, it is module inside SD.
Please check Colab notebook, I have added for quick demo.
https://colab.research.google.com/drive/1rd0_2AMyHlEaeYlWldZ-xGaGRYhP_TVb?usp=sharing


Dropdown is not working

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
The dropdown isn't working, it's not even working on the website. Also the website dropdowns aren't working like changing mode (dark and light mode) and version change dropdown.
I hope this issue can be resolved quickly, thank you.
Reduced test cases
https://codepen.io/codepen-io-swetha/pen/OJYjjKm
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.3.3

Hello @Ravula-Swetha

The dropdown isn't working, it's not even working on the website.

What do you mean by "it's not working"? When you click on it, the menu is not displayed?
If that's the case, you might try alternative CDNs as jsdelivr can be blocked in some countries or specific environments.

Yes, when I click on it, the menu isn't displayed. Thank you, I will try
using the alternative CDNs.
But why is it that the dropdowns aren't working on the bootstrap website
for me?
On Sun, Jun 9, 2024 at 11:35 AM Julien Déramond @.***>
wrote:

Hello @Ravula-Swetha https://github.com/Ravula-Swetha
The dropdown isn't working, it's not even working on the website.
What do you mean by "it's not working"? When you click on it, the menu is
not displayed?
If that's the case, you might try alternative CDNs
https://getbootstrap.com/docs/5.3/getting-started/download/#alternative-cdns
as jsdelivr can be blocked in some countries or specific environments.
—
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/issues/40538#issuecomment-2156337385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDB4ZVFEGMPU4LBAGU33LXTZGPWB5AVCNFSM6AAAAABJAEVWFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWGMZTOMZYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

But why is it that the dropdowns aren't working on the bootstrap website for me?

I don't know. Could you check if there are some errors in your console or anywhere else?

Seems like you may have JS disabled or some other browser extension interfering? Works fine for us.


Example with WSJ feed no longer works due to security

The WSJ feed used in this example now returns an error:
403 - The underlying RSS server forbids incoming requests.

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

ID: 4b68d35f-e331-bb2b-dd1e-c951bf6baeda
Version Independent ID: d01f87a2-a873-2e8e-37ca-94aecceb5e9f
Content: Create an automated integration workflow - Azure Logic Apps
Content Source: articles/logic-apps/quickstart-create-first-logic-app-workflow.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hello @ca-thompson, Thank you for your feedback! We will review and update as appropriate.

Hello @ca-thompson, I was able to perform the tutorial as shown in the example below. I did not encounter any 403 forbidden error.

Please let me know if you are still facing any issue.

Hello @ca-thompson, Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


Unable to install due to not up to date deps

When running npm install typebox-validators, npm tells me that it cannot resolve dependency @sinclair/typebox, as my project uses<EMAIL_ADDRESS>and this requires<EMAIL_ADDRESS>

Oh dear. I upgraded to typebox 0.32.x, and now some tests fail. It looks like typebox made some change that is incompatible with typebox-validators customer error messages.

same problem here; are you planning to update that, or not yet planned ? :)
and thanks for the lib

I'm not planning to revise the code, but I welcome a PR.
This will be the second time the code had to be revised to support a change in TypeBox, and this time it's not clear to me that I'll be able to retain existing functionality.
I get the feeling that it's better to move the functionality into TypeBox proper, so there will be effort not to break it on each revision.


Only provide guaranteed deprecation dates

Summary
Currently, we provide deprecation dates for our dependencies, but if there isn't one easily discoverable, we make our best effort to approximate it.
Since we will eventually be serving the dependency metadata in a Bill of Materials, we should not estimate any deprecation dates for our dependencies that are not explicitly stated by the vendor, and instead should leave them blank.
We should take an inventory of each of our dependencies' metadata and verify the deprecation date validity. If it is an estimation, we should remove that metadata entirely.

[ ] bundler
[ ] composer
[ ] curl
[ ] dotnet-aspnetcore
[ ] dotnet-runtime
[ ] dotnet-sdk
[ ] go
[ ] httpd
[ ] icu
[ ] nginx
[ ] node
[ ] php
[ ] pip
[ ] pipenv
[ ] python
[ ] ruby
[ ] rust
[ ] tini
[ ] yarn

Acceptance
The outcome of this issue should be that all dependencies in the dep-server contain either A. an accurate deprecation date provided by the dependency vendor or B. no deprecation date at all.

node, dotnet, php, python all have deprecation dates

Update: Node.JS parses the deprecation date off of https://raw.githubusercontent.com/nodejs/Release/master/schedule.json

Dependency
Deprecation Date

bundler
none

composer
none

curl
none

dotnet-aspnetcore
some (3.* and 2.*), not all (5.*)

dotnet-runtime
some (3.* and 2.*), not all (5.*)

dotnet-sdk
some (3.* and 2.*), not all (5.*)

go
none

httpd
none

icu
none

nginx
none

node
yes, all from nodejs/Release/master/schedule.json

php
yes, estimated to be +3 years from release date

pip
none

pipenv
none

python
yes directly from python.org/downloads

ruby
none

rust
none

tini
none

yarn
none

In conclusion, all the dependencies that have deprecation dates take them directly from official dependency release pages. The only outlier is PHP, in which we add 3 years onto the release date to get the deprecation date. An exception is made for this case because the PHP release page explicitly states the three year rule, with explicit examples on the page. I have a high degree of confidence in these deprecation dates


Integrate node-panic to dump process variables and info

This is just would be the marriage of node-panic and this file and exposing node-panic.

node-panic is no longer under active development.


Merge release 4.10.6

Note $subjetc

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Thisara-Welmilla:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.


feat: multi component in different namespace with same git url

Description
This PR adds a scenario when two components use same git url in two different namespaces, it should result in failure
Issue ticket number and link
https://issues.redhat.com/browse/STONEBLD-1613
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test all


Sytem crashes because of RAM Overload

Checklist

[x ] I have read the common issues wiki page
[ x] I have checked to make sure the plugin is up to date

Describe the bug
Error in Homebridge Protokoll. Over hours too much RAM load at synology.
"[TuyaAccessory] Operating system complained of resource exhaustion; did I open too many sockets?"
Environment (please complete the following information):

OS: Homebridge 1.30
iOS version:
Homehubs:
Node Version:
Plugin Version: back from 1.40 to 1.30 because of #205
Accessory Type

Hope you can help. Because the hole system crashes because of RAM-Overload.
Thanks.
Mark

This is homebridge or device related, not the plugin it seems.


Run pylint on Mac

Codecov Report

Merging #1085 (bf8e396) into master (34b6656) will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1085      +/-   ##
==========================================
+ Coverage   91.27%   91.28%   +0.01%
==========================================
  Files          90       90
  Lines       13358    13358
  Branches     1493     1493
==========================================
+ Hits        12192    12194       +2
+ Misses        954      953       -1
+ Partials      212      211       -1

Impacted Files
Coverage Δ

coverage/pytracer.py
20.51% <0.00%> (ø)

tests/test_oddball.py
82.73% <0.00%> (+1.19%)
:arrow_up:

Codecov Report

Merging #1085 (bf8e396) into master (34b6656) will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1085      +/-   ##
==========================================
+ Coverage   91.27%   91.28%   +0.01%
==========================================
  Files          90       90
  Lines       13358    13358
  Branches     1493     1493
==========================================
+ Hits        12192    12194       +2
+ Misses        954      953       -1
+ Partials      212      211       -1

Impacted Files
Coverage Δ

coverage/pytracer.py
20.51% <0.00%> (ø)

tests/test_oddball.py
82.73% <0.00%> (+1.19%)
:arrow_up:

Codecov Report

Merging #1085 (1f6f605) into master (34b6656) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #1085   +/-   ##
=======================================
  Coverage   91.27%   91.27%
=======================================
  Files          90       90
  Lines       13358    13358
  Branches     1493     1493
=======================================
  Hits        12192    12192
  Misses        954      954
  Partials      212      212

Impacted Files
Coverage Δ

coverage/pytracer.py
20.51% <0.00%> (ø)


fix: get correct github token

It appears we forgot to make this change when we started using the secrets environment.

This PR is invalid. The github token is being correctly retrieved from the secrets environment under the branches organization


Enhancement: Add per inverter AC_power_total, per panel DC_voltage & DC_current

It seems that currently APSystemsECU.py has some shortcomings.
From my view these are:

AC_voltage is reported in per panel data, where DC_voltage would be expected. Further outlined in this comment

AC_power for total inverter output is missing, but seems the most relevant value as AC_power is what gets charged by utility companies. Currently total DC input power is reported as "power" but that is a too high value due to DC to AC conversion losses.

per panel DC_voltage & DC_current are missing

From  findings during reverse engineering APSystems ECU communication in https://community.home-assistant.io/t/apsystems-aps-ecu-r-local-inverters-data-pull/260835/238 I assume (but have yet to proof!) that above shortcomings could be fixed.
Unfortunately the fix could introduce compatibly issues for existing solutions. Eventually just a fix of "power" as "AC_power for total inverter output" & per panel DC_voltage could be feasible.
Therefore an alternative would be adding a new class with the new values (and eventually fix of "power" as "AC_power for total inverter output" in current class)
May I ask what course of action would be the best approach to address the shortcomings?

Example from (restricted to installers) APS EMA report:

Data same time from (slightly modified) ECU_B.py:
{'current_power': 945,
 'ecu_firmware': 'ECU_B_1.2.33',
 'ecu_id': '2163******',
 'inverter_qty': 1,
 'inverters': {'7020********': {'DC_power': [469, 476],
                                'DC_voltage': [240, 240],
                                'channel_qty': 2,
                                'frequency': 50.0,
                                'model': 'YC60/DS3-S-M-D-L',
                                'online': True,
                                'signal': 73,
                                'temperature': 45,
                                'uid': '7020********'}},
 'lifetime_energy': 2001.8,
 'qty_of_inverters': 1,
 'qty_of_online_inverters': 1,
 'timestamp': '2024-09-14 13:14:41',
 'today_energy': 3.87}
Today energy : 3.87 kWh
Current power (AC): 945 W
Total energy : 2001.8 kWh
Number inverter: 1
Inverter Id: 7020********
Frequency: 50.0 Hz
Signal: 73 %
Temperature: 45 °C
Voltage inverter (DC) 1 panel 1: 240 V
Power inverter (DC)1 panel 1: 469 W
Power inverter (DC)1 panel 2: 476 W

Difference "Current power (AC): 945 W" to "actual AC power: 897 W" is 5.2% (= DC to AC conversion loss)

So this goes for an ECU-B with an YC600?

for an ECU-B with a DS3 and after this works with a QT2.
Most important from my view is an answer to question:

May I ask what course of action would be the best approach to address the shortcomings?

The query retrieves other data fields than what is being sent to EMA. The query in the integration does not contain DC voltages from individual panels (afaik). The data pushed to EMA does so that's why you see them in the EMA site.
Where you mention: "AC_voltage is reported in per panel data" you mean AC voltage per inverter right?

Where you mention: "AC_voltage is reported in per panel data" you mean AC voltage per inverter right?

correct

So that data is correct, I mean - I only see AC voltages that are within the standard for the country ~230V AC in The Netherlands

These are the data fields (YC600) which are being sent to EMA (currently zero because the inverter is down)

It's taken from the proxy solution (under contruction): https://github.com/HAEdwin/homeassistant-apsystems_ecu_proxy

It's taken from the proxy solution (under contruction): https://github.com/HAEdwin/homeassistant-apsystems_ecu_proxy

the data I'm after is apparently extracted in api.py function get_inverters.
Do you happen to know to APS command that triggers this response?

Unfortunately not. What we've done in the beginning is looking and interpreting data dat is shown in the ECU app (later EMA manager) and there it does not contain the data you're after. There is no documentation or further reference on what commands can be send to the ECU.

looking and interpreting data dat is shown in EMA manager and there it does not contain the data you're after.

The data is available in EMA web but only shown to privileged "installer" accounts (see screenshots in https://github.com/ksheumaker/homeassistant-apsystems_ecur/issues/268#issuecomment-2350959248 showing the data I'm after)

Yes but it ain't in the apps (unless you discover something else) and therefor is not included in this integration. The proxy method intercepts data that is sent to EMA and it does include the data.


Features request

Hi! Interesting app, but we already talk about :)
I would like to request some features:

Possibility to send mail when video is lost
Possibility to put the program in FULL Screen without the bar and border
Possibility to resize the Video in the matrix to create (if user need it) a camera view in different dimension. This will allow to have a focus on a camera and have others smaller.
Try to add an image for example.

Thanks

Fullscreen realized! Download Beta Portable

That's great Grigoy, thanks!!!!!!!!!!! :) :) :) :)
2018-04-26 20:48 GMT+02:00 Grigory Lobkov<EMAIL_ADDRESS>
Fullscreen realized! Download Beta Portable
https://github.com/grigory-lobkov/rtsp-camera-view/releases/tag/v<IP_ADDRESS>b
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grigory-lobkov/rtsp-camera-view/issues/1#issuecomment-384750947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkSDEFdMOad5TQeANQkmDNZJ5TtgErKJks5tshZ5gaJpZM4TFP3H
.

Have you tried <IP_ADDRESS> ?
Are  you using it, or wait for a new features ?

Hi Grigory,
No tried the <IP_ADDRESS>, I can’t find it on GitHub.
I tried the <IP_ADDRESS>b and it works but I managed to do “full screen” only manually editing the xml.
And I have a question: there is a tag in the xml called “screen”. I thought it was useful to open the app directly in full screen on a certain screen if I have multi monitor, but I don’t know how to use it.
Is for this kind of use?
Inviato da Iphone

Il giorno 05 mag 2018, alle ore 17:08, Grigory Lobkov<EMAIL_ADDRESS>ha scritto:
Have you tried <IP_ADDRESS> ?
Are you using it, or wait for a new features ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Fullscreen fixed in <IP_ADDRESS>
This options is for command line. Just add "screen=N", where N is number of monitor, started with 0.
You can also add "fullscreen" or "maximize" there.
You can find fresh beta in the same release:
https://github.com/grigory-lobkov/rtsp-camera-view/releases/tag/v<IP_ADDRESS>b
I'm planning to start new beta, when something really new will appear.
P.S. "full screen" bug was another "Issue" ;)  Next time, make it, please :) - it will be easier to search for somebody...

Ok Grigory, thank you!
Inviato da Iphone

Il giorno 05 mag 2018, alle ore 22:44, Grigory Lobkov<EMAIL_ADDRESS>ha scritto:
Fullscreen fixed in <IP_ADDRESS>
This options is for command line. Just add "screen=N", where N is number of monitor, started with 0.
You can also add "fullscreen" or "maximize" there.
You can find fresh beta in the same release:
https://github.com/grigory-lobkov/rtsp-camera-view/releases/tag/v<IP_ADDRESS>b
I'm planning to start new beta, when something really new will appear.
P.S. "full screen" bug was another "Issue" ;) Next time, make it, please :) - it will be easier to search for somebody...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

"fullscreen" available on right click

"screen=N" from command line and settings.xml

:)

I've found a lot of bugs there, while testing. So, new betas and implements are coming soon... :)

Grigory: installed the latest beta and is working very good! Need to
recreate the XML because tells me there was an error, but opened and worked
good.
What is not working is the screen number extension. It opens every time on
the screen where I launch the command.
Apart from that, is working very good and no more problem with the text on
the screen that disappear :)
Thanks again for your patience and support.
2018-05-06 21:14 GMT+02:00 Grigory Lobkov<EMAIL_ADDRESS>
I've found a lot of bugs there, while testing. So, new betas and
implements are coming soon... :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grigory-lobkov/rtsp-camera-view/issues/1#issuecomment-386905484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkSDEEeyyrNuO9Kd9YKsWhzE7GiIu7RUks5tv0uhgaJpZM4TFP3H
.

tells me there was an error, but opened and worked good.

Does program take your settings, or you needed to recreate sources ?

What is not working is the screen number extension. It opens every time on
the screen where I launch the command

Can you explain, how are you launching the app, maybe command line ?
Btw, screen number starts from zero in program ... (maybe it's habitually to increment it by one?)

no more problem with the text on the screen that disappear

Haven't heard yet. Don't explain, cause it's good now)
Thank you for your suport and feedback)

Hi Grigory, sorry for the delay:
tells me there was an error, but opened and worked good.
Does program take your settings, or you needed to recreate sources ?
                    The program take the settings, but tells me there

was an error on the XML. I saved the old XML with another name, launched
the program and let him save a new XML. So I opened the new XML and pasted
the  tags from the old to new and worked without recreate the
sources. I can try to recover the old XML and send to you with the new so
is possibile to see differences.
What is not working is the screen number extension. It opens every time on
the screen where I launch the command
Can you explain, how are you launching the app, maybe command line ?
Btw, screen number starts from zero in program ... (maybe it's habitually
to increment it by one?)
                     I launched a cmd shell and write directly the

command with the screen=1. It opens everytime on the screen where the cmd
shell is positioned. For the moment, I created 3 different folders with the
program inside, with 3 different xmls and also created 3 windows shortcuts
pointing to each directory executable, placed them on each display and
launched from there I can put the program on the screen where I launch the
shotcut. Saving in the XML the fullscreen=1, I have the program going
fullscreen on the desktop where the shortcut is placed. On the shortcut I
didn't put any attributes, just start the program.
Hope I was clear :-)
no more problem with the text on the screen that disappear
Haven't heard yet. Don't explain, cause it's good now)
Thank you for your support and feedback)
                   Mate, thanks go to you for your patience, kindness

and availability :-)
2018-05-07 19:41 GMT+02:00 Grigory Lobkov<EMAIL_ADDRESS>
tells me there was an error, but opened and worked good.
Does program take your settings, or you needed to recreate sources ?
What is not working is the screen number extension. It opens every time on
the screen where I launch the command
Can you explain, how are you launching the app, maybe command line ?
Btw, screen number starts from zero in program ... (maybe it's habitually
to increment it by one?)
no more problem with the text on the screen that disappear
Haven't heard yet. Don't explain, cause it's good now)
Thank you for your suport and feedback)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grigory-lobkov/rtsp-camera-view/issues/1#issuecomment-387144701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkSDEAl35Ah9UQ4SgcdLbYXHh6OUueMmks5twIdcgaJpZM4TFP3H
.

Great Grigory!
Tomorrow I’ll try the new version and let’s see if is the “screen=“ argument will work :-)
Have a nice Sunday!
Inviato da Iphone

Il giorno 11 mag 2018, alle ore 22:20, Grigory Lobkov<EMAIL_ADDRESS>ha scritto:
support old settings.xml - fixed.
some command line arguments skipped - fixed.
Please, check <IP_ADDRESS> out! 1.0.0 BETAs
Thanks for you help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok Grigory, I tried the new version. Now the "screen" option works, via
command line and also in the XML, but the app crashes whenever it starts.
It opens on the screen selected but crashes with no messages, windows just
says "program stopped". Click OK on the pop-up and need to reopen the app.
2018-05-13 10:57 GMT+02:00 Zio Webbo<EMAIL_ADDRESS>
Great Grigory!
Tomorrow I’ll try the new version and let’s see if is the “screen=“
argument will work :-)
Have a nice Sunday!
Inviato da Iphone
Il giorno 11 mag 2018, alle ore 22:20, Grigory Lobkov <
<EMAIL_ADDRESS>ha scritto:
support old settings.xml - fixed.
some command line arguments skipped - fixed.
Please, check <IP_ADDRESS> out! 1.0.0 BETAs
https://github.com/grigory-lobkov/rtsp-camera-view/releases/tag/v<IP_ADDRESS>b
Thanks for you help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grigory-lobkov/rtsp-camera-view/issues/1#issuecomment-388475213,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkSDEDnYIW_RykLt0ECzGa4h4Sqo2LEjks5txfKKgaJpZM4TFP3H
.

Can you provide a screen-shot?
What OS are you using? ... I tried WinXPSP2, Win10, cannot reproduce your error.
What Framework version?
Try to delete settings.cfg...
Try to take dll's from previous version...
Try to run without any command line parameters. I tried also:
"C:\Documents and Settings\Administrator\Desktop\rtsp-camera-view <IP_ADDRESS> beta\RtspCameraView.exe" screen=0 fullscreen

VLC 2.1.5 fresh installed.

WinXP SP3
Microsoft .NET Framework 4 Client Profile
Microsoft .NET Framework 4 Extended
You can download framework here
Windows 10.0.14393
No any additional framework

Everything worked fine.
What difference in our systems we have?

Hi mate!
The system is:
Windows 7 SP1
Microsoft .NET Framework 4.7
VLC 2.1.5 fresh installed
Inviato da Iphone

Il giorno 15 mag 2018, alle ore 06:01, Grigory Lobkov<EMAIL_ADDRESS>ha scritto:
VLC 2.1.5 fresh installed.
WinXP SP3
Microsoft .NET Framework 4 Client Profile
Microsoft .NET Framework 4 Extended
You can download framework here
Windows 10.0.14393
No any additional framework
Everything worked fine.
What difference in our systems we have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Testing OS: Windows 7 Enterprise SP1

C:\> ver
Microsoft Windows [Version 6.1.7601]

VLC 2.1.5 fresh installed

Microsoft .NET Framework 4.5
worked fine

Microsoft .NET Framework 4.7 NDP47-KB3186497-x86-x64-AllOS-ENU
worked fine

Please, check files rights, download again, reinstall Framework / VLC, try another OS / another beta.

Hi mate, I made other test and this is what I understood: the program crashes at start sometimes, but systematically when you point to a screen that was different than the last start.
This problem is present only on this version.

Il giorno 15 mag 2018, alle ore 19:26, Grigory Lobkov<EMAIL_ADDRESS>ha scritto:
Testing OS: Windows 7 Enterprise SP1
C:> ver
Microsoft Windows [Version 6.1.7601]
VLC 2.1.5 fresh installed
Microsoft .NET Framework 4.5
worked fine
Microsoft .NET Framework 4.7 NDP47-KB3186497-x86-x64-AllOS-ENU
worked fine
Please, check files rights, download again, reinstall Framework / VLC, try another OS / another beta.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you for testing.
I tried to add margins on screen size, please, try <IP_ADDRESS> beta with just one parameter screen=0 or screen=1
If it won't help, we will try another solution!

Hi Grigory, unfortunately nothing changed.
At first it seems that worked well, but after some trying of closing and
re-opening, it started to crash.
I think is a problem of my configuration and honestly I tell you to do not
put much effort on this problem at the moment, unless you have identified a
possible cause.
Potentially is only MY problem and changing video drivers or other could
fix the problem, but I haven't found time to do this test.
:-)
2018-05-22 19:30 GMT+02:00 Grigory Lobkov<EMAIL_ADDRESS>
Thank you for testing.
I tried to add margins on screen size, please, try <IP_ADDRESS> beta
https://github.com/grigory-lobkov/rtsp-camera-view/releases/tag/v<IP_ADDRESS>b
with just one parameter screen=0 or screen=1
If it won't help, we will try another solution!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grigory-lobkov/rtsp-camera-view/issues/1#issuecomment-391075319,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkSDEGzR9cDEB9AhKoizq9IEeJjfsLkqks5t1Es8gaJpZM4TFP3H
.

I can't try multi-monitor configuration :(
I will try another solution in next beta(it's commented for now).
What version are you using as a production?

Please, check out crashes and email alerts in new beta <IP_ADDRESS>
... please, open a new Issue, if any ...


macOS inconsistency - Status never returns "stopped"

For Darwin platform service Stop function use the following command:
launchctl unload <plist file path>

To get staus it uses
launchctl list <service name>

This command returns the following:
Could not find service "<service name>" in domain for system

So service Status function returns StatusUnknown event for installed but stopped service.
Result: StatusStopped is never returned.
If service library would use following command to stop the service
launchctl stop <service name>

it would not work as plist file has following key:
<key>KeepAlive</key>
<true/>

So service will restart and service.Stop function will not work.
So service Status/Stop/plist template file should be somehow changed.

Were you ever able to resolve this issue?

No I did not. My project is cross platform and macOS is not highest priority.

https://github.com/tjluoma/launchd-keepalive#keepalive-and-successfulexit


Added support for .NET Standard 2.0

I thought it might be useful to have this in .NET Standard as well, so we can use it in .NET Core projects.
However, @NeilSorensen and I wondered if it might not make sense to make the main Project Pluralsight.Maybe target .NET Standard, and rename the current one that targets .NET Framework 4.6.1 to Pluralsight.Maybe.461.

Let's go ahead and make the Pluralsight.Maybe package .Net standard 2.0 and create the 4.6.1 projects before merging.


Hud Configuration

Description
Base information

Minecraft version: 1.10.2
Minecraft Forge version: forge-1.10.2-<IP_ADDRESS>1
TolkienCraft II version: 0.9.5

vanilla armor bar hides the vanilla health bar in default hud configuration when you are wearing armor

workaround by going into mod options -> RPG-hud -> config -> debug settings -> player armor -> prevent event : ON

Aye, I forgot to add the files RPGHUD uses after I arranged everything in my gui.  Will be included in the next pack update and hopefully by then he will also have the placement piece implemented which will allow me to manually arrange where everything sits in the hud.

Should be fixed next update.


Add check for max mmap size.

The max mmap size was previous unchecked which resulted in a panic once the maximum size was reached. This commit adds a check for the max size when re-mapping and returns an error if the new map will exceed the size.
Note: Exceeding the max size did not cause corruption. It simple caused a panic.
Thanks to Tamás Gulácsi (@tgulacsi) for testing out the change on i386.

Also, note that this change realistically only affects 32-bit machines as the max mmap size on 64-bit machines is 256TB.


Android Basics: ViewModel: Wrong log tag for GameViewModel

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-viewmodel
In which task and step of the codelab can this issue be found?
6. The lifecycle of a ViewModel
Describe the problem
This section asks us to add logs for GameViewModel and GameFragment. However, the part for GameViewModel is:
class GameViewModel : ViewModel() {
   init {
       Log.d("GameFragment", "GameViewModel created!")
   }
   ...
}

The log is written in GameViewModel, but the log tag is GameFragment, which is misleading. Please fix it. Thanks.

@johnlinp
Thank you for reaching out to us.
This is done on purpose to make it easy to filter the messages.


fixing headers in README

Github changed how it's markdown parser handles headers.  It used to accept #SomeHeader but now requires a space, i.e. # SomeHeader.
Updating to the readme to match the new markdown syntax.

@LeeTL1220 This is an easy one here....


operator [O] opendatahub-operator (2.4.0)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
ref https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/3556
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@mporrato / @Allda would like to have some suggestion from you:
in previous 2.4.0 release, it was only published to "fast" channel, but the plan to is to 2.4.0 to both "fast" and "rolling" (rolling was used for v1.X release but we do not plan to have newer than 1.11.0)

@zdtsw this change would break the upgrade graph for the rolling channel because bundle v1.11.0 would be left with no valid upgrade path to 2.4.0.

@zdtsw this change would break the upgrade graph for the rolling channel because bundle v1.11.0 would be left with no valid upgrade path to 2.4.0.

thanks for point this out.
I should have this PR closed, but totally forgot.


Add table with API to MC version mappings

A table should be added with API versions linked to the MC versions that can run them in order to assist ore, and other systems with understanding what game versions plugins support that do not hardcode this information due to factors that limit them to only one version, or a subset of versions of the game.
This will be needed for spongepowered/ore#387

I would love if this could be done sooner rather than later. Something to replace my hand-maintained SpongeAPI <-> MC version mapping API for MCDev: https://github.com/minecraft-dev/minecraftdev.org/blob/master/versions/sponge_v2.json
I'd rather just parse a Sponge-maintained API that is actually kept up to date, as mine frequently falls out of date (which, at the time of me writing this comment, it currently is).

Question: Does API 7 target Minecraft "1.12" or "1.12.2"? The API generally shouldn't change at all for the minor point updates.

API 7 targets 1.12.2, I think 1.12 was originally being targeted but forge very quickly updated to 1.12.2


Travis Notifications

so the success: never function is nice, but the reason we added that was to not get a lot of emails with success status. With the addition of sauce, we have been getting a lot of time outs and failures. I would propose we look into the change option which means that you will get notified when the build status changes. This would effectively only email you once. Could be a nice improvement.
notifications:
  email:
    on_success: change
    on_failure: change

I'm good with that. The emails are not super important to me. I usually track the builds through GitHub anyway.


v9.0.0

This release includes one major change, which is the migration of the CurrencyRateController to the BaseControllerV2 API.

Related product PRs:

https://github.com/MetaMask/metamask-extension/pull/11005
https://github.com/MetaMask/metamask-mobile/pull/2649

A new version of the package @metamask/controllers (9.0.0) was published at 2021-05-19T17:03:36.535Z from
[redacted]. The shasum of this package was b8661f6fad246b20b92f684a63ab268b0e5248a7.


Remove unmaintained Elasticsearch versions

This commit removes formulae for versions of Elasticsearch that are no
longer actively maintained.

I couldn't be happier to see all of these go to the big ol' formula graveyard in the sky, but @mikemcquaid may have comment. He did a big cleanup of Elastic stuff in Versions recently.

I'm :+1: on these being :skull:d (selfishly because we don't use these versions). @DomT4 thoughts on whether these should :skull: or move to homebrew-versions-unsupported? or homebrew-versions-boneyard?

Anything that has an unpatched security hole that has no chance of being patched can :skull: as far as I'm concerned. Anything else can live in homebrew-versions-unsupported, which I'll actually go create shortly.

@DomT4 I guess my thinking is: I'm sure those all have similar security problems, even if we don't know about them.

@DomT4 (which isn't an argument against merging this but I think is perhaps an argument against homebrew-versions-unsupported

Anything that has an unpatched security hole that has no chance of being patched

Versions < 1.6.1 have known issues that will not be patched, and any unknown issues will also not be patched. Only versions 1.7.x, 2.0.x, and 2.1.x are currently being maintained.
That applies to all of the formulas removed in this pull request.

which isn't an argument against merging this but I think is perhaps an argument against homebrew-versions-unsupported

I'm willing to draw a narrow distinction between stuff that has security problems and stuff that has security problems that may be intended to be public facing. I appreciate how narrow a distinction this is.

I'm willing to draw a narrow distinction between stuff that has security problems and stuff that has security problems that may be intended to be public facing. I appreciate how narrow a distinction this is.

That's a reasonable distinction :+1:. We'll be much harsher on servers than libraries/clients. Sounds good.


Add missing migration due to #40

PR #40 modified the eregs_core.DiffNode class to be a proxy model, which required a new migration. This change adds that missing migration, which effectively deletes and recreates the table for that model. This will result in deleting existing DiffNode content in your DB.
Additions

Adds missing migration eregs_core.0012.

Testing

Run all migrations backwards and forwards:

$ ./manage.py migrate eregs_core
$ ./manage.py migrate eregs_core zero
$ ./manage.py migrate eregs_core

Confirm that no new migrations are needed:

$ ./manage.py makemigrations
No changes detected

Notes

@grapesmoker before this app goes live it'd be good to wipe out and recreate migrations from scratch. Unless you disagree I don't think this history really serves any useful purpose.
@willbarton I was considering copying over the "detect missing migrations" test from cfgov-refresh but wasn't sure if there was an easier way to duplicate. Do you think that might make a nice PyPI package somehow?

Checklist

[X] Changes are limited to a single goal (no scope creep)
[X] Code can be automatically merged (no conflicts)
[X] Code follows the standards laid out in the front end playbook
[X] Passes all existing automated tests

Hey, so, I am working on something regarding this. The basic thing about this is that actually DiffNode no longer has any purpose and should be removed entirely. I'm going through the code right now to eliminate all appearances of DiffNode. Originally, what happened was that version was just another column, not an entirely separate table connected to RegNode by a foreign key relation. But unfortunately this caused too many performance problems, so I broke the version information out into a separate model. DiffNode used to express the same semantics that are now expressed by the left_version and right_version columns of the eregs_core_version table, so we actually don't need it anymore. Because of this, I'm not going to merge this PR, since the work I'm doing right now will obviate the need for such a migration.

Sounds good, presumably that'll also include removing the migrations that refer to that table?

@willbarton I was considering copying over the "detect missing migrations" test from cfgov-refresh but wasn't sure if there was an easier way to duplicate. Do you think that might make a nice PyPI package somehow?

😍
Yes, yes I do.

Yes, the code from the migrations will also be removed.


React SSR package release workflow and plan

📇 User story

As a gcds developer, I want to have a release plan for the react ssr package, so that I have better monitoring and control over the process.

✅ Definition of Done / Outcomes

[ ] #971
[ ] Production or stable release plan is documented
[ ] Canary release plan is documented
[ ] A ticket and user story for releasing the new react-ssr package

📜 Acceptance criteria

[ ] Release plan is reviewed and approved by devs or as needed

📝 More info
🚫 Out of scope
This ticket is not about the release, but the preparation for it.

Release plan documentation can be found here: https://docs.google.com/document/d/14TwlBuSd01zNkF7srl8cL1KWP0dlMvWEiDZlrbY0F6c/edit


[kie-issues#624] Fix coercing double type in Mvel compiler (#5550)

(cherry picked from commit 67b5880df93aef6847bd1db92dd519b850180b66)
Backport of https://github.com/apache/incubator-kie-drools/pull/5550

lgtm


fix: update error string format

Checklist

[ ] Readme updated
[ ] Tests added and passing

Fixes #42


Configure tests

This project contains just a simple plugin, but in order to test it, it's necessary to bootstrap and configure an entire Laravel instance with an installation of Spatie Media Library. The only reason this is needed is because the FFmpeg instance the plugin uses needs to know the paths to the ffmpeg and ffprobe binaries, and these are obtained from the ML config, and access to that config is handled via Laravel's config helper function, which can't work unless there is an app instance, and so on, until you have a fully shaved yak.
The tests are very simple, but they have huge config implications, and I'm just not sure where to start.

You should require-dev the orchestra testbench and the base medialibrary package.
I will see if I can PR something.


SLIM-568 Synchronize Time with device timezone

 You should sign our Contributor License Agreement in order to get your pull request merged.

This pull request makes the build fail.


Add jdbc data access layer interface

Add jdbc data access layer interface.
In nowaday dss system, we need impletment singleton DAO(data access object) and call it in service actor.
It is so inefficient that add a data acess layer interface and user implement it, at last we run the data access actor in the background can work greate.

{
  "name":"hi"
}

interface DataAccessService

@LeeJuHyun

@JuHyun419
Hi there,
Is it on process?
If not i wanna unassign this one.

ok~ I got it.


Move most builds to ubuntu-20

Fixes #1252

I don't really track the linux side of things, so I'm not completely sure when's is the right time, but seems like the 20.04 images have been around for a while, so maybe it's time?  Thoughts?

Sounds good.  Landing.


Modified torch-sys build to fix usage for Cuda 9.2 and 10.1

I modified the download for the linux to work properly with Cuda 9.2 and 10.1. I got the links from https://pytorch.org/get-started/locally/ on 16th October 2019.

It seems the AppVeyor failed due to it taking too long. Is that an issue I need to worry about with this PR?

Looks good, thanks for the PR!


Fix ES signature serialization

The current signature serialization is not correct, it doesn't conform to the RFC nor what the other implementations do.
This makes jwt-go unable to interoperate with ES keys entirely.
NOTE: This is a breaking change. Any JWTs created before this change no longer validate. Similarly no JWTs created after this change will validate with older repos.

Sorry to add an unhelpful +1, but this blocks us using this library as we need to interop with a bunch of ruby and javascript.


Role service local config

Local config to enable a developer to run role-service locally without a config server or dependency on the mts-trial-deployment-config repo
Checklist:

[x] Branch name follows convention (feature/arts-#-short-name OR fix/arts-#-short-name)
[x] I have included a short-meaningful title, description and changes for this PR

We seem to have lost application-local.yml - I think Tamir may have removed it - I think I added a comment to his review...anyhow, if application-local.yml is in the resources folder bootstrap will pick up the liquibase properties.

Thanks Darren, do you mean this config should go in an application-local.yml rather than bootstrap-local.yml?