shape mismatch

When I am trying to train, I get the following error:

2018-07-15 22:31:21.210544: W tensorflow/core/framework/op_kernel.cc:1192] Invalid argument: Input to reshape is a tensor with 750000 values, but the requested shape has 187500
[[Node: annotation_reshape = Reshape[T=DT_UINT8, Tshape=DT_INT32](DecodeRaw_1, annotation_reshape/shape)]]

This seems to be related to the shape in tfrecord file. I used the code provided in the repository to create those files. Should I update them?

Hi, first thanks for sharing this works!
I have exactly the same problem. I wanted to train DeepLab , on the Ade20k dataset, I used the notebook provide to prepare the tfrecords. Is there any resize operation, or it's may be a cropsize problem?
Thanks for the answers!

Make sure you create the tfrecords in the correct way. The only thing I can say is that you are trying to reshape a tensor to the wrong shape.


how to execute the trajectory generated on a real robot

I am trying to run arm_to_cart_pose.py on real robot . How can I achieve it ?

You just simply replay the found trajectories on your robot.

I was able to visualize or replay on RViz, but on real robot I am unable to visualize as the generated trajectory dosen't contain accelerations and velocities . Kindly let me know  how to generate velocities and acceleration.


implement #249

this implements #249
@Ulexus @leseb

This appears to be half of #249, yes?  This does not incorporate the KV part.

ah, yes, working ...

@Ulexus @leseb what do you think about the following scenario?
In the beginning, admin generates keyrings and conf, put them into KV store, and ceph-docker gets from KV store and write to the host.
Later admin updates the config and keyrings in the KV store, should ceph-docker overwrite (current behavior) or keep the existing config?

@Ulexus @leseb this fix works for static config. can we merge this part first and discuss KV at a separate issue? Thanks.

I agree.  Thanks @rootfs


Google Auth - "Read from file" for "Service Account Credentials" inserts text into incorrect input field

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

On latest master, go to Security --> Authentication --> Google Auth
Click on "Read from file" for "Service Account Credentials"

Expected Result:
"Read from file" for "Service Account Credentials" should insert the file contents into "Service Account Credentials" input field.
Actual Result:
"Read from file" for "Service Account Credentials" inserts the file contents into "OAuth Credentials" input field.

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master head - latest - commit id: e8fbc0c84
Installation option (single install/HA): single

A fix was made in this PR already.
https://github.com/rancher/ui/pull/3732

Verified on latest master-head - commit id: f01cca783 ui tag: latest2

Navigate to Security --> Authentication --> Google Auth
Click on "Read from file" for "Service Account Credentials"
"Read from file" for "Service Account Credentials" inserts the file contents into "Service Account Credentials" input field.


Test Galata bot

Please update galata references

https://github.com/bqplot/bqplot/actions/runs/1788377770

Still not right


Separate ListPackages, PackageTree into subpackage

The primary gps package is becoming somewhat unwieldy, so it's worth starting to separate out logic dealing with discrete subsystems into their own subpackages. Unfortunately, a lot of gps' systems are deeply interwoven, so this isn't easy to do in a lot of areas.
One exception, though, is the family of functions around PackageTree - they're quite well self-contained. They're also growing, and are likely to continue to grow as we refine that subsystem. So, they're a good first candidate for separation into a subpackage.

Oh, this is all done. Thanks, @narqo!

(☞ﾟヮﾟ)☞


Bug in differences()

I believe there is a bug in differences. I tested the function with the following input data matrix:
5         1          22
6         2          21
7.5      4          19
6.5      8          16
4.5      13        11
6.6      7          3
calling differences(1) on this gives an output of 4 lines, rather than 5, and the difference of the two most recent observations is missing. Here is the output:
1         1          -1
1.5      2          -2
-1        4          -3
-2        5          -5
These values are correct, but I would also expect to see, as the last line:
2.1      -6        -8
Please confirm that this is indeed a bug.

great, the spacing in my matrix examples was collapsed to 1 space each... hopefully it's still readable...

Please ignore, this was user error... I had an error in my datetime index, which caused the truncation to 4 observations.


Enable custom tracing of TaskId based on Tag

What is this PR?
This PR adds a new field to Config: task_id_and_tag_to_string: Option<fn(TaskId, Tag) -> String>. If this field is set, then we will override Debug for TaskId to get the Tag associated with the TaskId, and then format the result of calling the closure with the TaskId and the Tag.
The motivation behind this change is to enable more meaningful traces and panics when using Tags. For instance, before this change, you might see something like:
2023-05-30T15:33:28.688495Z TRACE execution{i=9}:step{i=4 task=3}:outer{tid=2}: shuttle::runtime::execution: runnable=[TaskId(1), TaskId(2), TaskId(3)] next_task=Some(TaskId(2))

And after this change you could have it say something along the lines of:
2023-05-30T15:33:28.688495Z TRACE execution{i=9}:step{i=4 task=3}:outer{tid=2}: shuttle::runtime::execution: runnable=[MAIN_TASK, BACKGROUND_TASK, UNTAGGED_TASK] next_task=BACKGROUND_TASK

You can also see the provided test for an example of how to use this.
Alternative designs
For the field in the Config:
This has to be a closure to enable the use case where Tags are dynamically generated (if not, then one could just provide a HashMap and look up into that). There is a case to be made for having it return something which implements Debug, as that would result in a bit less code + allows the user to be a bit more lazy when making the closure.
For the design over all:
There exists an alternative design proposal here: https://github.com/awslabs/shuttle/pull/110.

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

I think maybe a better approach here is to make a Tag trait, store the tag as Box<dyn Tag> (or maybe Option it to avoid allocating in code that isn't using tags at all), and change the interface to be set_tag_for_current_task(tag: impl Tag). Then either require Tag to implement ToString or Display, or give it its own task_description(&self) -> String method, and use that when printing the task. The get_tag_for_current_task function would return Box<dyn Tag>, and presumably the caller knows what type it's using for tags so it can downcast to the concrete type.

Hmm, perhaps. I'm not sure I see the advantages of that approach. It would still requiring indexing from TaskId to Tag, and would also require the same boilerplate as found here: https://github.com/awslabs/shuttle/pull/110/commits/b782a0ebfd6248d235794f34740f1e113a53e011#diff-57b359b6ae887394c7aa7909db3f621ecb55f4eb1e92015354fe0977a78ea0d1R635-R708 + changes to all of the callsites (trace! + panic!).

Updated to the scheme proposed by James.
The change resulted in a slight change of output in that we will print using TaskId during setup (as in before the closure passed to check starts running). This can of course be solved, but I don't think it is an issue worth solving.
A potential improvement which can be made (regardless of scheme) is to enable setting the tag of a spawned task without having to get it from the parent. Currently we both have a race condition on reading the tag of the parent before it is changed, and no way to distinguish tasks before they have been run at least once (we will se a bunch of runnables with the same tag).

I think we want to add a way to get statistics for a run, as in at the end of a run printing how many times tag such-and-such was run. The easiest way to store this is if tags are Hash and then update a HashMap. I therefore think tags should be Debug + Hash.

I think we want to add a way to get statistics for a run, as in at the end of a run printing how many times tag such-and-such was run. The easiest way to store this is if tags are Hash and then update a HashMap. I therefore think tags should be Debug + Hash.

This is deemed not the right approach, so disregard this comment


Machine should have Constraints

All unary & binary Machine operations should propagate/merge Constraints

Specifying a constraints file from the command-line should have the effect of incorporating these Constraints into the Machine


1.22.0 update breaks IE11 compatibility

1.22.0 update introduces htmlparser2 ^4.0.0 dependency which depends on entities ^2.0.0 that contains regex unsupported by IE11
https://github.com/fb55/entities/blob/master/src/encode.ts#L65

This is a transitive dependency, it can't be fixed from here but you can follow the progress in the entities npm module:
https://github.com/fb55/entities/issues/209
You could pin that dependency in package-lock to 2.0.0 if necessary temporarily.
Leaving this open as I'm sure others will have the question.

This is instigating us to look at planning a major version update that 1) changes the package main source to index.js directly and 2) provides a separate built version to allow people to continue using it as they are now. The OP issue is from the dependency, but we can get around some of those issues by making it easier for people to require and build this as they need it.

We've published the new major version, removing the build and switching main to index.js.


Login/Signup button not working

The button for login/signup is not working. Add a form to signup/login if the form is not added or check the bug happened with the button tag

I would like to work on this issue. Please assign me this issue.
I see that no login/signup form exists, as a result, no value has been provided to the "href" attribute of the Login/Signup button.
Also, please tell me:
Do we need a separate page for login/signup forms (or)
Integrate the forms on the landing page?


Contact Merge Still Queries for User-Defined Rollups Fields After Customizable Rollups are Enabled

If a customer deletes a field previously referenced by User Defined Rollups and they have Customizable Rollups enabled, they receive the following error during Contact Merge:
First error: Invalid field: 'Opportunity.Amount_This_Year__c'
(where Amount This Year is a custom field I created and deleted).
Stacktrace:
Failed to invoke future method 'public static void rollupContactsandHouseholdsForTriggerFuture(Set<Id>)' on class 'npsp.RLLP_OppRollup' for job id 'xxxxxxxxxxx'
caused by:
System.QueryException: Invalid field: 'Opportunity.Amount_This_Year__c'

Class.npsp.RLLP_OppRollup.rollupContacts: line 525, column 1
Class.npsp.RLLP_OppRollup.rollupContactsandHouseholdsForTrigger: line 163, column 1
Class.npsp.RLLP_OppRollup.rollupContactsandHouseholdsForTriggerFuture: line 132, column 1

Steps to Repeat

Create field on Opportunity

Name = Amount This Year
Type = Formula (Currency)
Formula: IF(YEAR( TODAY()), Amount, 0)

Create field on Contact

Name = Total Amount This Year
Type = Currency (16,2)

Create User Defined Rollup in NPSP Settings → Donations → User Defined Rollups

Opportunity Field = Amount This Year
Rollup Operation = SUM
Target Object = Contact
Target Field = Total Amount This Year
Create Rollup

Enable Customizable Rollups
Create a Contact and a Closed Won Opportunity for that Contact.
Edit the Rollup using the NPSP Settings User Interface and switch to the following values:

Change Operation to Sum
Change Time Frame to Years Ago and Years Ago to This Year.
Make Sure the Date Field = Close Date
Change the Amount field to Amount
Hit Save.

Manually delete the Rollup record in Setup → Custom Metadata Types → Rollups
Delete the Opportunity field called Amount This Year.
Create a second Contact with the same name.
Merge the 2 Contacts using the NPSP Contact Merge object.
Confirm the following error in NPSP Settings → System Tools → Error LogFirst error: Invalid field: 'Opportunity.Amount_This_Year__c'

Workaround:
Go to Setup → Custom Settings → User Rollup Field Settings and delete the record that references the field you deleted.

**lurch: attach W-031664

Tracking W-031664


Object spread causes polyfills even in modern language_out

Version: From at least mid 2022 up to latest.
compilation_level ADVANCED
language_out ECMASCRIPT_2020
rewrite_polyfills false
With ES2020 and up, using {x:foo, ...bar} causes this to be added to the head:
var ba="function"==typeof Object.defineProperties?Object.defineProperty:function(a,b,c){if(a==Array.prototype||a==Object.prototype)return a;a[b]=c.value;return a};function ca(a){a=["object"==typeof globalThis&&globalThis,a,"object"==typeof window&&window,"object"==typeof self&&self,"object"==typeof global&&global];for(var b=0;b<a.length;++b){var c=a[b];if(c&&c.Math==Math)return c}throw Error("Cannot find global object");}var da=ca(this);
function ea(a,b){if(b)a:{for(var c=da,d=a.split("."),f=0;f<d.length-1;f++){var e=d[f];if(!(e in c))break a;c=c[e]}d=d[d.length-1];f=c[d];e=b(f);e!=f&&null!=e&&ba(c,d,{configurable:!0,writable:!0,value:e})}}var fa="function"==typeof Object.assign?Object.assign:function(a,b){for(var c=1;c<arguments.length;c++){var d=arguments[c];if(d)for(var f in d)Object.prototype.hasOwnProperty.call(d,f)&&(a[f]=d[f])}return a};ea("Object.assign",function(a){return a||fa});

Summary: Abstract polyfill support, single Object.assign polyfill.
When I use Object.assign({x:foo}, bar), this disabled + useless polyfill stuff is not in there. sus
Since this adds almost a kilobyte, I deem this worth fixable. In ES2020, there is no point in having an Object.assign polyfill. :wink:

How have you configured the compiler to run and how are you invoking it? In my IntegrationTest the polyfills are only getting injected if I set the language_out to ES3.

Will post later, but can be found in https://github.com/L3P3/lui -> build.js
Also just noticed that the polyfill code has both defineProperty and defineProperties there, which seems very weird. I optimistically assume that this is on purpose since both methods were introduced together and one is shorter...

google-closure-compiler --assume_function_wrapper --charset UTF-8 --compilation_level ADVANCED --dependency_mode PRUNE --entry_point ./src/luirt.js --js ./src --js_output_file ./dist/lui.r.js --language_in ECMASCRIPT_NEXT --language_out ECMASCRIPT5_STRICT --strict_mode_input --emit_use_strict --module_resolution WEBPACK --rewrite_polyfills false --use_types_for_optimization --warning_level VERBOSE
Sorry, for ES2020, there are no polyfills, but for ES5, there is!
The thing is that these polyfills are added even though that part with {...foo} is not even in the resulting code.
I am trying to nail it down. What I got so far is that the polyfill appears even with this code:
// ==ClosureCompiler==
// @compilation_level ADVANCED_OPTIMIZATIONS
// @language_out ECMASCRIPT5_STRICT
// @rewrite_polyfills false
// @output_file_name default.js
// ==/ClosureCompiler==

(() => {
  Object.assign;
  false ? { ...{} } : null;
})();

The polyfill code only appears when both lines are there. If you uncomment one of both, it is not appearing. Note that I DISABLED polyfills explicitly but they still appear... :wink:


Invalid type declaration?

Hi!
After upgrading to version 1.0.6 I am getting type errors. I see that index.d.ts contains the following:
function localIpUrl(name?: 'public' | 'private', family?: 'ipv4' | 'ipv6'): void;

export = localIpUrl

Is this correct? My code expects the function to return string instead of void.
Thanks in advance!

@aommm Upgrade v1.0.7

Wonderful, thanks for the quick turnaround!


Add jupyterlab-nvdashboard

A JupyterLab extension for displaying dashboards of GPU usage. Repo at https://github.com/rapidsai/jupyterlab-nvdashboard
Only adding this to pytorch-notebook and ml-notebook.
Closes #321

/condalock

Locking the forge environment takes >20minutes and times out for some reason (ml-notebook only takes <2min). Might need to look into this separately.

/condalock

/condalock

Locking the forge environment takes >20minutes and times out for some reason (ml-notebook only takes <2min). Might need to look into this separately.

Only takes 6min now at https://github.com/pangeo-data/pangeo-docker-images/actions/runs/4999316441/jobs/8955588572#step:4:19. Not sure what happened, but ready for review!

Thanks @scottyhq!


Fix an apparent race condition in MethodEditTutorialTest…

… commonly seen in TC "code coverage with debug" build

Agreed 100%.  I just want to see first if this fixes the immediate problem. I suspect it's an issue with the graphs update timer - test thread getting ahead of it and checking before it's even been triggered, or something like that - so WaitForGraphs probably needs some work.

The change in selection should immediately put all graphs on an update queue and WaitForGraphs() should be waiting until that queue empty. So, what you describe shouldn't really be possible. What could happen is that an individual graph might implement its on secondary timer where it updates a first time, and then updates itself again without being put on the queue. I know that Tobi added some background updating for Prosit and Kaipo is expanding on that for his new multi-peptide combo box. This fix makes me wonder what more we may need to do about graphs that add this type of background updating so that being removed from the update queue doesn't necessarily mean the plot has been finalized.

Let's be sure to mention it at today's team meeting.


feat(trading): datanode block header for env and node switcher

Related issues 🔗
Closes #1791
Description ℹ

Changes node health UI in trading footer to be determined by comparing header block height from the data node, and the 'core' block height in the statistics query. This has the benefit of not requiring multiple requests across different nodes to determine overall node health.
NodeSwitcher component has also been updated to use datanode block height rather than the query result block height.
Store selected node in localStorage and attempts to use that on startup

Technical 👨🔧

Adds a custom ApolloLink store a map of datanode urls to header values
Environment hook and NodeSwitcher dialog have been refactored so that additional nodes state and client instance is only created in the dialog itself and garbage collected when the dialog is closed.
Adds NodeGuard component to trading app to prevent rendering app connected to a non functioning node
Adds AppFailure with DynamicLoader component fallback/loading states consistent

Did a CMD+SHIFT+R, still same, created a new incognito tab, still offline, accessed using Firefox and it was online.
https://user-images.githubusercontent.com/100769129/218757546-2139ebb7-ae43-4392-af44-60759f8bfa57.mov


[FLINK-16219][runtime] Made AsyncWaitOperator chainable to non-sources.

What is the purpose of the change
Made AsyncWaitOperator chainable to non-sources.
Brief change log

Adding HEAD_AFTER_LEGACY_SOURCE ChainingStrategy.  Operators will be eagerly chained whenever possible, except after legacy sources.
Made AsyncWaitOperator chainable to non-sources.

Verifying this change

Added AsyncWaitOperatorTest#testAsyncOperatorIsNotChainedToSources

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Addressed all comments; let's wait for travis.

@pnowojski green


Dashboard Import Error: An error occurred while importing dashboard: Error importing dashboard Please re-export your file and try importing again superset

I exported my dashboard from superset. I deleted it and while trying to import it again, an error pops up
"An error occurred while importing dashboard: Error importing dashboard Please re-export your file and try importing again superset"
I also tried importing it to another system, then also the same error ocurred. But when I import a dashboard that is exported from a different system, it works.
How to reproduce the bug
It is a first time experience. Happens in my superset.
Expected results
Import Succesful
Actual results
Couldn't import. Error occurs.
An error occurred while importing dashboard: Error importing dashboard Please re-export your file and try importing again superset
Screenshots

Environment
(please complete the following information):

browser type and version: google - Version 114.0.5735.198 (Official Build) (64-bit)
superset version: 2.0.0.

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Please don't double-post your question https://github.com/apache/superset/discussions/25987

I am facing same issue , is there any resolution for this ?

Closing this out since it's gone silent, and we no longer support 2.0 (or 3.0). If you're facing this in 3.1/4.0, we can revisit. I suspect it's something to do with these older versions needing the VERSIONED_EXPORT feature flag turned on.

@rusackas  i face the same issue in 4.0.0


[Bug]: Getting a compilation error when Client is generated in the bal build

Description
I am in the process of integrating bal persist client generation into the bal build command. The whole purpose of having integrated is that you don't have to commit the generated code. Therefore, if we have code written using the client which is being created when building the project, it should work without any problems when we do a bal build.
However, even though the client is generated in the bal build before compiling resources, it results in a compilation error stating "unknown type 'Client'".
Steps to Reproduce

Client is generated in the generated folder.

Affected Version(s)
Using the lang timestamp version 2201.9.0-20240229-103900-a949e6d4
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Isn't the client still generated in a separate module? If so, you have to use the module prefix.

Isn't the client still generated in a separate module? If so, you have to use the module prefix.

When we execute bal build twice, this works.

Isn't the client still generated in a separate module? If so, you have to use the module prefix.

When we execute bal build twice, this works.

May be because the compilation doesn't happen the first time around, just the code generation.
Looping in @azinneera

The code generation is followed by the compilation and the generated sources are expected to compile. We didn't get this error with the OpenAPI code generation. Probably a bug when adding the generating code to the default module. Looping in @ShammiL

I am currently looking into this.
I have tried to reproduce this using the persist-cli tool jar provided with the following configurations in the Ballerina.toml
[[tool.persist]]
id = "persist-cli-1"
filePath = "/persist/model.bal"
options.datastore = "inmemory"

and am getting this error.
ERROR: the persist configurations does not exist under [persist] table.
Can you provide the tool configurations you used and also point me to the implementation of the tool?

This error is probably because we need to update the module-ballerina-persist version as well. Could you please try using this distribution? https://drive.google.com/file/d/1NjJdZeyce2oOr0warsImi5z6SVGzx3iv/view?usp=sharing
You can use the following toml configurations,
[[tool.persist]]
id = "persist-cli-1"
filePath = "/persist/model.bal"
targetModule = "pers"
options.datastore = "inmemory"

[[platform.java17.dependency]]
groupId = "io.ballerina.stdlib"
artifactId = "persist.inmemory-native"
version = "1.2.0"

And the PR is https://github.com/ballerina-platform/persist-tools/pull/331

When we do a bal build the execution first loads the project and then proceeds to run the build tools and then compile. Since the initial project loading happens before the running the build tools, the newly generated modules are not added to the project instance causing the aforementioned compilation failure.
Working on a fix to have the project loaded again to have the project instance updated with the generated code.

This error is probably because we need to update the module-ballerina-persist version as well. Could you please try using this distribution? https://drive.google.com/file/d/1NjJdZeyce2oOr0warsImi5z6SVGzx3iv/view?usp=sharing
You can use the following toml configurations,
[[tool.persist]]
id = "persist-cli-1"
filePath = "/persist/model.bal"
targetModule = "pers"
options.datastore = "inmemory"

[[platform.java17.dependency]]
groupId = "io.ballerina.stdlib"
artifactId = "persist.inmemory-native"
version = "1.2.0"

And the PR is ballerina-platform/persist-tools#331

Just wanted to note down a few things I noticed when running the persist tool with these configurations:

If a user does not provide the targetModule the tool is expected to consider the default module. But when running the persist tool, not explicitly providing the targetModule gives an error:
ERROR: the persist configurations does not exist under [persist] table. error.
This means, if a user wants to have the default module as the targetModule, it has to be explicitly provided with targetModule = "persist_sample".
Providing targetModule = "pers" in the configurations as mentioned gave the following error.

ERROR: invalid module name : 'pers' :
module name should follow the template <package_name>.<module_name>

So I tried with targetModule = "persist_sample.pers" and that worked fine.

This error is probably because we need to update the module-ballerina-persist version as well. Could you please try using this distribution? https://drive.google.com/file/d/1NjJdZeyce2oOr0warsImi5z6SVGzx3iv/view?usp=sharing
You can use the following toml configurations,
[[tool.persist]]
id = "persist-cli-1"
filePath = "/persist/model.bal"
targetModule = "pers"
options.datastore = "inmemory"

[[platform.java17.dependency]]
groupId = "io.ballerina.stdlib"
artifactId = "persist.inmemory-native"
version = "1.2.0"

And the PR is ballerina-platform/persist-tools#331

Just wanted to note down a few things I noticed when running the persist tool with these configurations:

If a user does not provide the targetModule the tool is expected to consider the default module. But when running the persist tool, not explicitly providing the targetModule gives an error:
ERROR: the persist configurations does not exist under [persist] table. error.
This means, if a user wants to have the default module as the targetModule, it has to be explicitly provided with targetModule = "persist_sample".
Providing targetModule = "pers" in the configurations as mentioned gave the following error.

ERROR: invalid module name : 'pers' :
module name should follow the template <package_name>.<module_name>

So I tried with targetModule = "persist_sample.pers" and that worked fine.

The users are not expected to fill in these values in the toml configurations, these are automatically filled from the inputs that are given from the bal persist add command. These validations are there, in case they change them. Otherwise, there is no need to edit those configurations.

This is fixed now in https://github.com/ballerina-platform/ballerina-lang/pull/42328

Timestamped snapshot with the fix can be accessed from https://github.com/ballerina-platform/ballerina-lang/actions/runs/8329068251


Fix id in TourManager.addTour

Fixes #27

cc @bollwyvl
Do you want to be added as contributor to the organization to get write access?


forge verify-contract errors with Fail - Unable to verify. Unable to locate ContractCode, yet Abi is compiled and available

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (d14a7b4 2024-11-24T00:24:44.637144000Z)
What command(s) is the bug in?
forge verify-contract
Operating System
None
Describe the bug
Unable to locate ContractCode error, yet all Abi needed is available in the repository. Not sure what more information needs to be provided.

@0xTimepunk do you have a minimal repro to check, quite hard to figure out what's wrong without. Thank you

just tried verifying couple of contracts on sepolia and sepolia base and all working OK

for context: base related issue which was fixed and @0xTimepunk was able to verify


Failure to open url with "C:" in url

Configuration:

Web browser and its version:
Electron 1.6
Operating system and its version:
Windows 10
PDF.js version:
(These are pdfjs-dist)
Works: v1.9.426
Doesn't work: Latest - eg: 1.9.583
Is an extension: No

Steps to reproduce the problem:

Try to open a file url: "file://C:\Users\John Doe\test.pdf"
PDFJS.getDocument( "file://C:\Users\John Doe\test.pdf")...
2.ENOENT: no such file or directory, lstat 'C:\C:\Users\John%20Doe\test.pdf"

I've spent a bunch of time on this, and I think there are two issues:

the encoded space, which is fixed in 8907
the file://C:... gets transformed to file:///C:... (extra slash), and then it later sees the / for the filesystem, and adds another c:\ to the front.

Note - this whole file://c:... works as expected in v1.9.426 (even with the encoded space).

Similar to https://github.com/mozilla/pdf.js/issues/8907 . We have to decode the url using decodeURI to get the correct file system path. There is a PR for this issue #8928 .

this error still exists ... decodeURI is not working
path before decodeURI: /C:/User/1234/Desktop/a.pdf
after decodeURI, path is still the same
fs.lstat would transfrom it to C:\C:\User\1234\Desktop\a.pdf and then this error occurred


[BUG 2.0.alpha] Drag spinboxes.

Problem founded in Particle2D, amount and lifetime.
If I move the mouse quickly up, it does not reach the maximum value.
and I get this error when I do this.
ERROR: set_amount: Index p_amount out of size (1024).
At: scene/2d/particles_2d.cpp:700
but the value stop in 854 for example.
Another bug, all controls that has "Range" properties, for example ProgressBar, if you change the "Min" value with this feature, godot will crash.

thanks for reporting this! will check asap
On Mon, Aug 31, 2015 at 12:39 PM, Guilherme Felipe<EMAIL_ADDRESS>
wrote:

Problem founded in Particle2D, amount and lifetime.
If I move the mouse quickly up, it does not reach the maximum value.
and I get this error when I do this.
ERROR: set_amount: Index p_amount out of size (1024).
At: scene/2d/particles_2d.cpp:700
but the value stop in 854 for example.
Another bug, all controls that has "Range" properties, for example
ProgressBar, if you change the "Min" value with this feature, godot will
crash.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/2411.

--
OkamStudio


Pushing down api version to 2018-04-01

Description

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

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

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

Testing Guidelines

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

SDK Generation Guidelines

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

@azuresdkci test this please

Closing as duplicate of https://github.com/Azure/azure-sdk-for-net/pull/4381


There is a problem with the connection logic of the timeline

When using Software to transcribe Chinese, I found a problem with the connection logic of some of the timelines. Even if there was no speech for a while in between, the subtitles of the previous sentence would continue in the timeline to the next sentence. This can lead to obvious errors in the output subtitles and audio, affecting their usability and readability. But I'm not sure if this is a problem with Whisper's model or with buzz.

In addition, this is really very good software that frees up a lot of my time, thanks to the author.

Yes, I think this should be coming from Whisper, unfortunately.


Payment systems

How can I add payment system? Any example?

@sonufrienko I will release PayPal in this week.


Test/smoke test dataset

closes #9

Codecov Report

Merging #24 (92946e5) into main (9da6d6b) will increase coverage by 0.06%.
The diff coverage is 14.28%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #24      +/-   ##
==========================================
+ Coverage   36.55%   36.61%   +0.06%
==========================================
  Files           7        7
  Lines         424      426       +2
==========================================
+ Hits          155      156       +1
- Misses        269      270       +1

Impacted Files
Coverage Δ

giga_connectome/workflow.py
13.82% <0.00%> (ø)

giga_connectome/outputs.py
21.35% <20.00%> (+0.56%)
:arrow_up:


Crash on startup when using Quilt on 1.19.2

note: Quilt uses the same fabric mappings, but there could be a problem there too, but 99.9% of mods i've tried haven't broken on quilt yet.
https://paste.atlauncher.com/view/934f2db6-7f18-4ce4-bc10-7dc09f6892e6

Weird. It seems like that the mod fabricloader is not installed in your modpack. But it is the main component of fabric that loads all other mods. Do you know what kind of mod loader you have? Since you seemingly do not have fabricloader.

I see. It is mentioned in the logs: Quilt 0.17.5-beta.1. I have never seen it. I will look into it. And how I can fix the problem.

I see. It is mentioned in the logs: The loader is Quilt 0.17.5-beta.1. I have never seen it. I will look into it. And how I can fix the problem.

It's essentially a community based enhanced fabric, but they kept the fabric mappings and api for the forseeable future. Fabric api is there, it's just either, not noticed because of the way they do it, or named differently.

I see. It is mentioned in the logs: The loader is Quilt 0.17.5-beta.1. I have never seen it. I will look into it. And how I can fix the problem.

It's essentially a community based enhanced fabric, but they kept the fabric mappings and api for the forseeable future. Fabric api is there, it's just either, not noticed because of the way they do it, or named differently.

They use "Quilt standar libraries/Quilted Fabric API"

Okay. I think I fixed it. My fork of amecs uses my helper library FabricMultiVersionHelper. If you download the latest release and add it to your mods folder, it should work. Because the loader will prefer the newer version of FabricMultiVersionHelper and this newer version is fixed. Please try it.

Bingo! thanks a lot! <3

This crashes on quilts latest beta update, for some reason.

@netcore10 I guess that reopen was accidental

yeah apologies!


Add support for custom package registry

Hi there.
We are working on a public registry of open source packages for Unity https://xcrew.dev/
It would be nice if you could support and update Zenject yourself.
For it you need:

Create a pair login:hash on the site http://www.htaccesstools.com/htpasswd-generator/
Select the scope in which your packages will be placed. (Apparently it is com.modesttree)
PM me it and I will add your account
Install npm
Start the terminal and enter npm set registry http://xcrew.dev
Enter npm login
Go to the root of your package in the terminal and enter npm publish

All dependencies are resolved automatically by the package manager.
It is necessary to specify the dependencies for additional packages like so
{
    "name": "com.modesttree.zenject.reflectionbaking",
    "author": "Modest Tree",
    "displayName": "Zenject.ReflectionBaking",
    "unity": "2018.1",
    "version": "8.0.0",
    "keywords": [
        "IoC",
        "DI",
        "Dependency Injection",
        "Zenject"
    ],
    "dependencies": {
        "com.modesttree.zenject": "8.0.0"
    },
    "repository": {
        "type": "git",
        "url": "https://github.com/modesttree/Zenject.git"
    }
}

To add registry support to the project, add the following lines to the manifest.json
{
  "dependencies": {
  },
  "scopedRegistries": [
    {
      "name": "Unity",
      "url": "https://packages.unity.com",
      "scopes": [
        "com.unity"
      ]
    },
    {
      "name": "XCrew",
      "url": "http://xcrew.dev",
      "scopes": [
        "com"
      ]
    }
  ]
}

In the editor it looks like this

My Contacts:

Email<EMAIL_ADDRESS>Telegram: https://t.me/benjminmoore
Skype: benjminmoore

Regards, Oleg

I'd plus one this for sure. Especially given Zenject is a version of 3 behind in the Asset Store most of the time.


Add desed to list of apps using tui?

Desed is new application that is using tui-rs. It's debugger for sed with all the things like stepping, setting breakpoints and examining runtime state.
It passed 500 github stars, so I think it's big and popular enough to be added to the list in readme.

This is a nice project ! I might start using it ;).


How to Cancel/Hide a scheduled notification?

I am guessing that CancelAll removes all Scheduled notifications but How can I remove a single scheduled notification? It is like I am doing a calendar with appointments and there can multiple scheduled appointments if I want to remove one, I need remove a toast notification for it also. I dont see any function exposed in the current code. Am I missing something please?

@adamped Do you know the answer for this please?

There is currently no support in this plugin to cancel a single notification. However it is supported natively. If you want to create a PR to implement, I'm happy to accept PR's, but I don't have any time in the immediate future to implement it atm.

@adamped I will try to get that for android but I am not good with IOS and UWP. I know this  done by this plugin. maybe we can take a look at there.


support PNG

Hi, what can I do to make the project support PNG, thanks！

Hi, I was discussing this with @boerniee today and we are considering moving away from using Exifr which can only handle JPEG and TIFF images. I am currently playing around with a Ruby wrapper for ExifTool and it looks quite promising! I will keep you updated.

Big ask I appreciate, but video support would also be amazing. This is less out of scope than you'd think, what with iPhone live photo formats (HEIC/HEVC, which are basically jpeg + mov files).

@timdonovanuk I am afraid it might be harder to implement videos than you think. :) While the library processing the images (libvips) does indeed support HEIC it still is a library for processing images only. Also since browsers are not able to display HEIC images you would have to convert HEIC videos to some other format. Right now I even struggle to get the convert function working so HEIC images get converted to JPEG. It just seems to ignore it when I set it in the config file.

PNG support will be coming along with WebP support #68


Outdated sysroot_linux-64 (try 2)

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
This feedstock defaults to using an outdated version of sysroot_linux-64, which causes compatibility issues with mpich 4.2.2 as reported in https://github.com/conda-forge/mpich-feedstock/issues/98
Also see https://github.com/Libensemble/libensemble/actions/runs/9862133688/job/27232089090?pr=1344#step:14:110
Steps to reproduce:
conda create -n testmpi mpich gcc_linux-64
export PYTHONNOUSERSITE=1
. activate testmpi
mpicc helloworld_mpi.c

... libmpi.so: undefined reference to<EMAIL_ADDRESS>
Installed packages
# packages in environment at /home/shudson/miniconda3/envs/test_gcc_linux_glibc:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       2_gnu    conda-forge
binutils_impl_linux-64    2.40                 ha1999f0_7    conda-forge
binutils_linux-64         2.40                 hb3c18ed_9    conda-forge
gcc_impl_linux-64         13.2.0              h9eb54c0_13    conda-forge
gcc_linux-64              13.2.0               h50dba11_9    conda-forge
kernel-headers_linux-64   2.6.32              he073ed8_17    conda-forge
ld_impl_linux-64          2.40                 hf3520f5_7    conda-forge
libgcc-devel_linux-64     13.2.0             hdb50d1a_113    conda-forge
libgcc-ng                 14.1.0               h77fa898_0    conda-forge
libgfortran-ng            14.1.0               h69a702a_0    conda-forge
libgfortran5              14.1.0               hc5f4f2c_0    conda-forge
libgomp                   14.1.0               h77fa898_0    conda-forge
libsanitizer              13.2.0              h6ddb7a1_13    conda-forge
libstdcxx-ng              14.1.0               hc0a3c3a_0    conda-forge
mpi                       1.0                       mpich    conda-forge
mpich                     4.2.2              h4a7f18d_100    conda-forge
sysroot_linux-64          2.12                he073ed8_17    conda-forge

Environment info
active environment : test_gcc_linux_glibc
    active env location : /home/shudson/miniconda3/envs/test_gcc_linux_glibc
            shell level : 1
       user config file : /home/shudson/.condarc
 populated config files : /home/shudson/.condarc
          conda version : 4.10.3
    conda-build version : not installed
         python version : 3.9.5.final.0
       virtual packages : __linux=5.15.0=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /home/shudson/miniconda3  (writable)
      conda av data dir : /home/shudson/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/shudson/miniconda3/pkgs
                          /home/shudson/.conda/pkgs
       envs directories : /home/shudson/miniconda3/envs
                          /home/shudson/.conda/envs
               platform : linux-64
             user-agent : conda/4.10.3 requests/2.28.2 CPython/3.9.5 Linux/5.15.0-113-generic ubuntu/20.04.6 glibc/2.31
                UID:GID : 1000:1000
             netrc file : /home/shudson/.netrc
           offline mode : False

We moved to glibc 2.17 universally across conda-forge per the end of June, so anything below 2.17 is not relevant anymore.
That said, the problem was now solved more generally: if anything depends on a newer glibc than our baseline (so >2.17, as of July 2024), we can handle this with the {{ stdlib("c") }} infrastructure. This will translate to a corresponding __glibc requirement.
If you want this to translate to a constraint on the sysroot_<target> as well, you can join the discussion in https://github.com/conda-forge/linux-sysroot-feedstock/issues/63 (or, barring a global solution like that, you can add the strong_constrains from there to mpich).

This issue should be fixed now

@h-vetinari @isuruf The MPICH recipe do have {{ stdlib("c") }} in the build section, but there is no sysroot_* dependency at all. What am I missing? Should I add the c_stdlib_version: [2.17] entry to conda_build_config.yaml ?

@dalcinl you don't have to do anything for now. This issue was fixed yesterday.


Fix code scanning alert - Final newline missing

Tracking issue for:

[ ] https://github.com/LucaMingarelli/CryptPandas/security/code-scanning/82

Solved.


LiE: init at 2.2.2

Motivation for this change
provide a common package for nixos and nix
Things done

[ ] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Hello!
Sorry for bringing this up again. During installation phase the file INFO.a was forgotten to be copied to $out.  At the moment many builtin functions are not available rigth now. For example start lie
% lie
and then run
 > max_sub(B3)
this should not return an error but a list of sub algebras.
Please consider to merge heilkn:lie again.
I'm sorry for the inconvenience.
Kind regards
Konstantin

Please make a new PR.


Some failed tests, hoping you can tell me what went wrong

Expected Behavior
I expected the 'make tests' suite to pass
Actual Behavior
16 of 634 failed
Steps to Reproduce the Problem
Well, just run 'make tests' on my system
Specifications
... Please describe your environment
HPX commit 3e63f6a73114dc923028851d622db902a6473819
Ubuntu 16.04
Cuda 9 (V9.0.176)
gcc 7.2.0
slurm 17.11
MVAPICH2 gdr 2.3a
cmakeCache_patch_lastTest.zip

Most (if not all) of the 'failing' tests are supposed to fail. Those are 'must-fail' tests. It looks like that 2 tests failed because of actual problems, one of which was addressed just yesterday. We're currently working on fixing the remaining issues.
It might be helpful if you could list the tests that you believe actually failed for you in a comment to this ticket..

OK, good to hear.  I'm really excited about your work on this -- I'm
wanting to put it through some paces on some interesting hardware.
I'm pasting this into the issue area:  [thanks Harmut]
grep -B 5 'Test Failed' LastTest.log
Process 1 failed with an unexpected error code of -6 (expected 0)
Process 0 failed with an unexpected error code of -15 (expected 0)

Test time =   0.23 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/broadcast_wait_for_2822_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=4 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   0.13 sec
Test Failed.
Executing command: /mnt/orrl/cluster_sw/hpx/hpx/build/bin/lifetime_588_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   0.14 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/lifetime_588_1_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   0.23 sec
Test Failed.
Base command is
"/mnt/orrl/cluster_sw/hpx/hpx/build/bin/command_line_required_arguments_2990_test
--hpx:threads=1 --hpx:localities=1"
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/command_line_required_arguments_2990_test
--hpx:threads=1 --hpx:localities=1 --hpx:node=0

Test time =   0.08 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/credit_exhaustion_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   2.25 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/remote_embedded_ref_to_remote_object_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   8.25 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/refcnted_symbol_to_remote_object_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   6.13 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/uncounted_symbol_to_remote_object_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   6.24 sec
Test Failed.
Base command is
"/mnt/orrl/cluster_sw/hpx/hpx/build/bin/migrate_component_test
--hpx:ini=hpx.parcel.mpi.enable=1 --hpx:ini=hpx.parcel.bootstrap=mpi
--hpx:threads=2 --hpx:localities=2"
Executing command: srun -K -n 2
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/migrate_component_test
--hpx:ini=hpx.parcel.mpi.enable=1 --hpx:ini=hpx.parcel.bootstrap=mpi
--hpx:threads=2 --hpx:localities=2

Test time = 1154.55 sec
Test Failed.
Process 1 failed with an unexpected error code of -9 (expected 0)
Process 0 failed with an unexpected error code of -15 (expected 0)

Test time = 1002.93 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/unordered_map_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=2 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   0.34 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/partitioned_vector_for_each_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=4 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   0.34 sec
Test Failed.
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/partitioned_vector_reduce_test
--hpx:ini=hpx.parcel.tcp.enable=1 --hpx:threads=4 --hpx:localities=2
--hpx:node=1
Process 1 failed with an unexpected error code of -6 (expected 0)

Test time =   0.26 sec
Test Failed.
Base command is
"/mnt/orrl/cluster_sw/hpx/hpx/build/bin/partitioned_vector_find_test
--hpx:ini=hpx.parcel.mpi.enable=1 --hpx:ini=hpx.parcel.bootstrap=mpi
--hpx:threads=4 --hpx:localities=2"
Executing command: srun -K -n 2
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/partitioned_vector_find_test
--hpx:ini=hpx.parcel.mpi.enable=1 --hpx:ini=hpx.parcel.bootstrap=mpi
--hpx:threads=4 --hpx:localities=2

Test time =   1.22 sec
Test Failed.
Base command is
"/mnt/orrl/cluster_sw/hpx/hpx/build/bin/apex_action_count_test
--hpx:threads=1 --hpx:localities=1"
Executing command:
/mnt/orrl/cluster_sw/hpx/hpx/build/bin/apex_action_count_test
--hpx:threads=1 --hpx:localities=1 --hpx:node=0

Test time =   0.11 sec
Test Failed.
On Tue, Feb 13, 2018 at 7:12 PM, Hartmut Kaiser<EMAIL_ADDRESS>wrote:

Most (if not all) of the 'failing' tests are supposed to fail. Those are
'must-fail' tests. It looks like that 2 tests failed because of actual
problems, one of which was addressed just yesterday. We're currently
working on fixing the remaining issues.
It might be helpful if you could list the tests that you believe actually
failed for you in a comment to this ticket..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/issues/3173#issuecomment-365482608,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiXDyVQDsBlKQqtmVF9NtF2j_89gnGOks5tUk8BgaJpZM4SEuP7
.

Hi @hkaiser, thanks for the info.
Can you be more specific with what you've fixed and what are expected failures?
I suppose I'm most concerned about the migrated component, partitioned vector and unordered map tests . . .

I suppose I'm most concerned about the migrated component, partitioned vector and unordered map tests .

Right, those are the ones we have not seen failing before.

Oh, well, good to narrow it down.
If you have any news you may also contact me at<EMAIL_ADDRESS>On Sat, Feb 17, 2018 at 4:39 AM Hartmut Kaiser<EMAIL_ADDRESS>wrote:

I suppose I'm most concerned about the migrated component, partitioned
vector and unordered map tests .
Right, those are the ones we have not seen failing before.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/issues/3173#issuecomment-366438790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiXD8v45WvbEjRn0wcQgS9SqeOgAlDeks5tVshxgaJpZM4SEuP7
.

@Geof23 since you mentioned it's an interesting and new piece of hardware, I wouldn't be surprised if you uncovered some obscure bugs. First thing I'd like to know is if this hardware has more than 64 cores (including logical cores), that might explain unexpected behavior unless you configure everything with HPX_WITH_MAX_CPU_COUNT=512 (or similar).

Hi Thomas -- yes, it is 80 logical cores.   I also set:
HPX_WITH_MAX_CPU_COUNT:STRING=80
HPX_WITH_MORE_THAN_64_THREADS:BOOL=TRUE
On Sun, Feb 18, 2018 at 11:50 PM, Thomas Heller<EMAIL_ADDRESS>wrote:

@Geof23 https://github.com/geof23 since you mentioned it's an
interesting and new piece of hardware, I wouldn't be surprised if you
uncovered some obscure bugs. First thing I'd like to know is if this
hardware has more than 64 cores (including logical cores), that might
explain unexpected behavior unless you configure everything with
HPX_WITH_MAX_CPU_COUNT=512 (or similar).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/issues/3173#issuecomment-366611664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiXD16PP5ElBfbSHxhCLi7ea7rtSFdhks5tWSeygaJpZM4SEuP7
.

Hmmm, would have been too easy ... Really hard to tell what's going on then. Would be interesting to rerun one of the failing tests in debug mode and see where they actually fail.
One thing that I noticed when skimming through the test log is that MPI complains about not being able to preallocate some buffers. What might actually help is to rebuild everything (with a clean build directory) without a special allocator: cmake -DHPX_WITH_MALLOC=system ...

Hi Thomas
. Would be interesting to rerun one of the failing tests in debug mode and
see where they actually fail.

What might actually help is to rebuild everything (with a clean build
directory) without a special allocator: cmake -DHPX_WITH_MALLOC=system ...
—

I’m game.  I’ll let you know what happens on both counts.

Best — Geof

Thomas, a quick question: is there a 'normal' way to configure the tests to
run with Slurm?
So what I've done is used a stream editor to modify all the
CTestTestfile.cmake's to insert 'srun'.
On Mon, Feb 19, 2018 at 1:47 AM, Geof Sawaya<EMAIL_ADDRESS>wrote:

Hi Thomas
. Would be interesting to rerun one of the failing tests in debug mode and
see where they actually fail.

What might actually help is to rebuild everything (with a clean build
directory) without a special allocator: cmake -DHPX_WITH_MALLOC=system
...
—

I’m game.  I’ll let you know what happens on both counts.

Best — Geof

sorry for the late reply.
The normal way is to set the environment variable HPXRUN_RUNWRAPPER to srun. The tests are executed using a python script. By setting the runwrapper to srun, you'll get what you want.

Hi Thomas — great, thanks for the info
On Thu, Mar 1, 2018 at 4:19 AM Thomas Heller<EMAIL_ADDRESS>wrote:

sorry for the late reply.
The normal way is to set the environment variable HPXRUN_RUNWRAPPER to
srun. The tests are executed using a python script. By setting the
runwrapper to srun, you'll get what you want.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/issues/3173#issuecomment-369574568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiXD7VCrPNdvcl4mi5CEtLZpYuw2EW7ks5tZ-dZgaJpZM4SEuP7
.

I can't do that because my MPI is integrated with SLURM and doesn't provide
those.
On Thu, Mar 1, 2018 at 4:34 AM, Geof Sawaya<EMAIL_ADDRESS>wrote:

Hi Thomas — great, thanks for the info
On Thu, Mar 1, 2018 at 4:19 AM Thomas Heller<EMAIL_ADDRESS>wrote:

sorry for the late reply.
The normal way is to set the environment variable HPXRUN_RUNWRAPPER to
srun. The tests are executed using a python script. By setting the
runwrapper to srun, you'll get what you want.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/issues/3173#issuecomment-369574568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiXD7VCrPNdvcl4mi5CEtLZpYuw2EW7ks5tZ-dZgaJpZM4SEuP7
.

Oh, in that case, we need to adapt the runscript. It is generated during the cmake step. So you'd need to change it somehow (not exactly sure how though) here: https://github.com/STEllAR-GROUP/hpx/blob/master/cmake/templates/hpxrun.py.in#L65-L75
The MPIEXEC and friends come out of CMake's FindMPI.cmake script ... what value does it have for you?


Dropdowns should be closed after selecting an option by default

As you can see on the non-React version of Tabler https://tabler.github.io/tabler/# the dropdowns are being closed once you select an option by default. This is not the case for tabler-react. If you'd prefer to not change the default behavior (understandable), can you at least provide an easily configurable way to do what I ask for? Thanks.

Thanks for reporting the issue, we strive to replicate the tabler behaviour has much as possible. This will be fixed in an upcoming release.
I’m sure this could be useful if the dropdown is not being use as navigation, more like an option selection. I hadn’t really thought of that before. I’ll definitely look into it.
Thanks

On Aug 13, 2018, at 04:56, Paweł Dąbrowski<EMAIL_ADDRESS>wrote:
As you can see on the non-React version of Tabler https://tabler.github.io/tabler/# the dropdowns are being closed once you select an option by default. This is not the case for tabler-react. If you'd prefer to not change the default behavior (understandable), can you at least provide an easily configurable way to do what I ask for? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@paolostyle Sorry for taking so long in getting back to you on this.  By dropdowns on tabler-react, do you mean for example the profile dropdown in the upper right?  Are you suggesting that on clicking an item such as Settings, the dropdown should close as it does on the tabler page?  Just trying to get a better understanding of what you are looking for.

Yep, exactly.

:tada: This issue has been resolved in version 1.20.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can I boost a field and not a term ?

I am building an index which has several fields (name, make, OEM name and description)
E.g
ID: 1
Name: Wrench
Make: Test
OEM Name: Wrench 123
Description: Nice wrench

ID: 2
Name: Allen Wrench
Make: Rick
OEM Name: null
Description: It's a good one!

So when I search for allen wrench, given that the word wrench is in name, oem name and description it makes sense that the first result is ID 1.
However I want to specify that the field Name has an extra boost so that when I search for allen wrench ID 2 will be the first result.
Is that possible?

I've put together an example to demonstrate how a query that boosted a field could look. That said, it doesn't have the behaviour that you want, document 1 still scores higher.
This is interesting because Lunr used to have field level boosts but they were dropped in 2.x. I justified this to myself by also introducing term level boosts at query time and assumed that it would be possible to replicate the behaviour of build time field boosts with query time term boosts. Your example seems to disprove that.
I need to run some more tests, because it might be the example data. I think the issue is that term boosts are a way of giving more weight to a term relative to other terms in that field, what you actually want is a field to have more weight to relative to other fields. You can see this in your example if you search just in the name field and make 'wrench' more important (document 1 is returned first despite not having the term 'allen':
idx.search("name:wrench^10 name:allen")

Thanks for bringing this to my attention, if it turns out that field boosts cannot be replicated with term boosts then it will be something I will address.

@olivernn No problem. Hopefully it'll be something you can address in the future :)
Also thank you very much this library. We have an offline capable application working with thousands of items in the IndexedDB and this brought a huge improvement over our simple regex based search 👍

@olivernn  Can we have field specific boosting available in lunr 2.0 similar to what we used to have in lunr 1.0.  Suppose, if we have 2 fields like 'title' and 'body' and we want to boost results which have queries matched in 'title' over the queries matched in 'body' , we cannot achieve it using term level boosting.
Thanks in advance.

I've been looking at this recently, in addition to bringing back the field boosts I also want to introduce document boosts. As mentioned in that linked comment there are a couple of snags with the current implementation of similarity ranking that needs to be worked out before this feature can land.

I've just released version 2.3.0 which now re-introduces field boosts as well as adding document boosts. Documentation is being updated, I will updated the guides at some point too, but this is what the interface looks like:
var idx = lunr(function () {
  this.ref('id')
  this.field('title', { boost: fieldBoost })
  this.field('body')

  documents.forEach(function (doc) {
    this.add(doc, { boost: documentBoost })
  }, this)
})

Thanks a lot @olivernn for adding it back . I will check it out.


Maintain Repositery

Hi,
This is the recent update from the main source. I noticed you are not maintaining this repository. If you don't have time to maintain then give me I will handle this.
PS: I am interested in making free things for the public and managing.

Hi, currently this project is in code freeze, meaning that no new features are going to be implemented and only PR that are emergency fixes are accepted.
If you want to contribute you can do it on the new projects TempusDominus


senderDB size related

Everything with this project seems to be designed carefully and achieve good online performance, except that the size of senderDB is quite large when label is long. I understand that the encrypted labels and multiple of them are saved, but is there a way to compress the senderDB size for the sake of storage? Maybe compression techniques will not affect online performance as well.

In the paper (https://dl.acm.org/doi/pdf/10.1145/3460120.3484760), the authors note that their HElib implementation is the one they use to focus more on improving communication overhead. This is because SEAL's plaintext parameter selection is much more rigid than in HElib or other libraries, and is not amenable to choosing parameters friendly to the optimization of low-depth exponentiation via Frobenius automorphisms. Thus, the SEAL implementation doesn't focus as much on communication overhead, but is primarily for making comparisons with related work.

The only way really to compress the SenderDB is by using the SenderDB::strip function. This removes all unnecessary data structures, but prevents the SenderDB from being modified any further (adding, deleting, or changing items/labels). If you do this and ensure there are no changes to the SenderDB, then you can probably also set the label seed to be 0 bytes, which will reduce the size a little.


Terminal crashes when vim split over ssh

Environment
Windows build number: Microsoft Windows [Version 10.0.18362.263]
Windows Terminal version (if applicable): 0.2.1831.0

Any other software?
Ubuntu Server 18.04.2 (host ssh'd to, probably doesn't matter)

Steps to reproduce
SSH to a server running Ubuntu 18.04.2. Edit something with vim and split view. Hopefully you know how to escape hotel vim and how to use it. This guide may help. It crashes for me, repeatedly.
EDIT: I tried this ssh'ing to a RHEL5 host, it did not repeat. Then when I tried it a 3rd time on the Ubuntu 18.04.2 host it did not crash. Sorry, this may be harder to reproduce than I thought. Specifically, I also used vs, vertical split. That may be important.
Expected behavior

Not crashing when I split view in vim over SSH, actually being able to edit 2 files side-by-side just like I can on my local host.
Actual behavior

Crashes. This does not happen on the local host, just over SSH to another.

It's actually just me pressing Ctrl-W twice as that switches windows in vim. That is also the default close tab shortcut in Terminal. Is it okay to change the subject? This is definitely a questionable default.

In that case, I've got good news!
#1417, #2014


windows support

prompt-sync does fs.openSync('/dev/stdin', 'rs')  - preliminary research suggests there is no  /dev/stdin equivalent on windows (hopefully there's something..)
on occasion we're concatenating paths instead of path.join

@davidmarkclements There might also be some issues that are Seneca / Windows specific. If you find them pop em on the Seneca board. This is something @rjrodger is interested in improving so we can get people on it.

I've had a lot of issues getting sync prompting to work correctly with my node cli tools. I finally broke down and started using a promise chain which allowed me to use inquirer. That library has all the bells and whistles. Not sure about their windows support but I'd be willing to bet it's good.

hey thanks @jondlm - yah we're using yeoman under the hood too which actually uses inquirer -
I love the idea of a synchronous prompt for code simplicity - promises are certainly an option but something I've been considering is using a conditionally installed native module fallback for windows (and possibly node .10). Since prompt-sync is wrapped in https://github.com/davidmarkclements/incite and positive it would be straight forward to update these modules and have a fix without any refactoring in fuge code base

ok I've discovered a prompt-sync fix for both windows and node 0.10
https://github.com/0xxff/prompt-sync/pull/9
Nevertheless, I'm going to create a reduced features version of prompt-sync for the incite and positive modules so we're not waiting on the PR.
thanks @jondlm for inspiring me to investigate

ok so the prompt issue for windows is solved -
but we still need to investigate seneca issues and any others that may arise - pending investigation
https://github.com/apparatus/fuge/commit/eb04270c5aed8064c37a59a817b032207ac741c9
https://github.com/davidmarkclements/syncoprompt
https://github.com/davidmarkclements/incite/commit/00e3ebbef86bc995d26666afddf5ad1cf78fa871
https://github.com/davidmarkclements/positive/commit/41559d92aba4641f7f061e6d5d4c3ec242f1f5c7

Awesome stuff!

@pelger didn't you close out the final pieces of this this last week  - okay to close issue?

@davidmarkclements just wrapping this up today - will have a PR shortly

I believe that windows support should be sorted now - can one of you guys please install the latest version for me and double check. Cheers.

Running on Win 10 - was having problems with watch, but seems to be working great now. Thanks!

Awesome - thanks for checking - will close this now.


Hyperion Component

I am interested in expanding the Hyperion component to include the built in effects that Hyperion offers.  There are about 20 effects native to Hyperion. I would like to add a drop down via input_select to the Hyperion card in the UI so that an effect could be chosen instead of an RGB color.
From a coding standpoint, all that needs to happen is that an input is selected and then it creates a JSON request like this...
self.json_request({"command": "effect", "priority": 128, "effect": self._effect_name})
I haven't done much component development, so I'm a little uncertain how to integrate with input_select. Do any other components utilize input_select that I can copy? I appreciate any pointers along the way. Cheers!
P.S. A stretch goal would be adding what what effects you want to enable in the hyperion config similarly to how sensors are added with weather components.

The first step could be to implement the effects the same way as scenes are (or simple a switches). So users can click the badge to activate them if they are included in the configuration.yaml file.
Well, I'm not much into frontend stuff, so I don't know if there is another element than the input_select card that is presenting a drop-down menu. Anyway, for frontend development, check the docs and the repo. You might find so more details.

Hmm, not sure what you mean exactly by creating scenes. Is there an easy way to send JSON requests as a service/switch,etc?
In the long run, I want to have a dropdown that has an effect name and then fires the corresponding JSON command. Is it possible to use the input_select component as a part of the Hyperion component in this capacity?
For example, in the component you use from homeassistant.components.light import ATTR_RGB_COLOR. Is there a from homeassistant.components.light import INPUT_SELCT equivalent with similar usage?
Blue Mood Blobs -  {"command":"effect","effect":{"name":"Blue mood blobs"},"priority":50}
Red Moob Blobs -  {"command":"effect","effect":{"name":"Red mood blobs"},"priority":50}
etc. I can easily get the list of JSON commands.

Components should not use the input_select component for offering their functionality.
I think a good first step would be to make sure the backend works and you can pass in the effect to the service.
Once you did that it would be pretty straight forward to setup an input_select and an automation to call the right effect without updating the frontend / extending the light component.
Adding a dropdown to the light more info means there has to be official support for this in the light component. I however consider this not to be a core feature that other lights would use and wouldn't want to have it added to the light component.

Closing this issue as feature requests should be posted in the forum.


Fix find-by-pattern blocks indefinitely

When the queue is empty, the cursor will start decrementing from 0 and will never stop at 0.
Since car/lrange allows negative values, I leave it unchanged as it is.

Hey @chage, thanks for reporting this bug.
The fundamental issue lies in stopping/terminal condition of scan-seq's recursion: (when-not (zero? next-cursor) (scan-seq ...))
Changing the condition to (when (< 0 next-cursor) (scan-seq ...) should fix this bug.
This bug also caused list-all-queues to run indefinitely. Above fix solves that too.

@chage can you make 2 changes to your PR:

Add the new condition we discussed to scan-seq
Add a small test in goose.brokers.redis.api-test that ensures all Redis APIs recurring over empty list/queue/scheduled-sets return empty results and aren't blocking?

Post that, we can merge it. If you have any other thoughts, do let us know.

Thank you, @olttwa.
I will make the changes you mentioned.
But I don’t think list-all-queues has the same problem. Cause the scan-fn it used directly return the result of car/scan. And SCAN family of Redis will return unsigned 64 bit number (doc). Anyway, I will add test cases, too.
And I want to confirm that if I need to revert my current changes? Because they are redundant if I modified the condition of scan-seq.

@chage you're right about list-all-queues. I was experimenting by changing the (zero? next-cursor) to (neg? next-cursor), and it was blocking for me then. It doesn't block with current setup.
I think we should modify the condition of scan-seq because that's the base recursion used by other functions. Your current changes will be redundant, so you can revert them.


remove wanted list cartridge from captain PDA

About the PR
See title.
Why / Balance
The captain is not security and in general we do not want the captain to be valid hunting. They do not have a sec HUD for the same reason. They still can talk to security over coms and see important updates there if needed.
Technical details
the only difference between BasePDA and BaseSecurityPDA are the installed cartridges
Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes
none
Changelog
:cl:

remove: Removed the wanted list cartridge from the captain's PDA.

Because of course cap doesn’t need to be aware of the serial killer running around their station lmao
But for real this is a pointless change as cap already has access to all the info given in this app via sec comms nor will it stop valid hunting lol
I see zero legitimate reason for removing it.  The sechud puts a big red W on wanted peoples and thus makes them a clear target within seconds of being seen, which is why we don’t want people who shouldn’t be hunting people to have such info, which is not in any way the same as this app, which is merely a reference guide for the crimes that have been going on in the station, info that cap already has access to via the chat log of sec comms.
So yeah the problem this pr aims to solve is already a non-issue, and even if it weren’t a non-issue this change wouldn’t really solve it.

This is not a good change. The Captain should always be aware of everything going on within their station. The Captain is also expected to help all departments when he is needed. Should the Captain actively be seeking for criminals? It honestly depends on Security and their numbers but for the most part no. Should he be able to make arrests when he sees crimes? Yes. The Captain has multiple lethal weapons for a reason. He should 100% keep his program.

The Captain might sometime need to fill in for Medical, yet there is no push for the Captain PDA to have the Med Scanner.
 You have access to the cartridge in the head locker by default, go install the software there.

The Captain might sometime need to fill in for Medical, yet there is no push for the Captain PDA to have the Med Scanner.
 You have access to the cartridge in the head locker by default, go install the software there.

The intention here is to completely revoke it and ban it from Captain and Head of Personnel. I can understand Head of Personnel not ever needing it but if eventually it becomes contraband for Security only then Captains will have a hard time staying in the loop completely. As others have said this could also be used to grant permits for contraband. This PR is attempting to solve an non existent issue besides making Captain do more tedious tasks round start.

The intention here is to completely revoke it and ban it from Captain and Head of Personnel.

Yes. It's not their job.

I can understand Head of Personnel not ever needing it but if eventually it becomes contraband for Security only then Captains will have a hard time staying in the loop completely. As others have said this could also be used to grant permits for contraband. This PR is attempting to solve an non existent issue besides making Captain do more tedious tasks round start.

As one can observe most clearly during NukeOps rounds, contraband is largely an IC issue and there are situations where Command are allowed to use contraband despite not going through the procedure of having explicit permission given. This PR addresses that a Captain should not have access to the Wanted List application by default, but there are situations (such as needing to step in as a Security head) where this can be permitted.
As Captain, you are not supposed to (by default) be in the loop about individual lawbreakers. That is not your role.

As Captain, you are not supposed to (by default) be in the loop about individual lawbreakers. That is not your role.

So the Captain should not be informed of the mass murdering rampages? They should have zero information when it comes to criminals? The Captains job is to literally know everything going on around the station. Captain REQUIRES Security play time. They should know about the power situation and how power is holding up. They should know about all criminals and if Security is properly doing their job. You might as well make it so Captain doesn't have access to Security or have Security comms.

So the Captain should not be informed of the mass murdering rampages? They should have zero information when it comes to criminals? The Captains job is to literally know everything going on around the station. Captain REQUIRES Security play time. They should know about the power situation and how power is holding up. They should know about all criminals and if Security is properly doing their job. You might as well make it so Captain doesn't have access to Security or have Security comms.

I am not going to engage in this conversation further since this comment is wildly extrapolating the consequences of the Captain not having the convenience of a PDA software, when there's still access to Security comms, Crew Records computers and all the other multiple methods of detecting a "mass murdering rampage" that worked just as well before the Wanted List software was even a thing in the game.


fix question mark stripped from url when no params are given (#776)

note: new URL() will return both search and hash with their starting character (? or #) but not when these parameters are empty, including when only their starting characters are given in url
however href keeps them both and this fix relies on that
hrefWithoutHash is technically incorrect when on that edge case with hash, but that doesn't matter here so I haven't wrote a code that doesn't matter in the final result
Fixes #776

See #782


Disable background tap to dismiss

Would be good for future users to know in your documentation they can:
alert.shouldDismissOnBackgroundTap = NO;
to disable the default behavior allowing background tap to dismiss.

@rjpalermo1 thank you for the suggestion. We will update the documentation soon.

@rjpalermo1 we have updated our library with cool new features and have also updated the documentation with it, which also covers use case of shouldDismissOnBackgroundTap property.
Thank you so much :)


test_eigen.py add quaternion example code to test

I think some of the functionality described in the readme may not exist. Adding the example will help clarify.
Here is the traceback from me trying things out in xonsh, a python shell:
$ id_q = eigen.Quaterniond()
$ id_q = id_q.setIdentity()
$ print([float(x) for x in id_q.coeffs()])
xonsh: To log full traceback to a file set: $XONSH_TRACEBACK_LOGFILE = <filename>
Traceback (most recent call last):
  File "/home/ahundt/.local/lib/python3.5/site-packages/xonsh/__amalgam__.py", line 15472, in default
    run_compiled_code(code, self.ctx, None, 'single')
  File "/home/ahundt/.local/lib/python3.5/site-packages/xonsh/__amalgam__.py", line 3634, in run_compiled_code
    func(code, glb, loc)
  File "/home/ahundt/.local/lib/python3.5/site-packages/xontrib/prompt_ret_code.xsh", line 1, in <module>
    from xonsh.tools import ON_WINDOWS as _ON_WINDOWS
AttributeError: 'NoneType' object has no attribute 'coeffs'

@gergondet could you give this a look?

Hi Andrew,
setIdentity() works in place just like the C++ version so id_q = id_q.setIdentity() sets id_q to None. Hence the error you're seeing.
I've force pushed my own patch to your branch that adds the missing Identity static method and actually tests the Quaterniond bindings.

Cool those tests are helpful, thanks!


Add pinch translatable

Would be awesome to be able to translate only with pinch in stead of single finger.

I mean technically it does, it just translates to the focus, which is the halfway point between the two fingers.


Event detail: Related board reports are not showing up

The most recent events do not show related board reports (though previous events do).
The SQL in the view code is not behaving as expected: https://github.com/datamade/la-metro-councilmatic/blob/master/lametro/views.py#L146

Initial Problem
Metro added agendas on July 13, around 2:30 CST. Over two dozen bills (present in Legistar) were not in the opencivicdata database at this time. As a result, the "Related Board Reports" did not render on Event Detail pages.
Preliminary Solution
I manually ran the scraper (twice), around 5:00, with the window option:
pupa update lametro bills window=7
pupa update lametro bills window=500

These scrapes caught nearly all of the missing bills (which were added to the OCD API database at 5:25 pm or 5:45 pm on July 13). The data import in Councilmatic subsequently added these bills to LA Metro.
Still, the related board reports did not render as expected.
Cause and Effect
I turned off the scraper crontasks during the manual execution of the scraper - hence, turning off the events scraper, which creates the related_entities and event items upon which the Councilmatic view depends. After turning on cron again, the event scraper ran, mitigating the issue (like magic).
Root Problem (Unsolved)
Why were these board reports missing? Many have a Legistar MatterLastModifiedUtc timestamp
of July 6, suggesting that the scraper should have scraped the bill on or before that date. Examples:
http://webapi.legistar.com/v1/metro/matters/5039
http://webapi.legistar.com/v1/metro/matters/5022
http://webapi.legistar.com/v1/metro/matters/5073
http://webapi.legistar.com/v1/metro/matters/5124
The Sentry logs do not show any corresponding errors, and the DataMade team did not develop the scraper on this day.

Reference: List of previously missing bills
'2018-0428', '2018-0238', '2018-0351', '2018-0412', '2018-0241', '2018-0389', '2018-0318', '2018-0139', '2018-0291', '2018-0308', '2018-0387', '2018-0441', '2018-0104', '2018-0137', '2018-0140', '2018-0187', '2018-0246', '2018-0339', '2018-0262', '2017-0782', '2017-0810', '2018-0069', '2018-0289', '2018-0342', '2018-0366', '2018-0230', '2018-0409', '2018-0321', '2018-0232', '2018-0368', '2018-0399', '2018-0411', '2018-0393', '2018-0403', '2018-0244', '2018-0388', '2018-0359', '2018-0453', '2018-0422', '2018-0434', '2018-0433'

My current suspicion this issue is caused by Metro making a board report public and that act not triggering an update of "MatterLastModifiedUtc". If that was so, it would explain why our windowed bill scraping seems to be missing these bills.
If that's so, then here are four things that we could do.

if possible have this fixed in the API, so that making a board report public would update "MattLastModifiedUTC".
let DataMade have access to private bills through the API
Scrape all bills nightly
Scrape all bills with high frequency on Friday night

If 1 or 2 happened, we wouldn't need to do 3 or 4. If we can't do 1 or 2, we probably need to do both 3 and 4.
I'm not completely sure that a failure to update "MatterLastModifiedUtc" on making a board report public is the cause.
In order to confirm it we would need to confirm that toggling the public status of a board report does not change "MatterLastModifiedUtc" With LA Metro's cooperation this should be pretty easy. We can choose some old board report that is currently public, ask them to make it private and then make it public again. This isn't the exact test we would like to do, but if "MatterLastModifiedUtc" does not update, we should be pretty confident.
In addition, we should bring in https://github.com/opencivicdata/python-legistar-scraper/pull/74 and make any other necessary changes so that the only unresolved board reports are private reports.

We have a preliminary solution that involves scraping all bills on Fridays, during a designated period of time: https://github.com/datamade/scrapers-us-municipal/pull/22
Metro and DataMade plan to test a couple bills next week to determine how the timestamp correlates with the shift from a "private" to "public" status.

@reginafcompton Re: your questions via email:
Which reports will we test? Metro will create an Agenda with the meeting “Location” field set to “TEST”, and add test reports to this Agenda. Some of the test reports will be set as “Not Viewable Via InSite”.
How will Metro will toggle reports from public to private?

Change an Agenda status to “Final”. (Reports which do not have “Not Viewable Via InSite” checked should become public, and those which do have it check should stay private.)
Uncheck “Not Viewable Via InSite” on a report which was published with this checked.
Check “Not Viewable Via InSite” on a report which was published with it unchecked.

Terrific!
We have a mechanism in place for hiding test events, but not test reports. Will you be doing any "real" data creation in Legistar tomorrow afternoon? If not, then we can turn off the automated scrape, while we test; we'll turn on the scraper, only after you remove the test data from Legistar. Does that work for Metro?
Otherwise, we'll need a way of knowing which bills are "TEST" bills, so we can hide them on the Councilmatic site. (That would require a few hours of development time on our part.)
What we want to learn from this testing
(1) How does toggling a report from private to public affect the MatterLastModifiedUtc timestamp (on the Legistar API)? Be sure to consider all three ways of toggling.
(2) If the timestamp does not change automatically, can Metro manually adjust it at the time of toggle?

Sounds great! There shouldn't be any issue with turning off the scraper while we test.

The test agenda is Board of Directors - Regular Board Meeting, 8/6/2018 at 9:30am.
It has 4 test reports. Two are "Not Viewable Via Insite":
2018-0517
2018-0518
Two are viewable:
2018-0519
2018-0520

We'd like to use BOTH options 3 & 4:
3. Scrape all bills nightly
4. Scrape all bills with high frequency on Friday night
Would it be possible to use the dashboard functionality in #257 to display the error log of agenda items pointing to missing items?

@shrayshray - we implemented the above suggestions a while back:

scrape all bills nightly
scrape all bills once every thirty minutes on Fridays

I made a note about the admin interface in the relevant issue.
Finally, I want to note that our new changes to the scraper, which enable scraping private bills, also help resolve this issue.
I think we can close this one! Let me know.


update keys script to use core release artefacts

after https://github.com/penumbra-zone/penumbra/issues/4130 https://github.com/penumbra-zone/penumbra/issues/4195 it is possible to download a tarball containing keys with checksum in the release manifest, rather than a curling a glob and checking a manually-generated manifest.
keys script should transition to using the official release artefact.

moved to todo since we discussed in sprint but the issue didn't actually exist

Not a high priority, can revisit this after mainnet


Identify potential contributors and add them to the admiral repository

[ ] Ask on #admiral slack who would be interested to be a contributor.
[ ] Collect GitHub user names to add them to the Repo with the right privileges
Optionally:
[ ] Advertise some of the "good first Issues"
[ ] Ask to create their own issues if they see gaps or have ideas

@kabis-ops Can this be closed?

Hi @thomas-neitmann , for the 1st contributor yes. But there may be others? Please feel free to close.


Too many classes in --main-dex-list, main dex capacity exceeded

Describe the bug
I've been trying to integrate Material UI in MIT Appinventor. I've updated a variety of libs to support the material library. Now, I've been facing some errors in compilation.
Affects

[ ] Designer
[ ] Blocks editor
[ ] Companion
[x] Compiled apps
[x] Buildserver
[ ] Debugging
[ ] Other... (please describe)

Expected behavior
The compilation should've worked normally and should'nt have caused any issue since MIT Appinventor has Multidex.
Steps to reproduce
Implement a bunch of libraries and it will exceed the limit of dx tool.
Stack Trace
     [java]
     [java] UNEXPECTED TOP-LEVEL EXCEPTION:
     [java] com.android.dex.DexException: Too many classes in --main-dex-list, main dex capacity exceeded
     [java]     at com.android.dx.command.dexer.Main.processAllFiles(Main.java:548)
     [java]     at com.android.dx.command.dexer.Main.runMultiDex(Main.java:368)
     [java]     at com.android.dx.command.dexer.Main.runDx(Main.java:289)
     [java]     at com.android.dx.command.dexer.Main.main(Main.java:247)
     [java]     at com.android.dx.command.Main.main(Main.java:94)
     [java]
     [java] Apr 16, 2023 5:48:23 PM com.google.appinventor.buildserver.Compiler setProgress
     [java] INFO: The current progress is 75%
     [java] Apr 16, 2023 5:48:23 PM com.google.appinventor.buildserver.Compiler runMultidex
     [java] INFO: DX time: 11.006000 seconds
     [java] Apr 16, 2023 5:48:23 PM com.google.appinventor.buildserver.Compiler runMultidex
     [java] WARNING: YAIL compiler - DX execution failed.

BUILD FAILED
C:\Users\Rudra\Documents\sources-beta\appinventor\build.xml:22: The following error occurred while executing this line:
C:\Users\Rudra\Documents\sources-beta\appinventor\buildserver\build.xml:200: Java returned: 1

Total time: 45 seconds
PS C:\Users\Rudra\Documents\sources-beta\appinventor>

You only need to put the classes into the main dex list required to get the application up and running, at which point multidex will take care of loading the remaining dex files (and on newer versions of Android this is all handled at install time). It sounds like you may have overdone it.

@ewpatton I've just upgrade the android libraries. Seems like with newer versions of android apis, like sizes and functions have increased. In my local instance, I've fixed this with implementation of D8 somehow.

It's good that you were able to resolve the issue with your changes.


Saving tab groups

This is a phenomenal extension :-)
However, I'm missing a feature for saving tab groups persistently.
Once the tab group is closed, it's gone forever. I would like to have the ability to save it for later, even if I close it.

Hey @dmurat-croz, glad you like it!
You can achieve this already using bookmarks. You can create a bookmark folder and then right click the folder and select 'Open All in New Tab Group' - this will also give the group a similar name as the bookmark folder.

tnx for tip


Update existential deposit for XCM transfer feature & transaction history

Description

Not show a warning if your balance < existential deposit
Show incorrect fee in the transaction history in case of user send fund/xcm transfer when balance < existential deposit

To do

[x] Update existential deposit for XCM transfer feature
[x] Update fee value on transaction history for this case

To be resolved after architecture update

Add the validate when xcm transfer in the new UI version


Ripple effect on list items [Enhancement]

Short description of the problem:
On beta.11 I was able to use buttons inside list, but seems like it's no longer working on RC.X
What behavior are you expecting?
Be able to see ripple effect like in native lists when tapping an element.

Did you checkout the changelog? https://github.com/driftyco/ionic/blob/master/CHANGELOG.md#new-behavior-of-button

Ohh closing this, thanks!


Improve none net 6 behavior

Have removed conditional compilation code by bumping dependency

@thompson-tomo thanks!


[nctl] NDRS-523: misc enhancements

Added new nctl-view-* commands to view on chain information.
Streamlined node-start command.
A few other miscellaneous changes.

bors r+

bors r-

Cancelled as I have not updated the nctl docs.  Doing that now.

bors r+


Unhandled Null Reference Exception

Hi, I've been using your nice library for a while now and just today we had an issue where we couldn't start one of our windows services that is using this ssdp lib. It was crashing with an unhandled exception being logged in Event Viewer:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Discovery.SSDP.MessageParser.GetNotifyMessage(System.Collections.Generic.List`1<System.String>)
at Discovery.SSDP.MessageParser.Parse(Byte[])
at Discovery.SSDP.Agents.AgentBase.ParseResponse(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
I've got a feeling there might be some other SSDP software on our network that is trying to discover its server by broadcasting out the "M-SEARCH * HTTP/1.1" string on port 1900. Looking at your code in the MessageParser class it looks like this might be causing the issue in GetNotifyMessage.
Changing this ssdp lib to use a different port fixed the problem, so it looks like when it uses the default 1900 port it's not handling messages received from other SSDP clients properly.

Thanks for taking the time to get in touch with me. I think i noticed this
bug when working on a new version. I'll take a look & see if I can track
down the issue.
Thanks again
Simon
On Wed, 27 Mar 2019 at 01:44, shaneh20<EMAIL_ADDRESS>wrote:

Hi, I've been using your nice library for a while now and just today we
had an issue where we couldn't start one of our windows services that is
using this ssdp lib. It was crashing with an unhandled exception being
logged in Event Viewer:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at
Discovery.SSDP.MessageParser.GetNotifyMessage(System.Collections.Generic.List`1<System.String>)
at Discovery.SSDP.MessageParser.Parse(Byte[])
at Discovery.SSDP.Agents.AgentBase.ParseResponse(System.Object)
at
System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at
System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object, Boolean)
at
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object, Boolean)
at
System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
I've got a feeling there might be some other SSDP software on our network
that is trying to discover its server by broadcasting out the "M-SEARCH *
HTTP/1.1" string on port 1900. Looking at your code in the MessageParser
class it looks like this might be causing the issue in GetNotifyMessage.
Changing this ssdp lib to use a different port fixed the problem, so it
looks like when it uses the default 1900 port it's not handling messages
received from other SSDP clients properly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/simongh/Discovery/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZ7T-sf4dZCJpMHwpfS_C1UMLKU8-dmks5vas0RgaJpZM4cMx2j
.


Debugger: Provide a helpful error when invalid connectUnderReset used

Fixes: https://github.com/probe-rs/vscode/issues/85
@Tiwalun This feels like a rather cumbersome way of propagating information about an error from the api to the application.
Is there a better approach than I took here?

I made changes to auto-handle invalid connect under reset in #1259 , specifically to session.rs and target.rs.
That code is no longer in the repo, and I can't find the PR (and reasoning) behind removing it. Can anybody help me with history please?


We don't have any RNA yet.

Use the Monarch RNA miniprep kit to extract mRNA from cell samples.
Product Info
Protocol Video

We have Total RNA and from WT HEK293T cells now.


Netlify/redirect3

👷 Deploy Preview for marvelous-chaja-fe3071 processing.

Name
Link

🔨 Latest commit
c1131a95f7ed33eb62b715f74be3131523bfa0a7

🔍 Latest deploy log
https://app.netlify.com/sites/marvelous-chaja-fe3071/deploys/642e20c37f41920007e05d32


Fix handling list params

default style and explode for params with various values of in
serialize values accordingly

fixed in lapidary-base


workspaces working in dev

In an effort to get hooks working across all of our application, I hit the stumbling block of React not being the same instance of react on the client when rendering from commonvs catalogue|content.
FYI: https://github.com/facebook/react/issues/13991
This made me think that we could probably get around this using workspaces.
Workspaces also make dependency management a bit nicer, it also remove the linkweco step, which is a bit odd.
It does however mean you need to run yarn from the root now, which slightly coupley, but  the apps are coupled to common.
This did make me wonder if we had a ./apps folder with content, common, and content in. Thoughts? Could be adding layers for nothing, or nicely compartmentalised?
There was some Sass resolving issues, but as we're moving away from Sass, the hack felt fine.

I've done a test, and this now means the react us the same version, so we're back in action with hooks.

I think it might be good to have a ./apps folder with the others inside

Let's pair on that so we can see if it feels right.