wpan_serial: Allow to build for other radios and doc update

Allow to build sample for other boards

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8964   +/-   ##
=======================================
  Coverage   52.25%   52.25%
=======================================
  Files         196      196
  Lines       24802    24802
  Branches     5155     5155
=======================================
  Hits        12961    12961
  Misses       9762     9762
  Partials     2079     2079

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 3f53e6d...a641608. Read the comment docs.

@dbkinder updated PR.

recheck

@finikorg is this PR going somewhere? provide status please

@dbkinder @pfalcon can you re-review this PR?
@jukkar @tbursztyka can you take a look?

@finikorg could rebase against master and see if that still builds properly ?

@finikorg could rebase against master and see if that still builds properly ?

Was working 6 days ago when I did last rebase.

@jukkar @tbursztyka @pfalcon can you please take a look at this one?

@finikorg can you rebase so we can try to get this merged

ping @finikorg

ping @nashif, can you recheck this one


Docs?

Nothing here: https://docs.rs/kabuki/0.0.1/kabuki/

Yeah, I haven't published yet... Kabuki is still at the "initial idea hack"...


Ask jwt.io t update the info about jwt-go

This library is mentioned on http://jwt.io but with a lot of red checkmarks for specific functionality that is missing. Is that correct? If not, is it possible to ask the people behind jwt.io to update that info?

A PR sent to this file would solve the question: https://github.com/jsonwebtoken/jsonwebtoken.github.io/blob/master/views/libraries/go.jade

Now you can check here:
https://github.com/jsonwebtoken/jsonwebtoken.github.io/blob/master/views/website/libraries/9-Go.json

Now you can check here:
https://github.com/jsonwebtoken/jsonwebtoken.github.io/blob/master/views/website/libraries/9-Go.json


Change copy on twitter connector deprecation

This is a copy replacement, as required in https://github.com/CartoDB/product/issues/49

Deprecated connector. Please contact support should you need Twitter data. is replaced with
Deprecated connector. Please contact support for more information.

retest this please

Working as expected! ✨


add an initial sambah_readme.md to the docs

GitHub Issue: #194
Description
A short description of the changes in this PR.
Local test steps
Summarize testing and verification you've done. This includes unit tests or testing with specific data
Overview of integration done
Explain how this change was integration tested. Provide screenshots or logs if appropriate. An example of this would be a local Harmony deployment.
PR Acceptance Checklist

[ ] Unit tests added/updated and passing.
[ ] Integration testing
[ ] CHANGELOG.md updated
[ ] Documentation updated (if needed).

📚 Documentation preview 📚: https://stitchee--195.org.readthedocs.build/en/195/

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 22.11%. Comparing base (722ae80) to head (9241c46).

Additional details and impacted files
@@             Coverage Diff              @@
##           develop     #195       +/-   ##
============================================
- Coverage    49.84%   22.11%   -27.73%
============================================
  Files           11       11
  Lines          642      642
============================================
- Hits           320      142      -178
- Misses         322      500      +178

Flag
Coverage Δ

integration
?

unittests
22.11% <ø> (ø)

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

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


Update IAO version

We're using an older version of IAO and should update to the latest dated release.
One change is that 'editor preferred term' is now 'editor preferred label', which we will have to update in our template headers.

The issue fixed in latest IAO release.
IAO_0000111 'editor preferred term'

The version of IAO has been updated.


[SE-0258] Diagnose uses of property wrappers in top-level code.

We don't current support property wrappers at the top level, so
error on them (rather than crashing later).
Fixes rdar://problem/51538524.

@swift-ci please smoke test and merge

Ugh, forgot the test!

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Fix for issue #42

Unregister listeners in onStop() callback.

@julianoes This should be the fix. But please try to reproduce and check if it crashes again. I will test from my side too.

@Sushma7785 a good spotting, thanks! Doesn't crash anymore for me


Implement litellm instead of different LLM inference classes

Suggestion:
Instead of having different packages for LLM inference, we can create a single litellm class which allows the user to use multiple LLMs and reduces dependency management.
Happy to build this!

Maybe lf.llms.REST is the litellm you suggested?
Usage:
lm = lf.llms.REST(
   api_endpoint='https://fake-api.com/',
   request=lambda message, sampling_options: dict(
       model='test-model',
       prompt=message.text,
       temperature=0.0,
       top_k=0.1,
       top-p=0.2,
       stop_sequences=['\n'],
   ),
   result=lambda r: lf.LMSamplingResult(
       [lf.LMSample(c) for c in r['content']]),
   headers=dict(api_key='fake_key')
)

REST only depends on requests, also it supports subclassing. Please check out lf.llms.Authropic and lf.llms.Groq on how to subclass lf.llms.REST. We plan to migrate OpenAI and VertexAI models to REST in future.
Hopefully it helps.

Hey @daiyip, thanks for the reply!


Updated mariadb to serve over tls

The issue resolved by this Pull Request:
Resolves [#RHOAIENG-4972](https://issues.redhat.com//browse/RHOAIENG-4972)
Description of your changes:

Updated MariaDB config to server over TLS.
Added the oc annotation to generate the certs.
Added a config map with the ssl info.

Testing instructions

Deploy DSPO and the dspa using the below yaml file. After deployment, verify that the health checks are successful.
Create a pipeline run and ensure that it completes successfully.
Execute the following command inside the MariaDB pod terminal to verify that the TLS setup is correctly configured.

mysql -u $MYSQL_USER -p$MYSQL_PASSWORD -h <IP_ADDRESS> -D $MYSQL_DATABASE

MariaDB [mlpipeline]> SHOW GLOBAL VARIABLES LIKE 'have_ssl';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| have_ssl      | YES   |
+---------------+-------+
1 row in set (0.001 sec)

apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: sample
spec:
  dspVersion: v2
  apiServer:
    enableSamplePipeline: true
    cABundle:
      configMapKey: ca.crt
      configMapName: kube-root-ca.crt
  objectStorage:
    # Need to enable this for artifact download links to work
    # i.e. for when requesting /apis/v2beta1/artifacts/{id}?share_url=true
    enableExternalRoute: true
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'
  database:
    customExtraParams: '{"tls":"true"}'
  mlpipelineUI:
    image: quay.io/opendatahub/ds-pipelines-frontend:latest

Checklist

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696
An OCP cluster where you are logged in as cluster admin is required.
To use this image run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/696/head
git checkout -b pullrequest f3a81ee0eba65788cceed4f723428d6946594abf
oc new-project opendatahub
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-696"

More instructions here on how to deploy and test a Data Science Pipelines Application.

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-696

/verified

/retest

some nitpicks, but
/lgtm

/lgtm
nice work!

awesome thanks folks!
/approve


Add Form Field support to Dropdown

Description
The dropdown should support being nested inside Form Field.
Tasks
### Checklist
- [ ] Density (HD, MD, LD, TD)
- [ ] Mode (Light, Dark)
- [ ] Fill (Primary, Secondary, Tertiary)
- [ ] State (Default, Hover, Selected/Active, Disabled, Read-only, Other)
- [ ] Controlled API
- [ ] UITK accessibility parity (screen reader + keyboard interactions)

### Deliverables
- [ ] Characteristics spec
- [ ] Interactions spec, where necessary
- [ ] In Code & Figma (Component + Guide)
- [ ] Supporting site documentation

Hold off picking this up, until we have a discussion on the next steps for List based components

Remove priority label, as no one will pick this up anytime soon.

Closed #3131


Smarter equation numbering

Currently, equations can either be all numbered or all non-numbered.
(Except for the user manually switching between the two over the course of the document.)
However, usually equations are only numbered if they will be referred to later (this avoids clutter). Therefore, in this PR, we change numbering to, by default, only appear if the equation has a label attached to it. The current behaviour can be recovered with a newly added option in equation elements: set math.equation(always_numbered: true) (it is false by default).
Still a draft! Tasks:

[x] main logic
[x] always_numbered
[ ] Set a (1) as the default numbering
[ ] Detect whether there is a label attached to the given equation (during typesetting, and in a few different contexts)
[ ] Update docs (I think this is done? seems not)
[ ] Add tests

The (essential) step of detecting whether there is a label attached to the given equation seems a bit tricky, but I see no reason for it to be fundamentally problematic.
But before continuing, I'd like some feedback on the feature itself. What do you think?

I've just found https://github.com/typst/typst/issues/380, seems like this PR might be going in the wrong direction.

Personally, I number virtually all of my equations, even those that are not referenced later, because they are useful not just to refer to them as the writer of the document, but also as the reader of a document (e.g., if discussing the document with someone), and there is virtually no cost in doing so.
This is also why in #380 I ask for being able to number the individual equations that are grouped together and aligned within a single equation command.  So in general I would rather prefer a system where all equations are numbered by default, but that still allows me to cherry-pick those that are not numbered (pretty much how it works in LaTeX).  It could also be good to have a system that allows for both options:  un-numbered by default with an option to opt-in, or numbered by default with an option to opt-out.
I'm also not convinced that using equation labels is the best way to determine whether an equation should be numbered or not.  I think labels and numberings should be independent from each other (except for the fact that it doesn't make much sense to label an un-numbered equation).  Maybe I'm too biased towards LaTeX, which is the typesetting tool I'm most familiar with, but I do like how it approaches this topic;  it's quite flexible, and allows the used to mix-n-match numebrings and labels however they want.

I want the exact behaviour that @dccsillag is proposing. It does not have to be the default, but it would be nice to have a way to achieve this behaviour without resorting to manually switching every time, like the following:
#set math.equation(numbering: "(1)")
$ U = U_1 plus.circle dots.h.c plus.circle U_n, $ <semisimple>
#set math.equation(numbering: none)

(Maybe there is a way to do this and I just haven't dug deep enough.)

Closing for now because it is unclear whether this is the right direction. We will definitely revisit the topic though.


[help wanted] Add quirks for tuya ts0601 touch devices

Adds quirks for Tuya TS0601 1,2,3,4-gang touch devices.
Only the first channel works for now.

[ ] Need help getting the other channels working

The devices I use are branded as Somgoms.

Home Assistant log

Excerpt.
Interesting parts I think are
channel: x in [zhaquirks.tuya] 5c:02:72:ff:fe:c2:01:d5 - Received switch event message, channel: 3, state: 0
[zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
[zigpy_deconz.api] APS data indication response: [33, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x06e7>, 1, 260, 61184, b'\tH\x02\x04!\x03\x01\x00\x01\x00', 0, 175, 183, 172, 20, 61, 0, -71]
[zigpy.zcl] [0x06e7:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=72 command_id=2>
[zigpy.zcl] [0x06e7:1:0xef00] ZCL request 0x0002: [Command(status=4, tsn=33, command_id=259, function=0, data=[1, 0])]
[zhaquirks.tuya] 5c:02:72:ff:fe:c2:01:d5 - Received switch event message, channel: 3, state: 0
[zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x06e7>, ep: 1, profile: 0x0104, cluster_id: 0xef00, data: b'09480204210301000100'
[zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]

[zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
[zigpy_deconz.api] APS data indication response: [33, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x06e7>, 1, 260, 61184, b'\tJ\x02\x04"\x04\x01\x00\x01\x01', 0, 175, 255, 191, 20, 61, 0, -61]
[zigpy.zcl] [0x06e7:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=74 command_id=2>
[zigpy.zcl] [0x06e7:1:0xef00] ZCL request 0x0002: [Command(status=4, tsn=34, command_id=260, function=0, data=[1, 1])]
[zhaquirks.tuya] 5c:02:72:ff:fe:c2:01:d5 - Received switch event message, channel: 4, state: 1
[zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x06e7>, ep: 1, profile: 0x0104, cluster_id: 0xef00, data: b'094a0204220401000101'
[zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]

[zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
[zigpy_deconz.api] APS data indication response: [33, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x06e7>, 1, 260, 61184, b'\tK\x02\x04#\x04\x01\x00\x01\x00', 0, 175, 255, 191, 20, 61, 0, -62]
[zigpy.zcl] [0x06e7:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=75 command_id=2>
[zigpy.zcl] [0x06e7:1:0xef00] ZCL request 0x0002: [Command(status=4, tsn=35, command_id=260, function=0, data=[1, 0])]
[zhaquirks.tuya] 5c:02:72:ff:fe:c2:01:d5 - Received switch event message, channel: 4, state: 0
[zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x06e7>, ep: 1, profile: 0x0104, cluster_id: 0xef00, data: b'094b0204230401000100'
[zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]

Relates to https://github.com/zigpy/zha-device-handlers/issues/716
Somehow fixed in z2mqtt / herdsman https://github.com/Koenkk/zigbee-herdsman-converters/pull/2137
Device signature for 4 gang switch
All devices only have 1 endpoint.
This is the initial signature:
{
  "node_descriptor": "NodeDescriptor(byte1=1, byte2=64, mac_capability_flags=142, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False, *is_valid=True, *logical_type=<LogicalType.Router: 1>, *user_descriptor_available=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0100",
      "in_clusters": [
        "0x0000",
        "0x0004",
        "0x0005",
        "0xef00"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_aqnazj70",
  "model": "TS0601",
  "class": "device.Device"
}

This is the signature after adding the quirk:
{
  "node_descriptor": "NodeDescriptor(byte1=1, byte2=64, mac_capability_flags=142, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False, *is_valid=True, *logical_type=<LogicalType.Router: 1>, *user_descriptor_available=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0100",
      "in_clusters": [
        "0x0000",
        "0x0004",
        "0x0005",
        "0x0006",
        "0xef00"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_aqnazj70",
  "model": "TS0601",
  "class": "zhaquirks.tuya.ts0601_touch_4gang.TuyaTouch4Gang"
}

Its 3 more PR for tuya switched with the same problem and need support for more then the first gang so i hope some device can helping implanting it in the quirk so we can adding it to our devices.

Codecov Report

Merging #899 (07e68d2) into dev (b180e4f) will increase coverage by 0.10%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##              dev     #899      +/-   ##
==========================================
+ Coverage   82.50%   82.60%   +0.10%
==========================================
  Files         185      193       +8
  Lines        4589     4834     +245
==========================================
+ Hits         3786     3993     +207
- Misses        803      841      +38

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0601_touch_1gang.py
88.88% <88.88%> (ø)

zhaquirks/tuya/ts0601_touch_2gang.py
88.88% <88.88%> (ø)

zhaquirks/tuya/ts0601_touch_3gang.py
88.88% <88.88%> (ø)

zhaquirks/tuya/ts0601_touch_4gang.py
88.88% <88.88%> (ø)

zhaquirks/xiaomi/mija/sensor_switch.py
58.69% <0.00%> (-12.28%)
:arrow_down:

zhaquirks/const.py
100.00% <0.00%> (ø)

zhaquirks/lidl/cct.py
100.00% <0.00%> (ø)

zhaquirks/tuya/valve.py
95.52% <0.00%> (ø)

zhaquirks/tuya/ts0041.py
100.00% <0.00%> (ø)

zhaquirks/tuya/ts0601.py
100.00% <0.00%> (ø)

... and 14 more

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 b180e4f...07e68d2. Read the comment docs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

32 of 36 (88.89%)  changed or added relevant lines in 4 files are covered.
121 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 82.602%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

zhaquirks/tuya/ts0601_touch_1gang.py
8
9
88.89%

zhaquirks/tuya/ts0601_touch_2gang.py
8
9
88.89%

zhaquirks/tuya/ts0601_touch_3gang.py
8
9
88.89%

zhaquirks/tuya/ts0601_touch_4gang.py
8
9
88.89%

Files with Coverage Reduction
New Missed Lines
%

zhaquirks/xiaomi/mija/sensor_switch.py
16
58.7%

zhaquirks/tuya/init.py
105
72.43%

Totals

Change from base Build 876824514:
0.1%

Covered Lines:
3993

Relevant Lines:
4834

💛  - Coveralls

Its looks one user have getting one working code for multi gang switches working but having problem testing it on system with multiple devices in the network.
https://github.com/zigpy/zha-device-handlers/issues/1038
Test and implantation help is needed :-))

Its looks one user have getting one working code for multi gang switches working but having problem testing it on system with multiple devices in the network. #1038 Test and implantation help is needed :-))

I have the ones pictured above, 1,2,3,4 gang and curtain switch.
But failing to get this to work I'm afraid I just switched to zigbee2mqtt 🙈
Sry, also no time any time soon to test a zha setup again...

Already implemented:

PR # 1166

Closing.


Universal Translation

Hi, i was seeing your code for the google translate script, and you have this:
if has_chinese_charactar(sys.argv[i]):
source_languege = "zh-CN"
target_languege = "en"
else:
source_languege = "en"
target_languege = "zh-CN"
But that if only works with Chinese characters. For the rest of the world, the translation will only work in one way.. There is any chance you can fix this or do you have any ideia how to fix it?
And great App btw :+1:

For now there is no other way than directly editing in the source. just change the source_language and target_language to your liking. You can find the right language code (en, zh-CN from google web translator).


Fix task-list checkbox styling

This pull request does two things:

Resolves #9656, by updating goldmark to v1.1.25 to incorporate goldmark-pr#112.
Styles task-lists to remove the bullets, when rendered with pandoc.

#9656 strictly describes the missing space. However, commenters asked for the bullet to be removed as well. This is a little more tricky as the GFM spec doesn't mention adding a class to the <ul> (the way pandoc does). It might be possible to convince the goldmark maintainer to add that class though, I'm not sure.
An alternative is to wait until CSS4 selectors are available. This should include the :has() selector, which would allow us to select based on containing an input field. Something like li:has(input[type="checkbox"]). But caniuse says I can't use it because nobody supports it.

When rendered with Pandoc, it now looks like:

When rendered with Goldmark, it now looks like:

Note: I'm using go v1.13.6 and it looks like the go.sum file didn't change correctly. What version of go should I be using to match this project's go.sum file preferences?

What version of go should I be using to match this project's go.sum file preferences

Latest go 1.13 should be fine. We're not on 1.14 yet.
This is LGTM, besides the odd checkbox rendering in those screenshots, but it's not related to this PR.

Tried the PR. It does not seem to add the class for me:

Nevermind, it does work with pandoc enabled, e.g.
[markup.markdown]
ENABLED         = true
FILE_EXTENSIONS = .md,.markdown
RENDER_COMMAND  = pandoc -f markdown -t html --katex

This is LGTM, besides the odd checkbox rendering in those screenshots, but it's not related to this PR.

Sorry, what's wrong with the checkboxes? If/when we get a class on the <ul> element or CSS4 selectors, we could fix the indentation to be consistent with GitHub (where a task list isn't indented and is more left-justified, unless it is nested obviously).
But the checkboxes themselves are correct. I'm on Fedora 31, under GNOME, and they match the system theme:

Tried the PR. It does not seem to add the class for me:

What are your rendering settings? As I mentioned above ("Styles task-lists to remove the bullets, when rendered with pandoc."), you have to use pandoc. My config is:
[markup.sanitizer]
ELEMENT    = span
ALLOW_ATTR = class
REGEXP     = ^(math\s*|inline\s*|display\s*){0,3}$

[markup.markdown]
ENABLED         = true
FILE_EXTENSIONS = .md,.markdown
RENDER_COMMAND  = bash /home/git/custom/conf/pandoc.sh

$ cat pandoc.sh
#!/bin/bash

export PANDOC_GITEA_PREFIX_SRC="$GITEA_PREFIX_SRC"
export PANDOC_GITEA_PREFIX_RAW="$GITEA_PREFIX_RAW"

pandoc -f markdown -t html -M PANDOC_GITEA_PREFIX_SRC="$GITEA_PREFIX_SRC" -M PANDOC_GITEA_PREFIX_RAW="$GITEA_PREFIX_RAW" --lua-filter=/home/git/custom/conf/pandoc.lua --katex

GNOME

Ah, that's why. They just look a bit "unusual" to me 😉
Thanks for the pandoc info, I just switched to it.

So to get this to work with the bluemonday sanitizer too, we need goldmark to add the class, right? Would you mind opening a goldmark issue on it?

Codecov Report

Merging #10668 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master   #10668      +/-   ##
==========================================
+ Coverage   43.61%   43.61%   +<.01%
==========================================
  Files         588      588
  Lines       82487    82490       +3
==========================================
+ Hits        35973    35979       +6
+ Misses      42053    42052       -1
+ Partials     4461     4459       -2

Impacted Files
Coverage Δ

modules/markup/sanitizer.go
92.5% <100%> (+0.29%)
:arrow_up:

modules/indexer/stats/db.go
50% <0%> (-9.38%)
:arrow_down:

modules/queue/workerpool.go
55.87% <0%> (-2.14%)
:arrow_down:

modules/log/event.go
64.61% <0%> (-1.03%)
:arrow_down:

models/notification.go
63.88% <0%> (-0.84%)
:arrow_down:

models/error.go
29.23% <0%> (+0.51%)
:arrow_up:

services/pull/pull.go
35.88% <0%> (+1.17%)
:arrow_up:

modules/git/command.go
89.56% <0%> (+2.6%)
:arrow_up:

services/pull/check.go
53.04% <0%> (+4.87%)
: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 33c5e5e...8e93fb1. Read the comment docs.

@silverwind Yes, I can file the issue when I get back. I was trying to figure out how to add the class earlier but I didn't get far enough.

@silverwind -- filed as https://github.com/yuin/goldmark/issues/113.


Appears to be installed but always shows "Start" option as if it has stopped?

I'm at the edge of my understanding here but I seem to have installed the add-on and added my iSMART sign-in details but I don't think it is working properly - I cannot see any Devices etc in Home Assistant.

Please check your MQTT broker configuration, when this happens login detaiils, ip etc there are usually incorrect.
You can also post the addon logs


add example for use with whatwg fetch

From what  I am developing:
https://github.com/kibela/hello-kibela/blob/master/hello-kibela-with-msgpack.ts

Codecov Report

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

@@           Coverage Diff           @@
##           master      #53   +/-   ##
=======================================
  Coverage   96.57%   96.57%
=======================================
  Files          15       15
  Lines         905      905
  Branches      183      183
=======================================
  Hits          874      874
  Misses         31       31

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 ae20f55...d143e44. Read the comment docs.


Certain Assembly Segments are missing

Certain Assembly Segments are missing in Gujarat and Madhya Pradesh.
Could you please update the same.
Also, the names and boundaries of the Districts are outdated, which requires an update also.
Thanks.

The following Assembly segments are missing:
Gujarat - PC 6. Gandhinagar

AC 45. Naranpura
AC 55. Sabarmati
Gujarat - PC 7. Ahmedabad East
AC 46. Nikol
AC 47. Naroda
AC 48. Thakkarbapa Nagar
AC 49. Bapunagar
Gujarat - PC 8. Ahmedabad West
AC 50. Amraiwadi
AC 51. Dariapur
AC 52. Jamalpur–Khadiya
AC 53. Maninagar
AC 54. Danilimda
AC 56. Asarwa
Gujarat - PC 24. Surat
AC 160. Surat North
AC 161. Varachha Marg
AC 162. Karanj
AC 166. Katargam
AC 167. Surat West
Gujarat - PC 25. Navsari
AC 163. Limbayat
AC 164. Udhna
AC 165. Majura
Madhya Pradesh - PC 25. Indore
AC 205. Indore-2
AC 206. Indore-3
AC 207. Indore-4
AC 208. Indore-5

Boundaries are available here https://eci.gov.in/files/file/3931-delimitation-of-parliamentary-assembly-constituencies-order-2008/?do=download&r=9309&confirm=1&t=1&csrfKey=b031eb639e71f1593fe1efed6f56c782

Hi @rsagasthya The Link is not accessible to me. Can you please download those files, and share it as Google Drive/Dropbox link?

The link will download a PDF file. However this file can be found:
https://eci.gov.in/files/file/3931-delimitation-of-parliamentary-assembly-constituencies-order-2008/
Also, the first 17 PCs of Andhra Pradesh must be transferred to Telangana.
Additionally, please refer the Jammu and Kashmir Reorganisation Act, 2019 which can be found:
http://www.prsindia.org/sites/default/files/bill_files/Jammu and Kashmir Reorganisation Act%2C 2019.pdf
And transfer the districts to the Union Territories of Jammu and Kashmir, and Ladakh.
Thanks.


Can't get your simple quickstart running

<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>title</title>
        <link rel="stylesheet"<EMAIL_ADDRESS>        integrity="sha512-puBpdR0798OZvTTbP4A8Ix/l+A4dHDD0DGqYW6RQ+9jxkRFclaxxQb/SJAWZfWAkuyeQUytO7+7N4QKrDh+drA=="
        crossorigin=""/>

All I'm getting is Failed to load resource: the server responded with a status of 404 (Not Found)

You're referring to a local JS file at js/leaflet-providers.js which may not exist
CSS length properties (i.e. height) must have an unit (e.g. 180px)
Beware using custom map IDs for mapbox (i.e. heliosnarcissus.l937n12c). Your code works using mapbox.streets, which is mentioned in the quickstart. (See https://jsbin.com/vuxeyuyema/edit?html,output ). For issues using mapbox raster tiles with custom map IDs, refer to mapbox support.

Hi, great to hear that you find Leaflet useful!
However, this issue tracker is used for reporting bugs and discussing new features. For questions on using Leaflet, please use gis.stackexchange.com or stackoverflow.
If you are really sure that this is a bug in leaflet, or a feature request, please change the wording to make it look like a bug report.

I've used leaflet before, but now the current version is not working. Using the cdn (no, my cdn is not broken) i get the following:

No console errors, controls not working, tile not working (i'm using the quick start OSM tile demo)


gimp-with-plugins: broken build on master

Describe the bug
Using commit d3f928282c0989232e425d26f0302120a8c7218b. See build output here. Gimp builds fine.
@jtojnar

I knew I was forgetting something. This is likely fallout from https://github.com/NixOS/nixpkgs/commit/b6aded3cd3d445fdfca86ef2c2e90e9da0f08640.
I was partially fixing it in #74301:
https://github.com/NixOS/nixpkgs/blob/537109e9ca24c3752f992b428d638e56320e6a83/pkgs/tools/graphics/gmic-qt/default.nix#L141-L142
but a more proper fix is necessary.


Use latest dependencies

@reviewbybees needed, update to the same structs version as used by git plugin, and use latest objenesis release.

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Adding some UART board definitions to match specification

This pull request adds some uart board definition json files to match the specification decided on in https://github.com/adafruit/Wippersnapper_Boards/pull/115 and check the validator

@lorennorman  This is the first PR involving the UART board definitions getting added in. Could you review this PR since @tyeth  will be basing a future task from this PR?


Add support for vue 2.7

Fixes #193

Note that vue 3.4 removed transformRef, so this will not work to detect the most recent versions of vue 3.


Compile error in geospatial/src/Dem.cc

Environment

OS Version: Ubuntu 18.04
Source or binary build?
Source, main. Commit ff5970e7aebb102eb38aa7d780bbdb015ea6544d

g++ --version
g++ (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to run latest ign-rendering7 fails because ign-common5's CMake tries to pull something-geospatial.cmake
But that won't exist unless GDAL dependency is installed.
So I installed GDAL, rebuilt from scratch and met with this gem:
--- stderr: ignition-common5
/home/matias/Projects/ign/src/ign-common/geospatial/src/Dem.cc: In member function ‘bool ignition::common::Dem::GeoReference(double, double, ignition::math::v7::Angle&, ignition::math::v7::Angle&) const’:
/home/matias/Projects/ign/src/ign-common/geospatial/src/Dem.cc:264:28: error: invalid conversion from ‘const char**’ to ‘char**’ [-fpermissive]
     sourceCs.importFromWkt(&importString);
                            ^~~~~~~~~~~~~
In file included from /home/matias/Projects/ign/src/ign-common/geospatial/src/Dem.cc:21:
/usr/include/gdal/ogr_spatialref.h:185:32: note:   initializing argument 1 of ‘OGRErr OGRSpatialReference::importFromWkt(char**)’
     OGRErr      importFromWkt( char ** );
                                ^~~~~~~
make[2]: *** [geospatial/src/CMakeFiles/ignition-common5-geospatial.dir/Dem.cc.o] Error 1
make[1]: *** [geospatial/src/CMakeFiles/ignition-common5-geospatial.dir/all] Error 2

Description

Expected behavior: To compile correctly (or alternatively why is ign-common5 marked as NOTFOUND if geospatial is skipped?)
Actual behavior: Compiler error (or alternatively, ign-common5 is being marked as NOTFOUND if GDAL is missing, despite successfully compiling)

Steps to reproduce

Pull latest main.
colcon build --cmake-args -DBUILD_TESTING=OFF -DCMAKE_BUILD_TYPE=Debug -DBUILD_DOCS=OFF --merge-install NOTE: Debug is the build type.

Using libgdal-dev 2.2.3+dfsg-2

the main branch of ign-common (major version 5) will be part of the Garden collection, which will be supported on Ubuntu 20.04 and 22.04:

https://ignitionrobotics.org/docs/garden/install#supported-platforms

so the failures on 18.04 are expected. Perhaps we should improve the messaging about which Ubuntu versions are supported?

What @scpeters said is right. Let me know how we can make this clearer.
We've announced the supported platforms on this post, which links to this issue:

https://github.com/ignition-tooling/release-tools/issues/597

We've also explicitly disabled Bionic CI on the main branches, i.e.

https://github.com/ignitionrobotics/ign-rendering/pull/583

I'll close this issue, but please reopen if the problem comes up in a supported platform.


Duplicates entry after saving a file

Hi,
the bug is annoying.
After each saving of a working file it duplicates the entry in the nav-panel.
Apart from that, nice package.
Thx.
Markus

okay. It was a dau-problem. Enable no Duplicates in the options and everything went fine..

okay. It was a dau-problem. Enable no Duplicates in the options and everything went fine..


reCaptcha error, has CF marked a new cipher?

I've starting getting the common exception:
RuntimeError: Cloudflare reCaptcha detected, unfortunately you haven't loaded an anti reCaptcha provider correctly via the 'recaptcha' parameter.
a few hours ago.
I'm getting this on my local IP which is unflagged and working without any captcha's on browser. I get the same on proxies.

Actually, I managed to get the captcha to pop up on the browser as well but all I need is refreshing the page to get rid of it. But making two requests with the same session does not work on py, I still get captcha

Hi @WASHEDDEVELOPEUR ,
Are you running the latest version?

import cloudscraper
print(cloudscraper.__version__)

also can you please supply some example code && url your trying to access when getting the problem.

`import cloudscraper
s = cloudscraper.create_scraper()
s.interpreter = "nodejs"
headers = {
'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36',
'referer': 'https://www.sneakersnstuff.com/',
}
response = s.get('https://www.sneakersnstuff.com/', headers = headers)
`
I think someone reported this site already in the past but I might be mistaken. As I said, if you get a captcha on browser, all you need to do is refresh the page.
I've tried different headers and interpreters but the result is still the same. I can DM you my private proxy as only using flagged IP's will result in getting a captcha

Why are you using custom headers? thats more than likely 100% your issue..

Yes, that's the first thing i tried. When I said "I've tried different headers" that included not using custom ones too . I'm still experiencing the same issue

Just you didn't mention "I've tried different headers" fwiw

Can you please add debug=True to your scraper
Python 3.7.3 (default, Apr  3 2019, 05:39:12)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cloudscraper
>>> scraper = cloudscraper.create_scraper(interpreter='nodejs')
>>> scraper.get('https://www.sneakersnstuff.com/')
<Response [200]>
>>>

Python 2.7.16 (default, Apr  6 2019, 01:42:57)
[GCC 8.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import cloudscraper
>>> scraper = cloudscraper.create_scraper(interpreter='nodejs')
>>> scraper.get('https://www.sneakersnstuff.com/')
<Response [200]>
>>>

By the way I was using the referer header as I noticed I was given captcha's only when accessing the site directly on a fresh incognito tab. If you look up the site on google and access it from there there's no captcha (or you can just refresh the captcha page).
C:\Python36\python.exe C:/Python36/mrp.py
< CONNECT https://www.sneakersnstuff.com/ HTTP/1.1
< Host: www.sneakersnstuff.com
< Connection: keep-alive
< Upgrade-Insecure-Requests: 1
< User-Agent: Mozilla/5.0 (Linux; Android 6.0; JERRY) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3555.2 Mobile Safari/537.36
< Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
< Accept-Language: en-US,en;q=0.9
< Accept-Encoding: gzip, deflate, br
<

> HTTP/1.1 403 Forbidden
> Date: Sun, 14 Jul 2019 08:43:40 GMT
> Content-Type: text/html; charset=UTF-8
> Transfer-Encoding: chunked
> Connection: close
> Set-Cookie: __cfduid=dd4cd73eac3653067a1e2c37c2054a22d1563093820; expires=Mon, 13-Jul-20 08:43:40 GMT; path=/; domain=.sneakersnstuff.com; HttpOnly
> Set-Cookie: __cf_bm=8628752fa51aedda5f683a54012d337d5723f969-1563093820-1800-AcRKj9rSpdDyldQfvt4z3TmjrSiSdKH8uZN91OGZlrYeAjzqPrVIr9KnYbJZfBYBhnNPelFgSClw/816qmKKXws=; path=/; expires=Sun, 14-Jul-19 09:13:40 GMT; domain=.sneakersnstuff.com; HttpOnly
> Cache-Control: max-age=2
> Expires: Sun, 14 Jul 2019 08:43:42 GMT
> X-Frame-Options: SAMEORIGIN
> Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
> Vary: Accept-Encoding
> Server: cloudflare
> CF-RAY: 4f6235da6c7a6b53-LHR
> Content-Encoding: br
>

This is my debug output, let me know if you need the html page as well. Btw thank you for the help and your prompt replies.

Can you also supply your ssl version with your python please
python -c "import ssl; print(ssl.OPENSSL_VERSION)"

OpenSSL 1.0.2k  26 Jan 2017

wow... super old..
Could you please run, and let me how many ciphers you get back
import ssl
ciphers = [
    'TLS13-AES-256-GCM-SHA384',
    'TLS13-CHACHA20-POLY1305-SHA256',
    'ECDHE-ECDSA-AES256-GCM-SHA384',
    'ECDHE-ECDSA-AES256-SHA384',
    'ECDHE-ECDSA-AES256-SHA',
    'ECDHE-ECDSA-CHACHA20-POLY1305',
    'TLS13-AES-128-GCM-SHA256',
    'ECDHE-ECDSA-AES128-GCM-SHA256',
    'ECDHE-ECDSA-AES128-SHA256',
    'ECDHE-ECDSA-AES128-SHA'
]

ctx = ssl.SSLContext(getattr(ssl, 'PROTOCOL_TLS', ssl.PROTOCOL_TLSv1_2))
for cipher in ciphers:
    try:
        ctx.set_ciphers(cipher)
    except ssl.SSLError:
        ciphers.remove(cipher)

print("We have {} matching ciphers".format(len(ciphers)))

8 matching ciphers

@WASHEDDEVELOPEUR are you free tomorrow to talk on discord rather than on here? so we I can work out what/where your issue is?

absolutely


Stop calling the D3 force worker, which we no longer use.

We were already fixing every single Node in place with the fx and fy parameters for the D3 force thingy. This meant that we were calling into it, and it was in turn doing nothing for some number of iterations. We don't really need to be doing that.
This change directly uses the [x, y] positions we get from the server to position Nodes and eliminates all use of the d3 force worker thing.

LGTM! Ty @thetorpedodog yeah it seems the worker is a remnant when we were doing the calculations client side.


[Simulator] Bugs fixes

fix #1078

[x] Send the UTC version of the day to the server
[x] Transform back to local timezone from server
[x] Implement UI when the token pair has no history price

[ ] date picker - pre select not visible
flow:

run simulation
click the back option
open date picker
expected: if the selected range falls into one of the pre defined option, it should be highlighted
actual: it is not highlighted

[ ] missing price history text
replace "token" with "pair"


Cyclic service dependency: ViewsService -> PaneCompositeParts -> CompositePart -> CompositeProgressIndicator -> ViewsService

marking as important because this blocks completion of https://github.com/microsoft/vscode/issues/159178

Please note that the attached fix just fixes the cyclic dependency and does not enable ViewsService to be lazy because it registers viewlets and panels in the constructor. To make it lazy, it needs bigger refactoring that workbench layout shall use ViewsService instead of PaneCompositeService. Re https://github.com/microsoft/vscode/issues/90020


Fully support wait_start

I think we're going to need to have a proper mechanism to have the robots wait for the start of the match if we want to have automatic video collection (#181) due to limitations in webots (https://github.com/cyberbotics/webots/issues/2386).
Since we previously ran the competition on Windows I'm assuming that we need to support doing this on Windows too. Obviously we'd really like that anyway in order to support development in competition mode on Windows.
The way that this works on the real robots is that a FIFO is created using os.mkfifo, however that's a Unix-only API so that's out.
The other alternatives I can think of are:

use a socket.AF_UNIX socket
Impractical as this isn't supported yet in Python (https://bugs.python.org/issue33408). It looks like it might land some time during Python 3.9, but it's not here yet.
use a Named pipe
pywin32 seems to be the consensus for using these on Windows, however that means adding a potentially complicated (and undocumented) dependency along with factoring out the backends to be platform specific
watch a directory for a file appearing (or disappearing)
This is horrible.

Any other ideas?

In an ideal world, I'd suggest using SIGUSR1 however that doesn't work on Windows :/
Easiest solution might be to pick a high TCP port that is not in the IANA list and wait for a connection on it. e.g 47623

SIGUSR1 would require at least knowing the PIDs of the robot controller processes though?
Yeah, a local TCP socket might be the way to go.
I'm also exploring whether there's something internal to Webots we can use.

I'm also exploring whether there's something internal to Webots we can use.

wb_robot_get_custom_data is looking quite promising for this. It allows a (webots) Robot to get or set a string about itself and is noted as being a way to communicate between a controller and robots.


Add / Remove Docker Workers without stopping / re-starting

Hi,
Right now if I want to tweak conccurency (add/remove worker nodes), I need to do a full restart, stopping all running build.
I would be nice if I could just send a SIGHUP to drone process and it will reload config without stopping drone.

I definitely see the value in such a change, but I think we'll need a slightly different implementation. There are a lot of people running Drone inside a Docker container and using environment variables for configuration, in which case SIGHUP wouldn't help.
In fact, when running Drone in Docker, you need to delete and re-add the container just to change the environment variables.
I think an interesting approach that would work with Docker (and non-Docker installs) would be to explore Docker Swarm. This would allow us to add / remove nodes on the fly, with the added benefit of being able to use Docker Machine. It should require very minimal changes to Drone.
Unfortunately I haven't had a chance to play around with Swarm yet.

I'm willing to take a stab at it with Swarm

this feature is added now in the 0.4 brach. Workers are managed via the UI


plugins dev-uninstall --all also removes the pluginsmanager itself

Not actually a bug in encapsia-api because the work is done in pluginsmanager dev_wipe method.
However that works ok because when it iterates through deleting the namespaces, it refuses to delete itself.
See example output below.
Hence closing issue as not a bug.
Found namespace: manager
supervisorctl -c /home/ice/inf-ice-pluginsmanager/icepluginsmanager/supervisor.conf stop schedule
schedule: stopped
Removed 3 scheduled tasks in namespace manager
supervisorctl -c /home/ice/inf-ice-pluginsmanager/icepluginsmanager/supervisor.conf start schedule
schedule: started
Stopped all task workers for namespace: manager
Destroyed virtualenv: manager
Removed tasks directory: /home/ice/manager
Removed webfiles directory: /var/share/nginx/iceplugins/manager
Destroying views namespace manager
Deleted PostgreSQL schema: manager

Found namespace: pluginsmanager
supervisorctl -c /home/ice/inf-ice-pluginsmanager/icepluginsmanager/supervisor.conf stop schedule
schedule: stopped
Removed 0 scheduled tasks in namespace pluginsmanager
supervisorctl -c /home/ice/inf-ice-pluginsmanager/icepluginsmanager/supervisor.conf start schedule
schedule: started
Destruction of task workers prevented: pluginsmanager
Aborting...      <<<<<<<<<<--------- SEE HERE ------------ >>>>>>>>>>

Found namespace: tags
supervisorctl -c /home/ice/inf-ice-pluginsmanager/icepluginsmanager/supervisor.conf stop schedule
schedule: stopped
Removed 0 scheduled tasks in namespace tags
supervisorctl -c /home/ice/inf-ice-pluginsmanager/icepluginsmanager/supervisor.conf start schedule
schedule: started
Stopped all task workers for namespace: tags
Destroyed virtualenv: tags
Removed tasks directory: /home/ice/tags
Removed webfiles directory: /var/share/nginx/iceplugins/tags
Destroying views namespace tags
Deleted PostgreSQL schema: tags


 Not sure what happened, but it definitely wasn't what I said. I tried it again and it was the same. Could you check it out?

Thanks for letting me know. The issue you are facing is due to "react-hook-speech-to-text" library. It is quite sensitive to surrounding noise, but I guess that's not the problem for your case as I tested it too and result were really not good. One other reason could be due to the fact that results depend heavily on browser's implementation of Web Speech API.
To fix this I will probably have to use Google Cloud Speech-to-Text API or the azure one. I will test it using other providers too and implement what fits best.
Thanks again for informing about the issue. Also, if you have suggestion of your own feel free to use the codebase.

Glad to hear. Will checkout the repo and try to contribute


[TA] Analyze Batch Actions implementation updates

This PR include all of the renaming and structure changes based on the latest meeting we have.
fixes: #18723

/check-enforcer evaluate

/check-enforcer override


Brackets Box/Flex CSS Update

Presently brackets is using an outdated version of flex, due to this the sidebar is not rendered properly within firefox.
Refer to: https://github.com/humphd/brackets/issues/180 for more information on this issue/fix explaination

@KeniMorri it looks like you have not signed the BRACKETS CONTRIBUTOR LICENSE AND DISTRIBUTION AGREEMENT

I'd recommend holding off on merging this until Linux gets CEF 2721 so nothing breaks on that platform (and I think I heard something about that possibly happening in 1.4?).

Earlier, flexbox caused us some very bad performance issues.  We should check:
a) whether this PR causes any performance regressions
b) whether this PR causes any performance improvements (maybe newer syntax uses a newer, faster impl under the hood) -- and if so, is it safe to start using flexbox more widely in the Brackets UI after this?

Updated because I forgot to include prefixes for safari
@abose my bad, I've signed it now

Marking this for 1.4, will update if there is any performance issues as peter pointed out.

I see that there is an overlap in hte project tree rendering.

@abose I just ran into this problem on an internal project (so I can't post any links). The solution for my particular case was to specify the min-height as the flex-basis parameter instead of auto, which is what Brackets appears to be doing -- see the .flex-item() mixin.

Thanks @redmunds .
Waiting for PR to be updated with the fix.


fix: improve error handling

:pencil: Description
When calling setFailed, log the full error instead of only the message.
:link: Related Issues
#153

:tada: This PR is included in version 1.17.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


The Wiki isn't publicly editable, nor is it clear how to suggest changes to the Wiki.

The GitHub Wiki is by default only editable by repository collabrators.
See https://docs.github.com/en/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis
I discovered this when I tried to edit the Wiki since I found some problems with it.
I understand that making GitHub Wiki publicly editable could be unwanted, and proposing changes to the Wiki by opening issues is cumbersome. Therefore, I suggest you close the GitHub wiki, and migrate its content to the Git repository.

An example of the problems is in:
https://github.com/run-z/run-z/wiki/Reusing-package-selectors

Just place an ellipsis before the name of the task containing selectors.
The task should be a group task. This task may, in turn, reuse other selectors.

It's better to write what an ellipsis is just after describing it in language.
"an ellipsis" can mean different things in different languages.

Just place an ellipsis (...) before the name of the task containing selectors.
The task should be a group task. This task may, in turn, reuse other selectors.

This not only makes sure everyone is on the same page,
but also reduce the cognitive load on the reader.

Note that after moving wiki articles to the repository, they should stay available via direct links from README file.
The latter is available in different places. E.g. in NPM repository. So, those links have to be absolute.

You got it! I do have a litte bit of bad news, though. My furnance stopped working earlier so the initial 24 hour deadline cannot be met.


Quick display resolution swap

Description of the new feature / enhancement
Add a quick way to swap between user predefined display resolutions / dpi scales.
Scenario when this would be used?
When the user uses a hi-resolution or non-standard ratio(f.e. ultra-wide) monitor
and often shares his display during on-line meetings
Then he needs to change the resolution so the others can see the shared content properly
or the hi-resolution does not take too much network bandwith.
Supporting information
No response

https://github.com/microsoft/PowerToys/issues/1052


Make path to the config.txt file configurable

The config.txt file, that's loaded as part of the boot process of
Raspberry Pi's, resides in the same directory as the firmware files
and kernel.
Raspberry Pi OS mounts this path at /boot, as do many others. However
some distributions use a different path. For example Debian for the
Raspberry Pi (https://raspi.debian.net) uses /boot/firmware.
This commit adds variable rpi_boot_config_file to allow users to
specify where config.txt is located on their device/distribution.

thx!


Session adapter doesn't update https connections cert data

Under a session, the first https request sets the HTTPSConnectionPool certs data.
If in a subsequent request, we change the certs data (eg: Set verify to True), the adaptor will update the ConnectionPool attributes, however each connection in the pool will still contain the old certs data, thus when requesting a connection from the pool, its info will differ from what we would expect.
Expected Result
The used connection should have updated certs data
Actual Result
The used connection have "old" certs data.
Reproduction Steps
These tests where performed against a server with a self-signed CA.
In [1]: from requests import Session

In [2]: url = "https://somepage"

In [3]: auth = ("admin", "admin123")

In [4]: s = Session()

In [5]: s.get(url, auth=auth, verify=False)

Out[5]: <Response [200]>

# This should fail, but doesnt
In [6]: s.get(url, auth=auth, verify=True)

Out[6]: <Response [200]>

# Create a new session
In [7]: Session().get(url, auth=auth, verify=True)
# Raises certificate verify failed

I'm aware ConnectionPool is in urllib realm, but since it's the adaptor who is updating the pool data, perhaps it should also handle this scenario?
System Information
{
"chardet": {
"version": "3.0.4"
},
"cryptography": {
"version": "1.7.2"
},
"idna": {
"version": "2.6"
},
"implementation": {
"name": "CPython",
"version": "2.7.12"
},
"platform": {
"release": "4.4.0-59-generic",
"system": "Linux"
},
"pyOpenSSL": {
"openssl_version": "1000207f",
"version": "16.0.0"
},
"requests": {
"version": "2.18.4"
},
"system_ssl": {
"version": "1000207f"
},
"urllib3": {
"version": "1.22"
},
"using_pyopenssl": true
}

Yeah. Requests is using some old APIs in urllib3 that don’t interact with the connection pooling. It should update to pass the TLS data into the pool manager to ensure that the TLS info factors in.

@Lukasa thanks for your prompt reply

This is also true of the certificate/key paths provided in the cert keyword argument. It seems that the certfile and keyfile attributes are maintained on the connection and not reset if a new cert kwarg is given on a subsequent request on the session.

Still observing this in 2.21.0, but you can issue session.close() to clear out the poolmanager, which will allow new requests with different verify values to be paid attention to.


update

Hello, what is the reason that the kernel has not been updated for a long time, and will it be maintained in the future, including components;

Hello, there are many bugs that you did not reply to


memento: 1.2.2 -> 1.4.0

Description of changes

Updates memento to 1.4.0
Migrates the app to qt6 (see upstream migration commit: https://github.com/ripose-jp/Memento/commit/afea4019a6a1c6bb5daa153490ecfa3ce9494a97)

Based on issue #322167
cc. @teto
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

tested and it worked perfectly thank you.


Adding handling commandline arguments for "dart run"

Dart doesn't handle commandline arguments for "dart run" command, like flutter does, for example:
flutter run -d windows --debug -a debugging

void main(List<String> args) {
  bool isDebugging = args.contains('debugging') ? true : false;
}

My new feature request is for "dart run" to handle the custom commanline arguments like "dart file.dart myArgument"
and "dart run file.dart myArgument" do, or optionally like flutter does.

dart-github-bot

Not entirely mr bot @dart-github-bot . As you may have noticed there is a syntax that handles "dart run" which requires a file name and arguments: "dart run file.dart myArgument" but this request is about passing args like this: "dart run somehowpassedargs".

How about --?
Eg, dart run -- arg1 arg2

I can get behind the --.
Asking for dart run foo to not think foo is the script feels a little too fragile.
Especially since it allows you to omit the .dart, so writing dart run foo already means the same as dart run foo.dart.

How about --?
Eg, dart run -- arg1 arg2

That would be also fine I believe.
The thing is currently there is no way at all to pass the main script any arguments without typing the script name explicitly.
So any approach will work. But as @brilliapps said, why invent a new interface beyond what already exists in flutter?

Even if possible both -- and -a and even something else, if it is broadly used, might be implemented. Not an important way for Dart to get broader "audience", but something familiar to different kind of programmers always helps a bit.


Grammar rules should be unique

Currently there is no mechanism in llguidance for determining a grammar rule (aka node) is unique.  This

makes the algorithm for counted sequences sub-optimal, and may prevent it from reducing the number of rules to O(n) in the length of the sequence;
makes our definition of grammar unnecessarily inconsistent with the usual one on the world of parsing theory, which
is likely, as we add parsing features, to cause other gotchas.

This can be done in GrammarBuilder; I guess we should also try to do it in Grammar::optimize

@mmoskal linked issue for hash consing?

I think this would be for both hash-consing in the GrammarBuilder and also Hash of (node_id, num_repetitions) cache in repeat_exact and (a separate but same shape) in at_most

See Commit 5bc30a8

@v-jkegler uniqueness is enforced a bit further up the stack when we are building a "TopLevelGrammar", see my recent commit here
https://github.com/microsoft/llguidance/blob/29655f3aef74a21fcdbfa7c4e349c07baa89e62d/parser/src/grammar_builder.rs#L186


Wrong format in committees-current.yaml

I found some issues on the file, instead of - name is pointing to - thomas_id, is this correct?

name: Immigration and the National Interest
thomas_id: '04'
wikipedia: United States Senate Judiciary Subcommittee on Immigration, Refugees
and Border Security
thomas_id: '24'
name: Bankruptcy and the Courts
thomas_id: '25'
name: Oversight, Agency Action, Federal Rights and Federal Courts
wikipedia: United States Senate Committee on the Judiciary...

["markdown","md","mkd"],"text/x-nfo":["nfo"],"text/x-opml":["opml"],"text/x-pascal":["p","pas"],"text/x-sass":["sass"],"text/x-scss":["scss"],"text/x-setext":["etx"],"text/x-sfv":["sfv"],"text

These are semantically equivalent in YAML.


Add typescript typings

These typings are missing the documentation as they are not in typedoc-format and would need to be maintained twice. They also already include the typings for the functions introduced in PR #105.

I merged these in for now; Though I'm curious: Can't TypeScript read the documentation from the JSDoc comments? Including this in those comments would remove the need to maintain different typings file separately.


#1163 Remove routes and other code for sending a PDF letter.

Description
These changes delete code used to send a PDF letter.
#1163
Type of change
Please check the relevant option(s).

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

How Has This Been Tested?

[x] All unit tests pass
[x] Deployed
[x] Regression suite passes
[ ] Cypress regression passes

Checklist

[x] I have assigned myself to this PR
[x] PR has an appropriate title: #9999 - What the thing does
[x] PR has a detailed description, including links to specific documentation
[x] I have added the appropriate labels to the PR.
[x] I did not remove any parts of the template, such as checkboxes even if they are not used
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to any documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have ensured the latest master is merged into my branch and all checks are green prior to review
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] The ticket is now moved into the DEV test column

Assuming Cypress regression passes, development for this ticket is finished. I will seek code review after Cris returns because we are not merging letter changes before then.


What if the user don't use nvm?

I personally use n ( https://github.com/tj/n ) instead nvm,
Is there any easy fix for that?
If we get the node version by node -v it should work in my case

Personally, I prefer nvm.
If we will use node -v than how will we hide this part for system version of node, like we do in case with nvm?
If you know how to do that, I'll be grateful if you send me pr.

You could add another variable, something like SPACESHIP_NODE_VERSION_CMD which by default is nvm current but can be overridden by the user

Please, check if #24 is related to your problem.
I'd prefer to name this variable as SPACESHIP_NODE_DEFAULT_VERSION for such cases.

+1

n support is coming soon.

You the best!

Sorry, accidentally closed this issue. It's still relevant. Reopened.


Allow creating CompletedRequestMaps from iterables

In cases where users create custom datasources by extending DataSource, they need to add each individual result to the CompletedRequestMap. With this PR, we allow creating CompletedRequestMap via iterables.
Besides the UX improvement, this is also ~30% faster and generates ~50% less GC allocations

Good idea! Went with a somewhat different signature but implemented in #460.


Adding sustain pedal control as a new performance event

Greetings Magenta authors,
Thank you for the wonderful effort of building Magenta.
Will it be a good idea if the sustain pedal control (or MIDI control changes in general) can be included as a new performance event here?
Reason: When MidiPerformanceEncoder is used solely to encode & decode MIDI files, all control events will not be captured after the encode-decode process. In terms of piano performance modelling, control changes such as sustain pedal and soft pedal can be crucial for the output results.
Thank you for your consideration once again!

Hi @gudgud96! It's definitely possible to do it that way. Thus far, we've just been using sequences_lib.apply_sustain_control_changes to lengthen notes played under sustain. It doesn't capture all the subtleties of sustain pedal usage, but it at least accounts for notes playing longer.
We haven't explored more direct pedal modeling at this point because a lot of our data comes from transcriptions, and our transcription model does not currently do anything to predict pedal usage.
If you get interesting results from a more direct modeling of pedal usage, we'd love to hear about them!


Update api.md

Description
Added notes to use sequence number and primary term when updating monitor.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@syrinx05p We recently implemented a DCO check with our commits, so now all commits require a sign-off using the -s flag.  Here are some steps: https://docs.pi-hole.net/guides/github/how-to-signoff/ Let me know if you need any help.

Resolved in favor of https://github.com/opensearch-project/documentation-website/pull/353


Load Testing Benchmark Analytics

Write load tests result to parquet dataset stored in internal S3.
ToDo: Determine whether to restrict to just default branch (i.e. release-3.0.0) or not.

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

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 332964c9da7dd36758b821505aa7d28deb7ee5c3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: b444824d8edb5427ecf33933d3f4231d4688a175
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: b444824d8edb5427ecf33933d3f4231d4688a175
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: b444824d8edb5427ecf33933d3f4231d4688a175
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 7a3d7a6b60d8ae89156cbc661ce2bad54949892a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 7a3d7a6b60d8ae89156cbc661ce2bad54949892a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 7a3d7a6b60d8ae89156cbc661ce2bad54949892a
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 6d7847017e50e7df7bf9c1d32f7fc5ed0d70ddeb
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 6d7847017e50e7df7bf9c1d32f7fc5ed0d70ddeb
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6d7847017e50e7df7bf9c1d32f7fc5ed0d70ddeb
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 8167525dce7af5dc53425751eee50b598abe8b76
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 8167525dce7af5dc53425751eee50b598abe8b76
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 8167525dce7af5dc53425751eee50b598abe8b76
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 8167525dce7af5dc53425751eee50b598abe8b76
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 8167525dce7af5dc53425751eee50b598abe8b76
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 8167525dce7af5dc53425751eee50b598abe8b76
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: fb7b13cbd6c3a8cc84546ec74e35559c59417764
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: fb7b13cbd6c3a8cc84546ec74e35559c59417764
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: ae838a33c53626f1e0e580090b5a2287499b2dba
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: ae838a33c53626f1e0e580090b5a2287499b2dba
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 9829abcc3cda512775f098932309b08a9920afe7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 4a136674c7c8024a2f4fbd95ff7d753b6c9d4abd
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 4a136674c7c8024a2f4fbd95ff7d753b6c9d4abd
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: e350341f2710386138352cf97285d728074163ec
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: e350341f2710386138352cf97285d728074163ec
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: e350341f2710386138352cf97285d728074163ec
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-ATYtnXPE7MOa
Commit ID: 6bb1b34838e0e943be33ed03968b150d3e4c60a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Location not clear

Venue location isn't particularly clear on the site

Lik Kan has sorted this out. Very appreciated! 🎉


'undefined' returned instead of undefined in string split with regex

node and deno evaluates the expression "a ".split(/(d)*/)  to [ "a", undefined, " " ], but quickjs-ng evaluates to [ 'a', 'undefined', ' ' ].

Kind of surprising because e.g. exec() does work correctly - and apparently test262 doesn't test it? Doubly surprising.
Anyway, legit bug - I'll fix it.


Feat: add partial vote sidebar notification

Summary
This PR aims to add a notification blob to the governance tab when a wallet has partial vote (has received funds since last vote, can merge funds)
Additionally it updates the existing logic for staking to work properly with wallet and tab switching
Changelog
feat: add partial vote sidebar notification
fix: sidebar notification on wallet & tab switch
fix: derived stores reactivity

Relevant Issues
Please list any related issues (e.g. bug, task).
Type of Change
Please select any type below that is applicable to your changes, and delete those that are not.

[ ] Breaking - any change that would cause existing functionality to not work as expected
[ ] Chore - refactoring, build scripts or anything else that isn't user-facing
[ ] Docs - changes to the documentation
[x] Fix - a change which fixes an issue
[ ] New - a change which implements a new feature
[x] Update - a change which updates existing functionality

Testing
Platforms
Please select any platforms where your changes have been tested.

Desktop

[ ] MacOS
[x] Linux
[ ] Windows

Mobile

[ ] iOS
[ ] Android

Instructions
Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.
Checklist
Please tick all of the following boxes that are relevant to your changes, and delete those that are not.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[x] I have made corresponding changes to the documentation

Really nice!


relayPagination does not play well with suspenseExchange

Hi! I'm using graphcache and suspense exchange both and I noticed that when suspense mode is enabled, the "fetch next results" request using the relayPagination will throw the Promise and display the initial suspense loader.
// urql version & exchanges
{
  "@urql/devtools": "0.1.2",
  "@urql/exchange-graphcache": "2.3.0",
  "@urql/exchange-suspense": "1.8.7",
  "urql": "1.9.5",
  "wonka": "4.0.9"
}

Steps to reproduce

Create a project with graphcache and suspense exchanges.
Wrap a page displaying a list of paginated items with a React.Suspense component and its fallback.
Scroll or click next to load next items.
The loading fallback will appear.

Expected behavior
It should be possible to disable suspense mode when fetching next paginated results and handle the list loading locally (or maybe another option I didn't think about?)
Actual behavior
The Promise is throw, then caught by the parent React.Suspense component, displaying the initial loading view.
I refreshed the app at start, then scroll to fetch more results:

That's unfortunately expected behaviour. When urql returns into a loading state then there's no way to avoid the suspense when you're using @urql/exchange-suspense with suspense mode.
The reason for that is that you're getting a cache miss here, so no result at all, which means that the hook doesn't have any data to display, hence the suspense interruption.
This can be worked around using the "partial cache data" mode in Graphcache, since then the result will be fetched in the background if only some data is missing.
Apart from that we don't recommend the usage of client-side suspense anymore. It boils down to being a "fancy loading state" for urql on the client-side, and isn't supposed to be used for that, since the normal fetching flag does the trick as well. Overall suspense doesn't currently really do much for us and we're considering deprecating @urql/exchange-suspense.

The reason for that is that you're getting a cache miss here, so no result at all, which means that the hook doesn't have any data to display, hence the suspense interruption.

Ok, I get it 🙂

Apart from that we don't recommend the usage of client-side suspense anymore. It boils down to being a "fancy loading state" for urql on the client-side, and isn't supposed to be used for that, since the normal fetching flag does the trick as well.

You recommend keeping suspense off and handle the fetching state in each component?

@zoontek If you can, it will give you more control over your loading states, yes 😅 That being said, if you already hoist much of your data fetching up to a higher component in your tree, this won't be as bad as it sounds

I removed suspense, everything work wells then. Thanks for all your help!

Hi @kitten ,
I also want to point out that it does not play well with subscriptionExchange too. Some subscription updates never come..
best regards

@micabe Hiya 👋 feel free to ask on Spectrum about that or open another question issue here on GitHub.
This shouldn’t cause any issues so this is definitely unexpected; but maybe something else may be going on.

Thanks @kitten,
I left a thread on Spectrum https://spectrum.chat/urql/help/subscriptions-updates-do-not-go-through-with-suspense-true~03ddb938-994f-496e-92cb-81915a3a4369 👍


Add a way to export your Token

It would be great if you can create a way to export tokens.
The problem is currently that you can't export your token or get their secret.

You can't even transfer them with application backup which is a real problem if you need to change of device (most of the time change of phone).

See #20


[Launcher]: Refine LAUNCHER_LOG_DIR

Coverage decreased (-8.5%) to 51.378% when pulling 6aba183afdd5cf958cee6b9bac8e206ae9aade98 on yqwang/launcher-dev into c526da726b4a609129569b7d9faca072bc759073 on master.


Custom Copiers #3: MockNamedValue Changes & Additions

in preparation for addition of copiers to copy non-native types.
Attempt to break up the work by @jgonzalezdr and myself (#676 and #675) into smaller, more manageable chunks.
This one completes the necessary changes and additions to the MockNamedValue class. There is now a list of MockNamedValueCopiers in addition to the list of MockNamedValueComparators and methods to handle both.

Closing these PRs as they are no longer needed.


add version limitation for lasagne

FYI
https://github.com/Lasagne/Lasagne/issues/702#issuecomment-226713102


Several things arent themed

This includes for example the new message button which stays the normal blue or the right click menu

Same problem. The settings page looks very bad. Last commit in this repo is from a year ago, but Thunderbird had a major UI update (v115) a few months ago. Not sure if this extension is still maintained


getting rid of featured bar, it's a tag

- also changing card style a little bit
- get rid of comment/tip icon for posts
- got rid of bounty flag, just don't think it's that important

Thanks, it looks really nice!
What do you think about moving the "New" indicator into the same spot as Featured?

I could do that!


Small bug in RandomVsRandom.componentWillUnmount

RandomVsRandom.componentWillUnmount has the line window.clearTimeout(this.timer()). Surely that should be this.timer, without the parentheses? Here's a fixed version: https://codesandbox.io/s/9q198jzz3w
This bug also exists in the git repository.

timer = () => window.setTimeout(this.makeRandomMove, 1000);
clearTimeout(timer())

timer is a function so I believe it's correct to call it with parenthesis
if it wasn't a function
timer = window.setTimeout(this.makeRandomMove, 1000);
clearTimeout(timer)


List students that have backups but are unenrolled

It's useful to see if you forgot to enroll someone - since otherwise they don't appear in the course stats
Here's some rough code that does what this going for
from server import jobs
from server.constants import STUDENT_ROLE
from server.models import Backup, User, Enrollment, Assignment

@jobs.background_job
def unenrolled_students(assignment_id):
    logger = jobs.get_job_logger()

    logger.info('Starting...')
    assign = Assignment.get(assignment_id)
    enrolled_students = set(e.user_id for e in (Enrollment.query
                            .filter(Enrollment.role == STUDENT_ROLE,
                                    Enrollment.course_id == assign.course_id)
                            .all()))

    submissions = (Backup.query.filter_by(assignment_id=assignment_id)
                         .group_by(Backup.submitter_id).all())

    submitters = set(s.submitter_id for s in submissions)

    difference = submitters.difference(enrolled_students)

    users = User.query.filter(User.id.in_(difference))

    for user in users:
        logger.info(user.email)

    logger.info('Finished!')
    return msg

We should be careful to not include staff members in the result (i.e. don't filter by STUDENT_ROLE)

Sorry for the title changes. Should it be backups or only submissions? We also don't want to spend resources composition grading if a student is not officially taking the course.

Backups - the idea here is to be a spot check for course staff to make sure they haven't forgotten to enroll some people. 184 asked for this like so:

can we see submissions from students who are not enrolled? because there's sometimes a mismatch between bcourses and what they actually login with, or with their berkeley email

Re Composition: I agree that we should not be auto enrolling users (and then giving composition feedback).
This job is just about giving some visibility to the fact that there are students working on the assignment who might not be enrolled - those users are hidden otherwise to course staff.

Hi, I've been working on this issue but am getting stuck at combining the "un-enrolled but submitting" student data with the enrolled student data. I'm working in server/controllers/admin.py in assignment_stats(). Using your code as a guideline I've got the following so far:
    assign = Assignment.query.get(aid)
    enrolled_students = set(e.user_id for e in (Enrollment.query
                        .filter(Enrollment.course_id == assign.course_id)
                        .all()))
    submissions = (Backup.query.filter_by(assignment_id=aid)
                     .group_by(Backup.submitter_id).with_entities(Backup.submitter_id).all())
    submitters = set(s.submitter_id for s in submissions)
    difference = list(submitters.difference(enrolled_students))
    for not_enrolled in difference:
        print(User.query.filter_by(id=not_enrolled).all())

The last 2 lines there are just printing out the users that are un-enrolled but have submitted the assignment. I'm able to get those users successfully. I've successfully got the details from their submitted assignments using Assignment.user_status() and passing in the user object.
Could you point me in the right direction as to what function/model to edit to include these un-enrolled users?

@wrobe0709 If I understood correctly you'd like to know where to display this info? I'd suggest either using the job interface or making a brand new view (I'd prefer creating a new view in admin.py)
I think all you need to display is the user's email.
Steps:

Create a new route in admin.py
A new template in staff/course/assign
Render the emails within the template

@Sumukh  Yes, I'm wondering where to display the info. Ok, you're steps make sense.
Would this then be another option on the sidebar of the assignment that says something like "Un-enrolled Submissions"? Basically, where would the staff member see this information?

Yeah. If you don't mind expanding the scope slightly, I actually think this makes more sense on a course level instead of a per assignment (since instructors would want to see this at once instead of checking each assignment)
You'd have to change the submission query to look more like this:
Backup.query.join(Backup.assignment).filter(Assignment.course_id == cid) ...
If you do decide to do that - you could add a link under the course dashboard actions (just like the assignment actions you referenced) (and the route could be something like /course/<int:id>/unenrolled)

Ok. I think that makes more sense too. I'll start on that. Thanks for the info.


Bug in dynamic data sequence generation

Hi,
Been working with your model for several months: I'm please to inform you that it, on average, performs as well if not better than boosted models on tabular data, on REAL world datasets (tried 3 at this point)
However, I have noticed a bug in the sequence generation
First, if we have a fixed sequence length of 10 and a transaction sequence length of 8 (for example), I expect all the data to be in the single sequence. However, the model seems to generate a sequence with 1 transaction first, and then attempts to stack the wrest of the values in the next sequence. I could be wrong, but this does not seem like typical behavior, unless the idea behind this is to have the model for that sample focus on the static data as opposed to the sequence data
Second, I have noticed some odd performance when the user sequence length starts approaching the stride.
For stride 1/2/3 and a minimum user sequence length of 5, the sequencing performs as expected
However, here are some preliminary results for alternative cases
fixed seq len= 20
stride = 5
9 user transactions
output sequences
[xxx 1 transaction]
[xxx 6 transactions]
and that's it - the sequencing appears to truncate the remaining elements of that sequence if the stride is larger than the fixed seq len minus existing sequence length
another set of results
fixed seq len = 10
stride = 8
9 user transactions
output sequences
[xxx 1 transaction]
[xxx 9 transactions]
so this works fine
5 OR 6 user transactions
[xxx 1 transaction]
and that's it - at this point, the loop exists to the next reviewer, and no other sequences from that user are added to self.data

Hey Jonathan, I'm also interested in using FATA-trans. Have you fixed the bug for yourself? If so would you mind maybe creating a PR for your fix? Thanks P.S Have you tried increasing the sequence length? What were your results?


Parse Concepts

In Concepts list, everything is reasonably straightforward, i.e. the instruction rows cover everything.
Just wait for the confirmation that the content has been revised and is ready for parsing.

Duplicate.


Old form state in FormBuilder.onChanged

When you try to read the value of the FormBuilderState it still has an old state.
The issue is in the FormBilderField.didChange method:
  @override
  void didChange(T? value) {
    super.didChange(value);
    _informFormForFieldChange(
      isSetState: false,
    );
    widget.onChanged?.call(value);
  }

This method calls super.didChange and this method calls the onChanged callback of the FormBuilder, but at this time the _instantValue of FormBuilderState is not updated yet. This happens in the next line by calling _informFormForFieldChange.
I don't quite understand why we need different Maps with the form values (_instantValue and _savedValue) but my workaround for this problem is as follows:
  @override
  void didChange(T? value) {
    super.setValue(value);
    _informFormForFieldChange(
      isSetState: false,
    );
    super.didChange(value);
    widget.onChanged?.call(value);
  }

This way the value is set using the setter. Then _informFormForFieldChange updates the _instantValue and then all didChange and onChanged methods are called.

I just noticed that this problem is related to #960. However the solution by calling widget.onChanged?.call();in setInternalFieldValue is quite ugly because the method name does not say that it will call the onChanged method of the FormBuilder. This could introduce other problems in the future.


Support x.com for tweets

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description

Confirmed locally that it works


Fix deprecation warnings (mainly happening in python 3)

To be merged after https://github.com/paylogic/halogen/pull/23

Coverage decreased (-0.7%) to 98.513% when pulling b01ec8ad99c433d66d916413c10b01c1ef51b38b on fix-warnings into af9f8a3d2b2a7f11545242026720af276d5de8a8 on update-pythons.


Include property in TypeScript client, but omit from JSON response

I currently have a .NET Core 2.1 API which has some DTO's with direct relations to one another.
Before returning those DTO's, I flatten the relations in a specific way, so that nested relations only get serialized once. The DTO then only holds a reference to the corresponding relation. The property with a direct relation to another is marked with a [JsonIgnore] attribute, so it isn't sent and client won't expect it.
I have an Angular application where I want to use the TypeScript client to parse these DTO's. These DTO's should then restore the relations (I now use the transformResult() using a ClientBase for that) their relations.
The problem I'm now facing is that the generated Clients and DTO's do not contain these direct relations (which makes sense, since these properties are marked with a [JsonIgnore] attribute). I do however would like these properties to be available in the TypeScript client if that is possible.
Is there currently a way to mark those Relation properties with a certain attribute, so that they will remain omitted from the final Swagger documentation, but they will be available in the generated DTO's in the TypeScript client?

so that they will remain omitted from the final Swagger documentation, but they will be available in the generated DTO's in the TypeScript client?

The generator works like backend code => spec => client code so if a property is not part of the spec it will also not be generated in the client code...


Selecting objects using a graphics tablet is difficult (requires zero movement)

Selecting objects in iD appears to require exactly zero movement of the cursor at the moment of clicking. This becomes evident when you try it with a graphics tablet plugged in, when it becomes very difficult to select anything!
This lack of tolerance for clicking is different to the behaviour of everything else within the web browser. For example I can click normal links (like the "History" link) in a fluid pass without ever stopping still.

(My system, btw: Ubuntu 13.04, Firefox 25.0, Wacom Bamboo.)

I presume that you're not using the standard web browser's "onClick" behaviour, but some kind of internal "onMouseDown/onMouseUp" logic? If so, please could you add a small tolerance for slight movement during clicking?
(I'd like to remark that this is not just an issue of convenience, but of interface consistency and accessibility.)

A lot's changed in six and a half years!
We now have pointer events (#5505) and can thus treat stylus and mouse interaction differently. I don't have a graphics tablet but selecting nodes without dragging them using an Apple Pencil on iPad was near-impossible, as described. I added a higher pixel tolerance for styluses which solved the issue. Selecting ways and areas appears unproblematic so whatever changed about that behavior in the long interim must have already fixed the issue.


[WFCORE-2223] Drop pointless validation of jboss.modules.dir

https://issues.jboss.org/browse/WFCORE-2223
The only use of this system property is to drive the value of a deprecated attribute in the core-service=[server|host]-environment resource. There is no good reason to validate it and doing so breaks some embedded use cases.

Jeff did basically the same PR so I'll take that as a code review. :)


Replace DocumentDB with CosmosDB

@alfredodev,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Merged


[Spike] Get rid of Gitea

Right now Gitea provides the following functionality:

Orgs concept (they are implemented by querying git)
Storage for the application code
Triggering hook for Tekton
Pushing mechanism (through git push)

Why remove it then?

Many responsibilities (no separation of concerns)
Hackish pushing method (shell script?!)
Triggering hook is a weak link. When it's not accessible, Tekton doesn't trigger and the user has no idea why
Git may be slow with applications that have big assets. This is because git is not good with large files and repos.
Pushing applications through the web UI is not possible if we only support git.

I've also had some issues where a delete then push breaks the hook

@agracey sent this as a possible alternative to minio: https://github.com/chrislusf/seaweedfs

We already started creating separate stories to implement the following concept:

Gitea stays but only as a storage for code and not an integral part of the push process
We create an upload API endpoint and we use that to upload the code as a tarball #308 #338
Eventually we support other ways to provide the sources (e.g. directly pull from GitHub)
We can use the web UI to upload the code and push the app.

There are or will be new stories about each one of these. Closing this Spike.


Bump Golang 1.13.15

full diff: https://github.com/golang/go/compare/go1.13.14...go1.13.15
go1.13.15 (released 2020/08/06) includes security fixes to the encoding/binary
package. See the Go 1.13.15 milestone on the issue tracker for details.
https://github.com/golang/go/issues?q=milestone%3AGo1.13.15+label%3ACherryPickApproved

/test pull-cri-containerd-node-e2e

/test pull-cri-containerd-node-e2e