Toggles with the same ID do not function correctly

Detailed description

Describe in detail the issue you're having.

When multiple Toggle elements exist, with the same id, then only the first Toggle is ever affected by the user's interaction.

Is this issue related to a specific component?

Toggle (and likely ToggleSmall)

What did you expect to happen? What happened instead? What would you like to see changed?

Whether or not a multiple Toggle controls use the same ID, the ID should affect the behaviour of the control.  Clicking any individual toggle should only affect itself.

What browser are you working in?

Chrome

What version of the Carbon Design System are you using?

Latest in git

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

Maximo
Steps to reproduce the issue
Here's a story that clearly shows the issue
.addWithInfo(
    'Default',
    `
      Toggles are controls that are used to quickly switch between two possible states. The example below shows
      an uncontrolled Toggle component. To use the Toggle component as a controlled component, set the toggled property.
      Setting the toggled property will allow you to change the value dynamically, whereas setting the defaultToggled
      prop will only set the value initially.
    `,
    () => (
    <div>
      <Toggle {...toggleProps} className="some-class" id="toggle-1" />
      <Toggle {...toggleProps} className="some-class" id="toggle-1" />
      <Toggle {...toggleProps} className="some-class" id="toggle-1" />
    </div>
    )
  )

Additional information
While you might argue that IDs should the unique in the DOM, the DOM specification clearly understands that is not always the case.
https://dom.spec.whatwg.org/#dom-nonelementparentnode-getelementbyid

The getElementById(elementId) method, when invoked, must return the first element, in tree order, within the context object’s descendants, whose ID is elementId, and null if there is no such element otherwise.

In a React system, this more common that we'd like, since, in many cases you might render a list of child components and one of those components might be a composite component and that component might use a Toggle with an ID to better support automation testing.

Hi :wave: thank you for reporting! You brought up a good topic on ID duplication, and it's actually what explains the problem here. id prop in our <Toggle> is used for setting the id to (hidden) <input> that the <label> working as our toggle UI refers to. Given the ID uniqueness is broken with multiple <Toggle>s with the same ID, the ID reference from <label> to <input> is broken.
It may be worth noting that <Toggle> has a mechanism to auto-generate a unique ID if id is not given. Probably that's what you may have wanted. Hope this helps!


Add shortcodes/ folder  as default

Signed-off-by: Jiang<EMAIL_ADDRESS>shortcodes feature need shortcodes/* as assets to copy  when building project
https://bartholomew.fermyon.dev/shortcodes

Hi @jmu, thank you very much for the PR!
I'm wondering if adding shortcodes/* to the spin.toml without a corresponding directory in source code might be slightly confusing. What if we also add a shortcodes directory and perhaps an example shortcodes script?
Also, can we add a line mentioning this directory along with the others in the README?

Sure, I will push later

Thank you @jmu, this looks great.
One last ask: Can you please GPG-sign the commits on this PR?  (See https://developer.fermyon.com/cloud/contributing#8-commit-changes).  Please let me know if you have any questions on the process.


Adding Webview switching to office-addin-debugging

This is intended to be pulled in after this PR is pulled in. The changes for separate packages are kept in separate PRs, so that deployment will be easier.

Btw, the CI loop failure on the Windows 1903 agent is a known issue.  @akrantz  was working on this but not sure if he ever figured this out.  You may want to merge master is you haven;t already done so

@arttarawork any ideas for the CI build failures?

Kicking off manual steps to install all packages on VM where CI loop fails and retriggering failed run

CI job passed


Have esgleam/bundle automatically install esbuild if it esgleam/install has not been run

Hello! Thank you for this project, it rules!
It would be cool if it automatically installed the dep if has not been done yet, like how gleam run does for Gleam deps.
Thanks,
Louis

Thanks. From v0.4.2, esgleam will automatically install esbuild when running esbuild.bundle


Change lifx state ignoring power state

Code changes allow for lifx bulbs to change their state such as
brightness, hue, and color, without changing the power state of the
bulb.

I don't want to add an extra value to the main abstract base class for this. You should be able to just compare to self._power?

A comparison could be done using a value template via a script or automation, but that would add a hell of a lot of lines to the configuration. I considered adding a change_state service, but that adds unnecessary complexity to the code base and isn't consistent with the Lifx API (Local or Remote).


Use correct binary path when entering lame duck mode.

When upgrading from 1.4.1 to 2.x.x entering lame duck mode would fail as it would lookup the binary server path for the desired version and not the currently running version.
This patch uses the currently running pod version to lookup the binary server path.

I think we just experienced this when going from v1.4.1 to 2.1.6 using the v0.6.2 version of the operator. Completely removing all of the nats cluster pods did the trick but we did experience 60 seconds of downtime during this period.


Tree Refresh

In working with the refresh I have noticed recently that the tree actually doesn't refresh until I click on it. The data appears to have updated behind the scenes but the visual state of the tree doesn't change until I click on a node.
Have you noticed this? I can port my code to a sample if it helps.
Thanks!

User Error, my apologies. :)
For those who may run across this, be very careful with your shouldComponentUpdate logic.


Regression: ProTerm 3.1 doesn't start with ProDOS 2.5.0a4

Regression: ProTerm 3.1 doesn't start with ProDOS 2.5.0a4

BUG

2.5
Description

Under ProDOS 2.5.0a4, ProTerm 3.1 will not start.  It complains "An error occurred accessing: /H1/PROTERM.3.1/pt3.bios".  Note the mixed case in the message.
This works under 2.5.0a3 release 2, so it is a recent regression.
Expected Behavior

ProTerm 3.1 should start.
Actual Behavior

Error dialog shown instead.
Possible Fix

Steps to Reproduce

Run PR3.SYSTEM
Observe the error dialog
Reboot into 2.5.0a3 release 2
Run PT3.SYSTEM
All is well.

Context

Was planning on regression testing the issue with the trailing garbage after the volume names.
Your Environment

Hardware:

Apple //e Ehhaanced 128k.  MicroDrive/Turbo.
ProDOS8 version:
2.5.0a4
Non-Operating System release software being used:
ProTerm 3.1

Good catch. Now fixed.
https://drive.google.com/open?id=1DNFFd2BLIXL3krPbGWvfu8E0m9fwZiRP

Confirmed fixed in the latest 2.5.0a4 ... 2.5.0a4r2 let's call it :)


"Cursor finalized without prior close()" warning

Hello! First of all, thanks so much for an incredible project! I recently noticed that every so often during syncing and configuration changes, there will be a "Cursor finalized without prior close()" warning. It seems like the cursor doesn't always get closed in the "loadHashcodes" method for SpeakersHandler, VideosHandler, and ExpertsHandler.

I'm pretty sure we took care of a few non-closed cursors in the 2015 source release. Please re-open if this re-occurs.


unable setup huawei_lte

Home Assistant release with the issue:

0.90.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

hassio
Component/platform:

https://www.home-assistant.io/components/huawei_lte/
Description of problem:
2019-03-22 21:58:40 ERROR (MainThread) [homeassistant.setup] Error during setup of component huawei_lte
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/setup.py", line 154, in _async_setup_component
    component.setup, hass, processed_config)  # type: ignore
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/huawei_lte/__init__.py", line 122, in setup
    _setup_lte(hass, conf)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/huawei_lte/__init__.py", line 142, in _setup_lte
    data = RouterData(client)
  File "<attrs generated init b1407ab531e0a88414e75b58be1b0189b46eb6cf>", line 8, in __init__
    self.__attrs_post_init__()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/huawei_lte/__init__.py", line 53, in __attrs_post_init__
    self._update()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/huawei_lte/__init__.py", line 97, in _update
    self.wlan_host_list = self.client.wlan.host_list()
  File "/usr/local/lib/python3.7/site-packages/huawei_lte_api/AuthorizedConnection.py", line 19, in wrapped
    return fn(*args, **kw)
  File "/usr/local/lib/python3.7/site-packages/huawei_lte_api/api/WLan.py", line 78, in host_list
    host = hosts.get('Hosts', {}).get('Host')
AttributeError: 'NoneType' object has no attribute 'get'
2019-03-22 21:58:40 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of huawei_lte.sensor. Setup failed for dependencies: huawei_lte
2019-03-22 21:58:40 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform huawei_lte.sensor: Could not set up all dependencies.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
huawei_lte:
  - url: http://<IP_ADDRESS>/
    username: *****
    password: *****

sensor:
  - platform: huawei_lte
    monitored_conditions:
      - device_information.WanIPAddress
      - device_signal.rsrq
      - device_signal.rsrp
      - device_signal.rssi
      - device_signal.sinr
      - traffic_statistics.CurrentDownloadRate
      - traffic_statistics.CurrentUploadRate
      - traffic_statistics.TotalUpload
      - traffic_statistics.TotalDownload
      - traffic_statistics.TotalConnectTime

Traceback (if applicable):
2019-03-22 21:58:39 DEBUG (SyncWorker_7) [homeassistant.components.huawei_lte] device_information={'DeviceName': 'B525s-23a', 'SerialNumber': 'XXXXXX', 'Imei': 'XXXXXX', 'Imsi': 'XXXXXX', 'Iccid': 'XXXXXX', 'Msisdn': None, 'HardwareVersion': 'WL1B520FM', 'SoftwareVersion': '*******', 'WebUIVersion': '<IP_ADDRESS>.03', 'MacAddress1': 'XXXXXX', 'MacAddress2': None, 'WanIPAddress': '*******', 'wan_dns_address': 'XXXXXX', 'WanIPv6Address': None, 'wan_ipv6_dns_address': None, 'ProductFamily': 'LTE', 'Classify': 'cpe', 'supportmode': 'LTE|WCDMA|GSM', 'workmode': 'LTE', 'submask': '<IP_ADDRESS>'}
2019-03-22 21:58:39 DEBUG (SyncWorker_7) [homeassistant.components.huawei_lte] device_signal={'pci': '332', 'sc': None, 'cell_id': '35907843', 'rsrq': '-12dB', 'rsrp': '-87dBm', 'rssi': '-59dBm', 'sinr': '1dB', 'rscp': None, 'ecio': None, 'mode': '7', 'ulbandwidth': '10MHz', 'dlbandwidth': '10MHz', 'txpower': 'PPusch:3dBm PPucch:-7dBm PSrs:13dBm PPrach:1dBm', 'tdd': None, 'ul_mcs': 'mcsUpCarrier1:19', 'dl_mcs': 'mcsDownCarrier1Code0:0 mcsDownCarrier1Code1:2', 'earfcn': 'DL:6400 UL:24400', 'rrc_status': '1', 'rac': None, 'lac': None, 'tac': '225', 'band': '20', 'nei_cellid': 'No1:323No2:330', 'plmn': '24803', 'ims': '0'}
2019-03-22 21:58:39 DEBUG (SyncWorker_7) [homeassistant.components.huawei_lte] traffic_statistics={'CurrentConnectTime': '526426', 'CurrentUpload': '155746501', 'CurrentDownload': '8428', 'CurrentDownloadRate': '0', 'CurrentUploadRate': '256', 'TotalUpload': '1295512707', 'TotalDownload': '15933986', 'TotalConnectTime': '10644416', 'showtraffic': '1'}

Additional information:

Same issue here.

Same issue, worked fine on 0.89.x and earlier.

Same issue with 0.91.0

Same issue with 0.91.1

any updates here?

Hey everybody,
I found the problem. This problem has been implemented by this commit : #21791
i tried to edit manifest.json (/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/huawei_lte/manifest.json) to put the release to 1.1.3.
HomeAssistant starts and does not raise any problem.
In version 1.1.3 the sendings notification does not work.
I tried release 1.1.4 and it works !
For the test I tried version 1.2.0 and I have the same errors as in 1.1.5
I hope that these tests will be able to help you and to find a solution to this bug
Bye

Hey everybody,
I found the problem. This problem has been implemented by this commit : #21791
i tried to edit manifest.json (/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/huawei_lte/manifest.json) to put the release to 1.1.3.
HomeAssistant starts and does not raise any problem.
In version 1.1.3 the sendings notification does not work.
I tried release 1.1.4 and it works !
For the test I tried version 1.2.0 and I have the same errors as in 1.1.5
I hope that these tests will be able to help you and to find a solution to this bug
Bye

good for you, but im running hassio and i dont have folders you mention.... still wating for fix but it looks like nobody doesnt care :)

Hi @kuradi,
You have tried this command
find / -name manifest.json | grep huawei_lte
Regards

Hi @kuradi,
You have tried this command
find / -name manifest.json | grep huawei_lte
Regards

just tried. no results.
its kinda ridiculous atm... i opened this issue 3 months ago and there are zero progress with it :(

@kuradi Totally agree - this is where home assistant lets itself down.
Anyway, a fix that has worked for me was to comment out the following lines in /usr/local/lib/python3.7/site-packages/huawei_lte_api/api/WLan.py
`#        host = hosts.get('Hosts', {}).get('Host')
if isinstance(host, dict):
hosts['Hosts']['Host'] = [host]`
Your path might be different depending on python versions.

@awarecan is there any progress at all?

Has anyone here written an issue up against https://github.com/Salamek/huawei-lte-api/issues?  The bug is not in home assistant, it's in the resource.  There's a code block that changed in the exact area that has the issue.
https://github.com/Salamek/huawei-lte-api/commit/df634440796e281a4cc8e8f1434df70a2e4682c8#diff-94d33c0e96407782108a8e8b438784aa
Would be advantageous if one of you guys (who has the device) would write up an issue against it.  Then when a new version of huawei-lte-api is built, it can be added to HA as a resource.  Otherwise you guys will always be downgrading to 1.14 through the manifest.json file.

Has anyone here written an issue up against https://github.com/Salamek/huawei-lte-api/issues? The bug is not in home assistant, it's in the resource. There's a code block that changed in the exact area that has the issue.
Salamek/huawei-lte-api@df63444#diff-94d33c0e96407782108a8e8b438784aa
Would be advantageous if one of you guys (who has the device) would write up an issue against it. Then when a new version of huawei-lte-api is built, it can be added to HA as a resource. Otherwise you guys will always be downgrading to 1.14 through the manifest.json file.

i have no idea what to write there :)

@kuradi this bug was present in version 1.1.5 to 1.3 of https://github.com/Salamek/huawei-lte-api, version >=1.4 should be ok again, current version is 1.4.1...
So update your depedencies && close this issue if it works...

@kuradi this bug was present in version 1.1.5 to 1.3 of https://github.com/Salamek/huawei-lte-api, version >=1.4 should be ok again, current version is 1.4.1...
So update your depedencies && close this issue if it works...

sorry but how should i do it when im using hassio?

@kuradi you can open a pull request to change the dependency version in https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/huawei_lte/manifest.json

thanx. i have no idea how to do it. maybe somebody smarter will open request?


StripeElement.vue options are considered optional but generate console warning when left empty

When creating the <StripeElement> component, the options prop is considered optional, but it generates an "Invalid watch source" console warning due to a watch() being supplied with a plain object instance via its default value:
https://github.com/ectoflow/vue-stripe-js/blob/ca1f828bc0d5b230927e7b0b37911e90371d0b89/src/components/StripeElement.vue#L33-L35
https://github.com/ectoflow/vue-stripe-js/blob/ca1f828bc0d5b230927e7b0b37911e90371d0b89/src/components/StripeElement.vue#L85-L87

I think the problem is that you try to watch non-reactive property, I'm pretty sure if you try toRefs on your props the warning will be gone. Note it's a Vue warning, not a typescript
import { toRefs } from 'vue'
const { options } = toRefs(props)

watch(options, () => {
  // ...
})

Ah, now I got it

Oh, I'm not watching anything. This is coming from the vue-stripe-js source element.
Here's my code:
<StripeElements
    v-if="stripe.ready && stripe.intent"
    ref="elements"
    class="space-y-4"
    #default="{ elements }"
    :stripe-key="stripe.key"
    :elements-options="elementsOptions"
>
    <StripeElement type="payment" :elements="elements"/>
    <!-- No :options configured above. -->
</StripeElements>

I'll take a look, this requires a fix, thanks for reporting

Happy to help! Let me know if you'd like help testing anything out 👍
Thanks so much for your work on this package ❤

Try version 1.0.1

Excellent, works great -- thank you! 🙏


fixed php location

# /usr/bin/php -v
bash: /usr/bin/php: No such file or directory
# /usr/local/bin/php -v
PHP 7.0.17 (cli) (built: Mar 21 2017 23:26:38) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies

Thanks!


Redirect on bad CSRF instead of presenting bad page

The current CSRF handler is a bit harsh with bad CSRF tokens on webpages
I think we can be a little kinder and redirect to base page with a flash error
Fix #14167
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Hmm, this certainly improves UE greatly, but I don't think merging this should close that issue entirely (although that issue lacks details for further investigation to take place).

But the submitted form information will be lost. Before we can click back button on browser to return back to form page.

But the submitted form information will be lost. Before we can click back button on browser to return back to form page.

The back button still works for me.

Codecov Report

Merging #14937 (e129316) into main (fc1607b) will decrease coverage by 0.00%.
The diff coverage is 13.33%.

@@            Coverage Diff             @@
##             main   #14937      +/-   ##
==========================================
- Coverage   45.51%   45.51%   -0.01%
==========================================
  Files         709      709
  Lines       83755    83767      +12
==========================================
+ Hits        38120    38124       +4
- Misses      39500    39508       +8
  Partials     6135     6135

Impacted Files
Coverage Δ

modules/context/csrf.go
70.17% <13.33%> (-11.20%)
:arrow_down:

services/pull/pull.go
41.99% <0.00%> (ø)

models/gpg_key.go
51.99% <0.00%> (+0.56%)
:arrow_up:

modules/queue/workerpool.go
54.96% <0.00%> (+0.76%)
:arrow_up:

modules/log/event.go
59.90% <0.00%> (+0.94%)
: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 fc1607b...e129316. Read the comment docs.

I think it's better to back port to v1.14

-> #16378


Mastership can bounce around, TTL not refreshed?

I think I've seen the mastership bounce around after the first TTL expiry.  Manifests as a CaS failure in the master's renewal loop.
Maybe we're not specifying the right parameters to etcd?  The docs say
The directory's TTL can be refreshed by making an update. You can do this by making a PUT with prevExist=true and a new TTL.

This was with the RPMs that were built today.

Hmm, did some manual testing on the python CLI and I see the TTL get updated when I run a command like this:
c.write("leader", "me", ttl=180, prevValue="me")

After the first failure it seemed to settle down and the master happily kept renewing.  Maybe the elector was getting starved or something else?

This may be related to ongoing problems with the ready flag.

For the elector to get starved it would need to stop spinning in its loop for 30 seconds. However, that probably can happen if the TCP connection to etcd gets broken: the timeout is also 30 seconds. I think the etcd timeouts should probably be far shorter than the interval: say 1/5 of it? That way we'll correctly spot a dead etcd connection fast enough to ensure that we can make a good attempt at getting a write into etcd.
Also, note that when we fail to maintain the master key in this block we don't actually attempt to formally give up the mastership. This leaves us without a master for quite a while.
Any of these problems could be the issue, but without a log I don't know any better. And there should be a log, because there aren't many places where exceptions can happen in the election code.

I'll see if I can get the log from the customer.  It was a ValueError from the master's refresh loop.  The logs should let us see the timing though.

Wrote a repro script but can't seem to hit this case: https://gist.github.com/fasaxc/e8c6a7d4dfb760a61503

If we can't get a log from the customer then I suspect the only thing we can do is try to repro live in neutron in the large scale test rig.  Maybe it really is getting starved out by Neutron's start-of-day processing?

@robbrockbank one possible next action is you receiving the log from the customer.

Currently this is blocked as we have no repro and no logs. Removing this from 0.21 until we can unblock it.

Similarly removing from 1.0, we can't fix it without something to go by.

I don't think we're going to get those logs, lets close unless we see this again.


LibUI::FFI::DrawBrush LinearGradient & RadialGradient Examples

The LibUI::FFI::DrawBrush object is supposed to support LinearGradient with Type=1 and RadialGradient with Type=2 if I understand correctly.
In those cases, these attributes could be set:

X0
Y0
X1
Y1
OuterRadius
Stops

Could you please provide examples of paths with draw_fill having LinearGradient and RadialGradient (perhaps applied to a rectangle)?
Again, my lack of expertise in Fiddle makes me prefer to rely on you as a reference for how to do advanced things with it.
Thanks

I understand. I'll work on it over the weekend.
The C sample code here should give us a good idea.
https://github.com/andlabs/libui/blob/master/test/drawtests.c

Great work. Just amazing.
The addresses of stop1 and stop2 are not contiguous, so I copy them and allocate contiguous memory as a new Ruby string. This is a little different from the original libui, but should not be a problem.


Fix for log_test.txt

The original device config needs to be restored after the test is done.

@europaul , should the tests here pass? I mean on EVE 13.7.0?

@europaul , should the tests here pass? I mean on EVE 13.7.0?

yes

How nice to see all the checks go green, huh? :D


[Question] azure - Executable doesn't exist at /ms-playwright/chromium-1097/chrome-linux/chrome

Hi,
I want to use playwright with azure, locally everything works.
Application deployment is done using pipelines.
After running on Azure and running the function, I get the following message:
Executable doesn't exist at /ms-playwright/chromium-1097/chrome-linux/chrome Looks like Playwright was just installed or updated. Please run the following command to download new browsers:  pwsh bin/Debug/netX/playwright.ps1 install
My docker:
`FROM mcr.microsoft.com/azure-functions/dotnet:4 AS base
WORKDIR /home/site/wwwroot
EXPOSE 80
RUN apt-get update -yq
&& apt-get install wget -yq
&& wget -q https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb
&& dpkg -i packages-microsoft-prod.deb
&& apt-get update -yq
&& apt-get install powershell -yq
RUN apt-get update
&& apt-get install -y
build-essential
cmake
git
wget
unzip
unixodbc-dev
&& rm -rf /var/lib/apt/lists/*
FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY ["src/Monitoring/Monitoring.csproj", "Monitoring/"]
COPY ["src/Monitoring/", "Monitoring/"]
RUN dotnet restore "Monitoring/Monitoring.csproj"
COPY . .

ENV AzureWebJobsScriptRoot=/home/site/wwwroot
AzureFunctionsJobHost__Logging__Console__IsEnabled=true`
Anyone had a similar problem?

Looks like you don't run the RUN pwsh ./playwright.ps1 install chromium command inside the final image.

Thanks, everything works fine now
FROM base AS final
WORKDIR /home/site/wwwroot
COPY --from=publish /app/publish .

COPY --from=build /app/build/Microsoft.Playwright.dll .
COPY --from=build /app/build/playwright.ps1 .
RUN pwsh ./playwright.ps1 install
RUN pwsh ./playwright.ps1 install chromium
RUN pwsh ./playwright.ps1 install-deps chromium


OSPAT logo

I apologize I missed the pull request that changed the OSPAT logo, but I think it's worth discussing.
The previous logo was this:

The current version is this:

(if you look close there are black words under the circle part of the logo)
I think a few discernment checks for choosing a logo should include:

single or minimal colors
easily identified symbols aligned with OSPAT theme
no words in the primary logo (we could create other versions with words for use on print or elsewhere)

I personally like the previous version, but am open to discussion or new ideas.

The original version could be modified to look better in the repo:

Personally, I think the brain logo looks like one of those off-the-shelf ones you can get from Upwork or Fiverr.

Haha, ouch. I made that one with Canva. I get it though. TBH I feel the same way about the other one. What if we simplify it a bit? Less colors. No words. Something like this?

Same idea w/ diff colors and white background...

Or transparent background...

My eyeballs like 3 the best out of those choices.

I like the last three. Better colour scheme, I tend to use these palettes (https://coolors.co/palettes/trending). Not sure I feel a difference between the different flips...

How about this version?

It's definitely better than the original! It ticks the open-source box, I like the ying yang aspect in the middle. The outer rim reminds me a little about how the psychedelic effect primarily hit the 5ht in the neocortex...

Great! I'll leave this for a few days in case others want to weigh in.


Fix jetstream calculation bug

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #1421

[x] Tests for the changes have been added (for bug fixes / features)

[ ] (If applicable) Documentation has been added / updated (for bug fixes / features)

[x] CHANGES.rst has been updated (with summary of main changes)

[x] Link to issue (:issue:number) and pull request (:pull:number) has been added

What kind of change does this PR introduce?

jetstream calculation used pressure coordinate, but it should be "vertical".
Modified test data to make it CF-compliant.

Does this PR introduce a breaking change?
Yes, it won't work with datasets that used "pressure" as the vertical coordinate, but that was not CF-compliant.
Other information:
https://cf-xarray.readthedocs.io/en/latest/coord_axes.html#coordinate-criteria

@Thomasjkeel Please take a look to make sure I didn't mess this up.


Feat: Improve SignIn and Signup Screens

Describe the feature
@Yashshukla11 to improve signin and signup screen , assign this issue for me
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

Hey, I'd like to work on this issue. Please assign me this issue.

Hi sir,
As i have good experience of UI design, so i think i can make better UI of sign In and signUp pages.
Please assign this issue to me.

Will you please assign me this issue? I have the experience of layouts by working as android app development.

I would like to work on this issue as part of my contribution to GGSOC. Could you please assign it to me?

please assign this issue to me


Host Frontend as Static Files with Nginx in Prod

I was able to resolve this issue by implementing the suggestion made by @donghj2000 in issue #197
If I add the option
 commonjsOptions: { transformMixedEsModules: true }
in the vite.config.mjs file, then Nginx is able to serve the static files without the need for frontend container to run.
If we proceed with my commit on production deployment, I can implement this one as well.

Addressed with https://github.com/openpredictionmarkets/socialpredict/pull/341


bug importing portal XML files

When importing from DCR portal's XML files, it seems that there is a parsing error. Look at the javascript console for that:

I attach a zip file of Portal files that should be parseable. The test passes if you can visualize them after import and there is no errors in the console.
Text DCR portal XMLs.zip

This bug is more serious than I thought.
After discussions with the original developer, we found that the code associated with the import/export of "DCR Graph XML format" has never been working.
Thus, the parser behind must be replaced with a parser that can extract models from the DCR portal.
In particular, you will need to look at the structure under
I am attaching a small example, bear with me the verbosity of the XML format. I will highlight in bold the key aspects

            <**events**>
                <**event id="Activity0"**>

                            <**location xLoc="250" yLoc="25"**/>

**Alice**

private

1
1
0

private

1
6
0

                <**labelMapping eventId="Activity0" labelId="A"**/>

                <**condition sourceId="Activity0" targetId="Activity1"** filterLevel="1" description="" time="" groups=""/>

                <**response sourceId="Activity0" targetId="Activity1"** filterLevel="1" description="" time="" groups=""/>

                <**exclude sourceId="Activity4" targetId="Activity0"** filterLevel="1" description="" time="" groups=""/>

                <**include sourceId="Activity3" targetId="Activity2"** filterLevel="1" description="" time="" groups=""/>

                <**milestone sourceId="Activity5" targetId="Activity0"** filterLevel="1" description="" time="" groups=""/>

            <**spawns/**>

                <**event id="Activity0"**/>

                <**event id="Activity0"**/>

Some overview:

We don't need anything from the  tags
The events are described as a collection, and they can have a type (nesting, subprocess, etc). The identifier is a string, but the labels you show are described in the  tag. I think there's some repeated code ( is redundant), so I would just focus in visualizing the labels from labelmappings
The xy location for each event is given in the tags . You can convert that to DCR.js canvas
The relations are described in , where each collection (conditions, responses, etc) is treated separately
The initial marking is given in , where each type of marking (executed, included, pending) has its own collection.
There are other fields, but I would suggest to start with this and start creating a test suite of imports that are working, then extend with other functionality

HA

DCR portal xmls.zip


Ion-java-cli-process

Description
Ion-java-cli has 2 core parts for version one: process and compare.
This commit is for process which supports:

--output
--output-format
--error-report

note: I just noticed some check style errors such as I forget space after if-else statement, I'll fix them in the next commit.
What I finished

Support binary/text/pretty format
test: some example files which include string value, integer, list, structure and local symbol tables.
Support events format
test: some example files which include string value, integer, list, structure and local symbol tables.
Support -o options which outputs a file to ion-java/.
test: some example files which include string value, integer, list, structure and local symbol tables.
Support -e options which outputs error report to ion-java/.
test: some example files which include string value, integer, list, structure and local symbol tables.
Implement Event structure
Able to Write a Event structure to outputStream in Events type
test: converted a ionReader value to a Scalar event
Convert ionStream to Event structure
test: converted five types of events to outputStream(container_start, container_end, symbol_table, scalar and stream_end)
Check if Symbol table changes
test: It works for two local symbol tables with the same imports or the second local symbol table imports the previous local symbol table's name (which means the imports field of the current symbol table is previous symbol table's name)

What I'm going to do next/not implement yet

Error report structure
Embedded stream
--output-format none

Question/Specific areas what to check:

If Annotation is $0, both text and import location show 'null.string' while ion-c just simply shows 'null'. Not sure if it's because ion-java and ion-c performance different.
Reproduce/code: Code is in Event.java line 55-59

The output file is always start with a blank line.
Reproduce/code: To reproduce this, use -o  and -f events options and generate a new output file which its first line is blank.

When checking if 2 symbol tables are same, my logic checks the cases of systemTables, shareTables and substitue too which may be redundant.
reproduce/code: Code is in IonProcess.java: line 236

Local symbol table has 2 fields, imports and symbols. I only checked imports when checking if 2 symbol tables are same, Do we need to check symbols as well?)
reproduce/code: Code is in IonProcess.java: line 236

Addition question:

I checked styles such as extra space, camel format. if I miss anything please comment the line number, I"ll fix them in the next commit. :)
Not sure if I name the functions or variables appropriately. For example, IonProcess 228, I named two symbol tables x and y.

I created another pr2 whose destination is pr1: https://github.com/cheqianh/ion-java/pull/2
Thanks!


Milestone 1.4: Create wallet - specs & progress

This is a tracker/discssion issue for the 1.4 milestone (design docs).
Goal is to add a wallet creation to the application. In milestone 1.3, we added wallet import, now we also let users create wallets. This includes a prompt during the first use experience, and a complex flow to guide users through creating different types of wallets. We will start simple, but need to ensure to keep future updates in mind, like creating multi-key wallets with several fallback paths.
Addition:

User flow for creating various types of wallets (1+ keys, external, descriptor, miniscript, etc)

Specs:
We really need to create specs for which technical features will be supported here to inform the design

#27 is an older issue on this topic form our design discovery in September 2022. Closing that one now in favor of this new one here that is in-line with our milestone schedule.

@GBKS I think you can assign me and @rabbitholiness
My updates from this week can be seen here

Regular

Multi-key

Custom

Main questions now

Should we allow to import keys for Multisig by uploading a file? (I think it's a bad practice)
Options in Custom wallet needs to be consulted with devs
Since hardware wallet and view-only is more of import than creation, I didn't include them here. Is this a good choice?

I iterated a bit on the flows and recorded a video going through the prototype. Most changed in how keys are added to the multisig, I tried to implement the idea we discussed on last call.
I think the designs need:

Design review on key adding flows
General technical review, especially for Custom flow

Link to Figma designs
Prototypes

Singlesig
Multisig
Custom

New Multisig + Custom designs

Here's handoff of Create single-sig wallet flow after round of user testing:
https://www.figma.com/design/CmK2n6zcXUqSTFV8QflP1d/Create-Wallet-Handoff?node-id=0-1&t=nmDB9OCUiurkQ4Jc-0

This is a very big issue. Now that wallet creation is implemented, both from onboarding and from within the app, we should try to wrap this one up and create smaller issues for anything still outstanding. I'll put that on my low-priority list, unless someone else wants to take it on.


Update user_project_wrapper configuration and views.

1- Updated the following in the user project wrapper configuration files:

Defined CORE_AREA in the fixed configuration to prevent having user projects that are larger than 3mm x 3mm
Removed FP_PDN_HPITCH from the default configuration and replaced with FP_PDN_HPITCH_MULT which is used to determine the horizontal stripes pitch using the following formula FP_PDN_HPITCH = 60 + FP_PDN_HPITCH_MULT * 30. This prevents any shorts that may happen with the external connections in the chip.
Removed FP_PDN_OFFSET from the default configuration.
Moved the source $script_dir/../../default_wrapper_cfgs.tcl and source $script_dir/../../fixed_wrapper_cfgs.tcl to the end of the configuration file to prevent overwriting any of the variables by the users.

2- Added obstructions in the LEF view of the user_project_wrapper that helps in caravel development.

The user_project_wrapper has taps, decaps, buffers and tie cells. It should be empty. Please refer to the one in sky130.


Realize graphic application tinyms in one minute Version update for 3.0

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:tinyms0. 3.0 running on jupyter>
/kind bug
/kind enhancement
/kind documentation

What does this PR do / why do we need it:
Improved the update of OPT, server and client interface problems. PIP install tinyms0.3.1 before installation package, start_ Change server to server start_ server,list_ Change servables() to client list_ servables(),Change predict() to client predict().It is done for version update
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewers:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for your submission! Please sign our Contributor License Agreement before we can accept your contribution.

Hi, @xinwenh, I see here you signed the CLA, and I see you are a First-time GitHub contributor, thanks again for the pr.
you have some problems with your first pr：

Your commit description is not accurate and concise enough
You need to change the introduction of your pr again, you need to clarify what type of pr you are, and simply clear what your pr does, you can list the pr tasks you do by serial number, and this The side suggests that you can mention an Issues and then link it through the anchor point in the Pr profile

Hi, @xinwenh, I see here you signed the CLA, and I see you are a First-time GitHub contributor, thanks again for the pr.
you have some problems with your first pr：

Your commit description is not accurate and concise enough
You need to change the introduction of your pr again, you need to clarify what type of pr you are, and simply clear what your pr does, you can list the pr tasks you do by serial number, and this The side suggests that you can mention an Issues and then link it through the anchor point in the Pr profile

Hi, @xinwenh, I have seen two commits on your side, but the tasks are the same, I suggest you merge them

Hi, @xinwenh, I have seen two commits on your side, but the tasks are the same, I suggest you merge them
Thank you for your hint，I will improve it。

Sorry, it needs to be closed because multiple duplicate PR's have been submitted


daemon-rpc: doc undocumented fields

What
Adds documentation for undocumented request/response fields within daemon RPC calls; requires review into monerod.
Some of these are lacking descriptions as I'm not sure what the behavior is for some of the fields. I will know after https://github.com/Cuprate/cuprate/issues/244 and may add more docs then.
Fixes
Table of fixes in this PR, originally tracked here: https://github.com/Cuprate/cuprate/issues/159.
Request fields
These endpoints/methods have undocumented request fields.

Endpoint/method
Link
Notes

get_block_header_by_hash
rpc/core_rpc_server_commands_defs.h @ 1245
hashes. This field lets you specify multiple block hashes.

hard_fork_info
rpc/core_rpc_server_commands_defs.h @ 1962, rpc/core_rpc_server.cpp @ 2760
version. This field lets you specify which hardfork info to retrieve.

get_output_distribution
rpc/core_rpc_server_commands_defs.h @ 2445..2465
top_hash, credits

/get_blocks.bin
rpc/core_rpc_server_commands_defs.h @ 174..179
Optional fields: requested_info, no_miner_tx, pool_info_since

/send_raw_transaction
rpc/core_rpc_server_commands_defs.h @ 617
do_sanity_checks

/get_peer_list
rpc/core_rpc_server_commands_defs.h @ 1373..1374
public_only, include_blocked

/out_peers
rpc/core_rpc_server_commands_defs.h @ 1909
set

Response fields
These endpoints/methods have undocumented response fields.

Endpoint/method
Link
Notes

get_block_header_by_hash
rpc/core_rpc_server_commands_defs.h @ L1260
block_headers. This method will return a block_header AND block_headers if the request only provided a hashes.  The current documentation is also incorrect as the output is not an array of distribution JSON objects, but rather, either raw binary or a JSON byte array. This may change with https://github.com/monero-project/monero/issues/9422 so it is not changed in this PR.

FYI migrating docs elsewhere is considered

lgtm


remove the temporary version.jackson-databind in the pom.xml

It was introduced due to an unmatched release from Jackson core and it is not necessary now.

 remove the temporary version.jackson-databind in the pom.xml master

 remove the temporary version.jackson-databind in the pom.xml 1.6.x


Infrastructure insights solution still required?

In the "onboarding at scale" section this document describes a pre-requisite of adding solutions "ServiceMap" and InfrastructureInsights" to the workspace.
However, while searching in the Solution gallery, infrastructure insights does not appear.
Is this still required for onboarding and if so is it only available through PowerShell or ARM Templates?

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

ID: 59ea9b7f-4a00-3623-7841-a06f71a9d224
Version Independent ID: 745cb2a2-f053-8410-553d-dc80eecb3304
Content: Onboard Azure Monitor for VMs (Preview)
Content Source: articles/monitoring/monitoring-vminsights-onboard.md
Service: azure-monitor
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@jeffwmiles Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@jeffwmiles - The preceding sentence (To configure your workspace for this scenario, see) links to the section of the at-scale deployment scenario detailing the steps to install the required prerequisites for that deployment scenario, which included ARM template to enable the two solutions - ServiceMap and InfrastructureInsights.  #please-close since this isn't a doc issue and I hope this resolves your question.  Thanks.

@jeffwmiles
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


MolecularDB flags: public/archived/targeted

Add migration scripts
Remove moldb lists from graphql configs
Modify MolDB GraphQL API

@LachlanStuart please verify the GraphQL API changes

@LachlanStuart BTW, as a result of these changes, the docker dev setup can be broken. Should I test it?

@intsco

BTW, as a result of these changes, the docker dev setup can be broken. Should I test it?

The changes I see in this PR wouldn't have broken it. In fact removing sm-mol-db from the docker-compose.yml would have actually fixed one of the issues


fix: ReplaySubject synchronous reentrant values

The tests you added in https://github.com/ReactiveX/rxjs/pull/6930 were really interesting, I gave it a go and came up with this. Probably needs approval from one of the RxJS core team.
The problem was that when ReplaySubject replayed all the values to a new subscriber, new emissions would hit the subscriber directly instead of being pushed afterwards.
My first take was to first emit every value and then subscribe to the actual subject, and this would make the new tests pass but it failed on another that tests specifically this (should add the observer before running subscription code). And it makes sense because if you don't do a take(_), then you want those values to come through as well.
This solution then keeps the subscribe before emitting values, but protects the subscriber in a way that if new values come through as it's emitting them, it just pushes them to the local copy, so that they will get emitted in sequence.
But it leaves some questions open... what if it completes? what if it errors? Currently I synchronously send the complete/error whenever it happens, but it could be argued that first all the values should be completely emitted before complete/error. I left it like this because I think that delay() has a similar behaviour too.

i think it is a little bit more efficient to use 2 different subscriptions:

"replay buffer" empty? if, yes, then subscribe with forwarding subscriber, else continue
copy "replay buffer"
subscribe with "temp buffer" (only records next emissions)
emit "replay buffer" copy
emit "temp buffer"
unsubscribe "temp buffer"
_checkFinalizedStatuses (return bool if terminated)? if, yes, then we are done, else continue
subscribe with forwarding subscriber

a fun testcase to be added:
const subject = new ReplaySubject(2);
subject.next(1);
subject.next(1);

const fib = subject.pipe(
  pairwise(),
  map(([a, b]) => a + b),
  tap((c) => subject.next(c)),
);

expect(await lastValueFrom(fib.pipe(take(5)))).to.equal(13);
expect(await lastValueFrom(fib.pipe(take(5)))).to.equal(144);

The new proposed test works with the current state of this PR, but I'm not sure what is it testing in specific?
I think adding different operators in a test for a subject breaks a bit the concept of unit testing - All the previous tests in ReplaySubject aren't using operators (except to work with hot/cold observables from the test framework)

its more like an integration test, i agree

i am fine with this fix, but i would wait until feedback from the maintainers on the bug ticket in the main repo.


fix: database for default configuration not initializing properly

Databases for all configuration names are created here: https://github.com/AxaFrance/react-oidc/blob/3e535c94dc57d59956498bfa0ca9536106039bda/packages/react/service_worker/OidcServiceWorker.ts#L288
Before a database is created, there's a check whether it already exists: https://github.com/AxaFrance/react-oidc/blob/3e535c94dc57d59956498bfa0ca9536106039bda/packages/react/service_worker/OidcServiceWorker.ts#L282
But the default database exists since the start: https://github.com/AxaFrance/react-oidc/blob/3e535c94dc57d59956498bfa0ca9536106039bda/packages/react/service_worker/OidcServiceWorker.ts#L41
Which means it won't get properly initialized, so if you do something like this in TrustedDomains.js:
const trustedDomains = {
    default: { domains: [ /* some domains */], showAccessToken: true }
}

the database for default won't show the access token anyway, since it's already initialized to hide the access token:
https://github.com/AxaFrance/react-oidc/blob/3e535c94dc57d59956498bfa0ca9536106039bda/packages/react/service_worker/OidcServiceWorker.ts#L50
I'm not 100% sure that it won't break something else (it seems not to!), but perhaps a maintainer could take a look.

Thank you so much @kosciolek !
I may wait another big pull_request merge before your.
It may create some conflicts because all files will move.


Add use_emulator setting to better align with object_store crate

Hi there
In many datascience project, fsspec and object_store crate settings are used here and there. I found myself writing a conversion method to convert the settings keys from one to the other and mostly it's pretty easy to do.

pandas uses fsspec/adlfs
deltalake uses object_store
polars uses object_store
Most python libs use fsspec/adlfs

See https://docs.rs/object_store/latest/object_store/azure/enum.AzureConfigKey.html#variants
Something I miss from adlfs is the use_emulator shortcut for Azure Blob Storage which should result in setting the connection_string to DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://<IP_ADDRESS>:10000/devstoreaccount1;QueueEndpoint=http://<IP_ADDRESS>:10001/devstoreaccount1;TableEndpoint=http://<IP_ADDRESS>:10002/devstoreaccount1; ( the default connection string of the azure storage emulator)
I think this one should be easy to add and make our lives a little easier :) would also do a PR

Looks like https://github.com/Azure/azure-sdk-for-python/issues/10040 is a similar issue in the upstream azure.storage.blob library. I think we should follow that.

MSFT does not seem to be willing to implement this, but I still think it would be useful


Added Watchlists Stable Version 2021-04-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@allenjzhang / @chiragg4u :
I created this new PR to make the review easier. As you can see, it has 2 commits.

The 1st commit is the copy-paste of existing watchlist spec version 2021-03-01-preview.
The 2d commit has the changes for the stable version.

Thank you for copying the existing version into new folder for first commit. It helps in reviewing the change. Changes looks good from ARM perspective, signedoff, please follow the process given @ https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/212/Swagger-PR-Review to continue


Improve user ergonomics, performance and deny a timing attack

(sorry for the bundled commits, I can separate them into separate PRs if you need)
This looks pretty useful so I wanted to help improve the ergonomics a bit (and then got a bit sidetracked in making it faster). Most of the ownership was not required (so to_owned is generally unnecessary), as the majority of work cannot be done in-place (at least not with current libraries).
This commit fixes a potential timing attack on hmac verification: 486c4a87f9603250167e40d70da2845e04a07500
Performance change:
# before
test bench_decode ... bench:      11,501 ns/iter (+/- 885)
test bench_encode ... bench:       5,036 ns/iter (+/- 511)

# after
test bench_decode ... bench:       3,460 ns/iter (+/- 718)
test bench_encode ... bench:       3,964 ns/iter (+/- 516)

Don't worry for the separated commits, going to have a look now

Much nicer overall!

Cheers!


Modify how Work Items are tracked and used.

We need to fix how Work Items are managed so we can ensure our records are complete. Currently Work Items can be deleted in the Project View to get it cleaned up. Rather than that, we should keep all work items evaluated and add the ability to select Project, Handle-It, or Decline/Ignore for each work item then sort and include based on that for Handle-it PDFs, PAF PDFs and Project Status for appropriate work items so we have a record of what is considered and the Handle-It and Project Views don't get cluttered. A bonus would be a Complete tick box so we know when a Work Item has been completed for larger projects with many work items over time. This replaces Issue #124 and issue #43 by updating the Work Items for new requests rather than having to start a new application.

Suggested changes:
Add:
"Request Date" for when Work Item is entered
"No Action" tick box when the Work Item has been inspected and excluded from Catalyst work
"Project" tick box when the Work Item will be included in Project Recommendation
"Complete" for when the Work Item has been completed, whether it is Handle-It or Project
Note that there is already a Handle-It tick box, which can be the model for the 3 additional tick boxes
And, note that No Action, Project and Handle-It are interlocked so only one can be checked for each Work Item.
PAF or Handle-It PDFs would filter for only Work Items with their respective tick boxes selected and ignore the other Work Items.
In Project Summary Handle-It Summary would sort by Handle-It tick boxes selected and show in the Handle-It Summary. This sorting is independent of Application Status and still collected per application. This will allow for tracking situations like tarping a roof as a Handle-It while the application may be approved as a project to replace the roof.


Update requiments.txt

when I ran kitti_dataset.py  it asked for scikit-image so I said it is better to add it here

Update requiements.txt


Improve sementic div > {nodeText} to div > p > {nodeText}

Q
A

Bug fix?
yes

New feature?
no

Breaking change?
no

Deprecations?
no

Tests added?
no

Fixed issues
-

Improve sementic div > {nodeText} to div > p > {nodeText}. According to: https://stackoverflow.com/a/2226574/2226755 elements should be : div > p > {nodeText}
This make no visual change is only semantic, you can check this : before / after
Q/A
Check the doc page, you should see no difference in the render.

When we use md plugin like this : "plugins": [ "node_modules/jsdoc/plugins/markdown" ],, we get double p like this : div > p > p > {nodeText}, we should fix the semantic when md plugin are not called.


AssertionError when the file is unsuccessfully attached to the message

This error is intermittent and it seems it pops up when the file was not successfully attached to the message by the webex teams backend. I can't reproduce it consistently, but I encountered this problem already twice.
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/api/messages.py", line 210, in create
    data=multipart_data)
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/restsession.py", line 393, in post
    **kwargs)
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/restsession.py", line 250, in request
    check_response_code(response, erc)
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/utils.py", line 217, in check_response_code
    raise ApiError(response)
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/exceptions.py", line 152, in __init__
    detail = _response_to_string(response)
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/exceptions.py", line 91, in _response_to_string
    if request.body else "")
  File ".../.venv/lib/python3.6/site-packages/webexteamssdk/exceptions.py", line 45, in _to_unicode
    assert isinstance(string, basestring)
AssertionError

I was sending a message using
api.messages.create(roomId="id", markdown="text", files=["path/to/file1"])

@dmfigol this issue was resolved with the simplified error messages - released in v1.1.  Thank you for catching and reporting this issue!


Need remove unusable package

Hi, I want to remove this unusable package and release new one, Thanks

Ok, but in general you don't need to remove a package to be able to release a new version.


feat: sign-up app

Add new sign-up application
:rocket: Feature
feat(sign-up): add new application and corresponding module
:house: Internal
ref: ECPROJ-258

CDS Report sms#3513.0 ■

Stage 1

Build CA ✔
Build EU ■
Build US ✔

CDS Report telecom-dashboard#3513.0 ■

Stage 1

Build CA ✔
Build EU ■
Build US ✔

CDS Report sign-up#3513.0 ■

Stage 1

Build CA ■
Build EU ✔
Build US ✔

CDS Report vrack#3513.0 ■

Stage 1

Build CA ■
Build EU ■
Build US ■

CDS Report pci#3513.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report public-cloud#3513.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report telecom-dashboard#3513.0 ■

Stage 1

Build CA ✔
Build EU ■
Build US ✔

CDS Report vrack#3513.0 ■

Stage 1

Build CA ■
Build EU ■
Build US ■

CDS Report sms#3513.0 ■

Stage 1

Build CA ✔
Build EU ■
Build US ✔

CDS Report sign-up#3513.0 ■

Stage 1

Build CA ■
Build EU ✔
Build US ✔

CDS Report public-cloud#3513.2 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report pci#3513.2 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report sign-up#3561.2 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report sign-up#3563.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report vrack#3563.0 ✘

Stage 1

Build CA ✘
Build EU ✔
Build US ✔

CDS Report installation#3574.1 ■

Stage 1

Install ■

CDS Report sms#3650.1 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report sms#3653.0 ■

Stage 1

Build CA ✘
Build EU ■
Build US ✘

CDS Report telecom-task#3653.0 ■

Stage 1

Build CA ■
Build EU ✘
Build US ✘

CDS Report pci#3653.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report freefax#3653.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report public-cloud#3653.0 ■

Stage 1

Build CA ✘
Build EU ■
Build US ✘

CDS Report overthebox#3653.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘

CDS Report sms#3654.0 ■

Stage 1

Build CA ■
Build EU ✘
Build US ✘

CDS Report overthebox#3654.0 ■

Stage 1

Build CA ■
Build EU ✘
Build US ■

CDS Report freefax#3654.0 ■

Stage 1

Build CA ✘
Build EU ■
Build US ✘

CDS Report telecom-task#3654.0 ■

Stage 1

Build CA ■
Build EU ✘
Build US ✘

CDS Report telecom-dashboard#3654.0 ■

Stage 1

Build CA ■
Build EU ✘
Build US ■

CDS Report sign-up#3654.0 ✘

Stage 1

Build CA ✘
Build EU ✘
Build US ✘


Navigate Mazes while being hunted by monsters, you have limited vison. your only tool is a flash that can stun them for a bit, can you beat all the levels?

How do you play your game?
WASD to move, L to flash, get to the exit(white circle), avoid red(bad guys)

Code
Check off the items that are true.

[x ] The game was made using the Sprig editor.
[x ] The game is placed in the in the /games directory.
[ x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[ x] The game runs without errors.
[ x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[ x] The game name is not the same as the others from gallery

Image (If an image is used)

[ x] The image is in the /games/img directory.
[x ] The name of the image matches the name of your file.

Thanks for your PR!

Thanks for your PR! Where did you hear about Sprig?

I heard about it from the hack club at our school

Nice:) Did you completed/won the game? it's hard haha

Yea I just did it, this game is hard indeed (level 24 especially), way harder than I want it to be. If possible, could I just submit a new pr after tweaking the difficulty to not be nearly impossible game?

Nice:) Did you completed/won the game? it's hard haha

Yea I just did it, this game is hard indeed (level 24 especially), way harder than I want it to be. If possible, could I just submit a new pr after tweaking the difficulty to not be nearly impossible game?

You can just update this PR:)

Hello I am back from my hiatus, I got distracted by my semester 1 finals :(,
I have the fixed up code ready BUT I sadly don't know how to edit the pull request to change PR, where do I input my changes?

Hello I am back from my hiatus, I got distracted by my semester 1 finals :(, I have the fixed up code ready BUT I sadly don't know how to edit the pull request to change PR, where do I input my changes?

Go to Files changed > ... > edit :)

updates have been made

Nice! Could you send a gameplay from level 21 to the end? it's hard haha

Nice! Could you send a gameplay from level 21 to the end? it's hard haha

https://youtu.be/0GxJM375tO0?si=oiujvmGkJFrxOSfz


updated guzzle

Hey,
this is just a simple update of guzzle, so we could use the channel in Laravel 8.
Closes #3

This is also an issue for us! If this could get approved & merged would help a few people out. Thank you

This is now redundant - merged in #5 - thanks!


Lower default max_labeled_demos in BootstrapFewShot

Hey team, I think it would be good to lower the default max_labeled_demos from 16 to 8. I have been playing with answering FAQs with 16 and it quickly results in compiling a massive prompt such that I exceed the max token limit. There is probably another way around this -- like ofc setting the argument to 8 or 4 or whatever, but I think this might slightly improve the UX for beginners starting with QA RAG and GPT-3.5-Turbo / ~4K input length LLMs.

Sounds sensible to me.

... like ofc...
What is ofc?

Hey @CShorten , I agree with this! But it will affect a lot of existing runs so it's a bit of a silent breaking change...
Maybe we should keep this and other related things in place for one big breaking release?


[BUG] hardfault after xTimerStart in a task in NRF52832

``
static void sample_task_entry(void * pvParameter)
{
UNUSED_PARAMETER(pvParameter);
EventBits_t event;
check_err_timer = xTimerCreate("Timer", 2000, pdFALSE,(void *) 0, check_error_timer_callback);
if( check_err_timer == NULL )
{
NRF_LOG_ERROR("Timer create failure\r\n");
}
while (true)
{
    event = xEventGroupWaitBits(
        sample_task_event_handle,
        IMU_DATA_DRDY_EVENT,
        pdTRUE,  /* bit should be cleared before returning. */
        pdFALSE, /* Don't wait for both bits, either bit will do. */
        portMAX_DELAY);
    if(event == IMU_DATA_DRDY_EVENT)
    {
        xTimerStart(check_err_timer, 0);
        if(icm4x6xx_read_raw_data(icm42686_dev) != SENSOR_SUCCESS)
        {
            NRF_LOG_ERROR("imu data read failure\r\n");
            NRF_LOG_PROCESS();
        }
    }
}

}
HardFault Detail:
 hardfault: HARD FAULT at 0x000075B6
 hardfault:   R0:  0x0000002E  R1:  0x00004AB0  R2:  0xD1015F00  R3:  0xF0014601
 hardfault:   R12: 0x00000002  LR:  0x00008449  PSR: 0x41000000
 hardfault: Cause: Data bus error (PC value stacked for the exception return points to the instruction that caused the fault)

@jinxiangwzh Were you able to address this issue?

Sorry ,I can't  the issue is still exist

Hi @jinxiangwzh, are you still having this issue? If so, can you please provide more information about the code and stack trace when the hardfault occurs?

Hi @jinxiangwzh,
Since we don't have enough information, closing this issue. Please reopen if you need additional help.


rename SourceCtrlOpts:chunk_size to max_chunk_size, remove rate_limit

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

#19635  👈 (View in Graphite)
main

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


Bad URL when downloading kong-oidc-.rockspec from revomatico/kong

Hello!
The problem is that in the Dockerfile from every version, the url that uses kong-oidc-<version>.rockspec is pointing towards revomatico/kong-oidc master branch, causing download failures.
For example: (revomatico/docker-kong-oidc version 2.4.1-1 -> KONG_OIDC_VER=1.2.3-1)
Dockerfile: https://raw.githubusercontent.com/revomatico/docker-kong-oidc/2.4.1-1/Dockerfile
In the line 39, it tries to download from this URL:
https://raw.githubusercontent.com/revomatico/kong-oidc/master/kong-oidc-${KONG_OIDC_VER}.rockspec
This URL will transform with the env-var substitution into:
https://raw.githubusercontent.com/revomatico/kong-oidc/master/kong-oidc-1.2.3-1.rockspec
The issue is that, on the master branch of revomatico/kong-oidc, there is no kong-oidc-1.2.3-1.rockspec, because it has been updated and now is kong-oidc-1.2.3-2.rockspec
The solution will be to modify every dockerfile to point to the correct url of the revomatico/kong-oidc version. In this case, the correct url would be:
https://raw.githubusercontent.com/revomatico/kong-oidc/v${KONG_OIDC_VER}/kong-oidc-${KONG_OIDC_VER}.rockspec
Hope it helps!

You are absolutely right, thanks for pointing this out! Fixed for the 2.6.x release and for 2.5.x release. I do not see many reasons now to go too much back in time for this.


Skylake server CPUs du not support PP1 domain

All server CPUs do not support the PP1 domain, including Skylake, but for the latter the domain is currently enabled, resulting in a measurement that is always zero.

We are currently not affected by this issue, as our code does not support the skylake server (as of yet). For the moment, we only support the Skylake signature types for the mobile- and deskop versions (model 78 and 94, respectively), whereas the server cpu uses the 85 as model number.
I will include the skylake server cpu in a future update.

Fixed in commit https://github.com/sosy-lab/cpu-energy-meter/commit/e43c19d38867c2a01de2787b27774296e085d230.
The available domains are now automatically detected during runtime, by directly checking the processor as to whether the domains are actually supported.

Unfortunately, there is no way to determine the supported RAPL-domains beforehand. Moreover, the model-types of the Intel cpu's can neither be used to manually dictate which domains should actually be measured. For example, we've checked the 'Skylake desktop'-cpu (model 0x506E0), which is used in both server- and client-cpu's, and found out that some of them support the pp1- and psys-domain, whereas others of the same model do not.
This has led to the current implementation, where we simply read the respective MSRs (that weren't disable before due to an error, for example) and omit the null-values in the final output.


Added duration based timeout to next/prev event

This fixes an issue where rapidly clicking the next/prev buttons will break the slide animation if it runs out of slides to animate to.

this is not correctly
setTimeout({o._animating = false;}, o.duration);
Correctly:
setTimeout(function(){o._animating = false;}, o.duration);


(PDB-2501) Add the ability to test against puppetserver nightlies

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/200/
Test FAILed.

I believe this is actually sufficient. We should be building puppetserver nightlies for all platforms, but on the off chance we don't, we can always fall back to the packages available in the public repos. Should I add a line that includes puppet-agent nightlies as well?

Get:12 http://nightlies.puppetlabs.com/puppetserver-latest/repos/apt/trusty/ trusty/PC1 puppetserver all 2.4.0.master-0.1SNAPSHOT.2016.04.28T0317puppetlabs1 [32.8 MB]
^^ installing puppetserver from the enabled nightlies repo instead of apt.puppetlabs.com

cc/ @wkalt @senior

@puppetlabs-jenkins test this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/201/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/202/
Test FAILed.

@wkalt done! This uses an environment variable to decide if it's going to use nightlies or not. It defaults to not. All I need to do now is update ci-job-configs! But that change isn't blocking this

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/203/
Test FAILed.

@puppetlabs-jenkins test this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/204/
Test PASSed.

This looks good to me, will merge when the pipeline is clear.


Just use the raw object with two parameters.

Just use the raw object with two parameters.
'date' => Medoo::raw("BETWEEN to_date(:today1, 'YYYY-MM-DD') AND to_date(:today2, 'YYYY-MM-DD')",  [
    ':today1' => $today1,
    ':today2' => $today2
])

Originally posted by @catfan in https://github.com/catfan/Medoo/issues/967#issuecomment-846370648

SELECT * FROM reporttata_user WHERE date = BETWEEN to_date('2021-05-19', 'YYYY-MM-DD') and to_date('2021-05-22', 'YYYY-MM-DD')"
$database->log() 多了= 号


fix type issues when creating newContext with extraHeaders

related to issue https://github.com/mxschmitt/playwright-go/issues/118

a test for it would be awesome!

no problem, will add it in a bit

@mxschmitt Let me know if anything doesn't look right. Thank you!

it would be awesome if you could apply the logic in browserImpl.NewPage too. To make this test actual test the feature, you could make an example request or navigate to the server.EMPTY_PAGE page via page.goto and check then on the request headers if the header is present.
I can also pick that up if you want.

That shouldn't be much work, let me add that. Thanks!

seems to be some data race on the test cases, will fix them then

Awesome, thanks!


event handlers are not pure

Event handlers in re-frame should be pure.
In the handlers there are side effects created by calling ajax functions.
https://github.com/yogthos/memory-hole/blob/master/src/cljs/memory_hole/handlers/admin.cljs#L15
The re-frame / pure way would be to write an effect handler which handles the execution of the state change.
Have a look at the following library to see how this can be solved in a pure way:
https://github.com/Day8/re-frame-http-fx

Yeah I keep meaning to switch to using those, just haven't had a chance to get around to it. If you're up for doing a PR that would be much appreciated though. :)


Document ResNet architecture tweak

Add note for resnet architecture
Closes #5964

@datumbox I'm having errors with unittest_onnx which I did not change. Could you give me some clue to resolve this error. Or is there any other reason that cause the error?

@puhuk that's not something you broke. The main branch is also failing. Feel free to ignore it.

The failures on the CI are due to the https://ghcr.io/v2/homebrew/core/gmp/manifests/6.2.1_1 being down temporarily. I checked the docs and they render fine.


Material icon doesn't show

Bug, feature request, or proposal:
Bug
What is the expected behavior?
It should work
What is the current behavior?
Result: Material icon doesn't show on button, on card, on anywhere
What are the steps to reproduce?
Step by step followed the https://material.angular.io/guide/getting-started
What is the use-case or motivation for changing an existing behavior?
First time try
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.0.0-rc.3
Material: 2.0.0-beta.12
OS: Windows 10
Typescript: 2.5.3
Browsers: Google Chrome
Is there anything else we should know?
I imported hammerjs.  I linked the google material+icon to index.html

Show your full code please.

https://github.com/leihuagh/MEAN-Project-Learning/blob/02_build_client/client/src/app/nav/nav.component.html

menu
Home

menu icon online show the text

https://github.com/leihuagh/MEAN-Project-Learning/blob/02_build_client/client/src/app/nav/nav.component.html

menu
Home

On Sun, Oct 22, 2017 at 1:33 AM, Edric Chan<EMAIL_ADDRESS>wrote:

Show your full code please.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/material2/issues/7948#issuecomment-338452952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFu8-QE2MeunzG-y_27cJZtHt2bW7yNoks5sutOmgaJpZM4QByFo
.

--
Lei Hua
<EMAIL_ADDRESS><EMAIL_ADDRESS>

That's because you're missing the CSS stylesheet for Material Icons!
Add the following to your index.html:
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">

Around here:
https://github.com/leihuagh/MEAN-Project-Learning/blob/ba731ca72d98e1eaaf9bb0067c130184979de035/client/src/index.html#L6-L8

@leihuagh - Import of MatIconModule is missing. (in "app-material.module.ts")
For troubleshooting / questions please use stack overflow, gitter, etc.

@ghd8 Thank you so much.  The MatIconModule was missing in my material list
It works now.
@Chan4077 Thank you too
It could be nice to have entire material package in one in the future releases.

Hello, i found this issue not working on IOS. I tried to use mat-error on IOS and its not showing, the code i use :

        <mat-icon color="warn">warning</mat-icon>

        {{errordesc}}

I also attach the stylesheet on index html.


Temporary fix for sites with multi-pnns

1.1.6 wmagent branch workaround for T3_UK multi-pnn sites.
@ticoann can you port it to the new wmagent branch (1.1.8_wmagent?) once that's created?

Thank Alan, I will do that.


EXTREME WIP: Switch to CMR as a backend directly

Seeing what is different between the two branches

To Look into:

Maybe move into translate.py properties, into ASFProduct (custom get attr. Only store umm once, and build the other half whenever it's accessed). Maybe subclass properties/geometry?
If passed SENTENL1, change in translate.py to SENTENEL1A/SENTENEL1B. Other platforms do the same.
Doublecheck subqueries working, and walking through each one. Check for long list searches (+500). Inside search.search.
In constants.py, remove ALL instances of *_PATH (The SearchAPI paths)

Codecov Report

Merging #103 (3bd812b) into master (9411cb6) will decrease coverage by 1.54%.
The diff coverage is 76.36%.

@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   80.55%   79.00%   -1.55%
==========================================
  Files          34       37       +3
  Lines         905     1124     +219
==========================================
+ Hits          729      888     +159
- Misses        176      236      +60

Flag
Coverage Δ

unittests
79.00% <76.36%> (-1.55%)
:arrow_down:

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

Impacted Files
Coverage Δ

asf_search/ASFSearchOptions/defaults.py
100.00% <ø> (ø)

asf_search/ASFSearchOptions/validators.py
64.10% <ø> (+1.70%)
:arrow_up:

asf_search/ASFSession.py
82.60% <ø> (ø)

asf_search/health/health.py
57.14% <0.00%> (ø)

asf_search/search/geo_search.py
58.33% <0.00%> (+4.48%)
:arrow_up:

asf_search/search/granule_search.py
66.66% <0.00%> (ø)

asf_search/search/product_search.py
66.66% <0.00%> (ø)

asf_search/search/search.py
54.16% <64.70%> (-2.31%)
:arrow_down:

asf_search/CMR/subquery.py
69.81% <69.81%> (ø)

asf_search/ASFSearchOptions/ASFSearchOptions.py
83.33% <70.58%> (-7.58%)
:arrow_down:

... and 11 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 9411cb6...3bd812b. Read the comment docs.


chore: deprecate upgrade standards implementation

Not quite sure why this was added, somewhat broken as per #855 and the interface doesn't make much sense and is inefficient.
Deprecating for now and can optimize/update if there are real use cases or the standard is actually added to NEPs

@ChaoticTempest noting that the CI had a failure with the same error as before, just to note the non-deterministic failures are still happening (maybe less frequent, unclear yet)

@austinabell hmm, weird. Yeah keep updating me about these. Might need to up it via the env var to 100 secs, or maybe its not even a timeout issue happening, but that the sandbox node wasn't able to start up. If its the latter that's the issue, the error should have been reported earlier on... It could be that GH has a shared CPU behind its task scheduling, so you get bursty workloads that leads to this non-determinism


MissingPluginException on iOS

MissingPluginException: MissingPluginException(No implementation found for method disableAutoLogIn on channel autologin_plugin)
  File "platform_channel.dart", line 165, in MethodChannel._invokeMethod
  File "<asynchronous suspension>"
  File "autologin_plugin.dart", line 31, in AutologinPlugin.disableAutoLogIn
  File "<asynchronous suspension>"
  File "future.dart", in Future.wait.<fn>

Cannot happen when you respect the result of AutologinPlugin.isPlatformSupported which is false for iOS


[C++][Parquet] Max buffer size for RLE encoding too small resulting in CheckBufferFull failure

I have been serializing dataset of 500 documents with nested schema
and repeated attributes. I had been batching 50 records to a rowgroup.
The check DCHECK_EQ(encoded, num_buffered_values_) in
ColumnWriter::RleEncodeLevels() failed.
We are running out of space in the allocated buffer. This seems
unlikely since we compute the worst case max size required and
allocate accordingly.
Looking more closely at the how the max size is computed and comparing
it with how we write the RLE I noticed the following inconsitency.
The worst case space required would be when there are no repeats and
everything is a literal run with the overhead of the
"litteral_indicator" which is 4 bytes(32-bits). The computation
assumes that we can get MAX_VALUES_PER_LITERAL_RUN = (1 << 6) * 8 of
literals encoded for the overhead of one literal_indicator.
However when I examine the actual code it actually emits literal
values after every 8 literals giving it the overhead of 4 bytes for
every 8 literal values. This can be ascertained from the following
fragments of code.
RleEncoder::Put() {
.....
if (++num_buffered_values_ == 8) {
DCHECK_EQ(literal_count_ % 8, 0);
FlushBufferedValues(false);
}
.....
}
as a result of this in RleEncoder::FlushBufferedValues() we will
encode only one group and not encode the maximum which is
theoretically possible with the scheme.
Suggested fix is to change MAX_VALUES_PER_LITERAL_RUN to 8 to
accurately calculate the buffer size for the current encoding scheme.
Reporter: Anand Mitra
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-698. Please see the migration documentation for further details.

Wes McKinney / @wesm:
This may be a dup of PARQUET-676 – that JIRA contains the makings of a test case. A patch would be most welcome, but I want to make sure that we understand exactly what the problem is.
https://github.com/apache/parquet-format/blob/master/Encodings.md#run-length-encoding--bit-packing-hybrid-rle--3
In Impala's implementation of RLE encoding, which is what parquet-cpp's came from, it does not encode literal runs larger than 504 so that the indicator byte for RLE vs. literal is only a single byte (and the LSB is 1 for literal and 0 for RLE).
See also the parquet-mr code:
https://github.com/apache/parquet-mr/blob/master/parquet-column/src/main/java/org/apache/parquet/column/values/rle/RunLengthBitPackingHybridEncoder.java#L105
and here's where the limit enforced
https://github.com/apache/parquet-mr/blob/master/parquet-column/src/main/java/org/apache/parquet/column/values/rle/RunLengthBitPackingHybridEncoder.java#L188
here's where the limit is enforced in parquet-cpp
https://github.com/apache/parquet-cpp/blob/master/src/parquet/util/rle-encoding.h#L447
so in other words when there are 63 groups of 8 bit-packed values, it flushes the literal run.
So the MAX_VALUES_PER_LITERAL_RUN should be 504, not 512, but it seems there is little harm in the overestimate.
That's as far as I can dig right now, if someone can find the bug and write a patch with a test case that would be most helpful.

Wes McKinney / @wesm:
This should be fixed by https://github.com/apache/parquet-cpp/pull/150

Wes McKinney / @wesm:
Resolved in https://github.com/apache/parquet-cpp/commit/fa6e47616e818f33d8d4774ce43ae6d62cdd59bd
If you still run into this bug can you reopen the JIRA with a reproduction if possible? Thanks


Dashboard sections require superuser permission

To access some of the features (attributes, product class, sites, groups, staff) in the Dashboard, one need to have a superuser status.
It would be more convenient to create new permissions for those sections.

For groups and staff we already work on it in #1267

Duplicate of #1259


Latest Stories by Project Not Showing

Bug Report
Symptom
The latest_stories function exhibited incorrect dictionary key access, resulting in issues when Story data from a specific project in dashboard.
Expected Behavior
List of Latest Stories both above and below threshold for a specific Project in dashboard section should be visible with further dropdown actions .
Actual Behavior
The latest_stories function had incorrect dictionary key access, leading to unexpected behavior when retrieving data from the results list.
Reproduce
Minimal steps to reproduce the bug:

Run Streamlit 'server.py' (containing the latest_stories section in the end).
Attempt to retrieve stories by selecting a specific project from the dropdown list in dashboard.

Additional Context
I have made changes to address this issue, Correcting dictionary key access in the latest_stories function. .
However, a new error related to unique identifiers in st.selecbox has emerged which again hinders the functionality of Latest stories section

Closing this issue as this was fixed with Project-Level Report Page Merge


Exposing TransportChannelProvider & CredentialsProvider

Disclaimer: I am still wrapping my head around the initialization code for Veneer clients, so please shout if this doesn't make sense.
This PR is mainly intended to allow users to specify the size of the GRPC channel pool, but it exposes a way to set all options consumed in the venner-generated FirestoreSettings. AFAIK, there was no way to overwrite the TransportChannelProvider or the CredentialsProvider.
Code snippet that sets the max pool size:
Builder options =  FirestoreOptions.newBuilder().build().toBuilder();
options.setChannelProvider(
   FirestoreOptions.getDefaultTransportChannelProviderBuilder().setPoolSize(2).build());
firestore = options.build().getService();

Without this setting, Firestore is limited to 100 concurrent listeners.

@garrettjonesgoogle Do you want to take a look?


What about recording videos too?

This is a good and reliable library, but it is not complete. Taking picture AND recording video are bound together. One without another is a 3 wheeled Lamborghini.

Hi @m-rahimy thanks for the comment!
think Dmitry has given a pretty nice answer already here: #7.
Contributions are always welcome!


Use async context in msal interceptor specs

Using timeouts, I find, makes the tests a bit hard to reason about. Angular provides a method for making async code synchronous, and one can tick to next or a number of millisecond https://angular.io/api/core/testing/fakeAsync.
Using done() can the be removed, also from the synchronous calls.
Before it takes approximately 4 seconds to run tests

After the changes it runs in approximately 0.15 seconds.

The reason I care is mostly that we have made or own customization as suggested in https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/contributing.md#build-library

and by starting with the same spec file, I found the tests to be a bit slower than I liked.

Codecov Report

Merging #5518 (642165c) into dev (67a1646) will not change coverage.
The diff coverage is n/a.

Flag
Coverage Δ

*Carryforward flag

msal-angular
96.50% <ø> (ø)

msal-browser
86.47% <ø> (ø)

Carriedforward from 67a1646

msal-common
85.22% <ø> (ø)

Carriedforward from 67a1646

msal-core
82.84% <ø> (ø)

Carriedforward from 67a1646

msal-node
83.37% <ø> (ø)

Carriedforward from 67a1646

msal-node-extensions
76.03% <ø> (ø)

Carriedforward from 67a1646

msal-react
94.68% <ø> (ø)

Carriedforward from 67a1646

node-token-validation
88.88% <ø> (ø)

Carriedforward from 67a1646

*This pull request uses carry forward flags. Click here to find out more.

@bjorn-einar-bjartnes-4ss thanks for the contribution! While it's under review, can you please run "npm run beachball:change" in the root to add a changefile as well?

@bmahall - I ran the beachball command after the build step failed. I might have done it incorrectly, but when I run it now it does say
❯ npm run beachball:change

> beachball:change
> beachball change --branch origin/dev

Checking for changes against "origin/dev"
fetching latest from remotes "origin/dev"
Your local repository already has change files for these packages:
  @azure/msal-angular
"msal" has a "none" change type, no version bump is required.
"@azure/node-token-validation" has a "none" change type, no version bump is required.
Skipping package dep validation - package @azure/node-token-validation has change type as none
Validating no private package among package dependencies
 OK!

No change files are needed

@microsoft-github-policy-service agree

@bmahall - I ran the beachball command after the build step failed. I might have done it incorrectly, but when I run it now it does say
❯ npm run beachball:change

> beachball:change
> beachball change --branch origin/dev

Checking for changes against "origin/dev"
fetching latest from remotes "origin/dev"
Your local repository already has change files for these packages:
  @azure/msal-angular
"msal" has a "none" change type, no version bump is required.
"@azure/node-token-validation" has a "none" change type, no version bump is required.
Skipping package dep validation - package @azure/node-token-validation has change type as none
Validating no private package among package dependencies
 OK!

No change files are needed

Yes, there is a changefile now, thanks!

Not that important for me tbh. Closing to avoid bot comments.


Allow directed input for LatentDistributionTest

Reference Issues/PRs
Fixes #218
What does this implement/fix? Explain your changes.
Allows input of directed data to fit function

Codecov Report

Merging #251 into master will decrease coverage by 0.1%.
The diff coverage is 70%.

@@            Coverage Diff             @@
##           master     #251      +/-   ##
==========================================
- Coverage    86.3%   86.19%   -0.11%
==========================================
  Files          33       33
  Lines        1935     1942       +7
==========================================
+ Hits         1670     1674       +4
- Misses        265      268       +3

Impacted Files
Coverage Δ

graspy/inference/latent_distribution_test.py
96.38% <70%> (-3.62%)
:arrow_down:

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 6473afa...9fd91ad. Read the comment docs.


Change development model

Git Flow's release cycle style of coding is not working well for this project as I found when a feature branch and a release branch were needed just to update the CodeSnip page just to bump the version number and release date.
A continuous deployment model will suit better.
Consider removing develop after the next release and branching off master to do development then merging development branches back into master and deploying straight away. Always leave master in a deployable state. Assume every commit / merge with master gets deployed.
The change log could become a log of changes at each deployment. The change log should be updated just before a branch gets merged.
Later, if the site is opened up for others to develop the full GitHub Flow model could be adopted.

Implemented at commit afee1ae


Tighten validation of Name and Namespace

Gonna break people's examples.... :)
Maybe we should make this land right at the beginning of 0.9?

I fixed all the in-tree examples :)
I am fine with letting this sit for a while, but I think that v1b3 should enforce these rules from day 1 (of it's own "real" lifetime).

Agreed - can you throw that on 1519?
----- Original Message -----

I fixed all the in-tree examples :)
I am fine with letting this sit for a while, but I think that v1b3 should
enforce these rules from day 1 (of it's own "real" lifetime).

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70747295

Done
On Tue, Jan 20, 2015 at 2:38 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:

Agreed - can you throw that on 1519?
----- Original Message -----

I fixed all the in-tree examples :)
I am fine with letting this sit for a while, but I think that v1b3 should
enforce these rules from day 1 (of it's own "real" lifetime).

Reply to this email directly or view it on GitHub:

https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70747295
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70749139
.

What would break in actual examples?  We auto-populate namespace from the request context on server side.  Maybe I am missing something.
Sent from my iPhone

On Jan 20, 2015, at 6:04 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
Done
On Tue, Jan 20, 2015 at 2:38 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:

Agreed - can you throw that on 1519?
----- Original Message -----

I fixed all the in-tree examples :)
I am fine with letting this sit for a while, but I think that v1b3 should
enforce these rules from day 1 (of it's own "real" lifetime).

Reply to this email directly or view it on GitHub:

https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70747295
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70749139
.

—
Reply to this email directly or view it on GitHub.

This also changed validation of ReplicationController, which used to allow
bumpyCaps, but now will not.
On Tue, Jan 20, 2015 at 9:16 PM, Derek Carr<EMAIL_ADDRESS>wrote:

What would break in actual examples? We auto-populate namespace from the
request context on server side. Maybe I am missing something.
Sent from my iPhone

On Jan 20, 2015, at 6:04 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
Done
On Tue, Jan 20, 2015 at 2:38 PM, Clayton Coleman <
<EMAIL_ADDRESS>wrote:

Agreed - can you throw that on 1519?
----- Original Message -----

I fixed all the in-tree examples :)
I am fine with letting this sit for a while, but I think that v1b3
should
enforce these rules from day 1 (of it's own "real" lifetime).

Reply to this email directly or view it on GitHub:

https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70747295

--
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70749139>

.

--
Reply to this email directly or view it on GitHub.

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70785896
.

Thanks.  Late night code reviews on a phone can cause me to miss that change.
Sent from my iPhone

On Jan 21, 2015, at 12:22 AM, Tim Hockin<EMAIL_ADDRESS>wrote:
This also changed validation of ReplicationController, which used to allow
bumpyCaps, but now will not.
On Tue, Jan 20, 2015 at 9:16 PM, Derek Carr<EMAIL_ADDRESS>wrote:

What would break in actual examples? We auto-populate namespace from the
request context on server side. Maybe I am missing something.
Sent from my iPhone

On Jan 20, 2015, at 6:04 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
Done
On Tue, Jan 20, 2015 at 2:38 PM, Clayton Coleman <
<EMAIL_ADDRESS>wrote:

Agreed - can you throw that on 1519?
----- Original Message -----

I fixed all the in-tree examples :)
I am fine with letting this sit for a while, but I think that v1b3
should
enforce these rules from day 1 (of it's own "real" lifetime).

Reply to this email directly or view it on GitHub:

https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70747295

--
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70749139>

.

--
Reply to this email directly or view it on GitHub.

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70785896
.

—
Reply to this email directly or view it on GitHub.

We're also still not validating annotations, AFAIK. /cc @markturansky

Is there an open issue for validating annotations?  It should be easy to
add, it's just a matter of sprinkling it about and then testing
On Wed, Jan 21, 2015 at 10:44 AM, Brian Grant<EMAIL_ADDRESS>wrote:

We're also still not validating annotations, AFAIK. /cc @markturansky
https://github.com/markturansky
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70895880
.

Let me know when you do so I can test it against the openshift annotations... we have some... large... annotations.
----- Original Message -----

Is there an open issue for validating annotations?  It should be easy to
add, it's just a matter of sprinkling it about and then testing
On Wed, Jan 21, 2015 at 10:44 AM, Brian Grant<EMAIL_ADDRESS>wrote:

We're also still not validating annotations, AFAIK. /cc @markturansky
https://github.com/markturansky
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70895880
.

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-70927916

Random note (not something you have to do here), we should make a validation test util that makes this easier - i.e. a public struct that says runtime.Object, function that invokes validation, errors I expect, and encourage bits of stuff like ValidateObjectReference(*api.ObjectReference, allowedTypes []string).  We also need to do conversion of embedded Kind fields automatically through the rest API (so v1beta1 returns "Minion" for an ObjectReference kind, but v1beta3 returns "Node").  Yet more work to make pod templates right....

@bgrant0607 See #3788.  Sorry, that fell off my radar for no good reason.

I'm going to build off this with #3789

I'm going to move this inside a new ValidateObjectMeta

We will need to expand service and namespace names to make that feasible.
On Jan 24, 2015 2:33 PM, "Clayton Coleman"<EMAIL_ADDRESS>wrote:

I'm going to move this inside a new ValidateObjectMeta
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/3646#issuecomment-71340972
.

Obsolete