Service Discovery Links Not Updating

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
After upgrading to rancher 2.2, DNS Service Discovery links are not created or updated.
Add Record in Service Discovery that points to a Workload
$ kubectl get service -n shiftreport
NAME            TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)
database        ClusterIP   None         <none>        42/TCP
database-test   ClusterIP   None         <none>        42/TCP

Result:
Logs are spammed with:
kubectl logs --namespace=kube-system $(kubectl get pods --namespace=kube-system -l k8s-app=kube-dns -o name | head -1) -c kubedns
...
I0401 07:55:58.537184       1 dns.go:601] Could not find endpoints for service "database" in namespace "shiftreport". DNS records will be created once endpoints show up.
I0401 07:55:58.537209       1 dns.go:601] Could not find endpoints for service "database-test" in namespace "shiftreport". DNS records will be created once endpoints show up.

Other details that may be helpful:
Worked fine before upgrading to 2.2
Update 1: Adding Type=Selector works fine, but not Type=Workload
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.0
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Hosted
Machine type (cloud/VM/metal) and specifications (CPU/memory): VM
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:      17.03.2-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 02:31:19 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.2-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 02:31:19 2017
 OS/Arch:      linux/amd64
 Experimental: false

@sangeethah can you try to reproduce the issue

Tested the following scenario in a HA setup upgraded from 2.1.6 to 2.2.0.
In existing cluster,
Create a workload - wkl1.
Create a DNS Record - say - test1-dns by choosing "One or more workloads" option pointing to wkl1.
DNS resolution for test1-dns  works as expected. It resolves to all pods of the workloads it is pointing to as expected.
root@testclient-667fc9ccfb-jkdsg:/# dig test1-dns.mytest1.svc.cluster.local  +short
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
root@testclient-667fc9ccfb-jkdsg:/#

We do see these errors in kube-dns , but there should be retries that would succeed.
I0401 18:12:10.609808 1 dns.go:601] Could not find endpoints for service "test1-dns" in namespace "mytest1". DNS records will be created once endpoints show up.
I0401 18:12:10.618171 1 dns.go:601] Could not find endpoints for service "test1-dns" in namespace "mytest1". DNS records will be created once endpoints show up.
I0401 18:12:21.678728 1 dns.go:601] Could not find endpoints for service "testclient" in namespace "mytest1". DNS records will be created once endpoints show up.

@danielbjornadal In your case , Does DNS resolution for "database-test" fails ? Does the DNS resolution for "database" work?
The error seen in kube-dns happens once but it should have retried and succeeded. Do these errors seen in kubedns stop for you?

@sangeethah
DNS to database and database-test does not work.
All Workload Service Links that where created before the upgrade works.
All Workload Service links that are created after the upgrade does not work.
All Selector Service Links created after the upgrade works.
Before the upgrade, creating a new workloadwould automatically create a Workload Service Link to that Workload. This does not happen in 2.2.0.
Our Rancher are managing 3 separated clusters. One have different K8s and Docker Version than the others (v1.13.4 & 18.06.3-ce), and all have exactly the same problem.
Two of the clusters is in the same /24 network as Rancher.
All kube-dns Workloads all report the same errors as mentioned in the original post. 1 every 5 minutes.

@danielbjornadal where exactly do you see this error The target type cannot be Workload.?

@danielbjornadal If you're still facing this issue, can you help answer the questions posed. Our QA team has not been able to reproduce.

We have upgraded to Rancher 2.2.4, and are no longer experiencing this issue.


Add support for resolving conflicting actions using URL fragments

I have several APIs that use the same URL and method but disambiguate based on the request content-type. This causes conflicts in the generated swagger document. The current pattern using ConflictingActionsResolver only allows you to choose which operation to use rather than providing a mechanism to support both. A common pattern for resolving this is to use URL fragments to force the key to be unique. One approach would be to use the operation ID as the fragment. The approach that I took here is to just use an incrementing index on conflicting actions. I added tests to ensure that it behaves as expected but I am certainly open to other approaches to disambiguating the paths.

@smbecker thanks for submitting this. I'd like to understand the problem a little better before discussing solutions and figure out if there's another way to describe these operations using OpenAPI's native support for media types rather than tacking on meaningless path fragments.
Could you please create a corresponding issue that describes the problem with as much detail as possible, including code/JSON examples, so we can talk through potential options. Then, when we're agreed on an approach we can link a new PR to that issue.


bug in extract_POS()

I finally got the code working. The extract_POS code in main_NER.py has this logic which picks up a start_pos. It ends up making terms_arr blank after that point, and nothing was working.
I don't know the reason for the start_pos being there, but that was the bug that killed everything.

That is my fault. It was a nasty hack as I mentioned in the comment, where I parse the text output of a service that should ideally be sending back json. I will fix it. Glad it works for you now.


Restoring missing segments broken with compaction

Compacting segments is not deterministic so nodes could have differing segments. The old method of requesting sstables over grpc doesn't work anymore.

One idea is to apply compaction from raft so that every node compacts the same way.


Documentation on identifying objects after the removal of slugs

Closes: #4303
What's Changed

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

In the Primary Keys Versus Natural Keys section, maybe a note that primary keys might be different across environments (e.g. dev vs prod) while natural keys are predictable?

I found this documentation to be very helpful, it:

Explained what the existing solution was
Explained what the reasons were from changing
What the drawbacks are for the changes
How to use the two new concepts introduced
The language was simple, other than the concepts (e.g. natural key) that were introduced
Established a pattern for customizing, that presumably I as an app developer should consider
Read more intuitive vs the semantically correct equivalent


Having some trouble importing this

I don't appear to be able to import anything from this package – I presume I need something like
import autocomplete from 'getaddress-autocomplete'

But a) that's not documented and b) the module doesn't seem able to resolve.
package.json says "main": "./dist/getaddress-autocomplete.mjs", but I don't have a ./dist folder after installing.

To get this to work as per the documentation, with import autocomplete from 'getaddress-autocomplete' as the import, I had to:
cd node_modules/getaddress-autocomplete
npm install
npm run build

I'm a ruby person rather than a JS person, but this isn't something I have to do with other packages I've yarn added to package.json – is the npm package publishing step missing the thing that creates dist?

@rgarner Try import { autocomplete } from 'getaddress-autocomplete'
This library used named, rather than default, imports

@watsom27 thanks, I did eventually do this a couple of years ago, but ended up just talking to the URLs directly so as not to take a dependency.

ended up just talking to the URLs directly so as not to take a dependency.

Im looking at probably having to do the same, this library looks abandoned and doesnt seem to play nicely with Bootstrap


feat(tabs): it should not select first not active tab as selected

Tabs should behave such way that if you specifically set tab.active to "false" is should not be selected even if it's first tab.
This behavior do not change current way tabs are working. It only adds new behavior if we specifically set active === false.
Test are added to cover new funcionality.

Landed as 91b5fb62eedbb600d6a6abe32376846f327a903d - thanks!
Closes #2742


Fix broken Keen links and drop IO

Description of the change: Several of the internal Keen links had drifted out of sync and were broken, and the company name is just Keen, not Keen IO
Reason for the change: 404 not found; correctness
Link to original source: https://keen.io/ + https://keen.io/guides/getting-started/

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

Hello @rdela,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Message to multiple User/All User

Hello,
thanks for the Awesome Plugin. Works realy nice. Is there a way to send Message for alle Users?
Would be very nice.
Thanks for sharing :)

You'd have to create individual messages for every user. I think other apps exist if you wanted to send out alerts or something.

My pleasure :)


Spyder doesn't launch on anaconda, it's also very slow in a newly created environment

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I'm not sure whether these issues are solved or not, but I still can't launch Spyder on anaconda in the base environment (despite restoring my base environment to it's original revision). Also if I create a new environment from scratch and install Spyder on it, typing in the IDE is annoyingly slow!
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: 4.2.1
Python version: 3.8.5
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version: macOS 11.2.1

Dependencies

PASTE DEPENDENCIES HERE

Hey @mhdmyz, thanks for reporting. We've already gone through this: the only way to make Spyder work on Big Sur right now is to use our DMG installer.
There's nothing we can do about Anaconda because they're using a very old version of Qt (the graphical library upon which Spyder is built). If you want to get information about when that will be fixed, please open an issue here:
https://github.com/ContinuumIO/anaconda-issues/


CloudVideoIntelligenceApi DetailedApiRequestError(status: 403, message: The caller does not have permission)

My Code:
final accountCredentials = ServiceAccountCredentials.fromJson(r'''{
      "type": "service_account",
      "project_id": "...",
      "private_key_id": "...",
      "private_key": "...",
      "client_email": "...",
      "client_id": "...",
      "auth_uri": "https://accounts.google.com/o/oauth2/auth",
      "token_uri": "https://oauth2.googleapis.com/token",
      "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
      "client_x509_cert_url": "..."
    }''');
    var scopes = [CloudVideoIntelligenceApi.cloudPlatformScope];
    AuthClient client = await clientViaServiceAccount(
        accountCredentials, scopes);
    try {
      final CloudVideoIntelligenceApi cloudVideoIntelligenceApi = CloudVideoIntelligenceApi(
          client);
      GoogleLongrunningOperation googleLongrunningOperation = await cloudVideoIntelligenceApi
          .videos.annotate(
          GoogleCloudVideointelligenceV1AnnotateVideoRequest(
              features: ['EXPLICIT_CONTENT_DETECTION'],
              inputUri: 'gs://...mp4'));
      print(googleLongrunningOperation.response);
    } finally {
      client.close();
    }

Why does it keep giving me this error?
flutter: ----------------FIREBASE CRASHLYTICS----------------
flutter: DetailedApiRequestError(status: 403, message: The caller does not have permission)
flutter:
#0      _validateResponse (package:_discoveryapis_commons/src/api_requester.dart:298:9)
<asynchronous suspension>
#1      ApiRequester.request (package:_discoveryapis_commons/src/api_requester.dart:72:16)
<asynchronous suspension>
#2      VideosResource.annotate (package:googleapis/videointelligence/v1.dart:486:23)
<asynchronous suspension>
#3      _Messages.lol (package:nabers.dart:352:63)
<asynchronous suspension>
flutter: ----------------------------------------------------

First, I would never put a service account in an app you ship to a client.
Second: there must be something wrong with the credentials. You need to make sure the service account you're using has access to the API you specify.


Turborepo on Vercel template is failing to be deployed

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
https://vercel.com/templates/next.js/monorepo-turborepo
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Which canary version will you have in your reproduction?
15.0.0-canary.95
Describe the Bug
While deploying I ran into error during build process
Error: No Output Directory named "public" found after the Build completed. You can configure the Output Directory in your Project Settings.

Expected Behavior
Successfully create a turborepo monorepo adn deploy it on vercel
To Reproduce

Go to https://vercel.com/templates/next.js/monorepo-turborepo
Click on "Deploy"
Wait for the build process to finish

Additional context
No response

I'll fix the template! This is happening because the Root Directory is missing. You can fix this in your Project Settings by setting the Root Directory to apps/docs or apps/web


Typo fix Timout->Timeout

Line 56: Timout->Timeout

Can you sign off on the DCO?

OK,I've signed off just now.

Please see https://github.com/helm/helm/pull/6138/checks?check_run_id=183025790

@AdamDang If you follow the directions on the Checks tab at the top it can help you fix the DCO signoff issue.
Unfortunately, Helm v2 lives on the edge of what circleci provides for memory. This latest error looks to be from that. When you see /usr/local/go/pkg/tool/linux_amd64/link: signal: killed that is what's usually happening. Helm v3 has no such issue.

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!


Failure in project initialization

To Reproduce

Run npx create-fumadocs-app in the terminal to create a new Fumadocs project
Complete the steps as requested by the CLI

Current vs. Expected behavior
Following the steps from the previous section, I expected a new project to be created, but a failure was produced by npm:

Provide environment information
(ran outside project since project could not be created)

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:28:45 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 21.7.2
  npm: 10.5.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: N/A
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)
CLI (create-fumadocs-app)
Additional context
No response

My mistake, after moving fumadocs-core to peer dependency, the latest release of Fumadocs MDX with correct peer dependency versions isn't released in time. It should be fixed now


How do I know the microservice is closed？

I had multiple microservices, when I registered successfully,
instance.length > 1 and I choose one of the instances randomly
const instances = client.getInstancesByAppId('YOURSERVICE');
if I shutdown one of the microservice,how to detect it immediately ?

Hey @Janking,
If you shut down the service, it will stop sending heartbeats to the Eureka server and eventually fall out of the registry. Both the Java client and this Eureka client cache the registry for a configurable amount of time, so it's always possible you will send a request to an instance that has gone down. In addition to that, the Eureka server won't drop it out of the registry until several heartbeats have been missed.
If you're using Eureka service discovery, the normal pattern is that you also use a fault tolerant and resilient HTTP strategy like Ribbon. In this setup, it doesn't really matter if the client sends a request to a DOWN service, because it's going to retry anyway on failure or timeout. When it retries, it will go to the next available instance. You must have this logic due to the nature of instances going up and down.
Hope this helps!

@jquatier  Thanks , but I don't know how to use Robbin in node project ,  can you provide any examples ? ☹

Hey @Janking,
Unfortunately there is no drop in replacement for ribbon in node, but you can use a library like https://www.npmjs.com/package/resilient. And then use this eureka client to supply the resilient client with a list of servers (https://www.npmjs.com/package/resilient#discovery).
Hopefully that information helps!
-Alex

@awolden Thank you very much !


Overriding component styles

How can i change default style for component in material?
This is my navbar.component.html
<mat-toolbar>     <mat-toolbar-row>         HBSOFT     </mat-toolbar-row> </mat-toolbar>
and my navbar.component.css
mat-toolbar {     height: 45px; }
mat-toolbar-row {     height: 45px; }
But it's not working.

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


Call a chain of downstream APIs within a one request

Appreciate your clarification with regard to my below question.
Aassume I have a chain of downstream API calls to be made.
e.g
From client-spa application a request made to access api-A,
then  api-A calls api-B, api-B needs to call api-C to satisfy api-A request.
How do you configure them in Azure? Any recommended best practice to manage these sort of integrations?

close the ticket with thanks @derisen


Italian translation is wrong

Italian translations has lots of errors, often completely changing the sentences. Documentation is important, and there are quite a few sentences whitout meaning.
How can I help? Thanks

This repo is not being used anymore. The new repo is here. It also has a better system for translations

You can help translate our new projects and documentation here: https://weblate.librescore.org/


Incompatibility between Eden Ring and Create #514

Describe the Bug
It crashes (porting lib) right at boot
Reproduction Steps
1.Install Create |514, Bclib,Eden Ring, Fabric modloader 14.2/13.3, Fabric API 0.51.1. MC 1.18.2
2.Run
3.
...
Expected Result
To just run the game as normal
Screenshots and Videos
latest.log
Crash Report or Log
No response
Operating System
Windows 10
Mod Version
0.4.1
Minecraft Version
1.18.2
Other Mods
BcLib, Eden Ring
Additional Context
No response

This was reported to Eden ring too!

Paulevs isnt willing to change his mixins for that yet...

From the logs, two mixins are trying to change the same thing. Given that porting lib is much smaller the eden ring, perhaps this could be rectified. Although I have 0 ideas how much work that takes so if its too much then we all understand.

I believe living entity mixin is also the same one that conflicts with eden ring too.


How to change the proxy setting in a failed task

Some of the tasks failed because of the proxy expired. And I noticed that the proxy setting was stored in taskdb's fetch field as such:
{"headers": {"Referer": "http://www.google.com", "User-Agent": "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.85 Safari/537.36"}, "proxy": "<IP_ADDRESS>:80"}
Is that means pyspider will use the same proxy setting in the next retry crawl?  if so, it will fail again and gain...
How to change the proxy setting in the retry proxcess? Or is that possible to set multiple proxies in one crawl?

Specify a proxy in task is not a good practice, it's better using some proxy management tools (e.g. squid) to manage your proxy pool.

I think squid is not the right choice, may be HAProxy will work.

use whatever you like.


v2 seems quite slow

I recently updated to v2 from v1 in order to support .trx files because of an issue with the junit reporter I was using, and I find that it's considerably slower.
With v1:

build
junit files
~7500 tests

With v2:

build
trx files
~9500 tests

With v2, consuming the test files takes almost twice as long as it does to run the tests and generate them.  The effect is that this has tripled my build times.
Maybe it's the different file type, I'm not sure.

Thanks for reporting, I have never had the chance to test this with large TRX files.
I have fixed this in #417.
Please test the fix in your CI by using the action from that branch:
uses: EnricoMi/publish-unit-test-result-action/composite@branch-xslt-trx-add-index

The current action takes 4.5 minutes to load your largest file (30MB):
2023-03-09 23:05:07 +0000 - publish -  INFO - Read 4 of 12 files in 4 minutes and 30.02 seconds
2023-03-09 23:05:10 +0000 - publish -  INFO - Detected 12 TRX files (33.0 MiB)

Note: the setup of the action might be slower than usual, but that parsing will be faster.

Thanks for the quick response. I should be able to test in a couple days.  (Daughter's 15th tomorrow!)

That's some improvement, but it's still taking longer than actually running the build and tests.
Why does this file take so long to process for a summary?  Looking at it, it doesn't look that complex.  Later in the build, I build a badge from this file using grep twice, and that only takes 21 sec.

If you are referring to this job, then you haven't tested the fix. That is only available in master, it has not been released yet.
You have to change the uses: in a branch to test this. See https://github.com/EnricoMi/publish-unit-test-result-action/issues/414#issuecomment-1463569702.

My apologies.  I thought the merge indicated it was available in v2.  I'll test again.

Yes... much better.

Reading the files now takes less than a second (was 4 1/2 minutes):
Finished reading 12 files in 0.73 seconds

https://github.com/gregsdennis/json-everything/actions/runs/4399301343/jobs/7703758592#step:3:164
I'll release this soon. Thanks for reporting!

This has been released.


How to install apple-darwin toolchain?

The apple-darwin toolchain has no <env> part (such as gnu or msvc). But when the <env> part is omitted, it defaults to the host. For example on linux:
~ $ multirust update x86_64-apple-darwin-nightly
info: installing toolchain 'x86_64-apple-darwin-nightly'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-nightly.sha256'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-nightly'
checksum passed
error: a binary package was not provided for: 'x86_64-apple-darwin-gnu-nightly (tracking)'

It seems like cross compilation isn't possible at the moment. It just installs the toolchain from https://www.rust-lang.org/downloads.html instead of providing a cross-compiled standard library.
So it doesn't make sense to install the apple toolchain on linux since linux can't use a rustc binary for Mac OS. Thus I will close this issue.


Add "Run in workspace" button in Example code cells

Ticket
CT-2374
Description
This is a growth experiment to bring visitors to workspace.

Add a button "Run in workspace" in each example code cell. For now this will just send people to the workspace landing page as we don't have a way to create a workspace from a block of code. If we notice good traction, this will be a follow up to implement this feature.
Add a link to workspace below each example code cell

Screenshots
On desktop:

On phone:

Some other things to note:

RDocs is only for R, so in follow-up improvements you'll want to send people to R workspaces.
RDocs contains docs on all R packages, but the workspace docker image doesn't necessarily have all of these R packages installed. I think it's fine, but just know that you'll likely be sending people to experiment with the code, when actually, they cannot experiment with the code straight away as they have to install the pacage using the install.packages() function first.  For more info on working with packages in Workspace, see here.

Some other things to note:

RDocs is only for R, so in follow-up improvements you'll want to send people to R workspaces.
RDocs contains docs on all R packages, but the workspace docker image doesn't necessarily have all of these R packages installed. I think it's fine, but just know that you'll likely be sending people to experiment with the code, when actually, they cannot experiment with the code straight away as they have to install the pacage using the install.packages() function first.  For more info on working with packages in Workspace, see here.

Got it, I see! That makes it more tricky. We can think about that if we notice high traffic and decide to make a follow up on this!
Btw I have update the link to create a base r workspace instead of just sending users to the landing page.


[Feature request] reactive file input field

Hi,
Most registration forms require an image input at a certain point, so it would be great to be able to integrate that field in the reactive form.
Thanks in advance.

@chahineaoun check
https://github.com/artflutter/reactive_forms_widgets
Or leave request for wrapper
https://github.com/artflutter/reactive_forms_widgets/issues/16


Plugin is not working for cli-6.3.0

Not able to build the app when using cli-6.3.0. Please help.

I ma also getting "fatal: unable to access 'https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin.git/': Unknown SSL protocol error in connection to github.com:443"


os error

📚 Installation

Environment

OS: windows
Python version: 3.6
PyTorch version:1.4.0
CUDA/cuDNN version: no
GCC version:
How did you try to install PyTorch Geometric and its extensions (pip, source):
Any other relevant information:

Checklist

[ ] I followed the installation guide.
[ ] I cannot find my error message in the FAQ.
[ ] I set up CUDA correctly and can compile CUDA code via nvcc.
[ ] I have cloned the repository and tried a manual installation from source.
[ ] I do have multiple CUDA versions on my machine.
[ ] I checked if the official extension example runs on my machine.
[ ] The offical extension example runs on my machine.

Additional context

import torch_geometric
Traceback (most recent call last):
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_sparse_init_.py", line 15, in
library, [osp.dirname(file)]).origin)
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_ops.py", line 106, in load_library
ctypes.CDLL(path)
File "G:\anaconda\envs\python3.6\lib\ctypes_init_.py", line 348, in init
self._handle = _dlopen(self._name, mode)
OSError: [WinError 126] 找不到指定的模块。

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_geometric_init_.py", line 2, in
import torch_geometric.nn
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_geometric\nn_init_.py", line 2, in
from .data_parallel import DataParallel
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_geometric\nn\data_parallel.py", line 5, in
from torch_geometric.data import Batch
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_geometric\data_init_.py", line 1, in
from .data import Data
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_geometric\data\data.py", line 7, in
from torch_sparse import coalesce
File "G:\anaconda\envs\python3.6\lib\site-packages\torch_sparse_init_.py", line 23, in
raise OSError(e)
OSError: [WinError 126] 找不到指定的模块。

Can you translate the OSError message?

windows OSError 126.
The error just mention the error code. After that I found some resources, because the lace of ddl file.
The way to slove the problem is to uninstall the package and reinstall it.
Thank you for your attention.
Best wishes
------------------ 原始邮件 ------------------
发件人: "Matthias<EMAIL_ADDRESS>发送时间: 2020年4月22日(星期三) 晚上8:58
收件人<EMAIL_ADDRESS>抄送: "朵朵"<884665320<EMAIL_ADDRESS>主题: Re: [rusty1s/pytorch_geometric] os error (#1146)
Can you translate the OSError message?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

hello,when I to import "torch_geometric",this error happened,have you solved this error?

Hello , I have met the same problem as you have met , I see that you say the way to solve the problem is to uninstall the package and reinstall it and you have found some resources, so could you please describle what the resources are and which the  package has to uninstall and reinstall ? thanks you @ AShappyboy


[Bug]6个postgresql历史CVE漏洞在PolarDB中未合入补丁修复

背景
最近在使用自研工具patch2ql生成的、覆盖postgresql所有已知历史CVE漏洞的CodeQL规则，对国内外主流的postgresql二次开发开源数据库进行扫描，分析其中未修复的上游漏洞。
在分析阿里云PolarDB时，发现若干个历史漏洞未修复。
未修复漏洞列表：

CVE
披露日期
CVSS3 威胁程度

CVE-2020-25694
2020/11/16   01:15
HIGH

CVE-2020-25695
2020/11/16   01:15
HIGH

CVE-2020-25696
2020/11/23   22:15
HIGH

CVE-2021-3393
2021/4/1   14:15
MEDIUM

CVE-2021-32027
2021/6/1   14:15
HIGH

CVE-2021-32029
2021/10/8   17:15
MEDIUM

CVE-2021-32028
2021/10/11   17:15
MEDIUM

CVE-2021-23222
2022/3/2   23:15
MEDIUM

CVE-2021-23214
2022/3/4   16:15
HIGH

CVE-2022-2625
2022/8/18   19:15
HIGH

CVE-2022-1552
2022/8/31   16:15
HIGH

CVE-2023-39417
2023/8/11   13:15
HIGH

详细漏洞上下文报告
以下为详细报告，包含了每个匹配到的缺陷函数位置，以及对应的检出规则（CVE号，postgresql上游修复的commit）
./CVE-2020-25694-8e5793ab60bba65ffaa0f2237b39c9580d8972c7/cluster_one_database-autogen.bqrs
|            func            |                                                col1                                                |           col2            |
+----------------------------+----------------------------------------------------------------------------------------------------+---------------------------+
| connectMaintenanceDatabase | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/scripts/common.c    | function startline is 158 |
| cluster_one_database       | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/scripts/clusterdb.c | function startline is 189 |
| reindex_system_catalogs    | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/scripts/reindexdb.c | function startline is 368 |
| reindex_one_database       | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/scripts/reindexdb.c | function startline is 275 |
./CVE-2020-25694-a45bc8a4f6495072bc48ad40a5aa0304979114f7/_allocAH-autogen.bqrs
|   func   |                                                    col1                                                     |            col2            |
+----------+-------------------------------------------------------------------------------------------------------------+----------------------------+
| _allocAH | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/pg_dump/pg_backup_archiver.c | function startline is 2302 |
./CVE-2020-25694-a45bc8a4f6495072bc48ad40a5aa0304979114f7/dumpOptionsFromRestoreOptions-autogen.bqrs
|             func              |                                                    col1                                                     |           col2            |
+-------------------------------+-------------------------------------------------------------------------------------------------------------+---------------------------+
| dumpOptionsFromRestoreOptions | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/pg_dump/pg_backup_archiver.c | function startline is 155 |
./CVE-2020-25694-a45bc8a4f6495072bc48ad40a5aa0304979114f7/NewRestoreOptions-autogen.bqrs
|       func        |                                                    col1                                                     |           col2            |
+-------------------+-------------------------------------------------------------------------------------------------------------+---------------------------+
| NewRestoreOptions | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/pg_dump/pg_backup_archiver.c | function startline is 955 |
./CVE-2020-25694-a45bc8a4f6495072bc48ad40a5aa0304979114f7/restore_toc_entries_postfork-autogen.bqrs
|             func             |                                                    col1                                                     |            col2            |
+------------------------------+-------------------------------------------------------------------------------------------------------------+----------------------------+
| CloneArchive                 | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/pg_dump/pg_backup_archiver.c | function startline is 4753 |
| restore_toc_entries_postfork | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/pg_dump/pg_backup_archiver.c | function startline is 4179 |
./CVE-2020-25694-a45bc8a4f6495072bc48ad40a5aa0304979114f7/restore_toc_entry-autogen.bqrs
|       func        |                                                    col1                                                     |           col2            |
+-------------------+-------------------------------------------------------------------------------------------------------------+---------------------------+
| restore_toc_entry | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/pg_dump/pg_backup_archiver.c | function startline is 740 |
./CVE-2020-25696-098fb00799ffb026ff12c64bd21635f963cfc609/StoreQueryTuple-autogen.bqrs
|      func       |                                             col1                                             |           col2            |
+-----------------+----------------------------------------------------------------------------------------------+---------------------------+
| StoreQueryTuple | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/bin/psql/common.c | function startline is 946 |
./CVE-2021-3393-6214e2b2280462cbc3aa1986e350e167651b3905/show_modifytable_info-autogen.bqrs
|         func          |                                                 col1                                                  |            col2            |
+-----------------------+-------------------------------------------------------------------------------------------------------+----------------------------+
| show_modifytable_info | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/commands/explain.c | function startline is 3598 |
./CVE-2022-1552-0abc1a059e27c5a71a1a186c97d9c0af407469cc/ExecRefreshMatView-autogen.bqrs
|        func        |                          col1                           |           col2            |
+--------------------+---------------------------------------------------------+---------------------------+
| ExecRefreshMatView | function relativepath is src/backend/commands/matview.c | function startline is 138 |
./CVE-2022-1552-677a494789062ca88e0142a17bedd5415f6ab0aa/ExecRefreshMatView-autogen.bqrs
|        func        |                                                 col1                                                  |           col2            |
+--------------------+-------------------------------------------------------------------------------------------------------+---------------------------+
| ExecRefreshMatView | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/commands/matview.c | function startline is 138 |
./CVE-2022-2625-5579726bd60a6e7afb04a3548bced348cd5ffd89/transformCreateStmt-autogen.bqrs
|        func         |                                                   col1                                                    |           col2            |
+---------------------+-----------------------------------------------------------------------------------------------------------+---------------------------+
| transformCreateStmt | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/parser/parse_utilcmd.c | function startline is 164 |
./CVE-2022-2625-5721da7e41e7a280587bda29cd1674c7da3317f8/transformCreateStmt-autogen.bqrs
|        func         |                                                   col1                                                    |           col2            |
+---------------------+-----------------------------------------------------------------------------------------------------------+---------------------------+
| transformCreateStmt | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/parser/parse_utilcmd.c | function startline is 164 |
./CVE-2022-2625-5919bb5a5989cda232ac3d1f8b9d90f337be2077/CreateForeignServer-autogen.bqrs
|        func         |                                                   col1                                                    |           col2            |
+---------------------+-----------------------------------------------------------------------------------------------------------+---------------------------+
| CreateForeignServer | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/commands/foreigncmds.c | function startline is 864 |
./CVE-2022-2625-5919bb5a5989cda232ac3d1f8b9d90f337be2077/CreateSchemaCommand-autogen.bqrs
|        func         |                                                   col1                                                   |           col2           |
+---------------------+----------------------------------------------------------------------------------------------------------+--------------------------+
| CreateSchemaCommand | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/commands/schemacmds.c | function startline is 51 |
./CVE-2022-2625-5919bb5a5989cda232ac3d1f8b9d90f337be2077/transformCreateStmt-autogen.bqrs
|        func         |                                                   col1                                                    |           col2            |
+---------------------+-----------------------------------------------------------------------------------------------------------+---------------------------+
| transformCreateStmt | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/parser/parse_utilcmd.c | function startline is 164 |
./CVE-2022-2625-7e92f78abe80e4b30e648a40073abb59057e21f8/transformCreateStmt-autogen.bqrs
|        func         |                                                   col1                                                    |           col2            |
+---------------------+-----------------------------------------------------------------------------------------------------------+---------------------------+
| transformCreateStmt | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/parser/parse_utilcmd.c | function startline is 164 |
./CVE-2023-39417-919ebb023e74546c6293352556365091c5402366/execute_extension_script-autogen.bqrs
|           func           |                                                  col1                                                   |           col2            |
+--------------------------+---------------------------------------------------------------------------------------------------------+---------------------------+
| execute_extension_script | function relativepath is /opt/exp/postgre-forks/PolarDB-for-PostgreSQL/src/backend/commands/extension.c | function startline is 818 |

报告者
fullwaywang

@fullwaywang Thanks for reporting. We will fix it in the following days.

@fullwaywang I have checked that some of the bugs has already been fixed.

@fullwaywang I have checked that some of the bugs you have listed has already been fixed. What is the theory of your scanning tool?

I used our novel tool, patch2ql, for generating CodeQL rules to match the unpatched vulnerable code context, indicated by patches to known CVEs. The ruleset for postgresql can be retrieved here.
The results for PolarDB had been checked for potential FPs manually. If any FPs remained please consider reporting them to me so that corresponding rules can be manufactored.

@fullwaywang I have checked that some of the bugs you have listed has already been fixed. What is the theory of your scanning tool?

I used our novel tool, patch2ql, for generating CodeQL rules to match the unpatched vulnerable code context, indicated by patches to known CVEs. The ruleset for postgresql can be retrieved here.
The results for PolarDB had been checked for potential FPs manually. If any FPs remained please consider reporting them to me so that corresponding rules can be manufactored.

@fullwaywang I fixed following CVEs yesterday:
CVE-2020-25694
CVE-2020-25696
CVE-2021-3393
CVE-2022-1552
CVE-2022-2625
CVE-2023-39417
Other CVE has already been fixed. Current stable branch should have fixed all the CVEs you have listed.

@fullwaywang I have checked that some of the bugs you have listed has already been fixed. What is the theory of your scanning tool?

I used our novel tool, patch2ql, for generating CodeQL rules to match the unpatched vulnerable code context, indicated by patches to known CVEs. The ruleset for postgresql can be retrieved here.
The results for PolarDB had been checked for potential FPs manually. If any FPs remained please consider reporting them to me so that corresponding rules can be manufactored.

@fullwaywang I fixed following CVEs yesterday:
CVE-2020-25694 CVE-2020-25696 CVE-2021-3393 CVE-2022-1552 CVE-2022-2625 CVE-2023-39417
Other CVE has already been fixed. Current stable branch should have fixed all the CVEs you have listed.

Yes, these were the very 6 vulnerabilities discovered. I mistakenly pasted the full list of CVEs as a consequence of a bug of copying selected data out of Excel : )

@fullwaywang Thanks for your reporting anyway.


Can I update web panel with old miner version 2.3.2

Can I update web panel with old miner version 2.3.2

Yes, I've tried it with many miner versions (even 2.0.0) and all have worked for me.

Good thank you very much


AccountDb is inefficient

For collecting changes while executing smart-contracts we use an abstraction called AccountDb.
It lets us collect some changes made to an account db (such as transfers, contract storage modifications, etc) and either commit these changes to the storage or discard them. Furthermore, it is possible to create nested account dbs which changes also can be commited to the parent db or discarded.
The problem with the current implementation of AccountDb is that it is rather inefficient. It uses cascade of hash maps. That is, nested account db is just a hash map with keys as account address and values as account data that collects all performed changes. If some value requested which isn't present in the hash map, a query to the parent account db is performed. It continues until value is found in some parent account db or if the last account db returned there is no such value. If the value is found then it is cached in the current overlay and returned.
With that construction, it is possible to make a very deep transaction that have a long chain of nested account dbs and try to query a large range of keys that lead to such cache misses and cost of which would be proportional to the depth of the transaction stack and not to how much is paid for the gas.
That's unfortunate and AccountDb should have runtime characteristics proportional to how much is paid for the gas.

Check the ethereum implementation, but I suspect that it's the same there. Fact of the matter is that (even dozens of) cache lookup is faster that a disk-DB lookup and that's what we charge gas price on.

parity-ethereum implementation is more efficient:
https://github.com/paritytech/parity-ethereum/blob/master/ethcore/src/state/mod.rs#L298-L306

This is the only non linear part of the current smart-contract runtime, as far as I can tell.

Closed as invalid


Change util_test.go's "ReadUrl" test URL to a neutral address (e.g., 'apache.org')

https://github.com/apache/incubator-openwhisk-wskdeploy/blob/master/utils/util_test.go
Currently the following address is hardcoded:
"http://www.baidu.com"
We should change this to a neutral (non-commercial) address, for example:
"https://www.apache.org/"

@mrutkows: Please could you review? https://github.com/apache/incubator-openwhisk-wskdeploy/pull/638


feat: move the tenant system namespace inside the tenant

Fixes #3

Need to lint 🫠

Wait for #7 to be merged and need to rebase on new mainline.

@prometherion the PR Is now rebased and readybfor review 🚀


Update frequency

Could you set the update frequency a bit higher, as 30 seconds is quite long. It's only getting a long string anyway. So bit of spam to the request server is no issue. I would suggest 10 seconds or even 5 seconds (like the old wallboard).

The plan is to add a polling setting per user so the polling to the different user/repos can be set more fine grained

Seems to me like a great solution :+1: !

fixed


fix(loader): Use better detection of amd loaders

Fixes: #68
Instead of checking require.version I'm checking for amd specs https://github.com/amdjs/amdjs-api/blob/master/AMD.md#defineamd-property-
Locally tested with alameda as replacement and it worked for me.

This seems good to me, but I'd like a second opinion. @bigopon @jods4 Can you also do a quick review?

Well, @huochunpeng is our AMD / requirejs expert. I'd prefer to have him confirm this.

Good point. @huochunpeng can you take a look when you are next available?

Looks Good to me.
As @fragsalat said, the loader-default has to be updated to support alameda too.


Remove ambiguous post-provisiong instruction

From @telphan on June 7, 2016 11:43
null
Copied from original issue: resin-os/resin-toradex#12

No further development is planned for this board.


Customize blank caption

So far the blank caption is "No Data" for table chart, can you make it customizable, so we can localize this hint.

It is customisable.
LineChartData(...,
              noDataText: Text("Hello World."))

Thx for your response, this is great, but I have another question: Is the width between two nodes customizable?

No, what you could do is,  not provide a label for every other data point;
LineChartDataPoint(value: 12000, xAxisLabel: "1"),
LineChartDataPoint(value: 10000),
LineChartDataPoint(value: 8000, xAxisLabel: "3"),
LineChartDataPoint(value: 17500),
...


Download problems again

I eventually managed to download the full simulator archive couple of weeks ago and got it working. However today it blew up with some memory pool error that I didnt understand, so I thought I would just delete and download again and start from scratch (Win 10 Visual studio version). However I have got the partial zip file problem back, I been trying to download the V8 master zip all day. It always downloads a zip but it has several folders with nothing in lvgl folder for example. I tried 3 ways to get the source code all failed.  Please fix this problem or put the correct zip file somewhere else so I can download it please

tried just clicking on the "download zip" here. Failed as above

tried git clone https://github.com/lvgl/lv_sim_visual_studio from cmd prompt.
It worked and downloaded files, but once again folders are empty

tried alternative source site from a google search.
https://lvgl.io/pc-simulator gives a 404 not found

Thanks

You need git clone --recursive https://github.com/lvgl/lv_sim_visual_studio, otherwise the submodules won't be cloned.

ah thanks for the cmd line correction, that fixed the git download for me as expected (I dont normally use cmd line for this so missed that)
Just for info. I again tested my usual method of clicking the "Download Zip" button. Same result again this morning, all folders in the zip below the 2nd level are empty still. No idea why
Least the archive version is now running again and has fixed my memory heap walker crash. I can start experimenting again to see what caused the crash for me.

Just for info. I again tested my usual method of clicking the "Download Zip" button. Same result again this morning, all folders in the zip below the 2nd level are empty still. No idea why

Unfortunately, we have no control over that, as GitHub still (!) doesn't include submodules in the ZIP they generate. It would be nice to just hide the ZIP link but unfortunately we don't get that option either. :laughing:


http://chafey.github.io/cornerstoneDemo/ not working

The demo at http://chafey.github.io/cornerstoneDemo/
linked from https://github.com/cornerstonejs/cornerstoneTools
does not load any images ..

If this is still linked in the ReadMe, then it needs to be changed. Not sure that demo has been maintained for a while now.

We've started to build out some basic examples here: https://tools.cornerstonejs.org/examples/
You can update them by changing code in the examples/ folder of this solution. Right now, the examples are "per tool" examples, but I'd like us to spin up a few more complex scenarios. Ideally, one would be a very simple viewer. We could also provide an "advanced" link to OHIF's

The OHIF viewer demo is now using v2 and appears to work on Safari.
Some basic examples have been spun up. If one is missing that you would like to see added, please create a new issue, or create and contribute an example.


Correct wrong type of equality check in benchmark GHA.

😳
In #5001 I intended to generate first_commit ONLY IF it was not already provided by the workflow_dispatch, but I got my equality the wrong way round.

Life-saver, thanks again @stephenworsley!


Using Gradle for building

This would (hopefully) simplify building and publishing

[x] javadoc, private and public API
[x] publish to bintray
[x] specify dependencies, maven central, jcenter, locally
[x] source sets specified (can be undone once #252 is fixed)
[x] make dist zip with README, LICENSE, examples, and all jars (in short, ant task create-dist)
[x] run unit tests
[x] run integration tests
[x] prepare integration tests by reading the config file and creating symlinks remotely
[x] jacoco coverage and report to HTML
[x] offline build mode: #251

Non-essential for pull request: fix directory layouts for gradle #252

Tested bintray upload (includes sources and javadoc jars)
dist zip is available as per 75837a835483fade6d7dc8ba78bf7837c31ccd50
integration test runs (although many tests fail due to missing configuration on my end)

When #251 is fixed, a pull request from branch issue/252-gradleize will complete this issue.

Per 9adf963, offline build also works, resolving #251, and this issue.


Add support for kubedns

Description
This PR adds support for kubedns.
If KubeDNS is detected in the kubernetes cluster and coredns is not installed. Maesh will install CoreDNS as a DaemonSet and will patch KubeDNS to add a stubDomains that forward all dns request with prefix .maesh to the coreDNS instances.

Yes it could be a better idea to have a Deployment with anti affinity. By default k3s deploy only replica of coredns.

From an end-user perspective: Having more than DNS instance is always a good idea. But we usually don't deploy one instance per machine. So having this as deployment with configurable replica count would be nice.

I agree @nbyl,
that would be pretty cool. However, it will require to rethink the current helm values.
What do you think of something like
core-dns:
    deploy: true
    replicas: 2

instead of kubednes: true? Any other suggestion?

I think since Maesh gets deployed as a daemonset, having CoreDNS as a daemonset in KubeDNS clusters makes sense. Also, it sounds like CoreDNS will only handle .maesh requests, so KubeDNS will continue to function the same it is prior to installing Maesh. Correct me if I am wrong there. I feel like this is a great step towards GKE support, which I am very excited about.

Please do not depend on helm hook support. This will make this incredibly difficult to use with tools like Pulumi which only use helm templating.


abn/web-eid and Fedora 40

Fedora 40 has been released for some time now. Could you please rebuild so that there would be an rpm for F40 too?
Thank you in advance!

New build should have Fedora 40 builds.
https://copr.fedorainfracloud.org/coprs/abn/web-eid/build/7696667/


Fix thread safety in hnsw

Signed-off-by: zh Wang<EMAIL_ADDRESS>

/kind improvement

/lgtm


Ability to view explainer while account is connected

Currently if a user visits the explainer they are not able to connect their account. Additionally, if they are connected and visit the explainer they will lose their connection.
There should be harmony across the site so that a user can connect and stay connected whether on the explainer or the main page

Yeah, totally agreed. It raises a really interesting point, because what it would require is basically lifting state up so that both pages of the site can see the blockchain state.
From an initial glance, this is very possible using Gatsby. Check out this article. Basically, you wrap both pages in the same wrapper, and this wrapper provides state via context to the different pages. More from the Gatsby docs

I see. This is quite interesting. TBH I didn't expect there to be much complexity with this feature but I'm glad that there are supported ways to deal with states across pages

Yeah it is pretty cool - you can have multi page stateful websites that are basically applications 😁

Have addressed this issue in commit 303279a698128d91e7989e49200cda7565128aa3 . The fix was actually pretty straightforward, just needed to do some digging in the Gatsby docs. If you are curious, the magic happens in wrapRootElement

This is great, the dApp feels a lot more congruent now


Update exonum_rocksdb [ECR-3169]

Overview
With this update, ROCKSDB_STATIC environment variable actually controls the linkage type of rocksdb library. With this variable set, we'll get binaries which are not depending on user-provided rocksdb dymanic library.

See: https://jira.bf.local/browse/ECR-3169
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 86.259% when pulling d9fe98e9b736fbde7dfef91daeaf3fd7fef031b1 on vitvakatu:update_exonum_rocksdb into 16087f8102ce8126d47dcf554f445267e3ad0524 on exonum:master.


DASHBUILDE-172: Fail fast on invalid CSV data

Proposed fix for the issue

Merged.
Thanks a lot @jhrcek !


Huge source: adblock.mahakala.is

I've used this source for a larger period of time and it works well. I don't know if the aim of this mod is to be as small as possible, if not this is an about 30MB big hosts file. Unfortunately I also don't know how many hosts are already persistent in the other hosts files, but if these lines get deleted automatically it shouldn't be that big of a problem.
Source: http://adblock.mahakala.is

Good mornig @mitchellkrogza,
If @StevenBlack don't add this to this repo you could add this source to our Ultimate.Hosts.Blacklist repo :smile_cat:
Have a nice day !

@funilrys I did have this input source originally in Ultimate Hosts Blacklist but removed it at one point as I found it a bit unreliable. But will re-implement it today now that we have the Centralized List Cleaning functions from our Central Repo controller for that.

Hi @node1634 thanks for this suggestion.
We hope to strike a balance between safety and usability.  A 30 MB data source is quite beyond what's usable on some (most?) devices.
So closing.


Hot fix parameter error

It is just a tiny mistake that makes fetching reviews return an error.

This PR is kinda sad


Added support for Microsoft Edge Chromium

Now that Microsoft released the Chromium-based version of Edge, I have added support for multiple browsers registration.

Code looks good, will have a further look this weekend

I've resolved the merge conflicts over on https://github.com/anewtonlevey/NativeMessaging/pull/8 and will pull in from there.

Olivier PIRLET
-------- Original message --------From: Alex Newton Levey<EMAIL_ADDRESS>Date: 12/09/2020  11:52  (GMT+01:00) To: anewtonlevey/NativeMessaging<EMAIL_ADDRESS>Cc: Olivier PIRLET<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [anewtonlevey/NativeMessaging] Added support for Microsoft Edge Chromium (#7)
I've resolved the merge conflicts over on
#8 and will pull in from there.
—
You are receiving this because you authored the thread.
Reply to this email directly,
view it on GitHub, or
unsubscribe.


Added support for container stop

This is my first time working with Electron/React/etc and couldn't figure out where the test units were. I believe that I added the proper 'Stop' container functionality, but I could also be very wrong.
Any input is appreciated!

Thanks @TeckniX! This is awesome! You even added the nice icons haha :) I'm sorry the test units aren't complete yet. I will take a look and play around with this PR.

That would explain it ;) - Yea the little icon was a quick photoshop deal. I wasn't sure who was responsible for the layout design.
As previously mentioned quite fresh on this type of build, is there an easy way to debug/log actions/events, so that I can follow clicks etc?

This feature is in HUGE demand. Awesome. Added one comment, otherwise LGTM.
Thanks so much for taking the time to make this PR. One last thing, can you sign your commit?

Can I just push a blank update and add as the comment my 'Signed-off-by: Joe Smith<EMAIL_ADDRESS>?

This should work:
git commit -s --amend
git push -f origin master
We're working making signing automatic / easier for contributors. Sorry about that!

Just took this PR for a spin. Fantastic! Looks great too. One last thing: center the text and then this is ready to merge:

Good catch - label should be centered now - Thanks!

Great! Merging. Thanks for the contribution, @TeckniX

Glad I could help :dancer:


[Bug] Canceling the stream takes user to an empty profile page

Canceling a stream does not mean that the donations made so far were withdrawed, so the profile should now show empty.

The donations aren't being removed. I think the wallet is empty due to this error that is preventing subgraph queries:

@sirpy @L03TJ3 I don't have access to the subgraph infra. Would you be able to take a look and see what's going on?

@krisbitney thegraph is a free service, we dont have any special access. Does this still happen?

@krisbitney thegraph is a free service, we dont have any special access. Does this still happen?

I'm no longer getting this error. Maybe it happened because I had recently redeployed the subgraph multiple times and we were rate limited, or maybe The Graph was having some issues on their end. I don't know.
@patpedrosa Could you please try again? I just tested it and my donation still showed.
I actually had the opposite problem: it took a few minutes before my profile reflected that the donation had stopped, so it looked like the donation kept flowing. My total donated amount went up to $GD 134, then reverted back to 132. The donation fetching is polled with an interval of 1 second (i.e. it checks for new data every 1 second), but it takes a short time for the transaction to finalize and the subgraph to update.

I've retested it, it's showing correctly. Thank you.

Thank you for taking another look. I appreciate it!


error: command 'g++' failed with exit status 1

Hello. Thanks for you open-source code. However, when i run the command in
python setup.py build_ext --inplace.
I meet the problems in here:
(pytorch15) sifan@fudan:~/slam-package/vistr/models/dcn$ python setup.py build_ext --inplace
running build_ext
building '_C' extension
creating /home/sifan/slam-package/vistr/models/dcn/build
creating /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7
creating /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable
Emitting ninja build file /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
1.10.2
creating build/lib.linux-x86_64-3.7
g++ -pthread -shared -B /home/sifan/anaconda3/envs/pytorch15/compiler_compat -L/home/sifan/anaconda3/envs/pytorch15/lib -Wl,-rpath=/home/sifan/anaconda3/envs/pytorch15/lib -Wl,--no-as-needed -Wl,--sysroot=/ /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable/deform_conv.o /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable/deform_conv_cuda.o /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable/deform_conv_cuda_kernel.o -L/home/sifan/anaconda3/envs/pytorch15/lib/python3.7/site-packages/torch/lib -L/usr/local/cuda/lib64 -lc10 -ltorch -ltorch_cpu -ltorch_python -lcudart -lc10_cuda -ltorch_cuda -o build/lib.linux-x86_64-3.7/_C.cpython-37m-x86_64-linux-gnu.so
g++: error: /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable/deform_conv.o: No such file or directory
g++: error: /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable/deform_conv_cuda.o: No such file or directory
g++: error: /home/sifan/slam-package/vistr/models/dcn/build/temp.linux-x86_64-3.7/deformable/deform_conv_cuda_kernel.o: No such file or directory
error: command 'g++' failed with exit status 1
I don't know how to solve this problem. Could you give me some help? Thank you very much!

I have the same problem. Have you solved it?

The reason for this error is that the setup.py file is repeatedly compiled.


LibURL: Don't return early parsing a URL with an empty input

This fixes all but one WPT URL constructor test case under https://wpt.live/url/url-constructor.any.html :^)

The last test case involves UTF-16 surrogates (specifically, \uD801\uDFFE), and will need USVString etc

Ok, folded in the remaining set of fixes made for that file. Only the niggly utf16 surrogate case left now :^)


Cannot parse events from Advanced Hunting CSV

Using the query described here:
https://github.com/MicrosoftDocs/WDAC-Toolkit/blob/main/WDAC-Policy-Wizard/docs/using/advanced-hunting.md
when attempting to import the produced CSV from MS Security Center into the WDAC Wizard, we receive "The Wizard could not parse any Advanced Hunting events from the CSV file(s)."
The file matches the requirements as described in said article. There are many relevant events int he exported data: "AppControlCodeIntegrityPolicyAudited", "AppControlCodeIntegrityOriginBlocked", "AppControlCodeIntegrityPolicyBlocked" are some examples of the ActionTypes present.
looking in ...\AppData\Local\Temp\WDACWizard\Temp\2023*\log*.txt shows nothing except for "No Advanced Hunting Records Parsed", no information as to why. If I run the WDAC wizard on a target system (whose events are in this export) and tell it to parse the event logs on the local computer, it will produce file rules--so it's not as though there is no parsable data.

Sure @jgeurten here's an example of a query submitted to the wizard.
WDAC_query.csv

@jgeurten my bad...I have discovered that the CSV I submitted does not have the AuthenticodeHash field. However it was in my Advanced Hunting query--it looks like the field returned a blank value and was thus omitted from the export.
I had to select 'Customize Columns' in the Advanced Hunting interface after running the query again, and select the Authenticode Hash column to be displayed for it to be included in the exported CSV.
After doing so, the CSV is parsed successfully by the WDAC Wizard. Might I suggest that since this seems to be the default behavior of Advanced Hunting that if this field is not present, then have the Wizard ignore that and parse the file anyway. You can feel free to close this issue--but please note that either a revision to the documentation or the application is desired.

hmm that is super odd. I see what you're describing in AH. That's never been an issue before, and I have previous csvs where the Authenticode column is present, but all the data rows are empty. AH must have updated their logic to drop columns where all the data is empty.
I'll need to fix this as I anticipate others will hit this too in the future

Update your KQL query from "project" to "project-keep", otherwise it drops the Authenticode Hash column if the whole column has null values.

@lee-halford that works--thank you.

Thanks all. I will update the documented KQL query!


STORM-2451: windows storm.cmd does not set log4j2 config file correct…

…ly by default
the dir from the default config is log4j2 and that should be relative to STORM_HOME, however this is check was missing
Signed-off-by: alexlehm<EMAIL_ADDRESS>

I don't have Windows machine but code change looks good to me, so +1 assuming you tested this manually.

yes, i am using the modified start script now

This PR is merged into asf git but asf git seems have some issue which might be related to mirror trigger. I'll try sync up mirror tomorrow. This will be closed automatically after sync up.


[WIP] autoPatchelfHook: search a valid interpreter, or fail

Motivation for this change
autoPachelfHook patches everything with the same interpreter
($NIX_CC/nix-support/dynamic-linker) even on incompatible binaries.
This happens in particular when building with multiStdenv.
See https://discourse.nixos.org/t/binary-still-not-working-even-when-properly-patchelfed/1570/3?u=layus for details.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @tadfisher

Tests finished. It seems that this patch breaks a lot of tools based on autoPatchelfHook. For example apktool fails with
searching an interpreted for /nix/store/yypk47fzqcbv0dkd9saaxfnlhcqj7qay-build-tools-28.0.3/libexec/android-sdk/build-tools/28.0.3/zipalign
found interpreter '/nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/ld-linux-x86-64.so.2' for '/nix/store/yypk47fzqcbv0dkd9saaxfnlhcqj7qay-build-tools-28.0.3/libexec/android-sdk/build-tools/28.0.3/zipalign'
searching for dependencies of /nix/store/yypk47fzqcbv0dkd9saaxfnlhcqj7qay-build-tools-28.0.3/libexec/android-sdk/build-tools/28.0.3/zipalign
  libc++.so -> found: /nix/store/yypk47fzqcbv0dkd9saaxfnlhcqj7qay-build-tools-28.0.3/libexec/android-sdk/build-tools/28.0.3/lib64/libc++.so
setting RPATH to: /nix/store/yypk47fzqcbv0dkd9saaxfnlhcqj7qay-build-tools-28.0.3/libexec/android-sdk/build-tools/28.0.3/lib64
searching an interpreted for /nix/store/yypk47fzqcbv0dkd9saaxfnlhcqj7qay-build-tools-28.0.3/libexec/android-sdk/build-tools/28.0.3/aarch64-linux-android-ld
/nix/store/s50lkmcg73qpd1gdybryndpk46fb8xw9-auto-patchelf-hook/nix-support/setup-hook: line 110: /nix/store/hpzj855nkgjvg58nrhq4910sb9q3kss1-gcc-wrapper-7.4.0/nix-support/dynamic-linker-m32: No such file or directory
objdump: '': No such file
No interpreter found for arch i386 needed by ''
builder for '/nix/store/ffhs8yvjwg51p436dpjjc58a669hky5f-build-tools-28.0.3.drv' failed with exit code 1
cannot build derivation '/nix/store/h1pm5pgkvaaxsg51nknlrlap9kv8swwr-apktool-2.4.0.drv': 1 dependencies couldn't be built

@aszlig Spacechem (https://github.com/openlab-aux/vuizvui/pull/18) needs this to patch correclty the 32bit binary rgb2theora used for solution saves.

The compelling reason was that I needed it for #65069. Not sure if switching to 32bit would be enough. It seems that the canon capt drivers have both 32 and 64 bits binaries packaged.

I'm curious if you tried the (somewhat simpler) patch in https://github.com/NixOS/nixpkgs/pull/51588?

Not sure how much more simple it is. I did not test it, but the fact that it seemingly does not introduce issues in other packages either means that it is much better than mine, or was just not tested against nixpkgs. Using dynamic-linker* is a good idea however. It makes the code more generic.

The hook is now python https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/setup-hooks/auto-patchelf.py


Disable systemd messages before starting the installer

The systemd messages can be hidden with the kernel parameter systemd.show_status=0.
But I don't think it's a good idea because the booting messages prior to the Harvester dashboard/installer are quite useful.
So the idea is to turn off the messager before starting the installer and turn it on after the installer is stooped. This makes messages before shutdown or reboots visible.
References:
https://www.freedesktop.org/software/systemd/man/systemd.html#systemd.show_status
https://www.freedesktop.org/software/systemd/man/systemd.html#SIGRTMIN+21
To get current show status:
# busctl get-property org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager ShowStatus
b false

Related Issue
https://github.com/harvester/harvester/issues/1132

@johnliu55tw I'm not sure if this can solve the issue, I'll apply the patch on my tests. Please take a look, thanks!

I'm thinking if systemd message only output to tty1, can we start Harvester console on other virtual console and then we switch to that one to prohibit systemd messages?

I'm thinking if systemd message only output to tty1, can we start Harvester console on other virtual console and then we switch to that one to prohibit systemd messages?

Could you test if that works? We also need to consider headless situations like there is only serial console available.

Yeah for the serial console case I think my proposal would not fit. I'll first verify if this PR could fix the issue.

@johnliu55tw Using a different TTY is still more elegant. I think we can move forward with this approach if possible.


add webdav support

Is your feature request related to a problem? Please describe.
So files can be added/created/modified in windows explorer
Describe the solution you'd like
builtin webdav support would be nice
Describe alternatives you've considered
dufs web server, https://github.com/filebrowser/filebrowser.
Additional context
Add any other context or screenshots about the feature request here if needed.

SWS is basically a web server that focuses on serving static files but is not a file manager.
So in that sense. Unfortunately, I do not see Webdav being a feature for SWS.
Unless you have a strong opinion on why Webdav should be considered as a feature.
Maybe Webdav could be a thing in the future, who knows but definitely not in the current stable.


Build spdlog as a shared library

The default configuration of spdlog is as a really big header only library, making each file which (possibly indirectly) includes a spdlog header take a lot longer to compile.
The previous linux build took 4 minutes and 58 seconds on github actions, but with this change takes 1 minute and 29 seconds, which is only a few seconds longer than it was before spdlog.
Also some small tweaks to prevent the thousands of lines of warnings generated by spdlog on linux and to make my IDE happy with the git submodule.

Pull Request Test Coverage Report for Build 285915772

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.009%) to 81.574%

Files with Coverage Reduction
New Missed Lines
%

game/overlord/iso_cd.cpp
1
13.03%

Totals

Change from base Build 285869186:
-0.009%

Covered Lines:
14238

Relevant Lines:
17454

💛  - Coveralls


Investigate UX improvements to the azd up provisioning flow

Background
As part of our usability studies and experience audit, we have identified that end-users sometimes struggle to understand what is happening behind the scenes when they run azd provision (or azd up during the provisioning stage). This contributes to the following negative outcomes:

Decreased likelihood of using the tool again due to lack of understanding
Inability to fully utilize capabilities of the azd CLI tool because they don't understand the various commands (init, deploy, provision, etc.)
Ensure that the developer can have a consistent mental model between azd and the Portal
Inability to troubleshoot error or failure states (we will focus specifically on error and failure states in X issue)

Hypothesis
We believe that we can reduce the amount of end-user journeys that end in failure, increase the likelihood a user will use azd again, and also increase a user's comprehension of the Azure Developer CLI by doing the following:

Introducing layout, language and visual improvements to the provisioning flow
Surfacing line-by-line feedback on each service as they're provisioned (aids in troubleshooting and comprehesion)
Closing the feedback loop by improving our success state messaging

Initial task list

[x] Investigate and capture existing experience and opportunities for improvement [@Austinauth]
[x] Quick audit of competitor experiences [@Austinauth]
[x] Create low-fidelity sketches exploring improvements to the provisioning flow (easy to implement & blue sky) [@Austinauth]
[x] Review low-fidelity sketches with team, capture feedback [@Austinauth  + Team]
[ ] Incorporate team feedback into designs and create final sketches for review [@Austinauth ]
[ ] Set up time with the developer who will be implementing [@savannah]

Relevant links

Initial experience audit
Accelerators Research Report
Provisioning flow improvements - Explorations (Figma)

Update: 08/08/2022

Completed initial explorations of an improved provisioning flow (Figma file)
This includes explorations of: flow, layout, headers, provisioning items, color, loading states and more
Setup time for us to discuss the explorations on 08/11/2022 (Feedback, critique, etc.)

Next steps:

Review explorations with team during 08/11/2022 - capturing feedback and ideas
Narrow down options we like best
Incorporate feedback into designs

cc: @puicchan @savannahostrowski

@Austinauth will the design support no-color environments?  https://no-color.org/

@Austinauth will the design support no-color environments? https://no-color.org/

Designs should work without color if user chooses to go that route. Colors will enhance the experience, but we won't rely on color only for any affordances.

Update 08/16/2022

@savannahostrowski to get me included on the bi-weekly dev demos
Will showcase this work on the dev bi-weekly demo call
Need to have discussion with Devs during that call on how we implement
How do we measure success since we are not doing a UXR session?
Don't need a/b testing since not comparing two options
Low risk that this makes the experience worse
Implement changes and next time we do a lab we'll focus more heavily on reactions to the CLI

Overall, I love the direction.  A few small notes:
I've noticed today that we use the prefix "Created" for resources in our status messages, even in cases where you run azd up a second time, without changing the infrastructure in any way.  If we can determine an operation did a create vs an update for a resource, I think we should surface that in the tool.  If we can't (I'm not 100% sure on the fidelity of the ARM API here) I think we need to come up with some other word other than "Created".  It's very confusing on subsequent updates to see "Created" for a resource that already exists (and made me wonder if were creating multiple copies)
This may be out of scope, but I think we need to think a lot about if azd up --template is really a thing we want long term.  I think the general concern here is that in steady state you never pass --template to azd up.  It's something you may do once, when initializing you project, but never again.
One of the nice things about azd up --template was it provided a single command that got you from "zero to wow" quickly.  It demos super well.  But I think we should still remove this support.
In fact, in https://github.com/Azure/azure-dev/pull/235, we are removing the usage of azd up --template from our prose, precisely because it has caused user confusion.
I think we should remove the --template parameter from azd up.  Instead, just support it on azd init (a command you would run only once anyway).

A consequence of removing --template from up perhaps means that up now just means provision + deploy.  init is no longer part of the up flow (since you only use up once you have a project initialized).

@ellismg

I've noticed today that we use the prefix "Created" for resources in our status messages, even in cases where you run azd up a second time, without changing the infrastructure in any way. If we can determine an operation did a create vs an update for a resource, I think we should surface that in the tool. If we can't (I'm not 100% sure on the fidelity of the ARM API here) I think we need to come up with some other word other than "Created". It's very confusing on subsequent updates to see "Created" for a resource that already exists (and made me wonder if were creating multiple copies)

This is a great idea. Love this. Could definitely help clarify that running azd up is not just something you can do once.

This may be out of scope, but I think we need to think a lot about if azd up --template is really a thing we want long term. I think the general concern here is that in steady state you never pass --template to azd up. It's something you may do once, when initializing you project, but never again.
One of the nice things about azd up --template was it provided a single command that got you from "zero to wow" quickly. It demos super well. But I think we should still remove this support.
In fact, in https://github.com/Azure/azure-dev/pull/235, we are removing the usage of azd up --template from our prose, precisely because it has caused user confusion.
I think we should remove the --template parameter from azd up. Instead, just support it on azd init (a command you would run only once anyway).

Yeah, probably out of scope for this. But I definitely see what you're talking about. I'm not sure I have a fully informed opinion on the matter yet, but certainly a discussion I'm interested in being a part of.

A consequence of removing --template from up perhaps means that up now just means provision + deploy. init is no longer part of the up flow (since you only use up once you have a project initialized).

Yeah, I would be very open to exploring this, but I don't feel confident enough to make a call on one approach over the other yet. Perhaps this is something we could prototype and a/b test? cc: @savannahostrowski , @puicchan

A consequence of removing --template from up perhaps means that up now just means provision + deploy. init is no longer part of the up flow (since you only use up once you have a project initialized).

I disagree about removing --template from up, so let's discuss before that happens.  Having a single command that get a complete solution up on Azure is a big selling point and value prop - the soul of azd.

I've noticed today that we use the prefix "Created" for resources in our status messages, even in cases where you run azd up a second time, without changing the infrastructure in any way. If we can determine an operation did a create vs an update for a resource, I think we should surface that in the tool. If we can't (I'm not 100% sure on the fidelity of the ARM API here) I think we need to come up with some other word other than "Created". It's very confusing on subsequent updates to see "Created" for a resource that already exists (and made me wonder if were creating multiple copies)

This is a great point. We should definitely see where it's possible to differentiate between "created" and "updated" (or similar).

A consequence of removing --template from up perhaps means that up now just means provision + deploy. init is no longer part of the up flow (since you only use up once you have a project initialized).

I think we'd really want to understand developer workflows and preferences with azd before deciding to remove --template from up. We do have an issue/discussion tracking asking whether people think that init belongs in 'up` (see https://github.com/Azure/azure-dev/discussions/114) but as of yet, it has not gotten a lot of community attention or feedback.

Update 08/23/2022

Expect discussion on how to best implement during our demo call today
Follow up with Developers on how I have help provide them with guidance

A consequence of removing --template from up perhaps means that up now just means provision + deploy. init is no longer part of the up flow (since you only use up once you have a project initialized).

I disagree about removing --template from up, so let's discuss before that happens. Having a single command that get a complete solution up on Azure is a big selling point and value prop - the soul of azd.

Absolutely agree. "One command to rule them all!".
Two things I would love to see here are:

Acknowledgement in the progress that the resources already exist (per the comment about differentiating between "created" and "updated")
"If it ain't broke, don't fix it" - figure out fast if the deployment will change a resource and if not, move on quickly. Perhaps azd is already doing this and the comparison is very slow, but ideally, if all I changed was adding a comment in a python file, azd up should run nearly as fast as azd deploy.

Seeing creating (3 of ~5 completed) change to (10 of ~11 completed), drives my brain nutz.
I love the idea of showing progress, but I would much rather you didn't show me the 'of ~##' part than keep moving the goalposts.

@charris-msft Our latest concepts remove this confusing piece of feedback in favor of showing more generalized progress!
Here's an example of how the loading state + feedback will look for individual items as they're provisioned / deployed (loading bar + success/failure state).

As for recovering SRE who spent lots of time watching the command line, I really appreciate it when I can estimate how much time is left, but if we can't do it well this is much better than today's experience.
Is it not possible to show all of the resources and then fill in the progress as azd is working on each one?

@charris-msft

As for recovering SRE who spent lots of time watching the command line, I really appreciate it when I can estimate how much time is left, but if we can't do it well this is much better than today's experience.

We had mocked up a few variations that explored showing the time left and the completion %, however, technically it doesn't sound like this is feasible at the moment without adding a significant amount of loading time. 😢
I'll continue to push on this in the future though.

Is it not possible to show all of the resources and then fill in the progress as azd is working on each one?

Hmm.. this is a good question, not something I had initially considered. I just want to make sure I'm understanding you correctly. You're suggesting that as soon as the provisioning starts you would like to see all the services being provisioned listed at once, and then the progress of each item individually?
I had just assumed items were provisioned in order and that this would not be possible, but I can definitely take it back to the team and create some explorations!

@Austinauth -
regarding showing all the resources - perhaps something like this if there are just 4 resources being created:
Creating resources
(v Done): App Service Plan: plan_abcdefg
(v Done): Log Analytics Workspace: log_abcdefg
(==    ): Application Insights: appi_abcdefg
(pending): Portal Dashboard: appid_abcdefg

@charris-msft Gotcha! I'll check with the team to see if something like this is doable 👍🏼

@vhvb1989 You can find all the flow updates in this prototype under the "UX Flows" section. Feel free to reach out if you have any questions or want to pair on anything!

@Austinauth can we close this from a design perspective. Implementation tracker - https://github.com/Azure/azure-dev/issues/557

Closing this as done from a UX design perspective.


investigation: possible bug with eslint warning caching?

Reportedly, the vim buffers bug persisted past an closing and re-opening.
The client used was coc-eslint with CoC and regular Vim. This will probably be mitigated by fixing #1, but it would still be good to know the behavior backing that issue persistence.

Closing as I was unable to reproduce this issue.


Enable BT classic

After following all the steps to compile the AT library and solving an issue in the ESP-IDF library :
https://github.com/espressif/esp-idf/issues/4658
I have been able to build the AT command set successfully.
But the ESP-WROOM-32 seems not be able to find the bootable app partitions anymore after changing the menuconfig.
I (254) esp_image: segment 4: paddr=0x00140018 vaddr=0x400d0018 size=0x130d74 (1248628) map
I (696) esp_image: segment 5: paddr=0x00270d94 vaddr=0x40083258 size=0x17d54 ( 97620) load
I (737) esp_image: segment 6: paddr=0x00288af0 vaddr=0x400c0000 size=0x00064 (   100) load
E (738) esp_image: Image length 1608576 doesn't fit in partition length 1572864
E (743) boot: OTA app partition slot 0 is not bootable
E (749) esp_image: image at 0x280000 has invalid magic byte
E (755) boot: OTA app partition slot 1 is not bootable
E (761) boot: No bootable app partitions in the partition table
I (60) boot: ESP-IDF v3.3-dirty 2nd stage bootloader
I (60) boot: compile time 16:16:47
I (60) boot: Enabling RNG early entropy source...
I (64) boot: SPI Speed      : 40MHz
I (68) boot: SPI Mode       : DIO
I (72) boot: SPI Flash Size : 4MB
I (76) boot: Partition Table:
I (80) boot: ## Label            Usage          Type ST Offset   Length
I (87) boot:  0 phy_init         RF data          01 01 0000f000 00001000
I (94) boot:  1 otadata          OTA data         01 00 00010000 00002000
I (102) boot:  2 nvs              WiFi data        01 02 00012000 0000e000
I (109) boot:  3 at_customize     unknown          40 00 00020000 000e0000
I (117) boot:  4 ota_0            OTA app          00 10 00100000 00180000
I (125) boot:  5 ota_1            OTA app          00 11 00280000 00180000
I (132) boot: End of partition table
I (136) boot: No factory image, trying OTA 0
The Wroom was having ESP32-WROOM-32_AT_Bin_V2.0 installed before as a baseline.
I have been performing the following steps in the menuconfig for re-building the AT set.
Enable BT classic
Component config -> AT -> [*] AT bt command support.
Set the UART port to align with ESP-WROOM-32
Component config -> EPS32-Specific-> [] UART for console output -> Custom.
Component config -> EPS32-Specific-> [] UART TX 17
Component config -> EPS32-Specific-> [*] UART RX 16
Set the correct output (connected with the ESP32 programming port).
Serial Flashed config - /Dev/COM7
Is there something I forget here ?
Is there an address I need to change to get this installed on the correct location ?
When I reprogram the released "esp-at.bin" at address location 0x100000 into the tool.
The tool is able to boot normally again without any issues mentioned.
But the AT commands are not handled normally.
It seems there is a misalignment with the written data locations and the existing..

Is the issue solved? May I close it?


Prepare Shelley NetworkLayer for rollback

Context
Adjust the Shelley network layer nextBlocks function so that,
instead of returning an error on rollback, it returns RollBackward.
This relies on the Shelley version of the network layer being a
stateful process.
Decision
Adjust nextBlocks to possibly return a RollBackward command.
The return types are modelled loosely on the Chain Synchronisation
Protocol from the Shelley networking spec.
data NextBlocksResult
  = AwaitReply
  | RollForward [Block (Tx t)]
  | RollBackward BlockHeader

nextBlocks :: NetworkLayer m -> BlockHeader -> ExceptT ErrGetBlocks m NextBlocksResult

Acceptance Criteria

ErrNextBlocksRollBack should be removed
Receiving the RollBackward message from the node results in a RollBackward return value from nextBlocks.

Development Plan

PR

Number
Base

#?
master

QA

Any work regarding the Haskell nodes is now of lower priority until the wallet reaches completeness regarding early Shelley features. So, closing this in order to prioritize the work on Jörmungandr instead.


A Autocomplete Tools For JavaComplete2

for some people who does not use YCM or Neocomplete

[ ] AutoComplete
[ ] closepairs

I think this function could be add into this plugin,as you know many peopel does not use YCM or other autocomplete plugin,so i add this function in it ,add this will not slowdown the speed of complete!
if any one want to use this function, he just need to add this to his vimrc
let g:auto_javacomplete2_wsd = 1

if do not add this to vimrc ,it just same as the previous commit!

here is my minivimrc you can have a try with the autocomplete
https://github.com/wsdjeg/DotFiles/blob/master/vimrc.vundle

i have add all the func to my vimrc,so the issue should be closed

#18


Implement Vertex AI kit

With all the cool stuff coming out of Vertex AI, we want to have a kit for their cool bits.

Still relevant, and worth doing.


[src/CMakeLists:txt]: cjson include flags from pkgconfig

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


Unlimited number of params at routing

Do we have some way of receiving any number of args from commands?
when(['/sum *'', ...]

Example:
/sum 1 2 3 4 5

I think we can add this in new version

Is this added? It'd be nice if you could add issue numbers in your commits or PR's so that it can be easier to track for others.

I could read a list of args by doing this. I don't think you need to implement something new if you just add this to the README
/sum 1 2 3 4

let params = $.args.split(' ')

=> ['1', '2', '3', '4']


Sync kerbals between clients

Kerbals are not in sync with the other players.
Ideally when a player "takes" a kerbal it should not be available to be used by other players

High priority as when 2 vessels share the same kerbals the last one that starts flying will see the kerbal with noise...

Finished :)


Align rootio with the current metadata format

Description
As it is now, rootio doesn't unmarshal the metadata returned for the node and doesn't perform any specified actions.
Why is this needed

Fixes: https://github.com/tinkerbell/hub/issues/75
How Has This Been Tested?
This has been tested by building a rootio with this change and running in the workflow.
Checklist:
I have:

updated and tested with the test json files

Cc @jacobweinstock for additional set of eyes

I've followed the DCO instructions and signed my commits.

seems reasonable to me. Thank you @vilkaspilkas!


Max. Number of Repetitions timer is not removed when the progress is completed

If the progress completes before the max-number-of-repetitions is reached, the timer should be removed.

Fixed with v22.1!


[CHA-RL3] Implement Room RELEASE operation

Implement all spec items that come under CHA-RL3.
Implement related integration tests.
Split from #6

┆Issue is synchronized with this Jira Task by Unito

Part of the impl. dependent on https://github.com/ably/ably-chat-js/issues/399


I want to use the middle mouse button instead of the left button to respond to the pan event, how should I use

I need to respond to the left shoulder on the svg, which conflicts with the pan, so I want to change the pan event to the middle button response

window.onmousedown = (e) => {
if (e.button === 2 || e.button === 0) {
svgObj[${this.currentTabIndex}]?.disablePan();
} else if (e.button === 1) {
svgObj[${this.currentTabIndex}]?.enablePan();
}
};


ipdk connect not working

I am trying to use the networking build with containerized version. I am following the steps described in

My host machine is running Ubuntu 22.04.
After the vagrant is up when I try to execute the following  command
ipdk connect
It gives the following output.

vagrant@ubuntu2004:~$ ipdk connect
-bash: ipdk: command not found
vagrant@ubuntu2004:~$

Can someone please guide me a bit here.

When you do vagrant up and vagrant ssh to your machine
Go to cd /git/ipdk since this is synced folder as you can see in Vagrantfile
Then run ./build/ipdk -install <your OS of choice>
you should see the message
As last step execute:
  export PATH=/git/ipdk/build:$PATH
to add the IPDK CLI to your path in the running environment!

When you do  export PATH=/git/ipdk/build:$PATH  you'll resolve ipdk: command not found problem
To connect to ipdk, first you need to launch ipdk container, so:
ipdk start -d (-d for daemon)
And finally ipdk connect

@jafingerhut i've seen in your README that you've mentioned it as well (Follow instructions in file build/networking/README_DOCKER.md, under heading "Login to the VM":)
@mestery @dandaly  what about extending provision.sh with export PATH=/git/ipdk/build:$PATH >> /etc/profile or some .bashrc? so the ipdk command will be available out of the box on vagrant's VM?

Anything that can be added to the README steps for installation that makes them work for more people, more completely, without any missing steps that they have to figure out on their own, or search through Github issues to find out, is a good thing, in my opinion.  Why make people who want to use your software solve puzzles, when you can give them working complete instructions?


npm ERR! 404 Not Found - GET https://registry.npmjs.org/less-plugin-clean-css - Not found

npm install -g less-plugin-clean-css
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/less-plugin-clean-css - Not found
npm ERR! 404
npm ERR! 404  'less-plugin-clean-css@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2024-12-08T18_24_39_813Z-debug-0.log

@drexlma seems to be an NPM issue?

yes sorry: https://status.npmjs.org/
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 08, 2024 - 18:00 UTC


Fix main rentry.co domain plz

part of our project stopped working, we can not change old domain to org, fix rentry.co plz
We need it as fast as possible

Same issue here


Support RAM for Tencent COS

With RAM support, we don't need to have Access key and secret keys in Redis.

It seems that COS does not support RAM, close it for now.


Write a JavaScript program to find the trace of a matrix

Description
Write a JavaScript program to find the trace of a matrix
The trace of a square matrix is the sum of the elements on the main diagonal (from the upper left to the lower right).
Input  :
1 2 3
4 5 6
7 8 9

Output :
15

How to contribute

Save the solution in program/FindTheTraceOfAMatrix.js file
Add FindTheTraceOfAMatrix.js file in find-the-trace-of-a-matrix folder

!assign


Update doc for ACR credential helper configuration

Fixes #1530.
@andxu following the same template and pattern for other credential helper documentation, I did not list the detailed steps to configure the ACR credential helper. I think we'll keep this simple and consistent.

@andxu I also think <credHelper>acr-windows</credHelper> is unnecessary as long as acr login configures ~/.docker/config.json correctly.

@chanseokoh The document looks good to me, thanks

@chanseokoh , yes, <credHelper>acr-windows</credHelper> is unnecessary, the config.json will set the right credential store for the file in ~/.docker/config.json during the installation of acr helper


added Apache 2.0 license

Added Apache 2.0 license in order to ensure that users can consume the code from Alpakka and use it in production.
Going to need the following existing contributors to write the following comment on the thread here in order to keep it kosher:
"I agree to license my previous commits to this repository under the terms of this license"

[x] @Horusiath
[x] @Silv3rcircl3
[x] @Arkatufus

I agree to license my previous commits to this repository under the terms of this license

I agree to license my previous commits to this repository under the terms of this license

I agree to license my previous commits to this repository under the terms of this license

Thanks gents!