Node Module issues

I have installed this in my Angular 11 Application, I get no errors while importing fromPath but as soon as I try to use fromPath it gives me error shown in the screenshot.
I am using macOs Monterey and have installed the ghostscript and graphicsmagick in my laptop using homebrew. My node version is v16.14.2.
There was no mention of importing anything in angular.json from node_modules etc, should I import something in the node_modules?
Please help me to understand what I am missing

This package works in node.js, not in your browser.
fs and path are node api's, browsers don't have them.

So I cannot use this package in Angular Application?

The package only supports node.js environment as stated in prerequisites.
It cannot work in the browser and probably not in the mobile app.


lxc rename asks for a destination remote

Distribution: Ubuntu
Distribution version: 16.04.4
The output of "lxc info" or if that fails:

Kernel version: 4.4.0-121-generic
LXC version: 3.0.0
LXD version: 3.0.0
Storage backend in use: zfs

Issue description
lxc rename is implemented as a wrapper around lxc move and the rename flavor is supposed to not require a destination remote to be provided. This is logical as a rename can only happen on a given remote. The issue is that calling lxc rename rmt:foo bar fails with:
Error: Can't specify a different remote for rename..
This can be worked around by providing "rmt:bar" as second argument but this kinds of defeats the purpose of rename altogether. IMHO, rename should accept a destination remote that's identical to the source one or default to the source one if none is provided.

Something like that maybe?
diff --git a/lxc/rename.go b/lxc/rename.go
index fce0282..a0922bd 100644
--- a/lxc/rename.go
+++ b/lxc/rename.go
@@ -44,7 +44,9 @@ func (c *cmdRename) Run(cmd *cobra.Command, args []string) error {
                return err
        }

-       if sourceRemote != destRemote {
+       if destRemote == nil {
+               destRemote = sourceRemote
+       } else if sourceRemote != destRemote {
                return fmt.Errorf(i18n.G("Can't specify a different remote for rename."))
        }


Can't install correctly on Python 3.4

I've tried install djangocms-youtube via pip but I keep getting this error when trying to run any migrate or runserver commands.
djangocms_youtube.Youtube.thumbnail: (fields.E300) Field defines a relation with model 'Image', which is either not installed, or is abstract.
I also had several other errors that were fixed by doing pip install easy-thumbnails and now I'm stuck on this one. Its probably something obvious but I've not worked much with django. Any advice?

Have you installed django-filer? It's a dependency for djangocms-youtube. Sorry it's not clear in the README!

FYI: This fork https://github.com/natgeo/djangocms-youtube by National Geographic removes the django-filer dependency, feel free to install their version if you don't want to use  django-filer.

Thanks for the quick response! I will give it a shot later today and report back.

@roemhildtg Have you resolved this issue? Can I close this now?

I haven't been able to test yet, but you can close the issue. If it still exists when I test it I will reopen.

Just a thought but it might be helpful for newcomers to django/python to list the other package requirements somewhere for django-youtube.


Can't save modification in a form using Internet Explorer

Tested with IE 10.
Using IE, if I post a form, I get a "save successful" message, but nothing is sent to the server.
Everything works fine on Chrome & FF.
I don't know if it's related, but when viewing the form, the error below occurs in the vendor.js file, on this line of code :
_this.props.action.updateProperties({
query: React.findDOMNode(_this.refs.query).value
});

Update : Data is actually being saved to database, but the browser is loading the old version of the page.

Should be declarated in focus components

Issue transfered to focus-components.


It seems like it doesnt work as it should.

"You should see the Vue app appear, that is populated via the API." - this is never happen:( I've tried to change ports etc, but still nothing.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c924f1c1-823e-3e29-bf09-405fc4c6bbb8
Version Independent ID: 585c2426-5f9b-8499-8eda-0e56bd64c93c
Content: Create an ASP.NET Core app with Vue - Visual Studio (Windows)
Content Source: docs/javascript/tutorial-asp-net-core-with-vue.md
Product: visual-studio-windows
Technology: vs-javascript
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@Tipsets -- Alexander, thank you for writing to us.  Please be more specific about the your issue and the displayed results.  Meanwhile, consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

Sure thing, William, - i've tried to do everything step by step, but couldnt archive the goal of your tutorial - "Vue app appear, that is populated via the API". I've tried to use different ports setups and installation order of projects, but blank page and console errors are all i've got so far.

@Tipsets -- Alexander, thank you for your follow-up.  This repo is solely for documentation issues, with limited support options, and this appears implementation-related.  Please try the resources I mentioned earlier.
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.

@Tipsets For this issue, please use the Report a Problem tool to report the issue. When you do this, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.


chore(release): Autobump agent service version (1.0.6)

Automated PR

Merging into the release notes branch


Dev

TreatmentPatterns 2.6.1

Bumped R version to 4.2.1
Added additional unit-tests for createSunburstPlot2() and createSankeyDiagram2()
Updated to use DATEDIFF
Added functionality to choose how groups below the minimum cell count are censored.
Made some parameters ambiguous for createSankeyDiagram2 and createSunburstPlot2() for more control over the figures.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (rc@9b57620). Click here to learn what that means.

:exclamation: Current head 9021486 differs from pull request most recent head 98a61e5. Consider uploading reports for the commit 98a61e5 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##             rc     #193   +/-   ##
=====================================
  Coverage      ?   92.66%
=====================================
  Files         ?        8
  Lines         ?     1240
  Branches      ?        0
=====================================
  Hits          ?     1149
  Misses        ?       91
  Partials      ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Added the following points:

Removed addNoPath parameter.
Renamed minFreq parameter to minCellCount.
Added Shiny app with exported module classes.
Added censoring options of persons falling below the minCellCount.


Better Documentatoin Design

The initial design is built with simple HTML  using bootstrap and Flat-UI theme, we want to have better design docs.

Look into Swagger docs.

if the API is [re]written in OAS/swaggerspec, you'll get a lot for free with swaggerui+generated clients - including better documentation. i've done this before, let me know if you'd like some assistance.
jazakumallahu khair on your work with this project

@amerghazal I want to look into https://www.django-rest-framework.org/topics/documenting-your-api/ and pick the right package, if you like to contribute and help, you can do the research and implement it.

i'll take a stab at this in the coming few days, iA


India site: RUVNL stability

When deploying new india site model.
Make sure the RUVNL service runs smoothly.
Might need to add filter on which sites to load in the database.

Need to add ruvnl to client_site_name and then add a search option in https://github.com/openclimatefix/india-forecast-app/blob/main/india_forecast_app/app.py#L46


Not able to get the prometheus metrics

What happened?
I have enabled the service monitor in the respective CRD's but after importing the dashboard I cannot see the fabric metrics.

What did you expect to happen?
Available metrics
How can we reproduce it (as minimally and precisely as possible)?
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts -n monitoring
helm install my-kube-prometheus-stack prometheus-community/kube-prometheus-stack --version 52.1.0 -n monitoring
kubectl port-forward deployment/my-kube-prometheus-stack-grafana 3000 -n monitoring
Anything else we need to know?
No response
Kubernetes version

# kubectl get nodes -o wide

resolved


API visibility - all non-public APIs should be in “implementation” package

In the review process of Sprig Cloud Azure 4.0, several classes are considered non-public APIs or chosen to expose later. We agree to move them to the "implementation" package.

The *ClientBuilderFactory classes in the spring-cloud-azure-service package.
The *ConfigurationProperties classes in the spring-cloud-azure-autoconfigure package (we will change the visibility of these classes).

For the *ConfigurationProperties classes, I've tried to make their visibility to package level, but it won't fit for most cases:

We use the AzureComosProperties in spring-cloud-azure-actuator for the Cosmos health indicator.
We use StorageBlobProperties in Event Hubs autoconfiguration for checkpoint store.
We use the EventHubsProperties in the resource manager configuration.

So this solution won't work.

@saragluna thanks for the info! would it be possible to explore an implementation package option that allows keeping shared classes accessible for other packages?

Hi @lmolkova, moving the *ConfigurationProperties classes to the implementation package will introduce another problem, for our *Autoconfiguration classes will reference these classes in their constructors.

Hi @lmolkova, moving the *ConfigurationProperties classes to the implementation package will introduce another problem, for our *Autoconfiguration classes will reference these classes in their constructors.

It can still be done with constructor injection (constructor would stay package-private) or am I missing something?

I will try to move them.

@lmolkova the pr has been merged.

Closing this issue now for all related classes have been moved to impl packages.


add GraalVM native image configuration files

This PR adds GraalVM native image configuration files. These configuration files allow applications that use JANSI to be compiled to native images.
This PR partly addresses https://github.com/fusesource/jansi/issues/162 ; I raised another PR in the hawtjni project to address the Library issue.
For reference, see

https://github.com/oracle/graal/blob/master/substratevm/JNI.md
https://github.com/oracle/graal/blob/master/substratevm/RESOURCES.md

The resource configuration allows the windows64/jansi.dll file to be included in the native image.
The intention is that these files end up in the jansi-$VERSION.jar file in the following locations:
/META-INF/native-image/jansi-native/jni-config.json
/META-INF/native-image/jansi-native/resource-config.json

The resource-config.json in the current PR only includes the win64 jansi.dll in the native image. It may be better to include the 64-bit libraries for all supported OS-es, to allow more general usage of the Jansi native code in GraalVM native images for  Linux and MacOS as well as Windows. (Since GraalVM doesn’t support 32-bit, there’s no need to include the 32-bit libraries as resources in native images.)
I’ll update the PR.

why support only Windows by default, and not other OS?
Linux or Mac are also very popular
I don't know what's the impact of having too much resources included, but perhaps the solution is to have no resource by default but provide a good documentation on how to add the right resource based on users native platform, isn't it?

on jni-config.json, is there a way to check that the content matches the library? to avoid issues in the future if the library is updated

@hboutemy Thanks for getting back!

I don't know what's the impact of having too much resources included, but perhaps the solution is to have no resource by default but provide a good documentation on how to add the right resource based on users native platform

Yes, that sounds reasonable.

why support only Windows by default, and not other OS? Linux or Mac are also very popular.

Interesting! What is the use case for Jansi on Linux and Mac? I thought on those OS's ANSI colors are supported out of the box.

on jni-config.json, is there a way to check that the content matches the library? to avoid issues in the future if the library is updated

Good point. Yes, every time the library is updated, the jni-config.json should be updated too, perhaps as part of the build. One idea is to invoke picocli.codegen.aot.graalvm.JniConfigGenerator that is included in picocli-codegen as part of the build. The below command (copied from the https://github.com/fusesource/jansi/issues/162 ticket) shows how this can be done in a windows batch script, please adjust the syntax as needed for your build tool:
REM (on windows)

set PICOCLI_VERSION=4.3.2
set JANSI_VERSION=1.18

java -cp picocli-%PICOCLI_VERSION%.jar;jansi-%JANSI_VERSION%.jar;picocli-codegen-%PICOCLI_VERSION%.jar ^
  picocli.codegen.aot.graalvm.JniConfigGenerator ^
  org.fusesource.jansi.internal.CLibrary ^
  org.fusesource.jansi.internal.Kernel32 ^
  -o=.\jni-config.json

Then, ensure the file is included in the jansi JAR in the following location (any unique location under /META-INF/native-image is fine):
/META-INF/native-image/fusesource/jansi-native/jni-config.json

@hboutemy Thanks for getting back!

I don't know what's the impact of having too much resources included, but perhaps the solution is to have no resource by default but provide a good documentation on how to add the right resource based on users native platform

Yes, that sounds reasonable.

why support only Windows by default, and not other OS? Linux or Mac are also very popular.

Interesting! What is the use case for Jansi on Linux and Mac? I thought on those OS's ANSI colors are supported out of the box.

Jansi provides access to several low level functions that are useful when a java application needs to access the console.  Those are the ones in the CLibrary and Kernel32 libraries exposed by jansi-native.

on jni-config.json, is there a way to check that the content matches the library? to avoid issues in the future if the library is updated

Good point. Yes, every time the library is updated, the jni-config.json should be updated too, perhaps as part of the build. One idea is to invoke picocli.codegen.aot.graalvm.JniConfigGenerator that is included in picocli-codegen as part of the build. The below command (copied from the fusesource/jansi#162 ticket) shows how this can be done in a windows batch script, please adjust the syntax as needed for your build tool:
REM (on windows)

set PICOCLI_VERSION=4.3.2
set JANSI_VERSION=1.18

java -cp picocli-%PICOCLI_VERSION%.jar;jansi-%JANSI_VERSION%.jar;picocli-codegen-%PICOCLI_VERSION%.jar ^
  picocli.codegen.aot.graalvm.JniConfigGenerator ^
  org.fusesource.jansi.internal.CLibrary ^
  org.fusesource.jansi.internal.Kernel32 ^
  -o=.\jni-config.json

Then, ensure the file is included in the jansi JAR in the following location (any unique location under /META-INF/native-image is fine):
/META-INF/native-image/fusesource/jansi-native/jni-config.json

I'd like to release a new version of Jansi.  Can we leave that aside or do we need to consider fixing the problems before ?

@gnodet Thanks for getting back!

I'd like to release a new version of Jansi. Can we leave that aside or do we need to consider fixing the problems before ?

A new release, great! Sounds like an opportunity to fix the problem! :-)
jni-config
This is straightforward. You can either include the file from this PR, or, you can regenerate the jni-config.json file with the command shown in my previous comment. Regenerating is only needed if the CLibrary or Kernel32 API has changed since jansi-1.18.
Include the jni-config.json file in this location in the new jansi jar:
/META-INF/native-image/fusesource/jansi-native/jni-config.json

resource-config
Given your feedback, the simplest idea is to create a resource-config.json file that lists all 64-bit native libraries that are included in the jansi JAR. The contents of this file looks like this:
{
  "resources": [
    {"pattern": "META-INF/native/freebsd64/libjansi.so"},
    {"pattern": "META-INF/native/linux64/libjansi.so"},
    {"pattern": "META-INF/native/osx/libjansi.jnilib"},
    {"pattern": "META-INF/native/windows64/jansi.dll"}
  ]
}

Include this resource-config.json file in the following location in the new jansi jar:
/META-INF/native-image/fusesource/jansi-native/resource-config.json

What this does
The above two steps will allow applications to use the jansi functionality in GraalVM native images.
Including all native Jansi libs in the GraalVM native image is a bit overkill, but these libs are not that big, and applications can customize with a separate exclusion config if they really really want to. Meanwhile, this works out of the box (nice for users) and is easy to maintain (nice for the jansi maintainers).


Adds --fix-dry-run option

Fixes #170

Here how the diff looks like in the console:

One issue though. At the moment diff will include all lines from a file. We can remove some unchanged lines like git does it, but I am not sure if it worth it. What do you think?

This looks great @mushketyk
Yes, it is absolutely worth compressing the unchanged lines just like git does.
I just ran your dry-run branch over zeppelin contracts. As you can see, with large codebases, this produces a lot of irrelevant lines that shouldn't concern the user.
Do you think you can achieve this (does the diff library have this feature in built)?

@duaraghav8 Makes sense. I'll look into this.

Does the diff library have this feature in built
It has another methods called createPatch. Maybe it can generate a proper diff.

@mushketyk is there an easy way to also display the line numbers? something like:
Diff for: /Users/raghavdua/Desktop/github/zeppelin-solidity/contracts/token/ERC20/TokenVesting.sol
@@ -71,9 +71,9 @@
28     released[token] = released[token].add(unreleased);
29     token.safeTransfer(beneficiary, unreleased);
30
31 -    Released(unreleased);
31 +    emit Released(unreleased);
32   }

Note: if there is no easy way to implement this, then we'll leave it for now and make modifications in subsequent iterations

Hi @duaraghav8,
Sorry for a late response.
That won't be that straightforward, unfortunately. We can get a raw diff from this library then count and display line numbers. None of this is provided out of the box.

@mushketyk not a problem!


link to ai from right panel

for folks new to this repo, api docs only work for aws classic, and aiven in the preview link

okay so the api docs preview looks super weird; @sean1588 is this cause related resources don't work in the previews? anyway to get an idea of what this will look like b before shipping?

closing in favor of https://github.com/pulumi/registry/pull/2437


v2s1 manifest followup

This is an update to #34 :

Fix references to the manifest format: v2s1, not v1s1
Move the code to a separate dockerutils package: the OpenShift client pushing data (or, possibly, a Docker registry push client) will need it, so the signature package is not appropriate.

Similarly, the OpenShift client will probably like to reuse the layer enumeration code from docker.go, and it seems cleaner to put such transport-independent utilities into a separate package (and leave docker.go for the Docker Registry transport only).
Alternatively, we could just vendor in more of docker/distribution and perhaps docker/docker instead of having our own implementations, but I got the impression (perhaps mistaken?) that this would be unwelcome.

Vendoring docker stuff was how skopeo was implemented but given the fast pace they're developing and fixing their libraries it wasn't feasible to me at all. This is how docker-utils from Vincent Batts is also implemented. The docker libraries pull in so much code also.
This LGTM

What I said applies to just the main interaction with registries. If you feel their libraries makes a better job at the stuff you're working on then I think I could leave with it. Otherwise I'd like to keep the vendor code base small and do things on our own.

Needs a rebase then I'll merge

Rebased.


Fixing the GCC tests

This is work toward fixing the GCC tests.

LGTM

@jamiebramwell Nice use of the sign-off mechanism!
I’m investigating why it failed...

@jamiebramwell Nice use of the sign-off mechanism!
I’m investigating why it failed...

Ha! I was sneakily investigating this to show off your work in the group meeting today. I'm slowly learning... 🐢

Erf... I wish it worked then!

Found the cause, but lunch is calling!

Should be fixed by #39

I'll check it out! This was probably it.

Looks like it passes in serial, but not parallel. The hunt continues! Thanks for the help @samuelpmish !

Getting close! Fixed the linear elastic test and now i'm going after the parallel dynamic one.

Good hunt!

The tests now pass using intel, gcc, and clang. 🎉 I'm going to try the quartz builds using gitlab.

LGTM

Can’t wait to see the results. Those three red dots and seeing the progress in your branch was my only thrill lately...

Yippee! 🎉

Thanks @adrienbernede !!


Update rspec & capybara

I'll going to upgrade Rails4.2 (#161), so I upgraded RSpec (~> 3.0) at first.
After RSpec upgrading, warnings is caused so i suppressed them by upgrading capybara.

LGTM

ohhhhh im resolving conflict....

Oh, I upgraded other gems...so i close this PR and create new PR  to upgrade rspec-rails and capybara... sorry...


feat: support sync cache creation

Please check if the PR fulfills these requirements

[x] Followed the Contributing guidelines.
[x] Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Add non-async createCache() that caching() uses to set up methods (keep current functionality intact).
Having createCache() as addition to caching() allows devs to create cache instances synchronously, and i.e use as default params in methods:
/** Awesome service that will use memory store as default cache, if nothing else specified */
class MyItemService {
   constructor(public cache = createCache(memoryStore())) { }
}

@denkan - can you add in an update to the readme on how to use this?

Codecov Report

Merging #598 (b2345ef) into master (64e5cce) will not change coverage.
Report is 6 commits behind head on master.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff            @@
##            master      #598   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          292       313   +21
  Branches        75        77    +2
=========================================
+ Hits           292       313   +21

Files
Coverage Δ

src/caching.ts
100.00% <100.00%> (ø)

@denkan - thanks so much for doing this. One thing I was thinking is that we might want to change it to be createMemoryCache as a simple helper function. The reason is that it could be confusing to do this function as sync when if they put in an async store it will cause issues.
You could even simplify and not require them to put in the in-memory store if you wanted.
Can you change that over and update the branch to latest? If you are good with these changes and update it we can check this in. 🎉

I'd love to use this feature as well!

@casey-chow - we are ready to merge this. Can you do the following:

update your branch to the latest and resolve conflicts
make sure you are at 100% test coverage
make sure documentation with how to use this is updated

🍻

@casey-chow are you able to update the branch?

@jaredwray and others,
Sorry I dropped the ball on this one (as I mostly use another github account for daily work nowadays).
✅  I've rebased and resolved conflicts.

@denkan - thanks so much for doing this. One thing I was thinking is that we might want to change it to be createMemoryCache as a simple helper function. The reason is that it could be confusing to do this function as sync when if they put in an async store it will cause issues.
You could even simplify and not require them to put in the in-memory store if you wanted.

I don't really want to do this, as it's not actually limited to memoryStore? I could easily define custom store that doesn't require async initialization.
And I think it's better to let the user of the lib define a shorthand if needed:
export const defaultCache = () => createCache(memoryStore({ /* my options */ }));

// later
class MyItemService {
   constructor(public cache = defaultCache()) { }
}

Let me know your thoughts or if it's ready to merge 🍻

@jaredwray and others,
Sorry I dropped the ball on this one (as I mostly use another github account for daily work nowadays).
✅  I've rebased and resolved conflicts.

@denkan - thanks so much for doing this. One thing I was thinking is that we might want to change it to be createMemoryCache as a simple helper function. The reason is that it could be confusing to do this function as sync when if they put in an async store it will cause issues.
You could even simplify and not require them to put in the in-memory store if you wanted.

I don't really want to do this, as it's not actually limited to memoryStore? I could easily define custom store that doesn't require async initialization.
And I think it's better to let the user of the lib define a shorthand if needed:
export const defaultCache = () => createCache(memoryStore({ /* my options */ }));

// later
class MyItemService {
   constructor(public cache = defaultCache()) { }
}

Let me know your thoughts or if it's ready to merge 🍻


add lines of clarification to CONTRIBUTING.md

Having people specifically open the Rproj file into
Rstudio is the best way to achieve consistency and familiarity.
@coughls and @hlapp, does this look satisfactory?

:+1:


how to enable TLSv1.2 when using KeyVaultClient to connect to Azure Key Vault via auzre keyvault sdk for python

I dont find any special param to set the ssl/tls version
I am refering this article to setup the python app, and there is nothing realtive to ssl/tls version, By default its TLSv1

Hi @VampireDaniel, thanks for reporting this we'll have someone on the team take a look.

Hi @loarabia , thanks for replying.
I really desire for this TLS v1.2 feature, may I have an ETA for this?

This should already be supported. I'll have to set up a test environment to verify, but in the meantime, can you run python -c "import requests; print(requests.get('https://www.howsmyssl.com/a/check').json()['tls_version'])" to see if TLS 1,2 is supported on your system.

thanks @johanste . one more thing is, the azure portal for keyvault don’t provide the option for me to set the minimal TLS version which don’t like other PaaS.
get response from chrome
"given_cipher_suites": [
"TLS_GREASE_IS_THE_WORD_3A",
"TLS_AES_128_GCM_SHA256",
"TLS_AES_256_GCM_SHA384",
"TLS_CHACHA20_POLY1305_SHA256",
"TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
"TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
"TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
"TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
"TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256",
"TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256",
"TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA",
"TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA",
"TLS_RSA_WITH_AES_128_GCM_SHA256",
"TLS_RSA_WITH_AES_256_GCM_SHA384",
"TLS_RSA_WITH_AES_128_CBC_SHA",
"TLS_RSA_WITH_AES_256_CBC_SHA",
"TLS_RSA_WITH_3DES_EDE_CBC_SHA"
],
"ephemeral_keys_supported": true,
"session_ticket_supported": true,
"tls_compression_supported": false,
"unknown_cipher_suite_supported": false,
"beast_vuln": false,
"able_to_detect_n_minus_one_splitting": false,
"insecure_cipher_suites": {},
"tls_version": "TLS 1.3",
"rating": "Probably Okay"
}```

response in python venv

print(requests.get('https://www.howsmyssl.com/a/check').json())
{u'unknown_cipher_suite_supported': False, u'able_to_detect_n_minus_one_splitting': True, u'rating': u'Bad', u'tls_compression_supported': False, u'tls_version': u'TLS 1.0', u'insecure_cipher_suites': {}, u'session_ticket_supported': True, u'given_cipher_suites': [u'TLS_DHE_RSA_WITH_AES_256_CBC_SHA', u'TLS_DHE_DSS_WITH_AES_256_CBC_SHA', u'TLS_DHE_RSA_WITH_AES_128_CBC_SHA', u'TLS_DHE_DSS_WITH_AES_128_CBC_SHA', u'TLS_RSA_WITH_AES_256_CBC_SHA', u'TLS_RSA_WITH_AES_128_CBC_SHA', u'TLS_EMPTY_RENEGOTIATION_INFO_SCSV'], u'ephemeral_keys_supported': True, u'beast_vuln': False}

Are you by any chance using the system installed version of Python on a Mac? And which Python version are you using - and from where did you install it from? Can you run:
python -c "import ssl; print ssl.OPENSSL_VERSION"

to check the version of openssl?
Older versions of openssl do not support TLS1.2. Something which has been problematic on some installs.

I am using venv and created Python 2.7.
the result of command is
import ssl; print ssl.OPENSSL_VERSION

This version of openssl does not support TLS1.2. Which explains why you end up with TLS 1.1.
Are you looking for a way for the client to fail unless it supports TLS 1.2 (refuse downgrade of the version) or to make your client actually support TLS 1.2?
Some background: http://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-v12.html

@johanste sorry I got confused, I am talking about the TLSv setting in auzre keyvault sdk for python. I dont see any special param to set the ssl/tls version in auzre keyvault sdk.
also the azure portal for keyvault don’t provide the option for me to set the minimal TLS version which don’t like other PaaS.

The azure-keyvault package for Python is using [requests](https://2.python-requests.org/en/master/) under the hood, It, in turn, will use openssl. Depending on which version of and how you installed Python, it will end up calling into different versions of openssl.
I don't have an answer as to what the service does (or does not) support w. regards to disabling TLS <=1.1. I've pinged some people internally who can hopefully provide more information.

@johanste got it, so how to set tls version in azure-keyvault package for Python?

As I mentioned above, by default, it will be negotiated to use the best (latest) possible version supported by both the client and the service. So if you update your Python installation so that it uses a later version of openssl, it will start using TLS 1.2.
If you want to set the lowest version that your client application is willing to use, it is a bit more trickery involved. The current version of the keyvault libraries don't have an explicit knob/parameter to do so. You'd have to create a requests.adapters.HTTPAdapter and configure your pool manager, but I don't see a good way to get access to the requests.Session() instance that you'd need to mount it to...
Incidentally, we just released a preview of the (next generation of client libraries for Python)[https://aka.ms/azure-sdk-preview1-python], which would allow you to specify a specific requests.Session() when you create your client, and thus would allow you to provide a specific requests.Session() instance...

@johanste After install latest requests, its still using TLSv1.

You need to make sure that the openssl version is 1.0.1 or higher (actually, you probably want it even later than that). Installing requests will not update the openssl version.
This post on stackoverflow has some information on how to update openssl on various platforms.

Thanks a lot, I can get tlsv1.2 now

Closing as the issue has been resolved..

Thanks a lot, I can get tlsv1.2 now

Hi which tool you are using to capture this.

Thanks a lot, I can get tlsv1.2 now

Hi which tool you are using to capture this.

Thanks a lot, I can get tlsv1.2 now

Hi which tool you are uisng to capture this.

Thanks a lot, I can get tlsv1.2 now

Hi which tool you are uisng to capture this.


🚧 API: TextEncoderStream

Context
Specification: Encoding
Specification interface: TextDecoderStream
Additional documentation:

mdn docs
deno docs
Cloudflare workers docs
Boa documentation

Dependencies:

#91
ReadableStream TODO
WritableStream TODO

Expected TypeScript interface

/** @category Encoding API */
declare interface TextEncoderStream {
  /** Returns "utf-8". */
  readonly encoding: "utf-8";
  readonly readable: ReadableStream<Uint8Array>;
  readonly writable: WritableStream<string>;
  readonly [Symbol.toStringTag]: string;
}

/** @category Encoding API */
declare var TextEncoderStream: {
  readonly prototype: TextEncoderStream;
  new (): TextEncoderStream;
};

@johnyob, TextEncoderStream got priority medium, but a dependency to WritableStreamwhich got a priority low.
We should probably review the priority of WritableStream ? If yes please remove the label Invalid, comment this issue and change the priority in excel.


Compile failed when executing "npm run deploy:twilio-cli"

Describe the bug
I execute the commands according to guidebook.
But when it begins to deploy, it got the following err message.
➜  twilio-video-app-react git:(master) npm run deploy:twilio-cli

><EMAIL_ADDRESS>deploy:twilio-cli
> cross-env REACT_APP_SET_AUTH=passcode npm run build && twilio rtc:apps:video:deploy --authentication=passcode --app-directory ./build

><EMAIL_ADDRESS>build
> node ./scripts/build.js

Creating an optimized production build...
Failed to compile.

TS2786: 'Container' cannot be used as a JSX component.
  Its element type 'ReactElement<any, any> | Component<Pick<DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>, "children" | ... 252 more ... | keyof ClassAttributes<...>> & StyledComponentProps<...> & { ...; }, any, any> | null' is not a valid JSX element.
    37 |
    38 |   return (
  > 39 |     <Container style={{ height }}>
       |      ^^^^^^^^^
    40 |       {roomState === 'disconnected' ? (
    41 |         <PreJoinScreens />
    42 |       ) : (

To Reproduce
Steps to reproduce the behavior:
Follow steps in the guide book. And when it comes to execute "npm run deploy:twilio-cli". It does not work.
Environment (please complete the following information):

OS: [Mac Intel bigSur 11.6]
Node.js version: [v16.10.0]

Hi @JoshuaSunsheng ,
Sorry for the delayed response. Is there a way I can access your source? I want to try the build myself.

Hi @JoshuaSunsheng ,
Sorry for the delayed response. Is there a way I can access your source? I want to try the build myself.

I do not change the code. I do as the guidebook. My teammates all compile failed.
The steps I did is as followed:
(1) check my local version
node --version     ->      v18.12.1
npm --version      ->      9.1.2
(2) git clone https://github.com/twilio/twilio-video-app-react.git
(3) npm install
(4) npm install -g twilio-cli
(5) twilio login
(6) twilio plugins:install @twilio-labs/plugin-rtc
(7) npm run deploy:twilio-cli
I compiled failed at the last step. I show the error as I mention in the page.

Hi @JoshuaSunsheng,
I've tried to reproduce it on my end, but I can't reproduce the error. Please confirm you are using the latest version of the plugins with the following command:
 twilio plugins:update
Could you please try with the latest version of the React App?

https://github.com/twilio/twilio-video-app-react/releases/tag/v0.8.0

Have a look at the versions that I used to reproduce it:
node -v  --> v18.2.1
npm -v  --> 9.1.2
twilio -v  --> twilio-cli/5.2.2 darwin-x64 node-v16.18.0
twilio plugins  -->  @twilio-labs/plugin-rtc 0.8.4
Please share with us your findings.

Hi @mcarrerasm,
Can you provide package.json and package-lock.json files to me after you compile it? I want to compare them with my local complied version.
I think the problem come from the React and its related plugin's version since the error is all about the syntax of typescript.

Hi @JoshuaSunsheng we are going to close this due to inactivity, but please let us know if you are still having issues and we will reopen it.


Add configuration options

Hi,
1st of all, thanks for this driver :-)
While making it work (and comparing it to the C Adafriut driver for Arduino platforms), I noticed that a few configuration capabilities were missing or not explicit.
This PR adds them, one per commit.
However, an initial commit applies rustfmt because in my environment it happens automatically and I did not want to disable it.
I understand that ideally this should stay in a separated PR but being in a separated commit the code review is doable anyway :-)
If you are really opposed to using rustfmt (and always complying to its style) I can rewrite the PR without it.
Thanks!

Note: I tested this on a bare metal cortex-m (and RP2040 board).
Everything works as expected.

Thanks for the PR!
I am not sure how to handle this PR to be honest. I will not be able to work on this driver before the end of November, when I have completed my thesis. On the other hand, the version on crates.io will stay unchanged.
Can you understand my hesitation to merge into master, without being able to test myself?

Of course, do not worry!
I can always reference my fork from my cargo builds :-)


[Bug] Go generated structs contain url annotations for every field

Describe the bug
The go model and SDK generators create structs for fern types. Each field in these structs contains a url annotation. These annotations are used for type safe URL param parsing in go. As far as I know, this is only useful server-side, so the SDK structs should not contain these annotations at all. These annotations are only useful in request types and so should not be in every model struct. Instead, they should be only in named request types.
To reproduce
Generate any fern type, e.g.,
types:
  User:
    properties:
      id: string
      name: string
      email: string

this results in the struct:
type User struct {
	Id    string `json:"id" url:"id"`
	Name  string `json:"name" url:"name"`
	Email string `json:"email" url:"email"`

	_rawJSON json.RawMessage
}

Expected behavior
I would expect the following struct
type User struct {
	Id    string `json:"id"`
	Name  string `json:"name"`
	Email string `json:"email"`

	_rawJSON json.RawMessage
}

The struct GetBar for the following API endpoint should have the url annotations, however
service:
  base-path: /foo
  endpoints:
    get:
      method: GET
      path: /bar
      request:
        name: GetBar
        query-parameters:
          baz:
            type: string

Version
Go generator 0.16.0

As far as I know, this is only useful server-side, so the SDK structs should not contain these annotations at all.

This is actually the annotation that we use to serialize query parameters sent from the SDK. This approach is inspired by Google's go-querystring, but our approach includes a few minor differences and improvements for types specific to Fern.

These annotations are only useful in request types and so should not be in every model struct.

Now that we support deepObject query parameters (link), it's important that we include url tags in every object contained in the transitive closure from every request type. For example, using your example above, we actually support specifying the User as a query parameter.

Instead, they should be only in named request types.

This is actually something we debated when rolling out the feature to begin with. Including them everywhere upfront will actually enable us to someday roll out a new RequestOption that allows us to add arbitrary query parameters to individual endpoints (where the query parameter is not already defined on the API). We haven't needed this feature yet, but it's been discussed a bit here and there so I know it might be on the horizon.
With all that said, we made the decision to include them everywhere knowing that we could later change the behavior to include them in a stricter subset (like you're suggesting), but I'm still not convinced that we should do that in general (especially with that new upcoming feature in mind).

@amckinney closing as not planned and up to re-open this if you want to track:

change the behavior to include them in a stricter subset


"Error happened with AutoTx" with no further information

Got this error back to back. The ID in the DB is a9363a8d-99a9-4091-93e3-3cf4e3c6c586, it shows as "running" but no error has been added to the table entry.

The error that happened is due to: https://github.com/polywrap/discord-bots/issues/49
And it was logged in the discord supabase.
Not sure why the task kept running on AutoTx service. It seems like the docker container restarted.


wording at https://atlas-test.fly.dev/

Instead of
"This is not the Scaife reading environment" we might want to say "This is an experimental step towards one component of Perseus 6."

Happy to tweak that wording. I want to err on the side of not making people think this is the actual front-end reading environment, though.


Warning pop up on selecting template - SAP Mobile Cards

Hello,
Scenario URL: https://developers.sap.com/tutorials/cp-mobile-cards-automatic-instance-generation.html
Similar issue:
https://github.com/SAPDocuments/Tutorials/issues/5964
Step 2:Provide the required information:
HTML template -> Gives warning message when selecting template
Warning   pop up comes, need to say OK to continue, then it gets selected.
Thanks,
Shubham
Labels to be added:
Sprint Label: SCPTest-2010A
Scenario Label:SCPTest-mcard
Landscape Labels: trial1, trial2, trial3
prio: high-prio

Hi @i353590
Thank you for raising the issue.
@shahchetali can you please look into the issue?

Hi @i353590 ,
Can you please attach a screenshot for the warning? We cannot see any warning, however, a confirmation box do appear.
Thanks,
Chetali Shah

Hi Chetali,
i meant that confirmation box only which comes after we select HTML template, which is not mentioned as part of tutorial.
I think it would be better to have it.
Thanks,
Shubham

I am closing this issue because it relates to the functionality of the product and not the tutorial.
@shahchetali Please consider sending this feedback to development, and consider any note that would help the user with this functionality.

Hi @thecodester , @i353590  ,
We will be deleting this tutorial soon as the Automatic Instance generation template no longer exist. Also, we will be removing the feature to create mobile cards from the cockpit in future, so this issue will be no longer relevant then.
Thanks & Regards,
Chetali


ConfigFactory Not Found

Hi, the Hystrix Configuration Readme said can use hystrix.ConfigFactory to config the opene/closer, but I did not find ConfigFactory in this repo. Is this readme out of date?

Nice catch!  It's at https://github.com/cep21/circuit/blob/700836dc9a95756136ce20df20ae5d3f3d8b59fd/v3/closers/hystrix/config.go and is called Factory not ConfigFactory.  I'll update the docs


WIP: [CI] fix unity build

Currently CI fails during tflite build with the next issue:

[2023-03-02T07:44:01.761Z] /opt/tflite/_deps/cpuinfo-build/libcpuinfo.a(api.c.o): In function cpuinfo_log_fatal.constprop.0': [2023-03-02T07:44:01.761Z] api.c:(.text+0xa3): undefined reference to clog_vlog_fatal'
[2023-03-02T07:44:01.761Z] /opt/tflite/_deps/cpuinfo-build/libcpuinfo.a(init.c.o): In function cpuinfo_log_error': [2023-03-02T07:44:01.761Z] init.c:(.text+0x9f): undefined reference to clog_vlog_error'
[2023-03-02T07:44:01.761Z] /opt/tflite/_deps/cpuinfo-build/libcpuinfo.a(processors.c.o): In function cpuinfo_log_error': [2023-03-02T07:44:01.761Z] processors.c:(.text+0x10f): undefined reference to clog_vlog_error'
[2023-03-02T07:44:01.761Z] /opt/tflite/_deps/cpuinfo-build/libcpuinfo.a(smallfile.c.o): In function cpuinfo_log_error.constprop.0': [2023-03-02T07:44:01.761Z] smallfile.c:(.text+0xa3): undefined reference to clog_vlog_error'
[2023-03-02T07:44:01.761Z] /usr/bin/ld: libtvm_runtime.so: internal symbol `clog_vlog_fatal' isn't defined
[2023-03-02T07:44:01.761Z] /usr/bin/ld: final link failed: Bad value
[2023-03-02T07:44:01.761Z] collect2: error: ld returned 1 exit status

Fix was done based on similar issue for Caffe2

@jwfromm could you see and merged this PR as intermediate fix of CI pipeline?


[DOCS] animation: missing instructions to add styles to global stylesheet

Description
The animation styles require the user to add the main stylesheet to their global styles but we are not instructing them to do so.

Ohh. I feel like I may have wrote this wrong. I can't quite remember now. Maybe it's an issue inside corgi?

I don't think it is, but we'll keep it open in case you remember. our Corgi templates removed all global stylsheets, and installing the component library overwrites that anyway

I did a fresh install of a project and everything is fine. I am not sure what spurred this but will close for now.


fix case "AutoHotKey" -> "AutoHotkey"

Glad it's mentioned here, but the name is joined from Auto and Hotkey, not three words.

Thanks for the fix!


Feature Request: Ability to specify different prompts/weights/params for different objects or areas of the image

Describe the feature you'd like to see:
edit: Since the title got adjusted, here's the original suggestion I had in the title itself:

Move parameters to the composition node itself, add button to create additional prompts, each prompt with a weight parameter, and also checkbox to inpaint alpha/mask

Something I've been wanting to try was to have multiple simultaneous AI passes, each masked to different objects on the scene and with their own prompts, with objects that will rotate during animation (or have the camera move around them) having multiple prompts specifying from which angle it's visible with the weights for those prompts controlled by drivers that calculate values based on the rotation of the objects relative to the camera; and then finally combine all of those together in a final AI pass.
ps: Lemme know if you need me to break it down into separate suggestions for each part
Additional information
No response

Wow, that's a very cool idea. I think that's probably beyond the scope of what I'll be able to do, but I would love collaboration for this. It would be pretty incredible to be able to have different prompts for different objects/areas of the screen.

can you just enable multiple AI render nodes at the same time ? that would be helpful to make compositions, also the ultimate workflow would be to configure the prompt and everything in the AI render Node so we can have different prompts per render layer or per scene, we can figure out things to mask out the result
thanks for the add-on!

Yeah, that's a cool idea. Right now the AI Render node doesn't work like that, but it could potentially be configured like that. I'll give that some consideration for the future!

can you just enable multiple AI render nodes at the same time ? that would be helpful to make compositions, also the ultimate workflow would be to configure the prompt and everything in the AI render Node so we can have different prompts per render layer or per scene, we can figure out things to mask out the result
thanks for the add-on!

https://www.youtube.com/watch?v=TYrHBFQPMys
There is probably an extension for everything! Very cool.
Not sure if a blender addon could solve everything automatic1111 does without a ton of work.

Good call on that Automatic1111 extension. If they add some kind of API access, then it would actually be possible to do something like vertex painting or textures in Blender that could hook into multidiffusion. Which would be very cool.


Fix register mapping for Neuropixels 2.0 public probes

Neuropixels 2.0 has a completely different register map compared to 2.0-beta. This is reflected in the changes in this commit.
Common static helper functions for 1.0, 2.0, and 2.0-beta were moved to BitHelper.cs and NeuropixelV2.cs

Its hard to know with 100 percent certainty, due the lack of proper Neuropixels documentation in general and unavailability of their API (even though its supposed to be open source given the terms of IMECs contract) that everything is functional but course tests with Jakob reveal that we are definitely shifting electrode positions etc.

Side note: I changed the SR check reporting level from raising an exception to printing to the Error stream. The reason is because on multishank probes the users should be able to use a probe even if one shank is broken.

I think this is totally reasonable and appropriate, especially given the current state of the integration, we can update this once we get certainty.

Yeah to be honest there are a lot of systematic issues I would like to go over that relate to shared state between devices that use passthrough and the way that gain corrections are handled here, which I think is pretty bad: declare as nullable double, use if sn detected and cast to double just feels gross.

I'll have time to debug this some more next week. I dont think I'm seeing any SR check errors but I have not verified that the channel map is behaving as expected.

@jvoigts When you use the library with np2.0 probes, please let me know so I can verify the SR programming is working for the whole probe


Missing word in expressroute-routing.md

The word "to" was missing in the sentence

Identical routes must be advertised from either sides across multiple circuit pairs belonging to you.

Also added period to end of bullet-point sentence.

@csundlof : Thanks for your contribution! The author, @ganesr, has been notified to review your proposed change.

Verified editorial correction.


amending image location in Osmand2 section in line with #306

Amending image location in line with #306
This pull request now relates to several files & associated images. I've viewed all locally using jekyll serve & I'm happy that all links will work and only redundant images have been removed.

@althio It's probably best if I just go ahead & merge these commits and the following ones - I'm simplifying the image filing system, removing duplicates and removing the redundant images that I find. Before I submit the pull request on any of them, or do the commit, I run the updated site on my machine using jekyll & check that the image links all work. Sometimes I'm sorting out slight problems as I find them - images in some sections of the beginner section in French are now fixed & I'll fix other problems if I find them.
With the number of changes, at some point I may well make a mistake, but I'm taking care to minimise the risk of this.
Although we normally check each others work, I think it will be nearly impossible for you to check every single change I make to links and duplicates.
Let me know if you would prefer to check my changes, otherwise I will just get on and merge them unless I am making some change that could be controversial.

@Nick-Tallguy

images in some sections of the beginner section in French are now fixed & I'll fix other problems if I find them.

Thanks for that!

With the number of changes, at some point I may well make a mistake, but I'm taking care to minimise the risk of this.
Although we normally check each others work, I think it will be nearly impossible for you to check every single change I make to links and duplicates.
Let me know if you would prefer to check my changes, otherwise I will just get on and merge them unless I am making some change that could be controversial.

By all means, go ahead and merge on your own if you are confident with your experience and local test.


Failed to initialize SPIFFS (ESP_ERR_INVALID_STATE) (IDFGH-6329)

Development Kit:  ESP32S2
Module or chip used:  Custom
Operating System:  Ubuntu
Using an IDE: Visual Studio Code
Power Supply: USB
Problem Description
Unable to upload spiffs in a custom Serial interface.
Ends up with error: Failed to initialize SPIFFS (ESP_ERR_INVALID_STATE)
Expected Behavior
Able to upload spiffs
Actual Behavior
Error: Failed to initialize SPIFFS (ESP_ERR_INVALID_STATE)
Code to reproduce this issue
esp_vfs_spiffs_conf_t conf = {
      .base_path = "/data",
      .partition_label = "data",
      .max_files = 5,
      .format_if_mount_failed = true,
  };

  esp_err_t ret = esp_vfs_spiffs_register(&conf);
  if (ret != ESP_OK)
  {
    if (ret == ESP_FAIL)
    {
      ESP_LOGE(TAG, "Failed to mount or format filesystem");
    }
    else if (ret == ESP_ERR_NOT_FOUND)
    {
      ESP_LOGE(TAG, "Failed to find SPIFFS partition");
    }
    else
    {
      ESP_LOGE(TAG, "Failed to initialize SPIFFS (%s)", esp_err_to_name(ret));
    }
    return;
  }
  size_t total = 0, used = 0;
  ret = esp_spiffs_info(conf.partition_label, &total, &used);
  if (ret != ESP_OK)
  {
    ESP_LOGE(TAG, "Failed to get SPIFFS partition information (%s)", esp_err_to_name(ret));
  }
  else
  {
    ESP_LOGI(TAG, "Partition size: total: %d, used: %d", total, used);
  }

  if (l_Addr == 0x1E800)
  {
    FILE *f1 = NULL;
    f1 = fopen("/data/mem.bin", "w");
    ESP_LOGI(TAG, "file opened to append");
    if (f1 != NULL)
    {
      fwrite(ringBuf_begin(pCmd->data) + 9, l_Len, 256, f1);
      ESP_LOGI(TAG, "firmware appended to flash");
    }
    fclose(f1);
    ESP_LOGI(TAG, "file appended and closed");
    esp_vfs_spiffs_unregister(conf.partition_label);
  }

Debug Logs
I (21) boot: ESP-IDF v4.4-dev-3401-gb86fe0c66c-dirty 2nd stage bootloader
I (21) boot: compile time 11:26:14
I (22) boot: chip revision: 0
I (26) boot.esp32s2: SPI Speed      : 80MHz
I (31) boot.esp32s2: SPI Mode       : DIO
I (36) boot.esp32s2: SPI Flash Size : 4MB
I (40) boot: Enabling RNG early entropy source...
I (46) boot: Partition Table:
I (49) boot: ## Label            Usage          Type ST Offset   Length
I (57) boot:  0 nvs              WiFi data        01 02 00009000 00004000
I (64) boot:  1 otadata          OTA data         01 00 0000d000 00002000
I (72) boot:  2 phy_init         RF data          01 01 0000f000 00001000
I (79) boot:  3 factory          factory app      00 00 00010000 00080000
I (86) boot:  4 ota_0            OTA app          00 10 000d0000 00080000
I (94) boot:  5 ota_1            OTA app          00 11 00190000 00080000
I (101) boot:  6 data             Unknown data     01 fe 00250000 00080000
I (109) boot:  7 hwinfo           WiFi data        01 02 002d0000 00003000
I (117) boot: End of partition table
I (121) boot: Defaulting to factory image
I (125) esp_image: segment 0: paddr=00010020 vaddr=3f000020 size=0bb34h ( 47924) map
I (144) esp_image: segment 1: paddr=0001bb5c vaddr=3ffbf870 size=01da4h (  7588) load
I (146) esp_image: segment 2: paddr=0001d908 vaddr=40022000 size=02710h ( 10000) load
I (153) esp_image: segment 3: paddr=00020020 vaddr=40080020 size=25cb8h (154808) map
I (190) esp_image: segment 4: paddr=00045ce0 vaddr=40024710 size=0b154h ( 45396) load
I (202) esp_image: segment 5: paddr=00050e3c vaddr=50000000 size=00010h (    16) load
I (208) boot: Loaded app from partition at offset 0x10000
I (209) boot: Disabling RNG early entropy source...
I (222) cach3�~���~�Սѥ���cache  : size 8KB, 4Ways, cache line size 32Byte
I (222) cpu_start: Pro cpu up.
I (234) cpu_start: Pro cpu start user code
I (234) cpu_start: cpu freq: 160000000
I (234) cpu_start: Application information:
I (238) cpu_start: Project name:     esp32s2-c
I (243) cpu_start: App version:      1
I (248) cpu_start: Compile time:     Dec  1 2021 11:26:09
I (254) cpu_start: ELF file SHA256:  89846084c0da4df3...
I (260) cpu_start: ESP-IDF:          v4.4-dev-3401-gb86fe0c66c-dirty
I (267) heap_init: Initializing. RAM available for dynamic allocation:
I (274) heap_init: At 3FF9E000 len 00002000 (8 KiB): RTCRAM
I (280) heap_init: At 3FFC58F8 len 00036708 (217 KiB): DRAM
I (287) heap_init: At 3FFFC000 len 00003A10 (14 KiB): DRAM
I (293) spi_flash: detected chip: generic
I (298) spi_flash: flash io: dio
I (302) cpu_start: Starting scheduler on PRO CPU.

FW and data:
os.system("~/esp/esp-idf/components/nvs_flash/nvs_partition_generator/nvs_partition_gen.py generate factory.csv factory.bin 12288")
os.system("esptool.py write_flash 0x2d0000 factory.bin")

Hi @enthusisastSR ,
I am not sure to understand, you say you cannot upload your spiffs partition to your board but the debug log shows the line:
I (101) boot:  6 data             Unknown data     01 fe 00250000 00080000

which is the partition you are trying to open from your code.
I also noticed that you are flashing factory.bin to the address 0x2d0000, but the partition table shows that this address corresponds to hwinfo partition:
I (109) boot:  7 hwinfo           WiFi data        01 02 002d0000 00003000

Is factory.bin the data partition you are trying to open in your code? What about /data partition? Where does it come from? If it's your spiffs data partition, then in the log, we can see that /data partition is of type phy (0x1) instead of nvs (0x2).
So can you please show us your factory.csv file and your partition CSV file (the one that contains your project partitions)?

Thank you @o-marshmallow. I have it working now. The problem was it was already initialized in my repository. So since I was trying to initialize it again I was running into this error. /data is custom partition type.

@enthusisastSR Great, thanks for coming back with the solution!


Inquiring about training codes

Thanks for the excellent work! could you please release the training code when you are available?

Hey @xuanxu92, thanks for your interest in our project.
Our training code is based on PIA. We re-implement the attention operation of Motion Module and use the following attention mask during temporal attention.
def make_tril_block_mask(video_length: int, patch_size: int, device):
    """
    tensor([[[1., 1., 0., 0.],
             [1., 1., 0., 0.],
             [1., 1., 1., 0.],
             [1., 1., 1., 1.]]])
    """
    tmp_mask = torch.zeros(video_length, video_length)

    # warmup steps
    for idx in range(patch_size):
        tmp_mask[idx, :patch_size] = 1
    # tril blocks
    for idx in range(patch_size, video_length):
        tmp_mask[idx, :idx + 1] = 1

    tmp_mask = tmp_mask.type(torch.bool)
    mask = torch.zeros_like(tmp_mask, dtype=torch.float)
    mask.masked_fill_(tmp_mask.logical_not(), float('-inf'))
    return mask.to(device)

Hey @xuanxu92, thanks for your interest in our project.
Our training code is based on PIA. We re-implement the attention operation of Motion Module and use the following attention mask during temporal attention.
def make_tril_block_mask(video_length: int, patch_size: int, device):
    """
    tensor([[[1., 1., 0., 0.],
             [1., 1., 0., 0.],
             [1., 1., 1., 0.],
             [1., 1., 1., 1.]]])
    """
    tmp_mask = torch.zeros(video_length, video_length)

    # warmup steps
    for idx in range(patch_size):
        tmp_mask[idx, :patch_size] = 1
    # tril blocks
    for idx in range(patch_size, video_length):
        tmp_mask[idx, :idx + 1] = 1

    tmp_mask = tmp_mask.type(torch.bool)
    mask = torch.zeros_like(tmp_mask, dtype=torch.float)
    mask.masked_fill_(tmp_mask.logical_not(), float('-inf'))
    return mask.to(device)

Hey, Thank you for your tips. Besides, I  just want to try live2diff with uni-directional attention and wonder what will happen. During inference, l add uni-directional attention mask to the first 8 frames and output them without other code changes. But there is a lot of noise in the result. Could you please help me figure out what causes this?
    def _memory_efficient_attention_pt20(self, query, key, value, attention_mask):
        query = query.contiguous()
        key = key.contiguous()
        value = value.contiguous()

        video_length = query.shape[2]
        tmp_mask = torch.zeros(video_length, video_length)
        # tril blocks
        for idx in range(0, video_length):
            tmp_mask[idx, :idx + 1] = 1

        tmp_mask = tmp_mask.type(torch.bool)
        mask = torch.zeros_like(tmp_mask, dtype=torch.float)
        mask.masked_fill_(tmp_mask.logical_not(), float('-inf'))
        mask = mask.to(query.device)

        hidden_states = torch.nn.functional.scaled_dot_product_attention(
            query, key, value, attn_mask=mask, dropout_p=0, is_causal=False
        )
        hidden_states = self.reshape_batch_dim_to_heads(hidden_states)
        return hidden_states

output result:
https://github.com/user-attachments/assets/7a662b50-ba4a-42a4-8432-d3a803c0d484


Update plugin.py

Added workflow to check for updates and create PRs automatically: https://github.com/sublimelsp/LSP-terraform/pull/29


Rehydration Error for NODE_IMAGE resolver

Hi,
I'm using Next JS and decided to add an image resolver for my wrapper for the Next Image.
However, I am getting rehydration errors even without using that component for the resolver.
render(blok.content,
                    {
                            nodeResolvers: {
                                [NODE_IMAGE]: (children, props) =>
Image Placeholder

                    },

If I remove the NODE_IMAGE node resolver, not React rehydration error.
Any ideas?
Cheers,
Gav

Hmm weird. Can you post the error log here?

I've just found the problem.
This is the image in the Storyblok Rich Text editor.

In my test for the image handler, I wrapped it in a .
[NODE_IMAGE]: (children, props) =>
Image Placeholder

Looking at one of the errors in the log, it says this:

If I look at the HTML source, I can see that the Storyblok editor has placed the img inside the paragraph, and so testing with a p creates a nested p ;-)

Replacing p with span in my test works without the rehydration error! :-D
[NODE_IMAGE]: (children, props) => Image Placeholder
So, my quick little test turned into a head-scratcher!

Ah yeah that once happened to me as well :) Glad you figured it out!

Having this problem as well, but not with a nested p element. I want to show the image in a figure element, so that I can add a figcaption, but they are always wrapped in p elements. I'm getting the following error:
Warning: validateDOMNesting(...):
 cannot appear as a descendant of
.

The issue seems to be that images are always wrapped in a paragraph, any way to circumvent this?

Hi Rene,
Thanks for letting me know and thanks for reaching out.
I’ll be sure to try the feature soon, but unable to do so at the moment.
Thanks,
Gav
From: René Lems @.>
Date: Wednesday, 30 November 2022 at 15:18
To: claus/storyblok-rich-text-react-renderer @.>
Cc: Gav Grayston (GOWTK) @.>, State change @.>
Subject: Re: [claus/storyblok-rich-text-react-renderer] Rehydration Error for NODE_IMAGE resolver (Issue #25)
Having this problem as well, but not with a nested p element. I want to show the image in a figure element, so that I can add a figcaption, but they are always wrapped in p elements. I'm getting the following error:
Warning: validateDOMNesting(...):  cannot appear as a descendant of .
The issue seems to be that images are always wrapped in a paragraph, any way to circumvent this?
—
Reply to this email directly, view it on GitHubhttps://github.com/claus/storyblok-rich-text-react-renderer/issues/25#issuecomment-1332332982, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS3KTXZ3UCIWHOGRKFT5BATWK5V23ANCNFSM6AAAAAARNV6UKU.
You are receiving this because you modified the open/close state.Message ID: @.***>

Has there been any developments or workarounds for this? We are also wanting to render images inside a figure element with a corresponding figcaption but as figure is block-level, it cannot be nested within a paragraph element.


Station similarities

Stations have sometimes similar availability profiles:

Questions?

How to create AI-defined profiles?

Why?

Station profile and location comparison might result interesting insight?
Map of residential / workplace areas?

Usage profiles might indicate problem points in bus / tram network?

More examples, now from Töölö (previous are near Esplanadi):

Stations 75, 76, 78, 80 are very similar but 81 has a different profile although it's located in the same neighborhoor.


Update 01.1_Docker-Workflow.md

Why:
This pull request addresses half of #11
What has changed:
the mattdavis0351/actions/docker-gpr action has been update to throw an error in the event that the package name has been used in a different repository.
Overview of the actual error:

blob upload invalid: Package "tic-tac-toe" is already associated with another repository.

Output from the updated action

blob upload invalid: Package "tic-tac-toe" is already associated with another repository.
##[error]Review the logs above, most likely you are using a package name associated with a different repository.  Rename your Image to fix.

The status of the action is also set to Failed if this error is thrown.
What has not changed:
The action has not been updated to check if the user has enough free space to store their image with GitHub Packages.  This may be implemented in a future update to the action itself, but may also be easier to handle at the Learning Lab level by providing some sort of feedback based on the stdout of the check_run.
We should think this through as a team!
This is a longer term issue for us as we develop content moving forward.  We need to figure out how we can address these things without relying on the creator/maintainer of the actions used to update them so that Learning Labs behave as expected.
This could be a use case for having out own Learning Lab GitHub Actions repo, or it may be getting new Learning Lab Actions added to the bot so that it can better utilize the output of a given action.
It may also include content creators providing that error checking at the workflow level when developing courses around the GitHub Actions platform.

@brianamarie are you comfortable merging this in so we can start using the action that has error checking?
It seems like the bigger problem ends up in our OKR discussion, but this PR still addresses a needed piece.

@brianamarie are you comfortable merging this in so we can start using the action that has error checking?

@mattdavis0351 Yep, let's 🚢!


Add Dockerfile and make docker target

It is ready.
@vahidrezanezhad @michalbubula this adds a Dockerfile, so we can run eynollah in docker, podman or kubernetes. It does not change anything in the code and should be compatible with all branches, so merging should have no adverse effects. With the default base image, there won't be support for GPU though but that can be rectified later (we do have cuda-tf2 core base images that should enable that but since we cannot use GPU in our cluster right now, it's low prio for us atm)


'unzip' is not recognized as an internal or external command, operable program or batch file.

Can someone help me with issue?
when i am trying to run this block
fname = 'glove.6B.%dd.txt'%embedding_dim
import os
datadir_base = os.path.expanduser(os.path.join('~', '.keras'))
if not os.access(datadir_base, os.W_OK):
datadir_base = os.path.join('/tmp', '.keras')
datadir = os.path.join(datadir_base, 'datasets')
glove_name = os.path.join(datadir, fname)
if not os.path.exists(glove_name):
path = 'glove.6B.zip'
path = get_file(path, origin="http://nlp.stanford.edu/data/glove.6B.zip")
!unzip {datadir}/{path}
i am getting this error
'unzip' is not recognized as an internal or external command,
operable program or batch file.

I am facing the same issue.
If you have found the solution then please provide it to me


M3-5058: Show promo service type in billing summary

Description
Displays Applies to: <service_type> in the promo billing summary if the service type is not "all".
How to test

You will need to update your .env file to use dev services
Login to a dev test account that has a specific service type promo applied to it. The 4th dev test account currently has the service type linodes applied.
Click on Accounts
You should see a promotions box, under the expires line, there should be another line that says Applies to: <service_type

The ticket didn't specify this, but I think we should remove the bit of code that's only displaying a single promotion

@Jskobos we do display multiple promotions correctly (here)...  I think the example you're talking about is because the expiry is null, and we're filtering those out here.


Angular cli production build - Supplied parameters do not match any signature of call target (v1.3.1)

After the 1.3.1 update, I encounter the following error when performing production build:
ERROR .../node_modules/ng2-slimscroll/src/directives/slimscroll.directive.ngfactory.ts (44,35): Supplied parameters do not match any signature of call target.
Build command: ng build --prod --base-href ./

cannot reproduce with latest angular-cli.
checked with ng build --prod and ng build --prod --aot.
altought I pushed some changes, can you check with 1.3.2?

Checked with angular-cli 1.0.2 and ng2-slimscroll .1.3.2 and it's still an issue. From what I checked, the issue is related to the addition of @HostListener in commit [c1daef9](https://github.com/jkuri/ng2-slimscroll/commit/c1daef95e3e8cbed5aa7f720d30de2097ac675b5).
Manually removing the HostListener from the directive solves the problem.

@vladmarginean9 but it lost a resize bug fix if you remove that part

#46


Return roomID when "M_ROOM_IN_USE" error

When create a new room, return below error:
{
"errcode": "M_ROOM_IN_USE",
"error": "Room alias already taken"
}
I wish can return the roomID of exiting too, then I can use the exiting room directly.

Why can't you just try to join that alias?


[Breaking] error should not emit expected/actual diags

Unlike throws, where one can argue that the error thrown is an actual that should be compared to an expected error provided to throws, the error provided to error is not compared to anything. It should therefore not appear in an expected/actual pair, where downstream TAP reporters can pick it up and diff it against undefined—I can't think of a case where such output would be helpful.

Thanks!


Add capture action to @detectXSS operator

Proposed fix for #1482.
Do notice that the API for @detectXSS in libInjection is still in Alpha stage so there's some missing features when compared with @detectSQLi.
In this case, there's no "fingerprint" returned from libInjection API to be fed into a "capture" action to tell us exactly what triggered the match like it's done with libinjection_sqli
So this proposed "capture" action would fill TX.0 with the full analyzed parameter value (var->value) when libinjection_xss returns true.

Is this any different to using MATCHED_VAR?

In this context, no @fgsch. But I'm not sure if there's much more we can do as the "API" looks limited in this aspect as of now.
But there's a chance I'm missing something, so let's see what others have to say :)

Merged. Thanks!


Add docs for dir resource and datasource

Good spot @florisvdg! I've applied your suggestions.
With these changes applied, is this ready to go? I'm proposing to merge to master, so that we can immediately release to get these directory additions visible in the registry.


Add a method to expose http.Server.Shutdown to allow graceful shutdowns

What does this PR do?
expose the API server's http.Server.Shutdown function.
Why is it important?
Allow callers to gracefully shutdown the HTTP server.
Related issues

https://github.com/elastic/fleet-server/issues/2902

While this is not strictly required for me to complete the fleet-server issue, it's a pretty simple addition.

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: 899cc3be2fb692c231463dd178dc6b4b643f60f9

Failed CI Steps

:linux: Test Linux

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: 899cc3be2fb692c231463dd178dc6b4b643f60f9

Failed CI Steps

:linux: Test Linux

History

:broken_heart: Build #126 failed 899cc3be2fb692c231463dd178dc6b4b643f60f9

:green_heart: Build Succeeded

Buildkite Build
Commit: 37ad5ef820d62f86137455f711ee60691e581adb

History

:broken_heart: Build #128 failed 899cc3be2fb692c231463dd178dc6b4b643f60f9
:broken_heart: Build #126 failed 899cc3be2fb692c231463dd178dc6b4b643f60f9


⚠ ClamAV has degraded performance

In cae284f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 224 ms

Resolved: ClamAV performance has improved in e1e88db.


Fix fixture

Minor edit to fixture for consistency.

Reviewer: @kennyt

This is to make this fixture align with this fixture: https://github.com/dcos/dcos-ui/blob/master/tests/_fixtures/OpenIDAuthProviders/providers.json#L2, so you can navigate to the detail page


Upgrade Error Prone 2.19.1 -> 2.20.0

Suggested commit message:
Upgrade Error Prone 2.19.1 -> 2.20.0 (#685)

Summary of key changes:
- The `MissingRefasterAnnotation` check was contributed to Error Prone,
  and so is deleted here (multiple checks with the same name are not
  supported).
- Similarly, Error Prone now supports the `-XepAllSuggestionsAsWarnings`
  flag out of the box. So the `ErrorProneFork` class is deleted, as it
  has currently no further use.

While there, include a tiny tweak to `run-mutation-tests.sh`.

Fixes #686.

See:
- https://github.com/google/error-prone/releases/tag/v2.20.0
- https://github.com/google/error-prone/compare/v2.19.1...v2.20.0
- https://github.com/PicnicSupermarket/error-prone/compare/v2.19.1-picnic-1...v2.20.0-picnic-1

@rickie due to the inclusion of MissingRefasterAnnotation in Error Prone 2.20.0 we have a conceptual repeat of #622: once again Error Prone Support is not compatible with the latest Error Prone release. So I think we should aim for a new release in the coming days. Edit: actual user impact reported @ #686.

The quality gate fails due to coverage on this change being below 80%, which is silly. Will make the gate less strict.

Warning
Renovate's suggested commit message is being replaced with improved initial commits to enable automerging. As a side effect, these suggested commit messages might have changed. Consider comparing the initial commit message and this message to determine the most suitable one. Please leave feedback in #sys-renovate.

Suggested commit message:
Upgrade Error Prone 2.19.1 -> 2.20.0

See:
- https://github.com/google/error-prone/releases/tag/v2.20.0
- https://github.com/google/error-prone/compare/v2.19.1...v2.20.0

^ Let's make sure to merge with the custom suggested commit message.

Rebased, will merge once :green_circle:.

Btw, slightly tweaked release notes as the words didn't add a lot of value IMHO :).


When can support Carthage

why not?

已经使用carthage集成了kingfisher,然后使用pods引入KingfisherWebP的时候，pods会重新引入一份kingfisher，请问有没有方法解决重复引入kingfisher的问题

Sorry for this terribly late reply 😂. From v1.0.0 KingfisherWebP can be used with Carthage now. See README.md for more details.


Getting Token

From what I can see this library is useless.  You get back an authorization code, but when you use that in another client / http request you always get back..
"error"=>"invalid_grant", "error_description"=>"The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client."
Also coinbase-ruby doesn't support getting a token either.... so I can get this working by using HTTParty all the way through an manually building my own OAUTH, whats the point of this library if you can't use it to get a token?

+1


Put this on packagist?

I was just about to wrote a library similar to this one as I couldn't find one. You mind putting this on packagist to make it both more easy to find and to access?

This was the plan. I built this tool for use on a project with my company and there has been some debate as to where the repo was going to be hosted so I was holding off.
I will be putting this up on Packagist soon.

After an embarrassingly long delay fixed.


CCH22-6: Adjust the snippets/dependencyManagement/customizingResolution-capabilitySubstitutionRule sample for configuration cache

The sample project located under subprojects/docs/src/snippets/dependencyManagement/customizingResolution-capabilitySubstitutionRule does not meet the configuration cache requirements.
The build scripts in the groovy and kotlin parts of the sample project need to be adjusted to follow the requirements.
Context
This issue is a part of the Gradle Configuration Cache Hackathon 2022.
If you wish to participate and contribute the fix, please follow the suggested workflow.
Expected behavior

The sample project is fixed so that the related documentation tests pass with configuration cache enabled.
The tests related to this sample project are removed from the testsToBeFixedForConfigurationCache list in subprojects/docs/build.gradle. You can find the test IDs below.
The doc pages that include the snippets from this sample project might need to be updated to be consistent with the sample. Feel free to ask the team for help with this! You can find the pages listed below.

Test failure details
These tests running in :docs:docsTest check the sample project and are failing with configuration cache enabled:

snippet-dependency-management-customizing-resolution-capability-substitution-rule_groovy_capability(Build Scan)
Could not get unknown property 'configurations' for task ':resolve' of type org.gradle.api.DefaultTask.

snippet-dependency-management-customizing-resolution-capability-substitution-rule_kotlin_capability(Build Scan)
Task `:resolve` of type `org.gradle.api.DefaultTask`: cannot serialize Gradle script object references as these are not supported with the configuration cache.

How to reproduce
To reproduce the failure in the Gradle documentation tests, run the following in the gradle/gradlerepository:
./gradlew :docs:docsTest \
    -PrunBrokenConfigurationCacheDocsTests=true \
    -PenableConfigurationCacheForDocsTests=true \
    --tests "*snippet-dependency-management-customizing-resolution-capability-substitution-rule_groovy_capability" \
    --tests "*snippet-dependency-management-customizing-resolution-capability-substitution-rule_kotlin_capability"

In the test build outputs, which you can find in the test report, the configuration cache problems are listed along with the URL pointing to the detailed HTML problems report that can help investigating the violation.
You can find more instructions on working with the sample projects in the FAQ.
Docs including the snippets from this sample project
The following doc pages include the snippets from this sample project:

subprojects/docs/src/docs/userguide/dep-man/03-controlling-transitive-dependencies/resolution_rules.adoc;

I would be happy to take this one.

Good luck, @cguerreros

@cguerreros  There was an issue with the test filters, I updated the description to specify them correctly (they were missing _substitution.sample at the end).

@abstratt Yes, I noticed yesterday but I figure it out :). Also, the link for the configuration cache requirements was not working. But now it seems fine. Thanks

PR for the fix -> https://github.com/gradle/gradle/pull/22039


"Mask" prop on TimePicker doesn't seem to do anything

Hi,
Thanks for all your hard work, love MUI, please keep it up.
The "mask" prop on TimePicker doesn't seem to enforce any formatting for input the way it does on DatePicker. Here's a codesandbox demonstrating the behavior. As you can see, you can only type numbers into the DatePicker, and they conform to the //____ mask. But you can type anything into the TimePicker.
https://codesandbox.io/s/basicdatepicker-material-demo-forked-dwm8x?file=/demo.js

Exactly like TimePicker, DateTimePicker also does not respect the "mask" value. Thank you for looking into this @adamfitzgibbon !

Any update on this?

+1; would love to ensure consistent behavior when grouped with the DatePicker and TimePicker components that do support this functionality.

I've been fighting with this for a while, and just found where it's explicitly disabled in the source: https://github.com/mui/material-ui-pickers/blob/e875729b3492a4aedebec9f14589accc83475241/lib/src/TimePicker/TimePicker.tsx#L50
You can use the prop disableMaskedInput={false} to override it, but the behavior is a little wonky which may be why it's not on by default.


Change exist child style  when enter a new child

for example
the first li left = 0;
then add another li;  the first is 20; the second is 0;
then add the third li; the first is 40; the second is 20; the third is 0;
how to do this
thx for your help！

I think that this question is outside the scope of velocity-react issues.


Stackblitz link is broken

Describe the Bug
stackblitz link is broken upon loading:

Generouted Version
workspace:*
Your Example Website or App or Reproduction
https://stackblitz.com/github/oedotme/generouted/tree/main/explorer?file=readme.md
Steps to Reproduce the Bug or Issue
open the link
Expected Behavior
show us newcomers the wonders of generouted
Screenshots or Videos
No response
Platform

OS: [e.g. macOS]
Browser: [e.g. Chrome]

Additional context
No response

Hey @MyTotoro, thanks for submitting this issue.
It should be working now, the explorer is now using an actual version of generouted instead of the workspace:* protocol.


⚠ ClamAV has degraded performance

In e958f8a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 48 ms

Resolved: ClamAV performance has improved in 977957b.


Release

I'd like to issue a release of dask/dask and dask/distributed at the end of the week.
In particular this should help to push out some Parquet fixes.

(note that parquet with pyarrow 0.13 is still broken in distributed)

I'm aware (just prodded on https://issues.apache.org/jira/browse/ARROW-5144).
I still think that we should push something out though.  The serialization
work is probably something that is better done in Arrow than Dask.
On Wed, Apr 10, 2019 at 10:12 AM Martin Durant<EMAIL_ADDRESS>wrote:

(note that parquet with pyarrow 0.13 is still broken in distributed)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4689#issuecomment-481732531, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszCOo8ircuYaYrnw5C9y_f4MBwcXYks5vff9RgaJpZM4cnbFk
.

Agreed, just wanted to note that things are not all well :)

Closing as 1.2.0 is live on PyPI and conda-forge. Thanks @mrocklin!

My pleasure
On Sat, Apr 13, 2019 at 4:47 PM James Bourbeau<EMAIL_ADDRESS>wrote:

Closing as 1.2.0 is live on PyPI and conda-forge. Thanks @mrocklin
https://github.com/mrocklin!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4689#issuecomment-482892635, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszOZj8fVRABzv6TKpIX01FW79N-SJks5vglBWgaJpZM4cnbFk
.


Recycle item not working

Hello
I see in my bot, recycle item not working
My config
� "type": "RecycleItems",
��������"config": {
����������"min_empty_space": 10,
����������"item_filter": {
������������"Pokeball":     { "keep" : 0 },
������������"Greatball":    { "keep" : 100 },
������������"Ultraball":    { "keep" : 130 },
������������"Max Revive":   { "keep" : 20 },
������������"Potion":�������{ "keep" : 0 },
������������"Super Potion": { "keep" : 0 },
������������"Hyper Potion": { "keep" : 10 },
������������"Revive":�������{ "keep" : 10 },
������������"Razz Berry":   { "keep" : 100 }
Ans when i look my bag pokemon
I have
50 pokeball
1 greatball
0 super ball
30 potion
....
Bref not working.
Have you got an idea ?
Thanks

Use the issue template or don't create an issue. It's working fine for me.

Config working
But not recycle items not numer what i enter

When you specify min_empty_space, it only recycles when space is less than specified number.
Close the issue.

@nikhil-pandey
how about if we config like this ?
{
"type": "RecycleItems",
"config": {
"min_empty_space": 15,
"item_filter": {
"Pokeball":       { "keep" : 100 },
"Greatball":      { "keep" : 50 },
"Ultraball":      { "keep" : 50 },
"Potion":         { "keep" : 5 },
"Super Potion":   { "keep" : 5 },
"Hyper Potion":   { "keep" : 5 },
"Max Potion":     { "keep" : 5 },
"Revive":         { "keep" : 5 },
"Razz Berry":     { "keep" : 50 }
}
}
},


Qatar is in the EU

Currently, echoip with a current GeoLite2-Country database considers Qatar to be a member of the EU.
Example IP: <IP_ADDRESS>
Current JSON response from a local instance with fully updated GeoLite2-Country:
{
    "ip": "<IP_ADDRESS>",
    "ip_decimal": 760449036,
    "country": "Qatar",
    "country_iso": "QA",
    "country_eu": true,
}

Qatar is not in the EU according to current GeoLite2-Country-CSV database. Verification with the GeoLite2-Country MMDB and Python code
import geoip2.database

with geoip2.database.Reader('/tmp/geoip/GeoLite2-Country.mmdb') as reader:
    response = reader.country('<IP_ADDRESS>');
    print(response.country.is_in_european_union)

$ python geoip.py
False

At this point I have to assume an error in echoip code.

Did a check on Demo MaxMind's GeoIP Databases - https://www.maxmind.com/en/geoip-demo


enable overriding envoy_bootstrap_tmpl.json location

envoy_bootstrap_tmpl.json is used to generate sidecar envoy configuration.
There should be a way to override path to envoy_bootstrap_tmpl.json(ie. way to provide custom template) - https://github.com/istio/istio/blob/master/pkg/bootstrap/bootstrap_config.go#L32
This is in favor to running envoy in non-kube plain VM.

Do you want to be able to override the template, or just provide custom config? I believe you can provide a custom boot strap config via the CustomConfigFile option. The comment implies it's only used in front of Mixer/Pilot, but looking at the code I don't think that's the case.
If you want to be able to control the full template (but still accept the same parameters as the original template) then we can take your PRs.

/cc @costinm who wrote the code initially

Just added a similar comment to the linked PR. --custom-config-file should work, it is already part of the proto.

I believe CustomConfigFile is meant to override the template completely. There should be a way for users to provide customized template in a not hardcoded path.
I think we should use this new parameter to replace the bootstrap template in mixer and pilot rather than replacing /var/lib/istio/envoy/envoy_bootstrap_tmpl.json during docker build.

customConfigFile allows to use a different template file that must exist already in the image.
How do we solve the problem of building with a different envoy bootstrap file?

Also, how do we customize for sidecars also?

@kidiyoor do you have a PR or has this been worked on?

We could use an environment variable in the Dockerfile, pointing to the template to be used when the image is built. There is currently a var ISTIO_BOOTSTRAP, but this allows overriding when the bootstrap file is already present in the container's filesystem.

not stale


[Snyk] Security upgrade nuxt from 2.13.3 to 3.12.4

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

package.json
yarn.lock

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Cross-site Scripting (XSS) SNYK-JS-NUXT-7640972
  648

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

👷 Deploy Preview for benevolent-blini-5169f6 processing.

Name
Link

🔨 Latest commit
6129bdbf44bd730aefcc26e5f5ed44c20bcfbf71

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-blini-5169f6/deploys/66b1e0dd906c420008140500


repo sync

This is an automated pull request to sync changes between the public and private repos.
:robot: This pull request should be merged (not squashed) to preserve continuity across repos, so please let a bot do the merging!

[image: 7580b7402263478b63909b10b2d55c50187fb81e]

On Wed, Jun 16, 2021 09:15 PM, "github-actions[bot]" <
@.***> wrote:

Thanks very much for contributing! Your pull request has been merged 🎉
You should see your changes appear on the site in approximately 24 hours.
If you're looking for your next contribution, check out our help wanted
issues
https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3A"help+wanted"
⚡
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/7432#issuecomment-862489740, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANZOOMABAY6J52M5ZVNTUV3TTDBINANCNFSM46ZW5BVA
.


Change remaining is-latest references to stable

/lgtm

/approve

Rebased to apply latest changes fixing e2e
/lgtm


Add a release system.

Add a release system:

build binaries and package releaser.sh
add a Makefile (much easier to use with Travis than scripts)
publish on GitHub .travis.yml

https://goreleaser.com/ works great


[TACHYON-335] Vagrant block device mapping for AWS

https://tachyon.atlassian.net/browse/TACHYON-335
This isn't a complete fix for this issue, but this will allow the user to make larger/more ebs volumes. Without specifying block device mappings, the disk provided will only be 10GB.

@rootfs

you found it :)
LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2901/
Test PASSed.