one channel CT channel reading differently

I am using the example ESPhome config and noticed that one CT channel reacted very differently to my large (supposedly) balanced 240V EVSE load. Fhase C reacts, but with much lower absolute reading.
I swapped the CT inputs and I got the similar channel readings which should eliminate the CT or the load as a cause.
I switched in a v1.4 rev3 board and am getting similar magnitude of readings from both channels (but with very off calibration).
Now that I bothered to type all this out, I think my issue might be that I failed to sufficiently sever the burden resistor jumper on CT2 channel because my CTs have built in burden resistors. Will report back after investigation.

I have spent considerable time trying to debug this issue myself and do not have a solution yet. I suspect a software issue may be at play, because I am able to calibrate the CTs I am using to reflect current fairly accurately.
The CTs I am using are 200A/50mA Current Transformer YHDC SCT-024 – 24mm Opening as sold on CircuitSetup's website here. Per your concern about burden resistors, I am not aware that these CTs have them (it is not mentioned in the documentation nor on CircuitSetup's storefront). For reference, the current calibration value I ended up computing based on Kill-a-Watt measurements with a resistive load is 49712.
Similar to the original post, I am seeing that one of the phases has a much lower computed Watts reading even though the current scales roughly as expected when I apply a resistive load. I can swap the CT inputs on the meter board and have the same behavior reproduce on the other channel. And I previously swapped the two CTs on the mains lines and think the behavior didn't follow the CT; it seems to follow the phase in the breaker box.
I'm not sure if this is a software problem or perhaps an issue with my installation. OP, please reply back if you discover that burden resistors were the culprit!

@chaseadam were you able to resolve this by severing the burden resistor?
@MaiaBlanco can you confirm that the CTs are installed on your mains like this?

I confirmed that my current clamps are installed on the mains as shown, yes. The first channel (CT1) is in stalled on the hot line that feeds the same breaker that the voltage monitoring is connected to. The direction (arrow) on the clamp points into the breakers. The second current clamp (CT2) is on the other hot line, pointing opposite to the first.
I think I had a reversed setup before, where the directions of both clamps were reversed from the above, because now I observe negative values reported in the interface for power factor and voltage. Reactive power is being reported as a positive value.
My problem still persists: on the second phase which is monitored by CT2, when I apply a water kettle as a load, the reported wattage is significantly lower than it actually is. For reference, I have checked and recalibrated both clamps individually with a clamp-style multimeter on each hot line, and the reported current values are correct. It's the wattage that is wrong, and only for the CT2 (second phase) channel. The magnitude of the discrepancy is almost 2x: I see an increase of ~512 watts (magnitude, since the values are being reported negative now) through CT2 while I see ~950 watts in the kill-a-watt meter I have on the kettle itself. There are no other loads turning on or off while I run this tests.

@MaiaBlanco If you're seeing negative values anywhere that usually means something is reversed. This is going to sound silly, but turn around the voltage transformer in the socket.
I bet you're seeing low wattage values because the meter is calculating power factor out of phase.
If this doesn't fix the issue, please supply your config file.

That makes sense wrt to negative values! Unfortunately, while the wattage values are no longer negative, the second current sensor is still far off on absolute wattage. I also note that while the power factor on the first current meter reaches 1 when I apply a large resistive load (and correctly reports wattage), the second current channel tops out at a power factor of 0.5 and reports roughly half of the wattage it should, as o described earlier.

Here is my config (minus wifi and other ESPhome boilerplate:
`substitutions:
Change the disp_name to something you want
disp_name: EMON
Interval of how often the power is updated
update_time: 1s
web_server:
port: 80
spi:
clk_pin: 18
miso_pin: 19
mosi_pin: 23
sensor:

platform: wifi_signal
name: ${disp_name} WiFi Signal
update_interval: 60s
platform: atm90e32
cs_pin: 5
current_phases: 2
phase_a:
voltage:
name: ${disp_name} Volts
accuracy_decimals: 1
current:
name: ${disp_name} CT1 Amps
id: "ct1Amps"
power:
name: ${disp_name} CT1 Watts
accuracy_decimals: 1
id: "ct1Watts"
# filters:

I don't know why but this one is always really off, even though the current measures correctly??
      # - multiply: 1.173
  reactive_power:
    name: "Reactive Power CT1"
    # filters:
    # I don't know why but this one is always really off, even though the current measures correctly??
    #   - multiply: 1.173
  power_factor:
    name: "Power Factor CT1"
    # filters:
    # I don't know why but this one is always really off, even though the current measures correctly??
    #   - multiply: 1.173

Voltage using a 9VAC power transformer
  gain_voltage: 3920
  gain_ct: 51074
phase_c:
  current:
    name: ${disp_name} CT2 Amps
    id: "ct2Amps"
  power:
    name: ${disp_name} CT2 Watts
    accuracy_decimals: 1
    id: "ct2Watts"

If the wattage is backwards due to the phase 180 degrees from the clamp direction
    # filters:
    #   - multiply: 1.0
  reactive_power:
    name: "Reactive Power CT2"
    # filters:
    #   - multiply: -1.0
  power_factor:
    name: "Power Factor CT2"
  gain_voltage: 3920
  gain_ct: 48845
frequency:
  name: ${disp_name} Freq
line_frequency: 60Hz
gain_pga: 2X
update_interval: ${update_time}

platform: template
name: ${disp_name} Total Amps
id: "totalAmps"
lambda: return id(ct1Amps).state + id(ct2Amps).state;
accuracy_decimals: 2
unit_of_measurement: A
update_interval: ${update_time}
icon: "mdi:flash-circle"

platform: template
name: ${disp_name} Total Watts
id: "totalWatts"
lambda: return id(ct1Watts).state + id(ct2Watts).state;
accuracy_decimals: 0
unit_of_measurement: W
icon: "mdi:flash-circle"
update_interval: ${update_time}

platform: total_daily_energy
name: ${disp_name} Total kWh
power_id: totalWatts
filters:

multiply: 0.001
unit_of_measurement: kWh

time:

platform: sntp
id: sntp_time

switch:

platform: restart
name: ${disp_name} Restart`

Okay, so everything is positive now? If so, what happens when you switch the CT inputs on the meter, and turn around the voltage transformer at the same time? Is CT1 now reading too low? If so, there is something up with the CT - it's either broken somehow, or is too loose/not closed all the way on the wire.
If not, then there is something wrong with the meter (likely a cold solder joint), and I'll send you a replacement.
I don't see anything wrong with your config, btw.

I switched the CT inputs on the meter, turned the voltage meter around, and got both negative wattage values AND incorrect wattage readings on CT1 (where previously they were on channel 2)

But, I’m confused, because the current values are correct. It’s just all the other values computed that seem incorrect. I know this because I calibrated both CTs independently using a resistive load and a current clamp multimeter. How can the current values be reported accurately but the wattage is consistently wrong for one of the current clamps?

Could the calculation be wrong because it’s the second phase, and not the clamp? I’ll try swapping the clamps to the other phases and see if the issue follows the phase in the breaker box or if it follows the clamp.

Update: I have swapped the current clamps between mains lines and between channels, such that the same channel on the PCB is monitoring the same mains line but with the other current clamp. I still see the discrepancy in which the second current monitoring channel under-reports wattage, but NOT current. This is starting to seem more and more like a software bug. Any thoughts?

Update: I have swapped the current clamps between mains lines and between channels, such that the same channel on the PCB is monitoring the same mains line but with the other current clamp. I still see the discrepancy in which the second current monitoring channel under-reports wattage, but NOT current. This is starting to seem more and more like a software bug. Any thoughts?

So the issue followed the meter channel, not the phase in your box, correct? If that's the case, I'll send a new meter for you to test. Can you provide your order number?

Update: I have swapped the current clamps between mains lines and between channels, such that the same channel on the PCB is monitoring the same mains line but with the other current clamp. I still see the discrepancy in which the second current monitoring channel under-reports wattage, but NOT current. This is starting to seem more and more like a software bug. Any thoughts?

So the issue followed the meter channel, not the phase in your box, correct? If that's the case, I'll send a new meter for you to test. Can you provide your order number?

No, the issue seems to have followed the phase in the box. It does not follow the meter channel, nor does it follow the current transformer clamp. The only factor I have not tested independently is putting the voltage measurement on the same phase that is giving bad wattage but not current readings. I will try this now.

So it seems that whichever phase does NOT have the voltage reading, does not report watttage correctly. It doesn’t matter which current clamp or which channel on the meter board is monitoring which phase. It’s just, whichever phase is not the same one the voltage transformer is connected to, this phase gives incorrect wattage readings.

Perhaps there is something wrong with the board, but it’s not the current sensing but the voltage sensing for channel 2? (Note: my configuration has just one voltage input for both phases).

Ohh okay!
So, the thing that is bringing down the wattage for CT2 (or phase 2), is the power factor. If the voltage were exactly 180 degrees out of phase with the 1st phase, and you only had resistive loads, the PF would be 1.
The calculations for wattage, (V * I) * PF, is done on the metering chip, and cannot be adjusted except by using the gain and calibration values.
It's possible that something is wrong with a circuit on phase 2, or the transformer feeding your house is failing.
The meter, by default, reads 1 voltage equally, assuming there is nothing wrong with the resistors going into that voltage channel. In this case, a defect with the meter is still possible.
Turning the voltage transformer around on a phase 1 circuit will reverse the polarity 180 degrees. If phase 2 is still reading wrong after turning it around, then it is not 180 degrees out of phase with phase 1 as it should be. If you were to measure the voltage from a phase 2 circuit, then phase 1 wattage would likely appear incorrect (assuming there is nothing wrong with the meter like mentioned above).

the voltage sensing for channel 2?

Thinking about this some more... what is the output of voltage 2 (phase c in the config) from the meter? If it's reading about the same as voltage 1 (phase a in the config), then the problem can't be with the meter.

I changed my settings to also dump the second voltage channel and it is indeed reading identically to the first. So this likely rules out the meter being defective, in addition to ruling out the current clamps as before.
I have a feeling you may be right; the two phases may not properly be out of phase (180 degrees apart). I’m going to have to figure out a way to measure this.
If I measure the AC voltage between the two hot lines, shouldn’t that give me a sense of their phase? If they are perfectly opposed I should see 120v x 2 peak to peak, and I should see less if the phase angle is anything else.
Also no, I do not observe lights flickering when a large load is applied. But I’ll keep in mind to investigate if anything else is wrong with my supply side.

Okay, I don’t recall if the multimeter will report peak to peak or RMS…probably RMS. In any case, I measure about 120v on each separate phase, and across both I see ~213v. Clearly not adding up.

Thanks for checking! That does rule out the meter being defective.

In any case, I measure about 120v on each separate phase, and across both I see ~213v.

This would make sense if you actually have 2 phases of a 3 phase wye configuration. Each phase is 120V out of phase from eachother. Are you in an apartment or single home?

It’s been a hot minute since EE coursework, but I think that I should be able to compute the relative phase offset of the two hot phases by using the RMS measurements I posted above.
123v+cos(theta) + 123v = 213.5v 1+cos(theta) = 1.73577 cos(theta) = 1.73577 theta = cos^-1(0.73577) theta = 42.6 degrees (or 0.744 radians)

I am in an apartment, so maybe I am getting 2 of three phases. Did I measure something incorrectly or do the wrong math above?

So, how should the meter be configured when a home is getting 2 of three phases? Is a second voltage reading required or is there a configuration I can change?

I am in an apartment, so maybe I am getting 2 of three phases. Did I measure something incorrectly or do the wrong math above?
Edit: well a quick google search confirms that it’s probably three phase power and that I should be seeing approximately 1.73x the voltage across two phases versus measuring on one. Time to study back up…

Yep! That makes sense!

So, how should the meter be configured when a home is getting 2 of three phases? Is a second voltage reading required or is there a configuration I can change?

There are 2 solutions here:

Use a 2nd voltage transformer to measure the 2nd phase & cut the voltage jumpers on the back of the meter
In the config, calculate the watts using lambda, using the voltage and PF from phase 1 (this will be slightly less accurate, but still very close to actual):
Make sure to give voltage and power factor an id:
     voltage:     name: ${disp_name} Volts     id: "p1Volts"     accuracy_decimals: 1     unit_of_measurement: V     device_class: voltage
     power_factor:     name: ${disp_name} CT1 Power Factor     id: "ct1PF"     device_class: power_factor

Then the template to calculate everything:
 - platform: template     name: ${disp_name} CT2 Watts     id: ct2Watts     lambda: return (id(ct2Amps).state * id(p1Volts).state) * id(ct1PF).state;     accuracy_decimals: 0     unit_of_measurement: W     device_class: power     update_interval: ${update_time}

Thanks for all your help debugging! I hope the original poster was able to resolve the initial issue. I will add a second voltage transformer to my setup and see how that goes.

To close the loop for my original issue: I had scraped the jumper off, but I guess not well enough. It tested as shorted, so I re-scraped it and removed the burden resistor. Everything is back to normal for me.
@MaiaBlanco I appreciate the discussion as being related. Glad you got to the conclusion of the phase shift being the issue. I may consider another voltage transformer as well for more accuracy even though I have split phase.
@CircuitSetup as always, thanks for chiming in with the great detailed guidance.
Preview for the next issue: Debugging ESPHome on an ESP32C3-mini dev board that is locking up a few times per day at exactly 26 minutes and 21-28 seconds past the hour...


Custom Icon Path not working for me

Describe the bug
Use Local icons custom path as my kiosk has no internet access.
Tried following paths in the custom icon path field on the card
/local/weather-icons/
local/weather-icons/
/local/weather-icons/icons2
local/weather-icons/icons2
/local/my-weather-icons/
Icons are named exactly the same as your hosted versions and as per the documentation.
Also followed someone having the same issue here, no luck https://community.home-assistant.io/t/lovelace-weather-chart-card/638917
To Reproduce
Add the icons to a folder, put that in the cards custom icon path field
The card just carries on using the hosted cdn versions of the icons
Expected behavior
Expect the icons to be from the folder I pointed to, not the hosted CDN versions
Desktop (please complete the following information):

WEATHER-CHART-CARD VERSION - 2.4.2
HOME ASSISTANT VERSION AND INSTALLATION - 2024.3.0
OS: HA OS 12.0
Browser: ALL

Update: It works if you turn Animated Icons to OFF


Use NS_EXTENSION_UNAVAILABLE_IOS instead of PIN_APP_EXTENSIONS

NS_EXTENSION_UNAVAILABLE_IOS can be used to mark symbols as unavailable to extensions. This should allow us to remove the PIN_APP_EXTENSIONS define and produce one library for both application and extensions.
Inspired by AFNetworking/AFNetworking#2737. Depends on pinterest/PINCache#37.

I created a pull request for this with the changes. Am I doing it right?

I actually think this was done incorrectly, the macro is meant to mark api's as unavailable to extensions. I think I need to revert the commit and investigate if this is even possible.

From my understanding, NS_EXTENSION_UNAVAILABLE_IOS will only allow us to mark methods as unavailable for use in extensions, it won't allow us to compile separate code paths. So I'm not sure it will actually add value? :(

From the documentation
Use any API marked in header files with the NS_EXTENSION_UNAVAILABLE macro, or similar unavailability macro, or any API in an unavailable framework
So you can explicit flag a method as unavailable in an extension. I don't know if there is a real impact on the code paths.
Idea

Different APIs for extension / app, the one for the app marked as NS_EXTENSION_UNAVAILABLE_IOS
Same API and under the hood two private methods that are switching with canPerformSelector in the hope NS_EXTENSION_UNAVAILABLE_IOS is handling this way
revert the commit and go back to the good old PIN_APP_EXTENSIONS. IMHO it's so last favorite way because each pod is using a different name here :(

Use this method to get UIApplication:
/// Returns nil in App Extension.
static UIApplication *_YYSharedApplication() {
    static BOOL isAppExtension = NO;
    static dispatch_once_t onceToken;
    dispatch_once(&onceToken, ^{
        Class cls = NSClassFromString(@"UIApplication");
        if(!cls || ![cls respondsToSelector:@selector(sharedApplication)]) isAppExtension = YES;
        if ([[[NSBundle mainBundle] bundlePath]<EMAIL_ADDRESS>isAppExtension = YES;
    });
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wundeclared-selector"
    return isAppExtension ? nil : [UIApplication performSelector:@selector(sharedApplication)];
#pragma clang diagnostic pop
}

and then use NS_EXTENSION_UNAVAILABLE_IOS  to mark the API.
See my example: https://github.com/ibireme/YYWebImage/blob/master/YYWebImage/YYWebImageManager.m

@mRs-

Is possible, though I'd only be in support of this if it were only a couple of methods we could mark this way. I think we could possibly get away with it, but it wouldn't be very clean.

I don't think it works that way. I'm 90% sure that NS_EXTENSION_UNAVAILABLE_IOS is just an indicator to the compiler to mark a method as unavailable. I don't think it changes anything at runtime nor compiles anything differently.

I think this is our best option at the time. I'd be very supportive of getting rid of it, but I think the above solutions create more cost. I could be wrong though and would be happy to merge in something that isn't too complex and has been thoroughly tested.

I'm going to close this for now as I don't think there's a good solution available.


didn't notice this before. But even the workspace folder have permission issues

    didn't notice this before. But even the workspace folder have permission issues

@snebjorn ➜ /workspaces/openapi-generator (feature/devcontainer ✗) $ ls
ls: cannot access 'Vagrantfile': Operation not permitted
ls: cannot access 'docs': Operation not permitted
ls: cannot access 'samples': Operation not permitted
ls: cannot access 'bin': Operation not permitted
ls: cannot access 'CODE_OF_CONDUCT.md': Operation not permitted
ls: cannot access 'new.sh': Operation not permitted
ls: cannot access 'docker-compose.yml': Operation not permitted
ls: cannot access 'scripts': Operation not permitted
ls: cannot access 'LICENSE': Operation not permitted
ls: cannot access 'appveyor.yml': Operation not permitted
ls: cannot access 'modules': Operation not permitted
ls: cannot access 'README.md': Operation not permitted
ls: cannot access 'CONTRIBUTING.md': Operation not permitted
ls: cannot access 'google_checkstyle.xml': Operation not permitted
ls: cannot access 'spotbugs-exclude.xml': Operation not permitted
ls: cannot access 'docker-entrypoint.sh': Operation not permitted
ls: cannot access 'bitrise.yml': Operation not permitted
ls: cannot access 'mvnw': Operation not permitted
ls: cannot access 'website': Operation not permitted
ls: cannot access 'sec.gpg.enc': Operation not permitted
ls: cannot access 'shippable.yml': Operation not permitted
ls: cannot access 'openapi-generator.code-workspace': Operation not permitted
ls: cannot access 'CI': Operation not permitted
ls: cannot access 'pom.xml': Operation not permitted
ls: cannot access 'mvnw.cmd': Operation not permitted
ls: cannot access 'run-in-docker.sh': Operation not permitted
ls: cannot access 'Dockerfile': Operation not permitted
appveyor.yml  bitrise.yml  CODE_OF_CONDUCT.md  docker-compose.yml    Dockerfile  google_checkstyle.xml  modules  mvnw.cmd  openapi-generator.code-workspace  README.md         samples  sec.gpg.enc    spotbugs-exclude.xml  website
bin           CI           CONTRIBUTING.md     docker-entrypoint.sh  docs        LICENSE                mvnw     new.sh    pom.xml                           run-in-docker.sh  scripts  shippable.yml  Vagrantfile
@snebjorn ➜ /workspaces/openapi-generator (feature/devcontainer ✗) $ whoami
vscode
@snebjorn ➜ /workspaces/openapi-generator (feature/devcontainer ✗) $

Originally posted by @snebjorn in https://github.com/devcontainers/images/issues/155#issuecomment-1272512525

It seems this is a subset / duplicate of another issue. But if I'm missing something, please let me know. Thanks!


Can I install a old version of npm from registry.npmjs.org?

I just found out that npm 0.2.8 and 0.2.10 series has been removed from registry.npmjs.org.
Right now the latest version is 0.2.14.
What if I want to install 0.2.8 at this point of time? and What is the oldest version of npm that can been installed?

@neurofen You can also just set the npm_install environment variable when the script is run.


is there a way to ensure csv in input.yaml is read by multiple executors?

in input.yaml we can define source files ie abc.csv that get loaded into a dataframe. If this is a big file like 300GB will it be read all on a single executor? or is there a way to set shuffle/partitions.etc

If you have only a single 300GB file that you load in metorikku you can set up first a step in the metric file that uses DISTRIBUTE BY or CLSUTER BY.
Check out the documentation here:
https://docs.databricks.com/spark/latest/spark-sql/language-manual/select.html


Add testing pipeline on GitHub

Goal
As a developer, I want to automate the testing of the code on GitHub to make sure that the code coverage stays greater than 97% without the need for manual testing.
Tasks

[ ] read https://medium.com/thelorry-product-tech-data/unit-testing-and-continues-integration-ci-in-github-action-for-python-programming-c8ad57fae3a1 (free article)

Closed because completion on time is not realistic.


Mqtt command back to wallpanel app

Hello :)
I need help from mqtt. After ringing my doorbell, wallpanel opens the Reolink application. I would need an mqtt command to close reolink application or re-open the wallpanel application with a mqtt command.
This command for reolink application
service: mqtt.publish
data:
  topic: wallpanel/mywallpanel/command
  payload: '{"url": "intent:#Intent;launchFlags=0x10000000;component=com.mcu.reolink/com.android.bc.login.WelcomeActivity;end"}'

You can use the Relaunch command
See description.
https://github.com/thecowan/wallpanel-android/wiki/MQTT-and-HTTP-Commands
{"relaunch": true} --> Relaunches the dashboard from configured launchUrl

See #341

@ice2009 - did you ever got this working?  Using the Relaunch command over MQTT doesn't close the Reolink app.  I would like to make a script which after x-minutes sends an MQTT command to wallpanel to return to "the wallpanel app".

Back to the wall app not working for me. I use wallpaper app to default launcher on android settings and after i use tasker for back home after 90 seconds


expr/builtin_fncall: implement Inet6Aton

Signed-off-by: sweetIan<EMAIL_ADDRESS>What have you changed? (mandatory)
expr/builtin_fncall: implement Inet6Aton
What are the type of the changes? (mandatory)

New feature (non-breaking change which adds functionality)

How has this PR been tested? (mandatory)
unit test
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
no
Does this PR affect tidb-ansible update? (mandatory)
no
Refer to a related PR or issue link (optional)
#3275

LGTM.


Modify Chrome plugin FDB to run it tests on local servers

Chrome plugin integration tests often failed because of publishing to GithHub pages takes from several seconds to 60 and more minutes. (I measured the time between pushing to kogito-online-ci and getting http 200 on https://kiegroup.github.io/kogito-online-ci/pull/{build.nuber}/# and I got almost 2 hours  ) We cannot afford wait that amount of time in the CI. Chrome plugin tests have to be run on local servers.

@tiagobento could you please take a look?

I am thinking how to test the FDB and I have two options:

rebuild the kogito-tooling repo after all steps by build:fast step and run the it tests
build the appformer, kie-wb-common, ... inside the Run integration tests goal. (Maybe the better way as we probably split all the it test for channel to separate ci goals)

@tiagobento @jstastny-cz WDYT

Hi @tomasdavidorg! Do we depend on the online resources we have on the Kogito Online CI repo?

@tiagobento Kogito tooling is built in FDB with
ROUTER_targetOrigin: "https://kiegroup.github.io"
ROUTER_relativePath: "kogito-online-ci/${{ steps.buildInfo.outputs.category }}/${{ steps.buildInfo.outputs.id }}/editors/"

@tomasdavidorg Hmm..... that makes total sense. I believe the best option would be exactly what you suggested. Rebuild the chrome-extension-pack-kogito-kie-editors with URLs pointing to a local webserver. You can do the exact same thing we do on the "Run integration tests" job.

@tiagobento Ok. I will update this PR and let you know when it is ready.

@tiagobento I updated the configuration. Please take a look. The change will not be visible in the current FDB.


Automation tests for keras grpc model for triton

Add support for trition server for keras model format using kserve using gRPC endpoint RHOAIENG-11563

Verified with Jenkins Build 554


Add quickwit-cluster package

Context / purpose
Add a new package for quickwit server implementation (quickwit-cluster) package.
Description
See https://github.com/quickwit-inc/quickwit/issues/141
How was this PR tested?
Describe how you tested this PR.
Checklist
Remove or complete this list if required.

[ ] tested locally
[ ] added unit tests
[ ] included documentation

@fulmicoton
I moved search-service, client, and client-pool to quickwit-search package.
Please see: https://github.com/quickwit-inc/quickwit/pull/143/commits/16f848c7b3627d362adbd5364db85a4954843d63

@fulmicoton Thanks!


Link to GitHub fork docs from the main README

The README stresses that this repo is intended for forks, but GitHub newbies
may have no idea what these are about, so we link to the official docs!

Hey Brigitte!
Nice improvement, thanks!


Update dependencies, translations; add Catalan

Replaced manual HTTP calls to the defunct Transifex API v2 with the Transifex API v3 JavaScript SDK. This required increasing the minimum Node version from 8 to 16 and rewriting the transifex.js script to use async/await and promises.
Added a complete Catalan localization from Transifex. Reran npm run transifex to synchronize this repository with Transifex for the first time since December 2019. I kept various pre-translations where an English string would otherwise have been backfilled. Thanks to the following translators for their help over the past four years or so, and apologies for the delay in pulling in the changes:

@eduardoaddad for Brazilian Portuguese
@rroset for Catalan
@cmahopper for Danish
arjanTransfix for Dutch
@verdulo for Esperanto
@operon for French
@debyos for Hungarian
nob.nihashi for Japanese
rafal.ferenc.broomee for Polish
@yuryleb for Russian
@chriswu42 for Simplified Chinese
@riiga for Swedish
@andygol for Ukrainian
@toblinkz for Yoruba

Fixes #310 and fixes #311. Supersedes #292, #297, #306, and #307.

Are you going to release v0.15.0?

Sure, if I can still figure out how to work this thing.

Tracking the release in #313.


Error declaring input for NN engine.

Hi,
I've converted my TF model to CoreML using the package. The conversion went well, but when I try to load the model, I receive "Error declaring input for NN engine.". The python side is able to parse the model file correctly, but the native side is unable to load it.
Does anyone know what might be causing it?
Thanks!
Vlad

Maybe the input size was incorrectly set?
What is the input size in the .mlmodel and what sized MultiArray did you pass at runtime?
If you can share the model (or an equivalent smaller version that displays the issue), it would be easy to debug.

Thanks! The engine fails long before trying to run inference, the engine can't even load the converted model.
I've attached the model. The conversion is run using:
import tfcoreml as tf_converter
coreml_model = tf_converter.convert(tf_model_path = 'epsilon.tf',
mlmodel_path = 'output.mlmodel',
output_feature_names = ['action:0'],
input_name_shape_dict = {'vector_observation:0' : [1,8], 'epsilon:0' : [1,2]})
epsilon.tf.zip

I put up PR #239 that should fix this issue. Please try again using that branch.
Btw, since in this model there are many other outputs which are not used, it is a good idea (although not required for this model) to simplify the TF model prior to conversion, using code similar to here.
In particular, something like this:
tf_model_path = 'models/Debug/model_issue_238.pb'
with open(tf_model_path, 'rb') as f:
    serialized = f.read()
tf.reset_default_graph()
original_gdef = tf.GraphDef()
original_gdef.ParseFromString(serialized)

with tf.Graph().as_default() as g:
    tf.import_graph_def(original_gdef, name='')

# Strip unused subgraphs and save it as another frozen TF model
from tensorflow.python.tools import strip_unused_lib
from tensorflow.python.framework import dtypes
from tensorflow.python.platform import gfile
input_node_names = ['vector_observation']
output_node_names = ['action']
gdef = strip_unused_lib.strip_unused(
    input_graph_def=original_gdef,
    input_node_names=input_node_names,
    output_node_names=output_node_names,
    placeholder_type_enum=dtypes.float32.as_datatype_enum)
# Save the feature extractor to an output file
frozen_model_file = 'models/Debug/model_issue_238_modified_graph.pb'
with gfile.GFile(frozen_model_file, "wb") as f:
    f.write(gdef.SerializeToString())

Confirming the fix. Thanks a lot!
Yes, we usually cut down the unneeded branches.


all[patch]: Add homepage to package.json for proper readmes

This allows each NPM package displayed readme to match the readme of that specific package
Tested with weaviate here
cc @jacoblee93 incase adding this has unwanted side effects?

I think fine, thanks!


awaiting finalization markets need to show under resolved in portfolio and account

Prob nust need to add awaiting_finalized to same conditional as check for finalized


Allow configuration of template, magic comment and titles

See also #35

[Current coverage][cc-pull] is 71.87%

Merging [#36][cc-pull] into [master][cc-base-branch] will increase coverage by -<.01%

@@           master        #36   diff @@
========================================
  Files          11         11
  Lines         313        327    +14
  Methods         0          0
  Branches       39         40     +1
========================================
+ Hits          225        235    +10
- Misses         79         83     +4
  Partials        9          9

Powered by Codecov. Last updated by [a6f5504...20613d2][cc-compare]
[cc-base-branch]: https://codecov.io/gh/hawkowl/towncrier/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/hawkowl/towncrier/compare/a6f5504a3e6bb8327a75dbe0ae7b120f79d43126...20613d2b90654983c9d0004bd763af4eb7dac8e9
[cc-pull]: https://codecov.io/gh/hawkowl/towncrier/pull/36?src=pr

Hi @meejah , thanks! I've added a comment, and the flake8 fails, so I'm happy to merge when that's cleared up. I'm also guessing you want to add to LICENSE :)

Hmm, should I do the "err=True" changes in a separate PR? (Thinking there is so you can redirect towncrier --draft output to a file, and not capture the "This is only a draft" lines...)

@meejah are you going to move forward on this?
I'm moving buildbot to towncrier, and the default template currently generates spelling errors.
I would wait until #41 lands, and then implement template in the toml (maybe even inline it).

Hi @tardyp thanks for the nudge! This had rolled off my radar but looks useful for sure. I think I was exploring this for building release-notes for txtorcon ... I'll rebase and fix flake8

Okay, @hawkowl it looks like you already fixed the thing you commented upon. I rebased this and force-pushed it with a flake8 fix.

Seems reasonable. I'll update #41 to have the new config options (@dstufft is testing it when they get time).


Adding inf2 and trn1n instances

Issue #, if available:
Adding support for inf2 and trn1n instances
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing Done
Spun up a new self managed ng on the AMI and it came up fine

See this guide for recommended testing for PRs. Some tests may not apply. Completing tests and providing additional validation steps are not required, but it is recommended and may reduce review time and time to merge.

Can you confirm that trn1n.32xlarge is the only trn1n instance we are supporting?

Yes. This is the only instance. See .


Add an editor setting to invert 3D pan/orbit on the X axis

This also makes the invert Y axis option apply to 3D panning.
This closes #28082.

@molevision If you can build this from source, can you test this please?

@Calinou Tested, works as desired now. Thank you.

Thanks!

Cherry-picked for 3.2.3.


x/vgo: support gopkg.in major versions properly

What version of Go are you using (go version)?
go version devel +104445e Wed Feb 7 19:22:09 2018 +0000 linux/amd64 vgo:2018-02-20.1
What did you do?
% cat go.mod
module "github.com/rogpeppe/xx"

require "gopkg.in/yaml.v2" v2.1.0
% vgo build
vgo: errors parsing go.mod:
/tmp/xx/go.mod:3: invalid module: gopkg.in/yaml.v2 should be v1, not v2 (v2.1.0)

If I change the module name in the requirements to "gopkg.in/yaml/v2", I see this output:
% vgo build
vgo: finding gopkg.in/yaml/v2 v2.1.0
vgo: gopkg.in/yaml/v2: invalid gopkg.in/ path: "gopkg.in/yaml/v2"
vgo: finding gopkg.in/yaml/v2 v2.1.0
vgo: gopkg.in/yaml/v2: invalid gopkg.in/ path: "gopkg.in/yaml/v2"
vgo: invalid gopkg.in/ path: "gopkg.in/yaml/v2"

OK, I see what's happening now. It's not grokking the major-version-in-path of gopkg.in.
As an example, if I run vgo build on this program:
package main // import "github.com/rogpeppe/xx"

import (
	_ "gopkg.in/juju/charm.v4"
	_ "gopkg.in/juju/charm.v5"
	_ "gopkg.in/juju/charm.v6"
)

func main() {
}

I get this go.mod file:
module "github.com/rogpeppe/xx"

require (
	"github.com/juju/names" v0.0.0-20180129205841-f9b5b8b7614d
	"gopkg.in/juju/charm.v4" v0.0.0-20150410205938-af4be7b079ac
	"gopkg.in/juju/charm.v5" v0.0.0-20161109084014-949f52b3948c
	"gopkg.in/juju/charm.v6" v0.0.0-20180119231043-96786fc3f869
	"gopkg.in/yaml.v1" v0.0.0-20140924161607-9f9df34309c0
)

So I titled this issue wrong; it is possible to use gopkg.in with a major version > 1, although the behaviour is still not correct.
Interestingly, the go.mod file does not contain all the dependencies that I'd expect. For example, it contains gopkg.in/yaml.v1 (used by gopkg.in/juju/charm.v4) but not gopkg.in/yaml.v2 (used by gopkg.in/juju/charm.v6); it contains github.com/juju/names but not gopkg.in/juju/names.v2).

require "gopkg.in/yaml.v2/v2"
works, sort of - it still includes the "gopkg.in/yaml.v2 v1.1.0-gopkg-v2.1.0" - see #24094

support gopkg.in major versions properly

"Properly" is a loaded word, but it should work at least a little better than it does right now. In the original case the v2.1.0 should probably just be rewritten transparently to v1.1.0-gopkgin-v2.1.0, because we know this is gopkg.in.
I'm going to leave this bug open to track deciding what level of gopkg.in support we want. Maybe we should actually just allow v2.1.0 instead of the funny pseudo-version.

Interestingly, the go.mod file does not contain all the dependencies that I'd expect.

It contains a simplified list of dependencies, omitting those implied by the ones already listed. Because charm.v6's dependencies.tsv lists the exact version of gopkg.in/yaml.v2 that the build chose, it lists charm.v6 in the go.mod and stops there.

this is still happening to me

Agreed still doesn't work for me either
module github.com/gobuffalo/pop

require (
	github.com/cockroachdb/cockroach-go v0.0.0-20180212155653-59c0560478b7
	github.com/fatih/color v1.6.0
	github.com/go-sql-driver/mysql v1.0.3
	github.com/gobuffalo/envy v1.6.2
	github.com/gobuffalo/packr v1.11.0
	github.com/gobuffalo/uuid v1.2.0
	github.com/gobuffalo/validate v1.0.0
	github.com/jmoiron/sqlx v0.0.0-20180406164412-2aeb6a910c2b
	github.com/joho/godotenv v1.2.0
	github.com/lib/pq v0.0.0-20180327071824-d34b9ff171c2
	github.com/markbates/going v0.0.0-20170113214412-0576708c56ce
	github.com/markbates/inflect v0.0.0-20180405204719-fbc6b23ce49e
	github.com/mattn/anko v0.0.3
	github.com/pkg/errors v0.8.0
	golang.org/x/net v0.0.0-20180420171651-5f9ae10d9af5
	golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f
	gopkg.in/yaml.v2 v2.2.1
)

vgo: errors parsing go.mod:
$GOPATH/src/github.com/gobuffalo/pop/go.mod:20: invalid module: gopkg.in/yaml.v2 should be v1, not v2 (v2.2.1)

Can we reopen this issue? I'm seeing the same issue as @kron4eg above.

I get the same with yaml.v2; the initial go.mod file was generated by vgo build but after that, it fails with the above error.  yaml.v2 has no tags, does not use semver or anything.

same problem with elastic
module modulename

require (
	github.com/BurntSushi/toml v0.3.0
	github.com/beorn7/perks v0.0.0-20180321164747-3a771d992973
	github.com/garyburd/redigo v1.6.0
	github.com/go-redis/redis v0.0.0-20160126235308-877867d2845fbaf86798befe410b6ceb6f5c29a3
.....
	gopkg.in/olivere/elastic.v3 v1.0.73-gopkgin-v3.0.73
)

→ vgo build
vgo: errors parsing go.mod:
.../App/go.mod:26: invalid module: gopkg.in/olivere/elastic.v3 should be v1, not v3 (v3.0.73)

And if I remove line with elastic from go.mod it builds.

I also see this issue.

Fixed by recent CL.

I am still seeing this with go version go1.12.1 linux/amd64
go test github.com/jaegertracing/jaeger/plugin/storage/badger/dependencystore -run ^(TestDependencyReader)$

go<EMAIL_ADDRESS>parsing go.mod: go.mod:6: invalid module: gopkg.in/inf.v0 should be .v0, not v1 (v1.9.1-gopkgin-v0.9.1)
go: error loading module requirements


@SuppressModernizer not applicable to type use

I'm unable to suppress the StringBuffer to StringBuilder recommentation:
StringBuffer sb = new @SuppressModernizer StringBuffer();

If I say
@SuppressModernizer
StringBuffer sb = new StringBuffer();

I get

'@SuppressModernizer' not applicable to local variable

I could maybe use the exclusions tag, but what the heck is a javap format: java/lang/String.getBytes:(Ljava/lang/String;)[B supposed to mean I dont know. Can you include a couple of examples? Presumably most people using this plugin have no knowledge of bytecode internals.

Hi, my org is using error-prone instead of modernizer so I'm not going to be contributing any more.

@gaul Perhaps the first step is to add ElementType.TYPE_USE, which should be easy if annotations were bumped to 1.8 or if it were a multi-release jar.
The second part is dealing with the annotation at detection point, I think: a TYPE_USE occurrence needs to be propagated to the corresponding variable allocation, which again would require JDK8+ (9+ in case of multi-release jar) as the runtime.
That would satisfy everyone at Java 11+ (mulit-release, which works for Java 9+). Java 8 users would be left off no worse than they are now.

I'm not too sure what the current minimum version is but JDK 6 used to work.  I am happy to declare Java 8 the new minimum so Modernizer can access ElementType.TYPE_USE.  Can you propose a PR for this?

I would like the next 2.6.0 release to include this feature.  @delanym @rovarga could you look into this?

Yes, PR coming out in a few minutes.

#171 , but it also touches definitions -- sun.misc.BASE64Decoder/Encoder no longer exist.

Just to be clear there is no fix provided.  There is an open linked PR with no explanation for what it does.

I still don't understand if this is possible to fix.  https://docs.oracle.com/javase/specs/jls/se8/html/jls-9.html#jls-<IP_ADDRESS> says:

An annotation on a local variable declaration is never retained in the binary representation.


Revenants death reduction - maxed combats

If the user has maxed combats removes the 5% default chance from the calculations.
Closes #3867

[x] I have tested all my changes thoroughly.

What does this make the death chance now, if maxed?


Upgrade 1.2.0 snapshot

Codecov Report

Merging #590 into master will decrease coverage by 0.15%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #590      +/-   ##
============================================
- Coverage     54.09%   53.93%   -0.16%
  Complexity      722      722
============================================
  Files           178      178
  Lines          3161     3161
  Branches        212      212
============================================
- Hits           1710     1705       -5
- Misses         1329     1334       +5
  Partials        122      122

Impacted Files
Coverage Δ
Complexity Δ

...tion/servicebus/queue/ServiceBusQueueTemplate.java
62.5% <0%> (-5%)
6% <0%> (ø)

...tion/servicebus/topic/ServiceBusTopicTemplate.java
62.79% <0%> (-4.66%)
6% <0%> (ø)

...tegration/servicebus/ServiceBusMessageHandler.java
72% <0%> (-4%)
9% <0%> (ø)

Continue to review full report at Codecov.

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


Call setLifecycleOwner on bindings

As noted in another issue this library doesn't currently support LiveData. What is particularly challenging is that ViewDataBinding objects that the adapters do not get their setLifecycleOwner methods called.

Got a WIP implementation started https://github.com/evant/binding-collection-adapter/tree/livedata-support

FYI - Today at the Android Developer Summit I was able to speak with several Googlers that work on Architecture Components / Data Binding about this issue. I brought their attention to https://issuetracker.google.com/issues/112929938 and they said they should be able to get it resolved soon.  Fingers-crossed.


Click keyword fails if locator is mix of element and something else

Click keyword fails with following error:
Error: elementHandle.click: : expected object, got string

if locator is mix of element and something else.
Here are examples to reproduce this issues:
*** Settings ***
Library    Browser

*** Test Cases ***
# Works as expected with mix of css and text locators
Mix of css and text
    New Page    https://github.com/MarketSquare/robotframework-browser
    Click    ul.UnderlineNav-body >> text=Issues
    Sleep    3
    Get Title    contains    Issues

# Works as expected with pure element locator
Just Element
    New Page    https://github.com/MarketSquare/robotframework-browser
    ${element}    Get Element    ul.UnderlineNav-body >> text=Issues
    Click    ${element}
    Sleep    3
    Get Title    contains    Issues

# Fails in case of mix of element and text locators
Mix of Element and text
    New Page    https://github.com/MarketSquare/robotframework-browser
    ${element}    Get Element    ul.UnderlineNav-body
    Click    ${element} >> text=Issues
    Sleep    3
    Get Title    contains    Issues

# Works as expected, Get Element does not fail in case of mix of element and text locators
Just Element-2
    New Page    https://github.com/MarketSquare/robotframework-browser
    ${base}    Get Element    ul.UnderlineNav-body
    ${element}    Get Element    ${base} >> text=Issues
    Click    ${element}
    Sleep    3
    Get Title    contains    Issues

Tested on robotframework-browser 5.1.0 and 4.4.0

@all-contributors please add @JaPyR  for bugs


Feature section

closes #23
Changing cards are added by fetching the features from features.js.
Responsive design

Great work @supunvindula! But one small fix, could you make the "changing card" feature more evident?Like could you change the colour of each card? And let the colours blend in well! Thanks for the contribution. Once that's implemented, Ill merge the PR

Hi, Its better to make it as a bug fix. I have tried different approaches for it. But still it didn't work.


Incorrect: host networking driver is not supported on Docker Desktop for Windows

File: network/host.md

The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server.

However, on current Docker Desktop for Windows on WSL2, there is a difference between
docker run -it --rm --network host alpine ip addr ls
docker run -it --rm --network bridge alpine ip addr ls

More, if I run something like
docker run --name redis -d -p 6379:6379 redis:5-alpine

Then I can connect to <IP_ADDRESS>:6379 with
docker run -it --rm --network host redis:5-alpine redis-cli -h <IP_ADDRESS>

but can't connect without --network or with --network bridge (unless internal IP or host.docker.internal is provided instead).
So it's clear that host has some effect, even though it is different from what's expected from Windows host point of view.

This should also be specified on the network/index.md page where it lists the network drivers.


Exclude Windows OS temp files from repo

We need to exclude any temp files created by Windows OS

closed from local


Docker overrides the IP address of my own manually created bridge

I just sorted and wrote what I think is a bug here, please take a look and tell me what do you think, it is just exactly as the title, Docker always overrides the IP address of my own manually created bridge and ignores the ip address which I use for the birdge
http://serverfault.com/questions/808151/docker-overrides-the-ip-address-of-my-own-manually-created-bridge?noredirect=1#comment1026696_808151

@mne91
On manual restart of docker, the bridge IP does not get overwritten.
I am guessing this has to do with some ordering at boot. Could it be docker is started before your bridge gets an IP assigned ? From the logs I am guessing your bridge gets an IP assigned via DHCP (which may in fact take some time).

@aboch
I am not sure actually, I am creating the bridge inside /etc/network/interfaces file.
Could you tell me how to prevent him from taking the ip from dhcp and force him to use what I wrote in interfaces file?

@mne91 I am not sure, it may have to do with the fact you are enslaving your eth0 interface into the bridge. Please try change that and see if the makes a difference. Or find out how to statically configure the IP address for your bridge.

@aboch i dont think this is a candidate for closing yet. We have to check the reproduction and if it is, then I think we should atleast document the behaviour. Especially as per the discussion in http://serverfault.com/questions/808151/docker-overrides-the-ip-address-of-my-own-manually-created-bridge, the author needs help with a recommended configuration.

@mne91 Assuming you are running a debian based distribution (from posting about etc/networks/interfaces) this link (https://www.howtoforge.com/debian-static-ip-address) for example should give you the info you need to statically configure the IP address for your docker0 interface.
Based on the comments above, I think we should now close this issue as not docker specific.

Thanks @aboch.
@mne91 pls comment if you this issue should be re-opened.

I just have the same issue, but another server works fine with the same config.
Used bridge util to create a bridge named kbr0, and configured dockerd options with -b=kbr0.
kbr0's address:<IP_ADDRESS>/24
after I restarted docker service, the address of kbr0 was changed to <IP_ADDRESS>.

I just have the same issue, but another server works fine with the same config.
Used bridge util to create a bridge named kbr0, and configured dockerd options with -b=kbr0.
kbr0's address:<IP_ADDRESS>/24
after I restarted docker service, the address of kbr0 was changed to <IP_ADDRESS>.


Broken "Edit this page" link

What happened?
Clicking on the "Edit this page" button on the right sidebar returns a "404: Not found" error.
What did you expect to happen?
Clicking on the "Edit this page" button should let me edit this page.
Steps to reproduce

Navigate to the "Notes to SoCcess" website.
On the right sidebar (shown below), click on "Edit this page"

Environment
I am viewing this webpage on a 32 inch monitor. The right sidebar seems configured to only show past a certain view-port width (1280px).

Thank you for pointing this out @euchangxian! Issue resolved following the instruction from the Nextra documentation.


fix(lnd): update lnd to 0.7.1-beta-rc2-3-g3d84693a

Description:

update lnd to 0.7.1-beta-rc2-3-g3d84693a
set neutrino user agent name and version
update lnd-grpc to v0.3.0-beta.2

Fix #2612
How Has This Been Tested?
Manually
Types of changes:
Dep Updates
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 20.131% when pulling f512ccbc37738b9fbaf5e7703057263ff4f87214 on mrfelton:chore/update-lnd into a9275e64d4a4348f33119721862e28566e12e4d8 on LN-Zap:master.


bpaf_derive should reorder fields in construct to ensure positional stuff goes at the end

By default it is not and it can be confusing

This can be done within the structure but it won't solve the problem if positional items are nested inside some other structure. Proper fix should involve change on the parser level.


fix(input-number): click the button can modify the data when mode is …

Types of changes

[ ] New feature
[x] Bug fix
[ ] Enhancement
[ ] Component style change
[ ] Typescript definition change
[ ] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

input-number
readonly时隐藏button
hide button when readonly
#3138

Checklist:

[x] Test suite passes (npm run test)
[x] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[x] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

@bsuooo 直接隐藏的方式不太合适，感谢贡献！#3314


Bottom view of a binary tree

💥 Proposal
Part of GSSOC '21 in python language
Implementing using level order traversal
Have you read the Contributing Guidelines on Pull Requests?
yes

/assign


Update ABC Metric for code related to the VisualModel functionality

Raised the ABC metrics bar from 20 to 15 for code associated with the new VisualModel functionality.

Coverage: 92.716% (+0.002%) from 92.714% when pulling edcd6d0efb84dadca9be96371b91c434fdde8bf4 on abc-metric-for-visual-models into d064c65839bd3a9069f687a15d8dde2133225003 on master.


i found new ishu i cant enter password ina  required promt

i tryed your tool and found this Ishu  i found new ishu i cant enter password ina  required promt

Same here bro, I have found a fix for it
That is by setting your terminal in raw mode which allows you to enter password
but it  a hard process kitty supports raw mode by default but other terminals need some sheneni ganse to enable it. Don't worry we are finding a way fix it through the prompt it self

Fixed


BibDocFile: Copyright and license for files

Adds possibility to add copyright and license for each file (separate
from copyright and license for whole record (closes #1684)

Modifies the filter_field_instances function in bibrecord:

Adds new mode to filter_mode that allows to filter all fields
without specific subfield

Adds functions (inside bibupload) to synchronize MARC for 542 and 540
field with copyright and licenses from BibDocs, whenever bibupload
with "FIX-MARC" field is run

Adds subfield $8 to 8564 MARC field, that stores the id of a BibDoc

FFT now modifies the copyright and license:

Added functions to bibupload, so when FFT is uploaded, it also
allows to modify the copyright and license

Fixed the regression tests (bibupload, websearch) after adding the
subfield $8 to the 856 field

Signed-off-by: Sebastian Witowski<EMAIL_ADDRESS>

No more WIP, it has been tested on cds-test and deployed on CDS.

@switowski can we close the PR since Invenio 1.x is in feature freeze state?

:+1:

I'll reopen it, as discussed with @tiborsimko IRL, this could go to v.1.3.0.


Timeout when debugging the operator locally

Operator exits with message Failed to update lock: rate: Wait(n=1) would exceed context deadline and stopping on a breakpoint for too long

Out of curiosity, what IDE do you use?
I've been facing that issue as well with Goland, though my understanding is that rather an issue with it not running other Go routines while one is being stepped. In my case, I step into the reconcile loop routine, and the routine that refresh the Lease used for leader election is also blocked.

I use VSCode for Go.
From the logs, it seems the issue arrise when debugging for more than 15 seconds which is the default LeaseDuration. I think this issue describes the problem in the Go debugger. From the comment section, it seems like a difficult fix

Thanks, that looks like the issue. It's likely Goland uses Delve as well.


better support for webdriverio options

The original method of passing options to webdriverio caused some
confusion. If the user wanted to simply pass a webdriverio config
directly through the codeceptjs config some properties would get
overridden with undefined if they didn’t set browser or url.
It makes more sense to allow the passing of a webdriverio config rather
than attempting to map these properties and construct that object since
it can get extremely complex.
I.E
// how you're currently doing it
{
  "helpers": {
    "WebDriverIO": {
      "proxy": {
        ...
      }
    }
  }
}

// it should be more like this
{
  "helpers": {
    "WebDriverIO": {
      "desieredCapabilities": {
        "proxy": {
          ...
        }
      }
    }
  }
}

Thanks. I will have some time to review and merge it then.

Thanks. Sorry for late reply, I was working on Protrator helper, so didn't have time to take major changes into WebDriverIO. I like your PR and I will merge it. The only thing, I'd keep is browser configuration in the root of WebDriverIO


can't use coldkeypub.txt

If you use btcli_regencoldkeypub to generate your coldkeyfile then run the validator you get the following error:
KeyFileError: Keyfile at: /root/.bittensor/wallets/default/coldkey does not exist
It should look for and work with /root/.bittensor/wallets/default/coldkeypub.txt as most validators do not import their cold key mnemonic to the validator machine.

I have just found btcli w update which now encrypts the coldkey file meaning you can import the key with the mnemonic and not worry. You need to update the cli description of that command as it currently says
update              Delegate Stake to an account.
Which is incorrect. That said i still think you should be able to enter just coldkeypub and never have to enter seed on gpu machine.

@Eugene-hu  @p-ferreira do we have eyes on this?

@Eugene-hu @p-ferreira do we have eyes on this?

This should be an issue with the bittensor repo, rather than the text-prompting repo. It has been addressed in the latest release: https://github.com/opentensor/bittensor/pull/1534


Implement #390 by renaming vault token files

Could you please update the config submodule in this PR?


in distill, how print teacher model accuracy of data

Thanks for your issue.
You can set the type of val_cfg to mmrazor.SingleTeacherDistillValLoop like this config.
Then you can get the accuracy of the teacher model during training like this log:
{"student.accuracy/top1": 29.884000778198242, "student.accuracy/top5": 55.50400161743164, "step": 1}
{"teacher.accuracy/top1": 73.62600708007812, "teacher.accuracy/top5": 91.59000396728516, "step": 1}

Thanks for your issue. You can set the type of val_cfg to mmrazor.SingleTeacherDistillValLoop like this config. Then you can get the accuracy of the teacher model during training like this log:
{"student.accuracy/top1": 29.884000778198242, "student.accuracy/top5": 55.50400161743164, "step": 1}
{"teacher.accuracy/top1": 73.62600708007812, "teacher.accuracy/top5": 91.59000396728516, "step": 1}

thanks for your reply, but i used mmseg，if i add val_cfg，i still can not get the teacher accuracy，and if i add student_recorders and teacher_recorders, it will occurs TypeError: GeneralDistill: SingleTeacherDistiller: init() got an unexpected keyword argument 'student_recorders'. i can not find ‘ConfigurableDistiller‘，

Please provide your training config and the output of pip list | grep "mmcv\|mmrazor\|^torch".

Your MMRazor version is 0.3.1, which does not support the recorder mechanism and SingleTeacherDistillValLoop.
Please update the version to 1.0.0rc1 by using the dev-1.x branch.

Please reopen it if there are any problems in the future.


Update README.md

Corrections, clarifications, and an additional deprecation.

Is anything inaccurate?
Are there any other deprecations we should include?

I’m not sure why akworks is listed separately, as it’s not a direct dependency of the SDK. Instead, it’s a dependency of the Dock crypto library, which is itself a dependency of the Dock WASM crypto library. This, in turn, is a dependency of the Dock TS crypto wrapper library, which ultimately becomes a dependency of the SDK.
Also, this library includes full anoncreds support using Pointcheval-Sanders and BBS+ schemes.


Add/hide tokens does not work when using results of search

When a token is hidden via the add/hide tokens screen with the search bar, the token is not hidden.

Sequence
Description

Delete

Deleted

Missing

@eviltofu not fixed AFAIK right?

@eviltofu not fixed AFAIK right?

This looks fixed.


Update documentation for Cloudstor in AWS/Azure for 17.06

Proposed changes
Updated persistent volume documentation for AWS/Azure. Mention several examples on how to use cloudstor volumes with local/shared backing in AWS.
Unreleased project version (optional)
17.06
Related issues (optional)
@friism @kencochrane @FrenchBen

Please ping after you have addressed the technical feedback, because I'd like to give this a copy-edit pass.

@ddebroy looks good. You mention it briefly, but we should probably describe how to clean up volumes and snapshots that are left over, and maybe call it out a little more. Because they are created outside of CloudFormation, people will need to manually remove these before they can delete their stack. We should mention that, so that we can point people to the docs when it happens and they email us.

Addressed review comments so far above. I have added a note on how to get the list of EBS created by the stack that one can manually delete. So far, I have found that the stack deletion goes through fine even with EBS volumes from cloudstor lying around but those volumes just never get deleted.

@mstanleyjones this is now ready as far as internal tech reviews are concerned.

Thanks, I'm doing copy-editing now. I'll have it finished by GA or very shortly after.

@ddebroy PTAL at the copyedit to be sure I didn't change any technical stuff in an incorrect way.

@mstanleyjones  LGTM.

@mstanleyjones I have addressed/undid the changes you requested.


Globalnet IP could not be connected after annotation was set

Testing GlobalNet annotation - Nginx service on OSP cluster B (private) should get a GlobalNet IP
export KUBECONFIG=/mnt/skynet-data/ocp-install/ocpup/.config/cl1/auth/kubeconfig
# Watching output of command: /mnt/skynet-data/ocp-install/oc get svc nginx-cl-b -n test-submariner -o jsonpath='{.metadata.annotations.submariner\.io\/globalIp}' |& highlight '[0-9\.]+'
# Search pattern (or exit code):/[0-9\.]+/
# Retry attempts: -1   # Timeout limit: 3m
nginx_global_ip='<IP_ADDRESS>'

Testing GlobalNet annotation - Netshoot pod on AWS cluster A (public) should get a GlobalNet IP
export KUBECONFIG=/mnt/skynet-data/ocp-install/nmanos-cluster-a/auth/kubeconfig
netshoot_pod_cluster_a=netshoot-cl-a
# Watching output of command: /mnt/skynet-data/ocp-install/oc get pod netshoot-cl-a -n test-submariner -o jsonpath='{.metadata.annotations.submariner\.io\/globalIp}' |& highlight '[0-9\.]+'   # Search pattern (or exit code):/[0-9\.]+/
# Retry attempts: -1   # Timeout limit: 3m
<IP_ADDRESS>

Testing GlobalNet connectivity - From Netshoot pod [netshoot-cl-a] on cluster A   To Nginx service on cluster B, by its Global IP: '<IP_ADDRESS>'
oc exec netshoot-cl-a -n test-submariner -- curl --output /dev/null --max-time 30 --verbose '<IP_ADDRESS>':8080
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0*
Could not resolve host: '<IP_ADDRESS>'
* Closing connection 0
curl: (6) Could not resolve host: '<IP_ADDRESS>'
command terminated with exit code 6

Full test report:
https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS/412/Test-Report

I was trying to connect '<IP_ADDRESS>':8080 instead of <IP_ADDRESS>:8080.
That's why it failed. Closing bug.


Add moveBefore and and moveAfter methods to useTreeData

Provide a general summary of the feature here
useListData has the moveBefore and moveAfter methods, which are useful for working with drag and drop. It would be useful to have equivalents for useTreeData. This was mentioned in this PR #4444 but it was closed.
🤔 Expected Behavior?
This should work just like the moveBefore and moveAfter methods for useListData. The types would be the same:
moveBefore(key: Key, keys: Iterable<Key>): void
moveAfter(key: Key, keys: Iterable<Key>): void

😯 Current Behavior
These methods currently don't exist.
💁 Possible Solution
No response
🔦 Context
It is currently difficult to reorder items in tree structures, particularly when working with drag and drop. This feature would make this much easier.
💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Just a fyi, I've added this issue to our internal tracking ticket: https://github.com/orgs/adobe/projects/19/views/4?filterQuery=treeda&pane=issue&itemId=26812541. Thanks for raising this, we'll definitely need it for our eventual implementation of Tree.


Using a Vector icon in a textfield

Is it possible to add a vector icon to a text field, such as in 'Password Input' field: https://www.google.com/design/spec/components/text-fields.html
We are looking to add a show password field to a text input field and would like to use an 'eye'-icon for this.

Maybe it's similar to #115 ?
Unfortunately, it's not in my mind when I wrote the Textfield component, but I'll try to do it in the future releases.

Any update on this?


Docker installation can not work with volumes

Describe the bug
Docker installation of Metatron Discovery (https://hub.docker.com/r/metatronapp/discovery) does not manage to persist data from volumes and correctly re-use them.
To Reproduce
Steps to reproduce the behavior:

Create docker containers using the Docker Installation Guide (https://metatron.app/download/installation-guide-docker/):

docker run -i -d --rm -m 6G -p ${HOST_DISCOVERY_PORT:=8180}:8180 \
-v /apps/host_volume/druid:/usr/local/druid-backup \
-v /apps/host_volume/mysql:/usr/local/mysql-backup \
--name metatron-discovery metatronapp/discovery:latest

Stop Metatron container.
Start it again.
It will not be able to run it again.

Expected behavior
After restart the container the volumes should be able to load all saved data from MySQL and Druid.
I'm pretty sure there is something wrong with the script "start-mysql.sh" but after many attempts I can't find a way to make MySQL work again manually.
Logs
My docker logs from the container show something wrong with MySQL after restarting the container:
2020-01-09 20:20:34,189 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-09 20:20:35,628 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>92712 for <Subprocess at<PHONE_NUMBER>44416 with name mysql in state RUNNING> (stdout)>
2020-01-09 20:20:35,628 INFO exited: mysql (exit status 1; not expected)
2020-01-09 20:20:35,628 DEBG received SIGCLD indicating a child quit
2020-01-09 20:20:36,631 INFO spawned: 'mysql' with pid 1781
2020-01-09 20:20:36,639 DEBG 'mysql' stdout output:
mysql data doesn't exists!!

2020-01-09 20:20:36,655 DEBG 'mysql' stdout output:
rm: cannot remove '/var/lib/mysql': Device or resource busy

2020-01-09 20:20:36,678 DEBG 'mysql' stdout output:
2020-01-09T20:20:36.678744Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
2020-01-09T20:20:36.678804Z 0 [ERROR] Aborting

Desktop (please complete the following information):

OS: Ubuntu 18.04.3 LTS
Docker: Docker 19.03.5, build 633a0ea838

@heronfonsaca Sorry for the delayed response.
I've written the document about docker persistence that linked to the body.
But I noticed that important content is missing from the document,
I will contact the homepage operator and it will be added soon.

I leave the missing contents here.
And many thanks for your very important contribution.
(TL;DR)
Add -e PERSIST_DISCOVERY=TRUE option when you (re)start a metatron-discovery docker.

One more important thing is the option for running Metatron Discovery application.
By default, Metatron Discovery run with --init option for docker container for initialize the database per every users. It is necessary for the first execution.
So, if you decide to keep the data, you must add a new environment variable from the next time you run it.

PERSIST_DISCOVERY=TRUE

Except for the very first time, please be sure to include this setting.
Finally, you can run a container with these options for persist data.
-v {HOST_DIR_FOR_DRUID}:/usr/local/druid-backup
-v {HOST_DIR_FOR_MYSQL}:/usr/local/mysql-backup
-e PERSIST_DISCOVERY=TRUE
 ‘PERSIST_DISCOVERY=TRUE’ option is required from the second run. It must be omitted for the first time in your entire environment.
At first, persist the data by just setting up the volume (-v), then add environment (-e) setting from the next run.


How can I redirect request  after response flow

class Modify:         def response(self, flow):                    # parse the flow and redirct to another web                      if ....:                          redirect.... addons = [         Modify() ]
How can I redirect to another web after parse the response flow
I got the sample of  "redirect_requests.py" , but it's redirct before response.
I need redirect after response, how can I do.
@mhils

Maybe add the Location header to the response? That way the browser will redirect you to the URL specified there.
flow.response.headers['Location'] = 'http://www.example.com'

Maybe add the Location header to the response? That way the browser will redirect you to the URL specified there.
flow.response.headers['Location'] = 'http://www.example.com'

@typoon , thanks
Set Location header，  it doesn't work。

Mind sharing your code and how are you validating that it doesn't work?

@typoon Is the header though? I would expect that flow.response.status_code should be changed as well, i.e. to 301/302 to make sure that client will even bother with Location header.
@hucailai On the other note, I think it was requested by authors to ask questions at https://stackoverflow.com/questions/tagged/mitmproxy

You probably want use Response.make(302, ...).
Also, please use StackOverflow. I wish we could, but just can't handle the volume of user questions here.


import issue of keras.layers concatenate

within dissect/dissect_expr.py line 26,
from keras.layer.merge import concatenate as concat
causes a module does not exist error
should be
from keras.layers import concatenate as concat

Thanks! I'm unable to reproduce. With Keras 2.7.0, it works for me. Could you check your keras version?

actually, importing concatenate from both keras.layers.merge and keras.layers should work. Also, line 26 is from keras.layers.merge import concatenate as concat not from keras.layer.merge import concatenate as concat. Could you check if source files were modified somehow?


IdleDeadline feature

Fix issue #358 create IdleDeadline functionality for the requestIdleCallback
Please have a look at the requestIdleCallback test section I comment out. I couldn't make this test work, and I think it's because the new feature open the callback and call it with the IdleDeadline object I created.

Thanks for this. I did have a quick look, but I guess getting those stack traces right is non-trivial and I can't see exactly what it is to be done by a quick glance.

It's been two years and it has not moved much. I have no personal interest in this, so for this to go forward, someone needs to pick it up. I can't debug on something I really do not know anything about. Will close in near future.


Back to Reducer (time-travel debugging would have helped here)

Fixes #42

Thanks a lot for looking at this so fast!

I can see that the map loading state has disappeared, and the same inconsistency could happen when changing the "Color by" setting. I will try to get these in here.
We could add error handling for both as well, if we can think up some sort of UI for it

latest commit also means the tiles config must be provided as numbers - would be good to add this to the documentation

Woop!

🎉


[SUP-646] Add screen reader announcement to loading spinner

From SUP-646:

Across Terra, we use a loading spinner when we are making a server call to let the user know that an action is in progress. The spinner does not have any accessible text attached to it, so a screen reader does not have anything to announce.
It would be helpful if the spinner announced that it was loading content. The proposal would be to add an aria role of alert with text that is not visible to sighted users. For an example, see https://codeburst.io/how-to-create-a-simple-css-loading-spinner-make-it-accessible-e5c83c2e464c
It might be nice if the text is not added unless the operation has been in process for a certain length of time, as often the loads are quite fast.

This adds a visually hidden alert to the spinner icon. DelayedRender is used to make an announcement only if the spinner is shown for more than 150ms.
To use DelayedRender here, I had to move it to its own module to avoid a circular import issue (DelayedRender was in components/common, components/common imports spinner from icons and creates a few spinner elements that are exported from the module).

This behaves very nicely-- thanks @nawatts !


Wiring

In ELN1 wiring can be frustrating - Only base Minecraft blocks could cover up the wires for example and they were just impossible to hide.
Please allow blocks from Chisel to be used to cover wires!
Also; a way to have a component "Centrally-Wired" would be nice. The concept here is a wire is inside of a wall, hidden. you could place a component - Like a light switch, lighting fixture or some member of the Signals family like a motion sensor - on your wall or ceiling and connect to that wire "from the back" of the thing. This would allow more clean-looking bases in certain applications where the hiding of the wires would be preferred.
I've said this before in Discord and it was mentioned that there could be a problem if the block behind the equipment has multiple wires. This is where I'm thinking this feature could require a different block - similar to a Hub. You place said component inside the wall and connect it to the wire you want. It would behave like a generic cable hub but would be what the component connects to.
In ELN1 when placing light fixtures, if you typed a wireless channel it seemed to save it but if you were powering with a cable it didn't remember that option - for those who wire with cable it's a pain to go one-by-one and change that option.
I could think of an evil way to dodge voltage drop by using lamp supplies and outlets - There seems to be no drop between a lamp supply and a load connected to it. Cmon this is ELN we're talking about here, such a easy way of escaping the stubborn-ness of electricity isn't tolerable! :p

Please allow blocks from Chisel to be used to cover wires!

This actually worked (somewhat) in the fork, except for situations where we had connected textures issues.
The rest of this is a duplicate of https://github.com/age-series/ElectricalAge2/issues/131, we have a lot of ideas about using conduits.
Yes, ELN1 lamp supplies and outlets are super broken and OP. It's actually one of the most efficient ways to move power, I think it can move more than poles. Wirelessly. Lol.. that system is 100% getting replaced with conduits.

Someone else mentioned the central wiring part?


Add support for HDRP and LWRP (Feature Request)

Great job on UMA so far. Any eta on adding support for LWRP and HDRP materials so UMA can be used with the new render systems? With some guidance I should be able to help on work and testing in that area.

This feature will be included in 2.9, kenamis has a test version working. I'll close this out, and you should see a beta available with this functionality when w

Awesome, thanks :)

@Jaimi how could I get the test version? I'd like to give it a try, i'm currently using the 2.8 git version.

kenamis created a branch for it: feature-HDRP,  select the code tab here in the GitHub project, change the branch and download the zip uding the "clone or download" button.

Any idea when 2.9 will be available?

No idea, sorry.

I just tested the Feature-HDRP branch but it doesn't seem to work either: any pointers about how to use it?

You should use the Develop branch - it has all the latest updates and HDRP support

@PinoEire You also need to convert your uma materials, overlays, slots to use the new shaders in the RP you are using.  I have a sample package for uma default for HD here; https://github.com/kenamis/UMAHumanHD

@kenamis Any specific instruction to get this running?

Checked out dev branch today
Checked out kenamis HD repo a week ago
Copied UMA and UMA_HD folders to a new HDRP project
Put in UMA_DCS
Put in UMADynamicCharacterAvatar
Rebuilt UMA Global Library
Switched active race to HumanMaleHD on avatar
Hit Play
Got a strange stretched something instead of an avatar. Looks the same as with 2.8.1 and kenamis HD

That sounds like the issue I had, try this.
@daschatten Find the directory with your UMA Materials in

edit the generated texture settings
the first one should be BaseMap, not MainTex

use the drop down to update it

@wirelessdreamer I use kenamis hd package and the uma material looks this, especially the diffuse keyword is different to yours. Which hdrp version do you use? For me it's 5.7.2

I'm using lwrp, never touched hdrp yet

Do you have any console errors or warnings? Can you post a screenshot of
what your issue loops like?
On Fri, Jul 12, 2019, 7:36 AM Nathanael Anderson<EMAIL_ADDRESS>wrote:

I'm using lwrp, never touched hdrp yet
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/umasteeringgroup/UMA/issues/192?email_source=notifications&email_token=AA46NG5JIDWOK5NVOFZIC2TP7CJF7A5CNFSM4GO6B7U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZZ57LY#issuecomment-510910383,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA46NGZM3NFVXQU3OU3IXBTP7CJF7ANCNFSM4GO6B7UQ
.

I think hdrp requires linear color space too. Did you set that in your
project settings?
On Fri, Jul 12, 2019, 11:20 AM Kenan<EMAIL_ADDRESS>wrote:

Do you have any console errors or warnings? Can you post a screenshot of
what your issue loops like?
On Fri, Jul 12, 2019, 7:36 AM Nathanael Anderson<EMAIL_ADDRESS>wrote:

I'm using lwrp, never touched hdrp yet
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/umasteeringgroup/UMA/issues/192?email_source=notifications&email_token=AA46NG5JIDWOK5NVOFZIC2TP7CJF7A5CNFSM4GO6B7U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZZ57LY#issuecomment-510910383,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA46NGZM3NFVXQU3OU3IXBTP7CJF7ANCNFSM4GO6B7UQ
.

I think hdrp requires linear color space too. Did you set that in your project settings?

Yep, it's set (by default).

Do you have any console errors or warnings? Can you post a screenshot of what your issue loops like?

No warnings or errors. Here is a screenshot:

I'm using Unity 2019.1.8 with HDRP template.

If you use the builtin Renderer do you have any problems? Your issue
doesn't look like anything specific to the SRP support (it doesn't affect
the mesh generation).
On Sun, Jul 14, 2019 at 12:55 PM Florian Bittner<EMAIL_ADDRESS>wrote:

Do you have any console errors or warnings? Can you post a screenshot of
what your issue loops like?
No warnings or errors. Here is a screenshot:
[image: grafik]
https://user-images.githubusercontent.com/2094680/61188608-f6049c00-a681-11e9-973c-a10138c425ee.png
I'm using Unity 2019.1.8 with HDRP template.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/umasteeringgroup/UMA/issues/192?email_source=notifications&email_token=AA46NG4GXMTVOZQD2WC2RJLP7OADBA5CNFSM4GO6B7U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ4MFPA#issuecomment-511230652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA46NG7DADHGQ47F63QL6XTP7OADBANCNFSM4GO6B7UQ
.

If i use a new 3D project template in 2019.1.8 and add uma dev branch there is no issue.

I posted another picture in slack as jaimi asked if the character is wrapped in a ear:

Ok, got it working:

It was really simple, i just replaced the unity material in those four files with the one from kenamis hd and set the shader channels correctly.

There must be something wrong in your package @kenamis.

Note: I used Unity 2019.1.8 and UMA develop branch!

Ok thanks.  I'll check it out and update it.

the HD repo's uma material is correct;
https://github.com/kenamis/UMAHumanHD/blob/master/UMAHumanHD/Assets/UMA_HD/HumanSharedHD/HDMaterial/UMA_Lit.asset
You said "It was really simple, i just replaced the unity material in those four files with the one from kenamis hd and set the shader channels correctly", were you not using the new HD race that has that new uma material already set?  If not, then I think the issues you were seeing would be the outcome.

At first i tried the new HD race but that resulted in the distorted textures as shown above. Finally i just replaced the unity material in those four default UMA materials (not the HD ones) and set it to yours (Simple material with HDRP/Lit shader), then the default HumanMale race worked.


I cannot login at Bitdefender.

I cannot get the text field element at the sign in page redirected from https://login.bitdefender.com/central. I have tried several browsers, Edge, Chrome, Opera, Firefox. The ACCViewer can detect the Email text field.  If I need UIA Access, then please help me as I don't know how to make it.

Unable to reproduce, running Windows 10, latest UIA, latest Chrome, AHK without UIAccess:


NameError: name 'load_custom_node' is not defined

Hi
I have converted the image upscale comfyUI workflow to python file. The json & python file as text attached for reference
workflow_image_upscale_api.json
workflow_image_upscale_api.py.txt
While running the python file, I got the below error. Please help.
Traceback (most recent call last):
File "D:\project\GenAI\ComfyUI\ComfyUI-to-Python-Extension\workflow_image_upscale_api.py", line 227, in
main()
File "D:\project\GenAI\ComfyUI\ComfyUI-to-Python-Extension\workflow_image_upscale_api.py", line 164, in main
init_builtin_extra_nodes()
File "D:\project\GenAI\ComfyUI\ComfyUI-to-Python-Extension\workflow_image_upscale_api.py", line 144, in init_builtin_extra_nodes
if not load_custom_node(
^^^^^^^^^^^^^^^^
NameError: name 'load_custom_node' is not defined

What version of ComfyUI-to-Python-Extension were you using to get this output? Was it a fork of this repo? I don't think it is possible to get the output you provided from a version of the repo I maintain.
The init_builtin_extra_nodes() should have never been defined within the script developed by the extension. That function comes from the nodes directory in ComfyUI.


Error: Got error while parsing Fastfile

Hi there!
After install this extension and reload my vscode, the error below is always showing:

Only this notification is displayed. I tried to see a detailed message error on vscode Output tab, but there isn't a pane for this extension there 😞
I just did a simple fastlane init command, that generates the Fastfile below:
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:android)

platform :android do
 desc "Runs all the tests"
 lane :test do
   gradle(task: "test")
 end

 desc "Submit a new Beta Build to Firebase App Distribution"
 lane :beta do
   gradle(task: "clean assembleRelease")
   firebase_app_distribution

   # sh "your_script.sh"
   # You can also use other beta testing services here
 end

 desc "Deploy a new version to Google Play"
 lane :deploy do
   gradle(task: "clean assembleRelease")
   upload_to_play_store
 end
end

Hi! Are you on windows?

Hi! Are you on windows?

@smsimone Yes, I am 😅

@mfdeveloper it was a problem given by how windows handles the paths
the version 0.1.2 which addresses this issue is now in verify, it will be soon available on the marketplace, thank you!

Hi @smsimone, thank you so much for you attention on this issue.
I tested right now, but unfortunately the error still persists 😢
The downloaded version from marketplace is: v0.2.0. Is that actual fixed version?

Hi @mfdeveloper, I'm adding the output on the output panel right now, I hope to deliver it by tonight

@mfdeveloper the new update should've been deployed on the store, can you check again?

@smsimone Sorry for my late reply. I saw your message only right now.
Follow my stacktrace error below:
ℹ: Found a single fastfile at path: file:///d%3A/projects/fastlane-project-test/fastlane/Fastfile
ℹ: Made some magic on the path to make it windows like. New path: d:\projects\fastlane-project-test\fastlane\Fastfile
⛔: Got error while creating tree view: Error: No lanes found
⛔: Error: No lanes found
	at Object.parseFastfile (%HOME%\.vscode\extensions\smsimone.fastlane-launcher-0.2.1\out\parser.js:19:15)
	at populateView (%HOME%\.vscode\extensions\smsimone.fastlane-launcher-0.2.1\out\extension.js:191:27)
	at %HOME%\.vscode\extensions\smsimone.fastlane-launcher-0.2.1\out\extension.js:177:17
	at Generator.next (<anonymous>)
	at fulfilled (%HOME%\.vscode\extensions\smsimone.fastlane-launcher-0.2.1\out\extension.js:5:58)

Seeing this error message, maybe you should replace the Windows backslash " \ " by a simple slash" / ", no ?
By the way, what do you think to label the Output panel with the display name, like the others extensions?

Analyzing this error message, maybe you should replace the Windows backslash \ by a simple slash /, right ?

Nope, on windows the right path is given by the backslashes, quite awful but that's it
Regarding the error Error: No lanes found, it's because right now the extensions looks for lines that starts with the regex ^(private_)lane, so the lane have to be put at the start of the line to be found. In your case, you're wrapping them in a platform section, which is indenting them inside by one tab
As a temporary workaround you could take them outside the platform section or align them on the left side

Hi @smsimone !
I tried the both workarounds that you suggested, but I'm still seeing the error: ⛔: Error: No lanes found 😢
Could you please try do that in your machine, with the Fastfile below?

# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

desc "Runs all the tests"
lane :test do
  gradle(task: "test")
end

desc "Submit a new Beta Build to Firebase App Distribution"
lane :beta do
  gradle(task: "clean assembleRelease")
  firebase_app_distribution

  # sh "your_script.sh"
  # You can also use other beta testing services here
end

desc "Deploy a new version to Google Play"
lane :deploy do
  gradle(task: "clean assembleRelease")
  upload_to_play_store
end

Hi @mfdeveloper! I've been busy with work and I managed to fix it now, as you update to version 0.2.2 it should be working

Hi @smsimone !
Thanks a lot for your attention to solve that issue.
Yaaaay, now it works, even though using platform section !!! 🥳🎉

Additionally, I would like to suggest some extra changes:

[ ] When click on lane, what do you think that select it instead of run ? Thus, you can add a context menu action to run and/or a keyboard shortcut.

[ ] When runs a lane, could you prefix the fastlane command with bundle exec ? This is recommended on terminal output

$ fastlane test
[✔] 🚀
[16:19:54]: fastlane detected a Gemfile in the current directory
[16:19:54]: However, it seems like you didn't use `bundle exec`
[16:19:54]: To launch fastlane faster, please use
[16:19:54]:
[16:19:54]: $ bundle exec fastlane test
[16:19:54]:
[16:19:54]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile

[ ] Could you add meaningful icons for each kind of lane, like Gitlens extensions does?

e.g lanes that starts or ends with _test, contains "publish, deploy, alpha, beta..." in lane name...

Maybe we can create one or more issues to implement each one of that suggestions. What do you think?

If you could create an issue for each one would be nice! Anyway, regarding the second point, it's already implemented: you can write the command which will be called as you click on the lane in the settings


Sample dataset for spearman calculation

https://github.com/CamDavidsonPilon/lifelines/blob/master/lifelines/utils/__init__.py#L1074
takes a long time (n^2) for large datasets. It may be preferable to subsample the dataset if the row count is high.

https://github.com/CamDavidsonPilon/lifelines/pull/496/commits/108f3f8af9e730243611a694ccc443f773bd947c


Linkage cache can grow to gargantuan sizes, causing poor post-install linkage checker performance

Bug report

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
When running brew install, I've noticed for awhile that Homebrew appears to hang after the install itself completes. I eventually figured out that it does complete, but it can take upwards of 60 seconds to complete even when the actual installation itself completes in under a second. After discussing it with @claui, it looks like I'm not the only person experiencing this. The factor I identified that's the same between both of us is that our linkage cache has grown to absolutely gargantuan proportions. Mine was 10MB of JSON, and hers was 20MB.
At this point I'm quite positive that the linkage cache is the culprit, because deleting my cache and allowing it to be recreated results in a 30KB cache and brew install operations now complete instantaneously.
I ran brew prof --stackprof install blah, and as expected it looks like most of the time is being spent in CacheStoreDatabase-related tasks. In particular it looks like Formula#undeclared_runtime_dependencies is slow when the cache gets this large, and it ended up being called 73 times here. This gets called several frames down from check_broken_dependents, via Formula#runtime_installed_formula_dependents.
It feels more than a little ironic that caching can end up making things many times slower than not caching at all! If we're never cleaning this cache file, or not correctly cleaning it, it would explain how it managers to get so bloated over time.
Here's the profiling data: https://gist.github.com/mistydemeo/638f2390bc3c4597fd3cc386e2b64900
What happened (include command output)
The actual install process looks pretty much like normal; the user simply experiences a hang after the installed step, without any feedback that anything is happening.

Command output

==> Downloading http://old-releases.ubuntu.com/ubuntu/pool/universe/v/vcdtools/vcdtools_0.4.orig.tar.gz
Already downloaded: /Users/mistydemeo/Library/Caches/Homebrew/downloads/7c68e206d63c8b5145c7a8e365fea3ba770a3350684f4e6a84503fffa425e110--vcdtools_0.4.orig.tar.gz
==> make clean
==> make
🍺  /usr/local/Cellar/vcdtools/0.4: 6 files, 66.5KB, built in 5 seconds

What you expected to happen
Installations complete in a short amount of time.
Step-by-step reproduction instructions (by running brew commands)
Simply brew install any software, if your linkage cache is suitably large.
Output of brew config and brew doctor commands

HOMEBREW_VERSION: 2.5.0-49-gc06848c
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: c06848c48795904a39fb5a0114b6ddc7b49ccbf4
Last commit: 34 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 403b107e3272fcc1cc1ef78f6aeb07c2bb96fdd2
Core tap last commit: 4 days ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.dp4MCkVr4f/org.macosforge.xquartz:0
HOMEBREW_EDITOR: subl
HOMEBREW_MAKE_JOBS: 4
HOMEBREW_NO_AUTO_UPDATE: set
HOMEBREW_NO_INSTALL_CLEANUP: set
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: quad-core 64-bit broadwell
Clang: 11.0 build 1100
Git: 2.28.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 1.8.0_172
macOS: 10.14.6-x86_64
CLT: <IP_ADDRESS>.1.1562985497
Xcode: 11.3.1
XQuartz: 2.7.11 => /opt/X11

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed formulae were deleted!
You should find replacements for the following formulae:
  wine

@mistydemeo Was there things in the linkage cache which weren't present on your system? It sounds like things weren't being removed from the cache correctly. Also, could you and @claui upload your cache somewhere so I can play around with it locally? Thanks!

It sounds like things weren't being removed from the cache correctly.

Sounds like you're right, here's an example for youtube-dl:
$ cat ~/Library/Caches/Homebrew/linkage.json | jq 'keys' | grep youtube-dl
  "/usr/local/Cellar/youtube-dl/2019.04.17",
  "/usr/local/Cellar/youtube-dl/2019.04.24",
  "/usr/local/Cellar/youtube-dl/2019.04.30",
  "/usr/local/Cellar/youtube-dl/2019.05.11",
  "/usr/local/Cellar/youtube-dl/2019.05.20",
  "/usr/local/Cellar/youtube-dl/2019.06.08",
  "/usr/local/Cellar/youtube-dl/2019.06.21",
  "/usr/local/Cellar/youtube-dl/2019.06.27",
  "/usr/local/Cellar/youtube-dl/2019.07.02",
  "/usr/local/Cellar/youtube-dl/2019.07.12",
  "/usr/local/Cellar/youtube-dl/2019.07.14",
  "/usr/local/Cellar/youtube-dl/2019.07.16",
  "/usr/local/Cellar/youtube-dl/2019.07.27",
  "/usr/local/Cellar/youtube-dl/2019.08.02",
  "/usr/local/Cellar/youtube-dl/2019.08.13",
  "/usr/local/Cellar/youtube-dl/2019.09.01",
  "/usr/local/Cellar/youtube-dl/2<IP_ADDRESS>",
  "/usr/local/Cellar/youtube-dl/2019.09.28",
  "/usr/local/Cellar/youtube-dl/2019.10.16",
  "/usr/local/Cellar/youtube-dl/2019.10.22",
  "/usr/local/Cellar/youtube-dl/2019.10.29",
  "/usr/local/Cellar/youtube-dl/2019.11.05",
  "/usr/local/Cellar/youtube-dl/2019.11.22",
  "/usr/local/Cellar/youtube-dl/2019.11.28",
  "/usr/local/Cellar/youtube-dl/2019.12.25",
  "/usr/local/Cellar/youtube-dl/2020.01.01",
  "/usr/local/Cellar/youtube-dl/2020.01.15",
  "/usr/local/Cellar/youtube-dl/2020.01.24",
  "/usr/local/Cellar/youtube-dl/2020.02.16",
  "/usr/local/Cellar/youtube-dl/2020.03.01",
  "/usr/local/Cellar/youtube-dl/2020.03.06",
  "/usr/local/Cellar/youtube-dl/2020.03.08",
  "/usr/local/Cellar/youtube-dl/2020.03.24",
  "/usr/local/Cellar/youtube-dl/2020.05.03",
  "/usr/local/Cellar/youtube-dl/2020.05.08",
  "/usr/local/Cellar/youtube-dl/2020.05.29",
  "/usr/local/Cellar/youtube-dl/2020.06.06",
  "/usr/local/Cellar/youtube-dl/2<IP_ADDRESS>",
  "/usr/local/Cellar/youtube-dl/2020.07.28",
  "/usr/local/Cellar/youtube-dl/2020.09.06",

Have opened https://github.com/Homebrew/brew/pull/8695 to address/improve this in several ways.


fix go mod tidy for 1.13

Our plans to support go 1.13 are not ready. Are you able to use 1.12 still?
We will address 1.13 issues, but it's still rather new and currently not supporting it in this project.
This brings up a point that the README should be updated to indicate that 1.12 is the target still


ac:status macro not displaying text

When I try creating two different ac:status macros, one for yes (green) and one for no (red), the Title is not correct.
<!-- Macro: :yes:
     Template: ac:status
     Title: Yes
     Color: Green -->

<!-- Macro: :no:
     Template: ac:status
     Title: No
     Color: Red -->

Try:
<!-- Macro: :yes:
     Template: ac:status
     Title: "Yes"
     Color: "Green" -->

<!-- Macro: :no:
     Template: ac:status
     Title: "No"
     Color: "Red" -->


dsa/dsa_gen: add error message for seed_len < 0

prio openssl 1.1.0 seed_len < q was accepted and the seed argument was
then ignored. Now DSA_generate_parameters_ex() returns an error in such
a case but no error string.
Signed-off-by: Sebastian Andrzej Siewior<EMAIL_ADDRESS>

Please make this a PR not an issue.
Please do a CLA.

Can we add error codes to release branches?
Please sign our CLA.

Just sent the CLA.
The error code probably helps to track down the issue. Is there any problem with assigning new error codes to the release branches?

Thanks for the CLA.  New error codes should be okay.

The Need CLA flag could go now. Is there anything else missing?

What branches are you targeting for this? We need to make sure the error codes are consistent across master/1.1.0.

I suggest we do this to 1.1.0, run make errors, then submit, then cherry-pick that patch FORWARD to master.  @mattcaswell , your thoughts?

It is better to do it the other way around, i.e. put it on master first. There are likely to be error codes used in master that are not used in 1.1.0. If you do it to 1.1.0 first then you might end up with one already allocated in master.

@mattcaswell i'll do it the way you said; can you plus-one this?

@richsalz to merge.

commit af54741 in master; commit 83b90e4 in 1.1.0  thanks!


docs: improved provider hints section

This is based on some suggestions from @hsanjuan

@lidel : are we good to merge given Hector approval?