Goslmailer install

Adds Goslmailer ansible playbook. This installs Mutt and all requisite config files and directories from our fork of goslmailer.

Please reference the git issue somewhere in the pr so I can go back to look at it as well.

Sorry I shouldn't have pinged you yet I was still writing the request

One last thing before I forget. Squash or fixup your commits before merging.


Incorrect model listing

System listed as N3DS XL RED, but system is actually N3DS XL NEW GALAXY EDITION

Lol, RED is the code name for N3DS XL. It isn't determining the colour.
https://3dbrew.org/wiki/Cfg:GetSystemModel#System_Model_Values

Lol sorry forgot that RED was the codename, that's what happens when codenames are normal words


Terminal tab issue

command workbench.action.terminal.focusTabs is invalid after September 2022 's update

In addition to this, my terminal tab showing "Starting..." endlessly after start.

/duplicate https://github.com/microsoft/vscode/issues/163789

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Changelog: Make compile-time errors catchable

Issue: https://github.com/dart-lang/sdk/issues/23684
Commit: https://github.com/dart-lang/sdk/commit/3e0d13bc287cc89ebc15969376a90bd7f67bef6a
Should make a lot of folks happy
sample with pkg/test
Before
00:00 +0 -1: loading test/io_server_test.dart
  Failed to load "test/io_server_test.dart":
  line 16 pos 15: 'continue' is illegal here
  void badFn() {continue;}
                ^
00:00 +0 -1: Some tests failed.

After
00:00 +0 -1: serves HTTP requests with the mounted handler
  'file:///Users/kevmoo/source/github/shelf/test/io_server_test.dart': error: line 16 pos 15: 'continue' is illegal here
  void badFn() {continue;}
                ^

  test/io_server_test.dart 30:20  main.<fn>.<async>.<fn>
  dart:async                      runZoned
  test/io_server_test.dart 30:5   main.<fn>.<async>
  dart:async                      _SyncCompleter.complete
  package:http/http.dart 167:5    _withClient.<async>

00:00 +2 -1: Some tests failed.

I can see where the bad call happened. The rest of the tests ran.

In progress: https://codereview.chromium.org/2368413003/


feat: define a simple CI pipeline

Introduces a CI workflow to run make test for PRs.

Currently the test make target is set up to install (part of) grafonnet from Github rather than the local branch, which doesn't always deliver reliable results for the changes they one makes. Taking that into account, this CI job is already an improvement as it does test changes in grafonnet-base.


ensure azure-service-operator community-operator contains latest fixes found in upstream-community-operators

This PR features same fixes that were committed to upstream-community-operators.
Signed-off-by: Matt Dorn<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ x] Does your operator have nested directory structure?
[x ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ x] Are you familiar with our contribution guidelines?
[x ] Have you packaged and deployed your Operator for Operator Framework?

[ x] Have you tested your Operator in all supported installation modes?
[ x] Have you considered whether you want use semantic versioning order?
[x ] Is your submission signed?
[ x] Is operator icon set?

Updates to existing Operators

[ x] Did you create a ci.yaml file according to the update instructions?
[ x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ x] Have you tested an update to your Operator when deployed via OLM?
[ x] Is your submission signed?

Your submission should not

[ x] Modify more than one operator
[ x] Modify an Operator you don't own
[ x] Rename an operator - please remove and add with a different name instead
[ x] Submit operators to both upstream-community-operators and community-operators at once
[ x] Modify any files outside the above mentioned folders
[ x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ x] Human readable name and 1-liner description about your Operator
[ x] Valid category name1
[ x] One of the pre-defined capability levels2
[ x] Links to the maintainer, source code and documentation
[ x] Example templates for all Custom Resource Definitions intended to be used
[ x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@madorn i set label to overwrite already published operator version. Click Ready for reviewif you agree

@madorn, checking deploy logs, I see
    NAME                                               READY   STATUS              RESTARTS   AGE
    azureoperator-controller-manager-5bfbcbb56-8gxts   0/2     ContainerCreating   0          16m

We also see CatalogSourcesUnhealthy from get subs and lastObservedState: READY from get catalogsource.
The 2 main reasons for this could be dependency on another operator, where our test is testing just one operator. Or another reason could be that you operator is unable to start in our test namespace. But I have feeling that there is some other issue, because operator got to a container creation phase. Please check.

@J0zi this operator has a dependency on cert-manager.
Same with the published upstream-community-operator version of this operator.


Fix Dockerfile build with the current upstream location

Update location of near_exporter on GitHub
Bump Golang to 1.22, but don't pin the image version firmly
go mod tidy

Tested with docker build --rm . and it seems to build.


Reference parameters within a context

Author Name: Steffen Claus (Steffen Claus)
Original Redmine Issue: 2117, https://dev.opennebula.org/issues/2117
Original Date: 2013-06-12

I am trying to dynamically define needed files for a template as follows:
CONTEXT[
FILES_DS="$FILE[IMAGE="testfile"] $FILE[IMAGE="$MY_NAME"]"
]
MY_NAME="image-name"
This doesn't work at the moment, as the parameter $MY_NAME is not expanded.

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2013-06-12T12:36:24Z

This makes sense indeed. I am moving this to the backlog to implement it in a future release. This issue will deal with this and a more general situation where substitutions may happen in other variables.
Additionally we may consider it in relation with flow, so variables can be substitute in multiple service templates.
THANKS for your feedback

Already implemented in current versions


Operation returned an invalid status code 'Forbidden': App Only Sample Code

I am getting below error for App Only Sample Code when i click on Embed Report.
Please help me to resolve this
Operation returned an invalid status code 'Forbidden'
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Rest.HttpOperationException: Operation returned an invalid status code 'Forbidden'
Source Error:
Line 74:                 // Generate Embed Token. Line 75:                 var generateTokenRequestParameters = new GenerateTokenRequest(accessLevel: "view"); Line 76:                 var tokenResponse = await client.Reports.GenerateTokenInGroupAsync(GroupId, report.Id, generateTokenRequestParameters); Line 77:  Line 78:                 if (tokenResponse == null)

Hi,
This could occur for many different reasons. mostly it's because the AAD token is expired or you are trying to access a group you are not a member of.
can you please give a request Id. you can find it in fiddler (or any other network capture tool).

Hi,
In debug mode i am able to see group, report URL and report Id detail, but its failing in while retrieving token response(Below code). my power BI app Setting and Fiddler detail is copied in below attached Doc.
Appreciate help on this.
PowerBI_Fiddler.docx
             var tokenResponse = await client.Reports.GenerateTokenInGroupAsync(GroupId, report.Id, generateTokenRequestParameters);

Hi,
Issue is resolved :) Just closed and reopened my Visual Studio there you go it started working :)


[FEATURE] ⛔ Handle Zero

Problem
Community member @CM2Walki kindly reported that when using TimeSpan.Zero as the Duration, no special treatment is being made by FusionCache. That value should clearly mean something like "don't cache this".
Truth be told, things are not this simple when you factor in fail-safe and similar mechanism, because you may want to say something like "store this as expired, but keep it for possible future usage as a fail-safe fallback", for example.
But still, it can make sense to special-case at least some usages of it.
All in all it is kinda similar to the special care reserved for infinite duration, where that logically means "never expire".
This situation, although maybe not that frequent, should be better handled.
Solution
Add a special handling for Durations with a value of TimeSpan.Zero, or negative values.
This special value should do one of two things, depending on the context:

if fail-safe is disabled, it should effectively Remove() the cached value, if any. It should NOT just skip saving the data, because if some value is already there and someone makes a call like cache.Set<int>("foo", 42, TimeSpan.Zero), at the next "get" operation they would get back the old value. So Remove() is the only thing that makes sense (if nothing is there, nothing happens)
if fail-safe is enabled, it should save it with a logical duration of zero, but with the correct FailSafeMaxDuration so that it can be used as a fallback in future calls

On top of this it would be nice to add to FusionCacheEntryOptions a couple of methods like SetDurationZero() and SetDistributedCacheDurationZero().

Hi all, v0.22.0 has been released and this is included 🎉


[INTEL oneDNN] Code clean: unsupport blocked format for fused batchnorm op

We will not support blocked format for oneDNN kernel operations.
This PR does related code cleanup of oneDNN FusedBatchNorm op and related tests.

Hi @gzmkl Can you please review this PR ? Thank you!

Any update on this PR?

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

Hi @gzmkl Can you please rebase your branch and resolve conflicts? Thank you!


Feature/react validation

Doing this more as a test if anything.

Can you add back the example config file? We don't want to remove that from the actual toolkit repo (my bad for doing that on your machine).

Done; I didn't realize the actual developer-config.js file is excluded via .gitignore.


Assignment 2

Edited 01-readinput.sh file and fixed the merge conflict

Don't see a branch or merge? See my comments on D2L gradebook.


Make sure that exports {default} throws an error

This checks if the local name of an export specifier is a keyword or reserved word only when there's no from clause (the case with a from clause appears to already work, though I'm not sure why).
Fixes #326

Are you sure that such check would be enough? (compared to https://github.com/marijnh/acorn/blob/master/src/expression.js#L642-L644)

Based on the tests I added, I think so. parseIdent is always called first, so this code seems to be triggered already.

parseIdent is called with liberal === true when keyword is _default so those conditions are not triggered https://github.com/marijnh/acorn/blob/master/src/statement.js#L551.

Yeah, that's for the form:
export default foo;

I haven't addressed that form in this PR as the bug was about non-default exports. Do you want me to look at that too?

No, that line covers exactly export { default } ....

Ah, I see. Still, I'm having trouble coming up with a test case that behaves incorrectly with this code. Do you have one in mind?

In fact you're right, there shouldn't be as default is a keyword so falls into another condition, and others are called with liberal = false anyway. It's me just being over-careful :)

No worries, I'd rather have you being over careful. :)

Any other changes needed here? @marijnh

Nope, looks great. But this airport wifi won't allow me to push to github, and this branch isn't based on the current master, so I don't want to use github's magic merge button which I expect will introduce needless merge commits. I'll merge this when I get home later today.

Merged as 37efe0b!

Thanks!


How to read highlighted text from the output not the command line?

I see how you can read highlighted text on the command line.
Is there a way to read highlighted text outputted from a previous command?
I’d like a short cut key where I highlight the url, ctrl+shift+b, and it launches it in the browser.

There is a win32 api GetConsoleSelectionInfo. PSReadline doesn't have a p/invoke signature for it, so you'll need some C#/Add-Type to use it, but it is possible. I don't plan on adding anything to PSReadlne though, because it will be confusing as I already have GetSelectionState which is different from the console's idea of what is selected.

Gave this a try. I have no clue. Could you provide an example to extend?


feat: support multiple time columns with time grain in Pivot Table v2

SUMMARY

If the FF Generic Axis is enabled, the Pivot Table v2 will support multiple time columns with time grain. The TIME GRAIN  control also moves out from the time section.
There is a limitation in the current design that the Adhoc Column wasn't able to apply the Time Grain, I will open separated PR to support the dynamic detector for the column type.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

After
The time grain is applied on Order Date and Ship Date

The time grain is applied on Order Date and Ship Date except Category

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

/testenv down

/testenv up FEATURE_GENERIC_CHART_AXES=true

/testenv up FEATURE_GENERIC_CHART_AXES=true


Mitigation of problems

Mitigations of the problems found, we still need to either make the Archive tell Reader about the CompressedSizes of the archive or make a search for DataDescriptor, or both since that would increase performace in general, no need to decompress if we know the compressed size, current code is already handling that.

thanks!


Launch: first argument no longer reaches extension window

I am no longer able to launch an extension on a specific workspace. To reproduce:

generate an extension
open launch.json
add a folder to open as first argument

=> the folder is not opened

add the folder again so that it shows up as the first two entries in the arguments

=> now the folder is opened
@weinand @isidorn any ideas?

My suspect is https://github.com/Microsoft/vscode/blob/master/src/vs/platform/environment/node/argv.ts#L87
/cc @joaomoreno

I commented out that code and it still reproduces so it must be something else...

@joaomoreno this might be a regression from using the shared IEnvironmentService also for the main process. A much easier repro is this:

go into the folder of the Electron executable
run ./Electron --nolazy someFolder
notice that Code refuses to open that folder

Debug adds --nolazy to our startup and somehow as soon as you pass an argument to an app that uses minimist for parsing that is not registered as known argument, things go wrong.
If I add nolazy to our list in https://github.com/Microsoft/vscode/blob/master/src/vs/platform/environment/node/argv.ts#L38 this issue is gone.
Any clue?

as soon as you pass an argument to an app that uses minimist for parsing that is not registered as known argument

Probably minimist is parsing --nolazy as an option that takes a string instead of as a boolean flag. So, try adding nolazy as a boolean option in here.

Awesome. Good catch.

@joaomoreno yup, added it. Just sucks that we need to be aware of this in the future. I think it would be better if debug adds their arguments maybe as last thing to the list and not first.

nolazy is a node flag, not a debug flag.
On second thought, the real fix here is to not let Node and Electron arguments reach our system at all. But this is a good quick fix.

I've introduced this issue through this fix https://github.com/Microsoft/vscode/issues/13434
It does not make sense to pass the --nolazy flag here because VS Code controls how the extension host is launched.
@bpasero should I revert this?

I'm no longer adding the --nolazy flag for EH debugging.


Bug Report: Show as triggered after entryDelay

Describe The Bug:
Hi, Thanks so much for continuing the development of this plug-in! Very much appreciate it!
The log is littered with the following messages, I am running 6 different homebridge plugins, but only the xfinity home plugin causes this message:

[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:35:00] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Motion Detected' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

To Reproduce:

Install Plug-in
observe the homebridge log

Expected behavior:
The messages: "This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info."
to no longer appear in the log.
Logs:
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:35:00] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Motion Detected' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

Config:
.

Operating System:
Raspberian
Node Version:
v16.15.0
NPM Version:
8.12.1
Homebridge Version:
1.5.0
Plugin Version:
2.2.1

That's strange, the only thing I can think of that would cause this is if you have a slow network. How many contact sensors do you have?

No, so I might add an option in the config to do that. I didn't want to do it by default because then Siri requests wouldn't always be correct

The only command for Siri would be "is the ___ door/window open" which is why I was making it fetch the status for accuracy. As for the security system I plan to add an option to delay the triggered state. I just don't know what the touchpad reports for triggered as I haven't set my own off yet

If you would like to try the value that I need is what the status changes to in homebridge ui>plugins>Xfinity Home Settings>logs>Panel>info and the field I need is properties.status
(If you just open this page before it's set off it should refresh automatically)

Status: "entryDelay" is what it's currently set to for the triggered state, I need to know what comes after to change HomeKit to wait until the countdown ends

Not without having to filter through all of the panels responses

It wouldn’t refresh it in the UI if you triggered via Motion because the UI is set to update whenever a new log is detected so if the panel went from armed to triggered to armed(due to the target state still being armed but the current status being unrecognized ) then the status would update

please try version 2.4.0 and let me know if it fixed this problem

Ok, I tried adding faultAlarm but I think that only happens when armed night

Describe The Bug:
Hi, Thanks so much for continuing the development of this plug-in! Very much appreciate it!
The log is littered with the following messages, I am running 6 different homebridge plugins, but only the xfinity home plugin causes this message:

[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:35:00] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Motion Detected' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

To Reproduce:

Install Plug-in
observe the homebridge log

Expected behavior:
The messages: "This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info." to no longer appear in the log.
Logs:
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:34:43] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Contact Sensor State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[09/07/2022, 11:35:00] [homebridge-xfinityhome] This plugin slows down Homebridge. The read handler for the characteristic 'Motion Detected' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

Config:
.

Operating System:
Raspberian
Node Version:
v16.15.0
NPM Version:
8.12.1
Homebridge Version:
1.5.0
Plugin Version:
2.2.1

In version 3.0.0 this will be patched. The beta is currently out if you would like to test it.

Unfortunately I will need more info to properly fix, once I finish adding low battery support I will add a log with the needed information to finally figure out what is shown when the alarm is triggered

The Status changed to … should be the raw status of the panel which is why I haven’t been able to figure out the proper status for the alarm triggered after the entry delay. At some point I will add a switch in the config that allows you to choose wether or not the alarm will show as triggered immediately after a door being opened

Please try version 3.6.1-beta.1

Ok, I changed a few more things, can you please try again with v3.6.1-beta.2? (And I forgot to mention this the first time, but make sure you disable the Trigger on Entry option in the config)

Ok, thanks for the heads up. For now, just check, then uncheck the box, as this should put it in the config. I’ll make sure to fix that before the release goes public

OK, I’ve had a few other people mention the panel show as Unknown when being disarmed outside of the plugin, but I’m still not quite sure what is causing this. I just released another beta (3.6.1-beta.3 I think) that adds another log to help identify the problem. If you could try that out and post what the logs look like, that would be great. I almost exclusively use HomeKit to arm/disarm my system, so I’m never exposed to these problems.
As for the states in the API, I unfortunately cannot access how the security system was armed/disarmed without getting the whole system history and filtering it out, and even if I did that, HomeKit wouldn’t have any convenient way to show it, as it makes the Activity History based off of the statuses it sees, so developers have no way to affect the info displayed in there.


Can't access data from Ecowitt-WH51 soil sensor

Hey! I have first commented my issue at #5, but thought I'd make a new issue so it's cleaner. I have an Ecowitt (Fineoffset) WH51, which has also an id, but not an uid or channel. I can provide a screenshot from MQTT Explorer with all published outputs.

If you have further questions don't hesitate to ask. I'd be grateful if you could look into it!

Sorry it took a bit to look into this.
What values do you see for the moisture sensor? Is it binary 0/1? 0-100? 0-1 decimal numbers?

Hey, no worries! I believe the value ranges from 0-100 with float numbers

Just pushed some updates that should hopefully add support for your WH51. I don't actually have one of these devices to test with (tho I suppose I can just publish a few messages on MQTT to mock it).
Let me know if it's working for you. I updated the documentation to cover adding a moisture sensor and added an example for how to add a WH51, since it uses just a single 'id' and not id+channel. You'll want to put your 'id' value in for the 'uid' key in the config.

Fixed with https://github.com/DanielWinks/HassOS-Addons/commit/f1e8f3c040398a6c7cc3006dc03117d1e2db1f03


Can it list "Simulator Runtime" and download it ?

As we known, new Xcode from 15.0 "Simulator Runtime" was seperated, and can be download and install by "xcrun simctl runtime add", so, it necessary to support such functionality.

I think the same it is very annoying to have such a powerhouse to download and install Xcode in record time and then have to wait 30 minutes for the iOS runtime to be installed…

Isn't this in xcodes since this summer when xcode 15 went into beta?  There is an xcodes runtimes subcommand that lists available runtimes and download and install subcommands that download and install respectively.  Or is there something else?

Ahh good to know! The question was about the GUI. I think there it is not supported yet

Xcodes.app supports downloading runtimes now!


[Issue 16] Implement proper removal of cloned disk

This change creates a method, remove_disk, which fully erases a disk file and its VirtualBox reference after cloning

@rsaikali This project seems inactive for quite a while - over a year indeed. Maybe the mantainer can clear this better.
@sprotheroe Is this an active project? It's very useful to me. Is there any help needed?

Just in case, if it can help:
As a workaround I use this command between any vagrant destroy/up:
vboxmanage list hdds | grep -B 2 inaccessible | egrep '^UUID' | awk '{ print $2 }' | xargs -I{} vboxmanage closemedium disk {} --delete
In my case it seems to fix the disk/media reference in VirtualBox.
Inspired from: https://coderwall.com/p/8m--dq/purge-deleted-hard-disks-from-virtual-box

This would fix my current problem in Vagrant. Is this repository unmaintained? If so, is there a way to change ownership to someone who would maintain this?

@danowar2k Some food for thought - a thread on RubyGems about project adoption. It doesn't seem to be implemented yet, but there seems to be some ideas.

This is so frustrating...
There is of course no procedure for stale repositories on Github and no way to check if the owner of this is ever coming back.
RubyGems doesn't have any procedure to let people publish gem forks, like detecting that a repo is a fork of another repo which is a published gem and automatically adding a gem fork (or something like it).
Vagrant doesn't have a way to install plugins directly from github repositories.
I want to make the way to setup my Vagrant boxes completely painless, but right now I'm completely stumped as to how to incorporate the fix from the fork.

@EmersonPrado : Would you please publish the disksize gem as vagrant-disksize-fork or something like it? At the moment it would be the easiest way :-/

I found out that I can access the directory where Vagrant plugins are installed with the Vagrant.user_data_path method.
Right now I'm creating a patch and write a method above my Vagrantfile configuration where every time the disksize plugin is installed, I apply your patch to the appropriate file.
As I am completely unfamiliar with Ruby, I hope that will be enough and I won't have to compile something or other.

@danowar2k Yes, uploading a forked gem with an alternative name (have to think of a good one) is doable. I never uploaded to RubyGems, so it'll take some learning. The main problem is I don't think I can truly mantain the package. But would be a step forward.
BTW, I have other two fixes waiting. If you'd like, check other pending PRs.
Good to hear on the Vagrant patch. I usually make the gem directory a Git local repo, then apply changes there. git apply is my friend there.
Ruby is an interpreted language. Once you change it, Vagrant will catch. Just avoid doing changes with VMs on. Just a caution.


Add initial tests

First take at adding some tests. Fixes #1

thanks for the change @wilburhimself ❤  merging.


Add send mail test

Add send mail test which certify send grid post method are being called whe send_mail method are called.

Thanks bro! :)


Upload file component doesn't respond to 'click choose file' due to Dragon / browser bugs

This issue is from May 2023 external accessibility audit report.
Usability issue
Issue ID:
DAC_Usability_Upload_File_02
URLs:
https://govuk-frontend-pr-3503.herokuapp.com/full-page-examples/upload-your-photo-success
Screen shots

The ‘choose file’ input does not respond to any verbal command for users of voice activation software. This means that the user must use verbal keyboard commands such as ‘Press tab’ etc, in order to access the component.
Current code ref(s)
#photo
Voice activation user comments

“I am unable to upload a photo with Dragon commands. The ‘choose file’ component does not respond to any Dragon commands. This means I must use keyboard commands with dragon to activate it this will simulate a manual keyboard through voice activation. I will use the command ‘press tab’ to move my focus onto the component. Then the command ‘press enters’ to activate for the file explorer to appear. This is very time consuming and frustrating to be able to access one component.
I would expect the ‘choose file’ button to respond to the command ‘click button’ and label by name. When I use the command ‘click choose file’ I would expect the file explore to automatically appear. This makes it more accessible for me to complete with dragon commands.”

Solution
Consider using the following implementation to enable all users to use the file upload as expected:
<div> <span> <input type="file" id="file-upload" style="display: none;"> </span> <label for="file-name">Upload your photo</label> <button id="file-upload-button" style="background:green; color:white;">Choose File</button> <input type="text" disabled readonly id="file-name" value="No file chosen"> </div>
<script> document.getElementById("file-upload-button"). addEventListener("click", function(){ document.getElementById("file-upload").click(); document.getElementById("file-name").value = document.getElementById("file-upload").value; }); </script>

Looking at this old issue, it seems that Dragon can sort of be coerced into working with file inputs if you use a label with role="link" on it.
This doesn't really fix the problem unless we make the input label read something like "Choose file". It apparently doesn't work unless the user states the entire label name (only saying part of the label does not work (although it does for other labels), it doesn't even work consistently anyway, and there's the fundamental weirdness of identifying something as a link when it isn't.

This came up again in the accessibility audit of GOV.UK Frontend components by DAC in July 2024.
The new (but same) issue: https://github.com/alphagov/govuk-design-system/issues/4031
This time we investigated if we could fix this in any way and spent more time trying various potential solutions.
Here is a summary of the work we've done recently to try to fix this issue.
We investigated this and are confident we can mostly fix this.
We've built a prototype to enhance the file upload component not just to fix this but also to add other useful enhancements. Because that was mostly successful, we plan to build it properly.
Although that generally fixes the issue, we noticed it only works the first time you interact with the component and after that it fails to react. We’ve looked at lots of different implementations across the web, and none of them fixes it consistently for Dragon.
The issue is that Chrome has a security feature which disallows any JavaScript that appears to do potentially malicious actions. Opening the file picker is one of the features gated by user activation. When trying to do that from the second time onwards, there is an error message in the browser console which says:
“File chooser dialog can only be shown with a user activation”
We asked DAC for their opinion on this, and they said that the majority of users wouldn't need to use the file upload more than once, so are not likely to notice that it won't work the second time.
And there is a work around to make it work the second time. When you say 'mouse click' (or any other command that interacts with the page) in between clicking on the file input button, it keeps on working.
I have added some of the solutions with technical details to this JSbin, including testable code.
There is another potential solution to add a role="button" to the <input type=file />. That makes the "click button" command work but not "click choose file". This is very likely to cause more issues with screen readers, though, and is therefore not something we will use.
But we could also create a browser extension to add it for Dragon users.


rendering flaws and fixes

@davidjamesbeck You offer a magnificent bugs report!

 1) the cells in the grid aren’t aligned (maybe the change to left-aligned cells I made to the CSS didn’t do it or wasn’t committed?)
Good point.   The css and javascript used in the rendering are now (but not for long) hosted by pshannon.net.  They seem to be out of date.   I will revisit them, include your left-alignment and then, given that they are both small, and because we want the downloaded html+sounds to be self-contained, needing no internet access, I propose to include them directly in the html file.  Same for the audio icon.  Your thoughts?
2) the colons in glosses get swapped out for hyphens (by the method that creates small caps?). We also should not have hyphens but n-dashes (–), it improves legibility (see the gloss of “smarrita” at the end)
When I hand-edited the inferno eaf file I used hyphens.  Shall we allow that, and then transform all hyphens in morpheme and morphemeGloss tiers into –?  I will add a (initially failing) test to test_MorphemeGloss.py to capture the colon -> hyphen bug.  Then fix.
3) Something happened to the “def” in the gloss of “la”
I'll look into that.
4) We should add single quotes around the glosses if the authors haven’t provided them in the ELAN file.
Should be easy to do this.

Good idea, the download should be as self-contained as possible, and the user needs to be able to customize it themselves.
Yes, we should transform all hyphens in both lines of the glosses. Something that goes with the colon problem, I notice that a hyphen was inserted after the nouns to introduce the gender markers (forest-fem) but there shouldn't have been a hyphen there in the input (since the word above isn't divided selv-a, which you can do in Italian but not, say, in French or German). This "fem" really should be subscripted to the word—in the old application, I just ignored things like that and had authors do it by hand because the input from ELAN was very idiosyncratic (I don't think .eaf supports that level of formatting). If we just put it in small caps, we have leave it to users to tweak manually in the HTML.

@davidjamesbeck Can I Tom Sawyer you into fixing these things?

the grammatical terms I used in the inferno demo
rendering all of them properly

This may be more approachable than you think.   Only two files are involved:

slexil/MorphemeGloss.py
slexil/tests/test_MorphemeGloss.py

I strongly and enthusiastically recommend a test-driven development strategy.  The idea is that, when you encounter a bug (as with the need to transform all hyphens into em-dash), you

write a test that demonstrates the bug, that is, a test which fails
fix the code so that the test passes
then run ALL  the tests to make sure that, in fixing the bug, you did not break something else

I'd be ever so grateful if you could take on this task!  If you can, that will free me up to get the downloads capability working - for the inferno demo data, and for the webpage.zip we create.

Hi, Paul
I will make a start on this. By way of learning git, I made some local changes and committed them to the repo—I added a reference to the IJAL styleguide for glossing to morphemeGloss.py (and corrected a typo or two) and uploaded a file “abbreviations.txt”. It is in the slexil directory for the moment, but probably should eventually live in the demo directory, no? All this seems to have been successful.
I will try to work on the rendering. It may come in dribs and drabs, but in principle doesn’t sound terribly challenging (famous last words),
David

On Feb 23, 2019, at 4:52 PM, Paul Shannon<EMAIL_ADDRESS>wrote:
@davidjamesbeck https://github.com/davidjamesbeck Can I Tom Sawyer you into fixing these things?
the grammatical terms I used in the inferno demo
rendering all of them properly
This may be more approachable than you think. Only two files are involved:
slexil/MorphemeGloss.py
slexil/tests/test_MorphemeGloss.py
I strongly and enthusiastically recommend a test-driven development https://en.wikipedia.org/wiki/Test-driven_development strategy. The idea is that, when you encounter a bug (as with the need to transform all hyphens into em-dash), you
write a test that demonstrates the bug, that is, a test which fails
fix the code so that the test passes
then run ALL the tests to make sure that, in fixing the bug, you did not break something else
I'd be ever so grateful if you could take on this task! If you can, that will free me up to get the downloads capability working - for the inferno demo data, and for the webpage.zip we create.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-466714073, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhkNhhizRAhuDSQtIJj9rA9ePhbJzks5vQdRNgaJpZM4a730Y.

we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
 <ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>

results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"

The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes.   Does the test also fail for you?

Yes, but I put this problem down to author error—you shouldn’t use straight apostrophes for punctuation since they are a common symbol (for ʔ) in practical orthographies. I didn’t want to correct for this in the method for adding quotes because of the risk of removing something that was intended as phonological notation. That was just Lokono, I didn’t notice problems with the other texts, did you?
Is there a good Pandas tutorial anywhere? I found a few online but didn’t find them especially helpful.
David

On Mar 4, 2019, at 7:50 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck https://github.com/davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
<ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>
results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"
The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes. Does the test also fail for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469279524, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhpvAbPTcosUWglq2PHoNwstUDGS9ks5vTTLAgaJpZM4a730Y.

Hi David,
Got it.  How about we test for bad input, and devise a way to handle it in a way users will appreciate?
Then detecting illegal input, as with the Lokono text, becomes part of our test suite.  We want all the tests to pass.
webapp.py now validates against the schema, and tries to handle failure with a little bit of grace.  If the user selects a .wav file rather than .eaf, then we can tell them.   Further validation, detecting illegal characters or a malformed tierGuie should be done also, and a warning given (rather than a crashed webapp.py!)
Thinking about this just now, I realize that schema validation, and any other validation we add, should be moved to the constructor (“init_”) of the Text class, in text.py.
Slexil uses pandas only for the DataFrame data structure it provides. It’s a dreadful, complicated hack, inspired by R’s data.frame but awkward to use.  I keep a list of “pandas dataframe tips” in my log file, for reference: I never remember the details from one session to the next.
Here are some tutorials:
https://towardsdatascience.com/pandas-dataframe-a-lightweight-intro-680e3a212b96
https://www.tutorialspoint.com/python_pandas/python_pandas_dataframe.htm
https://mode.com/python-tutorial/pandas-dataframe/

Paul

On Mar 4, 2019, at 7:16 AM, David Beck<EMAIL_ADDRESS>wrote:
Yes, but I put this problem down to author error—you shouldn’t use straight apostrophes for punctuation since they are a common symbol (for ʔ) in practical orthographies. I didn’t want to correct for this in the method for adding quotes because of the risk of removing something that was intended as phonological notation. That was just Lokono, I didn’t notice problems with the other texts, did you?
Is there a good Pandas tutorial anywhere? I found a few online but didn’t find them especially helpful.
David

On Mar 4, 2019, at 7:50 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck https://github.com/davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
<ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>
results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"
The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes. Does the test also fail for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469279524, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhpvAbPTcosUWglq2PHoNwstUDGS9ks5vTTLAgaJpZM4a730Y.

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

Hi, Paul
We can incrementally add test for certain kinds of bad input, though the possibilities are endless … . I too am all for not making anything like the straight apostrophe a fatal error, since the workflow will almost certainly involve checking the HTML output, tweaking the EAF, and generating a new page. But warnings will give users a head’s up about things to tweak.
So you wouldn’t recommend Pandas as a general way of dealing with table-like data? If not, I won’t bother (especially if you aren’t bothered by the try: —except techniques). But I do use tables for other projects, so if Pandas offers advantages I might be interested in learning about it. Though my first impression is that it is kind of awkward and not that transparent.
David

On Mar 4, 2019, at 8:39 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
Hi David,
Got it. How about we test for bad input, and devise a way to handle it in a way users will appreciate?
Then detecting illegal input, as with the Lokono text, becomes part of our test suite. We want all the tests to pass.
webapp.py now validates against the schema, and tries to handle failure with a little bit of grace. If the user selects a .wav file rather than .eaf, then we can tell them. Further validation, detecting illegal characters or a malformed tierGuie should be done also, and a warning given (rather than a crashed webapp.py!)
Thinking about this just now, I realize that schema validation, and any other validation we add, should be moved to the constructor (“init_”) of the Text class, in text.py.
Slexil uses pandas only for the DataFrame data structure it provides. It’s a dreadful, complicated hack, inspired by R’s data.frame but awkward to use. I keep a list of “pandas dataframe tips” in my log file, for reference: I never remember the details from one session to the next.
Here are some tutorials:
https://towardsdatascience.com/pandas-dataframe-a-lightweight-intro-680e3a212b96
https://www.tutorialspoint.com/python_pandas/python_pandas_dataframe.htm
https://mode.com/python-tutorial/pandas-dataframe/

Paul

On Mar 4, 2019, at 7:16 AM, David Beck<EMAIL_ADDRESS>wrote:
Yes, but I put this problem down to author error—you shouldn’t use straight apostrophes for punctuation since they are a common symbol (for ʔ) in practical orthographies. I didn’t want to correct for this in the method for adding quotes because of the risk of removing something that was intended as phonological notation. That was just Lokono, I didn’t notice problems with the other texts, did you?
Is there a good Pandas tutorial anywhere? I found a few online but didn’t find them especially helpful.
David

On Mar 4, 2019, at 7:50 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck https://github.com/davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
<ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>
results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"
The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes. Does the test also fail for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469279524, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhpvAbPTcosUWglq2PHoNwstUDGS9ks5vTTLAgaJpZM4a730Y.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469298333, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhv_XhRmU9Kf-5RoOktU-5WohF-_Vks5vTT4lgaJpZM4a730Y.

In python, alas, Pandas DataTable is the best we can do.
I am a little worried about the try/except approach to parsing.  It opens the door to “Ptolemaic programming” where we add special case code to accommodate edge cases.  Can we handle the 2, 5 and 6-line texts through the tierGuide?

On Mar 4, 2019, at 7:48 AM, David Beck<EMAIL_ADDRESS>wrote:
Hi, Paul
We can incrementally add test for certain kinds of bad input, though the possibilities are endless … . I too am all for not making anything like the straight apostrophe a fatal error, since the workflow will almost certainly involve checking the HTML output, tweaking the EAF, and generating a new page. But warnings will give users a head’s up about things to tweak.
So you wouldn’t recommend Pandas as a general way of dealing with table-like data? If not, I won’t bother (especially if you aren’t bothered by the try: —except techniques). But I do use tables for other projects, so if Pandas offers advantages I might be interested in learning about it. Though my first impression is that it is kind of awkward and not that transparent.
David

On Mar 4, 2019, at 8:39 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
Hi David,
Got it. How about we test for bad input, and devise a way to handle it in a way users will appreciate?
Then detecting illegal input, as with the Lokono text, becomes part of our test suite. We want all the tests to pass.
webapp.py now validates against the schema, and tries to handle failure with a little bit of grace. If the user selects a .wav file rather than .eaf, then we can tell them. Further validation, detecting illegal characters or a malformed tierGuie should be done also, and a warning given (rather than a crashed webapp.py!)
Thinking about this just now, I realize that schema validation, and any other validation we add, should be moved to the constructor (“init_”) of the Text class, in text.py.
Slexil uses pandas only for the DataFrame data structure it provides. It’s a dreadful, complicated hack, inspired by R’s data.frame but awkward to use. I keep a list of “pandas dataframe tips” in my log file, for reference: I never remember the details from one session to the next.
Here are some tutorials:
https://towardsdatascience.com/pandas-dataframe-a-lightweight-intro-680e3a212b96
https://www.tutorialspoint.com/python_pandas/python_pandas_dataframe.htm
https://mode.com/python-tutorial/pandas-dataframe/

Paul

On Mar 4, 2019, at 7:16 AM, David Beck<EMAIL_ADDRESS>wrote:
Yes, but I put this problem down to author error—you shouldn’t use straight apostrophes for punctuation since they are a common symbol (for ʔ) in practical orthographies. I didn’t want to correct for this in the method for adding quotes because of the risk of removing something that was intended as phonological notation. That was just Lokono, I didn’t notice problems with the other texts, did you?
Is there a good Pandas tutorial anywhere? I found a few online but didn’t find them especially helpful.
David

On Mar 4, 2019, at 7:50 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck https://github.com/davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
<ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>
results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"
The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes. Does the test also fail for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469279524, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhpvAbPTcosUWglq2PHoNwstUDGS9ks5vTTLAgaJpZM4a730Y.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469298333, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhv_XhRmU9Kf-5RoOktU-5WohF-_Vks5vTT4lgaJpZM4a730Y.

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

There are two places where I did try/except — one is in ijalLine.py.parse() where the method needs to determine if there is a second translation (translation2) or a second transcription (transcription2) category and, if so, need to set the values for self.transcription2 and self.translation2. I didn’t know how to ask if those categories existed in self.tbl without throwing an exception. I’m sure you know how to fix that.
The second place is text.py.getTierSummary(). Here, having a None value for the morpheme and morphemeGloss categories in the TierGuide threw an exception (that is, for the 2 line model—test_text_Chatino_2Line.py). That is probably solved by abandoning the requirement that the TierGuide always have those two categories. And, in fact, the need for them might just be because of the assertions in the test file (so might not be a problem with webapp.py). That was the first test I played with, before I really got the hang of the tests and I may not have clued in to what was going on. So, this too is probably a trivial fix.
David

On Mar 4, 2019, at 8:52 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
In python, alas, Pandas DataTable is the best we can do.
I am a little worried about the try/except approach to parsing. It opens the door to “Ptolemaic programming” where we add special case code to accommodate edge cases. Can we handle the 2, 5 and 6-line texts through the tierGuide?

On Mar 4, 2019, at 7:48 AM, David Beck<EMAIL_ADDRESS>wrote:
Hi, Paul
We can incrementally add test for certain kinds of bad input, though the possibilities are endless … . I too am all for not making anything like the straight apostrophe a fatal error, since the workflow will almost certainly involve checking the HTML output, tweaking the EAF, and generating a new page. But warnings will give users a head’s up about things to tweak.
So you wouldn’t recommend Pandas as a general way of dealing with table-like data? If not, I won’t bother (especially if you aren’t bothered by the try: —except techniques). But I do use tables for other projects, so if Pandas offers advantages I might be interested in learning about it. Though my first impression is that it is kind of awkward and not that transparent.
David

On Mar 4, 2019, at 8:39 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
Hi David,
Got it. How about we test for bad input, and devise a way to handle it in a way users will appreciate?
Then detecting illegal input, as with the Lokono text, becomes part of our test suite. We want all the tests to pass.
webapp.py now validates against the schema, and tries to handle failure with a little bit of grace. If the user selects a .wav file rather than .eaf, then we can tell them. Further validation, detecting illegal characters or a malformed tierGuie should be done also, and a warning given (rather than a crashed webapp.py!)
Thinking about this just now, I realize that schema validation, and any other validation we add, should be moved to the constructor (“init_”) of the Text class, in text.py.
Slexil uses pandas only for the DataFrame data structure it provides. It’s a dreadful, complicated hack, inspired by R’s data.frame but awkward to use. I keep a list of “pandas dataframe tips” in my log file, for reference: I never remember the details from one session to the next.
Here are some tutorials:
https://towardsdatascience.com/pandas-dataframe-a-lightweight-intro-680e3a212b96
https://www.tutorialspoint.com/python_pandas/python_pandas_dataframe.htm
https://mode.com/python-tutorial/pandas-dataframe/

Paul

On Mar 4, 2019, at 7:16 AM, David Beck<EMAIL_ADDRESS>wrote:
Yes, but I put this problem down to author error—you shouldn’t use straight apostrophes for punctuation since they are a common symbol (for ʔ) in practical orthographies. I didn’t want to correct for this in the method for adding quotes because of the risk of removing something that was intended as phonological notation. That was just Lokono, I didn’t notice problems with the other texts, did you?
Is there a good Pandas tutorial anywhere? I found a few online but didn’t find them especially helpful.
David

On Mar 4, 2019, at 7:50 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck https://github.com/davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
<ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>
results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"
The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes. Does the test also fail for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469279524, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhpvAbPTcosUWglq2PHoNwstUDGS9ks5vTTLAgaJpZM4a730Y.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469298333, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhv_XhRmU9Kf-5RoOktU-5WohF-_Vks5vTT4lgaJpZM4a730Y.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469303660, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhhG3i572dCwaqoUyrwnBoT50i8hsks5vTUFagaJpZM4a730Y.

Can we make the tierGuide the single place where per-text structure variety is captured?  That was what I have been trying to do.

On Mar 4, 2019, at 8:03 AM, David Beck<EMAIL_ADDRESS>wrote:
There are two places where I did try/except — one is in ijalLine.py.parse() where the method needs to determine if there is a second translation (translation2) or a second transcription (transcription2) category and, if so, need to set the values for self.transcription2 and self.translation2. I didn’t know how to ask if those categories existed in self.tbl without throwing an exception. I’m sure you know how to fix that.
The second place is text.py.getTierSummary(). Here, having a None value for the morpheme and morphemeGloss categories in the TierGuide threw an exception (that is, for the 2 line model—test_text_Chatino_2Line.py). That is probably solved by abandoning the requirement that the TierGuide always have those two categories. And, in fact, the need for them might just be because of the assertions in the test file (so might not be a problem with webapp.py). That was the first test I played with, before I really got the hang of the tests and I may not have clued in to what was going on. So, this too is probably a trivial fix.
David

On Mar 4, 2019, at 8:52 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
In python, alas, Pandas DataTable is the best we can do.
I am a little worried about the try/except approach to parsing. It opens the door to “Ptolemaic programming” where we add special case code to accommodate edge cases. Can we handle the 2, 5 and 6-line texts through the tierGuide?

On Mar 4, 2019, at 7:48 AM, David Beck<EMAIL_ADDRESS>wrote:
Hi, Paul
We can incrementally add test for certain kinds of bad input, though the possibilities are endless … . I too am all for not making anything like the straight apostrophe a fatal error, since the workflow will almost certainly involve checking the HTML output, tweaking the EAF, and generating a new page. But warnings will give users a head’s up about things to tweak.
So you wouldn’t recommend Pandas as a general way of dealing with table-like data? If not, I won’t bother (especially if you aren’t bothered by the try: —except techniques). But I do use tables for other projects, so if Pandas offers advantages I might be interested in learning about it. Though my first impression is that it is kind of awkward and not that transparent.
David

On Mar 4, 2019, at 8:39 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
Hi David,
Got it. How about we test for bad input, and devise a way to handle it in a way users will appreciate?
Then detecting illegal input, as with the Lokono text, becomes part of our test suite. We want all the tests to pass.
webapp.py now validates against the schema, and tries to handle failure with a little bit of grace. If the user selects a .wav file rather than .eaf, then we can tell them. Further validation, detecting illegal characters or a malformed tierGuie should be done also, and a warning given (rather than a crashed webapp.py!)
Thinking about this just now, I realize that schema validation, and any other validation we add, should be moved to the constructor (“init_”) of the Text class, in text.py.
Slexil uses pandas only for the DataFrame data structure it provides. It’s a dreadful, complicated hack, inspired by R’s data.frame but awkward to use. I keep a list of “pandas dataframe tips” in my log file, for reference: I never remember the details from one session to the next.
Here are some tutorials:
https://towardsdatascience.com/pandas-dataframe-a-lightweight-intro-680e3a212b96
https://www.tutorialspoint.com/python_pandas/python_pandas_dataframe.htm
https://mode.com/python-tutorial/pandas-dataframe/

Paul

On Mar 4, 2019, at 7:16 AM, David Beck<EMAIL_ADDRESS>wrote:
Yes, but I put this problem down to author error—you shouldn’t use straight apostrophes for punctuation since they are a common symbol (for ʔ) in practical orthographies. I didn’t want to correct for this in the method for adding quotes because of the risk of removing something that was intended as phonological notation. That was just Lokono, I didn’t notice problems with the other texts, did you?
Is there a good Pandas tutorial anywhere? I found a few online but didn’t find them especially helpful.
David

On Mar 4, 2019, at 7:50 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
we should add single quotes around the glosses if the authors have not provided them
Hi @davidjamesbeck https://github.com/davidjamesbeck
I just did a fresh pull and ran the tests.
test_Ijalline.py fails at line 85:
This line from the eaf
<ANNOTATION_VALUE>‘[a] child, a woman as well.'</ANNOTATION_VALUE>
results in this, as seen in the debugger
(Pdb) x3.getTranslation()
"‘[a] child, a woman as well.'’"
The problem seems to hinge on the different between a ‘ and a ' - that is, two kinds of single quotes. Does the test also fail for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469279524, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhpvAbPTcosUWglq2PHoNwstUDGS9ks5vTTLAgaJpZM4a730Y.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469298333, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhv_XhRmU9Kf-5RoOktU-5WohF-_Vks5vTT4lgaJpZM4a730Y.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/issues/4#issuecomment-469303660, or mute the thread https://github.com/notifications/unsubscribe-auth/ApvDhhG3i572dCwaqoUyrwnBoT50i8hsks5vTUFagaJpZM4a730Y.

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

That would work, though we will still need ijalLine.py to query the TierGuide (or the data frame built from TierGuide) as to what is and is not in the structure. So problem #1 is what it is and has to be fixed sooner or later.
I’m not sure about problem #2 (what happens with the null tiers). If we allowed for a TierGuide with only 3 lines (speech and translation, plus morphemePacking), then null tiers are a non-issue for the getTierSummary() method. Let me check to see why the null tiers are needed in the test files.
David

On Mar 4, 2019, at 9:15 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
t


Issue install R package xgboost in raspberry pi 3B+

I am trying to install the xgboost package for R in a raspberry pi 3B+ running on ubuntu 22.04. I was able to install the package from source, however, when I run the command library(xgboost) it seems is not available. I then read that I need to run the command R CMD INSTALL .. in the xgboost/R-package folder but couldn't install. I also tried the classic install.packages('xgboost') but it always get's stuck on the same line (see image). I thought it could be a problem with the RAM memory so I opened a 2GB extra swapfile but that didn't change anything. Thus, I would appreciate any help to solve the issue.
I only need it for loading models and predict, so there might be some work around if anyone comes up with.

It takes a while to compile the amagalmation file (amagalmation/xgboost-all.o). How long have you waited?

This is the method that I followed. In my original post I said I installed the package from source so I did this:
mkdir build
cd build
cmake .. -DR_LIB=ON
make -j$(nproc)
make install

which was successfully installed. Then I go to R and run "library(xgboost)" it does not find the library. Then I tried:
cd xgboost/R-package
R CMD INSTALL .

Maybe I did something wrong during the cmake installation and that is why is not detected but I can re-install it and send a screenshot so you can see if I followed the procedure properly.

Can you post the full log of the CMake installation?

Here it is:

You didn't run make install after make -j$(nproc)?

@hcho3 you are completely right. Now it's running perfectly. Sorry for the mistake. Thanks for the help!

Glad it worked!


Add custom ansi colors and CSS variables for them

Use our existing color palette to map to the 16 basic ansi colors. This is backwards-compatible because it aliases the existing color names.
Side note: I think the colors in console.css for console file rendering are incomplete, but fixing those is out of scope here imo.
Before and after:

Does it affect 256 and other colors?

No, only 16 colors. 256 colors still use inline style and I don't think ansi_up supports classes for those either.


Release 0.4.0

Release/publish a new latest version of tsp-typescript-client, using the newly added CI infrastructure.

The following 1 GitHub releases will be created once this pull request got merged.
Release v0.4.0 with changes since v0.0.0

Release v0.4.0 (Minor) 5c8dd33
Fix indentation in tsp-typescript-client/package.json 6b9950e
Run yarn upgrade 904d49b
Productify npm package, massage package and repo documentation ac17c6f
[ci] add infrastructure for automated publish of latest package 30aedb1
update to node 18 0b88769
Bump ip from 2.0.0 to 2.0.1 65505d5
Add CODE_OF_CONDUCT.md to the repository and update reference. b717d0d
Move rimraf dependency from prod to dev 15e47a8
Merge pull request #94 from eclipse-cdt-cloud/automated-pr-license-check 8af60e2
Add 3PP license check as part of PR CI b1c970e
Bump follow-redirects from 1.15.3 to 1.15.4 6621bc7
Bump axios from 1.5.0 to 1.6.1 54d71ef
Bump @babel/traverse from 7.22.20 to 7.23.2 252d22d
Update model for configuration source type parameters e23c508
Add support for configuration service end-points a5128df
Merge pull request #86 from eclipse-cdt-cloud/lerna-upgrade 5c2d465
[lerna] upgrade to recent version d646072
Make TspClient reuseable interface d8f8dcc
Bump word-wrap from 1.2.3 to 1.2.4 3279f64
Bump semver from 5.7.1 to 5.7.2 dc8cba0
releng: Include date in version string for next versions dc54697
Update ci-cd.yml 48d8efa
Use actions/setup-node@v3 instead of actions/setup-node@v1 289f26f
[lerna] option verifyAccess to false 64b90c9
Add data type DataType enum and usage in EntryHeader data structure 143a5ab
Add API for fetching Data Tree entries 9b23dfe
Bump http-cache-semantics from 4.1.0 to 4.1.1 43f2a05
Add XyEntry API to deserialize the XY specific attribute "isDefault" 30e85df
Upgrade to node 16.x for GitHub CI (publish) 97d6722
Upgrade to node 16.x for GitHub CI 7dcb90b
Bump json5 from 2.2.0 to 2.2.3 15acf80
Bump minimatch from 3.0.4 to 3.1.2 cb1db19
Bump decode-uri-component from 0.2.0 to 0.2.2 63d935d
Update package.json to cdt-cloud url/homepage 32fca72
Bump parse-url from 6.0.0 to 6.0.2 1cdb331
Add launch.json to debug test cases 7f692ba
Add unit test to test metadata in timegraph deserializer 46149eb
Add metadata to timegraph deserializer f4f132e
XY: Remove the unused commonXAxis from the model 5dd021b
XY: Add the series OutputElementStyle to the model 7cb768e
Replace theia-ide with eclipse-cdt-cloud references c1fe69d
Add support for requested_timerange in query parameters d59ed63
Add contribution documentation 49b55a7
Add Vulnerability Reporting Policy 425d9b8
Bump minimist from 1.2.5 to 1.2.6 04e64a4
Bump node-fetch from 2.6.6 to 2.6.7 622eb33
Update publish GitHub action to work with eclipse-cdt-cloud 3d74a4f
Add ConnectionStatusListener to RestClient eaf6511
Catch errors in RestClient c53f0da
Fix markdownlint in ./tsp-typescript-client README 1f03b97
Change XYSeries xValues to bigint array f487b14
Fix build errors 22bdc11
tslint: no-implicit-dependencies 4d094b0
depend on json-bigint from the right package 1ec950b
fix query string creation de3d2bc
Support BigInt values f3e197b
Avoid duplicates in requestedTimes array fa7ee18
Use lerna for managing the project and provide separate README for NPM 1d94efa
Serialize and deserialize timestamps as strings ee6165e
Documenting functions of rest-client's mock bf655d2
Expanding unit tests 58b8f5e
Bump ansi-regex from 5.0.0 to 5.0.1 6e3edcf
Bump tmpl from 1.0.4 to 1.0.5 b9aa47e
v0.3.0 25a45e7
jest.config.json: Apply default VS Code formatting 33d243c
RestClient: Fix minor use{d} verb tense typo(s) 7e58fa8
Start adding tests to project f02a98b
Entry model: Fix typo in style-related jsdoc 691c99f
XY model: Fix language typos in heading comments a22a896
Bump path-parse from 1.0.6 to 1.0.7 6934479
README: Fix the minor VS Code markdownlint issues a067d0c
JSON files: Apply standard default VS Code format 23350c4
TSLint: Fix unpermitted comments in VS Code's json ed221f2
Standardize the .gitignore file format and sort it 4fa4697
Add support for marker sets a8f4d3d
Change tooltip request to a POST 4122c7b
Add prepare script for installing directly from github 4323bb7
Change fetchTimeGraphArrows to return an array of TimeGraphArrow b2470f2
Merge pull request #17 from tahini/health 5f4f154
Add src directory when publishing to npm 799187d
Align table query parameters with Trace Server Protocol c51bd05
Implement the health check service of the TSP f9e9df7
Support unsuccessful request responses 2c0c62f
Update yarn.lock to bump minimist 0.0.8 to 1.2.5 for security fix 0b60632
Only publish when pushing on master of theia-ide/tsp-typescript-client e2c202a
Skip git commit and tag when publishing to NPM 6d2544d
Fix pre-publish build in ci-cd.yml workflow fa0a538
Fix syntax in build workflow yml file ca3a8ef
Use github workflow for CI/CD a6237ff
Update README.md fd4dd9c
Merge pull request #7 from PatrickTasse/master 8b58e1b
Add annotation model and tsp-client API for fetching annotations c34a2a2
Merge pull request #4 from tahini/align_tsp 339f1e7
tsconfig: Remove the composite:true 5993f70
align with the TSP for the table endpoint 368ec69
Align client classes with the TSP specification 0e496b1
Merge pull request #5 from theia-ide/dependabot/npm_and_yarn/node-fetch-2.6.1 1a3b29c
Bump node-fetch from 2.5.0 to 2.6.1 6d6f7b7
Add the ability to fetch styles from a trace server 85560d3
Change parameter keys again and clean-up comments 5ac4367
Update query helper to match the key name in the TSP 005121b
Fix wrong parameter handling for GET and DELETE 9136e05
Fix fetch*Tooltip to correctly build the URL 61ec32b
Update travis config for "next" publish 4da108d
Minor fixes in the models + travis config f521cc2
Change license to MIT 2e1b099
Fix and improve the tsp-client d9a002b
Update the responses handling e51d3fc
Small tweak to the tsp client and packaging 006d5e9
Fix dependency issue for node-fetch 55940d3
Add Query class for basic request 6a3627b
Experiment packaging stuff c32e450
Small fixes in various responses 724ad32
Draft for packaging 7cdac29

Thanks for the review!


test: Collect logs from init containers

If pods are failing to start and stay stuck in e.g. Init:CrashLoopBackOff, it will be useful to have the init containers' logs to investigate further.

/test

/test


Repeat "var" per declaration, and sort alphabetically or by length?

I typically sort by length, but here @chasenlehara suggests sorting var statements alphabetically:
https://github.com/bit-docs/bit-docs-tag-demo/pull/9#discussion_r114059172
I agree that repeating var for definitions aids in scanning, and I would go further to the extent that it can even be useful for declarations that don't set a value.
For example:
https://github.com/bit-docs/bit-docs-tag-demo/blob/c1224ca5ebe35be8b52be7fbedea3f9fcc62d4de/test.js#L130-L131
Is easier to scan than:
https://github.com/bit-docs/bit-docs-tag-demo/blob/00d53adf944af2ca113c7ba5c6b93da73b5b780e/test.js#L130

For single-character var declarations like in the example here:
http://eslint.org/docs/rules/sort-vars
I my opinion changes about using a separate var for each one, since they're a single character.

The reason I like sorting by length is because it's obvious when a later declaration depends on a former.
For (convoluted) example:
var path = require('path');
var zombieString = 'zombie';
var express = require('express');
var myHeadlessBrowser = zombieString + '-mine';
var Browser = require(myHeadlessBrowser);
var generate = require('bit-docs-generate-html/generate');

It's obvious that myHeadlessBrowser is used later, and this usually works out quite nicely.
Not sure if ESLint has a plugin that is capable of understanding sorting like this however.

There is a different rule that disallows single character variables, btw.

With regards to the sort-var rule. I don't personally feel like there is a huge need to be that nitty gritty, and people can make their own choices.
It doesn't really provide anything tremendously helpful in terms of readability and in some cases can be a hinderance. Specifically with sorting alphabetically, if we were talking about CSS, that would be a different story, because there are pre-defined styles to go by. In JS there's too much variable, not to mention that we should be encouraging people to use const first, then let if they need to mutate the variable (and never use var).
Sorting by length just feels like a recipe for making needlessly long variable names and can be a slippery slope.
The nice thing here is that sort-var is turned off, so you can do what you feel is best. :-)


Chart not display as full chart [multi tab]

Chart display as cluster when the position change
I try to do many ways and I found,  if chart stay in the same position and  I'm not using multi tab  it will display generally while when I use multi tab it's not display as full chart
ref: https://www.w3schools.com/howto/tryit.asp?filename=tryhow_js_tabs_close
I used this multi tab and I have nearly 10 tab and I have chart in each tab

I had a similar issue, I just set the svg width to 100%, then each time you switch tabs call call your chart.update, that should fix it.

I'm having the same problem. The charts only get the proper size when I resize the browser's windows. Could you fix this issue? I have already set the width to 100%, but it doesn't work yet. This is my code:
<ChartistGraph
                    data = {this.state.sixMonths.data}
                    type="Line"
                    options = {
                      {
                        low: this.state.sixMonths.min,
                        showArea: false,
                        width: '100%',
                        height: '50%',
                        axisX: {
                          showGrid: false,
                          showLabel: true,
                        },
                        lineSmooth: true,
                        showLine: true,
                        showPoint: false,
                      }}
                    />

I have also used the fullWidth: true option, and put
svg {
  width: 100% !important
}

in my css file.
Any clue?

I'm having the same problem. The charts only get the proper size when I resize the browser's windows. Could you fix this issue? I have already set the width to 100%, but it doesn't work yet. This is my code:
<ChartistGraph
                    data = {this.state.sixMonths.data}
                    type="Line"
                    options = {
                      {
                        low: this.state.sixMonths.min,
                        showArea: false,
                        width: '100%',
                        height: '50%',
                        axisX: {
                          showGrid: false,
                          showLabel: true,
                        },
                        lineSmooth: true,
                        showLine: true,
                        showPoint: false,
                      }}
                    />

I have also used the fullWidth: true option, and put
svg {
  width: 100% !important
}

in my css file.
Any clue?

I have the same problem. I set the chart to 100% width but it only happens when I resize the window.

Thanks to @gionkunz  I solved updating chart when selected tab change (I was on Angular 9).
Look here: #119


Bypass cloudflare anti-bot page

This is what I get when trying to capture a page from an Amazon EC2 instance. I routed my web traffic using SOCKS Tunnel with SSH and tried to access to archive.is then I got something like this. As requests library isn't able to solve cloudflare javascript challenge I added an alternative to it, cfscrape, which works the same way as requests library does but is able to solve those js challenges along with nodejs.


Radio Button Filter

I have a user request for a radio button for yes and no values. Will this be a filter type option available in the future?

Since there is a decent amount of open issues right now I don't think that this one will be added soon, but you are welcome to send a pull request for it :) But hey who knows it can happen sooner...

Any update on this ?

this might be helpful https://github.com/vedmack/yadcf/issues/289#issuecomment-185948373

Despite the fact that it could be a nice addition to yadcf it wont be implemented (luck of interest from the community / no time)


model invisible。In columbus mode，model is invisible。

Sandcastle example:

https://sandcastle.cesium.com/index.html#c=tVbbbts4EP2VqZ9kwEvZubSo1wma2Ei32E37EKdYoCoKRhrFRCjSIKlctui/75CUHMV2H4zAARyQQ/LMOcMRZ3KtrIN7gQ9o4AQUPsAUragr9jXYkqyXh/lUK8eFQpP1BvAzUwBClfpcP46h5NLiwJssSsyd0OqTKkTOnTYvVhe80A92DM7UrUXXsjhTouIOu/YcFV7qgmyjYEjTYDqcfVHyqcHM1K/+n5nKVFmr4BRyg4Tjz8mkNnIACxS3C9ePfKNIFoDY0ohKOHGPlhms9D2eSZlEOIA8BGWprQiwJ21Iptw4GnF1yEqjqxneGkSb+CMAf4wODtnw3dHR29H7QTQdHbHh8fDw3fBtY4h8/Ni7IkrcQOXpXnJnxOOzp7nhypbaVJYht+6zNm5xvZzrC/GIxYXhFSYtvTUkwvidUF4USYMfYhREfJSuTH5GegAUNRj7/4PW0qU37s5WO2zOJdLawSBG71e/oRRp5ETWcGbR+Yx6dlWgdUJxL2G8ivUgAoTzdL8eMF6GXvplS+q++bUGxeGjG0PWOxMmN7x0lJtxgbaGVKRUaZMj6cPKdzdRWhs57DGWXvFqKXHGHU+DWJvGkJGLZvSDhuxW3qyc+b/j4XDIhu08CiAlUc9gC+WZ0Qr3yDfgd8cblEfHuzH+aHStCviKC5HL/VCPLhoPL2cb9Heh/pd2QLcG51xKrdUew954eDnbDP2u2XIp5B3MTZ3f7ZG7dxJ8rM9fFfurO6EUFjBdcMNzFwrI3hTwNvI/aPgq2tdKCgdU3/ZCl3CDg9WAuLpyLUd2fE94rmGqq6VBaynegcleyAdXz562ZMualF10/D3/96ArY8dPVpSQvGmK3AVpqg3O0MWmhNl6uaRKas+5FTbplsl+BwLgQShqVBiVNeM64fABmS+EhRtDbQz1S4VGC4relgYYAjBcKyq3xnJJjcRKh9dHZGzWewZsw0GheP2T4wO3aXn90/OJyi9Xub+K/X0MKycvJls+iuPfM/8eurcrroqcWiaqGNTvzLWWN9xcoqqTpoXwB3uDXtZrmoz4A5hY9yTxtMX/IKpwpdQLJcTaIbEmSTa9oRRHx3JrWwqTtHt0Uoh7EMXJlsYZcsmtpZWylvJK/EdF9HSS0v6No1LzQqjbL5RHkj/5bYvR6T/RyBibpDTdftJFxWvI/wM
Browser:
Chrome 108.0.5359.94
Operating System:
windows
My solution
set minimumPixelSize: 1

Hi @lewhonly, thanks for the report. I modified the Sandcastle a bit so you can see that the model loads in and is briefly shown, then disappears. It also seems to happen inconsistently when choosing models from the drop down list.
@ptrgags or @lilleyse Any idea what may be going on here?

Yeah, it is strange that some models work and others don't.
Might be worth checking 1.96 or earlier to see if this is a regression with the new Model.js. @j9liu would you have a chance to look at this?

@lilleyse This does seem to be a regression with the new Model.js; I tested in 1.96 and Model works while ModelExperimental. I'll take a closer look soon.

Thanks! It works well.


Add Red Green Boundary.

Add Red & Green Boundaries at two sides.

Done. Added 3 sides white and one side green as per the new IARC rules.


Fix project dependencies so it could be cloned and built locally

The current dependencies seem broken. Once cloned to local, it fails to yarn install due to dependencies build errors.
Below are the errors from yarn install
➤ YN0009: │ msgpackr-extract@npm:1.0.15 couldn't be built successfully (exit code 1, logs can be found here: C:\Users\longh\AppData\Local\Temp\xfs-41b8c800\build.log)
➤ YN0009: │ lmdb-store@npm:1.6.13 couldn't be built successfully (exit code 1, logs can be found here: C:\Users\longh\AppData\Local\Temp\xfs-7d83501c\build.log)
The major error from build log is:
\logseq-inbox-telegram-plugin\node_modules\nan\nan_callbacks.h(55,23): error C2039: 'AccessorSignature': is not a member of 'v8' [\logseq-inbox-telegram-plugin\node_modules\lmdb-store\build\lmdb.vcxproj]
Based on nan_callbacks.h:55:23: error: ‘AccessorSignature’ is not a member of ‘v8’ #942, packages are updated to fix this error.
It also add .yarnrc.yml and .yarn/ to .gitignore

It's strange, but I have no errors. How can I reproduce this problem?

Clone the repository
Execute yarn install
Is it right?

It's strange, but I have no errors. How can I reproduce this problem?

Clone the repository
Execute yarn install
Is it right?

Yes. My dev environment is new, since I just installed the node and other tools before I cloned this repository.

What node version do you use?

It forces me to install Buffer.
@parcel/resolver-default: Auto installing polyfill for Node builtin module "buffer"...
/Users/shady/Documents/repos/logseq-inbox-telegram-plugin/node_modules/axios/lib/helpers/toFormData.js:128:74
127 |     if (utils.isArrayBuffer(value) || utils.isTypedArray(value)) {

128 |       return useBlob && typeof Blob === 'function' ? new Blob([value]) : Buffer.from(value);
|                                                                          ^^^^^^ used here
129 |     }
130 |

📝 Learn more: https://parceljs.org/features/node-emulation/#polyfilling-%26-excluding-builtin-node-modules
Installing buffer...
"devDependencies": {
"buffer": "^5.5.0",
"parcel": "^2.8.3"
},

It forces me to install Buffer.
@parcel/resolver-default: Auto installing polyfill for Node builtin module "buffer"...
/Users/shady/Documents/repos/logseq-inbox-telegram-plugin/node_modules/axios/lib/helpers/toFormData.js:128:74 127 | if (utils.isArrayBuffer(value) || utils.isTypedArray(value)) {

128 |       return useBlob && typeof Blob === 'function' ? new Blob([value]) : Buffer.from(value);
|                                                                          ^^^^^^ used here
129 |     }
130 |

📝 Learn more: https://parceljs.org/features/node-emulation/#polyfilling-%26-excluding-builtin-node-modules
Installing buffer...
"devDependencies": { "buffer": "^5.5.0", "parcel": "^2.8.3" },

it does the same thing for mine when i continued to update the code. do you know whether we should update that and others?


Coalesce fields in 'else if' clause

i.e. the if keyword and the condition should be a single field, with a single sequence node, that gives a suitable prompt and syntax completion.

Note to self: started on this in a new branch.


chore(pydantic) bump to pydantic 2

In our project we can't use pydantic 2 (reportedly 5-50 x faster than pydantic 1, as it was rewritten using rust), given that we use Langchain and it uses pydantic 1.
on Langchain, removing then adding pydantic using poetry:
Because langchainplus-sdk (0.0.20) depends on pydantic (>=1,<2)
 and no versions of langchainplus-sdk match >0.0.20,<0.0.21, langchainplus-sdk (>=0.0.20,<0.0.21) requires pydantic (>=1,<2).
So, because langchain depends on both langchainplus-sdk (^0.0.20) and pydantic (^2.0.2), version solving failed.

changes code using bump-pydantic, as recommended by the documentation
manually created default factories in the client as env= is no longer used
Please let me know if this seems ok.

Thank you for the PR! We are looking into the migration. Since langchain currently depends on this, we will likely first have to support both 1 and 2 to remain backwards compatible with peoples workloads

Langchain also depends on openapi-schema-pydantic which depends on a pydantic 1.9, which has a vulnerability. However, that project is no longer maintained. I've put some suggestions for how to address this in this issue.

I will be closing this for now to keep the repo clean.

We're planning to rm the openapi-schema-pydantic dep in langchain and do some more cleanup. Thanks everyone for your patience.


console error "You cant cut polygons with self-intersections" when cutting LineString

hi, this library rocks! hats off! thank you very much for your effort you put into this!
I noticed console error
You cant cut polygons with self-intersections

when you have a FeaturCollection with more than 1 LineString (one of them containing a self-intersection) and when you cut one of them.
the original FeatureCollection containing 2 LineStrings (one of them with a self-intersection):

{
    "type": "FeatureCollection",
    "features": [{
        "type": "Feature",
        "properties": {
            "shape": "Line",
            "name": "Unnamed Layer",
            "category": "default"
        },
        "geometry": {
            "type": "LineString",
            "coordinates": [
                [-74.011457, 40.713533],
                [-73.999996, 40.708816],
                [-74.008624, 40.707417],
                [-74.007722, 40.714476]
            ]
        },
        "id": "d6196156-259b-448f-a7ff-33ac94eebe93"
    }, {
        "type": "Feature",
        "properties": {
            "shape": "Line",
            "name": "Unnamed Layer",
            "category": "default"
        },
        "geometry": {
            "type": "LineString",
            "coordinates": [
                [-74.006477, 40.718412],
                [-73.9936, 40.712947]
            ]
        },
        "id": "2469b736-d97a-4985-9eff-4a97507270c4"
    }]
}

when you cut the "straight" LineString the error appears in the console.
the result is correct when using https://geoman.io/geojson-editor
{
    "type": "FeatureCollection",
    "features": [{
        "type": "Feature",
        "properties": {
            "shape": "Line",
            "name": "Unnamed Layer",
            "category": "default"
        },
        "geometry": {
            "type": "LineString",
            "coordinates": [
                [-74.011457, 40.713533],
                [-73.999996, 40.708816],
                [-74.008624, 40.707417],
                [-74.007722, 40.714476]
            ]
        },
        "id": "d6196156-259b-448f-a7ff-33ac94eebe93"
    }, {
        "type": "Feature",
        "properties": {
            "name": "Unnamed Layer",
            "category": "default"
        },
        "geometry": {
            "type": "LineString",
            "coordinates": [
                [-74.006477, 40.718412],
                [-74.000252, 40.71577]
            ]
        },
        "bbox": [-74.006477, 40.71397865883764, -74.00025214620568, 40.72020351263196],
        "id": "c33f1c14-941a-4b94-b959-fe71427e2c82"
    }, {
        "type": "Feature",
        "properties": {
            "name": "Unnamed Layer",
            "category": "default"
        },
        "geometry": {
            "type": "LineString",
            "coordinates": [
                [-74.000252, 40.71577],
                [-73.9936, 40.712947]
            ]
        },
        "bbox": [-74.00025214620568, 40.71103251263196, -73.9936, 40.71768465883764],
        "id": "501cb7ce-a29f-4515-9cf0-c7ad61de4d7c"
    }]
}

note: in the app where I am using your library I am running into the following error which might be a consequence of this issue (but could also be totally unrelated).
leaflet-geoman.min.js:1 Uncaught TypeError: Cannot read property 'enable' of undefined
    at leaflet-geoman.min.js:1
    at Array.forEach (<anonymous>)
    at NewClass.cut (leaflet-geoman.min.js:1)
    at NewClass._finishShape (leaflet-geoman.min.js:1)
    at NewClass.fire (leaflet-src.js:588)
    at NewClass._fireDOMEvent (leaflet-src.js:4403)
    at NewClass._handleDOMEvent (leaflet-src.js:4360)
    at HTMLDivElement.handler (leaflet-src.js:2669)

@udos thanks for reporting. I have fixed it and it will be in the next release


_initTrialLog could be a function in experiments.py

and have as input arguments the headers of the columns that are required in the logs.

and another input could be the name of the results folder.

Fixed it


Friends list search does not return correct party information for users

It shows that users only have 1/3 users in their party even if that's not the case.

Fixed in #183


Fix code includes style

Currently this is inheriting a lot of rules from wyrm that dont apply here.
To fix this some wyrm rules are manually overriden or copied.
With all the fixes made in the theme or work around wyrm issues we will want to carefully see what can be removed when we move to bootstrap.
Fixes #930

This currently breaks api docs


NO LICENSE ?

We'd like to import Exel2Html to our projects, so need to clarify the LICENSE.
What's your plan ?

Thank you for your request.
I'll consider a license
of the Excel2Html. Give me some time, please.

Added LICENSE.txt. We determined to use the MIT license.
Check for 93088e682060ed72c647ad62835afdc232e66ee1.


Bump Python Version

Pull Request
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

#187  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 9, 3:30 PM EDT: A user merged this pull request with Graphite.


[berkeley] Use Proof_cache for Test_zkapp_update tests

This PR builds upon https://github.com/MinaProtocol/mina/pull/14030, using the proof cache introduced there to skip the proof generation step on the kimchi side.
Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me

Inlining the proofs into the test files makes them hard to work with. I would really like to see these proofs in separate files that we load inside of the tests. In fact, with the way git works, it would be best to have those files contain compact JSON rather than pretty printed JSON so that every change to those files doesn't incur storing a diff of 60k+ lines of code. We may even want to mark such proof files for storage in LFS, which we can do by giving these files a custom extension (like .proof) and configuring the .gitattributes accordingly.

Inlining the proofs into the test files makes them hard to work with. I would really like to see these proofs in separate files that we load inside of the tests. In fact, with the way git works, it would be best to have those files contain compact JSON rather than pretty printed JSON so that every change to those files doesn't incur storing a diff of 60k+ lines of code. We may even want to mark such proof files for storage in LFS, which we can do by giving these files a custom extension (like .proof) and configuring the .gitattributes accordingly.

We may even want to mark such proof files for storage in LFS

Didn't we stop using LFS because the repo hit the quota and broke things?

I would really like to see these proofs in separate files that we load inside of the tests.

Will do :+1:

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!approved-for-mainnet


fix(app): switched npm token for release job

Signed-off-by: Anton Biriukov<EMAIL_ADDRESS>

Codecov Report
Patch and project coverage have no change.

Comparison is base (3e07c60) 89.73% compared to head (a70d74a) 89.73%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #620   +/-   ##
=======================================
  Coverage   89.73%   89.73%
=======================================
  Files         102      102
  Lines        4014     4014
=======================================
  Hits         3602     3602
  Misses        274      274
  Partials      138      138

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


Are Plus_Ultra weights pointing at Base weights???

The Base weights as seen in Remover.py can be found at this url:
https://drive.google.com/file/d/13oBl5MTVcWER3YU4fSxW3ATlVfueFQPY/view?usp=share_link
Plus_Ultra can be downloaded at the Model Zoo link provided in the repo (https://github.com/plemeri/InSPyReNet/blob/main/docs/model_zoo.md)
However, the Plus_Ultra link is pointing here -- which is the same link as Base:
https://drive.google.com/file/d/13oBl5MTVcWER3YU4fSxW3ATlVfueFQPY/view
Is this an error? Thanks.

Hi, there's an issue related to the url in the original repository plemeri/InSPyReNet#24. I'm trying to fix this issue.
Thank you.

We fixed the issue related to the url. Also, sorry for the late response but this repository is for general purpose, not for the academic evaluation, and for the best performance for the real-world scenarios, we use the checkpoint trained with all SOD datasets which are available in public.
Long story short, Base pointing Plus_Ultra is not an error, we intended to do so.
Thank you.


HB120rs_v2 nvme disks are not mounted?

Compute node image is OpenLogic:CentOS-HPC:7_9-gen2:latest
HB120rs_v2 compute nodes do not mount the local NVMe SSD's
[garvct@ip-0A001005 ~]$ df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 225G     0  225G   0% /dev
tmpfs                    225G     0  225G   0% /dev/shm
tmpfs                    225G   25M  225G   1% /run
tmpfs                    225G     0  225G   0% /sys/fs/cgroup
/dev/sda2                 30G   20G   10G  66% /
/dev/sda1                494M  166M  329M  34% /boot
/dev/sda15               495M   12M  484M   3% /boot/efi
/dev/sdb1                473G   73M  449G   1% /mnt/resource
<IP_ADDRESS>:/home-nxkogxwk  4.0T     0  4.0T   0% /anfhome

Duplicate of #371


Add introductory text on namespaces

This PR was from my mastre branch, and I have now also added some build scaffolding for examples. Basically, now you can stand in the root and issue "make examples" - causing all (for now, we only have 1) examples to be built. I want to use this with travis-ci for building all examples on push.
I'm using GNU Make here, just because it's simple and we don't want to do any magical stuff (yet, anyway..). It does the trick. If we're OK with GNU Make, I don't think this new part of the PR should be anything controversial.

I'm going to merge this, so I can try out building it with travis-ci. If we decide we don't like the contents of these commits, I think we can clean that up later.