glpk: 4.64 -> 4.65

Semi-automatic update. These checks were done:

built on NixOS
ran /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol -h got 0 exit code
ran /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol --help got 0 exit code
ran /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol -v and found version 4.65
ran /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol --version and found version 4.65
ran /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol -h and found version 4.65
ran /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol --help and found version 4.65
found 4.65 with grep in /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65
found 4.65 in filename of file in /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65

Success on x86_64-darwin (full log)
Partial log (click to expand)
make[2]: Entering directory '/private/tmp/nix-build-glpk-4.65.drv-0/glpk-4.65'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/private/tmp/nix-build-glpk-4.65.drv-0/glpk-4.65'
make[1]: Leaving directory '/private/tmp/nix-build-glpk-4.65.drv-0/glpk-4.65'
post-installation fixup
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/p3cbi6n3ibs25np35bpmj0nw1krbmmv8-glpk-4.65/lib  /nix/store/p3cbi6n3ibs25np35bpmj0nw1krbmmv8-glpk-4.65/bin
patching script interpreter paths in /nix/store/p3cbi6n3ibs25np35bpmj0nw1krbmmv8-glpk-4.65
/nix/store/p3cbi6n3ibs25np35bpmj0nw1krbmmv8-glpk-4.65

Success on x86_64-linux (full log)
Partial log (click to expand)
make[1]: Leaving directory '/tmp/nix-build-glpk-4.65.drv-0/glpk-4.65'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65
shrinking /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin/glpsol
shrinking /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/lib/libglpk.so.40.3.0
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/lib  /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65/bin
patching script interpreter paths in /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65
checking for references to /tmp/nix-build-glpk-4.65.drv-0 in /nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65...
/nix/store/ra315prmwpsflq6fwq5glpxq0zqa1v3y-glpk-4.65

Success on aarch64-linux (full log)
Partial log (click to expand)
make[1]: Leaving directory '/build/glpk-4.65'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65
shrinking /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65/bin/glpsol
shrinking /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65/lib/libglpk.so.40.3.0
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65/lib  /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65/bin
patching script interpreter paths in /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65
checking for references to /build in /nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65...
/nix/store/90hk95arjc6dw4vkja15nrm9afj00k3y-glpk-4.65


[Bug] temperature sensors showing as wrong unit of measure

Describe the issue

All temperatures showing the Celsius value but with Fahrenheit unit of measure. Ie. If a disk is 40 C, it shows as 40 F. If I manually edit the sensor to show in Celsius, it converts 40 as if it were fahrenheit.
How to reproduce the issue

Expected behavior

The value of the sensor is correct but the unit of measure is wrong (should be Celsius, not fahrenheit)
Screenshots

Software versions

Home Assistant version:
TrueNAS integration version:
TrueNAS version:
TrueNAS-SCALE-22.02.4

Diagnostics data

Traceback/Error logs

Additional context

That is not on integration side.
Provided values and native unit is celsius, any conversion or unit change is done by HA.


Update Client.cpp

simple change, we are now doing the same process with less lines of code (you made this change earlier when recording inventory slots, so i figured why not)

Weird I know I had this in there before, I must of undone it by accident at some point.

ah i see, i only had the change on master and not on lootbot. Good catch thanks


Clear timeouts when exiting so we don't leave garbage behind

Sorry for following up with another PR so quickly after you bumped the version!
When exiting, the timeouts weren't being cleared. This is normally a non-issue when we're just process.exit(0)'ing, but I'm not actually doing that. In all cases, garbage is left behind and then process.exit(0) lets the OS clean it up. In the case where you do something other than exit, the timer would still eventually fire even though it already gracefully exited and we should prevent that condition. Also, clearing this timeout lets Node exit on its own since I clean up all of the other timers in our app through some miracle :).

Ok :) 0.0.5 is available now.


Add M1 to the list of supported targets

Description of changes:
In preparation for adding M1 bundles to the releases, add M1 (aarch64-apple-darwin) to the list of supported targets.
Resolved issues:
Resolves #1167
Related RFC:

Optional #ISSUE-NUMBER.
Call-outs:

Testing:

How is this change tested?

Is this a refactor change?

Checklist

[X] Each commit message has a non-empty body, explaining why the change was made
[X] Methods or procedures are documented
[X] Regression or unit tests are included, or existing tests cover the modified code
[X] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

There's a step in the release process meant to ensure everything actually works as intended. It's the post-github-release, pre-crates.io-release validation step. (That's currently broken when using --git, so we have to do that bundle thing instead.)

There's a step in the release process meant to ensure everything actually works as intended. It's the post-github-release, pre-crates.io-release validation step. (That's currently broken when using --git, so we have to do that bundle thing instead.)

Do we do that for all architectures though?

Do we do that for all architectures though?

AFAIK, no.


Support for Telegram passport

In the Telegram Bot API version 4.0, Telegram added support for Telegram Passport. As part of our goal of supporting the whole Telegram Bot API, it would be really nice to add support for it in our library.
Here there are a few links that can be helpful at the time of implementing it:

https://telegram.org/blog/passport
https://core.telegram.org/passport

u can assign it to me 👌

but is it really popular feature?

@imorte:
Good question, I'm not sure if this is a really popular feature. I'd guess that it isn't, we only had a person requesting it (and that's all the data we currently have to know if people want it).
Anyways, it's in our plans to fully support the Telegram Bot API, so we should definitely work on this at some point. So, up to you, if you want to work on it I'll assign it to you and you can go ahead (of course, if you have any doubt or need help let me know). But also, if you find something else you'll be more interested in working on let me know and we can sort it out (it doesn't have to be in the list of issues).


Remove process all button from apps when interrupted/errored

It is on the deployed app page. You can find under number 2: :)

Closed in #2117.


Add API for notifying plugin when connection to page is closed

For proper memory management.

At present snaps are terminated if they remain idle (do not receive any messages) for a sufficiently long time, which we will consider the solution to this problem.


White translucent fill covering map view v1.4.2

Sorry @pauldendulk , not quite out of the woods yet! :)
On both iOS and UWP (Skia), I am getting what seems to be a 50% white translucency (sometimes) rendered overtop my mbtiles and polygon layers -- the top point layer doesnt appear to be affected.
My layers are:
MBTiles
Polygon
Point
I rolled back to 1.4.1, and I don't get this rendering issue. So it's got to be something that changed between 1.4.1 and 1.4.2.

Do you have a screenshot?
I don't see this in the Mapsui samples. What could be the difference?

oh i can reproduce it

Fixed it. Commit will be later.


Toolbox/Guidelines to run for Linemod Dataset?

Hi @yuxng ,
Thanks for providing a well structured code package. Could you also provide data pre-processing steps for the LINEMOD object dataset? I am unable to figure out ways to generate train/test index files.
P.S. - I am trying to train your network for benchvise object in linemod.
Thanks,

Actually, I specifically had to run for linemod, so I did not download LOV before, Now that i have it downloaded with me, I am facing the exact error as you have mentioned above @2017hack .
Do you have any thoughts in the above items @yuxng ?

Can you make sure you compile the layers in lib correctly?

@ashar6194 Can you run the the lov_color_2d_train.sh and lov_color_2d_test.sh? Do you happen below problem: "failed to call to cuInit: CUDA_ERROR_NO_DEVICE, No kernel was registered to support Op ‘HoughvotinggpuGrad’ with these attires. registered devices: [cpu], registered kernels: deice = 'gpu'; T in [DT_FLOAT]". How can you solve it, can you share it with us, thanks!

same errors,have you solved it?


fix(nuxt): correct RouteNamedMap generation for duplicate pages

🔗 Linked issue

#29350
📚 Description

Fix the RouteNamedMap generation. When I created pages/foo.vue and pages/foo/index.vue, the RouteNamedMap type located at .nuxt/types/typed-router.d.ts has keys named foo and /foo.This fix aggregates these two keys into foo

would you add a test to the basic-types fixture? 🙏

would you add a test to the basic-types fixture? 🙏

I added some pages to the basic-types fixture package to simulate the issue. Does this look okay to you?


Android app

When I click on download in the android app, I get 'Network Error'. But the Internet is fine.

Please do not ask for support on GitHub, GitHub is for code/project-related questions. Ask for support in the Discord server: https://discord.gg/DKu7cUZ4XQ.
To answer you anyways, it could either mean:

The server is down, try it again within the next 2 hours (restart the app before trying again)
Your device or network is blocking peer-to-peer (p2p) connections, try it again on another device or network, on a VPN, or ask someone else to download it for you on the Discord server


how to use template in node component?

How can I use Angular Events with a dedicated template in the component?
for example:
please help me about my code
 this.componentReader = new D3NE.Component(this.nodeTitle, {
        template: '
<button type="button" (click)="addTest()"></button>
'
         builder(node) {
          const inp1 = new D3NE.Input('input', numSocket);

          return node
             .addInput(inp1)
         },
         worker(node, inputs, outputs) {
          const sum = inputs[0][0] + inputs[1][0];
            (<any>self.editor.nodes.find(n => n.id === node.id).controls[0]).setValue(sum);
            outputs[0] = sum;
         }
      });

Currently the rendering of the Node template is carried out by the Alight library. The template should not have the logic of interaction with the outside world, but you can declare directives or do it with the help of Control.
Moreover, I am currently considering a new architecture, so this part will be changed and added the ability to work with templates directly using Angular, React or Vue through plugins.


Unable to use Desktop with TurboVNC, using latest image, via apptainer

Bug description
I'm running the docker container using apptainer/singularity (1.1.9) on a Rocky9 HPC cluster.
This works, I can access Jupyter just fine using the browser.
If I used the Launcher and click the Desktop icon though, I get an error. I think the salient part is:
TurboVNC Server (Xvnc) 64-bit v3.1.1 (build 20240127)
Copyright (C) 1999-2024 The VirtualGL Project and many others (see README.md)
Visit http://www.TurboVNC.org for more information on TurboVNC

(EE)
Fatal server error:
(EE) ERROR: /etc/turbovncserver-security.conf must be owned by you or by root(EE)

Indeed, if I shell into the container and list it i see:
-rw-r--r--  1 nobody nogroup  4155 Jan 27  2024 turbovncserver-security.conf
Alas, trying to chown it gives:
chown: changing ownership of '/etc/turbovncserver-security.conf': Value too large for defined data type

Importantly, if I use the TigerVNC one, everything works just fine!
How to reproduce

apptainer pull docker://quay.io/jupyterhub/jupyter-remote-desktop-proxy:latest-turbovnc
This work, I get a SIF.
apptainer run --env JUPYTER_PORT=11008 jupyter-remote-desktop-proxy_latest-turbovnc.sif
This works, I can connect in the browser
connect to Jupyter in the browser and try to launch the Desktop tab
This doesn't work

Expected behaviour
I expected it to work just like tigerVNC, but maybe faster with better openGL support -- to be determined.
Actual behaviour
The desktop never launches
Your personal set up
Rocky9
apptainer 1.1.9

Hmm, pretty sure this is do to something about apptainer that I don't understand and not related to jupyter-remote-desktop-proxy.
If anyone has any advice for solving it I'd be very appreciative, but otherwise I think this can be closed.

It definitely sounds like something to do with Apptainer, and not the image.
Try asking on an Apptainer forum, or you could try https://discourse.jupyter.org/ since quite a few Jupyter HPC people hang out there.


Sveltekit Integration

What package(s) are you using?

[ ] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
[ ] Legacy/CDAI
[ ] Legacy/Security

What did you want to know?
Hello, can I use these components with sveltekit?
Relevant information

Only React is currently supported and this is unlikely to change any time soon.
The main Carbon library has a number of community projects implementing various frameworks. As the SCSS can be used separately there is no reason you could not create Svelte versions of the components.

How can I do it? Can you give me some details? Do I need to reverse engineer? @lee-chase


Implement the Scaffolder Flow

Feature Suggestion

The scaffolder flow is currently implemented in a Mock example here https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/src/service/router.ts#L40-L47

This needs implementing properly.

Possible Implementation

A scaffolder is created which has 3 steps.

Repository - where to get the templates from.
Templater - the chosen templater (ie CookieCutter).
VCS - the interaction with the VCS (git/github).

As a simple implementation, when a post request is sent to the router, we could run all these steps and then send the response after all steps are complete, or return early if there are errors.
Moving forward, we can take a look at making these actual async jobs with the 201 response, and async workers picking up the templating jobs.
Depends on #1107 #1105
Related to #345

Store create jobs in memory with an ID that is returned 201 which the endpoint can poll for now, and server side events maybe later on down the line.
Move this job processing outside of the scaffolder-backend somewhere.

Part of this work will need to have a new /v1/job/:jobId route that will return the events for the created job.
For now this job store can be something as simple as this:
const jobStore: Record<string, JobDetails> = {
    [uuid.v4()]: new JobDetails(),
};


[SPARK-7186] [SQL] Decouple internal Row from external Row

Currently, we use o.a.s.sql.Row both internally and externally. The external interface is wider than what the internal needs because it is designed to facilitate end-user programming. This design has proven to be very error prone and cumbersome for internal Row implementations.
As a first step, we create an InternalRow interface in the catalyst module, which is identical to the current Row interface. And we switch all internal operators/expressions to use this InternalRow instead. When we need to expose Row, we convert the InternalRow implementation into Row for users.
For all public API, we use Row (for example, data source APIs), which will be converted into/from InternalRow by CatalystTypeConverters.
For all internal data sources (Json, Parquet, JDBC, Hive), we use InternalRow for better performance, casted into Row in buildScan() (without change the public API). When create a PhysicalRDD, we cast them back to InternalRow.
cc @rxin @marmbrus @JoshRosen

Build triggered.

Build started.

Thanks for working on this huge change!  Should InternalRow live in catalyst with the other semi-private APIs?

Build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build finished. Test PASSed.

How come Jenkins didn't print any meaning messages? cc @JoshRosen

Jenkins, retest this please.

I looked at the Jenkins configuration log and it looks like @andrewor14's credentials somehow auto-filled and overwrote the Jenkins GitHub token; Andrew and I were modifying the builder configurations this afternoon to attach unit-tests.log outputs to the builds as build artifacts (we'll email the dev list later with more details on this feature).
I've rolled back the configuration change so hopefully we'll see SparkQA posting soon.
For those with Jenkins admin access, see https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/jobConfigHistory/showDiffFiles?timestamp1=2015-06-12_09-30-32&timestamp2=2015-06-12_14-37-42

Merged build triggered.

Merged build started.

Test build #34816 has started for   PR 6792 at commit f2abd13.

Test build #34816 has finished for   PR 6792 at commit f2abd13.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Going to merge this quickly since it conflicts with a lot of other patches.

Another nit:
[warn] /home/michael/spark/sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/ScalaReflectionSuite.scala:24: imported `InternalRow' is permanently hidden by definition of object InternalRow in package catalyst


Main Page shows graph notation instead of rendered picture

The main mill-build.org page suddenly doesn't render the graph anymore, but shows the raw graph notation:

thanks for the reort, should be fixed by https://github.com/com-lihaoyi/mill/pull/3698

Should be fixed by https://github.com/com-lihaoyi/mill/pull/3700


Don't read unneeded columns when working with ngrams.

Fixing a bug that caused all columns of a dataset to be read when schema_fields=NGram(...) was used.
Now, we collect all UnischemaField instances that appears in at least one of the time offsets within an NGram and load only corresponding columns.

looks good


[Test]prop-types: add test

It is working. Adding test.
Closes #2747

@ljharb the issue for this PR was closed. Since this only adds a test I don't know if you want to add or close it.


[Feature] [helper]-[MapDraw]?

What problem does this feature solve?
src/component/helper/MapDraw.ts
What does the proposed API look like?
0

af8a4e2eeac56a4f53d94ed5dffe67d95b560fa0


Stuck in terminal when after coming back from another application or desktop

Bug description
When switching from desktop or full screen application, I got stuck in the terminal. I can't write anything anymore. I need to close the terminal and open another one. It's very annoying when doing debugging.
Put here a clear and concise description of what the bug is
Screenshots
If applicable, add screenshots to help explain your problem
Steps to reproduce

Open a ssh connection
Switch to another desktop or full screen application
Come back to the previously opened ssh connection
Error is thrown

Thank you @B1aSst for your feedback
I'm searching the root issue.
I'm merging your issue with this one : https://github.com/isontheline/pro.webssh.net/issues/1025

Hello @B1aSst 👋
Could you try the latest beta release please?
https://testflight.apple.com/join/QSrBK59z

Hello
Just tested the beta version 27.2 and I do not encounter the issue anymore.
Thanks you for your action and for developping this app.
Have a good day !

Hello @B1aSst 👋
You're Welcome!
Thank you so much for your feedback 🙏


DRM Version Detection

Hi there,
this is not an Issue, its just a Question.
Is there a Way to find out, which DRM System will be used?
We use a DRM System with Widevine AND PlayReady (which works very good), I just would like to know, if there is a way to get the chosen DRM System from Shaka itself easily?
Thanks,
Christoph

Maybe CDM schemeIdUri can uniquely identify PlayReady or Widevine?

You can call player.drmInfo() after playback has started.  This will get the DrmInfo that was used to initialize EME.  In your case, the keySystem property will be com.widevine.alpha for Widevine, or com.microsoft.playready for PlayReady.

Perfect, thanks!


Farm : Smart Silo Routing

[x] FarmEntity : add setting enum => queryRouterType

[x] If queryRouterType is "default" : call each Silo + Granary
[x] If queryRouterType is "language model" : ask LLM to choose one or more Silo + Granary
[x] Use FallbackStrategy => retrieve on all? Or none?

[x] SiloEntity + GranaryEntity : add String field "description" => mandatory or not?

[x] Description will be used in order to help the LLM to choose the best ones

[x] Use langchain4j "LanguageModelQueryRouter" => choose one or more Silos / Granaries to retrieve

Closed by https://github.com/dRAGon-Okinawa/dRAGon/pull/283


Multiselection does not work on mobile screens

Hello!
The plugin has some function to enable multiple selection on mobile screens ?, currently only simple selection can be made
regards!

Hi, the plugin doesn't have this kind of features yet, but i'll try to implement them this week. Any suggestions? You need something in particular?

Hello, thanks for answering!
I would like the addon to activate multiple selection on mobile screens when you make the longpress gesture and select the items you need (as in the Android gallery). Currently it only works with a simple selection on mobile screens.
It could also be that multiple selection is activated automatically and select multiple items when selected
Either solution would come in handy
Thanks for the work, the plugin is very simple and very functional!
regards!


Ram consumption

Hi!
Thank you for the trainer - it`s great!
But I have a problem with my memory when using the trainer 1.9 (especially "Loot" feature) with SPT-AKI 2.3.1. It's just going up and up and the game crash when I run out of RAM. I have 32GBs of RAM.
Player.log
trainerini.txt

I never hit this issue, and I see nothing special in the logs. Are you using other tools/mods with tarkov or spt-aki ?

Still no repro on my side. Closing


Improve rpath handling

This improves rpath handling on both Mac OS X and Linux so that the rpath and library paths are correct both in the source tree and after installation. The binaries are set up to look in ../lib/ for the libraries, unless the install prefix is a system directory (specified by CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES), in which case this is left up to the system to decide.
I have not tested this change on Windows. This brings things to a point where I can easily use Travis for both Mac and Linux.

Looks pretty good to me. The only catch is that the install prefix at configure time isn't necessarily where a package gets installed to (consider cpack as an example), so it would be preferable if this just set the default of a GUI cache variable, vs setting it directly (or some other way of permitting a user to override)

Oh, and nothing rpath related affects Windows builds, so no worries there ☺

I'll look into that — it should be easy enough to make this overridable with a cmake flag.

The documentation at https://cmake.org/Wiki/CMake:Packaging_With_CPack indicates that CPack uses the install target generated by CMake internally — which means it should be setting the rpath correctly on package generation. If it is doing this, the logic in here should work properly. I'd like to test this though...

I think the catch I'm concerned about is the fact that it's usually "not best practices" in CMake to refer to CMAKE_INSTALL_PREFIX in your build script, since that can be overridden at install time (make install does something like cmake -P cmake_install.cmake, and you can do cmake -DCMAKE_INSTALL_PREFIX=yourdest -P cmake_install.cmake to get the equivalent of something similar to make install DESTDIR=yourdest - commands are all from memory, but I used something like that with stow, and don't know if homebrew uses it too - or if it even matters, since the purpose in those cases is to compile-in an install directory different from where you're initially putting it but where it will be able to find itself later.)
That said, this is nitpicking and probably not a good reason to not merge. If you're fine with it, I'll merge this and your travis scripts, then just open an issue for overriding this behavior. Thanks so much for doing this! I'll wait to hear back from you before merging.

Hmm, looking more closely, you're still going to run into the fact that the rpaths for libfunctionality and boost are not relative... I'll have to look deeper into this. If you'd like to, feel free to merge, open a new issue, and assign it to me.

Android build looks good with this PR.


Issue with @cdk-cloudformation/mongodb-atlas-cluster

We're trying to use the cdk construct in region eu-west-1.
aws cloudformation activate-type \
        --type-name MongoDB::Atlas::Cluster \
        --publisher-id bb989456c78c398a858fef18f2ca1bfc1fbba082 \
        --type RESOURCE \
        --execution-role-arn ROLE_ARN

But get this error.
An error occurred (TypeNotFoundException) when calling the ActivateType operation: Type with publisherId bb989456c78c398a858fef18f2ca1bfc1fbba082 and typeName MongoDB::Atlas::Cluster not found

I works when we try to active this in us-east-1. I guess this means that the type is only published to that region, can you publish it to eu-west-1 as well?

I would love to see this module in ap-southeast-2!
https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension-stacksets.html

@eladb can we get this re-opened? I successfully repro-ed this issue in ap-southeast-2 for both this resource and for the mongodb-atlas-networkpeering template. I would like to be able to configure these templates using CDK.
aws cloudformation activate-type --type-name MongoDB::Atlas::NetworkPeering \
--publisher-id  bb989456c78c398a858fef18f2ca1bfc1fbba082  \
--type RESOURCE  \
--execution-role-arn <arn> \
--region ap-southeast-2


[Removal]:

Hotspot Name
best-green-ladybug
Hotspot b58 Address
111KKsVbecs9FK1SWmjCSx2N7nE8z4ekXcaKc7gSRJycyMs7nDo
Discord Handle
No response
Hotspot Manufacturer
Pisces Miner
Removal Reason
they are real installed, what's going on?
Modifications
No
Extra forwarders
Yes
Extra antennas
No
Additional Information
they are real installed, what's going on?

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


Out-of-Vocab for VALUES is not an error

This fixes #290.
When an out-of-vocab entity is used in a VALUES clause this previously triggered an exception which is wrong. This PR now ignores the affected rows and emits warnings that are passed to the user in the
Json response.
Internally this implements a general mechanism to transport warnings for all kinds of operations.

@hannahbast have your questions/requested changes been answered, I think this can be merged


[Support] Resolve .local with PiVPN & Pi-Hole over wireguard

In raising this issue, I confirm the following:

[X] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[] The issue I am reporting can be is directly related to the pivpn installer script.
[X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
I've set up Pi-hole and and PiVPN after each other (the later recognized it and is set up to be the DNS provider) on a Raspberry Pi 4 board which is dedicated only for this purpose. It has a static IP address and my router settings are okay (port open for wireguard and pi-hole is the local DNS server). I've set up the following Local DNS entries:

nas.local <IP_ADDRESS>
udm.local <IP_ADDRESS>

They accessible from the local network, however when I want to access them through wirguard when I'm on the go they do not resolve. (Under Settings/DNS the "Listen on all interfaces, permit all origins" is ticked in.)
Have you searched for similar issues and solutions?
(yes)

Console output of      pivpn debug
::: Generating Debug Output
::::		PiVPN debug		 ::::
=============================================
::::		Latest commit		 ::::
Branch: master
Commit: 027f257931d1f169e254def5d1552d55810fefda
Author: 4s3ti
Date: Thu Aug 5 15:12:33 2021 +0200
Summary: Latest Changes update.
=============================================
::::	    Installation settings    	 ::::
PLAT=Ubuntu
OSCN=focal
USING_UFW=0
IPv4dev=eth0
install_user=ubuntu
install_home=/home/ubuntu
VPN=wireguard
pivpnPORT=51820
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=
pivpnHOST=REDACTED
INPUT_CHAIN_EDITED=0
FORWARD_CHAIN_EDITED=0
pivpnPROTO=udp
pivpnMTU=1420
pivpnDEV=wg0
pivpnNET=<IP_ADDRESS>
subnetClass=24
ALLOWED_IPS="<IP_ADDRESS>/0, ::0/0"
UNATTUPG=1
INSTALLED_PACKAGES=(net-tools iptables-persistent wireguard-tools qrencode)
=============================================
::::  Server configuration shown below   ::::
[Interface]
PrivateKey = server_priv
Address = <IP_ADDRESS>/24
MTU = 1420
ListenPort = 51820
### begin Isti_iPhone ###
[Peer]
PublicKey = Isti_iPhone_pub
PresharedKey = Isti_iPhone_psk
AllowedIPs = <IP_ADDRESS>/32
### end Isti_iPhone ###
### begin Isti_Mac ###
[Peer]
PublicKey = Isti_Mac_pub
PresharedKey = Isti_Mac_psk
AllowedIPs = <IP_ADDRESS>/32
### end Isti_Mac ###
### begin Eszti_iPhone ###
[Peer]
PublicKey = Eszti_iPhone_pub
PresharedKey = Eszti_iPhone_psk
AllowedIPs = <IP_ADDRESS>/32
### end Eszti_iPhone ###
### begin Eszti_Mac ###
[Peer]
PublicKey = Eszti_Mac_pub
PresharedKey = Eszti_Mac_psk
AllowedIPs = <IP_ADDRESS>/32
### end Eszti_Mac ###
=============================================
::::  Client configuration shown below   ::::
[Interface]
PrivateKey = Isti_iPhone_priv
Address = <IP_ADDRESS>/24
MTU = 1420
DNS = <IP_ADDRESS>

[Peer]
PublicKey = server_pub
PresharedKey = Isti_iPhone_psk
Endpoint = REDACTED:51820
AllowedIPs = <IP_ADDRESS>/0, ::0/0
=============================================
:::: 	Recursive list of files in	 ::::
::::[4m/etc/wireguard shown below	 ::::
/etc/wireguard:
configs
keys
wg0.conf

/etc/wireguard/configs:
Eszti_Mac.conf
Eszti_iPhone.conf
Isti_Mac.conf
Isti_iPhone.conf
clients.txt

/etc/wireguard/keys:
Eszti_Mac_priv
Eszti_Mac_psk
Eszti_Mac_pub
Eszti_iPhone_priv
Eszti_iPhone_psk
Eszti_iPhone_pub
Isti_Mac_priv
Isti_Mac_psk
Isti_Mac_pub
Isti_iPhone_priv
Isti_iPhone_psk
Isti_iPhone_pub
server_priv
server_pub
=============================================
::::		Self check		 ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] WireGuard is running
:: [OK] WireGuard is enabled (it will automatically start on reboot)
:: [OK] WireGuard is listening on port 51820/udp
=============================================
:::: Having trouble connecting? Take a look at the FAQ:
:::: https://docs.pivpn.io/faq
=============================================
:::: WARNING: This script should have automatically masked sensitive       ::::
:::: information, however, still make sure that PrivateKey, PublicKey      ::::
:::: and PresharedKey are masked before reporting an issue. An example key ::::
:::: that you should NOT see in this log looks like this:                  ::::
:::: YIAoJVsdIeyvXfGGDDadHh6AxsMRymZTnnzZoAb9cxRe                          ::::
=============================================
::::		Debug complete		 ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.log
:::

Have you taken any steps towards solving your issue?
  1. Setting up "Conditional forwarding" under Settings/DNS
  2. Flushing local DNS cache
  3. Restarted DNS resolver

a work around for me to have domain resolution when i wg to my clients network. i add a dns server to my config on my machine
example
DNS= <IP_ADDRESS>, <IP_ADDRESS>, mydomain.com
This lets me resolve server.mydomain.com in remote desktop for example or just \server if i'm getting to a share.
I tried to add it to the pi config but pivpnDNS3 isnt reconised so i add it manually
to the user confs

I see your point. However I thought that it should pick up pihole as the DNS server on its own.

Moving to Discussions


I solved a bug,

When running blender using CATS on unbuntu linux in init.py there is line 319
bpy.context.window_manager.addon_support = {'OFFICIAL', 'COMMUNITY' , 'TESTING'}
Remove TESTING for plugin to work normally otheriwse it will continue to crash

I can confirm that this happens in 2.5 and not 2.4.
The error is "couldn't find TESTING in {'OFFICIAL', 'COMMUNITY'}".
Deleting 'TESTING' from init.py works.

This is already fixed in the development version of Cats which you should be using on Blender 3.0 and newer: https://github.com/absolute-quantum/cats-blender-plugin/archive/refs/heads/development.zip


Update jeweler for next release

@joschi I was trying to update the gem and then noticed that rake version etc was giving error
NoMethodError: undefined method dependencies_for' for #Bundler::Runtime:0x007fcc140f96e0
Did you mean?  dependencies
/Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler/specification.rb:73:in block in set_jeweler_defaults' /Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler/specification.rb:41:in chdir'
/Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler/specification.rb:41:in set_jeweler_defaults' /Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler.rb:37:in initialize'
/Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler/tasks.rb:52:in new' /Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler/tasks.rb:52:in jeweler'
/Users/tessy/.rvm/gems/ruby-2.4.1/gems/jeweler-2.1.1/lib/jeweler/tasks.rb:82:in block in define' /Users/tessy/.rvm/gems/ruby-2.4.1/gems/rake-12.1.0/exe/rake:27:in <top (required)>'
/Users/tessy/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in eval' /Users/tessy/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in '`
But now it showing a warning with nokogiri. I think this could be merged .Once this is done I could do the jeweler release

@tessie first things first: thank you for helping out! I'm really sorry I've been so unresponsive for so long, will try becoming more involved if necessary.
As for breaking compatibility with older versions, I think there are still people out there being stuck on Ruby 1.9. What do you think about making one last release with 1.9 support and then dropping support for pre-2.1 rubies?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Tasks ran with MySQL adapter relies on mysql client binary

Environment

Elixir version (elixir -v): 1.3.3
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): MySQL 5.7
Ecto version (mix deps): 2.0
Database adapter and version (mix deps): Mariaex
Operating system: Heroku Cedar-14 (applies to any OS though)

Current behavior
When running tasks such as ecto.create and ecto.migrate an exception occurs. Following the stacktrace leads to Ecto.Adapters.MySQL.storage_up/1 and Ecto.Adapters.MySQL.storage_down/2, which are delegating to Ecto.Adapters.MySQL.run_with_mysql/2.
Ecto.Adapters.MySQL.run_with_mysql/2 shells out to the mysql client binary. The problem is that in production environments you typically won't have the MySQL client binary installed on your servers that Ecto will be running tasks from. The common case is that you will have the MySQL client development headers installed (this doesn't matter for us because Mariaex is an Elixir implementation of the MySQL protocol).
Expected behavior
I would expect Ecto to use the Mariaex adapter to run these queries rather than shelling out to the mysql binary.

Yes, if someone wants to send a pull request, it is welcome. That's what we do for Postgres: https://github.com/elixir-ecto/ecto/blob/master/lib/ecto/adapters/postgres.ex#L189-L223

I'll take a stab at it. I just wanted to confirm this wasn't the preferred behavior first.

asdasd
asdasd
asdasd

@rbishop this would be helpful for me when working on Ecto. If you could find some time to pick this up I would be very grateful.

@fishcakez We just stopped using MySQL since Postgres is HIPAA certified on AWS RDS now, but I'll try and take care of this anyway. I will try my best in the coming weeks!


Unable to Copy ERR_INVALID_ARG_TYPE Errors

Steps to reproduce

Use utils-copy-error to copy a TypeError [ERR_INVALID_ARG_TYPE] error in Node
See new error thrown by Node

Current behaviour
Copying a TypeError [ERR_INVALID_ARG_TYPE] error results in Node throwing a new TypeError [ERR_INVALID_ARG_TYPE] error instead of providing the error being copied.
Expected behaviour
The original error is returned as-is.
Log Output
Original error (from console.error):
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at validateString (internal/validators.js:125:11)
    at Object.join (path.js:1147:7)

Error produced by module:
AssertionError [ERR_ASSERTION]: Code: ERR_INVALID_ARG_TYPE; The provided arguments length (1) does not match the required ones (3).
    at getMessage (internal/errors.js:220:5)
    at new NodeError (internal/errors.js:159:13)
    at copy (/opt/ws/webapps/apiv3/node_modules/utils-copy-error/lib/copy.js:29:8)

Other comment
I ran into this when trying to copy an error produced by Path.join with an undefined entry.

@thelaughingwolf Thanks for reporting this issue. Would you be able to provide a minimal code snippet I can use to reproduce this issue? Thanks!

Absolutely!
const Path = require('path');
const copy = require('utils-copy-error');
let error;

try {
	Path.join(undefined, undefined);
} catch (e) {
	console.error(`Original error:`, e);
	error = copy(e);
}

console.error(`Copied error:`, error);

Thanks! Let me try and reproduce on my end, and I'll circle back.

Okay. I investigated. At some point, Node.js moved away from vanilla V8 errors (Error, TypeError, etc) and created a custom error type NodeError. Unfortunately, I am not really able to make heads or tails of what the (internal) NodeError constructor expects as arguments (see here). Currently, this package assumes that the error to be copied is a vanilla error object, or at least, if a subclass, something that has the same signature.
Unfortunately, the internal NodeError objects do not have such a signature. And I am not sure how to go about providing such support.
If you have any ideas, LMK.

Thanks for investigating! I'll look into it some myself.

Oof, this was fun.
I can see the fundamental error is fired by an assert in getMessage. And the messages are preloaded by the convenience method E. So when you call error.constructor, it is actually trying to create a new NodeError with code ERR_INVALID_ARG_TYPE, which was defined here. That's the method that maps to error.constructor, and that's the method that needs three arguments. So Node thinks you're trying to register a method to warn about an incorrect parameter count, but then misusing the error constructor.
It's also clear from that long list that each predefined NodeError type expects its own list of arguments and types. It's definitely not feasible to try to replicate each code.
Perhaps, if error instanceof NodeError is true, you could copy the error some other way?

Yeah, the above was my conclusion, as well.
Re: copy. I am not sure if there is a viable way forward on this one. As we really cannot copy the NodeError instance without invoking its constructor. At least, we would not be able to copy it exactly.
We could, possibly, check if a NodeError instance is one of the built-in error types (e.g., TypeError, URIError, etc), and, if so, copy the error info to a new built-in error instance. This would not be 1:1, and it depends on the use case, I suppose, but this could be a way forward.


Fixes resolving promises when encrypting array

Make sure to wait for all promises in array to be resolved when encrypting an array
Why
The traverseObject function is currently returning an array of promises instead of waiting for all promises to be resolved.
How
Using await Promise.all on the array of promises waits for the promises to be resolved.

The github actions are acting weird here. I'm gonna clone this myself.

Now it's working. The Omnissiah works in mysterious ways.


lib/cpp/test/SecurityTest is flaky in jenkins Thrift-precommit build.

Previously, the server socket might not be fully closed from a prior
test, leading to flaky port bind failures in CI.  Avoid the issue
altogether by binding an ephemeral port.
Add a TODO to TestPortFixture.h to warn folks away from its usage
and link THRIFT-3609 to track the work of removing or replacing it.

Hrm, although it looks like Travis-CI will go green with this change, Jenkins still flaked out.  More investigation needed.  This PR will get a bit noisy with debug attempts and I may close it after debugging the issue and start a fresh PR + patch with the ultimate fix.

Coverage remained the same at ?% when pulling e71f20cd3ee9e812a064e492a7e692e2f2f98d35 on jsirois:THRIFT-3608 into e71f20cd3ee9e812a064e492a7e692e2f2f98d35 on apache:master.


Discourse fails to build with GemNotFound on 21.11

Describe the bug
A clear and concise description of what the bug is.
[nix-shell:~/REDACTED/]$ HOSTNAME=finnaboo nixos-rebuild switch -I nixos-config=. --use-remote-sudo --target-host root@REDACTED
building Nix...
(root@REDACTED) Password:
(root@REDACTED) Password:
warning: you did not specify '--add-root'; the result might be removed by the garbage collector
building the system configuration...
warning: you did not specify '--add-root'; the result might be removed by the garbage collector
these derivations will be built:
  /nix/store/d643awr7ibza1ag0sr3bm8cmic0cakyg-discourse-assets-2.7.4.drv
  /nix/store/bi5a06iwfd9gdqgywmllxqmi93l5m8vn-discourse-2.7.4.drv
  /nix/store/zmcwrwshyzi5mx9h9460f3rsmcrz68cj-discourse-rake.drv
  /nix/store/5c2yga9zmjqb5zc0frr2xqb1jbmhvmcg-system-path.drv
  /nix/store/ap4ajhhapb4198lsv9801zrz14il19fq-dbus-1.drv
  /nix/store/332s42q1v5v388k8311qnw8qswxkv7yg-unit-dbus.service.drv
  /nix/store/71c0f12fcar6b5jywwpja7fh8ismiwc4-unit-systemd-fsck-.service.drv
  /nix/store/s5h7755dncmjmw3jjgnqaqgsqbp2vr90-unit-script-discourse-pre-start.drv
  /nix/store/fn47k0nky439yxvqjlswz81iggcasb2m-unit-discourse.service.drv
  /nix/store/pxl92sqa0fjzs1bwkfch8xfbai2s84nj-unit-polkit.service.drv
  /nix/store/7zdqc1d6q0amg1nxrskipjjlypbn2zmw-system-units.drv
  /nix/store/zggivr1wvx8z7j7pgzmdxkw0svn5pli0-unit-dbus.service.drv
  /nix/store/xay0dgy54535a6v0ny4rz0rc4ngpap02-user-units.drv
  /nix/store/n19ha8g67za5c83gzfkqba2is0l8s5ry-etc.drv
  /nix/store/67cvz5k8sapwizsrqsikccjn4pfablq7-nixos-system-finnaboo-21.11pre301985.23cd13167a1.drv
building '/nix/store/d643awr7ibza1ag0sr3bm8cmic0cakyg-discourse-assets-2.7.4.drv'...
unpacking sources
unpacking source archive /nix/store/hd8cbp0i09lzk1xv2fq094arclw4qccw-source
source root is source
patching sources
applying patch /nix/store/fwr2l8n5jfd9h1c7h5v30cc9plsm44ik-plugin_gem_api_version.patch
patching file lib/plugin_gem.rb
configuring
no configure script, doing nothing
building
Waiting for Redis and PostgreSQL to be ready..
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/build/.s.PGSQL.5432"?
2021-09-03 05:09:02.644 UTC [32] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2021-09-03 05:09:02.646 UTC [32] LOG:  listening on Unix socket "/build/.s.PGSQL.5432"
2021-09-03 05:09:02.659 UTC [36] LOG:  database system was shut down at 2021-09-03 05:09:02 UTC
2021-09-03 05:09:02.664 UTC [32] LOG:  database system is ready to accept connections
CREATE ROLE
CREATE DATABASE
CREATE EXTENSION
CREATE EXTENSION
bundler: failed to load command: rake (/nix/store/iai83miyc25hxwd79w6xh0ana0b9md1r-discourse-ruby-env-2.7.4/lib/ruby/gems/2.7.0/bin/rake)
Traceback (most recent call last):
        27: from /nix/store/v11va3c5l83mjkypr6wv1axazd42yjpl-ruby-2.7.4/bin/bundle:23:in `<main>'
        26: from /nix/store/v11va3c5l83mjkypr6wv1axazd42yjpl-ruby-2.7.4/bin/bundle:23:in `load'
        25: from /nix/store/iai83miyc25hxwd79w6xh0ana0b9md1r-discourse-ruby-env-2.7.4/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/exe/bundle:37:in `<top (required)>'
        24: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/friendly_errors.rb:128:in `with_friendly_errors'
        23: from /nix/store/iai83miyc25hxwd79w6xh0ana0b9md1r-discourse-ruby-env-2.7.4/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/exe/bundle:49:in `block in <top (required)>'
        22: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/cli.rb:24:in `start'
        21: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
        20: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/cli.rb:30:in `dispatch'
        19: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
        18: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        17: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
        16: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/cli.rb:474:in `exec'
        15: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/cli/exec.rb:28:in `run'
        14: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/cli/exec.rb:61:in `kernel_load'
        13: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/cli/exec.rb:61:in `require_relative'
        12: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/setup.rb:20:in `<top (required)>'
        11: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/ui/shell.rb:88:in `silence'
        10: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/ui/shell.rb:136:in `with_level'
         9: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/setup.rb:20:in `block in <top (required)>'
         8: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler.rb:149:in `setup'
         7: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/runtime.rb:20:in `setup'
         6: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/runtime.rb:91:in `block in definition_method'
         5: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/definition.rb:240:in `requested_specs'
         4: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/definition.rb:258:in `specs_for'
         3: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/definition.rb:189:in `specs'
         2: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/spec_set.rb:90:in `materialize'
         1: from /nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/spec_set.rb:90:in `map!'
/nix/store/vpsp8197vb5s9y2rlmfgkmivz5r9wlrm-bundler-2.2.20/lib/ruby/gems/2.7.0/gems/bundler-2.2.20/lib/bundler/spec_set.rb:95:in `block in materialize': Could not find libv8-node-<IP_ADDRESS>-x86_64-linux in any of the sources (Bundler::GemNotFound)
builder for '/nix/store/d643awr7ibza1ag0sr3bm8cmic0cakyg-discourse-assets-2.7.4.drv' failed with exit code 1
cannot build derivation '/nix/store/bi5a06iwfd9gdqgywmllxqmi93l5m8vn-discourse-2.7.4.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/zmcwrwshyzi5mx9h9460f3rsmcrz68cj-discourse-rake.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/fn47k0nky439yxvqjlswz81iggcasb2m-unit-discourse.service.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5c2yga9zmjqb5zc0frr2xqb1jbmhvmcg-system-path.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/7zdqc1d6q0amg1nxrskipjjlypbn2zmw-system-units.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/67cvz5k8sapwizsrqsikccjn4pfablq7-nixos-system-finnaboo-21.11pre301985.23cd13167a1.drv': 1 dependencies couldn't be built
error: build of '/nix/store/67cvz5k8sapwizsrqsikccjn4pfablq7-nixos-system-finnaboo-21.11pre301985.23cd13167a1.drv' failed

Steps To Reproduce
Set the following on NixOs 21.11 and expect failure:
services.discourse = {
	enable = true;
	hostname = "discourse" + config.networking.fqdn;
	admin = {
		fullName = "Jacob Hrbek";
		username = "kreyren";
		# FIXME(Krey): Decide on admin mail
		email =<EMAIL_ADDRESS>		passwordFile = "/var/db/discourse.db";
	};
};
# HOTFIX(Krey): The PostgreSQL version recommended for use with Discourse is 13.3, you're using 11.12. Either update your PostgreSQL package to the correct version or set services.discourse.database.ignorePostgresqlVersion. See https://nixos.org/manual/nixos/stable/index.html#module-postgresql for details on how to upgrade PostgreSQL.
	## Note(Krey): The assertion happens https://github.com/NixOS/nixpkgs/blob/7f857f1c32580c056d3b09758f0196a2acae962d/nixos/modules/services/web-apps/discourse.nix#L523, no idea why it's using postgresql_11 by default, needs to be investigated
services.discourse.database.ignorePostgresqlVersion = false;
services.postgresql.enable = true;
# CONTRIB(Krey): The upstream still use postgresql_11 which breaks the discourse build
services.postgresql.package = pkgs.postgresql_13;

Expected behavior
Build Discourse
Additional context
Distributed build from this system on Hetzner's Cloud

Notify maintainers

CC @talyz
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
# Local Build system
[kreyren@leonid:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.48, NixOS, 21.11pre301985.23cd13167a1 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.12`
 - channels(root): `"nixos-21.11pre301985.23cd13167a1"`
 - channels(kreyren): `"home-manager-21.05, master"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
# Hetzner system
[root@finnaboo:~]# nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked):
  /nix/store/lp90qhw19dcp79cnlicjg09llgh7dzsz-bash-interactive-4.4-p23-dev
copying path '/nix/store/lp90qhw19dcp79cnlicjg09llgh7dzsz-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.44, NixOS, 21.11pre301985.23cd13167a1 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.12`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Solved as pebcak i had issue in my handling that caused it to fail update repos.


sami not support the @see/@deprecated .... tags?

sami not support the @see/@deprecated .... tags?

The @see tags is supported for sure (see #201). Not sure about @deprecated tag though. Anyway tags are collected, but maybe not displayed by default in currently used Twig templates.

oh,yes, sami support @see, but @deprecated is excluded

You can send PR with support for @deprecated tag.

sorry, I don't know how to send PR. can you give a advise?

Luckily GitHub has it all docummented: https://help.github.com/articles/using-pull-requests/.

@mumutou You have to:

Fork the sami repository (button above)
git clone your fork to a local directory
Run composer install etc.
change the sources, ideally add some tests for your changes
run the tests (vendor/bin/phpunit)
if everything is fine git commit your changes
git push your commits to your fork
visit your fork (https://github.com/mumutou/Sami) and create the pull request

ok, i see


[BUG] Longhorn error handling lacks delays to avoid bringing the k8s api down (eg creates 40k bogus replicas CRs)

Describe the bug (🐛 if you encounter this issue)
I'm observing that longhorn 1.4.1 and 1.4.3 are lacking delays when handling with errors, resulting in unfriendly high k8s api calls, either

high number of mutations on existing resources (Replicas whose desire state continuously flaps between running and stopped)
high number of bogus replica CRs created (40k instances in few days): https://github.com/orange-cloudfoundry/paas-templates/issues/2070

The later took down the k8s api database, and made the k8s api hardly useable after scaling out the k8s api database.
To Reproduce
The problem were triggered by network errors among longhorn pods

tcp offload preventing UDP & TCP traffic in pod-to-pod communication among k8s nodes https://github.com/orange-cloudfoundry/paas-templates/issues/2062
incorrectly configured http proxy env var with insufficient no_proxy clause in BackupTarget , see https://github.com/orange-cloudfoundry/paas-templates/issues/2088

Expected behavior
Longhorn controllers should be friendly with the k8s api server and apply delays (with potential exponential back-off) before handling errors resulting in k8s api calls
Workaround
Manually delete the bogus replica CRs from the k8s api database, to recover the k8s api server
Support bundle for troubleshooting

Environment

Longhorn version:
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
Kernel version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:
Impacted Longhorn resources:

Volume names:

Additional context

high number of bogus replica CRs created (40k instances in few days):

It sounds like a known issue https://github.com/longhorn/longhorn/issues/5762.
After upgrading the system to v1.4.3, is it still observed?

Thanks for the update.
The symptom is same as the issue https://github.com/longhorn/longhorn/issues/5762 and is triggered when network is unstable.
      "longhorn.io/backing-image": "",
      "longhorndiskuuid": "",
      "longhornnode": ""

Please try v1.4.2 or v1.4.3 instead. Appreciate your update in advance.

Thanks @derekbit for your prompt response. I'll try to reintroduce the network fault to reproduce the issue against 1.4.2

If available, could you provide wrong longhorn replica resource by kubectl -n longhorn-system get replica  -o yaml or a support bundle for investigation?

Sample faulty replica massively created: no diskid, attached node
{
  "apiVersion": "longhorn.io/v1beta2",
  "kind": "Replica",
  "metadata": {
    "creationTimestamp": "2023-09-06T13:02:13Z",
    "generation": 1,
    "labels": {
      "longhorn.io/backing-image": "",
      "longhorndiskuuid": "",
      "longhornnode": ""
    },
    "name": "pvc-b5b6f759-2e3c-4bc1-b6d4-c194760e298f-r-8260f72a",
    "namespace": "02-longhorn",
    "ownerReferences": [
      {
        "apiVersion": "longhorn.io/v1beta2",
        "kind": "Volume",
        "name": "pvc-b5b6f759-2e3c-4bc1-b6d4-c194760e298f",
        "uid": "e3170ceb-b93c-4e71-89fc-3ffddca7ab6e"
      }
    ],
    "uid": "77273538-b09a-4ad4-98d7-d06840326b7a"
  },
  "spec": {
    "active": true,
    "backingImage": "",
    "baseImage": "",
    "dataDirectoryName": "",
    "dataPath": "",
    "desireState": "stopped",
    "diskID": "",
    "diskPath": "",
    "engineImage": "longhornio/longhorn-engine:v1.4.0",
    "engineName": "pvc-b5b6f759-2e3c-4bc1-b6d4-c194760e298f-e-84648df6",
    "failedAt": "",
    "hardNodeAffinity": "",
    "healthyAt": "",
    "logRequested": false,
    "nodeID": "",
    "rebuildRetryCount": 5,
    "revisionCounterDisabled": false,
    "salvageRequested": false,
    "unmapMarkDiskChainRemovedEnabled": false,
    "volumeName": "pvc-b5b6f759-2e3c-4bc1-b6d4-c194760e298f",
    "volumeSize": "21,474,836,480"
  }
}

In comparison, sample healthy replica updated just before the longhorn incident started
{
  "apiVersion": "longhorn.io/v1beta2",
  "kind": "Replica",
  "metadata": {
    "creationTimestamp": "2023-08-14T09:44:12Z",
    "deletionGracePeriodSeconds": 0,
    "deletionTimestamp": "2023-09-05T20:35:07Z",
    "finalizers": [
      "longhorn.io"
    ],
    "generation": 5,
    "labels": {
      "longhorn.io/backing-image": "",
      "longhorndiskuuid": "18ffe9ff-aefe-46e3-a75c-57c3f077f081",
      "longhornnode": "minio-agents-0",
      "longhornvolume": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9"
    },
    "name": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9-r-21c2e67c",
    "namespace": "02-longhorn",
    "ownerReferences": [
      {
        "apiVersion": "longhorn.io/v1beta2",
        "kind": "Volume",
        "name": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9",
        "uid": "93cbd8e9-aa52-48ad-8b77-1fa502a95f50"
      }
    ],
    "uid": "c18a8325-6406-438d-b500-7071a9dcc404"
  },
  "spec": {
    "active": true,
    "backingImage": "",
    "baseImage": "",
    "dataDirectoryName": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9-64783947",
    "dataPath": "",
    "desireState": "stopped",
    "diskID": "18ffe9ff-aefe-46e3-a75c-57c3f077f081",
    "diskPath": "/var/vcap/store/longhorn/",
    "engineImage": "longhornio/longhorn-engine:v1.4.0",
    "engineName": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9-e-4339f7fc",
    "failedAt": "2023-09-05T20:04:49Z",
    "hardNodeAffinity": "",
    "healthyAt": "2023-08-14T09:44:32Z",
    "logRequested": false,
    "nodeID": "minio-agents-0",
    "rebuildRetryCount": 0,
    "revisionCounterDisabled": false,
    "salvageRequested": false,
    "unmapMarkDiskChainRemovedEnabled": false,
    "volumeName": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9",
    "volumeSize": "21474836480"
  },
  "status": {
    "conditions": [
      {
        "lastProbeTime": "",
        "lastTransitionTime": "2023-08-14T09:44:12Z",
        "message": "",
        "reason": "",
        "status": "True",
        "type": "InstanceCreation"
      }
    ],
    "currentImage": "",
    "currentState": "stopped",
    "evictionRequested": false,
    "instanceManagerName": "",
    "ip": "",
    "logFetched": false,
    "ownerID": "bastion-agents-2",
    "port": 0,
    "salvageExecuted": false,
    "started": false,
    "storageIP": ""
  }
}

diff <(jq .spec scratch_129.json) <(jq .spec scratch_130.json)
5c5
<   "dataDirectoryName": "",
---
>   "dataDirectoryName": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9-64783947",
8,9c8,9
<   "diskID": "",
<   "diskPath": "",
---
>   "diskID": "18ffe9ff-aefe-46e3-a75c-57c3f077f081",
>   "diskPath": "/var/vcap/store/longhorn/",
11,12c11,12
<   "engineName": "pvc-c3dad9f5-3fb6-4a53-a37c-4fa6a00e6b48-e-8bbd4a2d",
<   "failedAt": "",
---
>   "engineName": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9-e-4339f7fc",
>   "failedAt": "2023-09-05T20:04:49Z",
14c14
<   "healthyAt": "",
---
>   "healthyAt": "2023-08-14T09:44:32Z",
16,17c16,17
<   "nodeID": "",
<   "rebuildRetryCount": 5,
---
>   "nodeID": "minio-agents-0",
>   "rebuildRetryCount": 0,
21c21
<   "volumeName": "pvc-c3dad9f5-3fb6-4a53-a37c-4fa6a00e6b48",
---
>   "volumeName": "pvc-fdbe21ce-c5cd-40fc-bb72-35b009286ab9",

Please try v1.4.2 or v1.4.3 instead. Appreciate your update in advance.

I was unable to reproduce the network error to reproduce the problem fixed in #5762 in 1.4.3. See https://github.com/orange-cloudfoundry/paas-templates/issues/2070#issuecomment-1737770277 for test procedure and observed symptoms.
I however indeed experienced infinite loop of volume detaching and attaching, putting high load on the api server as described into https://github.com/orange-cloudfoundry/paas-templates/issues/2088

@derekbit, besides the validating admission webhook preventing write of bogus replica CRs, is there existing delays in error handling in longhorn to avoid entering infinite loop without backoff mechanism ?


Indicators are not centered

I layout a view in storyboard and then I set it up
let size = self.view.frame.size
self.pagerIndicator.frame = CGRect(x: 0, y: 0, width: size.width, height: 15)
self.pagerIndicator.scp_style = .SCJAFillCircle
self.pagerIndicator.set_view(model.numberOfCells, current: 0, tint_color: .black)

The indicators are not centered. The first indicator.origin.x looks centered, but I would expect the group of indicators to be centered in view as in the example file.
I'm using the last version and swift 4

Hello dnakiller.
I'm sorry for being late.
I have known recently.
so I have corrected in SCPageControl 2.0 version
you try 'pod update', If you can't, tell me again
thank you

Thank you for the answer,
I have installed the version 0.2.0 and I still have the problem.
Details:
I have a SCPageControlView set up in storyboard. Constraints fix the view to be as wide as the viewcontroller. Then in code I set the view as already mentioned and as found in the example app:
// let size = self.view.frame.size
// self.pagerIndicator.frame = CGRect(x: 0, y: 0, width: size.width, height: 15)
self.pagerIndicator.scp_style = .SCJAFillCircle
self.pagerIndicator.set_view(model.numberOfCells, current: 0, tint_color: .black)

The visual output is the same with and without the line specifying the frame:
visual_output
Thank you

Hello dnakiller
sorry. I thought it was something else.
if you use Autolayout, frame is not real size.
As a solution, this initial SCPageControll in ViewDidLayoutSubviews Method
(ViewDidLayoutSubviews method is call after viewWillAppear Method)
i will example project is update.
I hope this solution helps.
thank you

Hello myoungsc,
I tried moving the initialization in viewDidLayoutSubviews but I have the same problem. Also doing this I have to protect the initializer from subsequent calls (since viewDidLayoutSubviews it is called every time interface refresh).
I also tried to create a container plain UIView pinned with autolayout and add to it an SCPageControllView programmatically, but that doesn't solve the problem either.
Finally I had to change how the circle initial x is calculated.
I understand it might not be suitable for your implementation, but this is what it solves my problem:
// original code
 f_circle = 10.0
        var f_x: CGFloat = ((self.frame.size.width-f_circle)/2.0) + 5, f_y: CGFloat = (self.frame.size.height-f_circle)/2.0

f_start_point = f_x

// new calculation of `f_x`
f_circle = 10.0
let circle_distance: CGFloat = 10
let circle_plus_distance = f_circle + circle_distance
let number_of_page = CGFloat(numberOfPage)
let group_width = (circle_plus_distance * number_of_page) - circle_distance
var f_x: CGFloat = (self.frame.size.width / 2.0) - (group_width / 2.0)
var f_y: CGFloat = (self.frame.size.height-f_circle)/2.0

f_start_point = f_x

I have tried to maintain the naming convention used and break down all the steps.
If you think this change might be suitable for your library and don't create other problems to the way you intended it to be used, I'll use your update, otherwise I'll have to fork.
Thank you

I wrong calculate start point for SCJAFillCircle.
SCPageControl did update to 0.2.1 version for fix
Fixed the wrong calculate in 0.2.1 version And You can be use Autolayout.
When i did test. I succes.
if In case of trouble tell me.
Thank you.

All solved on my side updating to 0.2.1!
Thanks a lot


Web test server doesn't support https

Running flutter run -d chrome opens the app in http://localhost:[RANDOM PORT] but the lack of SSL makes it impossible to connect to Firebase. Can we get CLI flags to:

make the server use https
specify a hostname other than localhost

I realized that firebase serve works fine with just http.

You can also change the hostname with --web-hostname and the port with --web-port


Added limitations and mitigations section and relevant papers

I have added papers which are addressing the issue of training data replication in T2I diffusion models.

Thanks!


removed django 1.7 specific settings from travis

@nemesisdesign sending new separate PR's with logical commits

Coverage remained the same at 99.628% when pulling 7a455cd9cff07c0ee1d6b93d5290616f0dcc5a89 on auvipy:clean into e1f35515ef20084f55da60fc9c6ae10896593404 on djangonauts:master.

Coverage remained the same at 99.628% when pulling fad43f54174033d64c8862fde2638439bb836ee1 on auvipy:clean into e1f35515ef20084f55da60fc9c6ae10896593404 on djangonauts:master.


fix: update yarn links to point to classic yarn

Motivation
Lodestar uses classic yarn(1.x) but all the links in the README's point to the latest release of yarn(4.x).
Description
Yarn now points to https://classic.yarnpkg.com/lang/en/ instead of https://yarnpkg.com/

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in v1.17.0 :tada:


Support for Angular 7.x.x

What is the desired behavior?
To not have these warnings:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS><7.0.0 || >6.0.0-beta <7.0.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS><7.0.0 || >6.0.0-beta <7.0.0".
What is the use-case or motivation for the desired behavior?
Have a more stable base Angular Environment with 7.x.x for upgrading a 6.x.x app.
Is there anything else you want to share?
Current given dependencies of the latest 7.0.0-beta.5 are:
"dependencies": {
"@angular-devkit/build-angular": "0.9.0-beta.2",
"@angular/animations": "7.0.0-beta.5",
"@angular/cdk": "7.0.0-beta.0",
"@angular/cli": "7.0.0-beta.2",
"@angular/common": "7.0.0-beta.5",
"@angular/compiler-cli": "7.0.0-beta.5",
"@angular/compiler": "7.0.0-beta.5",
"@angular/core": "7.0.0-beta.5",
"@angular/flex-layout": "6.0.0-beta.18",
"@angular/forms": "7.0.0-beta.5",
"@angular/http": "7.0.0-beta.5",
"@angular/material": "7.0.0-beta.0",
"@angular/platform-browser-dynamic": "7.0.0-beta.5",
"@angular/platform-browser": "7.0.0-beta.5",
"@angular/router": "7.0.0-beta.5",
"@angular/service-worker": "7.0.0-beta.5",
"core-js": "^2.5.4",
"rxjs": "^6.2.2",
"tsickle": "0.32.1",
"tslib": "^1.9.0",
"zone.js": "~0.8.26"
}
Version information
@angular/*: 7.0.0-beta.5
typescript: 3.0.3
rxjs: ^6.2.2
node: 10.10.0
yarn: 1.10.0

@mastermsd we'll need to sync with the Angular CLI team before we release support for Angular version 7.


Blurred user interface

I'm Using two monitors with the same resolution but different DPI. OS is the latest Windows10. VS Code is also updated to the latest version - the problem occurs on all VS Code versions

/gifPlease

Hello,
Many thanks for your email.
The blurred font problem disappears the moment I click back onto VS Code,
the screenshot taken with  W10 build-in crop tool does look much better
than the actual situation on the screen.
Hope this helps
Jacek
On Thu, 8 Apr 2021 at 13:01, VS Code Issue Triage Bot <
@.***> wrote:

Thanks for reporting this issue! Unfortunately, it's hard for us to
understand what issue you're seeing. Please help us out by providing a
screen recording showing exactly what isn't working as expected. While we
can work with most standard formats, .gif files are preferred as they are
displayed inline on GitHub. You may find https://gifcap.dev helpful as a
browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling
screencast mode for the recording (Developer: Toggle Screencast Mode in
the command palette).
Happy coding!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/120758#issuecomment-815667751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFA4MXMKGV75HQDK4W2N4KLTHWEI5ANCNFSM42RPFPFA
.

--
Jacek

https://github.com/microsoft/vscode/issues/120758#issuecomment-815667751

Please see the gif - the actual situation on the screen is worse than the screenshot shows:

Thanks, this looks more like an Electron problem to me.
Does it help if you run code --disable-gpu from the command line?

I tried and seems that the issue is gone, I  wasn't using VS Code today for too long, but not a single blurred character so far. Big thanks, I have tried several solutions without effect, but looks like you had the right one for me, in case the problem reappears - I will write here.

Update: After spending more time with my editor, I have unfortunately experienced the blurred fonts issue again...

Can you check if the issue happens with latest insiders https://code.visualstudio.com/insiders/, if so please try launching with code-insiders --force-device-scale-factor=1

Hey Deepak, looks like your solution has worked! I have also tried with the regular version code --force-device-scale-factor=1
Many thanks, that was something annoying me for a long time!

Thanks for confirming, this kind of bug usually gets resolved with an update to the chromium runtime. I will close this for now with the above workaround, as there is not much we can do about the issue.


Event when a specific field get valid

Is there any way to know if a field get valid?
I would like to execute a function when the field #foo get valid. Only the field #foo not for every field on the form.
I have tried:
$('form[data-toggle="validator"] #foo').on('valid.bs.validator', function(){
x();
});
However it did not work.
Thanks in advanced.
Paulo

The event is fired on the form itself, with the field that triggered it attached to the event as event.detail.
So you'd need to do
$('form[data-toggle="validator"]').on('valid.bs.validator', function(e) {
  var $input = $(e.detail)
  if ($input.attr('id') == 'foo') x();
});

Thanks for your help, however it is returning undefined.
Is there any documentation about the provided details returned on the valid.bs.validator
Thanks.

ok changed the the input object to related target all good now.
var $input = $(e.relatedTarget);

Whoops, sorry. event.detail is where the error message is kept. Glad you got it figured out.

Hi, this doesn't work for me, am I missing something, i'm new to all this aswell
$(document).ready( function(){         $('form[data-toggle="validator"]').on('valid.bs.validator', function (e) {             var $input = $(e.relatedTarget)             if ($input.attr('id') == 'source_ip') x();         }); })
function x() {     alert('hi its valid') }
and my html
`

Add

`


Check if the component is mounted in the promise handler.

There is no guarantee that the component is still mounted when the promise resolves.

I dont mean to sound rude, but why would this component ever be unmounted? I really dont get it. Could you provide a gist with the code showing this particular case where it can be unmounted?

Check out the end of this file.
https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/client.js
Also the solution came from this description.
https://facebook.github.io/react/blog/2015/12/16/ismounted-antipattern.html
On Wed, Jun 1, 2016 at 8:07 AM Vitaly Aminev<EMAIL_ADDRESS>wrote:

I dont mean to sound rude, but why would this component ever be unmounted?
I really dont get it. Could you provide a gist with the code showing this
particular case where it can be unmounted?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/makeomatic/redux-connect/pull/27#issuecomment-222901457,
or mute the thread
https://github.com/notifications/unsubscribe/AASi2RmMv-XGuGaXNymStSYcK7L6Zw4Wks5qHSGFgaJpZM4IrDkF
.

Code you've sent should never dismount that component

On 01 Jun 2016, at 10:22, Rui Araújo<EMAIL_ADDRESS>wrote:
Check out the end of this file.
https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/client.js
Also the solution came from this description.
https://facebook.github.io/react/blog/2015/12/16/ismounted-antipattern.html
On Wed, Jun 1, 2016 at 8:07 AM Vitaly Aminev<EMAIL_ADDRESS>wrote:

I dont mean to sound rude, but why would this component ever be unmounted?
I really dont get it. Could you provide a gist with the code showing this
particular case where it can be unmounted?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/makeomatic/redux-connect/pull/27#issuecomment-222901457,
or mute the thread
https://github.com/notifications/unsubscribe/AASi2RmMv-XGuGaXNymStSYcK7L6Zw4Wks5qHSGFgaJpZM4IrDkF
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

It does though, I haven't investigated why because I am too busy and also because unmounting and mounting again should not be a problem.
Also if the component was unmounted it should not call setState.

@ruiaraujo it shouldn't. thing is that it shouldn't be unmounted either. And if you want to avoid checking isMounted() - the solution you proposed is essentially exactly the same as the deprecation notice. Proper case for this is to cancel in-flight action during componentWillUnmount lifeCycle method, however, normal promises are not cancellable (bluebird ones are though). Given that I still want you to examine why it dismounts in between renders first and only then proceed with that solution or another. I've been using this for 4 months in prod now and havent seen this once myself, nor many of devs I work with. It clearly is a concern, but again, I'm pretty sure it is not really a problem with this module, but rather with the way redux provider is used

Indeed, that's the second solution the link above suggests and I went the easy route and did the basic one.
Note that none of the developers here in the office did not have this issue, I was only able to reproduce it in a Nexus 5X and in some remote developer Mac mini.
Alas the problem does exist, so feel free to either implement a 'cancellable' promise and cancel the request in the willunmount or to use this simple yet effective approach. I am not attached to any of them. ;-)

@ruiaraujo - this is exactly the same thing as #26 as far as I'm concerned. I'll get this in, just because it helps, but, again, this is far from ideal :(


feat(python): support .rerank() on non-hybrid queries in Async API (WIP)

Fixes https://github.com/lancedb/lancedb/issues/1950

Hi @wjones127 , I am missing where/how to hook up the rerank method with the FTSQuery and the provided builders, or is the unit test wrong and I should focus on the queryBuilder rather than in chaining the operations?
Any help is much appreciated!