The Biggest Star: The hint of step2 is not accurate

Describe the bug
The Biggest Star: The hint of step2 is not accurate
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/--skillmap#star
2.The Biggest Star---->START
3.Click step 2
Expect behavior
It should be:

Actual behavior
The hint of step2 is not accurate

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.8.5
3.Microsoft MakeCode version: 7.4.12

Fixed in my next PR


Feature: Light mode bg

fixes this bg color in Deployments, Flow, WorkPool, and WorkPoolQueue

also uses latest prefect-design

fixing build here


Use rainbow kit for login

Description
Update the login system from a custom login page/modal to an already well-established tool https://www.rainbowkit.com/.
This will help in many ways:

Better detection of the wallets present on the user's browser
Better compatibility with wallets like nice connection to remote metamask, install of new wallets etc...
Simplification of the codebase

How to test
Go to any page and login with the "sign in" button in the nav bar or on the /login page
TODO

[ ] Fix issue that once connected wagmi onConnect function is not called

Note: The issue with the onConnect not called is related to the fact that useAccount is also using the useWagmiAccount. The custom useAccount should not use the wagmi's useAccount


[mgmt] neonpostgres release

https://github.com/Azure/sdk-release-request/issues/5640

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-neonpostgres

/azp run prepare-pipelines

/azp run js - neonpostgres - mgmt - ci


HTML auto direction for specific textual content

updated the onboarding flow to use automatic lang direction and removed unneeded fragment.

Is this the correct way to do it? What about english should that not be ltr?

I mean it does seems to work: https://rtl.snort-social.pages.dev/e/note170sn3kcxxzk9unchk4zh7zatzxu7pjgkn59hyqpt4h0yg454m7vsdrh7q2

auto will show text ltr or rtl depending on the content characters so does the right thing.


proposal : better_craigslist

Proposal for ZK Bankai

@johnsoncarl
Our implementation will stretch the capabilities of Plonky3 and Circom:
Our project aims to push the boundaries of Plonky3 and CIRCOM in practical, high-stakes applications. While we're building on existing ZKEmail concepts, we're innovating in several key areas:
a) We're developing specialized Plonky3 circuits optimized for high-throughput, low-latency email verification in a marketplace context. This will stress-test Plonky3's capabilities in ways not previously explored.
b) We're creating novel CIRCOM circuits for an anonymous reputation system, which is a new application in decentralized marketplaces.
c) Our project will provide valuable benchmarking data comparing Plonky3 and CIRCOM implementations in a real-world, high-stakes scenario.
Innovative aspects of ZKEmail circuits:
While ZKEmail circuits exist, our implementation differs in several important ways:
a) We're adapting these circuits for a new use case (secure marketplaces), which presents unique challenges and opportunities for optimization.
b) We're experimenting with Plonky3's advanced features like recursive proofs to enhance scalability and performance in our specific context.
c) We're developing a hybrid system that combines email verification with anonymous reputation tracking, which is a novel approach in this space.

@chiro-hiro
Would really appreciate your comments here as well.

@chiro-hiro
Would really appreciate your comments here as well.

Hi @YashBit,
I think your proposal is much more focus on application side and apply zkEmail to actual product in this case it's a C2C market (I hope I understand it correct). I'd prefer that you just focus on improving zkEmail or adding new feature into it then the proposal may fit to the program's requirement.
The idea is interesting but I have concern about data integrity and censorship.
Thanks,
Chiro

@chiro-hiro @johnsoncarl Updated.

@chiro-hiro Would deeply appreciate your comments on the updated proposal.

Gonna check now 🤗

@chiro-hiro Please can we connect on Telegram.

I've just added more comments, I'm prefer to have a section to provide more detail of your solution. Right now everything is described in common term, so I think it is very difficult for mentors to evaluate feasibility of the project.
My Telegram is: chiro8x
Don't hesitate to reach me.

@chiro-hiro Made the required changes.

Merging this PR For application review

@chiro-hiro Hi, I hope you liked all our answers. Thank you so much for putting in the energy to guide our team.


Push notification authorization + misc cleanup for README

Added content about push notification authorization requests
Cleaned up the content and formatting (and moved the rich push notification content into the section about push notifications)

Decided not to merge this; see: https://iterable.slack.com/archives/CAE79PMM5/p1559681481004800


testSequencer config silently ignored in projects

Note: This is fundamentally working as intended, this issue is now about validating the config and providing a sufficient warning.
🐛 Bug Report
The configuration testSequencer (https://jestjs.io/docs/en/configuration#testsequencer-string) is silently ignored in projects (https://jestjs.io/docs/en/configuration#projects-arraystring--projectconfig)
To Reproduce
Run this config and test sequencer:
module.exports = {
  projects: [
    {
      testEnvironment: 'node',
      testSequencer: './jestSequencer.js',
    },
  ],
};

const Sequencer = require('@jest/test-sequencer').default;

console.log('I will never get called.');

class CustomSequencer extends Sequencer {
  sort(tests) {
    // Test structure information
    // https://github.com/facebook/jest/blob/6b8b1404a1d9254e7d5d90a8934087a9c9899dab/packages/jest-runner/src/types.ts#L17-L21
    const copyTests = Array.from(tests);
    return copyTests.sort((testA, testB) => (testA.path > testB.path ? 1 : -1));
  }
}

module.exports = CustomSequencer;

Expected behavior
Jest should warn that the testSequencer should be global config, not per-project.
Original implementation: https://github.com/facebook/jest/issues/6216
Link to repl or repo (highly encouraged)
See above.
envinfo
  System:
    OS: Linux 4.4 Ubuntu 16.04.5 LTS (Xenial Xerus)
    CPU: (4) x64 Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
  Binaries:
    Node: 12.13.0 - ~/.config/nvm/12.13.0/bin/node
    npm: 6.12.0 - ~/.config/nvm/12.13.0/bin/npm
  npmPackages:
    jest: 25.1.0 => 25.1.0

Thanks for the report. I would however say that it is intended that we sort allTests (as we do in the runJest function where the sequencer is called). We should reserve the right to interleave tests of different projects in any way necessary to optimize overall performance. In fact, being smarter about the order of running tests from different projects is something I've wanted to improve on for quite some time.
I would instead say the expected behavior should be that the config validation throws straight away, instead of silently ignoring the project-level test sequencer option. We can make this issue about fixing that (and label help wanted / good first issue). If someone then wants to sort per project, they can still use the global sequencer and implement it in a way that groups by test.context.config.name or something.

@thernstig would you be fine with that change? You could edit the issue or I can, whatever suits you :)

@jeysal What I am trying to achieve is to run end-to-end tests. Our end goal is to run them in parallel, but right now we want to run a login suite first (hence the sequencer) and then the rest (using a custom test runner with isSerial=true). Reading back on many issues from the past, this seem to be more and more common, seeing as Jest is awesome and thus users want to use it for also e2e tests.
Thus, using projects for this is nice if I could use a testSequencer just for that project, the e2e project. I am afraid that for me, that have not looked deeply into the what context is, and a quick google shows nothing, so I assume it would be undocumented and I would have to read into the source code and/or console.log() what's in there? (I did and just found a hash, so that did not bring me forward).
What is your suggestion to this problem then? I do understand the logic for properly sequencing is impor tant for performance, but having a project used for e2e is a different beast.

Well, to be fair, manually writing a test sequencer is generally something that requires knowledge of some Jest internals, like writing a runner or an environment.
As for your use case, it's clear that you want to sort tests in the e2e in your custom way, and other tests in the regular @jest/test-sequencer way. Now ask yourself what should happen if a Jest run contains both e2e tests and other tests. If the answer is that other tests should run first and then e2e tests should run, I would recommend implementing your sequencer as follows:

Introspect test.context.config (the project config the test belongs to) to find out whether the test is e2e (this should be relatively easy, probably using rootDir)
If test1 and test2 are e2e, sort them in your custom way
If test1 and test2 are not e2e, delegate to @jest/test-sequencer (you can import and instantiate that to reuse its standard logic)
If test1 is e2e, but test2 is not, return 1.

Yes, fair points. I am pretty sure I can work around this regardless by introspecting everything in the sequencer. I've actually already got a way since I know the test case name for the login suite will be login.e2e.test.js I can just do:
    copyTests.sort((testA, testB) => {
      if (testA.path && testA.path.endsWith('login.e2e.test.js')) return -1;
      if (testB.path && testB.path.endsWith('login.e2e.test.js')) return 1;
      return undefined;
    });

Problem solved! :)
I think this issue more is so that if you have a sequencer inside a project, you still want the main sequencer to sort in whatever way, and then the project sequencer sorts it an additional time for just the test cases in that project root. This would mean the main/top-level sequencer would sort "slowest first" (or any other performance enhancers) whilst the internal sort when will sort by name. The return undefined part will make sure all other sorts does not change the logic from the top-level sequencer which keeps the whole run performant.
I think I come from the perspective that e2e testing is common, jest awesome, and more users want to use Jest for it's power to run various kind of projects.
(no matter - throwing is better than anything even though I obviously wish there was a way to use a sequencer in projects as well 😄)

I think we want to keep the concept of a test sequencer very lightweight (like just swapping out the @jest/test-sequencer module for something else is). It was introduced very hesitantly after a lot of demand for being able to customize the order. One global sequencer has all the powers that individual project sequencers have (I gave an example), so no need to introduce more logic into Jest just for the customization use case.
Let's keep this issue open for the config validation part, I'll make a small edit.

Ok that is fair. For me the API for this feels more convoluted than having supported sequencers per project as well (that would not have required me to know the internals as much).
Could you elaborate this part, for reference (for me and maybe others in the future) with some code? Appreciate it.

If test1 and test2 are not e2e, delegate to @jest/test-sequencer (you can import and instantiate that to reuse its standard logic)

Could you elaborate this part, for reference (for me and maybe others in the future) with some code?

Looks like it's not actually possible exactly the way I described it, since Jest's default sequencer does not expose its order function. But since sort is now pretty much guaranteed to be a stable sort in JS, you can first let Jest's default sequencer sort
import defaultSequencer from '@jest/test-sequencer';

// ... in your sort method
const preSortedTests = defaultSequencer.sort([...tests]);
// ... your custom sort on preSortedTests

and then do your sort - everything where you don't define an order (return 0) should remain in the order the standard Jest sequencer sorted it, your sequencer essentially just plucked out a few tests and moved them somewhere to the top or bottom.

Thanks @jeysal, already solved this some time ago by using the defaultSequencer's sort, worked great - even tested it to make sure it ran "slow first". 😃

hey, I want to contribute. please guide me on how to start contributing. I have fork and clone it and set the environment for this in my pc.

hey, I want to contribute. please guide me on how to start contributing. I have fork and clone it and set the environment for this in my pc.

https://github.com/facebook/jest/blob/main/CONTRIBUTING.md

I challenge to contribute.

https://github.com/facebook/jest/releases/tag/v29.3.0


IOS Refactoring & Partial UWP Refactoring

I was able to get all of the IOS Projects cleaned up.
UWP is kicking out 1300+ errors, System.Object not defined etc. I am unfamiliar with UWP and what may be missing (or may be .Net Standard bugs) causing the inability to compile.  I cleaned up what I could find in the errors list, so it should be close once the System dependencies or whatever is resolved.

Hi Mike. In order to get UWP to compile properly with .Net Standard 2.0 you need the latest VS release and a preview of the fall update

Ok, thanks for that, the fall update preview is what I'm missing.


Support NO_COLOR environment variable

Support disabling color output globally using the NO_COLOR environment variable as specified here: https://no-color.org/
In particular it would be useful for CI output and users who dislike stylized output for my CLIs.

Duplicate of #1498, although I had been looking at this again recently. I'm open  to review a PR if you'd like to submit one.

Duplicate of #1498. While I understand the intention of the proposal, it's not clear that it's the correct thing to do. For example, Click doesn't provide a --color option, so every project would still need to implement turning color back on manually. At that point, why not also do this:
if __name__ == "__main__":
    color = os.environ.get("NO_COLOR")
    color = color in {"1", "true"} if color is not None else None
    cli(color=color)

I did see that Rich implements this, but that alone isn't a convincing reason for it.

Sorry, I should have found the prior issue. I’ll stare at the code more.
It really doesn’t need to be supported directly, I guess, but easy to implement support without logic around every style or secho. It may be already, so I’ll shut up now and actually read.  I don’t mean to ask you to spell it out for me.
To me, ideally there should be a simple pattern for support or direct support.
And I should not just whine but say “thank you”.  This library has made me happy and more productive for so long.

No problem.
The color parameter shown above will tell Click to not output color codes. So if you want to support that env var, reading it and setting the parameter will do the right thing.

If you're interested @mmessmore, I've created a ready-to-use --color/--no-color flag option for Click that is supporting the NO_COLOR convention. It is available as a part of click-extra.

Oh, thank you. That’s great.


Deployment instructions before the next Heapster release

Updated the README file to include temporary deployment instructions for the Heapster Pod, until the next release is available
\cc @vishh @rjnagal

LGTM

We should add the licence check hooks to this repo @afein.


Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.

你好，引入插件后运行报错：
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
Could not find :rpsdk-4.5.0-open:.
Required by:
project :app > project :fl_ali_realperson
Could not find :oss-android-sdk-2.9.2:.
Required by:
project :app > project :fl_ali_realperson
Could not find :SecurityBodySDK-external-release-5.5.19:.
Required by:
project :app > project :fl_ali_realperson
Could not find :SecurityGuardSDK-external-release-5.5.14240408:.
Required by:
project :app > project :fl_ali_realperson
Could not find :MiddleTierSDK-external-release-5.5.13874142:.
Required by:
project :app > project :fl_ali_realperson
Could not find :windvane:.
Required by:
project :app > project :fl_ali_realperson

这是什么原因导致的呢？我新建的空项目试了下也是这样

你好，引入插件后运行报错：
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
Could not find :rpsdk-4.5.0-open:.
Required by:
project :app > project :fl_ali_realperson
Could not find :oss-android-sdk-2.9.2:.
Required by:
project :app > project :fl_ali_realperson
Could not find :SecurityBodySDK-external-release-5.5.19:.
Required by:
project :app > project :fl_ali_realperson
Could not find :SecurityGuardSDK-external-release-5.5.14240408:.
Required by:
project :app > project :fl_ali_realperson
Could not find :MiddleTierSDK-external-release-5.5.13874142:.
Required by:
project :app > project :fl_ali_realperson
Could not find :windvane:.
Required by:
project :app > project :fl_ali_realperson

这是什么原因导致的呢？我新建的空项目试了下也是这样

请提交一下flutter -doctor -v的输出信息


Unable to install nodegit#v0.23.0 on Node 10

Hi folks,
I'm running nodegit on my machine and was really happy to see support for node 10!
Sadly, I'm unable to install it. Can someone please help me with some ideas on how to fix it?
System information

node version: 10.13.0
npm or yarn version: 6.4.1
OS/version/architechture: Linux, Fedora 28 64-bit
Applicable nodegit version: 0.23.0

$>  ls -l /usr/lib64/libssl*
-rwxr-xr-x. 1 root root 360824 Sep  3 15:29 /usr/lib64/libssl3.so
lrwxrwxrwx. 1 root root     16 Sep 20 15:46 /usr/lib64/libssl.so -> libssl.so.1.1.0i
lrwxrwxrwx. 1 root root     16 Apr  5  2018 /usr/lib64/libssl.so.10 -> libssl.so.1.0.2o
-rwxr-xr-x. 1 root root 471024 Apr  5  2018 /usr/lib64/libssl.so.1.0.2o
lrwxrwxrwx. 1 root root     16 Sep 20 15:46 /usr/lib64/libssl.so.1.1 -> libssl.so.1.1.0i
-rwxr-xr-x. 1 root root 468080 Sep 20 15:46 /usr/lib64/libssl.so.1.1.0i

$>  ls -l /usr/lib64/libcrypto*
lrwxrwxrwx. 1 root root      19 Sep 20 15:46 /usr/lib64/libcrypto.so -> libcrypto.so.1.1.0i
lrwxrwxrwx. 1 root root      19 Apr  5  2018 /usr/lib64/libcrypto.so.10 -> libcrypto.so.1.0.2o
-rwxr-xr-x. 1 root root 2729216 Apr  5  2018 /usr/lib64/libcrypto.so.1.0.2o
lrwxrwxrwx. 1 root root      19 Sep 20 15:46 /usr/lib64/libcrypto.so.1.1 -> libcrypto.so.1.1.0i
-rwxr-xr-x. 1 root root 2907248 Sep 20 15:46 /usr/lib64/libcrypto.so.1.1.0i

Reproduce
Simply run: $> npm install nodegit
Output looks like:
><EMAIL_ADDRESS>install /tmp/node_modules/nodegit
> node lifecycleScripts/preinstall && node lifecycleScripts/install

[nodegit] Running pre-install script
[nodegit] Running install script
node-pre-gyp
WARN Using request for node-pre-gyp https download
[nodegit] Success: "/tmp/node_modules/nodegit/build/Release/nodegit.node" is installed via remote
[nodegit] Completed installation successfully.

><EMAIL_ADDRESS>postinstall /tmp/node_modules/nodegit
> node lifecycleScripts/postinstall

[nodegit] WARN - Could not finish postinstall
{ Error: Command failed: node "/tmp/node_modules/nodegit/dist/nodegit.js"
/tmp/node_modules/nodegit/dist/nodegit.js:16
    throw ex;
    ^

Error: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:717:18)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/tmp/node_modules/nodegit/dist/nodegit.js:12:12)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)

    at ChildProcess.exithandler (child_process.js:289:12)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:962:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
  killed: false,
  code: 1,
  signal: null,
  cmd: 'node "/tmp/node_modules/nodegit/dist/nodegit.js"' }

As you can see, I've installed compat-openssl10 on my maschine (libssl.so.1.0.2) and openssl (libssl.so.1.1.0). But nodegit still asks for libcrypto.so.1.0.0 and libssl.so.1.0.0. I do not know why. Where is my error?
I've tried linking ln -s /usr/lib64/libcrypto.so.<IP_ADDRESS>o /usr/lib64/libcrypto.so.1.0.0 (same for libssl), which leads to another error, telling me nodegit cannot find OPENSSL_1.0.0 in libssl.so.1.0.0 (which seems to be correct, since I've just linked 1.0.2 for it :-)). Any thoughts?

Ugh, and I'm unable to get fedora to install on my machine at home to try to take a stab at this locally.
How did you install node?

Thank you for answering!
I'm using nvm, so I've just nvm install 10 (which currently installs v10.13.0 alongside with npm v6.4.1) and running npm install nodegit.
My nvm --version is 0.33.9

Funfact:
$> nvm install 11.1
$> npm install nodegit

Just works (it installed nodegit#v0.23.0 successfully). Why not latest LTS? :thinking:

Have you installed with --build-from-source?

I feel like these links here in the binding.gyp are unnecessary for building nodegit on linux for Node (non-electron) https://github.com/nodegit/nodegit/blob/master/generate/templates/templates/binding.gyp#L194 and might be causing the issue you're seeing. @mvhirsch

@implausible you mean, the line in binding.gyp can be removed - and it works?

Sort of, those links are necessary in electron builds, but should not be necessary in regular node builds (node provides the libraries and headers for crypto / ssl). Let's watch the progress of this PR https://github.com/nodegit/nodegit/pull/1600

Fixed with #1600 in v0.24.0


Clustering plugin

@incanus mentioned that his clustering example may be able to be adapted to work as a plugin. This may be a good option until https://github.com/mapbox/mapbox-gl-native/issues/5814 is implemented in our Maps SDK.

This seems like a useful next plugin. I'll start working on it in early October.

It looks like the Android marker clustering plugin ports open-source clustering algorithms. I am leaning towards attempting this with the iOS equivalent, rather than simply porting the workaround. This would be more of a lift, but likely a better option in the long run. Thoughts?
cc @1ec5 @boundsj @fabian-guerra @lilykaiser

ClusterKit already implements clustering of view-backed annotations (alonside MapKit and Google Maps support). The project is MIT-licensed, so we could in theory adapt it into a plugin without much fuss. Assuming ClusterKit does well at what it does, should we still build this plugin, or should we focus on building annotation view clustering into the map SDK for MapKit parity (mapbox/mapbox-gl-native#5815)?

Considering that MapKit added this at last WWDC it may make more sense build this into our SDK for parity. I have seen clustering annotations is a requested feature in our repo and is a pretty common use case. Making this a first class citizen sounds like it's the way to go. But I may be wrong.

I have begun to experiment with both ClusterKit and the Google Maps utilities library in this branch: https://github.com/mapbox/mapbox-plugins-ios/tree/jk-clustering-plugin
Both libraries offer two algorithms. My current plan is to port the grid-based clustering algorithm first, since it doesn't rely on a quad tree (as far as I can tell). Based on how that goes, I'll work on porting the second algorithm.
A third option may be to create an iOS wrapper for SuperCluster, but I have not investigated how to go about that.
Introducing it as a plugin makes sense in the short term, since plugins are by nature experimental. It may be a better SDK feature in the long run, but I'd like to test it out here first.

A third option may be to create an iOS wrapper for SuperCluster, but I have not investigated how to go about that.

It would make sense to use Supercluster for an implementation built into the iOS SDK, because the SDK’s build system already pulls in that library. To use a C++ library like Supercluster in this repository would unnecessarily complicate the build system, for example by making it difficult or impossible to distribute the library as source code via CocoaPods or Carthage. Instead, if we persue a plugin implementation, we might as well use a C or Objective-C implementation of the same algorithms.

Using a C or Objective-C implementation of Supercluster may be the most straight-forward approach in the long run, but I'm not sure that I would be able to efficiently port it.
Next steps for me will be looking into how much of a lift these options would be. I'll keep looking at both ClusterKit and the Google Maps utilities library, but I can also look into what be needed in order to use Supercluster with MGLPointAnnotation in the iOS SDK.

I'm going to port ClusterKit, with some modifications to optimize it for Mapbox. It's the most feasible for me to complete in a reasonable amount of time. My first focus will be a direct port that I can then refactor to focus on Mapbox. Additional goals for further down the line:

Minimize the use of MapKit (for example, not using MKMapRectUnion)

Include a simplified clustering algorithm (similar to what Google Maps Utils for iOS offers) so that we can test out additional clustering algorithms before we begin work on introducing this to the SDK. This allows us to more safely experiment with other clustering algorithms as we look at using this with other algorithms.


Enhance automated tests due to race-conditions incl. DB Fix

Description
This PR enhances multiple unit-test due to race conditions. Furthermore, it fixes a bug for the inMemory and persistent database implementation.
Changes
New Test-Cases:

reconciliation repository:

Create multiple instances of single reconciliations in parallel; Only one should be successful
Update single reconciliation in multiple parallel threads; Only one should be successful
Mark single reconciliation as finished in multiple parallel threads; Only one should be successful

bookkeeper:

Mark two operations as orphan in multiple parallel threads; Each operation should only be updated once as an orphan
Finish two operations as orphan in multiple parallel threads; Each operation should only be updated once as an done

Workerpool:

Multiple WorkerPools watching same reconciliation repository; Each operation should only be assigned to one worker / should only be invoked once

Scheduler:

Multiple scheduler watching same inventory; For each cluster reconciliations should be only created once

Refactor:

Introduction of NewCluster  function and TestCluster type, to reduce code duplication in unit tests; adapt testcase due to this
Wrap errors in factory.go, sqlite.go for better error log output
Introduction of IsAlreadyInStateError
Refactor of bookkeeper: Introduction of BookkeepingTask to establish Chain of Responsibility pattern to have a better testable code (including written unit tests)

Fix:

Increase test timeout to 20min, since Pipelines take longer than 15min, local execution takes around 3,5min
Change host in unittest config to <IP_ADDRESS>, due to IPv6 issues
In update call (persistent and inmemory): Check if new wanted state is same as current state; If yes update should fail
Invoke of remoteInvoker called i.updateOperationState(params, model.OperationStateClientError, errorReason) twice; but it should only be called once
Adapt Remote Invoker test due to DB  and remote invoker fix

Related issue
https://github.com/kyma-incubator/reconciler/issues/374

/test pre-main-reconciler-integration-k3d


Development: Allow direct linking between Feedback and test cases

Contains migration, don't deploy this yet
Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[ ] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[ ] I chose a title conforming to the naming conventions for pull requests.

Server

[ ] I followed the coding and design guidelines.
[ ] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[ ] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[ ] I implemented the changes with a good performance and prevented too many database calls.
[ ] I documented the Java code using JavaDoc style.

Client

[ ] I followed the coding and design guidelines and ensured that the layout is responsive.
[ ] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[ ] I documented the TypeScript code using JSDoc style.
[ ] I added multiple screenshots/screencasts of my UI changes.
[ ] I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

Description

Steps for Testing

Prerequisites:

1 Instructor
2 Students
1 Programming Exercise with Complaints enabled

Log in to Artemis
Navigate to Course Administration
...

Exam Mode Testing

Prerequisites:

1 Instructor
2 Students
1 Exam with a Programming Exercise

Log in to Artemis
Participate in the exam as a student
Make sure that the UI of the programming exercise in the exam mode stays unchanged. You can use the exam mode documentation as reference.
...

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test

Test Coverage

Screenshots

Codecov Report

Merging #6381 (c7a6b85) into develop (13fd556) will increase coverage by 0.00%.
The diff coverage is 86.95%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #6381   +/-   ##
==========================================
  Coverage      80.28%   80.28%
+ Complexity     13012    13009    -3
==========================================
  Files           2301     2302    +1
  Lines          88939    88946    +7
  Branches       13149    13151    +2
==========================================
+ Hits           71405    71414    +9
+ Misses          9736     9735    -1
+ Partials        7798     7797    -1

Impacted Files
Coverage Δ

...in/www1/artemis/repository/FeedbackRepository.java
85.71% <ø> (+6.64%)
:arrow_up:

...ository/ProgrammingExerciseTestCaseRepository.java
100.00% <ø> (ø)

...temis/service/connectors/bamboo/BambooService.java
71.81% <ø> (ø)

...s/service/connectors/gitlabci/GitLabCIService.java
86.95% <ø> (ø)

...mis/service/connectors/jenkins/JenkinsService.java
92.62% <ø> (ø)

...w1/artemis/service/hestia/ExerciseHintService.java
89.62% <0.00%> (ø)

...rogramming/ProgrammingExerciseTestCaseService.java
84.21% <ø> (-4.81%)
:arrow_down:

...w1/artemis/domain/ProgrammingExerciseTestCase.java
94.02% <66.66%> (+1.38%)
:arrow_up:

...ng/ProgrammingExerciseFeedbackCreationService.java
85.71% <85.71%> (ø)

...programming/ProgrammingExerciseGradingService.java
91.73% <88.88%> (-0.21%)
:arrow_down:

... and 4 more

... and 2 files with indirect coverage changes

Flag
Coverage Δ

client
76.39% <ø> (ø)

server
84.60% <86.95%> (+<0.01%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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


Documentation skeleton

Updates README and provides some placeholders to start writing the documentation and tutorials.

Codecov Report

Merging #62 (9f96fdc) into main (e49d1d4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   48.77%   48.77%
=======================================
  Files          15       15
  Lines        1060     1060
=======================================
  Hits          517      517
  Misses        501      501
  Partials       42       42

Flag
Coverage Δ

unittests
48.77% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Short solution needed: "How to  scale y axis" (python-matplotlib)

Please help us write most modern and shortest code solution for this issue:
How to  scale y axis (technology: python-matplotlib)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to log scale Y axis


Refactor Render class

Adding types can help clarify methods and reduce potential issues with wrong arguments

@porcelain11 @Nitvex had to revert this, as it causes a bug with re-scaling


Add code generators section in other resources with initializr and bootify

Hello,
how about adding a "code generators" section under others? Spring Initializr is a must-know for Spring Boot developers I guess, and Bootify can be useful as well if you work with a relational database.

Is there any update on the issue?:)

@tleipzig Thanks for your contribution and sorry for the late answer. Could you list the two items alphabetically? Also, what do you think about changing the title of the section to "Project Scaffolding"?

Thank you @ThomasVitale - Scaffolding is more precise indeed! Applied your suggestions.

Thank you!

Thanks a lot!


yui compressor cannot compress infer.js (latest version) due to errors.

Can you please check this?
[ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [1315:34]: missing name after . operator [ERROR] ...infer.js:line 1315:column 34:missing name after . operator 	          target = (method.static ? fn : proto).defProp(pName, method.key) [ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [1316:18]: syntax error [ERROR] ...infer.js:line 1316:column 18:syntax error 	          target.initializer = true [ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [1317:43]: missing ; before statement [ERROR] ...infer.js:line 1317:column 43:missing ; before statement 	          if (method.kind == "get") target = new IsCallee(inst, [], null, target) [ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [1324:6]: syntax error [ERROR] ...infer.js:line 1324:column 6:syntax error 	    }) [ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [2159:3]: missing } after function body [ERROR] ...infer.js:line 2159:column 3:missing } after function body 	}); [ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [2159:3]: missing } after function body [ERROR] ...infer.js:line 2159:column 3:missing } after function body 	}); [ERROR] /Users/jgoldhammer/development/sources/js-console/javascript-console-share-aikau/src/main/amp/web/js/javascript-console/tern/lib/infer.js [1:0]: Compilation produced 6 syntax errors. [ERROR] ...infer.js:line 1:column 0:Compilation produced 6 syntax errors.
Thanks,
Jens

The YUI compressor is an outdated piece of junk, and I'm not really interested in supporting it. Consider using UglifyJS or any other compressor whose authors actually understand parsing.


feat(build): add cleanup-markdown feature flag

Closes #1073
I also documented the feature flags.

Looks like we just have a CI failure that needs to be resolved before we can merge

All tests run fine on my local machine, maybe you could re-run CI?

Ah @nylonicious since this changes the output of the generated code for tonic-types you will need to run cargo test --all then commit the extra code that was updated. That is why CI is failing.

I see, my bad. It now passes cargo test --all --all-features locally.


fix(EMI-1846): Pass "Purchase" title to partner offer checkout modal

This PR resolves EMI-1846
Description
This PR adds the "Purchase" title to the Partner Offer checkout modal
It also updates the podfile lock
Screenshots

Before
After

Android

iOS

PR Checklist

[X] I have tested my changes on iOS and Android.
[X] I hid my changes behind a feature flag, or they don't need one.
[X] I have included screenshots or videos, or I have not changed the UI.
[X] I have added tests, or my changes don't require any.
[X] I added an app state migration, or my changes do not require one.
[X] I have documented any follow-up work that this PR will require, or it does not require any.
[X] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

adds "Purchase" title to Partner Offer checkout modal - mrsltun

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (adds "Purchase" title to Partner Offer checkout modal - mrsltun)

  Generated by :no_entry_sign: dangerJS against 1af9fc374ae6d460368648a457c55f4570b07183


Unable to run any pool commands

When I try to run any commands with pool, such as pool accounts new [params], I get the following error:
unable to estimate on-chain fees: rpc error: code = Unknown desc = could not query auctioneer terms: insufficient_balance
This is the output of /root/.poold/logs/mainnet/poold.log:
~/.pool/logs/mainnet # cat poold.log
2020-11-20 03:04:23.212 [INF] LLMD: Version: 0.3.3-alpha commit=
2020-11-20 03:04:23.212 [INF] LNDC: Creating lnd connection to [redacted]:10009
2020-11-20 03:04:23.213 [INF] LNDC: Connected to lnd
2020-11-20 03:04:23.765 [INF] LNDC: lnd version: v0.11.1-beta, build tags 'signrpc,walletrpc,chainrpc,invoicesrpc,routerrpc'
2020-11-20 03:04:23.765 [INF] LNDC: Using network mainnet
2020-11-20 03:04:23.765 [INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while
2020-11-20 03:04:24.260 [INF] LNDC: lnd is now fully synced to its chain backend
2020-11-20 03:04:24.433 [INF] LLMD: Auction server address: pool.lightning.finance:12010
2020-11-20 03:04:24.440 [INF] CLDB: Checking for schema update: latest_version=1, db_version=1
2020-11-20 03:04:24.440 [INF] RPCS: Starting trader server
2020-11-20 03:04:24.905 [INF] RPCS: Connected to lnd node [redacted] with pubkey [redacted]
2020-11-20 03:04:25.466 [INF] RPCS: Trader server is now active
2020-11-20 03:04:25.467 [INF] LLMD: Generating TLS certificates...
2020-11-20 03:04:25.467 [INF] LLMD: Done generating TLS certificates
2020-11-20 03:04:25.468 [INF] LLMD: Starting gRPC listener
2020-11-20 03:04:25.469 [INF] LLMD: Starting REST proxy listener
2020-11-20 03:04:25.469 [INF] LLMD: RPC server listening on [::]:12010
2020-11-20 03:04:25.469 [INF] LLMD: REST proxy listening on [::]:8281
2020-11-20 03:07:15.151 [ERR] AUCT: [/poolrpc.ChannelAuctioneer/Terms]: rpc error: code = Internal desc = payment required
2020-11-20 03:07:15.151 [INF] LSAT: Payment of LSAT token is required, paying invoice
2020-11-20 03:07:15.182 [WRN] LNDC: Payment 2149f54cc48d7e9dc960fe0c274c3377eb086b82ca57f70305630c44ba58149b failed: insufficient_balance
2020-11-20 03:07:15.182 [ERR] RPCS: [/poolrpc.Trader/ListAccounts]: unable to query auctioneer terms: insufficient_balance
2020-11-20 03:07:26.281 [INF] LLMD: Get LSAT tokens request received
2020-11-20 03:08:32.517 [ERR] AUCT: [/poolrpc.ChannelAuctioneer/Terms]: rpc error: code = Internal desc = payment required
2020-11-20 03:08:32.517 [INF] LSAT: Payment of LSAT token is required, paying invoice
2020-11-20 03:08:32.552 [WRN] LNDC: Payment 48282cb078b726a364524bf22e06e6a276971a866546833f0a0bb8e1049e8d9d failed: insufficient_balance
2020-11-20 03:08:32.552 [ERR] RPCS: [/poolrpc.Trader/QuoteAccount]: could not query auctioneer terms: insufficient_balance
2020-11-20 03:09:02.400 [INF] LLMD: Get LSAT tokens request received
2020-11-20 03:09:12.168 [INF] LLMD: Get LSAT tokens request received
2020-11-20 03:09:13.580 [INF] LLMD: Get LSAT tokens request received
2020-11-20 03:09:23.133 [ERR] AUCT: [/poolrpc.ChannelAuctioneer/Terms]: rpc error: code = Internal desc = payment required
2020-11-20 03:09:23.133 [INF] LSAT: Payment of LSAT token is required, paying invoice
2020-11-20 03:09:23.165 [WRN] LNDC: Payment c8535c1f496797dde188a815f62e5e96c1d40becb8b963e3176ec8aec1833afe failed: insufficient_balance
2020-11-20 03:09:23.166 [ERR] RPCS: [/poolrpc.Trader/ListAccounts]: unable to query auctioneer terms: insufficient_balance

The documentation is unclear as to whether or not my LND node needs to be funded in the first place, and if so, how much initial funding is needed to allow poold to run properly.

Seems you don't have any channels at all. If you want to be selling channels in the system you'll likely want at least some existing connections, similar case if you'd like to request inbound as well (how can you use that inbound w/o outbound).

@Roasbeef That... does not answer my question/issue.
The quickstart guide does not mention these things at all; What exactly do I need to do, from starting poold to having my LN node funded to whatever else is necessary, so that I can work with pool and poold?

What exactly do I need to do, from starting poold to having my LN node funded to whatever else is necessary, so that I can work with pool and poold?

You should have at least one channel open. The quickstart guide atm assumes you've already been running a lightning node.

This is very good to know, thank you. Is it possible to update the quickstart guide to reflect the need for at least one open channel?

Yes, we should definitely update the quickstart guide. I'm going to create a PR for it shortly.


Step and smoothStep

Hi Brad,   I noticed a "bug" in Apple's metal,  that appears to only effect iPhoneXs (probably iPhoneXr) and possibly iPhoneX, (those newer CPU/GPU chips)   (I'm sure Apple will not call it a bug,  but when you get two devices with different outputs,  then something needs fixed)
if you use smoothstep  or step,  (and possibly many other math functions)  in a metal shader,  and you use this with "half" type rather than a "float" type,  you will get a far different result than if you are say running the code in an iPhone7+ or iPhone6s.
to fix this you can change all smoothstep/step functions form say this below: which you have in some shaders:
half blendValue = smoothstep(half(uniform.thresholdSensitivity), half(uniform.thresholdSensitivity + uniform.smoothing), distance(half2(Cr, Cb), half2(maskCr, maskCb)));

to this:
float blendValue = smoothstep(float(uniform.thresholdSensitivity), float(uniform.thresholdSensitivity + uniform.smoothing), distance(float2(Cr, Cb), float2(maskCr, maskCb)));
and the results are about the same in the iPhone7+ and the iPhoneXs.

Interesting. Could that possibly be the cause of the issue reported here?
https://github.com/BradLarson/GPUImage3/issues/33
I briefly tried to track that one down, without success. Neither Janie nor I have had much free time lately, so we're way behind on this, but I really want to get this going in the next few weeks.

hmm, thought my comment landed here,  here it is again:   very possible that is the issue,   could even be in more than smoothstep/step,  but so far those were the only places I noticed so far.

I did not check to see if it only happens if the input numbers are large or  if the result would be about the same if the inputs are in a more normal range that a "half" could use,   since most all of the time those can vary wildly in what I was using it for.


1.9 release missing

This is caused by https://github.com/kyrus/python-junit-xml/issues/69 and not the fault of conda-forge.

immediate issue fixed using a hack in #2


v1.25.3+k3s1 fails with helm based calico / nginx ingress

version:
v1.25.3+k3s1
(i did not try .0 / 1 / .2 of the 1.25 series yet, i was upgrading from 1.24.4 to 1.25.3 directly, so it might be 1.25 in common)
Node(s) CPU architecture, OS, and Version:
Single node, ubunut 22.04
Cluster Configuration:
single node, 1 server
Describe the bug:
When using 1.25.3 neither calico nor the nginx ingress come up. If i downgrading to 1.24.7, everything works fine again.
Steps To Reproduce:
Install latest (1.25.3)
curl -fL https://get.k3s.io | K3S_KUBECONFIG_MODE="640" INSTALL_K3S_EXEC="server --disable-kube-proxy --disable=servicelb --disable=servicelb --disable-network-policy --flannel-backend=none --disable traefik" sh

When you know install calico / nginx ingress from the official helm charts (latest versions)

https://artifacthub.io/packages/helm/projectcalico/tigera-operator (using v3.24.3, also tried v3.24.2)
https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx (using 4.2.5).

calico and nginx ingress will fail to come up
When you downgrade to 1.24.7 via
curl -fL https://get.k3s.io | K3S_KUBECONFIG_MODE="640" INSTALL_K3S_VERSION="v1.24.7+k3s1" INSTALL_K3S_EXEC="server --disable-kube-proxy --disable=servicelb --disable=servicelb --disable-network-policy --flannel-backend=none --disable traefik" sh

everything will be up and running again.
Expected behavior:
1.25 should work without any issues
Actual behavior:
calico and nginx ingress will fail to come up
Additional context / logs:
calico node
2022-10-31 10:16:15.923 [ERROR][7053] felix/discovery.go 153: Didn't find any ready Typha instances.
2022-10-31 10:16:15.923 [ERROR][7053] felix/daemon.go 323: Typha discovery enabled but discovery failed. error=Kubernetes service missing IP or port

calico operator
2022/10/31 10:16:09 [INFO] Version: v1.28.3
2022/10/31 10:16:09 [INFO] Go Version: go1.18.7b7
2022/10/31 10:16:09 [INFO] Go OS/Arch: linux/amd64
2022/10/31 10:16:39 [ERROR] Get "[https://<IP_ADDRESS>:443/api?timeout=32s](https://<IP_ADDRESS>/api?timeout=32s)": dial tcp <IP_ADDRESS>:443: i/o timeout

nginx logs
-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:       v1.3.1
  Build:         92534fa2ae799b502882c8684db13a25cde68155
  Repository:    https://github.com/kubernetes/ingress-nginx
  nginx version: nginx/1.19.10

-------------------------------------------------------------------------------

W1031 10:16:54.938970       7 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1031 10:16:54.939191       7 main.go:209] "Creating API client" host="[https://<IP_ADDRESS>:443](https://<IP_ADDRESS>/)"

Are you sure that the releases you're using support Kubernetes 1.25? Are you configuring your installation properly? We haven't changed anything between the two minor versions that would prevent Calico from working.
Note that ingress-nginx won't work until the calico CNI is functional.

@brandond calico v3.24.3 is suppose to work with 1.25 - AFAIR k3s (and rke2) bundle with prebuild calico, which will be supported in 1.25 too, right?
So i would assume that calico 3.24.x is supporting k8s 1.25. My configuration does not change from using 1.24 to 1.25, it is applied via terraform. My calico configuration is fairly standard and includes a couple of fixes that have been added to rke2/k3s too
# see https://projectcalico.docs.tigera.io/reference/installation/api#operator.tigera.io/v1.InstallationSpec
# also see https://github.com/rancher/rke2-charts/blob/main/charts/rke2-calico/rke2-calico/v3.22.101/values.yaml for RKE2 defaults
installation:
  controlPlaneTolerations:
    - key: "node-role.kubernetes.io/control-plane"
      operator: "Exists"
      effect: "NoSchedule"
    - key: "node-role.kubernetes.io/etcd"
      operator: "Exists"
      effect: "NoExecute"
  enabled: true
  kubernetesProvider: ""
  calicoNetwork:
    bgp: Disabled
    linuxDataplane: ${dataPlane}
    hostPorts: ${hostPorts}
    ipPools:
      - blockSize: 26
        cidr: ${clusterCidr}
        encapsulation: ${encapsulation}
        natOutgoing: Enabled
        nodeSelector: all()
apiServer:
  enabled: true

certs:
  node:
    key:
    cert:
    commonName:
  typha:
    key:
    cert:
    commonName:
    caBundle:

global:
  systemDefaultRegistry: ""
  clusterCIDRv4: ""
  clusterCIDRv6: ""

felixConfiguration:
  wireguardEnabled: false
  # Config required to fix RKE2 issue #1541
  # @see https://github.com/rancher/rke2/blob/master/docs/known_issues.md#calico-with-vxlan-encapsulation
  featureDetectOverride: "ChecksumOffloadBroken=true"

The errors you show are expected. You are deploying k3s without kube-proxy, so unless you enable something that replaces it (e.g. eBPF), there is no way for pods to reach services. The endpoint https://<IP_ADDRESS>:443 is the kubernetes service (kube-api) and it calico require connecting to it. It should also not work on v1.24.x, unless some old iptable rules remained uncleaned for some reason

UPDATE:
i have seen that my values are outdated, updated them to the latest changes in https://github.com/rancher/rke2-charts/blob/main/charts/rke2-calico/rke2-calico/v3.24.102/values.yaml
installation:
  kubeletVolumePluginPath: "None"

apiServer:
  enabled: true

felixConfiguration:
  healthPort: 9099
  defaultEndpointToHostAction: "Drop"
  failsafeInboundHostPorts: ""
  failsafeOutboundHostPorts: ""
  logSeveritySys: "Info"
  xdpEnabled: true

tolerations:
  - effect: NoExecute
  operator: Exists
  - effect: NoSchedule
  operator: Exists

from the current rke2 templates. I would not say that i see anything responsible but i will try to update my 1.24 based installation with this configuration and if that works, i will try a 1.25 based on and see if that fixed anything

@manuelbuil i'am using BPF here
  calico_dataPlane           = "BPF"
  encapsulation              = "VXLANCrossSubnet"

that is why the kube-proxy is disabled (in both cases_

I was calling it to soon. It was only working before i restarted the node. The it failed as before with the
calico node throwing
2022-10-31 17:21:13.215 [INFO][1773] tunnel-ip-allocator/config.go 60: Found FELIX_TYPHAK8SSERVICENAME=calico-typha
2022-10-31 17:21:13.215 [INFO][1773] tunnel-ip-allocator/config.go 60: Found FELIX_TYPHAK8SNAMESPACE=calico-system
2022-10-31 17:21:13.215 [INFO][1773] tunnel-ip-allocator/config.go 60: Found FELIX_TYPHAKEYFILE=/felix-certs/key.key
2022-10-31 17:21:13.215 [INFO][1773] tunnel-ip-allocator/config.go 60: Found FELIX_TYPHACERTFILE=/felix-certs/cert.crt
2022-10-31 17:21:13.216 [INFO][1773] tunnel-ip-allocator/config.go 60: Found FELIX_TYPHACAFILE=/typha-ca/caBundle
2022-10-31 17:21:13.216 [INFO][1773] tunnel-ip-allocator/config.go 60: Found FELIX_TYPHACN=typha-server
2022-10-31 17:21:13.224 [ERROR][1773] tunnel-ip-allocator/discovery.go 153: Didn't find any ready Typha instances.
2022-10-31 17:21:13.224 [FATAL][1773] tunnel-ip-allocator/startsyncerclient.go 48: Typha discovery enabled but discovery failed. error=Kubernetes service missing IP or port

and the typha server
2022-10-31 17:21:50.395 [INFO][7] watchercache.go 188: Failed to perform list of current data during resync ListRoot="/calico/resources/v3/projectcalico.org/kubernetesendpointslices" error=resource does not exist: KubernetesEndpointSlice with error: the server could not find the requested resource
2022-10-31 17:21:51.395 [INFO][7] watchercache.go 175: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/kubernetesendpointslices"
2022-10-31 17:21:51.397 [INFO][7] watchercache.go 188: Failed to perform list of current data during resync ListRoot="/calico/resources/v3/projectcalico.org/kubernetesendpointslices" error=resource does not exist: KubernetesEndpointSlice with error: the server could not find the requested resource
2022-10-31 17:21:52.399 [INFO][7] watchercache.go 175: Full resync is required ListRoot="/calico/resources/v3/projectcalico.org/kubernetesendpointslices"
2022-10-31 17:21:52.401 [INFO][7] watchercache.go 188: Failed to perform list of current data during resync ListRoot="/calico/resources/v3/projectcalico.org/kubernetesendpointslices" error=resource does not exist: KubernetesEndpointSlice with error: the server could not find the requested resource

So right now, i'am still stuck with the 1.25 upgrade

Just to be on one page, my current configuration looks like this
# see https://projectcalico.docs.tigera.io/reference/installation/api#operator.tigera.io/v1.InstallationSpec
# also see https://github.com/rancher/rke2-charts/blob/main/charts/rke2-calico/rke2-calico/v3.24.102/values.yaml for RKE2 defaults
installation:
  controlPlaneTolerations:
    - key: "node-role.kubernetes.io/control-plane"
      operator: "Exists"
      effect: "NoSchedule"
    - key: "node-role.kubernetes.io/etcd"
      operator: "Exists"
      effect: "NoExecute"
  enabled: true
  kubernetesProvider: ""
## not working right now, maybe we have outdated CRDS, we get
## Error: error validating "": error validating data: ValidationError(Installation.spec): unknown field "kubeletVolumePluginPath" in io.tigera.operator.v1.Installation.spec
# kubeletVolumePluginPath: "None"
  calicoNetwork:
    bgp: Disabled
    linuxDataplane: ${dataPlane}
    hostPorts: ${hostPorts}
    ipPools:
      - blockSize: 26
        cidr: ${clusterCidr}
        encapsulation: ${encapsulation}
        natOutgoing: Enabled
        nodeSelector: all()

apiServer:
  enabled: false

certs:
  node:
    key:
    cert:
    commonName:
  typha:
    key:
    cert:
    commonName:
    caBundle:

# Tolerations for the tigera/operator pod.
tolerations:
- effect: NoExecute
  operator: Exists
- effect: NoSchedule
  operator: Exists

nodeSelector:
  kubernetes.io/os: linux

global:
  systemDefaultRegistry: ""
  clusterCIDRv4: ""
  clusterCIDRv6: ""

felixConfiguration:
  wireguardEnabled: false
  # Config required to fix RKE2 issue #1541
  # @see https://github.com/rancher/rke2/blob/master/docs/known_issues.md#calico-with-vxlan-encapsulation
  featureDetectOverride: "ChecksumOffloadBroken=true"
  healthPort: 9099
  defaultEndpointToHostAction: "Drop"
  failsafeInboundHostPorts: ""
  failsafeOutboundHostPorts: ""
  logSeveritySys: "Info"
  xdpEnabled: true

with

dataplane being BPF
and encapsulation being VXLANCrossSubnet

I guess the most reasonable (again) thing to be falsy is eBPF

One thing that I'm missing is the place where you set the kube-api endpoint to Calico, so that it does not fall back to <IP_ADDRESS>, are you doing that somewhere? According to the Calico docs:
kind: ConfigMap
apiVersion: v1
metadata:
  name: kubernetes-services-endpoint
  namespace: tigera-operator
data:
  KUBERNETES_SERVICE_HOST: "<API server host>"
  KUBERNETES_SERVICE_PORT: "<API server port>"

@manuelbuil i;am setting this value when installing calico yes
# only needed in BPF mode
resource "kubernetes_config_map_v1" "ebpf" {
  count = var.dataPlane == "BPF" ? 1 : 0
  metadata {
    name      = "kubernetes-services-endpoint"
    namespace = "tigera-operator"
  }
  data = {
    KUBERNETES_SERVICE_HOST = var.kubernetes_api_external_ip
    KUBERNETES_SERVICE_PORT = "6443"
  }
  depends_on = [helm_release.calico]
}

Currently the value is (on 1.24)
data:
  KUBERNETES_SERVICE_HOST: <IP_ADDRESS>
  KUBERNETES_SERVICE_PORT: '6443'

(it is an AWS box, thus the private "external ip")
Are you expecting this to be the issue?

In the meantime, i fixed the issue by polishing / aligining the calico installation, fixing it's namespace and other glitches.
I also had an issue PGO 5.0.3 which was not 1.25.0 compatible (on top of that).
I upgraded all that and then the update to 1.25.5 went really smooth.
Can i suggest to close this issue (it is not valid)


The anonymous donations should be counted in number of contributors

Based on Griff comment, the anonymous donations should be counted in number of contributors
As you can see in below pic there is 1 unique donor if the anonymous donations aren't counted
but based on new requirment the anonymous should be counted

cc: @mohammadranjbarz @Meriem-B

We don't know how many anons are those, so I don;t think it's a good idea.

We don't know how many anons are those, so I don;t think it's a good idea.

I infer form Griff's comment that every anonymous donation should be counted as a one unique contributor


Revise counter-intuitive invite link design

The current design of invite links for Supabase immediately invalidates the link after first opening, which is counter-intuitive and confusing for users. It would improve the user experience to have a more intuitive design, such as allowing for multiple uses or providing an option to resend the invite link or having a time-limited design, such as expiring after one week.

@kiwicopple
I understand that the one-time use of the invitation link is a security feature, but it can also cause confusion for users. In normal system design, the invitation link should not pose any security risks. I suggest re-evaluating the design to find a balance between security and user experience. Instead of limiting the use of the invitation link to one time only, other measures  can be implemented to ensure security without causing confusion for users.

Hi @gaodeng, it would be great if you can share your usecase on why you require your users to click on the invite link more than once? We strive to design an API that's both secure by default and user-friendly and like most software systems design, it always requires a tradeoff. I believe a possible solution here would be to show to the user a clearer error message so that they know that the invite link has been used already or if they need to request for another one.

Hi @kangmingtay
The restriction on only being able to click the invite link once does not align with user expectations, as most other systems do not have such a limitation.


[Crash] when the server try to read a chunk data

https://paste.gg/p/anonymous/87fe38d23bf54453bc749186bd71d898
Java 21, minecraft 1.20.4
Nether world entity caused server crash, do you please know what could cause the crash or how to prevent this.
Thank you!

This server is not running LinearPurpur, please try to reproduce this with LinearPurpur and see if the issue still persists, otherwise, please report it to Leaf's GitHub repository.


extra space when figure size is big

running plt.imshow(img) outputs low quality images (when original image is better)
try the following code:
# %% prep
import numpy as np
import cv2
from matplotlib import pyplot as plt

# this is only for jupiter notebooks, no need in regular IDE plotting
# plt.rcParams['figure.figsize'] = [100, 50] # just for resizing output images later

def get_image_from_url(url):
    import os
    import urllib

    file_name = os.path.basename(url)
    urllib.request.urlretrieve(url, file_name)
    img = cv2.imread(file_name)
    img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
    return img

bikes_url = "https://upload.wikimedia.org/wikipedia/commons/3/3f/Bikesgray.jpg"
img = get_image_from_url(bikes_url)
plt.imshow(img)

outputs:

and it's the same also in "Plots" mode:

current workaround is adding at the start of the script:
plt.rcParams['figure.figsize'] = [100, 50] # just for resizing output images later
and then the outputs is relative high quality**, and also the image is scaled to ipython screen (a good feature that isn't happening in google colab for example)**

but we get a lot of unused space:

I assume that this is because of matplotlib, not VScode, but can you fix the bug of extra space when figure size is big?

This has been fixed for the next release. It's a dupe of #6724


No tests found.

Hello, I'm seeing a No Tests Found message for the following spec:
# frozen_string_literal: true

require "rails_helper"

RSpec.describe Collections::Foodiverse::WaitlistCollectionAdvertiserService do
  describe "Constants" do
    it { expect(described_class.const_defined?(:BODY_MESSAGE_KEY)).to be true }
  end
end

Running rspec via the terminal results in:
Finished in 0.37423 seconds (files took 7.58 seconds to load)
1 example, 0 failures

Randomized with seed 556

Do you know if there is support for the short it syntax?
I'm using Neovim nightly and the latest version of the plugin.
Thank you again for the time you've put in to developing this plugin, I use it pretty much every day.

Interestingly, I also get no tests found when i use a normal it message block syntax:
RSpec.describe Collections::Foodiverse::WaitlistCollectionAdvertiserService do
  describe "Constants" do
    it "is there" do
      expect(described_class.const_defined?(:BODY_MESSAGE_KEY)).to be true
    end
  end
end

That's very weird. I've copied the code from your initial post and detected the test.
Obvious question, is there a Gemfile, .rspec or .gitignore file present and are the tests ending in _spec.rb?
Finally if you open /Users/{YourName}/.local/state/nvim/neotest.log and try and run Neotest, you should see some output. Could you share that?

I also have this issue but don't have the log file you specified:
$ cat /Users/$(whoami)/.local/state/nvim/neotest.log                                           │~
cat: /Users/pat/.local/state/nvim/neotest.log: No such file or directory

Could you check the share did? Wonder if I made a mistake and autocorrected to state. I'm not at a laptop at the moment.
Also, any chance you guys could share a repo that displays this bug that I can clone and test with?

I've pushed a fix. I think the nested describe statements were scuppering this. However I've almost certainly broken #21 and specs which have no context

I also have this problem:
require 'rails_helper'

RSpec.describe User, type: :model do
  it 'works' do
    expect(1).to be_a(Numeric)
  end
end

Then run:
:lua require('neotest').run.run()

No tests found

I just can't recreate these No tests found unfortunately. If I plug your code into the playground with the treesitter queries I get the expected outcome:

@natematykiewicz - Can you share any more details about the repo or the test itself? Can you enable debugging in Neotest and share the outputs of /Users/Oli/.local/state/nvim/neotest.log?

I somehow didn't have the ruby treesitter installed. TSInstall ruby fixed my problem. Sorry to bother you.

Is there a way for it to realize you don't have the Ruby TreeSitter installed and suggest to you the right command to run to install it? Because that'd be an awesome UX.

Is there a way for it to realize you don't have the Ruby TreeSitter installed and suggest to you the right command to run to install it? Because that'd be an awesome UX.

I'm sure there is but I imagine it would be messy to check if it's installed depending on the user OS etc. I should add an issue template which asks the user to run checkhealth instead.
@prdanelli - Any luck at trying the latest commit?

I think the issues I was having might have been around naming the file "test.rb" the renaming it "test_spec.rb" and trying to run the tests before reopening the file. I've tested that scenario and it works perfectly now.

Appreciate the feedback thanks. I will update the readme at some point to save others some time

I somehow didn't have the ruby treesitter installed even though I did the other day. TSInstall ruby fixed my problem. Sorry to bother you.

This resolved my issue as well even though I had it listed in my 'ensure_installed' section.

@prdanelli 's suggestion fixed my issue. This seems like something that'd be good to mention in the README somewhere. Granted not many people probably have spec files that don't end in _spec.rb, but still

Thanks for the prompt. I've updated the readme to reflect this.


Issue/17 switch default break missing

Closes #17

@paulirwin I considered adding unit tests but there are not really a test set-up yet so it's hard to progress on it.


help

help to get the hack 1v1.lol email me<EMAIL_ADDRESS>

I don't do email support, sorry.
There's a video in the README that you can watch


Cannot use column names with dots in them

When running the following code:
package main

import (
    _ "github.com/go-sql-driver/mysql"
    "github.com/jinzhu/gorm"
    _ "github.com/lib/pq"
    _ "github.com/mattn/go-sqlite3"
)

var db *gorm.DB

type Test struct {
    Id int
    A text `gorm:"column:test.a"`
    B text `gorm:"column:test.b"`
}

func init() {
    var err error
    db, err = gorm.Open("postgres", "user=username dbname=password sslmode=disable")
    if err != nil {
        panic(err)
    }
    db.LogMode(true)
}

func main() {
    db.CreateTable(&Test)
}

I get the following error:
(pq: syntax error at or near ".")

Looking at the database log we see that:
ERROR:  syntax error at or near "."
STATEMENT:  CREATE TABLE "tests" ("id" serial,"test"."a" text,"test"."b" text , PRIMARY KEY ("id"))

Which is clearly wrong, we want a statement like:
CREATE TABLE "tests" ("id" serial,"test.a" text,"test.b" text , PRIMARY KEY ("id"))

The offending code seems to be in scope.go:71
func (scope *Scope) Quote(str string) string {
	if strings.Index(str, ".") != -1 {
		newStrs := []string{}
		for _, str := range strings.Split(str, ".") {
			newStrs = append(newStrs, scope.Dialect().Quote(str))
		}
		return strings.Join(newStrs, ".")
	}

	return scope.Dialect().Quote(str)
}

Removing the if-statement makes gorm generate the correct statement, but I don't know if it would break anything else.

I think dot . is not valid column name ?

It is a valid column name in postgresql at least, it just needs to be
quoted. e.g.
CREATE TABLE test("field.with.dots" INTEGER)

On Tue, 18 Apr 2017 at 11:21, Jinzhu<EMAIL_ADDRESS>wrote:

I think dot . is not valid column name ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jinzhu/gorm/issues/1280#issuecomment-294742640, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPVBVO62qDYYdJ7cUtWibFYwSnX8RMTks5rxICugaJpZM4LOk_L
.

I think GORM can't support it like this, as the dot . has other meaning in other databases...

AFAIK dots are allowed as column names in at least Postgres, MySQL and sql server.  I think SQLite supports them too. They always need to be quoted though.

A similar issue occurs when creating a table in postgres where one needs to specify the schema in a database. e.g.
func (u *User) TableName() string {
	// custom table name, this is default
	return "testdb1.users"
}

"testdb1" is the schema and "users" is the table name.
The error log is:
[2017-08-29 11:04:07]  [49.02ms]  CREATE TABLE "testdb1"."users" ("id" serial,"created_at" timestamp with time zone,"updated_at" timestamp with time zone,"deleted_at" timestamp with time zone,"username" VARCHAR(255),"last_name" text,"first_name" text,"role" text,"count" serial,"birthday" timestamp with time zone,"age" integer , PRIMARY KEY ("id"))
[0 rows affected or returned ]

(/Users/dfarago1/goprojects/src/github.com/defgolang/wstest1/datamodel/user.go:41)
[2017-08-29 11:04:08]  pq: syntax error at or near "."

How does one deal with this problem, as a Postgres database may have several schemas in a single database?


The interactive console is not rendering IO interactions as expected

Describe the bug
I was so happy that DiddiParser2 was getting well-stablished. I updated my Git clone and then ran the interactive console via diddiscript-console. I typed some commands, but noticed that interactions between user/script are not working.
I can confirm that this only happens with the interactive console, because the rough diddiparser2 command works fine.
To Reproduce
Steps to reproduce the behavior:

Go to an updated Git local clone of this repo
Type nox -s generate-console (this will create an interactive console)
Type the following code:

load_module("simpleio");
print_text("Some text that should be shown");
store_input("Some text displayed to get user inputs");

See error. You will see that no such action will happen.

Expected behavior
This should work like the file parser (diddiparser2), and show some kind of interaction.
Additional context
I remember that this worked before, so I think we made a regression.
Output:
C:\Users\Diego Ramirez\Development\diddiparser2>nox -s generate-console
nox > Running session generate-console
nox > Creating virtual environment (virtualenv) using python.exe in .nox\generate-console
nox > python -m pip install -e .
nox > Generating a DiddiScript console...
nox > diddiscript-console

Welcome to the interactive DiddiParser console.
Parser version: 1.0.0
============================================================

> load_module("simpleio");
> print_text("Some text");  !# this should print "Some text" inmediately
> ^Z
nox > Session generate-console was successful.

I suppose the error could be here:
https://github.com/DiddiLeija/diddiparser2/blob/b4df2f81e1942d5fc853c6772423aa4fd2eda202/diddiparser2/parser.py#L270-L287
Or maybe a bit further.

Oh, I found the issue. Seems like the interactive console had compile_only = True. That made the console to skip the executions.


i have a issue .Can you help me

Hai,
I have downloaded your package.b ut it's not working well .i will replace the client key, secret key and redirect URL in my webconfig.but it is not showing access token button. always show like this in my endpoint..
Callback
Code: none
State: 8942b5ae05334c32ab415de6b0e5e91d (valid)
RealmId: none
Error: invalid_scope

Hi ,  Can you please check what is the scope you provided and is your app connected to that scope?


Item model

Item Model is ready to use but I have a problem with "search" function in when i want to fetch the data array.

This PR includes the already merged customer related commits. You should rebase this PR on master.
Also, about the search, leave that to another PR.


Custom Template does not work (in Version 2.1.7)

Hi Norm,
i had to change the Headline for Chapters. For the first two chapters i want no token before the content. I took quite a while for me to understand that i have to create a custom localization (because i thought that localization is somehow related to translation from english to the german or other languages. Changing the headline format is not a matter of translation, so why should i look in the configuration file for the german language? But now i understand that localization also means configuation for my place.)
I followed the instructions in section 4.4.2: "Overriding mappings, groups, etc." of the reference Guide and created an custom localization like this:
<xsl:variable name="v:custom-localizations" xmlns:l="http://docbook.org/ns/docbook/l10n"
        xmlns:lt="http://docbook.org/ns/docbook/l10n/templates">
        <locale xmlns="http://docbook.org/ns/docbook/l10n/source" language="de"
            english-language-name="German">
            <group name="title-numbered">
                <template match="self::db:chapter[count(preceding-sibling::db:chapter) lt 2]">
                    <label/>
                    <separator/>
                    <content/>
                </template>
            </group>
        </locale>
    </xsl:variable>

But it had no effect at all. I am not sure, maybe i had some namespace related errors in my file. However, i tried to understand the mechanism of adding custom templates into the default templates,
I think there is (or has been in 2.1.7) a bug in xform-local.xsl with templates in the mp:expand-l10n-template mode.
It did not handle the elements within the customized template the way i would expect. There was also an unconditional xsl:message. I took this as a sign that this code fragment is work in progress.
I made some changes, and now it works for me. Maybe you can have a look at the attached file.
I tried to fork the repo so that you could pull, but i did not dare to do so. I don't understand the build mechanism (i use only the xslt part of the releases in my project), so i thought it is safe to send you the one isolated file).
xform-locale.zip
Greetings,
Frank

Well, i have tried again with a fresh installation of 2.1.9 and carefuilly reading of the instructions. Everything works fine.
I'm afraid I got tangled up somehow. However, i will close this issue.
Greetings, Frank


Refactor to use addon css

Surely we can refactor to use css classes and pack a css file with the addon.
As an added bonus, the current "responsiveness" placing two charts next to eachother can start responding to resize events.
PS. There's a advent-of-code-charts channel in the contributing.today Discord where I'll be if anyone has hacktoberfest-related questions!

This is a good candidate... if a 2023 edition of AoC will happen. Will revisit this issue in fall when we know more.

In #94 a start was made, some of the newer features were done with a CSS file. We can build on that.


Keep Spark version in a single place only (BeamModulePlugin)

It's a bit of a trap to have the Spark version in two places.
Especially because it's most obvious to change the one in the Spark build.gradle. But that one is always overruled by the one used in the artifact library in BeamModulePlugin.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aromanenko-dev

Retest this please

Run Spark StructuredStreaming ValidatesRunner

Run Spark ValidatesRunner

Run Java_Debezium_IO_Direct PreCommit

Run Portable_Python PreCommit


Error responses need to clean up response headers and body before replying

Potential issue. Should also clean halt at the same time if we're doing that.

any updates for this?

Done in my local copy. Push soon!


[NASA VEDA] Do a round of home directory cleanup

As a part of https://github.com/2i2c-org/infrastructure/issues/4858, we should do a round of asking users to clean up their home directories so we don't copy stuff that's not needed.
Definition of Done

[ ] Heavy users of home directory space are contacted and asked to clean up
[ ] We have a reduction in total home directory usage

Resources
https://grafana.nasa-veda.2i2c.cloud/d/688c04dba0500904/home-directory-usage-dashboard?orgId=1 has list of users. We should at least contact everyone who has more than 100G

Note that this is primarily going to be done by the science support team at NASA VEDA (@wildintellect and co) rather than 2i2c.

We managed to get everyone under 200 GB. There are 4 people over 100GB but I only directly know 1 of them. Do we call that good enough even though it would increase the cost significantly?


Fix scanning when no commits are found

I'm not sure whether this still is a problem after the changes done in #11:
https://github.com/dbschenker/contribution-checker/blob/24369a5cb72562709196ffd4a62be61a34ada666/contribution_checker/_commits.py#L173-L185


Poor performance

Issue Type: Performance Issue
I am facing poor performance from VS code while running my jupyternotebook. Strange that it even cannot run a single cell with only one line of code.
Very poor experience.
Any help will be appreciated.
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.55GB (8.47GB free)

Process Argv
--crash-reporter-id 0a2c520f-733f-4c67-a648-75f12c4ca82b

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    98	 14224	code main
    0	   136	  1096	   extensionHost
    0	   212	 14392	     "C:\Users\Eldhose\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node c:\Users\Eldhose\.vscode\extensions\ms-python.vscode-pylance-2022.1.5\dist\server.bundle.js --cancellationReceive=file:fcbee996a7614204cd260c9101de29c576f1948c2c --node-ipc --clientProcessId=1096
    0	   222	 14408	     "C:\Users\Eldhose\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node c:\Users\Eldhose\.vscode\extensions\ms-python.vscode-pylance-2022.1.5\dist\server.bundle.js --cancellationReceive=file:2eff5581a9bd31799308b53bf97e247558b591ccf7 --node-ipc --clientProcessId=1096
    0	    16	 14996	     C:\Users\Eldhose\anaconda3\envs\adsml\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
    0	   110	  5344	       electron_node hl.js
    0	    10	 14956	       console-window-host (Windows internal process)
    0	   259	 15124	     "C:\Users\Eldhose\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node c:\Users\Eldhose\.vscode\extensions\ms-python.vscode-pylance-2022.1.5\dist\server.bundle.js --cancellationReceive=file:a01677a8ce9bd41e0ca684557db96e6304c7064e69 --node-ipc --clientProcessId=1096
    1	    85	  6968	   issue-reporter
    0	    36	  8564	   utility-network-service
    0	   184	 10984	   gpu-process
    0	    96	 13384	   shared-process
    0	    72	  1348	     watcherServiceParcelSharedProcess
    0	    78	 13600	     ptyHost
    0	     6	  5532	       console-window-host (Windows internal process)
    0	    65	 10712	       C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
    0	   175	 13616	   window (Settings - project-adsml-ibex-c1-s1-4946-3104 - Visual Studio Code)
    0	    87	 13780	   window (undefined)
    0	    24	 14300	   crashpad-handler

Workspace Info
|  Window (Settings - project-adsml-ibex-c1-s1-4946-3104 - Visual Studio Code)
|    Folder (project-adsml-ibex-c1-s1-4946-3104): 59 files
|      File types: csv(34) ipynb(7) json(4) txt(2) yml(1) PNG(1) py(1) pyc(1)
|                  md(1) xls(1)
|      Conf files: onedrive(1);

Extensions (5)

Extension
Author (truncated)
Version

python
ms-
2021.12.1559732655

vscode-pylance
ms-
2022.1.5

jupyter
ms-
2021.11.1001550889

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.4

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392cf:30425750
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30429731
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30428979
pythonvs932:30410667
vscop341:30404997
vsrem710cf:30416617

@EldhosePoulose can you provide us some repro? such as ipynb file that shows the issue?

also, if possible, can you provide us log as described here - https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
for notebook, there will be multiple logs from pylance server in output window, can you provide us logs from all those output window? any log related to pylance should have python or pylance in the output window name.

(pyright 90161194) starting
[Info  - 4:53:36 PM] (12613) Server root directory: /Users/pouloeld/.vscode/extensions/ms-python.vscode-pylance-2022.4.2/dist
[Info  - 4:53:37 PM] (12613) No configuration file found.
[Info  - 4:53:37 PM] (12613) No pyproject.toml file found.
[Info  - 4:53:37 PM] (12613) Setting pythonPath for service "Desktop": "/usr/local/bin/python3"
[Warn  - 4:53:37 PM] (12613) stubPath /Users/pouloeld/Desktop/typings is not a valid directory.
[Info  - 4:53:38 PM] (12613) Assuming Python version 3.9
[Info  - 4:53:38 PM] (12613) Assuming Python platform Darwin
[Info  - 4:53:40 PM] (12613) Searching for source files
[Error - 4:53:50 PM] (12613) Enumeration of workspace source files is taking longer than 10 seconds.
This may be because:

You have opened your home directory or entire hard drive as a workspace
Your workspace contains a very large number of directories and files
Your workspace contains a symlink to a directory with many files
Your workspace is remote, and file enumeration is slow
To reduce this time, open a workspace directory with fewer files or add a pyrightconfig.json configuration file with an "exclude" section to exclude subdirectories from your workspace. For more details, refer to https://github.com/microsoft/pyright/blob/main/docs/configuration.md.
[Info  - 4:54:05 PM] (12613) Found 438 source files
[Info  - 4:54:05 PM] (12613) Background analysis(1) root directory: /Users/pouloeld/.vscode/extensions/ms-python.vscode-pylance-2022.4.2/dist
[Info  - 4:54:05 PM] (12613) Background analysis(1) started
[Info  - 4:54:09 PM] (12613) [BG(1)] Long operation: checking: /Users/pouloeld/Desktop/_NotebookConcat_84aa233e9b4c.py (2180ms)
[Info  - 4:54:09 PM] (12613) [BG(1)] Long operation: analyzing: /Users/pouloeld/Desktop/_NotebookConcat_84aa233e9b4c.py (3003ms)

After executing the first cell, does it still take a long time? Could it be taking a long time to load the kernel?

Closing old issue. If this is still a problem, please reopen with the information requested. thanks


Allow output bucket specification / minio egress

What is the ask?
I think it would be useful to allow the specification of an output bucket to separate the pipeline name and the data-repository handling.
An alternative would be to support minio as an egress destination.
What is the goal / desired outcome?
So that I can accomplish my goal to save results of my pipeline in a separate bucket so that other users can have access to it.
If there is a way to accomplish this today via workaround, what does that require?

Adding the docs label to clarify our docs a bit better as requested by @David-Development

We should probably accept something like:
"egress": {
    "URL": "s3api://<endpoint>/bucket/dir"
}

Specifying the endpoint in the storage secret will make it hard to egress to multiple endpoints, and just moves the information farther away from where it's actually used which will make it harder to understand / audit.


Improving Documentation: Touching upon the nova command while editing terraform script for Kubernetes bootstrap

In the Kubenow guidelines, It might be worthy to give users some extra tip and info on how to get the external_network_uuid or the list of all currently configured flavor when it comes to modify the terraform.tfvars file
HINT:

nova network-list (to get external uuid)
nova flavor-list

Great!


Are these libraries still under development?

I've been using Rx.NET (and Ix.NET in some projects) since 2014 and really like the programming model. But the last commit here was around 2 years ago. Current issues are discussed among users, pull requests seem to not get merged anymore. And the milestones are all overdue a long time now. I've also not really seen usage of the reactive extensions in other Microsoft products. So is it still being developed? Would you still use it in new projects or is it safer to try to adapt a different programming style, like System.Threading.Channels or plain async/await and IAsyncEnumerable?
 I'm genuinely concerned that the library is slowly being abandoned/already has been silently. But I've also just taken a look at this repo now and am a bit concerned by its state.

On IAsyncEnumerable - have you seen this video? Supporting IAsyncEnumerable with LINQ - https://www.youtube.com/watch?v=Ktl8K2b1-WU
TPL DataFlow is also a great thing to investigate and it interops with Rx very nicely.

I think the usual dilemma of OSS ("why isn't this project maintained") only partially applies here, because this repo in particular

originated from within Microsoft
is under the dotnet foundation umbrella and
mentions a "core team" on it's readme (which - disclaimer - I was included in)

and so might give the impression that there is a number of people (maybe even perceived to be with Microsoft) maintaining Rx (possibly even as part of their day jobs).
But there is not.
The last major activity was around 2018/2019 when @ghuntley managed to gather some people around who subsequently did some major rewrites of the Rx operators towards performance and memory-consumption. Occasionally, bugs were fixed and pull requests merged. Requests for new operators were and are usually referred to @akarnokd's extension library. I cannot speak for other contributors, but my efforts were mostly done on company time because we had a major interest in performance gains and lower memory pressure. We met the objective, that's when my efforts in OSS moved on (again, I don't know about anybody else).
This is open source software. If there is concern about the future of this project I'd kindly ask anybody who is serious about this to step up. If anybody would like to volunteer, I'd suggest they ping @clairernovotny and ask for write-access. Although I do have write access to this repo, I wouldn't want to make the decision of onboarding new maintainers solely by myself.
As for Rx.Async: AFAIK the code is clean and pretty and functional, but there's no unit tests. Unfortunately, no unit tests no release.

I did my contributions back in the day too but I haven't done anything since for two reasons: 1) I have zero understanding of the .NET infrastructure behind the project, 2) there seems to be no one left to make decisions about features. So when I rarely need something Rx.NET, I do it myself in my own project.

I don't agree that a project, like Rx, should be archived once active development ceases. I also don't agree that Rx should be 'ripped' out of code bases. The concept of Rx.NET (and reactive programming in general) is still valid and powerful, the implementation is extensive, performant, the operators match those of LINQ (AFAIK) and it's reasonably bug free.

I suggest, to make an announcement to archive this project beginning next year if no new maintainers come up until then so that people know that this is not going to be developed any further.

Disagree.

Also looks like I have to rewrite a number of code bases in the future and rip this library out :/

Alternatively you could step up and help?

And what is the alternative if we drop RX? there is nothing similar, RX is more like a programming model as you mentioned than a lib. As far as updates, note they come with pain. So, unless they give me crypto for free is really hard to update and risk changing the behviour of my systems.

I fell in love with RX because it allowed me to model systems as networks
of asynchronous event streams.  I thought it was a wonderful abstraction.
Is Apostolis correct that there is nothing similar?  If there is, can
someone give me a pointer?  Thanks.
On Thu, Oct 20, 2022 at 9:20 AM Apostolis Bekiaris @.***>
wrote:

And what is the alternative if we drop RX? there is nothing similar, RX is
more like a programming model as you mentioned than a lib. As far as
updates, note they come with pain. So, unless they give me crypto for free
is really hard to update and risk changing the behviour of my systems.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/reactive/issues/1822#issuecomment-1285829083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ6ZGLDOYVIXF2SPCD6YFWDWEFWN5ANCNFSM6AAAAAARJPQHHQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@danielcweber @akarnokd first of all, I want to say thank you so much for your careful steering of Rx in the last few years. Rx has remained critical for the infrastructure behind our visual programming language for 10+ years, and this will not change, so like last time I will always be happy to step up as a contender for maintainer if no one better suited is interested in taking up the mantle, so we can resolve the issue that no one is available to offer dedicated maintenance.
I agree there is nothing like it, and several other projects depend on it. However it does look like it is going to potentially go through cycles of maintainer renewal, as happened in the past. Maybe it is time to write down some guidelines and criteria on the expectations for releases and maintainers?

What is your "visual programming language"?
Thanks!
On Thu, Oct 20, 2022 at 1:06 PM glopesdev @.***> wrote:

@danielcweber https://github.com/danielcweber @akarnokd
https://github.com/akarnokd first of all, I want to say thank you so
much for your careful steering of Rx in the last few years. Rx has remained
critical for the infrastructure behind our visual programming language for
10+ years, and this will not change, so like last time I will always be
happy to step up as a contender for maintainer if no one better suited is
interested in taking up the mantle, so we can resolve the issue that no one
is available to offer dedicated maintenance.
I agree there is nothing like it, and several other projects depend on it.
However it does look like it is going to potentially go through cycles of
maintainer renewal, as happened in the past. Maybe it is time to write down
some guidelines and criteria on the expectations for releases and
maintainers?
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/reactive/issues/1822#issuecomment-1286078134,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ6ZGLGVUPTKYHMVDNAIIPDWEGQ4DANCNFSM6AAAAAARJPQHHQ
.
You are receiving this because you commented.Message ID:
@.***>

I'd also like to thank all the contributors for their hard work over the years. Rx has been a great way to model libraries and applications. Regarding stepping up as maintainer I - personally - just do not have the free time and mental resources to be a maintainer for any project anytime soon. I suggested to publicly archive this repo to signify that active development has ceased, as it clearly seems that way and is the de-facto standard to convey this info on Github. So that people don't open issues or PRs because they think it's still being actively maintained. Read the open issues: There are several where people gave up frustratedly because they don't get feedback from maintainers or their PRs just hang around, because they get the impression that this is a live project. Making this a public archive would be the honest way in MY opinion. That would also not mean that the project has become unusable, just that there is no active development anymore. Technology progresses quite fast in the .NET realm these days and Rx will become stale one day.
At least post an announcement (pinned issue) that this project is not being actively developed anymore and that you are looking for people who want to get into that role. Might get to the right people and find you some capable volunteers. And it would convey the info that PRs and issues might not be answered. It would just be honest to the community.

Update: new maintainers incoming https://github.com/dotnet-foundation/projects/issues/229#issue-1419815237

This is so great to hear! Thanks @HowardvanRooijen and others! I'm closing this issue now.

Please see https://github.com/dotnet/reactive/discussions/1868 for the current high level plan.