sage: import 10.2.beta3 patches

Description of changes

Import upstream patches:

doctest fix for python >= 3.11, sagemath/sage#36218
fix for ecl >= 23.9.9, sagemath/sage#36235

Failing Hydra logs, relevant lines:

[311/552] gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/jh2dj172jmmlw74kw4bsqa5ycf1blv4v-libxcrypt-4.4.36/include -fPIC -Isage/libs -I/nix/store/kiw2pplx7iadra2zy0c204bhngrjw8xg-gmp-with-cxx-6.3.0-dev/include -I/nix/store/jjxwn04kkwqy4nmdzp4np2pdjq21vhzv-ecl-23.9.9/include -I./sage/cpython -I/nix/store/0ikyy1lm97f36psav3pn2z1anglx678n-python3.11-cysignals-1.11.2/lib/python3.11/site-packages/cysignals -I/build/sage-src-10.0/pkgs/sagemath-standard -I/nix/store/2z836nvlwm17ih2sy1d1l165jihdr2ha-python3.11-numpy-1.26.1/lib/python3.11/site-packages/numpy/core/include -I/nix/store/5k91mg4qjylxbfvrv748smfh51ppjq0g-python3-3.11.6/include/python3.11 -Ibuild/cythonized -I/nix/store/5k91mg4qjylxbfvrv748smfh51ppjq0g-python3-3.11.6/include/python3.11 -c build/cythonized/sage/libs/ecl.c -o build/temp.linux-x86_64-cpython-311/build/cythonized/sage/libs/ecl.o -fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -Dlinux
In file included from build/cythonized/sage/libs/ecl.c:3373:
build/cythonized/sage/libs/eclsig.h: In function ‘ecl_bignum_from_mpz’:
build/cythonized/sage/libs/eclsig.h:48:45: error: ‘struct ecl_bignum’ has no member named ‘big_num’
   48 | #define ecl_mpz_from_bignum(obj) ((obj)->big.big_num)
      |                                             ^
build/cythonized/sage/libs/eclsig.h:53:13: note: in expansion of macro ‘ecl_mpz_from_bignum’
   53 |     mpz_set(ecl_mpz_from_bignum(z), num);
      |             ^~~~~~~~~~~~~~~~~~~
build/cythonized/sage/libs/ecl.c: In function ‘__pyx_f_4sage_4libs_3ecl_ecl_to_python’:
build/cythonized/sage/libs/eclsig.h:48:45: error: ‘struct ecl_bignum’ has no member named ‘big_num’
   48 | #define ecl_mpz_from_bignum(obj) ((obj)->big.big_num)
      |                                             ^
build/cythonized/sage/libs/ecl.c:7415:199: note: in expansion of macro ‘ecl_mpz_from_bignum’
 7415 |     ((struct __pyx_vtabstruct_4sage_5rings_7integer_Integer *)__pyx_v_N->__pyx_base.__pyx_base.__pyx_base.__pyx_base.__pyx_base.__pyx_base.__pyx_base.__pyx_base.__pyx_vtab)->set_from_mpz(__pyx_v_N, ecl_mpz_from_bignum(__pyx_v_o));
      |                                                                                ^~~~~~~~~~~~~~~~~~~

Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

cantor
labplot
sage
sageWithDoc

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Great, thank you very much! No need to worry about the plot.py failure, I've seen it before too.


Add an instance factory to let customize the instantiation on Store

In general the idea is to avoid having to duplicate the options offered by Instance.Builder.
I have been contacted regarding withStart, but I see the real value of using it with withMachineFactory.

you should also update the top post

do you have a proposal?


[C++] Prefer unsafe casting by default in Substrait

Describe the enhancement requested
Substrait specifies a failure behavior (return null or error) for casting.  However, it does not specify what exactly constitutes a failure. When we added bindings for the cast expression we assumed that Substrait wanted a safe cast.  However, I have since learned that most existing engines (e.g. postgres, spark, etc.) will perform an unsafe cast by default and only consider a failure when casting is impossible (e.g. "foo" to integer).
I'd like to eventually see Substrait add support for specifying more precisely what kind of casting should occur.  In the meantime I think we should update the default to unsafe casting to match user expectation.
Component(s)
C++

However, I have since learned that most existing engines (e.g. postgres, spark, etc.) will perform an unsafe cast by default

For postgres, that is not what I see based on a quick test for integer overflow:
test_db=# SELECT CAST (10000000 AS smallint);
ERROR:  smallint out of range

On the other hand, float truncation is indeed done by postgres:
test_db=# SELECT CAST (1.5 AS integer);
 int4
------
    2
(1 row)

(although it is interesting to see that the result is 2, while in arrow casting 1.5 to int64 with allow_float_truncate=True gives 1)

It seems SQL server truncates so I think we'll need both behaviors.  Sounds like something else we will need to document more thoroughly in Substrait and will also need to be added to the list of dialect behaviors.  My original motivation was to allow float->int.  I'm pretty open to whatever default we want (e.g. allow float/decimal truncation but not integer truncation) but I believe @icexelloss wanted something more flexible than defaulting to "safe only".


⚠ Processors has degraded performance

In bc6e166, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 1204 ms

Resolved: Processors performance has improved in fe0abd0.


Documenting some issues by creating a wiki

I've already add a comment before to create a wiki with specific configuration as I think lots of issues are users who don't understand some tricky part of usemin.
I've started to tag issue with label 'doc' as I plan to add specific use case in a wiki.
This issue is only here the need for the documentation.

users who don't understand some tricky part of usemin.

I'd rather see it made simpler than documenting tricky parts.

I'd rather see it made simpler than documenting tricky parts.

@sindresorhus I agree but it might take more time to make it simpler. Documentation might helps, at first, to not be overwhelmed by issues.

Sure, I've enabled the wiki. Go nuts.

@sindresorhus thanks!


fix: mdx analyzer plugin conflicts

Closes #160
Bumps TS plugin version to fix MDX analyzer conflicts

Thanks for the release in<EMAIL_ADDRESS>🙌
I can confirm that this is working, and is no longer conflicting with MDX Analyzer
cc @remcohaszing


Bit-vector basic operators

This pull request implements assert_bit_vector, supporting basic operators such as shift/and/xor/add/less than/etc. Every bit-vector variable/constant/operation are treated as unsigned.asssert_bit_vector makes a separate z3 query, and the main query assumes its corresponding integer properties. When making the corresponding property, bit operators that are not existing at the integer level (namely <<, >>, &, ^, | ) are translated as uninterpreted functions.
Function level bit vector reasoning is not supported yet, although it can be annotated with
#[verifier(bit_vector)]

Made a new pull request ( #32 ) with a few commits addressing Chris and Yi's comment.


Updated test.sequencing_summary.txt to fix column issues

The file test.sequencing_summary.txt was out of date and does not follow the current guidelines for sequencing_summary files due to column formatting.

Hello, as my commits have been approved, is it possible to merge my changes into the repo?
Thank you :)


Renderer should check block before getting properties

If the game does not remesh a chunk after the Pandora's Box block is removed here (this seems to only occur reliably with Embeddium, but a code analysis suggests it can occur in vanilla too), the block entity remains in the list to render on the next frame. When that happens, the following function will crash as it tries to retrieve a direction property from an air block.
https://github.com/Alexandra-Myers/PandorasBox/blob/6bcac95dc1000b45d39595f0398e492114c5848a/src/main/java/ivorius/pandorasbox/block/PandorasBoxBlockEntity.java#L46
To fix this, a check should be added that checks whether state.getBlock() instanceof PandorasBoxBlock, and if that is not satisfied, a default rotation should be returned. Other vanilla block entities (e.g. the shulker box in its block entity renderer) use a similar check.
I've worked around this in Embeddium by refusing to render removed BEs, but vanilla doesn't require that so I think this will still crash in vanilla under the right conditions.

fixed in next update


Rework auras inclusion algorithm to match WC3

This image shows how auras work in You TD 2. Compared to WC3 version, this is a different behavior. In WC3 map towers were affected by the aura if the aura range overlaps with the tower building area.

Demonstration with Skink tower which has 200 aura range.
Note that in WC3 distance between center of "tiles" is 128.

Investigated auras which target creeps.
The conclusion is that they do not extend rand by 64 like towers.
Tested using Icy Core tower which has an aura with range of 800 which applies a slow debuff to creeps.
In range @ 768

Out of range @ 832

This +64 extension appears to also apply to tower abilities which affect towers in range.
For example, fiery dog has ability with range of 420 but it affects this tower at 461 distance.


Update core to latest release v19.13

We had a partner recently ask for an updated quickstart image with this version of core

v19.13.0 is not officially released yet (it will be today though), so as of now latest stable is v19.12.0. I was going to update quickstart today once the release is done, so we can merge this PR then.

Alright, latest 19.13.0 RC has been promoted to stable, so this looks good to me. Thanks for putting it together!


Instance specific "tmp.txt" -> run multiple instances in parallel

Hey there,
if there wouldn't be a hardcoded tmp.txt but an instance specific tmp-file it would be possible to run multiple instances (in the same directory).
BTW, thanks for your work, very helpful.

FFMPEG encoding is typically pretty heavy CPU wise and I run this script on my Linux laptop. Never had much use for multiple instances. You are allowed to run the script over the entire directory serially however. Just run something like this
AAXtoMP3 -a <AUTHCODE> *.aax


Add adelarsq/neoline.vim

Adding my plugin adelarsq/neoline.vim 😄

Looks cool! Thanks!

Looks cool! Thanks!


Added a note on using venv instead of virtual-env

This is not super critical, because they can figure this out for themselves

Awesome. Thank you Alon :)


2.4.5

@rultor release tag is 2.4.5

@rultor release tag is 2.4.5

@portlek OK, I will release it now. Please check the progress here

@rultor release tag is 2.4.5

@portlek Done! FYI, the full log is here (took me 7min)


Disk cache outside webroot

The PR does quite a few things:

Allows for having the IP disk cache to exist outside of the web root
The paths configured for the IP disk cache can now be absolute paths or virtual paths, virtual paths can also be relative to go beyond the web root (i.e. "~/../OutsideOfWebRoot")
Adds unit tests for resolving the cache folder, absolute and virtual paths
Better performance for the disk cache - it now only validates and resolves the cache paths once (lazily) per application, before it did this for every file
Adds a new configuration option to opt-in to automatically creating file watchers for every cached image -> this is actually the main cause for FCN problems
Updates the _Layout.cshtml page to show more FCN details
Adds lots of notes regarding what has been changed and a few more TODOs (though these TODOs are outside of this PR scope)

Ok, so I'll try to explain as much as I can here :)

By default in ASP.NET with FcnMode="NotSet", ASP.NET will create a watcher for every sub folder in your application that is inside of the web root. It will create these watchers lazily, so once an IP cached image is fetched a watcher would be created for the folder it exists in
Using FcnMode="Single", ASP.NET will create a single watcher with a larger buffer but will still monitor all sub folders in your application that is inside the web root.

So why choose one over another? Well there's a couple of reasons. When running on Azure Web apps, the file server is a remote file server (i.e. UNC Share). When you have FcnMode="NotSet" then having all of these watchers will actually slow down the file server quite a lot... this is almost true... Azure Web apps runs a custom windows kernel so MS is doing something rather special to ensure that these watchers don't slow down the file servers, however other hosts like Umbraco Cloud aren't so lucky and run a normal Windows kernel. So running FcnMode="Single" on Umbraco Cloud makes the file system much happier, same would probably be true for any traditionally hosted IIS site that uses remote file system UNC file paths. However, the downfall of "Single" mode is that the buffer can overflow more easily because there's only one watcher watching a ton of folders. Since Image Processor creates quite a lot of folders and if people use Image Processor extensively then they may see this buffer overflow with errors like "Overwhelming change notifications" (among others).
Being able to store Image Processor cache files outside of the web root will reduce the amount of directories watched which this PR enables. However what I discovered is that even if we do this, there are still file watchers being created for every Image Process cache file! This is because by default when Image Process adds the result to the memory cache, it does so by adding a file dependency. This is so that the in memory cache can be invalidated if the cache files on disk changes. I don't really think it's a big requirement for people to have that functionality and it drastically increases the number of files watchers. In actual fact, I believe this to be the main root cause of FCN issues with Image Processor.
There is a new config option: useFileChangeMonitors and by default this will be false. This is sort of a breaking change (but is it?!) since it was true before. This one change could in fact reduce the number of file watchers so that FCN is no longer an issue. You can test this with the test web app by togging this value. But, even if this is false, you'll see that the "FileChangesMonitor aliases hash table" on the test website still grows anytime an Image Process cache file is accessed when it's in the web root so I'm fairly sure that the "Single" watcher is still watching those.
So when the cache is configured outside of the web root like with "~/../OutsideOfWebRoot" (make sure that folder exists and that the IIS user has access to it!), then load up and browse around the test website and you'll notice a vast reduction in the amount of image processor cache folders being watched, along with the default false setting for  useFileChangeMonitors, the number of folders monitored is now very low.

@Shazwazza This is all great!
As you spotted the only reason I have the monitoring was to keep the memcache in sync. As you say though most people won't need that level of tracking. I wonder whether the memcache is of that much benefit?

Hrm, I'm not really sure if the mem cache is of any use beside just occupying a lot of extra mem? The file cache handling should be ultra fast

Maybe for the Azure Cache since that reduces network requests... DiskCache will definitely be fast.

Merged. Much appreciated!

I've tested the latest with Umbraco and storing outside of the wwwroot and there's no error logs output with regards to using Response.End so I'm pretty sure it's not an issue

Great stuff. It occurred to me actually that it would have reset IIS during my initial testing if it was an issue.

Just gonna test on Umbraco Cloud now to see what happens.


Value not in list: control_net_name: 'control_unique3d_sd15_tile.safetensors' not in ['diffusion_pytorch_model.safetensors', 'sai_xl_depth_256lora.safetensors']

When I run the "Quque Prompt" after loading an image, the cmd system prompted:
Failed to validate prompt for output 289:

ControlNetLoader 192:

Value not in list: control_net_name: 'control_unique3d_sd15_tile.safetensors' not in ['diffusion_pytorch_model.safetensors', 'sai_xl_depth_256lora.safetensors']
Output will be ignored
Failed to validate prompt for output 195:
Output will be ignored
Failed to validate prompt for output 277:
Output will be ignored
Failed to validate prompt for output 299:
Output will be ignored
....
Output will be ignored
Failed to validate prompt for output 288:
Output will be ignored。
It just finished when finishing stage_1 but not running stage 2~4.

Hey @victorgaozhan sorry for the late responds
It seems you don't have control_unique3d_sd15_tile.safetensors in your corresponding model dir.
Download it and put it under Your ComfyUI root directory/ComfyUI/models/controlnet, for more info about Unique3D and each model, please check README


feat: Add event tracker  [DEV-3530]

Add the observer pattern implementation for tracking event handling
For now, there is only one event to track - track but it includes some operations inside.
By default enables logging and operation table filling
Adds the abstract handler for datadog without explicit implementation

Task linked: DEV-3530 Alerting/monitoring feature for tracking operation failures


Trying to get your music cast setup working

first of all thanks for putting the effort in to get this going .
I have a whole house music cast setup and have been playing around with your multi speaker setup but cannt get it working
first setup i did was add the following to the configuration file , this was in addition to the same devices i had added under  platform: yamaha_musiccast same ports
    host: 192.xxx
    port: 5005
  - platform: musiccast_yamaha
    host: 192.xxx
    port: 5006
  - platform: musiccast_yamaha
    host: 192.xxx
    port: 5007
  - platform: musiccast_yamaha
    host: 192.xxx
    port: 5008 ,,,

then added thr groups in min media player
``` entity: media_player.upstairs_lounge_main
group: true
icon: 'mdi:surround-sound'
name: Lounge Yamaha Sound Bar
speaker_group:
  entities:
    - entity_id: media_player.alfresco_main
      name: alfresco
    - entity_id: media_player.upstairs_lounge_main
      name: lounge
  expanded: false
  platform: musiccast_yamaha
type: 'custom:mini-media-player' ```

but still does not work.. must be doing something wrong

Hello, did you put the configuration for mini media player at the ui-lovelace file right?
Can you please paste the entire config of mini media player?

‘’’
1
entity: media_player.upstairs_lounge_main
2
group: true
3
icon: 'mdi:surround-sound'
4
name: Lounge Yamaha Sound Bar
5
speaker_group:
6
entities:
7
- entity_id: media_player.alfresco_main
8
name: alfresco
9
- entity_id: media_player.upstairs_lounge_main
10
name: lounge
11
expanded: false
12
platform: musiccast_yamaha
13
type: 'custom:mini-media-player'
14
volume_stateless: true
15
theme: dark_mint
16

I think I find what's wrong.
The speaker group must be under an entity.
id: media_player
icon: mdi:audio-video
title: glance
cards:
  - type: entities
    entities:
      - type: custom:mini-media-player
        group: true
        entity: media_player.livingroom_main #  <------  this is the main entity
        name: LivingRoom
        toggle_power: false
        artwork: cover
        hide:
          icon: true
          power_state: false
        shortcuts:
          buttons:
            - name: Tuner
              icon: mdi:radio
              type: source
              id: tuner
            - name: Spotify
              icon: mdi:spotify
              type: service
              id: switch.turn_on
              data:
                entity_id: switch.spotify
        speaker_group:   # <------ and the speaker group added here
          platform: musiccast_yamaha
          expanded: true
          entities:
            - entity_id: media_player.livingroom_main
              name: Livingroom
            - entity_id: media_player.bedroom_main
              name: Bedroom
            - entity_id: media_player.office_main
              name: Office
            - entity_id: media_player.yard_main
              name: Yard

entity: media_player.upstairs_lounge_main
group: true
icon: 'mdi:surround-sound'
name: Lounge Yamaha Sound Bar
speaker_group:
  entities:
    - entity_id: media_player.alfresco_main
      name: alfresco
    - entity_id: media_player.upstairs_lounge_main
      name: lounge
  expanded: false
  platform: musiccast_yamaha
type: 'custom:mini-media-player'
volume_stateless: true
theme: dark_mint
volume_step: 3```

here you go


ElastAlert not working after elasticsearch upgrade to 6.8

ElastAlert stopped working after the upgrade of Elasticsearch.
Elastisearch version used is : elasticsearch-6.8.2
I even upgraded the elastalert to new version, still it is not working
pip show elastalert
Name: elastalert
Version: 0.2.1
Python version :
python -V
Python 3.6.8
Also the elastalert index name changed to elastalert_status_status. In the older version it was elastalert_status
green open elastalert_status_silence 2CuKVwZyR3ObCjrpn8xB6A 5 1        0   0   2.5kb   1.2kb
green open elastalert_status_error   e7iJbT9_QjWhmsWveEBB9Q 5 1        0   0   2.5kb   1.2kb
green open elastalert_status_past    BdYuMq6ZRxOOQdX_jsal-Q 5 1        0   0   2.5kb   1.2kb
green open elastalert_status         wHwvcmRDRIC2K9lnJAg5Pw 5 1        0   0   2.5kb   1.2kb
green open elastalert_status_status  Q6dhNvsqSKCQ2SE6mM85sg 5 1       10   0  80.7kb  40.3kb
I even tried recreating the index but no luck. Can any one please help on this

When running the rule in debug mode I get the below output.
INFO:elastalert:Note: In debug mode, alerts will be logged to console but NOT actually sent.
To send them but remain verbose, use --verbose instead.
INFO:elastalert:Note: In debug mode, alerts will be logged to console but NOT actually sent.
To send them but remain verbose, use --verbose instead.
1 rules loaded
INFO:elastalert:Starting up
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 119.999921 seconds
WARNING:elasticsearch:GET http://localhost:9200/elastalert_status_status/_search?_source_includes=endtime%2Crule_name&size=1 [status:404 request:0.010s]
ERROR:root:Error querying for last run: NotFoundError(404, 'index_not_found_exception', 'no such index', elastalert_status_status, index_or_alias)
INFO:elastalert:Skipping writing to ES: {'message': "Error querying for last run: NotFoundError(404, 'index_not_found_exception', 'no such index', elastalert_status_status, index_or_alias)", 'traceback': ['Traceback (most recent call last):', '  File "/opt/elastalert/elastalert/elastalert.py", line 686, in get_starttime', "    _source_includes=['endtime', 'rule_name'])", '  File "/usr/lib/python3.6/site-packages/elasticsearch-7.0.2-py3.6.egg/elasticsearch/client/utils.py", line 84, in _wrapped', '    return func(*args, params=params, **kwargs)', '  File "/usr/lib/python3.6/site-packages/elasticsearch-7.0.2-py3.6.egg/elasticsearch/client/init.py", line 819, in search', '    "GET", _make_path(index, "_search"), params=params, body=body', '  File "/usr/lib/python3.6/site-packages/elasticsearch-7.0.2-py3.6.egg/elasticsearch/transport.py", line 353, in perform_request', '    timeout=timeout,', '  File "/usr/lib/python3.6/site-packages/elasticsearch-7.0.2-py3.6.egg/elasticsearch/connection/http_requests.py", line 155, in perform_request', '    self._raise_error(response.status_code, raw_data)', '  File "/usr/lib/python3.6/site-packages/elasticsearch-7.0.2-py3.6.egg/elasticsearch/connection/base.py", line 178, in _raise_error', '    status_code, error_message, additional_info', "elasticsearch.exceptions.NotFoundError: NotFoundError(404, 'index_not_found_exception', 'no such index', elastalert_status_status, index_or_alias)"], 'data': {'rule': 'Table SEPM OS attack alert Inbound traffic'}}
INFO:elastalert:Queried rule Table Test traffic from 2019-08-21 03:38 UTC to 2019-08-21 03:40 UTC: 0 / 0 hits
WARNING:elasticsearch:DELETE http://localhost:9200/_search/scroll [status:404 request:0.004s]
INFO:elastalert:Skipping writing to ES: {'rule_name': 'Table Test traffic', 'endtime': '2019-08-21T03:40:23.031579Z', 'starttime': '2019-08-21T03:38:53.031579Z', 'matches': 0, 'hits': 0, '@timestamp': '2019-08-21T03:40:23.079554Z', 'time_taken': 0.047934770584106445}
INFO:elastalert:Ran Table Test traffic from 2019-08-21 03:38 UTC to 2019-08-21 03:40 UTC: 0 query hits (0 already seen), 0 matches, 0 alerts sent
And no alerts are generated.  Please help on this

The above error fixed by recreating the index. But still we are not getting any alerts.
[root@ladcsealert01 elastalert]# python -m elastalert.elastalert --verbose --rule  /opt/elastalert/Rule_folder/port_scan.yaml
1 rules loaded
INFO:elastalert:Starting up
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 119.999923 seconds
INFO:elastalert:Queried rule Port Scan detection use case from 2019-08-21 08:01 UTC to 2019-08-21 08:02 UTC: 0 / 0 hits
WARNING:elasticsearch:DELETE http://localhost:9200/_search/scroll [status:404 request:0.004s]
INFO:elastalert:Ran Port Scan detection use case from 2019-08-21 08:01 UTC to 2019-08-21 08:02 UTC: 0 query hits (0 already seen), 0 matches, 0 alerts sent
INFO:elastalert:Background configuration change check run at 2019-08-21 08:04 UTC
INFO:elastalert:Background alerts thread 0 pending alerts sent at 2019-08-21 08:04 UTC
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 119.999681 seconds
INFO:elastalert:Queried rule Port Scan detection use case from 2019-08-21 08:02 UTC to 2019-08-21 08:04 UTC: 0 / 0 hits
WARNING:elasticsearch:DELETE http://localhost:9200/_search/scroll [status:404 request:0.004s]
INFO:elastalert:Queried rule Port Scan detection use case from 2019-08-21 08:04 UTC to 2019-08-21 08:04 UTC: 0 / 0 hits
WARNING:elasticsearch:DELETE http://localhost:9200/_search/scroll [status:404 request:0.003s]
INFO:elastalert:Ran Port Scan detection use case from 2019-08-21 08:02 UTC to 2019-08-21 08:04 UTC: 0 query hits (0 already seen), 0 matches, 0 alerts sent
INFO:elastalert:Background configuration change check run at 2019-08-21 08:06 UTC
INFO:elastalert:Background alerts thread 0 pending alerts sent at 2019-08-21 08:06 UTC
INFO:elastalert:Disabled rules are: []
Blow is the elastlalert mapping info:
curl http://localhost:9200/elastalert*/_mapping
{"elastalert_status":{"mappings":{"_doc":{"properties":{"@timestamp":{"type":"date","format":"dateOptionalTime"},"endtime":{"type":"date"},"hits":{"type":"long"},"matches":{"type":"long"},"rule_name":{"type":"keyword"},"starttime":{"type":"date"},"time_taken":{"type":"float"}}}}},"elastalert":{"mappings":{"_doc":{"dynamic_templates":[{"strings_as_keyword":{"match_mapping_type":"string","mapping":{"ignore_above":1024,"type":"keyword"}}}],"date_detection":false,"numeric_detection":true,"properties":{"@timestamp":{"type":"date","format":"dateOptionalTime"},"aggregate_id":{"type":"keyword"},"alert_time":{"type":"date","format":"dateOptionalTime"},"match_body":{"type":"object"},"match_time":{"type":"date","format":"dateOptionalTime"},"rule_name":{"type":"keyword"}}}}},"elastalert_past":{"mappings":{"_doc":{"properties":{"@timestamp":{"type":"date","format":"dateOptionalTime"},"aggregate_id":{"type":"keyword"},"match_body":{"type":"object","enabled":false},"rule_name":{"type":"keyword"}}}}},"elastalert_error":{"mappings":{"_doc":{"properties":{"@timestamp":{"type":"date","format":"dateOptionalTime"},"data":{"type":"object","enabled":false},"message":{"type":"text","fields":{"keyword":{"type":"keyword","ignore_above":256}}},"traceback":{"type":"text","fields":{"keyword":{"type":"keyword","ignore_above":256}}}}}}},"elastalert_silence":{"mappings":{"_doc":{"properties":{"@timestamp":{"type":"date","format":"dateOptionalTime"},"rule_name":{"type":"keyword"},"until":{"type":"date","format":"dateOptionalTime"}}}}}}

Can some one please help on this

The latest version of ElastAlert 0.2.X will not work for Elasticsearch v6.X. For Elasticsearch v6.X, you can try ElastAlert 0.1.39

@abhishekjiitr Thanka a lot. I check and let you know the update

@jayan800 there is a fork of this project on https://github.com/vsabelli/elastalert.
It aims to keep Python2 compatibility but getting the enhancements/features/bug-fixes of the original project. It currently works for ES6.8 (the version we are using in our company).
Have a look if you are interested!

Elastalert 0.2.x DOES work with ALL versions of Elasticsearch.

Thank you all. The issue has been resolved by changing the max_query value.

@jayan800 please tell me where to set the max_query value, as I am getting the same error


Support Autolinking

Description
This package's documentation implies that if you're using a RN version above 0.60, it supports autolinking. However, this is not the case. This package will not work on Android unless you run react-native link react-native-image-picker.
There is a similar issue with 3.0.0-vnext.3 right now I believe, where all calls to launchCamera and launchImageLibrary throw an error saying both of the native functions are null.
How to repeat issue and example

Create a new react native project
Install and use react-native-image-picker (DO NOT RUN react-native link)

Solution
Change the documentation, or support auto linking.
Additional Information

Image Picker version: 2.3.4 & 3.0.0-vnext.3
React Native version: 0.62.2
Platform: Android

The example app is even setup via a manual link:

This package uses autolink.
Don't compare it with example app inside this repo, that uses files from local folder not from node_modules. You have confused somewhere.
I tried in a fresh project auto link is working properly.


[BUG] Cant rewrite my settings in bloxstrap

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] My answer given in the checkbox above is a lie.

What problem did you encounter?
Everytime i try changing it i cant and it automatically opens roblox and i cant change it at all.

[!] My answer given in the checkbox above is a lie.

Did you read https://github.com/pizzaboxer/bloxstrap/wiki/Opening-the-Bloxstrap-menu?

Closed due to inactivity from OP.


lxd: Send operation progress when creating image or container.

Added metadata fields 'stage', 'percent', 'speed' to track
long running tasks in some operations.
In CreateImage, added stages 'create_image_from_container_tar'
and 'create_image_from_container_compress'.
In CreateContainerFromImage, added stage
'create_container_from_image_unpack'.
Modified images.go compressFile to take io.Reader and io.Writer
rather than a path name to allow imgPostContInfo to
supply an ioprogress.ProgressWriter that can track progress
of image compression.
Refactored imgPostContInfo to not require a separate pass
to determine the fingerprint when publishing an image from
a container.  The sha256 calculation is either done during
tar, or during compression.
Added tracker field in storageShared where callers can set
a ProgressTracker which is used when unpacking an image to
create new container in unpackImage and Unpack
Signed-off-by: Joel Hockey<EMAIL_ADDRESS>

Stéphane, I've split this into 5 different commits and made them separate pull requests.  I haven't used github much before, so I don't know if what I've sent is helpful.  I don't think there is a way for me to send the 5 different pull requests with dependencies on the previous.
I'll close this pull request now.

Hi Joel,
I was thinking keeping a single pull request but splitting things into multiple commits inside it which makes for easier review and then cherry-picking to stable.
But multiple pull requests will work too.
Stéphane


2nd function call argument 'buf' is a pointer to uninitialized value

2nd function call argument 'buf' is a pointer to uninitialized value
https://github.com/twitter/twemproxy/blob/c5c725d2b45715e378909ebc909b0492591c4715/src/nc_log.c#L257
'buf' initialized in line 209
if in line 223, the condition is false ,'buf' is a uninitialized value.

len = 0 means buf being initialized won't matter - this is inactionable


defaults aren't validated

expected behavior:
a schema like this:
..
  parameters:
   - name: number
     schema:
       type: integer
       default: "bad_default"

should error because the default is the wrong type.
(behavior also recently added to https://github.com/Yelp/swagger_spec_validator)

Hey @p1c2u , and ideas for how to implement this?
I'd be happy to work on this if you could give me some high-level guidance on how to get started.
AFAICT the type validation currently all happens in Draft4Validator, is that right?
I think in order to do this you'd need to call the Draft4Validator on the response example and schema somewhere in OperationValidator context?

Hey @dtkav I have fix prepared


Application error

Expected Behavior
Load new request from json
Actual Behavior
Can't insert key env_4e698cd2df805665c5e3cbbe5f72e9a73be8a233, it violates the unique constraint
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
version 2022.7.2
Insomnia Version
2022.7.2
What operating system are you using?
Windows
Operating System Version
Windows 10 Enterprise
Installation method
download from insomnia
Last Known Working Insomnia version
No response

Hi @kamaliamirthalingam1  thanks for reporting this, closing it as a duplicate of #5617


Self-Signed Certificate of the Huebridge (rectangle) Error message

Describe the bug
A clear and concise description of what the bug is.
I am using the rectangle Bridge and since a couple of days I see the following entries in the Node-Red Log:
25 Jun 14:20:36 - [info] [hue-bridge:Huebridge] Initializing the bridge (<IP_ADDRESS>)…
25 Jun 14:20:37 - [info] [hue-bridge:Huebridge] Error: self signed certificate
This leads to the Node does not work as desired. It only shows "connecting..." nothing more. I had this running earlier. But something broke this.
Flow to Reproduce
[
    {
        "id": "de63398919a2eaab",
        "type": "hue-bridge-node",
        "z": "abd3699b43c72ae4",
        "name": "",
        "bridge": "bc8d4785237d1937",
        "autoupdates": true,
        "skipglobalevents": false,
        "initevents": false,
        "x": 1130,
        "y": 80,
        "wires": [
            []
        ]
    },
    {
        "id": "bc8d4785237d1937",
        "type": "hue-bridge",
        "name": "Huebridge",
        "bridge": "xxx.xxx.xxx.xxx",
        "key": "removed due to security",
        "worker": "10",
        "autoupdates": true,
        "disableupdates": false
    }
]

Expected behavior
At least a switcht to aknowledge Self-Signed and ignore the Certificate error. Or at least switcht to http instead of https. As this is all local this should be fine.
Screenshots
https://imgur.com/a/LdetQRa
Please complete the following information:

Node-RED version: 3.0.2
NodeJS version: 16.9.1
Device running Node-RED: Raspberry

I did some research on my own based on what I found in the Code.
Based on Information from here there are certain Bridges that currently run with a self-signed certificate an others with a valid certificate issued by signify.
You can find my modifications within the attached api.js file.
I added row 5+6
and did changes on row
33 and 67
From my understanding you can provide to the https.Agent a specific CA File to be used for the request. This is what I am doing.
With this modification I was able to use the Node again :)
As I am not an experienced JS developer I leave this to you how to implement it in a proper way to the Node.
api.zip


MRG, ENH: Improve Epochs._name and Evoked.comment

Rework Epochs._name and Evoked.comment:

* replaced with × in Epochs._name

old: 0.50 * auditory/left + 0.50 * visual/left
new: 0.50 × auditory/left + 0.50 × visual/left

Evoked.comment in evoked differences created via mne.combine_evoked() now groups conditions via parens:

old: 1.500 × 0.50 * auditory/left + 0.50 * visual/left + -1.500 × × 0.51 * auditory/right + 0.49 * visual/right
new: 1.500 × (0.50 × auditory/left + 0.50 × visual/left) - 1.500 × (0.51 × auditory/right + 0.49 × visual/right)

special-casing for 1 and -1:

old: -1.000 × 0.50 * auditory/left + 0.50 * visual/left + 1.000 × 0.51 * auditory/right + 0.49 * visual/right
new: - (0.50 × auditory/left + 0.50 × visual/left) + (0.51 × auditory/right + 0.49 × visual/right)

Example using mne.viz.plot_compare_evokeds():
old:

new:

What do you think?
(btw unfortunately Evoked.comment cannot contain a proper minus character, as saving will fail then)

(btw unfortunately Evoked.comment cannot contain a proper minus character, as saving will fail then)

I'm surprised that it allows × but not −  ...  I'm guessing the FIF format encodes text in something bigger than ASCII but not as big as UTF-8?
BTW, this is still marked as draft.  LMK when it's ready for review.

I'm surprised that it allows × but not −

I could imagine that × gets mapped to ASCII 158?

BTW, this is still marked as draft. LMK when it's ready for review.

Just wanted to hear your general feeling about this before proceeding & fixing all tests etc :) So … no strong objections so far?
– Oh well, you know what, I'm just gonna mark this as ready for review :)

@hoechenberger is it ready for review now?  Several more commits were just pushed while I was mid-review.

e9dc642 fixes a bug that is present in main, related to the string representation / .comment of -Evoked:
main:
Evoked.comment: 0.50 * auditory/left + 0.50 * visual/left
-Evoked.comment: -0.50 * auditory/left + 0.50 * visual/left (minus sign only negates the first term)
with e9dc642
Evoked.comment: 0.50 × auditory/left + 0.50 × visual/left (unchanged except for multiplication signs)
-Evoked.comment: - (0.50 × auditory/left + 0.50 × visual/left) (minus sign correctly applied to all terms)

@hoechenberger is it ready for review now? Several more commits were just pushed while I was mid-review.

Oh noes, I'm sorry about this! It is ready for review now. Ouch … I owe you a review, I guess 😱

We're using proper minus signs now in the plot legend for plot_compare_evokeds() (replacing the ASCII hyphens with Unicode minuses)

Ouch … I owe you a review, I guess

Don't sweat it :)  But it's the end of my day now, so I'll have to wait until tomorrow morning

@larsoner I've added a changelog entry to the Enhancements section

The choice of Bugs was intentional, that is where we list backward-incompatible / breaking code changes without a deprecation period. So there must be an entry there. You could also have one in enhancements, but I don't see the point once you put one in Bugs...

The choice of Bugs was intentional, that is where we list backward-incompatible / breaking code changes without a deprecation period. So there must be an entry there. You could also have one in enhancements, but I don't see the point once you put one in Bugs...

I do see what you mean, and I agree that Enhancements might not be the right section. But the only reason to put it in Bugs is the historical argument you brought up – "we've always done it there in the past".
Can we not introduce a new section, Behavior changes, for stuff like that? or rename API changes to API and behavior changes? We've done exactly this in MNE-BIDS

But the only reason to put it in Bugs, IMHO, is the historical argument you brought up – "we've always put it there in the past".

I don't think of it as historical but rather as functional based on our current working definitions for each section: "Bugs" is where people should currently look for backward-incompatible changes that might break their code without any warning.

Can we not introduce a new section, Behavior changes, for stuff like that?

My response is the same as last time renaming changelog sections came up in a PR -- let's discuss in a dedicated issue/PR dedicated to that...

My response is the same as last time renaming changelog sections came up in a PR -- let's discuss in a dedicated issue/PR dedicated to that...

Believe it or not, but I had forgotten about the fact that we'd been there before … ouch.
Alright then :)

This should be good to merge now.

thx @hoechenberger !


PoliCheck failing due to existing code.

Hello,
I have created a pull request in repository: azure-rest-api-specs
Here is the PR link: https://github.com/Azure/azure-rest-api-specs/pull/19316
The pull request is failing the PoliCheck due to some words in the custom-words.txt file.
Although I have not added any invalid words in the PR but the file already contains some words.
I am not sure how to fix this check as removing existing words may cause breaking changes.
Can you please look into the issue?
If removing existing words will not cause any breaking change then can I remove the words and commit in my PR.

@ruowan didn't we fix this?

I think @tianxchen-ms have already fixed. Maybe you could resolve conflict and rerun the pipeline.

Hello, I have created a pull request in repository: azure-rest-api-specs Here is the PR link: Azure/azure-rest-api-specs#19316 The pull request is failing the PoliCheck due to some words in the custom-words.txt file. Although I have not added any invalid words in the PR but the file already contains some words. I am not sure how to fix this check as removing existing words may cause breaking changes. Can you please look into the issue? If removing existing words will not cause any breaking change then can I remove the words and commit in my PR.

@pansharm-ms , can you resolve branch conflicts in PR then re-run the CI checks?

Verified that the issue is no longer occurring when created a new PR with the latest code.
Closing the issue now.


Light copyedit

I am embarassed. Thanks for taking time out to fix the grammatical errors. @davorg

I am embarassed. Thanks for taking time out to fix the grammatical errors. @davorg


I prefer not making this change, as it is has the potential to break existing APIs that check for status: "fail" In addition to its verb usage, fail can be a noun per http://m-w.com/dictionary/fail

ISTM this is one of those cases where if we were starting from day 1, we might be inclined to go success|failure, but the cost to make the change (aka breaking backwards compatibility) seems higher than the value.

I prefer "fail" over failure. Although it might seem natural, the first is more understandable.


When i running the first command in the README , it comes an error.

when i run the command "python3 src/main.py --config=qmix_smac --env-config=sc2 with env_args.map_name=2s3z".The output is that
[ERROR 20:41:53] pymarl Failed after 0:00:00!
Traceback (most recent calls WITHOUT Sacred internals):
File "src/main.py", line 31, in my_main
env_args['seed'] = _config["seed"]
sacred.utils.SacredError: The configuration is read-only in a captured function!

Solved in https://github.com/oxwhirl/pymarl/commit/9be8cb078ffd05b55a2ee02842ed0ad4a3f28827.


Hide user role from discussion profile page.

Use theming instead of editing html/css in platform
@caesar2164 @stvstnfrd @tkim135

@saharm1 Fix the comment as noted, but otherwise this is good. I think you'll want to squash down to a single commit, then we can merge.

Thanks, @saharm1.
You should squash now!


post-synthesis simulation error

I tried to run post-synthesis functional simulation for the conter_arty test in xc7/tests by Modelsim. And I found that only the wave of led[0] was correct, other 7 led wires were always 0 (see Fig.1).
The only difference from your original test is modifying the verilog file to add a reset function. The code is as follows:
`module top (
input  wire clk,
input  wire [7:0] sw,
output wire [7:0] led

);
localparam BITS = 8;
localparam LOG2DELAY = 28;

reg [BITS+LOG2DELAY-1:0] counter = 0;

always @(posedge clk) begin
    if(!sw[0])
        counter <= 0;
    else
	    counter <= counter + 1;
end

assign led[7:0] = counter[7:0];

endmodule`
The post-synthesis file was generated by VPR, and the work libraries were  symbiflow-arch-defs/vpr/primitives.v and symbiflow-arch-defs/xc/xc7/techmap/cells_sim.v.
Is there something wrong with the simulation cells? Or is there something wrong with the simulation process?

Is there something in the documentation that needs to be updated to support your use case?  I see you closed the issue, but didn't mention how you resolved your issue.  It is a good idea to mention what solved you problem in these kind of cases.

Is there something in the documentation that needs to be updated to support your use case?  I see you closed the issue, but didn't mention how you resolved your issue.  It is a good idea to mention what solved you problem in these kind of cases.


Example does not output correctly

Hey there, I tried to run:
$array: (foo, bar, baz);

@each $val, $i in s, m, l  {
  .icon_size_$(val) {
    background: url('icons/$(array[$i]).png');
  }
}

but the $(array[$i]) is not being evaluated. Is there something I'm missing? I'm not certain if postcss-simple-vars supports that? Thanks!

Hey!
My fault, I've forgotten to fix the docs. Yep, it's impossible – postcss-simple-vars works with plain values only. Updated the readme.

@marthakelly Hey! Look at this https://github.com/outpunk/postcss-each/releases/tag/v0.6.0.


MISC - watch react-hook-form field value change

watch react-hook-form field value change to fix the reset function not working
update form-item props to leave control optional
added reset example to the example project

Fix #3

Thx for your PR!
https://github.com/jsun969/react-hook-form-antd/blob/56e65748338afe63f64f42ec2d73c781c0bef11a/example/src/App.tsx#L19
Please add an example here for reset

Hi @jsun969, here is the codesandbox example: https://codesandbox.io/s/falling-tree-mnwnhk?file=/src/FormItem.tsx

It seems I misunderstood your points, I'll update the example inside this repo.

sry for my late reply. Could you tell me why close this PR? 🥲

sry for my late reply. Could you tell me why close this PR? 🥲

Hey @jsun969, while doing the manual test after finishing the PR, I found there are still some problems between the new FormItem with react-form-hook, such as reset({}) not working as expected. I guess there might be something else that needs to be fixed, possibly related to initValue. However, I was not able to conduct a thorough investigation due to lack of time. Hence, I decided to close the PR as it was not complete. I believe you have the ability to figure out and resolve the issues on your own.


add back METRIC_BYTES_FROM_STMGRS

Related to #1908
Since the change from TupleStreamMessage to TupleStreamMessage2, the tuple structure information was lost, thus the following count cannot be fetched.

METRIC_BYTES_FROM_STMGRS
METRIC_BYTES_FROM_INSTANCES
METRIC_BYTES_TO_INSTANCES_LOST
METRIC_BYTES_TO_INSTANCES

I did not find the CachedByteSize() in protobuf.
There is SpaceUsed() which is noticeably slower than ByteSize()

@huijunw https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message_lite#MessageLite.GetCachedSize.details

thanks @objmagic

@huijunw we should use ByteSize instead of GetCachedSize. In fact, before https://github.com/twitter/heron/commit/557c9804af0c23952b3df7e29715f01e338884f8, we use ByteSize only.

@objmagic see the above comment, GetCachedSize was suggested @srkukarni

@srkukarni can you explain why we use GetCachedSize? I think its API description is not very clear. Will it return the correct current byte size of a message?

GetCachedSize returns the previously calculated GetByteSize. Thus in order for GetCachedSize to be valid, some one should have called GetByteSize and the message should not have been altered since then.
I am seeing that no one is calling GetBytesSize on HeronTupleSet. This means that GetCachedSize is likely incorrect.
Here is a proposal

In Stmgr-Server where stmgr first gets anything(either TupleStreamMessage from stmgr or HeronTupleSet from instance) we need to call GetByteSize().
Rest other places GetCachedSize should return the right values.
Can we see whats the perf impact of these changes?

@srkukarni makes sense. I was worried if we do not call ByteSize first we won't get correct value of GetCachedSize. Your proposal looks good. We need to carefully make sure ByteSize will be called at the very first. Then use GetCachedSize all the way until we release it.
For perf, we may need more time to fix the viz.


PRS environment setup

Output

Create an account and get API key in The Movie Database website.
Required Ubuntu packages are installed.
Python packages are installed successfully.
CPU, memory and network speed check while setup.
A Wiki document.

[20] PRS Setup

Modifications for Ubuntu 18.04 LTS

4039bd7

Note

2022/Dec/15: Add wiki link
2022/Dec/16: Add GitHub commit

Hello @quangvv9Life,
Task này tớ thấy output như mình mong muốn rồi.
Tớ sẽ closed lại nhé!!!
Thanks Quang.


Feature request: provide a default JSONWebKeyStore implementation

Is your feature request related to a problem? Please describe.
In order to create a new sdk.Verifier, you must provide your own JSONWebKeyStore implementation in the Datastore field of the sdk.Options struct. It may not be clear exactly how to do this.
Describe the solution you'd like
In sdk.New(), if no Datastore is provided, create a default in-memory cache. I would expect a small fixed size cache would be sufficient for most users.
Describe alternatives you've considered
n/a
Explain any additional use-cases
A default JSONWebKeyStore implementation would make it easier to provide a minimal example for correctly using the SDK.
Additional context
The verify service implements JSONWebKeyStore using the "github.com/hashicorp/golang-lru" package (cf. cache.go).

Makes sense to me.


Server error when accessing pages that reference built styles via webpack-loader

See https://github.com/Princeton-CDH/ppa-django/pull/363 for one instance of this problem, previously encountered only in CI. Although the styles build, loading a page that references them errors cryptically:
            for chunk in chunks:
>               asset = assets['assets'][chunk]
E               KeyError: 'assets'

Possibly caused by a particular set of node dependencies that resulted from https://github.com/Princeton-CDH/ppa-django/commit/98e726dc51a4d40249f1214430069c5351875354.

postmortem
this issue is caused by a particular relationship between django-webpack-loader (a python package) and webpack-bundle-tracker (a nodejs package), detailed in this part of the README for the former.
as of about 11 days ago, webpack-bundle-tracker published a 1.0.0 version that changed the format of the webpack-stats.json file that is output by webpack and that tells Django (via django-webpack-loader) where to find built static files (in our case the bundles/ folder). django-webpack-loader released a corresponding v1.0 to match this breaking change.
if the two packages have mismatched versions, the expected and actual format of webpack-stats.json will not match. this causes django-webpack-loader to error when parsing the JSON while attempting to construct a <script> or <link> tag to insert into pages that reference the built styles.
since our requirements.lock already specifies django-webpack-loader==1.0.0, the solution is to set webpack-bundle-tracker's spec to "webpack-bundle-tracker": "^1.0.0", in package.json, ensuring it cannot be below v1. the issue didn't appear when installing locally with npm install because our spec of "webpack-bundle-tracker": "^0.4.3", still allowed for the downloading/install of v1, but likely did appear in CI because there we use npm ci, which would have referenced an older version in package-lock.json.

Unfortunately, upgrading both django-webpack-loader and webpack-bundle-tracker doesn't completely solve this issue. Instead, a new error appears (copied from a deeply nested trace):
...
    for chunk in bundle:
  File "/var/www/ppa-django/env/lib/python3.5/site-packages/webpack_loader/loader.py", line 43, in filter_chunks
    for regex in self.config['ignores'])
  File "/var/www/ppa-django/env/lib/python3.5/site-packages/webpack_loader/loader.py", line 43, in <genexpr>
    for regex in self.config['ignores'])
TypeError: string indices must be integers

This same problem has been known since April 9 (https://github.com/django-webpack/django-webpack-loader/issues/227), and the recommended resolution was to pin django-webpack-loader back to v0.4.3.
Once v1 was released, however, the maintainers closed the issue, stating that upgrading both django-webpack-loader and webpack-bundle-tracker to v1 would resolve it. Unfortunately, this is not the case, verified in QA:
$ npm list webpack-bundle-tracker
ppa-django@ /srv/www/qa/ppa-django/3.6.1-0b934b
└──<EMAIL_ADDRESS>
(env) $ pip freeze | grep webpack
django-webpack-loader==1.0.0

...where the error still occurs, including after regenerating webpack-stats.json.
For now, it appears the only resolution is to pin django-webpack-loader back to v0.4.3 and ensure that webpack-bundle-tracker back to <1.

Confirm that 316cfae appears to have resolved this.


rewrite method lookup mechanisum

in current implementation, DSType maintain method handle.
Due to abort incompleted type (for supporting type definition), symbol table (or type pool)  should maintain method handle pointer.
require the following steps

merge TypePool with SymbolTable (#212)
refactor DSType (remove handle map from field)
rewrite type cache

related to #311


[VS Code] [Audio] Calling module not available. Cannot find module 'slimcore-2.0'

Error:
Calling module not available. Cannot find module 'slimcore-2.0'
Steps to Reproduce:

Version Data

extensionName
VSLS-Audio

extensionVersion
0.1.32

applicationName
VSCode

applicationVersion
1.26.1

platformName
MacOS

platformVersion
10.0.17134

@stefanstranger Hey! Could you try uninstalling the audio extension and reinstalling it? This issue may indicate that they install process failed for some reason. In the meantime, I’m going to close this as a duplicate of #827. Thanks!

Hi Jonathan,
I did and it solved the issue.
Thanks.
Stefan

Awesome! Thanks for confirming that.


🚸 Clarify language for required files (with references to examples)

Clarify language for required files (this ties into Policy Panda, too)
voting group: @commonhaus/cf-egc
Do one of the following:

Approve the PR or react with 👍 (:+1:) if it looks good to you
Review with Comments or react with 👀 (:eyes:) if you're "ok" with it (it may not be your favorite)
If you think it needs discussion or revision

Create a review, add your comments and require changes
Use the +- button to make a suggestion (instead of just adding a comment).

vote::result

after discussion with @jkschneider, we can/should proceed on some items without waiting for @timtebeek
otherwise, no disagreement


GA4 not compatible with Turbo?

I have a weird one.  Everything was working fine until I installed Google Analytics 4 (GA4).  Once I installed it, my turbo frame links are being followed instead of doing what they are suppose to do and just loading the response data.
Is anyone else having this issue and how did you solve it?

It seems to be related to GA4 automatically tracking outbound clicks.  When you shut that off it seems to work.

A couple random Stackoverflow posts also imply that if GA4 is implemented with google tag manager (gtm js), things should still work, but I haven't confirmed this personally.

I think it just "works". Again, haven't confirmed.
I have a UA site using gtm I was going to look into converting "soon" (since we have a year before UA goes away) and will give it a shot.
That said, at least there's an out for now with during off outbound clicks...

Enhanced Measurement in GA4 is not enabled by default, I think, which perhaps could explain why some people will see it just working.

grateful to have found this thank you!

I'm still experiencing this issue from the looks of it even today... Having the GTM tag in the <head> breaks the Turbo link visits and instead forces full page reload.

We are also experiencing this, we've disabled the "Enhanced measurement" feature in Google Analytics per the SO post above, and that has resolved it for now.
Interestingly we had this issue before, and like other commenters, it then "just worked" for a while and now it's back.

Same issue appears if you happen to use CloudFlare - it has a feature called Rocket Loader (https://developers.cloudflare.com/speed/optimization/content/rocket-loader/), which breaks Turbo in the same way (and it also adds new event listener for every link). Disabling the feature in CloudFlare fixed the problem.

I just integrated GA4 tracking in a Rails 7.1 app that uses Turbo Drive with a property that has "Enhanced Measurement" enabled by literally pasting the gtag.js code snippet just after <head> and and everything seems to be working.
Are you still seeing issues on the latest version of Turbo?

No issues for me with default GA4 config and Turbo. No hard reloads.

If anyone wants to document these compatibility issues in the turbo-site repo, I'd be happy to merge 👍

For those that were able to integrated GA4 tracking with Turbo Drive, how did you get it to work?
Because Turbo Drive relies on using a single, persistent process when navigating pages, the <script> element is only executed a single time. My experience when Turbo.Visit is driving the page click causes GA not to track the additional page views. I can confirm this when I check the network tab in developer tools after any page click, I don't see any requests that contain /collect?v=2. I can quickly find GA requests for the initial page load.
So far the only thing so far that has worked is to add data: { turbo: false } to the link_to helper that handles the page click.

I think the key to making it work when just including the script tag is to make sure "Enhanced Measurement" is enabled for the property. Then GA4 seems to automatically track pageview events based on the browser history events generated by Turbo Drive.

@tbcooney See the answer in the linked stackoverflow here as a starting point: https://github.com/hotwired/turbo/issues/572#issuecomment-1113339922
or alternatively, use the turbo:load event in place of the turbolinks variant as outlined here: https://gorails.com/episodes/gtag-js-with-turbolinks

Thanks @t27duck. Unfortunately, that is the exact script that is in place.
I've created this staging website to demonstrate the issue I'm facing. When I check the network tab in developer tools after any page click, I don't see any requests that contain /collect?v=2. I can quickly find GA requests for the initial page load.
For context, this is the same behaviour whether Enhanced Measurement is turned off or Enhanced Measurement is turned on with browser history-based events turned off -- any subsequent page view is not tracked.

So far the only thing so far that has worked is to add data: { turbo: false } to the link_to helper that handles the page click. That seems like a less than ideal solution as it requires developers to have quite an intimate understanding of the application and it's relationship with GA to follow this in practice when adding any new links in the future.

We also hit this issue while having GA4 served via GTM and after switching the Enhanced measurement in GA4 on.
We resolved the issue by disabling Enhanced measurement altogether but we noticed that enabling it and specifically disabling Outbound clicks + File downloads tracking worked for us too.


How to interpret (pinned handle) the output of !gcroot command?

[Enter feedback here]
How should i interpret when I see this in the output:
HandleTable:
00007F6C98BB15F8 (pinned handle)
I have an example output here:
0:000> !gcroot 000000322f1219b0
HandleTable:
0000003344471ff8 (pinned handle)
-> 00000032f9ae3968 System.Object[]
-> 00000030f9ed2f00 System.Collections.ArrayList
-> 00000031f9fccef8 System.Object[]
-> 00000031f9f27d18 SBUtils.TElByteArrayManager
-> 00000031f9f27d48 System.Collections.ArrayList
-> 000000332df9a220 System.Object[]
-> 000000322f121980 SBUtils.TElByteArrayInfo
-> 000000322f1219b0 System.Byte[]
SBUtils come from a third party SecureBlackbox.dll. Does "Pinned handle" mean that it is due to a reference from unmanaged to managed object?

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

ID: 2913d994-4c72-cc6e-0bd4-ba122ae21753
Version Independent ID: 03f3761e-be31-bae9-6ac7-ad86db389212
Content: Debug a memory leak tutorial
Content Source: docs/core/diagnostics/debug-memory-leak.md
Product: dotnet-fundamentals
GitHub Login: @tommcdon
Microsoft Alias: tommcdon

Does "Pinned handle" mean that it is due to a reference from unmanaged to managed object?

Yes, that it likely the case. See https://learn.microsoft.com/en-us/dotnet/framework/interop/copying-and-pinning.


Unable to generate HTML report.

Current behavior
Not able to generate HTML Reports . Please do let me know If I am missing any steps , and any resource to refer the same.
Desired behavior
Should Be able to generate HTML reports

Test code to reproduce
-Added as suggested by the documentation , attached details to Package.json

-I tried running my .feature file using cypress run/open .
-No HTML reports were generated for passed/failed TC .

Versions

Cypress version:^12.17.3
Preprocessor version:^18.0.5
Node version: 20.6.0

Checklist

[X] I've read the FAQ.
[X] I've read instructions for logging issues.
[X] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/docs/configuration.md

https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/docs/configuration.md
hey
I tried keeping the configuration as shown in the example.still not working :(

Then you need to provide a minimal, reproducible example issues that illustrates the issue.

Hey please find details below:
Issue :
Unable to Generate Json , HTML report after setting value as true in package.json file for the test suite.
Expected :
Should see a report generated in root folder after running npx cypress open/run once Test suite pass or fail
package.json
{
  "name": "minimal-code-example",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@badeball/cypress-cucumber-preprocessor": "^18.0.6",
    "@cypress/browserify-preprocessor": "^3.0.2",
    "cypress": "^13.2.0"
  },
  "cypress-cucumber-preprocessor": {
    "json": {
      "enabled": true
    }
  }
}

cypress.config.js
const { defineConfig } = require("cypress");
const {
  addCucumberPreprocessorPlugin,
} = require("@badeball/cypress-cucumber-preprocessor");
const {
  preprocessor,
} = require("@badeball/cypress-cucumber-preprocessor/browserify");

async function setupNodeEvents(on, config) {
  // This is required for the preprocessor to be able to generate JSON reports after each run, and more,
  await addCucumberPreprocessorPlugin(on, config);

  on("file:preprocessor", preprocessor(config));

  // Make sure to return the config object as it might have been modified by the plugin.
  return config;
}

module.exports = defineConfig({
  e2e: {
    baseUrl: "https://duckduckgo.com",
    specPattern: "**/*.feature",
    setupNodeEvents,
  },
});

Path for below files  .\Minimal Code example\cypress\e2e
duckduckgo.feature
Feature: duckduckgo.com
    Scenario: visiting the frontpage
        When I visit duckduckgo.com
        Then I should see a search bar

duckduckgo.js
const { When, Then } = require("@badeball/cypress-cucumber-preprocessor");

When("I visit duckduckgo.com", () => {
  cy.visit("https://duckduckgo.com/");
});

Then("I should see a search bar", () => {
  cy.get("input[type=text]")
    .should("have.attr", "placeholder")
    .and(
      "match",
      /Search the web without being tracked|Search without being tracked/
    );

  assert.deepEqual({}, {});
});

You need to provide a complete and runnable example, preferably in the form of a repository I can clone.

Hello ,
Please have a look  here https://github.com/Ljsam6/Minimal-Code-Example.git

Your example correctly generates a JSON report upon cypress run, which is expected. So what's the problem?

sorry my bad yes it is!!! but when I tried with cypress open it didn't work apparently .

but when I tried with cypress open it didn't work apparently .

Reports aren’t generated in interactive mode and this is explained in the FAQ.


Remove selection on longtap.

This removes the text selection that occurs on longtap due to the
standard iOS/Android behavior.
Fixes: #6480.

Just to confirm that I understand, is it still possible to select text from mobile, just it doesn't happen as well when you long-tap?  That seems good.  I'll test-deploy this to chat.zulip.org so we can get several folks to try it on their phones.

Deployed on chat.zulip.org.  @showell can you verify whether this works better?

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } It is better but it is still less than ideal and almost always tries to select text.
On Saturday, September 16, 2017, 3:03 AM, Tim Abbott<EMAIL_ADDRESS>wrote:
Deployed on chat.zulip.org. @showell can you verify whether this works better?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The only thing I can do past this is just remove the ability to copy/paste text at all on mobile.

This is definitely better than before, so I merged it.  I feel like we should start a thread on #design brainstorming ideas here.  @brockwhittaker can you do that?


Add language for translation - Latvian

Language To Add
Latvian

I saw that there is similar issue #2331
I could translate Bookstack to Latvian via Crowdin or other method. As far as I understand Crowdin is preffered.
@ssddanbrown

Thanks for offering to translate @aarchijs and thanks for the reminder and sorry for my really late reply.
I've added Latvian to the crowdin project. If you've changed your mind just let me know. If little translation progress is made after a couple of months I'll likely remove it from the project and it'll need to be re-requested.


fix(metrics): AttributeError raised by MediaManager and Typing and docs

Issue #, if available:
Description of changes:
Changes:

Correct typing to make mypy happier
Correct highlighted lines
fix(metrics): AttributeError raised when setting metadata_set

Checklist

[x] Meet tenets criteria
[x] Update tests
[x] Update docs
[x] PR title follows conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@heitorlessa  MyPy found a bug for us :)

Codecov Report

Merging #357 (fb6839a) into develop (4211796) will decrease coverage by 0.33%.
The diff coverage is 98.30%.

@@             Coverage Diff             @@
##           develop     #357      +/-   ##
===========================================
- Coverage    99.94%   99.61%   -0.34%
===========================================
  Files           96       96
  Lines         3642     3622      -20
  Branches       174      175       +1
===========================================
- Hits          3640     3608      -32
- Misses           0        7       +7
- Partials         2        7       +5

Impacted Files
Coverage Δ

aws_lambda_powertools/utilities/batch/base.py
100.00% <ø> (ø)

...wertools/utilities/idempotency/persistence/base.py
92.94% <ø> (-6.42%)
:arrow_down:

aws_lambda_powertools/utilities/parser/types.py
71.42% <50.00%> (-28.58%)
:arrow_down:

aws_lambda_powertools/logging/lambda_context.py
100.00% <100.00%> (ø)

aws_lambda_powertools/logging/logger.py
100.00% <100.00%> (ø)

aws_lambda_powertools/metrics/base.py
100.00% <100.00%> (ø)

aws_lambda_powertools/metrics/metric.py
100.00% <100.00%> (ø)

aws_lambda_powertools/metrics/metrics.py
100.00% <100.00%> (ø)

aws_lambda_powertools/shared/functions.py
100.00% <100.00%> (ø)

aws_lambda_powertools/utilities/batch/sqs.py
100.00% <100.00%> (ø)

... and 19 more

Continue to review full report at Codecov.

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


Update and rename social-image.md to outreach-hub.md

👷 Deploy Preview for famous-marshmallow-cfbd61 processing.

Name
Link

🔨 Latest commit
4368616ff54d64aef835a10ad0fad198b5c05f38

🔍 Latest deploy log
https://app.netlify.com/sites/famous-marshmallow-cfbd61/deploys/64db064ca3d87c000872a129


⚠ SceneTime has degraded performance

In e352bed, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2222 ms

Resolved: SceneTime performance has improved in 9805cdd after 6 minutes.


Will FEATURE override variables in CMakeLists.txt?

If yes, when? after patches?

You can check what variables will be affected by a feature by reading the portfile.cmake of the port.
In general the following steps occur when executing a portfile.

Download and extract sources.
(Optional) Apply patches.
(Optional) Evaluate features.
Configure CMake (this is when variables set by features are passed to CMake).
Build and install package.
(Optional) Fix CMake target files.
Clean up library output.
Run post-build validations.


Issue a XML signature with custom tags

Hi. First of all, thanks for your lib, in my initial test it work as expected.
Now, I'm looking to do a sightly different signature procedure, maybe you can enlighten me.
The tags used for the digital signature in your library are: Signature, SignedInfo, CanonicalizationMethod, SignatureMethod, etc...
I'm looking to renamed them like ds:Signature, ds:SignedInfo, ds:CanonicalizationMethod, ds:SignatureMethod, and so. Basically a prefix ds: in each tag.
How can I do this customization with your library? It is possible?
Also. before I finish the root tag Signature, additional signature fields has to be added. My XML file has a bit more complex structure, and those fields has an special signing procedure. I need to retrieve additional tags like ds:KeyInfo, <ds:X509Data, ds:X509Certificate, ds:KeyValue, ds:RSAKeyValue, ds:Modulus.
Is this possible (retrieve those extra tags with additional information of the signing process) with your library?
Where can I start for the customization.
Just in case, are you available to accept such paid customization job? Which is increase the information given for the sign procedure.
Thanks for your support and help.
Regards.

Hi @howdoyouturn69

I'm looking to renamed them like ds:Signature, ds:SignedInfo, ds:CanonicalizationMethod, ds:SignatureMethod, and so. Basically a prefix ds: in each tag. How can I do this customization with your library? It is possible?

Currently this is not support, but could be added as a new feature.

I need to retrieve additional tags like ds:KeyInfo, <ds:X509Data, ds:X509Certificate, ds:KeyValue, ds:RSAKeyValue, ds:Modulus.

These extra ds:KeyInfo element and all sub-nodes like ds:X509Data are also not supported.

Is this possible (retrieve those extra tags with additional information of the signing process) with your library?

This library provides only singing and validating functionality. To retrive such an XML node you could try to use the native PHP DOMXPath::query methods.

Where can I start for the customization.

This library does not provide much customization. When the community needs more features I will try to add it to the codebase.
As far as I know the robrichards/xmlseclibs provides all the features you are looking for. Have you already tried it?

Hi, thanks for your answers. yes I was capable to check robrichards work. And I decide to try yours first since it looks more clean, and easy to implement.
In any case, let me know if you're available for hire and customize.
Thanks.

I appreciate your support. Here is my Ko-fi and donate link.


Update to Senzing API V4 methods

Pull requests:

https://github.com/senzing-garage/sz-sdk-proto/pull/60


Feature/retrieve list of handlers

Coverage remained the same at 100.0% when pulling aecbba484aef552211196bdf7f9e8c72844e45c0 on feature/retrieve-list-of-handlers into 74c27f41eb39edb6b53894d684aec50cc60dc1a0 on develop.


Add %* format specifier

Split off from #614, which will let string interpolation be stabilized faster as it will be a purely compile time update.

Before I forget, we’ll also need to support %* in linter and type checker as both use format string parser to validate it and infer types, respectively.

Reminding myself

Should be noted that the FFlag only determines whether or not the format works. When merged, regardless of FFlag, %* will be treated as is with the type checker/linter.

Should be noted that the FFlag only determines whether or not the format works. When merged, regardless of FFlag, %* will be treated as is with the type checker/linter.

Yeah that's fine.


Document Queries From Product Requirements Document

User Story
As a ReportStream support engineer,
I want to understand how to query Azure Events,
so that I can create my own queries to help troubleshoot future issues
Description/Use Case
The Internal Message Monitoring PRD details TWO use cases that should be addressed by querying Azure Events (1.2.1 and 1.2.2. 1.2.3 is out of scope). We should implement sample queries that address these use cases. For example, create the following queries:

Give me a list of all messages that did not get sent anywhere that had a patient living in X state
Give me a list of all messages that got filtered out by X state. I want to see which filters failed.
Give me the original submitted report and the index of the item in that report for all items that got filtered out by receiver filters for X state so that I can easily identify which messages need to be resent through the pipeline after I fix an error with the receiver filters

Acceptance Criteria

[ ] Queries related to 1.2.1 and 1.2.2 tested and documented in the Azure Events document in the repo

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @brick-green @david-navapbc @jack-h-wang @jalbinson @JFisk42 @mkalish @thetaurean


Emit event when pod eviction is blocked due to pod disruption budget

Description
Have zero downtime for applications having single replica during consolidation/drift of underlined node
Very important (Blocker for adopting karpenter)
Hi,
We have cluster with development environments and each pod is a single replica. During the consolidation, Karpenter is deleting this single pod so it transforms to Terminating status and new pod is in Init status. Of course it cause downtime as new connections cannot be routed to Terminating pod.
We'd like to have some option to control how pods are rescheduled during consolidation. I think that maybe after node cordon, ideally we want to do rollout restart of pods instead of draining nodes.
I could see one pull request  regarding that which had been closed at the end of last year.
So can we do something regarding this? May be you can just emit a event from nodeclaim when it is about to be disrupted, we can catch the event from our own custom controller and do roleout restart of existing deployment and statefulsets which would reschedule the workloads in other nodes and then eventually karpenter would automatically taint and delete the existing node. We tried to follow this approach but what we seen that DisruptionBlocked event is being emitted continuously if app with 1 replica and PDB exist simultaneously  irrespective  of whether Node is disruptable or not. So we really can't run any logic based on DisruptionBlocked event and it's kind of a false alarm for us.
In a nutshell we need a event when actually node could not be disrupted (Not as a validation check like current DisruptionBlocked event ) because of presence of PDB. May be toggling the sequence of DisruptionBlocked and Unconsolidatable would help
Below is the sequence of existing events
  Normal  DisruptionBlocked  116s   karpenter  Cannot disrupt NodeClaim: pdb "cwe/nginx" prevents pod evictions
  Normal  Unconsolidatable   35s    karpenter  NodePool "default" has non-empty consolidation disabled

Can we disable this validation check conditionally based on some external NodePool configuration? We are hoping that if we can disable that somehow then later we can catch message here in form of some events when nodes are in hung state and rollout restart the deployments to unblock and and let the node get deleted?

What if we proceed with a rollout restart of the deployment if the current situation doesn't align with the PDB configuration?
The potential downside is that the pending pods from the restart might trigger the creation of new nodes, which could result in a never unstable environment.

Out of curiosity, I forked this repo and then commented out this validation check, and deploy that customised image in my cluster. I found out that a node (with app with single replica as well as PDB) is having below set of events in its corresponding nodeclaim. We can clearly see that node deletion is blocked for PDB violation. I guess DisruptionTerminating is key event here. When I did rollout restart of the existing deployment having one replica and PDB, it just gracefully scheduled the pod in other app and after that node got deleted.
So if we can get this request accepted then we can potentially  look for DisruptionTerminating  event from our custom controller and then just restart only those deploy/sts which are having one replica and PDB. For rest of the deploy/sts karpenter would automatically take care.
Not a nice solution but effective one
  Normal   Launched                34m                karpenter  Status condition transitioned, Type: Launched, Status: Unknown -> True, Reason: Launched
  Normal   DisruptionBlocked       34m                karpenter  Cannot disrupt NodeClaim: state node doesn't contain both a node and a nodeclaim
  Normal   Registered              33m                karpenter  Status condition transitioned, Type: Registered, Status: Unknown -> True, Reason: Registered
  Normal   Initialized             33m                karpenter  Status condition transitioned, Type: Initialized, Status: Unknown -> True, Reason: Initialized
  Normal   Ready                   33m                karpenter  Status condition transitioned, Type: Ready, Status: Unknown -> True, Reason: Ready
  Normal   DisruptionBlocked       27m (x3 over 31m)  karpenter  Cannot disrupt NodeClaim: state node is nominated for a pending pod
  Normal   Unconsolidatable        11m (x2 over 26m)  karpenter  SpotToSpotConsolidation is disabled, can't replace a spot node with a spot node
  Normal   DisruptionTerminating   9m14s              karpenter  Disrupting NodeClaim: Drifted/Replace
  Warning  FailedConsistencyCheck  4m                 karpenter  can't drain node, PDB "cwe/nginx" is blocking evictions
  Normal   ConsistentStateFound    4m                 karpenter  Status condition transitioned, Type: ConsistentStateFound, Status: True -> False, Reason: ConsistencyCheckFailed, Message: Consistency Check Failed
  Normal   DisruptionBlocked       35s (x6 over 10m)  karpenter  Cannot disrupt NodeClaim: state node is marked for deletion

Hey, can you control this on the pod level by having maxUnavailable = 0 and maxSurge = 1 ? To make K8s create a new pod first before proceeding with removing the previous?

@hdimitriou No that's not possible. k8s evict apis (which karpenter follows) does not respect maxUnavailable = 0 and maxSurge = 1. Before creating a new pod it would delete the existing pod

@jwcesign, are there any updates on the community review of that? Current behaviour breaks zero downtime on the pod moving between nodes. Karpenter should wait until new pods are marked as healthy before destroying old ones.

@indra0007

No that's not possible. k8s evict apis (which karpenter follows) does not respect maxUnavailable = 0 and maxSurge = 1. Before creating a new pod it would delete the existing pod

Hi,
I have a similar situation where I have an application with a single replica and I can't perform rebalancing without downtime. Are there any hacks or workarounds? For example, using preStop or terminationGracePeriodSeconds so that Kubernetes runs a new pod in parallel (handled by the deployment) while the old one is still alive for the time needed to start the new one.
I've also seen similar issues, but they mentioned custom controllers and handlers:

https://github.com/aws/karpenter-provider-aws/issues/500
https://github.com/aws/karpenter-provider-aws/issues/6086

We are also thinking of creating custom controller to handle it, but currently we need some event based on which we trigger the controller working and what this thread about.
Once this will close we can also plan to opensource it.


[entropy_src] software poll mode operations

Description
FW Override after Observe FIFO (32x32) practically enables poll mode of operations. Are there any changes needed to implement following mode:

Enable FW override to read data (but not write).
Disable path starting with precon packer, conditioner to reduce power
Disable interrupts from entropy source
Use status register to detect that observe FIFO has at least 32 bits to read. Can OBSERVE_FIFO_DEPTH register be it? Any tests for its correctness?
Read from FIFO ( via fw_ov_rd_data.d) kicks new bits from entropy source to forego health checks and be added to FIFO
Health checks can run, report alerts available to firmware, but do not stop random bits from being added to FIFO
When FIFO is full, stop the entropy source to reduce power consumption

I suppose there should be some signal to CSRNG that entropy is not available (es_entropy_valid?).
What about same as above, but on step 4 read is from entropy_data.d?

This hopefully answers some of your questions: https://opentitan.org/book/hw/ip/entropy_src/doc/programmers_guide.html#firmware-override--bypass-modes @vsukhoml

@vogelpi , thanks!  FW override mode is most likely what I'm looking for, but few more specific questions:

When Startup health testing is not yet completed (e.g., entropy source was complete disabled, and now enabled) and one or all health tests are enabled, will Observe FIFO be getting anything or these samples will be dropped until required number of samples is tested?  If firmware plans to implement additional checks, it would be more correct to receive all samples.

I assume that if fw disables health test, then Observe FIFO will immediately start receiving samples. Is it correct?

@vogelpi , thanks! FW override mode is most likely what I'm looking for, but few more specific questions:
1. When [Startup health testing](https://opentitan.org/book/hw/ip/entropy_src/doc/theory_of_operation.html#startup-health-testing) is not yet completed (e.g., entropy source was complete disabled, and now enabled) and one or all health tests are enabled, will Observe FIFO be getting anything or these samples will be dropped until required number of samples is tested?  If firmware plans to implement additional checks, it would be more correct to receive all samples.

Please note the difference between Firmware Override: Observe and Firmware Override: Extract & Insert mode (yes I did come up with these names and they are probably not the best but I had to better distinguish them in the design and doc when starting working on this). The Observe FIFO will always get the samples independent of which Override mode is running. But when running in Extract & Insert, no startup testing is performed (the assumption is that software needs to do that). When running in Observe mode, the startup testing is performed by the hardware.

2. I assume that if fw disables health test, then Observe FIFO will immediately start receiving samples. Is it correct?

The only way to "disable" the health tests is configuring very relaxed thresholds.


[WIP] New decorator with accessibility

⚠ This is WIP and I am sending this out to discuss possible implementation approaches.

Contributes to #2750 - decorator with enhanced accessibility
What did you change?

Add one more decorator variants with a second user interaction interface <button>, which could play the same role as pointer-right-click(onContextMenu).
Round shaped decorator. It can replace deprecated <Pill>.

How did you test and verify your work?

Keep original jest test cases with additional tests on the 2nd <button>.
Keep original storybook stories while adding some new stories showcase 2nd <button>.

Hello 👋 while I am migrating the new decorator code base, I am wondering whether we need some feature flag for people don't want the new round-shaped decorator? Like in [this style file line](https://github.com/liunate/ibm-cloud-cognitive/blob/a04bc55da2767e10605fcd7e79bd617dc9a6c4af/packages/security/src/components/DataDecorator/_index.scss#L16
https://github.com/carbon-design-system/ibm-cloud-cognitive/blob/a04bc55da2767e10605fcd7e79bd617dc9a6c4af/packages/security/src/components/DataDecorator/_index.scss#L16) some overriding rules making decorator border looks round followed. Will it be a good idea to leave the option to consumers whether they want to move over to new decorator look, or stay at original square-shaped decorator?
FYI you can see new decorator in action by spinning up storybook and go to:
iframe.html?knob-Active (`active`)=true&knob-Link (`href`)=&args=&id=decorator--default

@amtoussam @jlongshore I just checked up on the PR status and I'm wondering if there's anything else I can help to progress this PR? Tks~

@liunate There are conversations designers are having with each other but this implementation. I hope to have an answer for you by next week.
CC: @jlongshore

@amtoussam - have you synced with Jamie, Cameron, or whoever else needed to be involved? I know Jamie is planning to do a design review ASAP.

The decorator should not have an underline on hover, as per HTML standards this is not a link as it opens the right side panel after clicking it.

https://user-images.githubusercontent.com/130777697/232563127-cdc12402-0667-41c0-9bc3-6f0b1cea9c69.mov

I didn't see if the left-click context menu was available in the repo.

decorator should not have an underline on hover

The underline is only drawn when the right part of decorator alone is clickable to match existing decorator behavior and the new purposed design in figma
Do we want to change that to better match HTML standard?

I didn't see if the left-click context menu was available in the repo.

There are two reasons it's not part of this PR:

Carbon haven't had their Menu component ready for production(still in experiment).
I saw various decorator usages: with or without context menu(by various libraries). It seems to me decorator could be one general component that we don't force the context menu, or that context menu could be attached by decorator consumer by their own needs.

decorator should not have an underline on hover

The underline is only drawn when the right part of decorator alone is clickable to match existing decorator behavior and the new purposed design in figma
Do we want to change that to better match HTML standard?

Hey Nate, yes! Design has given this some thought as we want to move toward links being navigational, so removing the underline on hover and click will work well in this case.

if we don't have a context menu showing when the user clicks the left side of the decorator button, what happens?

Current implementation leaves the decision to new decorator consumer. The reason is mentioned here.
The biggest obstacle here is we don't have a context menu in shared code base. Current decorator users are using their own menu implementation(home-brewed, external libraries). By leaving the decision of what to do at click to them, they can keep their current implementation. It's also when Carbon menu is ready for production, we could enhance new decorator with that to provide a built-in menu feature on new decorator.

@jgodin2023

@liunate Any updates on this progress?

hi @elycheea sorry for the delay, I was busy with another assignment but will definitely progress this 1st thing next week.

What I plan to do is:

Rebase to keep good base of this PR head branch
Remove the underline per previous design comment
Check back here again see if we could move on next stage

As a side note, I just reviewed latest carbon menu and it is now production ready. That menu could be the next thing we could include in this component given that context menu is the common decorator use case.

What I plan to do is:

Rebase to keep good base of this PR head branch
Remove the underline per previous design comment
Check back here again see if we could move on next stage

@elycheea @jgodin2023 I just rebased and updated the component by previous comment. Let me know if there's anything else needs to be done to proceed with this PR. Many thanks!

@jgodin2023 I’m running the checks now so once they all pass, there should be a new preview if you could re-review. @jlongshore and I can help with the review from here. Thank you!

@elycheea tks for triggering the CI run for me and it's obvious I missed some linting and snapshot things, so I just fixed them right away. What's still blocking is I saw there are couple a11y test failures from c4p that does not seem to be related in any way to the security Decorator  I am working on. These three c4p test cases all failed at the a11y:
@carbon/ibm-products:  FAIL  src/components/EditSidePanel/EditSidePanel.test.js (14.743 s)
@carbon/ibm-products:   ● EditSidePanel › has no accessibility violations

@carbon/ibm-products:  FAIL  src/components/CreateSidePanel/CreateSidePanel.test.js (15.734 s)
@carbon/ibm-products:   ● CreateSidePanel › has no accessibility violations

@carbon/ibm-products:  FAIL  src/components/APIKeyModal/APIKeyModal.test.js (18.969 s)
@carbon/ibm-products:   ● APIKeyModal › has no accessibility violations

I can reproduce the same locally by running yarn run ci-check:test:c4p. Then I logged the rendered DOM to another browser tab and ran DevTool IBM achecker, it shows me the same violation as above.
    await wait(3000);
    screen.logTestingPlaygroundURL()screen.logTestingPlaygroundURL();

I know at this moment these packages c4p and security are configured independent versioning, and c4p could only actively maintained at another branch main instead of main_v1. Could that be the reason over time package c4p on main_v1 generating more a11y violation as accessibility check rule updated? Or are those a11y or whatever test fails in that c4p package not something we care about for this PR head branch based on main_v1?

@liunate I can help look into the that — I think it’s this issue that we fixed in main (#3177) but might not have opened a PR for main_v1 yet.
I think better to keep it as a separate PR that we merge before this one so you can keep the PR scope small here. Will let you know once we address it!

We merged https://github.com/carbon-design-system/ibm-products/pull/3233 this morning — this should resolve the issue now. 🤞

We merged #3233 this morning — this should resolve the issue now. 🤞

@elycheea Thanks for the prompt fix 🙏 Just ran all tests locally again and all passed, so could you please help trigger another round of CI check?

Hello there~ just checking in and wondering if there's anything else needed to move forward with this PR? Tks~


Add Sourcemap in Karma files

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          66     70    +4
=====================================
+ Hits           66     70    +4

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Broken IGNORE/REJECT metrics

Describe the bug
Starting from v1.10.0 we're not able to see IGNORE/REJECT by topics, instead it's just IGNORE/REJECT in general. This is likely an issue of gossipsub after we upgraded in v1.10.0

This is from unstable 1k node

This is from stable test mainnet node

Expected behavior
Should be able to view IGNORE/REJECT messages by topic
Steps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.10.0

This is a breaking change from https://github.com/ChainSafe/js-libp2p-gossipsub/pull/433/files
with this change, it's not possible to know which topic has % of ignore/reject/accept

waiting for #5869 to update these metrics on grafana

closed via #5899


Contact Matching within Summit Events - Manual intervention when matching on multiples

Hi Awesome Developers and Community Members!
We are using native Salesforce Duplicate and Matching Rules in coordination with Summit Events.  It works great, but I raise one use case where I'm hoping to get help.  When Salesforce finds more than one possible match on the criteria, can it create the Registration record and have a person come in later and manually match it to a Contact?  I explain more the use case below.
Use Case - Multiple Matches
We have multiple, but different people named John Sullivan in the Class of 1950 for example.

I register for the Event providing First Name, Last Name, Class Year and other data that is part of our Matching Rules.

The Summit Events registration processes and connected to one of the Contact records.  I am not sure how it picked the record, but the ideal scenario would be for someone to come through and matched it with a finer examination.
If I created this Contact record within Salesforce on the Contact object, I would receive the Alert (if selected within the Duplicate rule) and the possible matches.

Would there be any way to block the Contact matching if there are multiple matches and have users come in later and manually add?

Please let me know if you have any clarifying questions!
Have a great weekend!
Mike

Closed by merge #212


Autocomplete bound not working

I want to get suggestions restricted to a city (Bangalore, India). How to do that?

@adarsh10 Hi!
First of all, be sure that you use the last released version of jquery-locationpicker-plugin.
And the second one: here is my answer for the same question.

If you have a similar question - reopen that issue


<EMAIL_ADDRESS>

Hi @pcgandhinj466 the issue does not have any information. Closing this. Please open a new issue with information.


Meta: Plan the project via github issues, do milestones

@ct-jensschulze  JVM based SUNRISE has fairly elaborated issue  lists,  a little less detailed may be enought, but we need some planning
An opinions here?

Created some milestones and assigned them to the issues


Barcode would not print reliably on TM81

Just couldn't get barcodes to print reliably or completely on the TM81.
Looking at the docs
http://nicholas.piasecki.name/blog/wp-content/uploads/2009/12/ESC-POS-Command-Gu
ide.pdf  printing a barcode
to print

1. ASCII GS k md1...dk NUL
 Hex. 1D 6B md1...dk NUL
 Decimal 29 107 md1...dk NUL
2. ASCII GS k m nd1...dk
 Hex. 1D 6B m nd1...dk
 Decimal 29 107 m nd1...dk

1. 0 ≤ m ≤ 6 The definition region of k and d differ according to the bar
code type.
 2. 65 ≤ m ≤ 73 The definition region of n and d differ according to the bar code type.

Which boils down to the character string being printed if you use option 1,
needs a NULL terminator.  Option 2 the leading byte says how long the string
will be.

I opted for option 1, and include NUL  '\x00' at the end of the string.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 31 May 2013 at 4:13

Should be fixed with #98.


Fixed #29584 -- Implemented get_many() in django.core.cache.backends.db

https://code.djangoproject.com/ticket/29584

Did you consider trying to avoid much code duplication between get() and get_many()?

@timgraham
    def get(self, key, default=None, version=None):
        cache_dict = self.get_many([key], version=version)
        value =  cache_dict.get(key)

        if value is None:
            return default
        else:
            return value

How about modifying get() as above?
Could you give me some advice

@MyungSeKyo some databases won't optimize IN (1,) to = 1 so we might still want to teach get_many to use = when len(keys) == 1.

@charettes
Thanks for the advice!
It is better to fix it that way.
I think I can fix it.

I rebased latest but

For future reference, that error happens sometimes, especially if your branch contains multiple commits. Try again and it will usually resolve (and it's not really important if one or two builds fail with that error). Avoid creating multiple PRs because then we lose the comment history.