feat(pacmak): build all java targets at once

Improve build speed by building all jsii targets at the same time,
and using a special aggregate POM build for Java.

Improves speed by not unnecessarily re-reading jsii assemblies
for each individual build.
Improves speed by using an aggregate POM to build all Java
targets (can reuse JVM instances and compilation metadata by Maven).
Improves wall-clock time by building all languages in parallel.

Fixes #

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

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

(Obviously this will not compile with the current jsii version)

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

I removed the parallelism restriction. Can you re-review?

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


encoding/base32: buffered decoder expects padding even when NoPadding is set

A decoder created with NewDecoder and NoPadding expects to find padding at the end of the input, which differs from the behavior of Decode and DecodeString.
This bug is separate from #25296, which fixed the error result for the non-NoPadding case.
What version of Go are you using (go version)?
go version devel +ef24fd739b Thu May 10 15:40:01 2018 +0000 linux/amd64
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"

What did you do?
https://play.golang.org/p/k9HrTwJM29c
package main

import (
	"encoding/base32"
	"fmt"
	"io/ioutil"
	"strings"
)

func main() {
	withoutPadding := base32.StdEncoding.WithPadding(base32.NoPadding)
	input := withoutPadding.EncodeToString([]byte("foobar"))
	fmt.Printf("input %q\n", input)
	r, err := withoutPadding.DecodeString(input)
	fmt.Printf("DecodeString: %q %v\n", r, err)
	r, err = ioutil.ReadAll(base32.NewDecoder(withoutPadding, strings.NewReader(input)))
	fmt.Printf("NewDecoder  : %q %v\n", r, err)
}

What did you expect to see?
input "MZXW6YTBOI"
DecodeString: "foobar" <nil>
NewDecoder  : "foobar" <nil>

What did you see instead?
input "MZXW6YTBOI"
DecodeString: "foobar" <nil>
NewDecoder  : "fooba" unexpected EOF

Before the fix for #25296:
input "MZXW6YTBOI"
DecodeString: "foobar" <nil>
NewDecoder  : "fooba" <nil>

cc @zegl


Does deepstream.io provide any kind of rate limiting?

I am concerned about dos attacks against my deepstream.io servers. It's a public website, where user can register. Deepstream auth config allows only logged in user.
Can a malicious user register, and then connect to my deepstream server and launch million of events/records? How can I rate limit it per user/connection?
Can I also add limits on records? Size limits? Or number of records a user can create?

I guess I can run deepstream as npm module in nodeapp. I can add datatransforms to calculate rates, then in permission handler I can reject if rates are surpassed.

datatransforms is deprecated too :)
Hey @yasserf, any ideas how can I rate limit per connections/user? Any plugin hooks that will help. Can't find anything in docs.

You can do that inside of the permission handler, by that time it has the message (including the record data) and the userId and you can easily contain a map of all users and increment their usages and reset them on a second based timeout.
Deepstream first point of defense is at the connection layer, which means if you have millions of sockets being created at one go your memory will grow massively too. Concepts like whitelisting and banning should usually done at a higher level such as your loadbalancer, as with any other public facing server

Thanks. I will look into permissionhandler for rate limiting.


SyntaxError: Unexpected identifier

when i run npm run build having the error
/

What is your node version and npm version, I recommend using pnpm to manage dependencies

I recommend using at least version 18.x or 20.x of node

i use pnpm ，my pnpm version is 9.X , and node version is 18.x

I tried it locally and couldn't repeat your problem. Maybe you can delete node_modules and clear the cache, reinstall dependencies, or try to install a later version of node


Update guidance about using type="email" when asking users for an email address

Related documentation
The documentation and code examples for on how to ask users for an email address (under ‘Help users to enter a valid email address’) states:

setting the type attribute to email so that devices display the correct keyboard

Suggestion
The type attribute is used to achieve 2 things:

client side validation
showing the correct virtual keyboard, where applicable

On the first point, the Design System recommends only adding client side validation:

…if you find a user need for it. For example, because research shows it helps the user if you validate the information they’re providing as they type.

type="email" is recommended in this guidance in order to achieve the second point only.
Modern browsers now support the inputmode attribute, which addresses this need explicitly:

The inputmode global attribute is an enumerated attribute that hints at the type of data that might be entered by the user while editing the element or its contents. This allows a browser to display an appropriate virtual keyboard.

Evidence (where applicable)
Our service (Submit social housing lettings and sales data (CORE)) was recently audited by DAC. One of their assessors was using Dragon and found that the type attribute interfered with how they interacted with the input:

I found that I was able to access the ‘Email address’ field, but I was unable to dictate into the field unless I used keyboard commands which takes a lot more time to complete the process for example ‘Press r, Press o, Press b, Press full stop’ and so on until the whole email address has been dictated.

Their recommendation was to use type="text" inputmode="email" over type="email".

Interestingly Accessibility Support seems to suggest that data entry is supported by Dragon but it looks like that was last tested in August 2019 with Chrome 76 and Dragon 15.30. I imagine things might have changed since then.
Did DAC happen include the version of Dragon they were using, and what browser and browser version?

Would a PR updating the guidance be useful to get this moving?

I've done a little more digging into the spec and I think there are two other differences between type="email" and type="text":

Leading and trailing whitespace is trimmed from the value when using type="email", but not when using type="text". This affects both displaying a pre-populated value and the data sent when the form is submitted. (CodePen to illustrate)
Punycode in domains is handled when using type="email", but not when using type="text". If an email includes a domain with punycode, it'll automatically be translated to punycode and displayed correctly when presented back to the user. (CodePen to illustrate)

I'm not sure either of these should stop us from making this change, but we might want to consider whether any additional guidance is needed, especially if we want to publish any sort of communications encouraging users to make the change.
We're working towards another audit of GOV.UK Frontend at the minute – hopefully we'll learn more about this then, either by testing the 'new version' or by looking out for this issue cropping up in the audit report.


Code inside setInterval is not being run properly

I'm not sure if I'm missing anything here. My JS lib has to use setInterval to wait for a configuration to load. It works fine in browser. However, I'm not getting any code to run in Node.js environment with mocha-jsdom
Here's my code.
'use strict';
var chai = require('chai');
var expect = chai.expect;
var jsdom = require('mocha-jsdom')
var config = require('./config/');

describe('Sparrow', function desc() {
  jsdom();
  var sparrow;

  beforeEach(function beforeEach(done) {
    window._Config = config; // Simulating
    module = require('../src/module');
    done();
  });

  it('should fire event', function it() {
    console.log(window._Config);
  });
});

And this is my source
function Init() {
  var ms = 0;
  var wait = window.setInterval(function() {
    console.log(window._Config);
     window.clearInterval(wait);
  }, 100);
}

Init();

I striped it down to a simple version. When I run the test, the loop runs indefinitely. I was hoping that the setInterval will be cleared after window.clearInterval was called. However, if I moved window.clearInterval outside. It worked.

Apologies, this is my fault. I have to use Sinon to fake the timer.


Spaces in scripts path raise Error

If the script is saved in a path with a space, this error is raised:
Traceback (most recent call last):
File "", line 14, in
IOError: [Errno 2] No such file or directory: 'path with spaces'
I know it's stupid to have spaces in a folder name, but unfortunately, that's how "Google\ Drive" is set up.
I like to store my scripts in my Gdrive because it's an easy way to work from home and at work seamlessly...
It would be nice if this can be fixed, not a top priority, though.

Thank you for this report, will have a look as soon possible.


Use orginal tsv to download wav files or use the reformatted version?

Thanks for your sharing first. I feel confused when running audioset_download.py. Which tsv should I use, the original tsv or the reformatted version in GoogleAudioSetReformatted?

Hello!
Sorry for the confusion - the reformatted version is required for functions in audioset_scripts.py, to download the audios with audioset_download.py you need to make a file listing all necessary files (segments) line by line, like this:
--4gqARaEJE_0
-0BIyqJj9ZU_30000
-0jeONf82dE_21000

The scripts will then download the videos with given YouTube-ids (before the last underscore) and trim the 10s interval starting with the time given after the underscore (time in ms).


🛠 fix: Change oembed to dynamic player

This is the proposed change mentioned in #328.
As I couldn't find any document on how to test, I'll let the GitHub action do the lifting.

@ku1ik Do you mind take a look?


DOC: Fix installation instructions using venv/pip

Reference issue

What does this implement/fix?
Fixes a typo in the installation instructions for virtual env in "Building from source for SciPy development".
Additional information

Hi @aglebov - thanks for the PR! For reference, next time you are doing a docs-only PR you can skip some of the CI checks we run here (saving resources and time) by including skip commands in your commit message - see https://docs.scipy.org/doc/scipy/dev/contributor/continuous_integration.html#skipping
Since this is straightforward, I'll merge without waiting for CI. Hope to see you around!


tf.contrib.data: No op named OneShotIterator in defined operations

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
TensorFlow installed from (source or binary): binary (nightly build from May 23rd)
TensorFlow version (use command below): v1.2.0-rc0-172-g9e25de3
Bazel version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce:

python3 save.py
python3 load.py

Describe the problem
I'm playing around with the new tf.contrib.data stuff because it looks awesome and can make a lot of my code a lot simpler. However, I'm trying to save and restore a graph that contains these new ops. Saving works fine, but loading doesn't work. If I inspect the saved file, it seems to be serializing everything correctly, I recognize the structure of all the data set ops I added in the code so that seems fine. In the case of the below example, I'm getting an error No op named OneShotIterator in defined operations when trying to load the graph again.
Source code / logs
save.py
import tensorflow as tf

dataset = tf.contrib.data.Dataset.range(10)
dataset = dataset.map(lambda x: x + 2)
batched_dataset = dataset.batch(4)

iterator = batched_dataset.make_one_shot_iterator()
next_element = iterator.get_next()

tf.add_to_collection('next', next_element)
tf.train.export_meta_graph(filename='graph', as_text=True)

load.py
import tensorflow as tf

tf.train.import_meta_graph('graph')
next_element = tf.get_collection('next')[0]

sess = tf.Session()

print(sess.run(next_element))

load.py output
Traceback (most recent call last):
  File "/home/ede/test/load.py", line 3, in <module>
    tf.train.import_meta_graph('graph')
  File "/home/ede/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 1683, in import_meta_graph
    **kwargs)
  File "/home/ede/tensorflow/lib/python3.5/site-packages/tensorflow/python/framework/meta_graph.py", line 504, in import_scoped_meta_graph
    producer_op_list=producer_op_list)
  File "/home/ede/tensorflow/lib/python3.5/site-packages/tensorflow/python/framework/importer.py", line 283, in import_graph_def
    raise ValueError('No op named %s in defined operations.' % node.op)
ValueError: No op named OneShotIterator in defined operations.

Here's the saved graph file (in text format)
graph.txt

I think this is a general problem with ops defined in the tf.contrib namespace, because they are lazily registered on the first use of any tf.contrib module. If you add the statement dir(tf.contrib) (or something else that uses tf.contrib) before calling tf.train.import_meta_graph(), it should work.

Wow really. Will try that first thing tomorrow.

Yes, that fixed it. Thanks!

@EdeMeijer Could you please share the code that made it work? Because I face similar problem for a quantized graph of inception resnet model. I get .
I get "ValueError: No op named QuantizedAdd in defined operations"
I tried using "dir(tf.contrib)". However, it didn't work for me. I am not sure if I am using it right way.

@rajnamitha the Python file I used it in literally starts like this
import numpy as np
import tensorflow as tf

# Force load contrib ops
dir(tf.contrib)

and the rest is just ordinary TensorFlow code. If you're doing the same thing and still running into your problem my advise would be to open a new issue.

@EdeMeijer : It is still not solving the problem in my case, so opened an issue. Hope to get a solution. Thanks for your information :)

I get this: ValueError: No op named SSTableReader in defined operations when trying to freeze resnet_v2 graph.
Searching by all tensorflow code doesn't find 'SSTableReader' anywhere. Some help, please?

@1int : I didn't face "No op named... " error while freezing though. But maybe it is similar case as mine, where I got "No op named..." error while loading the quantized graph.
With what helped me, I suggest you to build tensorflow from latest source code rather than binary version.
As maybe you are using latest script  for freezing the graph but the tensorflow version you are using could be a older one. Building tensorflow from source code could help to avoid this problem.

I get the same error-
ValueError: No op named SSTableReader in defined operations.
while running tf.train.import_meta_graph on the meta file. The dir(tf.contrib) solution did not help.
I am using a pre-trained model from-
https://github.com/openimages/dataset
Thanks.

@1int @sxs4337 What was the source of the graph/metagraph containing an SSTableReader op? That is not part of the TensorFlow API, so it sounds like whoever built that graph inadvertently included some proprietary/custom ops in the graph....

I had used the graph from pre-trained model on OpenImages dataset. I was able to get a workaround as discussed in this post-
https://github.com/openimages/dataset/issues/21
Thanks.

OK, judging by the comments that issue, it's a bug in the released graph, which shouldn't contain an SSTableReader op in the first place. Glad to hear that you've found a workaround!

@EdeMeijer your solution worked for my VGG16 graph: https://gist.github.com/eggie5/7d9c31c08462ec42ed8d927f2c0c3e55
import tensorflow as tf
dir(tf.contrib) #hack per https://github.com/tensorflow/tensorflow/issues/10130
with tf.Session() as sess:
    tf.saved_model.loader.load(sess, [tf.saved_model.tag_constants.SERVING], 'model/export/1509295446/')
    print [n.name for n in tf.get_default_graph().as_graph_def().node]

Before I was getting that same error as you.


How can I use this on a tablet?

For a while now I've been "manually" exploring the idea of "consuming" our notes. Today, we consume them tiktok-style on our cellphone or tablet, why not do the same with our Obsidian notes?
I found your plugin and it works OK on the computer (I set up CTRL+arrows), but how can I transfer this use to an android tablet, i.e. navigate from one note to another just by swiping my fingers, tiktok-style?
Is that possible?

Great suggestion. This would make browsing around between notes a bit easier on mobile devices.
Currently I use an Obsidian Templater template for my daily notes to generate navigational links
(See GitHub: Obsidian Templater Templates)
So far I haven't found any useful documentation on implementing custom gestures for the mobile app.
I only found an older plugin implementing two finger swipe navigation here:
https://github.com/liamcain/obsidian-swipe-navigation
However, a quick test on reimplementing this plusin shows it only works on the desktop app.
Note that the Obsidian mobile app already uses swipe gestures extensively.

Single swipe will open left/right side menu
Two finger swipe will navigate forward/backward

Perhaps they restricted changing this behaviour on the mobile app, or I missed something.
Feel free to share any other ideas or suggestions.


ci: release with app token

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

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 78.14%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
595

Relevant Lines:
735

💛  - Coveralls


Astronomy data may overlap on small screens

Something is overwritten (v0.7). See screenhot.
sony xperia5, android10

Thanks, I'll look into adding an alternative layout for small screens here.

This has been fixed in the new release (0.7.1)

Thank you, you are realms fast.
Gesendet von ProtonMail mobile
-------- Original-Nachricht --------
Am 3. Sept. 2020, 21:28, Kyle Corry schrieb:

This has been fixed in the new release (0.7.1)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Dark and Light Mode Integration

dark and light mode switch for the wildlife website to enhance user experience, especially for users who prefer different viewing modes depending on the time of day or environmental conditions.
This contribution is part of Hacktoberfest 2024.

Can you assign this issue to me?


We can't afford to create one file per job on the master

It takes 45min to create 5000 children in the AWS job store. The creation of a file is relatively expensive in the AWS job store. I need to verify this but according to CJ there are five round trips involved in storing a file.
We cannot afford to maintain per-job state outside of the primary job store, especially if that state is written by the master.
I have the feeling that this is all caused by the Job/BatchJob dichotomy which may simply be a bad design choice.
Once we eliminate the file-per-job problem we can go ahead and batch up to 25 items (jobs) in SimpleDB by using BatchPutAttributes instead of  PutAttributes. This will need a separate issue as batching would require delaying writing to the store. The atomicity guarantee would still hold but the durability one would be violated by this. There are additional considerations like handling reads on the same node or another one while a batch is pending.

6 round trips required for 1 call to _makeJobWrappers, 4 of which are for storing the file: 1 initial registration of the file, then 2 (at a minimum) for the multipart upload, then another registration to update the file's version.

Also, this happens on the worker, not the master.

As discussed on 8/8, we will implement the following improvements:
Toil will not call  JobStore.create() followed by JobStore.update() when creating the wrappers, but instead invoke a single method. Alternatively, create will be changed to not persist right away. This is a commonplace pattern in the persistence layer of an application.
Secondly, we will provide batch-style methods to the JobStore API that allow for 1) persisting multiple jobs  at once and 2) saving multiple smallish files at once. The AWS job store will then implement these methods by 1) attempting to batch  SDB writes using BatchPutAttributes , 2) parallelize writing multiple batches using a thread pool and 3) inlining a small file in an SDB item as opposed to storing it in S3 and writing the version reference to SDB.

See #355 and #351. Closing this one.


fix: improve code and comments from feedback request

:tada: This PR is included in version 2.0.1-beta.82 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Be free of the GIL!

This should only be looked at after #269 and #270. Summary of what it does is below.
I suspect this is the best place for these calls. I originally had them in the execute() function itself, but this is more complete.
The only worry is that it may affect people's code who by default make python calls from their cells...in which case they would need to toss in a ECTO_SCOPED_CALLPYTHON whre they make the call. The official ecto stacks however do not seem to require this anywhere and I only do so in one cell of mine, so it's a rare occurence.
If this is an issue, this could be shifted to a new api so it doesn't effect existing usercode. For instance an execute_threaded() function or similar.
.....................
This lets ecto pipeline processing be free of its evil overlord, the GIL. That is, you can now schedule different plasms in different threads...e.g. some pseudocode:
# construct some plasms
image_scheduler = ecto.Scheduler(image_plasm)
odometry_scheduler = ecto.Scheduler(odometry_plasm)
image_thread = threading.Thread(name="image_thread", target=image_scheduler.execute)
odometry_thread = threading.Thread(name="odometry_thread", target=odometry_scheduler.execute)
image_thread.start()
odometry_thread.start()
image_thread.join()
odometry_thread.join()

Of course, inside a cell's process() call, you can always grab the GIL momentarily if you need to using the opposite macro...ECTO_SCOPED_CALLPYTHON.

I'll add a test and some documentation and lets see how this shapes up.

Ok..so this has meant me digging into details a bit more - this threaded behaviour I'm replicating appears to be something that the scheduler's execute_async function is supposed to support, but ever since I started using this, it doesn't. i.e. from the docs:
execute_async(niter)
These functions are the same as the blocking ones above, except they start an execution thread in the background and return immediately.

running()
Returns true if the execution started by execute_async() is still running.

stop()
Stops the background graph execution at the end of the current process() call and block until it is stopped

and this code snippet from the same documentation has never worked as intended:
s = Sheduler(p)
s.execute_async()
time.sleep(0.5)
s.stop()
s.execute_async()
assert s.running()

So the question is, when and why this stopped working?
And with what I'm doing here - should I just renable threaded execute_async calls inside the c++ instead of doing it from python like I have in c2a24a513?

| So the question is, when and why this stopped working?
Looks suspiciously like it disappeared in dd8fef0e where new thread creation in execute_async disappeared?

And with what I'm doing here - should I just renable threaded execute_async calls inside the c++ instead of doing it from python like I have in c2a24a5?

My preference would be to manage it from python spawned threads - that is where the user scripts the flow - i.e. graphs, plasms and scheduling. That is the easiest place to let the user design various kinds of scheduling like I have in c2a24a5.

@vrabaud at this point I would rename exec_async to just exec_implementation or something similar, add python handles to give some asynchronous capability and update the documentation to reflect the current state of threading support in ecto (it's currently way out). What are your thoughts?

feel free to do so. I know multi-threading got removed at some point,. I am not sure it impacts what you are describing.

Ach, rebasing always brings trouble! :boom:
Anyway, it's done. Ignore the earlier commits up to 'Be free of the GIL', they were brought in by the rebasing.

Scheduler updates
run*() methods now release the gil before executing
Refactored execute_async -> prepare_jobs

Releasing the gil enables multithreading capability by default and users can always recapture the gil in their cells if they wish (I do so in some of my cells).
The refactored name works around the confusion I had with it to begin with (it doesn't actually execute). This is less misleading I think, and we can reserve execute_async for later when I'd actually like to have it start a background thread and run jobs immediately as the documentation formely hinted at and similar to what execute does.

Tests

multiplasm test script, that also tests the connected_inputs_only feature.

minor fixes for the scheduler related scripts to keep everything running

Documentation updates

Revamped existing scheduler documentation

Added notes on the multiplasm scheduler

Another tutorial on utilising optional inputs

@vrabaud anything you think this needs to help move this along?

time is all I needed :) Sorry, it all looks good to me. Thx for the doc, it really helps.

and it's finally released

:neckbeard:


Setup some gitStream actions against JVM team PRs to assess this tool

The actions I've added will:

Categorize change with labels for each platform (for only a subset of directories, not the complete list yet) and with a label if the build script is touched.
Add table describing code experts in a comment.
Make complex changes (>20 files, > 45 estimated time to review) require 2 approvals.
Add estimated time to review label.
If a PR includes TODOs, add a comment announcing this and request changes.
If a PR is a source change that lacks tests, add a comment announcing this.

These are incomplete but can be expanded and modified later.  This PR is aimed at getting a variety of actions up and running so we can see if they are helpful.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Additional Patient Agent Attributes

Using PRSB core information standards mapped to FHIR

The PRSB Core Information Standard https://theprsb.org/standards/coreinformationstandard/ defines how to
share health information in a structured manner. The site contains a link to an Excel spreadsheet which presents the types of information that can be collected about a patient - an extract is shown to the right.
This kind of information can be included in the Alpha data model, by mapping to an appropriate FHIR resource type.
Blue rows mark the start of a segment of information (Patient demographics, GP practice), it is possible to map these to FHIR resource types ‘Patient; and ‘Practitioner.’ We believe it is also possible to map other core information segments to FHIR resource types.
Since the core information standard is mappable to FHIR, it can be used as an input to the Alpha data model. We have documented in the code base how various FHIR resources can be supplied to the model when initialising the patients and environments. This information can then be utilised by the Intelligence Layer.
The core information standard may introduce some extension fields to the respective FHIR resource, as well as some additional constraints (e.g. Patient demographics must have a name field). For these reasons, the FHIR patient health record that is generated by the model may not be Core Information Standard compliant (even when it is FHIR compliant).
In order to make it compliant, it would be possible to build the relevant rules into the FHIR report generator function; we also
recommend building a validator for outputs.


Convert setup.py/cfg to pyproject.toml (#1116) (#1122)

Convert setup.py/cfg to pyproject.toml

Add VERSION file

Set python version to >=3.7

!verified


Where are the top 20 most important features of the classifier?

It's a very nice job and useful for academic research and industrial application. I wonder what features play a pivot role in the stage classificaiton, and the paper said the top 20 most important features are illustrated in Figure S2, but I can't find Figure S2 in this URL(https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>6165v1.full.pdf). Could you give me some instructions?
Thanks a lot!!!

Hi @chenxuesongTHU,
You can find the figure importance here: https://elifesciences.org/articles/70092/figures#fig1s7. The importance was calculated using this script: https://github.com/raphaelvallat/yasa_classifier/blob/master/05_SHAP_importance.py
Thanks,
Raphael

I got it. Thanks again for your contributions to Sleep Research! The nice coding style makes readers enjoy it.


[backport] Add float16 support for scatter_add

Backport of #1684

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 47ed3173de1c7582b6abe582f81bdca94702f11e, target branch v5) succeeded!

LGTM!


Reconcile multiple years of data in XBRL instant tables

In some of the XBRL tables representing instant facts, there's more than one value for date associated with a single report_year. For example:
pis_dbf = pd.read_sql("f1_plant_in_srvce", ferc1_engine)
pis_xbrl_duration = pd.read_sql("electric_plant_in_service_204_duration", ferc1_xbrl_engine)
pis_xbrl_instant = pd.read_sql("electric_plant_in_service_204_instant", ferc1_xbrl_engine)
pis_xbrl_instant.date.value_counts()

2021-12-31    208
2020-12-31    206
Name: date, dtype: int64

How should we deal with this? What does it mean?
In the DBF tables there are sometimes "this year" and "last year" data reported next to each other for comparison. Is that what's going on here? If so, then we only need to keep the current year of data.  Need to identify which tables report this way in DBF and compare them to the tables with more than 1 year of data in the XBRL to see if they correspond.

If they do correspond then we should probably explicitly drop the "previous year" data when we are merging the instant and duration data in the XBRL transformers, rather than implicitly dropping those records in the merge.
Also check that this issue isn't coming up in the duration tables with start_date and end_date.
Log when we drop this data in the pre-concatenation XBRL processing.

At least in the plant_in_service table the two years of data that are reported are completely identical in both the instant and duration tables. Though strangely there are 206 records in one year and 208 in the other.
ferc1_settings = pudl.settings.Ferc1Settings(
    tables=["plant_in_service_ferc1"],
    years=[2020, 2021],
)

raw_dbf = pudl.extract.ferc1.extract_dbf(
    ferc1_settings,
    pudl_settings,
)

raw_xbrl = pudl.extract.ferc1.extract_xbrl(
    ferc1_settings,
    pudl_settings,
)

pis_xbrl_instant = raw_xbrl["plant_in_service_ferc1"]["instant"]
assert (pis_xbrl_instant.groupby(["entity_id", "date"]).nunique() > 1).sum().sum() == 0

pis_xbrl_duration = raw_xbrl["plant_in_service_ferc1"]["duration"]
assert (pis_xbrl_duration.groupby(["entity_id", "start_date"]).nunique() > 1).sum().sum() == 0

If we want to allow aggregation within a given report year, or we want the XBRL & DBF data to be directly comparable, then we need to translate the end-of-last-year and end-of-this-year data which is currently showing up as single columns with different date values in the instant table into separate columns that correspond to beginning of this year, and end of this year.
If we were to keep both of those columns, they would be duplicative, since we should be able to calculate the end-of-year balance based on the starting balance and accumulated adjustments across the year (additions, retirements, etc.).
If we want to keep the database normalized (within a given year) then we should store just the beginning balance and the deltas (there's another kind of aggregation happening elsewhere, within accounting categories, but here we're just concerned with the temporal aggregation across a year).
For development & validation purposes it'll be useful to keep all these start/end of year and categorical aggregated values so we can check that our aggregations reflect the reported numbers. So don't drop them yet.

Not all of the data in the duration and instant tables line up with each other perfectly... There are a few entity_ids that show up ONLY in the instant table -- i.e. they report starting and/or ending balances, but no additions, retirements, etc.
Maybe this is what we would expect for a utility that has plant in service but didn't modify it at all during the year.
There are also a few utilities that don't report a starting balance, but do report changes and an ending balance. In that case it's hypothetically possible to calculate what the starting balance should have been.

Weird missing data issues aside, I think it's clear what the meaning of the multiple years of data is: end of year balances, for this and last year, which get reported in the same year, but have different instantaneous timestamps / dates associated with them.
We're not currently adopting the instant vs. duration model of time. Maybe we should think about that at some point, but in our current data model we want to be able to easily aggregate data within or potentially across report_year values. In the other tables we're already dropping the start/end dates and keeping report_year. To get starting/ending balances into a single report year I think want to:

convert end-of-last-year rows into starting_balance columns
convert end-of-this-year rows into ending_balance columns
concatenate the instant and duration tables along the column axis based on shared (entity_id, report_year) index values.

This arrangement will allow us to look at a given report_year or series of report_years, and apply the many individual additions / retirements etc to the starting balance and calculate an expected ending balance that we can compare to the reported value (hopefully getting the same value), once we've done the reshaping of the concatenated XBRL table into a tidy format.
It seems like working this into the TableTransformer classes will require a pretty different path in the process_xbrl() method, but hopefully this general path can be applied to many of the tables that require reshaping.


Can I add questions?

Just curious. Didn't see a specific guide on adding new questions and test.

Welcome! problem-specifications/…/CONTRIBUTING.md is probably what you are looking for & possibly already found ;-)


Need a way to get the flat note count within a measure

Currently, Measure.noteCount does not take into account all the notes contained inside a deeply nested Tuplet. This causes issues with the way Measure.ModifyTie is implemented, due to the way range checks are performed.
It would also be useful to know how many notes are available within a measure give the way Measure.note(at:) is implemented.
This issue is to propose the creation of a Measure.noteFlatCount property to make the total note count available.

Yeah. I found that it would be useful to have this type of property on Tuplet which is what would be needed for this change. Need to figure out the right naming.

Make sure to write a test that exposes this issue in Measure.ModifyTie


folding doesn't seem to work with the many-star style

folding with alt-ctrl-[ and alt-ctrl-] works in this style:
* bake cake
  * buy flour
  * buy sugar

...but not with this style:
* bake cake
** buy flour
** buy sugar

Oh, and thanks for organized!

I’ll look into and see what I have to do to get atom to recognize stacked stars - at this point you’re getting what Atom is giving you by default, which I suspect is their default implementation for text.
In the meantime, I’m just about to release visibility cycling in 0.8.0. This has pretty much the same behavior as visibility cycling in emacs+orgmode and it works with stacked stars.

Thanks, that explains it.


re-structure files and directories in the repository

Create a typical structure for a go repository. It will be looks like:
gohello/
+-- go.mod
+-- gohello.go
+-- cmd/
|   +-- gohello/
|       +-- main.go
+-- internal/
    :

Close with #3.


[Automation] Generate Fluent Lite from Swagger netapp#package-2024-07

[Automation] Generate Fluent Lite from Swagger netapp#package-2024-07

/azp run java - netapp - mgmt - tests

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


[Enhancement] Support for Multiple Data Sources

Pebblo (as of 0.1.12 version) supports single data source. Having support multiple data sources within single RAG application would be a good feature.
Description:
When I have multiple data sources to be used in my app, I should be able to see all those data sources and their details in the pebblo report.
As part of this feature, following changes would need to be done in the report:

Report Summary: Aggregate details about all data data sources.
Top Files With Most Findings: Add new column to show to which data source the file belongs.
Data Source: It would show snippets about all data sources.

In order to support multiple data sources, we need to update out folder structure within scratch space as follows:
.pebblo/
       /<app-name>/
                  /metadata/metadata.json             => app name and run_id to load_id mappings.
                                                         This file will be protected by file lock.
                  /<run-id>/
                           /metadata/metadata.json    => All the details needed to generate report.json.
                                                         This will include details for all successful loads.
                           /report.json               => This is input to reports module.
                                                         This will include details for all successful loads.
                           /pebblo_report.pdf         => Report pdf including details for all successful loads.
                  /<load-id>/
                           /metadata/metadata.json.   => All the details needed to generate report.json.
                                                         This will include details for all successful runs.
                                                         This is only for backward compatibility
                           /report.json               => This is input to reports module.
                                                         This will include details for all successful runs.
                                                         This is only for backward compatibility
                           /pebblo_report.pdf         => Report pdf including details for all successful runs.
                                                         This is only for backward compatibility


chezmoi: 2.7.4 -> 2.9.0

Motivation for this change
New release: https://github.com/twpayne/chezmoi/releases/tag/v2.9.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Please also update sha256 and vendorSha256, otherwise it will simply use the old source to build.

Not sure why the ryantm bot hasn't automatically updated this recently, perhaps it is overloaded.  I don't see any recent attempts in https://r.ryantm.com/log/github/chezmoi/

Please also update sha256 and vendorSha256, otherwise it will simply use the old source to build.

fixed :)

Result of nixpkgs-review pr 147829 run on x86_64-linux 1

1 package built:

chezmoi


Update CRAW_Main.c

Memory allocation for the buffer string in grabData has been freed after its usage.  Strings name->valuestring and id->valuestring are duplicated using strdup to allocate memory for them and freed at appropriate points in the code to prevent memory leaks.

Not on purpose, I didn't capture it when I tried to copy/paste.


Speed-up HTML escaping by using equal sized entities

By using codepoint entities like '&' → "&", we have a much smaller lookup table (58 bytes instead of 29× pointer size ~= 232 bytes). This makes the cache happy, and the benchmark run about ~20% faster.
$ cargo bench --bench escape
Escaping                time:   [3.4087 µs 3.4126 µs 3.4168 µs]
                        change: [-19.790% -19.580% -19.354%] (p = 0.00 < 0.05)
                        Performance has improved.

This PR is based on #53.
TODO:

[x] fix all the expected outputs

That's great, thanks!


cast to expr

Codecov Report

Merging #2308 (b44c4eb) into master (6187a78) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #2308      +/-   ##
==========================================
- Coverage   25.74%   25.74%   -0.01%
==========================================
  Files         190      190
  Lines       32513    32515       +2
==========================================
  Hits         8372     8372
- Misses      24141    24143       +2

Impacted Files
Coverage Δ

src/DesignCompile/CompileType.cpp
22.54% <0.00%> (-0.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 6187a78...b44c4eb. Read the comment docs.


Move assets directory to Iterative-Achemy/rasayana-art repo

Delete empty assets directory from /rasayana repo and add assets directory to /rasayana-art repo.

Task completed.


Video File Issue?

I have successfully implemented react-native-share-extension into my IOS project. I got image path and its extension while sharing the image from photos app but I cant get the path if I share the video file from Photos app?
const {type, value} = await ShareExtension.data();
ShareExtension.m FIle:
if([videoProvider hasItemConformingToTypeIdentifier:VIDEO_IDENTIFIER]) {
videoProvider = provider;
//index += 1;
[videoProvider loadItemForTypeIdentifier:VIDEO_IDENTIFIER options:nil completionHandler:^(id item, NSError *error) {
NSURL *url = (NSURL *)item;
index += 1;
[itemArray addObject: @{
@"type": @"movie/mp4",
@"value": [url absoluteString]
}];
if (callback && (index == [attachments count])) {
callback(itemArray, nil);
}
}];
}
Bu the above statement does not return the path for video File?
Please, can you share the working code for video file

i ve used this package  with all new features with react native greater than 0.60 support  react-native-receive-sharing-intent


Transform the Count enum values into private constants

Hides implementation details for the C, Objective-C and Swift APIs.

Awesome! Will merge tomorrow

Changing this a bit before landing. Some RN stuff was depending on the count so I moved the defines into YGEnums.h


PowerToys installer try to install older Net Core version even if a newer is installed

Microsoft PowerToys version
0.61.1
Running as admin

[X] Yes

Area(s) with issue?
Installer
Steps to reproduce

Install the Desktop Net Core 6.0.8
Install the PowerToys 0.61.1

In log file :
[1364:0514][2022-09-02T12:49:42]i338: Acquiring package: DotnetRuntime6, payload: DotnetRuntime6, download from: https://download.visualstudio.microsoft.com/download/pr/dc0e0e83-0115-4518-8b6a-590ed594f38a/65b63e41f6a80decb37fa3c5af79a53d/windowsdesktop-runtime-6.0.7-win-x64.exe
[...]
[1364:0514][2022-09-02T12:49:42]e313: Failed to acquire payload: DotnetRuntime6 to working path: C:\WINDOWS\Temp{5046A225-1378-4867-9559-A85CA2F7FC6B}\DotnetRuntime6, error: 0x80072ee7.
[1364:18A8][2022-09-02T12:49:42]e000: Error 0x80072ee7: Failed while caching, aborting execution.
[...]
[1364:18A8][2022-09-02T12:49:42]i500: Shutting down, exit code: 0x2ee7
✔ Expected Behavior
PowerToys successfull installation if a newer version of Desktop Net Core is installed.
❌ Actual Behavior
Installation failed in my case because I don't have internet connection as admin and don't want Net Core 6.0.7 for security issues.
Other Software
Microsoft Net Core

Thanks for the report.
Indeed, we only check the presence of a dotnet version we're going to attempt to install if it wasn't found and rely on its installer to bail if the newer version is found. In case you don't have an internet connection, you're stuck with this issue.
We perform the check in such suboptimal way due to WiX Bootstrapper limitations: we can't just launch dotnet --list-runtimes and parse its output like we did before when we've had a custom bootstrapper, and there's no single registry key for dotnet 6+ which we could retrieve to get the latest version installed.
Apart from the making the dotnet's ExePackage non-vital, I'd go with maintaining a list of future possible dotnet versions to check agasint, e.g.:
<util:FileSearch Variable="HasDotnet608"
    Path="$(var.PlatformProgramFiles)dotnet\shared\Microsoft.WindowsDesktop.App\6.0.8\System.Xaml.dll"
    Result="exists" />
<util:FileSearch Variable="HasDotnet609"
    Path="$(var.PlatformProgramFiles)dotnet\shared\Microsoft.WindowsDesktop.App\6.0.9\System.Xaml.dll"
    Result="exists" />
<util:FileSearch Variable="HasDotnet6010"
    Path="$(var.PlatformProgramFiles)dotnet\shared\Microsoft.WindowsDesktop.App\6.0.10\System.Xaml.dll"
    Result="exists" />
<util:FileSearch Variable="HasDotnet610"
    Path="$(var.PlatformProgramFiles)dotnet\shared\Microsoft.WindowsDesktop.App\6.1.0\System.Xaml.dll"
    Result="exists" />

So in that case if we'd release PowerToys while the newest dotnet version is 6.0.8, the installer could handle 2 additional dotnet patch releases and a single minor one.

Another solution would be to

migrate from WiX altogether.

@jaimecbernardo thoughts?

Let's check if better powershell support is in wix's roadmap first?
I think the current longterm plan is to get a good self-containment scenario for all our utilities and try to ship a self-contained .net version with PowerToys. This would fix most installer issues like this.

Thanks for your feedback.
I don't know the "WiX Bootstrapper" but I'm pretty sure you can execute some custom scripts for detections or something like that ?
The second option is to work only with the MSI, which permit all custom detections you can imagine.

I also encountered the same problem: no matter what version of. Net is installed, I can't run PowerToys correctly.
What should I do to use PowerToys normally?

@yuyoyuppe appart from rare cases .NET is installed at the same path all the time.
Couldn't you just check the folder names for "6.X.X" >= "6.0.current_requirement"?
Just a guess. I have very little knowledge of this stuff.
But in an offline environment I cannot really control the installed version of .NET.

Of course, it'd be easily done if Wix bootstrapper allowed arbitrary code execution. It does not, thus my post explaining a possibility of circumventing those restrictions.

Latest developments (like #14374 and #19761) would make this issue obsolete, am I right?

I think this has been fixed, going to close. Let us know if you still see this happening!


[WIP] Improve GlobalCIDR auto-allocation mechanism

Idea is to create a configmap while deploying broker
and then populating it with the auto-assigned GlobalCIDR
while joining the cluster.
Closes: #299

This is handled via the following PR - https://github.com/submariner-io/submariner-operator/pull/501


Documentation for setting up with OKTA

I was going through the readme to setup the MVP site locally. Would you be able to provide a simple guide (screenshots) of what settings you expect with OKTA for a new developer account?

This article gave me some clue as what to do: https://www.linkedin.com/pulse/implement-okta-sitecore-federated-authentication-part-meng-han-li-1d

then, there is this blog :) https://navansitecorenotes.blogspot.com/2021/12/how-to-setup-okta-for-sitecore.html

@navancommits Perhaps you can submit a PR with details you learned from your post.

Closed as this repository is being archived.
This has been addressed in the new repository.


Remove Sendable conformance on Bundle from SwiftPM

Foundation added this conformance on their side in main (https://github.com/apple/swift-corelibs-foundation/pull/4963) and release/6.0 (https://github.com/apple/swift-corelibs-foundation/pull/4978).
rdar://129599679

@swift-ci test

@swift-ci test macos


git push hangs at Launching...

Sometimes when I do a git push deis, the deploy will be successful but the command won't terminate and just hangs at Launching.... deis v1.6.1 on AWS.
What might be causing this problem and is it a deis bug or incorrect configuration on my side?

Did you perhaps change the ELB timeout? We set it to 20 minutes. The deploy itself usually takes a few minutes where nothing is sent over the wire, so ELB or other load balancers will kill the request to the client.

This could also due to the controller detecting that the container is not in a running state (the container exited early). We should be capturing these cases, but that may not be the issue at hand here :)

Oh, it seems the deploy did indeed fail but it's really hard to tell it did:
$ deis logs --app=testnet
2015-05-27T22:10:46UTC deis[api]: williamcotton deployed fcad676
2015-05-27T22:13:18UTC testnet[cmd.1]:
2015-05-27T22:13:18UTC testnet[cmd.1]: ><EMAIL_ADDRESS>start /src
2015-05-27T22:13:18UTC testnet[cmd.1]: > psy start -n bsync -- node app/cli
2015-05-27T22:13:18UTC testnet[cmd.1]:

Also,
$deis releases --app=testnet
=== testnet Releases
v32     30 minutes ago               williamcotton deployed fcad676
v31     Tue 12 May 23:18:51 2015 CST olalonde added DEBUG_COLORS, changed DEBUG

If I deis open, the server is running correctly.
However, if I ssh into deis and run fleetctl list-units, I see
$ fleetctl list-units
...
testnet_v31.cmd.1.service       9c69bab3.../<IP_ADDRESS> active          running
testnet_v32.cmd.1.service       9c69bab3.../<IP_ADDRESS> inactive        dead
...

$ fleetctl journal testnet_v32.cmd.1.service                                                                                master ✗
-- Logs begin at Tue 2015-05-26 02:11:15 UTC, end at Wed 2015-05-27 22:45:29 UTC. --
May 27 22:13:13 ip-10-21-2-122.ec2.internal sh[18416]: 77af3279dddd: Pulling metadata
May 27 22:13:13 ip-10-21-2-122.ec2.internal sh[18416]: 77af3279dddd: Pulling fs layer
May 27 22:13:16 ip-10-21-2-122.ec2.internal sh[18416]: 77af3279dddd: Download complete
May 27 22:13:16 ip-10-21-2-122.ec2.internal sh[18416]: 77af3279dddd: Download complete
May 27 22:13:16 ip-10-21-2-122.ec2.internal sh[18416]: Status: Downloaded newer image for <IP_ADDRESS>:5000/testnet:v32
May 27 22:13:16 ip-10-21-2-122.ec2.internal systemd[1]: Started testnet_v32.cmd.1.
May 27 22:13:18 ip-10-21-2-122.ec2.internal sh[19256]: ><EMAIL_ADDRESS>start /src
May 27 22:13:18 ip-10-21-2-122.ec2.internal sh[19256]: > psy start -n bsync -- node app/cli
May 27 22:13:18 ip-10-21-2-122.ec2.internal docker[19357]: testnet_v32.cmd.1
May 27 22:13:19 ip-10-21-2-122.ec2.internal docker[19366]: testnet_v32.cmd.1

In terms of developer UX this isn't great but not sure if it's a "bug".
Is there any way for me to find out

why is testnet_v32.cmd.1.service "dead"

how to know a deploy failed next time without resorting to fleetctl list-units

It seems the problem was that the docker container immediately terminated because psy (https://github.com/substack/psy) runs processes in the background.

Hmm... Maybe we should add logs directly inside an application's systemd unit to notify that the container has shut down and is booting up as ExecStartPre and ExecStopPost entries.


main.FATAL Mounting file system: Mount: mount: running fusermount: exit status 1#012#012stderr:#012fusermount: fuse device not found, try 'modprobe fuse' first#012

s3 bucket not mounting on my instance but when i use "aws s3 ls" all s3 buckets are showing
error message:"main.FATAL Mounting file system: Mount: mount: running fusermount: exit status 1#012#012stderr:#012fusermount: fuse device not found, try 'modprobe fuse' first#012"

I have a similar issue.
The following command is executed:
sudo /root/gopath/bin/goofys [s3 bucket] [dir] -o allow_other,--file-mode=0777,--uid=500,--gid=500,--profile=s3

Checking the logs yield the ff.:
/root/gopath/bin/goofys[20220]: main.FATAL Mounting file system: Mount: mount: running fusermount: exit status 1#012#012stderr:#012fusermount: fuse device not found, try 'modprobe fuse' first#012

You are missing the fuse kernel module which is required by all fuse programs. Are you running in docker? If yes, you probably need to pass through /dev/fuse into your container.


New Project - v1 badges list

Shall we create a new project under badges for v1 badges list and shift all our available resources and conversations over there instead on the issue #8

@nodejs/badges

Sounds good, sure. We could also create milestones and stuff.


Layout in different browser sizes

Make the website work with different window/monitor sizes

Unable to make website adjustable to layout in time

Unable to make website adjustable to window size in time


CONTRIBUTING.md: update pull request guidelines

see #596

I've updated, changing the line to
The subject line should be a one-sentence summary, and should not include the word *and* (explicitly or implied).


Improve error reporting and use pre-defined token

https://github.com/jupyterlab/jupyterlab-desktop/issues/238 demonstrates that for an unknown reasons the Jupyter Server does not get setup correctly for some users. It is very difficult to debug currently, so I tried to address this in multiple ways:

removing one of the modes of failures which was in retrieving the token (which if not found could lead to promise rejection and error screen state)
displaying the actual error that led to the error screen (and encouraging reporting of these errors)
allowing users to change environment with the selector introduced in https://github.com/jupyterlab/jupyterlab-desktop/pull/317
rewriting the error message which was incorrectly suggesting that it was due to server not being in path, where in reality there are several code paths which could lead to the promise rejection and that screen; instead it is now more accurately titled "Jupyter Server Initialization Failed"
I also removed the "Install Jupyter" link, because the JupyterLab Desktop now ships with a builtin conda environment so it is redundant and it was directing users to rather not very useful generic Jupyter website (so they could end up installing Notebook and getting frustrated that it did not help).
I added code for parsing the actual version of Jupyter Server that got started, but end up not using it for now. We should consider if we want to add a check on the version at this level too - it could help against some inconsistent environments - but it can wait for another PR.
The server standard error output is now logged into the console. We may want to change this in the future (or make it optional, only for debugging) but it seems important for this stage of development.

I also restored the XSRF checks as I do not see any reason for having those disabled when the token is properly set up.
Tested by manually adding a reject(new Error('test')):

And selecting a non-Python path fusing the first button:

The environment selector works well too:

The CI errors are not related to this PR, but to lack of peer dependency pinning. Yarn is installing the latest versions of peer dependencies which causes compilation issues. Merging https://github.com/jupyterlab/jupyterlab-desktop/pull/337 will temporarily solve this issue, but we should find a way to better locking of peer dependencies.


add a way of getting the Crypto object

web_sys understands how to acquire Crypto from a Window or from a WorkerGlobalScope, but neither of these work in a worker context.
It turns out to be possible, but it's not obvious how to do it, so it's convenient to have the worker crate provide this access.
I find this very useful when doing JWT validation; I prefer letting the runtime handle the details of low-level cryptography.

From the peanut gallery (just sorta looking through some issues)
I think this is more like the sort of thing that could/should be in optional community-driven wasm crates, rather than part of worker core
For prior art, see gloo: https://github.com/rustwasm/gloo - idea is they are very useful Rusty wrappers around things like timers, event listeners, etc. Actually, I think adding a crypto crate to gloo would be a perfect fit :)
One reason I'm saying this is that it's not really enough to just get the Crypto web_sys handle, you're then going to want SubtleCrypto and the web_sys API stops being very helpful, need Rust-friendly representations of the methods and objects.
For example, the web_sys API takes a plain JS object for generateKey - and from a Rust perspective, we'd want to have this be typechecked, maybe an enum with only the allowed algorithm variants - and then inside of that enum again you're hit with web_sys taking an Object with a Rust-unfriendly API for, say, AesKeyGenParams
Getting all of this right is a bit opinionated, and will add a bit of bloat to worker projects that don't need/use it - but I really do think it's a great idea for the ecosystem as a whole, would love to see a crate that does this (and I do agree it's common enough to be a candidate for gloo) :)

btw, to access properties on the global namespace, you don't really need direct access to globalThis, you can just create bindings via js_namespace property of wasm_bindgen. At the top level that namespace's parent will be global, so it "just works" :)
See for example here: https://github.com/cloudflare/workers-rs/pull/529/files#diff-6401a7b68b5c3371692a10163e6e09c80b32bdaa0d9ceb1ae4ce49f12c7a70f6R50

it's not really enough to just get the Crypto web_sys handle, you're then going to want SubtleCrypto and the web_sys API stops being very helpful, need Rust-friendly representations of the methods and objects.

All of that exists in the web_sys crate. And it works-- I am using it in a project already. The only missing piece is to get access to the web_sys::Crypto object. There is a standard way of doing this, via web_sys::Window::crypto() or web_sys::WorkerGlobalScope::crypto().
But neither of those are available in the workers runtime-- meaning this is a workers-specific problem. So I think the workers crate is the right place to address it.

All of that exists in the web_sys crate

Can you show me an example? As far as I can tell, the web_sys crate expects plain objects and strings, there's no type safety. An idiomatic Rust API would use enums and structs to make it impossible at compiletime to do things like pass an invalid algorithm string or config object

There is a standard way of doing this, via web_sys::Window::crypto() or web_sys::WorkerGlobalScope::crypto()

Are you sure that works, and that you don't need to rather call web_sys::window() or global() (i.e. what you did here is just the standard thing you'd do anywhere)?
I agree with the headspace btw - it would be wonderful to have more Rust-friendly apis built on top of web-sys/js-sys (in fact I have my own personal grab-bag in awsm-web, very familiar with the pain point!)
I'm just raising the question of whether this crate in particular should be limited to creating bindings for worker-specific apis (like durable object, digest stream, etc.,)
For me it's just a question though, I'd be cool with it going either direction :)

I don't have public code to share, but I am successfully using the SubtleCrypto functions in both a browser and worker environment. The web_sys layer is pretty basic, and it may be missing some desirable idioms (e.g. enums for the algorithms, curves, etc.) but it's still perfectly usable.
Even a higher-level wrapper would still need access to the Crypto object to be able to call the underlying functions, which is the part that's accessed differently in a worker context, so this change is still useful.


[bug] command + args composition appears incorrect

Describe the bug
Related to #729, I'm unable to inspect how moon is composing the command to execute, so I can't provide further context
We're running a command to initiate a deployment with a bin that takes quite a few arguments. In an effort to clean up the presentation in tasks.yml, I put all of the args into an array.
Steps to reproduce
We used the args array as follows:
  deploy:
    command: 'cdk'
    args:
      - 'deploy'
      - '--all'
      - '--require-approval=never'
      - '--app "deploy --target=$projectRoot"'
      - '--output $workspaceRoot/.cdk/$project/$timestamp'

But running this command results in an error from cdk --app is required either in command-line, in cdk.json or in ~/.cdk.json. That arg is clearly defined, so something else must be awry. I figured that I would fall back to a single arg in a big string:
  deploy:
    command: 'cdk'
    args: 'deploy --all --require-approval=never --app "FORCE_COLOR=1 pnpm exec deploy --target=$projectRoot" --output $workspaceRoot/.cdk/$project/$timestamp'

And that worked. I then attempted to break that out as:
  deploy:
    command: 'cdk'
    args:
      - 'deploy --all --require-approval=never --app "FORCE_COLOR=1 pnpm exec deploy --target=$projectRoot" --output $workspaceRoot/.cdk/$project/$timestamp'

And a different error was thrown: Unknown command: deploy --all --require-approval=never --app "FORCE_COLOR=1 pnpm exec deploy --target=/Users/user/code/rally/rally/infra/core" --output /Users/user/code/rally/rally/.cdk/core/$timestamp
Given the different behaviors observed, I would suspect there is some composition logic that's not quite right.
Expected behavior
Args to be assembled and the command to be called successfully.
Screenshots

Environment
MacOS Ventura M2
Additional context

Understood. That's 0 for 2 for me missing things already documented. I'll be more diligent moving forward.

alright for anyone who runs across a similar use case: node_modules resolution doesn't apply to subcommands.


Install a global state management tool

Definition of done

[ ] User store can be accessed from any component in the RN app
[ ] username of the logged in user is available globally
[ ] function that returns if someone is logged in is available globally

Hints
Two options:

React hooks
Redux
maybe another one @Rebal67 knows about

https://www.reactnativeschool.com/comparing-redux-zustand-and-mobx-state-tree
Zustand for simplicity


Resolving changes caused by merge

File structure and file duplication was caused by merge. Created new branch in order to resolve this.

Merge completed


Update back to top function

Kindly assign this under hacktoberfest.
@Elijah699
the function is added to three pages you mentioned.
Thank you

I've reviewed and the functionality works well, thank you for contributing @Rajput-xv .


On chain plus one contract

The lsp is not working and I can't make hoogle to show me the PlutusTx docs, so I hope the draft for AdditionValidator works. With the draft I have enough to begin the off-chain counter part in #4

Subsumed by #6


We actually need to create the metric directory ourselves

https://bugs.chromium.org/p/chromium/issues/detail?id=989219
@hardikgoyal

CR+1, would be good to have Hardik confirm.


Javascript cookies set in cross-site iframes are not detected/considered by PSAT

Describe the bug
Javascript cookies (those set with document.cookie) set in cross-site iframes are not being detected by PSAT. They are considered by the browser, though.
To Reproduce
Steps to reproduce the behavior:

Create the https://domain-aaa.com/topframe.html file with this code:

<!DOCTYPE html>

Create the https://domain-bbb.com/iframe.html file with this code:

<!DOCTYPE html>

Open Chrome via helper chrome-3pcd-ps.
Open the page https://domain-aaa.com/topframe.html.

Obs: I have set up a similar test lab here: https://louren.co.in/PSAT/issue645/topframe.html
Expected behavior
The cross-site iframe tries to create a third-party cookie without the Partitioned attribute and can't because chrome-3pcd-ps has 3pc disabled. This is the expected behavior and even the DevTools console logs the try in the issues tab. The problem is that the try should be detected/logged by PSAT, but it doesn't.
Screenshots
Screenshot 1: DevTools issues panel evidencing that there was a failed attempt to create the 3PC without Partitioned attribute:

Screenshot 2: PSAT didn't detect the failed attempt to create the cookie:

Desktop (please complete the following information):

OS: MacOS 14.4.1 Sonoma
Browser: Chrome
Version: 124.0.6367.80 (Official Build) (arm64)

Additional context
PSAT System Information:
Open Tabs: 1
Active Extensions:
Google Docs Offline: ghbmnnjooekpmoecnnnilnnbdlolhkhi
Privacy Sandbox Analysis Tool: ikodlagpencphdljdpelmcajjlloiomb
Chrome Version: Version <IP_ADDRESS> (arm64)
PSAT Version: 0.7.0
OS - System Architecture: MacOS (arm64)

Hello @lcrespilho
Thanks for bringing this to our attention! You’re correct, PSAT’s JavaScript cookie detection (specifically the document.cookie ) is currently limited to the main website frame and doesn’t extend to sub frames (iframes).
We recognize this as a bug and are actively working on a fix. The solution will be included in an upcoming version, so stay tuned!

Describe the bug
Javascript cookies (those set with document.cookie) set in cross-site iframes are not being detected by PSAT. They are considered by the browser, though.
To Reproduce
Steps to reproduce the behavior:

Create the https://domain-aaa.com/topframe.html file with this code:

<!DOCTYPE html>

Create the https://domain-bbb.com/iframe.html file with this code:

<!DOCTYPE html>

Open Chrome via helper chrome-3pcd-ps.
Open the page https://domain-aaa.com/topframe.html.

Obs: I have set up a similar test lab here: https://louren.co.in/PSAT/issue645/topframe.html
Expected behavior
The cross-site iframe tries to create a third-party cookie without the Partitioned attribute and can't because chrome-3pcd-ps has 3pc disabled. This is the expected behavior and even the DevTools console logs the try in the issues tab. The problem is that the try should be detected/logged by PSAT, but it doesn't.
Screenshots
Screenshot 1: DevTools issues panel evidencing that there was a failed attempt to create the 3PC without Partitioned attribute:

Screenshot 2: PSAT didn't detect the failed attempt to create the cookie:

Desktop (please complete the following information):

OS: MacOS 14.4.1 Sonoma
Browser: Chrome
Version: 124.0.6367.80 (Official Build) (arm64)

Additional context
PSAT System Information:
Open Tabs: 1
Active Extensions:
Google Docs Offline: ghbmnnjooekpmoecnnnilnnbdlolhkhi
Privacy Sandbox Analysis Tool: ikodlagpencphdljdpelmcajjlloiomb
Chrome Version: Version <IP_ADDRESS> (arm64)
PSAT Version: 0.7.0
OS - System Architecture: MacOS (arm64)


Feat/vault integration

📝 Description
Reopening the PR 3287 https://github.com/LedgerHQ/ledger-live/pull/3287
❓ Context

Impacted projects: ledger-live-desktop ledger-live-common ledgerjs/hw-transport-http
Linked resource(s): VG-14376

✅ Checklist

[ ] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

Between the record of this GIF, I updated some wording and added some Alerts:

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

👋  we have recently merged https://github.com/LedgerHQ/ledger-live/pull/3455 in develop branch which reinforces the TypeScript checks, mostly related to modals and coin families. Could you rebase and check that everything still pass?
in the PR, i could see there is an impact on the way modals was defined, it is likely you will have to define a new modal in modals/types.ts and type the data it takes, then you should no longer expect a name generic prop from the modal code, but inline the name="YOUR_NAME".
Thanks, gre.

Thx @gre I will have a look next week

👋  ESLint config has been unified on develop after we merged https://github.com/LedgerHQ/ledger-live/pull/3622 – this will improve the project consistency, remove eslint dependencies duplicates, and overall simplify the maintenance. This comes with a prettier library upgrade and unification of the prettierrc too, so you likely have conflicts with develop.
Hopefully, here is the procedure to easily fix this. please proceed as follow:
Step 1: sync your branch with develop up to the config changes:
2 cases

if your branch were continuously rebased with develop and don't have any merge commit, you can do

git rebase aa1e0ebc0a0498b4350754899b6a368fbd42e811

otherwise prefer

git merge aa1e0ebc0a0498b4350754899b6a368fbd42e811

then, apply the config
pnpm i
pnpm lint:fix --force

if there are remaining errors that lint couldn't fix, please fix them and pnpm lint again.
then commit in your branch.
git commit -a -m "chore: lint fixes"

Step 2: finalize the rebase/merge with develop
2 cases

if your branch were continuously rebased with develop and don't have any merge commit, you can do

git pull --rebase origin develop

otherwise prefer

git merge origin/develop

you should now be up to date. 👍

Thanks and sorry for the inconvenience,
gre

@gre just in case you missed my previous comment. And if you agree with that and re-approve, do you mind if I rebase and squash all commits on this branch into 1 single commit so it will ease potential future rebase onto develop, in case this PR is not merged right away?

@flocks you can squash all commits.


Details Page

A details page is required for the details of pets to be displayed.

Hii ,  can i do this work to me


[AVM Module Issue]: Data sink issue when using diagnosticSettings with search-service module

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
Module Name
avm/res/search/search-service
(Optional) Module Version
0.7.1
Description
I am using the module like this:
module searchService 'br/public:avm/res/search/search-service:0.7.1' = {
  name: 'search-service'
  scope: searchServiceResourceGroup
  params: {
    name: !empty(searchServiceName) ? searchServiceName : 'gptkb-${resourceToken}'
    location: !empty(searchServiceLocation) ? searchServiceLocation : location
    tags: tags
    disableLocalAuth: true
    sku: searchServiceSkuName
    semanticSearch: actualSearchServiceSemanticRankerLevel
    diagnosticSettings: [
      {
        workspaceResourceId: monitoring.outputs.logAnalyticsWorkspaceId
      }
    ]
  }
}

It worked on the first deploy, but I get this error on the second deploy:
Deployment Error Details:
Conflict: Data sink '/subscriptions/d6957007-e9ca-4fca-ab8d-38a11be9656d/resourceGroups/rg-pf-voicerag/providers/Microsoft.OperationalInsights/workspaces/log-mkgwky6acxdmg' is already used in diagnostic setting 'gptkb-mkgwky6acxdmg-diagnostics' for category 'OperationLogs'. Data sinks can't be reused in different settings on the same category for the same resource.

I'm just going to remove the diagnostic setting for now.
(Optional) Correlation Id
fc57f154533cbff7fb862f7f200e1a91

@pamelafox thanks for reporting, I will look into it.

@pamelafox I think it is not a module issue. This error occurs when you try to create two diagnostic settings sending the same category of logs/metrics to the same Log Analytic workspace.
Going back to your example:
When I deploy your code snipped twice, the error doesn’t occur, because both deployments create a diagnostic setting with the same (default) name: <searchservicename>-diagnosticSettings, which is no problem.
But I can produce the error with following steps:

First deployment of the search service (using your code snippet)
Manually delete diagnostic settings created by deployment
Manually create a similar diagnostic setting, but with a different name
Then second deployment using the template will fail, because it tries to deploy diagnostic settings with the default name.

To resolve it, just delete all diagnostic settings from the search service and re-deploy the template.

Thanks for taking a look! That may have been the issue since I was porting from our custom modules to avm.


Describe new algo for quorum connections

For more info and an implementation pls see https://github.com/dashpay/dash/pull/2710
To see how new changes will be rendered after merge pls see https://github.com/UdjinM6/dips/blob/dip6newalgo/dip-0006.md

ACK


making code complete by added input to take as character or a whole s…

…entence
Closing Issue/Referencing Issue
issue reference (#)
Changes Made In Pull Request

Algorithm Inorder(tree)

Traverse the left subtree, i.e., call Inorder(left-subtree)
Visit the root.
Traverse the right subtree, i.e., call Inorder(right-subtree)


Can't create a torrent from a directory

There are two issues:

The file name contains Chinese. Torrent created cannot be resolved.
If create a torrent from a directory, the torrent file has no file name, like .torrent, and the torrent file located in the target directory instead of current work directory.

Hello... I have not added support for files with non ascii characters in it yet... It's on my todo list.
When you make a torrent from a directory ensure you do not have a "/" at the end or it does what you are describing.  This is a bug that will be patched in the next release.  Which will be soon.


get_node() not correctly getting grandparent nodes

Godot version
4.0.3 Stable
System information
Windows 11
Issue description
using get_node("...") should return the grandparent node of the node it is being called from however it instead throws an error forcing the user to have to use get_node("..").get_node("..")
Steps to reproduce
create a node. create a child for this node. create a child for this child node. attach a script to the grandchild node and in one of the prebuilt functions add get_node("...").name . When you try to run the program it will throw an error that it cannot get the property name on null instance.
Minimal reproduction project
N/A

Try using "../.." instead.

instead.

Thanks, wish that were in the documentation somewhere.

See the description of NodePath: https://docs.godotengine.org/en/stable/classes/class_nodepath.html#class-nodepath
. and .. are common notations used in regular file system paths for "current" and "parent" folder.

See the description of NodePath: https://docs.godotengine.org/en/stable/classes/class_nodepath.html#class-nodepath
. and .. are common notations used in regular file system paths for "current" and "parent" folder.

Which kind of implies '...' should be grandparent folder making it unintuitive that it isn't, especially when the actual notation: "../.." isn't mentioned in the NodePath documentation.

especially when the actual notation: "../.." isn't mentioned in the NodePath documentation.

It follows from the basic logic, it's literally "parent of parent", we could add a line for that but there's limits for how much the documentation should explain every little detail

Opened a PR to make the documentation a bit more clear, this should cover all the possible confusion going forward


Replace boto waiter with simple loop

When boto waiters fail they just say " botocore.exceptions.WaiterError: Waiter InstanceRunning failed: Waiter encountered a terminal failure state" which is effectively worthless. So, add a wrapper to catch that error and dump the stack event info. Regardless of which client is waiting, client('cloudformation').describe_stack_events() is probably the most relevant thing to dump upon bumping into a failure in time domain

@cmaloney this is ready for review

Huh, this is a little less useful and boto waiter are a bit more enigmatic than I hoped... Better than nothing though.

Note: wrapping boto not very helpful as waiters are buggy. Rather than wrap the waiter it is more prudent to use a simple waiter that will raise exceptions we can understand. Back to WIP fo rnow

@cmaloney This is ready for review

Rebased and addressed comments.

LGTM.

@cmaloney @spahl Can we get this in a train soon? Without this change, CI will continue to come to a crashing halt when we hit the AWS API rate limit


Vuln patched on Windows 10 v21H2 Build 19044.1826

Vuln is patched on Windows 10 v21H2 Build 19044.1826, you can read more about it here.
https://github.com/itm4n/PPLdump/issues/12

Which is exactly the reason this has been open sourced

Which is exactly the reason this has been open sourced.

Ohh okay, I thought its open source in the first place, just like PPLDump :sweat_smile:


Color of Resiliency graphs

Change the shade of blue, looks too much like the margin of error

Fixed!


IE11 not working on demo site / polyfill broken

Hi all,
it seems that we have a regression with IE11 on the demo page here:
https://angular2-tree.readme.io/
I do get an error that the object does not have property or method "fill", as provided in the array polyfill.
it is the same issue as #567 or #272: the polyfill needs to be uncommented:
https://github.com/500tech/angular-tree-component/issues/567#issuecomment-379474295

as documented in here: https://angular2-tree.readme.io/docs/ie11

I'll update the example and comment out the polyfills so that the doc site works on IE11


Incorrect time metrics

Description
$ sh paket.sh restore
Checking Paket version (downloading latest stable)...
Paket.exe 5.6.4 is up to date.
Paket version 5.6.4
Performance:
 - Disk IO: 1 minute, 59 seconds
 - Runtime: 23 seconds

Disk IO is calculated incorrectly here (for comparison: Runtime is very close to wall clock).
Repro steps
Run paket.
Expected behavior
Disk IO + Runtime = wall clock
Actual behavior
Disk IO is incorrect (seems like we sum all the time from parallel threads)
Known workarounds
Just ignore it.

@matthid any comments on this?

Yes it's a duplicate ;) But I'm on mobile right now to search the original one.

marked as up-for-grabs

Original is #2367


Image links mostly broken

Most every image link is broken.
Reproduce:

Visit http://www.shacknews.com/chatty?id=35724255
Open link (http://chattypics.com/files/dougpugJPG_rmcu1uxabo.jpg)
Get 404 (http://chattypics.com/files/dougpugJPG_rmcu1uxabo.jpg&%3Ca%20href='/search?chatty=1&type=4&chatty_term=%2310%27%3E#10;)

This has been going on for a few months now.
I looked briefly around the source code, but nothing jumped out at me in https://github.com/arhughes/chromeshack/blob/master/scripts/image_loader.js. I'll be happy to submit a PR if someone can point me in the right direction.

The search link it inserted looks like it is from the hashtag script, try
turning that off. It isn't obvious to me what is actually causing it to do
that though.
On Sun, Dec 4, 2016, 2:28 AM Timm Stokke<EMAIL_ADDRESS>wrote:

Most every image link is broken.
Reproduce:

Visit http://www.shacknews.com/chatty?id=35724255
Open link (http://chattypics.com/files/dougpugJPG_rmcu1uxabo.jpg)
Get 404 (
http://chattypics.com/files/dougpugJPG_rmcu1uxabo.jpg&<a href='/search?chatty=1&type=4&chatty_term=%2310%27%3E#10
;)

This has been going on for a few months now.
I looked briefly around the source code, but nothing jumped out at me in
https://github.com/arhughes/chromeshack/blob/master/scripts/image_loader.js.
I'll be happy to submit a PR if someone can point me in the right direction.
[image: screenshot 2016-12-03 23 26 36]
https://cloud.githubusercontent.com/assets/192263/20864729/fa753518-b9af-11e6-9851-5366e123df0a.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arhughes/chromeshack/issues/76, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE258yNh_cHgV1GTEpsIEMijY200gaNks5rEmuZgaJpZM4LDhbq
.

Seems to be the same problem as #73.  A great PR would be to remove that hashtag script.

Hashtag script is gone now.


[Profile Creation] Username overlaps with converse.xyz placeholder

[P3] The username overlaps with ".http://converse.xyz|converse.xyz" text.
Converse Messenger: 2.0.1 (2) | Samsung Galaxy S23 - Android 14.0.0
:warning: http://app.teammobot.com/reports/49f84449-53d5-4c23-9f34-c15658708114|Report | http://app.teammobot.com/observations/f06b7e20-086b-42a9-bc7b-1c158621e794|Issue
Slack Message

@nmalzieu when you click the link, are you able to sign in with your ephemera email?

This is what I get. I'll try to login first on the main website and come back to that link

@saulmc I managed to get to that page:

but your links still show a Page not found

Ohh, yes, looks like the link is broken bc github doesn't parse slack markdown.
Once we're sure this is valuable they'll start posting issues directly to GH.


Fix error toast not display when JavaScript syntax error

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

In /client/saga/err-saga.js#7, the dispatched action has type app.makeToast but there is no this type name in the project. I looked into /common/app/redux/types.js which contains all the action types with prefix app, and makeToast is no where to be found. So I use the action creator from /common/app/toasts/redux/actions.js instead.
closes #11198

Oh snap! I didn't test that. I'll try tracking those errors down. But one thing I know for sure is that err-saga.js now dispatch a correct action, so any action that has a key error that was dispatched will now cause the error toast to popup i.e. These 2 errors were there originally, but they just didn't show the error toasts.
To be honest, I'm not entirely sure if an error is handle by the middleware or is handle in a handler and then fire an action containing an error key. I'll need more time to investigate, hopefully I'll come up with something in a couple of days.

This code looks good and works. @atjonathan I think your issue has to do with a redux storage system I implement. It tends to keep the csrf token around between sessions during development.
@WiNloSt Thanks so much. Happy Coding!

Hello world

@aaryanrathi Please use the chat rooms to introduce yourself. The issue tracker is for reporting issues only.


docs: VlsChecker is just named export

fix: VlsChecker is just named export, just update README

Thanks! @angus96


how do I resolve this?

what modcharting tools it is? (zoroForce/mine)

what modcharting tools it is? (zoroForce/mine)

yours, because the original always gives problems


please i need your help

I want to load telegram.org in my WindowsFormsApplication with C# in webBrowser with this code:
webBrowser1.Navigate("https://web.telegram.org");
But result is empty.
How can I load this site?
thanks

What do you mean exactly by "the result is empty"?
This project is Telegram's bot API, so you can easily create bots in C#. It doesn't have anything to do with Telegram Web.


Support Admonitions

Describe the problem/need and solution
Problem
Right now, mdformat breaks indentation for admonitions. Below is a repeatable example based on the first snippet from the admonition documentation
~/Developer > pipx install mdformat-gfm --include-deps
  installed package mdformat-gfm 0.3.5, installed using Python 3.10.2
  These apps are now globally available
    - markdown-it
    - mdformat
done! ✨ 🌟 ✨
~/Developer > pbpaste > ad_test.md
~/Developer > bat ad_test.md
───────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: ad_test.md
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ !!! type "optional explicit title within double quotes"
   2   │     Any number of other indented markdown elements.
   3   │
   4   │     This is the second paragraph.
───────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
~/Developer > mdformat ad_test.md
~/Developer > bat ad_test.md
───────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: ad_test.md
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ !!! type "optional explicit title within double quotes"
   2   │ Any number of other indented markdown elements.
   3   │
   4   │ ```
   5   │ This is the second paragraph.
   6   │ ```
───────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Solution
admonitions are not part of the CommonMark specification and would be best handled by a plugin (i.e. mdformat-admonition)
I would be happy to try writing one, but I wanted to open an issue first so that I'm not duplicating effort. I saw that there was at least one other issue with admonition problems, but there didn't seem to be any updates since: #53 (https://github.com/executablebooks/mdformat/issues/53#issuecomment-928306196)

I naively think the plugin shouldn't be too difficult to implement

I found the plugin template: https://github.com/executablebooks/mdformat-plugin

and the mdformat-tables, mdformat-frontmatter, mdformat-footnote, and mdformat source will be useful to reference

Update: As a reference, here is a plugin that was recently ported with a good implementation

Benefit
Would be nice to have support for admonitions (particular for mkdocs which uses the markdown extension)
Guide for implementation
No response
Tasks and updates
No response

Hey thanks for the issue!
Yeah this should be a plugin, and the plugin template you linked should be helpful. The first step, however, is a parser extension for mdformat's Markdown parser (markdown-it-py).
You'll find the existing parser extensions in this collection repository: https://github.com/executablebooks/mdit-py-plugins. I suggest making a PR there (although it's entirely possible that you keep in a separate repo too).
Luckily you don't have to start from scratch: there seems to be a JavaScript version of the parser extension which you can port to Python https://github.com/commenthol/markdown-it-admon (I dont know whether the JS implementation is any good though).

Great! I've got a busy next few weeks, but I'll start on this once I have time!

@KyleKing had any chance to work on this?

Thanks for reminder. I had completed forgotten about this ticket. This is still an issue for me, but haven't had time to work on it

@KyleKing I guess there is still no advance, isn't it?

Yeah, no progress yet
I actually had these tickets open to try to get to it this week, but haven't had time yet with school and holidays here

Submitted a PR! It is a Draft, but I'll finish up and mark it ready for review sometime tomorrow

And I started the plugin for mdformat-admon here: https://github.com/KyleKing/mdformat-admon

This ticket keeps accidentally closing...but I had some time to make progress today!
If anyone is more familiar with mdformat and can weigh in on my implementation, let me know:
https://github.com/KyleKing/mdformat-admon/blob/master/mdformat_admon/plugin.py

After a long, busy year, I finally have a v1.0.0 release of the admonition plugin!
I will test it in a real world project and will revisit if formats other than !!!  will be supported, but I think we can close this issue (third times the charm!) and track any issues around admonition support in: https://github.com/KyleKing/mdformat-admon/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc 🎉


Remove Sparkle Sandboxing configuration

Due to a sandboxing issue new to macOS Sonoma, users may see a one-time warning when checking for updates about "Downloader" differs from previously opened versions. See https://github.com/sparkle-project/Sparkle/discussions/2514 for more information.
SwiftShift can simply resolve this issue by removing its sandboxed configuration for Sparkle because SwiftShift itself is not sandboxed. This involves removing the SUEnableDownloaderService and SUEnableInstallerLauncherService keys in its Info.plist along with removing the com.apple.security.temporary-exception.mach-lookup.global-name key in its entitlements file. These settings were retrieved from Sparkle's Sandboxing guide but again, this app is not sandboxed.

hey @zorgiepoo, thank you for taking the time to explain it! Would you say this will be enough? Or should I just remove the entitlements file too?

Shouldn't matter if you remove an empty entitlements file or not

Turns out Xcode complains if it's not there. Anyway, I tested and updating works, so I'll include this in the next release. Thanks for the help!


Make columns configurable

Right now the number of columns is hardcoded based on the width of the card. This should be made configurable. It should still be responsive, but the cutoff points and the number of columns should be configurable.

It looks like CSS variables can not be used in container queries and LitElement doesn't have a way to make the CSS dynamic. I'll have to research this some more. I'm going to remove the milestone for now.

sehr schöne Arbeit ... DANKE!
Wird es ggf. möglich sein, die Orientierung der aufeinanderfolgenden Tage (hier: 14) von horizontal
Mo - Di
Mi - Do
Fr - Sa
So - Mo
...
auf vertikal
Mo   Mo
Di     Di
Mi    Mi
Do   Do
Fr    Fr
Sa   Sa
So   So
konfigurieren zu können?
Danke für eine Berücksichtigung

@wobeco My German is nearly non-existent, but if I understand you correctly your question is not related to this issue. Can you please create a new issue for your question in English?

@wobeco As far as I can see there's no easy way to do this. You could use a card for each day, using startingDay and startingDayOffset to give them each a different day, and align them in the new sections view. But without knowing how many events there are for each they it's going to be hard to align I think.

Configurable columns has been added to the dev branch and will be included in the 1.11.0 release.


Document Traefik and cattle usage and what happens when disabled

Could you please describe what's the exact role of Traefik and Cattle in k3s and what's going to happen when it gets disabled on the server node?
I'm asking for this because  I noticed   that for a 4 node cluster there's a pod for each node that's responsible for (I guess) service  load balancing.:
➜  ~ kubectl get services -n kubernetes-dashboard -o wide
NAME                        TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)          AGE   SELECTOR
dashboard-metrics-scraper   ClusterIP      <IP_ADDRESS>     <none>          8000/TCP         26h   k8s-app=dashboard-metrics-scraper
kubernetes-dashboard        LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   8082:32638/TCP   25h   k8s-app=kubernetes-dashboar

It seems like a waste of resources, normally 5 deployments would result in 1 pod for each deployment (if not scaled) but in k3s it also adds additional pod per each node per each service so 5 different services * 4 nodes equals to 20 pods
➜  ~ kubectl get pods -n kubernetes-dashboard -o wide
NAME                                         READY   STATUS    RESTARTS   AGE   IP           NODE      NOMINATED NODE   READINESS GATES
svclb-kubernetes-dashboard-h2vgt             1/1     Running   1          25h   <IP_ADDRESS>   worker2   <none>           <none>
kubernetes-dashboard-5996555fd8-k684f        1/1     Running   1          26h   <IP_ADDRESS>   worker2   <none>           <none>
svclb-kubernetes-dashboard-b85qs             1/1     Running   1          25h   <IP_ADDRESS>   master    <none>           <none>
svclb-kubernetes-dashboard-j8tg5             1/1     Running   1          25h   <IP_ADDRESS>   worker3   <none>           <none>
svclb-kubernetes-dashboard-lq5tj             1/1     Running   1          25h   <IP_ADDRESS>   worker1   <none>           <none>
dashboard-metrics-scraper-76585494d8-bzccd   1/1     Running   2          26h   <IP_ADDRESS>   worker1   <none>           <none>

Noting here for future reference, Nginx will become the default ingress controller in our next release. You can still use Traefik if wanted however. See https://github.com/rancher/k3s/issues/817 for details.

thanks


Aerosandbox kills whenever i try to run a test or anything else

I just installed aerosandbox[full] on my mac m1 with python 3.11.19 with anaconda. Everything fails sooner or later. All the test fail instantly and tutorial programs that i tried to make take a while but eventually get the same error: zsh: killed     (whatever I ran in the terminal)
I probably just missed some stupid thing or forgot to install something but i am quite new and i couldnt find anything online

Operating System: sonoma 14.4
Python Version: 3.11.19 (also tested 3.12.6 and 3.8.19)
AeroSandbox Version: 4.2.6

Hi @janibert1 ,
The zsh: killed error usually indicates that the process was terminated by the operating system, which can happen due to insufficient memory, a bad allocation, or other resource constraints. Since you're running an M1 Mac with a fairly new operating system (Sonoma 14.4), this could also be related to compatibility with certain libraries used by AeroSandbox. However, none of the dependencies jump out immediately as potential culprits here.
I don't have access to a M1 Mac, so unfortunately can't provide too much direct help here (though other users may be able to).
A few general questions that may be useful:

How narrowly can you isolate this issue? Is it only occuring with aerosandbox? If so, how far into a script can you execute before the OS kills it - exactly which line causes the failure?
Are there any warning messages during install?
If the above doesn't help, it might be worth binary-searching the dependencies to try to see if you can pin down a common cause.


Error adding configMap

Tried to include configMap into the application and got an error
error: unable to recognize "example.yaml": no matches for kind "ConfigMap" in version "apps/v1"
in the yaml it is defined like this
....
componentKinds:
- group: core
kind: Service
- group: apps
kind: Deployment
- group: apps
kind: ConfigMap
....
apiVersion: apps/v1
kind: ConfigMap
metadata:
name: cfgtcl
...
Please help.  Thanks.

ConfigMap is a 'core' resource

Like @ant31 mentioned, ConfigMap should be under core instead of apps/v1. Please reopen if this doesn't address your need.
/close

@janetkuo  I tried adding configmap
componentKinds:
    - group: core
      kind: Service
    - group: apps
      kind: StatefulSet
    - group: core
      kind: ConfigMap

But in application status or logs, I dont see any information regarding configmap and service.
For more details on this issue pls refer to  https://github.com/kubernetes-sigs/application/issues/113

group: v1
kind: ConfigMap

@hemantha-kumara