db.close() crashing Electron after "electron": "26.0.0",

Error message before crash is

[20860:0821/201632.615257:ERROR:child_thread_impl.cc(235)] Invalid PlatformChannel receive right

Code is
      let database: Sqlite3Database.Database;
      try {
        database = new Sqlite3Database(':memory:', { verbose: logger.debug, nativeBinding: SQLITE_BINARY_PATH });
      } catch (error) {
        logger.error(`error when loading sqlite3 for workspace ${workspaceID}, skip because of error to prevent crash: ${(error as Error).message}`);
        return;
      }

It was working in 8.4.0 + "electron": "25.2.0",
Not working with 8.5.1 + "electron": "26.0.0", or 8.4.0 + + "electron": "26.0.0",
So it is electron's falut.

(fwiw, I'm stuck on electron 21.4.4 due to a litany of show-stopping bugs that their team won't fix. Every new release has new ways to crash. Last time I checked, vscode was also stuck on an ancient version)

Thanks for reporting, @linonetwo . @neoxpert contributed more context in #1053.

Using @neoxpert 's repo, using the debug build works fine:
npm install
cd node_modules/better-sqlite3
npx node-gyp rebuild --debug --build-from-source --runtime=electron --target=26.1.0 --dist-url=https://electronjs.org/headers
cd ../..
npm run start

So it looks like the optimized code doesn't play nicely with the new version of Electron.

But wasn't the prebuilt binary generated in Github action in the same cli command? Can you rerun action to publish a new one?
So is this a bug on Electron or here, do I need to close the issue there?

I've kicked off a rebuild for the latest version, but I suspect the same binaries will be emitted. I'll look into it a bit more tomorrow. @JoshuaWise  if you've got any suggestions, that'd be great.

Harumph--rebuilding resulted in the same behavior. Until this is properly resolved, I'd run https://github.com/WiseLibs/better-sqlite3/issues/1044#issuecomment-1693735596 in your postinstall.

I got this different error: [28380:0828/232451.103:ERROR:crashpad_client_win.cc(844)] not connected and it looks like the workaround solved it.

Just a small warning, one issue I discovered was that the machine you compile Better-SQLITE on's GLIBC version matters GREATLY.   If you use the above command line on say a Ubuntu 22.04 machine to rebuild it, your GLIB is 2.35 which means your app will crash on a fairly large percentage of all Linux machines, since a large number of them are running a version of GLIBC that is before 2.35.
I actually have a special build docker container I use to build better-sqlite (everytime I upgrade my electron) using GLIBC 2.28 because I ran into way too many people still having a GLIB 2.28 - 2.30 machine and the prebuilt version is GLIBC 2.31.    You don't need to go any farther back than 2.28, because Node 16 (iirc) requires GLIB 2.28 and higher to run, meaning most versions of Electron requires GLIBC 2.28 and higher to run.

Looking through the build logs I just found those lines for the Windows and Ubuntu builds:
Windows line 855 + 856
prebuild info build Preparing to prebuild<EMAIL_ADDRESS>for electron 26.0.0 on win32-x64 using node-gyp prebuild info build prebuilds\better-sqlite3-v8.6.0-electron-v116-win32-x64.tar.gz exists, skipping build
** Ubuntu line 942 + 943**
prebuild info build Preparing to prebuild<EMAIL_ADDRESS>for electron 26.0.0 on linux-x64 using node-gyp prebuild info build prebuilds/better-sqlite3-v8.6.0-electron-v116-linux-x64.tar.gz exists, skipping build
May it be that Electron 25 and 26 share the same NODE_MODULE_VERSION number, or at least the same number is resolved in the build process? Electron 25 and 26 both load the exact same prebuilt binary, thus leading to the crash on Electron 26 being somehow "expected" ...

May it be that Electron 25 and 26 share the same NODE_MODULE_VERSION number, or at least the same number is resolved in the build process? Electron 25 and 26 both load the exact same prebuilt binary, thus leading to the crash on Electron 26 being somehow "expected" ...

They do https://github.com/electron/node-abi/blob/f3efb50137fada3613298cf0b6055e9c4fe8ba6a/abi_registry.json#L255-L268
We had this exact same thing happen with Electron 14. Back then I was making the hypothesis that relying on the ABI version alone is not enough as a criteria, see https://github.com/WiseLibs/better-sqlite3/issues/694#issuecomment-912506229
If this is the case, then the whole prebuild system is broken for Electron and this is an issue greater than better-sqlite3 itself. It might just be that native modules are rarely used and maybe other native modules don't trigger the crash because of the APIs they use.
I'm not sure if back then we actually solved this or if we just sat it out until Electron 16 was released.

I opened https://github.com/prebuild/prebuild/issues/309 to have this discussion in the right place.

Same issue here,
Using any package (Enmap, better-sqlite3-multiple-ciphers, ...) that uses better-sqlite3 will run into a SIGSEGV when only creating the database. This occurs only when using Electron.
I'm on Ubuntu 23.04, Node v18.17, Electron 26.
But this seems to occur with any OS, Node >= 14, Electron >= 11 (of what I've found on other repo issues).

I did the steps https://github.com/WiseLibs/better-sqlite3/issues/1044#issuecomment-1693735596 and it throws this error on the build process. I assume ignore it?

To ensure your native dependencies are always matched electron version, simply add script `"postinstall": "electron-builder install-app-deps" to your `package.json`
  • writing effective config  file=dist/builder-effective-config.yaml
  • rebuilding native dependencies<EMAIL_ADDRESS>platform=darwin arch=x64
  • install prebuilt binary  name=better-sqlite3 version=8.6.0 platform=darwin arch=x64 napi=
  • build native dependency from sources  name=better-sqlite3
                                          version=8.6.0
                                          platform=darwin
                                          arch=x64
                                          napi=
                                          reason=prebuild-install failed with error (run with env DEBUG=electron-builder to get more information)
                                          error=/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/node_modules/node-abi/index.js:39
      throw new Error('Could not detect abi for version ' + target + ' and runtime ' + runtime + '.  Updating "node-abi" might help solve this issue if it is a new release of ' + runtime)
      ^

    Error: Could not detect abi for version 26.1.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
        at getAbi (/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/node_modules/node-abi/index.js:39:9)
        at module.exports (/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/rc.js:54:57)
        at Object.<anonymous> (/Users/coltonshaw/Desktop/scripts/pcomvp-desktop/node_modules/prebuild-install/bin.js:8:27)
        at Module._compile (node:internal/modules/cjs/loader:1233:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1287:10)
        at Module.load (node:internal/modules/cjs/loader:1091:32)
        at Module._load (node:internal/modules/cjs/loader:938:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47

    Node.js v20.5.1

  • rebuilding native dependency  name=better-sqlite3 version=8.6.0
  • packaging       platform=darwin arch=x64 electron=26.1.0 appOutDir=dist/mac

No, you can't ignore that. Something in your build environment / project seems to be incorrect. Looks like the node-abi module resolved is not up to date.

No, you can't ignore that. Something in your build environment / project seems to be incorrect. Looks like the node-abi module resolved is not up to date.

That's what I thought too, but it's just the packaged version of rebuild that has node abi 3.3.0.

Looks like migrating to N-API (#271) could resolve these issue in the future, as pointed out by the prebuild maintainer

If it's relevant for anyone, the above commands I made an arch adjustment and it seems to work. I have to build mainly for x64 and was yelling at me about arm.
npx node-gyp rebuild --debug --build-from-source --runtime=electron --target=26.1.0 --dist-url=https://electronjs.org/headers --arch=x64

Thanks, this worked for me. However, I'm still having issues with running it inside a Utility Process. The process just crashes right away with no log output that I can see. The main process which launches the utility process works fine.

If it's relevant for anyone, the above commands I made an arch adjustment and it seems to work. I have to build mainly for x64 and was yelling at me about arm.
npx node-gyp rebuild --debug --build-from-source --runtime=electron --target=26.1.0 --dist-url=https://electronjs.org/headers --arch=x64

Thanks, this worked for me. However, I'm still having issues with running it inside a Utility Process. The process just crashes right away with no log output that I can see. The main process which launches the utility process works fine.

Electron 27.0.0 seems to have resolved this issue for me.


[WIP] feat: add cdn fallback

Codecov Report

Merging #27 into master will decrease coverage by 33.43%.
The diff coverage is 58.82%.

@@             Coverage Diff             @@
##           master      #27       +/-   ##
===========================================
- Coverage   98.55%   65.11%   -33.44%
===========================================
  Files           2        2
  Lines          69       86       +17
===========================================
- Hits           68       56       -12
- Misses          1       30       +29

Impacted Files
Coverage Δ

src/index.js
64.63% <58.82%> (-33.83%)
:arrow_down:

src/get-resolver.js
75% <0%> (-25%)
:arrow_down:

Continue to review full report at Codecov.

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


bug: .ion-hide-md-down has wrong max-width value

Bug Report
Ionic version:
[x] 4.4.0
Current behavior:
.ion-hide-md-down has wrong max-width value:
@media (max-width: 991px) .ion-hide-md-down {     display: none !important; }
Expected behavior:
Documentation says:
Applies the modifier to the element when min-width: 768px (up) or max-width: 768px (down).
Steps to reproduce:
Add css class ion-hide-md-down to an element.
Ionic info:

Ionic:

   ionic (Ionic CLI)             : 4.12.0 (C:\Users\user\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework               : @ionic/angular 4.4.0
   @angular-devkit/build-angular : 0.11.4
   @angular-devkit/schematics    : 7.2.3
   @angular/cli                  : 7.2.3
   @ionic/angular-toolkit        : 1.2.2

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : none
   Cordova Plugins       : no whitelisted plugins (0 plugins total)

System:

   NodeJS : v8.11.3 (C:\Program Files\nodejs\node.exe)
   npm    : 5.6.0
   OS     : Windows 10

Thanks for the issue! This is actually the correct code but it is a documentation issue. We have an issue to fix this here: https://github.com/ionic-team/ionic-docs/issues/616


Export redirects from Umbraco 7 sites

I've just pushed a new v1.0.0 release that targets Umbraco 7, and adds an endpoint for exporting redirects to either a CSV or JSON file.


Add PUP to TreeLB

This got inadvertently closed when I deleted the ronak/fix-hang-when-no-lb branch after I merged the PR for it. I've reopened this as #3340.


When deploy cosmos db trigger to azure, it can't be triggered if the deploymentType set to "msdeploy" or "ftp"

Plugin name and version
Maven Plugin for Azure Functions: 1.0.0-beta-5-SNAPSHOT
<azure.functions.maven.plugin.version>1.0.0-beta-5-SNAPSHOT</azure.functions.maven.plugin.version>
<azure.functions.java.library.version>1.0.0-beta-5</azure.functions.java.library.version>

Plugin configuration in your pom.xml
            <plugin>
                <groupId>com.microsoft.azure</groupId>
                <artifactId>azure-functions-maven-plugin</artifactId>
                <configuration>
                    <resourceGroup>${functionResourceGroup}</resourceGroup>
                    <appName>${functionAppName}</appName>
                    <region>${functionAppRegion}</region>
                    <deploymentType>ftp</deploymentType> //or msdeploy
                    <appSettings>
                        <property>
                            <name>FUNCTIONS_EXTENSION_VERSION</name>
                            <value>beta</value>
                        </property>
                        <property>
                            <name>connection</name>
                            <value>xxx</value>
                        </property>
                    </appSettings>
                </configuration>
                <executions>
                    <execution>
                        <id>package-functions</id>
                        <goals>
                            <goal>package</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

Expected behavior
The function can be triggered successfully on azure, not matter the deploymentType is "zip", "msdeploy" or "ftp"
Actual behavior
After add a document in collection,
if the deploymentType  is "zip", which is default, the function can be triggered,
if  the deploymentType is "msdeploy" or "ftp", the function has no response.
Steps to reproduce the problem
connection : connection
databaseName : db
collectionName : col
leaseCollectionName : leasecol
createLeaseCollectionIfNotExists : true

Create a Cosmos DB in azure and create a datebase and a collection according to above configuration
Generate a Cosmos DB Trigger according to above configuration
In the POM file, update azure.functions.maven.plugin.version to 1.0.0-beta-5-SNAPSHOT
In the POM file, update azure-functions-maven-plugin configuration  as above
Run mvn clean package under the root folder which contains the POM file
Run mvn azure-functions:deploy under the root folder
Add a document to collection col to see if the function get triggered.

@JanusWu Please verify your pom.xml is valid. There is no version for azure-functions-maven-plugin.

Added the azure-functions-maven-plugin version under Plugin name and version.

In 1.0.0-beta-5 we have supported the zip deploy as the default deployment type. This issue can be addressed by using the zip deploy.


Feat/(info section)

mobile responsive car motion path

PLEASE DO NOT MERGE 🥺🥺🥺🥺🥺🥺🥺🥺🥺
LET ME EXPLAIN IN THE MEETING.

please rebase before commit next time 😢


README: update usage instructions

This updates the example to the :jekyll_plugins and config.yml gems convention as suggested by Jekyll's docs.

:+1:


How to send string data in lorawan.py

protocol.send_cmd("mac tx uncnf 1 hgbhbjbhjbbjyjbv")
This gives invalid_param. How to pass string?
I also tried :
protocol.send_cmd("mac tx uncnf 1 %s" % "fsdfdssdvdvs")
but it also gives invalid_param.
Please help.
Also what is the max size of string(payload) I can send?

The data has to be converted to hex. Take a look at the command reference linked in the README.
<data> hexadecimal value.
The length of <data> bytes capable of being transmitted are dependent upon the set
data rate (please refer to the LoRaWAN™ Specification for further details


How much timei t needs to start?

Flashed an sensecap M1 one hour ago.  i cannot see the web console. (it conencts, but waits forever) how much time can i expect to wait?

You might need to try it again, we just pushed an update that fixed an issue.
Please try to push the latest release

Can you share a screenshot @rampa069 ?
And can you share the diagnostics JSON from the main page?

{"AN":"melted-brunette-pheasant","BA":"HELIUM-SENSECAP","BALENA_DEVICE_TYPE":["raspberrypi4-64"],"BN":"dawn-violet","BT":true,"BUTTON":27,"CELLULAR":false,"CONTAINS_FCC_IDS":[],"CONTAINS_IC_IDS":[],"CPU_ARCH":"aarch64","E0":"E4:5F:01:88:DA:1C","ECC":true,"ECCOB":true,"FCC_IDS":[],"FR":null,"FRIENDLY":"SenseCAP M1","FW":"2<IP_ADDRESS>","IC_IDS":[],"ID":"8c7c14c2403eaed93c3a94f8ba2b5d80","KEY_STORAGE_BUS":"/dev/i2c-1","LOR":true,"LTE":false,"MAC":"wlan0","OK":"111QzHdGo683HUEdbRQKJyya6nQacWn4StdZXiWk2qQwpPPhuyM","PF":true,"PK":"111QzHdGo683HUEdbRQKJyya6nQacWn4StdZXiWk2qQwpPPhuyM","RE":"EU868","RESET":17,"SPIBUS":"spidev0.0","STATUS":22,"SUPPORTED_MODELS":["SenseCAP M1"],"SWARM_KEY_URI":"ecc://i2c-1:96?slot=0","TYPE":"Full","VA":"COMP-SENSECAPM1","W0":"E4:5F:01:88:DA:1D","firmware_short_hash":"b53ac26","last_updated":"18:51 UTC 06 Feb 2023","serial_number":"10000000452eb348"}

@rampa069 could you add gh_shawaj user to the device/fleet on balena so I can take a look?

@rampa069 I can load the /hnt page fine.
Can you try again?

it worked....


Scrotland?

Removed r

Ups 😬 - Thanks for being vigilant and sorry for not discovering this PR before now. I already fixed it before realizing that you found it before me


Import name-strings from Museum of Comparative Zoology Db (Harvard)

@chicoreus

Note that the MCZ's database is known as MCZbase, with that capitalization.    Some relevant links: Source is under doi:10.5281/zenodo.891420 at github.com/MCZbase/MCZbase, schema at github.com/MCZbase/DDL  IPT resource with the data is at: http://digir.mcz.harvard.edu/ipt/resource?r=mczbase with doi:10.15468/p5rupv

Also note @heliumcell

I made a quick reconciliation of names to whole GN and got the following matches distribution:
Exact matches: 194188
Fuzzy matches: 24463
PartialExact matches: 42402
PartialFuzzy matches: 1723
NoMatch: 4645
https://uofi.box.com/shared/static/u64iow4ql0vo6td85edly7vswqvsnrrs.csv

Import worked
@Archilegt the search for 'Cryptus heathi' does return MCZ result now
http://resolver.globalnames.org/data_sources/186
There are no IDs, so I generated fake ones (I do the same for Arctos). There is no taxonomic relationship between the names, but I decided to leave classification, as it might help people to orient themseleves better with search results.
Let me know if you want to improve on something! I will close the ticket for now, but can reopen it if there are improvements needed.

The data did not percolate to https://index.globalnames.org. I will update its database when I inish updating old and importing new data sets.

Note that Arctos and MCZbase have internal surrogate numeric primary keys for Taxonomy table entries, but the externally exposed identifier for the taxon record is the URI https://mczbase.mcz.harvard.edu/name/  followed by the taxon name without the authorship, e.g. https://mczbase.mcz.harvard.edu/name/Cryptus heathi

We'll (@heliumcell and I) probably make a request to update the textual metadata description of the resource https://resolver.globalnames.org/data_sources/186 will review with MCZ collections operations and get back to you.

Spot checking the quick reconciliation report above, noted these three names reported as NoMatch which look like they do have matches.  Issues with the report?
Esox lucius Linnaeus, 1758
Isistius brasiliensis (Quoy and Gaimard, 1824)
Trachinotus falcatus (Linnaeus, 1758)

Good catch @chicoreus, I am importing a few more datasets, and will fix this for all of them in a few days.

I rebuilt the index, all should work now at resolver.globalnames.org


Use generics to implement multiple-type parameters.

Describe the feature or improvement you're requesting
Some OpenAI API paramters have two or more kind of types.
Use generics is a much better choice to implement them.
Additional context
No response

https://github.com/golang/go/issues/49085
For now, Go1.21 doesn't allow type parameters in methods, which means it will make the api very complexed if we use generics in our case.


[WIP] Use makeiso to generate ISO instead of geniso-isospec

luet-makeiso is a golang binary having almost all needed to build the ISO (that I'll be happy to move to our own org once things are settled).
The only host requirement is mksquashfs and xorriso - until then that's the only
requirement.
makeiso is way more extensible with the new Golang structure, and
easier to embed into pipelines, definetly much more than the current extension.
We now just use jq and yq to build the package list to build, and to generate the repository when running a build against the remote repositories, so derivatives don't need to install that anymore
Related to #27

Seems there are some issue with EFI and QEMU, will move to wip until figure out

After a retake on it, the issue seems to be when constructing the iso itself. For the moment I've replaced it with xorriso, but that still gives us much more improvement as we generate the required images without any mount in the go binary, with a consequent drop of permissions when we run inside docker (and we can even generate the iso as user, but we loose permission bits).  So now with EFI works.
I've also embedded the repositories in the iso spec file, so we don't need to specify 2 yamls anymore. Now it's sufficient to add
repositories:
- ..
- ..

in the iso spec to specify where the packages are coming from. I've adapted the Makefile accordingly to drop the generation of the repository file. Some logic is still there (with yq) when we run make iso which instead generates it from the remote repositories


:bug: Setup / as shared mount on alpine

Since this is not handled in the boot process, we do this in our devoted file to setup the rootfs configuration. It also adds an e2e test to verify that the mounts are correctly set
Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #440
Thanks @christianprim for the finding!

Considering the output of "qemu-acceptance-tests (alpine) ", the command "mount --make-rshared /sysroot" failed in the fs stage. I wonder why not use "mount --make-rshared /" when root-partition is under /. Since the command recursively changes the type of all mounts, this should do the trick. Could be the last command before starting k3s...

Considering the output of "qemu-acceptance-tests (alpine) ", the command "mount --make-rshared /sysroot" failed in the fs stage. I wonder why not use "mount --make-rshared /" when root-partition is under /. Since the command recursively changes the type of all mounts, this should do the trick. Could be the last command before starting k3s...

right, what I'm concerned here is try to break user-contract, and allow to have that set as soon as possible to avoid any possible race - and user assumption when it can be expected those to be set. I'd prefer to have those as early as possible (as soon as a fs is set up) but that seems to be tricky. I'll first try to get a baseline and we can revisit this later on.

right, what I'm trying to be careful here is to not break user-contract, and allow to have that set as soon as possible to avoid any possible race - and user assumption when it can be expected those to be effectively ready in the system. I'd prefer to have those as early as possible (as soon as a fs is set up) but that seems to be tricky. I'll first try to get a baseline and we can revisit this later on.

Good point!

Just for your information: mounts are shared when the command is executed in the network stage (did this for testing purposes in  /oem/90_custom.yaml). But this may be very late in the boot process... [partition 2, 4 and 5 are remounted rather late in the boot-process, especially partition 4]


Added a GitHub Action for automatic validation of your citation metadata

Overview: What does this pull request change?

adds a workflow to validate CITATION.cff file

Motivation and Explanation: Why and how do your changes improve the library?

Hello!
We noticed that your repository is using the Citation File Format to store citation metadata in CITATION.cff. This Pull Request automates validation of that file using the cffconvert GitHub Action. That way, it's a little bit easier to be robust against future changes to the CITATION.cff file.
BTW it's perfectly fine if you don't feel like accepting this Pull Request for whatever reason -- we just thought it might be helpful is all.
We found your repository using a partially automated workflow; if you have any questions about that, feel free to create an issue over at https://github.com/cffbots/filtering/issues/
On behalf of the cffbots team,
@abelsiqueira / @fdiblen / @jspaaks
Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

Hi, thanks for your PR!
I'm not sure if I'm missing something, but the action doesn't appear to have been run?

Hi, thanks for your PR!
I'm not sure if I'm missing something, but the action doesn't appear to have been run?

Hi @Darylgolden,
As the Pull Request is coming from the fork of your repository, the action will run when it is merged. The fork of the repository is here: https://github.com/cffbots/manim

Ah, I see now. Won't it be better if it's set to run upon a pull request too, like our other actions? Also, can you provide more details on what your action does? What exactly does it validate?

I also don't see the action run on your fork.

Ah, I see now. Won't it be better if it's set to run upon a pull request too, like our other actions? Also, can you provide more details on what your action does? What exactly does it validate?

The action validates CITATION.cff file against CFF schema. When there is a problem in the CITATION.cff it will warn you and give you hints to fix it.
The action will be triggered on every push that includes changes in CITATION.cff file. This covers Pull Requests, too.

I also don't see the action run on your fork.

That is expected as I haven't modified CITATION.cff when creating the Pull Request.
I have just updated the cff-version to 1.2.0 to trigger the action. You can see the running action here: https://github.com/cffbots/manim/runs/5093186774?check_suite_focus=true


[Beginner][Document] batch_processing Document Internationalization

All documents of this repo need to be save as English and Chinese just like README.md and README_zh.md in this repo root directory.
This issue aims to find contributors to take on the following documentation work.

batch_processing

please assign to me,thanks


Consider datastar-replace-url event

The replaceUrl attribute plugin exists for keeping the URL in sync with signals, but it might be overkill. If we were to say that only the backend should be allowed to replace the URL, then a new SSE event might be a better way to make this possible.
Before:
<div data-replace-url="'/page' + $page">

After:
event: datastar-replace-url
data: url /page2

I like this better then the action or attribute

Superceded by https://github.com/starfederation/datastar/pull/37


Debugger freeze

Issue Type: Bug
I use VSC under Win10 to write Javascript modules for node.js (windows installation).
Debugging with bulit-in node-debug worked very well until two months ago. Since then - with new VSC updates - breakpoints are only possible if they were set in only one JS module. With breakpoints in two or more modules the debugger freezes after the first breakpoint reached and must be restarted. In some cases, the debugger can only be terminated with the Win Task Manager.
Another thing: starting the debugger takes a very long time, i.e. about 20 s.
Are there any comments to my difficulties?
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz (4 x 3500)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.87GB (3.33GB free)

Process Argv

Screen Reader
yes

VM
0%

Can you try two things?

See if the nightly extension fixes any of your issues
If not, collect a trace log using these instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to<EMAIL_ADDRESS>

I have a similar problem, though the debugger never actually launches and reach breakpoint.
Using these instructions which work on OS X lead to VS Code not reaching the first breakpoint and two (hanging?) processes:

C:\Users\alexa\Documents\Projects\electron-quick-start\node_modules\electron\dist\electron.exe --version
"node" "C:\Users\alexa\Documents\Projects\electron-quick-start\node-modules\.bin\\...\electron\cli.js" --version

that need to be killed by hand.

nightly extension doesn't fix it.
"debug.javascript.usePreview": true fixes it.

Attaching log from "trace": true:
vscode-debugadapter-0.json.gz

"debug.javascript.usePreview": true, did you mean "debug.javascript.usePreview": false?
I'm not seeing any output given from electron's stdout/err, which would be expected even if all else failed. What version of Node and Electron are you running?

indeed, I meant false, edited above.
Node.js 12.14.1
Chromium 83.0.4103.122
Electron 9.1.2.
(these versions are from the project) and VS Code 1.47.3

Okay, thanks. Try setting your type to pwa-node instead of node, and adding "nodeVersionHint": 10, to your launch config.

so indeed with those changes and usePreview back to true, the debugger launches.
However, the output is a bit different than with usePreview: false:
"usePreview": true , "type": "pwa-node", "nodeVersionHint": 10:
C:\Users\alexa\Documents\Projects\electron-quick-start/node_modules/.bin/electron.cmd .
Debugger listening on ws://<IP_ADDRESS>:53804/cbd7d9ce-cf7a-48cc-8427-29741274d00b
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

Debugger listening on ws://<IP_ADDRESS>:53808/d17f2e22-8265-4a51-8e50-93e8e5f0b51d
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
test: main process reporting

"usePreview": false:
C:\Users\alexa\Documents\Projects\electron-quick-start/node_modules/.bin/electron.cmd --inspect-brk=19977 .

Debugger listening on ws://<IP_ADDRESS>:19977/897058d5-e589-47d8-8c6d-7a91e5dda68b
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
test: main process reporting

That's expected -- we debug all processes, including the electron 'wrapper' process (there's probably some more correct word for that).
Good to hear the issue is fixed. I'm not sure why you get stuck on C:\Users\alexa\Documents\Projects\electron-quick-start\node_modules\electron\dist\electron.exe --version, though. What happens if you run ./node_modules/.bin/electron.cmd --version in a terminal?

Right on! It hangs, be it in powershell or cmd, not sure why...

Hm. I'm curious whether it still fails if you set "electron": "^11.0.0-nightly.20200805" in the package.json (and npm install). If it does we should file an issue on Electron.

yep, hangs as well (i had to use "electron-nightly": "^11.0.0-nightly.20200805" and remove the "electron" dependency but i suppose this is what you meant)

Okay, interesting, thanks. I'll open an issue and tag you on it. Since I haven't received reports of this from other users, I am not planning to put a mitigation in place within js-debug at the moment, but I'll keep an eye out.


Any reason why checkForUpdates after component first time rendered  in useSelector ?

Do you want to request a feature or report a bug?
Discussion, maybe a bug.
What is the current behavior?
In current useSelector implement I found this line:
https://github.com/reduxjs/react-redux/blob/4be8b3f09519333e85accb9eea918c014df32f07/src/hooks/useSelector.js#L99
I believe it means when component first rendered the useIsomorphicLayoutEffect, as known as useLayoutEffect on web or useEffect on non-web, will run the callback and checkForUpdates is called.
I don't understand why we have to do that check. It seem that even if user changed the state immediately after component mount, onStateChange could handle it and let component re-render. Is it right ?
I tried to remove this line and all unit test passed. So if this line is important and cannot be removed may we add some test cases for it ? Otherwise may we remove that line ?
Thanks!
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to a CodeSandbox (https://codesandbox.io/s/new) or RN Snack (https://snack.expo.io/) example below:
None.
What is the expected behavior?
Add some test cases.
Which versions of React, ReactDOM/React Native, Redux, and React Redux are you using?  Which browser and OS are affected by this issue? Did this work in previous versions of React Redux?
<EMAIL_ADDRESS>cc
@byunicorn

B.T.W. Is this line used for same purpose ?
https://github.com/reduxjs/react-redux/blob/4be8b3f09519333e85accb9eea918c014df32f07/src/components/connectAdvanced.js#L365

Because it's possible that more actions could have been dispatched between the time the component rendered and the time it subscribes.  This is the pattern shown in Brian Vaughn's useSubscription implementation:
https://github.com/facebook/react/blob/0f64703edf5970b12a878ea3b5e1e30ef1d71c74/packages/use-subscription/src/useSubscription.js#L113-L116

And yeah, if our existing tests don't cover it, I'd happily accept a test that shows that.

Thanks for you reply and your link.
I'd like to add test cases after thorough understanding that implement.


Footer update

Issue No : #1788
Updated the footer Layout
Added a About Us column which has the links for the team members, projects, and top contributors
Added hover animation and fixed colour problems regarding social media links

Updated the comment where I added the issue no.


SkipFCntValidation Not as expected #412

fix issue #412
update fcnt after mic checkout

mistake， The MIC validation needs the full 32bit frame-counter for validation


build(deps-dev): upgrade TypeScript and Jest

:tada: This PR is included in version 0.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Compilation failed: Compilation failure: Ran out of memory in memory space vmem. Please file a bug against XLA.

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):NO
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Google Colab
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:NO
TensorFlow installed from (source or binary):Already installed on Colab
TensorFlow version (use command below):1.13.1
Keras version: 2.2.4
Python version:3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
I'm training my model on cloud TPU colab. My model has ~27M params.
The model is not compiling.
Describe the expected behavior
I've used others model using the same procedure and have trained successfully.
But facing problem with this model. Not compiling.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
def seresnext_model(input_shape):
  base_model = SEResNextImageNet(input_shape,include_top = False)
  x = base_model.output
  out1 = GlobalMaxPooling2D()(x)
  out2 = GlobalAveragePooling2D()(x)
  out3 = Flatten()(x)
  out = concatenate([out1,out2,out3])
  out = Dropout(0.3)(out)
  out = Dense(256,activation = 'relu')(out)
  out = Dropout(0.3)(out)
  X = Dense(1, activation='sigmoid', kernel_initializer='glorot_uniform', bias_initializer='zeros')(out)
  model =  Model(inputs=base_model.input, outputs=X)
  return model

tf.logging.set_verbosity(tf.logging.INFO)
tpu_model = tf.contrib.tpu.keras_to_tpu_model(
    seresnext_model,
    strategy=tf.contrib.tpu.TPUDistributionStrategy(
        tf.contrib.cluster_resolver.TPUClusterResolver(tpu='grpc://' + os.environ['COLAB_TPU_ADDR'])
    )
)
tpu_model.compile(optimizer=tf.train.AdamOptimizer(learning_rate = 3e-4), loss=tf.keras.losses.binary_crossentropy, metrics=['acc'])
filepath = '/content/model.h5'
#clr = CyclicLR(base_lr=2e-4, max_lr=0.006,
#                     step_size=1070.)
checkpoint = ModelCheckpoint(filepath,monitor='val_loss', verbose=1,
                             save_best_only=True)
history = tpu_model.fit_generator(train_gen,steps_per_epoch = train_steps,validation_data = val_gen,validation_steps = val_steps,epochs = 60,callbacks=[checkpoint],
                                  )

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
INFO:tensorflow:Querying Tensorflow master (grpc://<IP_ADDRESS>:8470) for TPU system metadata.
INFO:tensorflow:Found TPU system:
INFO:tensorflow:*** Num TPU Cores: 8
INFO:tensorflow:*** Num TPU Workers: 1
INFO:tensorflow:*** Num TPU Cores Per Worker: 8
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:CPU:0, CPU, -1,<PHONE_NUMBER>547489192)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:XLA_CPU:0, XLA_CPU,<PHONE_NUMBER>4,<PHONE_NUMBER>446983684)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:0, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>3587280753)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:1, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>095158121)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:2, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>571034056)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:3, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>5351803975)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:4, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>356234775)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:5, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>4960296885)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:6, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>9723062214)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU:7, TPU,<PHONE_NUMBER>4,<PHONE_NUMBER>42712443)
INFO:tensorflow:*** Available Device: _DeviceAttributes(/job:worker/replica:0/task:0/device:TPU_SYSTEM:0, TPU_SYSTEM,<PHONE_NUMBER>4,<PHONE_NUMBER>3784483275)
WARNING:tensorflow:tpu_model (from tensorflow.contrib.tpu.python.tpu.keras_support) is experimental and may change or be removed at any time, and without warning.
Epoch 1/60
INFO:tensorflow:New input shapes; (re-)compiling: mode=train (# of cores 8), [TensorSpec(shape=(128,), dtype=tf.int32, name='core_id_20'), TensorSpec(shape=(128, 96, 96, 3), dtype=tf.float32, name='input_1_30'), TensorSpec(shape=(128, 1), dtype=tf.float32, name='dense_33_target_50')]
INFO:tensorflow:Overriding default placeholder.
INFO:tensorflow:Remapping placeholder for input_1
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/contrib/tpu/python/tpu/keras_support.py:302: to_float (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/math_ops.py:3066: to_int32 (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/math_grad.py:102: div (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Deprecated in favor of operator or tf.math.divide.
INFO:tensorflow:Started compiling
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-44-3196f76a2e41> in <module>()
     12 checkpoint = ModelCheckpoint(filepath,monitor='val_loss', verbose=1,
     13                              save_best_only=True)
---> 14 history = tpu_model.fit_generator(train_gen,steps_per_epoch = train_steps,validation_data = val_gen,validation_steps = val_steps,epochs = 60,callbacks=[checkpoint],
     15                                   )

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py in fit_generator(self, generator, steps_per_epoch, epochs, verbose, callbacks, validation_data, validation_steps, class_weight, max_queue_size, workers, use_multiprocessing, shuffle, initial_epoch)
   1424         use_multiprocessing=use_multiprocessing,
   1425         shuffle=shuffle,
-> 1426         initial_epoch=initial_epoch)
   1427
   1428   def evaluate_generator(self,

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training_generator.py in model_iteration(model, data, steps_per_epoch, epochs, verbose, callbacks, validation_data, validation_steps, class_weight, max_queue_size, workers, use_multiprocessing, shuffle, initial_epoch, mode, batch_size, **kwargs)
    189       progbar.on_batch_begin(step, batch_logs)
    190
--> 191       batch_outs = batch_function(*batch_data)
    192       if not isinstance(batch_outs, list):
    193         batch_outs = [batch_outs]

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py in train_on_batch(self, x, y, sample_weight, class_weight, reset_metrics)
   1189       else:
   1190         self._make_fit_function()
-> 1191         outputs = self._fit_function(ins)  # pylint: disable=not-callable
   1192
   1193     if reset_metrics:

/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/tpu/python/tpu/keras_support.py in __call__(***failed resolving arguments***)
   1258     input_specs = infeed_instance.make_input_specs(input_tensors)
   1259     tpu_model_ops = self._tpu_model_ops_for_input_specs(input_specs,
-> 1260                                                         infeed_manager)
   1261     infeed_dict = infeed_instance.make_feed_dict(tpu_model_ops)
   1262

/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/tpu/python/tpu/keras_support.py in _tpu_model_ops_for_input_specs(self, input_specs, infeed_manager)
   1169                                                  infeed_manager)
   1170       self._compilation_cache[shape_key] = new_tpu_model_ops
-> 1171       self._test_model_compiles(new_tpu_model_ops)
   1172
   1173     return self._compilation_cache[shape_key]

/usr/local/lib/python3.6/dist-packages/tensorflow/contrib/tpu/python/tpu/keras_support.py in _test_model_compiles(self, tpu_model_ops)
   1112     if proto.status_error_message:
   1113       raise RuntimeError('Compilation failed: {}'.format(
-> 1114           proto.status_error_message))
   1115
   1116     end_time = time.time()

RuntimeError: Compilation failed: Compilation failure: Ran out of memory in memory space vmem. It should not be possible to run out of vmem - please file a bug against XLA.

Largest program allocations in vmem:

  XLA label: register allocator spill slots
  Allocation type: scoped

  XLA label: %fusion.276 = (f32[256]{0}, f32[256]{0}, f32[128,24,24,256]{3,0,2,1}) fusion(f32[128,24,24,256]{3,0,2,1}, f32[256]{0}, f32[128,24,24,8]{3,0,2,1}, f32[128,24,24,8]{3,0,2,1}, ...(+33)), kind=kLoop, calls=%fused_computation.272
  Allocation type: scoped

  XLA label: %fusion.276 = (f32[256]{0}, f32[256]{0}, f32[128,24,24,256]{3,0,2,1}) fusion(f32[128,24,24,256]{3,0,2,1}, f32[256]{0}, f32[128,24,24,8]{3,0,2,1}, f32[128,24,24,8]{3,0,2,1}, ...(+33)), kind=kLoop, calls=%fused_computation.272
  Allocation type: scoped

  XLA label: %fusion.276 = (f32[256]{0}, f32[256]{0}, f32[128,24,24,256]{3,0,2,1}) fusion(f32[128,24,24,256]{3,0,2,1}, f32[256]{0}, f32[128,24,24,8]{3,0,2,1}, f32[128,24,24,8]{3,0,2,1}, ...(+33)), kind=kLoop, calls=%fused_computation.272
  Allocation type: scoped

  XLA label: %fusion.276 = (f32[256]{0}, f32[256]{0}, f32[128,24,24,256]{3,0,2,1}) fusion(f32[128,24,24,256]{3,0,2,1}, f32[256]{0}, f32[128,24,24,8]{3,0,2,1}, f32[128,24,24,8]{3,0,2,1}, ...(+33)), kind=kLoop, calls=%fused_computation.272
  Allocation type: scoped

@jlebar

@ymodak for TPU related-stuff we need to find a different point of contact.
Perhaps @broune can forward this to the right person.

Thank you for the bug report and congratulations for finding a way to make a loop fusion run out of VMEM, that's a bit of an achievement. :) I'd guess that it has something to do with the 33 input operands to the fusion node - maybe if you stick something into your graph that will defeat fusion around that location, you can work around it that way until we fix it on our end (I'm not sure what's best for that - a conv that in effect does a 1x1 average pool, i.e. no effect, might do it). There should also be a flag to make fusion less aggressive on TPU, but I'm not sure if/how you can access that from open source.
@majnemer is the right person for internal errors in the TPU backend.

Thanks, @broune ... had to do coz for the first time the error itself told to report the bug. :)
Grateful to Google for providing free access to Cloud TPU on Colab. It saves a lot of training time.
May I know what exactly VMEM is, and why is it not possible to run out of memory in memory space VMEM? I used other models with params range(5M-15M) and they trained successfully.
Basically, I'm using Keras to build my model and importing it from Tensorflow. Here's my model notebook if it can help in any way: https://colab.research.google.com/drive/1Vze56xg06pUNqOsS3iIusA8v2R6jwXri

I can't get into specifics on the architecture, but VMEM is a memory space that is managed entirely by XLA. XLA should always be able to ensure that you don't run out of VMEM, so whenever it happens that's a bug in XLA.

I talked this over with Jim and he suggested that this might be in @ukoxyz 's domain.

obsolete.


Add estimator-level plotting function for driver genes

[ ] Additional function parameters, change functionality or change defaults?
[ ] New estimator in cr.tl.estimators?
[ ] New kernel in cr.tl.kernels?
[ ] New gene trend model in cr.ul.models?
[ ] New plotting function in cr.pl?
[ ] Other?

Show genes in scatter plot, correlations with lin_1 vs. lin_2. Optionally, annotate some genes to check with ground truth. Example plot in Fig. 1 below. Code for the function below as well. The function has been called as
# define some gene sets
trophoblast_genes = ['Gata3', 'Elf5', 'Ascl2', 'Phlda2', 'Rhox6',
                      'Batf3', 'Elf3']
neural_genes = ['Pou3f2', 'Nr2f1', 'Myt1l', 'Scrt2', 'Nhlh2', 'Pou2f2']
stromal_genes = ['Id3', 'Nfix', 'Nfic', 'Prrx1']
genes_oi = {'Neural_1': neural_genes,
            'Trophoblast': trophoblast_genes,
            'Stromal': stromal_genes}

# compute mean gene expression across cells, so we have somethign nice to color the dots by
adata.var['means'] = np.mean(adata.X.A, 0)

# make sure we color gene sets in the lineage colors used above
colors = adata.obsm['to_terminal_states'][list(genes_oi.keys())].colors

# call the actual plotting utility
plot_driver_genes(adata,
                  lineage_1="Trophoblast",
                  lineage_2="Neural_1",
                  genes_oi=genes_oi,
                  gene_set_colors=colors,
                  color="means",
                  color_map='RdYlBu_r',
                  alpha=0.5,
                  title="Putative lineage drivers",
                  size=80)

Fig. 1

Code
def plot_driver_genes(adata: AnnData,
                      lineage_1: str,
                      lineage_2: str,
                      genes_oi: Optional[Dict[str, Iterable]] = None,
                      gene_set_colors: Optional[Iterable] = None,
                      figsize: Tuple[int] = (6, 6),
                      **kwargs):
    """Show scatter plot of gene-correlations with two lineages

    Optionally, you can pass a dict of gene names that will be annotated in the plot.

    Note: this based on an idea by Maren Buettner, credit goes to her! See her notebook on gastrulation analysis
    for the original plot: https://github.com/theislab/gastrulation_analysis/blob/main/6_cellrank.ipynb

    Parameters
    --------
    adata
        Annotated data matrix
    lineage_1, lineage_2
        Keys from adata.var
    genes_oi
        Dict of the form `{'gene_set_name': ['gene_1', 'gene_2'], ...}
    gene_set_colors
        List of colors where each entry corresponds to a key from `genes_oi`
    figsize
        Figure size

    Returns
    -------
    Nothing, just plots.
    """

    # if gene set to annotate given, create colors (if not passed)
    if genes_oi != None:
        if gene_set_colors is None:

            # import utility and create a set of categorical colors
            from cellrank.tl._colors import _create_categorical_colors
            gene_set_colors = _create_categorical_colors(len(genes_oi.keys()))

    # set the figure size
    rcParams['figure.figsize'] = figsize

    # produce the actual scatter plot
    ax = sc.pl.scatter(adata, x = f"to {lineage_1} corr", y = f"to {lineage_2} corr", show=False,
                      **kwargs)

    # add some lines to highlight the origin
    xmin, xmax = np.min(adata.var[f"to {lineage_1} corr"]), np.max(adata.var[f"to {lineage_1} corr"])
    ymin, ymax = np.min(adata.var[f"to {lineage_2} corr"]), np.max(adata.var[f"to {lineage_2} corr"])
    ax.hlines(0, xmin = xmin, xmax=xmax, color='grey', alpha=0.5)
    ax.vlines(0, ymin = ymin, ymax=ymax, color='grey', alpha=0.5)

    # annotate the passed set of genes
    if genes_oi != None:
        for (key, value), color in zip(genes_oi.items(), gene_set_colors):

            # Label names and positions
            mask = np.in1d(adata.var_names, value)
            x = [i for i in adata.var.loc[mask, f"to {lineage_1} corr"]]
            y = [i for i in adata.var.loc[mask, f"to {lineage_2} corr"]]

            # prettify the font
            path_effect = [patheffects.withStroke(linewidth=4, foreground='w',)]

            for i, txt in enumerate(value):
                ax.annotate(txt, xy=(x[i], y[i]), path_effects=path_effect, size=14, c=color)

    plt.show()

closed via #640


webapp's io.py might clash with the standard library

When I set up my PyCharm to do some development work on asreview, it generated confusing error messages because it recursively discovered /asreview/webapp/io.py which made the standard library's io not accessible anymore. The workaround was to set PyCharm's working directory to a directory that isn't a parent of /asreview/webapp/io.py,  but perhaps we should consider renaming /asreview/webapp/io.py.

It is now integrated with asreview/data. Will be released in v2.0.


fix: switch to apps/v1 for daemonset to support change after deprecat…

…ion of v1beta1 api

Hi, is it possible to merge this PR please? Should we submit PR for further improvements or fork the repo ?
Thanks :)


making alert_text as a field

Hello,
we have installed elastalert in elasticsearch-5.4 and we created a rule like below
es_host: 192.168.X.X
es_port: 9200
es_username: abc
es_password: def
name: salck_alerts
index: metrics-*
type: any
timestamp_field: "@timestamp"
use_terms_query: false
filter:
- range:
   cpu.cpu_utilization:
    from: 1.296
    to: 75.00
alert_text: "ElastAlert has detected suspicious activity for .At this time, an error occured. Do somes thing about it!"
alert_text_type: "alert_text_only"
attach_related: true
alert_text_args:
 - tag.host
alert:
-slack: xxxxxxxxxxxxxxx

we are able to send alerts to slack and the problem is we are able to see the content of alert_text in slack but we are not able to see the same alert_text in kibana.
can we make alert_text as a field in elasticsearch.
also can we add custom fields in elastalert that is present in elastalert metadata index

Seems like a good idea.
If you want to mess with it yourself, here's the function that adds the alert json: https://github.com/Yelp/elastalert/blob/master/elastalert/elastalert.py#L1273
And here's where the alert string is generated, https://github.com/Yelp/elastalert/blob/master/elastalert/alerts.py#L42

Hi,
can i send alerts generated from elastlaert to any event management tool?
like zenoss, netcool, alerta.io..

Hi...
can we have any updates on this plss..

Old thread but I did this recently
https://github.com/tomrade/elastalert/commit/8e75b6d9d027c483521925f1a572d64c1ba81cb7
Is this something people want upstream?


Hazelcast yaml

@mesutcelik , thanks for the feedback. I'm closing this PR and will open one to the Spring repo.


Implement mutation and validation logics of resources in the admission webhook

The general mutation and validation logics in HTTP API functions are moved or re-implemented in the admission webhook.
longhorn #3562

I think we need to remove the validations from the volume Creation/Update functions in manager/volume.go. Furthermore, as I mentioned in the comments, we need to re-visit and simplify the VolumeManager implementation.

Agree.
One question while I was handling the validation function.
What's the purpose of CheckEngineImageReadiness?
How do we get the currentNodeID after moving to the webhook?
func (m *VolumeManager) verifyDataSourceForVolumeCreation(dataSource longhorn.VolumeDataSource, requestSize int64) (err error) {
...
		if snapName := types.GetSnapshotName(dataSource); snapName != "" {
			if _, err := m.GetSnapshot(snapName, srcVolName); err != nil {
				return err
			}
		}
	}
	return nil
}

func (m *VolumeManager) GetSnapshot(snapshotName, volumeName string) (*longhorn.Snapshot, error) {
	if volumeName == "" || snapshotName == "" {
		return nil, fmt.Errorf("volume and snapshot name required")
	}
	engine, err := m.GetEngineClient(volumeName)
	if err != nil {
		return nil, err
	}
	snapshot, err := engine.SnapshotGet(snapshotName)

func (m *VolumeManager) GetEngineClient(volumeName string) (client engineapi.EngineClient, err error) {
	var e *longhorn.Engine
...

	if isReady, err := m.ds.CheckEngineImageReadiness(e.Status.CurrentImage, m.currentNodeID); !isReady {
		if err != nil {
...

When volume.spec.DataSource is set, it indicates that the new volume is a clone of an old volume. In Longhorn, the clone is similar to rebuilding but involves 2 volumes. You can check this for details: https://github.com/longhorn/longhorn/issues/1815


dnp3: test of dnp3 flow direction fix - v3

https://github.com/OISF/suricata/pull/5324

This requires the suricata PR for version 5 as well I think

Merged as commit 8ee61e68f5e1138a025f6f7daa4e17634b0ccb4f


ROX-17702: follow-up fixes for missed comments

Description
Answering missed coments in #7138
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] ~Evaluated and added CHANGELOG entry if required~
[ ] ~Determined and documented upgrade steps~
[ ] ~Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed
Automated tests.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

Current dependencies on/for this PR:

master

PR #7136

PR #7137

PR #7570

PR #7564

PR #7572 👈


Add logo to splash screen

Create FUNDING.yml
Add splash logo
Add vercel integration
Add tw icon to splash page

Made a mistake, sorry!


Hello, can I use the emulator in Yupi ONE V4 CMS?

Hello, can I use the emulator in Yupi ONE V4 CMS?

Hello i don't know what is this One CMS v4.
But i think Yupi is compatible with the most common CMS's.
Good luck.


my project suddenly stop working and getting error "SWIFT_UNAVAILABLE"

the project was working fine, after removing derived data and perform "carthage build --platform iOS"
now it's showing below error

Thanks.

It seemes Objective-C project. I stopped supporting Objective-C project :(

@shogo4405  so now lf.swift not going to work on  Objective-C? can you please tell me which tag going to work for objective c?

Please try 0.5.12 or 0.5.11.
I'm considering to revert a commit...

@shogo4405 i already try that tags and its also showing same error, if you didn't revert any commit then can you please do that for me because now i am familiar with lf.swift and its working perfectly.
Thanks.

@shogo4405  any update?

I reverted. But I will be able to release 7.1 after a few weeks
Please consider use old version. And I have looked into the tag 0.5.12 again.
That is contains support for Objective-C code.


Replay m-map chunks irrespective of WAL

We should always replay m-map chunks as that is something unavoidable, unlike WAL.
/cc @beorn7, would be nice to get it in 2.20, its a tiny change

Will merge on green.

Note: The problem solved here can only be exposed by using TSDB as a library. In the way it is used within Prometheus, h.wal can ever be nil.

Yes, BUT the extra log line is really great.

Should L710 be adapted to say: WAL and memory chunks replay.... ? or should we reset start after playing the mmap chunks?

I added the extra log line as that marks the end of the replay, so thought of keeping a single log at the end.
We could log time taken by mmap, checkpoint and WAL replay in the last log line.

I modified the last log line to be WAL and on-disk memory mappable chunks replay completed

What I do not like is that I have a lot of time before the WAL replay starts - or at least that it what it looks like. Would love a log line after the in memory replay stops.

Especially since WAL replay is quite verbose, while mmap chunk replay is completely silent.

I have added more logs. Also showing the time taken to replay each component (mmap chunks, checkpoint, and the WAL), which is useful.


Install Bug - Missing files

When trying to run this off a r2z file from Thunderstore it seems to fail after just a few mods? Importing it works fine, figuring this is a problem with the profile system itself; but figured if its fixable it'd be nice
Modlist (from mods file) - mods.txt
Export - https://www.dropbox.com/scl/fi/jt8uctvg6fl2mujo09ssc/testi_1711116452022.r2z?rlkey=ycw8rv6f6yrtgw6y4y7327jma&dl=0
Command used (I pulled the file as R2ModMan instead of the long name it has)
./R2ModMan --install-dir=/mnt/server/R2/Temp --work-dir=/mnt/server/R2 --profile-zip=${R2Z_FILE}.r2z --run-timeout=10m --thunderstore-cdn-timeout=600s --thunderstore-force-download
Same occurs if I define the R2Z file by hand rather than through a variable

I see the same issue when using your mod list. It consistently fails on processing the bid-FireSpreads mod. I think it's a problem with the profile system as you stated. The bid-FireSpreads mod contains files with \ windows separators in the actual file name, while DeterminePackageType assumes Linux causing the mod packaging structure to be misinterpreted.

https://github.com/mpawlowski/r2modman-headless/commit/676060a11c87ca1ff28e8318bf54e3231c414117 should fix this. I was able to extract your mod zip, let me know if you still see any oddities.


Problem in TypeScript using NPM package

Hey guys,
When using the NPM package, I'm having an error where when I set personalizations like this:
.setPersonalization(personalization)
The error is caused because my object is something like this:
    const personalization = [
      {
        email<EMAIL_ADDRESS>        data: {
          name: 'Test Value',
          order: {
            total: '',
            number: '',
            shipping: '',
            subtotal: '',
            createdAt: '',
          },
        },
      },
    ];

And the personalization interface says that data has a string key and a string value:
export interface Personalization {     email: string;     data: {         [key: string]: string;     }; }
Can we fix this? Do u want any help?

@pmtascencao You are always free to submit a PR 🙇 Otherwise it will take a little bit of time for our team to fix it.

@pmtascencao issue has been resolved

@opheus2 Thanks a lot for the quick fix :+1:   @fosron next time I'll do a PR instead!


Fixed #35143 -- Accessibility improvements to debug error pages.

Fixes ticket #35143.
Notes
The HTTP 400 error page uses the same template as HTTP 500.
Requested changes
The page should have a header, main, and footer.
Done. I did not fix the indentation within the <main> element in the HTTP 500 template because it would cause a shift in most lines. The new CSS is hence somewhat hacky.
The indentation is currently inconsistent and is best fixed in a separate ticket.
Each table should have scope attributes on th elements.
Done.
Monospaced text in the patterns list should use a code element.
Done for all the pattern items in the HTTP 404 template. I kept the CSS line that sets the list font to monospace, to prevent a visual change to the list marker font.
I have also wrapped the Python Path value in the HTTP 500 page in a code block, but couldn't get a working unit test for this scenario. (there is a test draft in the related commit message).
I left all other <pre> elements without <code> for future tickets.
The small text within the h1 should use a small element instead of a span.
Done. Since <small> looked different from the original styled span, I reused the former's CSS.

Apologies for the multiple failed checks; I have the pre-commit running locally now.

As far as I can see, I've resolved all the issues we've found in the last two days.

@MHLut Thanks for updates :+1:

Note: The Selenium test that failed is test_inline_add_another_widgets (admin_views.test_autocomplete_view.SeleniumTests.test_inline_add_another_widgets).
As far as I know, my changes should not touch the admin, and I'm not sure where this is coming from.


Merge Elm into master

something didn't work as I intended here, hold on...

OK, for some reason the commit I pushed didn't descend from release/elm. Now it's fixed.


AccessDenied build failures in 'prodcon/fsharp/master/' - '20180411.03'

There were a set of failures during this build. Here is a summary of these:

https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build?_a=summary&buildId=1580441

Agent: DDMBLDW179
Error log: 1>Warning: System.TypeLoadException: Access is denied: 'Microsoft.FSharp.Compiler.Server.Shared.FSharpInteractiveServer'. while resolving 0x200000e -<EMAIL_ADDRESS>

https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build?_a=summary&buildId=1580933

Agent: DDMBLDW129
Error log: 1>Warning: System.TypeLoadException: Access is denied: 'Microsoft.FSharp.Compiler.Server.Shared.FSharpInteractiveServer'. while resolving 0x200000e -<EMAIL_ADDRESS>

@jcagme This is the wrong repo, try http://github.com/Microsoft/visualfsharp


Update icon file.

It seems the previous version of the file was uploaded with error and the icon can not be shown.

Hey @SabaRG  !
Looking at the site https://soteledu.com/, I see that it is an educational platform.
However, in your commit #3112, you mark that it is a "platform as ac Software as a Service on the cloud for businesses".
Do you have more information?

Hey @SabaRG !
Looking at the site https://soteledu.com/, I see that it is an educational platform.
However, in your commit #3112, you mark that it is a "platform as ac Software as a Service on the cloud for businesses".
Do you have more information?

No, it is not just for education, there are many different services on this platform for conferences, journal, eshop and etc. like:
https://stskill.ir/ on this platform as an educational website
https://ect.stskill.ir/ on this platform as a conference website
https://jws.stskill.ir/ on this platform as a journal website
https://sabaamooz.com/ on this platform as an organizational website (CMS)
http://iaiu.ir/ on this platform as a community website
http://sabarg.ir/ on this platform as a personal website
http://profile.sabarg.ir/ on this platform as a CV website
https://cheetahtrade.com/ on this platform as an eshop website


🔴 Ecosystem Project Idea: OP Stack Deployment UI

Summary
The goal is to design and implement a user-friendly interface to facilitate the deployment process of an OP Stack based blockchain. The interface should allow users to efficiently configure all the required files necessary for the deployment, as well as handle the smart contract deployment. One potential source of inspiration for this project is the Arbitrum Orbit Deployment user interface. After successful deployment, the interface should provide users with the configuration files and instruct them on how to run op-node and op-geth components using these files.
Possible Features

A simple yet comprehensive setup process that enables users to configure all the necessary files for the deployment.
An integrated deployment mechanism that deploys the smart contracts on behalf of the users.
Post-deployment, the interface should provide an option to download the configuration files.
Clear instructions and guides on how to operate op-node and op-geth with the provided configuration files.

Impact

It can significantly streamline the process of spinning up an OP Stack based blockchain, making it accessible to a wider range of users.
By simplifying the configuration and deployment process, it may encourage more experimentation and development on the OP Stack.
It can enhance the user experience by providing guidance and clarity post-deployment, contributing to a smoother onboarding process.

Hi, we are going to develop this.
You can see our expertise and how do we integrate this in our grant proposal
https://op-grants.charmverse.io/proposals?id=4c18dfae-8f33-4db9-9aa0-7eb99fa79311
Currently it has subgraph deployment which is proven to be able to deploy to deployed OP stack chain
These kind of UI will be implemented shortly at https://deploy.upnode.org
We have deployed a demo OP Stack chain called Upstack

Upstack RPC: https://upstack-rpc.upnodedev.xyz/
Upstack Explorer: https://upstack-explorer.upnodedev.xyz/

We have also deployed a demo subgraph (Gravatar) in Ethereum Mainnet and Upstack (Our OP Stack chain)

Ethereum Mainnet: https://graph-demo.upnodedev.xyz/mainnet/subgraphs/name/mainnet-gravatar/graphql
Upstack: https://graph-demo.upnodedev.xyz/upstack/subgraphs/name/upstack-gravatar/graphql
Monitoring Dashboard: https://graph-demo.upnodedev.xyz/dashboard

Note: for demo purpose only, username: demo password: demo
Feel free to create your gravatar at https://upstack-explorer.upnodedev.xyz/address/0x07072C1959816C3216D5518C20176b9fb349D814/write-contract#address-tabs and see the change in real time!

I see it's still open : P

@smartcontracts doesn't conduit.xyz already solve this?


⚠ ESPN has degraded performance

In a3e1ae1, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 1270 ms

Resolved: ESPN performance has improved in bb2e7f3.


Adpater stürzt ab

Adapter stürzt ab sobald ein Bild gesendet wird.
echarts.0
2022-07-28 08:07:31.058	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
echarts.0
2022-07-28 08:07:31.056	info	terminating
echarts.0
2022-07-28 08:07:30.547	error	Cannot read properties of undefined (reading 'length')
echarts.0
2022-07-28 08:07:30.546	error	TypeError: Cannot read properties of undefined (reading 'length') at normalizeConfig (/opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:201:19) at ChartModel.analyseAndLoadConfig (/opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:288:31) at /opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:279:29
echarts.0
2022-07-28 08:07:30.545	error	unhandled promise rejection: Cannot read properties of undefined (reading 'length')
echarts.0
2022-07-28 08:07:30.543	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
echarts.0
2022-07-28 08:07:14.570	info	starting. Version 1.0.12 in /opt/iobroker/node_modules/iobroker.echarts, node: v16.16.0, js-controller: 4.0.23
echarts.0
2022-07-28 08:06:40.980	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
echarts.0
2022-07-28 08:06:40.977	info	terminating
echarts.0
2022-07-28 08:06:40.468	error	Cannot read properties of undefined (reading 'length')
echarts.0
2022-07-28 08:06:40.467	error	TypeError: Cannot read properties of undefined (reading 'length') at normalizeConfig (/opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:201:19) at ChartModel.analyseAndLoadConfig (/opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:288:31) at /opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:279:29
echarts.0
2022-07-28 08:06:40.465	error	unhandled promise rejection: Cannot read properties of undefined (reading 'length')
echarts.0
2022-07-28 08:06:40.459	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
echarts.0
2022-07-28 08:05:45.371	info	starting. Version 1.0.12 in /opt/iobroker/node_modules/iobroker.echarts, node: v16.16.0, js-controller: 4.0.23
echarts.0
2022-07-28 08:05:11.918	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
echarts.0
2022-07-28 08:05:11.916	info	terminating
echarts.0
2022-07-28 08:05:11.407	error	Cannot read properties of undefined (reading 'length')
echarts.0
2022-07-28 08:05:11.406	error	TypeError: Cannot read properties of undefined (reading 'length') at normalizeConfig (/opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:201:19) at ChartModel.analyseAndLoadConfig (/opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:288:31) at /opt/iobroker/node_modules/iobroker.echarts/_helpers/ChartModel.js:279:29
echarts.0
2022-07-28 08:05:11.405	error	unhandled promise rejection: Cannot read properties of undefined (reading 'length')
echarts.0
2022-07-28 08:05:11.399	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
echarts.0
2022-07-28 07:35:09.414	info	starting. Version 1.0.12 in /opt/iobroker/node_modules/iobroker.echarts, node: v16.16.0, js-controller: 4.0.23

Please try if it happens again in current versions

i cannot reproduce it


How to use continuation ident for parameters?

Hi guys,
How to have a setting similar to next:

There is an option in the .editor-config file. However it is not used anymore because the official kotlin style guide says to just use four spaces for continious indentation (https://github.com/yole/kotlin-style-guide/issues/38).

I don't remember if it defaulted or we set use continuation ident during team decision.
As for now, IDE adds 12 spaces to a method param on the new line = 4 from ident and 8 from continuation ident.

I'm sorry but both Android Style Guide and Kotlin Coding Conventions do not mention continuation indent size and so it's unlikely to be supported.
The recommendation is to set continuation_indent_size = indent_size = 4.


Up capacity void hatch

with void mode

void hatch has no capacity
It just removes matched fluid from outputs.

GT5u assumes that all output hatches only outputs 1 type of fluid(ME output hatch has special checks, that's an exception).
So it won't work if I add capacity to void hatch.
It only lets 1 type of fluid bypass the voiding check, if you mark 2 types of fluid, things are broken.
So you have to trun off voiding protection, or add more output hatch to trick the parallel system to run.

As you can see, there's no Multioutput Hatch in GT5u, if GTNH dev did not provide such API, that's unlikely to be done.


Add support for Bryophyta's Staff, Tome of Fire, and fixed miscalculation with fire rune cost.

Added support for Bryophyta's staff (1/15 chance of not using nature rune).
Changed the "Using Fire Staff" config to instead be a menu with Fire Staff, Tome of Fire, and Fire Rune.
The original calculation for fire rune cost didn't take into account that it takes 5 fire runes to cast High Alch.

Sorry for not breaking the changes up into individual commits. IDK how git works lol.


FPS added to Android benchmark

Android benchmark will run first with synchronous rendering and then async rendering.
It will save the results in different files: benchmark_results_sync_rendering.json and benchmark_results_async_rendering.json.
For each it will report FPS, encoding time and rendering time.

I would like all benchmark results in one JSON file. Makes processing a bit easier.
@alexcristici If you want I can make the needed changes.

Sure, thank you!

I have added another style and write out the results of each run individually (along with syncRendering boolean).
Also I cleaned up the code a little bit.
https://github.com/alexcristici/maplibre-native/pull/25

!benchmark android


Npm Publishing

Hi, thanks for the plugin, it is the only plugin works for IOS properly.
But there was a problem with adobe phonegap build system. Therefore I added it in to npm publish list.
Please accept my commits and change your paket name from it.almaviva.openurlext to "cordova-plugin-openurlext"
Thank you

Hi serdarde,
thanks for your contribution, i already merge your pull request and change to "cordova-plugin-openurlext".


Error igotify  | Disconnection happened, type: Error igotify  | Webseocket Reconnection failed with Error. Try to reconnect in 10s.

Latest ios 17
iphone 15 pro
Hello would you be able to help me igotify working ?
all i see are these error
igotify  | Disconnection happened, type: Error
igotify  | Webseocket Reconnection failed with Error. Try to reconnect in 10s.
igotify  | Disconnection happened, type: Error
igotify  | Webseocket Reconnection failed with Error. Try to reconnect in 10s.
and
gotify  | 2024-08-04T20:1808-04:00 | 400 |    1.186004ms |   <IP_ADDRESS> | GET      "/stream?token=[masked]"
gotify  | Error #01: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header
gotify  | 2024-08-04T20:1818-04:00 | 400 |     190.093µs |   <IP_ADDRESS> | GET      "/stream?token=[masked]"
gotify  | Error #01: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header
I am able to login successfully in the app no error

you can write me also on Discord, i accept the request

What was the solution?

He fixed it by his self
Can I help you?


Occasional rate limiting errors

We are running this tool with quite a lot of snapshots being generated (once an hour, kept for 7 days for multiple clusters).
In this configuration, we are seeing the occasional errors due to rate limiting:
[ERROR]	2018-10-08T02:30:33.680Z	6153e97f-733f-4764-899c-a89c052312c8	Exception sharing dev-aurora-cluster20181001042229986400000001-2018-10-04-23-00: An error occurred (Throttling) when calling the ModifyDBClusterSnapshotAttribute operation (reached max retries: 4): Rate exceeded

or
An error occurred (Throttling) when calling the ListTagsForResource operation (reached max retries: 4): Rate exceeded: ClientError
Traceback (most recent call last):
File "/var/task/lambda_function.py", line 49, in lambda_handler
ResourceName=snapshot_arn)
File "/var/runtime/botocore/client.py", line 314, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/var/runtime/botocore/client.py", line 612, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (Throttling) when calling the ListTagsForResource operation (reached max retries: 4): Rate exceeded

This happens often enough that it not only fails the Lambda but also the Step Function after retries.
Is there a way to reduce the number of calls the tool makes or are we simply going beyond the limit of what's possible with the current implementation?

Hi @flosell, how many instances of the tool are you running on the same account?

@mrcoronel one instance per account

Is there any chance you'd have other tools/scripts hitting the RDS APIs? How many snapshots have you got in that account?
There are a few optimisations that I could make (not too many though), but I won't have much time to implement them until next month.
If you've got a support subscription, perhaps you could open a case so they can help you find out why your calls are being throttled?

I've seen the same errors. We have 200 snapshots. I opened a PR (#12) that should help with this. Seems to work so far in my tests.  The function is fetching tags for automated snapshots that will never be returned and manual snapshots are being fetched twice.

Running over the weekend I didn't get any tag throttling. I did get throttled calling DescribeDBClusterSnapshots which is kind of confusing. It only happened once and was fine when it retired so I'm not worried.

just merged the PR... the new version is in the buckets too... thanks for the contribution!


Ran 2to3 on Expect.py + minor fix in AristaLibrary.py

@CloudAloud Here is my PR that you wanted me to do to get this up and running with Python version 3.  I have tested the changes against a lab switch at work and it works like it should.  Please let me know if you have any questions about my commits.
Thank you,
tetheredge


Proxy setup for Google Chat notifications

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
Hello,
I would like to use the Google Chat notifications system but I have a Timeout error:
Error: Error: Error: connect ETIMEDOUT <IP_ADDRESS>:443
    at GoogleChat.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
    at GoogleChat.send (/app/server/notification-providers/google-chat.js:41:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Socket.<anonymous> (/app/server/server.js:1124:27)

✔ Solution
To join the Google Chat server, I need to go through a web proxy.
It's possible to create and use proxy for monitors but not for notifications.
Solution: for notifications who use http(s) protocol, add a dropdown list to chose an existing proxy.
❓ Alternatives
No response
📝 Additional Context
No response

I have a similar issue with sending webhook requests to Microsoft Teams.  my uptime-Kuma setup in the internal environment, any HTTP request to the internet should go through the proxy. The proxy setup for minoring works perfectly, but the notification setup is not using the proxy setup.
Here is my log.

Error: Error: Error: connect ETIMEDOUT <IP_ADDRESS>:443
at Teams.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
at Teams.send (/app/server/notification-providers/teams.js:149:18)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)

@beavis6511  I have found the solution.
in your compose file set the environment variable something like this
environment:
  HTTP_PROXY: 'http://proxy.example.com:3128'
  HTTPS_PROXY: 'http://proxy.example.com:3128'

After setting up this the proxy through env variable, my Teams notification started working.

@dineshbabu179 Even after the environment variables HTTP_PROXY and HTTPS_PROXY have been stored in the package.json continues to run the teams notification in the error 'ETIMEDOUT'.  The proxy variables set in Linux are also not used. What other option do I have to send a notification via a proxy?

my log:
Error: Error: Error: connect ETIMEDOUT <IP_ADDRESS>:443
at Teams.throwGeneralAxiosError (/opt/uptime-kuma/server/notification-providers/notification-provider.js:38:15)
at Teams.send (/opt/uptime-kuma/server/notification-providers/teams.js:153:18)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Socket. (/opt/uptime-kuma/server/server.js:1189:27)

Duplicate of #616


webtorrent STUN server usage

How to use STUN server with webtorrent, is there any config for that ?
Maybe I am asking already answered question, but I cant figure out how to do that.

Thanks!


Digits on counters are not shown

Twitter has changed its counter and caused a problem: digits on all the other counters are not shown.
https://blog.twitter.com/2015/hard-decisions-for-a-sustainable-platform

Update to the latest version.


Real time video

Can this work to detect cards in real-time/live video?

You can close

I have not tested the package with real-time video. It does not have an interface for such a use case and, the speed may not be up to it when all the features are used.
In short, there is currently no support for real-time detection.


DartEditor should warn when a dash is used in the package name

This issue was originally filed by @zoechi

What steps will clearly show the issue / need for enhancement?
1.
http://stackoverflow.com/questions/24723315
It seems Polymer transformer (I suppose) produces library statements containing the package name which is invalid when the package name contains a dash
2.
3.
What is the current output?
What would you like to see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
This seems to require the opposite https://code.google.com/p/dart/issues/detail?id=19354

Closing, DartEditor is no longer being maintained.


BigQuery: Updates table snippets

Updates existing snippets and adds new snippets for inclusion in /bigquery/docs/tables

Circle is failing due to missing region tag reference in the usage docs.


__builtin_ia32_mwaitx undefined

I am on Ubuntu 16.04 using gcc 5.3 and CUDA 7.5 and get the error that __builtin_ia32_mwaitx is undefined. I have not made any changes to the user.mk file except to GPU_ARCHS line. Is there a recommended version of CUDA and gcc? Thanks

Updated to CUDA 8 (9 seems too new for now). Will post results here.

Hi @sherandoresearch, strange that this didn't work. What was the full error? Was it during the install or test stage?
I have also had some problems with CUDA versions less than 8 in the past. It's good to hear that CUDA 8 is now working for you.
I have also just added a note about this in the docs, thanks for letting us know.


WIP: RC-004-OAuth

Reddit page is called and it is possible to login but afterward, it fails with a bad request.
color scheme change

done in another branch

done in another branch


Image issue

Hi there!
I used this to work around the image issue once converting the GEF file to seurat readable format but I am still having issues with the proper image showing up. When plotting to check the QC i get the following image and I am not sure what I am doing incorrectly:

Hi there!
I used this to work around the image issue once converting the GEF file to seurat readable format but I am still having issues with the proper image showing up. When plotting to check the QC i get the following image and I am not sure what I am doing incorrectly:

Hi
Everything you are doing is correct! The legend shows the data is there just not visualized. The default parameters of SpatialFeaturePlot is set for 10X Visium data. Please try the pt.size=150, stroke=5... please try different parameters to visualize your heatmap.
Best,
Limin

Hi Limin!
So I have been switching around various parameters but it still does not seem to be rendering the image correctly? This is all being done on the demo mouse brain data. The QC png that is generated turned out just fine though. Do you happen to know the parameters you had tested?
Best,
Dipak

Hi Limin!
So I have been switching around various parameters but it still does not seem to be rendering the image correctly? This is all being done on the demo mouse brain data. The QC png that is generated turned out just fine though. Do you happen to know the parameters you had tested?
Best, Dipak

Would you mind share your rds obj, I could try and send you the code. Please share your rds to this email<EMAIL_ADDRESS>Best,
Limin

The file is too big to send via email. I used this link to download the demo data: http://<IP_ADDRESS>:8090/share/dd965cba-7c1f-40b2-a275-0150890e005f
I utilized the tissue.gef file and converted it to h5ad via stereopy and then used the converted file with the regist.tif with addimg2anndata to generate the RDS file.
Best,
Dipak

Hi Limin,
I was able to get it to work! pt.size.dactor = 10k with stroke being .25 was able to help me get the visual. So sorry to take up your time like this. Thanks again for making this package!
Best,
Dipak

Hi Limin,
I was able to get it to work! pt.size.dactor = 10k with stroke being .25 was able to help me get the visual. So sorry to take up your time like this. Thanks again for making this package!
Best, Dipak

Hi Dipak,
Glad you made it work. A lot of exploration I guess. That is the learning pass.
I am going to close this topic.
Best,
Limin


v2: wishlist

Tracking item for potential breaking changes we may consider when publishing a v2 (to be clear: such a release it not yet planned).
DateRangePicker:

Change default date format to ISO-8601

Closed while cleaning up the issues. Feel free to ping here with a comment in case I should create a new issue/task out of it.


98 voting pallet

Implemented functions to manage voting through the collective and democracy pallet for the House Council vote session and Investors vote session

Codecov Report

Merging #107 (2d70c77) into main (9bcff90) will decrease coverage by 8.04%.
The diff coverage is 8.53%.

@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
- Coverage   60.34%   52.30%   -8.05%
==========================================
  Files          22       27       +5
  Lines        1339     1585     +246
==========================================
+ Hits          808      829      +21
- Misses        531      756     +225

Impacted Files
Coverage Δ

node/src/chain_spec.rs
0.00% <0.00%> (ø)

pallets/voting/src/structs.rs
0.00% <0.00%> (ø)

pallets/voting/src/weights.rs
0.00% <0.00%> (ø)

runtime/src/lib.rs
2.77% <0.00%> (-0.30%)
:arrow_down:

pallets/voting/src/lib.rs
5.04% <5.04%> (ø)

pallets/voting/src/mock.rs
60.00% <60.00%> (ø)

pallets/voting/src/tests.rs
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update dev dependencies

This pull request includes a

[ ] Bug fix
[ ] New feature
[ ] Translation
[x] Update dependencies

The following changes were made

Migrate from node-sass (deprecated) to Dart Sass
Migrate from QUnit 1 to QUnit 2 https://qunitjs.com/upgrade-guide-2.x/

Questions

Should I commit dist/ files changes?
Why package-lock.json was not versioned?
Running grunt test I get a timeout error for tests/unit-jq*.html, but works ok opening a browser.

@kevin-brown this PR could replace the upgrade-qunit branch.
How can I help modernize this project?

Hi @kevin-brown
Should I do the effort to rebase this PR?
Feel free to close it if you think it will not be merged.


Reassigned types ignored after return

Bug Report

🔎 Search Terms

return
early return

🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about return

⏯ Playground Link

Playground Link
💻 Code

const a = (s: string) => {}

const b = (s: string | number) => {
  s = "";
  return;
  a(s);  // <- Error occurs here (type 'number' is not assignable to type 'string')
}

const c = (s: string | number) => {
  s = "";
  a(s);  // <- No error here
}

🙁 Actual behavior
On the line a(s); in the function b:
Argument of type 'string | number' is not assignable to parameter of type 'string'.
  Type 'number' is not assignable to type 'string'.

Type error is thrown even though s is reassigned as a string before the call.

🙂 Expected behavior
No type error.
Without the return, as in the function c, everything works as expected.

Not sure whether this is intended or not, but seems like a bug to me. Thanks!

See #26914

Ahh, thanks. Missed that.


Add integration spec and solve n+1 problem

Hello
I hope this message finds you well. I have recently completed a significant portion of the project, and I am now seeking your valuable feedback and review. I have made the following enhancements and additions based on the project requirements:
Addressing the N+1 Problem:
Ensured the resolution of the N+1 problem when fetching all posts and their comments for a user.
Instead of relying on the bullet gem, I meticulously analyzed the logs as illustrated in the provided article.
I have included screenshots of the application's logs before and after implementing the fix, which will be attached in the PR description.
Before

## After

## Integration Specs using Capybara:
Employed Capybara to create integration tests for each view in the project.
Organized the tests in a logical flow, grouping them by page functionality.
Here is a summary of the integration tests for each view:

User Index Page:

Verified the display of other users' usernames.
Ensured the profile picture is visible for each user.
Validated the accurate count of posts written by each user.
Confirmed the redirect functionality when clicking on a user, leading to their show page.

User Show Page:

Verified the visibility of the user's profile picture, username, and bio.
Confirmed the correct count of posts written by the user.
Ensured the display of the user's first three posts.
Validated the presence of a button allowing users to view all posts.
Confirmed the correct redirection when clicking on a user's post or viewing all posts.

User Post Index Page:

Validated the visibility of the user's profile picture, username, and post count.
Ensured the accurate display of a post's title and partial body.
Verified the visibility of the first comments on a post.
Confirmed the correct count of comments and likes on a post.
Ensured the presence of a pagination section for posts exceeding the view limit.
Validated the correct redirection when clicking on a post, leading to its show page.

Post Show Page:

Verified the display of the post's title, author, comments count, and likes count.
Ensured the visibility of the post's body.
Confirmed the presence of the commentor's username and their respective comments.
Additionally, I have included integration specs for any other features I have implemented throughout the project.

RSPEC TEST RESULTS SCREENSHOT:

N/B: I would love to inform you that I worked on this project alone, since I have no partner to pair with, as it is evident below::

I kindly request you to review my work and provide feedback regarding the addressed N+1 problem and the implementation of the integration tests. Your expertise and insights will be immensely valuable in enhancing the overall quality of the project.
Thank you for your time and attention. I look forward to your feedback.

Hi @Odongo006,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that is invalid because you worked on the project alone instead of working with your coding partner
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

Hello @codecaiine, as you can see I have not test failing and asking me to fix the tests, I don't even know where to start from since, the tests are working for me as it is evident below:

Hi @Odongo006 As you noticed on my screenshots and other CRs machine, there were some failed tests If you think that everything is working from your side, Please submit but I would like to recommend you double-check again. Good luck 👍


Simplify generated code

Rather than generate anonymous functions for getters and setters, add an internal function that matches the pattern so the generated code can simply apply the named internal function. This should reduce the size the library grows per added entity.

I did this and it cut 33 percent off of a library that contains all entities, functions, and actions. From 8MB to 5MB


Virtual text aligned "above": Wrong indentation when using tabs

Steps to reproduce
When using virtual text, with text alignment "above", in combination with using tab-characters, either in the text or in the virtual text, the indentation is not correct.

The wrong indentation depends on current window-width.
This happens with vim and gvim (of course, also when started with vim --clean or gvim --clean)

Used example text and vim commands:
123456789 123456789 123456789 123456789 123456789 12345678

        | space prefixed text
	| tab prefixed text
        | space prefixed text
	| tab prefixed text

set tabstop=8
call prop_type_add("test", { 'highlight' : 'Error' })
call prop_clear(1, 99)
call prop_add(3, 0, { 'text_align' : 'above', 'text' : '|<-', 'type': 'test', 'text_padding_left' : 8 })
call prop_add(4, 0, { 'text_align' : 'above', 'text' : '|<-', 'type': 'test', 'text_padding_left' : 8 })
call prop_add(5, 0, { 'text_align' : 'above', 'text' : '        |<-', 'type': 'test'})
call prop_add(6, 0, { 'text_align' : 'above', 'text' : "\t|<-", 'type': 'test'})

First screenshots before executing the vim commands for adding text properties: All pipe-symbols line up vertically (i.e. are displayed in the same column)
:set nolist

same with :set list

After execution of the vim commands from the script above: The indentation of the text following the virtual text is wrong and the indentation of the virtual text that is prefixed by a tab-character is wrong, too, i.e. the pipe-symbols do not line up vertically any more. The wrong indentation depends on the window width. Can be best seen on the right side (virtual text is highlighted in the color red):
:set nolist

:set list

This also happens with only one window, i.e. is not related to splits.
When adjusting the window size (e.g. by setting the option 'columns'), the wrong indentation changes, too. In order to visualize this a vertical split with two different widths is shown the screenshots above.
Expected behaviour
Text and virtual text shall be correctly indented, even when using tab-characters, .i.e. in the screenshots above all pipe-symbols shall line up vertically
Version of Vim
Vim AppImage Release v9.0.1433
Environment
Operating system: Ubuntu
Terminal: alacritty
vim executables: vim & gvim
Logs and stack traces
Is it possible that it is related to this?

https://github.com/vim/vim/blob/b6ebe5af74a965d703eb8ee66a07c97b0bbe6e58/src/textprop.c#L225

Some further analyses:

The case where the virtual text contains "\t" characters is already known and documented here (I'd assume there will be no change soon):

https://github.com/vim/vim/blob/bfc7cbd1d44e53e844a079d8ad16ae990dad664d/runtime/doc/textprop.txt#L220

If (non-virtual) text lines contain multiple tab characters then only the first "\t" seems to be affected. Below is a screenshot analog to the example above but now with two leading "\t" characters instead of only one. Take notice of the different rendering depending on the particular window width:


Interactive report Fixed to None.

Hi,
I have an interactive report which is quite big in size, when it is set to "fixed to none" the report is expanding in such a way which is going away from report template.

What would be the behaviour you want? There is multiple ways we can handle this. A report this size is usually something I want to rethink & redesign.
We can:

Crop horizontally and add horizontal scrolling inside the box
Expand the box and add horizontal scrolling to the page

My advice is to avoid horizontal scrolling completely and rethink the report.

We have reports usually of that length. will try with the solutions provided above.
Thank you..