ADC impedance is exteremely low

Hi,
I was working with the ADC, i just found out the input impedance is very low.
when i connected 3v3 to ADC through a 1k resistor, the adc readout is about 3.0v but without resistor it reads ~3.3v. with 10k and 100k resistor the readings are lower respectively. very much like there is a pull down resistor somewhere in the path.
After some search just seen this thread which had exactly same problem.
Seems the fix for this problem is to initialize the connected pin as input (please check the link above).
Thanks.

Good tip, thanks. Being an active user of rp2daq in a lab I also noticed there is some 30kohm pull down, which is however not a problem when reading the output of a buffering opamp. I will check out the pin config effect in the next weeks.
-------- Původní zpráva --------
22. 7. 2024 12:03, Ehsan M.A. napsal/a:

Hi,
I was working with the ADC, i just found out the input impedance is very low.
when i connected 3v3 to ADC through a 1k resistor, the adc readout is about 3.0v but without resistor it reads ~3.3v. with 10k and 100k resistor the readings are lower respectively. very much like there is a pull down resistor somewhere in the path.
After some search just seenthis thread which had exactly same problem.
Seems the fix for this problem is to initialize the connected pin as input (please check the link above).
Thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I did some tries with gpio_highz but still same problem.
did try with multiple resistors and this is values:
adcVref ----- RESISTOR -----  GPIO28

RESISTOR (KOhm)
V (Adc/4096*3.3)

0.018
3.29

0.075
3.29

0.22
3.28

0.33
3.27

1
3.17

4.7
3.01

10
2.74

33
1.63

51
1.15

75
0.85

100
0.7

175
0.415

390
0.22

499
0.19

Very much like there is a ~28KOhm pulldown at adc pin

Yeah, I can confirm it in my setup. I was going to conclude this is an internal limitation of RP2040, but on page 561 of the RP2040 docs they write:

"The effective impedance, even when sampling at 500ksps, is over 100kΩ, and for DC measurements there should be no need to buffer."

So more research is justified. The only apparent difference from the official ADC example is that they call adc_init() before adc_gpio_init(...). Not sure this makes the difference, and I will have to check this example has higher input impedance at all. Will get back to you soon, I hope.

thanks,
i was trying to validate official ADC example, successfully compiled it into .uf2 and uploaded to pico. but were not able to see the data from pico, because no COM port appeared on my pc...
Do you think the official pico example have low impedance problem?!

So connecting a simple kΩ-meter between pin 26 (i.e. ADC0 input) to board ground, I could get following figures:

RP2 just disconnected: ~15 MΩ
pristine RP2 without flash program, but powered up: 24.4 kΩ
RP2 with rp2daq firmware running, no ADC conversion:  24.4 kΩ again
RP2 with rp2daq firmware running, 50ksps ADC conversion active:  21.6 kΩ

So your issue is fully reproducible. Then I made an experiment, changing the ADC&pin initialization like this:
    adc_init();
	for (uint8_t ch=0; ch<4; ch++) {
        if (iADC_config.channel_mask & (1<<ch))
            adc_gpio_init(26+ch);
            gpio_set_dir(26+ch, GPIO_IN); // not necessary here?
            gpio_disable_pulls(26+ch); // sets the input into high-z state again
    }

... et voilà, the pin got some >200MΩ impedance, yet it seems to measure voltage correctly. I will have to test this thoroughly yet, but the problem seems resolved. I learned something new, too. Thanks for reporting.
The commit is 8a678eb. Since you started your oscilloscope, the binary messaging between rp2daq board and computer has changed several times. I guess you wish to continue with your custom C# oscilloscope software - this will require manually patching only the include/adc_builtin.c file of your chosen firmware version, and recompiling/uploading without any further changes to the codebase. Or - you may switch to latest firmware and upload it, but then check carefully your hardwired C# communication routine does not fail in this case.

So connecting a simple kΩ-meter between pin 26 (i.e. ADC0 input) to board ground, I could get following figures:
* RP2 just disconnected: **~15 MΩ**

* pristine RP2 without flash program, but powered up: **24.4 kΩ**

* RP2 with rp2daq firmware running, no ADC conversion:  **24.4 kΩ** again

* RP2 with rp2daq firmware running, 50ksps ADC conversion active:  **21.6 kΩ**

So your issue is fully reproducible. Then I made an experiment, changing the ADC&pin initialization like this:
    adc_init();
	for (uint8_t ch=0; ch<4; ch++) {
        if (iADC_config.channel_mask & (1<<ch))
            adc_gpio_init(26+ch);
            gpio_set_dir(26+ch, GPIO_IN); // not necessary here?
            gpio_disable_pulls(26+ch); // sets the input into high-z state again
    }

... et voilà, the pin got some >200MΩ impedance, yet it seems to measure voltage correctly. I will have to test this thoroughly yet, but the problem seems resolved. I learned something new, too. Thanks for reporting.
The commit is 8a678ebf. Since you wrote your oscilloscope app with hard-wired messaging, the binary protocol between rp2daq board and computer has changed several times. If you really wish to continue with your custom C# oscilloscope software, it will require manually patching only the include/adc_builtin.c file of your chosen firmware version, and recompiling/uploading without any further changes to the codebase. Or - you may switch to latest firmware and upload it, but then check carefully your hardwired C# communication routine does not fail in this case.

Thanks, really happy that problem is solved :)
Actually it was somehow hard to understand how rp2daq's API works, it is kind of automated. i finally ended up deriving a custom serial class from python's serial and replace it in the rp2daq.py and usb_backend_process.py to see what is going on under the hood. without this reporting serial i was not able to use all functions.
import serial
import binascii

class SYM1(serial.Serial):
    def __init__(self, *args, debug=None, baudrate=4800, timeout=1, **kwargs):
        super().__init__(*args, baudrate=baudrate, timeout=timeout, **kwargs)
        print('using port', self.port)

    def read(self, count):
        print('reading',count)
        retval = super().read(count)
        print(binascii.hexlify(bytearray(retval)))
        return retval;

    def write(self, data):

        print('writing',len(data))

        print(binascii.hexlify(bytearray(data)))

        return super().write(data)

    def connect(self):
        return super().connect()

and inside usb_backend_process.py line 52 replaced:
port = serial.Serial(port=port_name.device, timeout=None)

with
port = snifferSerial.SYM1(port=port_name.device, timeout=None)

Then it simply shows raw bytes on each command on the console.
Anyways thanks for the great work!

i think you didn't pushed the commit yet.

You are right, I will push it ASAP but I am not at the right computer. But the sufficient fix is posted above.
Thanks again.

yes, i actually did update the code and with new code it look extremely fine!
Thank you


fix(datastore): stop sync engine on non-retryable errors to allow restart

Issue #, if available:
Description of changes:
When the app is placed in the background for an extended period of time, the subscriptions get severed. This causes the sync engine to transition its state to cleanUp(error), and then scheduleRestartOrTerminate. Since the subscription error isn't handled as a retryable network error, the sync engine transitions to a terminal state. If the sync engine can accurately check the error from its downstream components as a retryable network error, then it can also perform the restart of the sync steps. For this fix, we aren't addressing whether the subscription error should be handled as a retryable or non-retryable error at the moment, and generalize this problem to handling non-retryble errors and provide a fix for this scenarios.
One of the problems we fixed recently had to do with treating all non-retryable errors as retryable, and sync engine would restart continuously, causing a retry storm on AppSync, getting limit exceeded / throttled (https://github.com/aws-amplify/amplify-ios/pull/1773). From this experience, we do not want to immediately restart the sync engine for non-retryable errors. Non-retryable errors will put the sync engine through a clean up step that stops the outgoing mutation queue and deinits the reconciliation queue, decides not to reschedule a restart, followed by sending the publisher's terminating completion event, putting the sync engine in a terminal state.
The completion event is handled by the storage engine, which then also sends a terminating completion event back up to the DataStorePlugin. DataStorePlugin logs the error. DataStorePlugin's operates on the storage engine by creating a new instance when it's started, and deinits it when it's stopped/cleared. This means that all subsequent operations will think that the storage engine is available despite it being in terminal state.  models and outgoing mutation event continue to be saved to local store with the storage adapter and mutation events injester. but none of the mutation events get synced to the cloud.
The fix here is for DataStorePlugin to stop the storage engine (in turn stops the sync engine and dereferences storage engine) when it receives a terminating event from the storage engine. This way, the non-retryable errors are not immediately retried. When a DataStore operation is performed at a later time, such as a save or a query, it will check if storage engine is there, if not it will create the storage engine and start the sync process. This avoids immediately/continuous retry when it encounters non-retrable errors, and allows the app to recover (for example, sync process goes through steps such as delta sync to get the latest data), without having the end-user or developer intervene by restarting the app or making calls to stop/clear/start on app lifecycle events like foregrounding.
Check points: (check or cross out if not relevant)

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1901 (1b0b1ab) into main (71782aa) will decrease coverage by 0.00%.
The diff coverage is 53.33%.

@@            Coverage Diff             @@
##             main    #1901      +/-   ##
==========================================
- Coverage   59.38%   59.38%   -0.01%
==========================================
  Files         715      715
  Lines       22056    22069      +13
==========================================
+ Hits        13098    13105       +7
- Misses       8958     8964       +6

Flag
Coverage Δ

API_plugin_unit_test
62.51% <ø> (ø)

AWSPluginsCore
71.15% <ø> (-0.08%)
:arrow_down:

Amplify
47.05% <100.00%> (+0.12%)
:arrow_up:

Analytics_plugin_unit_test
71.09% <ø> (ø)

Auth_plugin_unit_test
78.67% <ø> (ø)

DataStore_plugin_unit_test
76.29% <0.00%> (-0.11%)
:arrow_down:

Geo_plugin_unit_test
52.12% <ø> (ø)

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...Configuration/AmplifyAWSServiceConfiguration.swift
73.91% <ø> (ø)

...WSDataStoreCategoryPlugin/AWSDataStorePlugin.swift
68.84% <0.00%> (-3.68%)
:arrow_down:

...ries/DataStore/Model/Temporal/Temporal+Cache.swift
80.55% <100.00%> (+1.76%)
:arrow_up:

...e/AWSPluginsCore/Auth/AWSAuthServiceBehavior.swift
75.00% <0.00%> (-12.50%)
:arrow_down:

...Plugin/Sync/Support/MutationEvent+Extensions.swift
80.95% <0.00%> (-2.39%)
:arrow_down:

.../DataStore/Model/Internal/Schema/ModelSchema.swift
66.00% <0.00%> (+2.00%)
:arrow_up:

...s/AWSHubPlugin/Internal/HubChannelDispatcher.swift
94.11% <0.00%> (+5.88%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Fix duplicate metabolites identified by ChEBI IDs

Main improvements in this PR:

As discussed in https://github.com/SysBioChalmers/Human-GEM/issues/627

change ChEBI ID annotations for MAM02679e, MAM02579c, MAM02579m, MAM02579e, MAM02579r, MAM02579n, MAM02579x, MAM02043c, MAM03887x
replace mets

old ID
new ID

MAM03231c
MAM03232c

I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Selected develop as a target branch
[X] Any removed reactions and metabolites have been moved to the corresponding deprecated identifier lists

This PR will be redeveloped by @JHL-452b


Better migration

During my work on allowed dependencies plugin I found a better way of distributing plugins.

Should probably drop eslint 8 for that


Add missing ""

Fixes pkg-config file generation on windows where CMAKE_SHARED_LIBRARY_PREFIX is empty.
Any background context you want to provide?
Always quote string like inputs to functions because they can be empty.
Checklist

[x] I have fixed a bug and have added a regression test. (just run with HPX_WITH_PKGCONFIG=ON on windows)

Can one of the admins verify this patch?

What problem does this patch solve?

Congratulations, your first PR to the HPX repository has just been merged! As a 'thank you' we offer a free STE||AR-Group t-shirt to all of our first-time contributors. If you are interested in receiving one, please get back to me directly so we can set up the delivery.


[stable/prometheus-mongodb-exporter] Redeploy pods on config changes.

Signed-off-by: Anas Ait Said Oubrahim<EMAIL_ADDRESS>Is this a new chart
No
What this PR does / why we need it:
Pods need to be redeployed when the config changes (secret.yaml in this case).
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign
/ok-to-test

/test pull-charts-e2e

/lgtm
Thanks!


feat(cli): if no out or json cmd, put out to ./docs

I not really happy with this solution but idk how do another way.
If you have an idea i'll be happy to implement it
Closes #746

I accept the modification (directly on github (didn't know it was possible ^^))

I'm not sure i ask: I cannot merge even if you (@aciccarello) approved no ?

I'm leaving it open in case someone else wanted to chime in. I'll merge before the next release.


Everyone warning picking up nicknames

The warning system trying to prevent people from attempting to @everyone is also picking up on people with the nickname 'everyone'

Although after discussing this with other people in discord and looking at the code, it might just be an issue on discords side

I'm not sure if the message that you're highlighting is the one that actually triggered this filter. The filter normally also removes the message in question and there's no error that says that the bot was unable to delete a message here. My working hypothesis is that this user sent two messages in a row: the first one (still there) had a member ping and the second one contained an actual everyone-ping.

Ah yeah that sounds more likely


update variable constraints dependency order

this should get us things like [yaxis], [xaxis], [overlay, facet]
resolves https://github.com/VEuPathDB/EdaDataService/issues/190
depends on https://github.com/VEuPathDB/EdaCommon/pull/20
may also resolve https://github.com/VEuPathDB/EdaDataService/issues/213
and obviate the need for https://github.com/VEuPathDB/EdaDataService/issues/119

@bobular maybe confirm the way ive set up the new dependency order makes sense to you as well? and works for front end dev?
@ryanrdoherty how does merging this work given the edacommon dependency? i imagine i should include a version update for the dependency somewhere in this pr?

@d-callan The steps would be to merge the EdaCommon PR to main and then release it, then update this PR with the new version.  But if you do that before the client is ready, we won't be able to add new stuff to main (e.g. the compute client stuff I'm working on).  Is the client stuff ready to go out too?

@ryanrdoherty maybe I'm just being dense but why can't we add stuff to main in that case

We can but it will break dev sites, right?

I'm just guessing after grepping some files, but would it be possible to add a temporary tag to the corresponding branch in https://github.com/VEuPathDB/EdaCommon/pull/20 - e.g. something like v9.3.0pre
Then update build.gradle.kts in this repo?
val edaCommon     = "9.3.0pre"         // EDA Common version

Then I might be able to get the eda-data service running locally via docker-compose magic?

Hi @d-callan
I think there could be an issue with the array of arrays representation.
When we are talking about stratification variables, we want this:
[["xAxisVariable"],["overlayVariable","facetVariable"]]
to mean "overlay and facet variables are both constrained by xAxisVariable, but not by each other"
This is how I initially interpreted it.
But when I did the same for contingency tables, which have this dependency order:
[["yAxisVariable","xAxisVariable"],["facetVariable"]]
I constrained y and x variables only to be on the same branch as each other, but not depend on each other in any specific order.
So this would allow
y-axis: participant sex
x-axis: household water availability

which of course the current live site does using the old approach.
and also the other way around:
y-axis: household water availability
x-axis: participant sex

But the back end doesn't allow this. It complains about the variables being the wrong way round in the hierarchy.
Are we going to change the back end to allow both "directions" (x-y, y-x) for contingency tables?
If we don't, then I need a way to know that
[["xAxisVariable"],["overlayVariable","facetVariable"]] doesn't mean facetVariable depends on overlayVariable
but in [["yAxisVariable","xAxisVariable"],["facetVariable"]] it DOES mean that xAxisVariable depends on yAxisVariable.
An alternative would be to use the old-style dependencies for cont tables, e.g.
[["yAxisVariable"],["xAxisVariable"],["facetVariable"]]

I think the backed needs updating too.

OK, cool. I've just implemented it back to the my original interpretation and it seems to be working well for stratification. :smile:


jax.numpy.tan call adds chlo.tan call to exported StableHLO; stablehlo.tan should be preferred

Description
Is this intended behavior? I would have expected stablehlo calls to be preferred to external ones when possible. Note that stablehlo.tan does exist.
>>> import jax.numpy as np
>>> f = lambda x: np.tan(x)
>>> import jax
>>> jit_f = jax.jit(f)
>>> lowered = jit_f.lower(1.0)
>>> print(lowered.compiler_ir("stablehlo"))
module @jit__lambda_ attributes {mhlo.num_partitions = 1 : i32, mhlo.num_replicas = 1 : i32} {
  func.func public @main(%arg0: tensor<f32> {mhlo.layout_mode = "default"}) -> (tensor<f32> {jax.result_info = "", mhlo.layout_mode = "default"}) {
    %0 = chlo.tan %arg0 : tensor<f32> -> tensor<f32>
    return %0 : tensor<f32>
  }
}

System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.31
jaxlib: 0.4.30
numpy:  2.0.0
python: 3.12.4 (main, Jun  6 2024, 18:26:44) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
jax.devices (1 total, 1 local): [CpuDevice(id=0)]
process_count: 1
platform: uname_result(system='Darwin', node='LUSM493FC90MM', release='23.6.0', version='Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030', machine='arm64')

I suspect that stablehlo.tan was added after that code was written. Do you want to send a PR switching it to stablehlo? It should be a tiny change.

Sure, I'll give it a go.

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Created a pull request: https://github.com/google/jax/pull/23261/files Feel free to review @hawkinsp

FWIW,
(.jax) ➜  jax git:(stablehlo.tan) python
Python 3.12.4 (main, Jun  6 2024, 18:26:44) [Clang 15.0.0 (clang-15<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import jax.numpy as np
>>> f = lambda x: np.tan(x)
>>> import jax
>>> jit_f = jax.jit(f)
>>> lowered = jit_f.lower(1.0)
>>> print(lowered.compiler_ir("stablehlo"))
module @jit__lambda_ attributes {mhlo.num_partitions = 1 : i32, mhlo.num_replicas = 1 : i32} {
  func.func public @main(%arg0: tensor<f32> {mhlo.layout_mode = "default"}) -> (tensor<f32> {jax.result_info = "", mhlo.layout_mode = "default"}) {
    %0 = stablehlo.tan %arg0 : tensor<f32>
    return %0 : tensor<f32>
  }
}

I've signed the CLA, not sure how to re-trigger the corresponding check (which failed initially).


Response is slow when caching mechanism is used

I was noticing, from my own tests, that when apollo client is set up with caching, getting the response was considerably slower than when there was no caching policy.
Is the client currently caching the data first before serving the data? And if so, why does it have this policy instead of serving the data first and then caching?

Is it normalized cache you refer to?
And could you pls provide some metrics?

Yes, it happens when using normalized cache.
For a query returning around 50 items, which in turn had sub fields(4~6), the time was 2~4 secs per item.
When using http cache, the time was 0.5 sec for an item or sometimes less than 0.5 sec also.
Thanks!

Any chance you can do a trace and send it over. I can then analyze and optimize wherever the issue is.

One more question, what kind of cache? SQLlite or just mem?

Using this,
        SqlNormalizedCacheFactory secondaryCache = new SqlNormalizedCacheFactory(apolloSqlHelper);
        NormalizedCacheFactory normalizedCacheFactory = new LruNormalizedCacheFactory(EvictionPolicy.NO_EVICTION)
                .chain(secondaryCache);```

@digitalbuddha how to capture the trace? just logs ?

Easiest is by using the debug options. Somewhere before and after the apollo call Pls put
// start tracing
Debug.startMethodTracing("calc");
// ...
// stop tracing
Debug.stopMethodTracing();

This will generate a  `calc.trace' file and saves it to your phone. You can see the location in Adb logs. Next pull this file from Adb.

You may also need to add <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

My trace files are usually found by

cd /storage/emulated/0
find -name *.trace```
Here are the official docs on how to generate and pull the file. https://developer.android.com/studio/profile/generate-trace-logs.html
This would go a long way in us fixing the implementation. Thank you for working with us.

Try the snapshot version should be much faster

@sav007 Thanks for the update.
when is the next release ?


Error: panic: runtime error: invalid memory address or nil pointer dereference

I'm getting this error when running npm start on a newly cleaned app. I suspect it is due to not properly configuring nginx but I'm not sure and am not using nginx to host it. If so is there a way to disable it?
Error: panic: runtime error: invalid memory address or nil pointer dereference

github.com/inconshreveable/olive/recover.go:40
runtime/asm_amd64.s:403
reflect/value.go:419
reflect/value.go:296
github.com/codegangsta/inject/inject.go:102
<autogenerated>:30
<autogenerated>:132
github.com/inconshreveable/olive/recover.go:29
runtime/asm_amd64.s:401
runtime/panic.go:387
github.com/inconshreveable/olive/error.go:37
runtime/asm_amd64.s:401
runtime/panic.go:387
runtime/panic.go:42
runtime/sigpanic_unix.go:26
lib/tunnel/client/reconnecting.go:42
lib/tunnel/client/session.go:97
ngrok/tunnel_session.go:129
ngrok/web_api.go:95
runtime/asm_amd64.s:403
reflect/value.go:419
reflect/value.go:296
github.com/codegangsta/inject/inject.go:102
<autogenerated>:30
github.com/go-martini/martini/router.go:373
github.com/go-martini/martini/router.go:367
github.com/inconshreveable/olive/error.go:41
runtime/asm_amd64.s:403
reflect/value.go:419
reflect/value.go:296
github.com/codegangsta/inject/inject.go:102
<autogenerated>:30
github.com/go-martini/martini/router.go:373
github.com/go-martini/martini/router.go:367
github.com/inconshreveable/olive/recover.go:32
runtime/asm_amd64.s:403
reflect/value.go:419
reflect/value.go:296
github.com/codegangsta/inject/inject.go:102
<autogenerated>:30
github.com/go-martini/martini/router.go:373
github.com/go-martini/martini/router.go:367
github.com/inconshreveable/olive/logger.go:17
runtime/asm_amd64.s:403
reflect/value.go:419
reflect/value.go:296
github.com/codegangsta/inject/inject.go:102
<autogenerated>:30
github.com/go-martini/martini/router.go:373
github.com/go-martini/martini/router.go:250
github.com/go-martini/martini/router.go:120
ngrok/src/ngrok/web.go:25
runtime/asm_amd64.s:403
reflect/value.go:419
reflect/value.go:296
github.com/codegangsta/inject/inject.go:102
github.com/go-martini/martini/martini.go:173
github.com/go-martini/martini/martini.go:69

We don't use nginx at all, we have an express.js server running in the background.
Due to this highly likely being a problem with your local setup and nothing we can fix from our side, I'll close this issue for now! Feel free to continue the discussion though.

hmm it's a newly initialized and cleaned app though. I really only ran npm run setup and then npm run clean. Any setup problems I should look out for?

Hm, we fixed one yesterday so maybe try cloning and setting up again?

I'm only using an express server and i'm running into the same issue.

@Globolobo Please describe the command sequence you are using to reproduce the error.
Do you see all the .go files as in the OP? These are not part or react-boilerplate, could this be a GitHub error not related to react-boilerplate?
I run:
git clone ...
cd react-boilerplate
npm start (get example app on localhost)
npm clean
npm start (get "This is the Homepage" on localhost)

@gihrig thanks for the quick response! As I mentioned before it's an ngrok issue, they're aware of it but haven't tackled it yet (which is a dependency for boilerplate)
As far as seeing the same errors as OP, yea, i'm seeing the exact same ones.
I'm running an older version of boilerplate that had ngrok running by default on the server. So in order to reproduce the issue with the current boilerplate version, you need to set the "ENABLE_TUNNEL" enviro variable to true.
the steps i did are:
git clone ...
cd react-boilerplate
npm install
export ENABLE_TUNNEL="true"
npm start

So this issue ONLY affects people that need to enable the tunnel, or people that were using the previous version of the boilerplate when ngrok was default.

@Globolobo Thanks for the clarification!
FWIW, npm run start:tunnel and export ENABLE_TUNNEL="true" both work as expected with the current react-boilerplate.
Thanks for your contribution 😃


Add some stability to the core library logic

Codecov Report

Merging #17 into master will decrease coverage by 8.67%.
The diff coverage is 90.76%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   95.54%   86.86%   -8.68%
==========================================
  Files          19       19
  Lines         673      769      +96
==========================================
+ Hits          643      668      +25
- Misses         30      101      +71

Flag
Coverage Δ

#integration
?

#unit
86.86% <90.76%> (-0.36%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


Live Reload for development

Sounds good. How about using gulp in dev environment, to manage the build process? Just as a reference, heres the gulpfile for the project ive been working on lately. https://github.com/whoisandie/yoda/blob/master/gulpfile.js

That's interesting - will have to move from grunt to gulp but that's ok. Currently testing a new version with some major features(sounds and native notifications) so will set for next release!

Sounds good 👍

Tried webpack but had issues with octicons so I sticked back to gulp & browserify. Will close this one for now.


In C++ allow messages that compress to <5mb to be sent with batching enabled

Motivation
The current behavior when publishing big messages (>5MB) is to allow them if they fit in the 5MB range after compression. This is currently applied only when batching is disabled.
Adding support for same behavior when batching is enabled.

run cpp tests

Merged in 2.3.1 at
ec850a7


BracesFixer must be run before NoTrailingWhitespaceInCommentFixer

I think the conflict goes away with https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3820 , maybe someone can review it?

replaced by https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3820


New Step to Create Release Definition

There is a new step in between when creating release definitions

Potential duplication of #126


Make fixes

This pull request fixes #292 and finishes the work started in #291 to fix #270.
It completes the work started in #291 to move the container build and push to the rootfs directory and removes the dockerfiles and makefiles for the directories under cmd, which are no longer needed, since the only thing they added to the go build and test was container build and push.
@adamreese PTAL.

After decluttering the top level directory, I am uncomfortable with putting shell scripts at the top level. Can we put the start/stop shell scripts in either scripts/ or hack/?

Not sure I understand the make targets.  For example what is the command now if I want to build an image and push to my account at quay.io/adamreese/

@technosophos Good catch.

@adamreese it's no different from what it was. Just factored out the common parts into an include. The definitions are unchanged.
To push to quay.io/adamreese/, you would set DOCKER_REGISTRY to quay.io


Question: Have you tried this with a CloudWatch logging appender?

Hello & thanks for the great work! I'm having difficulties getting an executable Spring Boot jar to run from the CLI (Linux & Mac OSX) when using one of two CloudWatch appenders with LogBack.
Note I'm using your 4th method with the fluent SpringApplicationBuilder & StandardEncryptableEnvironment approach, and running this with -Djasypt.encryptor.password={blah} as an argument.

In the first case using the j256 appender I see the following when starting the app:

18:13:34,608 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [com.j256.cloudwatchlogbackappender.CloudWatchAppender]
18:13:34,610 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CLOUDWATCH]
18:13:34,610 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [EMERGENCY_FILE] to com.j256.cloudwatchlogbackappender.CloudWatchAppender[CLOUDWATCH]
18:13:34,640 |-INFO in ch.qos.logback.core.hook.DelayingShutdownHook@7e7dec46 - Sleeping for 0 milliseconds
18:13:34,640 |-INFO in ch.qos.logback.core.hook.DelayingShutdownHook@7e7dec46 - Logback context being closed via shutdown hook

...and that's as far as it gets, then stops.

In the second case using Pierre David Belanger's appender I got it to work by writing a custom ApplicationListener which reads the encrypted AWS credentials & sticks them into system properties where the AWS client code can find them.

I prefer the j256 appender personally, as it allows for manually setting the AWS credentials using the springProperty tag which your library supports, and has an overflow file appender option.
I created a minimal Spring Boot app which confirms this. Please let me know if you need any more info.

Do you have the sample code in github for me to take a look?
From the j256 appender docs:

You can also set the cloudwatchappender.aws.accessKeyId and cloudwatchappender.aws.secretKey Java System properties which will be used. If neither of those are specified then the appender will use the DefaultAWSCredentialsProviderChain which looks for the access and secret keys in:
Environment Variables: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY or AWS_ACCESS_KEY and AWS_SECRET_KEY
Java System Properties: aws.accessKeyId and aws.secretKey
Credential file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI
Instance profile credentials delivered through the Amazon EC2 metadata service

You can set your credentials in a few different ways instead of using logback.xml although, as you mentioned, jasypt-spring-boot supports encrypted properties in logback.xml with the help of spring properties.
<springProperty name="accessKeyId" source="accessKeyId"/>
<springProperty name="secretKey" source="secretKey"/>
<appender name="CLOUDWATCH" class="com.j256.cloudwatchlogbackappender.CloudWatchAppender">
    ...
    <accessKeyId>${accessKeyId}</accessKeyId>
    <secretKey>${secretKey}</secretKey>
</appender>


ValueError: Invalid Literal for int() with base 0

Hi! Thanks for updating. The error does not happen anymore. However, now I am getting a ValueError: invalid literal for int() with base 0. This happens both when I input the key in hex and input the key in ASCII. Is it that my key is wrong?
Originally posted by @brian-vb in https://github.com/donmai-me/MaiConverter/issues/7#issuecomment-968523789

Did you prepend your hex key with 0x?
The command should be something like this (notice the 0x before the example key in hex):
maiconverter encrypt /path/to/chart.sdt --key 0xFEDCBA987654321

Yes I did prepend the hex key with 0x and is saved in a file called key.txt

Why do you mention a file named key.txt? The key parameter should only be a hex literal (0-9 A-F). I'm not sure if you're giving the path to your key.txt file but key parameter doesn't accept file paths.

Oh I see! I have just input the Hex Key without the file and it now shows an Overflow Error where the integer is too big to convert. Thank you so much for your advice and really sorry to trouble you so much!
The command is now currently py -m maiconverter encrypt xxx.sdt --key (0xabcdef....)

That means your key is over 0x10 or 16 bytes which is the size of old maimai's chart key. Kindly check your key and make sure it's not mixed with other stuff like an IV.

That's strange. I am pretty sure the AES Key I have was from the Discord Server. Is there a way I can send my keys to you to see if I have the right ones? Thank you!

I copy-pasted keys and they all worked. If your hex key (without the 0x) is not 32 characters in length, then you have the wrong key.
Try asking for help in #support in MaiMai Tea Discord server. If you're not in, then the invite link is at README.md.

Alright! I will join the discord. Thank you!

Closing since the problem is not with the program.


Attempting to parse a Standard-format map in Valve mode temporarily locks the editor

Errors are spammed to the console for every face in the map, causing the editor to lock until they finish.
Ideally the distinction between valve-format UVs and everything else should be automatic, but the practical solution right now is to have the geo generation process cancel itself and print a warning to the user.

An 'automatic' format taking hints from TrenchBroom's .map header seems like a good compromise between advanced detection and basic user error prevention. Simply output a warning and fail to build if the header isn't present.
Still need to prevent an editor lock if a mis-parse happens though.

I've added automatic UV format recognition in the latest commit.
I'm shifting this task to generalized automatic parsing, since figuring out the bitmask format shouldn't be too big of a jump from here.

Since the bitmask values are stored at the end of each face and aren't used by the default Qodot implementation, I'm tempted to dump them all into an array and nix map format distinction entirely.

Implemented in the latest commit- QodotMapReader now parses any remaining params stored after texture scale as integer bitmasks and stores them in the bitmask_params property in QuakeFace.
This means Qodot doesn't have to care about the specifics of the format, but the data is parsed and available should a game-code implementation need it.


Jvenstad/remove cors

@bjorncs please review. I'll reopen against master if you approve.

Seems there is public interest in this.

The 5 first commits makes sense. We can keep the filters, but we should not use them ourself for the controller authorization filters.


fix: query-engine support for windows

Fixes resolution for query-engine in windows. When query-engine is resolved it doesn't look for the .exe extension so it won't resolve query-engine-windows. I've added a helper function to resolve the correct file.
I'm not sure what the best way to test this behavior. I copy-pasted this inside prisma2 and ran prisma2 generate and it worked.
Fixes https://github.com/prisma/prisma2/issues/585

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

@janpio Looks good to me too. I will test it once I have my setup ready on some windows.

Awesome! is there a good way to build prisma2 yourself instead of just copy-pasting it inside the compiled source XD

@wardpeet Yes, using this platforms syntax (), it will be soon renamed to binaryTargets.

@wardpeet Thanks again for raising this PR! 🙌
Curious to know how you are using Prisma! :)
Please feel free to DM me in our slack: slack.prisma.io


SecretStore Vault Kubernetes Auth failed with: an empty namespace may not be set when a resource name is provided

Hello,
I encountered an error within the SecretStore resource while using the Vault provider and Kubernetes authentication. I attempted to assign my custom certificate to the 'caProvider' field using the 'ConfigMap' type, resulting in the following issue:
Warning  InvalidProviderConfig  116s (x22 over 73m)  secret-store  cannot set Vault CA certificate: an empty namespace may not be set when a resource name is provided
When I include the 'namespace' field in caProvider block, I receive a validation error within the kubectl apply command:
error: secretstores.external-secrets.io "vault-remote-secretstore" could not be patched: admission webhook "validate.secretstore.external-secrets.io" denied the request: invalid Auth.Kubernetes.ServiceAccountRef: namespace not allowed with namespaced SecretStore
Related issue: https://github.com/external-secrets/external-secrets/issues/1024
Versions:
Kubernetes: v1.27.4
External-Secrets: v0.9.1
Vault: 1.14.0
Thank you for your reply!

Apologize! The mistake was probably on my side, as I left a namespace set in some other item too. I didn't notice.


Added option to count roads in statistics (#401)

@Atria1234 Thank you for the valuable PR (as always)! 🎉


Add java and C plus-plus courses with OOP and real projects

@MahmoudMiehob  this PR has conflicts, please solve them first


List All Wishlists of a Customer

As a customer
I want to view all my wishlists
So that I can easily manage and access the products I am interested in
Details and Assumptions
The request will include the customer's id.
Each customer can have multiple wishlists.
Acceptance Criteria
Given a customer with one or more wishlists
When a GET request is made to /customers/{customer_id}/wishlists
Then all wishlists associated with the customer should be retrieved from the database
And the list of wishlists should be returned in JSON format along with a 200 status


Quiche roll<PHONE_NUMBER>3554

Update QUICHE from b5824c589 to dd22dd1a7
https://github.com/google/quiche/compare/b5824c589..dd22dd1a7
$ git log b5824c589..dd22dd1a7 --date=short --no-merges --format="%ad %al %s"
2022-02-18 quiche-dev Migrates the underlying representation of QuicheLinkedHashMap from absl::node_hash_map to absl::flat_hash_map.
2022-02-17 quiche-dev Removes one pointer indirection from CallbackVisitor::StreamInfoMap.
2022-02-17 quiche-dev Adjusts internal OgHttp2Session state when sending SETTINGS_INITIAL_WINDOW_SIZE to the peer.
2022-02-17 wub Internal change
2022-02-17 wub Internal change
2022-02-17 quiche-dev Detects flow control window overflow and shuts down the stream or connection as appropriate.
2022-02-17 quiche-dev Updates OgHttp2Session's internal flow control window state when sending outbound WINDOW_UPDATE frames.
2022-02-17 quiche-dev Adds a WindowManager constructor parameter to disable automatic updates to internal window state.
2022-02-16 dschinazi Describe limitations of quic_enforce_single_packet_chlo flag
2022-02-16 renjietang Deprecate TLPR from crypto_protocol.h
2022-02-16 haoyuewang Internal change
2022-02-16 quiche-dev Extends WindowManager to handle the following new cases:   * one-time WINDOW_UPDATE frame increases the window beyond the persistent limit   * update to the persistent limit causes a window to become negative
2022-02-16 rch Fix typo in comment for QuicSelfIssuedConnectionIdManager
2022-02-16 quiche-dev Within WindowManager, changes the representation of flow control windows from size_t to int64_t.
2022-02-15 fayang Add a QUIC_PEER_BUG with more detailed information when self address changes at server.
2022-02-15 fayang Deprecate gfe2_reloadable_flag_quic_ignore_peer_max_ack_delay_during_handshake.
2022-02-15 wub Add constant kAddressTokenPrefix for the prefix of the source address token.
2022-02-15 vasilvv Provide default implementation for QUIC protocol flags.
2022-02-15 vasilvv Deprecate --gfe2_reloadable_flag_quic_match_ietf_reset_code
2022-02-14 vasilvv Provide default implementation for QUICHE flags
2022-02-14 quiche-dev Adds tests that demonstrate oghttp2's complete lack of reaction to flow control violations.
2022-02-14 fayang Deprecate gfe2_reloadable_flag_quic_drop_unsent_path_response.
2022-02-14 fayang Deprecate gfe2_reloadable_flag_quic_suppress_write_mid_packet_processing.
2022-02-14 fayang Deprecate gfe2_reloadable_flag_quic_donot_rearm_pto_on_application_data_during_handshake.
2022-02-14 bnc Public fix: Limit buffering on the QPACK encoder stream.
2022-02-11 quiche-dev Replaces if-else sequences with switch statements when handling SETTINGS identifiers.
2022-02-11 bnc Revert removal of some structured bindings and selection statements with initializers.
2022-02-11 quiche-dev Factors out a HandleOutboundSettings() method from the existing PrepareSettingsFrame() method.
2022-02-10 dschinazi Deprecate quic_ignore_key_update_not_yet_supported
2022-02-10 quiche-dev Fixes integer overflow in OgHttp2Session::UpdateInitialWindowSize().
2022-02-10 quiche-dev Makes the following changes to bring oghttp2_adapter_test.cc more in line with nghttp2_adapter_test.cc.
2022-02-09 quiche-dev Adds a using declaration for spdy::SpdyFrameType to nghttp2_adapter_test.cc, and uses the shorter name consistently in both oghttp2 and nghttp2 tests.
2022-02-09 quiche-dev Interprets SETTINGS_INITIAL_WINDOW_SIZE from the peer.
Risk Level: Low
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/lgtm deps

/assign @RyanTheOptimist

LGTM! Envoy main is locked for the release right now, but once the release happens and main is unlocked, I'll merge this.


Pads in adjacent cells too close when densely packed

When making a layout with a lot of devices, the pads end up awfully close together:

This wasn't an issue in previous layouts because they were sparser and the pads in adjacent cells ended up being offset from each other in the x-direction. When the x-locations are the same, though, there is simply not enough room. When wirebonding a layout like this there's a high risk of accidentally shorting an adjacent device's pads. It's probably fine, but it would stress me out.
I think there should be a Design-level option for building in padding between dies, not only for the edges of the chip.

Alternatively, could be solved with a cell-level parameter that moves pads away from the edges of cells.


question: API key generation fails (password length exceeds 72 bytes) : how to fix that ?

Hello,
I can't generate an API key through the auth portal, whenever I try I'm getting the following error :
FAIL: password generation error: bcrypt: password length exceeds 72 bytes

Is there something to configure somewhere that I'm missing ?
Thanks for your help!

@pav67 , that is a bug. There were recent changes to bcrypt library. Will fix and make a new release. Thank you for reporting this!

Any updates on this @greenpau? API Key Generation still seems to be broken in the current version.

@EntropyValley , I need to find some time to update this module.

@greenpau , I've created a dirty fix for this issue in a private repo. I'm not sure if it breaks anything or if there are security considerations I'm not aware of?
I've tested this locally and my fix allows authentication via X-Api-Key Header with ApiKeys generated via the local portal (diff for go-authcrunch - pkg:identity:database.go):
@@ -566,7 +566,7 @@ func (db *Database) AddAPIKey(r *requests.Request) error {
        if err != nil {
                return errors.ErrAddAPIKey.WithArgs(r.Key.Usage, err)
        }
-       s := GetRandomStringFromRange(72, 96)
+       s := GetRandomString(72)
        failCount := 0
        for {
                hk, err := NewPassword(s)

Since bcrypt now enforces a hard limit of 72 (non-unicode) chars, this fixes the issue.
If you don't see any issues with this, I can create a pull request. If not, let me know what I've overlooked and I might try to fix my patch?

@sdsys-ch , I would try looking at it this week.

@sdsys-ch , @pav67 , @EntropyValley , I added a fix for this. Will be available in the next release.

Appreciated! Great to see all the activity around caddy-security. Thanks

@sdsys-ch , thank you for the gift! Much appreciated 🎉

@pav67, @sdsys-ch , @EntropyValley , I am looking to add testimonial sections to https://authcrunch.com. Could you please write one and send it to me at<EMAIL_ADDRESS>


TST: Refactor to use new testing tools

I think we might have made a mix-up with tests/test_utils.py
There are functions that are testing daskml/utils.py (e.g. test_slice_columns, test_handle_zeros_in_scale). Others are functions that are utilities for writing tests (e.g. assert_estimator_equal)

Yep, I decided to throw the definition of assert_estimator_equal into tests/test_utils at the last moment, so that pytest's assertion rewriting would take place.
I found out afterwards that pytest lets you register specific modules for rewriting asserts. I'll make a PR tomorrow moving stuff so that the definition of assert_estimator_equal is in daskml/utils.py.


add cropping1d/2d/3d layers

This is a new feature that is being discussed in https://github.com/fchollet/keras/issues/3162. In this repo, https://github.com/keunwoochoi/keras_cropping_layer, I uploaded example code. I tested Cropping2D on theano/tensorflow, I haven't tested it on Cropping1D/3D yet. I would like to know if it makes sense to add this feature first before testing 1D/3D cases.
Some questions are:

Is the API okay? I think there should be some non-symmetric cropping cases. (At least I need it but I am not working on image, so..)
In Cropping1D, self.input_spec = [InputSpec(ndim=3)] exists in __init__(), but it seems like this layer needs overriding build()as below:

def build(self, input_shape):
        self.input_spec = [InputSpec(shape=input_shape)]

Does it mean that the line in __init__() should be removed?

It misses tests. LGTM otherwise.

There are three FAILs, which are,
[gw0] FAILED tests/integration_tests/test_temporal_data_tasks.py::test_temporal_classification <- keras/utils/test_utils.py
tests/integration_tests/test_temporal_data_tasks.py::test_masked_temporal <- keras/utils/test_utils.py

[gw0] FAILED tests/keras/backend/test_backends.py::TestBackend::test_ctc
tests/keras/backend/test_backends.py::TestBackend::test_one_hot

[gw1] FAILED tests/keras/layers/test_convolutional.py::test_atrous_conv_2d <- keras/utils/test_utils.py
tests/keras/layers/test_convolutional.py::test_averagepooling_2d <- keras/utils/test_utils.py

Tests are passing on Travis, so the issue is with your version of Theano.
On 18 August 2016 at 11:19, Keunwoo Choi<EMAIL_ADDRESS>wrote:

I ran the test and it fails at
keras/utils/test_utils.py:117:

tests/keras/layers/test_convolutional.py:154: in test_atrous_conv_2d
input_shape=(nb_samples, stack_size, nb_row, nb_col))

layer_cls = <class 'keras.layers.convolutional.AtrousConvolution2D'>
...

  assert expected_output_shape == actual_output_shapeE       assert (2, 2, 6, 2) == (2, 2, 8, 4)E         At index 2 diff: 6 != 8E         Full diff:E         - (2, 2, 6, 2)E         ?        ^  ^E         + (2, 2, 8, 4)E         ?        ^  ^

which I don't think is relevant to the part I added.
There are three FAILs, which are,
[gw0] FAILED tests/integration_tests/test_temporal_data_tasks.py::test_temporal_classification <- keras/utils/test_utils.py
tests/integration_tests/test_temporal_data_tasks.py::test_masked_temporal <- keras/utils/test_utils.py
[gw0] FAILED tests/keras/backend/test_backends.py::TestBackend::test_ctc
tests/keras/backend/test_backends.py::TestBackend::test_one_hot
[gw1] FAILED tests/keras/layers/test_convolutional.py::test_atrous_conv_2d <- keras/utils/test_utils.py
tests/keras/layers/test_convolutional.py::test_averagepooling_2d <- keras/utils/test_utils.py
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/pull/3509#issuecomment-240810299, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArWb63y8VjpJauU9dCP9bowaiTKLiCuks5qhKIkgaJpZM4JnJ1I
.

Is it ready now?
(PS. will group commits next time.
PPS. the test still fails after pip install keras --upgrade, on Mac, py2.7.)

LGTM. But a layer test is still necessary.

Okay. How does it work? Do you want me to add some code on test_convolutional.py?

Basically, yes, add one unit test per new layer in test_convolutional.
On 19 August 2016 at 10:58, Keunwoo Choi<EMAIL_ADDRESS>wrote:

Okay. How does it work? Do you want me to add some code on
test_convolutional.py
https://github.com/fchollet/keras/blob/2ac6811362aafdbf275c18d634ae6ba78cea406d/tests/keras/layers/test_convolutional.py?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/pull/3509#issuecomment-241089449, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArWbyMrZDc_iFbe2h7ECs0m85Cm0dmlks5qhe7MgaJpZM4JnJ1I
.

Finally, it passes all the tests. Sorry for many mistakes.

LGTM. Still a few minor touch-ups required, but otherwise it looks good to merge.

Hm....it's bit strange. Test has failed at some strange code.

Cool, LGTM. Thanks!


Can't use constant in python functions

I would like to also assign constants with code similar to:

import hal9 as h9

h9.dropdown("dropdown", on_update=lambda value: h9.set("dropdown", value), values=['x','y','World','Universe'], value='y')

h9.html("html", rawhtml=lambda: 'Hello World')


How to force update data

I'm using this to display mutable data, but when the data changes there is no way to force the inspector to show new values. If I collapse/expand the nodes, they update, but I want to show the changes immediately.
In my case, the object is linked to the entire app state, so cloning it is infeasible.

Perhaps you could use the ref attribute to get a reference to the mounted ReactNode and call forceUpdate on it?

Did you solve this? I've created a small example that shows how the ObjectInspector can be wrapped in a component that you manually forceUpdate when the object updates https://codesandbox.io/s/zk6lo7m473 .. and instead of passing the object, we pass a shallow copy.


fix import { $ } from 'module'

Thanks for your fixes. I will release the new version as soon as possible

@shiyiya I published. prelease try 0.06 version


@conda-forge-admin, please add bot automerge

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/icub-models-feedstock#22.


Build Errors

Hi
I'm trying to build from source to perform a more comprehensive tests as the current release version is causing all sorts of issues with 2.93.7 (e.g. I can no longer transform any object from the properties panel or directly, only through a transform node which needs to be filtered and then it's a mess on how to combine it back into the scene)
So, new windows 11 VM with:

Blender 2.93.7

Python 3.9.7 x64

numpy

requests

PyOpenGL

PySide2

Visual Studio 2017 Community

CMake 3.23

The build chugs along nicely and installs USD successfully, and I've added the paths recommended
adding c:\src\BlenderUSDHydraAddon\bin\USD\Install\lib\python to PYTHONPATH
adding c:\src\BlenderUSDHydraAddon\bin\USD\install\bin to PATH
adding c:\src\BlenderUSDHydraAddon\bin\USD\install\lib to PATH

Then it falls apart when trying to build hdRPR
-------------------------------------------------------------
Building HdRPR
-------------------------------------------------------------
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22000.
CMake Warning at cmake/defaults/ProjectDefaults.cmake:34 (message):
  Building USD on Windows is currently experimental.
Call Stack (most recent call first):
  CMakeLists.txt:10 (include)

-- Configuring usdview plugin
CMake Error at cmake/defaults/Packages.cmake:59 (find_program):
  Could not find USD_SCHEMA_GENERATOR using the following names:
  usdGenSchema.py, usdGenSchema
Call Stack (most recent call first):
  CMakeLists.txt:11 (include)

-- Configuring incomplete, errors occurred!
See also "C:/src/BlenderUSDHydraAddon/deps/HdRPR/build/CMakeFiles/CMakeOutput.log".
Traceback (most recent call last):
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 189, in <module>
    main()
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 171, in main
    hdrpr(bin_dir, args.G, args.j, args.clean)
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 96, in hdrpr
    _cmake(hdrpr_dir, compiler, jobs, [
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 78, in _cmake
    subprocess.check_call(['cmake', *build_args])
  File "C:\Users\User\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '-B', 'build', '-Dpxr_DIR=C:\\src\\BlenderUSDHydraAddon\\bin\\USD\\install', '-DCMAKE_INSTALL_PREFIX=C:\\src\\BlenderUSDHydraAddon\\bin\\USD\\install', '-DRPR_BUILD_AS_HOUDINI_PLUGIN=FALSE', '-G', 'Visual Studio 15 2017 Win64']' returned non-zero exit status 1.

The CMakeOutput.log doesn't show any errors so it's not helpful.
Any ideas?
Thank you

Try to install python module jinja2. In #198 we have updated README with new recommendations.

Hi @bnagirniak , thank you for the tip, but no bueno
I've tried a fresh build using VC 2019 as advised in #198 . I got far but not that far, after 36 GB of generated files I've reached this far:
-- Build files have been written to: C:/src/BlenderUSDHydraAddon/deps/HdRPR/build
Microsoft (R) Build Engine version 16.11.2+f32259642 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  Checking Build System
  Generating __init__.pyc
  Generating devicesConfiguration.pyc
  Building Custom Rule C:/src/BlenderUSDHydraAddon/deps/HdRPR/pxr/imaging/rprUsd/CMakeLists.txt
  Building Custom Rule C:/src/BlenderUSDHydraAddon/deps/HdRPR/pxr/imaging/rprUsd/CMakeLists.txt
  Building Custom Rule C:/src/BlenderUSDHydraAddon/deps/HdRPR/deps/CMakeLists.txt
  RadeonProRenderCpp.cpp
  tinyxml2.cpp
  cpprpr.vcxproj -> C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\deps\Release\cpprpr.lib
  Generating schema/api.h, schema/tokens.h, schema/rendererSettingsAPI.h, schema/objectSettingsAPI.h, schema/meshSettingsAPI.h, schema/materialSettingsAPI.h, s
  chema/domeLightSettingsAPI.h, schema/tokens.cpp, schema/rendererSettingsAPI.cpp, schema/objectSettingsAPI.cpp, schema/meshSettingsAPI.cpp, schema/materialSet
  tingsAPI.cpp, schema/domeLightSettingsAPI.cpp, schema/wrapTokens.cpp, schema/wrapRendererSettingsAPI.cpp, schema/wrapObjectSettingsAPI.cpp, schema/wrapMeshSe
  ttingsAPI.cpp, schema/wrapMaterialSettingsAPI.cpp, schema/wrapDomeLightSettingsAPI.cpp, schema/plugInfo.json, schema/generatedSchema.usda
  #################################################################################################
  #  USD_DISABLE_PRIM_DEFINITIONS_FOR_USDGENSCHEMA is overridden to 'true'.  Default is 'false'.  #
  #################################################################################################
CUSTOMBUILD : error :  [C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\pxr\imaging\rprUsd\rprUsdSchema.vcxproj]
          Error in 'pxrInternal_v0_21__pxrReserved__::PlugPlugin::_Load' at line 258 in file C:\src\BlenderUSDHydraAddon\deps\USD\pxr\base\plug\plugin.cpp : 'F
  ailed to load plugin 'usd': A dynamic link library (DLL) initialization routine failed.

   in 'c:/src/BlenderUSDHydraAddon/bin/USD/install/lib/usd_usd.dll''
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'C:
\src\BlenderUSDHydraAddon\deps\HdRPR\build\CMakeFiles\d793060c59b165284c5166b212fbd844\api.h.rule;C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\CMakeFiles\df04f
6ee9d0d9c6728cd8bed108836c2\rprUsdSchema.rule;C:\src\BlenderUSDHydraAddon\deps\HdRPR\pxr\imaging\rprUsd\CMakeLists.txt' exited with code 1. [C:\src\BlenderUSDH
ydraAddon\deps\HdRPR\build\pxr\imaging\rprUsd\rprUsdSchema.vcxproj]
Traceback (most recent call last):
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 189, in <module>
    main()
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 171, in main
    hdrpr(bin_dir, args.G, args.j, args.clean)
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 96, in hdrpr
    _cmake(hdrpr_dir, compiler, jobs, [
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 79, in _cmake
    subprocess.check_call(['cmake', *compile_args])
  File "C:\Users\User\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', 'build', '--config', 'Release', '--target', 'install']' returned non-zero exit status 1.

Any advise?
Next step is scrap everything and start again with 2017. All limbs crossed :)

Same issue with 2017
Building HdRPR
-------------------------------------------------------------
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22000.
CMake Warning at cmake/defaults/ProjectDefaults.cmake:34 (message):
  Building USD on Windows is currently experimental.
Call Stack (most recent call first):
  CMakeLists.txt:10 (include)

-- Configuring usdview plugin
-- C++ namespace configured to (external) pxr, (internal) pxrInternal_v0_21
-- Configuring done
-- Generating done
-- Build files have been written to: C:/src/BlenderUSDHydraAddon/deps/HdRPR/build
Microsoft (R) Build Engine version 15.9.21+g9802d43bc3 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  cpprpr.vcxproj -> C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\deps\Release\cpprpr.lib
  Generating schema/api.h, schema/tokens.h, schema/rendererSettingsAPI.h, schema/objectSettingsAPI.h, schema/meshSettingsAPI.h, schema/materialSettingsAPI.h, sc
  hema/domeLightSettingsAPI.h, schema/tokens.cpp, schema/rendererSettingsAPI.cpp, schema/objectSettingsAPI.cpp, schema/meshSettingsAPI.cpp, schema/materialSetti
  ngsAPI.cpp, schema/domeLightSettingsAPI.cpp, schema/wrapTokens.cpp, schema/wrapRendererSettingsAPI.cpp, schema/wrapObjectSettingsAPI.cpp, schema/wrapMeshSetti
  ngsAPI.cpp, schema/wrapMaterialSettingsAPI.cpp, schema/wrapDomeLightSettingsAPI.cpp, schema/plugInfo.json, schema/generatedSchema.usda
  #################################################################################################
  #  USD_DISABLE_PRIM_DEFINITIONS_FOR_USDGENSCHEMA is overridden to 'true'.  Default is 'false'.  #
  #################################################################################################
CUSTOMBUILD : error :  [C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\pxr\imaging\rprUsd\rprUsdSchema.vcxproj]
          Error in 'pxrInternal_v0_21__pxrReserved__::PlugPlugin::_Load' at line 258 in file C:\src\BlenderUSDHydraAddon\deps\USD\pxr\base\plug\plugin.cpp : 'Fa
  iled to load plugin 'usd': A dynamic link library (DLL) initialization routine failed.

   in 'c:/src/BlenderUSDHydraAddon/bin/USD/install/lib/usd_usd.dll''
Traceback (most recent call last):
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 189, in <module>
    main()
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 171, in main
    hdrpr(bin_dir, args.G, args.j, args.clean)
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 96, in hdrpr
    _cmake(hdrpr_dir, compiler, jobs, [
  File "C:\src\BlenderUSDHydraAddon\tools\build.py", line 79, in _cmake
    subprocess.check_call(['cmake', *compile_args])
  File "C:\Users\User\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', 'build', '--config', 'Release', '--target', 'install']' returned non-zero exit status 1.

Not sure why the DLL is not loading, could it be because of the VM?

@IRONIC3D did you install python jinja2 module for python3.9?
pip install jinja2

Hi @bnagirniak Yes I did, this is after I've installed jinja2
pip install jinja2
Requirement already satisfied: jinja2 in c:\users\user\appdata\local\programs\python\python39\lib\site-packages (3.0.3)
Requirement already satisfied: MarkupSafe>=2.0 in c:\users\user\appdata\local\programs\python\python39\lib\site-packages (from jinja2) (2.1.0)
WARNING: You are using pip version 21.2.3; however, version 22.0.3 is available.
You should consider upgrading via the 'C:\Users\User\AppData\Local\Programs\Python\Python39\python.exe -m pip install --upgrade pip' command.

@bnagirniak, what I mean is that error message about
CUSTOMBUILD : error :  [C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\pxr\imaging\rprUsd\rprUsdSchema.vcxproj]
          Error in 'pxrInternal_v0_21__pxrReserved__::PlugPlugin::_Load' at line 258 in file C:\src\BlenderUSDHydraAddon\deps\USD\pxr\base\plug\plugin.cpp : 'Fa
  iled to load plugin 'usd': A dynamic link library (DLL) initialization routine failed.

is appearing after installing jinja2.  Before installing jinja2 I was getting a different error about building hdRPR.

Can't say exactly the reason of such problem, our team didn't see it before. Maybe it happen because of Windows 11 and VM.
Can you try open HdRPR project in VS, it should be in deps\HdRPR\build, and build project here. It should show you more info about the error.

Thanks, still got an error when building from VS2019
Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB8066	Custom build for 'C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\CMakeFiles\d793060c59b165284c5166b212fbd844\api.h.rule;C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\CMakeFiles\df04f6ee9d0d9c6728cd8bed108836c2\rprUsdSchema.rule;C:\src\BlenderUSDHydraAddon\deps\HdRPR\pxr\imaging\rprUsd\CMakeLists.txt' exited with code 1.	rprUsdSchema	C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets	241

But reverting back to trace what is happening I've noticed something that keeps reoccurring (since I'm rebuilding from scratch all the time)
Running python tools/build.py -all -bin-dir bin goes like this:
1- Fetches all archives for openSubdiv, openvdb, exr..etc
2- says succeed and instruct to set up the environment variables for USD (which I do)
3- Builds hyRPR and reaches a point where it is copying binaries to libs
4- that is when the first error happens "FileNotFoundError: [Errno 2] No such file or directory: 'bin\USD\install\bin'" the folder is missing indeed and the repo size is at 20GB at this time
5- I run the same command again "python tools/build.py -all -bin-dir bin" and this is where it starts building USD this time instead of hyRPR and gives me the same notice to put the environment variables, then succeeds
6- then it tries to build hyRPR and it fails like so:
  #################################################################################################
  #  USD_DISABLE_PRIM_DEFINITIONS_FOR_USDGENSCHEMA is overridden to 'true'.  Default is 'false'.  #
  #################################################################################################
CUSTOMBUILD : error :  [C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\pxr\imaging\rprUsd\rprUsdSchema.vcxproj]
          Error in 'pxrInternal_v0_21__pxrReserved__::PlugPlugin::_Load' at line 258 in file C:\src\BlenderUSDHydraAddon\deps\USD\pxr\base\p
  lug\plugin.cpp : 'Failed to load plugin 'usd': A dynamic link library (DLL) initialization routine failed.

   in 'c:/src/BlenderUSDHydraAddon/bin/USD/install/lib/usd_usd.dll''
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: C
ustom build for 'C:\src\BlenderUSDHydraAddon\deps\HdRPR\build\CMakeFiles\d793060c59b165284c5166b212fbd844\api.h.rule;C:\src\BlenderUSDHydraA
ddon\deps\HdRPR\build\CMakeFiles\df04f6ee9d0d9c6728cd8bed108836c2\rprUsdSchema.rule' exited with code 1. [C:\src\BlenderUSDHydraAddon\deps\H
dRPR\build\pxr\imaging\rprUsd\rprUsdSchema.vcxproj]

Might try building natively today sometimes. Thanks for all your help

It's amazing how tracing the output can be helpful :) it works now.
So the 1st time I build the project I am requested to add the \deps\USD oaths into the PYTHONPATH and then PATH.
the 2nd time I build the program the USD is build and now I am requested to add the \bin\USD... into the PYTHONPATH and PATH.
I don't believe you you had the need to rebuild the whole thing from scratch like I did, and once the USD is built there is no need to rebuild it again, perhaps that is why it didn't happen to you. But once the path is updated the second time everything works fine and now I have a new build for the BlenderHydra addon.
Now to put it to the test.


[MAINT] Add dependencies for widget abstraction

Fixes parts of #10913.

Ah okay so does look like the dependencies are the issue, odd! I'll see if I can figure out how to fix it.

It's possible then that this is a test that used to be skipped on Windows (because of missing deps) but isn't. In that case I think it's okay to @pytest.mark.skipif based on the sys.platform with a # TODO: comment saying we should fix it at some point.
But if you want to continue and try to fix it, that's even better @alexrockhill -- up to you!

It's possible then that this is a test that used to be skipped on Windows (because of missing deps) but isn't. In that case I think it's okay to @pytest.mark.skipif based on the sys.platform with a # TODO: comment saying we should fix it at some point.
But if you want to continue and try to fix it, that's even better @alexrockhill -- up to you!

It took me several hours (a bit embarrassingly because of my lack of Windows ability but also I did have to go into the CIs and use the install OpenGL script to get the 3D plots to work which isn't too basic) to get the test up on Windows so since I have a machine that I have access to with things working, I'd really like to loop around at the end of GSoC and make sure everything works and looks nice on Windows. I remember with the ieeg_locate GUI, there were some really terrible things on Windows (the side bar with the channel names looked totally off as I recall) so I think that is really important to get done but I also want to make sure to stay on track so I'd like to do that as one big bug squashing PR at the end.


Quality of life parameters

Define parameters to measure quality of life

List of suitable quality of life parameters:

Crime
Transportation and Environment
Well-being
Politics (more socio-political)
Health (quality of life related)


go: Initial commit

Common packages for working on Go projects.
I frequently use this from my editor with:

https://github.com/flox/flox-direnv

And the following in .envrc:
use flox --remote floxenvs/go

In future the editor dependencies could be broken out to a separate
go-editor or go-lsp environment.
The GOENV hook is copied from our init --auto-setup hook with the
exception of:

Path is modified from goenv to go to match the other example
environments in this repo
go get . is omitted because it's surprising to fetch dependencies
when activating an environment and we have plans to remove it from
the default manifest.

The example module which includes a third-party module to prove that
dependency fetching still works is taken from:

https://go.dev/blog/using-go-modules

The minimum Go version is currently pinned, both in the manifest.toml
and go.mod, at the latest stable major and minor version. It should
continue to work after a flox upgrade assuming that there are no
breaking changes.

@garbas I've rebased in the changes that we paired on.


[Automation] Generate Fluent Lite from Swagger timeseriesinsights#package-2020-05-15

[Automation] Generate Fluent Lite from Swagger timeseriesinsights#package-2020-05-15

API change check
API changes are not detected in this pull request.


New COE Interface

This contains a new COE interface and new view for showing the COE console output + log file, and a space for the traceability daemon.
The new interface allows the COE to keep running in the background even when the app is terminated. On app restart the log and console.log are reconnected to the view and preloaded with a slice of history. However to have the console output become live again the COE must be restarted (this is not needed in most cases since the log shows nearly the same information)
I tested the implementation on windows and mac and it looks nearly the same and works in the same way.
I need some help improving the code since one of the files contains CSS style which I believe should be in a CSS file somewhere.
is also changed the project browser to load async.

Hey @ldcouto , we have carried out additional work on the issues. Could you take a look at it?

Looking good.
A few notes...

It's not very obvious what the stream redirect label and icon are supposed to be. I guess it's reconnecting to prior COEs. Maybe we can rename them?
The status and log viws do not pick up externally launched COEs (see figure)
The status page also shows the log
Should we we use Online/Offline instead of cross/tick? Might be more intuitive
The stream redirect does not pick up COEs launched from previous app runs. But the log does :)

@ldcouto few answers:

It's not very obvious what the stream redirect label and icon are supposed to be. I guess it's reconnecting to prior COEs. Maybe we can rename them?
COE Status will be changed to COE Console.
We will add some mouse-over text describing "Stream Redirect"
The status and log viws do not pick up externally launched COEs (see figure)
The log view connects to the coe.log file located in "into-cps-projects\install\coe-working-dir". It works externally, if piped into this file. The COE Status connects to the process running the COE. If this is from an earlier run, then a relaunch must be performed.
The status page also shows the log
This will be changed with next release of the COE
Should we we use Online/Offline instead of cross/tick? Might be more intuitive
We'll add some new icons
The stream redirect does not pick up COEs launched from previous app runs. But the log does :)
See bulletin 2 answer

"The log view connects to the coe.log file located in "into-cps-projects\install\coe-working-dir". It works externally, if piped into this file. The COE Status connects to the process running the COE. If this is from an earlier run, then a relaunch must be performed."
What does relaunch mean in this case?

Press stop and launch

Gotcha.
We need to be sure we document this feature. There's potential for a bit of confusion for the COE connections, etc. tagging @bandurvp so he tracks this as well.

Ready to merge @ldcouto ! :)

I'm finding a lot more trouble this time.
The coe console launches the coe  from install_downloads. The log picks it up from install. This causes obvious problems
The launcher has other problems. If there is no coe in install_downloads, it throws some ugly errors.
Eventually it launches off some other path, but the console command is still shown as Terminal args: java -jar C:\Users\CoutoLD\Documents\into-cps-projects\install_downloads\coe.jar
But none of my co-simulations go past 0% and no logs are generated, so something is wrong.
Any ideas what could be causing this? I put the coe in install, even deleted it from install_dir, but that just causes the launch to fail. By the way, if the launcher fails, it's quite ungraceful -- just hangs there. Should
At first I thought something was wrong with my settings but my install_dir is install
I'll do more extensive testing tomorrow.

Screenshot of error

I just pushed a change so it always runs from install_downloads
I think you have some none default settings somewhere to get that error. Did you set a custom path for the COE maybe?

not sure what the issue is with the logs in a different place than the COE but I changed it to be the same root folder now
if there is no coe in install downloads then I get a message saying that I should install it
do you know why no progress is being made. I mean is it related to this change? Maybe try enabling trace on the coe

I nuked my settings so everything was in defaults.
I've sorted out the co-simulation launching. Took a while to identify. If the coe_working_dir folder does not exist when the coe is launched, then the console and the log do not connect properly. If you launch a co-simulation, nothing happens (stays at 0% -- see attached)
If you kill and relaunch the coe, the console will connect. But the log will not. You have to relaunch the app for the log to get picked up.
If this is error is easy to fix, let's do it. Otherwise, it's a relatively simple workaround to relaunch the coe and retstart the app. This only has to be done once.
Also, all the code for this feature is in the root of src ? Can you move it to a dedicated folder like the other components?

I added a check and created the folder if the path is obtained

Working perfectly now.


Have a drop_common_labels() in the graph UI

While experimenting with queries, root-causing problems, etc. etc. etc. I often find myself adding drop_common_labels() around an existing query, because the key shown below the graph is too cluttered.
Would it be possible to have some short-hand feature for this? For example, having a checkbox next to the graph. When clicked, the query doesn't need to be re-executed, but the key below the graph is updated to no longer include common labels. The common labels may still be showed once below the graph, so the information is not lost.

We (Prometheus team) just had a bug scrub call and decided to close this, as this hasn't come up regularly and is likely not something we want to support in the built-in UI at this point.


Can't build with cargo or cargo-nightly

Hi,
try to build with cargo, I got this error:
error[E0554]: `#![feature]` may not be used on the stable release channel
 --> src/main.rs:1:12
  |
1 | #![feature(file_set_times)]
  |            ^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0554`.
error: could not compile `mlvd` (bin "mlvd") due to previous error

with cargo-nightly this one:
   Compiling proc-macro2 v1.0.47
   Compiling ring v0.16.20
   Compiling getrandom v0.2.8
   Compiling unicode-normalization v0.1.22
   Compiling aho-corasick v0.7.19
   Compiling serde_json v1.0.87
   Compiling atty v0.2.14
   Compiling anyhow v1.0.66
   Compiling ppv-lite86 v0.2.17
   Compiling ryu v1.0.11
   Compiling heck v0.4.0
   Compiling regex-syntax v0.6.28
   Compiling itoa v1.0.4
   Compiling argh_shared v0.1.9
error[E0635]: unknown feature `proc_macro_span_shrink`
  --> /home/pr0p37/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.47/src/lib.rs:92:30
   |
92 |     feature(proc_macro_span, proc_macro_span_shrink)
   |                              ^^^^^^^^^^^^^^^^^^^^^^

   Compiling rand_core v0.6.4
   Compiling flate2 v1.0.24
For more information about this error, try `rustc --explain E0635`.
error: could not compile `proc-macro2` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...

That's a wireguard error message, the wireguard kernel module isn't loaded in your kernel.
Try loading the kernel module or rebooting.


UI theme and fixes

You are adding .idea/workspace.xml to the master branch

Please remove it and then send the PR.


[release-1.11] oci: Don't use created from runc state

@runcom PTAL
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

/test integration

/test critest

/test e2e

looks good except a nit, we can merge afterwards

yeah we need to provide backwards compatibility.

@mrunalp do we still need this?

Closing as we fixed this a different way.


Pick the right compiler for CloudABI.

CloudABI is a sandboxed UNIX-like runtime environment. For CloudABI, the
compiler is always named -cc or -c++. The target name is
never mangled. As we use Clang, not GCC, we use -cc and -c++, as opposed
to -gcc and -g++.

Thanks!


The geth-localnet image is failing in >= v3.0.0-rc6

Describe the bug
Versions rc6 & rc7 are failing with error:
ERROR[01-23|18:26:09.670] Cannot start mining without etherbase    err="etherbase must be explicitly specified"
Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly specified
Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly specified

There is no a change of geth image between the rc5 and rc6 so it could be because some change introduced in geth. In the Dockerfile was using latest
To Reproduce
Steps to reproduce the behavior:
1.
2.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

fixed in v3.0.0-rc8


Docker image changed to latest commit not working.

Using zulip docker image when changing to latest code i.e. master
Commit id :- 855ac26c4811c5ce2b11a392beccdeb8265453b9
Getting below error.
File "/home/zulip/deployments/2021-03-18-19-02-33/zproject/backends.py", line 23, in
import ujson
ModuleNotFoundError: No module named 'ujson'
Error in the Zulip configuration. Exiting.
Works perfectly with 3.3 release

@andersk can you investigate?

@abhishekdeshmukh2209 can you provide a full traceback?  We no longer use ujson in Zulip, so I find this report surprising.

Closing due to lack of reply and the fact that ujson hasn't been used in Zulip since mid-2020 (61d0417e75a09075d9a61ac0ddd959efd6934478), which makes me think it unlikely this was tested against master.


fix: increase timeout for push-disk-images IR

The disk images for RHEL AI are very big and
we repeatedly saw timeouts. We will make it
customizable here:
https://issues.redhat.com/browse/RELEASE-1143
But for now, let's increase the values.

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite


Uncaught TypeError: o.HmrState is not a function

when i build this application for prod mode
npm run build:prod  is executed without error
then i run command "npm run server:prod"
it is alo executed with out error. but in broser console it is showing
app.service.ts:7Uncaught TypeError: o.HmrState is not a function

what version of angular/angular2-hmr do you have or did you download a fresh version of the repo

+1 (cloned the repo this evening)

is everyone using npm 3?

or on windows

can you revert this change be keep the angular2-hmr version
https://github.com/AngularClass/angular2-webpack-starter/commit/24a19a9f05b1840a28cfa5a013e2e9d254f4f43f#diff-d1535ca6497b532e66b6b853f99dc1f7L174
from
helpers.root('node_modules/angular2-hmr/prod.js')
to
helpers.root('config/modules/angular2-hmr-prod.js')

@gdi2290 Works now (npm 3.8.7 on Windows)

kk done via https://github.com/AngularClass/angular2-webpack-starter/commit/3ddddee3923f0b2a473bdd7364ec639a99c22f7b


Ambari WebUI differs in HDInsight 3.6

I recently deployed a HDInsight 3.6 cluster (Spark 2.3 variant), and logged into the Ambari WebUI.
I wanted to deploy a custom service, but the UI is different from the one depicted in this documentation page, and, there is no button "Actions" or "Add Service" in the "Services" section (https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-hadoop-manage-ambari#service).
Screenshoot of what I see in the Web UI: https://pasteboard.co/JiYkb1z.jpg
For reference, the custom service I'm trying to deploy is the SAP HANA Spark Controller, which requires the installation of some files on the master head node of the cluster beforehand (https://help.sap.com/viewer/6437091bdb1145d9be06aeec79f06363/<IP_ADDRESS>/en-US/9213000d628547f9b6c09693cf412be7.html)

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

ID: 00333262-d8b4-15ef-b1d3-72d25a9bb00a
Version Independent ID: 9835a785-de1b-1b5f-1f2c-ed0e3e464169
Content: Monitor and manage Azure HDInsight using Ambari Web UI
Content Source: articles/hdinsight/hdinsight-hadoop-manage-ambari.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

@stawo
Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

@stawo Thanks for reaching out. Currently 3.6 is still the default for all cluster types, so we have left the screenshots for the default version that most customers will use. When HDInsight 4.0 becomes the default version, we will update the screenshots accordingly. Thank you. If you need help navigating the updated Ambari UI, please open a ticket with Azure support. Select Support from the menu bar or open the Help + support hub.  Or you can create a topic on the new QA platform.

#sign-off

@hrasheed-msft , as I mentioned in the title and description, I'm referring to HDInsight 3.6, not 4.0.
I'm aware of your answer to my other issue regarding HDInsight 4.0, but the issue still persists even in HDInsight 3.6.
Please re-open the issue.

@stawo Apologies for the oversight. I will investigate updating the screenshot. However, the following warning in the article you referenced, seems to recommend against using the Ambari UI for adding services: "While Add Service is listed in this menu, it should not be used to add services to the HDInsight cluster. New services should be added using a Script Action during cluster provisioning." For that reason, I would still recommend that you reach out to Azure support for assistance adding the service that you mentioned to your cluster.


404 not found on install

Do you want to request a feature or report a bug?
bug
What is the current behavior?
can't install with yarn "yarn add draft-js" gives 404 not found error

Please confirm whether you enable http proxy

I was able to resolve the issue by running "yarn upgrade"


ValueError: ('Scale mismatches. GT (3078, 5472) is not 4x ', 'multiplication of LQ (1080, 1624).')

Thanks for the great projects!
i have a problem with training finetune paired data using finetune_realesrgan_x4plus_pairdata.yml.
and i don't know how to solve this problem.

Note that in the config file ( finetune_realesrgan_x4plus_pairdata.yml) that is present under the options folder, the scale is set as 4 by default. In your case, the dimensions of GT are not 4 times the dimensions of LQ. Dimensions of GT should be (1080 x 4 = 4320, 1624 x 4 = 6496) i.e. (4320,6496). Try using the below code to modify the dimensions of GT: -
import os
from PIL import Image
GT_folder = 'Path/to/GT'
output_folder = 'Path/to/GT_resized'
target_width = 4320
target_height = 6496
Create the output folder if it doesn't exist
os.makedirs(output_folder, exist_ok=True)
Iterate over the images in the LR folder
for filename in os.listdir(lr_folder):
# Open the image
image_path = os.path.join(lr_folder, filename)
image = Image.open(image_path)
    # Resize the image
    resized_image = image.resize((target_width, target_height), Image.BICUBIC)

    # Save the resized image to the output folder
    output_path = os.path.join(output_folder, filename)
    resized_image.save(output_path)

    print(f"Resized image saved: {output_path}")

Hope this helps!

Note that in the config file ( finetune_realesrgan_x4plus_pairdata.yml) that is present under the options folder, the scale is set as 4 by default. In your case, the dimensions of GT are not 4 times the dimensions of LQ. Dimensions of GT should be (1080 x 4 = 4320, 1624 x 4 = 6496) i.e. (4320,6496). Try using the below code to modify the dimensions of GT: -
import os from PIL import Image
GT_folder = 'Path/to/GT' output_folder = 'Path/to/GT_resized' target_width = 4320 target_height = 6496
Create the output folder if it doesn't exist
os.makedirs(output_folder, exist_ok=True)
Iterate over the images in the LR folder
for filename in os.listdir(lr_folder): # Open the image image_path = os.path.join(lr_folder, filename) image = Image.open(image_path)
    # Resize the image
    resized_image = image.resize((target_width, target_height), Image.BICUBIC)

    # Save the resized image to the output folder
    output_path = os.path.join(output_folder, filename)
    resized_image.save(output_path)

    print(f"Resized image saved: {output_path}")

Hope this helps!

thanks！ I already solved this problem.

Note that in the config file ( finetune_realesrgan_x4plus_pairdata.yml) that is present under the options folder, the scale is set as 4 by default. In your case, the dimensions of GT are not 4 times the dimensions of LQ. Dimensions of GT should be (1080 x 4 = 4320, 1624 x 4 = 6496) i.e. (4320,6496). Try using the below code to modify the dimensions of GT: -
import os from PIL import Image
GT_folder = 'Path/to/GT' output_folder = 'Path/to/GT_resized' target_width = 4320 target_height = 6496
Create the output folder if it doesn't exist
os.makedirs(output_folder, exist_ok=True)
Iterate over the images in the LR folder
for filename in os.listdir(lr_folder): # Open the image image_path = os.path.join(lr_folder, filename) image = Image.open(image_path)
    # Resize the image
    resized_image = image.resize((target_width, target_height), Image.BICUBIC)

    # Save the resized image to the output folder
    output_path = os.path.join(output_folder, filename)
    resized_image.save(output_path)

    print(f"Resized image saved: {output_path}")

Hope this helps!

thanks！ I already solved this problem.

can i ask how?


This plugin breaks the AST, causing cssnano to break

See prior discussion in cssnano/cssnano#658 and ben-eb/postcss-convert-values#27. It appears as though this plugin is the source of the error, though I'm not sure where.

Goodness, this plugin needs to be updated. Given time, I will try to work on this tonight. Please continue to ping me if you don’t see regular updates.


return users when search user keyword is empty

Coverage decreased (-0.09%) to 50.599% when pulling ec448a1a8ed12afa504a6b060b261b31fab504cc on lepdou:search_user into b9bca8705a03a91e1730d375187ea1e8a9d56891 on ctripcorp:master.

Codecov Report

Merging #742 into master will decrease coverage by 0.08%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #742      +/-   ##
============================================
- Coverage     47.16%   47.08%   -0.09%
+ Complexity     1547     1545       -2
============================================
  Files           352      352
  Lines          9678     9678
  Branches        959      959
============================================
- Hits           4565     4557       -8
- Misses         4772     4781       +9
+ Partials        341      340       -1

Impacted Files
Coverage Δ
Complexity Δ

.../spi/springsecurity/SpringSecurityUserService.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...work/apollo/biz/message/DatabaseMessageSender.java
50% <0%> (-16.67%)
6% <0%> (-2%)

...ervice/service/ReleaseMessageServiceWithCache.java
84.52% <0%> (-1.2%)
23% <0%> (-1%)

.../apollo/internals/RemoteConfigLongPollService.java
77.91% <0%> (+0.61%)
28% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


Are only 1709 and 1803 supportable?

I think other Win10 versions are also supported in-place upgrade. Why are only 1709 and 1803 listed?

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

ID: 5853ce95-f163-0739-0a57-50aab1719bdd
Version Independent ID: b1536434-3675-a736-22e8-28e5fea49f06
Content: Steps for in-place system upgrades for supported Windows 10 Azure VMs and workarounds for unsupported versions - Virtual Machines
Content Source: support/azure/virtual-machines/in-place-system-upgrade.md
Service: virtual-machines
GitHub Login: @genlin
Microsoft Alias: genli

@akozeki, Here the full list of windows 10 versions that support in-place upgrade:

Windows 10
Windows 10, version 1709, all editions
Windows 10, version 1803, all editions
Windows 10 Enterprise multi-session, all editions

So, does version after 1803 (1909 or 2004) not support in-place upgrade?

@akozeki, Thanks for your question.  I will check it with our engineers.

@akozeki, I have updated the article with all the supported versions.

#please-closed


Bumps Resteasy and Cloud Secret Manager to address CVEs

Sorry! I was working through a list for SOC2 compliance; I didn't realize these were related.
This change resolves the following:

CVE-2020-25633
CVE-2020-25647

Done in version 1.28.7, thanks Christopher :)


Fixed style and striped use in progressbar

Hi @Morgul, this is my proposal for resolve #12 .
I had added the striped option in uib-progressbar and uib-bar.
Cheers!

@krlos2011 Those changes look good, but the unit tests will need changes for this. Can you at least get them passing?

Hi again @Morgul, Sorry for the delay.
I modified the tests and, also, I have added the .dropdown-item class in the default template for typeahead.


Remove reference to SlackRubyBot which is based on RTM.

https://github.com/slack-ruby/slack-ruby-bot-server-events-sample/blob/a023ca0641a7ecd8023de42f5b31cb4707ee1980/lib/commands/help.rb#L3
Just asking, can't we use such commands now? Only slash commands are available? Didn't think of it yet..

This has been resolved by this commit.


caffe2 build issue on MacOS v10.12.16

Hi,
I am building the caffe2 on MacOS following the guideline of https://caffe2.ai/docs/getting-started.html?platform=mac&configuration=compile, I have tried with both Anaconda and Homebrew path, but both got below same issue:
[  1%] Built target gmock
[  2%] Built target gmock_main
[  2%] Built target gtest
[  3%] Built target gtest_main
[  3%] Linking CXX shared library libbenchmark.dylib
dyld: lazy symbol binding failed: Symbol not found: _utimensat
Referenced from: /usr/local/Cellar/cmake/3.9.3/bin/cmake
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: _utimensat
Referenced from: /usr/local/Cellar/cmake/3.9.3/bin/cmake
Expected in: /usr/lib/libSystem.B.dylib
make[2]: *** [third_party/benchmark/src/libbenchmark.dylib] Abort trap: 6
make[2]: *** Deleting file `third_party/benchmark/src/libbenchmark.dylib'
make[1]: *** [third_party/benchmark/src/CMakeFiles/benchmark.dir/all] Error 2
make: *** [all] Error 2
would you help to look at it? thanks in advance.
Regards,
jhuihe

A quick search shows that it might be an Xcode issue:
https://forums.developer.apple.com/thread/87097
https://trac.macports.org/ticket/54875
So it might be a mac issue. Maybe try downgrading your Xcode?


Google reCAPTCHA needs to be added!

https://developers.google.com/recaptcha/docs/v3

Google reCAPTCHA V3 added.


WIP: Claudia/enrich events with container image copy

Used for rebasing and testing for #1682 . Will be closed when done.

Done. Closing.


Fixed markdown syntax translation issue

This PR addresses two issues:

Removed test files: Unnecessary test files have been deleted to clean up the repository.
Fixed markdown syntax translation issue: Fixed the issue where markdown syntax like [!NOTE], [!WARNING], [!TIP], [!IMPORTANT], and [!CAUTION] was being translated. These block markers will now remain untranslated, while the content inside these blocks will still be translated as expected. (Solved #7 )

The regex/skip/replace method turned out to be more complicated than anticipated, especially when handling [!NOTE] and similar markers. On the other hand, updating the prompt delivered better results than expected, so I’ve implemented that solution for now.
In the future, if regex/skip/replace becomes a more practical option, we can revisit and apply that approach.

I have reviewed the changes myself and everything looks good to me


Updated README links to bloggers files moved in #217

Coverage remained the same at 69.33% when pulling 193f3a13b034ca5e4c25bdfdcd5884341560161d on Fixed-links-in-README into 5845d235924457a2af594bf87dcd25dbe12a4ebe on master.


Deploy without deno deploy

Hey! I'd like to know if there is anyone who has deployed his fresh app without deno deploy and can kindly share an example on how to do so

I used a dockerfile like this:
FROM denoland/deno:alpine-v1.23.0

EXPOSE 8000

WORKDIR /app

USER deno

COPY . .

RUN deno cache main.ts --import-map=import_map.json

CMD ["run", "--allow-net", "--allow-env", "--allow-read", "main.ts"]

@fulsomenko thanks mate! Will test this later appreciate you 🥇

Don't forget to include DENO_DEPLOYMENT_ID in your image as Fresh uses this env variable to determine if it's running in production or not.
Related issue: https://github.com/denoland/fresh/issues/535

This article might be useful, too, for Linux machines with systemd:
https://blog.jlcarveth.dev/hello_world

If someone wants to write docs for this, I'd be happy to merge a PR :)

@lucacasonato This should be closed right (with #680 being merged)?


Spinnaker Deck - Yarn Start fails with compilation error

I ran with following commands.
yarn
yarn start
Running in localhost:9000/ but after authentication it fails
Below is the result I am getting.
yarn run v1.7.0
$ sh ./start.sh
./start.sh: 8: ./start.sh: [[: not found
Launching deck using node v8.9.3...

<EMAIL_ADDRESS>start-dev-server /home/work/spinnaker-ui/deck-master
webpack-dev-server --progress --mode=development

INFO: cpus: 8 physical: 4 thread-loader threads: 3
Webpack mode: development
Starting type checking and linting service...
Using 1 worker with 2048MB memory limit
10% building modules 3/3 modules 0 activeℹ ｢wds｣: Project is running at http://localhost:9000/
ℹ ｢wds｣: webpack output is served from /
68% building modules 858/873 modules 15 active ...master/node_modules/lodash/partial.jspostcss-colorfix warning:
".search .search__input.search__input--focus" uses #66afe9 border-color.
Closest variable is --color-text-link
95% emitting HtmlWebpackPluginNo type errors found
No lint errors found
Version: typescript 2.8.3, tslint 5.10.0
Time: 25505ms
⚠ ｢wdm｣:
ℹ ｢wdm｣: Compiled with warnings.

Any update regarding above mentioned issue?
10% building modules 3/3 modules 0 activeℹ ｢wds｣: Project is running at http://localhost:9000/
ℹ ｢wds｣: webpack output is served from /                                                                                68% building modules 892/916 modules 24 active ...eact/UIRouterReactContextDecorator.jspostcss-colorfix warning:
".search .search__input.search__input--focus" uses #66afe9 border-color.
Closest variable is --color-text-link                                                              69% building modules 5943/5998 modules 55 active .../dist/es/vendor/binarySearchBounds.jspostcss-colorfix warning:
".heading-tag-overflow-group .account-tag" uses white border-top.
Closest variable is --color-white                                                                95% emitting HtmlWebpackPluginType checking and linting in⚠ ｢wdm｣:
ℹ ｢wdm｣: Compiled with warnings.
No type errors found
No lint errors found
Version: typescript 3.1.4, tslint 5.11.0
Time: 45289ms

I just grabbed the latest version of the repository, ran yarn, then yarn start, and the app started up without any issues for me.
If you go to http://localhost:9000, do you see anything?


doc(README): Update doc on parameter git_add_modified

Update doc about the git_add_modified parameter.
[skip release]

:pencil: Description
:link: Related Issues

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Pull Request

Pull request as said in the mail for CVG project.

ugh why?
ᐧ
*Giridhur S *
Undergraduate Senior
Electrical Engineering
Indian Institute of Technology,Madras
On Wed, Dec 21, 2016 at 2:08 PM, vikranth1997<EMAIL_ADDRESS>wrote:

Reopened #4 https://github.com/iitmcvg/numpy_exercises/pull/4.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iitmcvg/numpy_exercises/pull/4#event-901272353, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGIl2Ppc6rQawMdwhrITVQZam2Xn1eOcks5rKOWZgaJpZM4LP3JG
.

Excuse me for doing it wrong...its due to my wrong assumption. I created another pull request ("Exercises done") where the files r uploaded to repo.


Update SAML reply url

Colossyan's auth domain has changed. These changes has to reflected in the SSO documentation.

@jeevansd

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@AdamBelakovics, thanks for the request, we're creating a separate pull request for your changes in our private repo for better content validation, the changes will be going to live within 2-3 working days.
#please-close


Session Timeout

Hi, I logged in with remeber_me (3600 24 30 ) (30 days)as checked in login form. even though it will automatically logged out quickly. How to increase the time

I have tested this feature for few days, and it is working properly. There must be some problem with your amp configuration.