text:
Are you still maintaining this?

Hi,
This appears to be the better of the two existing Monocypher Python bindings but you haven't done a release since 2020 and there are some Monocypher functions missing that we need to use, although I see you have commits here rather recently. Our tracking issue is https://github.com/covert-encryption/covert/issues/63
I have built a new binding based on this but with a somewhat different design:

Removing the crypto_ prefix of all functions
Implementing a custom Python buffer type that automatically wipes its contents on deletion
Returning that type, or optionally using any existing bytes-like writable buffer for return values
Adding docstrings

The new implementation is based on your CFFI build and I'd wish to have it released on PyPi but would prefer not to add a third option there, and would also prefer not to keep maintaining it long term. So, I could either make a fork of this project, replace the Python implementation and release under another module name such as monocyph to avoid conflicts, or ideally you could adapt the new code (a breaking change obviously but given the version number is still 0.0.1 I gather that this might not be too bad). I could make a PR here if you wish to review it closer.
There are a few remaining issues such as using hashlib sha512 as a custom hash for Monocypher which itself only implements Blake2b, making it incompatible with standard Ed25519 keys and signatures. I am not sure whether @LoupVaillant intends to add a C implementation of SHA-512 to allow standards compatibility.
Let me know of your thoughts and intentions on this.

I am not sure whether @LoupVaillant intends to add a C implementation of SHA-512 to allow standards compatibility.

Monocypher already has an implementation of SHA-512 in its optional files. I needed it for Ed25519 to begin with, so I exposed it to the end user, and added HMAC to give it feature parity with Blake2b.
Note that the makefile provides a way to bundle both the main compilation unit and the optional compilation unit in the same shared library, so language bindings that want to rely on both, can.

@LoupVaillant Cool, then just need to add the optional files to the build (very simply done in Python CFFI by setuptools during package build, not using the Makefile) and implement wrappers for those functions as well. This is much better, as it avoids building vtables and supporting the generic functions in Python.

Hey there, apologies for the late response.
The library is (from my point of view) feature-complete since I don't plan to use the SHA256 features that you are requesting (which indeed, can be included by including the optional files in Monocypher). I'm actively using it for a small tool I have locally.
Couple of notes:

I initially used crypto_ prefix against all of the functions, so that I could easily find documentation for them in the Monocypher manual.
Yep -- that buffer bit did irk me a little, glad that you found a custom solution.
And yes, docstrings are lacking because the expecatation was that mainly users would use the higher level API, and if you're using the lower-level API they would map 1-1 with Monocypher's manual.

I'm more than happy to review your PR.

#2 adds the optional module but does no other changes and provides no high level wrapper. Feel free to make one, or change the current one to use standard Ed25519 instead (I find very little use for the non-standard implementation that uses Blake2b).
The other changes are more breaking, and will have to be done as separate PRs, if not as a separate module built on this.

repo: eugene-eeo/monocypher-py


text:
Add P3 examples

Adds a few hopefully interesting examples focusing on measurements from the P-3. Uses the colorcet, seaborn and especially cartopy Python modules. Cartopy has many dependencies so modules are now installed via conda for the Continuous Integration. Adding cartopy closes #50 and may be relevant to #11.
Probably best to squash-and-merge as no one needs to see my stumbling around.

To install Python dependencies with conda: conda env create -f environment.yml

... and probably we need to update gitlab-ci.yml to install dependencies and invoke the virtual environment with conda rather than `pip.

@tmieslinger In case you have the bandwidth to look over these changes (@d70-t being quite busy it seems), I would prefer not to merge them until someone else had a look at them.
Note that the cell timeout is currently set to 150 seconds; this sometimes is too short for the P-3 flight track cells.
Also - we're now using conda to manage Python dependencies in the Github CI but I don't know how to make this change on the Gitlab which builds the book for distribution.

Initially I thought the best solution might be to include cartopy in requirements.txt as this would require one step less to install manually (users would only have to install cartopys dependencies, not cartopy itself manually).
But now I am thinking, maybe it is actually better not to specify it in requirements.txt, because that way, the installation won't fail if the dependencies of cartopy are not there. In stead only those notebooks which actually use cartopy will fail. If someone wants to run / edit the book without having cartopy installed, this would then still be possible (one would have to ignore some build errors though, but that's probably ok?).
If a user who doesn't use conda is more in the cartopy-business, I think it is not significantly more complex to install cartopy's dependencies and cartopy itself.
I'd suggest to update the running locally document (which should soon turn into a few more chapters describing how to contribute, prepare datasets etc...) such that it contains at least a description on how to set the book up using conda. I'd also keep the description on pip and add a short note that one should try to get cartopy running as well. (This might be as simple as apt install python3-cartopy or something similar using brew, but I'd not go into further details. For the two alternatives, tabbed blocks or panels might be handy. I'd be happy if you could write something about conda, because I really don't know that thing. If you don't want to mess too much on pip here, I'd suggest to make this PR such that it runs smoothly on conda and is properly documented. I'll then create a new PR on top of this which tries to get a new pip based thing running again as well.

@d70-t I added material to the chapter on running locally to describe the use of conda. You can let me know if it's not clear. I don't mention, but maybe I should, that conda is much slower than pip, partly but not exclusively because it's managing cartopy and its dependencies.

As @tmieslinger noted, it seems like I've forgotten to include the color_of_day function in the review:
def color_of_day(day):
    return plt.cm.viridis(norm(day), alpha=0.9)

@d70-t @tmieslinger Thanks for your very helpful comments. I believe they are all incorporated including a little bit of extra explanation about how to run locally. I've explained that users need to manage the installation of cartopy themselves.
I have not updated the gitlab-ci to work with conda so the book won't publish automatically until/unless you adopt the Github publishing @d70-t is working on with #53 .
As of now I won't plan to make further changes until the publishing issue is resolved, but it would be nice to have this folded in sooner than later.

I would suggest that you add yourselves as co-authors to the commit.

@d70-t The speedup was an excellent suggestion, thanks a lot, and I think all the changes are in place. The CI is failing in the HAMP chapter for reasons I don't understand, but we can re-run the CI before merging once the domain is in place.

The HAMP files have been moved. That should be fixed in eurec4a/eurec4a-intake#67, but maybe I'll have to add another quick fix to the book as the version update could lead to a minor issue in some of the chapters... I'll sort it out.

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Error submitting OAuth registration for approval

HTTP Status 405 - HTTP method POST is not supported by this URL
Seems to be trying to go to the OAuth callback URL, which is wrong.

Was a wrong mime type set for the response for the user request endpoint in eurekaclinical-user-service. Fixed.

source: gharchive/issue

license_source: bigquery


text:
Decide about logging call style format

I checked. Back when I introduced go-autumn-logging, I didn't go through the entire code to update every place where the logging Wrapper was called, because the logging wrapper was also passed around as a function argument, and that would have meant bigger code changes. We knew we'd be reworking all the services anyway.
But now that time has come :)
While I don't mind a wrapper if it helps us, autumn logging already includes very similar convenience functions, which will look up the request logger in the context, meaning all log lines will have trace ids set etc.
See https://github.com/StephanHCB/go-autumn-logging/blob/master/convenience.go
We should decide whether we want to use

a wrapper
autumn convenience.go callstyle
autumn object callstyle (same style as zerolog)
and then stick to it across our codebase.

Originally posted by @Jumpy-Squirrel in https://github.com/eurofurence/reg-room-service/pull/37#discussion_r1285247350

Just to document the decision:
We picked autumn convenience.go callstyle.
For an example, see the database implementation on mainline.

authors: Jumpy-Squirrel Noroth

repo: eurofurence/reg-room-service


text:
uploading gif files is not possible

Evanca, thank you for this awesome template. I enjoy it a lot.
However, I could not add .gif files to the index page. I added that file to the images folder and gave the path in the index file, still it did not show up, while there is no any problem with .png or .jpg file types.
PS If I did anything wrong, please apologize me, I am a newbie here.

Hi @orkhan-amrullayev! Have you managed to add your gif? I have tried to show a gif file on the main page and on my end it is working well. I have used the following markdown to show animated image:
<img src="https://media.giphy.com/media/MGdfeiKtEiEPS/giphy.gif?raw=true"/>

Hi @evanca! Thank you for your attention. It was my fault, after correcting my code, it worked smoothly. Thanks!

authors: evanca orkhan-amrullayev

repo: evanca/quick-portfolio

license: Unlicense


text:
🛑 www.actionherojs.com is down

In 656c55e, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 6b92db9.

repo: evantahler/upptime


text:
Document: Du musst gar keinen Zähler eintragen, der wird automatisch von der WB genommen!

@7tobias Deine Alfen wird voll unterstützt. Du musst gar keinen Zähler eintragen, der wird automatisch von der WB genommen!
Originally posted by @andig in https://github.com/evcc-io/evcc/discussions/3392#discussioncomment-2821998

@andig   mir ist nicht ganz klar, wo hier die Doku aktualisiert werden soll. In  https://docs.evcc.io/docs/reference/configuration/meters  ist der Umstand ganz klar beschrieben.

Danke, dann erledigt 👍🏻

repo: evcc-io/docs


text:
Add support for throw expressions

These should pretty much transfer over unchanged, with the exception that in in CoffeeScript throw may be used in expression contexts, like this:
doSomething() or throw new Error('NOPE')

This should probably turn into something like this:
doSomething() || (function(){ throw new Error('NOPE'); })();

Available as of v1.8.0.

repo: eventualbuddha/decaffeinate

license: mit


text:
nginx-letsencypt cannot start (can't write to the '/etc/nginx/certs' directory)

When making a fresh installation of the proxy (clone, create .env, start), the nginx-letsencrypt does not start with the following repeating message in logs:
Warning: '/etc/nginx/certs' does not appear to be a mounted volume.
Error: can't write to the '/etc/nginx/certs' directory !
Check that '/etc/nginx/certs' directory is export as a writable volume.

However, there is a ./nginx-data/certs directory created. Even if I change its mode to 0777 - still the same. I have even tried commenting out the volume maps from the docker-compose.yml so it just uses the in-container directory, but no luck.
Do you have the same issue? Any suggestions?
Docker v1.13.1

Upgrading the Docker to 19.03 solved the issue. Similar problem: https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/issues/381#issuecomment-390419964
Used this docs to upgrade.


text:
Fix SDK backwards compatibility

Why
We previously changed the interface for disabling relay, but the change was not backwards compatible.
How
Made sure that both intercept !== false and relay !== false holds before overriding the HTTP requests.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: adamisntdead shanecurran

repo: evervault/evervault-node


text:
Setting permissions no longer works with chmod method

I've been using capifony to deploy an application to a mac mini running OSX and it worked beautifully. I recently updated capifony to 2.4.2 and the deploy now fails with this error message:
sh: getfacl: command not found

On OSX only the chmod +a method is supported and the getfacl and setfacl commands are not available.
I found this in lib/symfony2/deploy.rb on lines 45 to 51:
# ...snip...
if is_owner && permission_method != :chown
  has_facl = (capture "getfacl -p #{dir} | grep #{webserver_user} | wc -l").chomp != "0"
  if (!has_facl)
    methods[permission_method].each do |cmd|
      try_sudo sprintf(cmd, dir)
    end
end
# ...snip...

It seems that the getfacl command is triggered, even if it is not configured as the permission method. And this is what causing the error.
Until this is fixed, I downgraded capifony to v2.4.0 which does not fail.

+1

authors: DemonTPx JordyMoos

repo: everzet/capifony


text:
Log only errors

How can I configure the logger so, only errors are logged?
Honza

Disable everything except errors.
const logger = createLogger({
  level: {
    prevState: false,
    action: false,
    nextState: false,
    error: `error`,
  }
});

@evgenyrodionov Hi, with version "redux-logger": "3.0.6" this doesn't seems to work anymore
I've also tried:
const logger = createLogger({
      level: {
        prevState: () => false,
        action: () => false,
        nextState: () => false,
        error: () => 'error',
      },
    })

It is strange. Open separate issue

authors: evgenyrodionov guilhermebruzzi janodvarko theaqua

repo: evgenyrodionov/redux-logger


text:
feature want: 可以编辑当前的TODO List

rt

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

authors: endyul ffaady


text:
Some date types returned by Snowflake are interpreted as strings in Safari

Bug Description
Dates returned by the date_trunc function in Snowflake are interpreted by Evidence as strings. This only happens in Safari - other browsers correctly infer that the column is a date.
Severity

[x] Medium - I'm able to use Evidence, but a feature I need to use is not working

This wasn't as straightforward as I had expected. It turns out that these dates were not passing through the db-commons date inference logic as I expected. They were being passed through the inferColumnTypes module, which should only appear in cases where we are missing "evidence types" for columns.
I am wondering if this might have to do with the new reactivity in components - @mcrascal @ud3sh, could the evidence types somehow get dropped in a situation where the code is being re-run reactively?
A bandaid fix would be to add to the date inference logic in inferColumnTypes (confirmed that this approach works), but it wouldn't solve the problem of evidence types getting re-assigned/dropped.

Fixed by #539

repo: evidence-dev/evidence


text:
How to pop up Push Notification when app is killed? (iOS)

What version of RN and react-native-fcm are you running? RN 48 FB 9.6.2
What device are you using? (e.g iOS9 emulator, Android 6 device)? iOS11 iPhone SE
Is your app running in foreground, background or not running?

I am trying to pop up Push Notification when I get a message from my server when the app is killed. Below code is what I tried, but it doesn't pop up the Notification even if the event is triggered. Instead, when I open the app, it vibrate continuously. (I saw that you mentioned not to use the FCM.presentLocalNotification inside the event, but I have no idea how to pop up the notification except here when I get a message )
export function registerKilledListener(){
  // these callback will be triggered even when app is killed
  FCM.on(FCMEvent.Notification, async (notif) => {
    console.log('app is killed1');

    FCM.presentLocalNotification({
      vibrate: 500,
      title: 'Hello',
      body: 'Test Notification',
      big_text: 'i am large',
      priority: "high",
      sound: "bell.mp3",
      large_icon: "https://image.freepik.com/free-icon/small-boy-cartoon_318-38077.jpg",
      show_in_foreground: true,
      number: 10
    });

    AsyncStorage.setItem('lastNotification', JSON.stringify(notif));
  });
}

if you manually kill the app, the notification won't wake up the app. system design
you need to add content_available when you push your notification to wake app. check documentation
you can just use FCM's notification object for iOS to show notification

authors: KwangsubAhn evollu

repo: evollu/react-native-fcm


text:
Update sbt to 1.9.4

About this PR
📦 Updates org.scala-sbt:sbt from 1.8.3 to 1.9.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #243.

repo: evolution-gaming/cats-helper


text:
Update scala-library to 2.13.13

About this PR
📦 Updates org.scala-lang:scala-library from 2.13.12 to 2.13.13
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (2.13.12).
You might want to review and update them manually.
.github/workflows/ci.yml

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #280.


text:
Bet way to 'hold' package version

I see that pinning is an option but there doesnt appear to be a parameter for specific version. What's the best way to make sure a package retains it's version?
Thanks!

Would be interested, too. Because in the readme it says:
apt::hold

This define was removed. Simply use an apt::pin with priority => 1001 for the same functionality.

So I went with the following for my package:
  apt::pin { 'hold-kubelet':     packages => 'kubelet',     version  => '1.23.3-00',     priority => 1001,   }
But if I run apt-mark showhold on the server, nothing is shown. But after running apt-mark hold kubelet. Could somebody explain what I did wrong or is this a bug?

Okay, did some research. I didn't know that pin exists.
So apparently you can do both ways to hold / pin the version of a package.
With the hold, by using the mark keyword:
package { 'package_name':   ensure => '1.0.0',   mark => 'hold', }
Here apt-mark showhold yields that the package is on hold.
Or you go with the pin approach:
apt::pin { 'hold-package_name':   packages => 'package_name',   version  => '1.0.0',   priority => 1001, }
Personally I am using from now on the pin option, because this sound like the more robust way.

authors: brosev premar

repo: evolvingweb/puppet-apt


text:
new tax value for ukrainian embassy

New tax value for ukrainian embassy. Confirmed by embassy.

@alexrolls Дякую!

authors: alexrolls oleksiikyrychenko


text:
Increasing memory usage in Core

Describe the bug
Core occupies memory until eventually taking all memory available.
To Reproduce
Steps to reproduce the behavior:

Run CompreFace (ArcFace GPU) in WSL2.
Consume the API for 4-5h (sometimes less).

Expected behavior
Continuous availability.
Desktop (please complete the following information):

OS: Windows 10
WSL2: Ubuntu 22.04
Nvidia Geforce GTX 1060
Nvidia Driver 516.94
CUDA 11.7
Docker 20.10.12

Additional context
Core occupies memory until eventually taking all memory available. Tried increasing available memory, but even 23GB (set via .wslconf) wasn't enough.
I'm running the ArcFace GPU custom build in Ubuntu 22.04 (WSL2 in Windows 10), but the same behavior happened in Ubuntu 20.04 (also in WSL2). Even tried using Docker Desktop, but the issue persists. I have less than 1K faces in the database now.
Tried to reduce memory allocated to JAVA (api and admin) to as low as 1GB for each, but the result was the same.
My temporary solution is to restart the container every 3 hours, but I can't keep doing it forever.

I created a critical bug for this. We will look into it.

I am also having the same problem.
The Core will use all the available memory until it crashes the instance.

Just did a whole change in the setup, and the RAM issue still persists.
My current setup is the following:

OS: Ubuntu 20.04
Nvidia Geforce GTX 1060 (6GB)
32GB RAM
Nvidia Driver 530.30
CUDA 11.7
Docker 23.0.1

Now I also have a new issue, which might be worth mentioning, as it could be related:
When I was using Windows/WSL2, I was running the same image (SubCenter-ArcFace-r100-gpu), but could keep the default configuration of 2 processes in the .env file. Now in Ubuntu it will crash the Core after a few requests as it's not possible to run 2 uwsgi in the gpu, as it takes up to 4016MB of VRAM. Still don't know how to explain this behavior, as I expected it would run even better in Ubuntu, not having the load of Windows applications competing for GPU.

Another update that might be useful. I was able to run with 2 processes, but only if I limit the size of the images I send in the recognition endpoint. In this case, each uwsgi instance consumes 2694MiB of VRAM steadly (checked via nvidia-smi).

@evandromoura @GustavoDenobi
Could you pull images again and test again?
docker compose pull
On 2 March, we released CompreFace with ARM support. To make CompreFace support ARM we had to update some libraries.
I checked - the old version of CompreFace doesn't have such a problem.
So we rolled back this release.
Still, this ticket was created on 27 February, but I want to ensure the problem is still reproducible on your machines.
As it doesn't reproduce on my machine anymore.

Just started testing. Still too soon to say something about the RAM memory thing, but still can't run 2 processes.
I'm sending images with 480x720 (yes, portrait format). Hitting the recognition endpoint with frames without faces, the uwsgi VRAM usage go to something like 2240MiB. The first time I send a image with face, one of the instances go to 3084MiB. The second time makes it crash, (seems obvious to me that it fills the VRAM), and then the instance that couldn't find enough memory starts triggering the following message:
"Error during synchronization between servers: [500 INTERNAL SERVER ERROR] during [POST] to [http://compreface-core:3000/find_faces] [FacesFeignClient#findFaces(MultipartFile,Integer,Double,String)]: [{"message":"PluginError: insightface.Calculator@arcface-r100-msfdrop75 error - simple_bind error. Arguments:\ndata: (1, 3, 112, 112)\nTraceback (most recent call last):\n  File "../src/storage/./pooled_storage_manager.h", line 160\nMXNetError: cudaMalloc retry failed: out of memory"}]"
I'd be ok with not being able to run the container in my current GPU due to lack of memory, but given that I was able to run it steadly for days just 2 weeks ago with no issues, sending even bigger images, I believe it's a problem somewhere else.

Just checked that the insightface version used in Core is a bit old (0.1.5 -> 0.7.2). Tried to update it but it broke some other dependencies.

I'm having a similar issue running the following:
i7-1165G7 16GB RAM 500GB NVME
RTX2060 6GB RAM
Ubuntu 22.04
Docker 23.0.1
Driver Version: 525.85.05
CUDA Version: 12.0
running the SubCenter-ArcFace-R100-gpu maxes out the GPU RAM very quickly on my box. The process of even uploading 2-3 images is sufficient which then crashes the the core container. Unless I then kill the container the GPU RAM never subsides. I have done a docker compose pull and the issue remains

I'm sorry for not getting back to you sooner. I did a lot of tests, and here are the results:

I didn't find out why memory consumption is increasing. But it is reproducible in all CompreFace versions, and there is a limit.
In the 1.0.0 version, the initial and max memory consumption is less than in 1.1.0. This is why there is a possibility to run two processes on 8Gb GPU. But the main idea - it's not because there is a memory leak but because in 1.0.0 version initial memory, consumption is less.
Memory consumption increased in 1.0.1 version. The only significant change with 1.0.0 is updating CUDA and mxnet.
We can't revert it, as we updated them to support Nvidia 30xx GPUs.
I tried to update them, but the problem still reproduces.
So, what I can suggest:
@GustavoDenobi replace in your .env file CORE_VERSION=1.1.0-arcface-r100-gpu to CORE_VERSION=1.0.0-arcface-r100-gpu. 1.0.0 version of compreface-core should work fine with 1.1.0 version of other CompreFace containers. The only limitation is that you won't be able to use the 'face pose' plugin.
@arakasi55  replace in your .env file  uwsgi_processes=2 to uwsgi_processes=1. Your GPU can't run two processes with such a big neural network. You can continue using 1.1.0 version, as in my tests, it didn't use more than 4.2Gb per process.

In our plans, we won't try to optimize mxnet version. It looks like mxnet is dead. We need to migrate to another library. It makes sense to spend time optimizing the new library.

Thanks for the testing and suggestion, will update the env file and report back.

So far so good after chancing the max processes to 1. GPU RAM sits consistently at 4.072GiB
Thanks again

What are the implications of setting uwsgi_processes=1? Does it result in poorer performance? Is it only able to process half as many images (in a given period of time) as it would with 2 processes?

In short - yes, you can expect this.
But in reality, it's not so simple. If one process can load your GPU 100%, then adding a new process won't increase performance.
Also, there may be other bottlenecks in the system.
You can benckmark it on your system with 1.0.0-arcface-r100-gpu version, and see the difference.

I have the same problem with mobile-net gpu build . I am using docker desktop in windows 10 wsl
i did some testing with 1.1.0 core and 3 uwsgi processes:

jpgs 2592x1944 (with and without faces) were sent 4 times per second from 3 sources. it didn't leak much (200 mb in 30 minutes)

2 jpg sources 2592x1944 and 1 source 1920x1080 4 times per second were sent to compreface. this triggered a reactive memory leak. about 100 mb per minute

the amount of gpu memory in both tests kept a stable value
core 1.0.0 does not have these problems and consumes less ram/gpu memory. if I use it, will I not lose the quality of detection and recognition in comparison with 1.1.0?

Do I understand correctly:

You have RAM leaks, not GPU memory leaks?
There are no such leaks in 1.0.0?

Answering your question: yes, you can use 1.0.0 version. It has the same quality of detection and recognition.

Do I understand correctly:
1. You have RAM leaks, not GPU memory leaks?

2. There are no such leaks in 1.0.0?

Answering your question: yes, you can use 1.0.0 version. It has the same quality of detection and recognition.

yes
yes

I'm sorry for not getting back to you sooner.
We investigated memory leaks and found several causes. We fixed almost all of them. One case we didn't fix for now - is if you send images with different resolutions in MobileNet or Arcface, but it looks like it's not your case.
We will release them with a new release. I hope your case will be fixed.

Now that the exadel/compreface-core:1.2.0-arcface-r100-gpu version is released, has the oom problem been fixed?

This seems related to the OP; except the leak appears to be much slower.

I didn't find out why memory consumption is increasing. But it is reproducible in all CompreFace versions, and there is a limit.

I read this as saying there is a limit to how much RAM Compreface will consume. Figured I'd allocated 64GB of RAM to see what the limit is. Container has been running for 11 days and Compreface has commandeered approximately 29GB of RAM. On my setup it seems to be taking ~2.5GB of RAM per day. I expect the container to crash around day 24.
I have two faces. One with 27 images the other with 48 images. Using the API via Frigate and Double Take.
CORE_VERSION 1.2.0-arcface-r100-gpu
Proxmox-VE 8.1.0 (kernel 6.5.11-7-pve)
PVE-Manager 8.1.3
Debian 12 LXC
Docker 24.0.7
Driver Version: 535.146.02
CUDA Version: 12.2
x2 Xeon E5-2660v4
RTX 4060 8GB
Quadro P2000 5GB

Thanks to the last release, I no longer need to restart the core every 3h. Thanks a lot!
But the remaining memory issue is still impacting in my use case.
To optimize resource usage, I perform movement detection and crop only the regions of interest.
But due to the memory leak that happens when sending images with different sizes, I can't use this strategy.

repo: exadel-inc/CompreFace


text:
🐞 Generating and deploying multi version documentation fails

Summary
Generating and deploying multi version documentation does not work properly in all scenarios and workflows.
Reproducing the Issue
Scenario 1:

Re-run a workflow which was run successfully for a push on master/main

Scenario 2:

Run CI-CD workflow (triggered by tag push)

Expected Behavior
Entire multi version documentation gets built and deployed to GitHub pages.
Actual Behavior
Documentation build/workflow fails.
Root Cause (optional)
No clear single root cause identified yet.
Leads
There are two major issues which have been identified so far:

The docs build expects a setup/structure which causes a broken rendering of the API docs, otherwise it fails/tmp/tmpywesr85d/worktrees/worktree_source/doc/api.rst:4:toctree contains reference to nonexisting document 'api/exasol_bucketfs_utils_python'

The sgpg tool expects different parameters depending if a tag or branch is used as source, therefore the unparamerized
github workflow won't work properly in all cases.

Related Issues (optional)

https://github.com/exasol/bucketfs-python/issues/2

This bug is obsolete, because we are not using sgpg anymore.

authors: Nicoretti tkilias

repo: exasol/bucketfs-python


text:
Exposing some more functions from excalidraw package?

This is more like request for comments.
I've been developing an unofficial util excalidraw-animate, and now it's migrating to using the package. Previously, it was using git submodule to reuse some functions. PR 👉  https://github.com/dai-shi/excalidraw-animate/pull/16
Now, from my perspective, it would be nice if some functions are exposed from packages.
getFreeDrawSvgPath (too specific to my use case)
loadFromBlob
loadLibraryFromBlob
loadScene (too specific to my use case)

These are used outside React, so it's more for the former @excalidraw/utils.
cc @ad1992

We can expose getFreeDrawSvgPath, loadFromBlob and loadLibraryFromBlob , but loadScene is specific to excalidraw-app as it imports from backend hence that would need to be implemented in consumer.
cc @dwelle

We can expose getFreeDrawSvgPath, loadFromBlob and loadLibraryFromBlob , but loadScene is specific to excalidraw-app as it imports from backend hence that would need to be implemented in consumer.

Yes

authors: ad1992 dai-shi dwelle

repo: excalidraw/excalidraw


text:
fix: correctly resolve the package version

The property name is VITE_PKG_VERSION (not PKG_VERSION)
Resolves #7984

Supersede https://github.com/excalidraw/excalidraw/pull/7919

@ad1992 Would it be possible to cut a new release that includes this tiny fix? Thanks!

authors: ggrossetie jonesbusy


text:
Clearer documentation

Summary
Modified documentation. Separated add rows and splice functions. Added api specs for them.
Test plan
No additional testing needed.

@alubbe Please review this, and comment, if needs to be changed. Restructuring was needed, as rows currently have a lot of functionality now. And added api spec table for separated methods.

thanks!

repo: exceljs/exceljs


text:
change other settings from Chinese-specific servers

Ones I have found:
NTP server is set to cn.pool.ntp.org - could just be set to pool.ntp.org
The apt repository is set to one hosted at a Chinese university. This post has some suggestions about making a new sources.list:
https://askubuntu.com/questions/124017/how-do-i-restore-the-default-repositories

@argentcorvid According to the latest firmware version 1.1.5,
RG35XXPLUS-EN-240712 ntp server is already configured.
$ grep -i ntp /etc/systemd/timesyncd.conf
#NTP=
#FallbackNTP=ntp.ubuntu.com

timesync-status shows us
$ timedatectl timesync-status | grep -i server
Server: 185.125.190.56 (ntp.ubuntu.com)

As for the apt repository, it makes sense to change it. Will update soon.

@argentcorvid Apt's Chinese-specific settings have been changed to English. Checkout latest code.

authors: argentcorvid exdial

repo: exdial/anbernic-apps


text:
Duplication of link URL parsing

We are currently using a duplicated function out of @jupyterlab/rendermime introduced in #13.
The following Private function was copied without modification:
https://github.com/jupyterlab/jupyterlab/blob/2e8677624ed7301d47de703570a14ce3bb8036cf/packages/rendermime/src/renderers.ts#L950
There doesn't seem to be a way to get at that code without copying it out (certainly not intentionally, as it is marked private). It would be nice to stay as close as possible to the default JupyterLab markdown renderer, and these sorts of soft-forks don't feel great. :(
I am not sure if this constitutes an upstream modification though, as we are starting to get at internals of the markdown renderer that are maybe not designed to be gotten at?!
Any advice appreciated!

TBH I'm not too worried, because it's not a huge amount of logic. I equally see your point. Perhaps @bollwyvl has a sense for whether this is worth asking for upstream.

Hah, been there on jupyterlab-deck. There I wish it emitted a signal, as well, as sometimes you want to do something with an anchor click as well.
I think if the renderer is pluggable, that detail should be available in a utils.ts or something. It doesn't seem like a breaking change, so hoisting it could land in 3.x, even. Feature freeze for 4.x is the end of this month.

repo: executablebooks/jupyterlab-mystjs


text:
Add a demo page

The JS markdown-it package has a nice syntax demo page that comes with some pre-defined syntax and also lets you update the syntax manually to see how it behaves. I think it'd be useful if we had a simple page like this once we have the JS parser/renderer in good shape.
cc @rowanc1 who I believe showed off something like this a few months ago 🤔🤔

It is still accessible through the readme, live demo badge. Will continue to integrate the demos through the docs!

This will be throughout the documentation for the new package as well as a standalone page in the docs to show a playground. You will be able to show the preview, ast, and html outputs. See for example:

I will leave this up until we get the stand-alone demo page a bit nicer.

At the next team meeting I think @fwkoch and I can show what we have done with the docs here and have a conversation about where the content should live. I have taken some inspiration from both the jupyterbook and myst-parser pages and improved it with live demos and additional pointers and explanations. Some of this is less specific to mystjs and is likely hitting at a stand-alone repository for the myst-spec, which includes tests for new implementations and the canonical documentation of myst.

I am going to close this, now that the docs page is starting to have many more demos!
See:
https://js.myst.tools/guide/typography

repo: executablebooks/mystjs


text:
:paintbrush: add sidebar directive

We already have a margin directive, this PR adds support for sidebar. I don't know whether we want to advertise this directive for core MyST (it might be better to stick to a reduced set of directives to allow us more control), but JB will certainly need it.
c.f. https://github.com/executablebooks/myst-theme/pull/341

Any possibility that this is an alias for margin? Or can we document what the differences are?

This is in a weird space, and I'd benefit from some input I think.
I don't think we have to implement every directive from JB in MyST if we feel that e.g. a directive was a misstep. However, we probably do need to try and provide compatibility for all of the JB features where possible. I think sidebar might be one such case, but I'm not sure.
If we're not just kicking the can down the road (which this PR does as-is, by implementing but not documenting sidebar), then it's a lot easier to reason about grid layouts than floating layouts. So, in the interest of robustness and simplicity, we drop sidebar in MyST (and in compatibility mode, it's just an alias).
@choldgraf thoughts welcome too.

Ok - looking through the jupyterbook docs, I think these are just divs with classes from the AST perspective, that is: add new directive, but let's not add a new AST node though (and also remove the margin node which isn't working now anyways and is treated as a div). From the AST perspective this is content with style as a placement, not a new type of content node. (alternatively these are types of asides which has different semantic structure and classes?) Thoughts?
We also need to make some changes in the blocks in the theme to allow floating content, when there is a grid, you can't use float and we need to for the sidebar (and the margin). I think we still want to use the grid for placement when it is actually in the margin (for alignment etc. across different themes) and then transition to a right-floating div. I will review what you have already in the theme PR @agoose77.

Ok - looking through the jupyterbook docs, I think these are just divs with classes from the AST perspective, that is: add new directive, but let's not add a new AST node though (and also remove the margin node which isn't working now anyways and is treated as a div). From the AST perspective this is content with style as a placement, not a new type of content node. (alternatively these are types of asides which has different semantic structure and classes?) Thoughts?

Oh, I really like that idea. My feeling is that an aside is semantically important, but I agree that we should probably lean into the aside-ness, rather than margin/sidebar. I'll implement it here, and rework https://github.com/executablebooks/myst-theme/pull/341

Replaced by https://github.com/executablebooks/mystmd/pull/1012

repo: executablebooks/mystmd


text:
Fix: logo image stretching vertically

Reported in #686

it makes sense.
I tried testing, and sphinx is crashing now with weird errors.
I'll try to clean up my environment this afternoon...

I'm gonna merge this so that we can make a pre-release but please ping if it still doesn't work

@choldgraf sorry took me so long, but this indeed fixed it.
thanks again!

authors: PhilipVinc choldgraf

repo: executablebooks/sphinx-book-theme


text:
Stylesheet togglebutton.css not rendered

Describe the bug
The extension is not working out-of-the box as the according CSS file does not get added to the HTML header.
To Reproduce
Follow the instructions in README.md
Environment

Python Version 3.8.5
Package versions: 0.2.2
Operating System: Linux

Additional context
The reason is that the config.html_context is not filled accordingly , probably due to a premature call to app.add_css_file("togglebutton.css").
Adding these lines:
def add_to_context(app, config):
    # Update the global context
    config.html_context.update({"togglebutton_hint": config.togglebutton_hint})

    if not config.html_context["css_files"]:
        config.html_context["css_files"] = []
    config.html_context["css_files"].append('_static/togglebutton.css')

and renaming the file togglebutton.css_t (!?) in the _static folder to the expected file named togglebutton.css fixes the problem.

As a follow up: I read about Sphinx static templates and I can now strike out the *.css_t from the equation. Thus it is not necessary to rename the file, the template engine will do anyway.
It tested with default alabaster theme and sphinx_book_theme under a clean virtual environment, but still cannot get it to run from scratch. I need to add these lines:
if not config.html_context["css_files"]:
        config.html_context["css_files"] = []
config.html_context["css_files"].append('_static/togglebutton.css')

Otherwise the required <head><style>... reference will not be added to the rendered page.
Any help really appreciated.

Hey - sorry for the slow response, am dealing with a newborn baby :-)
That's weird that you don't see the CSS file in the header. It should be added with this line here:
https://github.com/executablebooks/sphinx-togglebutton/blob/master/sphinx_togglebutton/__init__.py#L53
what version of Sphinx are you running?
Also, in case it's helpful, you may also want to check out sphinx-panels (https://sphinx-panels.readthedocs.io/en/latest/#dropdown-usage) which has a similar "dropdown" functionality

No worries and congratulations for your newborn baby :fireworks:
I am using the latest Sphinx version 3.2.1, but it is still not working.
Thanks for pointing me to sphinx-panels, it is working great thus far and covers exactly what I was looking for :+1:

I'm closing this one as it sounds like sphinx-panels has worked out well for you, and I haven't had any reports from others that this isn't working in sphinx-togglebutton. Feel free to re-open or post a new issue if there's still a problem

authors: choldgraf hroemer

repo: executablebooks/sphinx-togglebutton


text:
Turn lucians-luscious-lasagna into a Concept Exercise + fix low-power-embedded-game

Closes #148
Also implemented AbsImpl to allow students to focus solely on tuples

@ErikSchierboom I am no longer able to merge my own nor other contributors' PRs, do you know what's going on?

My understanding is that while a track isn't launched, no reviews are needed before merging. On a live track, PRs should be reviewed by someone with write access besides the submitter before merging. So if Erik changed the merge settings, that'd make sense as to why you can't merge your own. That's pretty odd that you can't merge other PRs. If that just started occurring, it might be related to the work staff did in the last day to give @exercism/cross-track-maintainers write access to most of the track repos.
I'm a member of that team so I can wave your PRs through as needed.

@BNAndras

On a live track, PRs should be reviewed by someone with write access besides the submitter before merging.

Ok, makes sense. But just 2 days ago I was able to merge my own PRs, see https://github.com/exercism/cairo/pull/139 and https://github.com/exercism/cairo/pull/144 :thinking: Maybe there were recent changes to the merge settings.

That's pretty odd that you can't merge other PRs.

Just tried it with https://github.com/exercism/cairo/pull/49 and was able to merge it only if I previously explicitly approved it. It might be faulty memory of mine, but I feel like I was able to merge other people's PRs without explicit approval.

Sounds about right if the staff weren't able to change those track settings before launch. So the issue at hand is that PR reviews are now required before merging, not that you can't merge a PR after a review was done, right? The former is expected behavior, but the latter might be indicative of a bug.

Exactly. I've been in contact with Exercism support, and they explained they'd like all PRs to be reviewed by someone, even PRs from maintainers. The fact I was ever able to merge my own PRs on a live track was actually the problem :sweat_smile:

repo: exercism/cairo


text:
High-scores exercise: personalTopThree and mutating the list

I see most solutions for high-scores doing something like this:
    this.scores.sort { -it }.take(3)

This mutates the instance variable in-place, breaking the validity of the latest() method. What is needed is http://docs.groovy-lang.org/latest/html/groovy-jdk/java/lang/Iterable.html#sort(boolean, groovy.lang.Closure)
    this.scores.sort(false) { -it }.take(3)

I propose to add a new test that: creates an instance, does the top 3 then asks for the latest:
    def "Personal top three does not mutate"() {
        given:
        def hs = new HighScores(scores)
        def top3 = hs.personalTopThree()

        expect:
        hs.latest() == expected

        where:
        scores           || expected
        [40, 20, 10, 30] || 30
    }

If there is interest in this, I'll submit a pull request.

Sounds good to me!

PR #212

authors: amscotti glennj

repo: exercism/groovy


text:
Update links in array introduction

I made some changes to the links in this introduction.  The basic links at the end weren't working for some reason, so I changed them to be more like the links in the Strings introduction.  I kept the MDN attributions at the end because the text was pulled directly from MDN reference site.

@raydancer Thanks for raising this but I have trouble reproducing the problem. All the places that you changed are quotes and the source for the quote is provided in the footnote. I tested the footnote and the link in the footnote on the website https://exercism.org/tracks/javascript/concepts/arrays and it all seems to work fine. :thinking:
Could you clarify this:

The basic links at the end weren't working for some reason

What happened when you went to the page linked there?

You're correct, those links work when you go to the introduction page; however, the links don't work in the sidebar of the exercise editor: https://exercism.org/tracks/javascript/exercises/elyses-enchantments/edit
Is there something that breaks basic quotes when bringing them to the exercise sidebar?  If so, this might affect other introduction pages.
Also, I added inline code text markdown to unshift and splice to match the other sections.

@raydancer I think you mean that they are not linked here, right:

Right.  The URL's are there, but they appear as text, not anchors.  I see that the link markdown was correct, but I don't understand why they didn't appear as links.

I think this may be something @ErikSchierboom would want to look at. I think what you're saying is: in one place of exercise, the links are auto-linked, but in another place they are not. The solution would be to make them autolink on both places, or neither places.

I think this may be something @ErikSchierboom would want to look at. I think what you're saying is: in one place of exercise, the links are auto-linked, but in another place they are not. The solution would be to make them autolink on both places, or neither places.

@raydancer Could you create an issue at exercism/exercism for this?

@raydancer Could you create an issue at exercism/exercism for this?

Done:
https://github.com/exercism/exercism/issues/6522

I feel the better solution here is to wait for the Exercism-wide fix instead of merging this workaround. The links can still be copy and pasted and mainly exist only to provide the sources for the quotes. I am closing the PR.

authors: ErikSchierboom SleeplessByte junedev raydancer

repo: exercism/javascript


text:
added version update and new tests

updated the tests and the version.

I updated the test but didnt update the correct version. it should be up to date now if you would like to double check.

repo: exercism/kotlin


text:
Remove "tests" from template

Removes hardcoding of the word 'tests' from the test template and regenerates hello-world and acronym

LGTM 💯

authors: bmulvihill mhelmetag

repo: exercism/xcrystal


text:
Make bob example lispier

Likely using cond and/or if forms.

You mean instead of case? I'd leave it as-is. One of the really cool things about the LFE dialect of Lisp is its Erlang inheritance; case can be used quite elegantly in LFE (it's also one of the most prevalent conditionals in Erlang, so its appearance would be familiar to those coming to LFE from Erlang).

👍

authors: oubiwann yurrriq

repo: exercism/xlfe


text:
Binary problem.

I wrote several solutions - which do people think should be the 'official' one? Or maybe we leave all of them in the example file? But even in that case one should be left as the one not commented out.

http://lisptips.com/post/44261316742/how-do-i-convert-an-integer-to-a-list-of-bits

I thought I read somewhere that the example files aren't meant to be "canonical". I've been thinking of them as "meta-tests" in the sense that, if we change the testing suite, the example file will help us make sure we're still doing something reasonable. But I do see the case that making them into "good" examples would be useful for people contributing future exercises.

I always thought of the example file to be "a solution" that one could look at if one got stuck. But now I don't know where the user could actually see this example file... I don't seem to get them when I do exercism fetch.
Thanks for the link - I never remember all the ash and logand type functions - my brain never seems to think of them (dumb brain).

The only thing the example file is used for at the moment, is as a sanity check for the test suite. It would be a shame to have an unsolvable test suite. People could technically go look at the solution in the github repo, but I doubt that many do.

authors: kytrinyx verdammelt wobh

repo: exercism/xlisp


text:
Add generator for "say"

The exercise say should use generated tests (#396).
Canonical data for this exercise has already been created in exercism/x-common and can be viewed here.
Say does not currently use bookkeeping, so you will need to add a version file at exercises/say/.meta/.version and add the following to exercises/say/example.rb:
module BookKeeping
  VERSION = 1
end

To generate tests you will need to create a generator at lib/say_cases.rb and a template at exercises/say/example.tt.
All generators currently adhere to a common public interface, and must define the following three methods:

test_name - Returns the name of the test (i.e test_one_equals_one)
workload - Returns the main syntax for the test. This will vary depending on the test generator and its underlying implementation
skipped - Returns skip syntax (i.e. skip or # skip)

The wordy exercise can be used as an example while building this generator:

Canonical Data
Tests
Template
Generator

For additional information on generated tests, consult the Generated Test Suites section of the README.
As always, if you get stuck, let us know and we'll be happy to help! :smile:

I'm working on this now. I'm new to generated tests of this sort, so I'll probably be back with questions.

Once I've built the generator, should I generate a new test for the PR?

Yes, that will serve as a proof that the generator is working.

Ok sounds good. I've generated a new test, and then I went back and set the version for the generator to 1.

authors: definemethod kotp tommyschaefer

repo: exercism/xruby


text:
Add hints to hamming exercise

#220 add HINTS.md to hamming exercise.
I tried to be as close as possible to the hints for Either. Now is this good or bad?
What about the other exercises that use Option? Perhaps hints for the first one is enough?

Once again, great hints. I think only having the hints for the first one is good enough.

repo: exercism/xscala


text:
Updating JNI code for ProofMapIndex. [ECR-3321]

Overview
JNI code adapted to new MerkleDb API. Uncommented a set of integration tests.

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

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

Coverage increased (+1.7%) to 79.15% when pulling 80a64d6438b96b36a66dcbd82850727e3fe30e40 on skletsun:pmi-jni-ecr-3321 into 4e304be52004dd078eb8ee3dc37acf48845f395d on exonum:merkledb.

authors: coveralls skletsun

repo: exonum/exonum-java-binding


text:
Consider option to not attach the user's cache to their Results object

Attaching the cache to the Results object is taking up a huge amount of space for remote inference users. Consider the following example from prod:
from edsl import Results

results = Results.pull("bb2cc658-ac99-4daf-9107-af67391cffc6")

results_dct = results.to_dict()

for key, value in results_dct.items():
    value_as_string = str(value)
    print(key, f"{len(value_as_string):,}")

gives me this:
data 2,621,870
survey 1,338
created_columns 2
cache 183,212,709
task_history 1,470,219

Asking because a user's remote inference job failed due to their Results being so long that it exceeded the database driver's limit, and I think a lot of this character count is probably the attached cache.

Ah - thank you! So I'm running our unit tests right now w/ that removed. TBH, I don't recall why I did that - maybe the test will tell! More generally, we should start looking for places where we can do some optimizations. I developed edsl w/o any attention paid to memory or computation but now we need to tighten up as the usage increases.

Resolved in https://github.com/expectedparrot/edsl/pull/1329

authors: johnjosephhorton onmyraedar

repo: expectedparrot/edsl


text:
questions on custom_loss

In frontend.py, could anyone explain a bit for this two line in function custom_loss()?
        cell_y = tf.transpose(cell_x, (0,2,1,3,4))
        cell_grid = tf.tile(tf.concat([cell_x,cell_y], -1), [self.batch_size, 1, 1, self.nb_box, 1])

why to transpose and why to concat this two?

I think this is a mistake, since when the input image isn't square (W != H) then this code crashes.
I changed these lines to:
    cell_x = tf.to_float(tf.reshape(tf.tile(tf.range(GRID_W), [GRID_H]), (1, GRID_H, GRID_W, 1, 1)))
    cell_y = tf.to_float(tf.reshape(tf.tile(tf.range(GRID_W), [GRID_H]), (1, GRID_H, GRID_W, 1, 1)))
    cell_grid = tf.tile(tf.concat([cell_x,cell_y], -1), [BATCH_SIZE, 1, 1, 5, 1])

and it worked.
Moreover, make sure to fix the cv2.resize inputs in "aug_image" method in "BatchGenerator" class.
should be
image = cv2.resize(image, (self.config['IMAGE_W'], self.config['IMAGE_H']))
instead of
image = cv2.resize(image, (self.config['IMAGE_H'], self.config['IMAGE_W']))
I've opened a PR for that

Same issue, looking forward to further solution.

authors: AlucardNosferatu Golbstein rockkingjy


text:
project for the embeddings technical report

Description
This is the project for the technical report. It is a modified version of https://github.com/explosion/spancat-encoders that only has code that we will use for the report.
The only workflow in the project is setup, which for English, Dutch and Spanish downloads the corresponding spaCy models (lg) and also downloads and initialized the fastText vectors.
Other than this it has a train, an evaluate and an unfinished evaluate-unseen command.
It contains an implementation of MultiEmbed, which is the standard embedding version of MultiHashEmbed and is implemented in multiembed.py.
The tables for it are created using token_map.py, which is implemented similar to a spacy cli command. The tables are injected into MultiEmbed in the before_init stage and the callback for it is implemented in set_attr.py.

I get a failure in make-tables. Traceback:
================================ make-tables ================================
Running command: /Users/peter/miniconda3/envs/project-ner_embeddings/bin/python -m scripts.token_map configs/multiembed.cfg tables/anem --min-freq 10 --paths.train corpus/anem-train.spacy --paths.dev corpus/anem-dev.spacy --code scripts/custom_components.py --paths.tables tables
✔ Succesfully loaded pipeline.
Traceback (most recent call last):

  File "/Users/peter/miniconda3/envs/project-ner_embeddings/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,

  File "/Users/peter/miniconda3/envs/project-ner_embeddings/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)

  File "/Users/peter/projects/spacy-projects/benchmarks/ner_embeddings/scripts/token_map.py", line 128, in <module>
    app()

  File "/Users/peter/projects/spacy-projects/benchmarks/ner_embeddings/scripts/token_map.py", line 57, in init_tables_cli
    training = util.registry.resolve(config["training"], schema=ConfigSchemaTraining)

  File "/Users/peter/miniconda3/envs/project-ner_embeddings/lib/python3.8/site-packages/confection/__init__.py", line 728, in resolve
    resolved, _ = cls._make(

  File "/Users/peter/miniconda3/envs/project-ner_embeddings/lib/python3.8/site-packages/confection/__init__.py", line 777, in _make
    filled, _, resolved = cls._fill(

  File "/Users/peter/miniconda3/envs/project-ner_embeddings/lib/python3.8/site-packages/confection/__init__.py", line 898, in _fill
    raise ConfigValidationError(

confection.ConfigValidationError:

Config validation error
before_update   field required
{'dev_corpus': 'corpora.dev', 'train_corpus': 'corpora.train', 'seed': 0, 'gpu_allocator': None, 'dropout': 0.1, 'accumulate_gradient': 1, 'patience': 1600, 'max_epochs': 0, 'max_steps': 20000, 'eval_frequency': 200, 'frozen_components': [], 'annotating_components': [], 'before_to_disk': None, 'batcher': {'@batchers': 'spacy.batch_by_words.v1', 'discard_oversize': False, 'tolerance': 0.2, 'get_length': None, 'size': {'@schedules': 'compounding.v1', 'start': 100, 'stop': 1000, 'compound': 1.001, 't': 0.0}}, 'logger': {'@loggers': 'spacy.ConsoleLogger.v1', 'progress_bar': True}, 'optimizer': {'@optimizers': 'Adam.v1', 'beta1': 0.9, 'beta2': 0.999, 'L2_is_weight_decay': True, 'L2': 0.01, 'grad_clip': 1.0, 'use_averages': False, 'eps': 1e-08, 'learn_rate': 0.001}, 'score_weights': {'ents_f': 1.0, 'ents_p': 0.0, 'ents_r': 0.0, 'ents_per_type': None}}

I think the above issues are related. I attempted to initially run on spacy==3.5.0 and got the traceback, but things run fine on 3.4.0. With that, I'd suggest declaring the spacy_version to be something like >=3.3.0,<3.5.0 - though I'm not sure if that's the best lower bound.

I retried with spacy 3.4 and got a different issue. I think a step that creates the .spacy files is missing. I get to make-tables and then get:
FileNotFoundError: [Errno 2] No such file or directory: 'corpus/anem-train.spacy'

I also don't see a step that would create the files and no step has the .spacy files declared under output. Is there something I'm missing that creates the .spacy files?

I retried with spacy 3.4 and got a different issue. I think a step that creates the .spacy files is missing. I get to make-tables and then get:
FileNotFoundError: [Errno 2] No such file or directory: 'corpus/anem-train.spacy'

I also don't see a step that would create the files and no step has the .spacy files declared under output. Is there something I'm missing that creates the .spacy files?

Nevermind, it's in the instructions on how to get the datasets. Let me read better, first :)

I retried with spacy 3.4 and got a different issue. I think a step that creates the .spacy files is missing. I get to make-tables and then get:
FileNotFoundError: [Errno 2] No such file or directory: 'corpus/anem-train.spacy'

I also don't see a step that would create the files and no step has the .spacy files declared under output. Is there something I'm missing that creates the .spacy files?

Ah right, you have to use the freshly merged https://github.com/explosion/projects/tree/v3/benchmarks/span-labeling-datasets to generate the .spacy files.

I got to the train step and was able to train a model. I'm not on my GPU machine right now to be able to replicate all of the models being trained, but I will do that later.
My biggest piece of feedback is that we need to make sure the unconventional asset download process can be done without error. It would be nice if the whole thing was automated. Even if you're running shell commands, you can have a python script that calls out to subprocess.run that runs those commands instead of having a user have to type those in manually.
I also made a PR to the datasets repo to include pandas in the requirements. It failed for me at that step when I ran spacy project run anem.

Oh, we should use https://github.com/explosion/projects/tree/v3/benchmarks/span-labeling-datasets instead of https://github.com/explosion/span-labeling-datasets? Because the latter is referenced in the readme/project.yml.

authors: kadarakos pmbaumgartner

repo: explosion/projects


text:
BUG: Weasel DVC command error "run"

Hi, I'm quite new to weasel and ran into this basic problem and haven't been able to figure out a way to solve it.
Expected Behaviour
With running weasel dvc I can automatically create and maintain a dvc.yml from my project.yml.
Current Behaviour
When running weasel dvc I get an error message that "run" is an invalid command choice and no dvc.yml is created.
$ weasel dvc
⚠ No workflow specified for DVC pipeline. Using the first workflow
defined in project.yml: 'all'
ERROR: argument command: invalid choice: 'run' (choose from 'add', 'artifacts', 'cache', 'check-ignore', 'checkout', 'commit', 'completion', 'config', 'daemon', 'dag', 'data',

Steps to reproduce
I ran into this issue with both the templates tagger_parser_ud and textcat_demo as well as the tutorial ner_fashion_brands.
Set-up new project

mkdir new_folder && cd new_folder
python -m venv .venv
source .venv/bin/activate
pip install weasel && pip install dvc
git init && dvc init

Download and set-up template
6. weasel clone pipelines/tagger_parser_ud
7. cd tagger_parser_ud
8. weasel assets
Set-up weasel from project.yml
9. weasel dvc
Environment

WSL 2 Ubuntu
Python 3.10.12
weasel 0.3.4
dvc 3.48.1
git version 2.34.1

Detailed Description
It seems to me like under the hood a dvc run command is triggered, which causes an issue. It already tried to check the code weasel/cli/dvc.py, but couldn't find a run command there or in utils.

Hi! Thanks for the extensive report and way of reproducing. I can reproduce this on my own system as well.
The DVC integration is in a dire need of updating, as this was written before dvc run was deprecated for its 3.0.0 release. Weasel still uses this here.
If I downgrade dvc to version 2.58.2 this error goes away, though I'm running into other issues. We'll have to spend some time looking into this properly.

repo: explosion/weasel


text:
Make EAS cli auto terminate once build is submitted

Build/Submit details page URL
No response
Summary
When submitting a build in non-interactive mode (cloud build CI / CD), the cli tool stays running until the build is complete, these builds can take a while, so is there a parameter to make the build tool auto exit once the build is submitted? The command the cli runs is:
eas build --auto-submit --non-interactive
Managed or bare?
managed
Environment
eas build --auto-submit --non-interactive
Error output
No error, my cloud builder just times out and I don't want it to be running for the whole build, only the submission.
Reproducible demo or steps to reproduce from a blank project
Any applicable expo project submitted using a CI CD service such as cloud build.

Just run the build with --no-wait:
eas build --auto-submit --non-interactive --no-wait

Cheers!

authors: dsokal felixlucien

repo: expo/eas-cli


text:
Expose chunkSize, add various improvements

Exponent.chunkSize can be used
Update URL to https://expo.io
Check brackets of exponentPushToken

I can go ahead and update docs with code example for > 100 tokens as well

repo: exponent/exponent-server-sdk-node


text:
Migration failing if project already have migration setup using typeorm

Description
We are already using typeorm for migration, so getting following issue while using the package
(node:8882) UnhandledPromiseRejectionWarning: Error: Migration failed. Reason: Hashes don't match for migrations '0_create-migrations-table.sql,1-init.sql,2-add-db-functions-agg.sql,3-add-db-functions-ind.sql,4-add-db-functions-sessions.sql,5-hotfix-update-constraints.sql'.
This means that the scripts have changed since it was applied.
at /Users/arunrajkumar/Documents/code/ATOACore/node_modules/postgres-migrations/dist/migrate.js:100:27
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at /Users/arunrajkumar/Documents/code/ATOACore/node_modules/postgres-migrations/dist/with-lock.js:25:28
at /Users/arunrajkumar/Documents/code/ATOACore/node_modules/postgres-migrations/dist/with-connection.js:16:28
at applyMigrations (/Users/arunrajkumar/Documents/code/ATOACore/node_modules/@acpr/rate-limit-postgresql/dist/index.cjs:78:3)
(Use node --trace-warnings ... to show where the warning was created)
(node:8882) UnhandledPromiseRejectionWarning: 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:8882) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Library version
1.3.1
Node version
14.9.2
Typescript version (if you are using it)
4.5.5
Module system
ESM

https://github.com/express-rate-limit/rate-limit-postgresql/pull/14 , handle the migration in your base project


text:
How to get ipv6 address of client from req object

I am using req.ip to get the client ip address and it is returning ::ffff:192.168.2.110 but i think this is ipv4 address. I wanted to retrieve the ipv6 address of a client. Is it possible get it from req object?

Hi @ksushilmaurya, the req.ip property is just the IP coming from the Node.js req.connection.remoteAddress core functionality in most cases. The address you provided, ::ffff:192.168.2.110 is an IPv4 address that has been mapped into the IPv6 namespace (typically done from a dual stack network listening on IPv4.
The way you can get an IPv6 address is better asked over in the Node.js core repository (since you are most likely using the Node.js core HTTP server), but it boils down to the following two steps:

Start your server listening on the IPv6 network stack (typically app.listen('::'); see Node.js documentation for more https://nodejs.org/dist/latest-v6.x/docs/api/http.html#http_server_listen_port_hostname_backlog_callback).
Make a request to your server using the IPv6 network, not the IPv4 network.

authors: dougwilson ksushilmaurya

repo: expressjs/express


text:
Could we use different IncomingMessage implement in express?

In application.js
app.listen = function listen() {
  var server = http.createServer(this);
  return server.listen.apply(server, arguments);
};

Node http allow us use different IncomingMessage and ServerResponse implement
https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener
But express just ignore this useful opts
app.listen = function listen() {
  var server = http.createServer({/*my implement*/},this);
  return server.listen.apply(server, arguments);
};

Could be better 😋

Hi @iamwwc , the app.listen is just a helper. Just don't use it at all and you can create your http server with any options you want. Example:
var app = express();

// ...

server = http.createServer({/*my implement*/}, app);
server.listen(3000);

authors: dougwilson iamwwc


text:
add create flags to each CRDs resources for a more fine-grained control

In our use case, we strictly disallow external secrets to be created in the cluster scope.
Add flags to each of the CRDs so that we can skip the creation of all cluster-scoped CRDs during the deployment.
Example:
{{- if and (.Values.installCRDs) (.Values.crds.createClusterExternalSecret) }}
(...content omitted)
{{- end }}

Creating a CRD and denying access to a CRD are two different things. I think your requirement should be implemented with RBAC and/or a policy engine like Kyverno or OPA/Gatekeeper. The controllers rely on that resource to exist and won't be able to come up.

Creating a CRD and denying access to a CRD are two different things. I think your requirement should be implemented with RBAC and/or a policy engine like Kyverno or OPA/Gatekeeper. The controllers rely on that resource to exist and won't be able to come up.

With the new flags (processClusterExternalSecret and processClusterStore) added in https://github.com/external-secrets/external-secrets/pull/800, It is possible that I can spin up the operator without processing ClusterExternalSecret and ClusterStore so I can avoid creating ClusterExternalSecret and ClusterStore CRDs and have the operator running properly.
However, you can argue that ExternalSecret and SecretStore are the basic CRDs that must exist but I just added the controls here to cover them anyway. If needed, I can skip adding control flags to those two resources since I only want to avoid creating CRDs that are should not be used at all in the cluster.

Thanks for the quick response! I see now, sure then go ahead and remove the control flags for the namespaced resources. :+1:
Other than that LGTM :)

Thanks for the quick response! I see now, sure then go ahead and remove the control flags for the namespaced resources. 👍 Other than that LGTM :)

Updated. Seems working in my local :D

/merge

authors: kinyat moolen

repo: external-secrets/external-secrets


text:
feat: Implement add a “align” parameter for ui.inline

Fixes 1535

Progress

[ ] Should we address this comment? // TODO: Ugly, maybe introduce 'align' prop to ui.inline?
[ ] We probably should rename the alignment parameter of XComponents to justification and update its usages in the codebase
[ ] Add an example project

repo: extreme-sharks/wave


text:
deserialize a std::string_view similar to std::span

Hello, maybe this is already possible and someone can point out how.
This is my opinion, I feel it would be natural to have a std::string_view (a view to a stringlike sequence of const bytes) behave like std::span<const std::byte> (a "view" of a sequence of const bytes). Right now it does not, from what I've tried and read up on.
To illustrate, without going into too much detail on my use case I provide this code:
TEST_CASE("Tag string_view with cbor_tag") {
    auto [data, out]  = zpp::bits::data_out();
    auto [dataIn, in] = zpp::bits::data_in();

    // Data to transfer
    std::string_view s{"This is a string view"};

    // Encode data
    auto result = out(cbor::make_tag(1, s));
    CHECK(!failure(result));

    // Emulate data transfer
    dataIn = data;

    // Decode data (I would like to use string_view as type here, not std::span<const std::byte>)
    cbor::Tag<std::span<const std::byte>> s2;
    result = in(s2);
    CHECK(!failure(result));

    // Check data
    CHECK(1 == s2.first);
    CHECK(s == std::string_view(reinterpret_cast<const char *>(s2.second.data()), s2.second.size()));

    // Check data location is different (it was truly transferred)
    CHECK(s.data() != reinterpret_cast<const char *>(s2.second.data()));
}

I would like to avoid having to write extra layers and casting between them too much. If this is something that is possible to implement/change, I would be happy to help if needed.

I would really like to discourage deserializing into view types of const because this is not necessarily doing what you want - it just makes the view point to the data and is a bit dangerous - this is why it was restricted to span of const byte types only!
By the way - I would love to take a look at what you’re building there if it’s open source.

Hehe I can understand that reasoning. But in my specific case, I fully manage the lifetime of the buffer (and spans of it) where the data I would deserialize/interpret from reside. So the extra copy should not be necessary, but I'm definitely risking shooting myself in the foot.
While I can't go into details on that because it's related to work, I can show something close enough, which I do plan making open source.
I just started and I am still exploring a bit, but I pushed it so you can see:
https://github.com/jkammerland/cbor_tags
see the "usage" section in the readme.
The examples in the "usage" section does not use zpp_bits, because that is still general cbor. I thought zpp_bits (or something like bitsery) could shine as an example for defining your own objects, aka tag (6) in cbor. The standard is very flexible here, you can literally claim any id for your object and define the binary structure as "how zpp_bits would serialize this c++ struct". This could very flexible if your type only travels within a limited system where you could share headers with struct definitions.
I plan to work on this when I have time and try to either use zpp_bits as an example for how you could make your own types. Maybe directly incorporate it with no/"a few" abstractions, to also handle cbor specifics.
Anyway, back to the std::string_view, the reason why I want const bytes, is because it's "necessary" to differentiate text strings and binary strings as a variant when dealing with the MAJOR types. Defaulting to no copy, and then building more safe abstractions on top if necessary. Don't know if it's a good idea, but I'm exploring it.
I tried to hack a bit to make it work, this is the diff on my fork (but not sure if good):
https://github.com/jkammerland/zpp_bits_fork_string_view/commit/b6e1263311c9290de4dc81d45dad8851030e2211

Thanks for the info there, I’m excited to see the progress you make. I think however for this feature request that it’s safer for the larger user base of the library to keep the behavior as it is rather than introducing implicit behaviors that could become footguns.

Sure @eyalz800 I understand. Thanks for taking a look. Please revisit my library in the future when I announce it on reddit or similar :)


text:
It's not working EEEeeeeeeekkk!!!!!

Somehow with the namespace update it's all not working now.
So if you have a script dependent on another script loaded later, it isnt working.
FIX IT!!!!!

Sorte

repo: eyeamaman/Yo


text:
fix: update to eye v3.8.2

fix: update to eye v3.8.2

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

npm package (@latest dist-tag)
GitHub release
v4.8.1

Your semantic-release bot :package::rocket:

repo: eyereasoner/eye-js


text:
Simplify docker-compose setup

What did we change?

Removed Dockerfile, use standard ruby 2.6.6 image
Removed container names and unnecessary external ports from docker-compose
Add entrypoint script to automatically bundle

Why are we doing this?
To make it easier to do local development using docker with this repo.
This is pretty slick now. One command can be used to spin up Zeebe and run specs for the repo:
docker-compose run --rm console rspec

How was it tested?

[ ] Specs
[x] Locally
[ ] Staging

Rebased to show that tests are passing.


text:
explorer.exe broken after installing the thumbnail support

Describe the bug
After installing f3d on windows using the installer (or registering the shell extension), a bad file could segfault f3d and break the explorer completelly until unregistration of the winshellext
https://user-images.githubusercontent.com/3129530/145490946-792006de-fc46-4b64-b133-9623719c2ad5.mp4
System Information:

OS: Windos

fixed by #137


text:
Fix bug in fetch-all

Fetch-all doesn't store the last cursor data, so the results are always
limited to thousands, data fetching is incomplete.

I guess that should be merged and released asap, as data is not fully returned from the db.

repo: fMeow/arangors


text:
typo

https://github.com/faanskit/pyCheckwatt/edit/master/README.md#L13
reteive = retrieve

done

repo: faanskit/pyCheckwatt


text:
Qwik: form loader not loading, unexpected  type error

Hi,
I have this route:
import { component$ } from '@builder.io/qwik';
import type { DocumentHead } from '@builder.io/qwik-city';
import { routeLoader$ } from '@builder.io/qwik-city';
import { Button, Card, Heading, Input } from 'flowbite-qwik';
import { _ } from 'compiled-i18n';
import { useProfileLoader } from '~/lib/route-loader/data/use-profile-loader';
import type { InitialValues } from '@modular-forms/qwik';
import { useForm, valiForm$ } from '@modular-forms/qwik';
import * as v from 'valibot';

export { useProfileLoader };

const ProfileSchema = v.object({
  firstname: v.pipe(v.string(), v.nonEmpty('Please enter your firstname.')),
  name: v.pipe(v.string(), v.nonEmpty('Please enter your family name.')),
});

type ProfileForm = v.InferInput<typeof ProfileSchema>;

export const useFormLoader = routeLoader$<InitialValues<ProfileForm>>(async (requestEvent) => {
  const profile = await requestEvent.resolveValue(useProfileLoader);
  if (!profile) {
    return {
      firstname: 'test',
      name: 'test',
    };
  }
  console.log(profile);
  const { firstname, name } = profile;
  return {
    firstname,
    name,
  };
});

export default component$(() => {
  const [profileForm, { Form, Field }] = useForm<ProfileForm>({
    loader: useFormLoader(),
    validate: valiForm$(ProfileSchema),
  });

  return (
    <Card>
      <div class={'flex flex-col gap-8'}>
        <Heading tag={'h2'}>{_`Your Profile`}</Heading>
        <Form>
          <Field name="firstname">{(field, props) => <Input {...props} type="email" />}</Field>
          <Field name="name">{(field, props) => <Input {...props} type="text" />}</Field>
          <Button type="submit">{_`Save`}</Button>
        </Form>
      </div>
    </Card>
  );
});

Issues

The form is not being populated with initial values, even though the routeLoader correctly logs the data on the server side
 complains about a missing of= attribute that should be the formStore (profileForm), but even when supplying that it complains about mismatched types. Has no effect on missing initial values.

I mainly followed the tutorial on your website since I was away for a while and just returned to working with Qwik and didn't want to run into breaking changes I was not aware of.
I can't find anything that makes this differ much from the example, yet it doesn't work and there are weird type issues that should not (no?) be there. can you see something obvious?
Thanks for having a look
Versions:

qwik@1.9.1
modular-forms@0.28.2
valibot@1.0.0.beta.3

node 22, ts 5.6.2

I replaced the custom Input with regular input but there was no change in behaviour

It looks like value= needs to be set manually, spreading props is not enough. At some point I talked to one of the qwik devs and he suggested that prop spreading might not be such a great idea, but honestly I don't remember the context .. but it had to do with modular forms.
Anyways, when I set value={field.value} the form is correctly populated.
Not sure if this needs to be reflected in the docs:
https://modularforms.dev/qwik/guides/add-fields-to-form

Is this the problem? https://modularforms.dev/qwik/guides/controlled-fields

Well, it might be.
The example I mentioned does use initial values and seems like a "more complex form"  and has no value={field.value}. See bottom of the page: https://modularforms.dev/qwik/guides/validate-your-fields
Is it good it to have 2 way of doing things when one works always and the other might not work based on rules that are only later established in the documentation and are not really transparent (technically, I mean)?
I think it would be a better DX to have field.value separately attached in all cases, established as the default,  then the issue doesn't even come up.

The documentation teaches the library piece by piece, and controlled fields are not necessary in basic cases. That's why the first guides are kept simple and don't include this code. But I will consider your feedback in the long run. Maybe we should change this.

I think the documentation is great, it gets you started very quickly and you did a great job to introduce one thing at a time. Don't get me wrong. But this thing .. I am sure I stumbled over this for the second time now.
As a concrete suggestion I would like to add, that I think it would greatly help to mention this in some sort of infobox as soon as Fields are mentioned with an additional concise description of what makes a form qualify as "complex" and maybe even a short explanation of the underlying technical reasons.
Something like "A complex form is one that uses useFormLoader, implements custom components instead of directly using primitive HTML form elements or ..."
Then it is clear right from the beginning. Right now it is kind of a foot note and over ambitious devs might not even see it. I guess I qualify for this, or maybe its the attention span .. ;)
But yeah, just my experience. You are doing a great job with this library, it's great to use once the pitfalls are overcome and it makes life a lot easier.

authors: fabian-hiller genox

repo: fabian-hiller/modular-forms


text:
fix: jupyter-notebook issue issue-547

Kindly asking for a review - I removed the "python"-language alias which causes #547

Codecov Report

Merging #570 (42f1ac9) into master (471a04d) will decrease coverage by 1.09%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #570      +/-   ##
==========================================
- Coverage   60.28%   59.19%   -1.10%
==========================================
  Files          18       18
  Lines         841      843       +2
  Branches      170      169       -1
==========================================
- Hits          507      499       -8
- Misses        334      344      +10

Impacted Files
Coverage Δ

src/extension.ts
22.47% <0.00%> (+0.24%)
:arrow_up:

src/authextension.ts
42.50% <33.33%> (-2.24%)
:arrow_down:

src/redhatTelemetry.ts
60.86% <55.55%> (-2.77%)
:arrow_down:

src/multimanifestmodule.ts
46.26% <0.00%> (-5.98%)
: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 ad4a33f...42f1ac9. Read the comment docs.

Thanks for the fix, I verified this change and works as expected

Thanks for the merge. :-)


text:
Issue #772: updated module with runtime-specific info

Cleanup + remove notes about tech preview

merged: e42f6eba23e38fc060a4f96b64230f7adcc208a7


text:
import of template fails

I'm trying to import the Launcher template on latest CDK/minishift v3.9.14 but it's throwing an error while parsing the template from here.  See below:
[jupittma@jupittma openshift]$ oc project local-app-test
Now using project "local-app-test" on server "https://192.168.42.155:8443".
[jupittma@jupittma openshift]$ oc create -f https://raw.githubusercontent.com/fabric8-launcher/launcher-openshift-templates/master/openshift/launcher-template.yaml -n openshift
error: error converting YAML to JSON: yaml: line 330: did not find expected key
[jupittma@jupittma openshift]$ oc version
oc v3.9.14
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://192.168.42.155:8443
openshift v3.9.14
kubernetes v1.9.1+a0ce1bc657

Thanks @vap0rtranz, apparently it was an indentation error in the template. Thanks for catching that!

Ah sometimes it's the simplest thing.  Ty!


text:
Navigation on mobile does not show all links

The navigation on mobile devices (tested on Safari and Chrome, iOS) does not show all of the links. I can see the user dropdown, but the other items in the secondary navigation do not appear.
The menu should render in the same as the homepage (logged out).

@mindreeper2420 I'm giving this to you to include in your work to make the app mobile ready/viewable.

closed by PR #1566


text:
Any iOS SDK released?

Pod install failed, too more errors....
CocoaPods could not find compatible versions for pod "PeerTalk":
Or
CocoaPods could not find compatible versions for pod "ComponentKit":
Or
** /xxxxx/Pods/Sonar/xplat/Sonar/SonarWebSocketImpl.cpp:102:8: No member named 'delayedUnsafe' in 'folly::Futurefolly::Unit'  **
..............

Duplicate of #65

authors: priteshrnandgaonkar qokelate

repo: facebook/Sonar


text:
export_exe isn't available by default

Something I ran into last night: prelude//export_exe.bzl is pretty useful, but it's not exported by default, so you have to load() it before you can use it in a BUCK file. Is this intentional, or would a patch to change it be useful? (I guess it would also get attached to native. then, to be used in .bzl files?)

Hm, I think we'd like to move to a world where nothing is exported by default and everything needs to be explicitly loaded. idk if that principle is why this isn't exported and we're a long way off from that.
Note that one thing you can do is use the buildfile.includes config to basically extend the prelude. idk if I like that though because it can be really non-obvious to someone reading a buildfile that that's where the symbols are coming from (idk if the lsp jumps to def for them correctly or not, if it does that could mitigate this a little bit).

Yeah, in my own prelude I go the "explicit import route" for almost everything except some few trivial helpers; the global namespace only has about 5-7 things in it. But I figured since it was likely impractical for right now to make that change, that export_exe could go in. :)
The buildfile.includes thing is interesting; but I agree it probably makes readability worse. At least right now I can just point people to the single load_symbols call I make... So for now I think I'll close this; a single load statement with the normal prelude isn't the end of the world.

authors: cjhopman thoughtpolice


text:
Unset env variables are not properly embedded

Describe the bug
Variables like REACT_APP_FOO are hard-baked into the code if they were present in the environment during build-time. Referencing a variable that did not exist during build time results in rather useless code that cannot be minified:
process.env.REACT_APP_FOO

->
Object({
    NODE_ENV: "production",
    PUBLIC_URL: "",
    WDS_SOCKET_HOST: void 0,
    WDS_SOCKET_PATH: void 0,
    WDS_SOCKET_PORT: void 0
}).REACT_APP_FOO

This will neither cause an error, not is it minified into a constant expression.
Full example further below.
Did you try recovering your dependencies?
Problem is reproducible on a fresh install.
> npm --version: 6.14.4
Which terms did you search for in User Guide?
This behaviour is not documented on
https://create-react-app.dev/docs/adding-custom-environment-variables/
Environment
Environment Info:

  current version of create-react-app: 3.4.1

  [Tested on multiple systems, everything else is irrelevant]

Steps to reproduce
> npx create-react-app test
> cd test
> $EDITOR src/index.js

index.js:
if (process.env.REACT_APP_FOO) {
	console.log('Foo is enabled');
}
else {
	console.log('Foo is disabled');
}

> npm run build
> cat build/static/js/main*.js

main*.js (prettified):
(this.webpackJsonptest = this.webpackJsonptest || []).push([
    [0],
    [function(o, s, e) {
        o.exports = e(1)
    }, function(o, s) {
        Object({
            NODE_ENV: "production",
            PUBLIC_URL: "",
            WDS_SOCKET_HOST: void 0,
            WDS_SOCKET_PATH: void 0,
            WDS_SOCKET_PORT: void 0
        }).REACT_APP_FOO ? console.log("Foo is enabled") : console.log("Foo is disabled")
    }],
    [
        [0, 1]
    ]
]);

Expected behavior

Preferred: the build emits a warning or an error when referencing a missing variable. It's most likely either a typo in the variable name, or a broken build configuration.
Alternatively, the variable is replaced with undefined or void 0 or '' or some other sensible default value.
Alternatively, this behaviour is at least documented with a warning on the corresponding page.

The workaround is to define a default value for every used variable in .env and commit the file, but that doesn't protect against mistyped identifiers in the code.
Actual behavior
See above for actual output. The output contains both '"Foo is enabled"' and "Foo is disabled", even though one of them is dead code.
Reproducible demo
See above.
I am not sure how best to resolve the issue.
Replacing with undefined or '' isn't easy:

It's not a bug in terser - the code could evaluate to something other than undefined if someone sets Object.prototype.REACT_APP_FOO, so terser is not allowed to minify here. Playing around with terser's repl, I was unable to find a different construct for process.env that would allow minification here.
webpack's DefinePlugin does not allow regexps for replacements; substituting REACT_APP_.* is not possible.

Emitting an error isn't easy:

scanning the build output for remaining process.env.REACT_APP_ won't work, and scanning for the whole code snippet above seems really fragile.

This could be solved by moving the replacement logic from DefinePlugin into a custom babel plugin (similar to this one). Considering that cra only supports replacing with strings, and not with arbitrary javascript code, that might work. Is babel guaranteed to be run on every source file, including typescript?
If all else fails, I think it deserves at least a warning in the documentation.

I pushed a repo that is showing this behavior here:
https://github.com/abumalick/react_app_env_variables

@abumalick: That looks like a different issue. I'm not concerned that a list of ENV variables appears in the output - it's likely intended behaviour to account for code like:
let x = process.env;
let foo = x.REACT_APP_FOO;

Those variables shouldn't contain anything sensitive, and I'm sure some code somewhere relies on this working.
What concerns me (and what I consider a bug) is that referencing a variable that wasn't defined does not result in a constant expression. If env vars are used for feature gating, then this will prevent dead code elimination of the gated features.

Ran across this today and it's hugely annoying - i'm trying to include some debug code in a specific build but this bug causes it to still be included if the env var isn't set which is the opposite of the expected behaviour.
I would expect this to "fail safe", it's a potential footgun for devs.

I believe the most pragmatic way to fix this is to create a new eslint rule, similar to no-process-env (docs, source), except with a whitelist of allowed values. Ideally this should warn in dev, but error on production builds.
Implementing that is on my list of things to do when I get bored, but as you can see it hasn't reached the top yet.

Saw the same thing, I think a note in documentation is a good start
In my case, the code made it into the browser code and then threw a type error because process.env.REACT_APP_VAR didn't exist. Not my favorite javascript feature

A solution

create a "cra-env-defaults" in the package.json
create a new shell utility, say cra-cross-env that reads "cra-env-defaults" sets those environment variables or according to its arguments

Can be used in package.json scripts
"build:author": "npx cross-env REACT_APP_BUILD_MODE='author' react-scripts build",

I already use cross-env in this way

requires careful documentation
no changes to create-react-app code
backwards compatible

I think this also affects 3rd party libraries, e.g. https://github.com/styled-components/styled-components/issues/3166

Here's some recent activity for you, you bot! 😆

I also had this problem today.
The final solution is pretty much like @johnlobster did.
But simply adding a default REACT_APP_FOO in .env, so that DefinePlugin could replace the variable as constant.
echo "REACT_APP_FOO=false" >> .env
In such case, the if statement should rewrite as
if (process.env.REACT_APP_FOO === 'true') {
Details

TerserPlugin's Dead Code Elimination could only eliminate simple code block:

        const foo = 'true';
        if (foo !== 'true')
          console.log('This code should be removed');

But not for this:
        const foo = {};
        foo.bar = 'true';
        if (foo.bar !== 'true')
          console.log('This code will NOT be removed');

So we should try to make the code block like the previous one.

DefinePlugin will replace some variables as constants.
From if (process.env.REACT_FOO === 'true') to if ('false' === 'true')

Create React App will pass REACT_APP_* from .env to DefinePlugin.

In a server environment, process.env will be used as a whole
In a browser environment, process.env.${key} is used alone for part of the logic
We should distinguish the usage of this part in two contexts

authors: Kudo abumalick cauthmann dburrows dimaqq idler8 johnlobster

repo: facebook/create-react-app


text:
react project installation issue

npm WARN npm npm does not support Node.js v14.5.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.
npm WARN npm You can find the latest version at https://nodejs.org/
npm ERR! cb.apply is not a function
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\home\AppData\Roaming\npm-cache_logs\2020-07-20T07_40_46_090Z-debug.log

You need to update your node version although I dont really know of a npm version that does this. What versions of node/npm are you using?

@gowrikumar666 I suspect you will need to update npm itself.
This issue is missing a lot of information, I am guessing you are on win 10 with a C:\ drive so I would
npm cache clean -f
npm install -g npm

hi,
i  already updated to latest version of node but it's not working react
project folder not installed into my sysem please let me know the issue as
soon as possible .
thank u
On Tue, Jul 28, 2020 at 2:10 AM Stephen Mount notifications@github.com
wrote:

@gowrikumar666 https://github.com/gowrikumar666 I suspect you will need
to update npm itself.
This issue is missing a lot of information, I am guessing you are on win
10 with a C:\ drive so I would
npm cache clean -f
npm install -g npm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/9331#issuecomment-664626690,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRMF7J2NBD5XFXDA47KH33R5XQ35ANCNFSM4PB7NQ2A
.

I am having the exact same issue as well. This is my first time using react and I simply cannot get a project started. Every time I try to get a project started I get this error. I'm using the 12.18.3 version of node.
npm ERR! cb.apply is not a function

Having similar issues with both the latest LTS and current versions of node.js. I started having this problem out of nowhere as I can't remember if I did anything to node or npm to warrant this issue.
I have tried options 1 and 2 listed in the existing issue at nodejs and I am still having problems.

authors: Infinitay eddiemonge gowrikumar666 nipkip stemount


text:
docs: Add PostHog plugin

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.

Motivation
PostHog has a plugin that makes it easy to add analytics, session replays, surveys, and more to Docusaurus. I just updated it and the docs for it.
The Google Analytics plugin is also being deprecated, meaning there will be fewer options for analytics.
Test Plan
Tested plugin locally and it is already in use.
Test links
https://docusaurus.io/docs/api/plugins
Deploy preview: https://deploy-preview-10163--docusaurus-2.netlify.app/docs/api/plugins/
Related issues/PRs
https://github.com/PostHog/posthog.com/pull/8512
https://github.com/PostHog/posthog-docusaurus/pull/15

Hi @ivanagas 👋 funny to see you there.
Just realized that there's an official posthog plugin that I could use on my own newsletter website instead of a custom posthog-js integration 😅
But apparently this was already added on our community resources pages a while ago (https://github.com/facebook/docusaurus/pull/2957)
The docs page you modify is only for listing official first-party plugins that we build ourselves and maintain as part of this monorepo, so I'm going to close

Ahh, missed this. Thanks!

authors: ivanagas slorber

repo: facebook/docusaurus