XSD file append prefer-serialization

XSD file append prefer-serialization fix

Codecov Report

Merging #10998 (007838d) into 3.1 (e7f0ee3) will decrease coverage by 4.63%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.1   #10998      +/-   ##
============================================
- Coverage     69.28%   64.65%   -4.64%
+ Complexity      106       14      -92
============================================
  Files          1463     1418      -45
  Lines         75990    58857   -17133
  Branches      13292     8637    -4655
============================================
- Hits          52651    38053   -14598
+ Misses        18713    16783    -1930
+ Partials       4626     4021     -605

Impacted Files
Coverage Δ

...luster/router/script/ScriptStateRouterFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...he/dubbo/test/common/impl/GreetingServiceImpl.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...zookeeper/curator/CuratorZookeeperTransporter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...nfigure/DubboRelaxedBinding2AutoConfiguration.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../apache/dubbo/test/spring/SpringXmlConfigTest.java
0.00% <0.00%> (-96.16%)
:arrow_down:

...egistrycenter/context/ZookeeperWindowsContext.java
0.00% <0.00%> (-81.82%)
:arrow_down:

...istrycenter/processor/FindPidWindowsProcessor.java
5.40% <0.00%> (-81.09%)
:arrow_down:

...pc/cluster/router/file/FileStateRouterFactory.java
0.00% <0.00%> (-80.96%)
:arrow_down:

...ycenter/processor/KillProcessWindowsProcessor.java
10.00% <0.00%> (-80.00%)
:arrow_down:

...nter/processor/StartZookeeperWindowsProcessor.java
17.39% <0.00%> (-78.27%)
:arrow_down:

... and 420 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks. I will look into this PR


Using with ReadFrom.Configuration() advice seems to conflict with the advice above

In your readme you say we should be able to configure Serilog.Sinks.ApplicationInsights using ReadFrom.Configuration like so:
    ...
    "WriteTo": [
      {
        "Name": "ApplicationInsights",
        "Args": {
          "instrumentationKey": "YOUR-KEY",
          "telemetryConverter": "Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"
        }
      }
    ],
    ...

However above this you say:

You can also pass an instrumentation key and this sink will create a new TelemetryConfiguration based on it, however it's actively discouraged compared to using already initialised telemetry configuration, as your telemetry won't be properly correlated.

So can we do something using the telemetryConfiguration through the config?
    ...
    "WriteTo": [
      {
        "Name": "ApplicationInsights",
        "Args": {
          "telemetryConfiguration": "what would go here?",
          "telemetryConverter": "Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.TraceTelemetryConverter, Serilog.Sinks.ApplicationInsights"
        }
      }
    ],
    ...

If the PR gets approved the corresponding config would be
    "WriteTo": [
      {
        "Name": "ApplicationInsights",
        "Args": {
          "restrictedToMinimumLevel": "Information",
          "telemetryConverter": "Serilog.Sinks.ApplicationInsights.Sinks.ApplicationInsights.TelemetryConverters.EventTelemetryConverter, Serilog.Sinks.ApplicationInsights"
        }
      }
    ],

Looks good, thank you.

Niceone @DinoSourcesRex
The readme ought to be updated as well

@hisuwh I can raise a PR for that tomorrow, I am unfortunately totally stacked today. Someone else is free to beat me to it though 😄

@DinoSourcesRex
I've done it: https://github.com/serilog/serilog-sinks-applicationinsights/pull/109


upstream

(!) Bunnyshell could not create the Environment base / pull/2/head:main / PR-2 for PR #2.

(!) Bunnyshell could not create the Environment base / pull/2/head:main / PR-2 for PR #2.

(!) Bunnyshell could not create the Environment manual-test-3 / pull/2/head:main / PR-2 for PR #2.

(!) Bunnyshell could not create the Environment manual-test-4 / pull/2/head:main / PR-2 for PR #2.

(!) Bunnyshell could not create the Environment base-3 / pull/2/head:main / PR-2 for PR #2.

(!) Bunnyshell could not create the Environment Copy of base-4 / pull/2/head:main / PR-2 for PR #2.

:x: Preview Environment is deleting from Bunnyshell...
See: Environment Details | Pipeline Logs

:x: Preview Environment is deleting from Bunnyshell...
See: Environment Details | Pipeline Logs

:x: Preview Environment is deleting from Bunnyshell...
See: Environment Details | Pipeline Logs

:x: Preview Environment is deleting from Bunnyshell...
See: Environment Details | Pipeline Logs

:x: Preview Environment is deleting from Bunnyshell...
See: Environment Details | Pipeline Logs


mgmt, fix vmss outdated vm

Description
issue: https://github.com/Azure/azure-sdk-for-java/issues/32223
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

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


Azure AD Login implementation for authorizing user to see private documents

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
I am trying to implement azure ad login where user is authorized to see the documentation site. Is there a way to implement this? Any suggestions and comments can help. Thanks!
Self-service

[ ] I'd be willing to address this documentation request myself.

Duplicate of https://github.com/facebook/docusaurus/issues/6890.
Please don't use the issue tracker as a support forum. Please ask in discussions instead—and give more details about how the authentication system is expected to be interacted with. Remember, Docusaurus is just a React app, so you implement any API calls the same way as normal React app.


document.write call fails when there's a space in the value of a script tag attribute

We found an issue when writing a script tag with a filename that contains space characters.
Example:
<script src=https://secure-ds.serving-sys.com/BurstingRes//CustomScripts/OK - PL_ResponsivePushdown_CFV001.js></script>

The rendering then fails when it attempts to add the attribute '-' to the element.

WONT FIX.  As per the HTML4 RFC, that is invalid HTML anyway: https://www.w3.org/TR/html4/interact/scripts.html#h-18.2.1.  The attribute must be enclosed in quotes.

Sorry about that. I actually only noticed the lack of quotes after posting the issue. We'll report this to the advertiser.


update mariadb-java-client to 2.7.10

Hi,
the update includes the following fix:
[CONJ-1091] Ensure setting connectTimeout as timeout for socket timeout until connection is done. This permit to set a connectTimeout, while socketTimeout can still be set to 0
(from https://mariadb.com/kb/en/mariadb-connector-j-2-7-10-release-notes/)

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

Thank you for your PR, we will merge this into our pipeline in due course


[material-ui] Fix createEmotionServer in Next.js integration package

The emotion server shouldn't be created after rendering the App tree. Because cache.compat === undefined, emotion doesn't set styles on the cache and they are rendered in style tags inside <body>. So, the Next.js server sends the HTML with styles placed beside MUI components, rather than inside <head>.

[ ] I have followed (at least) the PR section of the contributing guide.

@petrovmiroslav Yes! I had just noticed the same, the plugin is currently useless, this restore its purpose 👍

Dang! I should have checked this PR before merging mine #40409


Improvements to findRenderable functions

Simplify the interfaces of findRenderableElements and findRenderableMaterialNodes, using return values instead of references to output arguments.  This enables function composability and copy elision optimizations, and improves the consistency of the API across languages.
Add deprecated wrappers for the original interfaces of these functions, allowing clients to proceed without code changes.
Mark BSDF, EDF, and VDF data types as unsupported in findRenderableElements, as these cannot yet be directly rendered across all languages.

Here are the associated render comparisons between GLSL and OSL, where unsupported data types are no longer included:
MaterialXRenderTests_03_04_2023.pdf

Based on a side conversation with @kwokcb and @niklasharrysson, I'll plan to move forward with this change, and we can continue refining the findRenderable functions in upcoming pull requests.


Function validation decorator (@validate_call) should provide JSON Schema serialization

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
When using pydantic with classes, it's possible to access the schema using model_json_schema() and similar methods as covered in the docs here: https://docs.pydantic.dev/latest/usage/json_schema/
However, when using the validation decorator @validate_call for either class methods or methods independent of any class, it does not appear possible to access the schema in the same way.
Consider the following example:
import json
from pydantic import BaseModel, validate_call

class Hello(BaseModel):
    ending: str

    def say_hello(self):
        print(f'Hello{self.ending}')

    @validate_call
    def say_hello_to(self, to: str) -> None:
        print(f'Hello {to}{self.ending}')

# Works - print schema for class
print(json.dumps(Hello.model_json_schema(), indent=2))

# Doesn't work - print schema for class method
_hello = Hello(ending='!')
print(json.dumps(_hello.say_hello_to.model_json_schema(), indent=2))
# > AttributeError: 'ValidateCallWrapper' object has no attribute 'model_json_schema'

@validate_call
def say_hello_to(self, to: str) -> None:
    print(f'Hello {to}{self.ending}')

# Doesn't work - print schema for method (not used in class)
print(json.dumps(say_hello_to.model_json_schema(), indent=2))
# > AttributeError: 'ValidateCallWrapper' object has no attribute 'model_json_schema'

In the above example you see a few attempts to call model_json_schema on method decorator with no success. It would be very useful to support this feature, thanks for your consideration!
Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[X] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[X] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Selected Assignee: @lig

Does this work for you?
import json

from pydantic import TypeAdapter

def say_hello_to(self, to: str) -> None:
    print(f'Hello {to}{self.ending}')

print(json.dumps(TypeAdapter(say_hello_to).json_schema(), indent=2))
"""
{
  "additionalProperties": false,
  "properties": {
    "self": {
      "title": "Self"
    },
    "to": {
      "title": "To",
      "type": "string"
    }
  },
  "required": [
    "self",
    "to"
  ],
  "type": "object"
}
"""

I think this should work with methods, and with or without the validate_call decorator as well.
If you want a different JSON schema than what is currently generated, you can probably achieve it by creating a custom subclass of pydantic.json_schema.GenerateJsonSchema and passing it to the schema_generator argument to TypeAdapter.json_schema.

It would be really nice if one could find the validators as attributes of the function returned from validate_call. I'm using the code from this comment, but also using validate_call, and it seems like it's doing things more than once.

+1 from me

+1


checkAutoCommitIsDisabled fails for kafka-clients v3.7.0

When using PC with kafka-clients v3.7.0, PC fails while trying to determine whether the provided Consumer has auto-commit enabled:
Caused by: java.lang.IllegalStateException: Cannot check auto commit is disabled for consumer type: org.apache.kafka.clients.consumer.KafkaConsumer
	at io.confluent.parallelconsumer.internal.AbstractParallelEoSStreamProcessor.checkAutoCommitIsDisabled(AbstractParallelEoSStreamProcessor.java:493)
	at io.confluent.parallelconsumer.internal.AbstractParallelEoSStreamProcessor.validateConfiguration(AbstractParallelEoSStreamProcessor.java:330)
	at io.confluent.parallelconsumer.internal.AbstractParallelEoSStreamProcessor.<init>(AbstractParallelEoSStreamProcessor.java:283)
	at io.confluent.parallelconsumer.internal.AbstractParallelEoSStreamProcessor.<init>(AbstractParallelEoSStreamProcessor.java:266)
	at io.confluent.parallelconsumer.ParallelEoSStreamProcessor.<init>(ParallelEoSStreamProcessor.java:46)
	at io.confluent.parallelconsumer.ParallelStreamProcessor.createEosStreamProcessor(ParallelStreamProcessor.java:26)
...
Caused by: java.lang.NoSuchFieldException: coordinator
	at java.base/java.lang.Class.getDeclaredField(Class.java:2610)
	at io.confluent.parallelconsumer.internal.AbstractParallelEoSStreamProcessor.checkAutoCommitIsDisabled(AbstractParallelEoSStreamProcessor.java:473)

Upon surface-level investigation, the failure is caused by https://issues.apache.org/jira/browse/KAFKA-15277. KafkaConsumer no longer holds a coordinator field.
Instead, KafkaConsumer now has a ConsumerDelegate<K, V> delegate field, which resolves to either LegacyKafkaConsumer, or AsyncKafkaConsumer.
LegacyKafkaConsumer still has a coordinator field, but AsyncKafkaConsumer does not.

I will need to work on making the reflection checks to account for this, but i am thinking that it may be worth to add an override option to disable this check in edge cases like when custom delegate / wrapper for Consumer is used or when things break due to dependency changes until Parallel Consumer code catches up etc.

Closing as fixed.
Please re-open if still an issue after the #762.
Thanks @nscuro and @ondryaso!


Add config option to ignore bad SSL certs when archiving

In the modern age of HTTPS everywhere, it's becoming increasingly common for sites to set up SSL badly or forget to renew their certificates (especially older 90's era sites), rendering the sites inaccessible.
When browsing I always want to be alerted of bad certs, but when archiving 90% I want it to attempt archiving cites with bad certs anyway in case the content is important.  After all, archiving a certificate error page is useless 100% of the time, so instead of throwing out hands up and skipping the site it's nice to at least attempt getting a snapshot.
TODO:

[X] Add option to skip checking SSL certificates for validity
[X] Implement fetch_wget cli option to skip cert check
[ ] Implement fetch_pdf cli option to skip cert check
[ ] Implement fetch_screenshot cli option to skip cert check

Last two steps just require doing some research on the chrome headless command line interface to find the right flags.
More Info:
- https://bugs.chromium.org/p/chromium/issues/detail?id=721739
- headless --ignore-certificate-errors
- https://groups.google.com/a/chromium.org/forum/#!topic/headless-dev/eiudRsYdc3A

I implemented this a little while ago, but thanks for your help @ShubhGupta2125


Fix resizer icon visiblity on light theme in GraphNode

Makes this visible..

Hmm. Maybe Its better to expose "resizer_color" as theme property

Thanks!


[IOTDB-2354] row number is not as expected when using nested expressions containing count() function in 'group by time' clause

Description
see IOTDB-2354 row number is not as expected when using nested expressions containing count() function in 'group by time' clause

Coverage decreased (-0.004%) to 67.662% when pulling 9fe78f8633be931a671986cb14a834081eff93d6 on Plutooooooo:IOTDB-2354 into e8810dd712ea0fdde76a43174554ffbf9fa68a78 on apache:master.

LGTM, but the CI of some basic unit tests are failed due to other reasons.


security check for bop

bop usage on tanks on/off for obvious reasons

You're trying to avoid using BoP on tanks correct?

its aswitch if bop should be used on tanks or not as it causes instant aggro loss

You want a switch, if enabled it will use it on tanks as well?


e2e tests are failing randomly on dependencies installation part

Each e2e test is installing dependencies on its own. Which from time to time results in failure. The Windows runner with node 18 is affected the most. Wasn't able to investigate the root problem.
Currently, we are installing dependencies with npm packager. I have tried with yarn it gets a better ratio but the problem is still there. pnpm gets even better results, my guess is it's somehow related to network connectivity failures.
E2E tests also take too much to execute, the major part of its installation of dependencies.
Unless we identify the root issue I'm recommending introducing the following changes

short-term: replace  with yarn packager -> shorter installation time, decreases rates of failure.

it's low complexity, it requires just replacing npm run install with yarn install

medium-term: replace with pnpm packager -> it reduces installation even more than yarn, and also decreases rates of failure.

it requires a little bit of refactoring of tests, to fix output for prisma and nexus-prisma and to fix post-install script for<EMAIL_ADDRESS>version.

By adding more logs in #578 I have narrowed the issue to the installation of dependencies, added logic to kill installation if it crosses the expected period, and added retry logic (max up to 3 retries)


feat(context): create strict context factory

This PR does two things:

Create the poutine to generate "strict context" (context where some context keys are reserved).
Showcase how one could generate a strict context

The whole ensemble is overcomplicated by design, the idea is to absorb the complexity in the factory and limit to the minimum the amount of code duplications and complexity for the strict context declarations.

lgtm. Will the example file be deleted before merging ?

I'll leave it until some better 'in the flesh and actually used' examples is created.


How to profile APL document download and render performance?

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

Base on issue #62
Sure, the best way to profile the rendering time is by profiling the time between TemplateRuntime::handleRenderPlayerInfoDirective and GUIClient::executeHandleRenderComplete. Alternatively, you can use MetricsRecorder.
Please open the ticket if you have any further questions.  Thanks!
Originally posted by @VaruPan in https://github.com/alexa/alexa-smart-screen-sdk/issues/62#issuecomment-744901341
We want to know about how to profile several things
1.How to profile APL document download time from user say uttrance?
2.Browser rendering performance
3.How to use MetricsRecorder to record it?
What is the expected behavior?

Browser rending UI fast as soon as possible
What behavior are you observing?

Browser rending UI to slow in first time.
APL document for browser rendering time too long
Log:https://github.com/alexa/alexa-smart-screen-sdk/files/5663979/sssdk240_playmusic_after.zip
Does the render time is about 17.728s on RPi4.
It doesn't make sense why it take too long time
2020-12-09 05:45:10.511 [ c] 5 TemplateRuntime:handleRenderPlayerInfoDirective
2020-12-09 05:45:28.239 [ 2] 3 GUILogBridge:GUILog:component=WSClient:message sent, type: renderComplete
Provide the steps to reproduce the issue, if applicable:

Run smart screen sdk v2.4 on RPi4.
Say ‘Alexa, play music’. Play music the first time.
Say ‘Alexa, stop’.
Wait 5 minutes.
Say ‘Alexa, play music’. Play music the second time.
Record the time interval between audio and playcard.
Tell us about your environment:

What version of the AVS Device SDK are you using?
AVS Device SDK: <1.21.0>
APL core library: <1.4.1>
Alexa smart screen SDK: <2.4.0>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[*] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[*] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Have you tried the same use case with AVS Device SDK SampleApp?

[ ] The issue is not applicable to the AVS Device SDK SampleApp.
[*] The issue is not reproducible on the AVS Device SDK SampleApp.

Could we measure from Thinking to TemplateRuntime:handleRenderPlayerInfoDirective about 1.38s for APL download time ?
2020-12-09 05:45:09.131 [ 17] 5 TemplateRuntime:onDialogUXStateChanged:state=THINKING
2020-12-09 05:45:10.511 [ c] 5 TemplateRuntime:handleRenderPlayerInfoDirective
2020-12-09 05:45:28.239 [ 2] 3 GUILogBridge:GUILog:component=WSClient:message sent, type: renderComplete

Could we measure from Thinking to TemplateRuntime:handleRenderPlayerInfoDirective about 1.38s for APL download time ?
2020-12-09 05:45:09.131 [ 17] 5 TemplateRuntime:onDialogUXStateChanged:state=THINKING
2020-12-09 05:45:10.511 [ c] 5 TemplateRuntime:handleRenderPlayerInfoDirective
2020-12-09 05:45:28.239 [ 2] 3 GUILogBridge:GUILog:component=WSClient:message sent, type: renderComplete

Hi @yuan0258 ,
It is possible to enable metrics for tracking APL performance within the Smart Screen SDK, however by default this functionality is not enabled. If you are primarily interested in APL metrics then it should be possible to add this by making a few small modifications (note that this metrics sink is provided as a sample for testing purposes only):

Rebuild and reinstall the AVS Device SDK with the -DMETRICS=ON flag
Modify the Smart Screen SDK code to use the Sample metrics sink
Add the following includes to SmartScreenClient.cpp

#include <Metrics/MetricRecorder.h>
#include <Metrics/SampleMetricSink.h>

Replace the null metrics recorder found at https://github.com/alexa/alexa-smart-screen-sdk/blob/master/modules/Alexa/ApplicationUtilities/SmartScreenClient/src/SmartScreenClient.cpp#L478 with the Sample implementation
    std::string metricsFilePath{"/tmp/metrics.dmp"};
    std::unique_ptr<alexaClientSDK::metrics::implementations::SampleMetricSink> fileSink{
        new alexaClientSDK::metrics::implementations::SampleMetricSink(metricsFilePath)};
    auto metricRecorder = alexaClientSDK::metrics::implementations::MetricRecorder::createMetricRecorderInterface(std::move(fileSink));

Rebuild the Smart Screen SDK adding the metrics and APL metrics flags -DMETRICS=ON -DUSE_APL_TELEMETRY=ON
When running the SampleApp, metrics can be found in the path provided above i.e. /tmp/metrics.dmp

Hi @yuan0258 ,
It is possible to enable metrics for tracking APL performance within the Smart Screen SDK, however by default this functionality is not enabled. If you are primarily interested in APL metrics then it should be possible to add this by making a few small modifications (note that this metrics sink is provided as a sample for testing purposes only):

Rebuild and reinstall the AVS Device SDK with the -DMETRICS=ON flag
Modify the Smart Screen SDK code to use the Sample metrics sink
Add the following includes to SmartScreenClient.cpp

#include <Metrics/MetricRecorder.h>
#include <Metrics/SampleMetricSink.h>

Replace the null metrics recorder found at https://github.com/alexa/alexa-smart-screen-sdk/blob/master/modules/Alexa/ApplicationUtilities/SmartScreenClient/src/SmartScreenClient.cpp#L478 with the Sample implementation
    std::string metricsFilePath{"/tmp/metrics.dmp"};
    std::unique_ptr<alexaClientSDK::metrics::implementations::SampleMetricSink> fileSink{
        new alexaClientSDK::metrics::implementations::SampleMetricSink(metricsFilePath)};
    auto metricRecorder = alexaClientSDK::metrics::implementations::MetricRecorder::createMetricRecorderInterface(std::move(fileSink));

Rebuild the Smart Screen SDK adding the metrics and APL metrics flags -DMETRICS=ON -DUSE_APL_TELEMETRY=ON
When running the SampleApp, metrics can be found in the path provided above i.e. /tmp/metrics.dmp

Closing the ticket due to inactivity, please feel free to open the ticket again. Once again, thanks a lot for contributing to Alexa Smart Screen SDK!

Closing the ticket due to inactivity, please feel free to open the ticket again. Once again, thanks a lot for contributing to Alexa Smart Screen SDK!

@powj,
I following your step to enable -DMETRICS=ON -DUSE_APL_TELEMETRY=ON in Smart Screen SDK.
It seems it could create /tmp/metric.dmp
But there is no timpstamp information in /tmp/metric file.

@powj,
I following your step to enable -DMETRICS=ON -DUSE_APL_TELEMETRY=ON in Smart Screen SDK.
It seems it could create /tmp/metric.dmp
But there is no timpstamp information in /tmp/metric file.


Include node location in node data record

This is a feature request for the Backend.
Explain what you want to do
We  would like to be able to setup an application, where many people can deploy sensors/nodes, whose data show up in the the same application. Our example would be a fine dust or noise sensor, and we want to be able to offer one endpoint where interested parites can get access to the sensor data.
for that reason we would like to be able to set a node location (via API/console - this already works) ...and similar to the gateway location the node location should also show up in the data/mqtt forwarded messages etc.
--> This avoids that people later on need to do lookup with the sensor data in the console, additionally the location of the node might have changed in the meantime.

This functionality is already implemented and works fine when I test it:
ttnctl devices register test
ttnctl devices set test --latitude 12.34 --longitude 34.56
ttnctl uplink <test-devaddr> <test-nwkskey> <test-appskey> <test-fcnt> <test-data>

On MQTT:
Client mosqsub/24393-Hylkes-Ma received PUBLISH (d0, q0, r0, m0, 'test/devices/test/up', ... (371 bytes))
{"app_id":"test","dev_id":"test","hardware_serial":"008BB99E229AB312","port":1,"counter":1,"payload_raw":"q80=","metadata":{"time":"2017-03-06T09:58:08.438167862Z","frequency":868.1,"modulation":"LORA","data_rate":"SF7BW125","coding_rate":"4/5","gateways":[{"gtw_id":"dev","gtw_trusted":true,"time":"","channel":0,"rssi":-25,"snr":5}],"latitude":12.34,"longitude":34.56}}

Similarly, on the console:


java handsOn 3 submited

Metric
Value

alert_status
b:white_check_mark: OK/b

bugs
0

code_smells
32

reliability_rating
A (0 Bugs)br/Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)br/Note: A being best, E being worst

vulnerabilities
0


ensure .pyc files are always written into the .pex

Right now .pyc files are not always written for every .py (e.g. some __init__.py and files within .egg and .whl directories.)  In order to speed up the invocation of directory PEXes owned by superuser (and hence where .pyc cannot be locally cached) we should always make sure that we're building these.  An example: the aurora client as directory PEX speeds up from 1.4s to 600ms when all .pyc's are present.

We used to build .pyc using the CodeMarshaller in twitter.common.python but stopped once multi-interpreter support was added, as we could no longer rely upon the current interpreter to produce correct .pyc.

The solution will involve bolting a compile() method onto PythonInterpreter that forks out a stub compile script.  We'd also need to consider doing this for multiple interpreters in case we want to support multi-interpreter pex files.  I believe starting in py3 they will build pep-425 tagged pyc, e.g. '.py33.pyc' so we could potentially compile multiply tagged pycs.

– @wickman on our internal issue-tracker

I have the compiling happening under the correct interpreter in https://rbcommons.com/s/twitter/r/2350/.  As noted on that review, this is only done for the 1 interpreter used for building the pex; however, the pex still runs properly under different interpreters.  So no support for multi-interpreter explicitly, but simple pexes with code and wheel that run under 2/3, run correctly.


java.lang.IllegalStateException: ButlerService is not started!

Hello, I have setup TestButler as specified except that the test that I am running was created with Espresso Recorder and I extended the class it created with AndroidJUnitRunner. I installed the TestButler .apk through the terminal with adb install. However when I attempt to use a test butler method within the espresso test I get the error mentioned above. Any help would be greatly appreciated. Thank you.

Are you running the tests on an emulator? And does the apk version match the version of the library?

Yes for both questions. Thank you for the reply.

No worries. Try unplugging all Android devices, close all emulators so there's only one emulator,  uninstall the test butler apk, do clean build, then drag apk file onto emulator and run the tests again.

FWIW, I'm having the same issue...fresh install 1.2.0 for plugin and APK.  The test butler APK doesn't show up as an app icon to run so it can't be found via the launcher...would be nice if there were a simple UI to show that it's installed and what the status of it is.

I like the idea of a simple UI to show its status. Would help for validating if app is installed and if OK.

Tried it on an AVD emulator w/ Google APIs and API 25 and have the same error msg.  It's like it can't talk to the installed APK which I presume has the magic service that lets it turn off/on the settings switches for wifi, rotation, etc.

Also tried version 1.1.0 with the same error.  My test right now is fairly trivial and the latest support libs are being used (25.1.0) for the latest support annotations:
package test.com.offlineokhttptest;

import android.os.Bundle;
import android.support.test.InstrumentationRegistry;
import android.support.test.runner.AndroidJUnit4;
import android.support.test.runner.AndroidJUnitRunner;

import com.linkedin.android.testbutler.TestButler;

import org.junit.Test;
import org.junit.runner.RunWith;

import java.io.IOException;

import okhttp3.OkHttpClient;
import okhttp3.Request;
import okhttp3.Response;

import static org.junit.Assert.assertEquals;

/**
 * Tests ability for okhttp to survive offlining
 */
@RunWith(AndroidJUnit4.class)
public class OkHttpCrapNetworkTest extends AndroidJUnitRunner {
    @Override
    public void onStart() {
        TestButler.setup(InstrumentationRegistry.getTargetContext());
        super.onStart();
    }

    @Override
    public void finish(int resultCode, Bundle results) {
        TestButler.teardown(InstrumentationRegistry.getTargetContext());
        super.finish(resultCode, results);
    }

    @Test
    public void verifyOkHttpCanReadSite() throws IOException {
        OkHttpClient client = new OkHttpClient();

        Request request = new Request.Builder()
                .url("https://www.google.com")
                .build();

        Response response = client.newCall(request).execute();
        assertEquals(response.code(), 200);
    }

    @Test
    public void verifyOkHttpCannotReadSiteWithNetworkDown() throws IOException {
        TestButler.setGsmState(false);
        TestButler.setWifiState(false);

        OkHttpClient client = new OkHttpClient();

        Request request = new Request.Builder()
                .url("https://www.google.com")
                .build();

        Response response = client.newCall(request).execute();
        assertEquals(response.code(), 200);
    }
}

The last test will obviously fail but before it gets to the assert, it fails in TestButler.setGsmState with:
java.lang.IllegalStateException: ButlerService is not started!
at com.linkedin.android.testbutler.TestButler.verifyApiReady(TestButler.java:278)
at com.linkedin.android.testbutler.TestButler.setGsmState(TestButler.java:181)

What's weird is the Test Butler helper app isn't running, though if it's just a service, it'll shut down as soon as nothing is connected to it or it's not handling anything...

Have you set the testInstrumentationRunner property in your build.gradle file? It looks like this step is not included in the README, but you can see an example in the demo project. You can verify by adding some log statements to your onStart method to check if it's being called.
Also btw, you shouldn't need @RunWith if you're using a custom test harness that extends AndroidJUnitRunner

Haven't heard anything back on this one, so I'm going to assume you figured it out. Feel free to re-open with more info if that's not the case.


fix: upgrade expo/config-plugins to 8.0.0

Upgrade @expo/config-plugins from from ^4.1.5 to ~8.0.0 in order to meet Expo SDK 51 needs.

42s are everywhere! Thank you so much for your PR :)

42s are everywhere! Thank you so much for your PR :)

Indeed ! Hahaha no thanks needed for that little baby PR, trying my best to help :) Thank you for the reactivity !


Docker Image with Node v14.15.5

Continuing from my comment https://github.com/cypress-io/cypress-docker-images/issues/449#issuecomment-798904136
It'd be great to have cypress/included official image based on latest Node LTS (v14) image. Any timeframe on that?
Previously I had my custom Node v14.15 image, with Cypress in it (I actually copy-pasted official Dockerfiles into that, nothing there was new or different from what we have in this repo). I have this script in my package.json file:

and it was working quite OK. But 2 days ago I decided to switch to official Cypress image, and I picked:

and since then, that ---inspect=... parameter stopped working. I keep getting EPIPE errors:

I didn't change anything in my code, so my suspicion is it is Node v12 related. As you might've guessed, my app is a NextJs one.
And for some remote reason if this isn't Node v12 related, then the only thing I'd suspect is my container having browsers now, and somehow those browsers are capturing port 9229. I really really don't think this is the case, coz browsers don't run any services or listen to any ports just by themselves.
And yes: when --inspect=... is removed, everything works. And yes, IP address listed there is correct.

I could also use an image using v14, I'm starting to have some dependencies that are available only on a few v12 versions while allowing all v14 versions.

Node 14 images have been released, or you can specify which versions you want by using the cypress/factory docker image
https://github.com/cypress-io/cypress-docker-images/tree/master/factory


Added UserClaimsPrincipal to ViewComponent

Addresses #4964
@Eilon

@Eilon @pranavkm Updated

:shipit: Just make sure there's exactly one commit going in for this change (The commit history looks suspect).


Documentation: Added code style for class; Changed docs preview to run local server

Can be merged to #172 before merging into master


Third Party ad server support

I am requesting a Third party ad .
i Get the following error: Unable to request the ads from the server due to the network error.
My VAST ad tag -"http://az739004.vo.msecnd.net/vast/vast_twitter.xml"

Hey there,
For general support (i.e. any issue not specific to these samples) please check out our support forum.
Thanks!
Shawn Busolits
IMA SDK Team


Change Payment option

Change payment option when invoice is generated is not working.

This option was working before this beta release.


chore: adjustments to runLinter so it can be used downstream

Is there anything we can do to make the default module be the current package instead of Std always? Otherwise I think this will have to be called as lake exe runLinter Mathlib from mathlib.

Is there anything we can do to make the default module be the current package instead of Std always? Otherwise I think this will have to be called as lake exe runLinter Mathlib from mathlib.

@tydeu, any suggestions?
https://github.com/leanprover-community/mathlib4/pull/8461 is already using lake exe runLinter Mathlib.

I gave this a bit of a think and I think there is nothing that can be done with the current design of lake, unless the linter is turned into a script (which both changes the interface, and also makes it run interpreted). Options considered:

Influence elaboration somehow so that the name of the current project is embedded in the executable.

We can't do this right now because we have no way to influence elaboration other than through builtin options. It would be nice to have a way to declare defs that are reachable from elaboration, similar to autogenerated files like version.h in lean4 repo.

Call lake to get the name of the default_target(s) and the roots for it.

Can't do it because we didn't get lake dump-config.

Have lake pass us this information in env vars.

Lake doesn't tell us much other than the LEAN_SRC_PATH and other things tailored for lean use. It doesn't even say what the current project folder is.

Add extra hard-coded CLI args to the lake_exe in the lakefile.

This seems relatively simple to implement, but lake doesn't do it currently. I'll try to make a PR for this.

Given this, I'll just merge it as-is and we can pursue alternatives in a future PR.

While I think many of @digama0's feature suggestions are generally reasonable (so feel free to create issues for them!), lake exe runLinter Mathlib looks quite good to me. One way to achieve a shorter command in the current setup would be a have a lint script that just builds and runs the linter on Mathlib (i.e., in a similar manner to the exe CLI command).


Make Configure Series a form menu

https://www.fuckdropdowns.com/

In case I'm using the wrong UIminology, all I mean something that allows configuration of more than one attribute at a time without disappearing. Going through a hierarchical dropdown 10 separate times to configure a single track is a lot of work.

And yeah, the video is actually pretty lame...

Possible duplicate of https://github.com/higlass/higlass/issues/233?

Definite duplicate of #233 :)


Vickel: Watch zno.osvita.ua

Vickel requests the watch of the watch_keyword zno\.osvita\.ua. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

zno\.osvita\.ua has been seen in 1 true positive, 1 false positive, and 0 NAAs.

Rejected by VLAZ in Charcoal HQ. Reason: 'Seems the website is legitimate. I found no reason for it to be watched. It has three hits on the SE network from 5 and 2 years ago'


dose .where("field = ?", value) consider sql injection?

will auto Escaping the value?

For postgres one of the way to avoid sql injection is to use toParam method, that returns text and values for parametrized queries.
See "Parametrized Queries" block:
https://github.com/brianc/node-postgres/wiki/Prepared-Statements

Yeah, toParam() is the method to use.
On 3 December 2015 at 17:39:32, FigoZhu<EMAIL_ADDRESS>wrote:
will auto Escaping the value?
—
Reply to this email directly or view it on GitHub.


checkstyle and semver maven plugin upgrade

@chandnisingh please review

we need japicmp update because it has some features exclusion/inclusion based on annotation. Apex may need that feature for new APIs and Malhar needs it now because in its next version it will inherit this plugin from Apex instead of re-declaration.
Checkstyle is needed as well because seems like there is a bug fix and which is why the number of violation is decremented.
@vrozov could you please rebase so that I can merge

Can this be captured in a JIRA so that it is clear? Neither was any of this mentioned in the PR.


Help treesitter parser has changed

I am getting the following error if I invoke :Telescope heading in a vim help file:

No treesitter language parser installed for [help]. Fallback to normal parser.

My guess is this is related to the change of the treesitter parser for help files to "vimdoc" https://github.com/neovim/tree-sitter-vimdoc/commit/b2ec4ec5f7be24cb6f7ccffafd7204477fe5784a

I am getting the following error if I invoke :Telescope heading in a vim help file:

No treesitter language parser installed for [help]. Fallback to normal parser.

My guess is this is related to the change of the treesitter parser for help files to "vimdoc" neovim/tree-sitter-vimdoc@b2ec4ec

Would you mind confirming it's TSInstalled?

Confirmed, I have the vimdoc parser installed. If you look in the output from TSInstallInfo there is no entry for help anymore.

It's like changing name to vimdoc would work. Would you mind testing it?

Happy to, point me to a commit for testing

@fbearoff Hello, I think I have figured it out.
You may try this PR: https://github.com/crispgm/telescope-heading.nvim/pull/24


Deployment: Align to upstream.

Tests on workload clusters (not always required)
For changes in the chart, chart templates, and ingress controller container images, I executed the following tests
to verify them working in live enviromnents:

Test / Provider
AWS
Azure
KVM

Upgrade from previous version

Existing Ingress resources are reconciled correctly

Fresh install

Fresh Ingress resources are reconciled correctly

Testing was done using hello-world-app.
Hint for KVM:
kubectl port-forward -n kube-system svc/nginx-ingress-controller-app 8080:80
ingress_domain=host.configured.in.ingress; curl --connect-to "$ingress_domain:80:<IP_ADDRESS>:8080" "http://$ingress_domain" -v

Yeah, I know. It's hard to keep track of them. You can try to go through commits one by one. TIL there is a "< Prev" and a "Next >" button in the commit detail view, this makes it a lot easier. :D

Could you at least try to have a look at the commits and maybe just leave a note on where you think upgrade could be critical or users might need more information in the change log? That would be awesome! 😌


[3.0 feature request] provide a class to group icons with buttons

There are a few classes to group text/buttons with inputs, but none to group something with buttons.
Please include an easy to use way, similar to input classes, which would allow building buttons like this:
https://developers.google.com/accounts/images/sign-in-with-google.png
http://www.blugraphic.com/wp-content/uploads/2012/06/Sign-in-With-Facebook-Twitter-Buttons1.jpg
by just having the icon, either as an image or as an icon font
Thanks

Is it possible we create this buttons as a sort of ready made buttons in bootstrap v4, as third party logins is now so much common and needful, it can just be a helper classed based off bootstrap button groups base classes.


feat: serde rename support

Hi!
I found that I cannot use #[serde(rename_all = "snake_case")] when using enumscribe. Is that something support can be added for?
#[derive(EnumSerialize, EnumDeserialize, PartialEq, Copy, Debug, Display)]
#[enumscribe(case_insensitive)]
#[serde(rename_all = "snake_case")]
pub enum MyEnum {
    AandB,
    C,
    D,
}

BR

I think a combination of snake_case and case_insensitive does not make really sense because it is mutual exclusive.

Although I don't intend to try to reimplement every possible serde derive attribute, adding support for rename_all seems like a good idea to me.
I do not think renaming a field is mutually-exclusive to matching it case-insensitively; for example, in the example you provided, using both case_insensitive and snake_case could allow both "A_AND_B" and "a_and_b" to deserialize to the first variant.

rename and rename_all are now implemented in the main branch (a3137d86c2c3af2af584228b036a6c1f6782c77f), I will publish a new release for this soon.

Version 0.4.0 has been published.


docker compose on M1 Mac

When running the line:
docker compose --env-file .env up --build -d
I am getting the error:
no matching manifest for linux/arm64/v8 in the manifest list entries
I believe this problem is because the code is written to be run on an Ubuntu system, which defaults to a different image type, than on my Mac.
https://forums.docker.com/t/run-x86-intel-and-arm-based-images-on-apple-silicon-m1-macs/117123
When I try to add a line to the docker-compose.yaml file to specific a different platform, I get an error. Any ideas how to fix this?

Hello @tomribaroff,
Your intuition makes sense. I never got the following error as I developed the course on an Ubuntu system, but I know people who went through the course on M chips and did not have this issue.
So, I don't think that is the issue.
But after searching no matching manifest for linux/arm64/v8 in the manifest list entries on google I found this link: https://stackoverflow.com/questions/65456814/docker-apple-silicon-m1-preview-mysql-no-matching-manifest-for-linux-arm64-v8
Let me know if it helps.


ds18B20 negative temperature issue

Hi,
When using   "family_code": "40" in attribute, thats ds18B20, negative temperatures are wrong.
For example -55 C  should be 0xFC90  but it's 0xFB70.
Also family_code attribute can not be set in HEX, for example  "family_code": "0x28" is not working.
Here is link to simulation : https://wokwi.com/projects/359211982602037249

Thanks for your feedback!
A couple of notes/questions:

regarding the attribute values - I do not control the manner in which the values can be provided in diagram.json so unfortunately the syntax does not support things like 0x28. I will update the document to reflect that.
Regarding the negative reading values. I am not sure how this code is interpreting the temperature, but I suspect that sign extension is causing issues in the way that you are computing this value. Can you tell me more about the manner in which this is calculated?

Hi,
this is not affecting simulation but for DS18B20 (0x28 device id)  BYTE-7 in SCRATCHPAD should be 0x10 and BYTE-5 should be 0xFF. (ds18b20.pdf,  page 8)

Hi,
this is not affecting simulation but for DS18B20 (0x28 device id) BYTE-7 in SCRATCHPAD should be 0x10 and BYTE-5 should be 0xFF. (ds18b20.pdf, page 8)

Thanks for this - I did not bother with those registers because I've never used them :)
I also found out the issue with the conversion - it was a stupid and over complicated way to store the temperature in the scratch pad that got carried over from another device - clearly not needed for the DS18B20.
I have also updated the README to state that the family code should be provided as an integer value
I will upload a new version soon.
You could either use this new version with a custom chip or wait for Wokwi to ratify this (I will raise a PR that will point to the new version.
Thank you very much for trying and helping me improve this chip.

@dpticar  can you please test this out by using a custom chip with version 0.4.4?

Hi,
Everything looks OK. I have not tested alarm as I'm not using it.
Also I think that ds18B20 is in 12bit resolution by default !
Probably some people does not know to set configuration bits to use 12 bit resolution, so they will think that something is not working.
So I'm suggesting to set 12bit resolution by default as it's on real ds18b20.

@dpticar
You're right about the default resolution value, I will need to change the POR value for the register.
However note that since there's no EEPROM, it all has to behave like the chip has not been programmed.
If you'd like to contribute to this project and provide a PR that would be awesome too :)


Add descriptions to request form's fields

Some of the form's fields are too complicated to understand just by the title, so we should add some description.
I think the cleanest way would be making it a hover-tooltip popping out of a help icon.
Hover actions should work as taps in touch devices.

can you assign this to me please ?

done


Add Llama 3.2 license

I forgot, but this is the correct way to add the license to moon @osanseviero @pcuenca since the final metadata is generated by a script, otherwise it gets overridden (like at https://github.com/huggingface-internal/moon-landing/pull/11251/files)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Speech to Text profanity_filter "Raw" mode not available?

I'm running the sample code in Python for transcribing one blob. Both "Masked" and "Removed" options are working, but "Raw" is considered a bad request.
If this is by design, can we have the documentation reflect that?

The value to request no masking of profanity is None.
From the docs here:

Accepted values are None to disable profanity filtering, Masked to replace profanity with asterisks, Removed to remove all profanity from the result, or Tags to add profanity tags. The default value is Masked.

Closed as answered, please open a new issue if more support is needed.


undefined: http2.TrailerPrefix

I am getting this error for the latestvendor/google.golang.org/grpc/transport/handler_server.go:202: undefined: http2.TrailerPrefix
this is from the latest head of master.
I did a clean glide get golang.org/x/net/http2 and still get this error.

No, somehow you have an old version still. Not sure what you did, though.


Terminal resizing fills terminal with previously cleared content

VSCode Version: 1.31.1
OS Version: Windows 10 Education version 1809

Steps to Reproduce:

Open a terminal.
Fill it with text (preferably long enough so it will wrap around).
Clear it with workbench.action.terminal.clear.
Resize the terminal.

Does this issue occur when all extensions are disabled?: Yes
Visual example:

I think this has something to do with text wrapping, as it happens sooner on instances where it is long enough to be wrapped. Without that I would have to resize the terminal to really small size to reproduce the issue.

Maybe a duplicate of https://github.com/Microsoft/vscode/issues/68721, also some messing up is expected currently.


Update deployment UX for time server changes

Change for vnext
Time server is now a required parameter
The time server must be specified as an IP and not an FQDN
UX will need to validate that the time server is indeed in an IP format

Completed


Generate compile_commands.json for clangd

There is a json compilation database format that c/c++ tools like clangd (lsp for c/c++, like rust-analyzer for rust) can use to understand c/c++ projects without knowing about the build system. Some build systems like cmake have first class support for it. It would be great to support an option for emitting it inside build.rs. There is a tool called bear that can proxy the calls to the compiler and emit that json but updating at each build without running a separate tool is even better.

Dupe of #497


Improve behavior on muliple register()

Currently, if you try to register() two different procedures on the same endpoint in the same session, your connection is simply dropped.
Perhaps it makes sense to let multiple methods get registered in the same session if the options= would have permitted if the sessions were different (e.g. ROUNDROBIN)? Or, we check early enough in the registration process so that we can simply error out the one register() instead of dropping the session?
At the very least, the reason for the connection being dropped should appear in the logs.

huh? you get a normal WAMP error when registering ...


Add support of typescript

Cannot parse src\components\example\example.vue: Error: SyntaxError: unknown: Unexpected token (17:0)

The line in question is the @Component from vue-component-class/vue-property-decorator.
I've setup the styleguide.config.js to point to the appropriate webpack config as well.

This would be resolved easier if you go with #11

Any word on this work?  We are an all-typescript shop and I think styleguidist would be a fantastic tool for us, but are currently blocked from trying it out.  Any help you can provide here would be appreciated!

Hi @wadetandy,
Yes, I had tried to implement https://github.com/jackmellis/require-extension-hooks-vue
But it doesn't support typescript
https://github.com/jackmellis/require-extension-hooks-vue/issues/23
So I have thought that the solution is to creates another repository like this
https://github.com/styleguidist/react-docgen-typescript
In this time I don't have too much time to create this repository, so it's probably that I will do it in the next months.
However, if you want to do it, you can tell me so I can help you.
Regards

@rafaesc So I haven't done a deep dive into this codebase yet, but it looks like all of the parsing work being done is here: https://github.com/vue-styleguidist/vue-docgen-api/blob/master/src/utils/getSandbox.js#L110-L111
Is there any reason it wouldn't work to sub in different parse function for typescript?

Hi @wadetandy,
yes, the problem it's that typescript has another syntax, so it isn't possible to use getParseBabel.
So it's necessary to develop a way to import the object with vue configuration component with typescript, maybe convert from ts to js, or create a channel to import this files, another parser like getParselBabel but for typescript.
https://github.com/vue-styleguidist/vue-docgen-api/blob/master/src/utils/getParseBabel.js

Thanks to @wadetandy,
there is a typescript support, on 2.3.0 version.
it's necessary to install the library typescript
npm install typescript --save
However also should support the library vue-property-decorator because vue-cli-plugin-typescript support that. case
For that, I created the branch ts-support, and I will work in that.
Thanks to everybody

Any update on this?


close res.Body

res.Body is closed by the caller of executeMethod we shouldn't close inside executeMethod. Look at closeResponse wrapper for this.

Ah, I see now, it's closed way up the call stack. Closing it.


Small question

Trying to integrate some laravel components into a project of mine.
Is there a way I can use Input::all() & Input::get() in that project?
Thanks

Illuminate\Http\Request::createFromGlobals()
use Illuminate\Support\Facades\Input;
add these line to your code and u can now use Input::all() , input::get('abc') and
all input methods


Add JS date program

What the program do ?
Formats JS Dates
In what programming language it is written?
Javascript

too many deletion


"Haiku" in readme has too many syllables

// Output => Robots protect us all
//           No harm to humans they bring
//           Peaceful coexistence
That’s 6-7-6. A haiku is 5-7-5. Not the best example to showcase this technology; reminds me of Google’s botched Bard announcement.

This is a good catch! Thank you for finding it!

LLMs and math :-) we'll update the docs soon, thanks for the report!


Spanner repository factory

Added spanner repository factory and tests

@balopat PTAL, these are the moved-over boilerplate files from the other PR :D

LGTM


Move line breaks after operators

Move line breaks to after operators as per PEP8 as Flake has started picking up on this in a newer version.
There were lots of flake warnings like this:
src/isodate/isoduration.py:140:11: W503 line break before binary operator

It looks like Flake has stopped being fussy again, so this could be closed.

I don't like this style, but you are right. PEP8 suggest to have the line breaks after the operator. Guess it's time to change habits.


Support one-piece registry dns names

CI failure seems to be unrelated to proposed changes.

Breaks a test case for library/busybox:
 thread 'valid_references' panicked at '
	library/busybox:
	expected: <"library/busybox">
	 but was: <"busybox">


Sunstone error on vCenter VM without ESX location

Description
When a vCenter VM is not monitorized yet, the error in the log is
06 HTTP/1.1" 200 - 0.1728
Wed May 25 07:55:42 2022 [E]: Could not determine the vCenter ESX host where
             the VM is running. Wait till the VCENTER_ESX_HOST attribute is
             retrieved once the host has been monitored

However, in the front-end the error message reads:
It appears there was a server exception. Please check server's log.
Details

Affected Component: Sunstone
Hypervisor: vCenter
Version: 6.4 and master

Progress Status

[x] Code committed
[x] Testing - QA
[x] Documentation (Release notes - resolved issues, compatibility, known issues)

@tinova PRs to be approved:

Code: https://github.com/OpenNebula/one-ee/pull/2105
Docs: https://github.com/OpenNebula/docs/pull/2295

Good morning community.
I have recently updated the version of my Vcenter to 7.0.3p
Since the update, the VMRC cannot start in OpenNebula as I get the same error
“Could not determine the vCenter ESX host where the VM is running. Wait until the VCENTER_ESX_HOST attribute is retrieved once the host has been monitored”
Can someone help me with this error?
Thank you very much in advance

please check your host is correctly monitored, and check /var/log/one for errors in monitoring


I have problem

 Unknown error while getting Access Token: 429, message='Too Many Requests', url=URL('https://api-gw-tg.memefi.club/graphql')

This issue has been preview on the Pull Requests. To resolve, Contact the official General support page to initiate a chat with our live agent using the chat button via support

use proxy


Wrong emoji category is selected if the a category is removed

Hello!
Thanks for the lib!
I experienced an issue with  the categories option when I build a new EmojiButton instance.
If I remove a category and then when I click to any category in the picker, the chosen category is not selected, even if the emojis related to the chosen category is displayed, see the screenshot below:

Here the written code to instanciate the picker:
import { EmojiButton } from "@joeattardi/emoji-button";

const picker new EmojiButton({
        categories: [
            "smileys",
            "people",
            "food",
            "activities",
            "travel",
            "objects",
            "symbols",
            "flags",
        ],
    });

As you can see, the Animals & Nature category was removed.
When I click on the Food & Drinks category, the Activities category is selected even if the Food & Drink category is displayed
Also when you click to the last category button, you get a console error.
You can reproduce and see the error here: https://emoji-button.js.org/docs/customize under the Specify categories section example
:information_source: As a workaround, I use the emojiData option with a customized JSON which does not contain the unwanted category.

This is fixed in the upcoming 5.0.0 release. Will close the issue upon release.

This issue is resolved in v5.0.0-beta.6.


There is no meta in the format when message contains '%c' token.

Please tell us about your environment:

winston version?

[ ] winston@2
[x] winston@3

_node -v outputs: v14.17.0
Operating System? (Windows)
Language? (TypeScript)

What is the problem?
We intercept messages from the console. Some messages come with a '%c' character. When we pass an object to the logger method, only the message and level fields reach the format, the rest of the fields are undefined.
What we have in the file now:
2021-06-07 00:00:00.00+03:00 | 00000 | info |  | %c next state color: #4CAF50; font-weight: bold [object Object] |
We are loosing meta here:
https://github.com/winstonjs/winston/blob/2625f60c5c85b8c4926c65e98a591f8b42e0db9a/lib/winston/logger.js#L251
What do you expect to happen instead?
We expect that the fields will be in our format and message won't be formatted.
What we expect in the file:
2021-06-07 00:00:00.000 +00:00 | 00000 | info | Renderer | %c next state color: #4CAF50; font-weight: bold [object Object] | (1) index.ts
Other information
Example of execution log method:
this.logger.log({ message, line, sourceId, scope }, undefined);
Logger has been created via:
 WinstonModule.createLogger({   transports: [this.FileTransport] })
Example of format:
Line, sourceId and scope fields are undefined when message contains '%c'.
format.printf(         ({ level, message = '', timestamp, line, sourceId, scope = '', exception = '' }) =>             `${String(timestamp)} | ${String(process.pid)} | ${String(level)} | ${String(scope)} | ${message} | ` +             `${sourceId ? `(${String(line)}) ${String(sourceId)}` : ''}\n${String(exception)}`,     );
Example of the message:
 %c action     color: #03A9F4; font-weight: bold [object Object]

Possibly related to #2029


Better support for @defaultonly and @tableonly annotations

These annotations are now "first-class citizens" in P4Info: an enum
field is used to indicate the scope of the action, i.e. how the action
can be used.
This commit also removes const_default_action_has_mutable_params, which
was introduced for P4_14 initially and has fallen out of use.
Fixes #83

@jafingerhut this is what we discussed at the API WG meeting, please take a look


simpleSignTxn() new method proposal

I suggest introducing a new method for generating signatures, which eliminates the need for a policy or information about other signers. This approach involves reading a Partially Signed Bitcoin Transaction (PSBT), utilizing the sighash type, UTXO type (determining if it's SegWit through the presence of a witness), transaction ID, value, vout, and output information. From these elements, it constructs a preimage, which is then displayed on a Ledger device. This allows the user to verify the amounts being spent and the recipients' addresses before signing and returning the signature.
Crucially, this method does not require knowledge of co-signers' extended public keys (xpubs) or any similar keys. It solely ensures that the user is aware of the transaction's details they are signing. The user's software then uses this signature to reconstruct the final transaction, adding other necessary signatures for broadcasting.
This approach enables Ledger devices to sign any redeem/witness scripts without the need to support specific types (standard multi-sig or complex... it is indifferent) or requiring users to gather information from other signers that adds complexity to the user experience. The user only needs their own keys and derivation paths, enabling the wallet to sign the preimage that is the same for any kind of redeem/witness script.
Do you think such a method is feasible and can be implemented?

Hi @pcfun19, thanks for your comment.
In terms of UX, this is underspecified: showing things that are not easy to understand/verify is equivalent to blind signing if it leads users to skip validation on the device's screen.
This also applies to showing "too much information". For the typical transaction:

all the inputs are coming from a uniform script type (your account)
the change output is going back to the same account
SIGHASH_ALL is used
These assumptions make it safe to minimize the amount of information that is shown to users, as it's no longer important to know exactly what inputs from your account you're spending - it's enough to check all the non-change outputs.

Wallet policies strengthen this greatly by allowing the user to identify from which account they are spending, with hardware guarantees (that is, malware in the software wallet can't tamper with that). The expectation is that people will have multiple accounts, and many of them will involve multiple keys (other co-signers). Wallet policies allow to know exactly from which account you're spending. That's important: if you have a 2-of-2 with your wife, and another 2-of-2 with your colleague at work, it's not enough to know that you're "spending 0.1 btc and sending it to bc1pxxx..", you want to know that you're "spending 0.1 from your work account and sending it to bc1pxxx". Without that, if your co-worker gets access to your computer, it's trivial for them to install malware to trick you to spend your wife's money when you think you're using the company account. Of course, this inherently requires full knowledge of the script on the hardware signer's end, including all of the cosigner's xpubs.
Your approach would possibly be safe in a setting where:

there is no change address (or you have some other way to identify the change address - that needs to be specified)
you're not using the same device / seed in multiple setups.

The second assumption, in particular, is not one I'm comfortable with as the default behavior of most users.
As I think wallet policies capture exactly what is needed in the vast majority of the use cases, if more advanced / different signing modes were to be added, the fact that the signing behavior is outside of the "wallet policy model" would have to be very clear in the UX, otherwise the strong security guarantees of wallet policies are lost.
Another option is to have separate apps for use cases that are beyond wallet policies.
Or it could be that wallet policies themselves could be generalized in a way that (safely) covers more use cases.
At this stage, I don't know well enough the landscape of use cases that are not covered from wallet policies; please feel free to document your use case as exactly as possible (what is the setup? What do the descriptors look like? What information is shown to the user? What additional checks does the device perform on the transaction, if any?)

I am not sure how it would temper. Without wallet policy Ledger would still hash the witness/redeem/pubkey script of each utxo (depending on type of utxo) so it would show to the user from which account he is spending without the need of a wallet policy. Not sure what I am missing here but probably you know better so I leave it on your judgement.
I believe with PSBT passing utxos and ouputs, sighash type etc all ledger should do is to hash whatever needs to be hashed to show addresses from and to, with respective amounts, generate sighash to sign if user approved that information and return signature. Not sure how one could temper what ledger shows on screen and signs even if someone got access to your computer or whatever.
If change address is all about then for outputs you would simply require developers to derivation pass path in PSBT's respective output and generate the hashed address from that path anyway. But for script wallets that wouldn't be the case anyway as there is no change address to my knowledge, so we talk only for pub key HD wallets cases and that could be the workaround.
Idk, I am probably missing something anyway.

Centralizing the discussion for this and other issues in #210.


More robust service scripts

Address issue #182 and #164 :

start detects already running service(s) and returns only
either after service(s) are up and running or a failure

stop does work also with non-default ports and config-files

fixes small bug in docker Makefile where wrong environment file was sourced
(omission from commit 7e4f29fe6883bfb43b1d4cf339ff1c8c66c35103)

found a problem...
pgrep finds processes that are not services because the command name includes the string. for example, ss-status.sh says that the processes are running because it found the process /usr/lib/accountsservice/accounts-daemon.
You can fix this pretty easily by replacing 'grep "$1"' in common.sh with 'egrep "\b$1\b"'

found a problem...
pgrep finds processes that are not services because the command name includes the string. for example, ss-status.sh says that the processes are running because it found the process /usr/lib/accountsservice/accounts-daemon.
You can fix this pretty easily by replacing 'grep "$1"' in common.sh with 'egrep "\b$1\b"'

good catch (thanks to trusty docker which has only minimal stuff running i didn't run into this problem test :-).    Anyway, pushed now a change which has a slighly more elaborate pattern to also capture basename/identity in addition to [esp]service ..


Look at new options to "semi" rule, and new rule "semi-style"

https://eslint.org/docs/rules/semi
https://eslint.org/docs/rules/semi-style

nope, that should be closed.


Request to add Brain Tumor Detection to this repository

Hey, can I add Brain Tumor Detection ML That I've been keen to work on. I'm just a beginner but I want to try. Can I?

The issue has been assigned to you , Please follow project guidelines for PR.

Please add the GSSOC2024 label and also give it a Level 3 label. Or else my contribution won't be counted. Please do this first.

Full name: Aditya Khamitkar
GitHub Profile Link: TheNaiveSamosa
Email ID<EMAIL_ADDRESS>Participant Role: Contributor for GirlScript Summer of Code 2024
Approach
1. Loading the Dataset

Read the training and testing datasets into dataframes.
Generated file paths with labels for images.

2. Data Preprocessing

Checked if the training data is balanced.
Split the testing data into test and validation sets.

3. Image Data Generation

Created an ImageDataGenerator for training, validation, and testing dataframes.
Used flow_from_dataframe to convert dataframes to numpy arrays.

4. Model Structure

Defined the model using Sequential API.
Added Conv2D, MaxPooling2D, Flatten, and Dense layers.
Compiled the model using Adamax optimizer and categorical_crossentropy loss.

5. Model Training

Trained the model using the fit method on the training generator.
Specified the number of epochs and used the validation generator for validation data.

6. Model Performance

Plotted training and validation loss and accuracy over epochs.
Identified the best epoch based on validation loss and accuracy.

7. Model Evaluation

Evaluated the model on training, validation, and testing data.
Printed the loss and accuracy for each dataset.

8. Prediction and Evaluation

Generated predictions using the model on the testing data.
Calculated the confusion matrix and classification report.
Saved the model to an HDF5 file.

This approach follows a standard workflow for building, training, and evaluating a deep learning model for image classification. It involves loading and preprocessing data, defining the model architecture, training the model, evaluating its performance, and saving it for future use.

##Approach for the Flask application I was thinking of adding. @Niketkumardheeryan

1. Loading Model and Labels

Loaded the pre-trained TensorFlow model for brain tumor classification.
Defined the class labels for different tumor types ('Glioma', 'Meningioma', 'No tumor', 'Pituitary').

2. Preprocessing Image

Defined a function to preprocess the uploaded image.
Resized the image to (150, 150) pixels.
Converted the image to a NumPy array and expanded its dimensions.

3. Converting Image to Base64

Defined a function to convert the processed image to a base64 string.
Used io.BytesIO to buffer the image and base64.b64encode to encode it.

4. Flask App Setup

Initialized a Flask application.
Loaded the model and class labels.

5. Routes

Defined a route ('/') to render the index.html template for uploading an image.
Defined a route ('/predict') to handle the image prediction.
Extracted the uploaded image, preprocessed it, and made predictions using the model.
Converted the predicted class to a label and rendered the result.html template with the prediction and the base64 encoded image.

6. Error Handling

Implemented error handling to catch any exceptions that might occur during image processing or prediction.
Rendered an error.html template with the error message.

7. Running the Application

Used the if __name__ == '__main__': block to run the Flask application in debug mode.

This approach sets up a Flask application for predicting brain tumor types based on uploaded images. It handles image preprocessing, model prediction, and error handling, providing a user-friendly interface for interacting with the model.

Please do assign this to me.


tune onnx like tvm

can disc tune onnx model like tvm?

We only support TensorFlow and PyTorch yet. Thus onnx model can not be directly imported. Maybe you could try onnx2tf or something similar.

Could BladeDISC tune torch.fx ?

Could BladeDISC tune torch.fx ?

Not directly. If you can convert to torchscript, then it's supported.

Something is happening to lower onnx to mhlo, the entrance IR of BladeDISC.
https://github.com/onnx/onnx-mlir/pull/1519/files


Updated README.md with more detailed basic usage instructions.

Updated the README.md file with some detailed basic usage instructions.

Fixed in 322460d6f752057ac76a2c530dd53886faf7fd27


[core]

JadxArgs jadxArgs = new JadxArgs();
jadxArgs.isSkipResources();
jadxArgs.isRespectBytecodeAccModifiers();
jadxArgs.isShowInconsistentCode();
jadxArgs.isFallbackMode();
jadxArgs.setInputFile(new java.io.File(input.getText().toString()));
jadxArgs.setOutDir(new java.io.File(output.getText().toString()));
try (JadxDecompiler jadxDecompiler = new JadxDecompiler(jadxArgs)) {
	jadxDecompiler.load();
	jadxDecompiler.save();

} catch (Exception e) {
e.printStackTrace();
}
I use this code, but it does not decompile the .dex file, but I change the name to .jar, it decompiles not as a java file but as a class. Can you send me the real code?

@Arashvscode most likely you forget to include jadx-dex-input plugin, check wiki page.

@Arashvscode most likely you forget to include jadx-dex-input plugin, check wiki page.

Can you help me a little more with the Java code, I just started the Java course, it's hard for me😅😅😅😅

Well, you just need to create a maven or gradle project and add maven dependencies mentioned in wiki :slightly_smiling_face:


Update gradle to pull the correct sheets connector version

Purpose
Fixes:6023
Examples
Checklist

[x] Linked to an issue
[ ] Updated the specification
[ ] Updated the changelog
[ ] Added tests
[ ] Checked native-image compatibility

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


Fix ingress tests

One of the ingress tests started failing once the hardcoded datetime in it fell 5 days behind the current date, because of the limitations of the API. I fixed it by using the freezegun library to mock all calls to datetime.now(). Introducing this ability made the override_inferred_weather_api argument unnecessary, so I removed it.

:O FreezeTime!! Should have known there would be a python library for my problems!


TestJlmRemoteMemoryNoAuth_2 failed on test-sxa-armv7l-ubuntu2004-odroid-1/2

TestJlmRemoteMemoryNoAuth_2 failed on test-sxa-armv7l-ubuntu2004-odroid-1/2
https://trss.adoptium.net/deepHistory?testId=62b87aaa250c3c428c4576ea

test suite/name?
Is there an existing issue elsewhere covering this?
Which machine(s) does it work on? other than those two problematic ones.
Which machine(s) does it fail on?  test-sxa-armv7l-ubuntu2004-odroid-1/2
Do you have a link to a Grinder re-run if the test with the failure? https://ci.adoptopenjdk.net/job/Grinder/5052/

Any other details:
https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_sanity.system_arm_linux/182/

The grinder youve linked shows the test passing on test-sxa-armv7l-ubuntu2004-odroid-1

Rerunning
test-sxa-armv7l-ubuntu2004-odroid-1
https://ci.adoptopenjdk.net/job/Grinder/5061/console
test-sxa-armv7l-ubuntu2004-odroid-2
https://ci.adoptopenjdk.net/job/Grinder/5062/console


NickeManarin.ScreenToGif - Version 2.37

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hot tip to change the folder name: Press "." on your keyboard when you have GitHub open to this PR in your browser, and a web version of VSCode will launch.
Once it loads, find the files you added, and rename the folder. Then use the source control button on the left to commit (it's automatically pushed).

@jedieaston Oh, I did but I forgot to push the changes after the commit. :(


Add missing translations on admin for buyer and buyer user

buyer user is still WIP

With this being a WIP, would you like to hold off the merge until you are complete, as complete as a partial update?


Prepare for new release of Confluence

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/3334594144, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/3334595487.

Integration tests pass, so current version of Jira Server for Slack is marked compatible with Confluence 7.20.1.


Class token in CvT?

Hi, thanks for your amazing work!
I have a question about CvT, to me it seems that there is no class token added before stage 3 but the features are averaged and passed directly to the classifier. Am I wrong?

@helia95 hey yes! now that you bring it up, I noticed I didn't add the classification token - however, this conflicts with the convolutional projections of queries (and the strided key / values), so I'm not sure how to approach it. it's not possible to append the one classification token to a square feature map

@helia95 honestly, after reading a bunch of papers, i don't think it'll matter much if it were CLS tokens or average pooled 😆 its just an interesting inconsistency in the paper


Error when deserialising BatchNormalization layers from yaml

System information

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow): Yes (see example below)

OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): Windows 10, Anaconda3

TensorFlow installed from: binary (pip)

TensorFlow version (use command below): tensorflow-gpu 2.1.0 (from pip)

Python version: 3.7.7

CUDA/cuDNN version: 10.2

GPU model and memory: GTX 1080

Describe the current behavior
When deserialising from yaml a model that contains a BatchNormalization layer, I get the exception yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/object/apply:tensorflow.python.training.tracking.data_structures.ListWrapper'. Indeed, inspecting the yaml shows that this tag is in the BN layer, as follows:
[... other yaml]
  - class_name: BatchNormalization
    config:
      axis: !!python/object/apply:tensorflow.python.training.tracking.data_structures.ListWrapper
      - - 3
[... other yaml]

I have included a script below that seems able to reproduce this. Oddly, I then tried the same script on a Ubuntu system with tensorflow==2.1.0 and that appeared ok, so this might only apply to tensorflow-gpu.
Describe the expected behavior
The script below serialises and deserialises to/from yaml without errors.
Standalone code to reproduce the issue
import tensorflow as tf

input_layer = tf.keras.layers.Input(shape=(32,32,3))
output = tf.keras.layers.BatchNormalization()(input_layer)
model = tf.keras.Model(inputs=input_layer, outputs=output)

yaml_out = model.to_yaml()
model2 = tf.keras.models.model_from_yaml(yaml_out)

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Full traceback:
Traceback (most recent call last):
  File ".\bin\reproduce-bug.py", line 13, in <module>
    model2 = tf.keras.models.model_from_yaml(yaml_out)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\tensorflow_core\python\keras\saving\model_config.py", line 76, in model_from_yaml
    config = yaml.load(yaml_string)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\__init__.py", line 114, in load
    return loader.get_single_data()
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 51, in get_single_data
    return self.construct_document(node)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 60, in construct_document
    for dummy in generator:
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 413, in construct_yaml_map
    value = self.construct_mapping(node)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 218, in construct_mapping
    return super().construct_mapping(node, deep=deep)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 143, in construct_mapping
    value = self.construct_object(value_node, deep=deep)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "C:\Users\nitbi_000\anaconda3\envs\tf2-gpu\lib\site-packages\yaml\constructor.py", line 429, in construct_undefined
    node.start_mark)
yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/object/apply:tensorflow.python.training.tracking.data_structures.ListWrapper'
  in "<unicode string>", line 24, column 13:
          axis: !!python/object/apply:tensorflow ...

@nitbix
i ran the code shared by you and do not face any error, please find gist here

@Saduf2019 thanks for checking. I tried tensorflow-gpu in colab and that seems to work as well.
I dug a bit more and narrowed it down a bit. This only happens with later versions of pyyaml - with 5.3.1 it fails on all environments I tested, with both tensorflow and tensorflow-gpu. Seems to be a change from 5.1 (ok) to 5.2 (not ok).
At this point I don't know if it's a bug in pyyaml or its behaviour has changed by design and something needs to be changed in tensorflow, that's where my knowledge of pyyaml stops.
I've managed to reproduce it in colab as well simply by changing the pyyaml version.

@nitbix
Can you please share the gist of google colab you have reproduced the error.

@Saduf2019 https://colab.research.google.com/gist/nitbix/b9db4179a0d72b1797f83909c89e69ae/37885.ipynb
the only difference from yours is the pyyaml version

@nitbix
i ran the same gist on the latest version of tensorflow and the error does not exist on the latest version of tensorflow, please find the gist here

👍 I guess someone must have already fixed this then. I'll keep an eye out for 2.2.0. In the meanwhile, for posterity, a temporary workaround for 2.1.0 is to downgrade pyyaml to <5.1.

@nitbix
please confirm if we may move this issue to closed status

Yup, I'll reopen it if it recurs in the future. Thanks.
On Thu, 2 Apr 2020 at 18:58, Saduf2019<EMAIL_ADDRESS>wrote:

@nitbix https://github.com/nitbix
please confirm if we may move this issue to closed status
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/37885#issuecomment-608013165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATCVCG6TVNMHKCZU6Q6VZDRKTG5NANCNFSM4LTEHILA
.

--
Alan

Moving this to closed status with user confirmation

version:2.2.0rc4 still has this problem.
ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/object/apply:tensorflow.python.framework.tensor_shape.TensorShape'
  in "<unicode string>", line 4, column 22:
      build_input_shape: !!python/object/apply:tensorflow ...

@lengthmin
I ran the code on tf nightly and 2.2 and did not face any issues, please find the gist here for nightly and 2.2.
Please share a colab gist in case you face any issues.

I am still facing this issue on tf nightly and 2.2. I am executing the code in a multinode spark cluster.
pipeline = Pipeline(stages=[estimator])
start = timeit.default_timer()
All the program statements
fitted_pipeline = pipeline.fit(df)
Error
ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/object/apply:tensorflow.python.framework.tensor_shape.TensorShape'
in "", line 4, column 22:
build_input_shape: !!python/object/apply:tensorflow ..

I am still getting the same error while executing on spark cluster even on   tf nightly and 2.2
pipeline = Pipeline(stages=[estimator])
start = timeit.default_timer()
fitted_pipeline = pipeline.fit(df)
Error
ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/object/apply:tensorflow.python.framework.tensor_shape.TensorShape'
in "", line 4, column 22:
build_input_shape: !!python/object/apply:tensorflow ...

The detailed log file is attached. Please let me know if any solution

@snigdhasen
Could you please create a new issue as this is closed.

I have created new issue
https://github.com/tensorflow/tensorflow/issues/47163
On Mon, Feb 8, 2021 at 10:36 AM Saduf2019<EMAIL_ADDRESS>wrote:

@snigdhasen https://github.com/snigdhasen
Could you please create a new issue as this is closed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/37885#issuecomment-774868770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM3WUNOWKCLYU3CDKX4FN23S55WOVANCNFSM4LTEHILA
.

--
Regards,
Snigdha Sen


Revert "feat: Add compareSnapshot option to allow test failure"

This reverts commit 5090510e997ada26dd8b80a7bd7a810440b935ab.

:tada: This PR is included in version 1.19.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add headerIsClipped for clipped header

Hi!
I have problem with shadow.
Can we add a property to avoid clipped in the header?

Hey @AndriiZakhliupanyi thank you for your contribution, have a wonderful day!


Issue refresh token

Hi,
It seems that the function refresh_ (with the underscore) doesn't exist is the 8th version. I have an error when I run my app and the token is expired. With the 7th version it's ok
Regards,

Thanks, silly mistake on my part.


Break the limitations

Use dict instead of OrderedDict for recent Python versions  …
Add custom_encoder to process "unsupported types"

I do not agree the suggestion. The custom_encoder is specialized for some use-case.
We can write as following:
q = pyjq.compile(".")
data = {"now": datetime.datetime.now()}
q.one(c_encoder(data))

Additionally, we can define a wrapper class:
class JqWithEncoding:
  def __init__(self, q, encoder):
    self.q = q
    self.encoder = encoder

  def one(self, data):
    return self.one(self.encoder(data))

  # also define all(), first()


Failed to create run" ... error=" run not due until: 2019-07-19T16:55:30Z

When the system starts up a miscommunication between the kv.TaskService and the scheduler causes the scheduler to believe it should be executing tasks but the kv.TaskService disagrees.

Should be fixed by https://github.com/influxdata/influxdb/pull/14668


Remove a few extra spaces

This makes the format more consistent across the table.
You can preview this PR here : https://gene1wood.github.io/foss_photo_libraries/

LGTM!


Ability to normalise 2 channel normal maps (and use custom packaged textures)

It would be super nice to be able to generate mipmaps for normal maps consisting of only 2 channels, and still have correct normalisation. This would likely also require the ability to specify which channels the 2 normal map channels are stored in, and mipmap the others as normal, which would allow normals to also be packed alongside existing data
I would envision adding channel parameters to -normalmap, so something like -mipmap -normalmap 1,3 (mipmap, treating channels 1 and 2 as the [2 channel] normalmap)
It would assume the source normals were initially normalised, and maybe calculate what the extra channel would be, then normalise the 2 remainder and the third in memory when generating each reduced mipmap, so that lengths were correctly maintained (or maybe some other method if there's a more sound mathematical convention).
Being able to specify channels for parameters like -normalmap would also provide knowledge about channel packing and may allow other abilities later on, when packing data together.

Got it - this is a good idea. It's on the TODO list.


Datasets/test file

Hello. Could you please tell me which sequence is the 000123.ply from?

Hi! This scan is from sequence 08 from SemanticKITTI, the validation sequence.


config-linux.md: document seccomp

The current documentation for seccomp specification is incomplete. This adds the missing details to allow for more complete utilization of the feature.
Fix: #742
Signed-off-by: David Lyle<EMAIL_ADDRESS>

Thanks for this PR but we actually had #706 open to resolve this.  I merged it this morning so I think this can be closed as a dup.
Thanks for opening the issue and PR.


Make sure change local serviceInstance after remote operation.

Make sure change local serviceInstance after remote operation.

Codecov Report

Merging #7798 (84ea756) into master (f29663b) will increase coverage by 0.04%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master    #7798      +/-   ##
============================================
+ Coverage     59.18%   59.23%   +0.04%
- Complexity      529      556      +27
============================================
  Files          1076     1083       +7
  Lines         43540    43761     +221
  Branches       6363     6365       +2
============================================
+ Hits          25771    25921     +150
- Misses        14903    14975      +72
+ Partials       2866     2865       -1

Impacted Files
Coverage Δ
Complexity Δ

...ubbo/registry/client/AbstractServiceDiscovery.java
45.45% <50.00%> (ø)
0.00 <0.00> (ø)

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-27.59%)
0.00% <0.00%> (ø%)

...ntext/event/AwaitingNonWebApplicationListener.java
46.96% <0.00%> (-25.76%)
0.00% <0.00%> (ø%)

...bo/rpc/cluster/support/FailbackClusterInvoker.java
52.45% <0.00%> (-18.04%)
0.00% <0.00%> (ø%)

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
0.00% <0.00%> (ø%)

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
0.00% <0.00%> (ø%)

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
0.00% <0.00%> (ø%)

...ache/dubbo/cache/support/AbstractCacheFactory.java
87.50% <0.00%> (-12.50%)
0.00% <0.00%> (ø%)

...bo/config/event/listener/LoggingEventListener.java
50.00% <0.00%> (-12.50%)
0.00% <0.00%> (ø%)

...che/dubbo/remoting/transport/mina/MinaChannel.java
35.52% <0.00%> (-10.53%)
14.00% <0.00%> (-1.00%)

... and 97 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 f29663b...84ea756. Read the comment docs.


Metrics refactoring suggestion

Problem:
Current state of exported metrics does not allow for flexible monitoring solutions.
Examples:
arangodb_http_request_statistics_http__requests_total:
Currently there's a separate metric for each http method. Such solution forces to manually type out each metric in queries which greatly increases code duplication (we can also make queries like {__name__=~"arangodb_http_request_statistics_http_.*_requests_total" }, but it's still not very nice).
The metric would make much more sense if http method became a label, i.e arangodb_http_request_statistics_http_requests_total{method="delete"}
*_percent metrics
It's generally better to return absolute values and their thresholds if known. This reduces the amount of computation on the server and allows for more informative dashobards in grafana. A more concrete example:
arangodb_network_request_duration_as_percentage_of_timeout
Splittng this metric into arangodb_network_request_duration and arangodb_network_request_timeout benefits observability and the percentage can be easily calculated.
Histograms are too aggregated
Suppose you wanted to find out most frequent slow query. Related metric is arangodb_aql_slow_query_time, but it only allows to get information about all existing queries. It would be nice to have a label query containing the body of the query.

Currently there's a separate metric for each http method. Such solution forces to manually type out each metric in queries which greatly increases code duplication (we can also make queries like {name=~"arangodb_http_request_statistics_http_.*_requests_total" }, but it's still not very nice).
The metric would make much more sense if http method became a label, i.e arangodb_http_request_statistics_http_requests_total{method="delete"}

Only if sometimes we create metrics v3.

arangodb_network_request_duration_as_percentage_of_timeout
Splittng this metric into arangodb_network_request_duration and arangodb_network_request_timeout benefits observability and the percentage can be easily calculated.

Good point, but we still need old metrics for backward compatibility.

Histograms are too aggregated
Suppose you wanted to find out most frequent slow query. Related metric is arangodb_aql_slow_query_time, but it only allows to get information about all existing queries. It would be nice to have a label query containing the body of the query.

I don't think it's useful.
You can have a million queries, also query lifetime can be short.
So we don't need to monitoring them

Feel free to reopen if have some questions


Metadata editor: allow for links to "documentation" to help users understand the purpose

1.0.0
Elyra exposes quite a few  metadata editors in the UI, such as the runtime images editor, shown below.

When a user accesses an editor (which is likely if it is exposed in the sidebar) it might not always be clear what the metadata is used for. While the metadata purpose can sometimes be inferred (e.g. for code snippets), there might also be quite a bit of ambiguity for a novice user who is not (yet) familiar with the workflow that is supported by this metadata.
It would therefore be nice if "the editor" could make additional information available that provides context information that helps new users understand its purpose. In the case of runtime images it might be a short piece of text (or a link to the relevant documentation page) that outlines what a runtime image is ("a Docker image in a public image registry") and maybe give an example what the user can do with it. ("Notebook pipelines can run notebooks in these runtimes.")
Just food for thought.

Good idea @ptitzler.  I would recommend we use the description property of the metadata property of the corresponding schema object to house this information.

For illustrative purposes, this is what this might look like.

Constraints:

The link should be represented in a way that makes it easy to notice.
The URL property should be part of the schema definition.
This property is optional. Nothing is shown in the UI if the property is not defined.
The URL should be validated when the schema information is read and a warning be logged if the URL is invalid.

What should happen in the UI if the URL is invalid? Should it still be displayed in some form to make it obvious that something is broken?

Delivery of this feature requires

updates to every schema (addition of an optional static value property)
a widget that renders the property value

For example:

Introduce a new optional property  reference_url in the schema, which points to a public URL, such as https://elyra.readthedocs.io/en/latest/user_guide/runtime-image-conf.html for the runtime image
If present, the property value is rendered in a user-friendly fashion in a prominent location when the editor displays a metadata entry during ADD and EDIT operations.

The link to the URL opens in a new browser window

metadata type
link

Runtime configuration Airflow  and Runtime configuration KFP
https://elyra.readthedocs.io/en/latest/user_guide/runtime-conf.html

Runtime image configuration
https://elyra.readthedocs.io/en/latest/user_guide/runtime-image-conf.html

Code snippet
https://elyra.readthedocs.io/en/latest/user_guide/code-snippets.html


Images overlaps the divider in the features section on page /catalog/traffic-management

Description
Some images overlap the divider line between images and descriptions.
Expected Behavior

Screenshots

Enviroment:

OS:  Windows
Browser: Chrome
Version:
Device: Desktop Mobile

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote Ok✌.


[REST API] Add support for returning values from Move calls to REST API

We have recently added support for returning values from Move calls (#784) but did not integrate it at the user-level. This task it to track adding this support to the REST API.

@awelc In https://docs.sui.io/build/move#move-functions, it still says
In general, an entry function, must satisfy the following properties:

- have no return value

Should we update that?

@awelc In https://docs.sui.io/build/move#move-functions, it still says
In general, an entry function, must satisfy the following properties:

- have no return value

Should we update that?

We should once user-facing changes are in. Otherwise it would be confusing - docs would say one thing and the user experience would be another thing.


[CAMEL-9121] activemq-camel pulls in outdated version of commons-pool2

Hi Thomas,
Thanks for this PR. The code has been merged.
Can you close the PR? Many thanks once again :-)