Updated README - do not merge

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
[ ] The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

@selvasingh,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Opened issue everyday

Hey there,
if the action is run on a schedule, the issue is created every day again and again till solved. This gives a little bit of a push to solve it, otherwise you sometimes rely on other resources to fix the link. Is there an easy way to avoid that?

Hey @Isengo1989,
can you try out these instructions for reusing/updating existing issues? https://lychee.cli.rs/github_action_recipes/reuse-issue/

Hey @mre
Great thx, did not know about those docs :wave:
One thing I noticed is the missing id in the  Find Link Checker Issue step that is used. I will create a PR on it.
I also added an extra if check to verify it was found. Wdyt ?
      - name: Find Link Checker Issue
        uses: micalevisk/last-issue-action@v2
        id: known-issue
        with:
          state: open
          labels: |
            link-checker

      - name: Create Issue From File
        if: steps.lychee.outputs.exit_code != 0 && steps.known-issue.outputs.has-found != 'true'
        uses: peter-evans/create-issue-from-file@v5
        with:
          issue-number: "${{ steps.known-issue.outputs.issue-number }}"
          title: Link Checker Report
          content-filepath: ./lychee/out.md
          labels: link-checker

steps.known-issue.outputs.has-found != 'true' could be steps.known-issue.outputs.has-found == 'false'.
Other than that, looks good to me.

@mre sounds good. Done -> https://github.com/lycheeverse/lycheeverse.github.io/pull/83


FoundationPress crashes Netbeans 7.4 (or makes it stall)

Hi,
I'm not sure whether this would be solely a FoundationPress issue or a Netbeans one as well, but if I have a FoundationPress project loaded up, Netbeans starts stalling on "Background scanning of projects" and I'm not exactly sure what's causing this. In the beginning Netbeans was reporting a sass compiler was missing and would also crash/stall, but I've installed one since then. Now, it just keeps stalling.
I'm using Windows 7, Netbeans 7.4 and the latest FoundationPress version.
Any ideas why this is happening?

Hello. Unfortunately I have no experience with NetBeans.

You did a great job with the theme, and I'd really like to keep using it but it keeps crashing my installation of Netbeans :/
Thanks anyway.

Ok, thanks.

I haven't tried Netbeans with FoundationPress - WebMatrix works fine, and seems a lot less complex than Netbeans to me.


Fix testcase for daylight saving

The dateTime in the test used local time, but the date was stored in UTC.
The test assumed that local time and UTC is the same, which isn't true in all cases.

Closing in favor of https://github.com/Readify/Neo4jClient/pull/305


Remove hardcoded secrets

We will be generating secrets with init containers. These secrets will
be created in a volume mounted from the host, so they survive reboots.
While being sufficient for our GA purposes we will need to rethink how
we do this in a HA environment.
Two secrets are generated with the init containers:

mysql root password
saltapi user password

Once we have chosen a mysql root password, we need to write this
configuration on a file that will be mounted on the salt-master, so the
salt-master mysql returner is able to connect to it.
Password generation uses /dev/random, asking for 1000 bytes, and doing
a sha256sum to it. While the set of characters is reduced (alphanumeric),
the length of the password is considerable.
Images will take this environment variables and they will use their
entrypoint to perform the required actions. Example:

mariadb container will set the root password and do some initializations
salt-master container will chpasswd the saltapi user to the generated
saltapi password.

This looks like a significant improvement over the current implementation.
@ukbelch what do you think about that from a security POV?

is this blocked, can it be merged?

is this blocked, can it be merged?

I think this is halted until we release the Beta 4, so it's not another point of friction.

Please, do not merge yet. Commit message needs tweaking, as well as PR description.

@flavio Asking for your review. Had to add setup folder because here documents didn't work fine on the annotations, and the double nesting quoting was making things nearly unreadable.
Please, confirm if everything looks fine for you. Merging this will require merging other related PR's and SR's, namely:

https://github.com/kubic-project/caasp-devenv/pull/1
https://github.com/kubic-project/salt/pull/83
https://build.suse.de/request/show/133060
https://build.suse.de/request/show/133059
https://build.suse.de/request/show/133030

@jordimassaguerpla asking for your review because I'm not sure I got the packaging side of things right.

This PR has been created sometimes ago, is everything working fine against rebased master?

Yes, I have been constantly rebasing them to master (all PR's), so everything should be fine.

Ok, then let's merge it. Please @ereslibre coordinate with the others to avoid issues during the merge process (eg: breaking the daily image or such).


Extract mockNetwork from tests

Explanation

Mocking JSON-RPC requests in tests is somewhat inconvenient due to needing to spell out the full path for an Infura endpoint and specify full JSON-RPC request and response objects, but to make this easier, we've written a small wrapper around Nock. Currently we use this in one test within the network-controller package, but we plan to use this in a different package, so this commit extracts the class responsible for doing this. This also makes a small improvement to the API and adds a function that makes the class even easier to use.
References

Extracted from https://github.com/MetaMask/core/pull/1499.
Changelog

N/A
Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

This PR is ready for review again.


Use the correct basename on the demo website.

When on a particular example, the URL displayed in the browser is https://sharlaan.github.io/example1 when it should be https://sharlaan.github.io/material-ui-superselectfield/example1.
For example, in react router it's solved using basename
This issue makes sharing examples harder.

Hello, thanks for the report.
I just deployed my current WIP with basename='/material-ui-superselectfield', but the poblem persists.... i think it maybe related to github hosting... i don't know :s

Probably yes. I don't know if there is a setting possible for html5 navigation on github pages.
You could try to use HashHistory instead of BrowserHistory. It's designed exactly for this use case.

ok i now deployed with HashRouter, it should works with:
https://sharlaan.github.io/material-ui-superselectfield/#/example1

Awesome thanks!


Architectury Forge Remapping Invalidates Dependencies

I have a pom for a forge mod with a dependency block that looks something like this:
<dependencies>
<dependency>
<groupId>org.jetbrains</groupId>
<artifactId>annotations</artifactId>
<version>23.0.0</version>
<scope>runtime</scope>
</dependency>
<dependency>

it's MANIFEST.MF file says:
Manifest-Version: 1.0
Multi-Release: true

Architectury remaps all forge dependencies without checking whether the file is indeed a mod. See --> ModCompileRemapper::shouldRemapMod
The problem is in the remapped library, the META-INF/versions folder disappears. The original library had it. This causes the remapped jar to be invalid (when it never should've been remapped in first place because it's not a mod). Jars that specify Multi-Release to be true require that folder.
Launching forge with this now broken dependency causes the expected crash:
"Exception in thread "main" java.io.UncheckedIOException: java.nio.file.NoSuchFileException: /META-INF/versions"

Transferred this here because this is a loom bug. We can fix the unnecessary remapping, but it should also work correctly with multi-release jars, so that needs fixing too.

Is there a fix for this?  Or a work around?

is there still no fix for this?


Python SDK fails to install (Windows/cp1251)

While following the Azure Getting Started guide for Windows/Python, I got an error while running pip3 install -r requirements.txt:
$ pip3 install -r requirements.txt
Requirement already satisfied: pulumi>=1.0.0 in c:\python36\lib\site-packages (from -r requirements.txt (line 1)) (1.1.0)
Collecting pulumi-azure>=1.0.0 (from -r requirements.txt (line 2))
Using cached https://files.pythonhosted.org/packages/8f/76/1cf9e1e4e1e8d13222a34034d388fcb03d4d973f46cc1249e4caa9bb6bbf/pulumi_azure-1.0.0.tar.gz
ERROR: Command errored out with exit status 1:
command: 'c:\python36\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\shilk\\AppData\\Local\\Temp\\pip-install-p4ffcswp\\pulumi-azure\\setup.py'"'"'; __file__='"'"'C:\\Users\\shilk\\AppData\\Local\\Temp\\pip-install-p4ffcswp\\pulumi-azure\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base pip-egg-info
cwd: C:\Users\shilk\AppData\Local\Temp\pip-install-p4ffcswp\pulumi-azure\
Complete output (9 lines):
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Users\shilk\AppData\Local\Temp\pip-install-p4ffcswp\pulumi-azure\setup.py", line 33, in <module>
long_description=readme(),
File "C:\Users\shilk\AppData\Local\Temp\pip-install-p4ffcswp\pulumi-azure\setup.py", line 28, in readme
return f.read()
File "c:\python36\lib\encodings\cp1251.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x98 in position 1467: character maps to <undefined>
----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Apparently, the readme.rst file contains symbols which have no meaning in the default codepage (CP1251 for me). We should change setup.py to read the file with explicit UTF8 encoding.
Doesn't happen for pulumi-aws for me, but I guess we should make the change across all repos.

Closed via #357 but not yet released
We will roll this out in a different manner with https://github.com/pulumi/pulumi-terraform/pull/494

Ah, failed to find #356 somehow, mea culpa

@mikhailshilkov so did I until I looked at the CHANGELOG :D


Added EkToast

Added EKToast it will be useful.

Can you please move the new item to the bottom of the category? Thank you!

Moved new item to the bottom.

Can you please rebase your changes? Tks!

merged with #234


[Question] How can I get out of bag error from lightbgm

This is not a bug just a question.
I just wanted to know if there was a way to get something like an 'out of bag error' from lightbgm.
I know for random forests I can easily get an out of bag error estimate. This comes from the error on the validation set that random forest is using when bagging (bootstrap aggregating).

Thanks for using LightGBM!
Random Forest implementations randomly sample rows of the training data in each tree, and so can calculate an "out of bag" error by predicting on each row using only an ensemble of the trees for which each sample wasn't chosen.
LightGBM, by default, does not work that way. With LightGBM's default settings, every row in the input data is used in every tree.
To get something like what you are describing, hold out a chunk of labeled data prior to training, and pass it to LightGBM as a validation set.
Here's an example using the R package.
library(lightgbm)

data(agaricus.train, package = "lightgbm")
data(agaricus.test, package = "lightgbm")

dtrain <- lgb.Dataset(
    data = agaricus.train$data
    , label = agaricus.train$label
)

dtest <- lgb.Dataset.create.valid(
    dataset = dtrain
    , data = agaricus.test$data
    , label = agaricus.test$label
)

model <- lgb.train(
    params =  list(
        objective = "regression"
        , metric = "l2"
        , num_leaves = 7L
    )
    , data = dtrain
    , nrounds = 5L
    , valids = list(validation_set = dtest)
)

Produces logs like
[1] "[1]:  validation_set's l2:0.203918"
[1] "[2]:  validation_set's l2:0.167247"
[1] "[3]:  validation_set's l2:0.137026"
[1] "[4]:  validation_set's l2:0.112671"
[1] "[5]:  validation_set's l2:0.0916572"

Hope that helps. Please let us know if you have other questions.


Warning from CMake

When I use the steps shown in README.md (under "Install from sources"), I get this warning from CMake:
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.

I get the warning with CMake version 3.22.1 and 3.30.0.
(This is on a Linux system.)

It looks like a simple fix is to add . at the end of the recommended cmake command:
cmake -D CMAKE_INSTALL_PREFIX=your_install_prefix .


[WV-244] Convert methods with warning to @staticmethod TEAM REVIEW

Removes self parameter for functions with warning and converts to @staticmethod.
Also fixes
-PEP 8 E111 Indentation not a multiple of 4
-PEP 8 E127 Continuation line over indented
-PEP 8 E501 Line too long
-PEP 8 E302 Two blank lines before class definition

Great work @smcvey7! 👍


⚠ Bofrost.at has degraded performance

In 67f955c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 996 ms

Resolved: Bofrost.at performance has improved in 3f37e70 after 53 minutes.


Show current version in Clipper

Make the current version and other common debug info available in Clipper, eg in General Settings.

Added in 0.10.1


TypeError: Can't instantiate abstract class MultiLabelPipeline with abstract methods _forward, _sanitize_parameters, postprocess, preprocess

Thanks for this great work.
I am using transformer v4
I know this is not transformer v2 as requested in the readme file but I cannot install v2.11.0 anymore because there are dependency errors in that version. And I tried v2.4.1 it raise other errors.
In transformer v4, it raises:
Traceback (most recent call last):
goemotions = MultiLabelPipeline(
TypeError: Can't instantiate abstract class MultiLabelPipeline with abstract methods _forward, _sanitize_parameters, postprocess, preprocess
Do you think you can update your code so it can work with the latest Hugginface transformer (v4)?

experiencing the same issue here

Same problem here:)

Hey, I had the same issue but I managed to make it work with this:
`
from transformers import AutoTokenizer, AutoModelForSequenceClassification
from pprint import pprint
from multilabel_pipeline import MultiLabelPipeline
tokenizer = AutoTokenizer.from_pretrained(
"monologg/bert-base-cased-goemotions-original"
)
model = AutoModelForSequenceClassification.from_pretrained(
"monologg/bert-base-cased-goemotions-original")
def tokenize_text(text):
# Replace "text" with whatever column name has your text inputs
return tokenizer(text, truncation=True)
texts = [
"Hey that's a thought! Maybe we need [NAME] to be the celebrity vaccine endorsement!",
"it’s happened before?! love my hometown of beautiful new ken 😂😂",
"I love you, brother.",
"Troll, bro.  The motherfucker does nothing but stink up libertarian subs talking shit",
]
goemotions = MultiLabelPipeline(
model=model,
tokenizer=tokenizer,
threshold=0.3
)
pprint(goemotions(texts))`
Just make sure to use the multilabel_pipeline provided in the python with the same name in this repo!

Hey, I had the same issue but I managed to make it work with this:
`from transformers import AutoTokenizer, AutoModelForSequenceClassification from pprint import pprint from multilabel_pipeline import MultiLabelPipeline
tokenizer = AutoTokenizer.from_pretrained( "monologg/bert-base-cased-goemotions-original" ) model = AutoModelForSequenceClassification.from_pretrained( "monologg/bert-base-cased-goemotions-original")
def tokenize_text(text): # Replace "text" with whatever column name has your text inputs return tokenizer(text, truncation=True)
texts = [ "Hey that's a thought! Maybe we need [NAME] to be the celebrity vaccine endorsement!", "it’s happened before?! love my hometown of beautiful new ken 😂😂", "I love you, brother.", "Troll, bro.  The motherfucker does nothing but stink up libertarian subs talking shit", ]
goemotions = MultiLabelPipeline( model=model, tokenizer=tokenizer, threshold=0.3 ) pprint(goemotions(texts))`
Just make sure to use the multilabel_pipeline provided in the python with the same name in this repo!

This will still not work, if you create a custom Pipeline with abstract Pipeline, you have to override the
abstract methods _forward, _sanitize_parameters, postprocess, preprocess

Solution :
`from transformers import BertTokenizer
##files from git
from model import BertForMultiLabelClassification
from multilabel_pipeline import MultiLabelPipeline
from pprint import pprint
tokenizer = BertTokenizer.from_pretrained("monologg/bert-base-cased-goemotions-ekman")
model = BertForMultiLabelClassification.from_pretrained("monologg/bert-base-cased-goemotions-ekman")
texts = [
"Hey that's a thought! Maybe we need [NAME] to be the celebrity vaccine endorsement!",
"it’s happened before?! love my hometown of beautiful new ken 😂😂",
"I love you, brother.",
"Troll, bro.  The motherfucker does nothing but stink up libertarian subs talking shit",
]
import torch
import numpy as np
results = []
for txt in texts:
inputs = tokenizer(txt,return_tensors="pt")
outputs = model(**inputs)
scores =  1 / (1 + torch.exp(-outputs[0]))  # Sigmoid
threshold = .3
for item in scores:
labels = []
scores = []
for idx, s in enumerate(item):
if s > threshold:
labels.append(model.config.id2label[idx])
scores.append(s)
results.append({"labels": labels, "scores": scores})
`

the implementation above is nearly identical to [https://github.com/monologg/GoEmotions-pytorch/blob/master/multilabel_pipeline.py](the pipeline.py) but i get different result. can somebody explain what is the reason for this?
results:
[{'labels': ['joy', 'neutral'],
  'scores': [tensor(0.3892, grad_fn=<UnbindBackward0>),
   tensor(0.5499, grad_fn=<UnbindBackward0>)]},
 {'labels': ['joy', 'surprise'],
  'scores': [tensor(0.9277, grad_fn=<UnbindBackward0>),
   tensor(0.4548, grad_fn=<UnbindBackward0>)]},
 {'labels': ['joy'], 'scores': [tensor(0.9889, grad_fn=<UnbindBackward0>)]},
 {'labels': ['anger'], 'scores': [tensor(0.7580, grad_fn=<UnbindBackward0>)]}]

@bubbazz if you mean that you aren't getting outputs for all labels, but only the main labels, try this.
from transformers import BertTokenizer, AutoModelForSequenceClassification, pipeline

model_name = 'original' #'ekman'

tokenizer = BertTokenizer.from_pretrained(f"monologg/bert-base-cased-goemotions-{model_name}")
model = AutoModelForSequenceClassification.from_pretrained(f"monologg/bert-base-cased-goemotions-{model_name}", num_labels=28)

goemotions=pipeline(
        model=model,
        tokenizer=tokenizer,
        task="text-classification",
        return_all_scores=True,
        function_to_apply='sigmoid',
    )

goemotions(texts)


Fix encoding bug when rendering to React components

Previously, meta tag values were encoded before being passed to React.createElement. This caused the values to be double-encoded because React already encodes when rendering. This change removes the manual encoding step when converting tags to React elements so that React can properly encode at render time.

The CLAHub link is broken and contributing.md doesn't mention any CLA instructions, but I'm happy to sign one if necessary.

Yep, sorry, it's a bug(?) with the webhook. Link: https://cla.nfl.com/agreements/nfl/react-helmet

Thanks, @doctyper. It looks like CLAHub might be having issues. I attempted to sign, but received a generic error message.

@bryanrsmith can you try authenticating with CLAHub again? If it fails can you send an email to<EMAIL_ADDRESS>requesting the Individual CLA? Can you also email the generic error message you saw - I wasn't able to recreate the issue.

Thanks @potench. It worked after re-authenticating.


Dynamic Routes

I don't see in the documentation how can I get a route param. Is there a way to get this dynamic params? Something like:
// pages/api/[name]/hello.ts

@api
export default class Controller extends ApiController {

 override async get(query) {
    const name = query.name;
    return `hello ${name}`
  }

}

You can access the route params from this.req.params, HTTP related methods only accept query string params.

@hyurl, thanks a lot for your answer. I have used your work on some of my projects and I liked it a lot.
But, about your answer, I'm receiving a type error when trying to use this.req.params.

If you're using the default Next.js server, it seems it binds route params to the query object directly, which will be overridden by the previous next-controller, so I've just published a fix (version 1.5.2) that merges the traditional query object and the route params, upgrade to this version and you can now access those params from the query object as Next.js' default behavior.

@luigiminardim If you're using the default Next.js server, it seems it binds route params to the query object directly, which will be overridden by the previous next-controller, so I've just published a fix (version 1.5.2) that merges the traditional query object and the route params, upgrade to this version and you can now access those params from the query object as Next.js' default behavior.

@hyurl, Worked really well. Thanks for your help!


add support for FocalLength AnimationCurveNodes

This commit fixes a nil-pointer dereference in
AnimationCurve.stringPrefix which was caused by the assumption
that AnimationCurveNodes always contain the Curves. This is true
for most cases (with one curve per X,Y,Z axis). However, the
FocalLength AnimationCurve property has exactly one Curve, not
three.
Panic prior to this commit:
 5  0x0000000000508d25 in github.com/oakmound/ofbx.(*AnimationCurve).stringPrefix
	 at /home/u/Desktop/ofbx/animationCurve.go:58
 6  0x0000000000508c9b in github.com/oakmound/ofbx.(*AnimationCurve).String
	 at /home/u/Desktop/ofbx/animationCurve.go:52
 7  0x0000000000509545 in github.com/oakmound/ofbx.(*Curve).String
	 at /home/u/Desktop/ofbx/animationCurve.go:87
 8  0x0000000000509d66 in github.com/oakmound/ofbx.(*AnimationCurveNode).stringPrefix
	 at /home/u/Desktop/ofbx/animationCurve.go:162
 9  0x0000000000508985 in github.com/oakmound/ofbx.(*AnimationLayer).stringPrefix
	 at /home/u/Desktop/ofbx/animation.go:109
10  0x000000000050838a in github.com/oakmound/ofbx.(*AnimationStack).stringPrefix
	 at /home/u/Desktop/ofbx/animation.go:64
11  0x000000000052b418 in github.com/oakmound/ofbx.(*Scene).String
	 at /home/u/Desktop/ofbx/scene.go:40
12  0x00000000004db522 in fmt.(*pp).handleMethods
	 at /home/u/go/src/fmt/print.go:626
13  0x00000000004db935 in fmt.(*pp).printArg
	 at /home/u/go/src/fmt/print.go:709
14  0x00000000004e03f4 in fmt.(*pp).doPrintln
	 at /home/u/go/src/fmt/print.go:1169
15  0x00000000004d8716 in fmt.Fprintln
	 at /home/u/go/src/fmt/print.go:264
16  0x00000000004d8865 in fmt.Println
	 at /home/u/go/src/fmt/print.go:274
17  0x0000000000532c70 in main.parse
	 at ./main.go:33
18  0x00000000005327d4 in main.main
	 at ./main.go:17
19  0x000000000043d223 in runtime.main
	 at /home/u/go/src/runtime/proc.go:225
20  0x0000000000470581 in runtime.goexit

Example animation layer with FocalLength AnimationCurveNode:
 &ofbx.AnimationCurveNode{
	  Object: ofbx.Object{
			id:            0x102c7e21,
			name:          "S\x00\x01AnimCurveNode",
			element:       &ofbx.Element{(CYCLIC REFERENCE)},
			nodeAttribute: nil,
			isNode:        false,
			scene:         &ofbx.Scene{(CYCLIC REFERENCE)},
	  },
	  Curves: {
			{
				 Curve:      &ofbx.AnimationCurve{(CYCLIC REFERENCE)},
				 connection: &ofbx.Connection{typ:1, from:0x2b73613c, to:0x102c7e21, property:"d|X"},
			},
			{
				 Curve:      &ofbx.AnimationCurve{(CYCLIC REFERENCE)},
				 connection: &ofbx.Connection{typ:1, from:0x1def8b85, to:0x102c7e21, property:"d|Y"},
			},
			{
				 Curve:      &ofbx.AnimationCurve{(CYCLIC REFERENCE)},
				 connection: &ofbx.Connection{typ:1, from:0x12919792, to:0x102c7e21, property:"d|Z"},
			},
	  },
	  Bone:         &ofbx.Node{(CYCLIC REFERENCE)},
	  BoneLinkProp: "Lcl Scaling",
	  mode:         0,
 },
 &ofbx.AnimationCurveNode{
	  Object: ofbx.Object{
			id:            0x3a35b911,
			name:          "FocalLength\x00\x01AnimCurveNode",
			element:       &ofbx.Element{(CYCLIC REFERENCE)},
			nodeAttribute: nil,
			isNode:        false,
			scene:         &ofbx.Scene{(CYCLIC REFERENCE)},
	  },
	  Curves: {
			{
				 Curve:      &ofbx.AnimationCurve{(CYCLIC REFERENCE)},
				 connection: &ofbx.Connection{typ:1, from:0x10fffb38, to:0x3a35b911, property:"d|FocalLength"},
			},
			{},
			{},
	  },
	  Bone:         nil,
	  BoneLinkProp: "",
	  mode:         0,
 },

Not sure what the contribution guidelines are for oakmound projects. In either case, I hereby release this code change into the public domain.
Cheers,
Robin


Add Movies Dataset

related #1
Feedback: https://github.com/john0isaac/rag-semantic-kernel-mongodb-vcore/issues/1#issuecomment-2052843127
Kaggle URL: https://www.kaggle.com/code/johnaziz/cleaning-imdb-movies
Action items:

[ ] Chunk in the data itself --> content: Movie title - Movie Description.
[x] Remove movie url
[x] attempt to load the generated json on Kaggle as it didn't work until you beautified it
[ ] Upload the small data sample to the /data folder
[ ] Format notebook, review comments
[ ] Add another notebook for history or add a section to the same notebook

Apparently the movie URL was causing troubles with json.load()


@envelop/sentry: obscure sensitive variable values added to scope

A nice practice would be to prefix sensitive variable values/input fields with sensitive_, thus the sentry plugin could automatically replace them with something like <redacted>. Customization of this behavior in userland would be great.

+1 this. But feel as though this would be better suited for a SDL directive envelope could just rip out, than looking for fields.

I tried to avoid sending anything that isn't static (so we send only the document). There is a flag for choosing if to send variables values or not. And I think Sentry has a built-in mechanism to clearing some fields (https://help.sentry.io/account/security/why-am-i-seeing-filtered-in-my-event-data/) .

I think just having a function overload option for the variables option that gets the variables object and should return a sanitized variables object would be enough. I don't like the directive approach


new dockerfile with cuda 10.1 and cudnn7

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1013   +/-   ##
=======================================
  Coverage   96.48%   96.48%
=======================================
  Files         151      151
  Lines        4974     4974
=======================================
  Hits         4799     4799
  Misses        175      175

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 2c6f0e9...1780704. Read the comment docs.


Arbitration for transmit messages.

I do not see where transmits are able to clear the transmit status.
It appears there may need to be a receive loop that processes the arbitration messages from the receiver during a transmit sequence. Transmit works with a small frame (7 bytes or less) that requires no arbitration.
In addition, I do not see where the uint32_t receive_arbitration_id is ever used.

I hope you don't mind, I edited your comment to include a proper code block.

Ah, I see one problem.
In CAN_ISOTP_RX_Loop, you have the following condition:
if (xSemaphoreTake(can0sem, 0) == pdTRUE) { continue; }

These means that the majority of the time, your loop is skipping the rest of the logic, so isotp_poll is rarely called.
Let's assume you only receive a message destined for your application every 2s. That would mean you call isotp_poll every 2.x seconds: the ISOTP protocol would time out.
One application I wrote using this library also utilises multiple threads.
For my specific use case, I had three threads.
Essentially, what I did was something like this.
This is a super quick and untested example in C++, but it should put you on the right track :)
/**
 * @file main.cpp
 * @author Simon Cahill<EMAIL_ADDRESS> * @brief A simple example of how to use ISOTP-C.
 * @version 0.1
 * @date 2023-06-08
 *
 * @copyright Copyright (c) 2023 Simon Cahill, licensed under the Unlicense.
 * https://unlicense.org/
 */

#include <mutex>
#include <thread>
#include <vector>

#include <linux/can.h>

#include <isotp.h>

using std::chrono::milliseconds;

using std::mutex;
using std::thread;
using std::unique_lock;
using std::vector;

static IsoTpLink* g_link = nullptr;

static volatile bool g_keepAlive = true;
static volatile bool g_hasMessageToSend = false;

static mutex g_mutex{};

static vector<uint8_t> g_inputBuffer{};
static vector<uint8_t> g_outputBuffer{};

namespace t = std::this_thread;

int main() {

    g_link = new IsoTpLink();
    isotp_init_link(g_link, 0xB0B, g_outputBuffer.data(), 4000, g_inputBuffer.data(), 4000);

    auto _pollThread = thread(pollThread);
    auto _sendThread = thread(sendThread);
    auto _rcvThread = thread(receiveThread);

    // do other stuff

    g_keepAlive = false;
    _pollThread.join();
    _sendThread.join();
    _rcvThread.join();

    return 0;
}

void receiveThread() {
    static int32_t CAN_FD = 5; // replace this with your actual file descriptor!
    timeval tval{0, (20*100)}; // timeout for 20ms
    vector<uint8_t> tmpBuf{};

    while (g_keepAlive) {
        if (select(CAN_FD, nullptr, nullptr, nullptr, &tval) > 0) {
            can_frame frame{};
            if (read(CAN_FD, &frame, sizeof(frame)) <= 0) { continue; }

            if (frame.can_id == 0xbad) {
                unique_lock locky(g_mutex);
                isotp_on_can_message(g_link, frame.data, frame.len8_dlc);
            }
        }

        // handle any fully received messages
        {
            unique_lock locky(g_mutex);

            uint16_t lengthOfReceivedIsotpFrame{};
            if (isotp_receive(g_link, tmpBuf.data(), 4000, &lengthOfReceivedIsotpFrame) == ISOTP_RET_OK) {
                // handle full message
                // if you're using multithreading, make sure the next function you call is
                // either really fast or that you free the mutex
            }
        }

        t::sleep_for(milliseconds(10));
    }
}

void sendThread() {
    while (true) {
        // only send messages if you actually have data to send
        if (g_hasMessageToSend) {
            unique_lock locky(g_mutex);

            if (isotp_send(g_link, g_outputBuffer.data(), g_outputBuffer.size() > 4095 ? 4095 : g_outputBuffer.size()) == ISOTP_RET_OK) {
                g_outputBuffer.clear(); // make sure you handle mutexes correctly here to avoid data races
            } else {
                // handle error
            }
        }

        t::sleep_for(milliseconds(10));
    }
}

/**
 * @brief Periodically calls isotp_poll, regardless of state.
 */
void pollThread() {
    while (g_keepAlive) {
        {
            unique_lock locky(g_mutex); // unique_lock ensure the mutex is freed after deallocation!
            isotp_poll(g_link);
        }
        t::sleep_for(milliseconds(3)); // choose a time that works best for you!
    }
}

int isotp_user_send_can(const uint32_t arbitration_id, const uint8_t* data, const uint8_t size) {
    // send frames somehow
}

Cool.  How would you scale this to include multiple CAN IDs to receive/transmit?  Multiple g_links?

You could easily filter the CAN IDs or (in C++) use multiple instances of a class where you pass the IDs as constructor arguments.
Otherwise a list of IsoTpLink objects would suffice and you could iterate through them (or create pointers to the instances) and save them as static/instance variables


Use correct base model

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Great to see that the CI/CD pipelines are so stable!


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_7e5362ea-a990-4ff9-b99b-bb0fc8005dab/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_7e5362ea-a990-4ff9-b99b-bb0fc8005dab.git

Docs Build status updates of commit fc390a0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

archiveSourceFolder/TOC.yml
:white_check_mark:Succeeded

archiveSourceFolder/content/someContent.md
:white_check_mark:Succeeded

archiveSourceFolder/content/sql-database-engine.png
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


docs as part of build

research how scalapb / lightbend do docs, find a way to publish paradox  (likely into gh pages)

@zenyui please any update on how to automate the doc deployment?

@zenyui please any update on how to automate the doc deployment?

Yeah the automation is easy, i'm just trying to figure out why the paradox search is breaking in the gcp storage static site deployment (with the double slash //)


Moving to node 6.9.2 and npm 3.10.9

Related ticket: https://github.com/CartoDB/cartodb/issues/11935
It will force us to have the same version of node (v6.9.2) and npm (v3.10.2) as we have in our staging and production servers.
And many thanks to shrinkwrap specialist @rochoa, who has make it possible ❤ .
How to test it

Install node 6.9.2, if you use nvm, it will install the necessary npm version, so safe and sound.
First thing, check that npm run update-internal-deps works in your machine.
Run your local CARTO environment and check if things work like the have to.
Then check the same in staging, check deploy times and compare with a previous one.

cc @CartoDB/frontend because it will force us to use the same version of node and npm for frontend development. And also is great to share all the black magic @rochoa has done in order to keep using shrinkwrap :dancer:.

Should we open a ticket to update vagrant?
El 7 abr. 2017 13:16, "Javier Álvarez Medina"<EMAIL_ADDRESS>escribió:

@xavijam commented on this pull request.
In CONTRIBUTING.md
https://github.com/CartoDB/cartodb/pull/11941#discussion_r110367727:

-5. That's it. When you change any Builder Javascript file grunt dev will build the application bundle and grunt affected_specs will build the specs.
+4. That's it. When you change any Builder Javascript file grunt dev will build the application bundle and grunt affected_specs will build the specs.
Ha! Ok, good to know 💃.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/pull/11941#discussion_r110367727, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABTbOz5U6EindHQvXm35_fTkXyJPEOh1ks5rthsOgaJpZM4M2xLV
.

cc @luisbosque

Hey @rochoa @jorgesancha, we have a problem here with the previous version of CartoDB.js.

I feel we should update the version in CartoDB.js, but it could take us a bit more in order to check everything is ok if we use a new version there :(.

I think we have to go ahead... Otherwise we are stuck with not being able to update the legacy machines.

cc @alonsogarciapablo

Forget my comment, I turned on the alarms when it is not necessary. It is due to another problem with the installation.

I've found two issues:

[ ] CI node is not using version 6 (cc @CartoDB/systems).
[ ] Old editor tests are not passing using the SpecRunner interface :S @CartoDB/frontend.

Second problem is happening in master right now, not related with this PR.

Fixed second bullet thanks to https://github.com/CartoDB/cartodb/pull/11951 and @ivanmalagon 💋 .

So, for some time we will have two shrinkwraps, the generated by node 6.9.2 called npm-shrinkwrap.json and the one generated by node 0.10.x called npm-shrinkwrap-010.json.
cc @CartoDB/systems

It is specified in the CONTRIBUTING.md, but yes, we can add it. Bad thing is I don't know if it could break the trick we need for deploys. Could we add it after we have node 6 in all machines?

Pending to update both dependencies due to last changes from CartoDB.js (https://github.com/CartoDB/cartodb.js/pull/1626).

test this please

retest this please

retest please

Frontend tests are now running with a node6 testing server... Let see if we are lucky https://ci.cartodb.net/job/CartoDB-PR-testing-frontend-node6/1/console

retest this

retest this please

test this please

Updated with last changes from dependencies :dancer:.

retest this please

retest this please

retest this

please, retest

retest whenever you want

please, retest!

Merging, frontend tests passing!


[DMS] Remove nonprofit background image

Nonprofits won't be able to upload their own background image, so we need to remove the backgroundImage attribute from our website.

[ ] Create a migrations script to remove the background field from all the nonprofits in our db.
[ ] Remove the background field from the nonprofit type in utils, and the nonprofit schema in server/models.
[ ] Refactor the create nonprofit action, DonationPageLayout (i.e. remove StyleProps, backgroundImage, backgroundSize, backgroundRepeat, backgroundPosition from the styles...), and refactor the DonatePage
[ ] Add a backgroundColor field in the DonationPageLayout style with a color of "#FFFAF1" (off-white)

@KoolCards Will the non-profit profile page use the same background image for all non-profits?

yea the plan is to use the same background image for all nonprofits.


Not found: cwd running the Cmake task on linux with working directory set to $(Build.StagingDirectory)

This issue is tied to the latest release, and did not exist in the previous release.  I had a build system up and running last week, and when I tried to build a fresh one this week, the cmake task and everything after that didn't work.
My cmake build was working based on<EMAIL_ADDRESS> My second machine which I set up a week later got<EMAIL_ADDRESS>The error message I recieved was as follows:
#[Error] 2016-03-11T00:52:34.803Z: Not found cwd: /home/vsoagent/BuildAgent/_work/2/s//home/vsoagent/BuildAgent/_work/2/a
I have traced this to the cmake2.js file in the _work/tasks/CMake/1.0.9 path.  I have confirmed through logging that the path in the error message is exactly what the task gets when it calls
var cwd = tl.getPathInput('cwd', false);
As you can see, the cwd input passed into the cmake task has been resolved incorrectly - instead of treating $(Build.StagingDirectory) as an absolute path, it is attached it to the source directory.
consequently, the task fails when it calls
tl.checkPath(cwd, 'cwd');
I consider this a break - I had a working build, that stopped working, but I could be wrong there.  For CMake, it is awefully convenient to use $(Build.StagingDirectory) to run the build in, instead of creating a subtree inside the source folder.  That being said, perhaps using $(Build.StagingDirectory) is not the right way to use the staging directory?
I was able to trace the rewriting of the path to the prepare phase, before the task was called.  I believe it was happening in agent/job.js, in JobRunner processInputs call.  I have managed to lose all of the logs, but I can reproduce them if more information is needed to discuss the issue.  The first sighting of the variable getting expanded incorrectly was logged starting with "rewriting value for "...
I was never able to get a build working with any other value for the working directory in my build script: I am sure with enough poking around I could have gotten all of my commands running properly, but it was easier to just copy the build agent from my first working machine to the new one instead of starting from scratch.  However, manually edit the test result publisher to be able to publish my unit test xml results from googletest -- it looks like that bug was already fixed in the newer version.

This is fixed in 0.6.1 agent


Unable to create stub responses on the website

Unable to create stub responses on the website
Expected behaviour
Able to create stub responses on the website
Actual behaviour
Unable to create. Website is unresponsive , there is no content
Steps to reproduce

Go to http://www.mbtest.org/imposters
Click on Add Icon
Click on Add Icon under stubs
Click on the Add Icon under responses

Software versions used
OS         : MAC OS
mountebank : Website
node.js    :
  (only if installed via npm)
Installation method :
  (npm, zip, tar, pkg, deb, rpm)

Used chrome, IE 8 and Safari
Log contents in mb.log when running mb --loglevel debug

Log contents here

Duplicate of https://github.com/bbyars/mountebank/issues/35


Ability to move messages from failed queue back to queue

Is there a way to move messages from failed queue back to queue for processing once for example the sysadmins have fixed the email server etc.. We rely on this on ActiveMQ and MSMQ (although with MSMQ we have to use a third party tool to handle this)

I did the trick via UI to move a job from failed to inactive and then the job is picked up to run again.
Is there any way to do this using the REST ?
cheers.

if you check the code behind that UI action you will find out the actual REST request to change job state, however I'm not convinced to expose that in public API documentation for now :)

Oh right, that's a good one.
I will check, cheers for the tip.

did you get to a solution ?

I did not got any solution for this, in fact I ended having to abandon kue because of the absence of this feature.

kue.Job.rangeByState( 'failed', 0, n, 'asc', function( err, jobs ) {
  jobs.map( function( job ){  job.inactive();  });
});

OR
queue.inactive( function( err, ids ) {
  ids.map( function( id ){
    kue.Job.get( id, function( err, job ){
      job.inactive();
    });
  });
});

Just curious, is there still an actual issue here?

I just keep it opened to remember to add a UI trigger for requeue-ing jobs.


Update of GKE deployment

Composed of several PRs to prevent conflicts between changes:
#24958
#25508
#25748
#25993

Added support for GCP Datastore namespaces
Added Terraform variables for Redis configuration
Changed default machine type for GKE nodes
Re-configured GKE pods autoscaling based on RAM and CPU for new machine types
Re-configured GKE pods resources for new machine types
Autoscaling values maxReplicas and minReplicas defined via Helm variables
Updated Gradle Terraform plugin to the latest version (1.4.2)
MITM proxy replaced by Firewall
Updated README files
Added support for multiple simultaneous Playground deployments to the same GCP project
Renamed "location" varaible to "zone" to follow common GCP terms
Fixed an issue with deployment to europe-west1 region
AppEngine deployment was deprecated.


Added story#add_owner

This might be an acceptable compromise to not supporting << for owner_ids. Also consistent with the add_label interface which exists for the same reasons.

@drselump14 how does this look? Not << but much clearer interface.

Coverage increased (+0.06%) to 96.534% when pulling 14fee7a1ae86eddeee4380d2222a81564319217c on add-owners into fbbb085bbf0cd9949e78bc6625952bef21ad8893 on master.

@forest it's fine I guess ... consistent with what stated on readme

@drselump14 feel free to take a stab at implementing <<. I'm not against it, but it wasn't worth the effort for me. I haven't dug in too deep yet, but some of the http://dry-rb.org/gems gems could be used to replace Virtus and might make this easier. It would be a huge rewrite. From what I have read dry-rb gems are the next generation of Virtus.


Create Backup of all pods in multiple namespaces and then restore the backup

Test Case Precondition:

Kahu project installed in given name-space (test-kahu) 2. All below pods should be up and running:
a. backup service
b. Meta service with nfs provider c. nfs-server
Metadata location is created already
Namespace test-ns1, test-ns2 is created and contains some of the kubernetes resources.

Test Case steps:

Create below backup CR using kubectl command (use kubectl create -f <backup.yaml>)
apiVersion: kahu.io/v1
kind: Backup
metadata:
name: backup-Kahu-0001
spec:
includeNamespaces: [test-ns1,test-ns2]
metadataLocation: nfs includeResources:

name: kind: Pod
isRegex: true

Use kubectl describe backup  -n test-kahu
Get inside nfs server pod and check for the content inside mount path given (use command kubectl exec -ti  -n test-kahu /bin/sh)
Create a restore CR on new namespace (restore-ns)
apiVersion: kahu.io/v1
kind: Restore
metadata:
name: restore-Kahu-0001 Spec:
backupName: backup-Kahu-0001 namespaceMapping:
test-ns1 : restore-ns1
test-ns2 : restore-ns2

Expected Result:

In step 2,
a) Verify that backup stage is Finished and State is Completed
b) Verify the resource list in status shows all the required resources
In step 3, verify that
a) tar file is created with name of backup
b) After untar file, All pods in the namespace test-ns1 and test-ns2 are backuped.
In step4, verify that
a) Backed up pods are up in new namespace restore-ns1 and restore-ns2 respectively.

Why this issue to fixed / feature is needed(give scenarios or use cases):
This is a testcase which is to automated to make sure deployment is properly backed up and restored
How to reproduce, in case of a bug:
Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

@kalaiselvikks76


FIX - Multiple HTTP verbs for a path

Allow multiples verbs for a specific path.

Thanks @spawnrider


Fish shell script linting with fish --no-execute

Creating this issue to track a couple things I've already tried.
There are a few issues I've identified why I think it doesn't work by default (but I'm not sure).
First, fish --no-execute outputs a code-window like so:
path/to/script.fish (line 5): Missing end to balance this function definition
function my-function
^~~~~~~^
warning: Error while reading file path/to/script.fish

But we only want to parse the first line with errorformat.
Second issue is that it only reports line, not column, but I think column is required? It also doesn't report an error level, which I think is also required.
null-ls worked around these by just defaulting column to 0 if it was nil, and skipping over any lines that fail to parse with errorformat.
I've got a modified lintCommand that attempt to fix these issues by:

prefix each output line with e: so we can parse the error level as error
modify the (line 5) to default column to 0 like (line 5, col 0)

The lintCommand I came up with is:
fish --no-execute path/to/script.fish 2>&1 >/dev/null | awk '/\(line [0-9]+):/ { sub(/\)/, ", col 0):"); print "e:" $0 }'

Which gives output like:
e:path/to/script.fish (line 5, col 0):: Missing end to balance this function definition

which I then tried to parse with lintFormats = { '%t:%f (line %l, col %c):: %m' }
But I am still not getting diagnostics in the editor.
Any ideas how I can further debug this?

Tried out the test code, I don't think you need to do any of that. errorformat will set the column number to 0.
Here is the format I did for it to work:
lintFormats = { '%.%#(line %l): %m' }

%f doesn't work because it's looking for a full path to the filename, but the output does not. So with %.%# it just matches anything (kinda like .* in regex).
However, it'd be nice to make use of multi-line format (check out :help errorformat-multi-line) so that we can parse the column number using the %p specifier (which reads the ----^ format). It's something I haven't extensively used 😅

Oh, awesome! I'll submit a PR with this change.


Integrate gRPC Runner Service

Solves #202

Currently facing the following issues:
@adambabik

InputData sent in the sendRawInput function (located in runner.ts > GrpcRunnerProgramSession) is completely empty by the time it gets to runnerService.Execute on the server. It's getting totally dropped, and this is a big blocker for interactive support. Do you have any idea why this might be? @sourishkrout please test and let me know if you have the same issue/any thoughts here, I have absolutely no idea what could be causing this...
I get the following trace when running Execute. I think what's happening here is that the program has exited, so the stream has ended, but srv.Recv() still gets called one last time, resulting in this "rpc Canceled" error. If this is not a client-side issue, I think we should make an issue about it on the runme repo.

2023-02-14T15:23:11.950-0600	INFO	runner/service.go:122	running Execute in runnerService
2023-02-14T15:23:11.969-0600	INFO	runner/service.go:204	finished command execution	{"exitCode": 0}
2023-02-14T15:23:11.969-0600	INFO	runner/service.go:173	failed to receive requests; stopping the command	{"error": "rpc error: code = Canceled desc = context canceled"}
2023-02-14T15:23:11.969-0600	INFO	runner/service.go:175	failed to stop the command	{"error": "os: process already finished", "errorVerbose": "os: process already finished\ngithub.com/stateful/runme/internal/runner.(*command).Stop\n\t/Users/mxs/Projects/runme/internal/runner/command.go:343\ngithub.com/stateful/runme/internal/runner.(*runnerService).Execute.func1\n\t/Users/mxs/Projects/runme/internal/runner/service.go:174\nruntime.goexit\n\t/opt/homebrew/Cellar/go/1.19.5/libexec/src/runtime/asm_arm64.s:1172"}

Is there any way to request a program exit other than sending an interrupt? Currently if the user requests a command stop,  the client sends an EOF, but then the program continues running. I think maybe that the program should try to stop if its still running during an EOF, since an interrupt can be cancelled by the program, but something like cmd.Stop() cannot - what do you think?

@sourishkrout

I added the main functionality to kernel.ts as an inline async function. Much of this is copy/pasted and/or adapted from taskExecutor and shellExecutor. I want to bring this to its own file/method, but its not clear exactly how. I basically see two ways to proceed:

Add a new executor function which runs the given runner. This is basically what I've done already, but results in lots of duplication/furthering the aforementioned issue of cementing the executor model.
Create an abstraction - my idea is something like an abstract class ExecutionNode, so for the runner it will be RunnerExecutionNode. For now it will be implemented rather simply (maybe it flatly produces some kind of "ExecutionResult" interface), but I think this is a good step towards things like multiple output stages, cleaner input utilization, chaining, etc.

Basically, if I understood correctly, in our 1:1 you were describing a desire for a kind of "middle ground" solution between a simplistic function (executor) and a full-blown solution. I think I can implement a class (ExecutionNode) which satisfies this desire and also can be built upon going forward. Maybe the exact abstraction described in (ii) isn't the one you want to go with, but in any case I don't think it will be a significant development effort to implement it. But I need your approval before going this way, as we could easily just do (i) and then work towards (ii) later/in follow up PRs, and I know this feature is time-sensitive.

Other issues:

Currently there is one environment per Kernel. We need to set-up a system that puts the session-id on the notebook metadata if we want per-notebook environment. @sourishkrout I could use your advice here - where in the code is the mechanism to manage notebook metadata? This metadata in particular should probably not be sent to the serializer since its irrelevant for serialization.
Environment is maybe not deleted on exit. I tried to make this happen as part of the dispose cycle, but it's still janky and needs further testing

InputData sent in the sendRawInput function (located in runner.ts > GrpcRunnerProgramSession) is completely empty by the time it gets to runnerService.Execute on the server. It's getting totally dropped, and this is a big blocker for interactive support. Do you have any idea why this might be? @sourishkrout please test and let me know if you have the same issue/any thoughts here, I have absolutely no idea what could be causing this...

I think i see the problem and have a hunch why but I'm not sure if I'm looking at the right "issue". What are the steps to reproduce for you @mxsdev?

@sourishkrout
I included a line that printed the InputData as-is in the runme go code, and it was always empty - didn't matter what I ran. Just tested node ./scripts/stdin.js and have the same issue.
I use zsh on my system, if that's relevant.

@sourishkrout
I included a line that printed the InputData as-is in the runme go code, and it was always empty - didn't matter what I ran. Just tested node ./scripts/stdin.js and have the same issue. Also have the same issue with a read command in a bash script.
I use zsh on my system, if that's relevant.

I believe the problem you're running up against here is that the Pty is not fully implemented. In other words, individual keystrokes result in individual calls of input data (and likely individual requests) and aren't being buffered until, let's say RETURN is being pressed what would tell the Pty to send the buffered input stream off to the server.
That's the fun of implementing the Pseudoterminal, now one has to define and implement the different user interactions with a underlying terminal.

I get the following trace when running Execute. I think what's happening here is that the program has exited, so the stream has ended, but srv.Recv() still gets called one last time, resulting in this "rpc Canceled" error. If this is not a client-side issue, I think we should make an issue about it on the runme repo.

Ideally, you'd like to notify the runner service that you want to drop the connection and let it do it. For example, when running a long running process like an HTTP server, try to kill it first by sending 0x03 byte (you likely need to start it with TTY (ExecuteRequest.tty). Then, the server should close the connection and send the exit code of the process. Alternatively, you can handle the rpc Canceled error if that's what you expect.

Is there any way to request a program exit other than sending an interrupt? Currently if the user requests a command stop, the client sends an EOF, but then the program continues running. I think maybe that the program should try to stop if its still running during an EOF, since an interrupt can be cancelled by the program, but something like cmd.Stop() cannot - what do you think?

Can you send the command and how you execute it (with TTY or not), please? Typically, the command should exit on its own. If you want to interrupt it, currently, you must start it with TTY and send 0x03 and 0x04 bytes (at least for bash).
Regarding the second part, when a program handles signals and ignores them, the client can drop the connection and the program will exit. You should try that with https://github.com/stateful/runme/pull/127 as it might have been broken.
Another solution would be to add a field to ExecuteRequest which would indicate a force stop.

Alternatively, you can handle the rpc Canceled error if that's what you expect.

There is actually another way that is preferable. I don't know exactly how the TS interface looks like but when you start a bi-directional stream, you can close the send direction with stream.CloseSend() in Go. This will notify the server that the client no longer wants to send anything. When this happens, the runner service will close the process' stdin, which usually terminates the whole process.
Check out service_test.go to see different variants. Overall, the following should always hold:

If you start an execution with TTY, try to interrupt the running command and close the send direction.
If you start an execution without TTY, the only reliable way is to cancel, unless the program exits when the stdin is closed (bash works that way, for example), then closing the send direction is enough.
If the executing command is unresponsive, cancelling will force it to stop.

I added the main functionality to kernel.ts as an inline async function. Much of this is copy/pasted and/or adapted from taskExecutor and shellExecutor. I want to bring this to its own file/method, but its not clear exactly how. I basically see two ways to proceed:

Add a new executor function which runs the given runner. This is basically what I've done already, but results in lots of duplication/furthering the aforementioned issue of cementing the executor model.
Create an abstraction - my idea is something like an abstract class ExecutionNode, so for the runner it will be RunnerExecutionNode. For now it will be implemented rather simply (maybe it flatly produces some kind of "ExecutionResult" interface), but I think this is a good step towards things like multiple output stages, cleaner input utilization, chaining, etc.

Basically, if I understood correctly, in our 1:1 you were describing a desire for a kind of "middle ground" solution between a simplistic function (executor) and a full-blown solution. I think I can implement a class (ExecutionNode) which satisfies this desire and also can be built upon going forward. Maybe the exact abstraction described in (ii) isn't the one you want to go with, but in any case I don't think it will be a significant development effort to implement it. But I need your approval before going this way, as we could easily just do (i) and then work towards (ii) later/in follow up PRs, and I know this feature is time-sensitive.

Just a quick comment on this one: I'd like to keep us focused on getting this to a place where it's shippable. Meaning, not try to do too many things in one PR. So my advice would be to potentially keep it simple and see if we can design a test suite that will help us with a refactor later. If there's an incremental step forward we can make, feel free to go ahead. From what I understand, I believe your thoughts are on the right track. Again, I'd suggest to keep it simple for now and capture notes for another PR to evolve executors down the line.

Should be good on my end, basically waiting for #131 and #130 before we can review/merge 👍

PR should be basically ready, contingent on runme #134 being merged.

cool 🤘. i'll start my review in a little bit. hopefully will finish before EoD.

cool 🤘. i'll start my review in a little bit. hopefully will finish before EoD.

FYI, if you want to do testing, you'll need to link the newest generated files from that PR, since there's been a change to the proto defs.

Overall this is a big step in the right direction. Let's figure out what the definition of "done" is for this PR.

Let's look into message: 'gRPC Server closed output stream unexpectedly!' after interactive execution completes.
List of incomplete functionality outside of this PR:

[ ] Environment Variables inherited from host-process
[ ] Use correct $SHELL
[ ] User-prompts for ENV variables
[ ] Deep integrations: Vercel/deno
[ ] Terminal dimensions (not high priority)

@sourishkrout Anything more preventing this merge?


Adding Variables to an existing Environment does not work

Problem Description
Safe settings does not detect addition of environment variables.
What is actually happening
Steps to reproduce:

Create Environment first time with one variable, Safe settings will create that environment and add variable to it.
Update Settings and add second variable to an existing environment. Safe settings does not determine the changes to the environment variable and hence does not create it.

What is the expected behavior
It should determine that variable has been added to the environment during dry run and implement changes once PR is merged.
Error output, if available
After debugging the code, looks like mergeDeep.compareDeep(existingRecords, filteredEntries) is not able to determine the changes correctly.
Please find debug screen shots
existingRecords object with one variable in it

filteredEntries object with two variable in it

results object with addition key as empty

PR Screenshots:

Dry run results on my PR (No addition on Environment Detected)

Context
Are you using the hosted instance of probot/settings or running your own?
Running our own and deployed using community helm chart
If running your own instance, are you using it with github.com or GitHub Enterprise?
Both, However, noticed similar behavior on both instance.
Version of probot/settings
2.1.10
Version of GitHub Enterprise
3.11.10

PR to fix the issue
https://github.com/github/safe-settings/pull/665

This is fixed after meting PR 665, So closing this issue.


Feature: parameters in metapage definitions

This would allow metapages defined with json that allow parameters.
For example, a compute API server  could run either locally, or via some company. The API is the same, but you don't want to hard-code it, since then it is too rigid.

This will be implemented by https://metapage.io, not this core library.


airs:Service needs a dct:title to refer to it by name

looking at Service, I see we have no dct:title.  I think we should add one there also.

resolved with 1df51e6af93cc7c4dc0f1c4b9acc24c5c51a2b5b


Add client administration interface.

What's this PR do?
This pull request moves the OAuth Clients administration interface from Aurora over into this application. This allows developers to create, edit, and view OAuth clients now that we've retired Aurora.
How should this be reviewed?
I've broken this work into separate commits:
💁♂ I added some remaining helpers from Aurora that were used in this flow in 8397119
👀 I added views & assets in 80d73f4. These are slightly modified from their original counterparts since we don't use the {!! Form:: helpers in this application. Where it made sense, I used our existing form partials to build these forms.
🤖 I added the routes & controller in e5c7520. This involved merging logic from Aurora's ClientController and Northstar's API ClientController to ensure we kept the same behavior.
🔗 I added links to this new section to the homepage & navigation bar in 30c4a24.
🥡 Finally, I updated the Client model to always return an array for redirect_uri in 6a29a5d. This is something we'd previously handled in the transformer, but now that this isn't hitting our API it makes sense to move into the model!
Any background context you want to provide?
🔏
Relevant tickets
References Pivotal #176850872.
Checklist

[ ] This PR has been added to the relevant Pivotal card.
[ ] Documentation added for new features/changed endpoints.
[ ] Added appropriate feature/unit tests.
[ ] If new attributes were added to users, there is a corresponding PR to surface these in Aurora.
[ ] If new attributes were added to users, then the data team already knows about these changes.

It does look like some tests need updating though 🤔

Ooof, it sure does! 👀

A ha! After using $this->withoutExceptionHandling() to print the 500 we were receiving on this test's HTTP request:
Symfony\Component\Debug\Exception\FatalThrowableError: Argument 1 passed to League\OAuth2\Server\Grant\AbstractGrant::validateRedirectUri() must be of the type string, array given, called in /home/vagrant/Sites/northstar/vendor/league/oauth2-server/src/Grant/AuthCodeGrant.php on line 263

/home/vagrant/Sites/northstar/vendor/league/oauth2-server/src/Grant/AbstractGrant.php:260
/home/vagrant/Sites/northstar/vendor/league/oauth2-server/src/Grant/AuthCodeGrant.php:263
/home/vagrant/Sites/northstar/vendor/league/oauth2-server/src/AuthorizationServer.php:157
/home/vagrant/Sites/northstar/app/Http/Controllers/Web/AuthController.php:65

Since the mutator now always returns an array for $client->client_secret, we have to pick the "first" one in this test. Otherwise we end up serializing an array (e.g. &redirect_uri[0]=…) into this URL and that's not what we want.
Fixed up in d7bd5cb & we're back to green! 🟢


k-means clustering data save and reload

Currently the ‘K-Means Clustering’ table must be generated  afresh (not from saved) & merged with concatenated Master (ex ‘saved’)  for step # 3 to work properly [using saved K-means table causes table #3 to miss cluster column]

6291e733d87ff69a0c916801abd0a61139b5c9a4


swDest in a subdirectory seems to cause incorrect generated paths

Library Affected: workbox-cli
Browser & Platform: all browsers
Issue or Feature Request Description:
My workbox configuration file looks like the following:
'use strict';

module.exports = {
  globDirectory: 'www/',
  globPatterns: [
    '**/*.{html,jpg,mjs,css}'
  ],
  swDest: 'www/service-worker/sw.js'
};

(This was generated from npx workbox wizard, then fixed to make ESLint pass.)
That is, my app is located in www/, and I want to generate a service worker in www/service-worker/sw.js. (That is, I want the 4 files workbox generates to go into www/service-worker/, instead of all over my root www/.)
However, the generated files don't seem to account for the service worker being in a subdirectory. They contain lines like
{url:"images/pea-protein.jpg",revision:"b9d1be7cf1fa59d0982288f2149e9167"}

which cause the following problem in the JS console
WorkboxError.js:28 Uncaught (in promise) bad-precaching-response: bad-precaching-response :: [{"url":"http://localhost:5000/service-worker/images/pea-protein.jpg","status":404}]
    at y.u (http://localhost:5000/service-worker/workbox-1bbb3e0e.js:1:5420)
    at async Promise.all (index 1)
    at async y.install (http://localhost:5000/service-worker/workbox-1bbb3e0e.js:1:4833)

i.e. it is looking for images/pea-protein.jpg in the service-worker/ directory, not relative to the root.
You can see the full project setup at https://github.com/domenic/remember-to-eat/commit/8166ddcee87c63092618152dc5fd992d335b2151, although I have not deployed that commit to a live URL since it's broken. I'm happy to do so if that would be helpful.
This seems like a bug---especially given that the config file was generated by the wizard---so I'm reporting it here instead of Stack Overflow. But maybe there's a better config file I should be writing...

👋 @domenic!
I wanted to cover two points:
First, the wizard experience is unfortunately not going to ask about all the possible options. (I'm honestly not sure how useful the wizard flow is anymore, as the configuration has grown since we originally developed it.) One option that you can add to your configuration, if you need to adjust the URLs that are generated in the manifest, is modifyURLPrefix. Something like:
module.exports = {
  // ...other options...
  modifyURLPrefix: {
    '': '../',
  },
};

would automatically prepend '../' to the start of your manifest's URLs. You can get "more fancy", if you need, via the manifestTransforms callback as well.
Second, and this gets to the root of why the generated manifest might not meet your expectations, are you sure you want to host your service worker script from the URL /service-worker/sw.js? Because of service worker scoping restrictions, that means the only web pages that the service worker can control are pages whose URL prefix is also /service-worker/, and I'm assuming that you're not actually using that URL prefix for your HTML.
If you were to use the Service-Worker-Allowed response header, you could override that restriction, and using modifyURLPrefix would then allow you to "fix" your URLs. But the expectation is that most folks would end up needing to serve their service worker script from their WWW root in order to give their service worker a change to control pages.

Second, and this gets to the root of why the generated manifest might not meet your expectations, are you sure you want to host your service worker script from the URL /service-worker/sw.js? Because of service worker scoping restrictions, that means the only web pages that the service worker can control are pages whose URL prefix is also /service-worker/, and I'm assuming that you're not actually using that URL prefix for your HTML.

Ah, thanks! I guess that is not what I want, after all. And probably adding the Service-Worker-Allowed header is not worth it just to keep the 4 generated files quarantined to their own folder. I'll just have to live with a messy root directory.
At this point my issue is solved, but I'll let you decide whether to close this, or use it as a tracker bug to try to give better error messages. (Perhaps workbox generateSW could give an error when it generates a service worker with paths, like service-worker/images/pea-protein.jpg in my example, that don't exist?)

The difficult part of that is that a standalone build tool doesn't know how your web hosting environment is set up. Figuring out whether service-worker/images/pea-protein.jpg is a valid URL is doable if we can safely assume that your web server just hosts static documents starting from a given directory as your WWW root, but that assumption falls apart for even moderately complex web servers—which is why we expose modifyURLPrefix and manifestTransforms to allow folks to adjust their URLs as needed.
(If your overall goal is to have fewer files in your top-level directory, adding sourcemap: false and inlineWorkboxRuntime: true to your  config will lead to only a single generated file, but you'll lose out on some update optimizations from breaking out the Workbox runtime code from the top-level service worker that contains your precache manifest.)


2.2.0 branch not version checking ElasticSearch properly

Getting a warning complaining of version mismatch. Bigdesk won't seem to let me connect after acknowledging the warning.
Installed ES 0.20.5, and lukas-vlcek/bigdesk/2.2.0
Here is the warning displayed in the popup:

Bigdesk may not work correctly!
Found ES node version: 0.20.5
Requires ES node version: 0.20.x

I am archiving this repository now. Thanks for contributions.


Add support for S3 storage providers

Longtail supports both Google Cloud Storage and S3 buckets, so I believe adding S3 support could open doors to more than one S3 storage provider (not just AWS, assuming https://github.com/DanEngelbrecht/golongtail/issues/209 gets implemented). I personally use DigitalOcean as my cloud provider, so it'd be great to not be locked in to using Google also.
I've started working on an implementation in a fork

Hi,
Thanks for showing interest in Gamecure! This is as you stated in the other Issue an early alpha or an MVP for Content Creators at GOALS and the way we work here (plastic, single repo for engine+game, jira, GCS).
The plan from the start was to make it possible to extend Gamecure with other cloud providers, VCS etc. and it's something we definitely want to do.
Documentation is not there yet, but it's something that we keep improving.
Regarding S3 support I've got some news for you.
This library is currently in development and we plan to replace the current go-longtail client with it.
https://github.com/Golle/longtail
This lib will make it easy to create your own BlockStore implementations and support any cloud provider (or local storage) you have.
Here's a simplified example of how a Remote store could be implemented once we have have integrated this lib.
public class CustomRemoteBlockStore : IBlockStore
{
    private static readonly HttpClient Client = new();

    private readonly string _baseUri;
    private readonly string _fileExtension;

    public CDNRemoteBlockStore(string baseUri, string fileExtension)
    {
        _baseUri = baseUri;
        _fileExtension = fileExtension;
    }

    public Task PreflightGet(ReadOnlyMemory<ulong> blockHashes)
    {
        // Preload any hashes if needed
        return Task.CompletedTask;
    }

    public async Task<StoredBlock?> GetStoredBlock(ulong blockHash)
    {
        // Get the stored block from any storage (Azure, S3, GCS, network drive, local filesystem)
        var blockname = $"0x{blockHash:x16}";
        var result = await ReadBytesFromStore($"{_baseUri}/{blockname.Substring(2, 4)}/{blockname}{_fileExtension}");
        return result != null ? new StoredBlock(result) : null;
    }

    public async Task<StoreIndex?> GetExistingContent(ulong[] chunkHashes, uint minBlockUsagePercent)
    {
        // Read the store index file
        var result = await ReadBytesFromStore($"{_baseUri}/storage/store.lsi");
        return result != null ? new StoreIndex(result) : null;
    }

    private async Task<byte[]?> ReadBytesFromStore(string uri)
    {
        var result = await Client.SendAsync(new HttpRequestMessage(HttpMethod.Get, uri));
        if (result.IsSuccessStatusCode)
        {
            var bytes = await result.Content.ReadAsByteArrayAsync();
            Logger.Trace($"Read from CDN url: {uri} statusCode: {result.StatusCode} elapsed: {timer.Elapsed.TotalMilliseconds} ms Total bytes: {bytes.Length}");
            return bytes;
        }
        return null;
    }
}

It would be awesome if you could join our public discord https://discord.com/invite/goals and ping me and we can have a chat about your use case and how your team would benefit from using Gamecure.

Regarding S3 support I've got some news for you.
This library is currently in development and we plan to replace the current go-longtail client with it.
Golle/longtail

Cool I guess; the golongtail CLI tool already supports AWS S3 and is a minor revision away from supporting non-AWS S3. I think this move to using the C bindings directly and reimplement the cloud provider side of thing is the right path, but it's not the shortest path for S3 🤷
Anyway, thanks for the response and diligent effort. I'm not really a fan of the opinionated structure and tight coupling the structure the app has and would require a bit of a overhaul to rethink interfaces to be more open to be flexible for other use cases. C# isn't my forte, so rapid prototyping just isn't as quick for me as NodeJS and the npm dependency ecosystem. As a typical software engineer, it's tempting for me to just start my own project from scratch 😅 I definitely don't like reinventing the wheel and spending time writing something from scratch however


[Draft][Unity][Transform] Extract partial-tuple-usage from FuseOps

Prior to this commit, the FuseOps pass explicitly tracked usage of
tuple arguments, to minimize the set of arguments provided to each
kernel.  The additional tgracking and handling of partially-used
tuples makes it difficult to follow the primary changes being made by
FuseOps.
This commit implements the same functionality in terms of the
ExpandTupleArguments and RemoveUnusedParameters transforms,
introduced in https://github.com/apache/tvm/pull/16115 and
https://github.com/apache/tvm/pull/16116 respectively.  By using these
passes before the main FuseOps changes, partial tuple usage is
already handled at that point.
This commit is intended to minimize any changes to user-facing
behavior, and so these pre-process passes are currently used
internally by FuseOps.  This may be avoided in the future by pulling
this internal delegation out into a lowering pipeline.

This PR is marked as a draft, until the pre-requisite PRs #16115, #16116, #16117, and #16118 land.

All prerequisite PRs have now landed, and this PR is ready for review.

Failing unit tests are due to MSC relying on relax variable names being preserved.  https://github.com/apache/tvm/pull/16349 is submitted to fix these unit tests, after which CI can be re-run for this PR.


Added a gaming breadcrumb

Fixes Issue🛠 #280
Closes #280
Description👨💻
It is a gaming breadcrumb which looks sassy and modern too.

Type of change📄

[] Bug fix (non-breaking change which fixes an issue)
[] New feature (non-breaking change which adds functionality)

How this has been tested✅

Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷

#280  have new pr please accept it and apology for spamming .
please consider me as a learner i will try to resolve it

please merge it @Rakesh9100 and apology for it


Wrong structure mapping in specification

https://swagger.io/docs/specification/components/ defines following mapping between old and new structures:
OpenAPI 2.0                    OpenAPI 3.0
'#/definitions/User'         → '#/components/schemes/User'
'#/parameters/offsetParam'   → '#/components/parameters/offsetParam'
'#/responses/ErrorResponse'  → '#/components/responses/ErrorResponse'
'#/components/schemes/User' is wrong, it should be 'schemas', not 'schemes'.

Thanks. I think the correct repo for that site is https://github.com/swagger-api/swagger.io - reporting it there will reach the right people.

@MikeRalphson Thank you for pointing into the right direction!


Add an optional parameter -o to integtest.sh

SignedOff by<EMAIL_ADDRESS>Description
A new optional argument OPTION [-o ] is added to integtest.sh
Issues Resolved
Fix to the issue #3316
Call to ./integtest.sh from integ-workflow can now use additional -o default parameter when -t is passed which executes the tests individually instead of altogether. This is optional and does not change the behaviour if -o is not passed.
Check List

[ ] Commits are signed per the DCO using --signoff

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

Here is the bug issue created @ashwin-pc @kavilla https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/648
Thanks!

@Divyaasm can you please backport this to 1.3 branch to move forward with 1.3.10 release.
https://github.com/opensearch-project/opensearch-build/issues/3331


Remove UWP (uap) references and special cased code

Some boy scouting on DataTestUtility (removed unused code)
fixes #2482

@ErikEJ personally, I support this pull request, but @David-Engel should include the conclusion.

@JRahnama Of course!

LGTM, with just a minor adjustment. Thank you @ErikEJ .

@ErikEJ if you can address the conflict this is ready to merge.

@JRahnama Which conflict?

@JRahnama Which conflict?

This is weird. I saw the conflict this morning.


Build reasonable testing for the playground

At the moment, the playground is tested poorly. We need to test the Typescript Frontend and the WASM backend.
The correctness of the examples will be tested in a separate issue. #56

[x] Test the frontend using https://reactjs.org/docs/testing.html
[x] Test the WASM part using unit tests and one integration test

Closed by #66


Shyrma casual conv1d

add causal padding mode to conv1d operation

I've pushed up some causal conv1d gradient checks.
Here's output for the first few cases:
https://gist.github.com/AlexDBlack/1bf0c9222f7f16628d1df3e68ac5fd7e
note sz there is sequence length
One thing I did notice is that the input gradients appear to have an off-by-1 issue
So analytic (op) gradient in[0,0,1] is equal to numericalGrad[0,0,0] and so on


Metamask mobile: issues when number pad is open

Top bar gets hidden and there's a gap above keyboard

@matt-bullock do you still see this issue?
If yes, could you also check and confirm if you see the same issue on uniswap when entering a value for swap amount.

@andrewdamelio yes still seeing the issue. No issues on uni but you'll notice they have their top bar above the keyboard so if you're forking something from uni then this might be why

@andrewdamelio what is status on this


chore: jx-railes-demo to 0.0.2

chore: Promote jx-railes-demo to version 0.0.2

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Allow markov bot to ingest multiple documents

The starter bot came from a conversational/chat project; it 'learns' by conversing. the loombreaker bot will 'learn' by ingesting documents from SOLR.
We need to update the bot to ingest whole documents, on demand.

This will have some overlap with @WildfireGaming 's work with Nutch & figuring out how to extract docs from SOLR


Unable to add Disqus

Hello folks. I'm trying to get Disqus on the blog following this: https://iveel.co/docs/alto-ghost-theme#section-disqus-comment
The file is not present, so I created one with the data required, but after restart Ghost, the comment box does not appear. I'm missing something?
Thank you
Ignacio

Hey @xe-nvdk,
Sorry, that documentation is outdated. To add Disqus, open /partials/comment.hbs and add the Disqus embed code between the <div>s. Also be sure to comment out the section by removing {{!-- and --}} 🙂


Safari: Browser prompt for form re-submit

Submit a non-remote form with a validation error. Rails renders "new" action again and we see the form with validation errors
Navigate to any other page via a link (turbolinks handles this – no reload)
Refresh the page via the browser's refresh button

Expected: page refreshes
Actual: I get a browser prompt asking me if I want to re-submit the form
This is happening in Safari, seems to work as expected in Chrome and FF.
Chrome and FF, however, don't allow me re-submit the form before I navigate away from the form page by clinking "refresh".
May be related to #60

Yes, the inverce problem occurs with chrome and FF.

Submit a non-remote form with a validation error. Rails renders "new" action again and we see the form with validation errors
Refresh the page via the browser's refresh button

Expected: Browser prompt asking me if I want to re-submit the form

Closing as duplicate of #60. I have added some more detail explaining the complexity in https://github.com/turbolinks/turbolinks/issues/60#issuecomment-423437233

This appears to be a browser bug with Chrome/Firefox when the history API is used. I have added some more detail in https://github.com/turbolinks/turbolinks/issues/60#issuecomment-441006244


Update README.md

add missing "/" when add disk configuration to filesystem.php

Thank you very much


VCM-7572: Add descriptive names to orders

We don't really have any sort of pipelines set up, so maybe this doesn't matter, but should we be making develop the target for merging these things in and then merging to main? Or do you think directly merging to main is fine?


How many face images per person is needed for retraining with own dataset ?

What's the minimum number of images？

look Wiki

find result in wiki


An error for install requirements.txt

I followed the tutorials to clone the repo, but I got an error when installing requirements.txt.
cd tinyBenchmarks/tutorials/ pip install -r requirements.txt ERROR: /home/skunk/tutorials/py-irt is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).

Hello,
Thank you for raising this issue. I have updated the requirements.txt. Please try it again and let me know!

It's fine! Thank you.


About free bayes info field

I have been working with somatic variant callers. I was using mutect2 but I stopped using it because of the false positives. I personally love Freebayes and thanks all the community.
The problem is I want to apply filters to my vcf file by a few values. Those values are QA, PQA, QR, PQR MQM, MQMR. When I observed the values I only saw some values such as 60 for all of them.
How can I fix this. Is it because I run freebayes with some filters that those values are not calculated ?

Thanks in advance

could you show the command and a vcf line?


Search input doesn't update state properly

Reproduce:

Go to https://explorer.testnet.near.org/
Type anything in the search bar
select all (with [cmd] + [a])
delete the text

-> results to the url in the navbar being updated (deleted) but the input stays the same (doesn't get deleted)

Thanks for the report, will be fixed soon!


CFY-4381 and CFY-4382 (master)

(direct copy of #174)

CFY-4381 Certificates support in install_new_agents
CFY-4382 Sanity checks for agents

@dankilman Ready to merge.


Fixes after merge

@pitchmuc couple of issues I found after upgrading to the latest merged version. Nothing big, probably I missed something or it was introduced during the merge.
An extra change from the 707057d commit: a dedicated __version__.py file which is used in the setup.py. Such a file is required in order not to import any dependencies while building the library in the cloud through setup.py script.
The version change is inspired by https://packaging.python.org/guides/single-sourcing-package-version/.

I didn't know that.
Thanks, that will help your use-case.


Create github project page

To have a better overview on the projects progress, a project page will be drafted to keep track of the repositories issues and their status, shown in context with their milestones, parent issue, sub-issues and whether an issue is currently deferred to the backlog, or will soon be taken up. The page is to give an idea of the intended long-term goals of the project.

The sub-issues are an opt-in feature from github beta. The opt-in has been requested, so the views might be reorganised in the future depending on how swift or late access to the advanced issue features is granted.

As a follow-up on the project page, two more automations remain to be added:

Upon closing, detect which type of closing happens on an issue and set the status of the issue to either complete or abandoned in the appropriate fashion. Putting the sprint field to Finished should be done manually. (Disable the automatic status update from project workflows and add a github actions automation).
Create a mask for the status field which bundles the statusses based on assigned colour. The mask should contain the statusses of 'todo', 'in-progress' (includes 'paused'), 'done' and 'completed'. Changing the mask should update the status field to the same value as the mask, while updating the status field should update the mask to the value corresponding to the colour assigned to the field. (Github actions are required to implement this feature).


[Experiment] Convert builderState namespace into a module

We don't have a perf suite for incremental/project references :(
@typescript-bot perf test this


Transpile the code to ES2015 for React

Transpile the code to ES2015 for React

@bogas04 Would you like to work on this? Good opportunity to learn IIFEs. 😉

Fixed in 9f57754cab3aa663d47fe7109c0750c0fed6d685


Provide a way to get commitmentATX for post via api call / cmd

For proper usage of postcli we would need to have a way to get commitmentATX that can be used for post, otherwise users of postcli are forced to start using smapp to get commitmentATX or use goldenATX always.

According to https://discord.com/channels/623195163510046732/820605182970036245/1125251881615228990 it is already possible with go-spacemesh with start smeshing arg, which generates postdata_metadata.json which has nodeid and atxid needed, all from cli.

grpcurl -plaintext <IP_ADDRESS>:9092 spacemesh.v1.ActivationService.Highest | jq -r '.atx.id.id' | base64 -d | xxd -p -c 64


Fix: Send dapps current network chainId through walletlink on wallet_watchAsset event

For this first version of watchAsset feature, we're assuming that once users authorize wallet_watchAsset request, the token should be added in the current network. That said, we've decided to follow the approach of sending its current network chainId on the event params (cc @brendanww).
It may be used by both extension and mobile apps to add token in the correct network

Review Error for erin-at-work @ 2022-03-08 13:52:01 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help


Do not use #pragma region if not supported by the compiler

Thanks for the PR! Just to clarify, which compilers don't support that pragma?

Yep, it is, but I believe there is a cleaner way to avoid this warning. You can set a push-options pragma on top of the file, and a pragma-pop, asking to ignore "unknown pragmas". That may be a less repetitive solution, assuming that region annotation is also used in SimSIMD and StringZilla 🤷♂

It's supported on GCC 13 and newer, so I'll patch the condition and merge 🤗
There are only 4 regions in the usearch/index.hpp, but if we include the submodules the number multiplies to 66. Any chance there is a cleaner way to define this pragma and backport it to older GCC versions, @mbautin?

I've tried using the _Pragma variant, but I believe that overcomplicates things.
// The `#pragma region` and `#pragma endregion` are not supported by GCC 12 and older.
// But they are supported by GCC 13, all recent Clang versions, and MSVC.
#if defined(__GNUC__) && ((__GNUC__ > 12) || (__GNUC__ == 12 && __GNUC_MINOR__ >= 0))
#define USE_PRAGMA_REGION
#elif defined(__clang__) || defined(_MSC_VER)
#define USE_PRAGMA_REGION
#endif
#ifdef USE_PRAGMA_REGION
#define PRAGMA_REGION(name) _Pragma(#name)
#define PRAGMA_ENDREGION(name) _Pragma(#name)
#else
#define PRAGMA_REGION(name)
#define PRAGMA_ENDREGION(name)
#endif

Will revert to your variant, @mbautin 🤗