Add key while creating SourceRecord for structured data

In the current version, Source Records with structured output format are only being written to 1 partition of topic even though other partitions are available. This was severely constraining our consumers from parallel consumption of data. We have fixed this by adding the key as user screen name with schema type String. This has made no effect to the data being produced in structured format, but has led to even distribution of data across all partitions hence reducing processing time with multiple consumers in same group.

Thanks for the PR, and thanks for the heads up, I would have missed your PR otherwise.
I don't understand how everything ends up in a single partition. The original null key should result in a round-robin partitioning, something I just confirmed on my system with the example in the README. Are you using the avro converter?
I'll merge anyway, since it doesn't hurt, but I'm interested to hear how this didn't work for you initially :+1:

Hi @rollulus I am using the JsonConvertor and writing data to a topic with 4 partitions, but data only used to go to 1 partition before this change. Here is how I verified data across partitions.
./bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic twitter --partition 0 --from-beginning
I only got data for --partition 1

Ah, I think I understand now what's going on, it is a quirk of the JsonConverter explained here. We've only used the AvroConverter fortunately, which explains why we've never run into this issue. Thanks for your contribution!


Investigate removing the globals __extends() and __assign() populated by applicationinsights-shims

As part of removing tslib usage because of #1269, we created the applicationinsights-shims package, which to ensure that any modules that uses it also exposes the __extends() and __assign() onto the global scope (it reuses any existing instances).
We have had a request that at least for the ESM modules (further details will be provided) if we can not pollute the global scope with these functions.

Seems like a good time to rip off the band aid and bump to typescript 3. WDYT?

It's not that easy (as I already tried that before breaking the dependency), the issue is that we are targeting es3 and the "PropertyKey" added by tslib is not available when compiling for a es3 target.
I've not tried using v2 of tslib with TS 3.x yet though, but I expect the same issue (if not more) -- one of the reasons I called this "Investigate".
And we also need to make sure that the generated code / modules don't break older users with that sort of move :-(

I am using Angular universal along with this package, and __extends and __assign are both undefined for me.

@CraigComeOnThisNameCantBeTaken, can you please share the details of the "@microsoft/applicationinsights-web" version you are using in your code. We want to make sure "@microsoft/applicationinsights-shims": "^1.0.0" in your dependency list. Please refer  to suggestions from #1281.

Did you use the applicationinsights-shims or the tslib version?
I have found (using a different modules) that Webpack ProviderPlugin can silently fail (and not include the references) if the module can't be found for some reason, which results in the same errors.
When the packages are correctly referenced and available the ProviderPlugin does work.

Perhaps I'm naïve, but what browsers are you trying to support by targeting es3 instead of es5?

Primarily IE8, we have customers that still need to target IE8 and a couple in the health industry that still need IE7.

Could you have a separate build under lib-esm/ or similar that targets es5 and esnext modules, then specify the path as "module": in the package.json? This would be a backwards-compatible change that would allow apps targeting modern browsers to both optimize/tree-shake the package bundle themselves, and avoid the tslib workaround.

The problem with that is many fold, however, this work-around actually has nothing to do with ES3 and our support for IE8.
The issue is one of compilation, we can't compile with the currently targeted version of TypeScript (2.5.3) AND use version 1.13.0 (or later) of tslib -- as fails to compile. The workaround was to break the dependency so that we don't break other teams / customers by targeting the older versions of tslib.
In short, until we can successfully upgrade the version of typescript that we use (work in progress) without breaking other teams or customers we are limited to using this workaround... Unless of course if tslib publishes a fix.

@MSNev : installed the latest package but still having the issue
"@microsoft/applicationinsights-react-js": "^3.1.0",
"@microsoft/applicationinsights-web": "^2.6.2",

We have not yet published a react update that uses v2.0.0 of the shims (should be later today), if you check your dependencies you should find that v1.0.3 is currently still getting included.

PR to update the versions for release is out #1552

React v3.1.1 and ReactNative v2.3.1 are now published to NPM

I've deprecated the react v3.1.1 and react-native v2.3.1 packages until I can publish an updated versions #1553

v2.6.2 is now fully deployed

I'm updating #1553 on the React and ReactNative releases with the current state, please see comments there for additional info.


mountChildren Uncaught TypeError: Cannot read properties of null (reading 'length')

Vue version
3.4.5
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-dp5c9p?file=src%2FApp.vue
Steps to reproduce

  {show.value ?
show
 : <></>}

  <button onClick={(show.value = !show.value)}>toggle</button>

--> Uncaught TypeError: Cannot read properties of null (reading 'length')

  {show.value ?
show
 : <> </>}

  <button onClick={(show.value = !show.value)}>toggle</button>

--> it's ok
What is expected?
.
What is actually happening?
.
System Info
No response
Any additional comments?
No response

Rendering an empty Fragment isn't necessary here, just use null.
We can handle this case better, though.

glad to give some hands !
so you're trying to conditionally render html tag ..
you can achieve this using this mechanism also using v-html directive :
in the script section :
let htmlSect = show ? '
show
' : '';
in the template  section :
`

toggle

`

v-html is not a solution here. OP doesn't have a usage question, they reported a bug in our handling of Frament elements.

I'm Sorry , I didn't understand the context of the OP


Add Dynamic TLS Record Sizing for Tengine

Hi, this pull request is a patch for NGX SSL module which added dynamic TLS record sizing feature.
As we known, TLS working over TCP with record  protocol, it's divides the data being transmitted into records of a fixed (maximum: 16 KB in Nginx ) size and then hands those records to TCP for transmission.  then TCP promptly divides those records up into segments which are then transmitted. In some case, record size can can touch off HoL.[1]
That is to say, we can reduce latency by tuning TLS record size. In a nutshell, static record size introduces an inherent tradeoff between latency and throughput – smaller records are good for latency, but hurt server throughput by adding bytes and CPU overhead. So,the scheme for dynamic record sizing in this patch is :

for echo connect start with records of size ssl_dyn_rec_size_lo  which can fit into one tcp segment (IPv4)
ssl_dyn_rec_size_lo = MTU(1500) - IP (40) - TCP (20) - TCP Options(40) - TLS Overhead(60-100)[2] ~= 1300
send 52 KB data with ssl_dyn_rec_size_lo
Incr record size to ssl_dyn_rec_size_hi which equal 3*ssl_dyn_rec_size_lo- Max TLS Overhead(100)[2] = 3800
then, send  152 KB data with ssl_dyn_rec_size_hi
After send 204 KB data, incr TLS record size to default ssl buffer size( 16 KB )
If the connection idles for longer than this time (in seconds) that the TLS record size is reduced to ssl_dyn_rec_size_lo

this patch's dynamic sizing logic like apache mod_h2 (https://github.com/icing/mod_h2/blob/master/mod_http2/h2_conn_io.c)
[1]http://chimera.labs.oreilly.com/books/1230000000545/ch04.html#TLS_RECORD_SIZE
[2]https://www.evernote.com/shard/s1/sh/a44a8ee5-d788-44c7-a3ad-6e505f99d592/00e0b141eef44288f338332085044e6a

 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 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.


Is this library deprecated with  Xamarin.Essentials/preferences ?

If this is the case, it seems that usage is totally changed. now preferences uses akavache style while settings plugin was simply assigning values like below. thats why I prefer to use settings library for simple types while akavache for object types.

Settings.LoginAccessToken = token;

I found preferences library similar to securestorage and akavache. i just wanted to share my opinion.  Not sure maybe i should create this issue in xamarin essentials? please feel free to move there or close it :)

Preferences in Xamarin.Essentials is a drop in replacement for the Settings Plugin...
Take the code above^
public static string LoginAccessToken
{
    get =>  AppSettings.GetValueOrDefault(SettingsKey, SettingsDefault);
    set => AppSettings.AddOrUpdateValue(SettingsKey, value);
}

With Xamarin.Essentials it is literally:
public static string LoginAccessToken
{
    get =>  Preferences.Get(SettingsKey, SettingsDefault);
    set => Preferences.Set(SettingsKey, value);
}

They even store them in the same location by default so you can easily replace them.
See my guide: https://montemagno.com/upgrading-from-plugins-to-xamarin-essentials/


Session ID

How can I get session id from instance? It's possible?

What do you mean by Session ID?

I talking about audio session id from player. To use with visualizers.
For example: https://pub.dev/packages/flutter_visualizers

Ok, I'll take a look at it and release the feature as soon as I can.

Okk! Thanks :)


Static field ctor not invoked as intended

Because static constructors are invoked automatically upon referencing them, resetting static fields and invoking the static ctor is not going to work assuming that static ctors can't be called the second time automatically.
I need to think of a solution for this.
OR assuming static ctors can be invoked how many times as I need them to be automatically, then I can just not call static ctor manually again which is the best outcome.

As it seems like you can't reset the static constructors to its default state
An idea

In the patcher, patch the static constructors of all types

This patch will track where it has been invoked from
Now using harmony, dynamically patch that location to flag or do something that makes it invoke the static constructor on soft restart

Tasks

[ ] Add a trace call to make a stack trace on all static constructors in the patcher

I've done the implementation where I simply invoke the static ctor in order it was invoked. This seems to fix things as well as get a free performance boost


vitest fails to recognize webpack module federation components because of which the tests fail

Describe the bug
vitest fails to recognize webpack module federation components from remote applications because of which the tests fail
I am currently using vitest (0.33.0) in my application for testing the code. When I tried to upgrade to the latest version (2.0.5) , I encountered the below problem. I am not able to find a good way to fix this and proceed so creating this report.

Any help to resolve the issue appreciated. Thanks!
Reproduction
This is a very simple & minimal reproduction for the issue I am facing -
https://github.com/sumeetgodse/testing-microfes-1
Clone the repo
app1

cd app1
npm install
npm start

Tests for app1 (tests for apps that do not import any module federation components PASS)

npm test

container

cd container
npm install
npm start

Tests for container (FAILS)

Any help appreciated, Thanks!
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
    Memory: 5.26 GB / 15.44 GB
  Binaries:
    Node: 18.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.3.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.10.0 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    vitest: ^2.0.5 => 2.0.5

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Vitest doesn't know what app1 is. To fix this, you can add aliases to your vitest.config, for example:
import { defineConfig } from 'vitest/config'
import { fileURLToPath } from 'node:url'

export default defineConfig({
  resolve: {
    alias: [
      { find: /^app1/, replacement: fileURLToPath(new URL('../app1/src/components', import.meta.url)) }
    ],
  },
})


Fail generation in the emitter if doc is missing/empty

All Tier-1 language DPG generators will fail generation if a doc tag is missing or empty, rather than generating documentation to fill in the gaps. And this would should be implemented in emitter side.
https://github.com/Azure/autorest.csharp/issues/2621

Is it "@doc" or "@summary"?
What's the target? Model? Operation?
Also this likely break lots of tests in cadl-ranch.

@weidongxu-microsoft it is all of those.  @doc should be provided for client, operations, operation parameters and return types, models, model properties, enums, enum elements, and possibly others - anywhere doc comments are needed in the API surface.

So that should at least include type

NamespaceType, for client
OperationType, for operation
EnumType, for enum; EnumMemberType, for enum value
ModelTypeProperty, for both class variable in model and request parameter in operation
ModelType but exclude intrinsic (also might exclude ModelType used as Response, as the Response class is from azure-core), for model/class

We might not want to do this too eagerly, as it might break basic emitter function, as cadl-azure-core might lack some required doc e.g. https://github.com/Azure/cadl-azure/blob/9dde245/packages/cadl-azure-core/lib/foundations.cadl#L126

Dependent on https://github.com/Azure/cadl-azure/issues/1748


Persistent crash on latest Windows 11 Pro Insider Preview build

Any attempt to open the app from either the Start menu or the Open button inside the Windows Store results in the following, even after uninstalling and reinstalling:
Access is denied. (Exception from HRESULT: 0x80070005)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at CharacterMap.Services.UserCollectionsService.<>c__DisplayClass10_0.<<LoadCollectionsAsync>b__0>d.MoveNext() + 0x2f8
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at CharacterMap.Services.UserCollectionsService.<LoadCollectionsAsync>d__10.MoveNext() + 0x14c
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at CharacterMap.ViewModels.MainViewModel.<LoadAsync>d__80.MoveNext() + 0x107

OS Version: 10.0.22567.100
OS Architecture: X64
App Version: 2<IP_ADDRESS>
App Culture: en-US

This lead me to believe there's perhaps something misbehaving on that Windows install, as all that happens at this point (as this is before it hits the iteration part of this method), is using the Windows Storage API's to create or open a folder, which has no reason to throw under normal circumstances - and if I can't create a file nothing is going to work. Especially strange is this happens after an uninstall as that folder would be deleted. I'm not sure how I can be any safer in this method without entirely disabling the Collections features if something happens. 🤔
I'll keep investigating it but I can't replicate anything like it on any of my devices (one of which is on the latest insider build). If you have the ability to do so, it would be really helpful if you could pull the code and tell me what line the code is failing on, otherwise I'm low on ideas, sorry! D;

@RogueScholar Any change I can follow up on this and ask if the  latest update from the Store still crashes for you?


logging: Make some cleanups, in config and in noisy logs.

This addresses #6674, and in particular fixes the headline issue there. There are still some noisy things in test output and likely in production that would be good to clean up.
This also does a couple of the cleanups I mentioned in chat on #backend the other day, but many other useful cleanups remain open.
/cc @hollywoodno

I merged 3 commits.  For the rest, I have a few concerns:

I'm not sure about including the logger name in every log line; I feel like our log lines are already about as long as they can reasonably be.  Maybe that should be in the debug option as well?
I'm not sure how to test the "Explain quirks" commit except in production.  I guess historically, we needed e.g. zulip.requests to be in the LOGGING config in order for that logger to not be suppressed, but now we don't, because we removed the config option that was doing the suppression?
I might do a round of adding comments to each block explaining its purpose while we have it all figured out.  Let me know if there's any you don't know what it's for and I can help.

I merged 8d7f961a67156c4b93065412020d3bb87fbeebc1, fixing missing test coverage caused by the changes I merged (this error was masked by the linter errors in a later commit; I guess I should have run the tests myself)

I'm not sure about including the logger name in every log line; I feel like our log lines are already about as long as they can reasonably be. Maybe that should be in the debug option as well?

Hmm. I kind of feel the same way on the "there was a request" lines, like
2017-09-13 13:18:21,035 INFO     <IP_ADDRESS>    GET     200  56ms (mem: 10ms/5) (db: 13ms/2q) /json/messages [stream]<EMAIL_ADDRESS>via website)

And the logger name doesn't really add anything there, because they're so routine.
But I think for a lot of the universe of less-frequent log messages, when I'm investigating something in production it's common to go and try to grep to find where the message is coming from; which isn't always easy, and even when it is easy, it's too much work to do for every type of message in a log I'm skimming.
I'll try tweaking it to omit this part, or maybe do a really short abbreviation like [zr], for the routine request logs.
We're also using a bunch of space on padding out "INFO" to 8 characters, the length of "CRITICAL". I may try shortening all those names to say 4 characters: DEBG, INFO, WARN, ERR, CRIT.

I merged 8d7f961, fixing missing test coverage caused by the changes I merged

Ah, that path was actually used! Just not by a test. :-) I'd considered cutting it, and didn't because I found where that exception could be raised outside of the call to the base class's authenticate.
Just pushed a commit here to fix that up, with a test.

I guess historically, we needed e.g. zulip.requests to be in the LOGGING config in order for that logger to not be suppressed, but now we don't, because we removed the config option that was doing the suppression?

Yeah, exactly. Hmm, I should add that point to the commit message.

I'm not sure how to test the "Explain quirks" commit except in production.

You can see on the run-dev.py console that these messages keep getting logged, which has been a useful form of testing for me in development. Because this is pretty config-dependent, it probably deserves some attention when first deploying in production too to confirm.

I posted one comment; otherwise this looks great.  Feel free to merge after addressing that and updating docs/logging.md to at least cover the log format change.

In terms of follow-ups, there's a few things that come to mind for me that we should be sure to track:

The development server logs these lines when the user_activity queue worker processes an event (which is all the time).  We should probably at least make it say zq, and arguably also suppress those logs entirely from the main log, since they're really spammy and of little interest.  For context, user_activity is a low-importance table that keeps track of things like "the last time and number of times that user X accessed endpoint Y", mostly for debugging, but it also controls whether the zephyr_mirror system reports that your mirror bot isn't running and something bankrupcty-related.

2017-09-28 21:29:20.471 INFO [] Received event: {'time':<PHONE_NUMBER>, 'client': 'website', 'user_profile_id': 153, 'status': 1}

We should improve create_logger and document it.

Oops, actually those logs are UserPresence.  I'll at least modify the log lines to not be terrible.

I merged 630ecf966904bd88d24da3091062d74c9acd4d4b to address the UserPresence log issue.

I just spotted a big spew of similar event messages in dev, like this one:
2017-09-29 01:28:06.623 INFO [] Received event: {'triggers': {'mentioned': False, 'private_message': True, 'stream_push_notify': False}, 'stream_name': None, 'user_profile_id': 2, 'message_id': 1, 'timestamp':<PHONE_NUMBER>.3143237}

Merged 2a832386d to downgrade those too.


Better structure for testing, also uses mocha

When Schemats was first started, we only had one end-to-end test on the OSM schema, as features are implemented, we got more fixtures and the test code unavoidably became cluttered.
This patch refactor tests into using mocha, and adopt a better directory structure.

Changes Unknown when pulling b6b7a95748cd8039555b2fd87b02207c813d3100 on better_test_structure into ** on master**.

Coverage remained the same at 100.0% when pulling b6b7a95748cd8039555b2fd87b02207c813d3100 on better_test_structure into 22715a88cf4f9e6630ebe6de95713a725afdd1d0 on master.


Versioning example year mismatch

There seems to be a mismatch between the version and explanation years in the versioning example.
What is there vs. what I'd expect:

2023.0.0.alpha – Pre-season alpha release before the 1st race round of the 2022 season.
2023.0.0.alpha – Pre-season alpha release before the 1st race round of the 2023 season.

Hi @TeFiLeDo thanks for reaching out.
I'm not sure what the problem is you are facing, could you maybe eloborate?

Hi @marceloverdijk. I'm not really facing any problem, however I believe that there is a mistake in the versioning section of the README.md file. It lists several examples of what a specific version number means. I think that there is a mismatch between the version numbers (2023) and the explanations (2022).
Example:

- **2023.0.0.alpha** – Pre-season alpha release before the 1st race round of the 2022 season.

- **2023.0.0.alpha** – Pre-season alpha release before the 1st race round of the 2023 season.

Ah I see, good catch 👍

Fixed and thanks again 👍


Support docker 1.11.1

Docker Cloud only supports version 1.11.1, so any engines running there cannot be cleaned by docker-clean due to Error response from daemon: client is newer than server (client API version: 1.24, server API version: 1.23).
I also propose the publication of the image created by this Dockerfile-1.11.1 under a docker-1.11.1 tag on Docker Hub.

Thanks for the contribution! About to merge your commit and some additions I made to help build and push these tags to Docker hub.  The docker tag now exists as well: https://hub.docker.com/r/zzrot/docker-clean/tags/


feat: Add basic Template for igHierarchicalGrid.

closes #7

Coverage decreased (-0.4%) to 31.753% when pulling 6e425f9bae8f8c36c0a3140ab808837b7ab3480d on IGanchev/Angular-Templates into 4d084c319a79d1f3fb9113515f675012bc5445bd on master.

Coverage increased (+0.1%) to 62.809% when pulling 3c8e14a0551370118ac37dce3da8ef5428576f17 on IGanchev/Angular-Templates into a0ae1494f8958a83cfa98fbdf4f175e90c2084a6 on master.

Changes Unknown when pulling bdf5a127288db243f1e16a16763821025e84dc54 on IGanchev/Angular-Templates into ** on master**.

Coverage increased (+0.1%) to 62.751% when pulling b538c5ba4420bc0dc7038450c12c65d797bbd9b0 on IGanchev/Angular-Templates into e44e633890e963e98c66d221bb2edc0a3ff1753b on master.


neo4j.exceptions.ServiceUnavailable: Failed to establish connection to IPv4Address(('<IP_ADDRESS>', 7687))

raise ServiceUnavailable("Failed to establish connection to {!r} (reason {})".format(resolved_address, error))\nneo4j.exceptions.ServiceUnavailable: Failed to establish connection to IPv4Address(('<IP_ADDRESS>', 7687)) (reason [Errno 111] Connection refused)","statusCode":430
when is use neo4j4.2.3 on tencent cloud function
use bolt drive  find Failed to establish connection to IPv4Address(('<IP_ADDRESS>', 7687)
when use <IP_ADDRESS>
Failed to establish connection to IPv4Address(('<IP_ADDRESS>', 7687)
why?
how to solve it? thank you!

Hi,
it looks like the driver cannot connect to the server. Please make sure, that you start the driver using the server's public IP address. <IP_ADDRESS> is definitely not correct. <IP_ADDRESS> will only work if the driver and the server are running on the same machine.
You can probably find the public IP address of your server somewhere in the tencent admin interface/console.

@anabapy, do yo still need assistance one this one?

Hi i'm not sure if similar but I'm trying to establish a connection on my local machine from a Jupyter notebook env using the Python driver.
Using version 4.2.1 and starting from default configuration settings.
Running:
uri = "bolt://localhost:7687"
driver = GraphDatabase.driver(uri, auth=(usr, psd))
It raises the error:
Failed to establish connection to IPv6Address(('::1', 7687, 0, 0)) (reason [Errno 99] Cannot assign requested address)
Following the instructions here: [https://neo4j.com/developer/kb/resolve-python-bolt-driver-error-connection/]
If I change localhost to <IP_ADDRESS> When I run:
uri = "bolt://<IP_ADDRESS>:7687"
driver = GraphDatabase.driver(uri, auth=(usr, psd))
It raises the following error:
ServiceUnavailable: Failed to establish connection to IPv4Address(('<IP_ADDRESS>', 7687)) (reason [Errno 111] Connection refused)
If I edit the following parameter in config:
dbms.connector.bolt.listen_address=<IP_ADDRESS>:7687
and rerun with localhost:
ServiceUnavailable: Failed to establish connection to IPv6Address(('::1', 7687, 0, 0)) (reason [Errno 99] Cannot assign requested address)
If you have any suggestions how to connect it would be much appreciated. Let me know if I've missed out some useful information for you.

Ok, so I will close this now. If the problem persists, feel free to re-open it, @anabapy
@LordLean, did it have anything to do with how you used the driver? If so, I'd be interested in hearing what the issue was. Just in case someone else has a similar problem in the future.

No no, I was a fool and hadn't reconfigured my runtime to be working
locally, it was still running code in a cloud environment. So no wonder I
couldn't connect to my local machine!
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Thu, 22 Apr 2021 at 15:05, Robsdedude @.***> wrote:

Ok, so I will close this now. If the problem persists, feel free to
re-open it, @anabapy https://github.com/anabapy
@LordLean https://github.com/LordLean, did it have anything to do with
how you used the driver? If so, I'd be interested in hearing what the issue
was. Just in case someone else has a similar problem in the future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neo4j/neo4j-python-driver/issues/509#issuecomment-824872000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOI52XBDY2M4474GZQLOZA3TKAULJANCNFSM4YMCWZ7Q
.

At present, the problem found is that the cloud function has insufficient memory.

hey, I have the same problem, how do you reconfigure my runtime to be working
locally?

In the first image, I changed the line in the conf of neo4j to allow a server connection.
And in the second picture, there are still errors
Would appreciate help
Thanks

If you are running your application inside Docker, it will be in its own virtual LAN. Depending on how you start up your neo4j server, you'll have to make sure it's reachable from within the docker container running your application.
Does it work when you start up the application outside docker?
Docs that might help you: https://docs.docker.com/network/

I have the same issue and I don't know what is the problem

This is shot in the dark: you're running this Python notebook on a google server. So localhost will point to what ever server this notebook is running on. Is the database running on the same machine as the notebook?

what does that mean? it doesn't connect through the URL? why is the data relevant, why it has to run on the same machine as the notebook?

@ellahn3 your screenshot shows code with the address bolt://localhost:7867. For this code to work, Neo4j must on the same server as this code is running on.
Given it's probably NOT what you want to do, you should update the Neo4j address to the correct one in your code.

That depends on where your Neo4j sever is running. It like asking what the right address for a postcard is. That depends on where you want that postcard to be sent to. Or in this case how the Neo4j server is reachable.
I know this is probably not very helpful but there is no way to answer this question without know how ans where exactly you run the Python code and the database Server.

So I'm running my Python code on Google Colab, so using their Google cloud server. I have the Neo4j database stored on my computer, so my issue right now is how to find a way to connect these two.

That's a somewhat not so easy setup. For this to work, you'd need Google's server running Colab to be able to reach your computer. For security and other reasons, your computer is (most likely) not directly reachable from the internet like Google's servers are. Here are a few ideas that might help you find a solution:

Use Aura Free (our free cloud hosted database service; comes with some limitations).
Use a reverse proxy (like ngrok) to expose the database running on your local machine to the public internet (free options in that area also come with bandwidth or other limitations).
Host the database on a proper server that is configured to expose it's service(s) to the public internet.
Lastly, probably the easiest: run the Python code on your local machine. For that, you can for instance use jupyter notebooks or plain Python scripts.

There is also an easy solution using port forwarding with ngrok
ngrok tcp 7687 and local neo4j database can be used in online services like Google Colab, Datalore, etc

my docker-compose.yml
version: '3'
services:
  neo4j:
    image: neo4j
    environment:
      NEO4J_AUTH: 'neo4j/password'
    ports:
      - "7687:7687"

  backend:
    build:
      context: ./backend
      dockerfile: ./Dockerfile
    image: backend
    ports:
      - "5000:5000"
    depends_on:
      - neo4j

and my python code
url = os.getenv("NEO4J_URI", "bolt://<IP_ADDRESS>:7687")
username = os.getenv("NEO4J_USER", "neo4j")
password = os.getenv("NEO4J_PASSWORD", "password")
database = os.getenv("NEO4J_DATABASE", "neo4j")

driver = GraphDatabase.driver(url, auth=basic_auth(username, password),encrypted=False)

and my error
backend_1  | Failed to establish connection to ResolvedIPv4Address(('<IP_ADDRESS>', 7687)) (reason [Errno 111] Connection refused))

I don't why

  In the first image, I changed the line in the conf of neo4j to allow a server connection. And in the second picture, there are still errors Would appreciate help Thanks

I am having the exact same error. Any suggestions on the quick fix would be greatly appreciated!

Please see the suggestion in this thread, e.g., https://github.com/neo4j/neo4j-python-driver/issues/509#issuecomment-1102159801 and https://github.com/neo4j/neo4j-python-driver/issues/509#issuecomment-1263287676
If that doesn't get you anywhere, consider opening a question on stackoverflow, our community forums https://community.neo4j.com/ or such. This issues tracker is generally not the right place for support unless there's a bug or a suspected bug in the driver involved.


Update to support requirejs in the browser, no functional changes

This wraps the existing diacritic index.js in a UMD boilerplate from https://github.com/umdjs/umd . This allows people to utilize diacritics in the browser via requirejs. The merge diff likes a nightmare but that's because it increased the indent level by 1 due to the wrapper. I didn't change any of the code inside the wrapper if you delete the wrapper and undo the indent you'll see no changes. It will continue to function in Node as it did before.

Why is this required? I've been using this module in the browser for years without this boilerplate.

If you are using this in the browser you must be wrapping it or copy-pasting it into a different file. module.exports is not something which is available in browsers so I don't see how you could do a standard <script src="/node-diacritics/index.js"></script> and have it work properly?


Add San Antonio, Texas please

Please add San Antonio, Texas. Please include non-elected officials as needed, such as city planners etc

Unfortunately this request does not meet our base criteria so we will have to close it. Please submit a new request with the following information and we will process it:

A subject message for the email
A list of emails (at least one) for the government officials you’d like to receive the message
A detailed message concerning the budgeting decisions that are at stake in your community

See our current links for examples at https://defund12.org.
Thank you!


🐛 Replace references to ks-0.20 with main

Summary
This PR replaces references to branch ks-0.20 with references to branch main or relative references.
This is part of the merging of branch ks-0.20 into main.
Related issue(s)
Fixes #

/cc @pdettori
/cc @ezrasilvera

/lgtm
/approve


Selection no longer visible

Atom 0.206.0 knows that a selection is made, shown by the character count at the bottom of the window, however there's no visible highlighting - I tried a number of syntax themes - to show what is selected. I'm using Linux Mint 17.1 with Cinnamon, 32-bit.

If you have time and interest, could you try building #7127? There's a bug on that branch still but I'm curious if it restores your selections. I think it might.

I'll give it a shot this evening and let you know how it goes

Sorry, I gave it a look but I have no idea how to do that.

That's okay. Can you fall back to a previous release for a bit and I'll ping you on this issue when a new release is out with what I hope will be a fix? If it isn't then we can go deeper and figure it out.

ok thanks
On 06/05/2015 06:08 PM, Nathan Sobo wrote:

That's okay. Can you fall back to a previous release for a bit and
I'll ping you on this issue when a new release is out with what I hope
will be a fix? If it isn't then we can go deeper and figure it out.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/7131#issuecomment-109455502.

I was never able to find a previous release for my 32-bit linux mint. I was hopeful when I got notified of the 0.207 update this morning but no joy.

i have the same issue, selection highlight is invisible but otherwise still functional.
it doesnt work for several themes e.g. "spacegray light" but does work for "one light"
i'm wondering if its a theming issue, but i dont know what selectors i can try on my stylesheet to see if i can fix it.
help is much appreciated

YES! Thank you for replying here @stefan-kern! I use Xeta syntax theme
and with 0.206 I had switched around to about 13 different syntax themes
to see if one worked, none did. Now, with 0.207 still no highlighting
with Xeta but it works with One Light and One Dark and possibly others
so there's hope! This has been slowing me down for days, thanks again!
On 06/09/2015 04:57 AM, stefan-kern wrote:

i have the same issue, selection highlight is invisible but otherwise
still functional.
it doesnt work for several themes e.g. "spacegray light" but does work
for "one light"
i'm wondering if its a theming issue, but i dont know what selectors i
can try on my stylesheet to see if i can fix it.
help is much appreciated
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/7131#issuecomment-110281795.

if it helps: i'm using Ubuntu 14.04 with unity. atom v0.207

I've now gone through 20 different syntax themes, most of which work with 0.207 but didn't with 0.206. I'm going to close this issue now as it seems more an issue with the theme packages than the editor.


Visiting goroutine stacks by pprof can block all goroutines

What version of Go are you using (go version)?

$ go version
go version go1.13.4 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/rilke/Library/Caches/go-build"
GOENV="/Users/rilke/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/rilke/go"
GOPRIVATE=""
GOPROXY="https://goproxy.io,direct"
GOROOT="/usr/local/Cellar/go/1.13.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.13.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/jg/d03tz52x12g_xf_x7cmdtn840000gn/T/go-build179904585=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I run the code below, and open the url http://localhost:6060/debug/pprof/goroutine?debug=1 in my browser. But the page never show and the string "xx" stop printing, which means goroutine2 stop running.
package main

import (
	"fmt"
	"net/http"
	_ "net/http/pprof"
)

func main() {
        //goroutine1
	go func() {
		for {
		}
	}()
       //goroutine2
	go func() {
		for {
			fmt.Println("xx")
		}
	}()

	http.ListenAndServe("<IP_ADDRESS>:6060", nil)
}

What did you expect to see?
I expect the page http://localhost:6060/debug/pprof/goroutine?debug=1 to be loaded normally, and goroutine2 should not stop printing
What did you see instead?
The page http://localhost:6060/debug/pprof/goroutine?debug=1 never load and goroutine2 stop printing when I visit the url http://localhost:6060/debug/pprof/goroutine?debug=1 in my browser.

Seems like #10958 - for goroutine profile, runtime tries to stop the world.

Don't write busy loops in Go.
That said, this should work better in the upcoming Go 1.14 release.  Closing as dup of #10958.


check that iis version is valid format

I have had some issues where this fact failed on servers that don't have IIS installed on them.
So in case you use plugin sync in your environment this messes up the iis_version fact.
adding a check for a valid version solves this.

Closed in favor of #62 which should have fixed


test.yml: use image cache with parameters created from template

This should reduce the cache size used by the CI.

Some templates download not only images but also nerdctl, so using only the image digest for caching might result in nerdctl not being cached. However, I believe that reducing the cache size should be prioritized over this.
Looking at the current cache status, it appears that some caches contain empty directories due to trial and error during the work process. I believe this can be resolved either by deleting the caches or by having the caches recreated when the PR is merged.
cache keys that contains empty directory:
Linux-7782f8b4ff8cd378377eb79f8d61c9559b94bbd0c11d19eb380ee7bda19af04e
macOS-8f37f663956af5f743f0f99ab973729b6a02f200ebfac7a3a036eff296550732
Linux-1c3b2791d52735d916dc44767c745c2319eb7cae74af71bbf45ddb268f42fc1d

Updated to create image caches on a per-directory basis under by-url-sha256/{sha256sum of location}.

It seems the image.location used in hack/test-templates/test-misc.yaml returns 404.
- location: "https://cloud-images.ubuntu.com/releases/22.04/release-20220902/ubuntu-22.04-server-cloudimg-amd64.img"
  arch: "x86_64"
  digest: "sha256:c777670007cc5f132417b9e0bc01367ccfc2a989951ffa225bb1952917c3aa81"
- location: "https://cloud-images.ubuntu.com/releases/22.04/release-20220902/ubuntu-22.04-server-cloudimg-arm64.img"
  arch: "aarch64"
  digest: "sha256:9620f479bd5a6cbf1e805654d41b27f4fc56ef20f916c8331558241734de81ae"

https://github.com/lima-vm/lima/actions/runs/10086752926/job/27889808281?pr=2508#step:10:11

It seems the image.location used in hack/test-templates/test-misc.yaml returns 404.

I created https://github.com/lima-vm/lima/pull/2513 to checking remote image existence on ci.

Updated PR description: https://github.com/lima-vm/lima/pull/2508#issue-2426866220

fixed commit message(key: "digest-$digest" -> key: "image-$digest") and force pushed

FYI, the details of the cache currently used in this repository's CI can be seen here: https://github.com/lima-vm/lima/actions/caches.

The cache settings are not efficient, so we quickly exceed the limit and caches expire. This PR will minimize the cache for files downloaded during limactl execution. Separately, I plan to create a PR to improve the cache set by actions/setup-go.

Following shfmt issue does not happen with<EMAIL_ADDRESS>that I'm using on local.
https://github.com/lima-vm/lima/actions/runs/10415694648/job/28846620704?pr=2508#step:13:23
It looks lint job using older version<EMAIL_ADDRESS>Are there any reason to pinning shfmt at older version?

Are there any reason to pinning shfmt at older version?

No, it is just out of sync with the latest version

Thanks! 🙏🏻


Connect to browser wallet

Issue: https://github.com/edakturk14/fuel-dapp-template/issues/8

To do:

[x] Check on the local network
[x] Connect & Disconnect to the browser wallet
[x] Test on Localhost
[x] Test on Testnet
[x] Update Readme

[x] Browser wallet instructions
[x] Configure localnetwork on browser wallet
[x] Update built-in wallet instructions

Hey @carletex,
I've update the local node to be In-memory local node (without state persistance) It displays some wallets when you directly start the chain on the terminal. With these accounts I was able to make a tx after connecting from the Browser wallet.

Now we can connect to the contract on both localhost and the beta-3 testnet from the fuel browser wallet.
Looks ready to merge imo.


[Safari 11] Animated Elements have weird backgrounds

Ok so this happens only in Safari 11(haven't tried on older ones)
basically the title is self explanatory but here's the gif:

you get this weird backgrounds right until the animation finishes.. then they disappear, but you can still see some of it left behind the letters.
Any ideas?

any ideas? anyone?

Can you please post a URL? It'll be hard to help without anything live.

I can't cuz it's a commercial project and I can't replicate the bug with a minified example.
Here's some additional info:
Content scrolls inside the DIV(with overflow-y: hidden and X auto) so it's not scrolling the actual body element.
structure goes like this:

all of them have background colors... that's pretty much it...
The bug goes away if I assign a white background color to everything (note: not transparent but actual white)
I think it has something to do with Safari's new rendering engine.. when there are a lot of composite layers and some transforms happen.. it starts to flicker.. basically this is render flickering.

Yeah, seems like a nasty Safari bug. Try to set a transform like transform: translateZ(0) at some flickering elements and see if it helps

Tried that didn't help :/  Even tried disabling the backface visibility(cuz it obviously composites the parent divs bg colors) that didn't help either.. we are doomed.

Nasty bugs need nasty solution. Try some of these:

Use `will-change: transform, opacity (read about it here) on animating elements;
Add clip-path: polygon(0 0, 100% 0, 100% 100%, 0% 100%); to some flickering element. It'll have no visual impact but might fix it;
Try to set the colors in rgb or hsl instead of hex.

If will-change or clip-path work, try applying it only on as few elements as possible as you can have some performance problems.
To be honest, last time I had a similar problem with Safari it happened with one specific version only, I think it was 9.x. Any other version, 8- or 10+ had no problem. The only solution was to do some nasty UA sniffing and disabling the features only on this specific version.
Lately Safari has being so unpleasant to deal with... It's kinda sad.

This is nightmare :/ none of this work.. even tried custom indents for will-change... -_-

Try to see if it affects only some specific Safari versions. IF so, I think that using UA sniffing to disable the animations on Safari might be the solution.
If you need help on this, just give a heads up.

I'm closing this as there was no more response for about 1 month. Feel free to reopen it if there's some news on this issue.

Hey. I have the same issue. Does anyone found any solution for this? I've checked this problem on few different mac's and it occurs only on one of them... Safari version on all devices is the same. As foxnoodles said, it's a nightmare, none of solutions given here is not working.

Sadly I couldn't find a solution, just disabled it in Safari 11 (happens only there)


[Fix] invalid keybindings (Alt is 18, Ctrl is 17)

ref. https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode#non-printable_keys_function_keys

You might also want to consider changing ToolBindingKeyboardType type to extend modifierKey with other values. Right now if someone wants to use a different modifier than the 3 defined in KeyboardBindings it's not possible because of TS throwing an error (it has to be one of the enum values). You could use the broad TS definition
https://github.com/nfriend/ts-keycode-enum/blob/master/Key.enum.ts


feature fold weeks_sub/add on fe

Proposed changes
support folding weeks_sub/add on fe

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

run buildall


Columns with fixed widths ignore max-width when there's not enough to fill the row

As discussed on Slack :D
Example: Currently if you only have one column width a width of one-half, it will extend past 50% of the width of the row. It's a flexbox / margins issue.

Fixed with https://github.com/cferdinandi/kraken/releases/tag/v10.0.0


Styling issue with Trained Spotter radio buttons

Buttons appear to "wiggle" when clicked/toggled in Internet Explorer 9.  May need to see about setting a default border in the CSS?

Screen shot:

Same behavior with the Training Report buttons.

Can we disable the orange border altogether on the individual radio buttons?

I believe I have a fix. It will get rid of borders when the radio button is clicked. Waiting on the Windows VM to do its update thing which could take a while and then I'll test it out.

Fixed.


Visual Studio 2017 Build Instructions

While trying to setup server for development cannot find OpenSSL Library 1.0.2n to download from the given link http://slproweb.com/products/Win32OpenSSL.html

Unfortunately, the documentation is slightly out of date. Please use v1.0.2o. If you have continue to have issues, then try v1.1.0h.
Please leave this issue open even if this addresses your problem. We are going to use it to track updating the documentation.

ok.. i ran into another issue:
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\crypt32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\msasn1.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\ws2_32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\mswsock.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\netapi32.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\netutils.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\wkscli.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\srvcli.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Unloaded 'C:\Windows\System32\netutils.dll'
'rippled_classic.exe' (Win32): Unloaded 'C:\Windows\System32\wkscli.dll'
'rippled_classic.exe' (Win32): Unloaded 'C:\Windows\System32\srvcli.dll'
'rippled_classic.exe' (Win32): Unloaded 'C:\Windows\System32\netapi32.dll'
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\cryptsp.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\rsaenh.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\cryptbase.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\bcryptprimitives.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\NapiNSP.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\pnrpnsp.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\nlaapi.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\dnsapi.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\nsi.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\IPHLPAPI.DLL'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\winrnr.dll'. Cannot find or open the PDB file.
'rippled_classic.exe' (Win32): Loaded 'C:\Windows\System32\wshbth.dll'. Cannot find or open the PDB file.
Exception thrown at 0x00007FFC2A72F218 in rippled_classic.exe: Microsoft C++ exception: std::runtime_error at memory location 0x000000AECDF7D098.
Unhandled exception at 0x00007FFC2A72F218 in rippled_classic.exe: Microsoft C++ exception: std::runtime_error at memory location 0x000000AECDF7D098.
The program '[12648] rippled_classic.exe' has exited with code 0 (0x0).

Check what's set in [node_db] type in your config. RocksDB is not available in Windows. Use NuDB instead. See rippled-example.cfg for more details.

I don't think the rippled build process includes RocksDB in Windows. See this line in rippled-example.cfg. I also confirmed that by running rippled under the debugger.


Setuptools2

Restructures the directories and adds a setup.py for installation via pip.

Looks nice. Rather uninvasive.
I'm used to seeing a requirements.txt file in these packages. Any thoughts on that?
Here is somebody's opinion that seemed reasonable.

Does it make sense to harmonize with the main scitran infra? Whichever is most useful, setup vs requirements, I assume that we should use the same across the board.

I don't have a strong preference either way, so whichever we use elsewhere
is good with me.  What do we use elsewhere?
On Thu, Jul 16, 2015 at 10:45 AM, Nathaniel Kofalt<EMAIL_ADDRESS>
wrote:

Does it make sense to harmonize with the main scitran infra? Whichever is
most useful, setup vs requirements, I assume that we should use the same
across the board.
—
Reply to this email directly or view it on GitHub
https://github.com/scitran/reaper/pull/10#issuecomment-121997977.

The main scitran infra uses a requirements file.

I've switched to requirements.txt.  I'll cancel this PR and make a new one.


Upgrade to go 1.16

https://github.com/open-cluster-management/backlog/issues/11916
Signed-off-by: Dominique Vernier<EMAIL_ADDRESS>

/lgtm


SVG Support

[ ] nested svg tags parsing
[ ] viewbox parsing
[x] gradients
[ ] clipping
[x] defs
[x] text tspan
[x] opacity

We already have basic SVG support. Full spec support need to be handled by separate tickets.


Feature/simplified labeling

Description
Simplifies labeling code
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[x] Chore: cleanup/renaming, etc
[ ] RFC

Notes

Acceptance

[x] I have read the Contributing guidelines
[x] I have read the Code of Conduct

Just wanted to update that I just tried with #391 and still getting the same unexpected result

It's still not working. Let's not worry about this if it's complicated to make it work with this idiomatic change.
Uploading Screen Recording 2023-11-24 at 4.11.30 PM.mov…

https://github.com/watermelontools/watermelon/assets/8325094/64bf4915-7710-4938-89aa-c10d794a3052

Closing for now


Better Vector2

with this change, I don't thing Vector2.set_x is necessary any more

I have made a library with F32. Maybe you can use it?
https://git.envs.net/iacore/lean-primitives
It's encoded as u32 by Lean.

Thanks for the pr! Sorry for not replying sooner.
It seems that the example in Main.lean broke (Vector2.x and Vector2.y always return 0, idk why).
Perhaps it would be better to use fully Lean's definition of vectors (without extern attributes) and change the C code using it, instead of using an "external" object. This would require a lot of changes in ffi though.

I don't thing Vector2.set_x is necessary any more

Definitely.

I have made a library with F32. Maybe you can use it?

I think it is better to keep using Float because it is a built-in. There are already multiple cases in this library where int is translated as UInt32 for convenience (where appropriate, e.g. sizes).

It seems that the example in Main.lean broke (Vector2.x and Vector2.y always return 0, idk why).
It works for me. (I tried Repr.repr (Vector2.mk 0 0))

I think it is better to keep using Float because it is a built-in. There are already multiple cases in this library where int is translated as UInt32 for convenience (where appropriate, e.g. sizes).

Float is f64. Type conversion takes time. Lean's FFI is still experimental. Depends on how much time you want to put into developing this library.

It works for me.

Part of the generated code for Main:
x_40 = lean_raylib__GetMousePosition(x_39);
x_41 = lean_ctor_get(x_40, 0);
lean_inc(x_41);
x_42 = lean_ctor_get(x_40, 1);

I suspect that extern might not work with auto-generated constructors and getters.
The following code doesn't use lean_raylib__Vector2_... when translated:
let tea := Vector2.mk 1.0 2.0
IO.println $ repr tea

Type conversion takes time. Lean's FFI is still experimental.

As long as that's the case, I don't mind the performance penalty.

I've started moving pod definitions to Lean side so the pr is now obsolete.


command not found: gorila

I did the pip install gorilla-cli and the command is not found.  Installer is maybe not working?
~ $ python3 --version
Python 3.11.3

~ $ pip --version
pip 23.1.2

$ sw_vers
ProductName:		macOS
ProductVersion:		13.4.1

$ arch
arm64

Thanks for trying it out, @dnajd I think there is a misspell? It should be gorilla and not gorila (the extra l). Hope this fixes it.


[eject]: Cannot find module '@babel/plugin-transform-react-jsx-source' after ejecting

Describe the bug
After ejecting the CRA successfully, when I tried to start the dev server (yarn start) it threw an error.
Failed to compile.

./src/index.js
Error: [BABEL] /home/wasd/github/lol/src/index.js: Cannot find module '@babel/plugin-transform-react-jsx-source' (While processing: "/home/wasd/github/lol/node_modules/babel-preset-react-app/index.js$1")
    at Array.reduce (<anonymous>)

Did you try recovering your dependencies?

Yep, after removing the node_modules and reinstalling them fixes the issue.
Which terms did you search for in User Guide?

Not applicable
Environment

  System:
    OS: Linux 5.0 Ubuntu 19.04 (Disco Dingo)
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
  Binaries:
    Node: 10.12.0 - ~/.nvm/versions/node/v10.12.0/bin/node
    Yarn: 1.12.3 - /usr/bin/yarn
    npm: 6.10.0 - ~/.nvm/versions/node/v10.12.0/bin/npm
  Browsers:
    Chrome: 75.0.3770.100
    Firefox: 67.0.4
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-dom: ^16.8.6 => 16.8.6
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: 3.0.1

Steps to reproduce

create-react-app <PRJ_NAME>
cd PRJ_NAME
yarn eject
yarn start

Error
Failed to compile.

./src/index.js
Error: [BABEL] /home/wasd/github/lol/src/index.js: Cannot find module '@babel/plugin-transform-react-jsx-source' (While processing: "/home/wasd/github/lol/node_modules/babel-preset-react-app/index.js$1")
    at Array.reduce (<anonymous>)

Expected behavior

Should compile successfully. :+1:
Actual behavior

Compilation failed due to lack of module.
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Related to https://github.com/facebook/create-react-app/issues/6099

Duplicate of #6099


Refine release policy

Refines the existing guidelines and policy. Adds policy for long-term supported and weekly releases.
@bkmartinjr and @atolopko-czi please review for clarity and make suggestions

What is the purpose of the "release policy" doc? It combines:

I agree with these points and I think 2 documents could suffice: 1) engineering requirements (which may or may not be worth having in the repo, but seems fine if labeled as such), and 2) user-oriented doc explaining what we're committing to provide

user-oriented doc explaining what we're committing to provide

And on this point: I suggest we keep it as narrow as is usable/friendly/practical (from the end-user perspective), as anything else constrains our ability to evolve and progress the schema, implementation and API.

Thank you for all the comments understood the feedback and it makes sense -- too many goals combined in one doc. I will likely make this a user-facing document that has clear information to be used a data hosting requirements and I can sync up with @atolopko-czi  to look into operational policies and implementations

Addressed in new PR #314


Add support for Android Gradle Plugin 7.+. Upgrade dependencies and publishing mechanics

Github issue
Resolves #50
PR's key points
The PR adds a series of improvements over the plugin's code:

First and most importantly, it adds support for Android Gradle Plugin 7+. This means that backwards compatibility will be broken (hence the idea of bumping the version tag to 3.0.0).
A lot of dependencies have been updated as a consequence of upgrading the plugin. I also took some time to migrate the versions' declaration to Gradle Version Catalogs.
I also took some time to tweak the publishing code to add proper metadata to POM files. Nothing major, but I took advantage of having to migrate from the maven plugin to the maven-publish plugin due to the upgrade of the AGP version :P

Definition of Done

[x] Changes summary added to CHANGELOG.md
[x] Documentation added to README.md (if a new feature is added)
[x] Tests added (if new code is added)
[x] There is no outcommented or debug code left

Hi @orgeslayer!
Could you please test that this version of the plugin works with your setup? It should work now with Android Gradle Plugin 7+
implementation "com.github.hyperdevs-team:poeditor-android-gradle-plugin:bugfix~agp-7.1.0-SNAPSHOT"

Thanks!

It fixed the issue for me at least :D

It fixed the issue for me at least :D

Cool! I also tested it in my projects and it seems to work well, so I'll get it into the release branch so you can import a proper version ;)

Hi @orgeslayer!
Could you please test that this version of the plugin works with your setup? It should work now with Android Gradle Plugin 7+
implementation "com.github.hyperdevs-team:poeditor-android-gradle-plugin:bugfix~agp-7.1.0-SNAPSHOT"

Thanks!

I checked this comment now. I also check fixed version and it work corrected.
Thank you for responding quickly :)


Not clear how to publish to nuget.org

Apparently NuGetAuthenticate isn't necessary for nuget.org because it doesn't accept API key authentication. Publishing to nuget.org is an extremely common use case and should be covered explicitly in this article.

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

ID: 11ed58a1-5819-f3a4-c674-dafcdbd56fbc
Version Independent ID: d68aca4d-3fd3-1864-09f5-6060295e0399
Content: Publishing to NuGet feeds - Azure Pipelines and TFS
Content Source: docs/pipelines/artifacts/nuget.md
Product: devops
Technology: devops-cicd-artifacts
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

Open?

@ramiMSFT Can you take a look?
@ahelwer If you have the info that needs added to the doc, we accept contributors--if you open a PR to update the doc, we have team of reviewers standing by to review and accept your updates.

I don't have the info because I couldn't figure out how to make it work from the docs.

@ahelwer My apologizes for the delayed response and thank you for your feedback. A backlog item has been created and I will be updating the article shortly.

@ahelwer The new content is live: Publish packages to NuGet.org


Big GPU footprint while training

Describe the bug
Not really a bug per se, more of a question/clarification request. If there are better avenues to discuss (discord server?) these issues I apologize for using the wrong channel.
To Reproduce
Feel free to run this test:
https://github.com/openclimatefix/skillful_nowcasting/blob/main/tests/test_model.py#L305
The training takes about 40G on the GPU with a batch size of 1. Had to upgrade to a A100 to be able to run decently.
Just curious if this is expected behavior or if you recommend another approach.

No, this is a great place to talk about it! That test does use a lot of GPU memory, and I think that is just expected, the model is almost a 1 to 1 copy of the DeepMind psuedocode and training code they released, and they trained it on 16 TPUs. I would try to just run it with reduced parameters, or smaller input size. Unfortunately its just a large model. But that is why I skip that test in the CI actions.

Ok this is what I thought.
I might play around with multi-gpu or TPU training with XLA to see if I can crank the batch size up. I am also curious if switching to a 16-bit architecture could help. The input data is 16 bits anyways.
If you're interested I also have some code to feed the tfrecords from the original dataset into the DataLoader, happy to send a PR. I'm trying to reproduce the results from the paper.

Yeah, a PR would be great! I'm currently working on mirroring the dataset on HuggingFace to make it easier for anyone else to reproduce the paper, but for now that code requires TF.

Tf/sonnet implementation I have trains decently distributed across 8 tpu cores (v2) and matching paper params (except global batch size 8 per step, and one sample per input during gen. step). Assume DM trained theirs on the v3 cores.

Thanks for the insights!

Thanks for your questions. I have run this code with TeslaV100s(32G), unfortunately, it raises Cuda out of memory. Do you have some suggestions or configurations for training this model with GPU-RAM=32G? @johmathe @jacobbieker
Best regards.

Thanks for your quick reply. I will try to do it and hope your training script. @jacobbieker
Best regards.


actions: fix promise handling and remove setFilesEnabled

adds async/await in all controller network request to resolve
Promises and blocking form state while submitting
removes setFilesEnabled network call and replaces it with local
state mutation only to toggle the display of the files drop zone
closes #250

@zzacharo @fenekku can you please review this one carefully? My first PR :)
I have removed thesetFilesEnabled because in my opinion is not needed. Use cases:

metadata-only record: just save the draft/publish when needed, files will not be there, no need to set enabled: false in the metadata.
records with files: draft is created with enabled: true on the first file upload

If the point 1 is not correct, then I think we should change in the backend when saving/creating the draft.
I have tested the following scenario, edit + publish:

metadata only record
record with files
switch between metadata only and files

Let me know what you think! :)
P.S. I am using Prettier + reformat and imports reorganization on save. I strongly recommend if we all do so to have cleaner code and Pull Requests.

Thanks a lot @ntarocco for this PR. It is an extremely nasty problem and I am thankful you guys found some way through it.
This is a summary of actions/comments:
setFilesEnabled
First, we should separate the setFilesEnabled issue from this PR. I don't quite
understand the 1- and 2- points from your comment, but here is how the UX should be:
1- A user can save a draft without files, but will get a warning about it.
2- A user cannot publish a draft without files unless they have checked the Metadata-only box (default)
(there is a fringe case of configuring instance to allow metadata-only by default, but we can leave that alone)
The second point is a product decision.
This area has a lot of ramifications that should be discussed and there are
currently some bugs (notably: absence of attached files doesn't prevent publication on the API front inveniosoftware/invenio-rdm-records#498) but should. The real solution is, as you and I have remarked, to have a field part of the draft payload that specifies if this is a metadata-only record as opposed to a separate API call.
Action: deal with it in other PR when dealing with not needing a separate API call (if possible).
Formik, redux-thunk and Promises
This is the crux of the original bug. What was happening:
We were giving to Formik's onSubmit prop a function that returned a Promise
which was fulfilled, so Formik did setSubmitting(false) for us per
documentation.
This fulfilled promise was Promise{state="fulfilled", state=undefined}
because dispatch(save(record, formik)); of
export const submitFormData = (record, formik) => {
  return async (dispatch, getState, config) => {
    const formState = getState().deposit.formState;
    switch (formState) {
      case FORM_SAVING:
        dispatch(save(record, formik));  // HERE
        break;
      case FORM_PUBLISHING:
        dispatch(publish(record, formik));  // HERE
        break;
      default:
        console.log('onSubmit triggered some other way');
    }
  };
};

immediately returns the pending Promise we want... BUT it's not assigned
or returned (or awaited) in the anonymous async function. So the async function wraps the return value of
the function (undefined by default in JS) into a Promise and passes that back.
For any wrapped value that is not a Promise, async makes the Promise fulfilled. boom bug.
Action: This PR fixes it. Great! We should be able to remove setSubmitting(false) from https://github.com/inveniosoftware/react-invenio-deposit/blob/master/src/lib/DepositController.js#L165 .
Prettier
This is a can of worms.
Having a JS linter, like we have a pep8 linter for python is fine by me.
Anything else and the tradeoff is not worth it for me (see some examples below).
Action: let's shelve this :)

Thank you for the explanation :) very useful for reviewers!
About the async/await and setFilesEnabled, I decided to do everything here because the first was not fixing the bug I reported. There was no easy solution to fix the metadata-only record bug and this refactoring was required.

To summarize our discussion:

using return seems like something @zzacharo @ntarocco and @fenekku all agree on, so we can go with that.
we can let the toggleFilesEnabled in and deal with consequences in next PR
we agree on linting (like we already do in Python) and the goal of having clear human readable code

Action for @ntarocco :

fix the conflict
use return
merge this in

If you need anything, let me know.

@fenekku I have pushed with the discussed changes, if you want to give it a second look.
I will probably merge it tomorrow morning Geneva time :)


Adding an allow list configuration option

Overview
Adds an optional folder allowlist configuration.
Motivation
Introduce an 'allowlist' feature to enable users to specify project folders explicitly, ensuring that only projects within these folders are included in the build process. This provides greater control over project compilation and improves workspace performance by preventing the accidental compilation of unrelated projects.
Issue
With our monorepo structure, we are unable to use the extension because it attempts to spin up several hundred projects at once causing device OOM's and reboots. Adding an allowlist will help us to specifically target the projects we work on.
Checklist

[x] I have run this code and it appears to resolve the stated issue
[x] README.md updated and added information about my change

LGTM. @Ben-A-Canva, Can you please update the readme also?

LGTM @mdesmet the doc has been added. We can merge this.

LGTM, but please add docs as @anandgupta42 asked.

Added an entry to the readme file. Is there anything else I need to update for docs? 👀


[types] Adding constructor for account event

Motivation
In order to create event data for ContractEvent, we need to generate account event and serialize it. Adding a constructor for it.
Test Plan
cargo build

@bors-libra r+

:pushpin: Commit 7f27760 has been approved by sunmilee

:hourglass: Testing commit 7f27760e6a198b98f87cf130c4c9b62825862319 with merge fb525f9058c86dec0d92ae15e3f6a92110a4d1e2...

@bors-libra r=runtian-zhou

:pushpin: Commit 2a8a589 has been approved by runtian-zhou

:hourglass: Testing commit 2a8a589aa6ab8f840cf3a2dc21afb9d22a65696b with merge 5a1413e7046179a9d23760d8ad6214d5547b9867...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: runtian-zhou
Pushing 5a1413e7046179a9d23760d8ad6214d5547b9867 to master...


Improvements jan24

OSPF underlay (only v2 and 1 area):

Add OSPF support to L1 intent
Add OSPF support in L2 fabric role

improvements to srl-upgrade role:

distinguish upgrade from downgrade by looking at version numbers
reset facts after reboot (to clean discovered_interpreter_python fact, e.g. for upgrade to 23.10.1 that changed OS to Debian)

DCGW-pruning:

convert RPC_* role templates to produce {path, value, operation}-triplets
change RPC_* role task to merge triplets into facts based on operation
configure role purge-templates for SROS

Add support to configure port-speed on SRL interfaces:

Add L1 support for interface port-speed

DCGW integration:

Don't overwrite/update certain existing settings in the base router (router-id, autonomous-system, system-interface)
Add flag dcgw_unsafe_updates to do this anyway

Adding purge for BFD and ethernet-segments as switching between envs/itents cause causes config push issues (eg remove lag1 interface while still being referenced by an ethernet-segment. Same for BFD.


fix: fix type hinting for tasks.py

Corrected the type hinting for the race pos argument in tasks.py.

Thank you!


add "DSA in rust"  section

add a section for DSA, and add rust examples

can you tell me this issue in detail

I think he wants a pull request with the implemented feature. So for each issue, we should submit a pull request to help advance that particular solution.
In this case, I guess we can clone the repo, switch to a dev branch you create, add a page for DSA, create some structure for that page such as data structures section, algorithms section, examples for each, etc.

yes @shawazi m what we need here is just a new component with a list of links.
We will take care of filtering the content later

Add the "DSA in rust" section in the project.
For reference, check these files:
https://github.com/FrancescoXX/rustcrab/blob/main/src/components/DevToolsSection.tsx
This for the data (similar structure)
https://github.com/FrancescoXX/rustcrab/blob/main/src/data/tools.ts
and then insert this component into the page.tsk file (similar to what is here at line 39)
https://github.com/FrancescoXX/rustcrab/blob/main/src/app/page.tsx

Hi @FrancescoXX, I can work on this feature.
Thanks

Hi @FrancescoXX, solved that on PR on #69 . Thanks

solved that on PR #69


[BUG] WindowSummarizer error when used in recursive reducer

From stackoverflow here:
https://stackoverflow.com/questions/73325333/call-windowsummarizer-from-sktime-recursively-to-the-forecasting-target-y-in
original message on stackoverflow:

I need help on how to use the WindowSummarizer function from the SKTIME library recursively in the future.
Because in the training and test data it is easy to generate the variables of moving averages and moving standard deviations.
But for future predictions, the WindowSummarizer function has to work interactively, with each new predicted observation, WindowSummarizer must recalculate all variables and thus make the next prediction, recursively, until the end.
Can anyone help me?
Follow a reproducible example:
#!pip install sktime[all_extras]

import pandas as pd
import numpy as np
from sktime.transformations.series.summarize import WindowSummarizer
from sktime.forecasting.base import ForecastingHorizon
from sktime.forecasting.compose import ForecastingPipeline
from sklearn.linear_model import LinearRegression
from sktime.datasets import load_airline
from sktime.forecasting.model_selection import temporal_train_test_split
from sktime.forecasting.compose import make_reduction, TransformedTargetForecaster

y = load_airline()

kwargs = {
        "lag_feature": {
            "lag": [0,1],
            "mean": [[0, 7], [0, 14],[0, 28]],
            "std": [[0, 7], [0, 14],[0, 28]],
            "kurt": [[0, 7], [0, 14],[0, 28]],
            "skew": [[0, 7], [0, 14],[0, 28]]
        }
    }

forecaster = make_reduction(
    LinearRegression(),
    scitype="tabular-regressor",
    transformers=[WindowSummarizer(**kwargs, n_jobs=1,truncate = "bfill")],
    window_length=None,
    strategy="recursive"
)

pipe = ForecastingPipeline(
    steps=[
        ("forecaster", forecaster),
    ]
)

model = pipe.fit(y)

model.predict(fh = np.arange(1,100,1))

This code return the error message:
Input contains NaN, infinity or a value too large for dtype('float64').

FYI @danbartl

I wonder, would we expect this to not break?
For reduced regression, the WindowSummarizer would need to produce values far enough in the future (up to 100 periods) - but from the settings it looks like that it does not?

Hello guys.
I was trying to use WindowSummarizer() in the same style as recursive() command from modeltime library in R, like showed in this link:  https://business-science.github.io/modeltime/articles/recursive-forecasting.html

Hm, I might not fully understand the algorithm that you are trying to run here.
From a very naive inspection, your exogeneous lags are not compatible with the forecasting horizon values.
Could you explain?
Here's my understanding so far:
For recursive regression with exogeneous data (coming from the WindowSummarizer, do you not need exoeneous data (actual/observed, or lagged) being present at all the future indices that you want to forecast at?
E.g., if you try to forecast 100 periods ahead, would you not have to choose lags in the WindowSummarizer so you have summaries available for 100 periods ahead, which, say, for the mean, requires you to have X windows being observed between 73 and 100 periods ahead?

Hello guys

PS: we're not just guys.

Hi the issue here is that you use kurtosis and skewness over a window for which your forecasting model(linear regression) creates all constant values.
Kurtosis and skewness are not defined for constant values however if I am not mistaken, so pandas kurtosis and skewness function return NAs, which in turn are not handled by linear regression - leading to the error.
So either pass your own function definition for skewness and kurtosis that can handle those values, or choose a different forecasting model.

@danbartl are you saying that kurtosis and skewness need more than 7 values?

@fkiraly NO kurtosis and skewness are not defined for constant values (since you divide by deviation to the power of 4). And since the forecast generates constant values, you will get NA.

oh, of course. Not a bug.


hcxtools: 6.0.3 -> 6.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ZerBea/hcxtools/releases.
meta.description for hcxtools is: "Tools for capturing wlan traffic and conversion to hashcat and John the Ripper formats"
meta.homepage for hcxtools is: "https://github.com/ZerBea/hcxtools"
meta.changelog for hcxtools is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.1.0 with grep in /nix/store/fj63666g9g3zyrdyg7kby0g545nb095c-hcxtools-6.1.0

directory tree listing: https://gist.github.com/4bed8a2fede747ebb38f257def8b1e4a

du listing: https://gist.github.com/219d7f13b19402d646f89219a6bc1bdf

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
hcxtools
wifite2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fj63666g9g3zyrdyg7kby0g545nb095c-hcxtools-6.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hcxtools https://github.com/r-ryantm/nixpkgs/archive/37e29b490dd8e4fe9dd154201f20adc7d64419a1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fj63666g9g3zyrdyg7kby0g545nb095c-hcxtools-6.1.0
ls -la /nix/store/fj63666g9g3zyrdyg7kby0g545nb095c-hcxtools-6.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

2 packages built:

hcxtools
wifite2

Maintainer pings
cc @dywedir for testing.

segfaults for me:
$ gdb hcxpioff
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from hcxpioff...
(No debugging symbols found in hcxpioff)
(gdb) r
Starting program: /nix/store/nf515ramrmsyajdfr3pp4qkk0hfrrys3-hcxdumptool-6.0.7/bin/hcxpioff

Program received signal SIGSEGV, Segmentation fault.
0x0000000000401598 in main ()
(gdb) bt
#0  0x0000000000401598 in main ()

Result of nixpkgs-review pr 94504 run on x86_64-linux 1

2 packages built:

hcxtools
wifite2


Can we consider make the script more modular so other ppl can better help?

Can we consider make the script more modular so other ppl can better help?
https://docs.python-guide.org/writing/structure/

not much interest.. so I will close this.


Unable to compile

Sorry to bother you again but I cannot make your sample work.
My error is :
~/Projects/go/ » go version
go version go1.6.2 linux/amd64
~/Projects/go/ » echo $GOPATH
/home/albin/Projects/go
~/Projects/go/ » go get github.com/go-authboss/authboss-sample
~/Projects/go/src/github.com/go-authboss/authboss-sample » go run blog.go
# command-line-arguments
./blog.go:45: undefined: NewMemStorer
./blog.go:82: undefined: NewCookieStorer
./blog.go:83: undefined: NewSessionStorer
./blog.go:129: undefined: cookieStore
./blog.go:130: undefined: sessionStore
./blog.go:145: undefined: authProtect
./blog.go:146: undefined: authProtect
./blog.go:150: undefined: authProtect
./blog.go:151: undefined: authProtect
./blog.go:199: undefined: blogs
./blog.go:151: too many errors

I don't really understand as for example : NewMemStorer which is in storer.go is in the same package as blog.go. It should find it no ? What am I missing ? Something wrong with my setup ?

If you want to use go run you must specify all the files:
~/.../authboss-sample>go run blog.go blogs.go middleware.go cookie_storer.go session_storer.go storer.go
Perhaps the simpler approach is to just use go build
Linux:
~/.../authboss-sample>go build && ./authboss sample
Windows:
~/.../authboss-sample>go build && authboss sample.exe

Ok, thanks a lot for the tip.
I tried go build but I was giving blog.go in parameter.
Could you please explain me the difference between this sample application and a 'typical' go application ? For my Gin based web app, I can just run go run on the main file and everything is founded without the need of specifying all of the dependency files.

 It's your lack of knowledge of the Go toolchain that's making you believe otherwise. go run only works when you pass it all files required to run the project, go build uses package structure to dictate which files to use.


Wheel not compatible with windows10 pro x64

I got suspicious when pip tried to install the tgz file.
I'm using it on ubuntu fine
pip install .\autopy-1.0.1-cp36-cp36m-win_amd64.whl
autopy-1.0.1-cp36-cp36m-win_amd64.whl is not a supported wheel on this platform.

systeminfo /fo csv | ConvertFrom-Csv | select OS*, System*, Hotfix* | Format-List

OS Name             : Microsoft Windows 10 Pro
OS Version          : 10.0.17134 N/A Build 17134
OS Manufacturer     : Microsoft Corporation
OS Configuration    : Member Workstation
OS Build Type       : Multiprocessor Free
System Boot Time    : 07.06.2018, 09.23.56
System Manufacturer : ASUS
System Model        : All Series
System Type         : x64-based PC
System Directory    : C:\WINDOWS\system32
System Locale       : no;Norwegian (Bokmal)
Hotfix(s)           : 4 Hotfix(s) Installed.,[01]: KB4103729,[02]: KB4287903,[03]: KB4284835,[04]: KB4103721

Thanks

This is odd, as I packaged it on a 64-bit system. I'm going to try wiping my virtual machine and take another stab at it for the next version (see https://github.com/autopilot-rs/autopy/issues/18). Combining these two issues for now.


Consider introducing a lazy API to set repository URL for PublishToRepository task

Expected Behavior
It should be possible to set a URL of a repository in a configuration-cache compatible lazy manner.
Current Behavior
The existing Maven/IvyArtifactRepository.setUrl(Object) method is not lazy, the URL is eagerly evaluated when stored to the configuration cache.
Context
The lazy API will allow tweaking the publishing URL without invalidating the configuration cache, e.g. by wiring an environment variable provider.
There's also a more complex scenario, though it isn't obvious how widespread it is. The "publishing credentials" sample needs something to become fully configuration-cache compatible. The sample starts a bundled web server that works as a maven repository and then publishes libraries into the server. The URL of the server (the port part) may change between runs and can only be obtained after the server is started.
The current implementation starts the server in doFirst action and reconfigures the publishing repository. This isn't compatible with the configuration cache, because repository object is not restored from the cache fully.
A configuration cache-compatible implementation can be the following:

The web server is implemented as a shared build service with a getUrl accessor/provider
This URL provider is wired into the URL of publishing task repository with the new lazy API.

We have one of the more complex scenarios in the vanniktech/gradle-maven-publish-plugin. We have a task that makes an API call to Sonatype OSS to create a staging repository to upload to. The repository url is then derived from that plus 2 other properties that are set through our extension. We currently use a provider for the url to make this possible.
This is the configuration code
https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/plugin/src/main/kotlin/com/vanniktech/maven/publish/MavenPublishBaseExtension.kt#L64-L71

Gradle Nexus Publish Plugin would use this facility to support configuration cache. The value is set via provider already, but when Configuration Cache is enabled, the serialization eagerly resolves the provider too early before the task that would set the value executes.
See point 3) at https://github.com/gradle-nexus/publish-plugin/issues/221#issuecomment-1562968954

BTW, does anyone have an idea why
./gradlew -Porg.gradle.configuration-cache=false publishAndReleaseToMavenCentral

does not work if I have org.gradle.configuration-cache = true in gradle.properties? While I get
./gradlew -Porg.gradle.configuration-cache=false properties | grep org.gradle.configuration-cache
org.gradle.configuration-cache: false

in that case, the publishAndReleaseToMavenCentral task still complains:
* What went wrong:
Configuration cache state could not be cached: field `repository` of `org.gradle.api.publish.maven.tasks.PublishToMavenRepository$PublishSpec` bean found in field `value` of `org.gradle.internal.Try$Success` bean found in field `result` of `org.gradle.internal.serialization.Cached$Fixed` bean found in field `spec` of task `:advisor:publishMavenPublicationToMavenCentralRepository` of type `org.gradle.api.publish.maven.tasks.PublishToMavenRepository`: error writing value of type 'org.gradle.api.publish.maven.tasks.PublishToMavenRepository$RepositorySpec$Configured'

Either this or -Dorg.gradle.configuration-cache=false. -P sets the project property and is not suitable for most of the Gradle configuration.

I've never really understood the difference TBH. I thought that everything that can go to gradle.properties is also overridable via -P, and -D is to set Java system properties instead of Gradle properties.


fix typo SPHardwareDataTypeng => SPHardwareDataType on /cloudflare-one/identity/devices/corp-device.md

There's a typo on the /cloudflare-one/identity/devices/corp-device.md page.
SPHardwareDataTypeng should be SPHardwareDataType

Already fixed on https://developers.cloudflare.com/cloudflare-one/identity/devices/warp-client-checks/corp-device/


feat: Configurable default package install sync period

Which issue(s) this PR fixes:
It could resolve partially the issue.
Does this PR introduce a user-facing change?
Not directly but user can now have a configurable global default syncPeriod value for App created using PackageInstall.
Previously the value was hardcoded to 10m, it could be modified by specifying syncPeriod as part of PackageInstall manifest, However having a default global value could be useful for some use-cases where specifying a syncPeriod is tedious to every PackageInstall manifest.
The default 10m is still respected after having a discussion with the community / maintainers on Slack: https://kubernetes.slack.com/archives/CH8KCCKA5/p1686321873099489
* Controller configuration to specify `PackageInstallDefaultSyncPeriod`

Additional Notes for your reviewer:
Review Checklist:

[x] Follows the developer guidelines
[x] Relevant tests are added or updated
[x] Relevant docs in this repo added or updated
[x] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[x] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:
Docs PR: https://github.com/carvel-dev/carvel/pull/658

Cool, Thx 👍


Coin98 implementation doesn't detect the extension and always send you to coin98.com

This issue qualifies more as a question.
The sub-package states in its readme that it is coming soon but since many other things say coming soon I don't know if Coin98 wallet provider implementation is done.
I have cloned the example app and added getCoin98Wallet() to the list of wallets to initialize and it indeed appears on the list but clicking in the Coin98 wallet option it takes me to their website even when I already installed the extension and I am connected. The wallet provider seems to not detect the extension.
If someone knows the status of Coin98 it would be great to know to make it available in my dApp.
Sorry if this doesn't have issue format, it is more a question.

After a while it started working, no idea why.

Glad you worked it out. I checked with the Coin98 team and they verified that the adapter is using the expected API. Can you mention what browser / device you are using? Just want to track this in case it occurs again.

Hey @jordansexton now I have confirmed that there is nothing wrong in the implementation. It seems that it is not enough with adding the Coin98 browser extension to pop it up. It needs to be initialized for the first time for Solana and as soon as you add (create/import) your first wallet for the current browser (tested with latest versions of Chrome, Opera and Brave) it starts popping up when the Coin98 option is clicked.
So essentially the only thing that is wrong that users can be frustrated with is the fact that they don't know this until they actually create a wallet for solana. None of my teammates had a Coin98 wallet so they all stopped there and none went through the process of creating a Wallet as "the solution of the problem", they simply complained and threw the implementation issue in JIRA, classic.
I hope this helped somehow.

Thanks for the extra details, that's very helpful. I'll test and raise this issue with the Coin98 team.

Closing this issue as the Coin98 team is aware and it's up to them to fix.


WAYF does not remember last selected IdP

Steps to reproduce:

Cleanup cookies related to IdP selection by WAYF (engine.surfconext.org "selectedIdP")
Login using IdP 1
login to another SP. The WAYF will now correctly present IdP 1 as the pre selection
Use IdP 2 to login
Login to yet another SP
WAYF will now present IdP1, not IdP 2
It should however preselect IdP 2

My cookies:
Host:                 engine.surfconext.nl
Name:                 selectedIdp
Path:                 /authentication/idp/
Content:              https%3A%2F%2Fidp.surfnet.nl
Content raw:          https%3A%2F%2Fidp.surfnet.nl
Expires:              di 04 nov 2014 17:08:38 CET
Expires raw:<PHONE_NUMBER>
Send for:             Any type of connection
Send for raw:         false
Created:              wo 02 apr 2014 10:35:16 CEST
Created raw:<PHONE_NUMBER>874516
Last accessed:        di 05 aug 2014 09:36:51 CEST
Last accessed raw:<PHONE_NUMBER>813410
HTTP only:            No
HTTP only raw:        false
This domain only:     No
This domain only raw: false
Policy:               no information available
Policy raw:           0
Status:               no information available
Status raw:           0
Host:                 engine.surfconext.nl
Name:                 selectedIdp
Path:                 /authentication/idp/process-wayf/
Content:              https%3A%2F%2Fidp.surfnet.nl
Content raw:          https%3A%2F%2Fidp.surfnet.nl
Expires:              di 04 nov 2014 09:17:28 CET
Expires raw:<PHONE_NUMBER>
Send for:             Any type of connection
Send for raw:         false
Created:              do 03 apr 2014 10:38:41 CEST
Created raw:<PHONE_NUMBER>920783
Last accessed:        ma 04 aug 2014 17:08:39 CEST
Last accessed raw:<PHONE_NUMBER>665488
HTTP only:            No
HTTP only raw:        false
This domain only:     No
This domain only raw: false
Policy:               no information available
Policy raw:           0
Status:               no information available
Status raw:           0
Host:                 engine.surfconext.nl
Name:                 selectedIdp
Path:                 /authentication/idp/single-sign-on/
Content:              https%3A%2F%2Fidp.surfnet.nl
Content raw:          https%3A%2F%2Fidp.surfnet.nl
Expires:              di 04 nov 2014 10:29:22 CET
Expires raw:<PHONE_NUMBER>
Send for:             Any type of connection
Send for raw:         false
Created:              do 03 apr 2014 14:46:40 CEST
Created raw:<PHONE_NUMBER>317684
Last accessed:        di 05 aug 2014 09:36:51 CEST
Last accessed raw:<PHONE_NUMBER>813410
HTTP only:            No
HTTP only raw:        false
This domain only:     No
This domain only raw: false
Policy:               no information available
Policy raw:           0
Status:               no information available
Status raw:           0
Host:                 engine.surfconext.nl
Name:                 selectedIdp
Path:                 /authentication/idp/single-sign-on/key:20140505/
Content:              http%3A%2F%2Fadfs.stenden.com%2Fadfs%2Fservices%2Ftrust
Content raw:          http%3A%2F%2Fadfs.stenden.com%2Fadfs%2Fservices%2Ftrust
Expires:              vr 31 okt 2014 13:34:06 CET
Expires raw:<PHONE_NUMBER>
Send for:             Any type of connection
Send for raw:         false
Created:              ma 21 jul 2014 14:02:04 CEST
Created raw:<PHONE_NUMBER>474926
Last accessed:        di 05 aug 2014 09:36:51 CEST
Last accessed raw:<PHONE_NUMBER>813410
HTTP only:            No
HTTP only raw:        false
This domain only:     No
This domain only raw: false
Policy:               no information available
Policy raw:           0
Status:               no information available
Status raw:           0
Host:                 engine.surfconext.nl
Name:                 selectedIdp
Path:                 /authentication/idp/single-sign-on/vo:managementvo/
Content:              https%3A%2F%2Fidp.surfnet.nl
Content raw:          https%3A%2F%2Fidp.surfnet.nl
Expires:              za 25 okt 2014 14:10:30 CEST
Expires raw:<PHONE_NUMBER>
Send for:             Any type of connection
Send for raw:         false
Created:              di 06 mei 2014 17:22:30 CEST
Created raw:<PHONE_NUMBER>323423
Last accessed:        do 31 jul 2014 14:16:36 CEST
Last accessed raw:<PHONE_NUMBER>821722
HTTP only:            No
HTTP only raw:        false
This domain only:     No
This domain only raw: false
Policy:               no information available
Policy raw:           0
Status:               no information available
Status raw:           0

Fixed in EB 4.5.


[5.9] Always specify -gmodules on built-in Clang invocations

Cherry-pick of https://github.com/apple/swift/pull/64912
This is currently always done when instantiating ClangImporter by manually setting the option on the Clang invocation with:
Invocation->getCodeGenOpts().DebugTypeExtRefs = true

Now also add it to importer::addCommonInvocationArguments so that the dependency scanner always generates command-lines with the required for Swift Clang flags.
Resolves rdar://107570568

@swift-ci test

Great findings!

@swift-ci test