[Snyk] Security upgrade python from 3.7-slim to 3.13-slim

Snyk has created this PR to fix 3 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

terraform/aws/resources/Dockerfile

We recommend upgrading to python:3.13-slim, as this image has only 37 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  823

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  823

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-6210098
  272

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-6210098
  272

Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963
  240

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – b4efee5e-204a-406d-be49-20444d18d2a5
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2024-42005
Python-Django-1.2
Vulnerable Package

Cx22d7540f-80c2
Npm-angular-1.8-1.8.2
Vulnerable Package

Cx7d3bd13f-4c2a
Npm-angular-1.8-1.8.2
Vulnerable Package

Cxdd90df0b-e1ac
Npm-angular-1.8-1.8.2
Vulnerable Package

Cxeaf4b44b-15c8
Npm-angular-mocks-1.8-1.8.2
Vulnerable Package

CVE-2024-27351
Python-Django-1.2
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-5.2.1
Vulnerable Package

CVE-2024-29415
Npm-ip-1.1.5
Vulnerable Package

CVE-2024-37890
Npm-ws-7.5.6
Vulnerable Package

CVE-2024-37890
Npm-ws-7.4.6
Vulnerable Package

CVE-2024-37890
Npm-ws-8.2.3
Vulnerable Package

CVE-2024-37890
Npm-ws-8.3.0
Vulnerable Package

CVE-2024-38355
Npm-socket.io-4.4.0
Vulnerable Package

CVE-2024-38875
Python-Django-1.2
Vulnerable Package

CVE-2024-39330
Python-Django-1.2
Vulnerable Package

CVE-2024-39614
Python-Django-1.2
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

CVE-2024-4068
Npm-braces-3.0.2
Vulnerable Package

CVE-2024-41989
Python-Django-1.2
Vulnerable Package

CVE-2024-41990
Python-Django-1.2
Vulnerable Package

CVE-2024-41991
Python-Django-1.2
Vulnerable Package

CVE-2024-45296
Npm-path-to-regexp-0.1.7
Vulnerable Package

CVE-2024-45296
Npm-path-to-regexp-1.8.0
Vulnerable Package

CVE-2024-45590
Npm-body-parser-1.19.0
Vulnerable Package

CVE-2024-47178
Npm-basic-auth-connect-1.0.0
Vulnerable Package

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 83
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 83
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

CVE-2024-28849
Npm-follow-redirects-1.14.6
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.19
Vulnerable Package

CVE-2024-28863
Npm-tar-6.1.11
Vulnerable Package

CVE-2024-29041
Npm-express-4.17.1
Vulnerable Package

CVE-2024-37168
<EMAIL_ADDRESS>Vulnerable Package

CVE-2024-38999
Npm-requirejs-2.3.6
Vulnerable Package

CVE-2024-39329
Python-Django-1.2
Vulnerable Package

CVE-2024-4067
Npm-micromatch-4.0.4
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CVE-2024-43788
Npm-webpack-5.64.1
Vulnerable Package

CVE-2024-43796
Npm-express-4.17.1
Vulnerable Package

CVE-2024-43799
Npm-send-0.17.1
Vulnerable Package

CVE-2024-43800
Npm-serve-static-1.14.1
Vulnerable Package

CVE-2024-45231
Python-Django-1.2
Vulnerable Package

CVE-2024-47068
Npm-rollup-1.11.3
Vulnerable Package

CVE-2024-47068
Npm-rollup-2.59.0
Vulnerable Package

CVE-2024-47764
Npm-cookie-0.4.1
Vulnerable Package

CVE-2024-47764
Npm-cookie-0.4.0
Vulnerable Package

CVE-2024-4128
Npm-firebase-tools-9.23.1
Vulnerable Package

Healthcheck Instruction Missing
/Dockerfile: 1
Ensure that HEALTHCHECK is being used.


Rewrite log configuration in yaml

Useful links:

kotlin logging library
guide to java logging
simple guide to yaml config

The logs should be written to the disk by default, not to the console.

Added RollingFile logger, not using yaml but still XML.


Disable ping.js

Hi, as my knowledge of html is far worse than 'limited' I thought I'd ask here, is it possible to disable the checking and jump straight to the mainpage and simply show it as "online". As I'm running my webserver on my plexserver there is really no need to check if its up. Is there a simple line of code I can change or something?

Nevermind, I found that your 1.0 release didnt check but instead just showed a static page, exactly what I was looking for.

@yeyeoke Glad you got it working.


fix(libsinsp): retrieve the correct exepath with execveat syscall

What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area libsinsp
/area tests
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
This PR fixes the retrieval of the execveat enter event when sinsp is parsing the execve exit event. Before this commit it was only possible to retrieve the enter event associated with the exit event we are parsing, so for example PPME_SYSCALL_EXECVE_19_X could only retrieve PPME_SYSCALL_EXECVE_19_E but not PPME_SYSCALL_EXECVEAT_E and this was a bug since in some cases the PPME_SYSCALL_EXECVE_19_X corresponds to a PPME_SYSCALL_EXECVEAT_E and not to a PPME_SYSCALL_EXECVE_19_E.
The execveat syscall is a wrapper of execve, when the call succeeds the event returned is simply an execve exit event. So if an execveat is correctly executed we will have, a  PPME_SYSCALL_EXECVEAT_E as enter event and a PPME_SYSCALL_EXECVE_19_X as exit one.
Moreover since we parse the exit event only if the syscall succeeds, i removed the support for PPME_SYSCALL_EXECVEAT_X in the parse_execve_exit method since we will never obtain a PPME_SYSCALL_EXECVEAT_X if the execveat call is successful.
I've added some tests to stress the new logic :)
Which issue(s) this PR fixes:
Fixes #543
Special notes for your reviewer:
This PR depends on https://github.com/falcosecurity/libs/pull/551, here we suppose that in userspace we receive only <NA> for empty PT_CHARBUF params.
Does this PR introduce a user-facing change?:
fix(libsinsp): retrieve the correct `exepath` with `execveat` syscall

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for this fix @Andreagit97! I tested it and the exepath is correct for the example program I posted in #543.
We look forward to seeing it merged soon!

LGTM label has been added.  Git tree hash: 5e0e74ec85bc056c7a29bbf2af8d2817d8893d9a

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

I've just rebased to have the CI working again! :)

LGTM label has been added.  Git tree hash: d8a52fafd9a4f3a85996a9da44593a86ddeee222

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


IEEE-695 (MUFOM) Binary Format Loader

Adds support for loading the binary format for IEEE-695 (MUFOM)
The ASCII format is defined in IEEE Std 695-1990 "IEEE Standard for Microprocessor Universal Format for Object Modules"
I found various datasheets with a description of the binary format

i960 Processor Software Utilities User’s Guide
S5U1C88000C Manual I (Integrated Tool Package for S1C88 Family)

ieee was dropped from binutils after 2.30 looks like

Works for a fairly large PowePC image, still looking at finding other samples, specially different architectures.
The debug information section is disabled ATM, definitely the most complex portion.

Please do a
sed -i -e "s:→:->:g" -e "s:“:\":g" -e "s:”:\":g" Ghidra/Features/Base/src/main/java/ghidra/app/util/bin/format/mufom/MufomHeader.java
to fix build issues like "error: unmappable character (0xE2) for encoding US-ASCII"

Execution failed for task ':Base:ip'.

No IP found for /tmp/ghidra/Ghidra/Features/Base/src/main/java/ghidra/app/util/opinion/MufomLoader.java in module: /tmp/ghidra/Ghidra/Features/Base. Expression: (ip != null). Values: ip = null


DRAFT: Refactor reflection helpers.

@brendt - Are you good with this general direction before I proceed?

Yes, for sure! As I mentioned in the other PR though: I'd like to avoid huge PRs at this stage. So if possible, let's merge this ASAP (just the namespace move and composer setup), and then do whatever finetuning you want in another PR

I'll merge this after #377.

@aidan-casey #377 is merged :)

Closing in favor of #382 😛


Errror on Container tag()

Larastan Version: v0.5.2
--level used: max

Description
Illuminate\Contracts\Container\Container::tag() expects array<int,
mixed>, string given.
Laravel code where the issue was found
$this->app->tag([App\Game\GameModule\KyGame::class], GameIF::class);

Hi,
I think this can be fixed in the Laravel repo by making the actual parameter $tags variadic in the method definition.
Also, you can try to open an issue in PHPStan repo. Maybe PHPStan can read that the variable is variadic from the phpdocs.


VRAM Viewer: Print value of pixel under cursor

Because the gametank has multiple different values that map to the same color under rendering, the VRAM viewer's visual output is not sufficient to fully differentiate grayscale pixels :(

oops i thought this was a PR and got excited but yes good idea
Actually the VRAM Viewer has been in need of an overhaul for a while. The Sprite RAM pages don't really represent the continuity within each page since each bank is represented as a 1x4 column instead of their true 2x2 layout. It's also the last debug window that's not using dear imgui at all.
Besides printing the value under the cursor it'd be good to add zooming in on each one, and indicating the active quadrant of the active bank.


Add Branch essential functions

add generate short url function
add get standard events function
add send branch event function
add disable tracking function
add setIdentity function
add logout function

Code looks good.  Doing a bit more testing then I'll approve and merge.


Camera Process + Mic Process sensor payloads exceed HA state limit

We need to refactor them to be an attribute, because HA limits state values to 255 characters and it's preventing us from getting all the apps using the mic. Attributes do not have that limit.
Suggestion:
main state: on/off (if count > 0)
processes (attribute): "string,of,processes,like,before"
I have many virtual mics enabled, so the payload looks like this:
C:#Program Files (x86)#Creative#Shared Files#CTAudSvc.exe,C:#Program Files (x86)#VB#Voicemeeter#voicemeeterpro.exe,C:#Program Files#NVIDIA Corporation#NVIDIA Broadcast#NvVirtualCamera#NVIDIA Broadcast.exe

None of the above actually count as me being in a meeting - those items are on all the time.
When I enter a Discord call, the MQTT payload has Discord, but HA never changes state due to the max 255 character error:
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/mqtt/client.py", line 661, in _mqtt_handle_message
    self._mqtt_data.state_write_requests.process_write_state_requests()
  File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 251, in process_write_state_requests
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 533, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 647, in _async_write_ha_state
    self.hass.states.async_set(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1463, in async_set
    state = State(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1124, in __init__
    raise InvalidStateError(
homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity ID: sensor.bebop_mic_process. State max length is 255 characters.

Nvidia broadcast being on all the time was what convinced me to try my hand at creating this sensor and submitting the PR. I'm not well versed in C#, but I'll try to adjust it, or adding the processes to attributes on the original mic sensor.


New docker image has no conda installed, fix km_s3 script

The change to a new Dockerbase image from this commit https://github.com/kappazeta/km_predict/commit/d72d533fdcba97a578295c6c13590ff1541354b7 breaks the script km_s3.sh as it used conda before. Conda is no longer available.
This PR executes python3 directly and does not require the conda version of python.
This fixes #26

Sorry, I missed it. The pull request looks good.
Thank you for the contribution!

@indrek-sunter Thank you very much!

@indrek-sunter Thanks for merging in and hope this helps. I was wondering if the docker images on docker hub will also get updated automatically? Thanks again

@thierryweo Docker builds are currently manual. I pushed kappazeta/kappamask:v2.2.
Can you check if it works any better?
Also, I noticed that the km_predict version did not match that of the Docker image. I increased km_predict version to 2.2.0.

@indrek-sunter Hi there,
So it seems that the latest fixes did not work really. There is some path problems that i tried to fix in the s3script. the /data directory is not used everywhere. I can fix that. However when i continue to run it the inference seems to start fine but then i get an error as follows:
`
Trainable params: 24552174 (93.66 MB)
Non-trainable params: 49504 (193.38 KB)

/opt/conda/envs/py311a/lib/python3.11/site-packages/rasterio/init.py:304: NotGeoreferencedWarning: Dataset has no geotransform, gcps, or rpcs. The identity matrix will be returned.
dataset = DatasetReader(path, driver=driver, sharing=sharing, **kwargs)
Traceback (most recent call last):
File "/home/km_predict/km_predict.py", line 437, in
main()
File "/home/km_predict/km_predict.py", line 434, in main
kmf.mosaic()
File "/home/km_predict/km_predict.py", line 383, in mosaic
tif_img.save(tif_name, tiffinfo=tif_img.tag)
File "/opt/conda/envs/py311a/lib/python3.11/site-packages/PIL/Image.py", line 2459, in save
save_handler(self, fp, filename)
File "/opt/conda/envs/py311a/lib/python3.11/site-packages/PIL/TiffImagePlugin.py", line 1888, in _save
offset = ifd.save(fp)
^^^^^^^^^^^^
File "/opt/conda/envs/py311a/lib/python3.11/site-packages/PIL/TiffImagePlugin.py", line 976, in save
result = self.tobytes(offset)
^^^^^^^^^^^^^^^^^^^^
File "/opt/conda/envs/py311a/lib/python3.11/site-packages/PIL/TiffImagePlugin.py", line 950, in tobytes
raise NotImplementedError(msg)
NotImplementedError: multistrip support not yet implemented
`
I tried to install a few dependencies mentionned on the PILLOW project site but this does not seem to have any effect.
I reverted back to the v2.0 for now which works fine.  On another site sometimes there are Sentinel products that are not found on sentinelhub and so the download fails, is there any where i can resolve this problem?
But thanks so nothing urgent on my side for now

Oh .. I will look into the remaining issues with the data directory and Pillow later.
While there shouldn't be significant differences in functionality between v2.0 and v2.2, both have issues with semi-transparent cloud class and S2 products starting from 2022. We would like to get both issues resolved for v2.3.
https://github.com/kappazeta/km_predict/issues/28

@thierryweo
Currently it uses products from AWS S3 buckets of Sinergise:
https://registry.opendata.aws/sentinel-2/
They state that "New Sentinel data are added regularly, usually within few hours after they are available on Copernicus OpenHub."
However, you could add your own scripts to the Docker base image which would also check for availability from other sources.

@thierryweo We pushed v2.3 which should also resolve the issue with semi-transparent cloud class on S2 products from 2022 and onward. The Pillow version was downgraded from 10.2.0 to 10.1.0. km_s3.sh should now use /data.

@indrek-sunter Wow thanks. Okay downgrading pillow helped. Thanks for pushing a new image I will try it out this week and also thanks for making me aware of the semi-transparent cloud issue.
Thank you for the help and work. Much appreciated


JSONPath Plus Remote Code Execution (RCE) Vulnerability

jsonpath-plus  <10.0.0
Severity: critical
JSONPath Plus Remote Code Execution (RCE) Vulnerability - https://github.com/advisories/GHSA-pppg-cpfq-h7wr
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/jsonpath-plus
  redis-om  >=0.4.0-beta.1
  Depends on vulnerable versions of jsonpath-plus
  node_modules/redis-om

2 critical severity vulnerabilities

I also encountered this issue. It caused the CI/CD pipeline to fail and blocked my work.
I have created a pull request to fix it: https://github.com/redis/redis-om-node/pull/249.
@guyroyse Could you please review and approve it? That way we can continue working. Thanks!

PR #249 from @dongshunyao has been merge and I pushed the new version to NPM. Y'all should be good to go.

Let me know if you run into any problems. Thanks again!


GetColumnNames() 64 char limit

Hi,
I am currently using the GetColumnNames() and it works great except for the fact that there is a char limit on the string it returns of 64. Is there a way I can make that limit a lot higher or set it to unlimited?
Kind regards,
RandomUniquename

@paulyoder could you maybe delete my name from your last post now? I think I have waited long enough for it. ;) Also this issue can be closed as its not relevant anymore.

@RandomUniqueName done! :-)

(Don' forget to delete the previous edit version please.)

Thanks! You still forgot to delete the edit history. ;)

(Don' forget to delete the previous edit version please.)

Thanks! You still forgot to delete the edit histories though. ;) You can open them and then hit delete.

On another note, nice to see we still had some courtesies like in mail on GitHub back in good old 2014. :smile:

Thanks! On another note, nice to see we still had some courtesies like in mail on GitHub back in good old 2014. :smile:


Start using @prisma/lens

To my naÏve eyes, everything looks in order, but please verify!

same Q as the one in /blog, otherwise LGTM!

Answered! https://github.com/prisma/prisma-blog/pull/199#discussion_r598667685
Does that make sense?


Work on render nodes: Blur passes, tone mapping and final post-processing nodes

Contains

refactoring/cleanup/documentation for ToneMappingNode
split BlurPassesNode into two instance of LateBlurNode
refactoring/documentation for FinalPostProcessingNode

How to test

Run terasology
Create a new game or open an existing one
Verify there are no changes to the rendering

Uh oh, something went wrong with the build. Need to check on that

Uh oh, something went wrong with the build. Need to check on that

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

I don't see any conflicts on this, so I figure it is ready just hoping for a bit of review :-)
Pinging @tdgunes @indianajohn @Avalancs for good measure.

Thanks @Avalancs!

@Cervator: I'm tempted to wait the whole weekend to give the chance to @indianajohn and/or @tdgunes to review this PR, but the changes are not huge and given at least one person has reviewed them I'd also be happy for this to be merged sooner rather than later. A following PR is almost ready.

I did my standard set of tests here (Macbook Air, Windows 10 with & without Vive) and everything functions as before. I also skimmed through each of the affected files and can see a reason for all of the changes. Almost the same line count with more documentation is always a plus.
Anyway, it looks like you're getting pretty close to finished with your refactor, congrats.
Thumbs up on the PR.

Thanks @indianajohn! Regarding the refactoring: I wish. As I refactored the nodes I progressively learned new tricks or simply understood some things better. As such I'll do another (shorter) round of refactoring to apply the new knowledge to the nodes, especially the earlier ones.
I also want to simplify FBO management and with that I should be able to address the bugs occurring during resizing. After that I intend to remove the ShaderParameters classes and put their code into the nodes. That would be the end of the near-future foreseeable node refactoring.
Medium term I'll also have to descend into the depths of shaderland and overhaul the visual debugging system. Meanwhile I hope a GSOC student will pickup where tdgunes left and will complete the transition from a list-based renderer to a graph-based one. :crossed_fingers:
In any case: @Cervator, let's go ahead and merge this when you have a moment.

Scanned through code which looked reasonable and tried it out and it seemed fine: I merged it.

Thanks @flo!

Thanks for the review @tdgunes! How is England treating you?
It's tons of work + 🍺 + ☕ with milk of course 😄


fixed - css libraries importing order

This PR fixes the order of css libraries (Bourbon and Neat) that should be before the base files.

Hi @renancouto thanks for your PR.
What you are trying to fix here? Accordingly to the README on the 5. at installation section we need to

And import Neat after Bitters in your application.css.scss or main manifest file:
@import "bourbon";
@import "base/base";
@import "neat";

And we already uncomment the file mentioned here.

Hey @maurogeorge, this PR doesn't fix anything. I was having a problem on another project and thought that might be the cause. Sorry about that.
Anyways, I think this type of files (a bunch of mixins that doesn't generate any styles by themselves) should be grouped together or even be moved on to another file (ex. _shared.scss). This way other files, instead of the main one, could import it and benefit from its libraries too. What do you think?

@renancouto I see. I think the better way is to fix the problem in the other project and if the solution is a good one to all new projects we add this on pah. Makes sense?
In fact the bitters generate styles, a base style and it is recommended to the people to edit the base/base files and add new ones accordingly to the need.
I think we can close this PR, makes sense?

Great @maurogeorge! Sure, let's see how this evolves.

:+1:


[Suggestion] Add "Copy Unit position" to the "MoveUnit" Element

Hello, I have started to use the editor few weeks ago and was playing with the MoveUnit Element and noticed that there was no option to copy the position of a unit on the map to the "Translate End Position" of the element. This is why I would like to ask if you could add such an option to this element so it is easier to move objects to a precise point.
Thanks for taking this in consideration.

Added, forgot to close


[CVE-2022-40897] pypa/setuptools vulnerable to Regular Expression Denial of Service

Overview
CVE-2022-40897 - Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page.
CVSS
Base: 7.5 HIGH Trivy list this as high in the pipeline but there isnt a score yet.
Description
Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py..

Can maybe set docker build to use pull or no-cache but not sure

sigh reading comprehension is a skill sigh
since this is a python package added it to the requirements.txt file.
Will see if that fixes it

so for now not using the multistage builds. It just adds double every time a vulnerability comes out. Ideally would probably need to setup separate containers in separate repos to be able to keep them up to date for multistage builds.


Remove need for Vec on events

What
Change topic list from Vec to tuple. Also add some docs.
Why
To remove one case of surfacing EnvVal in the SDK API.

@leighmcculloch Thank you for making this follow up change. I was also working up a solution yesterday but didn't finish before the end of day: https://github.com/stellar/rs-soroban-sdk/pull/469/files. It is pretty similar to what you have, except I made a trait and impl'ed on those tuples, such that you don't need the publish_n functions. I also added a couple of validity checks on each of the topic.
I'm good with either approach. So feel free to keep either one. I've marked the other one in draft as I still have a thing to fix and it depends on some light change on the env crate.

Closing in favor of #469.


Port match for listening IPv6 address fails

A simple port test (postgres in this case)
root@postgres-01:/etc/goss# cat goss.yaml
port:
  tcp6:5432:
    listening: true
    ip:
      - 2001:db8:ff:842:5054:ff:fe12:f0d8
  tcp:5432:
    listening: true
    ip:
      - <IP_ADDRESS>

against the following IPv6 address
root@postgres-01:/etc/goss# ip -6 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 2001:db8:ff:842:5054:ff:fe12:f0d8/64 scope global mngtmpaddr dynamic
       valid_lft 3598sec preferred_lft 598sec
    inet6 fe80::5054:ff:fe12:f0d8/64 scope link
       valid_lft forever preferred_lft forever

seems to match against a garbled address.
root@postgres-01:/etc/goss#  goss --gossfile /etc/goss/goss.yaml validate -f tap
1..4
ok 1 - Port: tcp6:5432: listening: matches expectation: [true]
not ok 2 - Port: tcp6:5432: ip: doesn't match, expect: [["2001:db8:ff:842:5054:ff:fe12:f0d8"]] found: [["0470:0120:0842:006F:00FF:5054:F0D8:FE12"]]
ok 3 - Port: tcp:5432: listening: matches expectation: [true]
ok 4 - Port: tcp:5432: ip: matches expectation: [["<IP_ADDRESS>"]]

Looks like a problem with the stringification of the IPv6 address used in the match (the byte order representation of localaddress in /proc/net/tcp6 appears to be of different than that represented by tools?)
root@postgres-01:/etc/goss# goss --version
goss version v0.1.5

root@postgres-01:/etc/goss# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (stretch)
Release:        testing
Codename:       stretch
root@postgres-01:/etc/goss# uname -r
4.3.0-1-amd64

This appears to be a problem in adding the port as well.
root@postgres-01:/etc/goss# goss add port tcp6:5432
Adding Port to './goss.yaml':

tcp6:5432:
  listening: true
  ip:
  - 0DB8:0120:0842:00FF:00FF:5054:F0D8:FE12

What does netstat show?

It does appear that go-netstat is not working properly, thanks for filing this.

Had some time to track down the issue and test out a fix locally, hoping to have a fix released sometime later this week. Sorry for the delay.

Ohh, I wasn't expecting so much - thank you though .. the tool is flexible enough to fall back to commands that I've got a temporary workaround until you put out a fix. I do really appreciate your time on this and the other issues. And for such an invaluable tool - it's just a massive time saver!

Fixed in v0.1.6. Let me know if you run into any more issues.


handle Mixin expressions

I see you started with a test. That's good.

yeah this time I started with a test because this feature is quite intrusive.

it was good advice to test related stuff...
I found a bug in how switches are handled...

Yes, I like this test much better :)

@deadalnix do you approve of the test.

ok I addressed the stuff you ponted out.


update name of project

Preview is available here:http://amm-demo-pr21.previews.kube001.services.stellar-ops.com/


Quick question about Firebase-list.js

Hope you don't mind me asking via this means, but I have a very quick question about the firebase-list.js class used in https://github.com/r-park/todo-react-redux/blob/master/src/core/firebase/firebase-list.js
I've spent hours studying this code and inserting lots of console logs to track the flow / sequence of events.. I can not wrap my mind around how ref.once function one line 52 is working.
How do you get it to wait until the all the ref.on('child_added' events occur before the .once function emits the list?
I don't see any explicit sequencing here, so I can not figure it out.  It appears that events happen in this order:

Action starts the subscription.
list is initialized as empty array.
the .on('value') function fires.. and loads all the items from the ref into the list.
the .once function then sets initialized to true and emits the list.

How in the world is the .once function waiting until all the .on('value') process is complete? And do I read this correctly that the .once() is not actually utilizing the data it grabs because there is no snapshot being passed to the callback / no unwrapping?
Can anyone help me understand?

Hi @jakelowen
angularfire takes care of it for us :)
From the docs:

The value event is used to read a static snapshot of the contents at a given database path, as they existed at the time of the read event. It is triggered once with the initial data and again every time the data changes.

The implementation in firebase-list.js is just an example to show how you can use the value callback to wait until the initial data has loaded.

Thanks @r-park - Thank you, I think I'm with you.
In this code snippet (directly from firebase-list.js)
ref.once('value', () => {
      initialized = true;
      emit(this._actions.onLoad(list));
    });

    ref.on('child_added', snapshot => {
      if (initialized) {
        emit(this._actions.onAdd(this.unwrapSnapshot(snapshot)));
      }
      else {
        list.push(this.unwrapSnapshot(snapshot));
      }
    });

Are both ref.once('value'.... AND ref.on('child_added'.. both separate database reads that are happening simultaneously?  So if there are 3 children at that path, I am actually downloading the 3 children twice (total of 6 records), but because .once is not reading the snapshot it is essentially throwing away the data collected and thus only being used as a timer mechanism to emit the list (presumably after the .on('child_added') is also done populating the list?
Could I theoretically avoid the ref.once('value'.... call altogether by expanding the  ref.on('child_added'.. section to something like: (pseudocode, untested):
     ref.on('child_added')
      .then(snapshot => {
        if (initialized) {
          emit(this._actions.onAdd(this.unwrapSnapshot(snapshot)));
        } else {
          initialized = true;
          emit(this._actions.onLoad(this.unwrapSnapshot(snapshot));
        }
      })

Or is the ref.once('value'....  playing some special role that I am failing to grasp?

Oh, I see. My above rewritten code only grabs the first item from child_added into onLoad. All subsequent children on initial read are put into onAdd. So I need a way to wait for all children before I dispatch to onLoad. That must be what your .once function was doing.

If you're only going to use child_added, the initialized flag is probably unnecessary, unless you want to know when the first item has been loaded.
You can simplify it to something like this:
//let initialized = false;
//let list = [];

/*
ref.once('value', () => {
  initialized = true;
  emit(this._actions.onLoad(list));
});
*/

ref.on('child_added', snapshot => {
  emit(this._actions.onAdd(this.unwrapSnapshot(snapshot)));
}

Keep in mind that this._actions.onAdd() will trigger a view update each time it's fired.

That must be what your .once function was doing.

👍

Thank you @r-park - I follow now. Kudos on an extremely well written code example. I don't think I could have cracked firebase with redux had it not been for you.
For future reference to other future searchers.., this SO question addresses why this approach of both a .once and a .on('child_added') work well together: http://stackoverflow.com/questions/27978078/how-to-separate-initial-data-load-from-incremental-children-with-firebase?noredirect=1&lq=1


[DOC] The image not present under the heading "Quick Start".

Documentation issue
The image is not present in the read.MD file under the heading "Quick Start".

Describe the thing to improve
An image of the landing page of the website present at localhost:3000 can be used as the image.
Describe the solution (optional)
No response

Hey @FidalMathew ,
Thank you for contacting us! We've fixed ⚡


Type representing money values

Problem description
Currently amounts of money are defined as:
        amount:
          type: number
          format: float
          multipleOf: 0.01

Swafgger docs indicates

multipleOf may be used with floating-point numbers, but in practice this can be unreliable due to the limited precision or floating point math.

Possible evolution

Storing amount values as long integers is a common best practice

Field Name
OpenAPI type
OpenAPI format
Description

amount
integer
int64
Represented in "minor units"

currency
string
currency
"Minor units" depend on the currency value.

Note: Minor units are specified according to ISO 4217 and can be found in this table.
Additional context
Recommendation in:
https://github.com/team-monite/api-style-guide/blob/main/Guidelines.md#should-use-the-common-money-object

Storing amount values as long integers is a common best practice, adopted by API payment providers like Adyen and Stripe.

Most currencies have two decimals. Some currencies do not have decimals, and some have three decimals. For example:

GBP 10: GBP has two decimals, so in minor units submit an amount of 1000
JPY 10: JPY has no decimals, so in minor units submit an amount of 10
BHD 10: BHD has three decimals, so in minor units submit an amount of 10000

25/10: Moving forward with
        amount:
          type: number
          format: float
          multipleOf: 0.001

Closed as per PR#19 MERGED


The witcher's sheet changes

localization of the HP attribute showed on The Witcher TRPG's character sheet.
some spelling corrections and changes in pt-pt translation to improve the layout.

Hello! Your Pull Request includes changes to translation files. We will not deny your Pull Request, but we would prefer sheet contributors use Crowdin for translations. Please email Cassie at<EMAIL_ADDRESS>and she will get you an invite to our Crowdin within 48 hours. Be sure to include the languages you would like to translate, and please use Crowdin for future translation updates! Thanks for all you do!

Hi,
I already translated this file two weeks ago in the translation group, but
I realized that most of the translations there, of several files, are all
pending to be approved for months. So as my original version of this
translation has already been posted by github, I decided to update it in
the same way.
Sorry for this.
Em seg., 27 de jul. de 2020 às 14:20, Olivia Kristiansen <
<EMAIL_ADDRESS>escreveu:

Merged #7034 https://github.com/Roll20/roll20-character-sheets/pull/7034
into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/pull/7034#event-3590863849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE6ILITJ6IBVE2T5QQZ4GELR5WZO5ANCNFSM4PFAZROQ
.

--
Atenciosamente,
Kirlian Silvestre


Ingress gateway does not respect the values.global.proxy.accessLogEncoding argument

Bug description
When installing istio via Helm, if you set global.proxy.accessLogFile=/dev/stdout and global.proxy.accessLogEncoding=JSON, your ingress gateway spits out JSON output.  That's desirable.
However, if you install via istioctl, you do not get JSON output.
If you install via istioctl and then manually patch in accessLogEncoding: JSON just after accessLogFile: "/dev/stdout" with kubectl edit cm istio -n istio-system, and then kick the ingress gateway pod, your desired JSON output returns.
Expected behavior
JSON output from the ingress gateway
Steps to reproduce the bug
Install a cluster with ./bin/istioctl manifest apply --set values.global.proxy.accessLogFile=/dev/stdout --set values.global.proxy.accessLogEncoding=JSON and then get logs from the ingress gateway; they are not JSON-formatted.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl version
client version: 1.4.2
control plane version: 1.4.2
data plane version: 1.4.2 (1 proxies)

How was Istio installed?
Via istioctl (see steps to "reproduce the bug")
Environment where bug was observed (cloud vendor, OS, etc)
GCP and local docker/kubernetes

Will https://github.com/istio/installer/commit/715ec75c7ea4bddd61d3a68c8a8e8ad047987eaa perhaps solve this issue?  I'm a bit perplexed by how the different https://github.com/istio/* projects work together.

Yes, that will fix it so it will be fixed on 1.4.3 so I think there is nothing to do here.

:-( Looks like it missed the 1.4.3 cut-off.  Oh, well.  🤞 for 1.4.4 :-)


SWIMMING MODE

Good afternoon I would like you to implement SWIMMING in this conversion!  Thanks for such codes are great.

I have added swimming as a flag option, so that the exercise type is altered in the resultant TCX, however I can't test this as I don't have a HiTrack file from a swimming activity so don't know what kind of data is available or required. Could you please provide me with a HiTrack file to test with?

Good morning here is the HiTrack file link: https://drive.google.com/file/d/1-8QwfxBRc0T3COX0nC2fSJ5_EjdM7y-X/view?usp=drivesdk
Thanks for the code work very well!  Excited to play the swim data for the Strava

Hello, I did the tests with the new script with codes for swimming and the only data that shows available is the uptime!  It does not show us heart rate, strokes, distance traveled, swolf etc.  Just to report that the only result provided is the uptime in swimming.  And again thanks for the codes

I have re-done the tests and the swimming function is not good!  Measuring only time and nothing else

Hello,
thank you very much for TCX Converter (on github). Your work is great :good:
I have one example of swimming data with real value. You can make easy some change in your converter to get correct data.
Here is original HiTrack file
https://drive.google.com/drive/folders/0B218WnQMXdvwcVFBbGJWcWVwVW8?usp=sharing
Here is report about my swimming
Total value
pool length 25m
time 00:06:04
kcal 58
number of strokes 93
1 - breaststroke
time 00:00:45
swolf 60
number of strokes 15
2 - breaststroke
time 00:00:48
swolf 67
number of strokes 19
3 - backstroke
time 00:00:57
swolf 74
number of strokes 17
4 - backstroke
time 00:02:11 (with pause, play with my new watch :) )
swolf 148
number of strokes 17
5 - free style
time 00:00:36
swolf 48
number of strokes 12
6 - free style
time 00:00:33
swolf 46
number of strokes 13
Thank you
D.Z.

Thanks for the file Dan1967. I had a look at it, but I must admit I can't relate some numbers in the file to the ones in your report.
What I found up till now:
*** it looks like the tp=s-r records could be the lap times for swimming, but they don't match the lap times you're mentioning. E.g. the first lap should have taken 60 seconds according to the file<PHONE_NUMBER>000 -<PHONE_NUMBER>000) whereas your provided data reflect 45 seconds,
*** The SWOLF values can be found 1:1 in the tp=swf records.
*** I can't figure out what the tp=p-f and tp=rs records are, although the latter seem some kind of speed (with no clue to what unit)
Looks like I'll need to go and find a swimming pool myself first to get some extra data...

Huawei developers smoke tooooooo much marijua.. :-)
I try understand swimming hitrack file, compare with Hua Health info...
My opinion, is impossible convert swimming hitrack file to REAL tcx.
Hitrack file is data for Hua health table/graph view, match perfect to hitrack file. But... lot of information is missing. They are stored in the database, maybe.
Hitrack for pool swimming...
s-r - looks like one length, but NO
swf - SWOLF
p-f - number of strokes per minute
r-f - tempo/speed per minute
This data is used ONLY for graph view in Hua Health
No information about laps/pool time, swimming style...
In the end of august I try open water swimming...
ps:
sorry for my english...
ps2 :
Huawei Watch is nice toy... i love it, yes, really. For running, biking, mountain walking...gps, heart rate
But for swimming I have Garmin Swim watch.


Click on  always causes reload

I was able to find that evt.nativeEvent.which in link-factory is 1. Observed in Chrome 44.0.2403.157 and Safari 8.0.8. No idea what causes, what it means, but it prevents the clickHandler from doing its job :).

What is purpose of that condition? If I get it correctly, react-router uses following logic to filter out special clicks:
function isLeftClickEvent(event) {
  return event.button === 0;
}

function isModifiedEvent(event) {
  return !!(event.metaKey || event.altKey || event.ctrlKey || event.shiftKey);
}

Hi @vojtech-dobes: the purpose of this condition is to not prevent default on middle click (so it opens a new tab using the hyperlink href. It works fine for me, I'll run more checks and test RR's logic :smile:

Thanks for quick reply :). Great.

Just released v0.1.4 using RR's logic :D

Awesome sir :).

Please tell me if you have any issue with it!

Nope, works like a charm. No reloads, History API is in action now.

:+1:


Fix error seen when this gem installed but not specified as dependency in project

Related issues

https://github.com/rubygems/rubygems/issues/5289

coverage: 93.95%. remained the same
when pulling dc0b3ce4437f797a095a255595fc6003cacdb939 on fix/rubygems-plugin
into 5b274f82786a97e2ba4012192655c651c627fc40 on master.

Took me a while to get it right
You can install via gem install gem-release -v '2.2.3.alpha4' to test (uninstall all other gem-release versions first I guess

Woohoo!! Thanks to much @PikachuEXE installing '2.2.3.alpha4' resolved this issue for me.

Fix released in https://rubygems.org/gems/gem-release/versions/2.2.3


Turn off VertConv for ocean BGC

Description
Turn off VertConv for ocean BGC. See #590 for issue description. This PR, however, does not fundamentally solve the described problem but rather provide a temporal solution to get pass soca-science ctests.
Tests
soca-science 3dvar_bgc ctest failed travis-ci with VertConv on (built with soca develop branch):
build link
and passed with VertConv off (built with this branch):
build link

@guillaumevernieres Sorry, another quick PR seems to be needed to address the NaN issue... with this update I can finally pass travis-ci.

@guillaumevernieres Sorry, another quick PR seems to be needed to address the NaN issue... with this update I can finally pass travis-ci.

@liuxiao37k , you are the master of your domain, so I'll approve if that's what you really want to do, but could you create a "bug" issue so we remember to fix this in the future?

@guillaumevernieres Sorry, another quick PR seems to be needed to address the NaN issue... with this update I can finally pass travis-ci.

@liuxiao37k , you are the master of your domain, so I'll approve if that's what you really want to do, but could you create a "bug" issue so we remember to fix this in the future?

@guillaumevernieres good suggestion. I edited issue #590 to further describe the problem (i.e. doing vertconv for BGC routinely creates NaN with GNU, but not with Intel) and made a note that this PR only provides a temporal fix to pass ctests. I would definitely want to revisit this issue later. thanks!

@guillaumevernieres and perhaps those hardwired variables would be eventually moved out of the source code so that we can control in .yaml which variables we want to do vertconv with?

@guillaumevernieres and perhaps those hardwired variables would be eventually moved out of the source code so that we can control in .yaml which variables we want to do vertconv with?

@liuxiao37k  If you are using "SocaError" as your covariance model, it is only 2D, so all 3D variable would require VertConv to make it 3D. Your var is going to be wrong without fixing that bug. We're not using BGC yet, so I'm open to making the test wrong, but considering that you've cornered the bug down to VertConv, why not just fix it? Is your issue not being able to replicate the bug on Hera or Orion?

@guillaumevernieres and perhaps those hardwired variables would be eventually moved out of the source code so that we can control in .yaml which variables we want to do vertconv with?

@liuxiao37k If you are using "SocaError" as your covariance model, it is only 2D, so all 3D variable would require VertConv to make it 3D. Your var is going to be wrong without fixing that bug. We're not using BGC yet, so I'm open to making the test wrong, but considering that you've cornered the bug down to VertConv, why not just fix it? Is your issue not being able to replicate the bug on Hera or Orion?
To answer your question: Yes, at some point will will revamp our change of variables to make the input/output variables choice more flexible.

Oh sure, it would be great that we can fix that issue (although for BGC only 2D surface analysis is taken and the 3D field analysis will be generated based on 2D analysis as well as background vertical distributions in .py scripts). My issue is that I don't know how to fix it, so any help is appreciated.
See the travis-ci tests with VertConv on (link):
RPCG Starting Iteration 1
5712RPCG alpha = 0.308053
5713RPCG end of iteration 1
5714  Gradient reduction ( 1) = 8.580603313088303e+116
5715  Norm reduction ( 1) = 4.992094945483949e+115
5716
5717RPCG Starting Iteration 2
5718RPCG beta =<PHONE_NUMBER>472639760087050174335677991176518254049227003286194533401360503603853900768268093544002868597683434253837222602388600014375149021378707176141394844113498325795685241184060631142095127104574060169490256621299025338370621440.000000
5719RPCG alpha = -nan
5720RPCG end of iteration 2
5721  Gradient reduction ( 2) = -nan
5722  Norm reduction ( 2) = -nan

and with VertConv off (link)
I cannot replicate this issue on Hera (haven't figured out an GNU option) and having login issue on Orion, but with Hera Intel I encountered similar NaN problems many times with the 1deg tests.

Hi @guillaumevernieres, as we discussed last week, ocean BGC DA is done at a 2D space so it does not make a lot sense to do VertConv, so we decided to proceed with this PR. Before you merge, can you please check again what I have done (long time ago) with GetValues to make sure that I did not mess up the BGC states' dimensions? thank you!

@guillaumevernieres thanks and I fully understand your point. I'll keep it in mind that we should revisit this issue.

@guillaumevernieres never mind what @liuxiao37k2 said. It was me forgetting to switch account. hmmm... I thought soca is a private repository...


[MINOR] Rename Pig tutorial note to consider priority

What is this PR for?
After #1830 merged, Pig tutorial note placed as a first under Zeppelin Tutorial folder. I told to @zjffdu, I thought the note name should be same with Spark ("Basic Feature (Spark)") in this comment (because they have same contents).

But considering the number of Spark and Pig users, the Spark tutorial note needs to be placed as first I think.

What type of PR is it?
Rename Pig tutorial note
What is the Jira issue?
N/A
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

@zjffdu Sorry for the confusion. If you don't mind, could you take a look into this?

LGTM

Let's merge it now. :-)

Yup merge into both master and branch-0.7 if there are no more comments


In ashe.py missed the 10 percentile

A fill right didn't catch the 10 for some reason.
Bug in documentation, or bug in excel_ref or something else?

Fill is exclusive.
On Mon, 9 Feb 2015 14:11 Francis Irving<EMAIL_ADDRESS>wrote:

A fill right didn't catch the 10 for some reason.
Bug in documentation, or bug in excel_ref or something else?
—
Reply to this email directly or view it on GitHub
https://github.com/scraperwiki/xypath/issues/72.


How import makerjs model?

How import makerjs model? Give an example, please.

Look at the demo  https://github.com/onlfait/svg-blueprint/blob/master/demo/index.js#L15


Setup for releases to maven central

Added configuration to POM files to enable relase of the LicenseScout to Maven central
Type of request

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Refactoring
[x] Documentation or documentation changes

Related Issue(s)

Precondition for #22
Concept
Adding configuration to POM files to enable release including source and Javadoc build, signing and staging.

Description of the change

Description of current state
No release of LicenseScout to Maven central
Description of target state
Estimated investment / approximate investment

Initiator
Matthias Pfisterer
Technical information
Platform / target area

known side-effects
other
DB Changes (if so: incl. scripts with definitions and testdata)
How has this Tested?
Doing the release as described in the maintainer documentation.
Check if artifacts are actually available on Maven central.

Screenshots, Uploads, other documents (if appropriate):

Checklist:

[x] All the commits are signed.
[x] My code follows the code style of this project.
[x] I agree with die CLA.
[x] I have read the CONTRIBUTING docs.
[x] I have added/updated necessary documentation (if appropriate).

Please resolve conflicts in pom file. Then i'll review. Thanks


⚠ Bofrost.de has degraded performance

In 2eeaa7e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 875 ms

Resolved: Bofrost.de performance has improved in 2ce21f9 after 6 minutes.


Test fails because of missing property of a button, neither the test or the component being tested has any buttons...

Error:
ErrorComponent
ERROR: 'NG0303: Can't bind to 'mat-dialog-close' since it isn't a known property of 'button'.'
Chrome 88.0.4324.150 (Windows 10): Executed 27 of 210 SUCCESS (0 secs / 0.92 secs)
ERROR: 'NG0303: Can't bind to 'mat-dialog-close' since it isn't a known property of 'button'.'
ERROR: 'NG0303: Can't bind to 'mat-dialog-close' since it isn't a known property of 'button'.'
Chrome 88.0.4324.150 (Windows 10): Executed 27 of 210 SUCCESS (0 secs / 0.92 secs)
ERROR: 'NG0303: Can't bind to 'mat-dialog-close' since it isn't a known property of 'button'.'
Chrome 88.0.4324.150 (Windows 10): Executed 28 of 210 SUCCESS (0 secs / 0.95 secs)

My spec file:
import { ComponentFixture, TestBed, waitForAsync } from '@angular/core/testing';
import { ErrorComponent } from './error.component';

describe('ErrorComponent', () => {
  let component: ErrorComponent;
  let fixture: ComponentFixture<ErrorComponent>;

  beforeEach(waitForAsync(() => {
    TestBed.configureTestingModule({
      declarations: [ErrorComponent]
    }).compileComponents();
  }));

  beforeEach(() => {
    fixture = TestBed.createComponent(ErrorComponent);
    component = fixture.componentInstance;
    fixture.detectChanges();
  });

  it('should create', () => {
    expect(component).toBeTruthy();
  });
});

ts-file:
import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-error',
  templateUrl: './error.component.html',
  styleUrls: ['./error.component.css']
})
export class ErrorComponent implements OnInit {

  constructor() { }

  ngOnInit() {
  }

}

html-file:
<p>
  error works!
</p>

Why do i get an error about "mat-dialog-close" and "button" here?
Neither the ts-file, the html-file or the spec-file mentions "mat-dialog-close" or "button" ? 🤔

Thank you for reporting this issue, but it is specific to your application code and is not related to Karma.
Please use StackOverflow for questions and support in the future as we want to keep the issue tracker for bug reports and feature requests.
Looks like mat-dialog-close is used somewhere in the component tree and you forgot to add the module declaring it to the TestBed.configureTestingModule() call.


New rule: no-disallowed-property-values

NOTE: I haven't done the DCO/Emoji stuff yet because I'm not sure if this is a desirable addition. If it is, I'll be happy to make any additional changes necessary to merge.
What do the changes you have made achieve?
This should allow blacklisting certain property values, in contrast to no-disallowed-properties which blacklists the property names. For example, this allows banning text-transform: capitalize while allowing other uses of text-transform.
Are there any new warning messages?
Just the ones from the lint rule.
Have you written tests?
I have added tests based off the tests for no-disallowed-properties.
Have you included relevant documentation
I have added a new doc in docs/rules/no-disallowed-property-values.md
Which issues does this resolve?
No open issues that I found.
<DCO 1.1 Signed-off-by: Isaac Wolkerstorfer<EMAIL_ADDRESS>

Coverage decreased (-0.1%) to 97.419% when pulling 18ff8824e3ccfb2a9cdc7c4cd9d9e5d93dc1cbc7 on Asana:no-disallowed-property-values into deabaf663ccd268f8a979ccd4ca995123145d1af on sasstools:develop.

closes #1019

Coverage decreased (-0.06%) to 97.463% when pulling 116a4d08901dbf53235b48202eb2404376bd4d13 on Asana:no-disallowed-property-values into 241e5a01eed1e15116f721792afb7fa1e6d28318 on sasstools:develop.

Great comments! Updated the docs and tests for those cases - I think we actually don't need the "array with one value" case if we're testing "array with two values" and "single string value"?

Hi @agnoster it would be good to include both. so single value as a string, single and multiple values in an array. It makes sense to test all the allowed cases like this just so we cover all cases. If you wouldn't mind just adding that case too then we could get this merged 👍

Ah, fair enough, good reasoning! Done :-D

Coverage decreased (-0.06%) to 97.463% when pulling cdce791c5732e1c230811ca9c0dfe7d2c293a8c3 on Asana:no-disallowed-property-values into 241e5a01eed1e15116f721792afb7fa1e6d28318 on sasstools:develop.

What's the status of this PR? I'm hoping to use this rule in a project.
Also, is there any plan to support blacklisting values that are strings? I noticed that if a property value is set to a string, ast.traverseByType('value', function (valueNode, idx, parent) { will not pick it up. String values have a node type of 'string'. And will there be any support for blacklisting values that are resolved through a variable?

Looks like it got approved but never merged?

Sorry, our develop branch is now work for v2 and I just haven't had time to go back through everything and merge it all. I will hopefully in the next few days and release this. It will be part of our v2 update though which just removed the eslint dependencies etc.

Coverage decreased (-0.06%) to 97.572% when pulling 16407a6de3eb832e3f8f25c23abc697119a640ac on Asana:no-disallowed-property-values into fad4e51e07b43f4f857895785dd3ece0f2363e75 on sasstools:develop.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix Win 10 timing issue

https://github.com/ashupp/SFX-100-Timerfix/blob/main/SFX-100-Timerfix.cs

Fixed in revision #98


ModuleNotFoundError: No module named 'passlib.handlers.phpass'

Error:
Traceback (most recent call last):   File "C:\Users\STEELH~1\Desktop\pthon\CALLOF~1\BOT2~1.DIS\bot2.py", line 26, in <module>   File "C:\Users\STEELH~1\Desktop\pthon\CALLOF~1\BOT2~1.DIS\passlib\registry.py", line 43, in __getattr__   File "C:\Users\STEELH~1\Desktop\pthon\CALLOF~1\BOT2~1.DIS\passlib\registry.py", line 352, in get_crypt_handler ModuleNotFoundError: No module named 'passlib.handlers.phpass'
This was how I ran nuitka:
py -m nuitka --standalone bot2.py --enable-plugin=tk-inter

In the template, I have made it clear, that not filling out the issue template is not acceptable. I am closing this kind of report as invalid. The main reason is that I do not want to be left guessing. For you it's easy to erase the issue template and expect me to ask you questions only as necessary, but I cannot do that. I would much rather wait for you to create a new report, fill out the template, or wait for somebody with the necessary skill to do it.
In short: No issue template, no fun. Therefore I am likely just deleting the issue, as it serves as a bad example and detraction for searches.  And even worse, it might keep good reporters from reporting as is this "already known."


deadLetterQueue not working

Hello I tried to access deadLetterQueue using java api but its throwing null pointer exception.
ServiceBusContract service = ServiceBusService.create(config);
..
..
..
ReceiveMessageOptions RECEIVE_AND_DELETE_60_SECONDS = new ReceiveMessageOptions().setReceiveAndDelete().setTimeout(60);
ReceiveQueueMessageResult resultQM = service.receiveQueueMessage("queueName/$DeadLetterQueue",RECEIVE_AND_DELETE_60_SECONDS);
Please let me know how to do it if possible.

the ServiceBus SDK is here: https://github.com/azure/azure-service-bus-java


Redesign Header of website

Hey ,I would like to contribute by redesigning the header section of this website.

2024-SANDHYA I would like to work on this please assign it to me

Hey ,I would like to contribute by redesigning the header section of this website.

No changes are required in the header. @shefali12-ab  Thank you :)


Overhaul of storage account art defs

I think these changes are important, as it simplifies what the artifacts will look like for varying storage account types, but they'll ultimately output the same format of an artifact and rely on RBAC for authentication.
I also think renaming the current file to azure-storage-account-blob.json will further restrict potential connections that will be expecting a blob type of storage account and not a queue or data lake.

There are a few breaking changes in here. Do we have anybody provisioning with bundles that use this currently?

I'll check w/ Chris.


No console + Windows 10 + Shortcut = Similar to launching app or game

Great Job guys :)
As of now, I unable to create windows shorcut. Please make it with windows shortcut, so it is easy to use from talk bar icon as other windows app. Thanks :0

https://github.com/Genymobile/scrcpy/issues/2159#issuecomment-801898530 ?

right-click scrcpy-noconsole.vbs -> send to -> Desktop (create shortcut)

#2159 (comment) ?

It works as expected after followed your steps. Thanks to the team :)


docs(contributing): fix broken url for github pull request

The old url gets you to a 404 GitHub page, so I changed it to a properly GitHub pull request documentation.

Thanks for helping!
I don't see why not merge it.


expose prop types

Prop types are not accessible from the library.
It should be easy to expose them, at least with typescript 3.8+.
export { ReactFlow as default } from './container/ReactFlow';
export type { ReactFlowProps } from './container/ReactFlow';
export { default as Handle } from './components/Handle';
export type { HandleProps } from './components/Handle';

etc

Hey. Do you mean the types or the React prop types?

I mean the type of the props of the components.
I have a habit of extending components props, so future consumers could add arguments I did not expect.
This might explain it better: https://blog.bitsrc.io/the-vanilla-and-flavouring-pattern-fcf07942a57a

Released in 6.1.1


check_install_sanity: Use formula.runtime_dependencies

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Fix…
$ brew install wget
Error: wget contains conflicting version recursive dependencies:
openssl<EMAIL_ADDRESS>View these with `brew deps --tree wget`.
$ brew deps --tree wget
wget
├── libidn2
│ └── libunistring
├──<EMAIL_ADDRESS>│ └── perl
│ ├── gdbm
│ ├── berkeley-db
│ └── expat
│ └── libbsd
└── util-linux
└── ncurses

On Linux, libidn2 has no linkage to gettext and so is a :build dependency rather than a run-time dependency. libintl is a header-only and provided by glibc rather than by gettext, as it is on macOS.

In some circumstances, this has broken the check. If I make the node<EMAIL_ADDRESS>option the default, it is still possible to install emscripten despite the recursive dependency on both openssl and<EMAIL_ADDRESS>git bisect led me to 95bf23404ea39a8847b56612c3fef44497daf893.

runtime_dependencies seems to be first level (deps -1) only
irb(main):004:0> :emscripten.f.recursive_dependencies
=> [#<Dependency: "pkg-config" [:build]>, #<Dependency: "sphinx-doc" [:build]>, #<Dependency: "gdbm" []>, #<Dependency: "makedepend" [:build]>, #<Dependency: "openssl" []>, #<Dependency: "readline" []>, #<Dependency: "sqlite" []>, #<Dependency: "python@2" []>, #<Dependency: "cmake" [:build]>, #<Dependency: "icu4c" [:recommended]>, #<Dependency<EMAIL_ADDRESS>[:recommended]>, #<Dependency: "node" []>, #<Dependency: "yuicompressor" []>]
irb(main):005:0> :emscripten.f.runtime_dependencies
=> [#<Dependency: "gdbm" []>, #<Dependency: "openssl" []>, #<Dependency: "readline" []>, #<Dependency: "sqlite" []>, #<Dependency: "python@2" []>, #<Dependency: "node" []>, #<Dependency: "yuicompressor" []>]
irb(main):006:0>

hmm no there's more to it than that. openssl is still indirect.

OK the issue is that runtime_dependencies ignores all optional and recommended dependencies, and only looks at required dependencies. 🐛

CC @sjackman

I've opened https://github.com/Homebrew/brew/issues/4124


Introduce testcontainer based cluster integration tests

Motivation
Introduce testcontainer based cluster tests for replacing existing arquilian tests.
testcontainer is more flexible and more nature to how we write unit tests. arquilian is configuration based and hard to change cluster at runtime.
it is possible to add bookies/brokers/proxies at testing runtime using testcontainers.
current arquilian based integration tests can only run in linux environment (which is using host network). it is impossible to run arquillian tests in mac environment,
where host network is meaningless. changing to testcontainers is allowing running integration tests on mac to speed up development.
Changes
This mirrors the exact same setup as existing arquillian tests - 1 zk container, 1 cs container, 3 bk containers, 2 broker containers and 1 proxy container.
add a semantic integration test module to using the new testcontainer test base PulsarClusterTestBase.
Result

both arquillian and testcontainers exist.
new integration tests are encouraged to be written using PulsarClusterTestBase. It is just as easy as how you write normal unit tests.
existing arquillian tests will be migrated in future PRs.

related issues:
#2036 - is testcontainer based standalone test.

retest this please


Fixed broken table of contents link

Short Description:
Fixes:

Table of contents link did not link to usage
Made the usage steps a normal list as opposed to a code snippet, which was hard to read because it kept getting cut off.

@TheSavior what changes is this waiting on?

does it matter if readme is in dev or master branch?


Open Api Specification

For apis which have a public open api specification, there is additional power given to the developer such as the ability to automatically generate a client, a server, documentation, testing and more. This page has a collection of projects which support the above-mentioned abilities  https://apis.guru/awesome-openapi3/.
I was wondering if people in the list have any interest in adding a column to this list to link the open api specification if it is available. Alternatively, does anyone know of a list which contains links to open api specifications?
Here is an example of an api specification for The Movie DB. https://api.stoplight.io/v1/versions/9WaNJfGpnnQ76opqe/export/oas.json

Hi @lukesmurray , thanks bringing this up. Allowing every entry to link to its preferred documentation was worked well for us for quite some time. I also would feel pretty confident that most entries in this project do not support this specification, so the extra column would be empty more times than not. I'm going to close this issue for now, but please feel welcome to contribute to the project in the future!
Hope you enjoy this xkcd comic regarding "standards" and "specifications" :)
https://xkcd.com/927/


password error and timeout error on the server

Bug Description
I have two apps that are almost exactly the same (same infra, same package versions, same db config code). They are connecting to two different CloudSQL Postgres instances but same PG versions and configurations as far as I can tell in GCP console.
pg-pool is 3.6.1
pg is 8.11.3
cloud-sql-nodejs-connector is 0.5.1
The connection code is:
    const connector = new Connector();
    const clientOpts = await connector.getOptions({
      instanceConnectionName: host,
      ipType: IpAddressTypes.PRIVATE,
      authType: AuthTypes.IAM,
    });

    return new Pool({
      max: maxPoolSize || 5,
      database,
      user,
    });

I've verified db and user are correct in both cases. On the client side, I immediately get this error:
Uncaught Error: SASL: SCRAM-SERVER-FIRST-MESSAGE: client password must be a string
    at /nodejs/app/node_modules/pg-pool/index.js:45:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async PostgresDriver.acquireConnection (/nodejs/app/node_modules/kysely/dist/cjs/dialect/postgres/postgres-driver.js:21:24)
    at async RuntimeDriver.acquireConnection (/nodejs/app/node_modules/kysely/dist/cjs/driver/runtime-driver.js:46:28)
    at async DefaultConnectionProvider.provideConnection (/nodejs/app/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:10:28)
    at async DefaultQueryExecutor.executeQuery (/nodejs/app/node_modules/kysely/dist/cjs/query-executor/query-executor-base.js:36:16)
    at async SelectQueryBuilderImpl.execute (/nodejs/app/node_modules/kysely/dist/cjs/query-builder/select-query-builder.js:295:24)
    at async REPL1:1:33

In CloudSQL logs I see this after the process ends:
2023-09-26 22:03:07.306 UTC [3124945]: [1-1]<EMAIL_ADDRESS>FATAL:  canceling authentication due to timeout

Any ideas? I did cross-coding and verified that trying to connect to the "bad" db with the "good" code also fails. So I'm suspecting something is wrong the the CloudSQL db but I don't know what.

I have a feeling this is a mismatch in the user account on the db where it's missing the domain name. SO I think the bug MIGHT be just that the error is really really useless.

@djMax, you are not passing clientOpts when creating the Pool.

Hi @djMax, I believe the issue is as @edosrecki mentioned, it seems you are not passing the clientOpts to the call to new Pool().
Can you try updating your code to the following:
const pool = new Pool({
  ...clientOpts,
  user<EMAIL_ADDRESS>  database: 'db-name',
  max: 5
});

Let me know if the change solves the problem, this snippet was taken from our README

Sorry - that was a bad cut paste as I was trying to remove extraneous detail. It was being passed. BUT, the problem is the service account that terraform had mapped in the "bad case" was wrong - it was missing the @test-project.iam bit. But for whatever reason, it wasn't saying "login failed for that SA" it was saying this other weird thing, and then timing out on the SQL side.


[Tap To Pay] Reader has been disconnected unexpectedly on Android devices

Describe the bug
After putting the Android app in the background for some time, then reopening the app to do the first Tap to Pay transaction causes the following issue happens:
[Stripe terminal]: didReportUnexpectedReaderDisconnect { message: 'Reader has been disconnected unexpectedly',
  code: 'UNEXPECTED_ERROR.UNEXPECTED_SDK_ERROR' }

It happened after after creating the Payment Intent by the createPaymentIntent function and before the collectingPaymentMethod function executes. Then the collectingPaymentMethod function throws this error, which causes the transaction to fail:
{ code: 'INTEGRATION_ERROR.NOT_CONNECTED_TO_READER',
  message: 'LocalMobile reader is not connected' }

To Reproduce
Steps to reproduce the behavior:

Put app to the background for a while (eg. more than 2 hours).
Reopen the app, start the first transaction.
Tap To Pay screen appears, try to tap a card.
The issue above happens.

Expected behavior
The Reader should not be disconnected unexpectedly when doing the transaction.
Stripe Terminal React Native SDK version

^0.0.1-beta.17
^0.0.1-beta.18

Smartphone (please complete the following information):

Device: Google Pixel 3a
OS: Android 12

Hi,
It also happens on a Pixel 4, running Android 13.
Note that the error is random.  We left the app in the background over multiple periods, sometimes the payment works on re-opening the app, sometimes the above error happens.

@tzecheng and @ThanJack can you share account and serial numbers so we can investigate?

Hi @nazli-stripe , I can't find the account and serial numbers when the payment is cancelled.
The latest has id: pi_3PF7CwEcr8OExvfT1zxs98vO
Attached bugfender screen shot
android cancelled 4.pdf
Hope that helps.  Thanks.

It also happens on a Pixel 4, running Android 13.
Note that the error is random. We left the app in the background over multiple periods, sometimes the payment works on re-opening the app, sometimes the above error happens.

Same problem here on Samsung Tab Active 3, running Android 13.

This appears to be a potential issue with our native Android SDK, we are investigating internally. Will update this ticket with new information

Hi @nazli-stripe ,
This is one of the latest instances where there is a serial number:
serialNumber: '7808ed1a-4ea0-4f73-9c83-5a7bc28a04f4'

Here's another serial number:
serialNumber: 'b7c812c4-0237-4b3b-9366-cc9318004df0'

Any news? @nazli-stripe

Hello, @nazli-stripe ,
Any progress on this?

Hi there,
Here's is a screenshot of latest failure,
Serial number: 6b16a116-d082-4568-af55-34e1104bdf3a

Hi there,
Have tried with
^0.0.1-beta.19 and ^0.0.1-beta.20
Problem is still there.
Latest serialNumber: '2e941d93-52cb-4eea-a3db-9fbe1ecd1c13'

We are also experiencing this. The only solution so far has been to disconnect and reconnect the reader every time we want to initiate Tap to Pay. It looks like the library is unable to monitor the connection state of the reader in background and reconnect properly.

Hi there,
Have updated to v0.0.1-beta.22, but this problem still appears occasionally.
Latest serial no:

hey sorry for the radio silence on this one, we just released beta.23 with upgrades to the native Android SDK. Do you run into the issue there as well?

@tzecheng did updating to beta.22 help with the occurrences of the issue?

Hi @nazli-stripe ,
Problem still happening in v0.0.1-beta.22, as mentioned in an earlier chat https://github.com/stripe/stripe-terminal-react-native/issues/693#issuecomment-2435664847
Will be testing with v0.0.1-beta.23 next week.
Thanks.

Hi @nazli-stripe ,
We updated to v0.0.1-beta.23, but unfortunately the error is still there.

First tap - it errors, the white Tap to Pay screen does not appear
App goes back to the payment screen - the amount is still there
Second tap - the white Tap to Pay screen appears, tap the card to the back of the phone and it completes

Latest error:
payment_intent_id: 'pi_3QPxgUEсr80ExvfT1oaFUjK6
serialNumber: '0cb69f75-032f-4863-b2a6-7b7a9ed4e4ab'
android bg error.pdf

Hi @KillianLarcher , @nabilfreeman ,
Not sure whether I should post this here:
Did you manage to find a work around for this and would you mind sharing it?
Users are finding this is frustrating especially when they need to take a payment quickly.
We show them an error modal and ask them to retry again which works, but it is still annoying.
cc: @nazli-stripe

@tzecheng the solution for us has been to disconnect the reader after every success/failure and make sure we are connecting from scratch whenever the user initiates the payment flow.
I mentioned this above in a comment a few months back - it seems that there are some issues with the library maintaining a synchronised connection state with the OS.
This is not necessary on iOS, but the Android side has a lot of Tap to Pay bugs and a degraded experience. See #809 for more problems
Worth understanding that this library is a wrapper for closed-source iOS and Android SDKs, which are often several versions ahead of the pinned version here, so it’s very difficult for us to debug.

Hi @nazli-stripe ,
We did some further testing with v0.0.1-beta.23 and this is our observation:

In our onDidReportUnexpectedReaderDisconnect callback, we remove our codes to disconnect any existing readers, then to discover and connect to readers - basically let the Stripe SDK handle the reconnects
On coming from background, we start a payment
onDidChangeConnectionStatus shows the reader trying to connect → happens 3 times
At this point, the payment intent returns a timeout about a second later
[Stripe terminal]: didChangeConnectionStatus now connects → appears about 5 seconds later
Now retrying the payment works since reader is now available
Note the timing is from our app, and will not apply across board

Our guess is that in our case, when coming from background or when network is reconnecting, the reader takes time to connect, but the payment intent has timed out.


Update for BcContainerHelper?

This page still talks about NavContainerHelper. Shouldn't it use BcContainerHelper instead?

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

ID: 6979fc73-1395-b63f-50bf-b2fb1bfda4df
Version Independent ID: eaf8c4d6-15a5-6444-bc72-48bd0a2e326a
Content: Running a Container-Based Development Environment - Business Central
Content Source: dev-itpro/developer/devenv-running-container-development.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for catching this. You are right, both work, but we want to promote using BCContainerHelper going forward as this is also the version being updated. Will be fixed with the next doc refresh. Thanks.


Add query for extended column detail

Includes #72 (until it's merged), so only the last commit in this branch is currently relevant.
As mentioned in #72, I'm interested in querying column detail ahead of time so I can know use different implementations depending on the certain column types. The most interesting use cases for me are:

Handling data source-specific types like datetime2 by matching on the column's type_name

This is currently a bit difficult to work around without having multiple error fall backs, e.g. trying to cast and handling the returned error

Knowing which columns are available ahead of time so I don't need to create empty result sets (e.g. WHERE 0=1) to list them

The workaround is mostly ok, but doesn't expose some of the extra detail here, e.g. buffer_length which is useful to use as the input to later queries

This branch already seems to work well for the use cases mentioned, but I'm interested in how we could improve this. There are also three columns that I've skipped for now, because they don't seem to be necessary (data_type) or we don't have a place to expose them yet (sql_datetime_sub which could probably become part of DataType, is_nullable which could probably become part of Nullability).

Hi @grovesNL ,
sorry I am currently extremely busy and have little time left to review OS. I am grateful for the work you are doing here!
To the matter at hand. ODBC itself exposes with SQLColumns the column information via a cursor. At the lowest level visible to the application it is nothing more than a way to execute a query. The load_column_details I would like to rename to columns and forward to the top level odbc_api::Connection.
At that point we already enable power users to query additional columns.
If you want to go the extra mile you can also implement columns on Preallocated opening a path for users to reuse the statement handle if they want to query columns of multiple users in succession.
Contrary to a generic execute we have some Idea about that the schema of the resulting query looks like. We can persist that knowledge in a method creating the Connection::columns_buffer_description. I am as of now a bit unsure about the design of the higher level convenience function returning the Vector and its relation to the other two ways of describing a column 😅 . (That's however some madness we inherit also from ODBC itself).
Merging these lower level functions however would be a no brainer for me if you were to extract them into their own PR.
I feel the higher level functionality would integrate easier if there would be some nice way for row based queries already in place, but alas it's not and that's a different feature altogether.
Cheers, Markus

Sounds great, thanks for the review! I'll split the lower level functions into a separate PR so we can start there.

sorry I am currently extremely busy and have little time left to review OS.

No problem, please don't feel pressured to respond to my PRs quickly. I use my own fork internally so it's totally fine if it takes weeks, months, or longer to respond :)

Let's close this for now and we can think about it later

Yeah, sorry for not reacting sooner myself. I hope the merged low level functionallity is enough, so your local fork doesn't diverge to far. I am currently still struggling what to do exactly with the two types of column descriptions already in this crate (one using col_desc and the other the individual methods).

No problem! I'm just using the low level functionality directly and it works great :)


This project is only iOS 14?

Hi,
i want to build this project, but i get the error code which say this is for ios14. Could i build for ios 13?

Yes - that's right. In BooksListView, this code uses @StateObject, which requires iOS 14.


added new models and migrations for msgboard

Added the new models and migrations to go along with the database lecture.

@ifireball - I fixed the flake8 problems, except for the ones in 0001_initial.py which is auto generated by the system and has lines too long.
What is the accepted practice for this situation?

does extending the flake8 line-length tolerance to 100-120 not resolve the situation?

It's already at 120

I can add
# flake8: noqa
to the top of the file, so that it's ignored.
This is a question that's going to come up for all of our students, which is why I'd like to have a standard answer for them.

# flake8: noqa will switch off all Flak8 checks for the entire file, maybe we can just switch off the line length test

Being that the file is autogenerated do we want any flake8 tests on it?

If someone will inadvertently change it (While resolving a Git conflict for example), we want to catch the situation where it becomes invalid

ok

@RawanAbuleil what do you mean to do my marking approval on this PR?

This PR is very outdated by now


[jax2tf] Expand the support for jax.remat.

In the simplest forms, remat is already handled by the process_call.
But when the remat has outputs computed from values captured from
an outer environment, we need to also implement post_process_call.

@SIben FYI


Enable SPAR backend and frontend to run locally in containers

Describe the task
Update docker files and readmes to run and give instructions on how to run both Java backend API and frontend locally containerized.
Acceptance Criteria
Run these services locally in containers, instead of host machine.

[ ] backend api
[ ] frontend

Additional context
Ideally it should work on all operational systems, but if not, it must work on MacOS and Linux.

I noticed we already have Dockerfiles in place. Both backend and frontend already are working and running locally inside containers. The only missing feature is Remote Debug for the backend API.


Binary operators between DataFrame and Series object doesn't seem to work

related similar operation
http://stackoverflow.com/questions/19484344/how-do-i-use-a-specific-columns-value-in-a-pandas-dataframe-where-clause/19494873#19494873
http://stackoverflow.com/questions/19507088/filtering-a-pandas-dataframe-without-removing-rows/19516869#19516869
http://stackoverflow.com/q/21627926/190597
This should be a bit more intuitive
In [59]: data = """      A    B    C    D
1/1   0    1    0    1
1/2   2    1    1    1
1/3   3    0    1    0
1/4   1    0    1    2
1/5   1    0    1    1
1/6   2    0    2    1
1/7   3    5    2    3"""

In [60]: df = read_csv(StringIO(data),sep='\s+')

In [61]: df
Out[61]:
     A  B  C  D
1/1  0  1  0  1
1/2  2  1  1  1
1/3  3  0  1  0
1/4  1  0  1  2
1/5  1  0  1  1
1/6  2  0  2  1
1/7  3  5  2  3

In [62]: df.where((df>df.shift(1)).values & DataFrame(df.D==1).values)
Out[62]:
      A   B   C   D
1/1 NaN NaN NaN NaN
1/2   2 NaN   1 NaN
1/3 NaN NaN NaN NaN
1/4 NaN NaN NaN NaN
1/5 NaN NaN NaN NaN
1/6   2 NaN   2 NaN
1/7 NaN NaN NaN NaN

Given that normal binary operators like addition or logical and work well between a pair of Series objects, or between a pair of DataFrame objects (returning a element-wise addition/conjuction), I found it surprising that I cannot do the same between a Series object and a DataFrame object.
Here's a demonstration of what doesn't work now and what would be the expected result: http://nbviewer.ipython.org/urls/dl.dropboxusercontent.com/u/52886258/000-qdoqud/Untitled0.ipynb

So this is causing a warning here: https://github.com/pydata/pandas/blob/master/pandas/tests/series/test_operators.py#L1200
because df & s raises a ValueError, which is really doing: df.__and__(s, axis='columns')
and the alignment should be df.__and__(s, axis='index') but of course & is going to default align this way.


Nested array is not serialized in the rails format

I think the nested array serialization is not working as expected. For example, I have :
@app.factory('Order', ['RailsResource', 'railsSerializer', (RailsResource, railsSerializer) ->
  class Order extends RailsResource
    @configure url: '/account/products/1/orders', name: 'order', serializer: railsSerializer( ->
      @nestedAttribute('lineItems')
    )
])

This will send something like :
{"order"=>
  {"id"=>nil,
   "line_items_attributes"=> [{"_destroy"=>false }]}
 },
 "controller"=>"account/products/orders",
 "action"=>"create",
 "product_id"=>"1"}

It's a correct json format but I think rails is waiting for [[0, {"_destroy"=>false }]].
I think we can change this lines. I'm ready to contribute to resolve this issue but I just need a confirmation.
Thanks.

I'm not familiar with that syntax for destroying a nested attribute.  That does not appear in the examples for one-to-one or one-to-many in the docs: http://api.rubyonrails.org/classes/ActiveRecord/NestedAttributes/ClassMethods.html.
Also, the code you linked to was deserialization which would be processing response data.

The format  I gave is for nested forms as you can see here.  The correct format is :
   "line_items_attributes"=>
    {"0"=>
      {"quantity"=>"123",
       "style_color_id"=>"2",
       "style_color_size_id"=>"8",
       "_destroy"=>"0"},
     "1"=>
      {"quantity"=>"4",
       "style_color_id"=>"4",
       "style_color_size_id"=>"",
       "_destroy"=>"0"}},

I think I can do a custom serializer if there is not built-in solution. I think it can be useful to have an option in the configuration, like asNestedForm: true. What you think?


Merging Version 0

Epic 1: Include Project with MVP (#2)

epic_1_include_mvp

This release brings the basic API with the essential resources required to perform coalescing operations. The docstrings are still not fully covered. The repr and str magic methods are also not fully covered. The API.md file and the /examples directory won't be filled at this release. And lastly, the unit tests haven't still been elaborated.

Features: - Special Objects: 1. VoidTypes - Special Types 1. UndefinedType - Special Constants 1. UNDEFINED - alias: Undefined 2. VOID - alias: Void - Special Agents 1. VOIDSAFE - alias: VoidSafe 2. VALUE - alias: value - Special Operators 1. IFNONE - alias: ifnone 2. IFNDEF - alias: ifndef 3. IFVOID - alias: ifvoid

#1: Include Project with MVP

Gustavo Cardoso Ribeiro

2024-03-10

epic_1_include_mvp_2

README.md image centered and resized.

#1: Include Project with MVP
Gustavo Cardoso Ribeiro
2024-03-10

Update README.md

fix( README.md ):

Corrected image alignment;

Removed spacers;

Added a disclaimer about /examples.

#1: Include Project with MVP

Gustavo Cardoso Ribeiro

2024-03-10

3_change_nonesafe (#4)

FIX: changed "/nonesafe" to "/voidsafe"

#3: Change "nonesafe" Directory Name
Gustavo Cardoso Ribeiro
2024-03-12

5_library_documentation (#11)

doc(*): Added an extensive documentation to the package
This release includes an extensive documentation for the package, which covers the following scopes:

Documentation:

Finished covering declarations' docstrings;
Finished implementing __repr__ methods;
Elaborated the API.md file;
Elaborated the content for the /examples directory;
Elaborated more on the README.md;

12_install_via_pypi (#12)

doc(*): Install via PyPi

Added twine-generated directories to .gitignore;
Added instructions on how to install the package;
Added metadata about the project's description on setup.cfg.

#12: Install via PyPi

Gustavo Cardoso Ribeiro

Version 0 will be merged with master. The GitFlow will be applied only by using the develop branch.


types(ChannelManager|GuildChannelManager): removed unnecessary overload

The overload on the line below each already accounts for the same return type, so marking the second argument as optional is enough. No need to have a separate overload with no second argument

thanks!

thanks!


Fix: Rubocop latest version issues

Summary

Rubocop new version 0.73 has been released; https://github.com/rubocop-hq/rubocop/releases
Travis builds are getting failed due to this new release; https://travis-ci.org/optimizely/ruby-sdk/jobs/559878094
Used latest version and resolved lint errors.

Coverage decreased (-0.02%) to 99.522% when pulling 42103382c4898a4e0cd2b0b87958bc9d6eba5edd on rashid/fix-rubocop-latest into 45e7e2b87041d9fc81d047c17c5c6429a0a731e5 on master.

Coverage decreased (-0.02%) to 99.522% when pulling 42103382c4898a4e0cd2b0b87958bc9d6eba5edd on rashid/fix-rubocop-latest into 45e7e2b87041d9fc81d047c17c5c6429a0a731e5 on master.

Coverage decreased (-0.02%) to 99.522% when pulling 42103382c4898a4e0cd2b0b87958bc9d6eba5edd on rashid/fix-rubocop-latest into 45e7e2b87041d9fc81d047c17c5c6429a0a731e5 on master.


Updates to upgrade tests

Continuing to evolve providertest library; this is introducing the preferred pattern from that library, breaking out top-level tests by test-program and combining upgrades with other forms of testing (e2e, sdk).
Curious about CI results here; this may need a little more support from the Makefile and CI system since these tests run in the prerequisites phase which may not have the necessary credentials available to test pulumi preview.

Blocked by https://github.com/pulumi/ci-mgmt/issues/675

This is now upgraded to 0.0.2 of the provider and passing locally for me. I think there still is a problem with running these in CI. Perhaps I can find a way to skip them in CI until we can circle back to reintroducing creds into the prerequisites job.

I've worked around the issues with lack of credentials. We can check this in, I think it will help with having the upgrade tests aligned with the latest shape of providertest. CC @guineveresaenger


Ignore markdown file in /locales

Hi
Is it possible to ignore markdown files or some specific files from the /locales folder?
I am working on a project with some other developers and we like to have a readme file with some guidelines on how to structure the folders and files. We now always get a warning in the console.

We are using next 10.0.3 and next-translate 1.0.0.
BR, Cedric

I think this is the problem of the dynamic import of webpack. By doing this, it causes all the files that exist inside locales to be created as chunks.  Including the markdown file, which complaints about not having a proper loader. I am not very clear how from next-translate we can solve this...

I think this is the problem of the dynamic import of webpack. By doing this, it causes all the files that exist inside locales to be created as chunks.  Including the markdown file, which complaints about not having a proper loader. I am not very clear how from next-translate we can solve this...

A solution you could choose is to use a different structure and overwrite the import in the property loadLocalesFrom.
I'm not sure if replacing ./locales/${lang}/${ns} to ./locales/${lang}/${ns}.json (adding the .json) is enough or not. We do not put an extension to give the opportunity to work by default also with other types  like .js.
{
  // ...rest of config
  "loadLocaleFrom": (lang, ns) =>
    // Adding the .json at the end to tell webpack that you only want the .json files
    import(`./locales/${lang}/${ns}.json`).then((m) => m.default),
}

A solution you could choose is to use a different structure and overwrite the import in the property loadLocalesFrom.
I'm not sure if replacing ./locales/${lang}/${ns} to ./locales/${lang}/${ns}.json (adding the .json) is enough or not. We do not put an extension to give the opportunity to work by default also with other types  like .js.
{
  // ...rest of config
  "loadLocaleFrom": (lang, ns) =>
    // Adding the .json at the end to tell webpack that you only want the .json files
    import(`./locales/${lang}/${ns}.json`).then((m) => m.default),
}

A solution you could choose is to use a different structure and overwrite the import in the property loadLocalesFrom.
I'm not sure if replacing ./locales/${lang}/${ns} to ./locales/${lang}/${ns}.json (adding the .json) is enough or not. We do not put an extension to give the opportunity to work by default also with other types like .js.
{
  // ...rest of config
  "loadLocaleFrom": (lang, ns) =>
    // Adding the .json at the end to tell webpack that you only want the .json files
    import(`./locales/${lang}/${ns}.json`).then((m) => m.default),
}

Thanks for the quick response! This worked :)

A solution you could choose is to use a different structure and overwrite the import in the property loadLocalesFrom.
I'm not sure if replacing ./locales/${lang}/${ns} to ./locales/${lang}/${ns}.json (adding the .json) is enough or not. We do not put an extension to give the opportunity to work by default also with other types like .js.
{
  // ...rest of config
  "loadLocaleFrom": (lang, ns) =>
    // Adding the .json at the end to tell webpack that you only want the .json files
    import(`./locales/${lang}/${ns}.json`).then((m) => m.default),
}

Thanks for the quick response! This worked :)


Users that uses this tool

Here you have all the users that succesfully finished reading the readme
2 users:

@nescalante
@dschenkelman

+1

-1

+1

-1

+1

+1

+1


Add error handling and retry mechanism to curl calls within curlgh

RFC :)
We've seen a few pipelines fails because of rate-limit / network issue / don't trust the Internet.
For instance, we've had instances of pipelines fail because of rate-limiting it logged in the Concourse job's step logs: "Not found for ". Our developers were quite confused by this and we wanted to better handle some HTTP errors to give relevant feedback in the resource's logs.
Therefore, I've added some error handling and retry mechanism for curlgh. The main idea is to dump the HTTP response headers in /tmp/responseheaders and check whether we had a 200 OK back (or not - and then handle it).
Points of discussions:

Usage of 'echo "some log " >&2' as a mean to output logs (letting the user know what went wrong and if the script will retry)
Whether the retry on Rate-limit should be enabled/disabled through a configuration flag
Whether we should limit or let the user configure the maximum sleep time for X-RateLimit-Reset (eg: if the limit gets reset in 40 minutes, should the build really sleep for 40 minutes?)

If https://github.com/dpb587/github-status-resource/pull/15 is merged first, I can rebase my PR on it to use the same retry_count and retry_timeout flags.


TypeScript declaration seems wrong

Thanks for writing this library, it looks great. But I've tried to use it with a TypeScript project and it gives me an error when I try to call matched(req, res):
Argument of type 'IncomingMessage' is not assignable to parameter of type 'FSRouterIncomingMessage'.
  Type 'IncomingMessage' is missing the following properties from type 'FSRouterIncomingMessage': params, queryts(2345)

Looking at fs-router's bundled TypeScript declaration, it says the request handler returned by fs-micro takes a customized req, adding params and query objects:
    interface FSRouterIncomingMessage extends IncomingMessage {
        params: {
            [paramName: string]: string
        },
        query: {
            [paramName: string]: string
        }
    }

But why? Micro doesn't add these extra properties to req. According to its own TypeScript declarations (in both the latest DefinitelyTyped package and the bundled declaration included in the latest Canary release of micro itself), the req argument is just a standard IncomingMessage. Where are these params and query properties supposed to come from?

OK, looking a bit closer at the TypeScript example, it seems I'm supposed to import RequestHandler from fs-router, and use that to type my micro handler. But while that might pass type-checking in the example, it's a hack and could cause problems in real code. The micro handler doesn't really implement fsRouter.RequestHandler. It seems this hack is suggested because the match(req) call actually modifies req so it's a different type after the call. I'm not sure if there's any correct way to represent this in TypeScript.

Since this library extends req (a pattern you are welcome to take issue with, but also just a fact in the library’s current architecture), using a type that extends IncomingMessage seems correct to me - I don’t believe it’s a hack at all to provide a type for the object that this library returns.
That said, I’m not sure that any architecture change would get you to a place where you could write anonymous handlers without assigning them a type. Right now typing your handlers as RequestHandler will solve your problem cleanly. If query and params were to be passed as arguments rather than added to req you’d still need this.
If I were to write this lib from scratch I might consider returning parsers from it (like micro) for parsing query and params functionally, which would leave alone the req, but that would break existing code so I’d need to bump major. Would be happy to consider a PR doing just that if it seems preferable, I could release that under a tag. In any case, this is a design critique rather than a bug so I’ll close this issue.