Add test fcr

For the PR were introduced changes:

changed api client (okhttp on rest-assured) and regenerated all classes
modified existing tests and adjusted for new client
added tests for Cloud Router endpoints
added test for Port endpoint
added flow to run tests only

@tutkat , please add descriptions of why you changed what you changed. The status update was confusing as well so it's important to add as much context as you can to whomever will be reviewing your code.

It looks like this is a breaking change for existing users of the Java SDK. What will be the outcome to the user? Do they have to adjust their code based on this update?
We need to prevent breaking changes because our customers have to make many modifications as a result. We only make them if absolutely necessary and I still haven't seen enough evidence in your description to warrant the breaking change. What was the exact issue that okhttp-gson gave you that rest-assured is not?

I don't know the reason but this client wasn't able to execute POST calls. I'm sure any client didn't do that because someone reports that doesn't work. I spent few days to try to configure it but unfortunately I was forced to move to another http client

I don't know the reason but this client wasn't able to execute POST calls.

How does this issue manifest?  Are the requests never sent at all?  Are they sent in an invalid format and failing?  Is the API responding with an HTTP error?  Are all POST calls impacted or only for particular endpoints?  The metal-java SDK also uses okhttp-gson, and although metal-java is now defunct it was definitely used successfully to send POST requests, which indicates it should be possible for fabric-java to send POST requests successfully without introducing a breaking change to the client.

@tutkat, please remove code generation from this PR. You need to figure out how to separate your test files from any changes you've made to the SDK during this time. There shouldn't be changes to 1,209 files just to add your tests.

@tutkat , this PR cannot be reviewed until it has been trimmed.


[CMT-975-1348] add(article): how-to-contribute-to-daos - EN

Description
Add the transcription for How to Contribute to daos
Type of change

Please delete options that are not relevant and check the box.

[X] Add a new article/page
[ ] Fix a Typo
[ ] Add a new translation
[ ] Other

hey @DarkGhost7 , could you check and remove this from the changed files?

also, could you check the image dimensions in the article, they do not match the img files

Will do!


test(composer-app): skip collab tests in webkit when not on macos

copilot:all

Current dependencies on/for this PR:

main

PR #3045

PR #3051   👈

This comment was auto-generated by Graphite.

@wittjosiah queued this pull request to merge with Graphite.

Graphite rebased this pull request as part of a merge.


Load and bootstrap Angular within web worker without manually creating window and document objects

It is currently (Angular 1.3.17) possible to load Angular, and bootstrap a module within a web-worker, but it needs window and document with a few stub properties/functions that Angular assumes is in place. The following example is in worker.js and loaded by new Worker("worker.js");
// Angular needs a global window object
var window = self;

// Skeleton properties to get Angular to load and bootstrap.
self.history = {};
var document = {
  readyState: 'complete',
  querySelector: function() {},
  createElement: function() {
    return {
      pathname: '',
      setAttribute: function() {}
    }
  }
};

// Load Angular: must be on same domain as this script
importScripts('angular.js');

// Put angular on global scope
angular = window.angular;

// Standard angular module definition in separate file (so can be loaded by Karma/other test runner)
importScripts('worker-app.js');

// No root element seems to work fine
angular.bootstrap(null, ['worker-app']);

I suspect Angular should itself support being loaded in the web worker environment, so it doesn't need window / document, and can just use self (perhaps then injectable as $self?).

I think it might be possible to load angular in a web worker. Maybe if you explain the issue that you are having, it would ease things up

Ah sorry I was unclear. Yes, it is possible, but only if you create the window and document objects in the global scope as in the code in the issue. If this isn't done, at various stages in the loading/bootstrapping process, exceptions are thrown due to undefined objects/properties.
It seems a bit hacky to have to do this, so my issue/suggestion is that Angular should support being loaded without window and document being present in the global scope. The web worker environment has self as the global object, so Angular could use that, and then test for the presence of document when required?

Hi, I would like to know is what are you trying to achieve by loading
Angular in a web worker. This is, why do you need this

I'm writing a Javascript JPEG decoder (yes, I know others exist), and the bulk of the processing is done in a web worker. Doing it in Angular service(s) allows me to use the dependency injection system, $q, and unit test the worker code much like any other service. It would also (I suspect, I haven't needed to so far) allow code, as Angular modules, be used in both the worker and UI environments.

I created a minimal patch that would make angular boot inside a web worker. You can find it at https://github.com/lgalfaso/angular.js/commit/acd3e479d737d6f3a1bd8c0ec0f2587daf42d5f8. There are several things that I doubt that they will work as expected (eg $location, same origin $http, cookies)
Now, I doubt that will get a lot of traction, but will let @petebacondarwin decide

We've recently removed all direct references to window but you still need to provide a window object with a functional document. I don't think there are plans to make angular 1.x fully "universal".


Fixed issue with emotion tone - likely, unlikely calculation

The float values were being compared as strings.
As a result 5.0 value was being marked greater than 40.0

Thanks for submitting this.  I think it would be better to fix the underlying function _percentagify so that other parts of the code that use this don't suffer from the same problem.
Also,  some tests to describe the problem and demonstrate the new code has fixed it.


Tests for recommendation component

@gkarat Is this also a federated module?

@ikerreyes, yep, all the rule details (before the Affected clusters table) is a federated module from RHEL https://github.com/RedHatInsights/insights-advisor-frontend/blob/master/src/PresentationalComponents/RuleDetails/RuleDetails.js

Closing as is related to a federated module


Plugging vector-quantize-pytorch into taming-transformers

Hi,
I noticed your architecture could be plugged within the pipeline from https://github.com/CompVis/taming-transformers. I have proposed a code here (https://github.com/tanouch/taming-transformers) doing that. It enables to properly compare the different features proposed in your repo (Lower codebook dimension, Cosine similarity, Orthogonal regularization loss, etc) with the original formulation.
The code from this repo can be seen in both files

taming-transformers/taming/models/vqgan.py
taming-transformers/taming/modules/vqvae/quantize.py

As you can see, it is easy to launch a large scale training with your proposed architecture.
I am not sure this issue belongs here or in the taming-transformers repo. However, I thought you might be interested.
Thanks again for your work and these open-sourced repositeries !

@tanouch thank you! i'm also open to redesigning the base class (or adding an adapter wrapper on top) that would allow it to plug into the taming transformers library more easily, if you think that makes sense

Hi @lucidrains,
Thanks for your response... So the way I understand it is that your current base/main class "class VectorQuantize" is the equivalent of the class "class VectorQuantizer" from (https://github.com/CompVis/taming-transformers/blob/master/taming/modules/vqvae/quantize.py).
This consequently makes the two following classes the same...(and redundant)

class VQModel (from TT)
class VQLucidrainsModel (deriving from your quantizer)
(here: https://github.com/tanouch/taming-transformers/blob/master/taming/models/vqgan.py)

Maybe, we could simply add an argument in the constructor of the VQGAN class specifying what quantizer are we going to use...
What do you think ?


Delete CUDA buildchain from RHODS deployer

Delete CUDA build chain from RHODS deployer
Description
This PR deletes the CUDA build chain code from odh-deployer repository. The new pre-build images now are going to be loaded into RHODS through ImageStreams objects that will be located jupyterhub/notebooks/overlays/additional on odh-manifests repository. The corresponding PR is here
Files that deleted:

buildchain.sh
nbc/cuda-11.4.2/manifests.yaml
From prometheus-configs.yaml (on the 'alerting.rules' section deleted the part of build alerts)

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message.
[x] JIRA link(s): https://issues.redhat.com/browse/RHODS-5336
[ ] The Jira story is acked.
[x] Live build image:  quay.io/rh_ee_atheodor/rhods-operator-live-catalog:1.18.0-rhods-5336
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] QE contact acknowledges that this has been tested and is approved for merge.

/hold WIP

Is there a corresponding rhods-live-builder PR yet for the dockerfile updates?

Not Yet, I am working on it, I will update all the correspond PR with it when it will be ready

/unhold

Tested the latest live build (quay.io/rh_ee_atheodor/rhods-operator-live-catalog:1.20.0-rhods-5336) and images are looking good (i.e. cuda is present), still in the process of going through all automated tests.


rdMolDraw2D, problems during generation of pictures from SMARTS, differences between Cairo and SVG

Configuration:
import rdkit
rdkit.version
-->

RDKit Version: 2020.09.1
Operating system: MacOSX Darwin
Python version (if relevant): 3.7
Are you using conda? Yes
If you are using conda, which channel did you install the rdkit from? rdkit
If you are not using conda: how did you install the RDKit?

Description:
I would like to generate pictures for some SMARTS definitions using rdMolDraw2D. I found that for some SMARTS it is not possible to generate pictures using Cairo, as it ends up with kekulization error. The same procedure using SVG as is succesful. Setting parameters like prepareMolsBeforeDrawing = False, or PrepareMolForDrawing(mol, kekulize=False), does not help and ends up with the same error. Example code below

Working code for SVG engine

from rdkit import Chem
from rdkit.Chem import AllChem
from rdkit.Chem import Draw
from rdkit.Chem.Draw import rdMolDraw2D
from rdkit.Chem import rdDepictor
rdDepictor.SetPreferCoordGen(True)
from rdkit.Chem.Draw import IPythonConsole
from IPython.display import SVG
import rdkit
print(rdkit.__version__)
mol = Chem.MolFromSmarts('c[N+]#[N]')
d2d = rdMolDraw2D.MolDraw2DSVG(300, 300)
d2d.DrawMolecule(mol)
d2d.FinishDrawing()
SVG(d2d.GetDrawingText())

The same for Cairo

from rdkit import Chem
from rdkit.Chem import AllChem
from rdkit.Chem import Draw
from rdkit.Chem.Draw import rdMolDraw2D
from rdkit.Chem import rdDepictor
rdDepictor.SetPreferCoordGen(True)
from rdkit.Chem.Draw import IPythonConsole
from IPython.display import SVG
import rdkit
print(rdkit.__version__)
mol = Chem.MolFromSmarts('c[N+]#[N]')
d2d = rdMolDraw2D.MolDraw2DCairo(300, 300)
d2d.DrawMolecule(mol)
d2d.FinishDrawing()

end up with error:
RDKit ERROR: [17:49:00] non-ring atom 0 marked aromatic
It does not work even if I try to switch preparation of molecule before drawing
from rdkit import Chem
from rdkit.Chem import AllChem
from rdkit.Chem import Draw
from rdkit.Chem.Draw import rdMolDraw2D
from rdkit.Chem import rdDepictor
rdDepictor.SetPreferCoordGen(True)
from rdkit.Chem.Draw import IPythonConsole
from IPython.display import SVG
import rdkit
print(rdkit.__version__)
mol = Chem.MolFromSmarts('c[N+]#[N]')
d2d = rdMolDraw2D.MolDraw2DCairo(300, 300)
d2d.prepareMolsBeforeDrawing = False
Options = d2d.drawOptions()
Options.prepareMolsBeforeDrawing = False
d2d.SetDrawOptions(Options)
mol1 = rdMolDraw2D.PrepareMolForDrawing(mol, kekulize=False)
mol1.UpdatePropertyCache(False)
d2d.DrawMolecule(mol1)
d2d.FinishDrawing()

RDKit ERROR: [17:52:50] non-ring atom 0 marked aromatic

The difference is that the Cairo drawer calls addMoleculeMetadata and the exception is being thrown from there.  So it's not a drawing error as such.

@wopozka , the comment from @DavidACosgrove is correct. You can work around the problem (which is a bug) by disabling the code which writes metadata to the PNG Options.includeMetadata = False

@greglandrum, thanks for the valuable advice. As I can use svg that is not a problem for me. I just noticed strange behaviour during png generation and then switched to svg.


Cannot read property 'example' of undefined

I tried to export documentation for a workspace and after creating 700+ md files the output stops with an error Cannot read property 'example' of undefined
Has somebody also seen this? Is there maybe an option to get to some debugging output to see which file broke the process?
EDIT:
Tried again, folder by folder per app. Some work, some break with this error.

Hi @RafaelKoch,
Thank you for reporting this issue. We will looking into it as soon as possible.
Do you see which object causes the crash? Is there an  documentation included?
/Chris

No unfortunately I do not see which object crashed it. The output ends with the last successful object and then the error. I found no way to reliably find the next object to be processed.
Here is one example of a crash:

BTW: when it works, the output is very cool!

Ok, thank you anyway. I will try to reproduce and get back to you.


When integrating a Dishwasher, button.dishwasher_start and button.dishwasher_stop unavailable

The problem
I have the dishwasher fully operationnal, except for the start and stop buttons which are reported unavailable.

config_entry-miele-33f6d178335262caf69a35d998040b72.json.txt
Version of miele integration having the issue?
V 0.1.4
Version of Home Assistant Core having the issue?
Home Assistant 2023.1.6 Supervisor 2023.01.1 Operating System 9.4 Interface utilisateur : 20230110.0 - latest
Anything in the logs that might be useful for us?
No response
Additional information
No response

The button will be displayed as unavailable if the API is not accepting the action in this moment.
This can be seen in the diagnostic dump where the processAction key is empty.
"actions": {
  "Appliance_1": {
    "processAction": [],

Try to power on the device, set a program and close the door. The start button should then be set to available.

Tack,
I will have a check on that.

I also encounter exactly the same issue for both my washing machine and dryer.
I'm able to run automation to power on the device, however always fail to trigger "button.washing_machine_start" as the status is Unavailable.
Device has been powered on, program has been selected and door is closed, but start button still unavailable.

Hi,
The start buttons become available when you set the delayed start on your appliances. So you can start them earlier (for example with an automation that is triggered when energy price is convenient).
The stop buttons should become available while appliances are running.

Hi @aturri thanks clarification. so we still need to input delayed timing/schedule manually in the washing machine or Miele app, then only homeassistant will override with "start button" when energy price is convenient?
Or is there a way in Homeassistant we can send "delayed start" timing to the washing machine?
Appreciate if you can share with me your HA automation script if you have any for your Miele appliances so I can understand better how we can automate it

Hi Ake and Vhardono,
When reading the above from Aturri and Vhardono about the Miele API conditions for "starting and stopping", would it help that the Home Assitant integration/device also has one extra controling entity/attribute: Starttime  (i.e. "to manipulate the startTime" in MIele's cloud)  and whereby the timevalue could be:

the current time of setting this entity and simultanously start the Miele device,
a variable-time-value for future (for those that want to start / stop the Miele device during a specific time window in future), or
0,0, 23 hour, 59 minutes (Latest possible time in that day) ?

e.g. somewhere in the code, something as:
PUT /devices//actions
{
"startTime": [
[0,0],
[23,59]
],
}
And, by the way, when I press the 'start' at Integration/Device (with the time-preset to a later time already in the Miele-mobilephone-app, and hence the press button is available in the Integration/devise controls section) then unfortunately the integration seems (for me) not to have the correct attribute name in the code. Because the error message I got is:
" Failed to call service button/press. 'MieleButton'object has no attribute '_attrr_name' ".
Or did I do something earlier wrong?
Anyhow, already I am appreaciating the works done for collect the sensor and diagnostic data.

I am not sure that I fully understand your first request.
But to start from the end...
Are you sure that the code looks for attribute "_attrr_name" ? Only attr with a single "r" exists in the code.

Hi Ake, you are right 1 r.

And with regards to the first suggestion about the StartTime entity with time value attribute, the attached screenshot may clarify:

Hi Ake, about the first suggestion, the attached screenshot may clarify my thought:

Hi Ake, With regards to the first suggestion, the attached screenshot may clarify.

hi @Wipnose,
As I'm automating my washing machine to start during the cheapest hours, I just use the existing Miele integration with simple automation created in HA. It has been working without any issue so far for more than a month. This is the steps if you are interested to replicate it:
Go to Settings --> Automations & Scenes --> Create Automation. Use YAML format and paste the following code:
alias: Washing Machine Automation               description: ""               trigger:                 - platform: time                   at: input_datetime.device_start_time               condition: []               action:                 - type: turn_on                   device_id: [insert your device ID here]                   entity_id: switch.washing_machine_power_on                   domain: switch                 - delay: _#10 seconds delay to ensure that the first step to turn on device is fully executed by the machine_                     hours: 0                     minutes: 0                     seconds: 10                     milliseconds: 0                 - service: miele.set_program                   data:                     programId: 31 _#this is automatic plus program obtained from Miele API website, you can choose other program ID as needed_                   target:                     device_id: [Insert your device ID here]                     entity_id: sensor.washing_machine_program               mode: single
When you have loaded the machine with laundry, just need to turn the washing machine dial to "Remote Start" and press "Start", then the automation will start by itself at the cheapest hour. If there is no laundry and dial is not at "Remote Start", automation won't run so it will prevent machine to run with empty drum.
Hope that will help you to achieve your goal!


What will I get? or faster ?

Hi , thank you guys build this code, its really help me.
but I have some question on this.
question 1.
I dont want use tquery or pquery but mysql_query.
and I have tested that if I use cache system, I get a ID from mysql_query.
and I have to detele it after data loaded.
I think this is good, but really scared if I forget to detele.
There is some method to prevent this? or proper way?? THX.
question 2.
forward checkPlayerAccount(name[], queried = 0);
public checkPlayerAccount(name[], queried = 0) {
	if(!requeried) {
		new query[128];
		mysql_format(mySQL, query, sizeof query, "SELECT * FROM `accounts` WHERE `name` = '%e' LIMIT 1", name);
		mysql_tquery(mySQL, query, "checkPlayerAccount", format[] = "sd", name[], 1);
	} else {
		// Do something..
	}
};

just like a inline way.... this is a proper way??
question 3.
did really that tquery is faster than mysql_query way??
I made a test for this, but I get 0ms on mysql_query, 6ms on tquery.
I thought the reason is CallLocalFunction??
THX to reply.

1: It can't be checked if you forgot to delete a cache result (as the plugin can't know if you don't need the result set anymore), so just make sure you never forget it.
still need the ID), so just make sure you never forget it.
2: Yes, that will do it (as long as "requeried" is renamed to "queried" and other mistakes will be fixed).
3: mysql_tquery is better because it won't block your server's thread (noticeable at huge/bad queries). It will send the query to the MySQL server and will receive the result, then the MySQL Plugin will automatically call the callback for you to manipulate the result, and after the callback was finished, the MySQL Plugin automatically deletes it for you (so your problem from 1 will be gone). The disadvantage of tquery is that, unlike pquery, it will execute only on one connection, so if another big dirty ugly query is slowly executed, it will block that new query from being executed, but still not your main server's thread ! You will receive the result when it has it. If you use pquery you can send more than one unoptimised query and you will receive the results when they are received from each query. (I don't recommend you to use it just because you don't know how to make some queries optimised, you still have to optimise them)

Nice answer @IstuntmanI, couldn't say it better!


Monterey testing template

[ ] Aurelia-CLI
[ ]  Default ESNext

[ ] npm install && au-run
[ ] NOT npm install && au-run

[ ]   Default ESNext

[ ] npm install && au-run
[ ] NOT npm install && au-run

[ ]  Custom

[ ] npm install && au-run
[ ] NOT npm install && au-run

[ ] skeleton-esnext-aspnetcore

[ ] skeleton-esnext-webpack

[ ] skeleton-esnext

[ ] skeleton-typescript-aspnetcore

[ ] skeleton-typescript-webpack

[ ] skeleton-typescript

[ ] ZIP

[ ] App launcher

[ ] Add app launcher

[ ] Remove app launcher

[ ] Get more ...

[ ]  Share this app launcher

To be added
Aurelia-CLI used for KendoUI (RequireJS loader)
"Frozen" KendoUI-Navigation-Skeletons (need to ensure that KendoUI works with Webpack)

Closing this, it will still exist so we can take this template again when needed


Fix quoting on columns for seeds/incremental models (#1847)

Fixes #1847
There are a few of fiddly places where this is an issue, expanding column types also hits it. Hopefully this is all of them.
Added tests accordingly.

I had to update a lot of tests to get this passing, but no actual code changes.


Custom validation for Request data

Hi,
My nodejs app is using swagger-tools middleware with express which works fine with most of my service's contracts defined in the swagger spec.
I have a requirement where a request's body object's (json payload) some part is dynamic. So, I can't validate it using the spec. I am thinking of using express validation middleware for any custom validation. Is that a sensible approach or can I use swagger middleware for custom validation as well?
Thankyou

Can you elaborate?  Swagger should allow for some level of dynamic even if it's just having an open schema for the dynamic part(s).

Hello, thankyou for the response. Based on the below example I would like vehicleType inside vehicle definition to be of type either car or bike:
paths:
/vehicle:
post:
parameters:
- $ref: '#/parameters/vehicle'
responses:
200:
description: Success!
parameters:
vehicle:
name: vehicle
in: body
required: true
schema:
$ref: "#/definitions/vehicle"
definitions:
vehicle:
type: object
properties:
id:
type: string
name:
type: string
vehicleType:
type: object
anyOf:
- $ref: "#/definitions/car"
- $ref: "#/definitions/bike"
car:
type: object
properties:
model:
type: string
type:
type: string
enum:
- Saloon
- Estate
bike:
type: object
properties:
model:
type: string
type:
type: string
enum:
- Scooter
- Sport

Sorry for the indentation problem above. Not sure how to paste it indented.


nixos/nvidia: enable fbdev when available

Description of changes
In my experience this is required to get Plasma 6 Wayland to work on my GTX 1080 with the proprietary driver. Otherwise, I get errors in my journalctl --user about "MESA-LOADER: failed to open simpledrm" (among many other things) and Plasma just presents a black screen with a cursor and nothing else.
I discovered this by searching the aforementioned error and found this Arch Linux forum post and some further clicking around led me to this section on the ArchWiki, which is where I got the versionAtLeast value from.
Tested with nvidia-x11-555.58-6.9.7.
An alternative to this might be to pull in this kernel patch. Honestly, this stuff is (currently?) beyond my understanding so I'm not sure what the best course of action here actually is.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Tagging kernel people for the potential kernel patch.

It's not feasible (or a good idea) for us to try to maintain kernel patches that will never make it upstream.  If this command line change works, that's probably the way to go.

How do I disable this? fbdev=1 causes SDDM to fail to start for me


feat: add graph-indexed header in subgraph query response

Fixes #494

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

3 of 4 (75.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 80.223%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/service/src/routes/request_handler.rs
3
4
75.0%

Files with Coverage Reduction
New Missed Lines
%

crates/watcher/src/lib.rs
4
92.71%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.04%

Covered Lines:
6827

Relevant Lines:
8510

💛  - Coveralls

@Theodus Thanks for the review. Pushed the changes


[Enhancement] Set up release directories for each integration and setup latest tag for each integration release

Description
Since in PR https://github.com/opensearch-project/dashboards-observability/pull/1860 of dashboards observability we have pointed the sourceURL to the release page of catalog repo, it is necessary for us to set up a release directory under each integration's asset directory. By doing that, we don't have to change the URL link in dashboards observability's sourceURL each time once we are having a new releases. In addition, we should also apply the latest label for the latest release version in catalog repo, so that the sourceURL can always be pointed to the latest release URL.

In principle, since we have legacy releases available in the releases page, we should limit the integrations here to always be the latest ones and let version control handle the historic versioning. Long-term we may want a dedicated version browsing space (the catalog webpage?) to work from, but short-term it works. The bulk of the work I think could be done by making a build directory containing a large bundle of all the built-in integrations in one:
build
|- opensearch_catalog.ndjson

For better granular version control we could also just have the whole per-integration repository directory copied and make the build process separate, though. Better practice and all.


VHD disk feature on blobfuse

Is your feature request related to a problem? Please describe.

Describe the solution you'd like in detail

Create VHD disk in blob storage container directly, and then blobfuse mount to local VM, by this way, disk attach/detach could only costs < 1s
Describe alternatives you've considered

Additional context

Update:
The create vhd operation on blobfuse driver would make system quite slow, and it costs quite a few minutes to running complete. Per current experiment result, I don't think it's a good idea to write VHD disk feature based blobfuse driver, instead, VHD disk feature on azure file is quite amazing.
export AZURE_STORAGE_ACCOUNT=
export AZURE_STORAGE_ACCESS_KEY=
mkdir blob
blobfuse blob --container-name=test --tmp-path=/tmp/blobfuse/
truncate -s 100G /tmp/blob/test.vhd
mkfs -t ext4 /tmp/blob/test.vhd

top - 13:19:11 up 61 days, 11:24,  2 users,  load average: 11.30, 8.00, 3.83
Tasks: 161 total,   1 running,  85 sleeping,   0 stopped,   0 zombie
%Cpu(s):  4.3 us,  6.3 sy,  0.0 ni, 59.2 id, 28.8 wa,  0.0 hi,  1.4 si,  0.0 st
KiB Mem : 14339172 total,   167716 free,  1356240 used, 12815216 buff/cache
KiB Swap:        0 total,        0 free,        0 used. 12277516 avail Mem

   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 52774 root      20   0 1414436 682772   3360 S  34.2  4.8  12:24.35 blobfuse


0.5.8 import error

Failed to notify project evaluation listener.
Could not get unknown property 'android' for project ':image_picker_plus' of type org.gradle.api.Project.
Could not find method implementation() for arguments [project ':photo_manager'] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
Could not get unknown property 'android' for project ':image_picker_plus' of type org.gradle.api.Project.

See the #72 branch and version 0.5.9


[Scheduled Maintenance] TIM server migration and maintenance

Additional context
TIM will undergo a major system upgrade on 8th August starting 18:00 UTC+3. During the upgrade, TIM will be inaccessible for normal users.
The migration is expected to last for at least 30 minutes, but delays are possible. This page will be kept up-to-date with the latest status.

The migration process has started. The current progress will be reported here.
Final system updates are being run before the switchover. Expect TIM servers to go down momentarily.

System updates are being run, after wich the servers will reboot. Expect a 4-5 minute total downtime of the server.

The maintenance page is now being served from the new server. We will continue with transferring the final TIM files over to the new machine. The transfer is expected to take about 20-30 minutes.

TIM documents and uploads have been transferred, the database transfer is in progress. The ETA is 10-20 minutes.

The database has been transferred and is now being restored to the new TIM server. The restore is expected to take 5-10 minutes.

The database transfer is complete. We will run the final update to ensure everything is up to date and then start up TIM.

TIM has been restarted and opened for use. Some systems are still being checked for their functionality.

Final system checks have been completed. TIM is ready to use.
Thank you for the patience! If you encounter any issues, please contact us at<EMAIL_ADDRESS>


Searching for labels by name uses incorrect syntax

Describe the bug
As seen in an article here: https://help.trello.com/article/808-searching-for-cards-all-boards, when looking at the "label" section, the following syntax can be used to search for labels:
label:"FIX IT" or #label
However the second example does not include quotes. I think the Trello API, however, does expect quotes. For example:
#"label"
Upon investigation, the query builder does not seem to add these quotes (which makes sense to me since it doesn't seem to be documented).
To Reproduce
When manually searching, adding the quotes, it works:
var board = trelloFactory.Board(~ID~);
var result = trelloFactory.Search("#\"label_name\"", modelTypes: SearchModelType.Cards, context: new [] {board});

await result.Refresh();
Console.WriteLine(result.Cards.Count());

When attempting to use the search query builder, it does not work:
var board = trelloFactory.Board(~ID~);

await board.Labels.Refresh();
var label = board.Labels.Single(l => l.Name == "label_name");

var query = trelloFactory.SearchQuery().Label(label);
var result = trelloFactory.Search(query, modelTypes: SearchModelType.Cards, context: new [] {board});

await result.Refresh();
Console.WriteLine(result.Cards.Count());

Expected behavior
I expected to be able to search for a label by specifying it when calling SearchQuery().Label().
Desktop

OS: Windows 10
Target: netcoreapp3.1
Version: 4.3.0

Thanks for reporting this.  I've been busy with life and other things lately and haven't had the opportunity to tend to my open source libraries.  I'm happy to review PRs if you want to take a stab at it.  Otherwise, it might be a little bit.

@gregsdennis No worries, especially in these times make sure to take good care of yourself. I found a different way to achieve what I'm doing without using the search api. If I have the opportunity I might submit a pull request, but personally there's no real urgency.


Flag to control emission of line directives

Emitting line directives is probably the right default in "rewriter" mode (since we need to see error messages from the downstream compiler), and it is arguably the right default when you want debug output. It isn't the right thing when people want to look at the output and know what is going on.
Realistically, we probably want:

A direct flag (e.g., -no-line-directives and -line-directives) to control whether we output line directives at all

Make line directives the default for "rewriter" files and when debugging is desired (e.g., when a -g flag is specified), but otherwise skip it

One more detail here is that we might want to either:

switch to always using proper C-style line directives, even for GLSL output, or
give the user a way to control the directive style

This is because glslang at least supports better line directives, so we might as well take advantage of it to produce better error messages in rewriter mode

Pull request #132 added a reasonable level of control for #line directives through the API interface, and I'd like to call that good enough for now. If users want to resurrect this issue, they can.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1050 ms

Resolved: Bofrost.at performance has improved in 555f39a after 9 minutes.


Reduce lag of YouTube embeds

The default youtube embedding script does not play nice with smooth scrolling and causes a bit of stutter lag. This script called Lite Embed embeds YouTube videos without the player itself until clicked.
You could say that it's effectively delaying the actual embedding of the YouTube player until the user clicks it.

 Faster YouTube video loading when embedded


Project: Create and Explore Reference Catalogs

This will be a new notebook showing how to create and use reference catalogs used through the Butler.
Good starting point is here: https://community.lsst.org/t/creating-and-using-new-style-reference-catalogs/1523
Not sure exactly which folder this fits under...maybe Basics?

@bechtol has contributed Validation/refcat_loader_demo.ipynb, maybe this satisfies (or at least starts to address) this issue?
Currently this notebook is only running at NCSA with HSC data, but if someone wanted to modify it to run on the DC2 refcats, then we could also get it running at the IDF. This could also be a good way for @psferguson to get involved and learn about the butler and reference catalogs.

I'd be happy to work on setting that demo up to work on the DC2 refcats.


Doucumentation View is not showing properly on mobile view 320px

Dear Sir,
I read daily ## codeigniter user guide via offline daily on mobile .I am facing problem to read on mobile the user guide offline on 320px  for the latest Version 3.1.2. It break the html norm .I attached the image also taken from Mozilla at 320px. Please fix it.
Thanks
Asraful Haque

<EMAIL_ADDRESS>

I don't really care about the docs working on mobile browsers, but our last 2 doc builds were indeed broken ... We've fixed them, does it display correctly now?

Dear Sir,
Thanks for your response. But I need it because I have only one
source to study it on Mobile. I use Firefox and Chrome . On both browsers
it is broken. If you fixed it , it will be helpful for me!
Thanks
Asraful Haque
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Mob: +91-7042805660
On Tue, Nov 22, 2016 at 4:16 PM, Andrey Andreev<EMAIL_ADDRESS>wrote:

I don't really care about the docs working on mobile browsers, but our
last 2 doc builds were indeed broken ... We've fixed them, does it display
correctly now?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcit-ci/CodeIgniter/issues/4912#issuecomment-262207761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHa0tYyj2Kj_5fXWCCLDw7LldmmWlb_zks5rAsf6gaJpZM4K2LGq
.

You'll have a very hard time convincing me that you're programming on a mobile device with a 320px-wide screen, which is the only case you'd really "need" it.
But beside that, you didn't directly answer my question - after trying to open it now, is it still not displaying properly for you?

Dear Sir,
I wrote you that I have only one source to study it on Mobile
but not programming . How can I program on mobile! I used CodeIgniter
project in our small office but love to study on Mobile browser at home. I
don't have any PC/Laptop.
     *Yes , Still is same problem.It is broken.*

Thanks for your swift response!
Asraful Haque
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Mob: +91-7042805660

I just tested the user guide on my Samsung Rugby, running Android 4.1.2.
The classic layout button does not appear top right, in any orientation.
Going back to my desktop, the classic layout button appears at higher resolutions (which is what I tested originally), but disappears at "small" and "extra-small" window sizes (<772px, it would seem).
I went back to the CI 3.1.0, where the classic layout button appeared "normally", but it disappeared at "small" window size too. The same happens with the CI 3.0.6 user guide.
Conclusion: I suspect that the classic layout button may have been not visible at smaller window sizes for some time now, and that that is an issue possibly unrelated to the current fix :(
@hqasraful Which is the newest version of CI where you noticed the user guide having a working classic layout button visible at smaller resolutions?

Dear Sir ,
I am tired to explain . I have attached three images. All Snapshot taken on the 320px basic!

Show pretty good! Old version

Show nothing on codeigniter 3 1 2 documentation

After some change of the theme.js file on line no 43
(// $('.wy-nav-content-wrap').css({background: 'none repeat scroll 0 0 #fcfcfc;', 'margin-left': '300px'});)

My content shows just perfect except Classic Layout

Thanks
Asraful Haque
<EMAIL_ADDRESS>

Sorry to include that I am using current version CodeIgniter Version 3.1.2. It is also showing classic button but now working(create event).

Well, I'm tired of this too.
@jim-parry All is up to you here.

I think, just remove the old button version 2 and upgrade the new Sphinx RTD Theme with a little customization.

The latest version of Sphinx causes other issues, like the button disappearing altogether at all sizes :(
It could be that a fresh implementation of the feature, and/or getting to the bottom of the latest Sphinx problems, would be a logical next step ... for someone more familiar with Sphinx, and with some time to put into the task.
The CI4 user guide has the same issue, with the classic layout button disappearing at smaller screen sizes.
This needs to be solved at some point, but doesn't feel like a high priority compared to the other work on our plates :(
@hqasraful Have you tried the epub format of the user guide? I seem to recall us adding that becuase of a community member wanting to read the guide on their tablet or smartphone.

This is how it looks on my Samsung Galaxy S7 Edge:

I have also experienced this problem. It should be fixed.

Hmm - I thought this had been fixed, but obviously not.
@Elias-Black A 300px margin is mentioned in two places: lines 43 and 99. Are you suggesting that only the one should be changed?
There was a suggestion emailed to me that one/some of the screen width tests should be looking for a width of 980, presumably in place of 768. Does this make sense?

@jim-parry about the resolution of 768 and 980 pixels: no, it does not make sense. Code from 83 to 101 line works on resize only... I have the bug without entering to these conditions.
Line 43 works on load the pages.

Problem is in /user_guide/_static/js/theme.js
here:
$('.wy-nav-content-wrap').css({background: 'none repeat scroll 0 0 #fcfcfc;', 'margin-left': '300px'});
just wrap it in if statement like that:
if ($(window).width() > 980) {
$('.wy-nav-content-wrap').css({background: 'none repeat scroll 0 0 #fcfcfc;', 'margin-left': '300px'});
}

Hello, I checked the documentation on mobile and this is still the same. The issue is still there.
The problem is when the DOM is ready inline style "margin-left: 300px;" is get added to the section.
One simple fix i came with is adding !important to the css media query here:
file at line: 4
@media screen and (max-width: 768px)
.wy-nav-content-wrap {
     - margin-left: 0;
    + margin-left: 0 !important;
}

This seems to solve the issue.

@jim-parry Again, leaving this one all up to you.  :)

Hopefully put to bed :)


Compat with 4.07

This broke the tests. I'll fix them as it's trivial.

#53 fixes the tests.

Thanks @rgrinberg !


Exception when loading new kstar_hybrid profile

Describe the bug
After updating to latest version 24.08.17, I get an error on the log, and sensor is not updated
Attach the debug log
2024-08-18 15:42:43.028 ERROR (MainThread) [homeassistant.components.sensor] Error adding entity sensor.kstar_dsp_alarm_code for domain sensor with platform solarman
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 662, in state
    numerical_value = float(value)  # type:ignore[arg-type]
                      ^^^^^^^^^^^^
TypeError: float() argument must be a string or a real number, not 'list'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 598, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 912, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1366, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 664, in state
    raise ValueError(
ValueError: Sensor sensor.kstar_dsp_alarm_code has device class 'None', state class 'measurement' unit 'None' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '['0x0', '0x0']' ()

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Metadata:
Version: [e.g. v24.08.17]
Additional context
Add any other context about the problem here.

Hey,
Try remove state_class: "measurement" from entities which are causing issues.

OK, working on removing the "measurement" on problematic entities...


Problems with graceful-fs/polyfills.js : process.version "undefined"

I'm encountering this problem:
I discovered that once I activate this line:
const stateRecord: App = loadSettings()
in /src/store/modules/app.ts
I get this error: "Cannot read property 'match' of undefined"

This is /src/store/modules/app.ts :
import Vue from 'vue'
import { loadSettings, setSettings } from '@/services/electron-services/setting/setting'

const TOGGLE_THEME = 'TOGGLE_THEME'
const TOGGLE_LANG = 'TOGGLE_LANG'

const stateRecord: App = loadSettings()

const app = {
  state: {
    currentTheme: stateRecord.currentTheme || 'light',
  },
  mutations: {
    [TOGGLE_THEME](state: App, currentTheme: Theme) {
      state.currentTheme = currentTheme
    },
  },
  actions: {
    TOGGLE_THEME({ commit }: any, payload: App) {
      setSettings('settings.currentTheme', payload.currentTheme)
      commit(TOGGLE_THEME, payload.currentTheme)
    },
  },
}

export default app

this is src/services/electron-services/setting/setting :
import db from '../database/index'

export const loadSettings = (): App => {
  return db.get<App>('settings')
}

export const setSettings = (key: string, value: string | boolean | number): string | boolean
| number => {
  return db.set<string | boolean | number>(key, value)
}

export default {}

and this is electron-services/database/index.ts :
import Lowdb from 'lowdb'
import FileSync from 'lowdb/adapters/FileSync'
import path from 'path'
import fs from 'fs-extra'
import LodashID from 'lodash-id'
import { app, remote } from 'electron'

interface Schema {
  windowSize: {
    height: number
    width: number
  }
  settings: {
    currentLang: string
    currentTheme: string
  }
}

const isRenderer: boolean = process.type === 'renderer'
// Render process use remote app
const APP: Electron.App = isRenderer ? remote.app : app

const STORE_PATH: string = APP.getPath('userData')

// In production mode, during the first open application
// APP.getPath('userData') gets the path nested and the datastore.js is loaded.
// if it doesn't exist, create it.
if (!isRenderer) {
  if (!fs.pathExistsSync(STORE_PATH)) {
    fs.mkdirpSync(STORE_PATH)
  }
}

class DB {
  private db: Lowdb.LowdbSync<Schema>
  public constructor() {
    const adapter: Lowdb.AdapterSync<Schema> = new FileSync<Schema>(path.join(STORE_PATH,
'/db.json'))
    this.db = Lowdb(adapter)
    // Use lodash-id must use insert methods
    this.db._.mixin(LodashID)
    if (!this.db.has('windowSize').value()) {
      this.db
        .set('windowSize', {
          width: 1025,
          height: 749,
        })
        .write()
    }
    if (!this.db.has('settings').value()) {
      this.db
        .set('settings', {
          currentLang: 'en',
          currentTheme: 'light',
        })
        .write()
    }
    // Purple to Night
    if (this.db.get('settings.currentTheme').value() === 'purple') {
      this.db.set('settings.currentTheme', 'night').write()
    }
    if (!this.db.has('settings.currentLang')) {
      this.db.set('settings.currentLang', 'en').write()
    }
  }
  // read() is to keep the data of the main process and the rendering process up to date.
  public read() {
    return this.db.read()
  }
  public get<T>(key: string): T {
    return this.read().get(key).value()
    //return this.db.get(key).value()
  }
  public find<T>(key: string, id: string): T {
    const data: $TSFixed = this.read().get(key)
    return data.find({ id }).value()
  }
  public set<T>(key: string, value: T): T {
    //return this.read().set(key, value).write()
    return this.db.set(key, value).write()
  }
  public insert<T>(key: string, value: T): T {
    const data: $TSFixed = this.read().get(key)
    return data.insert(value).write()
  }
  public update<T>(key: string, id: string, value: T): T {
    const data: $TSFixed = this.read().get(key)
    return data.find({ id }).assign(value).write()
  }
  public remove<T>(key: string, id: string): T {
    const data: $TSFixed = this.read().get(key)
    return data.removeById(id).write()
  }
  public filter<T, K>(key: string, query: K): T {
    const data: $TSFixed = this.read().get(key)
    return data.filter(query).value()
  }
  public has(key: string): boolean {
    return this.read().has(key).value()
  }
}

The operation setSettings has the same problem:
once I only activate setSettings in src/store/modules/app.ts  I get the same error:
import Vue from 'vue'
//import { loadSettings, setSettings } from '@/services/electron-services/setting/setting'
import { setSettings } from '@/services/electron-services/setting/setting'

const TOGGLE_THEME = 'TOGGLE_THEME'
const TOGGLE_LANG = 'TOGGLE_LANG'

//const stateRecord: App = loadSettings()

const app = {
  state: {
    //currentTheme: stateRecord.currentTheme || 'dark',
    //currentLang: stateRecord.currentLang || 'en',
    //currentTheme: 'light',
  },
  mutations: {
    //[TOGGLE_THEME](state: App, currentTheme: Theme) {
    //  state.currentTheme = currentTheme
    //},
    //[TOGGLE_LANG](state: App, currentLang: Language) {
    //  state.currentLang = currentLang
    //},
  },
  actions: {
    TOGGLE_THEME({ commit }: any, payload: App) {
      setSettings('settings.currentTheme', payload.currentTheme)
      commit(TOGGLE_THEME, payload.currentTheme)
    },
    //TOGGLE_LANG({ commit }: any, payload: App) {
    //  setSettings('settings.currentLang', payload.currentLang)
    //  commit(TOGGLE_LANG, payload.currentLang)
    //},
  },
}

export default app

src/services/electron-services/setting/setting.ts :
import db from '../database/index'

//export const loadSettings = (): App => {
//  return db.get<App>('settings')
//}

export const setSettings = (key: string, value: string | boolean | number): string | boolean | number => {
  return db.set<string | boolean | number>(key, value)
}

export default {}

Also  modifying
public constructor() {
    // const adapter: Lowdb.AdapterSync<Schema> = new FileSync<Schema>(path.join(STORE_PATH, '/db.json'))
    const adapter= new FileSync('db.json')

still get this error

This is the line in fileSync.js which seems to be involved:

It seems that the line involved in node_modules/graceful-fs/polyfills.js is the following:
 process.version.match(/^v0\.6\.[0-2]|^v0\.5\./))

in this function:
function patch (fs) {
  // (re-)implement some things that are known busted or missing.

  // lchmod, broken prior to 0.6.2
  // back-port the fix here.
  if (constants.hasOwnProperty('O_SYMLINK') &&
    process.version.match(/^v0\.6\.[0-2]|^v0\.5\./)) {   // <------------------------------------------------------------------------------------
    patchLchmod(fs)
  }

vue info:
Environment Info:

  System:
    OS: Linux 5.4 Ubuntu 18.04.5 LTS (Bionic Beaver)
    CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
  Binaries:
    Node: 14.5.0 - ~/.nvm/versions/node/v14.5.0/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v14.5.0/bin/npm
  Browsers:
    Chrome: 85.0.4183.83
    Firefox: 80.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.1.2
    @vue/babel-preset-app:  4.4.6
    @vue/babel-preset-jsx:  1.1.2
    @vue/babel-sugar-functional-vue:  1.1.2
    @vue/babel-sugar-inject-h:  1.1.2
    @vue/babel-sugar-v-model:  1.1.2
    @vue/babel-sugar-v-on:  1.1.2
    @vue/cli-overlay:  4.4.6
    @vue/cli-plugin-babel: ~4.4.0 => 4.4.6
    @vue/cli-plugin-e2e-cypress: ~4.4.0 => 4.4.6
    @vue/cli-plugin-router: ~4.4.0 => 4.4.6
    @vue/cli-plugin-typescript: ~4.4.0 => 4.4.6
    @vue/cli-plugin-unit-mocha: ~4.4.0 => 4.4.6
    @vue/cli-plugin-vuex: ~4.4.0 => 4.4.6
    @vue/cli-service: ~4.4.0 => 4.4.6
    @vue/cli-shared-utils:  4.4.6
    @vue/component-compiler-utils:  3.2.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/test-utils: ^1.0.3 => 1.0.3
    @vue/web-component-wrapper:  1.2.0
    babel-helper-vue-jsx-merge-props:  2.0.3
    typescript: ^3.9.7 => 3.9.7
    vue: ^2.6.11 => 2.6.11
    vue-class-component: ^7.2.5 => 7.2.5
    vue-cli-plugin-electron-builder: ~2.0.0-rc.4 => 2.0.0-rc.4
    vue-hot-reload-api:  2.3.4
    vue-i18n: ^8.20.0 => 8.20.0
    vue-loader:  15.9.3
    vue-property-decorator: ^9.0.0 => 9.0.0
    vue-router: ^3.2.0 => 3.3.4
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.11 => 2.6.11
    vue-template-es2015-compiler:  1.9.1
    vuex: ^3.5.1 => 3.5.1
    vuex-class: ^0.3.2 => 0.3.2
  npmGlobalPackages:
    @vue/cli: 4.4.6

  electron version: 10.0.0

This is vue.config.js :
const WorkerPlugin = require('worker-plugin')

module.exports = {
  // options...
  publicPath: '',
  pluginOptions: {
    electronBuilder: {
      // Prevent bundling of certain imported packages and instead retrieve these external
dependencies at runtime.
      // In order to connect to websocket.
      // https://github.com/nklayman/vue-cli-plugin-electron-builder/issues
/652#issuecomment-583764345
      externals: ['ggc', 'tesseract.js'],
      builderOptions: {
        productName: 'GGC',
        win: {
          icon: './public/app.ico'
        },
        mac: {
          icon: './public/icons/Icon.icns',
          target: [
            'pkg',
            'dmg',
            'zip',
          ],
        },
        linux: {
          icon: './public/app.png'
        }
      },
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/configuration.html#webpack-configuration
      chainWebpackRendererProcess: (config) => {
        // Chain webpack config for electron renderer process only
        // The following example will set IS_ELECTRON to true in your app
        config.plugin('define').tap((args) => {
          args[0]['IS_ELECTRON'] = true
          return args
        })
      },
      mainProcessFile: 'src/background.ts',
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/configuration.html#typescript-options
      disableMainProcessTypescript: false, // Manually disable typescript plugin for main
process. Enable if you want to use regular js for the main process (src/background.js by
default)
      mainProcessTypeChecking: false, // Manually enable type checking during webpck
bundling for background file.
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/guide.html#preload-files
      preload: 'src/preload.js',
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/security.html#node-integration
      nodeIntegration: false
    },
    // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide/guide.html#web-
workers
    configureWebpack: {
      plugins: [new WorkerPlugin()]
    }
  }
}

And this is webpack.config.js :
module.exports = {
  entry: './src/background.ts',
  target: 'node',
  output: {
    path: path.join(__dirname, 'build'),
    filename: 'background.js'
  },
  // https://github.com/GoogleChromeLabs/worker-plugin
  plugins: [
    new WorkerPlugin()
  ],
  // https://webpack.js.org/plugins/define-plugin/
  new webpack.DefinePlugin({
    'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV)
  }),
  //https://vuetifyjs.com/en/getting-started/quick-start/#webpack-install
  rules: [
    {
      test: /\.s(c|a)ss$/,
      use: [
        'vue-style-loader',
        'css-loader',
        {
          loader: 'sass-loader',
          // Requires<EMAIL_ADDRESS>          options: {
            implementation: require('sass'),
            fiber: require('fibers'),
            indentedSyntax: true // optional
          },
          // Requires<EMAIL_ADDRESS>          options: {
            implementation: require('sass'),
            sassOptions: {
              fiber: require('fibers'),
              indentedSyntax: true // optional
            },
          },
        },
      ],
    },
  ],
}

This is vue.config.js :
const WorkerPlugin = require('worker-plugin')

module.exports = {
  // options...
  publicPath: '',
  pluginOptions: {
    electronBuilder: {
      // Prevent bundling of certain imported packages and instead retrieve these external
dependencies at runtime.
      // In order to connect to websocket.
      // https://github.com/nklayman/vue-cli-plugin-electron-builder/issues
/652#issuecomment-583764345
      externals: ['ggc', 'tesseract.js'],
      builderOptions: {
        productName: 'GGC',
        win: {
          icon: './public/app.ico'
        },
        mac: {
          icon: './public/icons/Icon.icns',
          target: [
            'pkg',
            'dmg',
            'zip',
          ],
        },
        linux: {
          icon: './public/app.png'
        }
      },
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/configuration.html#webpack-configuration
      chainWebpackRendererProcess: (config) => {
        // Chain webpack config for electron renderer process only
        // The following example will set IS_ELECTRON to true in your app
        config.plugin('define').tap((args) => {
          args[0]['IS_ELECTRON'] = true
          return args
        })
      },
      mainProcessFile: 'src/background.ts',
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/configuration.html#typescript-options
      disableMainProcessTypescript: false, // Manually disable typescript plugin for main
process. Enable if you want to use regular js for the main process (src/background.js by
default)
      mainProcessTypeChecking: false, // Manually enable type checking during webpck
bundling for background file.
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/guide.html#preload-files
      preload: 'src/preload.js',
      // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide
/security.html#node-integration
      nodeIntegration: false
    },
    // https://nklayman.github.io/vue-cli-plugin-electron-builder/guide/guide.html#web-
workers
    configureWebpack: {
      plugins: [new WorkerPlugin()]
    }
  }
}

I've put in node_modules/graceful-fs/polyfill.js
console.log("process.version: ", process.version)  :
function patch (fs) {
  // (re-)implement some things that are known busted or missing.

  // lchmod, broken prior to 0.6.2
  // back-port the fix here.

  console.log("process.version: ", process.version)

  if (constants.hasOwnProperty('O_SYMLINK') &&
      process.version.match(/^v0\.6\.[0-2]|^v0\.5\./)) {
    patchLchmod(fs)
  }

And this is the output:
process.version: undefined

node is working fine:
(base) marco@pc01:~/webMatters/electronMatters/ElectronVueTypeScriptScaffolding$ node -v
v14.5.0

(base) marco@pc01:~/webMatters/electronMatters/ElectronVueTypeScriptScaffolding$ node
Welcome to Node.js v14.5.0.
Type ".help" for more information.

> console.log(process.versions)
{
  node: '14.5.0',
  v8: '<IP_ADDRESS>-node.23',
  uv: '1.38.0',
  zlib: '1.2.11',
  brotli: '1.0.7',
  ares: '1.16.0',
  modules: '83',
  nghttp2: '1.41.0',
  napi: '6',
  llhttp: '2.0.4',
  openssl: '1.1.1g',
  cldr: '37.0',
  icu: '67.1',
  tz: '2020a',
  unicode: '13.0'
}

> console.log(process.version)
v14.5.0

May be this version "undefined" is due to the fact that I set, to keep the app as safe as possible, nodeIntegration: false in
webPreferences: {
      nodeIntegration: false,
      contextIsolation: true, // protects against prototype pollution
      preload: path.join(__dirname, "../dist_electron/preload.js"),
    },

?
But this nodeIntegration: false shouldn't affect the node functioning and in particular the node's process version
I searched in graceful-fs folder for all the occurences of process.version :
(base) marco@pc01:~/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/node_modules/graceful-fs$ grep
--recursive "process.version" *
graceful-fs.js:  if (process.version.substr(0, 4) === 'v0.8') {
polyfills.js:      process.version.match(/^v0\.6\.[0-2]|^v0\.5\./)) {

Why process.version is "undefined" in node_modules/graceful-fs/polyfills.js ?
And why process.version is defined, thus not undefined in node_modules/graceful-fs/graceful-fs.js ?
If I put console.log in:
  if (process.version.substr(0, 4) === 'v0.8') {
     console.log("graceful-fs-process.version: ", process.version)
    var legStreams = legacy(fs)
    ReadStream = legStreams.ReadStream
    WriteStream = legStreams.WriteStream
  }

in node_modules/graceful-fs/graceful-fs.js
I do not get any output...
Putting console.log(process) in node_modules/graceful-js/polyfill.js :
function patch (fs) {
  // (re-)implement some things that are known busted or missing.

  // lchmod, broken prior to 0.6.2
  // back-port the fix here.

   console.log("process: ", process)

  console.log("process.version: ", process.version)

I get :
 INFO  Launching Electron...
process:  process {
  version: 'v12.16.3',
  versions: {
    node: '12.16.3',
    v8: '<IP_ADDRESS>-electron.0',
    uv: '1.34.2',
    zlib: '1.2.11',
    brotli: '1.0.7',
    ares: '1.16.0',
    modules: '82',
    nghttp2: '1.41.0',
    napi: '5',
    llhttp: '2.0.4',
    http_parser: '2.9.3',
    openssl: '1.1.0',
    icu: '67.1',
    unicode: '13.0',
    electron: '10.0.0',
    chrome: '85.0.4183.84'
  },
  arch: 'x64',
  platform: 'linux',
  release: {
    name: 'node',
    lts: 'Erbium',
    sourceUrl: 'https://nodejs.org/download/release/v12.16.3/node-v12.16.3.tar.gz',
    headersUrl: 'https://nodejs.org/download/release/v12.16.3/node-v12.16.3-headers.tar.gz'
  },
  _rawDebug: [Function: _rawDebug],

plenty of other output at the end of which :
process.version:  v12.16.3
(node:9831) ExtensionLoadWarning: Warnings loading extension at /home/marco/.config/base/extensions
/nhdogjmejiglipccpnnnanhbledajbpd: Unrecognized manifest key 'browser_action'. Unrecognized manifest key 'update_url'.
Permission 'contextMenus' is unknown or URL pattern is malformed. Cannot load extension with file or directory name
_metadata. Filenames starting with "_" are reserved for use by the system.
No type errors found
Version: typescript 3.9.7
Time: 4215ms

So, it seems that process.version used by node_modules/graceful-fs/polyfill.js is: v12.16.3
Why the print of console.log("process.version: ", process.version) gives "undefined" and not v12.16.3 ?
I've put nodeIntegration: true in src/background.ts :
    webPreferences: {
      // Use pluginOptions.nodeIntegration, leave this alone
      // See nklayman.github.io/vue-cli-plugin-electron-builder/guide/security.html#node-integration for more info
      //nodeIntegration: (process.env
      //    .ELECTRON_NODE_INTEGRATION as unknown) as boolean,
      nodeIntegration: true,
      //nodeIntegration: false,
      //contextIsolation: true, // protects against prototype pollution
      //preload: path.join(__dirname, "../dist_electron/preload.js"),
    },

but still get the same error: "Uncaught TypeError: Cannot read property 'match' of undefined"

Anyway, as far as I understand, to keep electron.js app safer nodeIntegration: false in conjunction with the use of preload file should be preferred: https://www.electronjs.org/docs/tutorial/security#electron-security-warnings
I do not understand why process.version is "undefined" in node_modules/graceful-fs/polyfill.js but when printed outside of polyfill.js is v12.16.3
You can find the GitHub repo here: https://github.com/raphael10-collab/ElectronVueTypeScriptScaffolding
Looking forward to your kind help

Here is a workaround I came across:
const { remote } = window.require('electron');
const fs = remote.require('fs-extra');

Hi @truefusion
thanks for answering.
I do not understand what I should do.
In src/services/electron-services/database/index.ts I tried to substitute
//import fs from 'fs-extra'

with
import pathExistsSync from 'fs-extra/pathExistsSync'
import mkdirpSync from 'fs-extra/mkdirpSync'

if (!isRenderer) {
  //if (!fs.pathExistsSync(STORE_PATH)) {
    //fs.mkdirpSync(STORE_PATH)
  if (!pathExistsSync(STORE_PATH)) {
    mkdirpSync(STORE_PATH)
  }
}

but got "Cannot find module 'fs-extra/pathExistsSync' or its corresponding type declarations"
and "Cannot find module 'fs-extra/mkdirpSync' or its corresponding type declarations."

I couldn't provide you with relevant code because I didn't know what exactly you were trying to do. But if you were trying to use the fs-extra module in an electron environment, then the code I provided should be enough. The code you responded with did not make use of the code I provided. I will assume you know how to program in JavaScript and about the many different ways to import or require modules, so I won't go into details for that. But if you are trying to use fs-extra in an electron environment, then you must use the code I provided in exactly the way I provided it.
In other words, this code
import fs from 'fs-extra'

Becomes this code
const { remote } = window.require('electron');
const fs = remote.require('fs-extra');

Then you can start using fs anywhere. For example,
const { remote } = window.require('electron');
const fs = remote.require('fs-extra');

if (!isRenderer) {
  if (!fs.pathExistsSync(STORE_PATH)) {
    fs.mkdirpSync(STORE_PATH)
  }
}

I don't know where isRenderer came from, but I don't need to know.

@truefusion where does window come from?

window is a pre-defined, global variable. Therefore it comes from the environment, in this case it would be from electron's environment. If you were running your script in a node environment, I would not expect window to be defined.

@truefusion
I tried to put
//import fs from 'fs-extra'

const { BrowserWindow } = require('electron').remote
let window = new BrowserWindow()
const { remote } = window.require('electron');
const fs = remote.require('fs-extra');
import LodashID from 'lodash-id'
//import { app, remote } from 'electron'
import { app } from 'electron'

But I got this error:
A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: Cannot destructure property 'BrowserWindow' of '__webpack_require__(...).remote' as it is undefined.
    at eval (webpack:///./src/services/electron-services/database/index.ts?:16:9)
    at Module../src/services/electron-services/database/index.ts (/home/marco/webMatters/electronMatters/GGC-Electron
/dist_electron/index.js:1984:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/GGC-Electron/dist_electron/index.js:20:30)
    at eval (webpack:///./src/background.ts?:7:100)
    at Module../src/background.ts (/home/marco/webMatters/electronMatters/GGC-Electron/dist_electron/index.js:1960:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/GGC-Electron/dist_electron/index.js:20:30)
    at eval (webpack:///multi_./src/background.ts?:1:18)
    at Object.0 (/home/marco/webMatters/electronMatters/GGC-Electron/dist_electron/index.js:2007:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/GGC-Electron/dist_electron/index.js:20:30)
    at /home/marco/webMatters/electronMatters/GGC-Electron/dist_electron/index.js:84:18

actually window, aka win, is already defined in src/background.ts :
import { app, protocol, BrowserWindow, ipcMain, shell, Menu } from 'electron'

async function createWindow() {
  win = new BrowserWindow({

But window has to be defined in src/services/electron-services/database/index.ts as well in order to be able to do
const { remote } = window.require('electron')

The moment you redefine window is when you break its original value. I'm not sure what your programming background is, but there is a bigger underlying issue here. It is best if you take this time to come to a deeper understanding of JavaScript and its environments before continuing to any further on your project.
Here may be a good place to start: https://developer.mozilla.org/en-US/docs/Web/JavaScript

@truefusion thank for your kind suggestion.
I would be grateful if you would have a look at the file where you suggest to modify how to import fs-extra : https://github.com/raphael10-collab/ElectronVueTypeScriptScaffolding/blob/master/src/services/electron-services/database/index.ts and tell me how to use window, which cannot be redefined, otherwise its original value will be broken, there

@truefusion thank you for your pull request
Doing :
const { app, remote } = window.require('electron')
import Lowdb from 'lowdb'
import FileSync from 'lowdb/adapters/FileSync'
import path from 'path'
const fs = remote.require('fs-extra')

I get : "ReferenceError: window is not defined".
So I have to understand how to define window in src/services/electron-services/database/index.ts

How are you compiling your code? And how are you running your app?

This is the complete output:
(base) marco@pc01:~/webMatters/electronMatters/ElectronVueTypeScriptScaffolding$ yarn electron:serve
yarn run v1.22.5
warning ../package.json: No license field
$ vue-cli-service electron:serve
 INFO  Starting development server...
Starting type checking service...
Using 1 worker with 2048MB memory limit
98% after emitting CopyPlugin

 DONE  Compiled successfully in 1725ms
10:26:28 PM

Type checking in progress...

  App running at:
  - Local:   http://localhost:8080
  - Network: http://<IP_ADDRESS>:8080

  Note that the development build is not optimized.
  To create a production build, run yarn build.

⠏  Bundling main process...

 DONE  Compiled successfully in 855ms
10:26:29 PM

  File                      Size                                                                       Gzipped

  dist_electron/index.js    1366.33 KiB                                                                274.09 KiB

 Images and other types of assets omitted.

  DONE  Compiled successfully in 11ms
 10:26:29 PM

  File                        Size                                                                      Gzipped

  dist_electron/preload.js    76.96 KiB                                                                 5.19 KiB

  Images and other types of assets omitted.

 INFO  Launching Electron...
App threw an error during load
ReferenceError: window is not defined
    at eval (webpack:///./src/services/electron-services/database/index.ts?:8:25)
    at Module../src/services/electron-services/database/index.ts (/home/marco/webMatters/electronMatters
/ElectronVueTypeScriptScaffolding/dist_electron/index.js:1894:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:20:30)
    at eval (webpack:///./src/background.ts?:7:100)
    at Module../src/background.ts (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:1870:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:20:30)
    at eval (webpack:///multi_./src/background.ts?:1:18)
    at Object.0 (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron/index.js:1917:1)
at __webpack_require__ (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:20:30)
    at /home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron/index.js:84:18
A JavaScript error occurred in the main process
Uncaught Exception:
ReferenceError: window is not defined
    at eval (webpack:///./src/services/electron-services/database/index.ts?:8:25)
    at Module../src/services/electron-services/database/index.ts (/home/marco/webMatters/electronMatters
/ElectronVueTypeScriptScaffolding/dist_electron/index.js:1894:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:20:30)
    at eval (webpack:///./src/background.ts?:7:100)
    at Module../src/background.ts (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:1870:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:20:30)
    at eval (webpack:///multi_./src/background.ts?:1:18)
    at Object.0 (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron/index.js:1917:1)
    at __webpack_require__ (/home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron
/index.js:20:30)
    at /home/marco/webMatters/electronMatters/ElectronVueTypeScriptScaffolding/dist_electron/index.js:84:18
No type errors found
Version: typescript 3.9.7
Time: 3989ms

Your dist_electron/preload.js script is not designed to properly launch electron.

@truefusion
This is the preload.js I'm using, based on the suggestions here: https://github.com/electron/electron/issues/9920#issuecomment-575839738
const {
    contextBridge,
    ipcRenderer
} = require("electron");

// Expose protected methods that allow the renderer process to use
// the ipcRenderer without exposing the entire object
contextBridge.exposeInMainWorld(
    "api", {
        send: (channel, data) => {
            // whitelist channels
            let validChannels = ["toMain"];
            if (validChannels.includes(channel)) {
                ipcRenderer.send(channel, data);
            }
        },
        receive: (channel, func) => {
            let validChannels = ["fromMain"];
            if (validChannels.includes(channel)) {
                // Deliberately strip event as it includes `sender`
                ipcRenderer.on(channel, (event, ...args) => func(...args));
            }
        }
    }
);

How should I modify preload.js in order to properly launch electron?

This is as far as I will help you on the matter. https://www.electronjs.org/docs/tutorial/quick-start
For anything else, you'll have to become more acquainted with web technologies.

Thank you very much for tour kind valuable contribution
Il gio 17 set 2020, 21:11 truefusion<EMAIL_ADDRESS>ha scritto:

This is as far as I will help you on the matter.
https://www.electronjs.org/docs/tutorial/quick-start
For anything else, you'll have to become more acquainted with web
technologies.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/isaacs/node-graceful-fs/issues/196#issuecomment-694441549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQYOI2YP3K2UI2KVKIDM5RTSGJNPBANCNFSM4Q2YKXCA
.

I have the same problem:
Uncaught TypeError: can't access property "match", e.version is undefined
c polyfills.js:30
v graceful-fs.js:104
0da7 graceful-fs.js:96
0da7 chunk-vendors.331b15a4.js:1
Webpack 14
polyfills.js:30:16
c polyfills.js:30
v graceful-fs.js:104
0da7 graceful-fs.js:96
0da7 chunk-vendors.331b15a4.js:1
Webpack 14
I've tried everything under the sun, and don't think it's my npm installation.
Let me know if you would like more info.  Meanwhile I'm going to try commenting out:
if (constants.hasOwnProperty('O_SYMLINK') &&
process.version.match(/^v0.6.[0-2]|^v0.5./)) {
patchLchmod(fs)
}
which seems to be the problem area so far.

i faced the same issue and fixed it by downgrading to graceful-fs "4.2.4" version; force it using 'npm install<EMAIL_ADDRESS>the recent versions breaking for me

You need to make sure that dart-sass is not loaded, because this sass cannot run in the browser yet.
I had to remove "implementation: require('sass')," in my vue.config.js and then it worked.

webpack config, try this, may works
plugins: [
  // https://webpack.js.org/plugins/environment-plugin/
  new webpack.DefinePlugin({
    'process.version': process.version,
  }),
],

Running into this as well with react on the latest version. Workarounds aren't really an option for my project.

This problem is most likely caused by Webpack5. Webpack5 no longer automatically populates the nodejs core module.
https://webpack.js.org/configuration/resolve/#resolvefallback


Mods do not apply, bad lag spikes, and FPS seems to get worse overtime [BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Recently (issue seems to have occurred today, but I haven't played roblox in a while, so who knows), Bloxstrap seems to have been causing a ton of issues for Roblox. The title explains the issue.
To not waste your time,

No, another Roblox is not running in the background
Yes, Bloxstrap is running
Yes, my FPS is actually being capped at 60 (Supposed to be 120)
I checked everything on https://github.com/pizzaboxer/bloxstrap/wiki/Roblox-is-still-capped-to-60-FPS-after-raising-the-limiter
The only fix I've seen is playing Roblox without Bloxstrap

Below are the files asked to be attached:
Files:
Settings.json
State.json
ClientAppSettings.json
Help would be appreciated!

It appears that the Bloxstrap menu says that Roblox is running in the background, when task manager says completely otherwise...

It appears that the Bloxstrap menu says that Roblox is running in the background, when task manager says completely otherwise...

If you were opening the menu right after closing Roblox, then Bloxstrap would've been picking up on Roblox before it had actually exited.
Only thing I can suggest for you to do is to try disabling the 'Disable Fullscreen Optimizations' option in the Mods tab.
It would also help if you clarified if this happens only when using Bloxstrap: https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap
Regarding your FPS not going past 60, are you using an Nvidia GPU?

Sorry for the late response - Randomly fixed itself. Thanks for the help though!


Zamp Solar RJ12

Hi. Sorry in advance if this is not the best way to ask for help opening an issue here.
I arrive here coming from this post.
My RV has a Zamp Solar ZS-30A that uses a RJ11/RJ12 port for communication with a Remote Digital Display ZS-RT1 that I'd like to gather and store information from it and further integrate somehow in my home automation system.
I'd like to ask you solar controller in general uses the same communication protocol standard where the messages and codes are standardized or the worst case scenario that I'll to guess the information based on log from the serial communication.
I appreciate any help that can point me in a direction.
Thanks.

The Zamp Solar ZS-30A does not use the same protocol as Renogy devices use, so it is not currently supported by SolarThing.
After looking at it a bit, my guess is that Zamp has its own unique protocol, or uses something similar to the MT-5 protocol (not MT50, that is different). Your best bet to find existing software to monitor this device is to figure out if the Zamp Solar ZS-30A is a rebrand of another charge controller that has existing open source software out there to monitor it. A good chunk of the time when someone brings up some obscure charge controller, it's usually a rebranding of a better known charge controller with existing software to monitor it (that might not be the case here, but it could be).
If you end up developing software yourself for this charge controller, I wish you luck. The first part is to figure out what the data lines are for the RJ12 port on your controller. Once you know RX, TX, and GND on your port, you can connect those to your serial adapter. Now, I don't know if you need a RS485 adapter or a RS232 adapter for your controller, so you should figure that out too. At this point, you should be able to open up the serial port using your language of choice and read and write to it. Very rarely, the port's TX (that you connect to your own RX), will just start spitting out data for you to do stuff with. However, most of the time, newer charge controllers will use the modbus protocol which allows you to request specific information from the charge controller. If that is the case, you will need both RX and TX working.
Many charge controllers that are rebranded use the exact same protocol, but for the most part there is no common protocol for solar charge controllers to use. Many charge controllers will use the Modbus protocol, but almost all of the time the registers of a given charge controller will vary from one to another, making it impossible to use the same code to gather data from charge controllers of different brands.
I hope this information helps you out, it looks like you have a more obscure charge controller that isn't very well known. Feel free to pick my brain more.


The error message says this document should answer why I am getting the error.  It does not.

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

ID: bf2d3f7f-74d8-6a2f-e662-7d437d0c1043
Version Independent ID: 0638247c-2b9e-68e4-e54d-66f1918a9fa0
Content: Azure Data Factory - Frequently asked questions - Azure Data Factory
Content Source: articles/data-factory/v1/data-factory-faq.yml
Service: data-factory
Sub-service: v1
GitHub Login: @dcstwh
Microsoft Alias: weetok

@rihoughton
Thanks for your feedback! We will investigate and update as appropriate.

Hi @rihoughton
Could you please go through this below link for your reference.
https://learn.microsoft.com/en-us/azure/data-factory/self-hosted-integration-runtime-troubleshoot-guide?tabs=data-factory#:~:text=Error message%3A Self,the following screenshot%3A
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@rihoughton
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Typo in documentation for ASN1_STRING_set

https://www.openssl.org/docs/man1.1.0/crypto/ASN1_STRING_set.html

In general it cannot be assumed that the data returned by ASN1_STRING_data() is null terminated or does not contain embedded nulls. The actual format of the data will depend on the actual string type itself: _for example for and IA5String_ the data will be ASCII, for a BMPString two bytes per character in big endian format, UTF8String will be in UTF8 format.

I've highlighted the section with the typo above.

Considering this is fixed, can't we close this?

Sure. Thanks for reporting it!


Sell Google Drive LH3 METHOD 360P 480P 720P 1080P

Simple and reliable script for generating HTML5 video streaming links from Google Drive files.
it's not a proxy script, provide links direct to Google's Video CDN
Easy Installation, You just need PHP hosting and Google Cloud PHP App account thats all, now you are ready to fly.
It's work with all public google drive videos on free and gsuite accounts.
MORE INFO AND TEST ON: https://google.driveplayer.stream/

FRAUD!!!!!!!!!!

You dont have money to buy it and you dont know how this method is working its easy to say FRAUD LOL!!

When you have proof of course it's easy to say FRAUD! https://www.youtube.com/watch?v=iSNL3mZu7uE

ArdiArtani get some money and learn how get links on google drive


Cartesian sampling operator

closes #19

Regarding ypur question of caching the results:
We can use the tensor._version to check if the tensor has been modified.
a) invalidate the cache in the setattr
b)  in the property, check if the cache exists and if a _cache_version=[int,int,int] is the same as the versions
in kx,ky,kz's ._version. Otherwise, invalidate chache. Calulate properties. And cache.
I think this could make for a nicer interface

I added a first (incomplete) implementation of the cache idea where the function _type_of_traj() is only called if something has changed in kz, ky or kx. Otherwise the cached result is returned. @fzimmermann89 is this roughly what you had in mind?
Currently this only works for in-place changes of kx,ky and kz (see test_traj_type_update()). setters would have to be defined for kx, ky and kz to update the ._version for this too. Might also need a new variable to not miss with the standard way tensor._version works.
Question is, is it worth it? _type_of_traj() is really quick and not sure if the overhead of caching is really justified or if we should simply call this function whenever the type of the trajectory is queried. Opinions?

Yeah, I came to a different conclusion: Maybe you were right and we should make KTrajecteroy frozen (and throw an exception if the _version changes.
Otherwise yes, we would need a setter to invalidate the cache also on replacement of one of the tensors..

I woul prefer to change the type logic to a flag that checks different properties.
For now, it willjust be ongrid and singlevalue.
Both can be set or not set in the flag.
This feels like a more flexible way to do this and this pattern can more easy be applied to different properties as well.
so, maybe take a look at some point at #150 , which is based on your branch just before te last commit

@schuenke or @koflera
Do you mind having a look, after starting the review, I made some extensive refactor changes, also to the FourierOperator, which I now rebased onto this PR.
One of the goals was to enable multiple 'other' dims in the Fourier Operator and some general streamlining of code.
So maybe we could use an independent review / sanity check..

Do we want to rebase it already to operatorsugar? or first merge #128 which makes all operators return tuples of tensors...

I would suggest to first merge #128

@ckolbPTB:
What do you think about this?
@schuenke
I would like to get this merged soonish.... As it also fixes some other issues with the Fourier Operator


update references to Android support

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/add-in-commands-for-outlook.md
:white_check_mark:Succeeded

docs/add-ins/contextual-outlook-add-ins.md
:white_check_mark:Succeeded

docs/add-ins/outlook-addin-design.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Post release automated changes for identity releases

Post release automated changes for azure-identity

API change check
API changes are not detected in this pull request.

I don't believe this is actually necessary since the hotfix went out, and we can abandon this hotfix branch entirely so i am closing... but, I am not 100% sure so you know, if you see something say something 😄
AFAIK if we were to cut a new hotfix it would be off of the latest released tag and not this branch


New API version for Microsoft.Resources stable/2022-09-01

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

azp run

/azp run

Hi @leni-msft , pinging again. I think I made the appropriate edits but the checks are still failing. Could you help me figure out what I'm missing?

@meghanagupta95 please follow the guidance in https://github.com/Azure/azure-rest-api-specs/pull/20494#issuecomment-1232539462 to fix the CI errors

@meghanagupta95 - Note the BreakingChangeReviewRequired label must be addressed before ARM review. See instructions in the PR comments.

@mentat9 @leni-msft  We need to add a 202 response for the Tags PUT/PATCH/DELETE APIs (Tags_CreateOrUpdateAtScope, Tags_UpdateAtScope, Tags_DeleteAtScope) We had not accounted for this earlier since we didn't expect RPs to return a 202 for modifying lightweight properties on resources. I believe this change was approved by the breaking change committee as well.
The pipelines seem to be failing due to some changes that were already present in the previous API version, since I have copied the previous API version file and only made changes to the Tags_CreateOrUpdateAtScope, Tags_UpdateAtScope, Tags_DeleteAtScope APIs. Perhaps there were new validations added to the pipeline?

I believe this change was approved by the breaking change committee as well.

@meghanagupta95 - Normally, the breaking change process should add an approval label (Approved-BreakingChanges) to the PR upon approval (and remove the BreakingChangeReviewRequire label). Can you confirm with them?
Note: ARM review oncall this week is @rkmanda. Please remove the ARMChangesRequested label to queue your PR back to the (current) ARM reviewer.

Adding in current ARM reviewer @rkmanda
We were able to get approval for the breaking changes in this PR. Please approve the PR when possible.

@meghanagupta95 - Your PR is not ready for ARM review.
Please create a new PR following this process (and check the box when you submit):
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
Ref: https://armwiki.azurewebsites.net/rp_onboarding/process/api_review.html#introduction.
Also, please study the materials mentioned in the submission form and attest to that by checking the box:
[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
Respond back by removing the ARMChangesRequested label.

New PR as requested at https://github.com/Azure/azure-rest-api-specs/pull/21203

New PR as requested at #21203

Can you close this PR if this is no longer valid? And get breaking change approved on the new PR as well. Thanks

New PR as requested at #21203

Can you close this PR if this is no longer valid? And get breaking change approved on the new PR as well. Thanks

@zizw123 do we need to get the breaking changes approved for the new PR even if both PRs have the same changes?


[BUG] Org agenda kills existing org buffers (sometimes)

Description
Summoning org-agenda kills already open org buffers (sometimes).
This behavior is observed using existing keybindings such as SPC o a t as well as with a custom org-agenda command. I've found that this mostly happens when the file being opened is part of the files that agenda looks through. I've never been able to reproduce this when summoning org-agenda from a non-agenda file.
Steps to reproduce

Open an org file (that contains TODO tasks that will be read by org-agenda)
Summon org-agenda, e.g. by pressing SPC o a t

System information

- OS: darwin (x86_64-apple-darwin18.6.0)
- Shell: /bin/bash
- Emacs: 27.0.50 (Jul 26, 2019)
- Doom: 2.0.9 (HEAD -> develop, origin/develop f754d4ff9 2019-07-23 18:23:17 +0200)
- Graphic display: t (daemon: nil)
- System features: RSVG IMAGEMAGICK GLIB NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS JSON PDUMPER LCMS2 GMP
- Details:
  ```elisp
  env bootstrapper: exec-path-from-shell
  elc count: 0
  uname -a:  Darwin 18.7.0 Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64 x86_64
  modules:   (:completion company (ivy +childframe) :ui deft doom doom-dashboard hl-todo modeline nav-flash ophints (popup +all +defaults) treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor evil file-templates fold multiple-cursors rotate-text snippets :emacs dired electric vc :term eshell term :tools eval flycheck (lookup +docsets) lsp macos magit :lang data emacs-lisp latex markdown (org +dragndrop +ipython +pandoc +present) perl (python +lsp +pyenv) (sh +lsp +fish) :config literate (default +bindings +smartparens +snippets +evil-commands) sid)
  packages:  n/a
  exec-path: (~/.pyenv/shims ~/.pyenv/shims/ ~/bin/ ~/Library/Python/3.7/bin/ /usr/local/opt/python/libexec/bin/ /usr/local/bin/ /usr/bin/ /bin/ /usr/sbin/ /sbin/ ~/.pyenv/shims/ ~/bin/ ~/Library/Python/3.7/bin/ /usr/local/opt/python/libexec/bin/ ~/Documents/buildAnalysis/bin/ ~/Documents/buildAnalysis/bin/ /usr/local/Cellar/emacs-plus/HEAD-e3575ee/libexec/emacs/27.0.50/x86_64-apple-darwin18.6.0/)
  ```

Observation: This seems to happen only when I invoke org-agenda from within a workspace containing the buffer that is about to be killed.

This is the cause. Its purpose is to clean up buffers that org-agenda opens. This should leave buffers that were already opened alone though. I'll look into it.

As of de223e7 this issue should be resolved. Let me know if that isn't the case and I will reopen it. Thanks for bringing it to my attention!


Feature request: make it installable with mint

Afaik, all it takes for this is to add an executable product to the Package.swift file, right?

If this is something you'd like to see, then feel free to open a PR with that change 👍