Carthage support

Add Carthage support

Coverage remained the same at 67.288% when pulling 86b58c8b07eaa388815b99475a8a781c18c971ff on carthage_support into 7d54b87be47e91afd7d4778eaef74d24490e34e4 on master.


048 conversion only supports marc codes in subfield a, not subfield b or 2.

The way the codes are mapped in marc2bibframe2, the codes are extracted from subfield a and subfield b into bf:instrument bf:ensemble, or bf:voice with textual labels not codes. While subfield 2 and ind2=7 is ignored, the source is hardcoded.
When they come through bibframe2marc, only subfield a is supported along with ind2=blank; no subfield b or subfield 2 are created. WC has about 600k v048$b. There's about ~3k v048$2, and in that case ind2 would be 7; so for example, the IAML medium of performance codes wouldn't work with the lookup table.
A tweak to use bf:code instead of strings, and mapping bf:source should fix ind2=7 & $2; a soloists property/class may or may not be needed for $b support, perhaps "not bf:ensemble" will work?

The MARC-to-BIBFRAME conversion of the 048 and 382 fields needs further review and reconciliation with the PMO Medium of Performance ontology.


chore: night render profile

WHY
right now our halloween and Xmas render profiles set their respective empty parcels and they also use the night mode by default.
The problem is that we frequently need to enable the night mode by default without the change in the empty parcels, and we can't do that using the existing render profiles.
WHAT
Added a night render profile that only enables the night mode, without changing the empty parcels.
Now Xmas and Halloween render profiles use the same underlying settings applied for the new night render profile.
TEST

DEFAULT -> default empty parcels, day mode
https://explorer.decentraland.zone/branch/chore/NightRenderProfile/index.html?ENV=org&FORCE_RENDERING_STYLE=0

HALLOWEEN -> halloween empty parcels, night mode
https://explorer.decentraland.zone/branch/chore/NightRenderProfile/index.html?ENV=org&FORCE_RENDERING_STYLE=1

XMAS -> Xmas empty parcels, night mode
https://explorer.decentraland.zone/branch/chore/NightRenderProfile/index.html?ENV=org&FORCE_RENDERING_STYLE=2

NIGHT -> default empty parcels, night mode (new)
https://explorer.decentraland.zone/branch/chore/NightRenderProfile/index.html?ENV=org&FORCE_RENDERING_STYLE=3

Maybe for later, but, Is it possible to decouple this a little bit more? If we want Halloween empty parcels with day mode we will find our self kind of in the same situation we are right now

Yeap, we talked about this with Brian and we will decouple it completely in the future.
Also I'd like to have these kind of settings in the senes JSON so that we can lerp diferent render profiles when you enter/exit a scene (and we wouldn't be bothered with changing the defults of the world if the event developers can set this directly in their scenes...)

Maybe for later, but, Is it possible to decouple this a little bit more? If we want Halloween empty parcels with day mode we will find our self kind of in the same situation we are right now

Yeap, we talked about this with Brian and we will decouple it completely in the future.
Also I'd like to have these kind of settings in the senes JSON so that we can lerp diferent render profiles when you enter/exit a scene (and we wouldn't be bothered with changing the defults of the world if the event developers can set this directly in their scenes...)


SCIP/GCG parameters

Dear support team,
Is it possible to use some useful SCIP/GCG parameters like:
m.setParam('limits/time', 40)
m.setPresolve(SCIP_PARAMSETTING.AGGRESSIVE)
m.setHeuristics(SCIP_PARAMSETTING.AGGRESSIVE)
m.setSeparating(SCIP_PARAMSETTING.AGGRESSIVE)

It seems despite of first, the remaining three parameters cannot affect the solving process, while in the SCIP, they really have a good impact on the solving process and decrease the total solving time.
Best regards
Abbas

Dear support team,
May I have your insight about using the above SCIP parameters in GCG?
Is it possible to use these parameters or they do not affect GCG?
Best regards
Abbas

This is an answer by Prof. Lübbecke:

There are also "emphasis" parameters for heuristics (both, for the original and master program), cuts separation, detection, etc. with which you can experiment. To determine "whether different parameter settings (other than the default) can be useful" I would always first check the solving statistics: where did you spend the time? In heuristics? No? Then, obviously, there is no need to reduce heuristics solving time.

The full list of GCG parameters is in the documentation:
Link
All the best
Abbas


fix fix issue when read hive table stored on tencent OFS

Fix two issues:

error when read hive parquet table with snappy compression on ofs:  Invalid magic number in parquet file
error when read hive orc table with none  compression on ofs:  Init OrcReader failed. reason = Read past EOF in DecompressionStream::readBuffer

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run feut

run feut

run clickbench


Autoscaling test

All Submissions:

[ ] Have you signed our CLA?
[ ] Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if there is one).
[ ] Update docs/release-notes/release-notes.md if your changes should be included in the release notes for the next release.

resolves https://github.com/commercetools/say_terabyte/issues/577

Please add a screenshot of the successful test result
@n3ph

@yzdann should we keep this PR open?

@zonorti No, it's not necessary!


AE2stuff blocks get duplicated in the AE network on chunk unload/reload

I've had a world now (Forge 1517, AE rv2-stable-10, AE2stuff <IP_ADDRESS>, bdlib <IP_ADDRESS>, although also happened with <IP_ADDRESS>/<IP_ADDRESS> version of AE2stuff and bdlib) with a network containing one each of a crystal growth chamber, a pattern encoder, and an AE2 advanced inscriber. Over time, the number of these blocks, as reported by an AE2 network tool, steadily grows; since the pattern encoder draws power continuously this causes the power drain to grow, essentially without bound. 208 pattern encoders draw a lot of power.
I've determined that this happens when the chunks containing the network are unloaded and reloaded; I can cause the counts to increment by one by disconnecting and reconnecting, which (of course) causes a chunk unload/reload. My best guess is that the pattern encoder is not removed from the network on chunk unload, but is readded to it on chunk load, leading to multiple instances in the network.
Breaking the block containing the pattern encoder removes only one instance from the network, leaving any phantoms behind. (Doesn't matter whether I use a pickaxe or a wrench.) The ME cable connecting the encoder to the network remains, apparently connecting to nothing. Breaking that cable removes all of the phantom encoders and resolves the power drain issue. The same thing happens with the phantom advanced inscribers and crystal growth chambers, but as these don't draw passive power they're less of a concern.
Obviously, I could obviate this by using chunkloaders, and that's likely what I'll do as a workaround, but I thought I'd report it.

That's odd, i think i know what's going on, but i can't reproduce it.
Does some part of the network remain chunk loaded while the area is unloaded?

At any rate, please try this build: http://jenkins.bdew.net/job/ae2stuff-1.7.10/60/artifact/build/libs/ae2stuff-<IP_ADDRESS>-mc1.7.10.jar
I think it will fix this issue.
You might need to update BDLib as well to a newer build: http://jenkins.bdew.net/job/bdlib-1.7.10/109/artifact/build/libs/bdlib-<IP_ADDRESS>-mc1.7.10.jar

It's possible (indeed likely) that part of the network is in the server spawn protection area and thus remains loaded even when all players are disconnected.
I am not observing the problem with the builds recommended above (tested both by disconnecting and reconnecting, and by moving away so that the chunks unload while still connected). Thanks for the quick attention to this issue.


Fix test failure in cuDNN v7.5

Fix for https://github.com/cupy/cupy/pull/2117

Jenkins, test this please.

Jenkins CI test (for commit f938847e0073c1bd5d82e25607a33f8f514543ff, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit f938847e0073c1bd5d82e25607a33f8f514543ff, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins failures seem unrelated. Will merge after checking Travis.

LGTM!


Fix build

fix whitespace between variable error

Codecov Report
Patch and project coverage have no change.

Comparison is base (0da60a2) 87.56% compared to head (b1117ab) 87.56%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #87   +/-   ##
=======================================
  Coverage   87.56%   87.56%
=======================================
  Files           3        3
  Lines         185      185
=======================================
  Hits          162      162
  Misses         23       23

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Build is back to green. Merging


investigate #1351 functionality with compartment searches

Issue #1351 was implemented to provide a means to constrain search options.
Need to confirm behavior with compartment searches.

This one is about "how do we catch overly broad queries BEFORE executing them".
Troy added some stuff under #1351 for saying "you can only search by search parameter x if you ALSO include parameter y"
where the main use case would be "you need to include the patient parameter in your searches" (to scope them to a single patient).
But then, we were like "what if the query is scoped to a single patient by virtue of being a patient compartment search?"
"How do we make that work with what troy added for 1351?"

When a tenant has configured search parameters or search parameter combinations using the fhirServer/resources/<resourceType>/searchParameters or fhirServer/resources/<resourceType>/searchParameterCombinations properties in the fhir-server-config.json file, there are potential issues with compartment search. These issues are as follows:

If compartment inclusion criteria search parameters are not specified in the fhirServer/resources/<resourceType>/searchParameters list for a given resource type, then the new generated compartment search token (if the fhirServer/search/useStoredCompartmentParam value is set to true - see issue #1708) or the tokens for the inclusion criteria search parameters, are not created/stored at resource create/update time, and thus that resource will not get returned on a compartment search as it should.
Example:

fhir-server-config.json only specifies _id and _lastUpdated as valid search parameters for the Procedure resource type, not the patient and performer inclusion criteria search parameters:
"resources": {
  "Procedure": {
    "searchParameters": {
      "_id": "http://hl7.org/fhir/SearchParameter/Resource-id",
      "_lastUpdated": "http://hl7.org/fhir/SearchParameter/Resource-lastUpdated"
    }
  }
},

A Procedure resource is created which contains the following Patient reference, meaning it should be associated with that Patient compartment:
"subject": {
  "reference": "Patient/17575"
},

However, the Patient compartment inclusion criteria search parameters for the Procedure resource type, patient and performer, are not in the fhirServer/resources/<resourceType>/searchParameters list, so are not considered valid search parameters. This means the generated compartment search token (if enabled) or the inclusion criteria search tokens will not be created and indexed when the Procedure resource is stored.

The following compartment search is performed:
Patient/17575/Procedure

The Procedure created in step ii will not be returned in the search results because the necessary compartment search token(s), which are what's used in the compartment search SQL, were not created and indexed.

If a compartment inclusion criteria search parameter is specified in the fhirServer/resources/<resourceType>/searchParameterCombinations list to limit search scope (i.e. patient or performer), then that parameter must be specified on a compartment search even though the compartment search already scopes the query to that search parameter. In addition, the search parameter will be specified twice in the generated SQL.
Example:

fhir-server-config.json specifies the patient search parameter in its fhirServer/resources/<resourceType>/searchParameterCombinations list for the Procedure resource type:
"resources": {
  "Procedure": {
    "searchParameterCombinations": ["patient","patient+date","patient+status","patient+code"]
  }
},

The following compartment search is performed:
Patient/17575/Procedure

It will fail because the patient search parameter was not specified, even though the compartment search already scopes the search to a single Patient.

The following compartment search is performed:
Patient/17575/Procedure?patient=Patient/17575

It will correctly return the Patient's Procedure resources, but the patient search parameter has to be unnecessarily specified, and the generated SQL will contain functionally duplicate WHERE clauses to scope the results to a single Patient.

Possible options to address issue #1

Option
Pros
Cons

1. Leave it working as-is and document behavior.
Documentation change only.
User may not get expected compartment search results.

2. When storing a resource for which compartment search tokens will not be indexed, return a warning on the POST or PUT request.
Gives user an indication that compartment search will not work for this resource.
User may not get expected compartment search results.

3. When generating the compartment search tokens, assume the inclusion criteria search parameters are always valid, rather than checking against the search parameter list configured for the tenant.
Tokens required for compartment search to work properly will always be indexed.
?

Possible options to address issue #2

Option
Pros
Cons

1. Leave it working as-is
No code changes required.
Requires user to specify superfluous search parameter, and generated SQL includes two WHERE clauses when it only needs one.

2. On compartment searches, just ignore the search parameter configuration properties in fhir-server-config
Doesn't require user to specify superfluous search parameters on compartment searches
Although compartment search currently constrains the search to a single compartment, tenant might actually want to constrain these searches even more.

3. Add new versions of the searchParameters and searchParameterCombinations properties in the fhir-server-config that are compartment-specific
Allows tenant to configure compartment search and normal search independently.
May be confusing to user. May be overkill.

4. Attempt some kind of matching where if a compartment inclusion criteria search parameter is specified in the searchParameters or searchParameterCombinations properties, then we don't require that parameter to be explicitly specified on a compartment search, since the search will already be constrained by that search parameter.
Doesn't require user to specify superfluous search parameters on compartment searches
May be confusing to user. Code would be fairly complex.

After discussion with the team, issues will be addressed as follows:
Issue 1: For the short-term, we will go with option 1 to address this - work as-is and document potential conflicts between compartment search and configured search parameters (issue #1780). For the longer term, issue #1777 has been opened to implement option 3 (When generating the compartment search tokens, assume the inclusion criteria search parameters are always valid).
Issue 2: For the short-term, we will go with option 1 to address this - work as-is. For the longer term, issue #1778 has been opened to implement a derivation of option 3 (Add new versions of the searchParameters and searchParameterCombinations properties in the fhir-server-config that are compartment-specific).


EspMdns::query crashes when no services are found

When running mDNS queries that return no results, the EspMdns::query function crashes the microcontroller. As far as I can tell, this is due to the   https://github.com/esp-rs/esp-idf-svc/blob/269657361af4677dc2d4a05c3312da2a1f6ebc5a/src/mdns.rs#L347
for which result.is_null() still returns true, if mdns_query does not find any services. This causes a panic by the
https://github.com/esp-rs/esp-idf-svc/blob/269657361af4677dc2d4a05c3312da2a1f6ebc5a/src/mdns.rs#L363
(thread 'main' panicked at 'unsafe precondition(s) violated: NonNull::new_unchecked requires that the pointer is non-null').
I fixed this with a simple
if result.is_null() {
            Ok(0)
        } else {
            Ok(copy_query_results(
                unsafe { Box::from_raw(result) },
                results,
            ))
        }

If there's nothing more to do, I can open a pull request for this.
The function also crashes when passing None to the name parameter of the function, though this might also be caused by simultaneously using Type::Any, just fyi.
Side question: Is there any more elegant way to work with mdns? At the moment I have to create a Vec of manually created QueryResults to pass as the results array, which is kind of annoying.

if result.is_null() {
            Ok(0)
        } else {
            Ok(copy_query_results(
                unsafe { Box::from_raw(result) },
                results,
            ))
        }

If you could open a PR, that would be great, yes.

Side question: Is there any more elegant way to work with mdns? At the moment I have to create a Vec of manually created QueryResults to pass as the results array, which is kind of annoying.

Not really. We do try to avoid the alloc module in the Rust wrappers (ESP IDF does allocate though), hence our APIs are slightly more inconvenient to work with.

Actually, I've implement a simpler and more correct fix. The whole Box thing is completely unnecessary in the first place.


Unable to cast object of type 'OPCAutomation.OPCServerClass'

Hi sam,and all friends,
I have an OPC.Da.The server for the KEBA company is named Kestudio.
I connected to it with the Kebserver software and there is no problem.
but Error in IoTGateway master:
Unable to cast object of type 'OPCAutomation.OPCServerClass' to type 'OPCAutomation.IOPCGroups'.
at System.StubHelpers.InterfaceMarshaler.ConvertToManaged(IntPtr& ppUnk, IntPtr itfMT, IntPtr classMT, Int32 flags)
at OPCAutomation.OPCServerClass.get_OPCGroups()
at Automation.OPCClient.OPCClientWrapper.Init(String serverIP, String opcServerName) in E:\Project\IoTGateway\Plugins\Drivers\OPC.DaClient\OPCClient\OPCClientWrapper.cs:line 132
Please help me,
Thanks

Hi, can you send the software  'OPC.Da.The server for the KEBA company is named Kestudio' to my email?

It is true that iotgateway cannot connect to KeStudio.Opc, and the enterprise version can be connected through other solutions, but the open source version is not available yet.


hypothesis.errors.HypothesisException: The $HYPOTHESIS_DATABASE_FILE environment variable no longer has any effect.

Hi,
todoman fails to build on Debian:  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952161
http://qa-logs.debian.net/2020/02/22/todoman_3.5.0-2_unstable.log
...
The manual pages are in build/sphinx/man.
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8/build; python3.8 -m pytest tests
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8/build/todoman/formatters.py:133: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if priority is None or priority is '':
ImportError while loading conftest '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8/build/tests/conftest.py'.
tests/conftest.py:165: in <module>
    settings(
/usr/lib/python3/dist-packages/hypothesis/_settings.py:175: in __init__
    kwargs[setting.name] = getattr(defaults, setting.name)
/usr/lib/python3/dist-packages/hypothesis/_settings.py:75: in __get__
    result = ExampleDatabase(not_set)
/usr/lib/python3/dist-packages/hypothesis/database.py:61: in __call__
    return _db_for_path(*args, **kwargs)
/usr/lib/python3/dist-packages/hypothesis/database.py:34: in _db_for_path
    raise HypothesisException(
E   hypothesis.errors.HypothesisException: The $HYPOTHESIS_DATABASE_FILE environment variable no longer has any effect.  Configure your database location via a settings profile instead.
E   https://hypothesis.readthedocs.io/en/latest/settings.html#settings-profiles
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=4: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8/build; python3.8 -m pytest tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.7" returned exit code 13
make: *** [debian/rules:28: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Can you provide the output of pip install?

The package is built only from other Debian packages. Maybe you want the version of hypothesis available on Debian? python3-hypothesis 4.36.2-1

I investigated a bit further and found the problem, which was in the packaging: we did set HYPOTHESIS_DATABASE_FILE to prevent the installation of the Hypothesis example file, to make the build reproducible. It does not seem to be useful anymore. Sorry about the false alert!


directory modTimes are ignored and can't be changed even when different.

$ mkdir -p A/B/C/D A/D/E && drive push A
$ drive push A
Resolving...
Everything is up-to-date. # Expected
$ drive touch --recursive A
/A: 2015-11-06 20:16:47 +0000 UTC
/A/D: 2015-11-06 20:16:48 +0000 UTC
/A/D/E: 2015-11-06 20:16:48 +0000 UTC
/A/B: 2015-11-06 20:16:49 +0000 UTC
/A/B/C: 2015-11-06 20:16:50 +0000 UTC
/A/B/C/D: 2015-11-06 20:16:51 +0000 UTC
$ drive pull A
Resolving...
Everything is up-to-date # Unexpected
$ drive list A
d- owner       0.00B     	0By5qQkvRAeV2TjhPdzVhNldJUjA		2015-11-06 20:16:49 +0000 UTC	/A/B
d- owner       0.00B     	0By5qQkvRAeV2Rmg0T2VwTzZPekk		2015-11-06 20:16:48 +0000 UTC	/A/D
$ ls -l A
total 3
drwx------+ 3 odeke ugrad 3 Nov  6 13:14 B
drwx------+ 3 odeke ugrad 3 Nov  6 13:14 D

Addressed by PR https://github.com/odeke-em/drive/pull/464


Document keySet query parameter

Fixes #2099

Coverage remained the same at 100.0% when pulling 8bc3030d97444be2b0e8bb0e89ebd494a85b08bf on eoogbe:spanner-docs-keyset into ae33610dff748dccfa5bfb6fd103cc9779f645d5 on GoogleCloudPlatform:master.

Rather than making the users write out the entire keySet object we've always supported the keys and ranges options (although I'm noticing ranges is not documented). These act as convenience options for keySet. Are there use cases for wanting to pass in a raw keySet object?
/cc @stephenplusplus @vkedia

My choice would be to allow "shorthand" options, but always allow "raw" options. createReadStream is called underneath, which accepts the raw query object: https://github.com/eoogbe/google-cloud-node/blob/8bc3030d97444be2b0e8bb0e89ebd494a85b08bf/packages/spanner/src/table.js#L113 -- it would be nice to allow the user to pass that through from read() as well.
Note that I'm not very well-versed in the conventions of Spanner and our API. If this was closed out for a reason, we probably just need better docs about it.

@callmehiphop @stephenplusplus The keySet option already works; it's just undocumented. This PR fixes that by adding documentation as requested in #2099. If we want to keep the documentation incomplete for some reason, we should close that issue.

I think it's fine to add this to the docs. We typically try to show the common-case options in the docs, and let the others exist on the cloud.google.com site, which we link to. In this case, we probably just overlooked keySet. Thanks for fixing this!


PHP 5.6 support

According to php7mar these arre the only issues to fix if we want this tool to work with php 5.6
# nuance
#### /Users/davidfernandez/htdocs/phpfmt8/fmt.stub.php
* funcGetArg
 * Line 863: `				$params = array_slice(func_get_args(), 1);`
 * Line 2215: `			$args = func_get_args();`
 * Line 2240: `			$args = func_get_args();`

phpcompatibility says

FOUND 4 ERRORS AFFECTING 4 LINES
4203 | ERROR | The constant "T_SPACESHIP" is not present in PHP version 5.6 or earlier
4819 | ERROR | The constant "T_COALESCE" is not present in PHP version 5.6 or earlier
4838 | ERROR | The constant "T_SPACESHIP" is not present in PHP version 5.6 or earlier
7608 | ERROR | The constant "T_SPACESHIP" is not present in PHP version 5.6 or earlier


Timezone issue with moment.js and with client time

After searching for hours I couldn't solve my issue. I saw your example on the plugin's website but whenever I change the machine time, the countdown changes too (on your website too!).  The strange thing is that a few months ago it was working!
Here is my code
 <script>   var countUTC = moment.tz('<?php echo $countdownField->format(DATE_ISO8601); ?>', "Europe/Athens"); $('div#clock').countdown(countUTC.toDate())     .on('update.countdown', function(event) {         $(this).html(event.strftime('<?php _e('%D days %H:%M:%S', 'sometextdomain'); ?>'));     })     .on('finish.countdown', function(event) {       $(this).html('Available! Refresh the page').css('font-size', '2rem');     });;      </script>
Can you reproduce the issue by changing your computer's time on your website's example?
Thanks!

Well I ended up doing @samgavinio solution
:)

I've noticed the same problem. Will have a look at that solution...


[AIRFLOW-3259] Internal Server Error when creating charts because of sort function

Check the following JIRA for more clarifications.
JIRA issue
Problem
When you try to create a chart and display metrics you get an internal server error.
Cause
A dependency issue: the function "sort" was deprecated and is no longer a part of pandas Dataframe and thus it creates a problem when creating charts in airflow.
Solution
The sort function needs to replaced by sort_values instead (See code below)
# Replace this
df = df.sort(df.columns[0])
# By this
df = df.sort_values(by=df.columns[0])
In views.py
Result
The data is loaded and the chart displayed

Could you retrigger the build please? Travis timed out on the last job for no apparent reason. I tried building my fork and it passed gracefully. Thank you.

Codecov Report

Merging #4093 into master will decrease coverage by 7.15%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #4093      +/-   ##
==========================================
- Coverage   77.91%   70.76%   -7.16%
==========================================
  Files         199      199
  Lines       15956    18251    +2295
==========================================
+ Hits        12432    12915     +483
- Misses       3524     5336    +1812

Impacted Files
Coverage Δ

airflow/www/views.py
68.73% <0%> (ø)
:arrow_up:

airflow/utils/dag_processing.py
42.78% <0%> (-47.57%)
:arrow_down:

airflow/example_dags/example_trigger_target_dag.py
55% <0%> (-36.67%)
:arrow_down:

...le_dags/example_passing_params_via_test_command.py
65.21% <0%> (-34.79%)
:arrow_down:

airflow/example_dags/example_subdag_operator.py
65.38% <0%> (-34.62%)
:arrow_down:

airflow/example_dags/tutorial.py
68.18% <0%> (-31.82%)
:arrow_down:

...low/example_dags/example_short_circuit_operator.py
68.42% <0%> (-31.58%)
:arrow_down:

airflow/example_dags/example_python_operator.py
64.28% <0%> (-30.46%)
:arrow_down:

airflow/example_dags/example_xcom.py
34.88% <0%> (-27.62%)
:arrow_down:

airflow/example_dags/example_skip_dag.py
67.85% <0%> (-27.15%)
:arrow_down:

... and 12 more

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 33be7fd...f904157. Read the comment docs.

How is it possible that my changes decreased code cov by 7% ?!!

@zackmeso Would it be possible to test this?

Hello @Fokko I answered you on this new PR
I created a new PR in order to comply with the contribution guideline.


Added menu_fixed to the sidebar, but scroll doesn't work / show up. I can't scroll through the sidebar.

As the title says.
I just added an external style="overflow:auto;" in the sidebar div class just to make the scroll "work" but it looks untidy.
menu_fixed doesn't work. Please help! Thank you! =)

A screenshot please ?

We assume you solved this one on your own after all so we will close this one for now.


update repo URL

Hunting down why I can't get npx bitburner-filesync to work from npm script, but works on the command line and I noticed this.  It isn't going to fix me, but this should probably match the true repo location 😎

Thanks, missed that one!


Getting cacheType none while retrievingImage after successful storing.

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[ ] I have read the wiki page and cheat sheet, but there is no information I need.
[ ] I have searched in existing issues, but did not find a same one.
[ ] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
I am getting cacheType as 'none' while retrieving image for a cacheKey after successful storing of that image.
Note: For sometimes I can able to retrieveImage, but after a while it returns none.
I have created my own ImageCache & set the disk expiration time to 'never'.
myCache = ImageCache(name: "myCache")
myCache?.diskStorage.config.expiration = .never

And store images using corresponding cacheKey for images
myCache?.store(image, forKey: cacheKey, completionHandler: { (result) in
    //getting success here
})

I can able to retrieve image for a few minutes. But after sometimes, the same retrieve image func returns cacheType as 'none'. Checked my cacheKey, there is no problem.
myCache?.retrieveImage(forKey: cacheKey) { result in
    switch result {
        case .success(let value):
            // cacheType is .none
        case .failure( _):
    }
}

Please help.

I tried it but cannot reproduce this issue.
The only possible reasons (if it is not a bug) are:

Your disk is full and the system cleared the disk cache.
Or maybe you are doing some cache cleaning manually.
Or you stored too many images in the disk and it exceeds the sizeLimit and the cleaning task is triggered inside Kingfisher.

Can this issue be reproduced in a sample project?

I didn't cleared the cache manually. BTW, I have stored many images (nearly 300 icons) but the size of each one will be around 200kb. I didn't set any sizeLimit for disk cache. What is the default sizeLimit for disk cache? Or do I have to explicitly mention the disk sizeLimit.

:( The default value is 0, means no limitation for disk cache.

Does it happen only when you switch your app background and then foreground? Or does it also happens when keeping using your app in foreground?
And since I cannot reproduce it myself, it is not an easy thing to guess what happens. It would be great help if you can provide a stable reproducible sample for this issue.

Not sure it occurs due to background & foreground switching of the app, because I cannot reproduce all the time. But after a while when I opened the app from background, the images are gone. If there is any solution for this switching case, I could try it.
Sorry I cannot provide you the sample project as it contains my company data. I will try with something similar to provide it to you.

Yes I can reproduce it now by switching the app to background and then foreground.

Switching app to the background will trigger Kingfisher's auto purge for memory cache. So it means your image is cached to memory successfully, but it fails to be cached to disk for some reasons. Can you try to make some change to your code like below and let me know the result?
cache.store(image, forKey: key) { result in
    print(result.diskCacheResult)
    print(cache.imageCachedType(forKey: key))
}

As you said, result. diskCacheResult returns Result.success(())
And cache.imageCachedType(forKey: key) returns as '.none' if I cleared the memoryCache as in your code.
If didn't do cache.clearMemoryCache(), then the imageCachedType returns as '.memory'

It is really strange. Let me check.

Does it have anything to do with my own cache name. If I create a cache with the same name again, it wont create another cache right?
What my app does is, those images will be downloaded only once while logging in by creating my own imageCache. If I killed the app & open it again, I create the cache by same name and retrieving the images. Only while logging out I'm clearing all the caches.

No problem. The same name will point to the same cache.
Will it work normally if you change to use the default cache ImageCache.default?

@RAITERN I've added and temporary log in the branch https://github.com/onevcat/Kingfisher/tree/try/creating-failure
Can you update your integration to that branch and check the log there? Thanks!

Just now tried that default.cache and it works good. But I need both my own cache(for disk expiration never) & I'm using default cache for another purpose.

What's the name of your own cache? Is it possible that you are using an invalid name so the disk cache fails?

"LogoCache" is the name.
logoCache = ImageCache(name: "LogoCache")

Seems fine. Maybe try to use all lower case? I am not sure although...

(And I want to declare again that the disk cache is not a good persistence if you want these images live there forever. Kingfisher uses system cache folder for caching purpose, and that folder could be purged by the system without noticing your app or the framework. But it is another story.)

Hi. Found the issue. On logging out I clear all the folder under cache directory which I use for several purpose to store files, which in turn removes the cache folder created by Kingfisher. However if I login again, it won't create the cache folder again even though I call 'ImageCache(name: "LogoCache")'. That why it cant store images again in disk.
It would be good to create the cache folder again if not available.
Also is there any way to use these cache image data in app extensions.

It should create the folder again when you call the ImageCache initializer, which in turn would call these code. A bit strange why that could happen.


Add support for GNU/Hurd

Do you have any notes about testing you've done with this?

The rust-mdns package went fine


rework build system

We want the build command to include everything it needs to build. We can do this by making the binary a polyglot file, where it is literally an executable followed by a zip file as one file. The zip file contains compile, link, and all the .a files of the standard library (plus whatever else we need to build wanix components). The build command can write these files out to /tmp, or with a zipfs it could temporarily mount itself (being a zip) file to a location. Then it can run as normal and then clean up.

Running into a linker issue, not entirely sure yet how to fix.

It seems the linker errors come from whether Library.Main is set to true. It's only set and read here. Here's the blame for the check as well.

I think it's worth looking into the main.a the compiler outputs. Maybe compare the binary output of the old working prototype compile and see if there's anything significantly different. If there's not a lot of ways for the linker to get to library.Main = false, it makes me think something is wrong/different with main.a

the problem seems to be in the compiled-out wasm (update from julian)


Bump gopkg.in/pg.v2 to v3

See https://github.com/snowplow/sql-runner/issues/38#issuecomment-156193816


Ping pong

Developer Checklist

[x] Followed guidelines mentioned in the readme file.
[x] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
[x] Starred ⭐ the Repo (Optional)

Summary
As mentioned in the issue  #748 , I added the ping pong multiplayer game in the repo please have a look and merge my pull request @PBJI

@PBJI Have a look

@ayan-joshi change name from Ping Pong to PingPong/ayan-joshi

okay.

@ayan-joshi change name from Ping Pong to PingPong/ayan-joshi

okay.

@PBJI did the change u asked

cannot add @ayan-joshi, delete Sort Visualizer from the above commit and please add PingPong/AyanJoshi as the directory name. Thank you

cannot add @ayan-joshi, delete Sort Visualizer from the above commit and please add PingPong/AyanJoshi as the directory name. Thank you

got it @PBJI , and did the changes

also delete the Sorting Visualizer directory that you accidentally left from your last commit in your fork.

@PBJI donee lesgo

I am sorry just one issue change it to PingPongGame instead as their already exist a directory by that name. And I'll merge it.
Thank you
Purshotam Bohra

@PBJI please merge its approved by @NitkarshChourasia

@PBJI please merge its approved by @NitkarshChourasia

I just review codes.
Merging standards, are being managed by @PBJI.
He takes care that it follows repository standards, as mentioned on README.md
@ayan-joshi
Thank you.
@NitkarshChourasia

@PBJI please merge its approved by @NitkarshChourasia

I am sorry just one issue change it to PingPongGame instead as their already exist a directory by that name. And I'll merge it.
Thank you Purshotam Bohra

Do this.

I just review them, merges are made by @PBJI
On Wed 11 Oct, 2023, 10:40 PM Ayan Joshi, @.***> wrote:

@PBJI https://github.com/PBJI @NitkarshChourasia
https://github.com/NitkarshChourasia made the changes please merge it
—
Reply to this email directly, view it on GitHub
https://github.com/thinkswell/javascript-mini-projects/pull/763#issuecomment-1758133629,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVTTXYHIUYIKYNIBW3JH3ATX63HJBANCNFSM6AAAAAA5X5XCKU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Good Night.
On Thu, 12 Oct 2023 at 02:46, Purshotam Bohra @.***>
wrote:

Merged #763
https://github.com/thinkswell/javascript-mini-projects/pull/763 into
master.
—
Reply to this email directly, view it on GitHub
https://github.com/thinkswell/javascript-mini-projects/pull/763#event-10624328917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVTTXYGFIHQTV3HG2TQL4X3X64ED3ANCNFSM6AAAAAA5X5XCKU
.
You are receiving this because you were mentioned.Message ID:
<thinkswell/javascript-mini-projects/pull/763/issue_event/10624328917@
github.com>

--
Nitkarsh Chourasia


Login/Register button on Startpage

The Startpage should contain a login/register button for anonymous users. The button can maybe be shown instead of the workspace container when the user isn't logged in.
The frontend knows whether the user is logged in based on the GET-Request to /workspaces, since the server responds with {success: false} if the user isn't logged in.

Because an anonymous user is created automatically if the user isn't logged in, we need a separate endpint specifically for checking if the user is anonymous or not. Using this info we can then show Sign up/Sign in buttons


Question on the default App ID URI value: What's controlling the format?

In the Tenant registration and tenant-verified domains section, the text states (emphasis added) ...

When you register a new app, the publisher domain of your app might be set to a default value. The default value depends on where the app is registered. The publisher domain value depends especially on whether the app is registered in a tenant and whether the tenant has tenant-verified domains.

It doesn't say exactly where tho. It doesn't make it clear what type of tenant has "tenant-verified domains."
I've looked at every Azure document that cites "App ID URI," and I can't find a clear explanation on the exact reason that the App ID URI defaults to either of the following formats:

https://{TENANT DOMAIN}/{SERVER API APP CLIENT ID} - Where only the {SERVER API APP CLIENT ID} is under dev control. Example: https://contoso.onmicrosoft.com/41451fa7-82d9-4673-8fa5-69eff5a761fd
api://{SERVER API APP CLIENT ID GUID} - Where the entire App ID URI is under dev control with some scheme limitations that the portal mentions when one edits the value. Example: api://41451fa7-82d9-4673-8fa5-69eff5a761fd

It seems like the default is based on the tenant type. The former value (the https:// version) is the default for Azure Active Directory B2C tenants. The latter value (api:// version) is the default for Azure Active Directory tenants. 🤔 I think. I can only base this on the cryptic remarks in this article, the Azure UI text and behaviors, and the behaviors of test apps in each of those tenant types. AFAICT, no Azure doc coverage exists to explain the exact values Azure provides ... but it's possible that I missed something, of course.
I'm not necessarily asking for this guidance to change. Can you just tell me if my assumption is correct?
I ask because I'm making updates to a pair of Blazor tutorials on https://github.com/dotnet/AspNetCore.Docs/pull/29067, and these default App ID URIs figure prominently in the guidance. Our hosted Blazor WebAssembly with AAD tutorial works with either type of tenant. However, devs who use our guidance with an app registered in a AAD B2C tenant must make default access token scope changes and server API configuration changes in their apps, both apps requiring an updated audience. I've been able to craft the guidance to cover it, but I'd sleep a lot better 🛌💤 knowing that I've written the guidance based on the correct assumption about what's controlling the format of the default App ID URI and that I'm telling readers the correct reason for the difference in App ID URIs.
Thanks in advance for any light you can shed on this.
cc: @jmprieur @hakenr

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

ID: 61edea45-b5d6-05b3-33c3-2265ef8cb309
Version Independent ID: c7d5813c-5cf1-44c3-88ff-3c194d3e44ad
Content: Configure an app's publisher domain - Microsoft Entra
Content Source: articles/active-directory/develop/howto-configure-publisher-domain.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

@guardrex
Thanks for your feedback! We will investigate and update as appropriate.

@guardrex
I'm going to assign this to the document author so they can take a look at it accordingly
@OwenRichards1
Could you Please review this and update as appropriate.

@ManoharLakkoju-MSFT ... Is there an Azure product unit engineer who could answer the question?
TL;DR ... All I really want to know is if the default format of the App ID URI in the portal for a new app registration is controlled by the Azure tenant type, either an "Azure Active Directory" tenant type (default format: api://{SERVER API APP CLIENT ID GUID}) or an "Azure Active Directory B2C" tenant type (default format: https://{TENANT DOMAIN}/{SERVER API APP CLIENT ID GUID})?
If we can get an answer to that question in the affirmative, I'll be able to sleep 🛌😴 easy knowing that I finally have it right in the official Blazor auth docs.


Move example*.tex and files/ from / to /examples/

The root directory of the project is starting to look hairy.
Tasks

[ ] Create directory examples/
[ ] Move example-*.tex and Markdown to examples/.
Drop the leading example- from the filenames, fix Makefile, and update compile instructions in README.md.
[ ] Move files/README.md to examples/.
[ ] Move files/ to examples/.
[ ] Fix .github/workflows/main.yml.

To allow the use of *.sty and *.tex files from the root directory, examples/Makefile should execute latexmk with the TEXINPUTS=.:..: environmental variable exported.

Here is how the updated compile instructions would look like:

To typeset the example documents, execute the following command on a system with
an up-to-date installation of TeX Live and Pandoc:
$ make -C examples

Alternatively, you can use the witiko/markdown Docker image, which includes
both TeX Live and Pandoc:
$ docker run --rm -it -v "$PWD":/workdir -w /workdir witiko/markdown \
> latexmk -shell-escape -pdf examples/man-pandoc.tex

All done.


ESM + Tests + Making Everything Green

General cleanup, building on the work Vlad did to start the new version. I want to get this to a nice state and then add a couple of features.
I'll update as I go, here in the issue.

Test Suites: 1 failed, 1 total
Tests:       102 failed, 1 passed, 103 total
Snapshots:   0 total
Time:        5.053 s

🍾

Epic holiday weekend. Not everything even makes sense, but we need to get some features in here before we release the main project.

todo: npm ci just doesn't work with the Eslint action. It may work with coverage.yaml, but I'm too afraid to try.
The sematic release action is an issue, but I want to pull that out of the project anyway.

Great work @roblarsen !


[SPARk-34848][SQL][FLLOW-UP] Fix merge conflict issue cause UT failed

What changes were proposed in this pull request?
Fix issue of  https://github.com/apache/spark/pull/31948#issuecomment-808647121
Why are the changes needed?
fix ut failed
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existed UT

gentle ping  @yaooqinn @srowen  cc  @c21

Test build #136583 has started for PR 31977 at commit f6fa5ac.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41167/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41167/

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

Test build #136583 has finished for PR 31977 at commit f6fa5ac.

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

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

@dongjoon-hyun @maropu @cloud-fan @HyukjinKwon Any committer can merge this quick fix? Since it will impact all tests.

Let me check.

Well, the master branch looks healthy according to the last commit. What is the problem here, @AngersZhuuuu ?

https://github.com/apache/spark/commit/769cf7b966cd2f980e385ac407f6b29f2a0389b9

Hm, got it. I'm running HistoryServerSuite now.

Oops, thanks. Looks like we had a bit of a race condition between two merges and test results.


setTimeout ignores timeout when called from page.includeJs() callback

<EMAIL_ADDRESS>commented:

Which version of PhantomJS are you using? Tip: run 'phantomjs --version'. => 1.7.0 win7 x64
What steps will reproduce the problem?
Run the attached JS file with phantomjs.
It will try and load google.com, include jQuery - both work fine and then tries do perform a setTimeout of 5 seconds. The function passed to setTimeout is called immediately.
What is the expected output? What do you see instead?
After the console log "BeforeTimeout" I expect 5 seconds to pass before "AfterTimeout" is written to the console. Instead, "AfterTimeout" is written instantly to the console.
Which operating system are you using?
Win7 x64
Did you use binary PhantomJS or did you compile it from source?
Binary
Please provide any additional information below.

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #832.
:star2:   6 people had starred this issue at the time of migration.

I have this issue as well. No delay on the timeout callback.

@simonklb Which version of phantomjs are you working with? I thought it was already resolved in one of the recent releases.

@apendua I got the build in the Ubuntu repo. Version 1.9.0. Which version is this solved in?

In that case you're using pretty outdated version. I guess you should try 1.9.8.

Looks like it's working, thanks! This should perhaps be marked as resolved then?

Just a note for users. 1.9.8 still had the setTimeout bug when I tried it. I updated to 2.0 and setTimeout works properly.

The setTimeout still doesn't work on my Fedora 21, phantomjs version 2.0

Still happening for me - PhantomJS 2.0 built from source on RHEL 6.3.

@ashafer01
use http://casperjs.org/ , which laverages the phantomjs. No issues with setTimeout

Still no working for me with Win 7 and phantom 2.0

https://newspaint.wordpress.com/2013/08/15/phantomjs-window-settimeout-appears-to-be-ignored/
solve my issue

Still facing the issue on Mac!!

Bump.  I have some code under test which uses setTimeout, the interval is ignored, the callback executes immediately.  I have the callback recurse on itself (it's a classic "wait for" pattern), but the recursion always dies after 3 iterations.  Versions:

PhantomJS 2.0.0
poltergeist 1.9.0 (Ruby gem)
Capybara 2.7.1 (Ruby gem)

The exact same spec passes 100% of the time when I have Capybara execute in Firefox instead of PhantomJS.

In fairness, I have tried to set up a minimal example, and could do it.  Something is particular to my code (websockets?) which is causing the problem.

Wow, this bug has been open for 4 years and still no resolution?

Solution:
setTimeout(function(){             setTimeout(function(){                 //Your function here             },700);         },1);

@frazras I remember using this fix ~3 years ago. It worked for some time and then it broke again with another release of phantomjs. Glad to hear it's working again, but I am also surprised that this issue has not been resolved for so long.

@frazras Right on time :)
https://developers.google.com/web/updates/2017/04/headless-chrome

I have been struggling with this issue as well. Did some quick tests to see if it was related to load.
Which version of PhantomJS are you using? Tip: run 'phantomjs --version
2.1.1
Which operating system are you using?
CentOS7
Did you use binary PhantomJS or did you compile it from source?
Binary
What steps will reproduce the problem?
Construct a HTML document with a number of Divs.  I did it in PHP (see attachment)
generateHTML.php.txt
start a setTimeout loop and have PhantomJS open the html we just generated, vanilla page.open logic:
var count = 0;
function counter()
{
  setTimeout(function()
  {
    count++;
    counter();
  }, 100);
}
function openPage()
{
  counter();
  var sTime = (new Date).getTime() / 1000;
  var url = http://devserver.example.com/test.htm
  page.open(url,  function(status) {
    var duration =  sTime  - (new Date).getTime() / 1000;
    console.log(duration);
    console.log(count);
  });
}

openPage();

The count is always 1. I then increase the number of Divs and measure how long it takes PhantomJS to open on localhost + memory consumption. CPU is locked at 100% when opening the page, i get memory from bash.
Here are the results:

As you can see there is not a linear relationship between the size of the document and load time or memory consumption. Also it appears page.open blocks all other processing.
Opening HTML with ~1200 divs causes PhantomJS to consume 10GB+ memory and almost 5 minutes just to open the page on a gigabit network.
This is the root cause of many exceptions when opening pages. I do not know C++ or i would help find the structure that causes memory and execution time to grow exponentially.

What might be the reason PhantomJS does not scale linearly with the size of the document?
Is it possible to push certain functions off the main thread?


DSpace 7.0: Bitstream download filename lose non-latin characters

Describe the bug
When download a bitstream having filename with character other than latin, those characters will be missing in file save dialog. For example, file named "ภาษาไทย File.pdf", will be saved as " File.pdf"
This happen only on 7.0, 6.x and earlier handle this properly.
To Reproduce
Steps to reproduce the behavior:

Running DSpace 7.0 on Tomcat 9.0
Upload a file to and item with non-latin character in file name, e.g. "ภาษาไทย File.pdf"
Download the file from DSpace 7.0 UI
Browser will suggest save file name " File.pdf" instead of the correct "ภาษาไทย File.pdf"

More Information
This happen because HttpHeadersInitializer does not encode filename in Content-Disposition header. It just use the file name as is. Since HTTP header (or Tomcat?) does not support UTF8, all non-latin characters become "?" in the header.
In contrast, DSpace 6.x encode filename in Content-Disposition header by using
MimeUtility.encodeText(name, "UTF8", "B");
Discussion
Although encoding filename work fine in earlier version of DSpace, I am wondering if the proper solution should be using filename* which can indicate character encoding?

I did some more searching and found this RFC https://datatracker.ietf.org/doc/html/rfc6266#section-4.3. My understanding is that the "filename" parameter only support ISO-8859-1 character set, and "filename*" allows other encoding like UTF-8. So, we should be adding a "filename*" parameter with RFC5987 encoding of file name.
We will try to fix this and submit a PR.


[BUG] the debug option doesn't check for missing network interfaces

In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}

[x] I have read and understood the contributors guide.
[x] The issue I am reporting can be replicated.
[x] The issue I am reporting is directly related to the pivpn installer script.
[x] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Describe the bug
If you remove the network interface originally specified when setting up pivpn then (at least with wireguard) the iptables rule will not be correct and the VPN will not route traffic properly, but the debug script doesn't check for this, or attempt to correct it.
To Reproduce
Steps to reproduce the behavior:
Go through the pivpn setup and choose a network interface that exists, remove that interface and then try and use the VPN and the debug function.
Expected behavior
The debug option should check available interfaces and warn that the interface originally specified no longer exists.
Additional context
This is probably fairly rare, but in my scenario I moved an SD card from a Pi 3B which I had plugged in via ethernet to a Pi Zero W which only has WiFi.
I was then stuck trying to figure out why my wireguard pivpn install was not working anymore. After a bit of digging through what the debug pivpn command was checking for and fixing, I saw that it looks for the iptables rule and will add it back if it is missing but it only ever uses the interface name originally given, so for my pi3 install this was eth0 yet now on the PiZero that interface didn't exist and only wlan0 is available for active network connections.
I think it'd be good if part of the debug script section greps for the available interfaces and checks to see if the ipv4dev variable name exists in the output, if it does not then you should be able to change the ipv4dev field to then allow the debug fixer to modify the iptables rule, this fixing the network issue I experienced.

Pre-archive closing, more information here


Capture Cplex specific errors and raise a unified optlang.SolverError [WIP]

When working with different optlang solver interfaces error handling should be agnostic. So far this is implemented for Cplex and Gurobi should come next. As far as I'm aware GLPK raises no errors but maybe surprising behavior should still be handled by raising from optlang. I'm not sure.
So far this pull request also implements test cases for accessing dual values on MIP problems. These should go into a separate branch/PR, I suppose.
Tests cannot pass at the moment since I introduce two failing tests due to the above.

Codecov Report

Merging #94 into devel will decrease coverage by 0.17%.
The diff coverage is 82.6%.

@@            Coverage Diff            @@
##           devel      #94      +/-   ##
=========================================
- Coverage   88.8%   88.63%   -0.18%
=========================================
  Files          8        8
  Lines       2386     2419      +33
  Branches     542      542
=========================================
+ Hits        2119     2144      +25
- Misses       166      174       +8
  Partials     101      101

Impacted Files
Coverage Δ

optlang/exceptions.py
100% <100%> (ø)
:arrow_up:

optlang/cplex_interface.py
88.92% <81.39%> (-0.92%)
:arrow_down:

Continue to review full report at Codecov.

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

Closing due to #96 which is a polished version of this branch.


Import error when not using node

When not using bulma using node (npm, yarn), sass throws the following error:
Error: File to import not found or unreadable: node_modules/bulma/sass/utilities/mixins.
            on line 1:1 of bulma-list/sass/bulma-list.sass
            from line 35:1 of css/default.scss
    >> @import "node_modules/bulma/sass/utilities/mixins";

       ^

Use case: I have bulma and bulma-list as git submodules instead of using a package manager.
Removing the bulma import on the first line of /sass/bulma-list.sass worked for me.

Hey — thanks! This wasn't really needed in that file anyway and could have been causing some side effects in certain cases too. Should be sorted for you in https://github.com/bluefantail/bulma-list/releases/tag/v1.2.0


Add toolbar select from settings.json

Add color dropdown from settings.json, if not in settings will use default template

Bump @ilmartyrk

Bump @ilmartyrk

n1 thanks :)  Wonder if it's worth copy/pasting this to other font plugins IE size, family, align, line height??

n1 thanks :)  Wonder if it's worth copy/pasting this to other font plugins IE size, family, align, line height??


[Spatial Editor] weird object selection when changing from VIEW_PERSPECTIVE to VIEW_ORTHOGONAL

Godot version:

3ca06e1184e49abd300bce03db1bec0e559c0d03.
OS/device including version:

Debian 8.10
Issue description:

Weird object selection when changing from VIEW_PERSPECTIVE to VIEW_ORTHOGONAL
Steps to reproduce:
In Spatial editor (in perspective view), click on an object, to select it... change then to orthogonal view... after doing some action on the viewport, the selection tool is then fine rendered again.
(1) Select object in perspective view

(2) After changing to orthogonal view

duplicated with #14619


[cryptolib] change implementation of HW backed keys

Description
Due to #22283, #22297, #22296 it is unlikely we will be able to claim that output of keymgr is a "key" in the NIST sense. This means we need to revisit implementation of hw backed keys and stop using sideloading  from keymgr where FIPS-approved key is needed.
One of the solution would be to use DRBG to mix entropy, keymgr output and additional inputs and use its output as a key or key candidate. We can try to employ CSRNG wherever possible or use SW DRBG.
@ballifatih @jadephilipoom

removing Hotlist label since will be discussed in other forum


unrecognized element  [ warning ]

Describe the Bug

[/home/falko/git/bpmn-miwg-demos/2020-06-omg-technical-meeting-boston/discussion/parent-process.bpmn] unparsable content <import> detected
	line: 4
	column: 2
	nested error: unrecognized element <import> [ warning ]

Steps to Reproduce

Open a BPMN model with an import element, e.g. https://github.com/bpmn-miwg/bpmn-miwg-demos/blob/master/2020-06-omg-technical-meeting-boston/discussion/parent-process.bpmn
See log

Expected Behavior

At least no warning should appear because it is a valid BPMN element.
Environment

OS: Ubuntu 18.04.3 LTS
Camunda Modeler Version: 3.1.2

This issue was discovered during the preparation of the 2020 BPMN MIWG demo.

The import element is the only one missing the prefix. Adding the prefix fixes the issue.

Oops. Thank you for the hint. It looks like I shouldn't be handcrafting BPMN XML in the middle of the night ;-)


Extend architecture test to include ARM6/7/8

This adds if branches for choosing the correct architecture names for
armv6l, armv7l, and arm64 variants in addition to the x86 and x64 variants.
Fixes #38

Hey, is this repo maintained? I like this better than the npm plugin and would like it to stick around.

@ryanq Things have been slow for a while, but yes, it still is.


tlsextraip settings for LND

Currently if I have there are more than 1 lines of tlsextraip is given in the lnd.conf there is a warning on the LCD:
While reading from '<string>' [line 18]: option 'tlsextraip' in section 'Application Options' already exists

Also the default setting tlsextraip=<IP_ADDRESS> is not useful.
Any IP address or domain used to connect vis REST or GRPC needs to be added as a new
tlsextraip= or tlsextradomain= line.
See: https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf#L31

Ah.. My bad. So you would suggest to not do any configuration validation from Raspiblitz side..?

LND would not start with an erroneous lnd.conf, so I don't see the merit of checking it again.

@openoms when is that happening ... the nodes I am running all just have one tlsextraip line and all is good.

I needed to use multiple lines due to connecting through ZeroTier and using the Tor2IP tunnel too.

I agree. The tlsextraip=<IP_ADDRESS> line makes no sense and should be removed.

Interessting (re)discovery.. run this on your Node: openssl x509 -in /mnt/hdd/lnd/tls.cert -noout -text | grep -A 1 "Subject Alternative Name"

I opened https://github.com/lightningnetwork/lnd/issues/4271 for the "finding" in my last comment here.

when is that happening ... the nodes I am running all just have one tlsextraip line and all is good.

@rootzoll The point isn't really when this is happening.. the line makes no sense to me in any scenario. There is no possibility to connect to a RaspiBlitz using <IP_ADDRESS> as the destination IP address.
My suggestion would be to remove the lines that add this to lnd.conf from lnd.autounlock.sh. But I'm not sure whether we should also actively remove it from /mnt/hdd/lnd/lnd.conf. People who care can do this themselves. And new installations will not longer have this setting added.
Let me know if I missing something.

Found an interesting setting here: https://github.com/alexbosworth/run-lnd
# Delete and recreate RPC TLS certificate when details change or cert expires
tlsautorefresh=1

Found an interesting setting here: https://github.com/alexbosworth/run-lnd
# Delete and recreate RPC TLS certificate when details change or cert expires
tlsautorefresh=1

# Delete and recreate RPC TLS certificate when details change or cert expires
tlsautorefresh=1

# Do not include IPs in the RPC TLS certificate
tlsdisableautofill=1

@openoms To not include IPs at all could maybe help a lot to make to prevent TLS changes at all.

# Delete and recreate RPC TLS certificate when details change or cert expires
tlsautorefresh=1

# Do not include IPs in the RPC TLS certificate
tlsdisableautofill=1

@openoms To not include IPs at all could maybe help a lot to make to prevent TLS changes at all.

@rootzoll yes we should definitely try these

@rootzoll yes we should definitely try these

# Delete and recreate RPC TLS certificate when details change or cert expires
tlsautorefresh=1

# Do not include IPs in the RPC TLS certificate
tlsdisableautofill=1

@openoms To not include IPs at all could maybe help a lot to make to prevent TLS changes at all.

Tested these with good results. Only drawback was that my LND restarted without notice after regenerating the TLS.cert and sat for waiting for the password C.
The TLS.cert was expired a couple days ago, but the refresh only happened hours after I have set the lnd.conf. Did not restart after removing an IP from tlsextraip= eitehr so not sure what was the trigger of the restart. Anyway it is better then having the authenticated GRPC connections stop working because of the expired cert.
Old cert:
admin@rpi64:~ $ openssl x509 -text -noout -in /mnt/hdd/backup_lnd/tls.cert
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            51:d7:92:0f:93:71:90:a5:d2:96:e8:ba:8f:a7:7d:cb
        Signature Algorithm: ecdsa-with-SHA256
        Issuer: O = lnd autogenerated cert, CN = raspberrypi
        Validity
            Not Before: Nov  9 19:22:23 2020 GMT
            Not After : Jan  4 19:22:23 2022 GMT
        Subject: O = lnd autogenerated cert, CN = raspberrypi
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:bb:ad:91:f6:73:1e:9b:f2:6b:5b:3c:bb:fb:90:
                    08:06:a5:69:56:65:1b:ea:a7:46:fb:df:20:f7:c8:
                    60:bd:d3:c5:08:bb:bd:bd:9f:c2:f9:5b:ad:e6:c6:
                    d1:de:8a:d5:77:df:83:66:c3:79:a0:1f:ce:59:34:
                    5f:74:9d:42:56
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Extended Key Usage:
                TLS Web Server Authentication
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Alternative Name:
                DNS:raspberrypi, DNS:localhost, DNS:unix, DNS:unixpacket, DNS:bufconn, IP Address:<IP_ADDRESS>, IP Address:0:0:0:0:0:0:0:1, IP Address:192.168.X.XXX, IP Address:XXXX:0:0:0:XXXX:XXXX:XXXX:XXXX, IP Address:XXXX:0:0:0:XXXX:XXXX:XXXX:XXXX, IP Address:EXTERNAL_IP_set_in_lnd.conf
    Signature Algorithm: ecdsa-with-SHA256
         30:45:02:20:47:9d:fe:49:b5:de:97:7d:5f:19:8b:21:0e:0d:
         a7:b2:4a:40:e8:f4:17:5a:a4:0b:ff:d2:11:56:00:b6:f4:91:
         02:21:00:b3:b6:aa:93:14:ab:6a:93:0e:9d:6d:59:09:e4:28:
         09:92:7c:9d:e2:dc:05:69:50:8b:3a:50:fa:1b:4f:bd:67

Also solves the issue raised by @frennkie in: https://github.com/lightningnetwork/lnd/issues/4271 by leaving out the internal IPv4 and IPv6 addresses.
openssl x509 -text -noout -in /home/admin/.lnd/tls.cert
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            e2:5d:07:fb:5a:1c:f7:9b:0d:83:eb:29:8d:33:ef:61
        Signature Algorithm: ecdsa-with-SHA256
        Issuer: O = lnd autogenerated cert, CN = localhost
        Validity
            Not Before: Jan 12 04:46:34 2021 GMT
            Not After : Mar  9 04:46:34 2022 GMT
        Subject: O = lnd autogenerated cert, CN = localhost
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:29:ce:03:3c:2a:f2:49:71:91:13:c4:e4:1a:aa:
                    65:be:90:9e:5a:63:78:f7:b5:1b:98:91:1b:22:7f:
                    a5:3d:ef:f4:d9:9b:a6:54:02:17:57:6b:ed:a3:81:
                    37:94:fb:f8:8c:15:b2:9c:38:23:f6:0b:5c:9b:ca:
                    6a:69:e8:40:8b
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Extended Key Usage:
                TLS Web Server Authentication
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Alternative Name:
                DNS:localhost, DNS:unix, DNS:unixpacket, DNS:bufconn, IP Address:<IP_ADDRESS>, IP Address:0:0:0:0:0:0:0:1
    Signature Algorithm: ecdsa-with-SHA256
         30:45:02:21:00:f4:ab:12:97:68:77:92:75:b1:3a:df:bd:db:
         54:bf:04:d9:8e:eb:24:04:d4:2b:d7:7c:56:a0:51:69:4a:da:
         ff:02:20:0f:f7:14:0a:5d:b6:15:ce:89:00:17:8b:66:27:0a:
         82:f1:c1:64:68:f0:87:9a:c5:b0:0b:96:fd:41:ea:f8:55

We should add both flags by default to the LND.conf.

# Delete and recreate RPC TLS certificate when details change or cert expires
tlsautorefresh=1

# Do not include IPs in the RPC TLS certificate
tlsdisableautofill=1

@openoms To not include IPs at all could maybe help a lot to make to prevent TLS changes at all.

Tested these with good results. Only drawback was that my LND restarted without notice after regenerating the TLS.cert and sat for waiting for the password C.
The TLS.cert was expired a couple days ago, but the refresh only happened hours after I have set the lnd.conf. Did not restart after removing an IP from tlsextraip= eitehr so not sure what was the trigger of the restart. Anyway it is better then having the authenticated GRPC connections stop working because of the expired cert.
Old cert:
admin@rpi64:~ $ openssl x509 -text -noout -in /mnt/hdd/backup_lnd/tls.cert
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            51:d7:92:0f:93:71:90:a5:d2:96:e8:ba:8f:a7:7d:cb
        Signature Algorithm: ecdsa-with-SHA256
        Issuer: O = lnd autogenerated cert, CN = raspberrypi
        Validity
            Not Before: Nov  9 19:22:23 2020 GMT
            Not After : Jan  4 19:22:23 2022 GMT
        Subject: O = lnd autogenerated cert, CN = raspberrypi
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:bb:ad:91:f6:73:1e:9b:f2:6b:5b:3c:bb:fb:90:
                    08:06:a5:69:56:65:1b:ea:a7:46:fb:df:20:f7:c8:
                    60:bd:d3:c5:08:bb:bd:bd:9f:c2:f9:5b:ad:e6:c6:
                    d1:de:8a:d5:77:df:83:66:c3:79:a0:1f:ce:59:34:
                    5f:74:9d:42:56
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Extended Key Usage:
                TLS Web Server Authentication
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Alternative Name:
                DNS:raspberrypi, DNS:localhost, DNS:unix, DNS:unixpacket, DNS:bufconn, IP Address:<IP_ADDRESS>, IP Address:0:0:0:0:0:0:0:1, IP Address:192.168.X.XXX, IP Address:XXXX:0:0:0:XXXX:XXXX:XXXX:XXXX, IP Address:XXXX:0:0:0:XXXX:XXXX:XXXX:XXXX, IP Address:EXTERNAL_IP_set_in_lnd.conf
    Signature Algorithm: ecdsa-with-SHA256
         30:45:02:20:47:9d:fe:49:b5:de:97:7d:5f:19:8b:21:0e:0d:
         a7:b2:4a:40:e8:f4:17:5a:a4:0b:ff:d2:11:56:00:b6:f4:91:
         02:21:00:b3:b6:aa:93:14:ab:6a:93:0e:9d:6d:59:09:e4:28:
         09:92:7c:9d:e2:dc:05:69:50:8b:3a:50:fa:1b:4f:bd:67

Also solves the issue raised by @frennkie in: https://github.com/lightningnetwork/lnd/issues/4271 by leaving out the internal IPv4 and IPv6 addresses.
openssl x509 -text -noout -in /home/admin/.lnd/tls.cert
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            e2:5d:07:fb:5a:1c:f7:9b:0d:83:eb:29:8d:33:ef:61
        Signature Algorithm: ecdsa-with-SHA256
        Issuer: O = lnd autogenerated cert, CN = localhost
        Validity
            Not Before: Jan 12 04:46:34 2021 GMT
            Not After : Mar  9 04:46:34 2022 GMT
        Subject: O = lnd autogenerated cert, CN = localhost
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub:
                    04:29:ce:03:3c:2a:f2:49:71:91:13:c4:e4:1a:aa:
                    65:be:90:9e:5a:63:78:f7:b5:1b:98:91:1b:22:7f:
                    a5:3d:ef:f4:d9:9b:a6:54:02:17:57:6b:ed:a3:81:
                    37:94:fb:f8:8c:15:b2:9c:38:23:f6:0b:5c:9b:ca:
                    6a:69:e8:40:8b
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Extended Key Usage:
                TLS Web Server Authentication
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Alternative Name:
                DNS:localhost, DNS:unix, DNS:unixpacket, DNS:bufconn, IP Address:<IP_ADDRESS>, IP Address:0:0:0:0:0:0:0:1
    Signature Algorithm: ecdsa-with-SHA256
         30:45:02:21:00:f4:ab:12:97:68:77:92:75:b1:3a:df:bd:db:
         54:bf:04:d9:8e:eb:24:04:d4:2b:d7:7c:56:a0:51:69:4a:da:
         ff:02:20:0f:f7:14:0a:5d:b6:15:ce:89:00:17:8b:66:27:0a:
         82:f1:c1:64:68:f0:87:9a:c5:b0:0b:96:fd:41:ea:f8:55

We should add both flags by default to the LND.conf.

OK changes were merged into dev for v1.7RC1 release for testing. But still some further questions see:
https://github.com/rootzoll/raspiblitz/pull/1943#issuecomment-807318797

OK the new strategy in the config will now be added for old nodes on update/recover: https://github.com/rootzoll/raspiblitz/blob/45784b2b716c96eb1944b74fe24210f23abf77e3/home.admin/_bootstrap.migration.sh#L210


Add stats and capacity score calculation

@richbrowne
What issues does this address?
Need capacity score calculation to support multi-agent scheduling.
Fixes #177
What's this change do?
Adds functions to get stats needed for capacity score function; adds generate capacity function; adds capacity score section to agent ini file; adds tests of stats functions.
Where should the reviewer start?
Start with generate_capacity_score() in icontrol_driver.py
Any background context?
Supporting same functionality as in LBaaS v1.
Issues:
Fixes #177
Problem: Need capacity score caclulations for BIG=IPs in order
to support multi-agent scheduling.
Analysis: Added mutliple stat functions and generate_capacity_score()
function
Tests: test_stats.py

Jeff, I am going to merge this.  The tests that I suggested can be merged separately.


CM-31412 - Fix severity sorting for unknown severity

as i understand it breaks this code:
https://github.com/cycodehq/cycode-cli/blob/7978be2c8bb91681510a95dca922a496a11b714e/cycode/cli/commands/scan/code_scanner.py#L756-L761

ig we can create Severity.get_value (without try) and return -2 if non exists. and leave existing method without changes
or even get_sort_value/get_member_weight to be more clear. and this method will be used in table printer

as i understand it breaks this code:
https://github.com/cycodehq/cycode-cli/blob/7978be2c8bb91681510a95dca922a496a11b714e/cycode/cli/commands/scan/code_scanner.py#L756-L761

Fixed

ig we can create Severity.get_value (without try) and return -2 if not exists. and leave the existing method without changes
or even get_sort_value/get_member_weight to be more clear. and this method will be used in table printer

@morsa4406 in case you missed this. btw linter failed


Update Network.ini

Updated External IP check to use ipify.org, as it has a better uptime history and is not blocked by most security proxies (blueCoat, etc) like wtfismyip.com is.  Its a dropin replacement.

Nice find! I chose wtfismyip.com because it was simple, straightforward, and very reliable, but this is even better!
One thing though: Please add the URL as well as the regex code to the comments block below the measure. Once that's done, I'll merge it.

Good call.  Done.


feat: Add heartbeat endpoint & tests

This PR adds an cron job endpoint that, when triggered, sends an cron job heartbeat to Sentry.

Please see my comment on the slack message. That is not going to be a robust way to alert people that the system is down. You want a proper datadog alert with pagerduty attached instead.

Added Sentry cron job monitoring + datadog event alerts


Java 8 is still supported - Should Randochoose also run with that?

That's the problem - On a computer where Java 8 was still installed, it received an update yesterday - for the Java version that's considered obsolete. Turns out it's still supported until 2025. Shall we support Java 8?

No, it shouldn't!


python310Packages.sfrbox-api: 0.0.4 -> 0.0.5

Changelog: https://github.com/hacf-fr/sfrbox-api/releases/tag/v0.0.5
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Thank you!


Japronto CORS

How can I use CORS in Japronto?
I'm already try to use Flask-CORS, Sanic-CORS but doesn't work for me.

add request.Response header


Replace magic GAS_LIMIT constant with something intuitive

Right now, you cannot spend more than pub const GAS_LIMIT: u64 = 10_000_000_000; gas in a contract. This number is an arbitrary choice. It should be possible to change it to u64::MAX, allowing you to not worry about the value anymore. communicating that there is no special reason to

After some debugging I now believe that the points used in Wasmer metering can overflow. We get logs like this:
set_points_used:<PHONE_NUMBER>3709531615
get_points_used:<PHONE_NUMBER>3709531615
try_consume_gas: 134
get_points_used: 41721

Since there is no set_points_used from us between get_points_used:<PHONE_NUMBER>3709531615 and get_points_used: 41721, it must be the Wasmer execution that triggers an overflow. When points used can overflow, it must not be close to u64::MAX.


Throttle position went up while braking for Gen 2 BRZ

Hi Timur,
Thanks for putting the database together. I was able to use it for my THW track day and it was super helpful!
One issue I found is sometimes when I brake, the throttle position captured would go up too even though I didn't touch the throttle at all. You can see the video here when I entered T3. I didn't downshift so there shouldn't be throttle movements at all.
I'm new to CAN bus data logging so I'm not sure what could've caused this. Is this because of a bad equation/PID/RaceChrono/CAN adapter? I used a CAN adapter I purchased online which is specifically designed for Gen 2 BRZ and GR86.
Any help is appreciated!

Hi Yaoming!
The underlying CAN bus data protocol makes it pretty much impossible for any wiring issue to cause wrong data to be received — it has checksums and stuff. It would be a lot more likely to just stop receiving data than to get wrong data.
In your video, I see the throttle pedal data going smoothly from 0% to 15% slightly after you start braking, and smoothly going back to 0% pretty much in sync with how you release the brakes.
My hunch is that you did in fact touch the throttle pedal without realizing it.
The throttle pedal in these cars is pretty light, so it's hard to notice when it's only lightly pressed, and 15% requires very little force.
I guess at this point we don't have good data to prove that this is what actually happened (or to prove that it definitely didn't happen)...
If you see this happening often, you might consider using a foot cam to see what's going on down there.

Also minor unrelated tip: since you already have the steering angle gauge and you see the steering wheel in your video, you should be able to sync the data to the video more precise.
In your video, the data is a bit behind the video.

Hmmm, interesting... I checked the videos from some other laps and they don't seem to have this issue sometimes, so actually could be a user error :) Thanks for pointing this out!
Re: video sync - I tried using RaceChrono to sync the GoPro videos for me but unfortunately, my phone just doesn't have enough storage space needed so I had to manually sync in iMovie which is much more error-prone :(


Create the Single Page User View

When a user clicks on their profile
Then they are presented with information about themselves
They see a list of saved jobs

Completed


Revisit kwargs in open_remote.

This passes more Catalog parameters through and I think a little more
clear as well.

@danielballan , perhaps we should catch up in the next couple of days, if you have the time.

To clarify: this PR affects the case that a remote catalog is opened from within another remote catalog - then the three parameters getenv, getshell and auth should be passed on.
I think this is a good idea in general. Do you think it's possible that the auth parameter (or all three) should be overridable somehow? I'm thinking that the new remote cat may be on a different server - is this possible?

It does seem like it might be possible and useful to allow for. At this point I don't think I have a firm enough grasp of the different ways that information can flow to be sure how to do implement that.

OK, I will merge this now, and we can postpone working on the idea I surfaced above. Perhaps that should be written into a new issue to track it.


Motion Matching as an addon

I know very little about motion matching, so this may take time
I will try to learn motion matching and implement it in the system as a plugin so anyone could take the plugin and use it in another project without the need for AMSG

Motion Matching Example :
https://youtu.be/307omU48Feg
Motion Matching Explanation :
https://youtu.be/Egp1rQh1FAg

@ywmaa
Coordinate Godot Motion Matching


Cannot reference ServiceHelper

Probably something simple but I've not been able to figure out how to reference ServiceHelper in the LocalizeExtension class. Google searches have turned up the Microsoft Enterprise Libraries but these seem quite old and on the path of deprecation leading me to believe there something I'm missing. I did check the project file with no luck. Thanks in advance!

Yep, it was simple! Totally missed the "ServiceHelper.cs" file! [Forehead-slap]


Niivue cleanup after useEffect unmount.

Hi
I am using niivue to display a 3d rendering, but the memory used by page is kept on increasing after every swtich to a new image. I believe I am not doing  aproper unmount cleanup.
As a part of cleaning up, I am removing all volumes and updating the GLvolume, but looks like the earlier image arrays are still persisting in the memory.  The images, I am fecthing are of a size of 100+ MB, so I clearly see the memory increase.
I am no expert in WebGL and pretty new react. would apprecaite your inputs.
following is my unmount cleanup
return () => {

        for (let i = 0; i < nv2.volumes.length; i++) {
          nv2.removeVolumeByIndex(i);
        }
        nv2.updateGLVolume();
      }

partial roguh code I am using.
 const [nv2,setNv2] = useState(new Niivue())
  useEffect(() => {

    console.log("TRIGGER: Image attachment")
    nv2.attachTo("gl2");
    setInitialRender(!initialRender);
    }, []);

 useEffect(()=> {

    nv2_volumelist = [
                  {
                    url: `${process.env.REACT_APP_FLASK_API_URL}/data/Alzhemier/Normal/Boundary/${props.fileName}`,
                    colormap: "gray",
                    opacity: 0.15,
                    visible: true,

                },
                    {
                        url: data.url + `?nocache=${new Date().getTime()}`,
                        colormap: "actc",
                        opacity: 0.9,
                        visible: true,
                        cal_min: data.cal_min,
                        cal_max: data.cal_max,
                        trustCalMinMax: true
                    }
                ];

nv2.loadVolumes(nv2_volumelist);
nv2.setSliceType(nv2.sliceTypeRender)

return () => {

        for (let i = 0; i < nv1.volumes.length; i++) {
          nv2.removeVolumeByIndex(i);
        }
        nv2.updateGLVolume();
      }

}, [props.fileName]);

@hari7696 , in your clean up code, you are referencing nv1 in the for loop, but all other niivue instances in your code snippet are referenced as nv2. Is this a typo, or the source of your observed issue?
In addition, you may want to look into useContext and createContext with React. We use this in our NiiVue desktop app. Here is an example.

@hari7696 , please reopen if you can provide a minimal React demo showing the bad behaviour.

Hi @hanayik @neurolabusc
Thanks for the inputs, here is the standalone code that simulates the issue I am facing.
I hosted the code here : https://devmetavision3d.rc.ufl.edu/  in "dummy" tab

import React, { useState, useEffect } from 'react';
import { Niivue } from '@niivue/niivue';
import { Dropdown, DropdownToggle, DropdownMenu, DropdownItem } from 'reactstrap';

function DummyRender() {
  const [fileName, setSelectedFile] = useState("");
  const [dropdownOpen, setDropdownOpen] = useState(false);
  const [isattached , setIsAttached] = useState(false);
  const nv1 = new Niivue();
  const nv2 = new Niivue();

  const files = ["5x_ADP.nii.gz","5x_AMP.nii.gz","5x_Aarachidonic.acid.nii.gz","5x_Alanine.nii.gz","5x_Ascorbic.Acid.nii.gz","5x_Aspartate.nii.gz","5x_Carnosine.nii.gz","5x_Citric.Acid.nii.gz","5x_Docosahexaenoic.acid.nii.gz","5x_Fructose.1.6.Bisphosphate.nii.gz","5x_G6P.nii.gz","5x_GMP.nii.gz","5x_GSH.nii.gz","5x_Glucose.nii.gz","5x_Glutamate.nii.gz","5x_Glutamine.nii.gz","5x_Glycerol.3.phosphate.nii.gz","5x_Glycerophosphorylethanolamine.nii.gz","5x_HEME.nii.gz","5x_Hypoxanthine.nii.gz","5x_IMP.nii.gz","5x_Inosine.nii.gz","5x_LPA..20.1..nii.gz","5x_LPA..20.4..nii.gz","5x_LPA..22.4..nii.gz","5x_LPA..22.6..nii.gz","5x_LPA.18.0..nii.gz","5x_LPA.18.1..nii.gz","5x_LPE..16.1..nii.gz"]

  useEffect( () => {
     nv1.attachTo('gl1');
     nv2.attachTo('gl2');
    setIsAttached(true);
  }, [fileName]);

  useEffect(() => {

    console.log("Main  func invoked")
    if (isattached) {
      console.log("volumes loading")
      const volumeList1 = [
        {
          url: `https://devmetavision3d.rc.ufl.edu/data/Alzhemier/Disease/Inverted/${fileName}`,
          opacity: 0.9,
          visible: true,
          colormap: 'blue2red',
        }
      ];
      nv1.loadVolumes(volumeList1);
      nv1.updateGLVolume();
      nv1.setSliceType(nv1.sliceTypeAxial);

      nv2.loadVolumes(volumeList1);
      nv2.updateGLVolume();
      nv2.setSliceType(nv2.sliceTypeRender);
    }

    return () => {
      for (let i = 0; i < nv1.volumes.length; i++) {
        nv1.removeVolumeByIndex(i);
      }

      for (let i = 0; i < nv2.volumes.length; i++) {
        nv2.removeVolumeByIndex(i);
      }
      setIsAttached(false);
      console.log("Volumes removed");
    };
  }, [fileName]);

  const toggleDropdown = () => setDropdownOpen(prevState => !prevState);

  return (

            <Dropdown isOpen={dropdownOpen} toggle={toggleDropdown} style={{ textAlign: 'left', width: '300px', padding: '10px' }}>
                <DropdownToggle caret  style={{ width: '400px' }}>
                    {fileName || "Select a file"}
                </DropdownToggle>
                {/* The right prop is omitted or set to false for left alignment */}
                <DropdownMenu className="scrollable-menu">
                    {files.map((file, index) => (
                        <DropdownItem
                            key={index}
                            onClick={() => setSelectedFile(file)}
                        >
                            {file}
                        </DropdownItem>
                    ))}
                </DropdownMenu>
            </Dropdown>

Wild Type Brain

          <canvas id="gl1" style={{ width: '500px', height: '400px' }}></canvas>

          <canvas id="gl2" style={{ width: '500px', height: '400px' }}></canvas>

  );
}

export default DummyRender;

Behaviour observed.

After every image switch, the the Memory usage [ Windows Task Manager] is kept on increasing. I am adding screen grabs taken between image switches.

I monitored the page performance as well, I dont see any exponential increase.

@hari7696 , from what I can see, it looks like you have two useEffect statements that have the same dependency. In the past, this has caused issues in my other apps.
Also, your implementation seems to create a new Niivue instance on every re-render. I would suggest using useContext or useRef for the Niivue instances. I would also leave the Niivue instances attached to the canvas, and just use the Niivue removeVolume and loadVolumes methods to change the image you want rendered in the canvas.

when I use the useContext  and createContext, I am loosing the webGL context, if I dont attach them to canvas everytime. It would be great if you can provide a template code on how can I leave the niivue instances attached. I believe, what I am asing goes beyond the scope of this framework, but I would apprecaite the input. Thanks.

Hi @hanayik
Thanks for the suggestion. Switching to useRef and leaving the instances attached solved my issue.


we inconsistently rm thing with and without docker

this causes a problem if you have manually deleted the image before running clean.

LGTM

The reason we added docker to those commands was to make the permission situation easier. When you build the binaries in docker, the bin folder that is created and everything in it is owned by root, so my account can't rm -rf bin without sudo. Running it in docker got around this as a hack. Ideally we could make the files created in our build process be owned by the user that ran make build, but I looked into it a bit and it seemed like a very painful process.

I'd love for the docker build to not run as root for this reason. From what I understand, the build container would need to create a user with the same gid as the host system and add a USER line.

Whelp, it seems the new deploy stage actually runs into this exact issue when trying to deploy our releases. In the interest of unblocking our release, and because in the grand scheme of things having to sudo rm -rf bin is not the worst thing in the world and the ownership issue should eventually be solved, I'm happy with this going in.


IGeoLocator TimeSpan? added to interface, but not implementations

Bug
It could be my lack of full understanding of the Git environment, but the IGeoLocator interface was updated to use TimeSpan? instead of int (milliseconds) but the implementation was not updated.  As a result the build is currently broken.

The current repo is a work in progress and reflects 4.0.


explain cyano-rhodo coculture metabolite excretions based on computational simulations

@ShantMahserejian Include co-culture visualization for @djinnome. I will provide a flux file.


feat: add completion command

Usage:
NAME:
   envd completion - Install shell completion scripts for envd

USAGE:
   envd completion [command options] [arguments...]

CATEGORY:
   Management Commands

OPTIONS:
   --shell value, -s value [ --shell value, -s value ]  Shell type to install completion
   --help, -h                                           show help (default: false)

@gaocegege
#3 docker-image://docker.io/tensorchord/envd-sshd-from-scratch:v0.2.5-rc.2
#3 resolve docker.io/tensorchord/envd-sshd-from-scratch:v0.2.5-rc.2 0.2s done
#3 ERROR: docker.io/tensorchord/envd-sshd-from-scratch:v0.2.5-rc.2: not found

It seems the failure caused by unstable CI env?

The test failures are not from the PR, I am merging it.
Thanks for your contribution! :tada: :+1:

@all-contributors Please add @tisonkun for the code contribution.


feat: move KeepKey's pin changing behavior to the wallet menu

Description

Moved the Pin logic and markup to a reusable component and added some props needed to customize it for the menu
Fixed a bug crashing the app inside error handling of the new pin action
Added a new wallet state isUpdatingPin in order to prevent the regular modal to open when the reset pin action is launched from the menu
Added a new wallet state isLoading so we can force a loading state when the device is loading for example
I used polling to handle the passphrase sent event response, because the KeepKey is silent on success, see code comments for more information!

⚠ There is a keepkey bug when cancelling / going back to previous route, the cancel method from hdwallet makes the keepkey crazy, I guess this is a firmware issue and will be fixed with https://github.com/shapeshift/web/issues/1613

Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #1414
Risk

The reset pin feature could be broken or buggy
The enter pin feature could be broken or buggy in case I did an error while moving to a reusable component

Testing

Connect your keepkey
Open the wallet menu on the top-right and try to reset the pin of the keepkey
Complete the whole pin reset process, everything should work as expected until the end
Try to also cancel, go back to the previous menu screen
You'll have more information in the issue, mockups and as a video in the screenshots part

Engineering

Connect your keepkey
Open the wallet menu on the top-right and try to reset the pin of the keepkey
Complete the whole pin reset process, everything should work as expected until the end
Try to also cancel, go back to the previous menu screen
You'll have more information in the issue, mockups and as a video in the screenshots part

Operations

Connect your keepkey
Open the wallet menu on the top-right and try to reset the pin of the keepkey
Complete the whole pin reset process, everything should work as expected until the end
Try to also cancel, go back to the previous menu screen
You'll have more information in the issue, mockups and as a video in the screenshots part

Screenshots (if applicable)
https://www.awesomescreenshot.com/video/11006360?key=80a2f395eaa20c19c602b2d95329e46f

@0xApotheosis
As we discussed, I addressed all your feedback and finally used polling to handle the keepkey passphrase response event.
Unfortunately, I can't fix the cancel problem, it already exists in the current reset pin implementation and is probably a firmware thing that you already added to another issue (see the description of the PR).
Thanks for the great feedbacks and tests 👍


Find unused Sass variables

@XhmikosR and @Johann-S made a plugin which detects variables that aren't used: https://github.com/XhmikosR/find-unused-sass-variables
It would be nice if we can make a stylelint plugin of this. I tried to make something myself but I don't really have an idea how I should approach this and I'm afraid I'm just not experienced enough in these things to make something valuable.
I think this could be something we could definitely use in Bootstrap.

I like the idea and I think that you have a good start for a great tool.
The idea reminds me of this eslint plugin:
https://github.com/atfzl/eslint-plugin-css-modules#readme

I'd definitely love to see this as a rule here and drop that plugin for sure. :)

I have nothing against adding the rule to this plugin as long as the implementation can be done in a way that the perf stays good :)
Reading the files from a disk and parsing the SCSS can be fast when you have 100 files in your project, but what happens if you have thousands or tens of thousand of files?
I think it makes sense to make a proof of concept and see if the rule can be implemented so that it prints correct line numbers in correct files for the unused vars.

There was some additional discussion in #328 about this.
There are two major issues with creating a rule like this:

Very difficult to achieve good performance.
The difficulty/impossibility of correctly resolving variables:

In addition to performance, there's the issue of accurately resolving imports. Many applications pass load paths or custom importers to Sass which the linter won't have access to, without which accurately resolving imports to see which variables are defined in a given scope becomes essentially impossible.

That's why it instead of having a rule it makes more sense to have a script that finds unused variables:
https://github.com/XhmikosR/find-unused-sass-variables