Exhaustive match does not work for case methods.

When implementing exhaustive match in #1891, I had intended to include case methods in the implementation, even though they weren't mentioned in the original RFC. However, case methods proved to add a significant additional challenge of their own on top of the original challenge, and I opted to punt and skip case methods for now.
The central issue is that exhaustive match detection happens in the expr pass (because types are resolved and available for all constituent expressions), but case method desugaring happens in the casemethod pass, which comes prior.
When desugaring a case method, we need to know whether to add an implicit None into the union of the return value type, but we cannot know this without doing exhaustive match detection, which happens later.
I also think we'd run into problems if we tried to add or remove the None from the return value later in the expr pass - I don't think we can mutate any method return types in the expr pass because some calls to that method may have already been typechecked.

General statement from me during sync: without this, case methods aren't particularly useful. So we should definitely solve this or remove case methods.

@sylvanc @Praetonus @plietar - would it be true that any case method that has no guards would be exhaustive by definition?  That is, if the param type of the wrapper method is the union of the argument types, then any case method with no guards in any of the cases will always be exhaustive, right?
That seems intuitively true to me, but if it's also formally true, we can at least have exhaustive case methods when there are no guards. Which would help with a lot of situations, at least.

@jemc Your reasoning looks correct to me.
I think we should move case methods handling to a later pass, probably between the traits and docs passes. This will also be needed in order to implement method specialisation (because specialisation must be handled before case methods, and specialisation requires type information). Doing this would solve the two problems at once.

Case methods don't do what I'd like them to do, at the moment. They are not very strictly typed. For example:
actor Main
  new create(env: Env) =>
    foo("hi", 1)
    foo(1, "hi")
    foo("hi", "hi")
    foo(1, 1)

  fun foo(a: String, b: U32): String => "1"
  fun foo(a: U32, b: String): String => "2"

That program type checks, when clearly the last two calls to foo should not type check. As a result, the return type of the aggregate foo is currently (String | None).

Another way in which case methods can be weird :
actor Main
  fun foo(a: String): String => "1"
  fun foo(a: U32): U32 => "2"

I agree that @sylvanc's example is rather undesirable behaviour. @plietar's example seems downright buggy, though I understand why it works that way, based on how it's currently implemented.
I think we need to collaborate to come up with a general idea for what we want case methods to actually be, then someone can write up an RFC with the details of the necessary changes.

I think we should move case methods handling to a later pass, probably between the traits and docs passes

I'm not sure what the implications of such a change are, but as they are currently implemented, case methods have the advantage that they are simply syntax sugar. This means a bug in their implementation would be caught by the type checking pass, rather than cause unsoundness.
While bugs in a compiler pass are never desirable, not being able to cause unsoundness is always a good thing. For instance @sylvanc's example, in a situation where exhaustive case methods were implemented in a "obvious naive" way, in a later stage of the compiler than type checking, would be unsound.

@plietar That's a very legitimate concern, and it is part of the reason why I suggested to move case method handling to that specific place.
There are two main "events" in the compiler passes regarding types.

After the traits pass, the relations between types are fully known. In other words, is_subtype will always return the correct result once this pass is done.
After the expr pass, the type of every expression in the program is known and guaranteed to be safe (assuming no bugs in the implementation).

This means that a pass which requires full type information could be placed after the traits pass, because any correctness issue would be catched by the expr pass. But you're right, generally speaking the expr pass should be the last mutating pass.
Also, @sylvanc's and @plietar's examples made me realise that moving case methods handling after the traits pass wouldn't solve many problems, including these ones. I suspect a better approach would look like this:

In the sugar pass or somewhere near it, collect every method of a type with the same name in a new AST kind (something like TK_FUNSET).
The scope and traits passes should be updated to handle method sets correctly. These would probably be minor changes.
In the expr pass, typecheck each member of the method set separately (solving @plietar's problem) and build a TK_FUNSETREF of the members of a method set that a call could possibly refer to, and issuing a compiler error if there is none (solving @sylvanc's problem). Exhaustive match would also be handled here.
The method set and associated match expression can then be handled during reachability and code generation, with a lot of potential optimisations like reaching each member of the set separately and eliding the match expression if the call isn't ambiguous.

This would add some substantial complexity to the compiler, particularly by making case methods visible all the way through the compilation chain instead of having them as sugar, but I think it's the best way to solve the issues raised so far with them. Also, method specialisation could be added almost seamlessly on top of this.

Also, method specialisation could be added almost seamlessly on top of this.

Yeah, I think that's the core sell here - most of this is work that probably needs to be done anyway for method specialization.  I endorse it.

On a side note, I wonder if we should force all case methods to be exhaustive?  That is, stop adding an implicit None-returning default case, and raise an error if the overall match is not exhaustive.  Honestly, I think the implicit None-returning default case for case methods causes more confusion than help - if it's ever wanted it can be added explicitly.

On a side note, I wonder if we should force all case methods to be exhaustive? That is, stop adding an implicit None-returning default case, and raise an error if the overall match is not exhaustive. Honestly, I think the implicit None-returning default case for case methods causes more confusion than help - if it's ever wanted it can be added explicitly.

I'd second that. I don't really see a use case for non-exhaustive case methods anyway except to save one an additional match at runtime but that doesn't sound like something very common.

I've been thinking a lot about this and how the ideal handling of case methods would work, and it's basically exactly what @Praetonus described in https://github.com/ponylang/ponyc/issues/1893#issuecomment-302285393.

Do you want to handle it @jemc?

Not particularly :wink:, but if you don't have time for it, I might have to dive in - did you already make some progress on specialisation that I could start from, or has it all been conceptual work up til this point?

I do have time for it, I just thought you had some ideas on how you'd like implementation details to be since you've been thinking about the issue. In that case I'll start working on it in the coming days.
Also, assuming that the bugs raised by @sylvanc and @plietar are going to be fixed, do we still need to discuss whether we want to remove case methods altogether?

I started working on the implementation and there are several properties of case methods that seem rather strange to me. Here are the changes I'm proposing:

Type parameter constraints: currently, the constraints from every instance of a case method are intersected to create the constraint of the match method. This doesn't really have any use case since this constraint will be the most common type anyway. I'm proposing that every instance of a case method should define the same constraint for a given type parameter
Type parameter defaults: currently, only one instance of a given case method can define a default for a given type parameter. Since that default will be used anyway by the match method, I'm proposing that, in the same way as constraints, a default type parameter should be defined in the same way by every instance of a case method
Parameter defaults: currently, only one instance of a given case method can define a default for a given parameter. This has a lot of different issues. In particular:

The default argument will be used by all other instances of the case method. We can't chose to ignore the default argument based on the called instance since default arguments are resolved at compile-time and case method calls are resolved at runtime
It is possible to have a default argument that doesn't satisfy the guard of its case method instance, which is problematic for exhaustive match
For these reasons I'm proposing to simply disallow default arguments on case methods

Does anybody have any objections to these changes?

Sounds right to me. The only change to those rules I think we should consider is:
Instead of disallowing case method cases from using different type parameter constraints, we could think of it as a different way to implement #1410. That is, we could allow them to be different, and use that as a way to refine the selection of possible candidates from the TK_FUNSET.
So instead of this:
fun [A: (B | C)]apply(a: A) iftype A <: B => // ...
fun [A: (B | C)]apply(a: A) iftype A <: C => // ...

We would have this:
fun [A: B]apply(a: A) => // ...
fun [A: C]apply(a: A) => // ...

Arguably this is a more succinct syntax for arriving at the same conclusion.

That makes sense @jemc.
However, since the implementation would be roughly similar to #1410, I'm going to hold off on implementing that rule for now, and implement it at the same time as part of #1410. In the meantime, I'll use the rule disallowing differring constraints.

I think we also need to discuss how we want case methods (and method specialisation) to work with method default implementation from traits. For example
trait T
  fun foo(x: U32) => None

class C is T
  fun foo(x: U64) => None

Here, should we add the version of foo from T to C, resulting in C.foo being a case method, or should we say that C doesn't provide T?
Some more complicated cases also raise different issues, like this one
trait T1
  fun foo(x: U32, y: Any) => None

trait T2
  fun foo(x: Any, y: U32) => None

class C is (T1 & T2)

Here, to which implementation should a call to C.foo(U32(0), U32(0)) dispatch to? One possibility would be to use the order of the provides list, i.e. to use the one from T1 here. Another possibility would be to treat the case method as ambiguous and issue a compilation error. We could also extend those ambiguous cases to plain match expressions but maybe that would be taking it a step too far.
There also are problems with guards
trait T1
  fun foo(x: U32) if x < 20 => None

trait T2
  fun foo(x: U32) if x > 10 => None

class C is (T1 & T2)
  fun foo(x: U32) => None

A call to C.foo would be ambiguous if the argument is between 11 and 19, and that ambiguity seems hard to detect at compile-time.

Discussed on today's sync.
@SeanTAllen is going to file an RFC to remove case methods as they currently exist. If we want a different case method semantics in the future after that, they could be added as a new feature.


Microsoft.Extensions.Logging.Abstractions not marked CLSCompliant

The Microsoft.Extensions.Logging.Abstractions assembly is missing the CLSCompliant(true) attribute. Is there a reason for this, or was this merely an accidental omission?

@PavelSafronov do you have a use case to have this attribute in the Logging repo?

The use case is writing a CLS-compliant library which uses or extends Microsoft.Extensions.Logging.Abstractions.
Is there a reason not to have this attribute?

ran into this today. we may drop clscompliant from our own library but it would be nice to not be forced to make the choice

@muratg I think it is about consistency most of all. I got asked to add that back to my libraries although it has very little value I think?! But some Microsoft.* or aspnet core packages actually do have that set.
https://github.com/search?p=7&q=org%3Aaspnet+CLSCompliant&type=Code
https://github.com/search?l=C%23&q=org%3Adotnet+CLSCompliant&type=Code
Personal opinion: Wouldn't be too bad if everyone would just drop it, kinda annoying to care about it (in static code analysis) ;)

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Failure in htex init blocks vs monitoring test in CI

Describe the bug
I saw this in a superficially-unrelated PR #3286
2024-03-24T10:16:18.0960186Z parsl/tests/test_monitoring/test_htex_init_blocks_vs_monitoring.py .F
2024-03-24T10:16:18.0960831Z
2024-03-24T10:16:18.0961086Z =================================== FAILURES ===================================
2024-03-24T10:16:18.1023586Z ____________________________ test_row_counts[none] _____________________________
2024-03-24T10:16:18.1024233Z
2024-03-24T10:16:18.1025500Z tmpd_cwd = PosixPath('/home/runner/work/parsl/parsl/.pytest/parsltest-current/test_row_counts_none_-bqmyez8f')
2024-03-24T10:16:18.1026682Z strategy = 'none'
2024-03-24T10:16:18.1026952Z
2024-03-24T10:16:18.1027125Z     @pytest.mark.local
2024-03-24T10:16:18.1027956Z     @pytest.mark.parametrize("strategy", ('none', 'simple', 'htex_auto_scale'))
2024-03-24T10:16:18.1028832Z     def test_row_counts(tmpd_cwd, strategy):
2024-03-24T10:16:18.1029561Z         # this is imported here rather than at module level because
2024-03-24T10:16:18.1030543Z         # it isn't available in a plain parsl install, so this module
2024-03-24T10:16:18.1031425Z         # would otherwise fail to import and break even a basic test
2024-03-24T10:16:18.1032096Z         # run.
2024-03-24T10:16:18.1032462Z         import sqlalchemy
2024-03-24T10:16:18.1033307Z         from sqlalchemy import text
2024-03-24T10:16:18.1033992Z
2024-03-24T10:16:18.1034479Z         db_url = f"sqlite:///{tmpd_cwd}/monitoring.db"
2024-03-24T10:16:18.1035221Z         parsl.load(fresh_config(tmpd_cwd, strategy, db_url))
2024-03-24T10:16:18.1035839Z
2024-03-24T10:16:18.1036168Z         this_app().result()
2024-03-24T10:16:18.1036583Z
2024-03-24T10:16:18.1036918Z         parsl.dfk().cleanup()
2024-03-24T10:16:18.1037370Z         parsl.clear()
2024-03-24T10:16:18.1037758Z
2024-03-24T10:16:18.1038153Z         engine = sqlalchemy.create_engine(db_url)
2024-03-24T10:16:18.1038775Z         with engine.begin() as connection:
2024-03-24T10:16:18.1039302Z
2024-03-24T10:16:18.1039945Z             result = connection.execute(text("SELECT COUNT(DISTINCT block_id) FROM block"))
2024-03-24T10:16:18.1040796Z             (c, ) = result.first()
2024-03-24T10:16:18.1041504Z             assert c == 1, "We should see a single block in this database"
2024-03-24T10:16:18.1042205Z
2024-03-24T10:16:18.1043226Z             result = connection.execute(text("SELECT COUNT(*) FROM block WHERE block_id = 0 AND status = 'PENDING'"))
2024-03-24T10:16:18.1045240Z             (c, ) = result.first()
2024-03-24T10:16:18.1045913Z >           assert c == 1, "There should be a single pending status"
2024-03-24T10:16:18.1046767Z E           AssertionError: There should be a single pending status
2024-03-24T10:16:18.1047448Z E           assert 2 == 1
2024-03-24T10:16:18.1047742Z
2024-03-24T10:16:18.1048245Z parsl/tests/test_monitoring/test_htex_init_blocks_vs_monitoring.py:78: AssertionError

Inspecting the artifacts (monitoring.db and log files), it looks like there is a PENDING status recorded in the database for two different run IDs. In database_manager.log:
2024-03-24 10:16:12.037 database_manager:619 [INFO] [Monitoring-migrate-block<PHONE_NUMBER>49024] Will put [{'run_id': '3fde70cb-ce68-4473-af86-874f65ae156f', 'status': 'PENDING', 'timestamp': datetime.datetime(2024, 3, 24, 10, 10, 56, 544680), 'executor_label': 'htex_Local', 'job_id': '18046', 'block_id': '0'}] to pending block queue
...
2024-03-24 10:16:12.164 database_manager:619 [INFO] [Monitoring-migrate-block<PHONE_NUMBER>49024] Will put [{'run_id': '72783ebc-417e-4890-903d-683150696422', 'status': 'PENDING', 'timestamp': datetime.datetime(2024, 3, 24, 10, 16, 12, 162436), 'executor_label': 'htex_local', 'job_id': '27303', 'block_id': '0'}] to pending block queue

The run for this test is 72783ebc-417e-4890-903d-683150696422 so the first PENDING message (with run ID  3fde70cb-ce68-4473-af86-874f65ae156f) is for the wrong run
sqlite> select * from block;
3fde70cb-ce68-4473-af86-874f65ae156f|htex_Local|0|18046|2024-03-24 10:10:56.544680|PENDING
72783ebc-417e-4890-903d-683150696422|htex_local|0|27303|2024-03-24 10:16:12.162436|PENDING
72783ebc-417e-4890-903d-683150696422|htex_local|0|27303|2024-03-24 10:16:12.219174|RUNNING
72783ebc-417e-4890-903d-683150696422|htex_local|0|27303|2024-03-24 10:16:14.789575|CANCELLED

That bad pending message is from a run around 6 seconds before.
None of the other monitoring.db databases in this test run contain any other reference to that bad 3fde7... workflow run, and in the relevant run for that bad run, it looks like the monitoring router hung on startup:
$ cat runinfo/008/monitoring_router.log
1711275051.469708 2024-03-24 10:10:51 Monitoring-Router-Process-18007 MainThread-140017148053312 monitoring_router:85 __init__ INFO: Initialized the UDP socket on <IP_ADDRESS>:55055
1711275051.470886 2024-03-24 10:10:51 Monitoring-Router-Process-18007 MainThread-140017148053312 monitoring_router:203 router_starter INFO: Starting MonitoringRouter in router_starter
$

so then the ZMQ layer would likely have sat around in the pytest processing continuing to try to asynchronously sent a monitoring message - and eventually it would have found one.
So two pieces to this issue:
i) monitoring startup hung without failing the test - this is, in some part, a (mis?)feature of the original monitoring design, based I think on lack of confidence in monitoring code turning into "we can't let broken monitoring break 'real' parsl"
ii) this is the monitoring version of htex issue #2199 - components from one run can connect to the components from another run

The reason that monitoring router did not continue to log stuff is not because of a hang, but because this 3fde7... run is a test of killing monitoring components - so it killed the monitoring router deliberately. So this test is successfully detecting (although presenting it in a very awkward way) some misbehaviour around there.


Update raw data

Adds a command to be able to update the files attached to a raw data object - similar to what we have for update preprocessed data.
This is needed to update the EMP data uploaded at the beginning of Qiita, and this can be useful for any future problems.
@antgonza able to review?

My only concern is that update_raw_data_from_cmd overwrites (deletes) old raw data, should we have a parameter or confirmation for this? Note that I understand why this behavior is required for the current situation but not sure we want to have it in the future.

Is it worthwhile to add a note the change log?

@ElDeveloper I've addressed all your comments.
@antgonza That is not the route that we used for the update_preprocessed_data. Note that here it is not removing the data, is actually moving it to the uploads folder, so we are not loosing any data.
This is part of the CLI which is supposed to be used by advanced users/

Thanks @josenavas, it looks good to me now!
On (Sep-30-15|16:02), Jose Navas wrote:

@ElDeveloper I've addressed all your comments.
@antgonza That is not the route that we used for the update_preprocessed_data. Note that here it is not removing the data, is actually moving it to the uploads folder, so we are not loosing any data.
This is part of the CLI which is supposed to be used by advanced users/

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/1482#issuecomment-144569838

:+1:


Show the yellow dot

please see the screenshot

@Kammy6679
Could please provide steps to reproduce?

When you log in, the dialog box will pop up. you will see the the yellow dot in the dialog.

Could you please provide more details?
what OS do you use?
what gcc version do you use?
what qt version do you use?
did you build source code from master or dev branch?

@v-vlshch , This is my bug, not RMS SDK. Thank you for your help.


Solved the problem when we have an array with inner array and need co…

Problem with an array has another inner array and needs copy the values.
Issue #23  : What you think about this

Hi,
Can you please merge this pull request. I have similar issue and this change will solve it.
Thanks,

Sorry for the delay guys
If you want, we might need some help maintaining the project.


Multi language support

In particular German was suggested.
Also Latin (though I don't believe Wordle supports Latin yet, but I bet we could PR that one too : )

Intent is to use a LANG=... override, similar to how we added support for controlling whether or not system dictionaries were used in 063a71bfa0a80b4165d88f42acc007b99da19170.


related-links in pdf2 should not generate links to unreferenced topics

I could not find an issue for this and I'm unsure, whether this a desired behavior. So I do not know, whether this is a bug report or an enhancement request.
tl;dr: We use keymaps to define keys once and then refer to those maps to propagate the keys to use them in publication maps. Unfortunately, the related-links mechanism, as it is implemented, does not care for, if a topic is referenced in a map, it looks for, whether the key is defined and then processes it. This creates link stubs, see screenshot.
DITA-OT: 2.3.2
transformation: pdf2
samples: related-links-issue.zip

Explanation
This is the publication map map.ditamap. It has a link to the key map and refers to chapter1 and chapter2 but not to chapter3.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map>
  <title>DITA Topic Map</title>
  <topicref>
    <mapref href="keymap.ditamap" toc="no" format="ditamap"/>
  </topicref>
  <topicref keyref="chapter1"/>
  <topicref keyref="chapter2"/>
</map>
```

The **keymap.ditamap** defines keys for all 3 topics:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map>
  <title>Keymap</title>
  <topicgroup>
    <keydef keys="chapter1" href="chapter1.dita" processing-role="resource-only"/>
    <keydef keys="chapter2" href="chapter2.dita" processing-role="resource-only"/>
    <keydef keys="chapter3" href="chapter3.dita" processing-role="resource-only"/>
  </topicgroup>
</map>
```

The **chapter1** topic has related links to **chapter2** and **chapter3**, but, because **chapter3** is not referenced in the map, the related link should not be generated.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="topic_kky_2y5_kx">
  <title>chapter1</title>
  <shortdesc>chapter1 is defined on keymap and referenced in map.</shortdesc>
  <related-links>
    <link keyref="chapter2"/>
    <link keyref="chapter3"/>
  </related-links>
</topic>
```

I agree--related links should only reflect links to normal-role topics.

Same applies to xhtml:


experiment w/ atomic/thread-safe approach to passing Geth L1 timestamps an…

When accessing blockNumbers and timestamps in memory, might be safer access them via one function and store them as an atomic.Value{}. The worry is that by having separate setters and getters, there might be situations in which a process changes the timestamp after the blockNumber is returned, leading to a corrupted {timestamp,blockNumber} pair being passed to later functions and data structures.
Experimental approach:
safeTimeBlock: atomic.Value{},

// Log the OVMContext information on startup
stb := service.safeTimeBlock.Load().(OVMContextT)
log.Info("Initialized Latest L1 Info Safe", "stb.timestamp", stb.timestamp, "stb.blocknumber", stb.blockNumber)

Current approach code snippets:
func (s *SyncService) GetLatestL1BlockNumber() uint64 {
    return atomic.LoadUint64(&s.OVMContext.blockNumber)
}
...
ts := s.GetLatestL1Timestamp()
bn := s.GetLatestL1BlockNumber()

Codecov Report

Merging #163 (fad7b35) into develop (703c617) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #163   +/-   ##
========================================
  Coverage    86.05%   86.05%
========================================
  Files           49       49
  Lines         1936     1936
  Branches       307      307
========================================
  Hits          1666     1666
  Misses         270      270

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 703c617...fad7b35. Read the comment docs.

Was a dead end - root problem addressed by #210


[WIP] @orta => Use Fastlane for automated deploys

Fixes #359.
Need to get the following up and running:

[x] Tests running
[x] OSS install running
[ ] Signing
[ ] Updates version/build numbers
[ ] Generates release notes from CHANGELOG
[ ] Deploys to Hockey
[ ] Post-deploy slack notifications
[ ] Remove Makefile
[ ] Update README

nice work on the keys

Thanks – took the extra time to get it "Orta" right.

So this is ready to go; tests pass locally.

Somehow changing from using a Makefile to Fastlane to invoke xcodebuild for tests broke Travis again. Getting the following error:
iPhoneSimulator: Unable to connect to "com.apple.instruments.deviceservice.lockdown" (Error Domain=com.apple.CoreSimulator.SimError Code=146 "Unable to lookup in current state: Shutdown" UserInfo=0x7fb04b468750 {NSLocalizedDescription=Unable to lookup in current state: Shutdown})
iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.

I am so tired of these failing CI tests.
Tomorrow, if I'm feeling adventurous, I might try reverting to just using .travis.yml to run tests instead of going through any other tools ¯_(ツ)_/¯ But that'll be in a separate PR.

It'd be awesome to have @KrauseFx give it a one-over, too.

It's back to this, eh?

This looks pretty cool! :+1: I'm not yet sold on the changelog part. Maybe you should use YAML or a different system to store them?
Once this is in production, I'd love to link to eidolon on the fastlane project page.

None of my opinions are blockers. I'm happy to have this merged whenever.

:+1:

This is a great reference for setting up fastlane :+1:


Doesn't Seem to Work on W3.org MathML Examples Page

I'm new to the MathML field, and don't have any great experience yet, but your extension doesn't seem to work on https://www.w3.org/Math/XSL/csmall2.xml. Sorry if I'm jumping at shadows, I may be misunderstanding things.
Thanks

@plwvicuni sorry for the late reply. This issue seem to be related to the https://github.com/andrusha/mathml-chrome/issues/7 as well as the way mathml is setup on this page. I might give a close look to it eventually, but hadn't had time to do it.

The 2.0 should address this problem partially

I am using 2.0 in latest Google Chrome; none of the three examples in the link works properly. Do you need a screenshot?

Yea, it would help to debug it if you tell me:

What did you do?
What did you expect to happen?
What actually had happend?

I just went to https://www.w3.org/Math/XSL/csmall2.xml mentioned above, and "What your browser displays" seems different from "Suggested sample rendering". Latest Chrome. This extension is enabled there (tick is green).

The problem seems to be Chrome trying to render math tags itself, before mathjax gets to hold on them (or its not recognizing mml:math). I played a bit with the config, but did not find easy solution.
Those links could have some clues:
http://docs.mathjax.org/en/latest/mathml.html
http://docs.mathjax.org/en/latest/options/mml2jax.html
http://docs.mathjax.org/en/latest/config-files.html#the-tex-mml-am-svg-configuration-file

Should this be submitted as a Chrome bug?


fix txn token,dc and consistency

fixes #148

added auto-decode for values

Hi @amuhametov, Thank you for your PR! I will review your PR soon. Stay tuned!

@amuhametov, I have added comments to your PR. In short, doc strings needs to be updated plus I suggest to hide encoding/decoding into method logic. After this encoding and decoding are transparent to user similarly to current KV put() method logic. This can break API backward compatibility. If nobody is against I prefer to move in this direction.

@matusvalo are you sure we should break API?
I think it is wrong to annoy users. Rolled back API change.

@cablehead @matusvalo guys?

ping

welcome to here


[release/1.5] cherry-pick: Allow git commands in Vagrantfile

Due to a git CVE, we need to mark /vagrant as a "safe" directory
otherwise building containerd inside Vagrant fails with git command
failures.
Cherry-pick of #6941
Signed-off-by: Phil Estes<EMAIL_ADDRESS>

/test pull-containerd-build

Looks like some auth issue with the prow-managed jobs (well, the build one at least):
gcloud auth activate-service-account --key-file /etc/service-account/service-account.json --project=k8s-cri-containerd
ERROR: (gcloud.auth.activate-service-account) There was a problem refreshing your current auth tokens: ('invalid_grant: Invalid JWT Signature.', {'error': 'invalid_grant', 'error_description': 'Invalid JWT Signature.'})


CLI command groups in preview cause $? to be false even when they succeed when CLI invoked from PowerShell

When calling Azure CLI commands from a PowerShell host, command groups which are in preview appear to report that information to stderr which (presumably) causes PowerShell to think that the az command failed, whether or not it actually did. This makes it difficult to determine the success or failure of az commands.
$LastError reports 0, but $? reports false
Command Name
Example, as of today, is az monitor log-analytics workspace create, which is currently in preview.
Errors:
Creation of the workspace completes successfully, but the PowerShell host thinks that it failed because the following message is (presumably) written to stderr:
az : Command group 'monitor log-analytics workspace' is in preview. It may be changed/removed in a future release.
At C:\scripts\PrepOMSWorkspace.ps1:62 char:7
+ $la = az monitor log-analytics workspace show --resource-group $Resou ...
+       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Command group '...future release.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

To Reproduce:
$la = az monitor log-analytics workspace create --location eastus2 --resource-group someresourcegroup --workspace-name myvault 2>$null
$success=$?
$le=$LastExitCode
Write-Host "Success? $($le) $($success)"
Write-Host $la

Expected Behavior
Success 0 true (if it worked)
today it returns
Success 0 false
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.5.1

Extensions:
application-insights 0.1.7
azure-devops 0.18.0
interactive 0.4.4
subscription 0.1.3

Additional Context

Closing this because --only-show-errors from #6341 provides the desired behavior by leaving out warning text.
Made a suggestion that this should be included in the global parms list in #13384


Arkworks cargo install does not seem to work reliably

using cargo install to install the binary from the local path, seems to trigger a method not implemented error in arkworks.
The workaround for this was to:

cargo build to create the binary
copy binary into the PATH
chmod +x /path/to/binary if it is sometimes seen as a text file

@brson has correctly noted that using --locked fixes this.
To close this issue, the documentation should be updated to reflect this.

Closing as documentation has been updated in the book.


Upload keeps failing

I have tried a couple of times, but this 1 upload for evansport keeps failing. Is there anything wrong server side?
https://github.com/Safihre/spksrc/actions/runs/4916395862

AFAICS sabnzbd v4.0.1-61 for evensport-7.1 was sucessfully uploaded and is visible under https://synocommunity.com/package/sabnzbd
direct link to download https://packages.synocommunity.com/sabnzbd/61/sabnzbd.v61.f42661[evansport].spk

Strange, all builds failed with timeouts..


Use HTTP and gRPC guides as the entry point

Users are confused by the low-level API due to the significant
highlight on the README. Document the HTTP and gRPC guides as
the main entry points and reduce the number of low-level API
snippets.

@bogdandrutu, this structure is what I was suggesting.


How to inject dependencies into a query create filter?

Hi,
I've been trying to set up a create filter on my resource, but I want to be able to inject my authorization service into the filter so that I can filter based on the logged-in user.
I added the filter to my configuration here:
    'zf-apigility' => [
        'doctrine-connected' => [
            'MyApi\\V1\\Rest\\Order\\OrderResource' => [
                'query_create_filter' => 'MyApi\V1\Rest\Order\OrderFilter',
            ],
        ],
    ],

And I extended AbstractCreateFilter:
use ZF\Apigility\Doctrine\Server\Query\CreateFilter\AbstractCreateFilter;
use ZF\Rest\ResourceEvent;

class OrderFilter extends AbstractCreateFilter
{
    /**
     * @param string $entityClass
     * @param array  $data
     *
     * @return array
     */
    public function filter(ResourceEvent $event, $entityClass, $data)
    {
        // do stuff
        return $data;
    }
}

This appears to work, but I can't figure out how to inject my authorization service. Normally I would create a factory, but I don't know how to do that in this instance.

In order to add a filter you must create the filter in the service manager.
https://github.com/zfcampus/zf-apigility-doctrine/blob/master/src/Server/Module.php#L59-64
'zf-apigility-doctrine-query-create-filter' => array(
    'invokables' => array(
        'entity_name' => 'Application\Query\CreateFilter\EntityName',
    )
),

That configuration is a plugin manager so you can attach factories, abstract factories, etc. to it.

Can you give me an example of how to attach an abstract factory? I've made one like this:
class AbstractFilterFactory implements AbstractFactoryInterface
{
    public function canCreateServiceWithName(
        ServiceLocatorInterface $serviceLocator, $name, $requestedName
    ) {
        return (fnmatch('*Filter', $requestedName)) ? true : false;
    }

    public function createServiceWithName(
        ServiceLocatorInterface $serviceLocator,
        $name,
        $requestedName
    ) {
        if (class_exists($requestedName)) {
            $filter = new $requestedName();
            $authService = $serviceLocator->get('Zend\Authentication\AuthenticationService');
            $filter->setAuthService($authService);
            return $filter;
        }

        return false;
    }
}

The problem is, I can't figure out the proper configuration to get ZF2 to actually use my factory with the filter class I created.

A Service Manager question is outside the scope of this repo.  Know you're using a plugin manager which is an instance of a Service Manager and you can read up on ZF2's Service Manager and configuration here:  http://framework.zend.com/manual/current/en/modules/zend.service-manager.quick-start.html

I appreciate that this may be out of the scope of this repo, and I also appreciate your quick responses. However, I have read through the Service Manager documentation multiple times, and am still having a hard time. Perhaps you can let me know if I am on the right track?
If I am registering the filter as an invokable here:
'zf-apigility-doctrine-query-create-filter' => [
    'invokables' => [
        'Application\Entity\Order\Order' => 'MyApi\V1\Rest\Order\OrderFilter'
    ],
],

That means it will not look for any abstract factories, right? However, if I remove that config key and instead add an abstract factory like this:
'abstract_factories' => [
    'AudiologyEdgeApi\V1\Rest\AbstractFilterFactory',
],

I get a this error when testing it:
An abstract factory could not create an instance of myapiv1restordercontroller(alias: MyApi\V1\Rest\Order\Controller).


Vibration feedback?

Is there a way to trigger vibration feedback on the controllers?

That's a good point, I'll add that.
WebXR supports it and it's not complicated to add: https://w3c.github.io/gamepad/extensions.html#gamepadhapticactuator-interface
It seems to me that Quest is compatible

Good to hear!


Update core to version 25955fc5

Functionally tested and it works great! I've just pushed the updated release notes and updated example.


Update tag to v0.2.0 ready for release

Signed-off-by: joshvanl<EMAIL_ADDRESS>/assign @SgtCoDFish
/hold
until #51 #50 are merged.
Once merged we can cut the release.

/retest

/lgtm
/approve

/hold cancel

/retest


⚠ Fortnite has degraded performance

In 5aabbfd, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1579 ms

Resolved: Fortnite performance has improved in 3f26d21.


Flutter - Migrate to the Play Install Referrer API

Hi there, I have a flutter app published in Google Play, I have received yesterday the following email from Google:

Hello Google Play Developer,

We recently announced that we’ll be deprecating the install_referrer intent broadcast mechanism. Because one or more of your apps uses this intent to track referrals, we wanted to ensure you make the switch before March 1, 2020. After this date, new versions of the Play Store app will no longer broadcast the install_referrer intent after app installs.

Action required

Migrate to the Play Install Referrer API to track your app installs for the following apps and/or games.

My app uses both firebase and AdMob plugins, so I guess either or both of them causes this. Any suggestion would be greatly appreciated!

Hi @angel1st
for what I can see the issue is related to a FlutterFire plugin,
please open the issue in the dedicated github.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
thank you


AKS Private Endpoints

The private dns zone name for AKS I believe is only half right. The AKS DNS zones can be either privatelink.{region}.azmk8s.io or {subzone}.privatelink.{region}.azmk8s.io. I have typically seen the latter when I deploy in Australia East.
See: https://docs.microsoft.com/en-us/azure/aks/private-clusters#configure-private-dns-zone

Furthermore for clients using kubectl to interact with the AKS Kube API via private endpoint. The client (via the kubectl) will actually use the privatelink FQDN to get to the private endpoint which is quite different to how it works for other Azure services. Might be worth adding a note about this on this page.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

@pnarsi Thanks for the feedback! We are currently investigating and will update you shortly.

@pnarsi Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue. #please-close


Can't drag the map while drawing a road anymore

Description
I used to be able to drag the map while drawing a line / way. This is very convenient when you draw longer ways especially if you're zoomed in.
I think as of beta 2 I can no longer draw and drag. See the movie for visual illustration.
What's sad is that the entirety of the way already drawn disappears as well :(
https://user-images.githubusercontent.com/120452/229169094-a360ad64-1b2a-47ea-bc42-177524529440.mov
Version
2.0.0-beta.2
What browser are you seeing the problem on? What version are you running?
No response
The OS you're using
No response
Steps to reproduce

Start drawing a way.
While drawing, left click and hold to initiate dragging
See your way in progress disappear :(

The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-beta#background=EsriWorldImagery&datasets=fbRoads,msBuildings&map=21.56/40.54441/-111.84823
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response

This is related to https://github.com/facebook/Rapid/issues/687 which is now fixed but not in the way I expected. The 'nudging' is..okay as is the arrow key panning, but I really prefer to be able to do this: (taken from iD)
https://user-images.githubusercontent.com/120452/229171818-d7179a8f-79b1-4d00-863c-a76dc74b50d6.mov

Oh yeah, I agree the nudging that happens at viewport edge is still messed up ..

I think this is superseded, but not the same as, https://github.com/facebook/Rapid/issues/879
I can now drag the map while drawing a way or area, but it results in the line or area in progress disappearing altogether.


Adding new health authorities and/or the CommonTrust Network?

First of all, thank you for open sourcing this! I think you should link to the repository somewhere in the App Store description, it's quite nice to see things appear to have been done properly.
What is the procedure for non-Ontario health departments to have their public keys included? I live in a region where we already use the exact same SMART® Health Card QR codes. (I personally already have an Ontario enhanced vaccine certificate, but I'm thinking about others who visit Ontario and don't have a local address or OHIP card.)

First of all, thank you for open sourcing this! I think you should link to the repository somewhere in the App Store description, it's quite nice to see things appear to have been done properly.

Agree! And the reverse link on the GitHub repo back to https://covid-19.ontario.ca/verify.  I had to hunt to find the deployed app link.

After doing a bit more research, Ontario should really join the CommonTrust Network. Seems like this is already a solved problem.
This would allow interoperability within Canada for British Columbia, Northwest Territories, and Yukon. https://www.commontrustnetwork.org/verifier-list
https://www.commontrustnetwork.org/joinhealth

After doing a bit more research, Ontario should really join the CommonTrust Network. Seems like this is already a solved problem. I do like that Ontario's Verify app is open source (which the "official" app by is not), which is extremely helpful for privacy sensitive topics like this.
This would allow interoperability within Canada for British Columbia, Saskatchewan, Manitoba, Northwest Territories, and Yukon. https://www.commontrustnetwork.org/verifier-list
https://www.commontrustnetwork.org/joinhealth
You just need to submit a PR to this repo:
https://github.com/the-commons-project/vci-directory

This is something we're actively looking into. Right now our priority is lining up with our fellow provinces and territories under the guidance of the Public Health Agency of Canada. We're working closely across the confederation to chart a path here on GitHub to share public keys and test cases openly. Stay tuned.

@spncrd Roughly how long do you think this policy and legal review would take? It is definitely a priority for travel.

Ontario joining the Common Trust Network is a must. I am trying to go back to Singapore with my partner who has non-curable cancer. As a Singaporean he can go back. I cannot as they will only let short term visitors in who are on the Common Trust Network. This has created a situation where I, as a Canadian, cannot travel with my partner to see my in-laws in Singapore because I live in Ontario....but if Iived in BC, The Yukon, or The Northwest Territories I could go back no problem...because they have joined the CommonTrustNetwork.

@Aseatondream my deepest sympathies, and thank you for the framing the human cost. I am doing everything I can to move this along, but the policy review and decision ultimately sits in the Ministry of Health.
To formally correspond with the Ministry of Health you can use the following contact form (being sure to request a reply): https://www.ontario.ca/feedback/contact-us?id=25811&nid=98977
@serenadolan and anyone with similar sentiments and concerns might see more traction via the above channel.

@Aseatondream my deepest sympathies, and thank you for the framing the human cost. I am doing everything I can to move this along, but the policy review and decision ultimately sits in the Ministry of Health.

@spncrd I do not see anything in the getting started page that would require a policy review. I question if the correct technical information is being passed along to decision makers, as joining the CommonTrust Network does not share any additional information.
Publicly sharing your public key with The Commons Project Foundation should not expose any information that we (the public) don't already have. If publishing your public key in a public directory causes a security or privacy concern, then https://github.com/ongov/OpenVerify/issues/1#issue-1027065216 would be correct.. 🙄

And since we've already got agreement to share keys

To clarify https://github.com/ongov/OpenVerify/issues/4#issuecomment-951932193, are you saying agreements are needed to share public keys?

Thank you. I did submit through the Ministry of Health link a couple of days ago, as well as through my local MPP. Awaiting responses. I do encourage anyone reading this to also submit through: https://www.ontario.ca/feedback/contact-us?id=25811&nid=98977 https://www.ontario.ca/feedback/contact-us?id=25811&nid=98977
Alan\

On Nov 4, 2021, at 1:54 PM, Spencer Daniels @.***> wrote:
@Aseatondream https://github.com/Aseatondream my deepest sympathies, and thank you for the framing the human cost. I am doing everything I can to move this along, but the policy review and decision ultimately sits in the Ministry of Health.
To formally correspond with the Ministry of Health you can use the following contact form (being sure to request a reply): https://www.ontario.ca/feedback/contact-us?id=25811&nid=98977 https://www.ontario.ca/feedback/contact-us?id=25811&nid=98977
@serenadolan https://github.com/serenadolan and anyone with similar sentiments and concerns might see more traction via the above channel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-961283359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6DBRUS5FSFYRU3TQCDUKLJG3ANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@Manouchehri it's beyond my purview as to the level of detail of approvals and review required to join a network like CommonTrust, but I would expect a focus on privacy and legal due diligence to account for some of the time elapsed and some to come.

@spncrd Thank you for the link, I have submitted accordingly. I think most of us here are anxious to be able to go home/ go about what we need to do.

In the last two hours Quebec, Manitoba, and Saskatchewan were added to the Common Trust Network (BC, Yukon and Northeast Territories were already there). See link
https://www.commontrustnetwork.org/verifier-list https://www.commontrustnetwork.org/verifier-list
Come on Ontario!
Alan

On Nov 4, 2021, at 2:35 PM, serenadolan @.***> wrote:
@spncrd https://github.com/spncrd Thank you for the link, I have submitted accordingly. I think most of us here are anxious to be able to go home/ go about what we need to do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-961312814, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6AUZXNK3F2VEK3NMG3UKLN6PANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@Aseatondream very timely, I was just pulling the latest list to pass along and saw it updated too!

@Aseatondream @spncrd Hopefully this gives a much needed push to get us into the list as well! It looks like most provinces and territories are on the list now so I am hoping Ontario now gets in quick too.

YES!!!
Alan

On Nov 4, 2021, at 3:20 PM, serenadolan @.***> wrote:
@Aseatondream https://github.com/Aseatondream @spncrd https://github.com/spncrd Hopefully this gives a much needed push to get us into the list as well! It looks like most provinces and territories are on the list now so I am hoping Ontario now gets in quick too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-961346153, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6CYRMJ5YFWX6SQCD33UKLTIHANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I understand that everyone has a different approach but the other provinces got onto it so quick!

I understand that everyone has a different approach but the other provinces got onto it so quick!

@serenadolan It's quick because it's not difficult..
@TASelwyn has already done 100% of the technical work for free over two weeks ago. Literally all Ontario has to do is sign a piece of paper saying they're going to promise to try to only issue legitimate certificates.
https://github.com/the-commons-project/vci-directory/pull/200

I’m going to remain positive based on what we just saw happen today and assume it is coming real soon…but if not it may need to hit the news media with a headline like “Think you can travel where Canadians can travel? If your from Ontario…don’t be so sure”.
Alan

On Nov 4, 2021, at 4:26 PM, David Manouchehri @.***> wrote:
I understand that everyone has a different approach but the other provinces got onto it so quick!
@serenadolan https://github.com/serenadolan It's quick because it's not difficult..
@TASelwyn https://github.com/TASelwyn has already done 100% of the technical work for free over two weeks ago. Literally all Ontario has to do is sign a piece of paper saying they're going to promise to try to only issue legitimate certificates.
the-commons-project/vci-directory#200 https://github.com/the-commons-project/vci-directory/pull/200
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-961391192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6ASDKIVI2BOVSBS6CTUKL3BBANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

it may need to hit the news media with a headline like “Think you can travel where Canadians can travel? If your from Ontario…don’t be so sure”.

@Aseatondream This issue ticket is already a classic of "not my job".. It's ridiculous it's taken over two weeks to fill out one short form.

The Ontario Ministry of Health needs to be spammed (figuratively speaking, not literally) with requests until they join the CommonTrust Network. There's absolutely no reason for them not to join. I've already contacted them on my own. I do believe it will happen in the coming weeks, especially after Quebec joined. Which, Ontario's system is basically a carbon copy of Quebecs.

Thanks for the engagement and feedback, all. I'm passing it up to very senior levels and advocating for users like you. These issues matter and I appreciate you posting here. But formal channels like official ministry correspondence and via MPPs get logged, tracked and responded to in a way that will register differently than GitHub. Many avenues are effective, but some are more effective than others when it come to policy.

And to pull back the curtain, the forms have been filled out and ready to go for weeks to join VCI and Common Trust and I have volunteered to facilitate the submission process. However, the approval and final decision to do so sits in the Ministry of Health. The Ontario Digital Service is part the Ministry of Finance - there is truly only so much we can do outside of the app itself. I hope you all can appreciate that.

Thank you! I have only been part of this conversation today, but I have sensed from the beginning you are a good person doing what you can. I appreciate it very much.
Alan
Sent from my iPhone

On Nov 4, 2021, at 9:55 PM, Spencer Daniels @.***> wrote:

Thanks for the engagement and feedback, all. I'm passing it up to very senior levels and advocating for users like you. These issues matter and I appreciate you posting here. But formal channels like official ministry correspondence and via MPPs get logged, tracked and responded to in a way that will register differently than GitHub. Many avenues are effective, but some are more effective than others when it come to policy.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Tha k you got that info! Again…it’s appreciated.
Alan
Sent from my iPhone

On Nov 4, 2021, at 10:16 PM, Spencer Daniels @.***> wrote:

And to pull back the curtain, the forms have been filled out and ready to go for weeks to join VCI and Common Trust and I have volunteered to facilitate the submission process. However, the approval and final decision to do so sits in the Ministry of Health. The Ontario Digital Service is part the Ministry of Finance - there is truly only so much we can do outside of the app itself. I hope you all can appreciate that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Jumping on to the ask for Ontario to be on the verified list asap. I lost my father in May of 2020 due to Covid and was unable to travel for the funeral. Now I was looking to go meet my mum and sis in Singapore since travel opened up and suddenly find that Ontario vaccine proof is not on the approved list.
It has been such a nerve racking time, naively I had already booked tickets on a VTL flight to Singapore for Dec 2nd week, the thought that Ontario would not be in approved list never crossed my mind.
I read in the conversations above the suggestion to write to ONTHealth, will do so but really feeling not too positive at the moment.

@lonelypilgrimonearth I am in the same boat as you. My VTL flight is 3 weeks from today, really hoping it gets sorted by then.

Nova Scotia has just been added to Common Trust Network.

Why is it so easy for everyone else but not Ontario? I really don't get it.

Newfoundland and Labrador now added
Alan Read-Chua, Broker and Branch Manager
Sutton Group - Associates Realty Inc., Brokerage
Office:<PHONE_NUMBER>
Cell:<PHONE_NUMBER>
@.***

On Nov 5, 2021, at 11:57 AM, serenadolan @.***> wrote:
Why is it so easy for everyone else but not Ontario? I really don't get it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-962013410, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6DDM563SRVCD23Q4ADUKQEHFANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I am happy for other provinces. Gutted that there is still no action on ours.

I’m keeping hope. It’s gone from 3 provinces/territories to 8 in the last 36 hours.
Sent from my iPhone

On Nov 5, 2021, at 10:51 PM, serenadolan @.***> wrote:

I am happy for other provinces. Gutted that there is still no action on ours.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I just looked at the VTL requirements for Singapore and looks like they have solved the problem for travellers to Singapore. Now SmartHealth Cards for all provinces will be accepted. "https://safetravel.ica.gov.sg/vtl/requirements-and-process > Accepted Proof Of Vaccination > 3c" was added overnight.
I want to thank @spncrd for his responsiveness on this forum and his commitment to helping people here. This is probably not first and foremost in your job description, but you did help give people some hope through your transparency here; not many in the business would do what you did here and I appreciate it.

Wowww...this is such good news, will try and apply for the VTL right away.
I totally second the thanks to @spncrd for this stream and all the direction and responses. It was only after I found this conversation that I felt a little less anxious about the whole thing. Thanks again to all.

This is awesome!!!!
Sent from my iPhone

On Nov 6, 2021, at 10:16 AM, Ernestly @.***> wrote:

I just looked at the VTL requirements for Singapore and looks like they have solved the problem for travellers to Singapore. Now SmartHealth Cards for all provinces will be accepted. "https://safetravel.ica.gov.sg/vtl/requirements-and-process > Accepted Proof Of Vaccination > 3c" was added overnight.
I want to thank @spncrd for his responsiveness on this forum and his commitment to helping people here. This is probably not first and foremost in your job description, but you did help give people some hope through your transparency here; not many in the business would do what you did here and I appreciate it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Yes…huge thanks to @spncrd for all he has been trying to do!
Sent from my iPhone

On Nov 6, 2021, at 10:16 AM, Ernestly @.***> wrote:

I just looked at the VTL requirements for Singapore and looks like they have solved the problem for travellers to Singapore. Now SmartHealth Cards for all provinces will be accepted. "https://safetravel.ica.gov.sg/vtl/requirements-and-process > Accepted Proof Of Vaccination > 3c" was added overnight.
I want to thank @spncrd for his responsiveness on this forum and his commitment to helping people here. This is probably not first and foremost in your job description, but you did help give people some hope through your transparency here; not many in the business would do what you did here and I appreciate it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I just tried uploading the QR pdf for the VTP but unfortunately get the same error :(

I got the same error as well and have sent the error here: https://form.gov.sg/#!/60e693e777fd6b00111885d5
They have been quite responsive on that forum - so hopefully they will fix it soon. [This week I had received a message that they were "working on it", and today it looks like the policy changed] It IS a Saturday night there, so I'd expect it would maybe take a business day or 2 for the systems to update.

Thanks, sent in the enquiry form, yep I think it.may be Monday before any new developments.

Go back to Singapore site. They now have this message with a link:
For short-term visitors and long-term pass holders
If you encounter an error upon uploading the QR code on your vaccination certificate onto the VTP application portal, despite meeting the requirements above, please write to the Safe Travel Office using the enquiry form here https://go.gov.sg/sto-enquiry and provide your vaccination certificate. If you are unable to obtain one of the digitally verifiable vaccination certificates listed above, you will not be eligible for travel on the VTL.
Alan

On Nov 6, 2021, at 10:57 AM, lonelypilgrimonearth @.***> wrote:
Thanks, sent in the enquiry form, yep I think it.may be Monday before any new developments.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-962463447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6BYILS4BZV7PDPBRTDUKVF5FANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Damn. Gotta praise Singapore for their quick changes and responses to this issue for people.
How many provinces are left to join the CommonTrust network anyways? Seems like its just Ontario now lol

There are still a few areas left to join Thomas but you are right…must have joined...till not on CommonTrust Network are
Ontario
Alberta
Prince Edward Island
New Brunswick
Nanavut
Alan

On Nov 7, 2021, at 12:14 AM, Thomas Selwyn @.***> wrote:
Damn. Gotta praise Singapore for their quick changes and responses to this issue for people.
How many provinces are left to join the CommonTrust network anyways? Seems like its just Ontario now lol
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-962549216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6AXFFN7PAARPQHAGQDUKYDK7ANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

There are still a few areas left to join Thomas but you are right…must have joined...till not on CommonTrust Network are
Ontario
Alberta
Prince Edward Island
New Brunswick
Nanavut
Alan

Three weeks ago, we were told that Ontario was trying to individually meet with each province to exchange public keys. 🤦♂
https://github.com/ongov/OpenVerify/issues/4#issuecomment-945041578
Turns out that's not a great approach..

Got my VTP from SG through their appeal form.  The emails to ONTHealth just was replied directing me to the provincial vaccine contact center number. Thankfully didn't have to wait for Ontario to get on the verified list to get the pass.

I think they needed to manually validate the issuing link. I’m a Singaporean living abroad, so I suppose I probably can only get validated when I land.

Got my VTP from SG through their appeal form. The emails to ONTHealth just was replied directing me to the provincial vaccine contact center number. Thankfully didn't have to wait for Ontario to get on the verified list to get the pass.

This is great news! Thank you for update! I'm patiently waiting on mine to get approved now, also requested via their webform.

That is correct: “ All SC/PRs and unvaccinated children aged 12 and below in the current calendar year do not need to make any applications under the Vaccinated Travel Lane. However, you will need to present an acceptable proof of vaccination for verification at check-in and arrival immigration. ”
Sent from my iPhone

On Nov 8, 2021, at 10:17 AM, serenadolan @.***> wrote:

I think they needed to manually validate the issuing link. I’m a Singaporean living abroad, so I suppose I probably can only get validated when I land.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

@Aseatondream It's just such a relief to know our Ontario proof of vaccination is now being accepted :)

Yes!!!
Sent from my iPhone

On Nov 8, 2021, at 1:10 PM, serenadolan @.***> wrote:

@Aseatondream It's just such a relief to know our Ontario proof of vaccination is now being accepted :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Got my VTP from SG through their appeal form. The emails to ONTHealth just was replied directing me to the provincial vaccine contact center number. Thankfully didn't have to wait for Ontario to get on the verified list to get the pass.

Hi Sir,
Could you shine me some light on how long you waited for their response to grant you VTP? and in the appeal, what information did you provide?
Thank you!

Sg took  about a week in total from the first form to supplying additional information. Hope rhis helps.

Yeah the VTP site is still rejecting Ontario's QR codes. How is Ontario still not on this verifier list??

Thanks for the patience, y'all. I was given approval to submit our application to CommonTrust and VCI on Friday and I'm pleased to report we provided them additional testing collateral yesterday and have been told we should be verified as early as today or tomorrow.
All your advocacy was brought forward and helped move this along.

Great. Thanks for staying on this Spenser. We know the hod up was NOT you.
Cheers!
Alan

On Nov 23, 2021, at 1:43 PM, Spencer Daniels @.***> wrote:
Thanks for the patience, y'all. I was given approval to submit our application to CommonTrust and VCI on Friday and I'm pleased to report we provided them additional testing collateral yesterday and have been told we should be verified as early as today or tomorrow.
All your advocacy was brought forward and helped move this along.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-977001637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6HKS2A5OHQENPFVKQDUNPOGRANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Actually…it may not be appearing in text on the list yet but if you use the common trust networks verifier app to scab your QR code it is already reflecting the fact that the issuer (ontario) is verified. Yay!!!
Alan Read-Chua, Broker and Branch Manager
Sutton Group - Associates Realty Inc., Brokerage
Office:<PHONE_NUMBER>
Cell:<PHONE_NUMBER>
@.***

On Nov 23, 2021, at 1:43 PM, Spencer Daniels @.***> wrote:
Thanks for the patience, y'all. I was given approval to submit our application to CommonTrust and VCI on Friday and I'm pleased to report we provided them additional testing collateral yesterday and have been told we should be verified as early as today or tomorrow.
All your advocacy was brought forward and helped move this along.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ongov/OpenVerify/issues/4#issuecomment-977001637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWLDU6HKS2A5OHQENPFVKQDUNPOGRANCNFSM5GDZM4DA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

As of https://github.com/the-commons-project/vci-directory/pull/358, Ontario has been added to the VCI Issuers directory & the SMART Health Card Verifier app now shows Ontario as a validated origin.

I've edited the title and my initial post to reflect what the majority of the thread was.
Closing as Ontario joining CommonTrust is now complete (woot woot, only 3rd last), and continuing the other question I had in #21.

@edwardjcruz @spncrd Could you please address https://github.com/the-commons-project/vci-directory/issues/365? You appear to be violating VCI directory agreement already..


Incorrect version causing formatting issue in docs

LocalAI version:
v2.13.0
Environment, CPU architecture, OS, and Version:
N/A - Docs Issue
Describe the bug
The current version being used in the OpenAI Docs is "🖼 v2.13.0 - Model gallery edition".  This is being pulled from:
https://github.com/mudler/LocalAI/blob/master/docs/data/version.json
The docs use a {{< version >}} dynamic value referencing the above json file.
This is causing all the Docker commands to have the emoji and incorrect values in them here:
https://localai.io/docs/getting-started/run-other-models/
To Reproduce
Copy the Docker command from the Run Other Models Docs page, and attempt to run it.  You will get this error:
docker run -ti -p 8080:8080 localai/localai: :frame_photo: v2.13.0 - Model gallery edition-ffmpeg-core phi-2
docker: invalid reference format.
See 'docker run --help'.

Expected behavior
Correct Docker syntax with proper image names and tags to pull the image properly.
Logs
N/A
Additional context
Based on the file history, the version should just be v2.13.0.

I can work on fixing this tomorrow.

Thanks @linuxtek-canada for raising this issue.
https://discord.com/channels/1096914990004457512/1233965318100094996/1233965325851168799

This is fixed via this commit: https://github.com/mudler/LocalAI/commit/3179c019af17a7fdede8089eaa410359ca151d74
Confirmed the website is already corrected.


Python Version 3.8 - conda-forge fbprophet not working using custom image

dockhub gtno1chun/note-custom-image:1.0.0을 사용했을 경우 fbprophet 동작하지 않음
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: \
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:
Specifications:

fbprophet -> python[version='2.7.|3.5.|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.5,<3.6.0a0']

Your python: python=3.8
If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.
Note that strict channel priority may have removed packages required for satisfiability.
Note: you may need to restart the kernel to use updated packages.

I have updated custom image.
docker pull gtno1chun/note-custom-image:1.1.0

정상 동작 확인 완료


Automated Package Upgrade

:tada: This PR is included in version 25.4.52 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Main fix casing

Description
Fixes case sensitivity issue with Windows in landingPage.js/LandingPage.js
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Unit Tests
[ ] Integration Tests
[ ] User Tests

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

deleted lower case landingPage

deleted lower case landingPage


updates: On Windows with closed firewall a PowerShell error is returned

This issue respects the following points:

[X] This is a bug, not a question or a setup/configuration issue.
[X] This issue is not already reported on Github (I've searched it).
[X] I use the latest release of the Monitoring Plugins (https://github.com/Linuxfabrik/monitoring-plugins/releases).
[X] I agree to follow Monitoring Plugins's Code of Conduct.

Bug description
see title
Steps to reproduce - Plugin call
'C:\ProgramData\icinga2\usr\lib64\nagios\plugins\updates.exe' '--critical' '50' '--warning' '2'

Steps to reproduce - Plugin Version
v2022021501
Steps to reproduce - Data
Exception from HRESULT: 0x80072EE2
At line:4 char:5
+     $Pending = $SearchIndex.Search('IsInstalled=0');
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException

Python version
No response
Environment
Windows
Application
No response
Python modules
No response
Additional info
No response

"Closed Firewall" means "Block all outgoing connections".
Confirmed. Only happens in Powershell after a 10 second timeout. In a batch terminal, updates.exe hangs forever.

Fixed in source. If you like, please give it a try. Don't forget to use the updated libs as well (implemented a new timeout parameter in shell_exec() - it is more general than relying on PowerShell).


Put request for post

add these tests:
put with invalid arguments such as key: XXX value: YYY
post with invalid arguments such as key: XXX value: YYY
put editing a post that does not belong to the current authenticated user


inconsistent behaviour by setting element property via attribute

Currently skate behaves inconsistent when property value is set within HTML via attribute and when it's set from within custom element to other nested custom element.
I've created plnkr:
https://plnkr.co/edit/flbU9Pt1nxqUFXCnPJuq?p=preview
thing is, if you set attr/prop syncing via {attribute: true} it works consistently but that's quiet confusing
here is root component:
class Foo extends Component {
  static get is(){return 'my-foo'}
  static get props(){
    return {
      label: prop.string({
        // attribute:true
      }),
      done: prop.boolean({
        // attribute:true
      })
    }
  }
  static render(elem){
    const {label,done} = props(elem);
    return

        hello {label}.

        I am {done ? 'DONE':'NOT FINISHED'}

        <iron-icon icon="boom"></iron-icon>
        <Icon icon="moom"/>

  }
}

here is nested component
class Icon extends Component {
  static get css(){
    return `
      :host{
        display: block;
      }
    `
  }
  static get is(){ return 'iron-icon'}
  static get props(){
    return {
      icon: prop.string({
        // attribute:true
      })
    }
  }
  static render(elem){
    const {icon} = props(elem);
    return [
      ,
      {icon}
    ]
  }
}

so if I use root component like this:
<my-foo label="World" done></my-foo>

properties are not set correctly and have default value (done===false; label==="").
One has to explicitly set those prop definitions to {attribute:true} to make it work, which makes sense right ? ( attr/prop sync )
What is not ok is that when you use that Icon component within Foo it works without setting  {attribute:true}
        <iron-icon icon="boom"></iron-icon>
        <Icon icon="moom"/>

If this is the same issue I'm experiencing, then it will fail in polyfill-land even if you use Icon with Foo.
cc @bengummer

i've just written a test to demonstrate this behaviour (code at  https://github.com/skatejs/skatejs/commit/a63d8f1b3cef4b11a9ea02b99530eb2ca8ce73a6 and travis build here)
it looks like when we generate an element inside render() { ... } the generated element's attributes are actually set by vdom as props. This would be ok if the generated props got sync'd to attributes, but that doesn't happen if the prop/attr isn't linked.
cc @treshugart

When you go through render(), it prefers properties if available. This is why you're seeing this behaviour, I think. Nonetheless, this is intentional, so I think I'm going to close this. What might change in the future is that props may end up automatically syncing from attributes (auto-linked) but that's still under discussion in #838.


Where to write code?

Hello WSL community,
I am am new to WSL and found this setup guide extremely helpful.
My questions is where should I be writing my code? I thought I could write my code in Windows editor and run this code in Ubuntu, but when I have tried that linux complains about /r in my code.
.../ncbi-blast.sh: line 8: syntax error near unexpected token $'do\r''`
In your setup guide you install VCode; however, I am accustomed to using Atom. So, I wrote my code in Atom on windows.
Any and all help would be appreciated.
Thank you!

Solved this by changing the line sequence in Atom from CRLF to LF


Bounty - First Input Priority SOCD

Add in First Input Priority (FIP) as an SOCD resolution option in the webconfig. Does not require a shortcut, webconfig option only.
First Input Priority
(1st Direction + 2nd Direction = Result)
L+R=L
R+L=R
U+D=U
D+U=D
Given Simultaneous Cardinal Directions (Up/Down, Left/Right), you do not get the second directional input until the first is released.
Example:
So the button sequence
L, L+R, R, R+L, L
results in the inputs
L, L, R, R, L

I can take a look at this if no one else is. I've got the code already just need to copy it over, compile and test.

Hey @ScrubTier !
I believe @deeebug already started work on this but I would recommend we all connect and see if it can be worked on together.
Moving forward I will try to call out who’s taken on what.

Sorry, forgot to tag this issue.


[Suggestion]: About the user-define color theme.

VSCode Version: 1.4.0
OS Version: Win7 sp1

I have a suggestion:
Why we can not choose another color theme? Not only the dark black style like now, especial when you preview the markdown file. The user experience is too bad on default dark black theme.

@shines77 I am not sure if you are aware that you can

Select a theme from an existing installed themes.

Install a new theme from the extensions market

@sandy081
Thanks, I got it.


Pagination is not working properly on best efforts view

See https://www.opensplittime.org/courses/twisted-branch-trail/best_efforts
The pagination widget shows 15 pages, but only the first 8 have names on them. Could be a discrepancy between scoped (visible) efforts and all efforts?

This turns out to be a discrepancy between efforts that have finished the course and those that have not.
The best efforts presenter runs the following query to determine efforts to show in this view:
  def filtered_efforts
    all_efforts.over_segment(segment).unscope(:where, :joins)
      .where(filter_hash).search(search_text)
      .paginate(page: page, per_page: per_page, total_entries: filtered_efforts_count)
  end

This query is expensive. If we use the same query to determine total count of all filtered efforts, then we run the expensive query twice. So for now, we are using the following cheaper query to estimate total count:
  def filtered_efforts_count
    @filtered_efforts_count ||= all_efforts.where(filter_hash).search(search_text).count
  end

But this query does not determine who has completed the required segment to make valid for listing in this view.
What needs to happen here is we need to do away with the total count entirely and just do this view with endless scrolling.


DataTables: Multiple a11y issues

Note the list of issues by number are from the PI Portal manual evaluation (internal document to ORIS). Look at that document for full details on context, WCAG citations, recommendations. Language has been adjusted a bit to be generalized for GitHub.
Not every item is serious, but overall I'd consider this to be a severe issue that warrants a replacement.
--
Issue 9: The filter dropdown does not announce their states of expanded/collapsed upon activation.
Issue 16: NVDA announces “clickable” for many of the table elements that are not interactive components.
Issue 21: Selectable row checkboxes cannot be activated with space or return.
Issue 22: Ddata cells are not programmatically associated with their column header.
Issue 26: Column headers provide sorting but if the column is not already sorted, the screen reader does not indicate that functionality either with text or by announcing the visible arrows.
Issue 30: When the text spacing test is applied, content overlaps in the table.
Issue 32: Nested table rows have a chevron icon indicating expand/collapse. These buttons do not announce any accessible name.
Issue 33:  Where pagination is present, name, role, and value are not announced.
Issue 40: With the screen reader on, the checkboxes are not consistently checking/unchecking with a double tap, nor are they announcing the correct state consistently.

Also of note, we do a direct import of primereact/datatable (v6.6.0) as UI v4 guidance, and have included custom CSS to standardize it with our brand. But we do not provide any form of React component directly from UI 4 for data tables.


Implement  StringViewArray and BinaryViewArray

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Recently two new types were added to the Arrow format that make it more suitable for certain types of operations on strings
Specifically when doing filtering / take with string data, creating a new Utf8Array requires copying the strings to a new, packed binary buffer. The "VariableSizeBinaryView" was designed to solve this limitation and recently added to the Arrow spec.
Describe the solution you'd like
I would like to implement StringViewArray and BinaryViewArray following the spec:
The spec:  https://arrow.apache.org/docs/format/Columnar.html#variable-size-binary-view-layout
https://github.com/apache/arrow/blob/3fe598ae4dfd7805ab05452dd5ed4b0d6c97d8d5/format/Schema.fbs#L187-L205
Initially, I would suggest we get the basic types in place:

[ ] DataType
[ ] Array implemntations and layout and basic construction

Then as follow on PRs, add support to key kernels:

[ ] cast (to/from StringArray / DictionaryArray)
[ ] filter
[ ] take

Describe alternatives you've considered
I think a good plan would be to dust off the prototype on https://github.com/apache/arrow-rs/pull/4585 from @tustvold  (linked from https://github.com/apache/arrow-rs/issues/4253).
Initially, the idea would be to dust off the PR and split it into a few smaller PRs with tests and docs.
Additional context
Polars implemented it recently in rust so that can serve as a motivation
Blog Post https://pola.rs/posts/polars-string-type/
https://twitter.com/RitchieVink/status/1749466861069115790
Related PRs:
https://github.com/pola-rs/polars/pull/13748
https://github.com/pola-rs/polars/pull/13839
https://github.com/pola-rs/polars/pull/13489

@tustvold  pointed out the previous PR he made was https://github.com/apache/arrow-rs/pull/4585
We can probably dust that off and get it ready to merge as part of this project

@kallisti-dev I believe may do some work on this.
I suggested breaking it down into a sequence of PRs (keeping notes of what is not yet implemented along the way)
Specifically, I suggest the first PR should have:

The new DataType
The new StringViewArray and impl Array
A basic constructor for creating and validating StringViewArray
Any feature (e.g. IPC support, parquet support, etc) should return a Arrow::NotYetImplemented error (rather than panic)

That will likely be a sizeable PR on its own.

Post from Velox on iimportance of stringview: https://engineering.fb.com/2024/02/20/developer-tools/velox-apache-arrow-15-composable-data-management/

Moving an update from  @sundy-li  and @ariesdevil  from https://github.com/apache/arrow-rs/pull/4585#issuecomment-1965896483  to here for visibility
I believe @ariesdevil is considering working on this relatively shortly

Hi @alamb, I'm willing to work on this feature after datafuselabs/databend#14662 is finished.

@XiangpengHao, who will be working with us at InfluxData this summer (starting in May) is also interested in this project, so when we get closer to May we'll engage more fully and perhaps we can figure out how to split up some of the work.

Moving an update from @sundy-li and @ariesdevil from #4585 (comment) to here for visibility↳
I believe @ariesdevil is considering working on this relatively shortly↳

Hi @alamb, I'm willing to work on this feature after datafuselabs/databend#14662 is finished.↳

@XiangpengHao, who will be working with us at InfluxData this summer (starting in May) is also interested in this project, so when we get closer to May we'll engage more fully and perhaps we can figure out how to split up some of the work.

Do we have a group similar to Discord or Slack?

Do we have a group similar to Discord or Slack?

@ariesdevil  There is both discord and slack -- links are here https://github.com/apache/arrow-rs?tab=readme-ov-file#arrow-rust-community
The discord server doesn't require an invite and seems to be a bit more active recently

Hi @alamb
I'm interested in the progress of this issue regarding the addition of ListViewArray and LargeListViewArray to arrow-rs. I've been following the discussion and would like to know if there have been any updates or if there's anything specific I can assist with to help move this forward.

@ariesdevil  says they have time to begin work on this so I will begin filing subtasks

Update here is that @ariesdevil  has a PR https://github.com/apache/arrow-rs/pull/5481 that we plan to merge tomorrow

Is there an issue to make sure that parquet support for the new arrow view types are supported. Currently can not use with the parquet writer when they are specified in the schema.
I am actually more familiar with Arrow than I am Parquet so excuse the question: is there an official Parquet spec or implementation plan for the view types?

I'm working on read/write parquet for view types.

I'm working on read/write parquet for view types.

I filed https://github.com/apache/arrow-rs/issues/5530 to track

BTW if anyone is interested, I have a proposal for how to improve manipulating the views in Rust https://github.com/apache/arrow-rs/pull/5619 (I really enjoy the rust type system in general -- it is quite cool)

Update here: thanks to @ariesdevil  and @XiangpengHao  and @RinChanNOWWW  we have pretty good basic support for StringView in arrow-rs -- we have basic construction, cast and soon comparison functionality complete. Also, we can now read directly from parquet into StringView arrays https://github.com/apache/arrow-rs/issues/5530
We have also begun the work to integrate this into DataFusion, which is tracked in https://github.com/apache/datafusion/issues/10918

Update here is that most of the basic StringView work for basic scanning / filtering is done. There will likely be an large tail of places to implement special StringView support as follw on.
Over the next week or two I plan to file a new ticket for the remaining known work and close this ticket down

Given we have now released all the basic support in arrow 52.0.0 am going to claim we are done with the initial implementation and close this ticket 🎉
Huge kudos to everyone who helped including @RinChanNOWWW @ariesdevil @tustvold @XiangpengHao and @a10y  (sorry if I forgot anyone)
I am collecting additional potential work items in https://github.com/apache/arrow-rs/issues/6163


Is ?eval is really needed in Chrome?

Dear devs,
I noticed that using Chrome UI5 adds ?eval to all my resource ( remote and local ) during debugging the code.
In the scenario when we do local development (ui5 serve) this is extremely not convenient cause in this case we loose one of the amaziest Chrome features - ability to change the code from the runtime.
It makes it even worse - that again and again I forget where I stay ( Chrome or VsCode debugger ) and I do changes in Chrome and of course they are lost after reload.
Analyzing the code I see that this ?eval string is added intentionally in sap-ui-core.js
The variant of having sourcemaps also is not preferabble cause we talk about local development when we do not generate sourcemaps and on the fly. I would prefer to create manually a js file and to be able to run it immediately without any additional tasks.

I really hope you can find workaround for module name issue and make the resource name same as as local file.
Thank you!

That comes as a surprise because Chrome/Chromium claims to have added support for URL params with "Persistence 2.0" (see https://bugs.chromium.org/p/chromium/issues/detail?id=277885 ).
The ?eval only serves as a marker to distinguish resources that have been loaded with an XHR from resources that only might be loaded due to source maps. Without the parameter, Chrome only displayed one of them, which was hard to understand during debugging.
From the commit f0b436048e43e7593b4ae099ce18ba6be732d31e:

Additionally append '?eval' to the sourceURL annotation in Chrome. This
helps to distinguish bootstrap relevant sources referenced via source
maps from the same sources loaded via debug mode. Without that suffix,
Chrome displays only one source, sets breakpoints in the sourcemap
source but executes the debug source.

As it doesn't have a functional purpose in productive scenarios, we definitely could omit it, either in general or on demand (config).
But before doing anything into that direction, I would like to understand one of your remarks better:

"It makes it even worse - that again and again I forget where I stay ( Chrome or VsCode debugger ) and I do changes in Chrome and of course they are lost after reload."

I didn't get how this is related to the ?eval ?

@codeworrior
I meant that I during development, going deep into debug sometimes you really forget where you are - in the debugger of Chrome or in the VS code editor..
So in this case when you make a change in Chrome:

As it doesn't have a functional purpose in productive scenarios, we definitely could omit it, either in general or on demand (config).

That's correct. We talk about the case when we do not have debug or preload files and Component.js - is a raw  source.  Therefore sourcemaps are not relevant here also. It must be direct mapping.

I see, thank you for the clarification.
I would suggest to activate async loading (data-sap-ui-async=true) in your app. Anything loaded asynchronously will be loaded as a script tag and won't have the ?eval param in the URL.

Thanks for the advise. Unfortunately our target version is still 1.44 ( SAP FES 3.0 ). So I guess it won't work yet with this version. That's why we would gladly prefer to have this fix if it's available in all supported versions. ( https://openui5.hana.ondemand.com/versionoverview.html )

I tested this on my machine and I don't encounter any issues. Modified files are saved and after refresh properly loaded with the modified content. This is also what I would expect after reading the above Chromium bug report (which claims the issues with query parameters to be fixed).
I even modified the ?eval string in the ui5loader source via Chrome's workspace and still the connection between local sources and browser content worked after a refresh (with the modified parameter).
The issue in your case must be a different one.
What runtime do you use to serve the files? I couldn't find detailed information how Chrome's automated mapping works. But I first mistakenly used a src folder with similar, but not identical sources and then the mapping did not work. So my assumption is that Chrome infers the mapping from an exact match of the file content (+ maybe the base name). Chrome clearly indicates whether the mapping could be inferred by green bullets on the source's icon:

If my assumption is correct, any source-modifying middleware that is active in the server and which does not add sourcemap information might prevent the use of Chrome's workspace feature.
I added the wontfix label now as I don't see anylonger how this should be related to ?eval. But I leave the issue open for further analysis and discussion.

[Update] I've tested now with ui5 serve, grunt serve and Tomcat and all of them worked 99%. The 1% was the Global.js for which our middleware replaces the ${version} placeholder with a concrete version (to avoid runtime issues). This still would fit my assumption about how Chrome's mapping might work.

Man, you are right. This is a miracle - I cloned another project and it works with same cli and middleware. Something is wrong with my folder - chrome doesn’t want to pick up from it


Cannot connect to websocket

I have aria2 running in terminal, but when I open the index.html it says the following: Error while talking to aria2 over websocket and gives me no further details. Can I please have some assistance here? And in the terminal all it says is:
2013-06-22 15:41:56.209883 NOTICE - IPv4 RPC: listening to port 6800
2013-06-22 15:41:56.210544 NOTICE - IPv6 RPC: listening to port 6800
I would love it if I could get some assistance here.

Close seems the issue seems dead (4 years old)


Image Upload script seems broken

$.ajax(...).success is not a function

Should probably be:
$.ajax({ ... }, function(success) { cb }), ...

I saw this too:

Mixed Content: The page at 'https://www.shacknews.com/chatty' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://chattypics.com/upload.php'. This request has been blocked; the content must be served over HTTPS.

That's unfortunate. I think Matt Burris owns the site. Maybe someone can convince him to run certbot against his server and turn on SSL?

I'm not sure whether I should make a separate issue for this, but I'm considering doing a PR adding Gfycat support to the image uploader seeing as the image embedder already has display support. This would just be another alternative in case Chattypics stops working and people don't want to use Imgur.
Would this be a reasonable idea?

I agree that we should just move away from chattypics all together as a community. It was cool at the time but it just seems to be more trouble than it’s worth for everyone involved at this point.
... he says not wanting to update his own app

I like chattypics and don’t want to lose all those lol’d images.  :/
On Thu, Oct 25, 2018 at 6:41 PM Willie Zutz<EMAIL_ADDRESS>wrote:

I agree that we should just move away from chattypics all together as a
community. It was cool at the time but it just seems to be more trouble
than it’s worth for everyone involved at this point.
... he says not wanting to update his own app
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arhughes/chromeshack/issues/82#issuecomment-433229470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABOtnD8Vo_xCW4dziJ1qAsaQwHqzfWPks5uoj4KgaJpZM4X5QXv
.

I messaged M. Burris on the Chatty as a first attempt to get in touch with him since we was last active today, and I pointed him at this issue ticket so hopefully he'll work with us to get something sorted.

I don't think anyone actually uses this script in ChromeShack; I discovered it was broken in the current release when I was testing @WombatFromHell's Firefox port.  I just want to do whatever is the minimum required to get it working again.  I bet Matt will be receptive to setting up HTTPS, as we only need it for the upload script and we don't need to actually access images over HTTPS, which could be tricky since he hosts those separately on Dream Objects.

I believe this is the relevant doc for configuring Let's Encrypt for DreamHost shared hosting: https://help.dreamhost.com/hc/en-us/articles/216539548-How-do-I-add-a-free-Let-s-Encrypt-certificate-

M. Burris got back to me about Chattypics, and he's fixed his server by enabling HTTPS and installing a proper SSL certificate. We should be able to just change the Chattypics URL to use the HTTPS protocol and call it a day.
Let me know if you want me to fork a PR for this or not.


Quick fix to darksidewalletd docs, will need improvements

Merging this without review because I urgently need it before a meeting with Aditya, I opened https://github.com/zcash/lightwalletd/issues/290 to come back later and make improvments.