test_str for some Unicode strings fails in Windows 10

In Windows 10 64-bit: When running the test suite via the cmd (>setup.py test...) or via Cricket, test_str in all suites fails with the following error:
AssertionError: '>>> [321 chars]abs\n>>> x = "Mÿ hôvèrçràft îß fûłl öf éêlś"\n[319 chars]==\n' != '>>> [321 chars]abs\n<class \'UnicodeEncodeError\'> : \'charma[341 chars]==\n'
More details:
tests.builtins.test_any.BuiltinAnyFunctionTests.test_str

Traceback (most recent call last):

  File "C:\python34\Lib\unittest\case.py", line 57, in testPartExecutor
    yield

  File "C:\python34\Lib\unittest\case.py", line 574, in run
    testMethod()

  File "c:\Users\Harry\pybee\voc-dev\voc\tests\utils.py", line 1037, in func
    substitutions=getattr(self, 'substitutions', SAMPLE_SUBSTITUTIONS)

  File "c:\Users\Harry\pybee\voc-dev\voc\tests\utils.py", line 1075, in assertBuiltinFunction
    run_in_function=False,

  File "c:\Users\Harry\pybee\voc-dev\voc\tests\utils.py", line 399, in assertCodeExecution
    self.assertEqual(java_out, py_out, context)

  File "C:\python34\Lib\unittest\case.py", line 794, in assertEqual
    assertion_func(first, second, msg=msg)

  File "C:\python34\Lib\unittest\case.py", line 1167, in assertMultiLineEqual
    self.fail(self._formatMessage(msg, standardMsg))

  File "C:\python34\Lib\unittest\case.py", line 639, in fail
    raise self.failureException(msg)

AssertionError: '>>> [157 chars]any\n>>> x = "Mÿ hôvèrçràft îß fûłl öf éêlś"\n[154 chars]==\n' != '>>> [157 chars]any\n<class \'UnicodeEncodeError\'> : \'charma[231 chars]==\n'
  >>> f = any
  >>> x = ""
  >>> f(x)
  False

  >>> f = any
  >>> x = "3"
  >>> f(x)
  True

  >>> f = any
  >>> x = "This is another string"
  >>> f(x)
  True

  >>> f = any
+ <class 'UnicodeEncodeError'> : 'charmap' codec can't encode character '\u0142' in position 28: character maps to <undefined>
- >>> x = "Mÿ hôvèrçràft îß fûłl öf éêlś"
- >>> f(x)
- True

  >>> f = any
  >>> x = "One arg: %s"
  >>> f(x)
  True

  >>> f = any
  >>> x = "Three args: %s | %s | %s"
  >>> f(x)
  True

  ===end of test===
 : Global context: Error running f(x)

The problem here appears to be rooted in the environment. Specifically, the codepage of the console (terminal) is not utf-8.
I can't be 100% sure of this, since I do not have Windows 10, however see this SO answer for a similar situation. If you have Windows 10, feel free to try running chcp 65001 before running the test. If that makes the error go away, then I would feel fairly confident this is what's going on.
I have found some activity starting in August 2016 addressing this problem directly in Python:
https://www.python.org/dev/peps/pep-0529/
http://bugs.python.org/issue1602
Could someone (who has seen this behavior in Windows) try updating Python to see if that resolves the error?
I looked for a way to change the parent terminal's encoding directly from python, however I saw no obvious solutions. It is possible that executing the chcp command from within python would resolve the problem, but that's a platform-dependent fix. I have no way of even testing that without Windows 10, and if there is a native Python way of getting the same effect, that would be preferable.
Note about non-Windows environments:
The same type of behavior can occur on other platforms, however most use UTF-8 by default.
I was able to cause a similar failure of the test in Ubuntu by creating a custom charset (CP850 in my case,) compiling a locale with it, and changing my LANG environment variable to reference the new locale/charset combo.
The basic process is laid out in this SO answer, however they were making a custom locale and I was making a custom charset.


Favorites tab no longer updates

The Favorites tab no longer updates with new images.  I changed the "last viewed" time to an earlier time and it still doesn't update.  If I add new favorites, they don't update either.  However, I can still manually search the tags in a new tab.  Any ideas?

Did you make sure to use a source that supports date-based search or gives date information when searching?
Since it happens now that Gelbooru has blocked its API, I guess you're using it? The fallback from the Gelbooru API (regexes) does not give out date information.
I'll try to look for alternates methods for favorites on Gelbooru but in the meantime I advice you switch to another source :)
On the 10/15/15 at 10:47PM, lozertuser said:

We are working on updating the API to prevent future abuse. It will be some time until this happens though due to me wanting it to be compatible with 0.3's application of access keys. Just waiting on Geltas to commit his working version to the SVN.

Oh, sorry. I forgot to mention that the main source was Gelbooru.  I guess having their API not public anymore would cause this.  Oh well.  I can continue to do manual searches.
Thanks for the reply and great job on the application :smiley:

If you want to keep using Gelbooru for favorites, you have to set-up your credentials in Gelbooru's settings window to access their API.


Prefix for vector processes?

Originates from https://github.com/Open-EO/openeo-processes/pull/382#issuecomment-1385610604
Should we change the vector_ prefix for the vector-related processes to something else?
After thinking a bit more about it, I think vector_ is fine. We still have a vector data cube as input, only the dimension is using the geometry terminology. As the prefixes do usually reflect the type of data you are passing in (i.e. vector data cube), we can stick with the names. Also to preserve a bit of backward compatibility with some rare implementations.
Other opinions?

Voted to be vector (4, 1, 2)


Update to recent version of 'hakyl' and GHC

This repository it very old... But it is the only simple example that has Hakyll with Bootstrap. Also, the first googlable... I will really appreciate updating this repo!

Using Stack it would probably take like an hour to update it to modern Hakyll

@sdiehl I can try to update it later via Pull Request. Currently I'm working on website with Hakyll + Bootstrap. So this shouldn't be so hard to do...

@ChShersh This should be updated for modern GHC and Haskell. Let me know if this fixes your problem.


Unify DevTools UI and Scaffold UI styles

Descriptions
Integrate the styles between DevTools UI and Scaffold UI.

We'll be moving away from "DevTools UI" (aka the Welcome screen), so this is no longer relevant.


Duplicate keys in supplies dataset?

🐛 Describe the bug
% pipx run jafgen
...

% head -n1 jaffle-data/raw_supplies.csv
id,name,cost,perishable,sku

% cat jaffle-data/raw_supplies.csv | grep SUP-001
SUP-001,compostable cutlery - knife,7,False,JAF-001
SUP-001,compostable cutlery - knife,7,False,JAF-002
SUP-001,compostable cutlery - knife,7,False,JAF-003
SUP-001,compostable cutlery - knife,7,False,JAF-004
SUP-001,compostable cutlery - knife,7,False,JAF-005

Instead of one row per id value, there appears to be one row per id and sku combination. Is this intentional perhaps? I expected one row per ID and not sure how to interpret one row per id per sku.
Versions
% python --version
Python 3.10.6

Looks like this is by design.
https://github.com/dbt-labs/jaffle-shop-generator/blob/0806cb627139238225503f019af042e4aa39f92e/jafgen/stores/stock.py#L26-L130
I'll apply id and sku as composite primary key for supplies, per code above.


do not set provisioningNetwork in acm_setup role

currently in deployments with IPI provisioningNetwork is set to Managed and that requires extra provisioning* parameters to define the CIDR, IP, and Range, but in Assisted mode none of that information is set or required.
This change removes the provisioningNetwork definition when adding watchAllNamespaces:true to allow compatibility with Assisted Installer

@manurodriguez let me know when you feel comfortable for this PR to be merged, I saw the successful runs but not sure if you have some more tests in mind.

@manurodriguez let me know when you feel comfortable for this PR to be merged, I saw the successful runs but not sure if you have some more tests in mind.

Thanks @thekad I'm going to merge now, apologies for the delay and lots of tests without more details, till yesterday we were able to sync about the final changes, but we tested all the scenarios now,   I avoid the need to use facts from the agent, but I agree that if needed we need to find a way to pass them to the collections and document them as requirements.
More details in https://issues.redhat.com/browse/CILAB-1283
Thanks


Update subler to 1.3.5

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] sha256 changed but version stayed the same (what is this?).
I’m providing public confirmation below.

Thank you for the contribution. It was merged directly as<PHONE_NUMBER>aa313fc3754a93c96d65e24e8c2052. Your contribution is still credited to you.


sim4life LB points to one manager instead of all

As soon as this merged https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/merge_requests/403, we can close it


⚠ Fox Sports has degraded performance

In 504a94d, Fox Sports (https://foxsports.com) experienced degraded performance:

HTTP code: 200
Response time: 1640 ms

Resolved: Fox Sports performance has improved in f2d8502.


Update node wrapper dependencies

Signed-off-by: Patrik Stas<EMAIL_ADDRESS>

Codecov Report

Merging #472 (ca5a33d) into main (7a45070) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #472   +/-   ##
=======================================
  Coverage   60.27%   60.28%
=======================================
  Files         154      154
  Lines       14543    14558   +15
  Branches     3586     3586
=======================================
+ Hits         8766     8776   +10
  Misses       2382     2382
- Partials     3395     3400    +5

Flag
Coverage Δ

integration-aries-vcx
47.47% <ø> (+0.03%)
:arrow_up:

unittests-agency-client
26.08% <ø> (ø)

unittests-aries-vcx
49.35% <ø> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../src/protocols/connection/inviter/state_machine.rs
64.57% <0.00%> (-0.33%)
:arrow_down:

.../src/protocols/connection/invitee/state_machine.rs
65.28% <0.00%> (+0.17%)
:arrow_up:

aries_vcx/src/libindy/utils/ledger.rs
36.87% <0.00%> (+1.79%)
:arrow_up:

Continue to review full report at Codecov.

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


Exclude TextIO from FlinkRunner integration tests

I'm not 100% that this is the best thing to do, if there is some other simple and surgical fix. But this is how you would disable the test.
CC: @aljoscha Reuven is adding windowed text file writes, and the Flink runner's override causes some problems here. Is it still needed? Any other feedback or advice is welcome.

@kennknowles Are you referring to TextIOWriteBoundStreamingTranslator and WriteSinkStreamingTranslator? If yes, then I think it's time to remove them. Even more so if they cause problems.


Stunner: Differences assessment of the Stunner codebases (BPMN/DMN/SCESIM vs SWF)

As a result of the project management changes announced 10 months ago, the Stunner codebase has been forked in two different streams:

BPMN/DMN/SCESIM stream
SWF (Serverless Workflow) stream

In the last months, several bug fixing, improvements, and new features have been merged in stream 2. We need to evaluate which of those changes are worthy to be "cherrypicked" in stream 1.

@yesamer to me it seems, we have in codebase now 3 clones of appformer/uberfire. Is addressing it somehow part of #47 too?

@jomarko Yep good point. I would suggest ignoring the Dashbuilder fork because I consider it a totally separate project from ours. In addition, I don't see any valuable fix/feature in its stunner modules  (https://github.com/kiegroup/kie-tools/commits/main/packages/dashbuilder/appformer), these are mostly dependencies for security updates and Dashbuilder-specific issues. WDYT?

My point was rather, aren't we building the same three times during CI for example?

@jomarko Our CI/CD is smart enough to build the modules related to PR changes. Eg. if you modify something on DMN Editor module, the CI will build its parent modules only, and not all the modules in kie-tools. Please correct me if I'm wrong @tiagobento

I completed my analysis (with @romartin support, thank you, man!)
Fix and Performances fixes to "cherrypick" (Higher Priority)

KOGITO-6974: SWF Diagram Editor - Line control points are enabled in view-only mode, but they should not https://github.com/kiegroup/kie-tools/pull/943
KOGITO-7736: SWF Viewer - Performance improvements https://github.com/kiegroup/kie-tools/pull/1248

Nice to have new features (Lower Priority)

KOGITO-7108: SWF Viewer - Fit diagram into canvas (default size)  https://github.com/kiegroup/kie-tools/pull/997
KOGITO-7078 : SWF Viewer connector Labels https://github.com/kiegroup/kie-tools/pull/1237
KOGITO-7199: SWF Viewer - Usability improvements for mediators (Mouse Pointers) https://github.com/kiegroup/kie-tools/pull/1123

All other PRs are related to SWF only.
The tickets of the first list can be cherrypicked as a 1:1 copy.
The tickets of the second list require integration with the editors, so the required effort is higher.
For this ticket scope, my proposal is to cherrypick the items of the first list only

KOGITO-6974 - DONE
KOGITO-7736 - Discarded: Performance improvements are not significant in BPMN/DMN/SCESIM stream. Please check https://github.com/kiegroup/kie-tools/pull/1357 for further consideration.


investigate load_contacts() importing into My Contacts

Currently, loads into Other Contacts in GMail interface
Verify this is does not block get_contacts()

not a blocker ... closing


Export variables should support other data types

Current definition is a map<string,string> but it should be a map<string, google.protobuf.Value>

Unfortunately, changing this is going to break existing deployments using a DB backend because the policies are stored in protobuf encoding and any data type change would make those policies undecodable.

So, the map values would either be a constant value to be used directly as the value of the variable, or a CEL expression to evaluate to produce the value of the variable? How would we distinguish between a "raw" string and an expression?
At the moment we have definitions: map<string, string>, what if we just introduced an additional field constants: map<string, Value>, so that definitions contains CEL expressions and constants contains raw values?

So, this originally came up because someone asked how to define an array variable. The answer is to use a stringified representation (e.g. x: "[1,2,3]") and Cerbos converts it to an array at runtime because it evaluates the string as a CEL expression. That's what got me thinking whether we could change the data type from string to google.protobuf.Value and let users write "native" lists, maps etc.
I don't know whether introducing a constants field is worth it for fixing this minor annoyance. It might even confuse the users because they now have two options to pick from.

I think changing the data type would be too confusing (e.g. if the list had string values, are those literals or CEL expressions?). I also agree it's probably not worth introducing another field. Shall we close this one as wontfix then?


Using nbformat instead of json

Issue #123

Thanks for working on this @AntHoneyLam !
I'm away for the weekend so I can't look closely for a bit but will next week. But preliminarily I think you will need to add nbformat to the docs requirements in setup.cfg to get the docs to build.
Also I think it may be possible to do the output modification using nbformat? If that is possible it would be good to do as well.

The docs failure:
looks real with this error:

Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/envs/200/lib/python3.7/site-packages/sphinx/config.py", line 323, in eval_config_file
    exec(code, namespace)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/checkouts/200/docs/conf.py", line 26, in <module>
    gogogo_all("../examples", "examples/")
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/checkouts/200/docs/gifmaker.py", line 17, in gogogo_all
    gogogo_gif(nb, to)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/checkouts/200/docs/gifmaker.py", line 50, in gogogo_gif
    nbformat.write(nb, f)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/envs/200/lib/python3.7/site-packages/nbformat/__init__.py", line 164, in write
    s = writes(nb, version, **kwargs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/envs/200/lib/python3.7/site-packages/nbformat/__init__.py", line 110, in writes
    return versions[version].writes_json(nb, **kwargs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/envs/200/lib/python3.7/site-packages/nbformat/v4/nbjson.py", line 54, in writes
    nb = split_lines(nb)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mpl-interactions/envs/200/lib/python3.7/site-packages/nbformat/v4/rwbase.py", line 81, in split_lines
    if output.output_type in {'execute_result', 'display_data'}:
AttributeError: 'dict' object has no attribute 'output_type'

which is because when this was just a dict it was ok to overwrite the output with a custom made dictionary. but now nbformat expects the output to be some sort of nbformat object. So we need to change this parts:
https://github.com/ianhi/mpl-interactions/blob/74966bcc43bca45890151329f19ca0004b1de538/docs/gifmaker.py#L40-L47
to use https://nbformat.readthedocs.io/en/latest/api.html#nbformat.v4.new_output
you can test this locally from the terminal by going to the docs folder and running make html.


WIP: Added converters via UnityEngine.JsonUtility

Inspiration from https://github.com/jilleJr/Newtonsoft.Json-for-Unity/issues/28#issuecomment-579997306
This is not a bulletsafe solution, as can be shown by some failing tests. The following serialization/deserialization fails for the follow (tested) types:

BoundsInt
Bounds
NativeArray (only deserializing fails)
RectInt
Rect
Vector2Int
Vector3Int

Closed in favor of #7 due to base branch change.


Improve handling of alert failures

We should make sure to do the right thing when sending a fatal alert fails. What is the right thing?

If sending the alert fails because the peer has already closed the connection, there is nothing else to do, we can ignore the failure.
If sending the alert returns MBEDTLS_ERR_SSL_WANT_WRITE, we should probably let the caller know that it must retry, i.e. propagate MBEDTLS_ERR_SSL_WANT_WRITE and return the error that triggered the alert on a subsequent call. To be reviewed, there may be cases where it's important to return the error immediately.
Other cases?

Historically the behavior has been inconsistent. PR #892 (scheduled for mbed TLS 2.5.0) changes the behavior to systematically ignore the failure.
ARM Internal Ref: IOTSSL-1385

ARM Internal Ref: IOTSSL-1402

As far as I remember, alert failures are still not handled fully consistently. It is good enough in practice, so maybe this issue should be relabeled as enhancement?


Basic Cryptarchia fuzz test

This contains a basic fuzz test for Cryptarchia. This doesn't cover all possible cases, but I'd like to draw a line here and discuss if this testing strategy is good to move on.
Testing strategy
The Proptest State Machine testing suggests us to mimic the core logic into the ReferenceStateMachine, so that it can be used to generate state transitions and can be compared to the real state machine (aka. SystemUnderTest; SUT) to ensure that the real state machine works as intended.
I tried it at the beginning, but found that defining a minimal essential logic from the whole Cryptarchia to be mimicked is not simple. Even if I mimicked a certain logic that I thought essential, the ReferenceStateMachine and SUT didn't work because of missing logic that I didn't mimic.
Instead of mimicking, I end up using the real logic for both ReferenceStateMachine and SUT (that we want to test).

ReferenceStateMachine is a leader node that proposes new blocks.
But, the new blocks are sent to the SUT (a follower node) in random order.
SUT processes blocks in the order they arrive.

In overall, the SUT must always follow the leader chain eventually. However, the follower's chain in the SUT may not grow at this moment, because there is a missing logic (requesting missing parents) in both real code and tests.
NOTE
Unlike Carnot fuzz, I added Cryptarchia fuzz test under the {root}/tests because the entire Cryptarchia is split into multiple crates (engine, ledger, and core). At the beginning, I tried to write fuzz tests for each crate but end up thinking it's not beneficial than I thought.
TODO
We may be able to diverse the testing strategy as below:

Making the leader creates several forks intentionally or having multiple leaders in the ReferenceStateMachine, in order to test how the follower handle forks.

This PR has been opened for a long time. I don't think this fuzz test is not so beneficial. It would be better to add fuzz tests after having enough unit tests first. Currently, I think this fuzz test is not intuitive and not easy to maintain. I'm closing this PR for now, but please provide your opinion if you have other thoughts.


Bug Report: Deny-MgmtPorts-From-Internet.json

Describe the bug
The policy checks for the source address to be * or Internet, but doesn't check for <IP_ADDRESS>/0.
Per https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview
"<IP_ADDRESS>/0 in the Source and Destination columns represents all addresses"
Steps to reproduce

Deploy policy in deny mode.
Create an NSG, and allow port 22 from <IP_ADDRESS>/0 address range.
Note, policy is compliant.

@Springstone can you take a look

Opened PR: https://github.com/Azure/Enterprise-Scale/pull/1768


DEPR deprecate hub_utils.get_model_output

This deprecates the function, to be removed in the next released.

@BenjaminBossan so should we merge?


refactor: add headroom/legroom wrapper elements

Introduce headroom / legroom wrapper divs to improve UX:

Not require content to be single child
Not require functional components used as content to implement ref forwarding in order to fix the Function components cannot be given refs error.

👍🏻


Update post-processor to provide nicer feedback

Error out more quickly if local and remote_vm are specified together.
Provide clearer feedback when performing local-only registry action(s).

Signed-off-by: Tom Duffield<EMAIL_ADDRESS>

Hey @tduffield , feel free to merge whenever you're comfortable :)


Does not install directly from uv

Describe the bug
reloadium.corium is not found when running from uv
To Reproduce
Install https://docs.astral.sh/uv/getting-started/installation/
~\test> uv venv --python 3.11                                                                                05 Nov 2024 19:00:59
Using CPython 3.11.10
Creating virtual environment at: .venv
Activate with: overlay use .venv/Scripts/activate.nu
~\test> uv pip install reloadium --python 3.11                                                                         05 Nov 2024 19:01:04
Resolved 1 package in 8ms
Installed 1 package in 42ms
 + reloadium==1.5.1
~\test> uv run reloadium --python 3.11                                                                                05 Nov 2024 19:01:10
It seems like your platform or Python version are not supported yet.
Windows, Linux, macOS and Python 64 bit >= 3.8 (>= 3.9 for M1) <= 3.11 are currently supported.
Please submit a github issue if you believe Reloadium should be working on your system at
https://github.com/reloadware/reloadium
To see the exception run Reloadium with environmental variable RW_DEBUG=True
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\giuli\test\.venv\Scripts\reloadium.exe\__main__.py", line 5, in <module>
  File "C:\Users\giuli\test\.venv\Lib\site-packages\reloadium\__init__.py", line 4, in <module>
    pre_import_check()
  File "C:\Users\giuli\test\.venv\Lib\site-packages\reloadium\__utils__.py", line 24, in pre_import_check
    import reloadium.corium
ModuleNotFoundError: No module named 'reloadium.corium'

Expected behavior
~\test> uv run reloadium --python 3.11                                                                                05 Nov 2024 19:01:10
No command provided

Desktop or remote (please complete the following information):

OS: Windows
OS version: 11
M1 chip: no
Reloadium package version: 1.5.1
PyCharm plugin version: none
Editor: none
Python Version: 3.11.10
Python Architecture: 64bit
Run mode: Debug

Works though by downloading the windows whl package and installing through uv add --dev <file>


helm install abort with  Exception at <.Capabilities.APIVersions.Has>: nil pointer evaluating interface {}.APIVersions

Hi,
I am trying to install a chart I created and which evaluates fine using "helm template" on our kubernetes test server.
But when I try to install the chart the Capabilities do not seem to be set and I get the following error:
Error: template: empower/charts/discoveryapi/templates/ingress.yaml:40:34: executing "empower/charts/discoveryapi/templates/ingress.yaml" at <.Capabilities.APIVersions.Has>: nil pointer evaluating interface {}.APIVersions
What I am trying to do is to choose the correct ingress api version depending on the capabilities of the server:
{{- if .Capabilities.APIVersions.Has "networking.k8s.io/v1/Ingress" -}}
apiVersion: networking.k8s.io/v1
{{- else -}}
apiVersion: networking.k8s.io/v1beta1
{{- end }}
The command I am using to try the installation is:
sudo helm install -f values.yaml -n empower-dev empower-dev ./empower --dry-run
What could be the problem that it is not working correctly on the server.
Thanks.
Best regards
Christopher Black
Output of helm version:
version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.15.8"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.10", GitCommit:"62876fc6d93e891aa7fbe19771e6a6c03773b0f7", GitTreeState:"clean", BuildDate:"2020-10-15T01:52:24Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.10", GitCommit:"62876fc6d93e891aa7fbe19771e6a6c03773b0f7", GitTreeState:"clean", BuildDate:"2020-10-15T01:43:56Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): selfhosted kubelet on ubuntu 18.04

This can occur if you're invoking this if clause within a for loop or from within another context. Go's context of the dot operator (.) changes scope in these blocks.
https://golang.org/pkg/text/template/
One way to work around this is to try using the global operator ($). That will allow you to reference the root scope from anywhere EXCEPT in define blocks, as those are separate function calls where the root scope changes to the input of the function call.
In other words try this:
$.Capabilities.APIVersions.Has

Yes I was using it in a for loop.
But if I change that part to the global values other values can no longer be accessed.
It works fine with the default values defined for the chart but as soon as I use the values.yaml (which I also use for a version without capabilities check, where it works fine) an new error occurs:
"YAML parse error on empower/charts/discoveryapi/templates/ingress.yaml: error converting YAML to JSON: yaml: line 19: mapping values are not allowed in this context".
The line number matches the first line after "spec:"
{{- if .Values.ingress.tls }}
Here is my current yaml template:
{{- if .Values.ingress.enabled -}} {{- $fullName := include "discoveryapi.fullname" . -}} {{- $svcPort := .Values.service.port -}} {{- if .Capabilities.APIVersions.Has "networking.k8s.io/v1/Ingress" -}} apiVersion: networking.k8s.io/v1 {{- else -}} apiVersion: networking.k8s.io/v1beta1 {{- end }} kind: Ingress metadata:   name: {{ $fullName }}   labels:     {{- include "discoveryapi.labels" . | nindent 4 }}   {{- with .Values.ingress.annotations }}   annotations:     {{- toYaml . | nindent 4 }}   {{- end }} spec:   {{- if .Values.ingress.tls }}   tls:     {{- range .Values.ingress.tls }}     - hosts:         {{- range .hosts }}         - {{ . | quote }}         {{- end }}       secretName: {{ .secretName }}     {{- end }}   {{- end }}   rules:     {{- range .Values.ingress.hosts }}     - host: {{ .host | quote }}       http:         paths:           {{- range .paths }}           - path: {{ . }}             pathType: Prefix             backend:               {{- if $.Capabilities.APIVersions.Has "networking.k8s.io/v1/Ingress" -}}               service:                 name: {{ $fullName }}                 port: {{ $svcPort }}               {{- else -}}               serviceName: {{ $fullName }}               servicePort: {{ $svcPort }}               {{- end }}           {{- end }}     {{- end }} {{- end }}
What could be the problem.


⚠ Bofrost.be has degraded performance

In 7e38dc7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 907 ms

Resolved: Bofrost.be performance has improved in b12e3f5 after 23 minutes.


Like operator and int64 not working together with HibernateTemplate

With an Oracle database table with a column named Data with type NUMBER(16,0) I could with old versions of Spring.Net and nHibernate write an HQL and use the like operator like done in regular SQL:

string query =
"from TD.Common.DataObject.TDDetectorFileInfo as info where info.Data like ?";
object[] values1= new object[1];
object[] values2 =new object[1];
values1[0] = "19911111000000"
values2[0] = "1991111100000%"
var res = HibernateTemplate.Find(query, values1);
var res2 = HibernateTemplate.Find(query, values2);

I expect to get the same result in res and res2 since the like operator in Oracle can be applied to numbers.
Using Spring.Net 2.0.1 and NHibernate4 I instead get an expection for the res2 call.
Inner exception text: "Failed to convert parameter value from a String to a Decimal."

My friend. I don´t understand. Your field type on DB is NUMBER and you passes string on variables "values1" and "values2". have you tried using string cast to decimal?

Thank you for the input. Unfortunately the LIKE operator without being able to use the wildcard character '%' is pretty much pointless.
On the other hand further study of problem has made me suspect that the problem is not really located in Spring.Net. The NHibernate project has marked the API that uses the HQL syntax as deprecated. It seems likely NHibernates project has made the move to require typed parameters and the LIKE operator used in HQL suffer from this decision.
Currently I am considering to change API used for these calls. There is no strict requirement to stay with using the HQL syntax and I expect better performance if I avoid HQL.

Have you tried changing the HQL by Criteria or Linq to NHibernate?

I'm doing a rude experiment with closing this, like what stale bot does, but maybe more human as I will probably actually react to feedback. As this issue has been stale for so long, I'll close it. If it's still an issue you would like to pursue, we can definitely reopen.
With limited resources this is just something that we need to do. Thank you for your understanding.


Fix handling an empty priority

Per http://xmpp.org/rfcs/rfc3921.html#rfc.section.<IP_ADDRESS>
“If no priority is provided, a server SHOULD consider the priority to be zero.”

Maybe a matching test? :pray:

@benlangfeld test added

Could you please repeat this PR against the master branch? The dev branch is no longer used.

 I cherry-picked cleanly. All done :)


escrow authorization: authorize deployment payment

Overview
We would like to be able for an account to be able to pay for deployments owned by any number of other accounts.
The first use-case for this will be to give users free hosting for some amount of time, without transferring them tokens.
Background
Authz
Newer versions of cosmos-sdk include an authz mechanism that allows for one account to authorize actions for other accounts.
Escrow
Akash uses a so-called escrow accounts for lease payments.  This escrow mechanism is implemented in a standalone module x/escrow.
The escrow account is currently funded from the account that owns the deployment.  Funds are transferred from the owner account to the escrow account in two transactions:

when creating the deployment
when "topping up" the escrow account.

When a deployment is closed, any balance remaining in the escrow account is currently returned to the owning account.
Requirements
Create a set of authorization objects that can be used to allow a separate account to both fund the deployment escrow account and receive remaining balances from the escrow account when the deployment is closed.

funding account must be able to fund deployments for any number of other accounts.
funding account must be able to declare maximum limit of funding for each account.
funding account must be able to de-authorize any unused funding amount.
an escrow account may have only one non-owner funding account
deposits to the escrow account after deployment creation can be made by either the owning account or the authorized funding account.

Note, to begin with, this authorization is only for authorizing spending - the deployment owner controls all other aspects of the deployment, including:

the funding account cannot close the deployment.
the funding account cannot restrict which providers are able win leases for the deployment.

CLI
Create a set of akash tx, akash query commands that enable, use, and report on deployment payment authorizations.
Example workflow:
# allow "deploy-wallet" to use 20AKT for deployments from "funding-wallet"
akash tx escrow authorize $(akash keys show deploy-wallet -a) 20000000uakt --from funding-wallet

# create a deployment from "deploy-wallet" that is paid for by "funding-wallet"
akash tx deployment create --payment-from $(akash keys show funding-wallet -a) --from deploy-wallet

# view authorizations created by the funding wallet
akash query escrow authorizations $(akash keys show funding-wallet -a)

# reduce amount for an authorization
akash tx escrow update $(akash keys show deploy-wallet -a) 10000000uakt --from funding-wallet

# deposit additional funds from the owning account
akash tx deployment deposit --dseq 1 --from deployment-wallet

Super excited about this!

Question: It might happen that an escrow account can get funded by both the funder and the deployment owner. Let's say while creating the escrow account:

it was funded by the funder with 5akt
then 3akt were deducted from it as provider's fees
then the deployment owner added 10akt to the escrow account
2akt got used again as provider's fees
then the deployment owner decided to cancel the lease, so the escrow account needs to be closed.

In this situation, the escrow account has 10akt left. The funding wallet had only sent 5akt to the escrow while the deployment owner had sent 10akt. If we send the remaining 10akt to the funding  wallet, then it doesn't seem fair. What should we do?
Possible Solution:
In escrow account for app deployment we maintain two seperate balance.

Direct fund(Pays from deployment wallet)
Allowance(Pays from funding wallet)

We prioritize spending from Allowance and then use Direct fund.
In case of lease cancel, we return back Direct fund to the Deployment wallet and Allowance to Funding wallet.

Maintaining two separate balances could work, but only if there was a single external funding account. I think we want any number of external accounts to fund any single deployment. Is that accurate @boz ?

It's okay if we have just one external funding account.  if it can be made more general and allow for multiple in a clean way* then that would be great.
*maybe always have one active payer, and order by (external?,time created).

In that case the solution proposed by @arijitAD sounds good to me.


Add roundtrip parsing/rendering

Fixes #12
Until now, this library could parse Commonmark into other formats, but not back into Commonmark format. This is understandable, as the Commonmark spec itself uses conversions to HTML to depict compliance. However, with the new CoreCommonMarkNodeRenderer it becomes possible to render Commonmark once it has been parsed - a "roundtrip" rendering. Usage is identical to HtmlRenderer.
KNOWN ISSUE:

If using IncludeSourceSpans.NONE (the default) or IncludeSourceSpans.BLOCKS, 4 test cases related to link reference definitions (193, 195, 198, and 217) will fail. In all cases it's due to line breaks, this is the only data structure where I couldn't find another way (besides SourceSpan) to track the line number if newlines occur. Use of IncludeSourceSpans.BLOCKS_AND_INLINES is recommended for 100% Commonmark roundtrip compliance.

DETAILS:
This is a relatively large PR. I have attempted to keep backwards compatibility whenever possible, but it's uncertain whether this update may break extensions to the core specification. Core specifications are confirmed to all pass.
In order to achieve this roundtrip functionality, new fields have been added to the various Commonmark nodes, and many changes to parsers have been added to populate these new fields. The commonmark-java library is geared towards conversion to HTML already, so I have chosen to keep that functionality and its optimizations intact and build extra structures on top of that approach rather than trying to rewrite what has already been done.
The one change which departs from existing functionality is the addition of a new BlankLine node type. This node represents a concept explained in the Commonmark spec (blank lines), but it is not truly defined in the spec as a Commonmark block. BlankLine should be treated as SourceSpan already is - a utility class that helps to describe the structure. (Speaking of SourceSpan, I have elected to keep them tracking the HTML wherever possible rather than the raw text in order to avoid breaking changes.)
The BlankLine class is specifically ignored in HTML rendering and is only currently used by the roundtrip rendering to fill in gaps which otherwise can't be determined from the parsed AST tree. In this way, existing plugins can render to other formats the same as they always have, but will also have the option of rendering back to Commonmark.

Hey! Just wanted to let you know that I haven't gotten around to review this yet, but it sounds promising :)!

Use of IncludeSourceSpans.BLOCKS_AND_INLINES is recommended for 100% Commonmark roundtrip compliance.

I think that's reasonable. As long as without the option, we can produce equivalent output (but not source-identital).

I'm glad it looks promising so far, just let me know if there's anything I can help with. :)

I think that's reasonable. As long as without the option, we can produce equivalent output (but not source-identital).

Yes, that's the case right now. The 4 test cases that fail would still render all other details of the link reference definitions (including most whitespace), they would just be missing any line breaks inside the link reference definition itself.

All individual comments addressed, a couple will need your comments.

1. I might have missed it but where are the tests?

Other than updating some of the internal tests where they had broken, I hadn't added new ones because most of what I have done are edits to existing work. I do see that I'm missing a test for the new renderer, but in my mind it also happened to be thoroughly tested by making sure all CommonMark tests cases are rendered correctly. (I also figured it would be a bit overkill to include all 652 CommonMark tests.) If you have suggestions for where you'd like to see more test coverage I will be happy to write them and push an update.

2. Have you run the benchmarks yet and compared to before your changes? I wonder if it makes sense to put the code for this behind an option (which would also automatically enable source positions). I'm not sure it's worth it, just thinking.

Other than the output for how long individual existing tests took, I couldn't see an obvious benchmarking method. Is there a wiki or document for how I could achieve this? I'm open to running the benchmarks, I just want to make sure that whatever I provide is an apples to apples comparison.

3. What are your thoughts about users that would like to generate an AST using code and then render to CommonMark? In that case, with the current implementation, users would have to use `setRaw` to get the desired rendering, otherwise they'd get invalid CommonMark, right (i.e. just `setLiteral` wouldn't be enough).

I think generating an AST directly, without going through parsing, is already risky without my changes and would continue to be about the same level of risk. Unless someone uses a DocumentParser.parse method in some way, they are skipping pieces of parsing logic. Even manually generating individual type parsers for some limited sanity checks would still be messy to stitch together.
My guess is that most people attempting to generate an AST would be directly making a tree of nodes. This means they have to be very confident they know things per node like the correct literal values, when lists are tight, when Text is in a Paragraph and when it's just by itself, etc. After my changes, they would also need to have confidence in where certain whitespace is and make sure that setRaw is used in addition to setLiteral. There's a little more that could go wrong once roundtripping is available, but I think someone encountering a problem with direct AST creation is already in the Land Of Dragons to begin with. 🔥 🐉

4. In general, I feel like it's a lot of tricky code additions. If you have any ideas on how to condense some of the parsing code, that would be great. Do you think something like `Scanner` for block parsers would help?

I agree that much of what is changed in the parsers, at least, is tricky. commonmark-java is not, from my outsider observations, a library that aims to natively roundtrip and also just happens to render to HTML. Rather, I encountered a lot of places where rendering to HTML is clearly its native focus. I'm dancing on the edges of that code and trying to capture information that was often not intended to be captured by an HTML-first design. I'm taking it as a large compliment that you haven't outright called this PR an ugly hack. 😃
As for ideas, I will say that I can't think of much which would also preserve this library's original intent. It would likely be much cleaner to start with a roundtrip object and split out what the HTML needs (as HTML rendering is usually heavily distilled from the raw). That would also probably be a ton of work, starting at DocumentParser.parse and going all the way through. On the plus side, at least if that ever happened the POJOs you needed for each data structure are already done... just sayin'!
(To answer your specific question, I think a Scanner for block parsers would be only partially useful from this PR's perspective. CommonMark seems to recommend parsing in a single pass, which means a scanner would be only able to deal with a single block and wouldn't have a good grasp of any relationships between blocks. It might, however, be able to identify the blank lines between blocks in a more intelligent fashion. If a block-level scanner parsing through raw contents knew that a previous block existed there would probably be ways to capture the blank lines between "previous" and "the current block".)

I believe all initial review comments have been addressed for now. I was able to successfully run a mvn clean package -P release on my local machine, which also helped in cleaning up several items that caused some of the extensions to fail tests.
No rush, just making sure I close the loop on your original review.

@ToWi87 I did not keep this PR in sync with the main repository, as it seemed like the PR wasn't going to be accepted.

is there someone active on this? I'd really like to see the roundtrip feature deployed

Seconded!

Hey @seii. You might have seen that I've implemented a MarkdownRenderer in https://github.com/commonmark/commonmark-java/pull/306 now. It's not perfect but it's a start and it focuses on producing equivalent Markdown, either from parsed nodes or from manually created nodes.
I'm sorry this PR didn't work out, closing it now.
I think the way forward for improving round-tripping should be a few focused smaller PRs, e.g. one for links, one for escaping, insignificant whitespace, etc. For each of those, the aim needs to be:

The data that is added to the nodes is additional, not a whole replacement of e.g. literal. But I think it also means that when a node tree is parsed from source, and then manipulated, some of that extra data needs to be reset in order not to produce an invalid output. E.g. if you parse a foo\!bar (unnecessary escape) as a Text, but then call setLiteral on it to change the text, the escape data needs to be cleared. (There is another option here, we could make nodes immutable once constructed but that's a bigger departure from the current API which is very mutable everywhere.)
If a node is constructed manually, the rendering still works and produces equivalent output. This should apply to the whole node tree or even if parts of it are processed.
It should not rely on IncludeSourceSpans being set. That doesn't mean the parser can't share some of the logic to achieve both, but from an API perspective, I think we should have good round-tripping without requiring source spans.


found block 0

thanks for this guide i try it with guncoin wallet and stratum server and all thing work fine but i have a problem always block found =0 and last block =0 i check the data base and i see that table block is empty .and table round is emty i passed 3 days mining i have 9000 shares but always last block found =0 and confirm block=00000 and unconfirmed =0000 how i resolve that?

Check your Stratum, Check your coind for created blocks. Probably not an MPOS issue unless this coin does something totally different than others.

what is the best coin that mpos support?


Support any F-Droid repo

https://github.com/EFForg/apkeep/commit/c30cda59d620ea58d747a310870154d13b0533b9 add supports for f-droid.org https://github.com/EFForg/apkeep/issues/5
F-Droid provides everything needed to run your own repository as well.
The only thing that'd change for those is the download URL and the fingerprint, the rest would stay the same.
Some example repos:

https://guardianproject.info/fdroid/
https://apt.izzysoft.de/fdroid/

It actually looks like a lot of repos are failing at https://github.com/EFForg/apkeep/blob/9cad87870675746682cbc7c87ded130e7483320e/src/fdroid.rs#L363, meaning that the signature in the certificate file does not match the contents of the signature file!
This looks to be the case for

https://apt.izzysoft.de/fdroid/repo?fingerprint=3BF0D6ABFEAE2F401707B6D966BE743BF0EEE49C2561B9BA39073711F628937A
https://rfc2822.gitlab.io/fdroid-firefox/fdroid/repo?fingerprint=8F992BBBA0340EFE6299C7A410B36D9C8889114CA6C58013C3587CDA411B4AED
https://divestos.org/fdroid/official/?fingerprint=E4BE8D6ABFA4D9D4FEEF03CDDA7FF62A73FD64B75566F6DD4E5E577550BE8467https://divestos.org/fdroid/official/?fingerprint=E4BE8D6ABFA4D9D4FEEF03CDDA7FF62A73FD64B75566F6DD4E5E577550BE8467

Even if the fingerprint of the signer is verified, the contents of the repo should not be trusted unless the signature matches the signed data!

https://gitlab.com/fdroid/fdroidserver/-/issues/94 includes example code and test cases for verifying JAR signatures
And apksigner's test suite has a number of test files to work with.  APK v1 signatures are JAR signatures, v2 and later are different, but usually include JAR signatures as well.
https://android.googlesource.com/platform/tools/apksig/+/refs/heads/master/src/test/resources/com/android/apksig

Doing the signature verification in pure rust isn't working for some reason.  Does every implementation of this that works call out to a foreign binary?
Regardless, in 29b454fd444ac3c9d4710ca36082c9633f91c03a I've added a 'verify-index' flag to allow users to bypass f-droid index verification.  It's not pretty but it works:
$ target/debug/apkeep -d f-droid -o repo=https://guardianproject.info/fdroid/repo,verify-index=false -a org.torproject.android .
Downloading F-Droid package repository...
Package repository downloaded successfully!
Extracting...
Downloading org.torproject.android...
org.torproject.android downloaded successfully!

Continuing this discussion in https://github.com/EFForg/apkeep/issues/65, since the issue of arbitrary repo support is resolved.


Move script to body instead of head

Was running into some issues (unrelated to this plugin) and noticed that according to the docs the script should be in the body tag, not the head tag! I've tested this locally and while I haven't actually noticed a difference in behavior it does not seem to change behavior of the plugin.

What: move pinit script to body instead of head

Why: the docs say "You’ll run into trouble if you place our script tag somewhere else, like in: The document’s head" and we sure don't want trouble!

Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged

Codecov Report

Merging #26 (ad01965) into master (e343be4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #26   +/-   ##
=======================================
  Coverage   60.00%   60.00%
=======================================
  Files           1        1
  Lines          10       10
  Branches        3        3
=======================================
  Hits            6        6
  Misses          2        2
  Partials        2        2

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 e343be4...ad01965. Read the comment docs.

This makes sense @robinske, thanks a lot for your contribution! (and for the nice PR description 🙏)

@all-contributors please add @robinske for code


         <%= react_component

   <!-- Comments Form -->
    <%= react_component("CommentsApp", { comments: @comments, replies: @replies, csrf_token: form_authenticity_token, post_id: @post.id }) %>

  </div>

does not work on ubuntu, no comments

Support requests filed as GitHub issues often go unanswered. We want you to find the answer you're looking for, so we suggest the following alternatives:
Coding Questions
If you have a coding question related to React and React DOM, it might be better suited for Stack Overflow. It's a great place to browse through frequent questions about using React, as well as ask for help with specific questions.
https://stackoverflow.com/questions/tagged/react
Talk to other React developers
There are many online forums which are a great place for discussion about best practices and application architecture as well as the future of React.
https://reactjs.org/community/support.html


Add Qiskit to QIR translation

New PyQIR interface landing soon, use this build for development: https://github.com/qir-alliance/pyqir/actions/runs/1842672161


set use_single_app_instance config through env var

Signed-off-by: Nima Kaviani<EMAIL_ADDRESS>

Please do not merge immediately, we just wanted to expose what we were doing, we still need to figure out how to solve for credhub

@sjolicoeur - since you want us to hold on integrating this, do you have tracker story that we can block this on?

@heyjcollins  here's the link to our story: https://www.pivotaltracker.com/story/show/159444743

And we are good to proceed with the PR

closing in favor of the upcoming PRs.


dependabot: change update frequency to monthly

Signed-off-by: Dorian Johnson<EMAIL_ADDRESS>cc @allisonsuarez @feng-tao

Summary of Changes

Tests

Documentation

CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes, including screenshots of any UI changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes all tests documented in the developer guide

Other repos were already monthly, so this is the last one


More informative errors for HMR errors

Description
Implements a new error overlay to replace the default Vite HMR error overlays.
This first version handles a few cases, but there are probably ~20 permutations to cover most of the HMR overlay errors a user can run into today.
The identification of the errors is not perfect, as it involves checking the code snippet we get from Vite and inferring which category the error should fall into for our users.
Error messages in this PR are placeholders, but we can include more descriptive messages and link out to docs as required.
Checklist

[ ] For UI or styling changes, I have added a screenshot or gif showing before & after
[ ] I have added a changeset

in the most recent commit, a new line is added to the svelte config. Initially I tried to add this to the config for the svelte vite plugin in vite.config as shown here (which feels like a better place for it), but that didn't work.

When I tried to trace the path that a warning takes in the svelte vite plugin, I noticed that svelte-tiny-linked-charts seems to generate a lot of work/noise for the preprocessor. I don't know for sure, but I suspect this has an impact on performance of the initial page load since it's duplicating a bunch of the workflows

We should deprecate this feature I think - we've talked about it before

What's the story on this PR currently?
cc: @mcrascal @Winterhart

@ItsMeBrianD I can take a look. It was paused during the USQL release, but I suspect it's good to go.

@ItsMeBrianD It's not ready to go -- I'm getting URL.split is not a function when trying to boot it up.

This one seems to be working on my end


Migrate to Appyx for navigation

[x] Read CONTRIBUTING.md.

Removing compose-destinations, which was giving me anxiety attacks, and replace it with Appyx.
Transition animations are gone, we should look into something fancy to replace them.
We will need to rethink our approach to hiding the navigation bar, there is no obvious way to check whether we have traversed a child node in Appyx.

Tested changes:
App still runs.

Closing this due to blockers with Appyx


bump msrv and crate versions, remove std::error references

I think we have just about all the changes that are reasonable to wait for for v0.2. All the breaking changes are pretty small, and the majority of users will likely only need to adjust MSRV
Breaking changes:

All error and internal structs marked as non_exhaustive to improve forward compatibility

Breaks anyone who was destructuring the De{format}Err structs
Can be fixed by non-exhaustively destructuring or just accessing error fields directly

binary/json/ron/toml formats split into feature flags, with all enabled by default

Breaks anyone who was using default-features = false before, but we didn't have any features so should be rare

no_std feature removed, added std feature which gates the couple remaining items (mostly HashMap/HashSet)

Breaks anyone who used the old no_std feature
Can be fixed by removing the no_std feature, and switching to default-features = false

Bump MSRV to 1.81 (for core::error::Error)

Breaks anyone who is on a rust version <1.81

Hardcode the nanoserde crate name (with override)

Breaks anyone who renamed the nanoserde crate and used the derive macros
Can be fixed using default name or the new nserde(crate="renamed") attribute

Other changes since last non-beta release:

Support for comments in JSON
Support for nserde(default) on non-Option types and
Bug fixes to float serialization, proxy attrs, along with toml and explicitly numbered enum parsing
Removed no_std hashbrown dependency

Check for toolchain '1.80.1-x86_64-unknown-linux-gnu' failed with:
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ error: rustc 1.80.1 is not supported by the following packages:                                         │
│<EMAIL_ADDRESS>requires rustc 1.81.0                                                                 │
│<EMAIL_ADDRESS>requires rustc 1.81.0                                                          │
└─────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Check for toolchain '1.82.0-x86_64-unknown-linux-gnu' succeeded
Check for toolchain '1.81.0-x86_64-unknown-linux-gnu' succeeded
   Finished The MSRV is: 1.81.0

Confirmed to work with MSRV of 1.81

@not-fl3 Anything else you want done before v0.2?


Provide conformity link from minions table

It should be easily possible to access conformity from an minion. The easiest solution is a link from the current minion table and status.

Sorry, i broke everything :disappointed:  could you please rebase or recreate this branch on develop?
Thanks for the PR!


 This appears here even though I did not ask for a new pull request, is that normal ?

Yes, is normal. All commits that you push to the same branch end up in this pull request.

Nice ! Did I actually ask a pull request ? I thought my changes would only concern by fork

I just clicked on "inspect " or something, I thought it was for my fork to accept the push to master but that was for the "official "project


Unable to trigger Custom Auth Challenge Lambda during sign up from iOS

Describe the bug
I am trying to setup custom flow auth with Cognito. I have created the Auth Define, Create & Verify Lambda functions up and running. Also in the client, configuration JSON , made sure default auth is CUSTOM_AUTH & enabled in the user pool client App configuration too. No matter what, when I try from iOS client with Amplify SDK, it always uses SRP_A and skips the lambda trigger.
Steps To Reproduce
Setup Custom Auth Flow
Set up Cognito User Pool
Trigger Sign up from iOS client App

Expected behavior
Should trigger the Auth Define Lambda function.
Amplify Framework Version
Latest
Amplify Categories
Auth
Dependency manager
Cocoapods
Swift version
5.3
CLI version
5.4.0
Xcode version
12.4
Relevant log output
No response
Is this a regression? (i.e. was this working before a version upgrade)
No response
Device
iPhone 12 Sim
iOS Version
iOS 14
Specific to simulators
No response
Additional context
No response

Please see the note under the "Define Auth Challenge" lambda trigger here, Amplify.Auth plugin currently starts the custom auth with SRP has the first step. You can work around this as mentioned in the lambda trigger.


⚠ Turnos 24x7 has degraded performance

In 81836fe, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 949 ms

Resolved: Turnos 24x7 performance has improved in e97696c.


Docs?

Hi.
Can you add some documentation about this module?
Tks

Yes, yes. Working on docs.

Docs now exist. I am closing this, but do feel free to reopen or open a new one if there is some documentation you feel missing.


[Q] How do I get the final URL after all redirects?

I want to get the URL after all redirects (presumably with a limit to disallow infinite loops). I don’t want the URL to actually be downloaded (a small <1MB download is fine, but not more than that). How do I do this using httpie?
My wget solution (in zsh):
[[ "$(2>&1 wget --no-verbose --spider "$1" )" =~ '.* URL: (.*) 200 .*' ]] && print -r -- "$match[1]"

I think I got this, feel free to close the issue:
url-final-hp () {
local out="$(2>&1 http --all --follow --headers "$1" )"
local res

 res="$(<<<"$out" command rg --only-matching --replace '$1' 'Location: (.*)'  | tail -n1 )"
test -n "$res" && echo $res || echo "$1"
}


Can't create account

bast_1         | [2020-09-30T20:48:48Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:41616 "POST /api/register HTTP/1.1" 200 40 "https://SITE/register" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.444690
bast_1         | [2020-09-30T20:48:49Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:41616 "POST /api/login HTTP/1.1" 401 22 "https://SITE/register" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.446657

On both v0.2.0 and master

Attempting again results in
DatabaseError(UniqueViolation, "duplicate key value violates unique constraint \"users_email_key\""

Hi @aspenluxxxy, thanks for the issue! :)
It seems that the account was created but when the client made the login request; you got an error. You got a 200 from the register endpoint and when you tried to create the same account, you got an error saying that it already exists.
On the client, we try to log you directly after creating a new account. I had this issue once, I'll look into it!
However, you should be able to sign in with your account from the /login URL! :-)

I wasn't able to log in.

I tried it a few times from docker-compose on my machine and all were good. I also tried it from the deploy button of Heroku, all good. Do you still have the issue (with another email)?

Still having issue. Tried two emails.
Attaching to services_bast_1
bast_1         | Starting server on bast:8080
bast_1         | [2020-10-05T12:45:12Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:60392 "POST /api/register HTTP/1.1" 200 40 "https://[mysite]/register" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.473863
bast_1         | [2020-10-05T12:45:13Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:60392 "POST /api/login HTTP/1.1" 401 22 "https://[mysite]/register" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.274252
bast_1         | [2020-10-05T12:45:16Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:60392 "POST /api/login HTTP/1.1" 401 22 "https://[mysite]/login" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.496001
bast_1         | [2020-10-05T12:45:23Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:60394 "POST /api/register HTTP/1.1" 200 26 "https://[mysite]/register" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.449323
bast_1         | [2020-10-05T12:45:24Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:60394 "POST /api/login HTTP/1.1" 401 22 "https://[mysite]/register" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.457620
bast_1         | NotFound
bast_1         | [2020-10-05T12:45:28Z INFO  actix_web::middleware::logger] <IP_ADDRESS>:60394 "POST /api/login HTTP/1.1" 500 0 "https://[mysite]/login" "Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0" 0.006101
Gracefully stopping... (press Ctrl+C again to force)

And here's what the database looks like after: https://ghostbin.co/paste/aye5w

I figured it out.
It's a problem with passwords? It works 100% if I make the password hunter2? Wtf

Ok thanks for the tips, I just replicated the bug. I'm on it ;)

Oh my... Fixed there https://github.com/kooparse/bast/commit/31a656ff8017764b2ba254fb32071a2a5a52a712. Sorry about it! :-)


Bubblemenu

Bubble menu added.
Three buttons are added to make the selected text bold, italic, and strike.

This is fantastic, but ideally we'd want to add more features to the bubble menu + make it look nicer UI-wise before rolling it out.
Take something like Notion's bubble menu for reference:

Currently working on this — @steven-tey does moving into a separate component sound good to you?

I've made a PR https://github.com/steven-tey/novel/pull/14

I'm closing the PR because many things have already been done in #14


Cookie from Production Server Doesn't Get Sent Properly on HTTPS

I have an CACCL 2.0.5-backed LTI app that works fine on the dev server.  In installed it on a cloud server on Kubernetes where it runs in pure HTTP mode on port 8080.
When Canvas calls the /canvas/launch URI, the browser gets a Set-Cookie for CACCL_Canvas_app and a session cookie, but that cookie is marked HttpOnly.  Thus the browser, on subsequent requests, knowing it's going to an HTTPS URL, doesn't send the cookie.  Therefore the LTI thinks that someone is trying to run it's being run outside of Canvas and barfs.
I'm looking through the code to see where the cookie sent back, but I haven't found it yet.

I'm not sure it's related to the HttpOnly flag on the cookie as that prevents JS from accessing the cookie but will still allow it to be sent on HTTPS and HTTP requests (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies).
Could it be that the browser is blocking the cookie being sent on the subsequent requests because it is considering the LTI tool running in the iframe to be 3rd party content and it's more strict about what cookies it will send in that context?

We’re tracking this issue and most often, it seems to come down to the fact that many browsers no longer allow 3rd party sites to have cookies within iframes. We’ve fixed this in one of two ways: use a domain that matches the specific canvas instance (if canvas is canvas.Harvard.edu then the app should be myapp.canvas.Harvard.edu or something), OR we just have the app open in a new tab. Honestly, that’s the option we usually go with (app in a new tab).

(@buckett, I’m pretty confident that your second paragraph explains what’s happening here)


Added test case where string.replace hangs

@kfarnung you can remove external contributor tag I'm Microsoft employee.

@dryganets it's possibly a bad name for the idea but "External Contributor" means that someone with access to Chakra's internal infrastructure needs to adopt this PR, run internal (Chakra + ChakraCore) tests, and merge it through our tools. If you'd like to do this yourself, please contact us offline and we can walk you through it.

Hey @dryganets, I originally added and then removed it when I realized that you work at Microsoft, but the purpose of the tag is to indicate PRs which need to be landed by a Chakra developer.

The bug has already been filed: https://github.com/Microsoft/ChakraCore/issues/4774

@dilijev I didn't mean to contribute this.
This way it is just easier to repro for you.

Thanks for the detailed report and repro @dryganets, we'll continue to track this in #4774.

@dryganets feel free to contact me at work and I can walk you through how to get a better sense of how your regex would be evaluated which might help put your mind at ease.


Remove the support for Cargo.toml of the cargo-script

What does this PR try to resolve?
ref https://github.com/rust-lang/cargo/issues/12207#issuecomment-2358818671
I had a discussion with @epage two weeks ago, and we decided to defer this feature and remove it now. The reason is that we couldn't always resolve the symbolic link that breaks some use cases, and the use cases of cargo Cargo.toml may be rare.
How should we test and review this PR?
The unit test has been removed.
Additional information
r? @epage

The reason is that we couldn't always resolve the symbolic link that breaks some use cases

We can't resolve symlinks for all manifests immediately on load as some people do weird trickery with templated Cargo.toml files where symlinks exist to point to the generated version of them.  Resolving the symlinks could change target-dir and other areas.  I'm not making any statement on whether this is meant to be officially supported workflow but likely not worth investigating.
That means we'd have to resolve the symlink only for determining how to parse the manifest.  The downside to that is a symlink to a Cargo.toml with a #! in it won't reuse your package's target-dir.

@bors r+
Thanks!

:pushpin: Commit 76cd19b54995694b5d46180dba792da030f20667 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit 76cd19b54995694b5d46180dba792da030f20667 with merge 1ea02ffc5ee2b4e3584871f8bd95717e1456ec3d...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 1ea02ffc5ee2b4e3584871f8bd95717e1456ec3d to master...


Long pause immediately after Camera initializes

When rendering the react-native-camera module, the app locks up for about 15 seconds before I can interact with the app.  Can't scroll; can't navigate anywhere, etc.  Seems like a case of locking the UI thread.  Anyway, after the 15 seconds, the camera works fine.

@achang28 Thanks for reporting this, I haven't experienced this but I'm going to look into it tomorrow.

So I saw and replied to your pull request, waiting for your thoughts. In the mean time, here's something I'm proposing. This fixed UI lock up for me, let me know if it works for you.
https://github.com/lwansbrough/react-native-camera/tree/performance-improvements

Caused a crash (in Xcode) when I unmounted react-native-camera module.  See attached image.
So I Downloaded everything from "performance-improvements" branch, and restarted everything (Xcode, and  terminal instance running Node (iojs v2.3.4)).

@achang28 Try moving line 97 to before the super call on line 95 and report back.

oh Damn!  Just retried the app about 15x (e.g. relaunched in Xcode).  Works like a charm!  Awesome shit!  I'll keep playing around with it, but it has been working consistently with "only" a 0.5 second delay after rendering the react-native-camera module.  Consistent 0.5 second delay beats 15 seconds any day!!!

Ok cool, that's good to hear. I think I'll merge this with master then push to npm.

Merge it!

looks like your suggested change of [self.manager stopSession] above [super removeFromSuperview] didn't make it through w/ 0.3.1.  In RCTCamera.m, around line 95

Oh sorry, I guess that wasn't clear. This change is needed to fix the problems you mentioned?

Yeah.  Specifically the app crashing that occurs when unmounting Camera module.

My bad, 0.3.2 published to accommodate these changes.

Hot like buttah.    Works beautifully.

👍


Support Legacy WordPress Meta Boxes

Feature Description
In https://github.com/Yoast/wordpress-seo/pull/15532 / #113 we made the first step to support plugins like Yoast SEO.
To give users control over things like meta descriptions and Open Graph descriptions, we need to support WordPress' legacy meta box system, so that we can display meta boxes like the one from Yoast SEO.
There's a lot of prior art for this in WordPress and Gutenberg.
Alternatives Considered

Additional Context
Yoast SEO support was mentioned in support requests like #3086 and #3107.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

@swissspidy to provide estimate

Experimental support has been added now in #5048. #5519 has been created to stabilize it for 1.3


(PDB-3611) Deduplicate facts (again)

Previously, we had changed fact storage to put the value in the facts table, in
order to simplify storage and sidestep the problematic garbage collection issues
when fact values had their own table. But this proved to make queries too slow,
especially when dealing with queries which have multiple conditions on facts.

TODO:

[ ] Shortcut the initial redupe migration for users that haven't done it yet
[ ] Add a migration diff test

Test PASSed

Test PASSed

CLA signed by all contributors.

Test PASSed

Test PASSed

generally seems sane. I'm going to work on a dataset for testing it now.

Test FAILed

Test PASSed

Test PASSed

Test PASSed

Test FAILed

Closing in favor of https://github.com/puppetlabs/puppetdb/pull/2346


feat: infer mass when the first amp caculate

constant mass when calculate |p0|

Codecov Report

Merging #32 (b7af167) into dev (9fde629) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev      #32      +/-   ##
==========================================
+ Coverage   70.69%   70.73%   +0.03%
==========================================
  Files          78       78
  Lines       10139    10152      +13
  Branches     1936     1938       +2
==========================================
+ Hits         7168     7181      +13
  Misses       2443     2443
  Partials      528      528

Flag
Coverage Δ

unittests
70.73% <100.00%> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

tf_pwa/amp/core.py
74.28% <100.00%> (ø)

tf_pwa/tests/test_amp.py
100.00% <100.00%> (ø)

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 9fde629...b7af167. Read the comment docs.


x/tools/gopls empty struct literal providing incorrect completion suggestions

What version of Go are you using (go version)?

$ go version

go version go1.14.4 darwin/amd64
Does this issue reproduce with the latest release?
yes, did a fresh you complete me install
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/ryan.mcnamara/Library/Caches/go-build"
GOENV="/Users/ryan.mcnamara/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY="github.com/DataDog"
GONOSUMDB="github.com/DataDog"
GOOS="darwin"
GOPATH="/Users/ryan.mcnamara/code"
GOPRIVATE="github.com/DataDog"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="0"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/vp/t7z89ng12n7f629v_26str8w0000gn/T/go-build672772168=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I am using vim withthe latest version of YouCompleteMe which I believe uses gopls under the hood. I would like to verify the following using the gopls cli but have not been able to figure out how to get autocomplete suggestions with the cli. Direction there would be appreciated as it would likely help narrow down if this is actually a gopls issue or a you complete me issue.
When autocompleting on empty struct literals
When populating an autocomplete list inside an empty struct I get the same autocomplete recommendations as outside the struct (all available identifiers):

What did you expect to see?
The list restricted to only the fields of the struct: Asdf, and Qwer in the above case
More info
When the struct literal has any token in it, even if that token is not a valid member, I do see the autocomplete suggestions as desired

This is what I see in Emacs:

I recommend you look at an RPC trace to see the back and forth between gopls and your editor. You can enable this on the gopls side (https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md#capture-logs) or perhaps your lsp client can also dump out the details.
If you suspect your editor/client may be to blame, you can try VSCode to see how it behaves.

The gopls cli does not currently support autocompletion, but as @muirdm suggested, you could try using a different editor or client that also uses gopls (for other vim clients you can check this list: https://github.com/golang/tools/blob/master/gopls/doc/vim.md).


Make 'AcceptedConnectionsLimit' configurable

Currently the limits are hard coded in the node,
ref.

Is closed by https://github.com/input-output-hk/cardano-node/pull/3435


Issue in updating VS Code

We have written the needed data into your
Type: Bug
Failed to install Visual Studio Code update
Updates may fail due to anti-virus software and/or runaway processes. Please try restarting your machine before attempting to update again.
Please read the log file for more information.
C:\Users\shiva\AppData\Local\Temp\vscode-inno-updater-1661656898.log
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 10.0.22000
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i5-1235U (12 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.68GB (2.67GB free)

Process Argv
--crash-reporter-id 76e2fe8e-f80e-43b5-9a1b-56d41b44044f

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

code-runner
for
0.11.8

cpptools
ms-
1.11.5

java
red
1.9.0

LiveServer
rit
5.7.5

vscodeintellicode
Vis
1.2.23

vscode-java-debug
vsc
0.43.0

vscode-java-dependency
vsc
0.21.0

vscode-java-pack
vsc
0.25.0

vscode-java-test
vsc
0.36.0

vscode-maven
vsc
0.37.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
vscaat:30438848
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
i497e931:30553904

clipboard because it was too large to send. Please paste.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Sir I also want to update to 1.70.2 version but it is not updating. So, that is my issue

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Sir I also want to update to 1.70.2 version but it is not updating. So, that is my issue

It's a bot.. It doesn't listen.

@Shivam7061 Can you uninstall and reinstall VS Code?
Related: #47841

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Hovering over test on test-list removes the color

when a user hovers over a test, the color goes away

See #172


Update create-routebased-vpn-gateway-cli.md

Here is TestRG1 i think

@charlesguo404 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thank you! I'll be putting this page in for a review. In the meantime, I'll go back and update these fields. #please-close


Keychain access while running fastlane on crontab

I'm trying to run my fastlane script from crontab, but it seems it can't get the apple developer account password from the keychain. The script runs fine when I run it in the terminal, but when I see the stdout.log from the crontab, it gets stuck at the authentication part. What's the best way to fix this?

I'd say it would be to create a new keychain for the cron job, install your developer .p12 into the new keychain, set it as default, and unlock it. This should all be possible via fastlane actions.

how do I create a new keychain for the cron job?

Have a look at the docs under the building section. You will find all the relevant keychain actions there. These actions will be run by your cron user--ensuring you are creating keychains for their use later in building.

Hm, I don't know if it will help, since to unlock and all that during runtime I have to provide a password, but the point is to keep these passwords local. But either way, I think it magically worked now, by adding the certificates and passwords to the system keychain.
But I have a new issue now: https://github.com/fastlane/fastlane/issues/1020 :(

It looks like there hasn’t been any recent activity on this issue in some time, so I’m closing it. If this is still a problem, feel free to re-open a new issue and I’d be happy to help :+1:


filter db by date

Filter the db by date when detecting ministers. This is handy when we have the role and date but not a name.

Is sth wrong (?) with the notebook? @ninpnin

politicians -> persons

LGTM. In the future, we want to use logging / trainerlog , so that it's easy to turn prints on and off.

Should we make the notebook update the date / version every time we merge to main?

That would be most professional.


Phase 4: Charter Approval

Description
Feedback and approval from the steering committee. (Duration: 1 Week)

Groups that do not receive approval will be removed and notified.
This decision can not be appealed.

Output

Approval status (approved / rejected) for all charters / groups.
Notifications sent to all group managers.

Supporting Documents

Phased Plan

Closing issues associated with deprecated project plan. Please see https://github.com/orgs/DevRel-Foundation/projects/7 for new project plan


let the user change the theme

i added a button that permits the user to switch between two themes.

So we don't want Covalent to depend on UI Platform. UI platform already depends on Covalent. UI platform is meant to be a sort of super-set of Covalent, with Teradata specific logic/styling. With that being said, I do think a generic dark theme toggling would be useful. 🤔 Thoughts @philgetz ?

So we don't want Covalent to depend on UI Platform. UI platform already depends on Covalent. UI platform is meant to be a sort of super-set of Covalent, with Teradata specific logic/styling. With that being said, I do think a generic dark theme toggling would be useful. 🤔 Thoughts @philgetz ?

Agree, Covalent should have its own implementation.

I would suggest making the ui-platform dark theme a bit more generic and moving it here.
And keep the specifics in ui-platform as an add on theme

Closing this for now as it is not a priority.


0.9.3 fails to start

After updating to 0.9.3 the addon fails to start with
s6-overlay-suexec: fatal: can only run as pid 1
Obviously this has something to do with the latest changes to the base image and might be fixed in master already.
Can I some how update to master in HA or can you tag the master with a new version so we can update if it is fixed?
Thanks in advance!

this has been fixed already in   3b0a504feea2f  and 1cc83eaabee , probably just too slow to update the docker, as the build takes a while. Should all work now.

I will bump the . release versions again, so that it automatically updates for everyone who - in the meantime - installed 0.9.3

I downgraded to 0.9.2 which also failed, then updated to 0.9.3 again which effectively updated to master and it works again. So updating to 0.9.4 should fix it for everyone!
❤


Does is it work on UWP

Support on UWP applications (xbox,pc,tablet,x86,x64,arm)?

Yes, this is specifically for UWP applications. All flavors.

I need merge audio and video with FFmpeg. Is it support render to file ?

Hi @omansak,
This library focuses on playback of media, leveraging FFmpeg to support additional formats that might not be supported natively by Windows Media Foundation. It is not a full FFmpeg API. If you follow the instructions to build a version of FFmpeg that is UWP compatible, you can then leverage for your scenario.

@khouzam how to do build o  VS2017 ? or with .bat ?

Can you look at the config.log and see what's failing in the compiler tests?

@omansak any updates, have managed to make it working, I'm looking for the same as you 'merging audio and video on UWP'
Thanks


RootView access

Is it possible to make root view controller available when bottom sheet is opened. Like in the Apple Maps app? The sheet is open but you can scroll the map behind it.

It's surely a good addition to the BottomSheet, unfortunately currently it's not supported
I'll try to take a look at it, not sure when though

I've been working on customizing the bottom sheet implementation of this feature and wanted to know if you had any ideas or pointers to how this would work ?
currently, in the BottomSheetPresentationController I modified the containerView size, but it breaks the presentationView
Could you provide any guidance on how to modify the container to achieve this?
Thank you!


feat(NODE-5566): add ability to provide CRL file via tlsCRLFile

Description
Adds the ability to provide a CRL file as an option in the connection string or client options.
What is changing?

Adds a new option, tlsCRLFile, that takes a string as a path to the crl.pem.
Refactors a bit of TLS testing variable names.

Is there new documentation needed for these changes?
Yes, TLS options should be updated.
What is the motivation for this change?
NODE-5549/NODE-5566

Release Highlight

Users may now provide a CRL file name as a client option.
For users wanting to provide a TLS client revokation list as a filename and not a Buffer, a new option tlsCRLFile has been added and can be provided in either the connection string or as a MongoClient option.
new MongoClient('mongodb://localhost:27017/db?tls=true&tlsCRLFile=path/to/crl.pem'); // option in connection string.
new MongoClient('mongodb://localhost:27017/db', { tls: true, tlsCRLFile: 'path/to/crl.pem' }) // option in client options.

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[x] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Parse error in test/manual/tls_support.test.ts but otherwise LGTM

Fixed.


Error in CSS highlight...

(Original issue 311 created by None on 2007-12-05T18:55:09+00:00)
This doesn't look right:
http://pygments.org/demo/531/
Same CSS code here::
{{{
#!css
.PyLucidPlugins.search {
/* change the input field of the search plugin /*
border: 1px solid grey;
}
.PyLucidPlugins.SiteMap p.deep_1 {
/* change the first entry in the generated sitemap */
border-bottom: 2px solid #red;
}
}}}
Reported by guest

(Original issue was assigned to gbrandl)
(Original issue 311 last updated on 2007-12-14T22:30:05+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by gbrandl on 2007-12-14T22:30:05+00:00)
Tim is right, the CSS comment delimiter is faulty.

(Original comment by thatch on 2007-12-06T17:07:53+00:00)
The parsing of the comment looks correct to me, the second line ends with /* (open comment) instead of */ (end comment).


Ubuntu-latest is failing to deploy SWAs properly

Description
Since Friday we've had strange issue in our SWA in Azure. It's randomly providing 404s for files that were properly deploying on Friday 18th Oct 2024.
If we try and redeploy the same commit that we deployed successfully on that date, then the build appears to be successful, but browsing to our SWA seems to cause random files to not be deployed, resulting in 404s and page load issues. We are deploying a Blazor app using the AzureStaticWebApp@0 task. at version 0.247.1. This version is UNCHANGED and so is not the tasks fault.
For example after 1 deploy, and a full cacheless refresh, we get a 404 on blazor.boot.json,
After another deploy we get a 404 on our scoped css file.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[X] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] macOS 15
[ ] macOS 15 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Issue with 20241015.1.0
Worked last friday with 20241006.1.0
Is it regression?
Yes
Expected behavior
Deployments to be full and correct.
Actual behavior
randomly missing files
Repro steps
deploy using AzureStaticWebApp@0 to a SWA site in Azure.
Attempt to browse to the site after deployment
From dev tools, notice random 404s on files

Hi @Skintkingle ,
This issue not related to runner images repo, i request you to kindly raise a new issue with static web app repo .
I have seen already an issue has been raised , please look into the below link.
https://github.com/Azure/static-web-apps/issues/1560

Thanks for the quick response. This might be related although we aren't using Functions, just pure SWA file hosting. I'll raise an issue there, thank you.

We're closing the issue as it it not belongs to runner images. thank you !.


#VULCAN-274/Feat: Border around cards and minimizable buttons

Border around cards and minimizable button for the cards

Overall very good PR Monish. Splendid work. I have shared some comments (mostly only suggestions, so feel free to disagree) - kindly take a look. Looks almost merge ready but if you have time, think it can benefit from 1 round of improvement mostly based on clean-code principles.


Macos startup errors

Yo!
I use doom-nvim and .norg i not working on neither of my old intel macbook pro or my new M1 macbook air.
M1 startup error
nvim-treesitter[norg]: Error during compilation
Undefined symbols for architecture arm64:
  "_tree_sitter_norg_external_scanner_create", referenced from:
      _tree_sitter_norg.language in parser-29db6d.o
  "_tree_sitter_norg_external_scanner_deserialize", referenced from:
      _tree_sitter_norg.language in parser-29db6d.o
  "_tree_sitter_norg_external_scanner_destroy", referenced from:
      _tree_sitter_norg.language in parser-29db6d.o
  "_tree_sitter_norg_external_scanner_scan", referenced from:
      _tree_sitter_norg.language in parser-29db6d.o
  "_tree_sitter_norg_external_scanner_serialize", referenced from:
      _tree_sitter_norg.language in parser-29db6d.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Intel startup error
nvim-treesitter[norg]: Error during compilation
Undefined symbols for architecture x86_64:
  "_tree_sitter_norg_external_scanner_create", referenced from:
      _language.0 in cc3MwxxW.o
  "_tree_sitter_norg_external_scanner_deserialize", referenced from:
      _language.0 in cc3MwxxW.o
  "_tree_sitter_norg_external_scanner_destroy", referenced from:
      _language.0 in cc3MwxxW.o
  "_tree_sitter_norg_external_scanner_scan", referenced from:
      _language.0 in cc3MwxxW.o
  "_tree_sitter_norg_external_scanner_serialize", referenced from:
      _language.0 in cc3MwxxW.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status

When syncing plugins in doom nvim this info is given:
vhyrro/neorg/unstable: updated: 1a85556...6c01988

Welp, that's not good. A lot of this comes from clang being nasty on MacOS. nvim-treesitter guys are working on it from what I know. Dany has a workaround here if you haven't seen that already, although I don't know how applicable it is in your scenario. If all fails then the best thing you can do is unfortunately wait i suppose

The error points to fact that src/scanner.cc was not compiled. Make sure you add it to sources of nvim-treesitter norg parser config.

Hmm. I'd imagine doom has the scanner.cc set up properly. @molleweide you are running on the latest doom version right?

I got such error too. This part of my config was problematic:
local parser_configs = tsparsers.get_parser_configs()
parser_configs.norg = {
  install_info = {
    url = "https://github.com/vhyrro/tree-sitter-norg",
    files = { "src/parser.c" },
    branch = "main"
  },
}

as @JoeyGrajciar pointed, you need to add src/scanner.cc here:
local parser_configs = tsparsers.get_parser_configs()
parser_configs.norg = {
  install_info = {
    url = "https://github.com/vhyrro/tree-sitter-norg",
    files = { "src/parser.c", "src/scanner.cc" },
    branch = "main"
  },
}

also, clang from macos can't compile it anyway. So, brew install gcc or brew install llvm and start nvim like
CC=/opt/homebrew/Cellar/gcc/11.2.0/bin/gcc-11 nvim

you can then run TSUpdate and everything will be OK


Solve "large-dates" ambiguity

Hi,
bson enables the "large-dates" feature, which means that when you add it to your crate, everything that parsed some time::PrimitiveDateTimes using the plain version of time will potentially break, due to some documented ambiguities.
Is it possible to provide a way to solve those ambiguity, so that we don't have to change our program in order to handle different date-time formats?
Maybe a way to provide the number of characters dedicated to the [year] value?
This is the datetime which causes problems when "large-dates" is enabled:
20240602205731Z

I recently ran into this exact problem with the simple_asn1 crate when attempting to use bson in the samebinary
Upstream issue: https://github.com/acw/simple_asn1/issues/34
MR working arouond the large-date problem: https://github.com/acw/simple_asn1/pull/35
This problem is ultimately the root cause of this upstream issue in the arti-client crate (when bson crate is also present): https://gitlab.torproject.org/tpo/core/arti/-/issues/1632

@morganava Feel free to create a pull request if you are able. Otherwise you'll be waiting on me to eventually get around to this (and there is no time frame).

@jhpratt would the acceptable solution be to make an explicit [short-year] (or some other better name) format specifier which forces years into the range -9999 to 9999 even if time/large-dates is enabled?

The solution would be what I described in a previous comment. Basically it would be a modifier rather than its own component.

What do you mean by modifier? This -> https://docs.rs/modifier ?

@dennisorlando See the current reference, which contains terminology and all current supported syntax.
https://time-rs.github.io/book/api/format-description.html

Minimal reproducable example, which panics when "large-dates" is enabled:
use time::{macros::format_description, PrimitiveDateTime};

fn main() {
    let format = format_description!("[year][month][day][hour][minute][second]");
    let datetime = PrimitiveDateTime::parse("20240602205731", format).unwrap();
    println!("{}", datetime);
}

Anyways: I'm currently working on this. Is this new modifier suitable? I.e. an explicit 4 digit modifier?
#[non_exhaustive]
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
pub enum YearRepr {
    /// The full value of the year.
    Full,
    /// Standard 4 digit format, to be used when `large-dates` feature is enabled
    Four,
    /// Only the last two digits of the year.
    LastTwo,
}

I'm continuing the discussion here since the nature of the problem appears to have changed due to 19120acaf47945e98473a4c48e504cd98939a51d.
The M.R.C. has become:
use time::{macros::format_description, PrimitiveDateTime};

fn main() {
    let format = format_description!("[year][month][day][hour][minute][second]");
    let datetime = PrimitiveDateTime::parse("-20240602205731", format).unwrap();
    println!("{}", datetime);
}

Anyways: I saw that you mentioned in #650 the idea of removing the large dates feature in favour of supporting it by default via a new modifier. Wouldn't removing such feature be the best design choice?
By introducing repr:century, a new ambiguity is being introduced due to large-dates. Adding a new modifier which fixes this ambiguity feels weird..
What about this course of action:

remove large-dates (via previous deprecation to allow projects to adapt to the newer version)
add a "maxdigits" modifier which defaults to 4 (when no sign is present) and 6 (when a sign is present; this should allow compatibility with existing extended year ranges) and lastly 2 when representing a century (I mean, who writes centuries If not with only 2 digits?)

The fact that it's a "maximum" means that it will also support years with less digits, when such year is divided by other components with whitespaces, slashes or other characters.
For example, this crashes:
"204/12/12" ("[year]/[month]/[day]")
Even tho it's not ambiguous.
(I'm writing from my phone, sorry for the terrible text that I just wrote)

Anyways: I saw that you mentioned in #650 the idea of removing the large dates feature in favour of supporting it by default via a new modifier. Wouldn't removing such feature be the best design choice? By introducing repr:century, a new ambiguity is being introduced due to large-dates. Adding a new modifier which fixes this ambiguity feels weird..
What about this course of action:
* remove large-dates (via previous deprecation to allow projects to adapt to the newer version)

* add a "maxdigits" modifier which defaults to 4 (when no sign is present) and 6 (when a sign is present; this should allow compatibility with existing extended year ranges) and lastly 2 when representing a century (I mean, who writes centuries If not with only 2 digits?)

The fact that it's a "maximum" means that it will also support years with less digits, which is useful when such year is separated from the other components by whitespaces, slashes or other characters. For example, this crashes because the year component has only three digits: "204/12/12" ("[year]/[month]/[day]") Even tho it's not ambiguous.
(I'm writing from my phone, sorry for the terrible text that I just wrote)

@jhpratt
(should I have already pinged?)