Python: add FUNCTION LOAD command

Issue #, if available:
N/A
Description of changes:
https://redis.io/docs/latest/commands/function-load/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

You can use the opened pr and work on it :)

You can use the opened pr and work on it :)

I don't have the access to your opened PR. After discussing with Andrew and Yury, we decided to create a new PR. I will reference your PR.

This new Python FUNCTION LOAD PR is based on https://github.com/aws/glide-for-redis/pull/1589.
I will close PR 1589 after this PR is merged.
I only addressed review comments and merged with the latest changes.


Add mutation observer to check if cookie banner has been acknowledged

Who is this for?
#10915
What is it doing for them?
This PR adds a value in the context that checks if the cookie banner has been acknowledged. I put it at that level as I thought it could be useful elsewhere, but if we think it's overkill I can move it.
What's going on?

When the cookie banner shows on a page with a Modal (such as this work), the latter is stopping the former from being interacted with as it is locked in with FocusTrap (for a11y reasons).
We need to deactivate FocusTrap if the cookie banner has yet to be acknowledged and interacted with, then re-activate it to stick by good a11y practices.

The banner can be considered acknowledged in three different ways:

The user clicks "Accept All": the CookieControl cookie is set, and the banner is removed from the DOM.
The user clicks "Essential only": the CookieControl cookie is set, and the banner is removed from the DOM.
The user clicks "Manage cookies": the CookieControl cookie is set, the banner is removed from the DOM and the Preference centre popup is added to the DOM. The user then interacts (or not) with the contents of the Preference centre popup, then clicks "Save and close". The popup is removed from the DOM.

Because the cookie is not automatically set at the same time as everything is removed from the DOM, we can't count on detecting the cookie to re-activate the FocusTrap.
We also can't use CivicUK's callbacks to re-activate FocusTrap as it offers one for onAccept and onRevoke, but not for when a user dismisses the cookie preferences by clicking "Manage cookies" and then simply "Save and close".
So we have to find out when the banner and popup are fully removed from the DOM, and we can do that by detecting when the #ccc Element (ccc being the ID of the parent container) has zero children left - because yes, the parent stays in the DOM, but is an empty div. I'm thinking it's so the Preference centre popup knows where to inject itself should it be called up again. Only then can we then activate the FocusTrap.
We use ccc-overlay to check if the banner is up as it is a sibling of both the popup and the banner should one of them be active.
This was a bit of a maze so happy to jump on a call to run through it.

We also can't use CivicUK's callbacks to re-activate FocusTrap as it offers one for onAccept and onRevoke, but not for when a user dismisses the cookie preferences by clicking "Manage cookies" and then simply "Save and close".

It is quite disappointing that this is the case, I would have expected there to be some kind of signal for any choice even dismissal.


chore: remove unused package

Checklist:

README.md includes:

[ ] The details of signing data and transaction data, this includes parameters.
[ ] Official docs or white paper.
[ ] Website or api can query assets and broadcast transaction.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Task linked: CW-19346 Upgrade libraries in cp-node-graphql-endpoint service


Direct - User - ValidatePassword

Hi, im developing an Android App for Sakai.
I found an issue when i try to use /direct/user/validatePassword
It always mark as OK, its an issue?

@deinok we currently don't use GitHub issues for anything other than the GradebookNG project. Please create a JIRA ticket if you wish to report this issue:
https://jira.sakaiproject.org


Auto-updating fetch version in docs

Also, it removes the duplicated badges.
Please, @fedefernandez could you take a look? Thanks!

Codecov Report

Merging #116 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #116   +/-   ##
=======================================
  Coverage   77.59%   77.59%
=======================================
  Files          10       10
  Lines         250      250
  Branches        2        2
=======================================
  Hits          194      194
  Misses         56       56

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 1e74dd8...801b41c. Read the comment docs.


Is CockroachDB supported?

CockroachDB has similar API as PostgreSQL, and Npgsql driver is supported. Do you have plan to support it?

support Npgsql.dll

DbType = SqlSugar.DbType.PostgreSQL,


Error

Expected behavior
Actual behavior
(HTTP code 401) unexpected - {"message":"Get https://registry-1.docker.io/v2/library/postgres/manifests/latest: unauthorized: incorrect username or password"}
Information about the Issue
Steps to reproduce the behavior

...
...

Please try to login using your Docker ID (hub username) instead of your email. This should fix the issue.


Rongxin Zhang: Assignment 04

Assignment 04 Compeleted:
Changed URL: www.roguepandaz.com:8080
@amfleming @rchatterjee
Working on EC2:

Hi! Please resolve conflicts

@amfleming please review


feat: trigger release

previous run failed - https://github.com/supabase/storage-api/actions/runs/4649068615

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.515%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6987

Relevant Lines:
8209

💛  - Coveralls


Output effective (biologically plausible) weights in get_weights

Codecov Report

Merging #16 into master will increase coverage by 1.21%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   51.11%   52.32%   +1.21%
==========================================
  Files          13       13
  Lines         718      730      +12
==========================================
+ Hits          367      382      +15
+ Misses        351      348       -3

Impacted Files
Coverage Δ

psychrnn/backend/models/basic.py
0% <0%> (ø)
:arrow_up:

psychrnn/backend/rnn.py
89.08% <83.33%> (-0.5%)
: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 4ae590c...ebd9b5c. Read the comment docs.


make Element Pricing Model forward compatible with updated Market class

make Element Pricing Model forward compatible with updated Market class

npm run sim works now @jrhea

please download this 50mb pdf to prove the results

https://drive.google.com/file/d/0BwPAx00btgr3X19QN0tIMUhnM28/view?usp=sharing&resourcekey=0-w-EouBGD8F2P2MT2G8QOFw


JsonWebTokenError extends Error class

I'm writing a REST API with JWT authorization, and only want to know, why did you guys don't make JsonWebTokenError function on /lib/JsonWebTokenError.js a class that extends Error class ?
I though that for better 'checking' (maybe not the words), when handling errors with try/catch.
So instead
try{
 // with the JsonWebTokenError here
} catch (err) {
if (err.message === 'jwt malformed') {
// and handle this..
}

becomes this:
try{
 // with the JsonWebTokenError here
} catch (err) {
if (err instanceof JsonWebTokenError) {
// and handle this..
}

or even more specific like:
/ ...
if (err instanceof MalformedJsonWebToken)
/ ...

Thanks in advance :smile:

We do not "extends Error class" but we use Object.create() to achieve the inheritance.
Isn't working for you? You can find the errors in the root of the library:
const jwt = require('jsonwebtoken');
jwt.JsonWebTokenError

To let you do if (err instanceof jwt.JsonWebTokenError) {}

@ziluvatar  Thank you man! I wrote this in the "fire" of a sprint, only to know! Thank you for the tip! :+1: :smile: You guys are awesome!


Streams3 all the things!

There are lots of browserify dependencies (and brfs dependencies) that are still using old versions of readable-stream. We could make the install faster (and perhaps bundle sizes smaller), if we updated everything to ^2.0.0.
$ npm outdated
readable-stream                1.0.33  1.0.33    2.0.2  brfs > static-module > readable-stream
readable-stream                1.1.13  1.1.13    2.0.2  browserify > labeled-stream-splicer > stream-splicer > readable-wrap > readable-stream
readable-stream                1.1.13  1.1.13    2.0.2  browserify > duplexer2 > readable-stream
readable-stream                1.1.13  1.1.13    2.0.2  browserify > labeled-stream-splicer > stream-splicer > readable-stream
readable-stream                1.1.13  1.1.13    2.0.2  browserify > read-only-stream > readable-stream
readable-stream                1.1.13  1.1.13    2.0.2  brfs > static-module > duplexer2 > readable-stream
readable-stream                1.1.13  1.1.13    2.0.2  browserify > read-only-stream > readable-wrap > readable-stream

I started moving stuff over to streams3:
https://github.com/substack/stream-splicer/pull/10
https://github.com/substack/read-only-stream/pull/4
https://github.com/deoxxa/duplexer2/pull/12
I didn't bother updating "readable-wrap" because it's fix is already in streams3. So instead my PRs simply remove it.
Updating to<EMAIL_ADDRESS>will bring with it streams3 (https://github.com/maxogden/concat-stream/pull/36). As well as updating to<EMAIL_ADDRESS>I'll have to see once these are merged in how the deps resolve to see what's missing. @substack how about merging the read-only-stream and stream-splicer (and updating labeled-stream-splicer) PRs?

stream-splicer and read-only-stream updated

cool! I've also got https://github.com/substack/module-deps/pull/97 and https://github.com/substack/stream-combiner2/pull/4, but they're both waiting on https://github.com/deoxxa/duplexer2/pull/12

Would be nice to get all these packages updated in time for browserify 12.0.0. See: https://github.com/substack/node-browserify/issues/1398

Cool, I think all outstanding PRs are merged so we should be completely streams3 for browserify 12, but we should verify with npm outdated.

module-deps doesn't have the updated stream-combiner – when I update it, the tests fail. I can't look into this now, I'm at work :(

<EMAIL_ADDRESS>has all the streams3 updates

It looks like this is now finished and the issue can be closed. :+1:
>npm outdated --depth 10
Package                Current  Wanted  Latest  Location
acorn                    1.2.2   1.2.2   2.6.4  browserify > syntax-error
acorn                    1.2.2   1.2.2   2.6.4  browserify > insert-module-globals > lexical-scope > astw
acorn                    1.2.2   1.2.2   2.6.4  browserify > module-deps > detective
array-filter             0.0.1   0.0.1   1.0.0  browserify > shell-quote
builtin-status-codes     1.0.0   1.0.0   2.0.0  browserify > stream-http
date-now                 0.1.4   0.1.4   1.0.1  browserify > console-browserify
glob                    5.0.15  5.0.15   6.0.1  browserify
json-stable-stringify    0.0.1   0.0.1   1.0.0  browserify > deps-sort > shasum
json-stable-stringify    0.0.1   0.0.1   1.0.0  browserify > shasum
os-browserify            0.1.2   0.1.2   0.2.0  browserify
source-map               0.4.2   0.4.2   0.5.3  browserify > browser-pack > combine-source-map
source-map               0.4.2   0.4.2   0.5.3  browserify > insert-module-globals > combine-source-map
source-map               0.4.2   0.4.4   0.5.3  browserify > insert-module-globals > combine-source-map > inline-source-map
source-map               0.4.2   0.4.4   0.5.3  browserify > browser-pack > combine-source-map > inline-source-map


set empty uboot var in boot.txt instead of deleting it; fix ssh enabling

This PR modifies uboot code so we set an empty var when unseting (only used for pv_rev=). It also fixes ssh activation, which was being set to true when the arg "splash" was not present. Now, besides being configurable, one can enable debug ssh and shell with the "pv_debug" arg.

lgtm. lets land it


Select-Object : Property "Value" cannot be found.

When I run the script, Invoke-Maester, I got this error for Get-MtUser and Test-PrivilegedAssignments.
Don't know if this is on my machine.

Can you confirm your setup
Windows PowerShell?
Which version of the Microsoft graph module?
Thanks for reporting this issue

I had the same error with Powershell 5. It's working with PowerShell 7

Thanks, this was what I was guessing. I will take care of it over the weekend

Fixed in version 0.0.117


Apply command not reading credentials from AWS Secrets manager without placeholder in cluster config

Looks like topicctl apply is not trying to read SASL credentials from AWS Secrets manager while topicctl check does.
$ echo $TOPICCTL_SASL_SECRETS_MANAGER_ARN
arn:aws:secretsmanager:<region>:<account-id>:secret:<secret-id>

$ topicctl --version
topicctl version v1.18.0 (ref:dev)

Steps to reproduce:
$ cat /tmp/topic.yaml
---
meta:
  name: test_topic
  cluster: test_cluster
  environment: dev
  region: some-region
spec:
  partitions: 12
  replicationFactor: 3
  placement:
    strategy: any

$ cat /tmp/cluster.yaml
---
meta:
  name: test_cluster
  environment: dev
  region: some-region
spec:
  bootstrapAddrs:
    - <b1-endpoint>:9096
    - <b2-endpoint>:9096
    - <b3-endpoint>:9096
  tls:
    enabled: true
  sasl:
    enabled: true
    mechanism: SCRAM-SHA-512

$ topicctl apply /tmp/topic.yaml --skip-confirm --cluster-config /tmp/cluster.yaml --expand-env --debug

{{test_topic test_cluster some-region dev  map[] []} {12 3 0 map[] {any  [] []} <nil>}}
[2024-06-24 13:04:08] DEBUG No ZK addresses provided, using broker admin client
[2024-06-24 13:04:08] DEBUG Connecting to cluster on address <b1-endpoint>:9096 with TLS enabled=true, SASL enabled=true
[2024-06-24 13:04:08] DEBUG Getting supported API versions
[2024-06-24 13:04:09] ERROR 58: SASL Authentication Failed: SASL Authentication failed: Authentication failed during authentication due to invalid credentials with SASL mechanism SCRAM-SHA-512

Output from topicctl check:
$ topicctl get topics --cluster-config /tmp/cluster.yaml --expand-env --debug

time="2024-06-24 12:59:50" level=debug msg="No ZK addresses provided, using broker admin client"
time="2024-06-24 12:59:50" level=debug msg="Setting SASL SecretsManagerArn from override value"
time="2024-06-24 12:59:50" level=debug msg="Fetching credentials from Secrets Manager for secret: arn:aws:secretsmanager:<region>:<account-id>:secret:<secret-id>"
time="2024-06-24 12:59:50" level=debug msg="Fetching secret value for secret name: <secret-id>"
time="2024-06-24 12:59:50" level=debug msg="Connecting to cluster on address <b1-endpoint>:9096 with TLS enabled=true, SASL enabled=true"
time="2024-06-24 12:59:50" level=debug msg="Getting supported API versions"

You can clearly see that topicctl check tries to read secret from Secrets manager.

Just noticed that it ONLY works if value or placeholder is set for secretsManagerArn in cluster.yaml while Username & Password works just by setting as environment variables without the need for placeholders in cluster.yaml


Jitter and Shaking issue in Character2D node using physics process

Tested versions
Tested on version Godot 4.2.1 and Godot 4.0
System information
Windows 11 - Godot v4.2.1
Issue description
Godot Engine v4.2.1
**Jitter in Character2d Node move right and left or top and down **
https://docs.godotengine.org/en/stable/tutorials/rendering/jitter_stutter.html
Below are some steps done to resolve the Jitter issue
Update the Max FPS to 60 and also make sure that the ticks_per_second is 60 still jitter issues
Tried change the ticks_per_second to 60 and Increase the Max Physics step per second, but issue is still there.
extends CharacterBody2D

const SPEED = 300
var viewport_size
const MARGIN = 20

func _ready() -> void:
	viewport_size = get_viewport_rect().size

# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta: float) -> void:
	pass

func _physics_process(delta: float) -> void:
	var direction = Input.get_axis("move_left", "move_right")
	velocity = velocity.normalized()
	if direction:
		velocity.x = direction * SPEED
	else:
		velocity.x = move_toward(velocity.x, 0, SPEED)

	move_and_slide()

Steps to reproduce
Create a Character2D player and add the sprite 2D and Rectangle collision 2D node. Once done configure the script for Character2D Node and add the following below code
extends CharacterBody2D

const SPEED = 300
var viewport_size
const MARGIN = 20

func _ready() -> void:
	viewport_size = get_viewport_rect().size

# Called every frame. 'delta' is the elapsed time since the previous frame.
func _process(delta: float) -> void:
	pass

func _physics_process(delta: float) -> void:
	var direction = Input.get_axis("move_left", "move_right")
	velocity = velocity.normalized()
	if direction:
		velocity.x = direction * SPEED
	else:
		velocity.x = move_toward(velocity.x, 0, SPEED)

	move_and_slide()

	if global_position.x > viewport_size.x - MARGIN:
		global_position.x = -MARGIN

Sprite2D will contain the simple PNG image of character and run application to check if character move left to right.
**Note: ** move_left and move_right is the Input mapping to A(physical)  Left(physical) and D(physical) Right(physical) respectively.
Character shows the jitter and shaking response.
Sometime it works for few minutes after it again shows Jitter effect and below are steps also followed provided in document: https://docs.godotengine.org/en/stable/tutorials/rendering/jitter_stutter.html
Still no effect.
Minimal reproduction project (MRP)
Added player.tscn and png file in below zip file, with script
Game.zip

I'm not seeing an effect I'd call stuttering/jitter on Linux 5.15 x86_64, maybe windows specific? Is there anything specific that you do immediately before the stuttering happens other than move left/right?
Is "Max Physics Steps Per Frame" still set to 8?

No, I added only base physics process code, I already checked frame rate on which machine and screen is working by enabling the debug frame rate and it was working on 60 fps but still there was issue.

The MRP provided does not contain a project, so I was unable to test this, but from the description it sounds like the same behavior as #93048


readme example for local browsers hanging

If I run the following script:
var launchpad = require('launchpad');

launchpad.local(function(err, local) {
	console.log('launchpad.local callback');
	if (err) { throw err; }
	local.browsers(function(err2, browsers) {
		console.log('local.browsers callback');
		if (err2) { throw err2; }
		console.log(browsers);
	});
});

... my console output is launchpad.local callback and then nothing happens.
I think this is following the example in the readme properly. Am I missing something, or is this a bug?

Sorry I somehow missed this issue. You can set the DEBUG=launchpad:* environment variable to get more information on what it is trying to do while discovering the browsers.
I'm closing the issue since it has been around for a while. Please reopen if you have more information.


perf(behavior_velocity_planner): remove pose.orientation from occlusion_spot

Signed-off-by: Ryuta Kambe<EMAIL_ADDRESS>Description
cc: @taikitanaka3 @soblin
In occlusion_spot module in behavior_velocity_planner node, pose of collision information are calculated, though those pose are used only for extracting pose.position information. pose.orientation are wastefully calculated and they have a lot of computational cost. Thus I deleted that calculation and replaced calcPose function to calcPosition.
Related links
https://github.com/autowarefoundation/autoware.universe/issues/2097

The red line is the original latency of occlusion_spot, and the blue one is the latency when this commit is adapted.

@veqcc
is virtual wall refactoring necessary with this PR?I think  this PR should include part of this PR
https://github.com/autowarefoundation/autoware.universe/pull/2506

@veqcc
Please run
git rebase HEAD~4 --signoff
git push --force-with-lease origin remove_pose_orientation_from_occlusion_spot

to pass the check


Delete (cmd + delete) not working

Possible regression:

https://supabase.slack.com/archives/CSMGA08FP/p1622343866081800
https://supabase.slack.com/archives/CSMGA08FP/p1622403490082400

fixed: https://github.com/supabase/grid/commit/9e329cc5bdb12b06e3a2fd9cc20b79336b0d3586

There're issues with delete row shortcut:

it depend on row index which will change after a deletion
it's dangerous

I will remove this shortcut. We will bring back row context menu. Hope it's good enough.


Asset emission reworking

This PR represents a reworking of the asset emission algorithm including:

Removing the "not found" require handling and instead relying on not found errors being runtime errors in ncc itself via https://github.com/zeit/ncc/pull/378.
Refactoring of asset emission handling to avoid a number of special cases including the need to special case ffmpeg (which has tests here)
escapeNonAnalyzableRequires is no longer an option, and this is done much more consistently for both require and require.resolve. As a result many previously non-working dynamic require cases should now work out correctly.
Implementing wildcard asset handling, and process.cwd() analysis - https://github.com/zeit/webpack-asset-relocator-loader/issues/10

The exact emission logic is described below:
process.cwd
The path.resolve and process.cwd() analysis will use the process.cwd of the build process itself. So if the build is run from the wrong directory these can not work out and cause assets not to be emitted.
To support a custom cwd, this can be passed as an option as well.
require.resolve

ALWAYS escape it as __non_webpack_require__.resolve.
Inline its expression wherever possible further.

require

If we're unable to analyze the input, escape it as __non_webpack_require__.
If the input is known but not webpack analyzable (utilized getKnownBinding), then inline the analyzed value (including in branched cases).
On the Webpack side, ensure that all require calls fallback to outer (like we did previously).
In addition ensure that any not found resolutions do not fail.

variable declarations and assignments

All variable declarations and assignments are analyzed for pure static values
If the value is an absolute path string, then it is allowed to become an asset emission
Otherwise, the walking routine will continue to check for internal asset triggers
The logic here has been significantly improved, with a lot of special casing removed. Even 'require()' is handled as a standard call expression analysis now in a variable declaration.

call expressions

All call expression callee values are statically analyzed to determine if they are known (typically from the known staticModules that might be required such as fs functions, path functions).
If the callee is a known pure function it is executed in the analysis
If the callee has a [TRIGGER] property, then it can trigger an asset emission (eg in path.resolve('./a')), the path.resolve function has a [TRIGGER] for emission like this, so we don't analyze every "./a" string).
If the callee is a well-known symbol, then we have various special cases applied (eg EXPRESS gets its own treatment this way etc).
Well known symbols are also applied for all fs functions as asset emission points. In this way fs.readFile(...) will emit the argument as an asset if it can be computed.

This PR should now resolve the following issues on ncc core:

https://github.com/zeit/ncc/issues/290
https://github.com/zeit/ncc/issues/216
https://github.com/zeit/ncc/issues/349
https://github.com/zeit/ncc/issues/41
https://github.com/zeit/ncc/issues/216
https://github.com/zeit/ncc/issues/297

Just a few ncc bugs left before this should be ready for further review and merging.

Codecov Report

Merging #30 into master will decrease coverage by 0.16%.
The diff coverage is 73.13%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage    70.3%   70.13%   -0.17%
==========================================
  Files          10       10
  Lines         899      904       +5
==========================================
+ Hits          632      634       +2
- Misses        267      270       +3

Impacted Files
Coverage Δ

src/utils/static-eval.js
66.5% <100%> (+6.6%)
:arrow_up:

src/utils/wrappers.js
97.95% <100%> (+0.08%)
:arrow_up:

src/utils/special-cases.js
77.35% <16.66%> (-17.88%)
:arrow_down:

src/asset-relocator.js
78.35% <76.36%> (-1.52%)
: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 b0520b5...7c94f73. Read the comment docs.

ncc tests are passing against this PR. Merging for a beta release to gain further feedback.


Update READMEs

See #1
This PR is to address out-of-date details in our README.md files across the repo.
Primarily, address README for the following:

[x] apps/namada-interface
[x] apps/extension

Also, check docs under packages for an erroneous or out-of-date documentation.

Closing this - README has been updated in appropriate place to bring up-to-date, though we should still revisit this to add README where they currently don't exist!


DBZ-6363 Replacing MongoDbContainer with MongoDbReplicaSet and fixing mongodb visibility for other containers

The few tests I tried worked on my MacOS machine. Somebody should try it on linux.
This PR supersedes ##700

Superseded by #701

@rk3rn3r  @ani-sha  I moved this under new Jira ticket and polished a code a bit (mainly moving things which should be moved directly to debezium-testcontainers). This seem to work on MacOS.
Somebody should take it from here and make sure it also works with linux :).

Hi @jcechace, I ran the test suite locally, and it works like a charm.  I'm going to do the following:

Apply the change in the main repository against Debezium 2.3.0-SNAPSHOT.
Add a commit to this PR to remove the @Disabled annotation on the MongoDB tests.
Move the Debezium UI repository to Debezium 2.3.0-SNAPSHOT.
Rebase this PR and merge

This should get everything lined up and working again.  Thanks for all the help on this!

Applied to main (=2.3).

Thx a lot @jcechace! :pray:
Great work


Feature implement sample using reinforcement learning tflite

@st-tuanmai This is an object detection sample, not reinforcement learning? Please submit the correct app.


[1:1] pfe-tile

Component name: <pfe-tile>

The tile component exists in PF 4 and will be added to RHDS, but it's not part of PFE yet.

Design specification
PatternFly v4 Tile

PF's Tile is currently in Beta. Wondering if we should be attempting to do an 1:1 work on Beta components at this time.
Also, the definition of "tile" might be a source of confusion. In PF, Tiles seem to be "selectable" (i.e. listbox). Our use might be more "clickable" (i.e. <a>).
Carbon seems to allow multiple types of interaction within their definition of Tile.
When migrating this as 1:1, do we narrow the scope for PFE and then widen the scope for RHDS to match Carbon's usage? What's the industry standard on these?

The impetus for this issue was to unblock <rh-tile>. We're fine to prioritize this only slightly higher than that.

closed by #2187


Stop nominating_timer on shutdown

Looks like this causes more issue. I think there might be some more timers lingering, will have a look this afternoon.


fix translate call

Call was failing due to a call to translate which does not exist.
`neiferna@neiferna-mac quicksql % npm run example-cli -- ./test/department_employees.quicksql

<EMAIL_ADDRESS>example-cli
echo "running example..." && ./examples/cli.js ./test/project_management.quicksql "./test/department_employees.quicksql"

running example...
file:///Users/neiferna/gitpub/quicksql/examples/cli.js:43
console.log( quicksql.translate( file_content ) );
^
TypeError: quicksql.translate is not a function
at file:///Users/neiferna/gitpub/quicksql/examples/cli.js:43:23
at ModuleJob.run (node:internal/modules/esm/module_job:183:25)
at async Loader.import (node:internal/modules/esm/loader:178:24)
at async Object.loadESM (node:internal/process/esm_loader:68:5)
at async handleMainPromise (node:internal/modules/run_main:63:12)`
Fixed `translate` to `toDDL` which is the correct function name.


Switch account after encountering 'Not Enough Funds' does not switch account

Stacks Wallet for Web
Tested on Chrome / Macbook pro
Just noticed that after encountering You don't have enough STX to make this transfer. Try switching accounts, switching networks, or adding STX to this account.

Just realised this it keeps you on the same account as the one your logged into app with - so maybe the message should read 'try logging into the app with a different account or adding stx etc - or the app should get an error to handle this?

@radicleart this seems to be an outdated version of the wallet, can you confirm the version you're using?


Enhancement: Add a line graph for unstable mood (mood swings).

It would be a great thing if the graph showed mood trend (mood swings) as a line graph of a certain color that would show turbulence in moods.  Currently, mood log is displayed under each bar of the graph upon clicking on it, so it needs to be checked manually. Instead, it could be displayed graphically over the bar for each day.
Think of it as an earthquake-type of a line of a different color (customizable) that would run across the present graph.
It would probably need to be a toggle thingy that one could turn on/off if need be. The more mood swings on a particular day, the more unstable the line graph would look over the particular day.
Say, one feels great in the morning (5) then horrible in two hours (1) and okay again (3) in the evening and awesome again 1 hour later (5). Now, the graph only averages the values. If there was this line graph showing rapid mood changes, then one could see if the mood swing patterns are present repeatedly because the graph would show elevated line graph on certain days and one could do something about it.
This is the best way I can describe it. I have no idea how this would need to be programmed, but perhaps it could just record mood variables and display them individually (every single change, similar to this picture)

Visually, it might look something like this:

@tiovialde This looks really useful - although I'm not sure if it can be implemented with charts.js (library I'm using) as you envision.
I wonder if a different mode - one that would display only graph (with fine-grained resolution), without bars - will achieve the same effect? It's definitely more doable :)

Thanks for considering it, @dartungar
By "fine-grained" you mean something like this?

All my comments are in the picture.


How to enable auto popup for autocomplete?

Description of your problem
The auto complete feature provided in the spyder require user to either use tab or ctrl + space. However, I would like to have a auto complete popup without using additional key.
Is this possible at all under spyder? If yes then how do I enable? I have searched quite a bit but it did not find any useful link on this topic.
What steps will reproduce the problem?
Open any python file and start importing modules and work normally. When I use os module and typr os.pat, the auto complete popup window should appear without pressing any key
What is the expected output? What do you see instead?
Same as mentioned above.
Versions and main components

Spyder Version: 3.2.3
Python Version: 3.6
Qt Version: 5.6.2
PyQt Version: 5.6
Operating system: Debian 9.2

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
IPython >=4.0    :  6.1.0 (OK)
cython >=0.21    :  None (NOK)
jedi >=0.9.0     :  0.10.2 (OK)
nbconvert >=4.0  :  5.2.1 (OK)
numpy >=1.7      :  1.13.1 (OK)
pandas >=0.13.1  :  0.20.3 (OK)
psutil >=0.3     :  5.2.2 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.7.2 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
sphinx >=0.6.6   :  1.6.3 (OK)
sympy >=0.7.3    :  None (NOK)
Edit:-
this link https://stackoverflow.com/questions/30640755/is-it-possible-to-set-spyder-auto-completion-without-pressing-the-tab-key say that it will be implemented in version 3. Is it implemented?

Is it implemented?

No, sorry, it'll be implemented in Spyder 4.

when will Spyder 4 be available? And when i choose code type "(" ,my code will be delect,for example:
a --> (a),must I type '(' twice? In rstudio, I can choose 'a' and type '(' to get '(a)'

Is it implemented?

No, sorry, it'll be implemented in Spyder 4.

I am running Spyder 4.0.0b1 on Anaconda in Mac OS X 10.13.6. I don't have popup autocomplete--is it a feature I have to enable in some way?

Running v 4.0 (Anaconda) (W10) - This works...

Tools -> Preferences
Completion and linting
Enable everything there
Set "Show automatic completions after characters entered" to your preference (I chose )
Set "Show automatic completions after keyboard idle (ms)" to your preference (I left default of 300)
Click Ok_

Should be good :)

Great news. I feel that it should be documented in the official documentation...


This change avoids needlessly recreating symlinks.

There are cases (i.e.: emergency situations) where we may want to chmod -w a data directory and recreating the symlinks systematically then prevents the server from being able to start up. This change inspects the symlink which is already present and avoids recreating it if it's already pointing at the right destination.

Looks good to me.

Squashed and merged https://github.com/FelixGV/voldemort/commit/49beabbc94755af04777a1d2e8ba2c3f7d31a6c9.


About convention used in rs-motion example

I am using the imu in L515 and I am studying the rs-motion example.  However, I fail to figure out the convention used in the example.
Firstly, in draw_axes(), the x-axis is drawn from (0,0,0) to (-1,0,0). Why is it not the common convention from (0,0,0) to (1,0,0).
y-axis has similar problem while z-axis follows the common convention.
void draw_axes()
{
    glLineWidth(2);
    glBegin(GL_LINES);
    // Draw x, y, z axes
    glColor3f(1, 0, 0); glVertex3f(0, 0, 0);  glVertex3f(-1, 0, 0);
    glColor3f(0, 1, 0); glVertex3f(0, 0, 0);  glVertex3f(0, -1, 0);
    glColor3f(0, 0, 1); glVertex3f(0, 0, 0);  glVertex3f(0, 0, 1);
    glEnd();

    glLineWidth(1);
}

Secondly, in the function render_camera(float3 theta) from class camera_renderer, the rotation direction are in different form for different axes. For theta.x, it is rotated by the z axis. For theta.z, there is an extra -pi/2. What are the reasons behind these implementation?
glRotatef(theta.x * 180 / PI, 0, 0, -1);
glRotatef(theta.y * 180 / PI, 0, -1, 0);
glRotatef((theta.z - PI / 2) * 180 / PI, -1, 0, 0);

Thirdly, in function process_gyro(), the gyro_angles are added to theta in the order of z y x. What is the reason behind?
theta.add(-gyro_angle.z, -gyro_angle.y, gyro_angle.x);

Lastly, in function process_accel(), how is the acceleration angle derived?
accel_angle.z = atan2(accel_data.y, accel_data.z);
accel_angle.x = atan2(accel_data.x, sqrt(accel_data.y * accel_data.y + accel_data.z * accel_data.z));

Hi @kuwt
The convention should be the same amongst all our products that have IMU similar to what is outlined in this blog:  https://www.intelrealsense.com/how-to-getting-imu-data-from-d435i-and-t265/
We do need to make modifications to the blog there as well as the readme.md of rs-motion to take into consideration the RealSense cameras that include IMUs.  The convention should be the same amongst the cameras.

Hi @kuwt
Is there anything else on this thread needed?
*If we don’t hear from you in 7 days, this issue will be closed.


Alejo

https://discord.gg/TzEdfYeZ
El mié, 24 nov 2021 a las 20:26, Alejo Viñeta @.***>)
escribió:

Merged #1 https://github.com/Franc-hub/Ticket-Reseller/pull/1 into main.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Franc-hub/Ticket-Reseller/pull/1#event-5668992699,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARO6UIOPIYKGBIBS57DAHLLUNU35TANCNFSM5IW2YOYQ
.


modelnum counting through different model instances

I discovered that if I create multiples of the same model, i.e.:
M = GasMALE()
M2 = GasMALE(DF70=True)

The model count is preserved throughout.  In the example below the modelnums should be [0,0,0] or [1,0,0] because there are only two Climb flight segments.  But because I created two GasMALE's the count kept going...
In [18]: solM2("V").items()[2][0].descr
Out[18]:
{'label': 'cruise speed',
 'modelnums': [2, 1, 1],
 'models': ['Climb', 'Mission', 'GasMALE'],
 'name': 'V',
 'shape': (5,),
 'unitrepr': "<Quantity(1.0, 'meter / second')>",
 'units': <Quantity(1.0, 'meter / second')>}

@mjburton11, let me or @bqpd if you have further questions about this.

@bqpd explanation was sufficiently clear.  Thanks.


Use San Francisco font

San Francisco is available in Safari as -apple-system but is not usable by name, like other fonts. Chrome does not support -apple-system, so we’ll use the secret, hidden name of the font for now.
This name is subject to change at any time. Hopefully we can use font-face: system in the future.

If you were to actually use the status bar, you'd see that this throws off the vertical alignment. :trolleybus: I've got some fixes for that written, but I'll probably go ahead and merge this, then commit my stuff before a release. Sound good?

Ha! I see the misalignment now. I was only checking the tab bar, search results, and settings page. Yeah, that sounds good to me.

Released in 2.1.2


Wrong API Version

Hi The example calls are showing the wrong API version and this version does not work.
GET https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupJobs/{jobName}?api-version=2017-07-01
If I user the equivalent as shown in the API docs proper then I get the results as shown above
https://management.azure.com/Subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroupName}}/providers/Microsoft.RecoveryServices/vaults/{{vaultName}}/backupJobs/{{jobName}}?api-version=2019-05-13

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

ID: ddd9b94e-1705-1f24-f761-564abf0551b8
Version Independent ID: 205c3adb-a49b-91b4-b2af-2a48dd74889b
Content: Azure Backup: Manage Backup Jobs using REST API
Content Source: articles/backup/backup-azure-arm-userestapi-managejobs.md
Service: backup
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

@MrDecisive Thanks for the feedback. We are looking into this and will get back to you shortly.

#reassign:pvrk

Acknowledged, the API versions have to updated. Thanks for the feedback. Will update at the earliest.

Updated all documents with latest, relevant REST API versions. Thanks for the feedback.
#please-close


add options to set user and database

Setting a specific user:database
If you want to use another database with another user
docker run -d -p 27017:27017 -p 28017:28017 -e MONGODB_USER="user" -e MONGODB_DATABASE="mydatabase" -e MONGODB_PASS="mypass" tutum/mongodb

You can now test your new credentials:
mongo mydatabase -u user -p mypass

Note: with mongo 3.x an admin user is also created with the same credentials
mongo admin -u user -p mypass

Thank you


Update npm tests

Updated the npm test file to reflect updated PlantUML build metadata (from 1.2022.3beta2 to 1.2022.6beta4).

By an apparently weird coincidence the build metadata just now changed to 1.2022.6beta5, so I have updated the tests accordingly.

Thanks for the update


Replace Bouncy Castle Blake2b

Description
Fix bug in existing Blake2b implementation.
Replace Bouncy Castle Blake2bDigest in MaskedField.
Changes are backwards compatible. The only difference is that the Blake2b hash values will be different per value due to the nature of the bug mentioned above.
No documentation changes are required.
Issues Resolved
Resolves https://github.com/opensearch-project/security/issues/4212
Testing
Relevant tests have been updated.
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thank you for the contribution @terryquigleysas!
This change looks good to me. For FIPS compliance, will all references to non-FIPS BC libraries be removed when compiling/running in FIPS mode?

For the rfksystems library, the repo does not have a License file but the README specifies Apache 2.0

@cwperks Do you mean that you expect to see a license file in https://github.com/rfksystems/blake2b ?
Both the README you reference and https://mvnrepository.com/artifact/com.password4j/password4j state it is licensed under Apache 2.0. Will the absence of an actual file prevent this from being accepted?

@terryquigleysas It's fine as long as the license is specified somewhere. I left a comment in case others were looking for the license. In my experience, open-source repos will typically have a separate LICENSE file containing the full terms of the license.
In opensearch core there's a gradle check called ./gradlew dependencyLicenses that requires licenses to be added to the core repo directly (Example in discovery-gce plugin) to ensure that new dependencies have acceptable licenses.

@cwperks Thanks, sounds good. Is there anything else I need to do?

Closing off this PR and replacing with https://github.com/opensearch-project/security/pull/4275 and bug https://github.com/opensearch-project/security/issues/4274


Feature request: per-container home instance setting for better multi-account support

I manage two separate Mastodon accounts: my main personal account, and an institutional account on a different instance which mostly posts, but occasionally needs to follow someone, boost something, etc..
I know that FediAct has a setting which prevents it from running on other instances if I am logged in there, and that solves a lot of problems. However, there are still two possible failure modes:

I want to follow an account on the second instance from my home instance account. I have navigated to the profile page on the second instance, where I am logged in, so FediAct is not running, so all my actions are executed on the second instance instead.
I want to follow an account outside the second instance from the second account. I have navigated to the profile page outside the second instance, so FediAct is running, so all my actions are executed on my home instance instead.

Currently I have solved this problem by logging into the second account only in a private window, and by disabling FediAct in private windows, but this is a bit clumsy.  It looks like Firefox's container tabs are designed to solve exactly this kind of problem, but FediAct's home instance setting appears to be global. It would be useful if it could be configured per container. Is this possible? I don't know if the container that a tab is running in is exposed in the API.
(Ironically, I think this would all be working smoothly if both my accounts were on the same instance -- each container would have separate cookies and be logged into a different account, but the instance setting wouldn't need to change.)

Hi, good suggestion. I will look into this, but I will priorize some other todos first (stability, bug fixes, smaller feature requests).
Thanks!

I'll close this in favor of #18 which also aims at better multi-account support.


View interface in MVI extending MvpView?

Hey @sockeqwe, Is there a reason why the View interface in MVI in Mosby should implement MvpView? Just because there is a Presenter in MVI too, I think mixing Mvi* and Mvp* prefixes is confusing. I would prefer to see MviView marker interface added instead.
I am talking about public interface MviPresenter<V extends MvpView, VS> extends MvpPresenter<V> {
Thanks

We had a similar discussion here:
https://github.com/sockeqwe/mosby/issues/296

Thanks! I see your point about giving users flexibility with the API. I am not advocating adding a render method to MviView just advocating a separate marker interface MviView.
If you had started Mosby with MVI and then added MVP, would you end up end up with MvpView interface for both? Unlikely. It seems like the interface was just re-used but the name just irks me. Sure I can create my own MviBasePresenter just to get around it—it just seems like more code I’d like to write to get around this small but visible (to me) issue.
Anyway, not a huge deal. Feel free to close this.

Yes, starting from scratch today maybe we would have something like MVI inteface and MviPresenter.
The historical reason why in Mosby-MVI  we have this relationship to MvpView and MvpPresenter is that there is a PresenterManager which is basically a Map<KEY, MvpPresenter<MvpView> that keeps Presenter during screenorientation changes and so on. As you see, unless we use raw types instead of generics, there must be some common super type for both, mvp and mvi ...
So what would you recommend to do?

I see! How about a parent interface Presenter to be extended by MvpPresenter and MviPresenter and parent marker interface View to be extended by MvpView and MviView?  Perhaps the new interfaces could live in the presentermanager module or a new module common or presentermanager could be renamed to common.


fix: Kustomize skip commit if nothing changed

Related: https://github.com/argoproj-labs/argocd-image-updater/issues/371

If a change to manifest is not synced, image updater will keep trying to update the image and try to produce a commit without any changes, this is resulting in error log and metrics which is noisy
This PR will skip commit for kustomization file when nothing is changed. this case can happen when the manifest in git is not synced

👋 It looks like a year has passed and the problem is still active, the merge is welcome 😄

@lukaszsurfer thanks for bringing that up. Will take a look.

Codecov Report
Attention: Patch coverage is 31.25000% with 11 lines in your changes missing coverage. Please review.

Project coverage is 75.37%. Comparing base (13f01ec) to head (fa22967).

Files with missing lines
Patch %
Lines

pkg/argocd/git.go
31.25%
8 Missing and 3 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #607      +/-   ##
==========================================
- Coverage   75.47%   75.37%   -0.11%
==========================================
  Files          31       31
  Lines        3144     3151       +7
==========================================
+ Hits         2373     2375       +2
- Misses        636      639       +3
- Partials      135      137       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I resolved the conflict, and can you all please take another look?


#hacktoberfest

If you are a first-time contributer or just want to participate in this October event,  Thank you for looking at this repo!

I wish to work on this. What exactly am I supposed to do?

@tezansahu check the readme of the project, that will give you good insight.

i would like to do

I would like to contribute

I would like to add my profile as well. PR #85

Hey! I added to this yesterday and it was on there last night, however, I've checked it again today and my profile link is missing. Did I do something wrong?

I Want to contribute

Hello!!!
I've made a PR with a fix of a little bug on the HTML and I've added my Profile to the list. :)

https://github.com/Nguyen17/Hacktoberfest-Sign-In/pull/517 Added my PR as well

#517 Added it!

Added PR #654

Hi, could you take a look at my PR #663 ? Thank you!

Happy hacktoberfest my friends, please merge my PR #683
Keep coding. Keep contributing.

Please merge my PR #719
Happy Hacktober Fest

please merge my PR
happy hactober fest!!!

added PR #888  .
please merge my PR
happy hacktober fest!!!

added PR.
please merge

Please merge my PR! Would love to get the t-shirt!

Added my profile link #1485

Added my profile to index.html #1599

I added my profile, Thank you for doing this. This is my first Pull Request and it is not as bad as I thought.


remove quotes from string values

Previously, Cycic would inject quotes into string variables which cannot be read properly. This removes all such quotes in facility forms.
@FlanFlanagan, do you think you can review this, merge it, and get a new windows binary up for users to download?

Could you take a look at mine. They work fine on my local build. I'd like to have those in if I am making a new distribution.
Also, do we need one for Linux as well?


Support further installation methods besides Helm Repositories

According to the official docs, the following methods exist:

A chart repository (as we've seen above)
A local chart archive (helm install foo foo-0.1.1.tgz)
An unpacked chart directory (helm install foo path/to/foo)
A full URL (helm install foo https://example.com/charts/foo-1.2.3.tgz)

I'm specifically interested in the 2 "local" variants mentioned above.
Looking at the implementation of InstallOrUpgradeChart, install and update in client.go we could provide a variant which accepts a local chart directory.
I can try to make contributions if there's a chance that this gets merged ;)

This is actually working as expected. See the docu update in PR #36


Uncaught TypeError: Cannot read property 'file' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.12.7
Electron Version: 1.3.13
System: Ubuntu 16.04.1
Thrown From: valhalla package, v0.14.0
Stack Trace
Uncaught TypeError: Cannot read property 'file' of undefined
At /home/geange/.atom/packages/valhalla/lib/doc-viewer.js:134

TypeError: Cannot read property 'file' of undefined
    at DocViewer.home (/home/geange/.atom/packages/valhalla/lib/doc-viewer.js:134:46)
    at DocViewer.load (/home/geange/.atom/packages/valhalla/lib/doc-viewer.js:23:18)
    at /home/geange/.atom/packages/valhalla/lib/valhalla.js:98:20
    at Workspace.module.exports.Workspace.openURIInPane (/usr/share/atom/resources/app.asar/src/workspace.js:501:22)
    at Workspace.module.exports.Workspace.open (/usr/share/atom/resources/app.asar/src/workspace.js:436:19)
    at atom-workspace.valhallaDocumentation (/home/geange/.atom/packages/valhalla/lib/valhalla.js:105:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:259:29)
    at /usr/share/atom/resources/app.asar/src/command-registry.js:3:59
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:587:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:382:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/share/atom/resources/app.asar/src/window-event-handler.js:106:36)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app.asar/src/window-event-handler.js:3:59)

Commands
  6x -3:13.1.0 core:backspace (atom-text-editor.editor.is-focused)
     -3:06.1.0 core:save (atom-text-editor.editor.is-focused)
     -3:02.8.0 editor:newline (atom-text-editor.editor.is-focused)
     -2:55.7.0 core:backspace (atom-text-editor.editor.is-focused)
     -2:50.9.0 core:save (atom-text-editor.editor.is-focused)
     -2:47.7.0 valhalla:surround (atom-text-editor.editor.is-focused)
     -2:46.1.0 core:undo (atom-text-editor.editor.is-focused)
     -2:41.1.0 settings-view:open (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -1:50.8.0 editor:newline (atom-text-editor.editor.is-focused)
  7x -1:44.8.0 core:backspace (atom-text-editor.editor.is-focused)
     -1:41.9.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
  2x -1:40.6.0 core:undo (atom-text-editor.editor.is-focused)
     -1:39.1.0 core:save (atom-text-editor.editor.is-focused)
     -0:00.1.0 valhalla:documentation (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "telemetryConsent": "limited"
  },
  "valhalla": {
    "firstTime": false,
    "vapiDir": "/usr/share/vala/vapi/:usr/share/vala-0.30/vapi/"
  }
}

Installed Packages
# User
autocomplete-xml, v0.9.4 (active)
language-vala-modern, v0.3.2 (active)
platformio-ide-terminal, v2.2.2 (active)
valhalla, v0.14.0 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.45.0 (inactive)
base16-tomorrow-dark-theme, v1.3.0 (inactive)
base16-tomorrow-light-theme, v1.3.0 (inactive)
one-dark-ui, v1.6.2 (active)
one-light-ui, v1.6.2 (inactive)
one-dark-syntax, v1.5.0 (active)
one-light-syntax, v1.5.0 (inactive)
solarized-dark-syntax, v1.0.5 (inactive)
solarized-light-syntax, v1.0.5 (inactive)
about, v1.7.0 (active)
archive-view, v0.62.0 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.13.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.4 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.2 (active)
command-palette, v0.39.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.202.2 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.60.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.2 (inactive)
markdown-preview, v0.158.8 (active)
metrics, v1.1.2 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.1 (inactive)
package-generator, v1.0.1 (inactive)
settings-view, v0.243.1 (active)
snippets, v1.0.4 (active)
spell-check, v0.68.4 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.2 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.103.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.210.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.35.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.54.0 (active)
language-clojure, v0.22.1 (active)
language-coffee-script, v0.48.0 (active)
language-csharp, v0.13.0 (active)
language-css, v0.40.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.43.0 (active)
language-html, v0.47.1 (active)
language-hyperlink, v0.16.1 (active)
language-java, v0.24.0 (active)
language-javascript, v0.122.0 (active)
language-json, v0.18.3 (active)
language-less, v0.29.6 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.37.0 (active)
language-php, v0.37.3 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.1 (active)
language-ruby, v0.70.2 (active)
language-ruby-on-rails, v0.25.1 (active)
language-sass, v0.57.0 (active)
language-shellscript, v0.23.0 (active)
language-source, v0.9.0 (active)
language-sql, v0.25.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.29.1 (active)
language-toml, v0.18.1 (active)
language-xml, v0.34.12 (active)
language-yaml, v0.27.1 (active)

# Dev
No dev packages

I change the path of the .vapi files. On ubuntu16.04.1, the files are under /usr/share/vala-0.30/vapi/.
And I press the ctr+alt+w, and I found something wrong. I also couldn't use the completition of the vala.

Hi, thanks for the bug report.
If you re-open the docs, does it crash again ?

Reboot the ubuntu and I re-open the file, there is no problem. Thank you very much.


how to cotribute

Hello!
i would like to contribute, but i need some kind of tutorial on how to start and what are prerequisites.

Hello @egdeeno !  Thank you for the offer to contribute.  I am working hard to get rhdl to the point that it can be effectively used and people can contribute.  The mental model is completely different than rust-hdl, and I need to write some docs and tutorials.  I expect to complete that in the coming month or two, at which point there should be enough docs for people to pick it up and contribute.  I suggest you monitor the Discord or the main page.  I will update there.
Thanks for your patience!


chore(deps): update to looplab/fsm 1.0.0

Description

How has this been tested?

Checklist

[x] changelog was updated with notable changes
[ ] documentation was updated

/e2e --mode standalone

End to end tests: :hourglass_flowing_sand: STARTING

why is that a breaking change ?

Good point, it's only internal to the orchestrator


remove unnecessary warning log message

This message is not needed because the IDP chooser page will take care of the case where a browser-based authorization flow did not request any specific IDP. For browserless flows (only allowed for the pinniped-cli client), the client must request a specific IDP (except in backwards-compatibility mode) because there is no browser in which to show the IDP chooser page. Failing to request a specific IDP in a browserless flow will result in a helpful error message being returned.
Release note:
NONE

The CI job is failing, but unlikely it is related to this change.

I'm not sure what is causing these integration test failure flakes. They all look the same, which is a dial tcp i/o timeout while trying to make a Kubernetes API call to a remote Kind cluster. Each of the four failed jobs encountered this problem only once (out of hundreds or maybe thousands of API calls made by the whole integration test suite), and each failed on a different Kubernetes API.
This is strange because it seems to be happening a lot lately, but did not happen often previously.


Running tests

First of all, big fan of spåK. Thanks.
My issue, however, is running tests on a module that uses App.localize. I'm getting the following error:
Error: Can not return App.instance(). App.run must be invoked first.

I've followed the docs and added the following to my test/support/setup.js:
import { TestApp } from "spak/providers";
TestApp.run();

I was hoping that this was enough to get the default implementation of App.localize, which would be perfect.
Any thoughts on how to get this working?

Closing. The issue was that I was invoking the component from outside of mocha's it. I moved my code around and it now works. Thx @pbouzakis for helping me debug this.

Anytime buddy :)


Disabling Bluetooth Crashes Runelite

I have noticed a recurring issue. Normally I will use Runelite while watching YouTube with my Bluetooth earbuds enabled. When I finish using my headphones and turn of Bluetooth on my laptop, Runelite crashes every time.
Steps to reproduce the behavior:

Enable Bluetooth under Settings > Bluetooth and other devices
Open Runelite
Log in and begin playing
Disable Bluetooth in Settings > Bluetooth and other devices
Runelite freezes and becomes unresponsive

Environment:

OS: Windows
RuneLite version: <IP_ADDRESS>
Launcher version: 2.1.0
Oldschool revision: Rev 190

Can't reproduce on my machine

I've reworked this myself. I can't reproduce it if I just enable and disable Bluetooth. It only happens when i have Bluetooth enabled and have been using a Bluetooth enabled audio device for an hour or more. Then, once I turn off the device and disable Bluetooth, it crashes the client.

This crash should generate a jvm_crash_pid file in your RuneLite logs folder. Can you upload that file?

I don't see a file with the _pid at the end. Perhaps my description was inaccurate. The client doesn't crash as in "close out" on me. However, the game becomes completely unresponsive. I can't click anywhere and the screen freezes up. I have waited a couple of minutes in the past but always end up closing the client and reopening.

Do you have GPU enabled?
Does minimizing and maximizing RuneLite after this apparent hang cause any change?
Is the full window (including title bar, sidebar, buttons, etc.) hanging at this time, or only the game window?

GPU is disabled.
If I minimize and maximize the window, it no longer shows the game. Instead, the game window becomes transparent and I see my Windows background.
Only the game window hangs.
Thanks for the continued support!


Lack of spaces in the noop message between user names

Notice: /Stage[main]/User::Jenkins/Group[xxx-xxxx]/members: current_value jenkinsuismail, should be jenkinsmanagehometrueensurepresent (noop)

Thanks for the report! We'll get this patched.

Hi @usmanismail,
Could you please provide the version of Puppet and Ruby you're running this against?
Thanks

Thanks, The versions are below.
puppet --version
3.7.3
ruby --version
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

It looks like I just need to implement the 'members_to_s' method, but I need to validate this on a live system.


Draggable handle not working in Firefox and Edge, not in Chrome

Hi there, hope this is the right place to ask.
We have an instance of angular-sortablejs working good in Chrome. This is the main gist of list component template:

      <customListItem *ngIf="!item.isEditing"
          [field]="item.field" [disabled]="actionsDisabled"
          (edit)="onListItemEdit(index)" (remove)="onListItemRemove(index)">
      </customListItem>

      <customEditItem *ngIf="item.isEditing"
          [field]="item.field" [uniqueId]="index" [disabled]="actionsDisabled"
          [allFields]="allFields"
          (confirm)="onListItemEditConfirm(index, $event)" (cancel)="onListItemEditCancel(index)">
      </customEditItem>

The custom item template is initially created within DOM, as item.isEditing is initially false, so *ngIf is set to true. Here are the drag options set, constants:
this.dragOptions = {
  onEnd: this.onListItemDragEnd.bind(this),
  handle: '.drag-handle',
};

Within list item component template, there's a button with drag-handle class:

      <button type="button" class="btn btn-xs btn-default drag-handle"
              [disabled]="actionsDisabled">

        Drag
      </button>

      <button type="button" class="btn btn-xs btn-primary" (click)="onEdit()"
              [disabled]="actionsDisabled">

        Edit
      </button>

      <button type="button" class="btn btn-xs btn-warning" (click)="onRemove()"
              [disabled]="actionsDisabled">

        Delete
      </button>

When in Firefox or Edge, no item seems to be draggable. The drag handle receives focus (on Firefox it looks bordered), but the item stays there. From inspection, I can see sortable-chosen class and draggable="true" attribute being set on item, but visually nothing changes.
Here there's a screencast trying to capture the issue:

Is there anyone aware of differences in behaviour among Chrome, Firefox and Edge on this side?

Hi @BrainCrumbz
I'm not sure there is any difference for the browsers here... What's done in angular-sortablejs is just a directive which operates with the model, it listens to the same events etc.
The only thing I can advice here is trying to debug the sortablejs original library files from the node_modules. That's how I usually solved things like this...
There is no automatic testing here, I can't really imagine how to correctly test the dragging behavior in different browsers automatically.

Hi @smnbbrv , thanks for clarifying (and excuse for late reply). To gain a better understanding, by any chance:

do you know about a ready-made plunker with angular-sortablejs? That's just to avoid starting from scratch, and avoid any issue that might be related to our project

do you have any pointer into sortablejs original source code, where to start debugging an issue like this?

Thanks in any case

Hi @BrainCrumbz
I didn't  create any yet, would be good to have one.
Debugging sortablejs is hard. It has many fallbacks, browser related code etc. so the issue could be nearly at any line... I'm not strong at the original library, maybe ask @RubaXa to help you out

Tried putting up a plunker, starting from one of the latest angular + typescript seed plunkers. As for other npm modules, angular-sortable.js is referenced from unpkg.com.
In app.ts, as soon as SortablejsModule is added to @NgModule.imports array, the app breaks and console is not helping in understanding what goes wrong. If you want to have a look, here it is.
Anyway, this of plunker is a side issue. Main point is still trying to reproduce the issue with a seed project.

@BrainCrumbz I couldn't have noticed that you use<EMAIL_ADDRESS>in the plunkr which is known for many issues. Have you tried to override it with<EMAIL_ADDRESS>

Hi there, thanks for pointing that out, will give that a spin right away. That version is the one I found when looking into angular-sortablejs own dependencies in its package.json. So, if I got it right, basically is the one our project is including because of angular-sortablejs.

No luck, runtime error shows up as soon as angular-sortablejs module is added to import list:

Error: (SystemJS) XHR error (500 Internal Server Error) loading<EMAIL_ADDRESS>patchProperty/desc.set/wrapFn@https://unpkg.com/zone.js@0.6.21/dist/zone.js:628:26
ZoneDelegate.prototype.invokeTask@https://unpkg.com/zone.js@0.6.21/dist/zone.js:225:23
Zone.prototype.runTask@https://unpkg.com/zone.js@0.6.21/dist/zone.js:125:28
ZoneTask/this.invoke@https://unpkg.com/zone.js@0.6.21/dist/zone.js:293:28
Error loading<EMAIL_ADDRESS>as "angular-sortablejs" from https://run.plnkr.co/yPl1nTMGWBPrEANT/src/app.ts

@BrainCrumbz no, I mean did you try it on your local machine to fix the original issue? :)

Tried this workaround in v1.5.0-rc1 and it worked. Not sure if that also works with the version currently shipping with angular-sortablejs.
BTW, it seems like angular-sortablejs installed package holds a local node_modules subdirectory, with a local sortablejs directory too. Is that intentional? Shouldn't that be listed as a dependency or peerDependency, and let npm install it?
Cheers

@BrainCrumbz the version ^1.4.2 is shipped with angular-sortablejs, so whenever non-rc version is released everybody will get a modern one.

I close this I guess

Still actual for me the version 1.7.0


Inaccurate 'unstake' balance

Description
Incorrect balance is displayed as max available amount for 'unstake'. Input sanitation prevents withdrawing full matured balance/
Solution

'unstake' input available balance should reflect current 'matured' balance
update input tooltip to indicate source of value (currently just says 'click to populate')

Screenshots

Notes
feedback via @aamirpashaa

resolved


fix unknown instruction error

When running this I get the error:
failed to solve with frontend dockerfile.v0: failed to create LLB definition: dockerfile parse error line 19: unknown instruction: &&

Have fixed that here

@HarleyB123 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Duplicate of #10604, closing in favour of that PR

Strange... I've just ran all my pipelines and after the modification it's showing a positive:


feat(runtime): add jest.mockModule

Summary
A start on #10025. Lots of stuff missing

[ ] Manual mocks (i.e. mocks from __mocks__ directories)
[ ] Docs
[ ] mocks without factories - not sure how to load them and determine types etc.
[ ] behavior when calling mock and doMock on an ES Module, and mockImport on CJS. I think it should throw?
[ ] jest.importActual
[ ] handle concurrent imports of mocks. Right now there's a race condition since it doesn't populate the cache immediately upon creating a mock. Need some sort of mutex

Test plan
I'll add more tests as we go

@SimenB as you said in https://github.com/facebook/jest/issues/9430#issuecomment-750349327 this is needed to implement the exports feature: do you know of any workaround meanwhile?

@SimenB as you said in https://github.com/facebook/jest/issues/9430#issuecomment-750349327 this is needed to implement the exports feature: do you know of any workaround meanwhile?

@SimenB as you said in #9430 (comment) this is needed to implement the exports feature: do you know of any workaround meanwhile?

This is not related to exports, what I meant is that that is the final missing piece. Not dependent on the feature in this PR. You can track exports support in #9771

Codecov Report

Merging #10976 (eac6673) into master (a03b6fe) will decrease coverage by 0.10%.
The diff coverage is 30.23%.

@@            Coverage Diff             @@
##           master   #10976      +/-   ##
==========================================
- Coverage   64.28%   64.17%   -0.11%
==========================================
  Files         308      308
  Lines       13480    13512      +32
  Branches     3286     3291       +5
==========================================
+ Hits         8665     8671       +6
- Misses       4106     4134      +28
+ Partials      709      707       -2

Impacted Files
Coverage Δ

packages/jest-resolve/src/index.ts
45.96% <0.00%> (ø)

packages/jest-runtime/src/index.ts
53.15% <30.95%> (-1.70%)
: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 a03b6fe...eac6673. Read the comment docs.

what's the state of this?

I currently don't have the motivation to work on this feature, so it's in hiatus until I get back to it. Others are of course free to pick it up 🙂

Codecov Report

Merging #10976 (9d2349a) into master (bba34bd) will decrease coverage by 0.12%.
The diff coverage is 24.44%.

@@            Coverage Diff             @@
##           master   #10976      +/-   ##
==========================================
- Coverage   68.95%   68.82%   -0.13%
==========================================
  Files         312      312
  Lines       16310    16345      +35
  Branches     4722     4726       +4
==========================================
+ Hits        11246    11250       +4
- Misses       5036     5067      +31
  Partials       28       28

Impacted Files
Coverage Δ

packages/jest-resolve/src/resolver.ts
55.82% <0.00%> (ø)

packages/jest-runtime/src/index.ts
56.74% <25.00%> (-2.04%)
: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 bba34bd...9d2349a. Read the comment docs.

@SimenB, is there a natural point to split up this PR / what remains? For example, if __mocks__ or jest.importActual is a significant amount of work, would it be preferable for a contributor to work on the rest first and land those things in a follow up PR?
I can take a look at helping with some of this tomorrow. A rebase, if it'd be quick for you, would be appreciated (assuming there might be conflicts to be resolved that I wouldn't have the context for).

Some of the items from above look required to merge this, but I wonder if some might be able to be moved to follow-ups? E.g. this could provide a lot of value without manual mocks support

Checking it in as jest.unstable_mockModule would be awesome and very much appreciated!

@benmccann landed that now, will release tonight or tomorrow (cest)

Out in https://github.com/facebook/jest/releases/tag/v27.1.1

Thank you so much!

@SimenB time to update https://jestjs.io/docs/ecmascript-modules , it still says "Please note that we currently don't support jest.mock in a clean way in ESM, but that is something we intend to add proper support for in the future. Follow this issue for updates."

@n0mer if you're up for a quick PR adding a small note that'd be awesome 👍

Are there any plans to continue this work in the near term? @SimenB

All work on ESM  is paused until most issues linked in https://github.com/nodejs/node/issues/37648 are solved.
(I got a message from a developer at Google last week about movement, so hopefully that'll actually move along very soon)

That said, happy to take PRs of course. But any personal effort is on pause until node's APIs are closer to stabilization.

The downside to jest.unstable_mockModule() right now is that it mocks the entire module.  This is maybe not a downside if that's what you're looking for.  It's really falling down for me right now though, because I only want to mock a few functions from the module.  This really needs a jest.importActual() to fill in that missing gap.  Trying to use jest.requireActual() on an ESM of course returns a 'Must use import to load ES Module' error, which one would expect to happen.  I'm getting to the point where even I might take a crack at implementing that functionality, but
a) For the past 26 years I've written in pure javascript for use in a browser environment (hence why I'm using ESM)
b) Am not super familiar with TypeScript outside of Haxe because I've always been able to do what I need to in pure JavaScript (And transpiling/bundling feels dirty since it's supposed to be a runtime script)
c) Am not super familiar with Node outside of using npm to pull down libraries, as the server side has always been Perl/PHP/C#/Python up until the last few years.  Of course this all means that using Jest has been a struggle learning opportunity.
At the very least it looks like the requireActual() implementation is happening in node_modules/jest-runtime/build/index.js, and that it is basically just calling requireModule() with a flag flipped to true.  The flag being flipped to true seems to only really effect if modulePath = manualMock or not, which then effects if you receive the mocked module or the actual module through black magic Node CJS shennanigans transforms.
From this I would guess that within the same file, the unstable_importModule() function (or further down the line loadEsmModule() function) could be extended to accept the same sort of flag solution.  However, once we get there, there is even more Pure ES Standards Javascript to CJS/Babel transform voodoo to decipher.  When I get to this point it starts bringing on too many Bad Memories of the JavaScript vs. JScript days and I get triggered and have to leave the room and have a lie down.
I guess if anybody was to take a crack at jest.importActual that's the place to do it (or wherever jest-runtime/build/index.js is actually transpiled down from).  Unfortunately, it's probably not going to be me, because ironically I find pure JavaScript easy (again, 26 years of practice), but find the modern workflow bloated and overly complicated. However, I hope somebody who understands the newer way of doing things finds the research helpful, or like Simen says, we wait for Node to support the standards and it doesn't take another few years.

The downside to jest.unstable_mockModule() right now is that it mocks the entire module. This is maybe not a downside if that's what you're looking for. It's really falling down for me right now though, because I only want to mock a few functions from the module. This really needs a jest.importActual() to fill in that missing gap. Trying to use jest.requireActual() on an ESM of course returns a 'Must use import to load ES Module' error, which one would expect to happen. I'm getting to the point where even I might take a crack at implementing that functionality, but
a) For the past 26 years I've written in pure javascript for use in a browser environment (hence why I'm using ESM) b) Am not super familiar with TypeScript outside of Haxe because I've always been able to do what I need to in pure JavaScript (And transpiling/bundling feels dirty since it's supposed to be a runtime script) c) Am not super familiar with Node outside of using npm to pull down libraries, as the server side has always been Perl/PHP/C#/Python up until the last few years. Of course this all means that using Jest has been a ~struggle~ learning opportunity.
At the very least it looks like the requireActual() implementation is happening in node_modules/jest-runtime/build/index.js, and that it is basically just calling requireModule() with a flag flipped to true. The flag being flipped to true seems to only really effect if modulePath = manualMock or not, which then effects if you receive the mocked module or the actual module through ~black magic~ Node CJS ~shennanigans~ transforms.
From this I would guess that within the same file, the unstable_importModule() function (or further down the line loadEsmModule() function) could be extended to accept the same sort of flag solution. However, once we get there, there is even more Pure ES Standards Javascript to CJS/Babel transform voodoo to decipher. When I get to this point it starts bringing on too many Bad Memories of the JavaScript vs. JScript days and I get triggered and have to leave the room and have a lie down.
I guess if anybody was to take a crack at jest.importActual that's the place to do it (or wherever jest-runtime/build/index.js is actually transpiled down from). Unfortunately, it's probably not going to be me, because ironically I find pure JavaScript easy (again, 26 years of practice), but find the modern workflow bloated and overly complicated. However, I hope somebody who understands the newer way of doing things finds the research helpful, or like Simen says, we wait for Node to support the standards and it doesn't take another few years.

I appreciate all the work done on Jest but I'm switching to vitest for first-class typescript and ESM support, including support for hoisted ESM mocks and importActual support


fixed bug for #345

fixed bug for print program usage when the program runs without any command-line args.

Codecov Report

Merging #347 into master will increase coverage by 0.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #347      +/-   ##
==========================================
+ Coverage   42.51%   42.86%   +0.35%
==========================================
  Files          12       12
  Lines       10175    10175
==========================================
+ Hits         4326     4362      +36
+ Misses       4708     4647      -61
- Partials     1141     1166      +25

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 5fd2b64...7d043ba. Read the comment docs.


isServerSide is not picket up in gatsby

After your release earlier I got over-excited and wanted to try it out: https://deploy-preview-305--gu-stav.netlify.app/
Apparently none of the tags are rendered server side, which indicates that isServerSide = typeof document === 'undefined'; is not picked up for some reason. Wondering why that could be. The gatsby team always recommends to reverse the check and do client side detection: isClientSide = typeof window !== 'undefined'. I don't know if this is related to the problem ...
I'll have a look at it tomorrow if @JoviDeCroock isn't faster :rocket:

Hey @gustavpursche
Is the code you used for this public? I can try and take a look, not sure if you have a plugin of some sorts to do the toString() part on the server side before you send down the html.
There is an existing one for react-helmet in our case we would just do toString and append it

Right. For some reason I assumed it would just work out of the box 🙃
Code is here: https://github.com/gustavpursche/stav.dev/pull/305

Seems to be a private repository, good luck on it though!
I've also pinged someone I know at gatsby if the toString() API is easily compatible with how they are doing things right now. If not I might change how that works and also provide component instances.
toString and toComponent but in theory I think toString is a good approach.

Seems to be a private repository, good luck on it though!

Ah damn. Forgot about it. Can make it public in a sec.
// gatsby-ssr.js

import { toString } from 'hooked-head';

export const onRenderBody = () => {
  console.log(toString())
};

prints:
true
{
  head: '\n        <title>undefined</title>\n        \n        \n      ',
  lang: undefined
}
{
  head: '\n        <title>undefined</title>\n        \n        \n      ',
  lang: undefined
}
{
  head: '\n        <title>undefined</title>\n        \n        \n      ',
  lang: undefined

So something doesn't seem quite right there.

toString and toComponent but in theory I think toString is a good approach.

For gatsby we'd then have to create components out of the strings, but I guess that's fine.

@gustavpursche I just cloned your repo and tried but useEffect doesn't seem to get called on the ssr render....
Adding
  useEffect(() => {
    console.log('I am sane');
  });

never pops up in my console

@JoviDeCroock Mmh, now remember I read somewhere that useEffect is a no-op in Gatsby.
That would mean this approach doesn't work with Gatsby I guess ...

I mean we'll have to find a way to effectively call what normally would be in an effect synchronously which is the reverse approach we are doing currently so I'm kind off thinking what the best approach would be.
Now we account for:
Child effect run
Parent effect run
Where as in a non deferred synchronous approach it would be
Parent run
Child run
If we add additional complexity for next.js we'll come to the conclusion that certain hooks can run multiple times with for instance prepass we need to hold a ref.
I just verified and the ref doesn't get lost so this would fix our issue:
const useTitle = () => {
  if (isServerSide && !hasMounted.current) {
    hasMounted.current = true; dispatcher.add()
  }
  ...normalCode
}

Put up a PR, going to think about this some more first before merging.

I did notice however that even though the title and meta are hydrated on client-side they were picked up by GoogleBot


Model is containing   with text and checkbox, checking on checkbox is not updating List view

I am using list view inside my modal. That list view is indicating items and check box. When I am checking item from list, I want that user can see the check box to be checked. I want to show check/uncheck action on list view, which is inside my modal.  Problem is that, its not rendering the list view of which is inside modal, on changing the state. Please help. Thanks in advance.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/model-is-containing-with-text-and-checkbox-checking-on-checkbox-is-not-updating-list-view
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

@facebook-github-bot close

@facebook-github-bot label Icebox

Im facing the same problem. Did you find any solution?
The link to productpains seems to be dead.


spring boot 1.5.3 + freemaker Chinese characters messy code

You can reprude this probleam by add
spring.freemarker.cache=false
spring.freemarker.charset=UTF-8
spring.freemarker.content-type=text/html;charset=UTF-8
spring.freemarker.expose-request-attributes=true
spring.freemarker.expose-session-attributes=true
spring.freemarker.expose-spring-macro-helpers=true
spring.freemarker.allow-session-override=true
spring.freemarker.suffix=.ftl

spring.freemarker.settings.datetime_format=yyyy-MM-dd HH:mm:ss
spring.freemarker.settings.default_encoding=UTF-8
spring.freemarker.settings.output_encoding=UTF-8
spring.freemarker.settings.number_format=0.##########
spring.freemarker.settings.template_exception_handler=ignore
spring.freemarker.settings.template_update_delay=0

add add a ftl file which title is chinese charset
finally i found the messy code is because
org.zalando.logbook.servlet.LocalResponse.getCharset()

return ISO-8859
close logbook off ，the problem resovle,please fix this bug, thank you

I have upload the demo project to my repository https://github.com/wyzssw/logbookbug
please just execute LogbookbugApplication in IDE, and open browse http://localhost:8080/test

I make a hand mistable ---- "close this issue ",please reopen

I ran you example with the 1.2.5 that includes a bugfix for the missing content type header:
HTTP/1.1 200
Content-Language: en-US
Content-Type: text/html;charset=UTF-8
Date: Thu, 15 Jun 2017 12:06:18 GMT
Transfer-Encoding: chunked

<!DOCTYPE html>

<
    <meta charset="utf-8">
    <title>有乱码</title>

有乱码

What I get back looks good to me. But it also looked ok before the fix. Can you verify on your side?


Clarification needed on what "administrator account" means

Page states
"sign in using the credentials for an administrator account in your organization."
This needs clarification on exactly which RBAC roles can achieve this task.  Thanks.

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

ID: 7108464d-597a-c79d-cac8-94e35d9dd3d0
Version Independent ID: ba0d3744-707d-c506-47f4-83519022d4cb
Content: Create and manage inactive mailboxes - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/create-and-manage-inactive-mailboxes.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@turnma Thank you for your feedback.AFAIK, compliance and global administrators can perform this action. I'm currently testing this with different admin roles and will update the document shortly.
Thanks
Sri

@turnma I was able to test this with only global and compliance admin roles. I have made changes to the document accordingly via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5835
Thank you again for your valuable feedback.
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @turnma Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


License missing

Hi.
I would like to package the semaphoreci-agent for use with self-hosted CI runners on NixOS in the nixpkgs repository. Currently, this repository is missing a LICENSE file, COPYING file, or SPDX license annotations in source files, meaning (unless I missed the indication elsewhere) it will have to be considered "unfree" and not be cached automatically by NixOS's caching infrastructure.
Also, my employer and your customer, Replit, would like to use NixOS self-hosted runners and this would make it easier on us.
Could you consider adding a open source software license file, or making a declaration of the license of this source code in this issue?
Thanks,
Ryan Mulligan

@ryantm thanks for flagging this up. We'll assess it, thanks

@ryantm license added in https://github.com/semaphoreci/agent/pull/245.


chore: swift lint

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


nest: 3.6 -> 3.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/nest/nest-simulator/releases.
meta.description for nest is: NEST is a command line tool for simulating neural networks
meta.homepage for nest is: https://www.nest-simulator.org/
meta.changelog for nest is: https://github.com/nest/nest-simulator/releases/tag/v3.7
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.7 with grep in /nix/store/zdfr1f2dgzl6kap9ad5lgss7vw56ywqr-nest-3.7
found 3.7 in filename of file in /nix/store/zdfr1f2dgzl6kap9ad5lgss7vw56ywqr-nest-3.7

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
nest
nest-mpi
python311Packages.nest
python312Packages.nest

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zdfr1f2dgzl6kap9ad5lgss7vw56ywqr-nest-3.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nest https://github.com/r-ryantm/nixpkgs/archive/04becf280aa0126cc3893089a14d187d00492e9f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/04becf280aa0126cc3893089a14d187d00492e9f#nest

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zdfr1f2dgzl6kap9ad5lgss7vw56ywqr-nest-3.7
ls -la /nix/store/zdfr1f2dgzl6kap9ad5lgss7vw56ywqr-nest-3.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

nest
nest-mpi
python311Packages.nest
python312Packages.nest

Maintainer pings
cc @jiegec @CyborgPotato for testing.

Nest loads and run :+1:

Addressed by https://github.com/NixOS/nixpkgs/pull/303624


Include nltk data uncompressed; restore support for pip-installing specific commits

Problem
#31 made it so that during sdist creation, nltk data files are unpacked from a tarfile and included in the nltk data path.
This works great, but introduces the following limitation: when nlp_primitives is installed in a way other than from an sdist/wheel/egg, the nltk data files aren't unpacked. This is the case for the following install paths:

Install from repo source: pip install .
Install from specific hash: pip install -e git+git@github.com:FeatureLabs/nlp_primitives.git@<hash>#egg=nlp_primitives, where <hash> is a git commit hash

The former case was handled by the additions we made to the makefile to unpack the tarball during developer env setup. But the latter case cannot be addressed in this manner. We've encountered this as we prepare to use the nlp primitives in evalml--we want to be able to pip-install a specific hash from this repo in our testing, and find we're unable to do so.
Fix
I looked into hijacking other setuptools commands like install and develop. This would work, but I wasn't able to get the pathing to work out correctly. When I ran pip install ., I saw the nltk data tarball was getting extracted to a temp directory instead of to site-packages in the virtualenv I was in.
Instead of digging further into that approach, I suggest we simply add the data here in uncompressed format. The compression wasn't saving any space -- the tarball and the unpacked directory are both currently around 53M.
Future
Rather than always including the data files in the package, we may want to look into providing both an "offline" installation path, where the data is included in the package, and an "online" installation path, where the data is downloaded during installation.

@rwedge good call, done!


Is there a way to access the thumbnails on a file?

How do I access the thumbnail end-point with this gem?

i know this is an old question, but I wanted to put this here for new people coming to this gem.  there is no thumbnail endpoint for files on the box api(they don't give you a url). I have asked the lead integration person at box to add this as an endpoint.. i wouldn't hold your breath.


Create ESLint rule

Is it possible to create a ESlint rule for the untilDestroyed operator? Which means that we check that every Observable in a Component should contain a untilDestroyed(this) and at the last position in the pipe chain.

You're welcome to create a PR. It'll be nice to validate that the decorator exists.

You can use this as a reference.

@NetanelBasal I believe that the @UntilDestroy() decorator is already checked at compilation. We could do it but what I really want to is detect Observable in every component and detect those who doesn't have the operator.
I already seen the work of @cartant but I have a hard time trying to understand how this thing works.

You are right, I forgot that we have protection.

FWIW, the rule linked above can be configured to use an alias - in addition to takeUntil - so you ought to be able to configure it to do what you want (if I understand you correctly). See the docs for the rule.
Also, something to be aware of is that ESLint rules are composable - see eslint-rule-composer and this post of mine. So if what you want to do can be represented by feeding configuration into an existing rule - i.e. to reduce boilerplate from more general, verbose config - that's possible.

Thanks, @cartant.
@Odonno I think that you want the following:
{
  "rxjs/no-unsafe-takeuntil": [
    "error",
    {
      "alias": ["untilDestroyed"]
    }
  ]
}

Is that right?

Well, kinda. The only missing part would be to also check Observable without pipe. @cartant Can you confirm you also check Observable without pipe.

@Odonno I think that the rule only works if you are using the operator. It doesn't check if you have it.

This rule is probably what you are looking for. The other just makes sure that the takeUntil - or alias - is in the right place. You probably want both, TBH. If prefer-takeUntil doesn't effect a failure if subscribe is called without pipe being used, that would be a bug.

Awesome rules. @Odonno you can use it. It'll be great if you can create a PR that adds this information to our README.
Closing the issue. Thanks.

@Odonno @NetanelBasal @cartant Are you successfully using this rule? I've attempted to install it in a project, but I'm unable to get the rule to fire as documented.
We've configured the plugin as such:
"rxjs-angular/prefer-takeuntil": [
    "error", {
     "alias": ["untilDestroyed"],
     "checkComplete": true,
     "checkDecorators": ["Component"],
     "checkDestroy": true
} ]

And using code similar to this in our components:
this.xyzService
  .pipe(untilDestroyed(this))
  .subscribe(data => {
  });

But the plugin throws errors for `Forbids calling 'subscribe' without an accompanying 'takeUntil'.
Any idea what might be going on? I'm happy to open a new ticket (here or in the rxjs-angular repo) if you'd prefer.

Hi @mattdsteele I'm facing the same issue, despite following the readme step-by-step. Have you got any progress eventually?


Updated app.js to correct destination index.js

Thanks for finding this. Will merge it :) actually there is a refactoring going where I will merge them too.


First attempt at writing down supported platforms

It turns out that we don't write down anywhere what operating systems we are really supporting. Here are some words for people to argue over.

people to argue over

👍
What does "support" mean?
Actually, I ask that in two senses:

You say we "support" CentOS 6 and various versions of macOS, but code is only required to work on CentOS 7. What does it mean to support platforms which our code might not work on?

Does "support" imply an offer from the project to provide support to folks who want to get our code working on one of the supported platforms? I'm sure the answer ought to be "no", but "support" is quite an ambiguous term.

"Support". What do we really mean? It's not entirely clear if "support" is the same for all of the stack. @fritzm could declare that Qserv only has to run on CentOS7 and ignore macOS and CentOS6. "Support" means we'll try to make sure our software works on all the supported platforms but if we are going down a rabbit hole trying to keep CentOS6 going we can drop it (dropping CentOS7 would be a lot harder to justify). Similarly, when SIP turned up on macOS as a project we were okay with not spending any effort on macOS for a few months.
So maybe "support" means "we will endeavor to ensure that our software works on all supported platforms" but we can decide to drop any non-CentOS7 platforms if they are becoming too much of a burden and we can drop specific subsets of "the stack" from some platforms.
"Supported" for actual releases is a definite statement that that suite of software that was part of that release definitely did work on those operating systems.

I've had another crack at the text.

I've rejigged it based on @ktlim's feedback.


Error - Decoding

G'day Richard, awesome work and i was super pleased to see that you'd refined it even more since its inception.
Curious, have you done much with the error reporting? It appears that the heatpumps have a vary array of E, H, P & F Fault codes, yet via RS485 it only outputs a single digit.
I've seen a few random E8's on the Baxi screen and looking at history the RS485 interface is reporting an error code of 9.

Hi,
nope, I did not dive into the error codes yet. It is in the back of my head to work on sometimes. But a pull request is very welcome! ☺

Hi @beccsjb,
I have just committed an update to heatpump.yaml where the faults (current, 1, 2 and 3) are mapped to an error code. For the current fault, I also created an extra mapping with the error description.