Xcode 8.2.1 can't be Signed!

Description
Xcode 8.2.1 can't be Signed!
show
➜  ~ sudo codesign -f -s XcodeSigner /Applications/Xcode.app
/Applications/Xcode.app: replacing existing signature
[1]    2833 segmentation fault  sudo codesign -f -s XcodeSigner /Applications/Xcode.app

Operation
Xcode update 8.2.1 from  8.2
Expected behaviour
[Write here]
Environments

Xcode Version [  8.2.1  ]

@tanpengsccd
I had same problem but resolved.
follows:

remove XCodeSigner code sign from Keychain
recreate XCodeSigner code sign
run sudo codesign -f -s XcodeSigner /Applications/Xcode.app

@jazzsasori  YES , it worked another Mac! thanks!


items collapse upon themselves in timeline

I am dynamically adding data to the timeline component using a multi-select picker and api call. When I add new data to the timeline component, it causes the old data on the timeline to collapse upon itself. Any idea what is happening?

Hi, any chance you're mutating the data? When adding a new item, you should pass in a completely new array and not add the new item to the end of an existing array.
I added a comment about this here: https://github.com/namespace-ee/react-calendar-timeline#api

fixed...this was a data mutation issue. Thanks!


Wrong output returned by /api/v1/transaction-info when IDsOnly set to true

My node is running of current stable version (as of ~2 hours ago) of docker images.
When called with IDsOnly: false - output is correct (that is TransactionIDBase58Check are what they should be).
When called with IDsOnly: true - TransactionIDBase58Check field contains wrong data, looks more like a hash hex.
Example input, and beginning of output below.
{
"TransactionIDBase58Check":"",
"PublicKeyBase58Check":"BC1YLgYmxwTbjUhiqQk1ad4brLyYP4FgnNT8Yf2naYTL8Ty3XeMqQq7",
"IDsOnly":true
}
{
"Error": "",
"Transactions":    [
{"TransactionIDBase58Check": "a5b69c72999fc8b7f2befd0e8742c920776d7a1b2ec361fed54fa2c878ee2821"},
{"TransactionIDBase58Check": "4e1c53163b2289fc87bc409057cd700cf7c94248c4be4b4e56438dd480811253"},

Thanks for the report!

Thanks for fixing!


Run container with CUDA support?

In the readme there is instructions for how to let your applications do rendering using the nvidia GPU: https://github.com/dfki-ric/docker_image_development/blob/master/doc/010_Setup_Docker.md#nvidia-docker-2
Right now I stumbled accross the problem that one of the things running inside the container require CUDA support from my GPU (e.g., tensorflow), which apparantly doesn't work yet, or at least requires extra steps. (Tensorflow complains about libcudart.so and lubcuda.so missing. My simulation appears in the nvidia-smi process list, but the Tensorflow processes just use the CPU instead.)
Do you have any experience with setting that up?
I found this documentation, is this how it works?
Do I need to integrate some special docker image into my image? Or build my own base image based on a nvidia/cuda image instead (normally this is used)?
Or do I need to install it inside the container as described here?

Hi,
This could be related to the base image used to create the images.
Currently we use https://hub.docker.com/r/nvidia/opengl base images. F
For CUDA, I guess you need to use images from https://hub.docker.com/r/nvidia/cudagl
To test, you can change it e.g. here: https://github.com/dfki-ric/docker_image_development/blob/master/image_setup/01_base_images/build_plain_20.04.bash#L9
And use the script to build a base image for CUDA, in case it works also with x11 (and acceleration) in development we could switch completely to use the cuda images.

Maybe nvidia runtime wasn't installed or --gpus all wasn't passed for some reason. Anyways, this is obsolete to me now and therefore I'm closing this.


Added ternary quantization option

Added ternary quantization option based off the code used for weight quantization in bitlinear1.58
Example Weight:

Example Activation:

Looks good, one more thing, would you be able to create a README.md in the quantization folder and add an example for how to use the ternary for weights but 8 bits for activations?


Add workflow for pull requests

When a contributor makes a pull request, we want to be able to test the code in the PR while also avoiding running the integration tests for pull requests to reduce attack surface for bad actors.

After reading this I'm thinking we should take a look at pull requests before running any workflows on them.


Move max distance to the joint rule components

Rational is that e.g. L topology shouldn't allow centerlines which don't meet to be considered an L

Been playing with this a little. I think we should have some kind (ideally quite small) of a global limit on how high this, maybe something that's proportional to the average beam dims or maybe to the unit used. Once this gets big enough funky things start happening and then the joint themselves have to deal with some really sick cases, potentially making the code less readable.
@obucklin @jonashaldemann @funkchaser what do you think?

rule component max distance overrides the one of the assembly component's for that specific rule.
assembly max distance gets some default when nothing specified

cap max_distance to something proportional to the unit used
https://github.com/orgs/gramaziokohler/projects/5/views/1?pane=issue&itemId=51489076

Maybe it could be the largest width or height of all beams in the Assembly. You never want it any bigger than that.

IDEA:

max_distance is set globally in the Assembly component and is used to find potential pairs
each Joint also has a max_distance setting which may be lower, this allows the joint itself to check again and potentially reject this pair

yes, I think that could help to customize and solve some joints.


option

Current coverage is 20.68% (diff: 25.00%)

Merging #15 into master will decrease coverage by 1.72%

@@             master        #15   diff @@
==========================================
  Files             1          1
  Lines            58         58
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits             13         12     -1
- Misses           45         46     +1
  Partials          0          0

Powered by Codecov. Last update bf58f70...1056574


Allow common dataflow options to be specified via a config file

Would be nice if common, rarely-changing dataflow options like the project and client secret could be specified in a config file rather than as part of every hellbender command.

You can kind of do this right now by specifying --arguments_file and pointing to a file with those arguments.

Good to know -- forgot that we had --arguments_file.
The advantage of the config file approach would be that you wouldn't have to specify any extra args -- it would just look in the current directory or a known location for a file with your dataflow settings. Things like the pipeline runner would probably still be manually specified, though (perhaps with nice aliases like --cloud and --local)

config file is good for convenience, but I find that they cause lots of confusion and errors because people forget their existence

This issue was moved to broadinstitute/hellbender-dataflow#13


Support Web Worker files (eg. autocomplete.worker.js?worker syntax)

It looks like web worker js files with the ?worker suffix are ignored by this plugin.
My app uses an import such as:

import AutocompleteWorker from "@/autocomplete.worker.js?worker";

My output produces:

npm run build

build
vite build

vite v5.3.3 building for production...
✓ 293 modules transformed.
rendering chunks (1)...
Inlining: index-CIvNPwLS.js
Inlining: style-BvRGwxcl.css
dist/autocomplete.worker-CFomeDza.js     90.96 kB
dist/index.html                       1,964.05 kB

I think it's just a matter of updating the isJsFile regex at https://github.com/richardtallent/vite-plugin-singlefile/blob/main/src/index.ts#L42 ?

Same issues with Service Worker...

using let worker_import = await import("@x.worker.js?worker&inline"); worked for me

@nikoPLP yes, but that's making a packaging decision at all the call sites for web/service workers.
Ideally the application code stays agnostic to how the final scripts are bundled up, and it's just the configuration of this singlefile plugin that controls inlining vs normal vite packaging.


[SPARK-21788][SS]Handle more exceptions when stopping a streaming query

What changes were proposed in this pull request?
Add more cases we should view as a normal query stop rather than a failure.
How was this patch tested?
The new unit tests.

Test build #80859 has started for PR 18997 at commit 8aa3a29.

Test build #80859 has finished for PR 18997 at commit 8aa3a29.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80859/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #80901 has started for PR 18997 at commit 8aa3a29.

Test build #80901 has finished for PR 18997 at commit 8aa3a29.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80901/
Test PASSed.

Test build #81058 has started for PR 18997 at commit bbb0b0e.

Test build #81058 has finished for PR 18997 at commit bbb0b0e.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81058/
Test PASSed.

LGTM. Merging to master.


no validation for incorrect model names

edit: on v6.1.2
e.g. a typo of --model sd-2.0 (instead of SD-2.0)creates a python failure rather than just saying 'unknown model' or some such..
e.g. output is:
  File "/Users/shaun/dev/py-venv3/lib/python3.10/site-packages/torch/serialization.py", line 771, in load
    with _open_file_like(f, 'rb') as opened_file:
  File "/Users/shaun/dev/py-venv3/lib/python3.10/site-packages/torch/serialization.py", line 270, in _open_file_like
    return _open_file(name_or_buffer, mode)
  File "/Users/shaun/dev/py-venv3/lib/python3.10/site-packages/torch/serialization.py", line 251, in __init__
    super(_open_file, self).__init__(open(name, mode))
FileNotFoundError: [Errno 2] No such file or directory: 'sd-2.0'

Thanks @PaulMest for taking care of this!


Fix output on login breaking K8s authentication

monoctl outputs non json logs during the authentication flow which breaks the parsing of kubectl.
+-----------------------------------------------------------+
|monoctl has opened the browser for you to authenticate.    |
|It should show the log in screen of your identity provider |
|or the consent window if you are already logged in with it.|
+-----------------------------------------------------------+
Waiting for you to log in and give consent for OIDC flow...
You're successfully authenticated as '<OMITTED>.
---
{"kind":"ExecCredential","apiVersion":"client.authentication.k8s.io/v1beta1","spec":{},"status":{"expirationTimestamp":"2022-03-21T12:09:18Z","token":"<OMITTED>"}}

Coverage decreased (-0.04%) to 35.619% when pulling 3bba69a192a79d99d108f041979462b5df7d3494 on fix/get-cluster-credentials-output into e868e440951082565aaa4c8003fd6a897cf0c131 on main.


sokol_app.h: fix macos with glcore33 to update dimensions / dpi on startup

macOS with GLCORE33 doesn't call _sapp_macos_update_dimensions on startup like with METAL does, which keeps DPI at default value until a resize event comes in.
Not sure if it's the best place to put this function tho I'm not familiar with sokol_app.h codebase

oh I'm sorry didn't see this is already fixed in the master branch, nvm

Hi, yes sorry, this change slipped in as part of the big code cleanup merge I did yesterday. Also, I haven't looked at your other PRs yet, but I'll try to work through them in the next few days.
Cheers!

Thanks for the reply! Love the new updates and fixes! It also fixes metal not being able to startup on my macOS device.

It also fixes metal not being able to startup on my macOS device.

Oh... interesting. Do you know what sort of error you got before?

@floooh Sorry I failed to reproduce, there might be a problem with my setup the time I tried.


fix redirect link over the website

Purpose
fix the outdated redirect link in website. solves https://github.com/CenterForOpenScience/osf.io/issues/2467.
Changs
Sign up bottom on the main page now redirect you to the correct signup form

the bottom on the slide in footer should all work and redirect you to the right place

The back to osf link on two factor page and forget password page now redirect you to main page instead of log in page.

@sloria rdy for review

Pass finished. :poodle:

@sloria rdy for another pass

@sloria rdy for review and merge


Ragnarok Odyssey ACE [PCSE00300]

App summary

App name: Ragnarok Odyssey ACE
App serial: PCSE00300
App version: 1.00

Vita3K summary

Version: v0.1.5
Build number: 2726
Commit hash: https://github.com/vita3k/vita3k/commit/c2044c3c
CPU backend: Dynarmic

Test environment summary

Tested by: gymzatan
OS: Windows 11
CPU: AMD Ryzen 7 5800H
GPU: AMD Radeon(TM) Graphics
RAM: 16 GB

Issues
Game softlocks during opening movie.
Screenshots

Log
vita3k.log
Recommended labels

Intro
softlock bug

as of https://github.com/Vita3K/Vita3K/commit/f36797d8f04cdf9ae9c7646c8361dd4eb34b6492, the game no longer softlocked.
Screenshots

Log
vita3k.log
Recommneded Labels

Ingame +
graphics bug


merge from template-sync/template-arlac77-github

package.json

chore(deps): add ^3.79.0 remove ^3.78.12 (devDependencies.wrangler)

.github/workflows/update_package_lock.yml

chore: add<EMAIL_ADDRESS>(jobs.update_package_lock.steps.uses)

.github/workflows/update_readme_api.yml

chore: add<EMAIL_ADDRESS>(jobs.update_readme_api.steps.uses)

.github/workflows/deploy.yml

chore: add<EMAIL_ADDRESS>(jobs.deploy.steps.uses)

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

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

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
62

Relevant Lines:
71

💛  - Coveralls


How to create support for other devices

Sorry if i'm posting in the wrong place, but I have this device in my home:
https://www.basementwatchdog.com/basement-watchdog-wifi-module/
It provides notifications to my phone. How would I go about building a homebridge app for this, or even simple: how do I find out if this MIGHT be homebridge compatible.

If it communicates over wifi then it's compatible with homebridge. You just need an API to send commands or enpoints to listen to alerts. If it has any local page you use to manage it, start there. Otherwise find its IP on your network and try looking at the traffic using wireshark to see what it does. Preferably, you would contact the manufacturer for some documentation.


Error transferring container data: exit status 10

Hi.
I have very strange issue on copying one of containers between two servers. Both of servers are under Ubuntu 14.04.x with 4.4.0-X-generic kernel and "fresh" lxd 2.7 from PPA. I tried to dig in, but after enabling debug for lxd on receiver i stuck with this:
INFO[01-15|23:09:43] Creating container                       ephemeral=false name=tst
INFO[01-15|23:09:44] Created container                        ephemeral=false name=tst
DBUG[01-15|23:09:44] ContainerCreateFromImage                 driver=storage/dir imageFingerprint=5f19596a09c19d4beed653de08ea438c32e2fee35a10c6963a8285cae95c0a43 isPrivileged=false name=tst
DBUG[01-15|23:10:04] Shifting root filesystem                 container=tst rootfs=/var/lib/lxd/containers/tst/rootfs
DBUG[01-15|23:10:14] New task operation: 09c3f83d-cfb0-4174-92e5-390c8605050c
DBUG[01-15|23:10:14] Started task operation: 09c3f83d-cfb0-4174-92e5-390c8605050c
DBUG[01-15|23:10:14]
        {
                "type": "async",
                "status": "Operation created",
                "status_code": 100,
                "metadata": {
                        "id": "09c3f83d-cfb0-4174-92e5-390c8605050c",
                        "class": "task",
                        "created_at": "2017-01-15T23:10:14.296728898+03:00",
                        "updated_at": "2017-01-15T23:10:14.296728898+03:00",
                        "status": "Running",
                        "status_code": 103,
                        "resources": {
                                "containers": [
                                        "/1.0/containers/tst"
                                ]
                        },
                        "metadata": null,
                        "may_cancel": false,
                        "err": ""
                },
                "operation": "/1.0/operations/09c3f83d-cfb0-4174-92e5-390c8605050c"
        }
DBUG[01-15|23:10:21] Found cert                               k=1
DBUG[01-15|23:10:21] handling                                 ip=<IP_ADDRESS>:62608 method=GET url=/1.0/operations/09c3f83d-cfb0-4174-92e5-390c8605050c/wait
DBUG[01-15|23:10:28] MigrationSink                            container=tst driver=storage/dir live=false objects=[] op="&{id:09c3f83d-cfb0-4174-92e5-390c8605050c class:1 createdAt:{sec:63620107814 nsec:296728898 loc:0x11c4580} updatedAt:{sec:63620107814 nsec:296728898 loc:0x11c4580} status:103 url:/1.0/operations/09c3f83d-cfb0-4174-92e5-390c8605050c resources:map[containers:[tst]] metadata:map[] err: readonly:false onRun:0x56ba10 onCancel:<nil> onConnect:<nil> chanDone:0xc820d1a900 lock:{state:0 sema:0}}" srcIdmap="{Idmap:[{Isuid:true Isgid:false Hostid:231072 Nsid:0 Maprange:65536} {Isuid:false Isgid:true Hostid:231072 Nsid:0 Maprange:65536}]}"
DBUG[01-15|23:10:29] Updated metadata for task operation: 09c3f83d-cfb0-4174-92e5-390c8605050c
EROR[01-15|23:10:30] Error during migration sink              err="exit status 10"
INFO[01-15|23:10:30] Deleting container                       created=2017-01-15T20:09:43+0000 ephemeral=false name=tst used=1970-01-01T00:00:00+0000
DBUG[01-15|23:10:30] containerDeleteSnapshots                 container=tst
DBUG[01-15|23:10:30] Got error writing to writer read tcp xx.yy.143.58:14996->xx.yy.20.155:8443: use of closed network connection
DBUG[01-15|23:10:30] sending write barrier
DBUG[01-15|23:10:30] rsync recv error for path /var/lib/lxd/containers/tst/: exit status 12:
DBUG[01-15|23:10:30] ContainerDelete                          container=tst driver=storage/dir
INFO[01-15|23:10:32] Deleted container                        created=2017-01-15T20:09:43+0000 ephemeral=false name=tst used=1970-01-01T00:00:00+0000
DBUG[01-15|23:10:32] Failure for task operation: 09c3f83d-cfb0-4174-92e5-390c8605050c: Error transferring container data: exit status 10
DBUG[01-15|23:10:32]
        {
                "type": "sync",
                "status": "Success",
                "status_code": 200,
                "metadata": {
                        "id": "09c3f83d-cfb0-4174-92e5-390c8605050c",
                        "class": "task",
                        "created_at": "2017-01-15T23:10:14.296728898+03:00",
                        "updated_at": "2017-01-15T23:10:29.532761263+03:00",
                        "status": "Failure",
                        "status_code": 400,
                        "resources": {
                                "containers": [
                                        "/1.0/containers/tst"
                                ]
                        },
                        "metadata": {
                                "fs_progress": "tst: 1016.96kB (961.41kB/s)"
                        },
                        "may_cancel": false,
                        "err": "Error transferring container data: exit status 10"
                }
        }

And even more strange symptom - any other containers existing or created from "public" ubuntu images aren't affected by this issue. Based on "rsync recv errror", i assumed, that problem somehow related to copying container via rsync. In sources of storage.go around line 76, i found, that rsync is launched with those params:
rsync -a -HAX --devices --checksum --numeric-ids /var/lib/lxd/containers/tst/ remote.server.tld:/var/lib/lxd/containers/tst/

And i successfully synced directory /var/lib/lxd/containers/tst/ to the same remote server on which i tried to copy container via lxc copy command.
Any ideas how to debug this further?

I suspect this is #2494. Can you build a LXD with the top patch on https://github.com/tych0/lxd/tree/print-rsync-error and see what shows up in /tmp/lxd_netcat_*? Let me know if you don't have a way to build LXD, and I can upload a test build.


?raw skips svg optimization

First of all, thank you for creating this! <3
Second: I'm unsure if this is an issue or more of a feature request. According to the readme 'SVGs can be imported as strings using the ?raw suffix'
As I wasn't using the ?skipsvgo suffix and svg optimization is enabled in the config, I initially assumed this would still include svg optimization. And therefore I thought it would output the results of the optimization as a string, but that's not the case. The string is the content of the original file, unoptimized despite svg optimization settings.

I used an SVG with original file size of 500kb
With ?raw it remains 500kb
Without it, as a component, it's 312kb
I ran svgo on top of the string after loading it with the ?raw suffix and then it will become 312kb. Therefore my conclusion svg optimization isn't done while using ?raw suffix.

Would love this as a feature: to be able to import an optimized svg as a string. Maybe changing the behavior of ?raw is too confusing and should remain as it is, and this should be more like ?string with a note in the docs that this is as a string, but optimized?

Yes, that's not an issue. : https://github.com/jpkleemans/vite-svg-loader/blob/main/index.js#L36-L38
raw skips optimization. changing the raw behavior would break backwards compatibility, as raw means raw and not optimized :-)
Not sure if we have capacity to add this as a feature, but feel free to open up a PR! I'm helping the core maintainer and I'll happily review your PR.


Updating recommended list

Update the recommended list.

Set ubuntu as recommended
Set fedora as recommended
Remove mageia from recommended (It is rarely used and pointless to be around here, nobody actually use it)

Sorry, but Fedora is not going to be a distro we recommend as long as they continue to have a terrible release cycle.


Issue 21: Use source downloadable data rather than API

closes #21

Not focusing on gnomAD because of this comment: https://github.com/cancervariants/evidence-normalization/issues/21#issuecomment-1081962242


fix: cli build-docs / use stdout instead of stderr for simple logs

Hey there,
Using CLI redocly build-docs
This always prints the following into stderr.
Found /Users/(...)/redocly.yaml and using theme.openapi options
Prerendering docs

I have many other stuff happening in my project, and generating multiple docs, so this just adds noise & annoyance, whereas it's just (verbose) logs and not errors anyway.

Seems like a good idea 🧠 ! Thanks @pv-g

Could you update the failing snapshots? (npm run e2e -- -u)

Sure @tatomyr. Just did it.


Failed to install

I got this error message when trying to install the plugin:
G:\Users\myser\work\app>cordova plugin add https://github.com/lucasdupin/cordova-bring-to-front.git
Failed to fetch plugin https://github.com/lucasdupin/cordova-bring-to-front.git via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Error: npm: Command failed with exit code 1 Error output:
npm ERR! premature close

The debug log:
7 silly fetchPackageMetaData error for git+https://github.com/lucasdupin/cordova-bring-to-front.git premature close
8 timing stage:rollbackFailedOptional Completed in 0ms
9 timing stage:runTopLevelLifecycles Completed in 3818ms
10 verbose stack Error: premature close
10 verbose stack     at PassThrough.onclose (C:\Program Files\nodejs\node_modules\npm\node_modules\end-of-stream\index.js:47:67)
10 verbose stack     at PassThrough.emit (events.js:203:15)
10 verbose stack     at emitCloseNT (internal/streams/destroy.js:68:8)
10 verbose stack     at process._tickCallback (internal/process/next_tick.js:63:19)

Same problem.


Clicking multiple pages in one tick turns all pages yellow

Normal view:

After double-clicking any page (or multiple pages) in one tick besides the currently visible page:

It doesn't happen when the plugin is disabled. Using version 3.1.3 of the plugin.

Also it seems this doesn't happen on the Clues or Minigames tabs, only Bosses and Misc. I'm unsure if it happens with Raids as I don't have any greenlogged.


unknown directive proxy_connect_data_timeout

zty-jcjg-nginx-proxy-prod:/opt/nginx1.24.0>sudo ./sbin/nginx -s reload
nginx: [emerg] unknown directive "proxy_connect_data_timeout" in /opt/nginx1.24.0/conf/vhost/conf/proxy.conf:32

It means this module is not built into your nginx binary, you need patch nginx source and build it with this module, see here: https://github.com/chobits/ngx_http_proxy_connect_module#install


Prints validation metric. Closes issue #56.

This PR adds the print_metric_score function to the MLP model, and calls it in the fit method on the validation set, if the validation_metric parameter is not None. Any dataset, set, and metric can be used with this method.
While implementing, I was wondering if I should use set_train_mode(False), but as it wasn't used in the FitPredictError experiment I didn't.
Also, as I am not comfortable enough with some of the other models (DBNs, Balances, and RBMs) I did not try to add it there. The autoencoder example (which doesn't use the autoencoder class by the way) seemed to work fine. And as I haven't looked carefully at the RNN code yet, I did not try to modify it.
Thanks for your comments and have a nice day,
Séb

HI Séb,
there are two things we do going from training to prediction mode: In predict_generator, there is the self.data_layer.use_set(setname, predict=True), which tells the dataset provider to take batches from the test set. Then in fit_predict_err we have  self.model.set_train_mode(False) which switches the drop-out layers, switching them to deterministic mode, and switching batch normalization to inference mode. All of these need to be undone if you want to continue training after running inference. It should be relatively easy to check if you still get the same final error if you have the callback in place, than without it. Also make sure the validation misclass percentage is the same as what you get from the final metrics call, to verify that the dropout layers and batch norm layers switch mode correctly.

Hello,
Thanks for the comments, I completely forgot to revert back to the train set. I just tested it with mnist small, and with the same random seed I get the same results when both printing and not printing the validation metrics, which should be news.
One thing I believe could still be improved is that after printing the metrics, I revert to the train set. But maybe the user used another set before printing the metric score. From looking at the DataLayer class, I can find a good way to get which set was being used before printing the metric score. Any idea ?
Have a nice day,
Séb

Hi Séb,
It great that the feature works with the MNIST-small model; see above though for difficulties I expect with dropout and batch normalization because they rely on self.model.set_train_mode. In this case, your feature would lead to unexpected behavior, i.e. you would get wrong metrics reported. Note the MNIST example does not use those layer types.
All dataset have, or should have, a training set, so generally I think it's safe to attempt to revert to that for continued training.

Alright, for some reason I thought that set_train_mode(False) was already in predict_generator and removed it in commit 2a6ddd1. I just re-added the line back, and testing with batch norm and dropout gives both times the same results, whether the validation metric is printed or not.

I've taken a look through this change and think the following updates are in order:

Revert the changes to mnist-small.yaml example.  Probably better to make a new mnist-epoch_val_print-small.yaml or something like that.
The current validation_metric name is misleading and should be changed.  We already have a metrics parameter for things to compute after training, maybe this parameter should instead be called per_epoch_metrics and have a similar format to metrics.
From the above we shouldn't be restricted to just specifying a single metric, and only be allowed to compute them on a validation set.  We should support per epoch computation of potentially multiple metrics on each of the train, test, and validation sets.  If this variable is not specified we default to our current training error reporting.
We should add this functionality to RNN's since doing so should be straightforward.

Good afternoon,
Didn't have much time to work on this. I included the suggested modifications 1, 2, 3 and printing metrics for RNNs is coming soon. (the name of the parameter is now epoch_metrics)
As there might be a list of such metrics for each epoch (eg, in mnist-epoch_metrics-small.yaml), I added a "header" stating the epoch for which the metrics were printed.

Alright, I believe it is also working for RNNs. In addition I modified print_metric_score so that it takes a list of metrics for one set to avoid recomputing the predictions. One thing that could be nifty enhancement would be to print the metrics in a table so that it is easier to see their evolution. I am trying to see if there is a way to do it through python's logging.

HI Séb,
I've had a look through the updates and they look good from my perspective. :+1:
As for table based printing, I think the best way to go may be to support dumping these metrics to a user specified flat text file (1 column per metric, one row per epoch).  We have this ability for regular, end of model training metrics via the -o parameter and the dump_metrics() function.  This computes other info so probably not what we want to use in this case, but may give you a couple of ideas to get started.
Only other suggestion would be to flatten all of your commits down to a single one with relevant description to keep the changelog clean, but I can do that on my side when I merge it in.  Let me know if I should go ahead and merge now, or wait for some table file dumping changes (maybe making these a separate pull request would be better anyway).
Thanks for the contribution!

Hello,
I did not know about -o, that can be useful. If I do the table printout, it will be quite further in the future and so I believe it can wait for its own pull request.
Thank you for the comments and your help,
Séb


AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

I got this when performing build command 'gulp':
[22:35:19] Starting 'build'...
Traceback (most recent call last):
File "/Volumes/Private_dev_own/lnpp/app/manage.py", line 18, in
execute_from_command_line(sys.argv)
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/core/management/init.py", line 385, in execute_from_command_line
utility.execute()
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/core/management/init.py", line 354, in execute
django.setup()
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/init.py", line 18, in setup
from django.utils.log import configure_logging
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/utils/log.py", line 10, in
from django.views.debug import ExceptionReporter, get_exception_reporter_filter
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/views/debug.py", line 10, in
from django.http import (HttpResponse, HttpResponseServerError,
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/http/init.py", line 4, in
from django.http.response import (HttpResponse, StreamingHttpResponse,
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/http/response.py", line 13, in
from django.core.serializers.json import DjangoJSONEncoder
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/core/serializers/init.py", line 23, in
from django.core.serializers.base import SerializerDoesNotExist
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/core/serializers/base.py", line 6, in
from django.db import models
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/db/models/init.py", line 6, in
from django.db.models.query import Q, QuerySet, Prefetch  # NOQA
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/db/models/query.py", line 13, in
from django.db.models.fields import AutoField, Empty
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/db/models/fields/init.py", line 18, in
from django import forms
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/forms/init.py", line 6, in
from django.forms.fields import *  # NOQA
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/forms/fields.py", line 18, in
from django.forms.utils import from_current_timezone, to_current_timezone
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/forms/utils.py", line 15, in
from django.utils.html import format_html, format_html_join, escape
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/utils/html.py", line 16, in
from .html_parser import HTMLParser, HTMLParseError
File "/Users/devil/.virtualenvs/lnpp/lib/python3.5/site-packages/django/utils/html_parser.py", line 12, in
HTMLParseError = _html_parser.HTMLParseError
AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

Hey Adam, thanks for the report. It appears that you are using Python 3.5, which I believe there was a known issue using Django 1.7 with your version of Python (see this report for details). Either upgrading Django to a later version or downgrading Python should fix your issue.

Hi Andrew,
thanks for fast answer. I switched to Django 1.9 and it works. I found one more issue, on 'gulp serve' server starts at port 3000 but browser opens page at 9000.

Adam,
That is intended. What's happening is Django runs its server at port 3000 and BrowserSync runs as a proxy at 9000. You can view your app in either, but with BrowserSync running at port 9000 you get live reload features as you make changes. During development I recommend running gulp --d --w --s, which builds your project in debug, serves it and watches for ongoing file changes, all in one go. For more info on what the flags mean you can refer to gulpfile.js which should point you to .taskconfig. Please be warned that BrowserSync might get stuck on the first time around, so you might have to do a manual browser refresh (just this one time) :).

Hey,
Thank you for posting this issue, I had a similar challenge and update to Django version 2.1.2 and the matter got resolved.


Add fontFamily to Heading

While it's easy enough to extend Heading to change the font, I imagine there are enough projects out there with different heading/body fonts to warrant including fontFamily here for convenience.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #431   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          63     63
  Lines         228    228
=====================================
  Hits          228    228

Impacted Files
Coverage Δ

src/Heading.js
100% <ø> (ø)
:arrow_up:

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 afa5439...000f090. Read the comment docs.

Can do

Awesome thanks!


FAQ (mobile and desktop view), Circular page(Mobile and desktop view)

https://www.figma.com/file/dOQv8d0yWU9BU7Adea2LIU


ADULT MENTAL HEALTH CARE CLUSTER CODE (FINAL)

The Data Element ADULT MENTAL HEALTH CARE CLUSTER CODE (FINAL) was untired in the November 2024 release but it is not showing correctly
James will fix it for the November release and Together will be checked to ensure it works for the next release.

Looks OK on the new test publication


How to approach Laravel 5 pull request?

The Laravel Service Provider of this package does not work with Laravel 5. I could easily make a Pull Request to add support for Laravel 5.
Would you all prefer a new League\StatsD**\Laravel5**\Facade\StatsdFacade or just upgrade the current Laravel facade and break compatibility with Laravel 4?
I think a new Facade for Laravel5 would be nicer, to avoid breaking old installs.

I mean ServiceProvider... :)

Any progress on a L5 service provider?

Amy updates on this ? It's still not working on 5.1

Well, because I did not get a response, I just made my own Service provider in our app. This is the code:
<?php namespace App\Providers;

use Illuminate\Support\ServiceProvider;
use League\StatsD\Client as Statsd;

class StatsdServiceProvider extends ServiceProvider {
    public function boot()
    {
        //
    }

    public function register()
    {
        $this->registerStatsD();
    }

    protected function registerStatsD()
    {
        $this->app['statsd'] = $this->app->share(
            function ($app) {
                // Set Default host and port
                $options = array();
                if (isset($app['config']['statsd.host'])) {
                    $options['host'] = $app['config']['statsd.host'];
                }
                if (isset($app['config']['statsd.port'])) {
                    $options['port'] = $app['config']['statsd.port'];
                }
                if (isset($app['config']['statsd.namespace'])) {
                    $options['namespace'] = $app['config']['statsd.namespace'];
                }
                // Create
                $statsd = new Statsd();
                $statsd->configure($options);
                return $statsd;
            }
        );
    }
}

Apologies for the delay. I've never used Laravel before so I'm not in a position to review this. There is a pull request open (#21) so if someone wants to verify that it works and is a valid provider then I can merge that.

I've ended up implementing manually the changes in the pull request and it works just fine.
A couple of things need to be changer though:

In src/Laravel5/Provider/StatsdServiceProvider.php the current code in the pull request looks for '/config/config.php' it should look for '/config/statsd.php' instead


Bug - "wear torch" when already equipped in both hands

When you already have something equipped in both hands and try to "wear torch" the server crashes.
Fixed it by adding this to character.js Character.prototype.wearLight:
var slot = this.getEmptyWeaponSlot(target);

    if (!slot) {
        World.msgPlayer(target, {
            msg: 'You are already wielding something in both of your hands.'
        });
        return false;
    }

Same issue for wearShield and wearWeapon.


the info map is now being marshaled to json in its own sub node to av…

…oid overwriting the status

The issue discussing this PR can be found at https://github.com/dimiro1/health/issues/9

oh.. checks failed.. i will check the db and url tests.

Hey @bestform sorry about it, I was thinking about this problem and I decided to give priority to the status defined in the Health struct. If some check add a status key, it will not be rendered in the json. Take a look at the master branch.
https://github.com/dimiro1/health/commit/68671c53fef441bd953e542ca449df7863ed111d

ok. fair enough, that is what open source is all about :)

@bestform Thank you so much for giving so much attention to this project. Lets keep working.

no problem :) i love contributing to open source projects in my free time. making better software via open source is what i truly endorse. Keep up the good work :)


contact could be part of Core not just Test specific

Hi,
I've discovered as plans raised me warning about contact is not proper value inside plan, so that I've looked into doc:
https://tmt.readthedocs.io/en/stable/spec/tests.html#contact
and found that contact is part specification for tests, not allowed in plans.
My perspective is that it should be in Core specification and valid for everything.

Yes, currently property contact is defined in class Test.

https://github.com/teemtee/tmt/blob/main/tmt/base.py#L10321024	@dataclasses.dataclass(repr=False)
1025	class Test(
1026	        Core,
1027	        tmt.export.Exportable['Test'],
1028	        tmt.lint.Lintable['Test']):
1029	    """ Test object (L1 Metadata) """
1030
1031	    # Basic test information
1032	    contact: List[str] = field(
1033	        default_factory=list,
1034	        normalize=tmt.utils.normalize_string_list
1035	        )

And class Core doesn't have attribute contact. It seems simple to fix it, I'll file a PR soon.

Yes, currently property contact is defined in class Test.
* https://github.com/teemtee/tmt/blob/main/tmt/base.py#L1032
  ```python
  1024	@dataclasses.dataclass(repr=False)
  1025	class Test(
  1026	        Core,
  1027	        tmt.export.Exportable['Test'],
  1028	        tmt.lint.Lintable['Test']):
  1029	    """ Test object (L1 Metadata) """
  1030
  1031	    # Basic test information
  1032	    contact: List[str] = field(
  1033	        default_factory=list,
  1034	        normalize=tmt.utils.normalize_string_list
  1035	        )
  ```

And class Core doesn't have attribute contact. It seems simple to fix this issue, I'll file a PR soon.

Thank you very much.
Regards
Honza


ImportError: cannot import name wraps (Python 2.7.6)

when trying to do but this
from latex import build_pdf

I get an import error.
Traceback (most recent call last):
  File "test.py", line 1, in <module>
    from latex import build_pdf
  File "/usr/local/lib/python2.7/dist-packages/latex/__init__.py", line 4, in <module>
    from .build import build_pdf
  File "/usr/local/lib/python2.7/dist-packages/latex/build.py", line 6, in <module>
    from data import Data as I
  File "/usr/local/lib/python2.7/dist-packages/data/__init__.py", line 9, in <module>
    from six import text_type, PY2, reraise, StringIO, BytesIO, Iterator, wraps
ImportError: cannot import name wraps

(Python 2.7.6, Ubuntu)

apparently I had an old version of the sixt package
pip install six -U

fixxed it for me.


[feature] introduce subtests

Is your feature request related to a problem or a nice-to-have?? Please describe.
I often run into the decision between writing short tests with a lot of boilerplate and larger tests where its hard to describe which part specifically failed.
Consider the following scenario:
descibe('some tests', () => {
  it('test1', () => {
    const someObject1 = fromSomeCall()
    expect(someObject1).to.matchSnapshot()
  })
  it 'test2', () => {
    const someObject2 = fromSomeOtherCall()
    expect(someObject2).to.matchSnapshot()
  })
})

this is good because I can test these two calls individually, if one fails I know exactly what went wrong based on the test names. However, if I want to test that these two objects are in fact equal, then I can rewrite the test like so:
descibe('some tests', () => {
  it('test1', () => {
    const someObject1 = fromSomeCall()
    expect(someObject1).to.matchSnapshot()
    const someObject2 = fromSomeOtherCall()
    expect(someObject2).to.deep.equal(someObject1)
  })
})

however, now if this test fails it is harder to tell exactly what went wrong.
Describe the solution you'd like
I would like to see the idea of subtests in pytest or node-tap. In mocha, we like the idea of completely independent tests, this is great because we can run one test and iterate quickly. However, I still think there is value to be added in adding more metadata to individual tests. What I am proposing is creating sub sections in a test that cannot be ran separately, the whole test still needs to be ran, but now we have more information on where a test failed.
Here is the syntax I imagine:
descibe('some tests', () => {
  it('test1', () => {
    const someObject1 = subtest('test fromSomeCall result', () => {
      const someObject1 = fromSomeCall()
      expect(someObject1).to.matchSnapshot()
      return someObject1
    })
    subtest('test fromSomeOtherCall result matches fromSomeCall', () => {
      const someObject2 = fromSomeOtherCall()
      expect(someObject2).to.deep.equal(someObject1)
    })
  })
})

Describe alternatives you've considered
currently I just use plenty of comments in my tests, but that information isnt immediately useful when reading test failures on CI and doesnt necessarily section out tests well. The other other alternative I already described, which is simply breaking up tests further, but this means its harder to combine testing different but related pieces of code without writing more overlapping tests.

[edit] I have discovered the package https://www.npmjs.com/package/mocha-steps which accomplishes some of what I want, e.g. tests are coupled together. The piece it is missing though is a shared variable scope.

I personally would love this feature!... But per #5027 we're not trying to make any significant changes. Wontfixing.
If anybody feels strongly this should exist, do yell at me and we can take another look. Cheers!


Players dying in Warmup cant speak in the round

If someone dies before the round start, they will be muted and not be unmuted if the round beginns.
They will respawn after the warmup but are still muted because they died.

#9 hopefully this should fix this.

after looking in the garrys mod documentation I came up with the exact same solution.
I hope this event is triggered even at respawn by Items like secound chance

Thanks for fixing :)


Does this require a passwordless sudo user?

Nothing happens when I run cap staging monit:status.
I opened capistrano console (bundle exec cap staging console) and entered sudo monit status, it asked for a password.

@chibeepatag if your server asks for a password, then this won't work, unfortunately.
I didn't setup any mechanism to handle that. (when I created this for my own use, I had password-less access via my SSH key)


MQTT Failures in Integration Tests

Running the Sawtooth and Ethereum/Besu integration tests always fails since 0.3.0 complaining about mqtt failures.
Context
The integration tests fail to run because of reasons unrelated to the systems under test.
Expected Behavior
I expect the integration tests to execute sucessfuly, or fail for reasons specific to the system under test.
Actual Behavior
Caliper is unable to stand up the Systems under test because of MQTT messages relating to the "prepared" state
Steps to Reproduce

run the integration tests for Ethereum, Besu, or Sawtooth
Observe in the log messages such as

2020.03.19-10:02:18.088 -0600 debug [mqtt-worker-messenger] ethereum worker sent message: {"to":["orchestrator"],"from":"41953","timestamp":"2020-03-19T16:02:18.088Z","data":{"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}}
2020.03.19-10:02:18.089 -0600 debug [process-master-messenger] Processing worker message: {"to":["orchestrator"],"from":"41953","timestamp":"2020-03-19T16:02:18.088Z","data":{"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}}
2020.03.19-10:02:18.110 -0600 debug [worker-orchestrator] Dealing with prepared message {"to":["orchestrator"],"from":"41953","timestamp":"2020-03-19T16:02:18.088Z","data":{"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}}
2020.03.19-10:02:18.110 -0600 error [message-handler] Handled unsuccessful "prepare" message for worker 0 and test round 0 with error SyntaxError: Invalid or unexpected token
2020.03.19-10:02:18.110 -0600 debug [worker-orchestrator] Handling prepared message from 41953 with data {"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}

Context
I am unable to evolve the Ethereum adapter to fix other bugs (such as nonce management)
Your Environment

Version used: Caliper 0.3.0, bffcd484a42fb7571331dd57544e1a5539fbbb8f
Environment name and version (e.g. Chrome 39, node.js 5.4): Node v10.16.3
Operating System and version (desktop or mobile): Mac OSX 10.15.3
Link to your project:

@shemnon I think this was fixed by #782. Can you confirm it?

Yea,  besu works now.


commiting lab2 to ask for some feedback from partner

@ondreagray
Hey I only got part 1 done pretty formally, I ran out of time to get a really good start on the rest; Any feedback on part 1 would be much appreciated, we can talk more in person tomorrow!

Hey nice work so far! I think my overview comments are more on sentence style and structure. Overall, your explanations, code and diagrams are very well labeled and thorough. I think the main issues are that I sometimes get lost in your longer explanations and I'm not always sure what part of the lab I'm looking at. I think labeling each section by content is helpful, but it might be nice to just see "Problem 1", "Problem 3, Version 1" etc. That's also just a personal preference.
In the longer explanations, there are often sentences that have a lot of information packed in them. This makes it harder to glean the main point you want to share. Maybe try splitting it into two or more sentences. It's okay to state something then provide reasoning or context in the next sentence.
This is an example in section 1.1 : "This makes sense because as we gather data over more intervals, a constant average rate (which is required for a distribution to be poisson) implies that the most likely measurement in multiple days should be the most likely measurment in one day multiplied by the number of days over which we collect data."
It contains a lot of good explanation and information it's just harder for me to follow. Maybe instead:
"This result is reasonable because it's the most likely measurement (average) for one day multiplied by the number of days we collect data. This means the per day average for 4 days remains the same."
There's also a lot of repetition in phrasing. I think common phrases you repeat are "we shall", "this makes sense" and "that is". A lot of the time these are at the beginning of a sentence or paragraph. Maybe try mixing them up or eliminating them altogether if you don't need them, just to be more concise.
Then in Section 1.3 maybe specify what you're dividing by n. In this case it's the x-axis.
Those are most of my comments. Most of your sections look good. I didn't wnat to go into the ones you made comments about still working on so I think that's everything. Like I said, I only really noticed clarity issues rather than math problems so that's what my comments are all about.
Hope this helps!!


readme: add aidful-ollama-model-delete to community integration

A simple Python UI which allows to easily select and delete any number of models to free up disk space.

So cool that it is merged, feels good to be listed with my tiny tool on the official README of such an outstanding project. 🥰
Thanks, Jeffrey!


datahub metadata-ingestion support for preset

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Summary by CodeRabbit

New Features

Introduced support for the Preset.io data ingestion source, enhancing the system's ability to integrate with diverse data platforms.
Added structured representations for dashboard and chart metadata, improving the management and retrieval of data in the ingestion pipeline.

Bug Fixes

Implemented user authentication for the Superset API connection during initialization to ensure secure data access.

Tests

Added integration and unit tests to validate the functionality of the new Preset data ingestion source and its configurations.

@llance there's a few minor comments pending on this one, but it's a great contribution so would be good to get it in. Let me know if you have any questions or need some help

@llance there's still a few pending review comments and lint/test issues here
Let me know if you need help making sense of any of the comments

Hey @hsheth2,
I'm on the same team as Shuixi, we've built out the remaining ingestion pipeline for Preset (dataset sync, upstream/finegrained lineage)  but need this PR merged in first (before we submit our other contributions for review)
Looking to take this PR across the finish line, in addition to fixing lintting issue, is the expectation to address all of coderabbitai's comments as well?

Looks like there's still some lint/test failures

the self.login in the superset class will call login() from the preset method already - that's the behavior of method overrides with python
So I believe things should "just work" without the explicit calls

@hsheth2 You're right, great catch. I've made the changes and the ingestion works without issues. I've also updated the tests so they should pass now.


initial bootstrap script for incremental compiler support

Description
In order to support in browser hot reload/hot restart, we need to create a bootstrap script to invoke various dart sdk methods and attach functionality to the window. This is a first pass at what needs to be done to configure it correctly.

This isn't quite ready yet


Prototype for #10

@nopeslide
Prototype for #10, just some pseudocode to discuss about the implementation.

I think I got it.
you not worried about how to resolve dependencies,
but how to resolve the tensors, since they are named arbitrarily by the network and not by the operator using them?

@nopeslide Yes, exactly. AFAIK there are 3 types of input tensors in a node:

The initializer ones. Not a problem, they are part of the model and we can search them by their name.
The input ones. These are the input tensors to the model (i.e. in MNIST is only one and its the image). Also not a problem, we can search them by name.
And the inputs that are some other nodes output. So far we are not storing the name to pointer mapping. So for example if the output of an operator is O, we would have it stored in the context operator__onnx__xxx__output and we can of course access it ->O but some other node will need that output as input, but that node doesn't know about O. It only knows about a name i.e. Output_From_Add_Operator. So we need to think about storing this mapping somewhere.

So we need to think about storing this mapping somewhere.

Instead referencing the Onnx__TensorProto objects directly we could make them resolvable:
struct operator_tensor {
  char                    *name;   // name given by model
  struct operator_context *ctx;    // context the tensor originated from
  Onnx__TensorProto       *tensor; // resolved tensor
};

struct operator_context{
  struct operator_tensor   **input;
  size_t                     n_input;

  struct operator_tensor   **output;
  size_t                     n_output;

  struct operator_attribute *attr;
  size_t                     n_attr;

  onnx_operator run;
  int status; //error code
};

The list of input and output tensors can still be overlayed by the specific context of an operator and we can still replace unspecified tensors with a NULL pointer.
Additionally we now have knowledge about the dependencies of our current node and can use this to create a execution schedule.

Btw I played around with on-demand resolving of inputs and found the length specified (n_*) pretty handy. would prefer them now over NULL-termination

@nopeslide Is it possible to have the function pointer inside the operator_context and then the operator context as part of the function pointer? Isn't this some kind of circular dependancy. I can't get it to work.
struct operator_context{
  ...
  onnx_operator run;
 ...
};

typedef int (*onnx_operator)(
  operator__context *context
);

@nopeslide Is it possible to have the function pointer inside the operator_context and then the operator context as part of the function pointer? Isn't this some kind of circular dependancy. I can't get it to work.
struct operator_context{
  ...
  onnx_operator run;
 ...
};

typedef int (*onnx_operator)(
  operator__context *context
);

typedefs are definitions and not declarations. to solve such circular declarations you may need forward declarations, which typedefs can't provide:
struct A;
struct B;

typedef struct A {
  struct B *b;
} A;

typedef struct B {
  struct A *a;
} B;

you also can only use pointers on forward declarations (since the struct can't be filled)

@nopeslide Just uploaded a new patch with some more nasty code. Now I think we can play around with it and come up with a final design solution. Iterates all nodes and calls the previously resolver operator with the previously resolved context.
MNIST operator is working and now the inference function is just:
  for (int nodeIdx = 0; nodeIdx < n_nodes; nodeIdx++)
  {
    all_op_context[nodeIdx]->operator(all_op_context[nodeIdx]);
  }

The code that would be generated is under the function resolve_check_get_input_and_attr. It gets the model with its inputs, and returns an array of contexts, with the operator, i/o/attr resolved ready to be used to run inference.
The context for each operator looks like this:
struct operator__onnx__maxpool__context{
  struct operator__onnx__maxpool__input *in;
  struct operator__onnx__maxpool__output *out;
  struct operator__onnx__maxpool__attribute *attr;
  int (*operator)(struct operator__context*);
};

struct operator__onnx__maxpool__input{
  Onnx__TensorProto *X;
};

Just measured the times of the inference (excluding the resolving process ofc) for mnist and looks a bit higher. Don't know why, now that we have everything resolved and no time is wasted on searching I expected it to be quicker. The only difference in the operators is the cast:
struct operator__onnx__matmul__context *sc = (void *) context;

Will continue looking at it, but I think we need to start taking the decision on how the context is going to look like.

Instead referencing the Onnx__TensorProto objects directly we could make them resolvable:
struct operator_tensor {
  char                    *name;   // name given by model
  struct operator_context *ctx;    // context the tensor originated from
  Onnx__TensorProto       *tensor; // resolved tensor
};

struct operator_context{
  struct operator_tensor   **input;
  size_t                     n_input;

  struct operator_tensor   **output;
  size_t                     n_output;

  struct operator_attribute *attr;
  size_t                     n_attr;

  onnx_operator run;
  int status; //error code
};

Onnx__TensorProto*
resolve_tensor(operator_tensor *tensor) {
  if (!tensor->tensor) {
    tensor->tensor = findOutputTensorInContext(tensor->name, tensor->ctx);
  }
  return tensor->tensor;
}

The list of input and output tensors can still be overlayed by the specific context of an operator and we can still replace unspecified tensors with a NULL pointer.
Additionally we now have knowledge about the dependencies of our current node and can use this to create a execution schedule.

I like the simplicity of this solution, which is similar to what we already had on master. We would still need to search the tensor but only on operator level, among less entries. I have played a bit with our context specific idea, and being able to address the tensor like in->X is really convenient, but it adds some complexity on the Python side. Lots of structures, and quite a lot of autogenerated code for input/output/attributes resolving (which so far is the only drawback I have seen). Even though, I like this solution and I would move forward with this. The Python autogenerated code was thought to eliminate boiler plate code, and with this we could avoid some lines per operator.
But maybe I'm missing something here and you have other thoughts. Lets discuss it and close this so we can move forward :)

But maybe I'm missing something here and you have other thoughts. Lets discuss it and close this so we can move forward :)

Autogenerating these should be no problem, will do.
I also played around with the definitions, why not simply put the arrays into their own structs?
typedef struct operator_context operator_context;
typedef struct tensor           tensor;
typedef struct array_tensor     array_input;
typedef struct array_tensor     array_output;
typedef struct array_attribute  array_attribute;
typedef int (*operator)(void *ctx);

struct tensor
{
    Onnx__TensorProto *tensor;
    operator_context  *origin;
    char              *name;
};

struct array_tensor
{
    size_t  length;
    tensor *tensor[];
};

struct array_attribute
{
    size_t                length;
    Onnx__AttributeProto *attribute[];
};

struct operator_context
{
    array_input     *input;
    array_output    *output;
    array_attribute *attribute;
    operator         operator;
};

this would make the specific defines more readable
typedef struct array_input_TEST     array_input_TEST;
typedef struct array_output_TEST    array_output_TEST;
typedef struct array_attribute_TEST array_attribute_TEST;

struct array_input_TEST
{
    size_t  length;
    tensor *A;
    tensor *B;
};

struct array_output_TEST
{
    size_t length;
    // empty
};

struct array_attribute_TEST
{
    size_t length;
    // empty
};

typedef struct context_operator_TEST context_operator_TEST;

struct context_operator_TEST
{
    array_input_TEST     *input;
    array_output_TEST    *output;
    array_attribute_TEST *attribute;
    operator              operator;
};

void
operator_TEST(context_operator_TEST *ctx)
{
    printf("A: %s, B: %s\n", ctx->input->A->name, ctx->input->B->name);
}


connector: slack send self as first parent

Description
Related to https://github.com/dust-tt/dust/issues/9069

Start sending self (documentId) as first parent of slack documents

Risk
Low: no impact on content-nodes API nor retrieval (these additional parents are never used)
Deploy Plan

deploy connectors

(testing locally before merging)


Doesn't run blueprint

I installed with denali install and also tried running it manually, but no files added to the project.

Looks like the dist folder wasn't published.


t.init() not required for Size()

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 95.208%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1053

Relevant Lines:
1106

💛  - Coveralls


Adds an option to add columns with time zone

Adds an option to create time related columns like time, timestamp and
datetime with the option "with time zone" instead of just without it.
So we wouldn't break BC, the default is still false.
This is done by passing a with_time_zone=True as a parameter when
creating columns and so we don't break BC, the default is False.
Example:
with schema.table('users') as table:
    table.string('name')
    table.timestamps(with_time_zone=True)
    table.soft_deletes(with_time_zone=True)

This PR closes issue #185

@sdispater merge this into 0.9 or develop?

@josephmancuso I hadn't seen this but, yeah, since it's a new feature it should be made on develop to eventually land in the next 0.10 version.
@pedrochaves Can you change the base branch to develop?

Actually, I was able to fix it just now, it was easier than I had imagined in the first place.
Good to go now!

@pedrochaves Great! Thank you for your contribution! This should be available in the next release!

When is 0.10 coming out with this feature?


ServiceStack.Text incompatibility

Describe the feature
value.ToJson() result is
{"Value":"Fancy","Name":"Fancy"}
explected result: Fancy

Implemented in #137


Added Datastructures on IPFS blog

We need to ask InfoQ if we can embed their video. It is downloadable; are they alright we us adding it here?
Also, the slides were not interleaved with the text in the summary I got (which I had to edit at length). We can have someone do that if we think it is necessary.
cc @skylarnorris and @jbenet

Closing ancient posts that never got posted.


Syslog-agent does not sanatize hostame

The syslog hostname has historically been sanitized to comply with RFC 1034. https://github.com/cloudfoundry/cloud_controller_ng/blob/a732bdfe9c8013e69fd610f342b00c0ce384b1c8/spec/unit/controllers/internal/syslog_drain_urls_controller_spec.rb
The syslog agents don't do this when the org, space, and app names exist as tags on the logs:
https://github.com/cloudfoundry/loggregator-agent-release/blob/4125b9897614b6e711591a635ce09c7c46b2686c/src/pkg/egress/syslog/rfc5424.go#L66-L81
This might allow invalid characters into the hostname and break downstream log consumers

Just wanted to give a heads up and mention that we're affected by this and are losing logs from several spaces.

We are having issues because of this change. Some users created spaces or apps with _, so the resulting hostname field is something like my_app.my_space.organization, and as you know _ is not an allowed character data in DNS names.
Also, I think is is a breaking change and I could not find it in the release notes.

As you might be able to tell from above.  I have submitted a PR to help solve this in the syslog agents.

This has been fixed, and will be released in 6.0.2 in the next few days.


[BUG] Using synonym filter after hunspell.

Describe the bug
When using synonym filter after hunspell. I don't see the expected plural synonyms in the output. In the configuration below, I have added synonyms:

stationary
stationery
stationaries
stationeries

PUT /test-index3
{
  "settings": {
    "analysis": {
      "filter": {
        "custom_synonym_graph-replacement_filter": {
          "type": "synonym_graph",
          "synonyms": [
            "stationary, stationery, stationaries, stationeries"
          ]
        },
        "custom_hunspell_stemmer": {
          "type": "hunspell",
          "locale": "en_US"
        }
      },
      "analyzer": {
        "test_analyzer": {
          "type": "custom",
          "tokenizer": "whitespace",
          "filter": [
            "lowercase",
            "custom_hunspell_stemmer",
            "custom_synonym_graph-replacement_filter"
          ]
        }
      }
    }
  }

While testing, I don't see stationaries and stationeries in the output.
POST /test-index3/_analyze
{
  "analyzer": "test_analyzer",
  "text": "stationary"
}

--
{
  "tokens": [
    {
      "token": "stationery",
      "start_offset": 0,
      "end_offset": 10,
      "type": "SYNONYM",
      "position": 0
    },
    {
      "token": "stationary",
      "start_offset": 0,
      "end_offset": 10,
      "type": "SYNONYM",
      "position": 0
    },
    {
      "token": "stationary",
      "start_offset": 0,
      "end_offset": 10,
      "type": "word",
      "position": 0
    }
  ]
}

Here is the details analysis from Opensearch:
POST /test-index3/_analyze
{
  "analyzer": "test_analyzer",
  "text": "stationary",
   "explain": true
}

------------------
{
  "detail": {
    "custom_analyzer": true,
    "charfilters": [],
    "tokenizer": {
      "name": "whitespace",
      "tokens": [
        {
          "token": "stationary",
          "start_offset": 0,
          "end_offset": 10,
          "type": "word",
          "position": 0,
          "bytes": "[73 74 61 74 69 6f 6e 61 72 79]",
          "positionLength": 1,
          "termFrequency": 1
        }
      ]
    },
    "tokenfilters": [
      {
        "name": "lowercase",
        "tokens": [
          {
            "token": "stationary",
            "start_offset": 0,
            "end_offset": 10,
            "type": "word",
            "position": 0,
            "bytes": "[73 74 61 74 69 6f 6e 61 72 79]",
            "positionLength": 1,
            "termFrequency": 1
          }
        ]
      },
      {
        "name": "custom_hunspell_stemmer",
        "tokens": [
          {
            "token": "stationary",
            "start_offset": 0,
            "end_offset": 10,
            "type": "word",
            "position": 0,
            "bytes": "[73 74 61 74 69 6f 6e 61 72 79]",
            "keyword": false,
            "positionLength": 1,
            "termFrequency": 1
          }
        ]
      },
      {
        "name": "custom_synonym_graph-replacement_filter",
        "tokens": [
          {
            "token": "stationery",
            "start_offset": 0,
            "end_offset": 10,
            "type": "SYNONYM",
            "position": 0,
            "bytes": "[73 74 61 74 69 6f 6e 65 72 79]",
            "keyword": false,
            "positionLength": 1,
            "termFrequency": 1
          },
          {
            "token": "stationary",
            "start_offset": 0,
            "end_offset": 10,
            "type": "SYNONYM",
            "position": 0,
            "bytes": "[73 74 61 74 69 6f 6e 61 72 79]",
            "keyword": false,
            "positionLength": 1,
            "termFrequency": 1
          },
          {
            "token": "stationary",
            "start_offset": 0,
            "end_offset": 10,
            "type": "word",
            "position": 0,
            "bytes": "[73 74 61 74 69 6f 6e 61 72 79]",
            "keyword": false,
            "positionLength": 1,
            "termFrequency": 1
          }
        ]
      }
    ]
  }
}

The hunspell rules and dictionary files are attached.
en-US.aff.txt
en-US.dic.txt
Related component
Other
To Reproduce
N/A
Expected behavior
The screen capture for Solr analysis screenshot where the synonym graph filter is highlighted. You will see all the synonyms displayed under SGF

Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Coming from https://github.com/opensearch-project/OpenSearch/issues/16263 and with the proposed fix to add synonym_analyzer for the synonym_graph (PR https://github.com/opensearch-project/OpenSearch/pull/16488) should solve this bug as well.

Download the attached .aff and .dic files and put them under config/hunspell/en_US folder.
Please note there is an issue in the attached .aff file, the following has to be updated to SFX Z Y 14 as SFX Z rule has 8 declared in the header but actually contains 14 rules.

SFX Z Y 8
SFX Z   0     rs         e
SFX Z   y     iers       [^aeiou]y
SFX Z   0     ers        [aeiou]y
SFX Z   0     ers        [^ey]
SFX Z   0     ners         [aiu]n
SFX Z   0     ers          [^e]an
SFX Z   e     ners         [aiu]ne
SFX Z   0     rly         e
SFX Z   y     ierly       [^aeiou]y
SFX Z   0     erly        [aeiou]y
SFX Z   0     erly        [^ey]
SFX Z   0     nerly       [aiu]n
SFX Z   0     erly        [^e]an
SFX Z   e     nerly       [aiu]ne

Once assembled (https://github.com/prudhvigodithi/OpenSearch/tree/bug-fix-synonym) start with ./gradlew run -PnumNodes=1.

Testing the query  with synonym_analyzer.

curl -X PUT "localhost:9200/test-index5" \
-H "Content-Type: application/json" \
-d '{
    "settings": {
        "analysis": {
            "filter": {
                "custom_synonym_graph-replacement_filter": {
                    "type": "synonym_graph",
                    "synonyms": [
                        "stationary, stationery, stationaries, stationeries"
                    ],
					"synonym_analyzer": "standard"
                },
                "custom_hunspell_stemmer": {
                    "type": "hunspell",
                    "locale": "en_US"
                }
            },
            "analyzer": {
                "test_analyzer": {
                    "type": "custom",
                    "tokenizer": "whitespace",
                    "filter": [
                        "lowercase",
                        "custom_hunspell_stemmer",
                        "custom_synonym_graph-replacement_filter"
                    ]
                }
            }
        }
    }
}'

  curl -X POST "localhost:9200/test-index5/_analyze" -H "Content-Type: application/json" -d '{
	"analyzer": "test_analyzer",
	"text": "stationary"
  }'

Output: The output now contains stationaries and stationeries.

{
  "tokens": [
    {
      "token": "stationery",
      "start_offset": 0,
      "end_offset": 10,
      "type": "SYNONYM",
      "position": 0
    },
    {
      "token": "stationaries",
      "start_offset": 0,
      "end_offset": 10,
      "type": "SYNONYM",
      "position": 0
    },
    {
      "token": "stationeries",
      "start_offset": 0,
      "end_offset": 10,
      "type": "SYNONYM",
      "position": 0
    },
    {
      "token": "stationary",
      "start_offset": 0,
      "end_offset": 10,
      "type": "word",
      "position": 0
    }
  ]
}

Thank you
@msfroh @getsaurabh02 @nupurjaiswal @dblock @aswad1


Equivalent of codecarbon in another programming language? (C)

Hello!
Not really an issue here, but I was wondering if there were any equivalent to
codecarbon in another programming language like C?
(or at least, a way to replicate the tracking part codecarbon has)
Actually working on a project using a microcontroller from ST.
Apart from that, did you ever consider porting codecarbon in another programming language?
Thanks!

Hi Theo!
I don't personally know any equivalent tool, which could track emissions from a program.
In virtualized environments, where a hypervisor is self-administrated, we recommend using Scaphandre, which can be used to segregate consumption from VMs (and maybe by process, also).
For your use case, the chip is not supported by the project, and if its operating system doesn't expose a RAPL interface, there is a few chance that we could be able to read its electrical consumption.

Hello,
You are talking about a microcontroller, it's a very different world and we won't support that anytime soon, sorry.


calculator: improved the code and added a simple user interface

I improved the code:

more efficient  in the evaluate(...)
added a error management in the parser(...) and in the UI.

And I added a simple user interface (command-line)

@christianbender  Good work. I have left some comments for you suggesting some changes.

@goswami-rahul  I have changed my code across your request.


Updated dependencies for node 0.12 compatibility

Updated dependencies and ran npm test. All test passed using node 0.12.

Addressed in b71c001ec6ab545b7b28a31758fa1a6e2495eaf3.
Thanks

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Q: project repo available to fabfile?

Hi,
this project is quite new to me and looks very exciting. Great job, this looks like what I've been looking for for a while now.
I've successfully installed fabric-bolt and deployed a project with it.
Now I am trying to build a custom fabfile which would initialize the project on the host if the project doesn't exist there yet. In order to do that I need to have access to the project's repo_url (to do the iitial clone). I cannot find it in the env. Am I missing something or is the repo_url not available from inside the fabfile?
Cheers,
Emma

Hey Emma,
Thanks for the interest in the project. It's exciting to know you've been able to run a deployment.
As to your issue, we don't currently add the repo url automatically to the env variable in Fabric. However, you can use a project configuration to accomplish what you're after.
Here's a screen shot

Notice that there are project & stage configurations. If you define repo_url on a project & then again on a stage it will be overridden by what's defined on the stage.
Let us know if we can help further.

Hi Nathaniel,
thanks for the answer, this will help me get started with what I want to do! :smile:


Win32API removed in Ruby 2.1+

Win32API was removed from Ruby 2.1+.  We should consider switching to the win32-api gem.
@jrafanie @tenderlove @roliveri
Here is git grep Win32API:
manageiq-gems-pending/lib/gems/pending/util/extensions/miq-file.rb:2:require 'Win32API' if Sys::Platform::OS == :windows
manageiq-gems-pending/lib/gems/pending/util/extensions/miq-file.rb:23:      returnSize = Win32API.new("kernel32", "GetShortPathNameA", 'ppl', 'L').Call(longName,  buffer, size)
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:2:require 'Win32API'
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:25:  @@createFile        = Win32API.new('kernel32', 'CreateFileA',       'PLLLLLL',  'L')
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:26:  @@setFilePointerEx  = Win32API.new('kernel32', 'SetFilePointerEx',  'LLLPL',      'L')
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:27:  @@readFile          = Win32API.new('kernel32', 'ReadFile',          'LPLPL',    'L')
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:28:  @@writeFile         = Win32API.new('kernel32', 'WriteFile',         'LPLPL',    'L')
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:29:  @@closeHandle       = Win32API.new('kernel32', 'CloseHandle',       'L',        'L')
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:30:  @@getFileSize       = Win32API.new('kernel32', 'GetFileSizeEx',     'LP',       'L')
manageiq-smartstate/lib/disk/modules/MiqLargeFileWin32.rb:31:  @@getLastError      = Win32API.new('kernel32', 'GetLastError',      nil,        'L')
manageiq-smartstate/lib/metadata/util/win32/Win32EventLog.rb:16:require 'Win32API' if Sys::Platform::OS == :windows

It's actually still in Ruby, as of 2.2.2. They've been threatening to remove it for years, but never do.
In any case, I think this should be refactored to use FFI instead of win32-api since we already have ffi as a dependency. One less gem to worry about. :)

Actually...I think this file can be removed. Ruby has supported large files on Windows since 1.9. I don't see this code doing anything special.

@djberg96 Which file can be removed?

@chessbyte MiqLargeFileWin32.rb

Updated OP list.

@jerryk55 @roliveri As mentioned above, Ruby has supported large files for Windows since 1.9, so you shouldn't need MiqLargeFileWin32.rb any more.

We don't run on Windows at all anymore, so I think this can all just be deleted.

@Fryguy They still need it for SSA on Windows VM's though, don't they?

I don't believe so, no, but I'd have to double-check.  I think all usages of Win32API are inside code blocks that say if Sys::Platform::OS == :windows

I have found instances of MiqLargeFileWin32 required in manageiq-smartstate, and in manageiq-gems-pending only, and they all are in code blocks as stated by @Fryguy above.  I agree that this can be removed.

@Fryguy @jerryk55 https://github.com/ManageIQ/manageiq-gems-pending/pull/239

@Fryguy Since the remaining references to this are in the smartstate repo, can you please reassign this to Jerry or Rich?

Done @djberg96 .  Thanks for the PR!

@Fryguy @djberg96 @roliveri https://github.com/ManageIQ/manageiq-smartstate/pull/15

@Fryguy I think we can close this one.


the domain schemas.lepo.co is down

Describe the bug
the domain schemas.lepo.co is down
To Reproduce
the domain schemas.lepo.co is down
Expected behavior
the domain schemas.lepo.co is down
Screenshots
the domain schemas.lepo.co is down
OS version
the domain schemas.lepo.co is down
.NET version
the domain schemas.lepo.co is down
WPF-UI NuGet version
the domain schemas.lepo.co is down
Additional context
the domain schemas.lepo.co is down

Bro ... this is NOT a domain. Please close this "issue", thanks.

@joseborges Bro ... this is NOT a domain. Please close this "issue", thanks.

Bro, it's not a domain, but isn't it needed for using WPF-UI xaml files?

@joseborges it is but not as domain, so close this. That's not an issue.

Is there a way I can get the missing "content" expected from those endpoints? I can't find them on the repository.


Basic question using ESP32

I have gone through the examples but I do not see any code that indicates which GPIO to connect to my data pin for my WS2812B strip. I'm guessing I'm missing something very basic.
I was able to upload the examples and I find the devices in the Alexa app, but I'm unable to actually do anything with them (even though I turn lights on and change colors in the app). The examples don't show any data pin configurations, so how do I get the ESP32 to communicate with my WS2812B LED strip?

In the examples there are no strips connected. The EspalexaColor just prints out the color values via the serial monitor.
You need another library for your led strips (e.g. Adafruit NeoPixel, NeoPixelBus or FastLED).

In the examples there are no strips connected. The EspalexaColor just prints out the color values via the serial monitor.
You need another library for your led strips (e.g. Adafruit NeoPixel, NeoPixelBus or FastLED).

In the examples there are no strips connected. The EspalexaColor just prints out the color values via the serial monitor.
You need another library for your led strips (e.g. Adafruit NeoPixel, NeoPixelBus or FastLED).

Great, I think I got it figured out. Thank you!

In the examples there are no strips connected. The EspalexaColor just prints out the color values via the serial monitor.
You need another library for your led strips (e.g. Adafruit NeoPixel, NeoPixelBus or FastLED).

Great, I think I got it figured out. Thank you!


Only comment test coverage on Pull Request (Take 2)

The verifier test failure is related to an ACA-Py bug. Looks like the 7s sleep may be too short for some ledger updates ... you can just rerun the tests


Move to ESM to be compatible with Vite/SvelteKit

Hi again :slightly_smiling_face:
I've been recommending your preprocessor to everyone in the chats who struggle with svelte scoping problems since v2 :grin:
It seems people want to use it for SvelteKit, which uses Vite for devmode, and it hard if at all possible to fix that: link.
Is it feasible or possible to move to ESM?
Thanks again for your work, Svelte is much better with your preprocessor :+1:

Yes, we should implement both distribution CommonJs and ESM


Switch to Vite

This stops manually vendoring dependencies and switches to npm+vite. Adding new dependencies later gets much easier. Please make sure the instructions for running locally in the readme work for you and make sense.
I also got rid of the d3 graphviz rendering.
It's possible I've messed up the github actions, but it's impossible to tell without just deploying it. :(
I left the smooth zoom plugin as a manual dep, because I couldn't get it working. The original repo has no NPM package. I found https://www.npmjs.com/package/projektpro-leaflet-smoothwheelzoom but it doesn't seem to work?

And while I'm here, I cleaned up the unused code for handling drag-and-drop files. Now that we need a .osm and a .geojson boundary as input, not sure we'll ever be able to revive this


Exclude unnecessary files from the npm package

Listed a few files and folders which are currently included in the published npm package, while they should not be.

Thank you

Worth releasing?


update elasticsearch plugin for elasticsearch 7

This PR will update the elasticsearch plugin to the 3.7.1 version and add the elasticsearch-xpack gem to be able to use ILM from within the plugin.

Thanks!


SPX API Redesign

Problems

Lack of non-blocking version for animation APIs, #327
Lack of property-transition APIs

Design Principles

Names should be easy to understand and close to natural language.

Existing capabilities in Scratch should have equivalent alternatives.

The usage style should fit with the overall coding style of Go+.
For example:
animate "jump", 0.5

In contrast, the following forms should be avoided:

Chainable API, like animate("jump").duration(0.5)
Constructing abstract objects, like newAnimation("jump").start()

The overall structure should be neat and intuitive.

For complex features (like animation, collision detection, etc.), the user code should describe the needs, not the implementation, leaving room for optimization by the engine.

Keep it short, ideally no more than 3 words.

Adjustments

Time-consuming operations (including animate, play, etc.) default to blocking, with non-blocking versions provided.
Transition versions should have a "trans" prefix.
Non-blocking versions should have a "start" prefix.

Details
https://realdream.larksuite.com/wiki/QF7Pwxn0tiO0n0kvllFuwluZsWb?from=from_copylink

Adjustments

Time-consuming operations (including animate, play, etc.) default to blocking, with non-blocking versions provided.
Transition versions should have a "trans" prefix.
Non-blocking versions should have a "start" prefix.

1 & 3 confirmed with @xushiwei , 2 requires further discussion.


Bug: Android Messages "Use Messages for web here"

Bug description:
When on Ferdi loads for the first time on boot up. Android Messages shows this pop up

I don't have another desktop app running that has Android Messages signed in nor another computer running that might cause the conflict.
Perhaps, it's because I'm using a VPN though I don't experience this issue in Rambox.
Steps to reproduce:

Add Android Messages as a service
Sign in
Reboot or completely closed Ferdi and open Ferdi again
Access Android Messages
Issue appears

Expected behavior
Pop up shouldn't appear
Environment:

Operating System: Windows 10 x64
Ferdi Version: 5.5.0
Server: Ferdi

This has nothing to do with Ferdi. Google's server has identified that there are 2 IPs associated with the android messages (web) - thus, in effect counting them as 2 different sessions. Once this scenario is deduced, then the popup gets triggered - from/by the server.
To fix this issue, you should use your Android Messages mobile app, go into the three-vertical-dots on the top right (called the context menu), and select "Messages for web". Here, all active sessions will show up - and you can evict the ones that are old.


Miscellaneous interop changes

This contains the following changes:

Added support for CBool Marshalling
Parse MarshalAsDescriptor correctly based on native type
Separate out AllocManagedToNative and TransformManagedToNative from
AllocAndTransformManagedToNative for Array Marshaller so that the
codepath that calls TransformManagedToNative works correctly.
Handle ByRef type for delegate marshalling

This fixes two CoreCLR tests:

MarshalBoolArrayTest
BoolTest

@yizhang82 @tijoytom  PTAL


[BEAM-7284] Cleanup MappingProxy reducer since dill supports it now.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @lazylynx

@tvalentyn LGTM, thanks!

Thanks for a quick review, @lazylynx !


Feature request: mark as spam

Hi, would it be possible to add a "mark as spam" option to the {make private, edit paste, delete} menu? It would be nice if it would automatically ban the IP and delete the paste.

Btw, how do you manage to keep the amount of spam tolerable in paste.kde.org? I have all spam filters (with default thresholds) enabled, but I'm still struggling with the amount of spam lately. :(
Sticky Notes version: 1.9
PHP version: 5.4.36-0+deb7u3
DB driver: mysql

It would be also useful to be able to manually re-run the spam filters after adding censored phrases.

You can disable public posts - which is unfortunately the best fix. KDE Paste needs some manual monitoring but usually the stealth filter knocks out quite a bit of spam.


allow pass attribute and options as Collection

Example if css-attribute is Collection implode with ","

Released with 1.2.0


Reviewdog gets confused when proposing changes of code that include markdown

See here
https://github.com/JuliaManifolds/Manifolds.jl/pull/400#discussion_r672321087
where the code change included markdown, but since posted as a markdown comment, this got screwed up.

The document says it is needed to wrap them inside quadruple backticks.
https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks

To display triple backticks in a fenced code block, wrap them inside quadruple backticks.

````
```
Look! You can see my backticks.
```
````

```
Look! You can see my backticks.
```

Thanks, that could help.
But what if the code uses quadruple backticks? Then watchdog has to use quintruple ones?


Adds jq -r for correct metering host value

Without the -r flag to jq, command as written in the docs to get the METERING_ROUTE_HOSTNAME was incorrect -- was surrounded by double quotes.

We also mentioned this in configuring reporting-operator


Still have errors with actix-web-grants

Hello,
Thank for fixing most of the errors, but there is some left.
error[E0599]: no function or associated item named responses found for struct ResponseWrapper in the current scope
error[E0599]: no function or associated item named schema found for struct ResponseWrapper in the current scope
error[E0599]: no function or associated item named child_schemas found for struct ResponseWrapper in the current scope
error[E0599]: no function or associated item named error_schemas found for struct ResponseWrapper in the current scope
Error is like:
function or associated item not found in ResponseWrapper<Box<dyn futures_util::Future<Output = actix_web::Either<Result<HttpResponse, actix_web::Error>, HttpResponse>> + Unpin>, __openapi_accept_presentation>

Hey ! Should be fixed in 0.3.3


[vgpu-manager] update firmware search path so nvidia kernel module ca…

…n find GSP firmware

Let's do this is in rhel9 as well please

Let's do this is in rhel9 as well please

We currently do not have a rhel9 directory for the vGPU Manager image.

Could you re-write the commit message/ PR tittle so it doesn't show as both title and message as is happening right now

Done.
ping @shivamerla for a re-review.

@cdesiniotis Can this be merged?


Add support for yarn 3+

Drop the --prefer-offline flag if the yarn magor version is not 1 since it is not supported in v3+ of yarn.
Add caching to .yarn/cache which yarn 3+ uses as it's cache.

I tested this on https://github.com/planningcenter/church-center/pull/2256 and it works well.

@molawson Yeah, we can let yarn handle setting the version 😆
@sheck I'm not sure what benefit enabling corepack has, but it works without it, so I removed it.
Thanks for your input, team. This is ready for re-review.

@sheck I can add a new tag. That's all we need to push a new "release" of an action right?
@molawson yeah, I made a test PR with no changes to confirm that it works with classic yarn.

Ah, I see we are running https://github.com/marketplace/actions/advance-semver-tags so I can cut a new Release. 👍


Dependency Problem

When I try to update to the newest version I receive the following error (on two different machines)
Error installing fastlane:
conflicting dependencies highline (~> 1.6.11) and highline (>= 1.7.2)
  Activated highline-1.7.2
  which does not match conflicting dependency (~> 1.6.11)

  Conflicting dependency chains:
    fastlane (= 1.101.0), 1.101.0 activated, depends on
    krausefx-shenzhen (>= 0.14.10), 0.14.10 activated, depends on
    highline (>= 1.7.2), 1.7.2 activated

  versus:
    fastlane (= 1.101.0), 1.101.0 activated, depends on
    krausefx-shenzhen (>= 0.14.10), 0.14.10 activated, depends on
    commander (< 5.0, >= 4.3), 4.3.0 activated, depends on
    highline (~> 1.6.11)

Nothing to update

I have tried uninstalling and reinstalling to no avail.
Thanks for your help.

Hi @glancashire Thanks for reaching out. Do you use RVM to manage rubies? Also can you uninstall the highline gem and then run sudo gem update fastlane?

Dear Todd
I am not using RVM.
I have uninstalled highline and installed fastlane
Both of which worked (highline-1.7.8), w.o. error.
When I try to update, the same error.
As far as I can see commander v4.3 is used which requires highlane 1.6… which causes the problem
…
ERROR:  Error installing fastlane:
conflicting dependencies highline (~> 1.6.11) and highline (>= 1.7.2)
Activated highline-1.7.2
which does not match conflicting dependency (~> 1.6.11)
Conflicting dependency chains:
fastlane (= 1.101.0), 1.101.0 activated, depends on
krausefx-shenzhen (>= 0.14.10), 0.14.10 activated, depends on
highline (>= 1.7.2), 1.7.2 activated
versus:
fastlane (= 1.101.0), 1.101.0 activated, depends on
krausefx-shenzhen (>= 0.14.10), 0.14.10 activated, depends on
commander (< 5.0, >= 4.3), 4.3.0 activated, depends on
highline (~> 1.6.11)
Nothing to update
…
Kind Regards
Graham
➜
Swift Management AG | Managing Partner
St. Alban Vorstadt 104 | 4052 Basel | Switzerland
T ++41 61 385 55 50 | M ++41 79 485 25 20
<EMAIL_ADDRESS>| www.swift.ch

On 24.08.2016, at 17:09, Todd Burner<EMAIL_ADDRESS>wrote:
Hi @glancashire Thanks for reaching out. Do you use RVM to manage rubies? Also can you uninstall the highline gem and then run sudo gem update fastlane?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you run gem cleanup and then [sudo] gem install fastlane? 👍
If that doesn't work, you might want to start using a Gemfile, which is the recommended way to store dependencies in your repo.

This worked

gem cleanup

Thanks for the suggestion I added a gemfile
Graham

On 25.08.2016, at 00:55, Felix Krause<EMAIL_ADDRESS>wrote:
Can you run gem cleanup and then [sudo] gem install fastlane? 👍
If that doesn't work, you might want to start using a Gemfile, which is the recommended way to store dependencies in your repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah 🎉


Overwrite the existing dlls while unzipping

In vision, the build & test are running on Windows GPU machines.
So far, The default cuda driver is 10.1 in circleCI image.
So there's alreay gpu_driver_dlls, we should allow the old dlls could be overwrited by the downloaded dlls(10.2).
Else, there's the error

https://app.circleci.com/pipelines/github/pytorch/vision/10311/workflows/c0f4755c-4254-40cd-ad67-418617a7817f/jobs/781019

@malfet @NicolasHug
It's the first step to enable CUDA tests in vision.
Could you please review this PR as soon as possible. I could submit the following PRs.
There're only 4 mac workflows failure. I think it's a known issue and has nothing with this PR

For 10.2, if the dlls are not overwrited.
the cuda driver version and cuda runtime version will not be consistent

As mentioned in https://github.com/pytorch/vision/pull/4058#issuecomment-862532742
There's always No CUDA Runtime is found,... when running python setup.py install with cuda 10.2.
I'll make the copying logic only for 10.2 in another PR.


[CHORE] add render component test to all components

Check all components and add .spec.js. Test renders a component.
import { shallowMount } from "@vue/test-utils";
import SfFooter from<EMAIL_ADDRESS>
describe("SfFooter.vue", () => {
  it("renders a component", () => {
    const component = shallowMount(SfFooter);
    expect(component.contains(".sf-footer")).toBe(true);
  });
});

@peoray are you going to finish this task or can I assign myself? :)

I'm working on it :)


Video session is not started

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to Video
Click on Cancel
Again open the picker and go to video and then again click on cancel. Do this scenario for upto 3-4 times. You will see video session is not started properly.

Environment (please complete the following information):

Device: [e.g. iPhoneX]
OS: [e.g. iOS12.1]
Xcode Version [e.g. 10.0]
Swift Version [e.g. 4.1]

Installation Type

Cocoapods

There is 2022 year outside🎉 Old outdated issues are closing. Please search if there are already existing issues with the same problem before opening new ☮


2024-11-20_01-35-31_master-next_aws-crt-python

Automatically created.

Successfully created backport PR for kirkstone-next:

#10429

Successfully created backport PR for scarthgap-next:

#10430

Successfully created backport PR for styhead-next:

#10431


suggest add sessionStorage

Because sometimes sessionStorage is needed, so this is my suggest.
just like this
Vue.use(VueLocalStorage, {
localStorageName: 'ls',
sessionStorageName: 'ss',
bind: true
})

I would like to work on this feature!
Ideally one would create a storage-unagnostic system where you could switch between multiple implementations of local/sessionstorage as long as they are standards compliant!